Skip to content

Commit 42dd1ce

Browse files
major doc cleanup (grammarly)
1 parent 4aae0a2 commit 42dd1ce

File tree

11 files changed

+107
-150
lines changed

11 files changed

+107
-150
lines changed

README.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,13 @@
1111
[![License](https://img.shields.io/pypi/l/sopa.svg)](https://github.com/gustaveroussy/sopa/blob/master/LICENSE)
1212
[![Imports: isort](https://img.shields.io/badge/imports-isort-blueviolet)](https://pycqa.github.io/isort/)
1313

14-
Built on top of [SpatialData](https://github.com/scverse/spatialdata), Sopa enables processing and analyses of image-based spatial-omics using a standard data structure and output. We currently support the following technologies: Xenium, MERSCOPE, CosMX, PhenoCycler, MACSIMA, Hyperion. Sopa was designed for generability and low-memory consumption on large images (scales to `1TB+` images).
14+
Built on top of [SpatialData](https://github.com/scverse/spatialdata), Sopa enables processing and analyses of image-based spatial-omics using a standard data structure and output. We currently support the following technologies: Xenium, MERSCOPE, CosMX, PhenoCycler, MACSIMA, Hyperion. Sopa was designed for generability and low memory consumption on large images (scales to `1TB+` images).
1515

16-
The pipeline outputs contain: (i) Xenium Explorer files for interactive visualization, (ii) a HTML report for quick quality controls, and (iii) a SpatialData `.zarr` directory for further analyses.
16+
The pipeline outputs contain: (i) Xenium Explorer files for interactive visualization, (ii) an HTML report for quick quality controls, and (iii) a SpatialData `.zarr` directory for further analyses.
1717

1818
# Documentation
1919

20-
The easiest way to getting started with `sopa` is to check [our documentation](https://gustaveroussy.github.io/sopa). It contains installation explainations, CLI/API details, and usages examples.
20+
The easiest way to start with `sopa` is to check [our documentation](https://gustaveroussy.github.io/sopa). It contains installation explanations, CLI/API details, and tutorials.
2121

2222
# Overview
2323

@@ -30,12 +30,12 @@ The following illustration describes the main steps of `sopa`:
3030
# Installation
3131

3232
### PyPI installation
33-
Sopa can be installed via `PyPI` on all operating system. Make sure you have an environment with `python==3.10` (more versions will be soon supported), and run the following command:
33+
Sopa can be installed via `PyPI` on all operating systems. Make sure you have an environment with `python==3.10` (more versions will be soon supported), and run the following command:
3434
```
3535
pip install sopa
3636
```
3737

38-
To install extras (for example if you want to use `snakemake`/`cellpose`/`baysor`/`tangram`), please run:
38+
To install extras (for example, if you want to use `snakemake`/`cellpose`/`baysor`/`tangram`), please run:
3939
```
4040
pip install 'sopa[snakemake,cellpose,baysor,tangram]'
4141
```
@@ -46,15 +46,15 @@ Important: even though `pip install 'sopa[baysor]'` will install some dependenci
4646

4747
You can clone the repository and run one of these command lines at the root of `sopa`:
4848
```
49-
pip install -e . # dev mode installation
49+
pip install -e . # dev mode installation
5050
poetry install # poetry installation
5151
```
5252

5353
# Features
54-
Sopa comes with three different flavors, each corresponding to a different use case:
54+
Sopa comes in three different flavours, each corresponding to a different use case:
5555
- `Snakemake pipeline`: choose a config, and run our pipeline on your spatial data in a couple of minutes
56-
- `CLI`: use our command-line-interface to prototype quickly your own pipeline
57-
- `API`: use directly `sopa` as a python package for full flexibility and customization
56+
- `CLI`: use our command-line-interface for prototyping quickly your own pipeline
57+
- `API`: use directly `sopa` as a Python package for complete flexibility and customization
5858

5959
### Snakemake pipeline
6060

@@ -69,7 +69,7 @@ For more details on `snakemake` configuration and how to properly setup your env
6969

7070
### CLI
7171

72-
Below are example of commands that can be run with the `sopa` CLI:
72+
Below are examples of commands that can be run with the `sopa` CLI:
7373

7474
```bash
7575
> sopa --help # show command names and arguments
@@ -81,7 +81,7 @@ Below are example of commands that can be run with the `sopa` CLI:
8181
> sopa explorer write merscope_directory.zarr # convert for interactive vizualisation
8282
```
8383

84-
For a full description of the CLI, please refer to the [documentation](https://gustaveroussy.github.io/sopa/cli).
84+
For a complete description of the CLI, please refer to the [documentation](https://gustaveroussy.github.io/sopa/cli).
8585

8686
### API
8787

@@ -91,21 +91,21 @@ import sopa
9191
# use the 'sopa' python package
9292
```
9393

94-
For a full description of the API, please refer to the [documentation](https://gustaveroussy.github.io/sopa).
94+
For a complete API description, please refer to the [documentation](https://gustaveroussy.github.io/sopa).
9595

9696
# Cite us
9797
Our article is not published yet. In the meantime, you can cite our [preprint](https://www.biorxiv.org/content/10.1101/2023.12.22.571863v1):
9898

9999
```txt
100100
@article {Blampey2023.12.22.571863,
101-
author = {Quentin Blampey & Kevin Mulder et al.},
102-
title = {Sopa: a technology-invariant pipeline for analyses of image-based spatial-omics},
103-
elocation-id = {2023.12.22.571863},
104-
year = {2023},
105-
doi = {10.1101/2023.12.22.571863},
106-
publisher = {Cold Spring Harbor Laboratory},
107-
URL = {https://www.biorxiv.org/content/early/2023/12/23/2023.12.22.571863},
108-
eprint = {https://www.biorxiv.org/content/early/2023/12/23/2023.12.22.571863.full.pdf},
109-
journal = {bioRxiv}
101+
author = {Quentin Blampey & Kevin Mulder et al.},
102+
title = {Sopa: a technology-invariant pipeline for analyses of image-based spatial-omics},
103+
elocation-id = {2023.12.22.571863},
104+
year = {2023},
105+
doi = {10.1101/2023.12.22.571863},
106+
publisher = {Cold Spring Harbor Laboratory},
107+
URL = {https://www.biorxiv.org/content/early/2023/12/23/2023.12.22.571863},
108+
eprint = {https://www.biorxiv.org/content/early/2023/12/23/2023.12.22.571863.full.pdf},
109+
journal = {bioRxiv}
110110
}
111111
```

docs/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
# `Sopa` documentation
22

3-
The documentation is generated by [Mkdocs material](https://squidfunk.github.io/mkdocs-material/) and deployed when pushing a new tag on Github.
3+
The documentation is generated by [Mkdocs material](https://squidfunk.github.io/mkdocs-material/) and deployed when pushing a new tag on GitHub.
44

55
## Serve locally
66

7-
Clone the repository, and install all the dependencies:
7+
Clone the repository and install all the dependencies:
88

99
```
1010
poetry install --all-extras
@@ -19,4 +19,4 @@ You can also update the CLI docs (if you install `typer-cli`) with the following
1919

2020
```sh
2121
typer sopa.main utils docs --output tmpfile --name sopa && sed '1,2d; s/## /### /g; s/Usage:/!!! note '\"'Usage'\"'/g' tmpfile >> docs/cli.md && rm tmpfile
22-
```
22+
```

docs/cli.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22

33
## Usage
44

5-
When installing `sopa` are written in our [getting-started guidelines](../getting_started), a new command named `sopa` becomes available.
5+
When installing `sopa` as written in our [getting-started guidelines](../getting_started), a new command named `sopa` becomes available.
66

77
!!! note "CLI helper"
8-
Run `sopa --help` to get details about all the command line purpose. You can also use this helper on any subcommand, for instance `sopa read --help`.
8+
Run `sopa --help` to get details about all the command line purposes. You can also use this helper on any subcommand, for instance, `sopa read --help`.
99

1010
<div class="termy">
1111
```console
@@ -17,7 +17,7 @@ $ sopa --help
1717
│ annotate Perform cell-type annotation │
1818
│ check Run some sanity checks │
1919
│ crop Crop an image based on a user-defined polygon │
20-
│ explorer Convertion to the Xenium Explorer's inputs │
20+
│ explorer Conversion to the Xenium Explorer's inputs │
2121
│ patchify Create patches with overlaps │
2222
│ read Read any technology + write a SpatialData object │
2323
│ report Create a web-report with figures/QCs │
@@ -34,7 +34,7 @@ $ sopa segmentation cellpose sdata.zarr
3434

3535
If you don't know in which order to run these commands, refer to the image in the [homepage](..), or see our [CLI usage tutorial](../tutorials/cli_usage).
3636

37-
When running the `sopa` CLI, some arguments are required while some are optional. For instance, for the `sopa read` command, `sdata_path` is an argument and a path has to be given directly, while `technology` is an option, and in this case the `--technology` prefix has to be used. For instance, if you read MERSCOPE data, it will be:
37+
When running the `sopa` CLI, some arguments are required, while some are optional. For instance, for the `sopa read` command, `sdata_path` is an argument, and a path has to be given directly, while `technology` is an option (in this case, the `--technology` prefix has to be used). For instance, if you read MERSCOPE data, it will be:
3838

3939
```
4040
sopa read /path/to/merscope/directory --technology merscope

docs/faq.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ You need the raw inputs of your machine, that is:
44

55
- One or multiple image(s), usually corresponding to one or multiple `.tiff` file(s)
66

7-
- Optionally a file of transcript location, usually a `.csv` or `.parquet` file
7+
- Optionally, a file of transcript location, usually a `.csv` or `.parquet` file
88

9-
In our tutorials, we use `data_path` to denote the path to your raw data. Select the right tab below to understand what is the right path to your raw data:
9+
Our tutorials use `data_path` to denote the path to your raw data. Select the correct tab below to understand what is the right path to your raw data:
1010

1111
=== "Xenium"
1212
`data_path` is the directory containing the following files: `morphology.ome.tif` and `transcripts.parquet`
@@ -21,16 +21,16 @@ In our tutorials, we use `data_path` to denote the path to your raw data. Select
2121
=== "Hyperion"
2222
`data_path` is the directory containing multiple `.ome.tiff` files (one file per channel)
2323

24-
## Cellpose is not segmenting enough cells, what should I do?
24+
## Cellpose is not segmenting enough cells; what should I do?
2525

2626
- Maybe `min_area` is too high, and all the cells are filtered because they are smaller than this area. Remind that, when using Cellpose, the areas correspond to pixels^2.
2727
- This can be due to a low image quality. If the image is too pixelated, consider increasing `gaussian_sigma` (e.g., `2`) under the cellpose parameters of our config. If the image has a low contrast, consider increasing `clip_limit` (e.g., `0.3`). These parameters are detailed in [this example config](https://github.com/gustaveroussy/sopa/blob/master/workflow/config/example_commented.yaml).
2828
- Consider updating the official Cellpose parameters. In particular, try `cellprob_threshold=-6` and `flow_threshold=2`.
2929

3030
## Can I use Nextflow instead of Snakemake?
3131

32-
Nextflow is not supported yet, but we are working on it. If you want, you can also help re-writing our Snakemake pipeline for Nextflow.
32+
Nextflow is not supported yet, but we are working on it. You can also help re-write our Snakemake pipeline for Nextflow.
3333

34-
## I have another issue, how to fix it?
34+
## I have another issue; how do I fix it?
3535

36-
Don't hesitate to open an issue on [Sopa's Github repository](https://github.com/gustaveroussy/sopa/issues), and detail your issue with as much precision as possible, in order for the maintainers to be able to reproduce it.
36+
Don't hesitate to open an issue on [Sopa's Github repository](https://github.com/gustaveroussy/sopa/issues), and detail your issue with as much precision as possible for the maintainers to be able to reproduce it.

docs/getting_started.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Choose one of the following, depending on your needs (it should take at most a f
4949

5050
## Snakemake setup
5151

52-
To use the Snakemake pipeline, the installation process is slightly different, because you'll need the full repository.
52+
To use the Snakemake pipeline, the installation process is slightly different because you'll need the whole repository.
5353

5454
1. Clone the `sopa` repository, and move to the root of the project:
5555
```sh
@@ -71,12 +71,12 @@ pip install -e ".[snakemake,cellpose,baysor,tangram]"
7171
Now, follow our [snakemake tutorial](../tutorials/snakemake) to run your first pipeline.
7272

7373
!!! Note
74-
You can also use a separate environment for `snakemake`. In this case, you don't need to install the `'snakemake'` extra when installing `sopa`. But you may still need to install other extras, for instance `'cellpose'` if you plan to run Cellpose.
74+
You can also use a separate environment for `snakemake`. In this case, you don't need to install the `'snakemake'` extra when installing `sopa`. But you may still need to install other extras, for instance, `'cellpose'` if you plan to run Cellpose.
7575

7676
## Usage
7777

78-
Sopa comes with three different flavors, each corresponding to a different use case:
78+
Sopa comes in three different flavours, each corresponding to a different use case:
7979

80-
- `Snakemake pipeline`: choose a config, and run our pipeline on your spatial data in a couple of minutes. See our [snakemake tutorial](../tutorials/snakemake).
80+
- `Snakemake pipeline`: choose a config, and run our pipeline on your spatial data in a few minutes. See our [snakemake tutorial](../tutorials/snakemake).
8181
- `CLI`: use our [command-line-interface](../tutorials/cli_usage) to prototype quickly your own pipeline
82-
- `API`: use directly `sopa` as a python package for full flexibility and customization (see a tutorial [here](../tutorials/api_usage))
82+
- `API`: use directly `sopa` as a Python package for full flexibility and customization (see a tutorial [here](../tutorials/api_usage))

docs/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44
<img src="./assets/sopa.png" alt="sopa_logo" width="250px"/>
55
</p>
66

7-
Built on top of [SpatialData](https://github.com/scverse/spatialdata), Sopa enables processing and analyses of image-based spatial-omics using a standard data structure and output. We currently support the following technologies: Xenium, MERSCOPE, CosMX, PhenoCycler, MACSIMA, Hyperion. Sopa was designed for generability and low-memory consumption on large images (scales to `1TB+` images).
7+
Built on top of [SpatialData](https://github.com/scverse/spatialdata), Sopa enables processing and analyses of image-based spatial-omics using a standard data structure and output. We currently support the following technologies: Xenium, MERSCOPE, CosMX, PhenoCycler, MACSIMA, Hyperion. Sopa was designed for generability and low memory consumption on large images (scales to `1TB+` images).
88

9-
The pipeline outputs contain: (i) Xenium Explorer files for interactive visualization, (ii) a HTML report for quick quality controls, and (iii) a SpatialData `.zarr` directory for further analyses.
9+
The pipeline outputs contain: (i) Xenium Explorer files for interactive visualization, (ii) an HTML report for quick quality controls, and (iii) a SpatialData `.zarr` directory for further analyses.
1010

1111
## Overview
1212

@@ -19,9 +19,9 @@ The following illustration describes the main steps of `sopa`:
1919
## Why use `sopa`
2020

2121
- `sopa` is designed to be memory-efficient, and it scales to large datasets with millions of cells
22-
- Depending on your need, you case use our Snakemake pipeline, our CLI, or our API
23-
- It's very easy to move on to another spatial-omics technology, since `sopa` is general to every image-based spatial-omics
24-
- You can open any data with the [Xenium Explorer](https://www.10xgenomics.com/support/software/xenium-explorer), which is a user-friendly software with many functionnalities
25-
- Spatial statistics are optimized, since geometric operations uses `shapely` internally
22+
- Depending on your need, you can use our Snakemake pipeline, our CLI, or our API
23+
- It's straightforward to move on to another spatial-omics technology since `sopa` is general to every image-based spatial-omics
24+
- You can open any data with the [Xenium Explorer](https://www.10xgenomics.com/support/software/xenium-explorer), which is a user-friendly software with many functions
25+
- Spatial statistics are optimized since geometric operations use `shapely` internally
2626
- You can customize `sopa` and add your own segmentation or annotation tool if desired
2727
- `sopa` integrates naturally with other community tools such as [Scanpy](https://scanpy.readthedocs.io/en/stable/index.html) or [Squidpy](https://squidpy.readthedocs.io/en/latest/index.html).

docs/toy.md

Lines changed: 0 additions & 43 deletions
This file was deleted.

0 commit comments

Comments
 (0)