-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update cellfinder CLI name to brainmapper
- Loading branch information
1 parent
4f161b2
commit 4a2c551
Showing
29 changed files
with
38 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,15 +24,15 @@ You can also find the documentation for the backend BrainGlobe tools these workf | |
|
||
At present, the package offers the following workflows to users: | ||
|
||
- [cellfinder](#cellfinder): a command-line tool for whole-brain detection, registration, and analysis. | ||
- [brainmapper](#brainmapper-command-line-interface-cli): A command-line tool for whole-brain detection, registration, and analysis. | ||
|
||
Additionally, this repository provides functionalities to support code developers. See [Developers documentation](#developers-documentation) for further details. | ||
Additionally, this repository provides functionalities to support code developers. See the [developer documentation](#developer-documentation) for further details. | ||
|
||
## User documentation | ||
|
||
### Installation | ||
|
||
### Installation of the cellfinder CLI tool | ||
At the moment, users can install the cellfinder CLI tool as a standalone tool, by running `pip install` in your desired environment: | ||
At the moment, users can install all available workflows by running `pip install` in your desired environment: | ||
|
||
```bash | ||
pip install brainglobe-workflows | ||
|
@@ -41,43 +41,45 @@ pip install brainglobe-workflows | |
`brainglobe-workflows` is built using BrainGlobe tools, and it will automatically fetch the tools that it needs and install them into your environment. | ||
Once BrainGlobe version 1 is available, this package will fetch all BrainGlobe tools and handle their install into your environment, to prevent potential conflicts from partial-installs. | ||
|
||
See the sections below for more information about the workflows and command-line tools provided. | ||
|
||
### Cellfinder Command Line Interface (CLI) | ||
#### `brainmapper` Command Line Interface (CLI) | ||
|
||
Whole-brain cell detection, registration and analysis. | ||
|
||
If you want to just use the cell detection part of `cellfinder`, please see the standalone [cellfinder](https://github.com/brainglobe/cellfinder-core) package, or the [cellfinder plugin](https://github.com/brainglobe/cellfinder-napari) for [napari](https://napari.org/). | ||
|
||
If you want to just use the cell detection part of `brainmapper`, please see the standalone [cellfinder](https://github.com/brainglobe/cellfinder) package and its [`napari`](https://napari.org/) plugin. | ||
`cellfinder` is a collection of tools developed by [Adam Tyson](https://github.com/adamltyson), [Charly Rousseau](https://github.com/crousseau) and [Christian Niedworok](https://github.com/cniedwor) in the [Margrie Lab](https://www.sainsburywellcome.org/web/groups/margrie-lab), generously supported by the [Sainsbury Wellcome Centre](https://www.sainsburywellcome.org/web/). | ||
|
||
`cellfinder` is designed for the analysis of whole-brain imaging data such as [serial-section imaging](https://sainsburywellcomecentre.github.io/OpenSerialSection/) and lightsheet imaging in cleared tissue. | ||
`brainmapper` is a workflow designed for the analysis of whole-brain imaging data such as [serial-section imaging](https://sainsburywellcomecentre.github.io/OpenSerialSection/) and lightsheet imaging in cleared tissue. | ||
The aim is to provide a single solution for: | ||
|
||
- Cell detection (initial cell candidate detection and refinement using deep learning) (using the [cellfinder](https://github.com/brainglobe/cellfinder-core) backend package), | ||
- Cell detection (initial cell candidate detection and refinement using deep learning) (using the [cellfinder](https://github.com/brainglobe/cellfinder) backend package), | ||
- Atlas registration (using [brainreg](https://github.com/brainglobe/brainreg)), | ||
- Analysis of cell positions in a common space. | ||
|
||
Basic usage: | ||
|
||
```bash | ||
cellfinder -s signal_images -b background_images -o output_dir --metadata metadata | ||
brainmapper -s signal_images -b background_images -o output_dir --metadata metadata | ||
``` | ||
|
||
Full documentation can be found [here](https://brainglobe.info/documentation/cellfinder/index.html). | ||
|
||
NOTE: The `brainmapper` workflow previously used the name "cellfinder", but this has been discontinued following the release of the [unified `cellfinder`](https://github.com/brainglobe/cellfinder) backend package to avoid conflation of terms. | ||
See our [blog post](https://brainglobe.info/blog/version1/cellfinder-core-and-plugin-merge.html) from the release for more information. | ||
|
||
## Developer documentation | ||
|
||
This repository also includes workflow scripts that are benchmarked to support code development. | ||
These benchmarks are run regularly to ensure performance is stable, as the tools are developed and extended. | ||
* Developers can install these benchmarks locally via `pip install .[dev]`. By executing `asv run`, the benchmarks will run with default parameters on a small dataset that is downloaded from [GIN](https://gin.g-node.org/G-Node/info/wiki). See [the asv docs](https://asv.readthedocs.io/en/v0.6.1/using.html#running-benchmarks) for further details on how to run benchmarks. | ||
* Developers can also run these benchmarks on data they have stored locally, by specifying the relevant paths in an input (JSON) file. | ||
* We also maintain an internal runner that benchmarks the workflows over a large, exemplar dataset, of the scale we expect users to be handling. The result of these benchmarks are made publicly available. | ||
|
||
- Developers can install these benchmarks locally via `pip install .[dev]`. By executing `asv run`, the benchmarks will run with default parameters on a small dataset that is downloaded from [GIN](https://gin.g-node.org/G-Node/info/wiki). See [the asv docs](https://asv.readthedocs.io/en/v0.6.1/using.html#running-benchmarks) for further details on how to run benchmarks. | ||
- Developers can also run these benchmarks on data they have stored locally, by specifying the relevant paths in an input (JSON) file. | ||
- We also maintain an internal runner that benchmarks the workflows over a large, exemplar dataset, of the scale we expect users to be handling. The result of these benchmarks are made publicly available. | ||
|
||
Contributions to BrainGlobe are more than welcome. | ||
Please see the [developer guide](https://brainglobe.info/developers/index.html). | ||
|
||
|
||
## Citing `brainglobe-workflows` | ||
|
||
**If you use any tools in the [brainglobe suite](https://brainglobe.info/documentation/index.html), please [let us know](mailto:[email protected]?subject=cellfinder), and we'd be happy to promote your paper/talk etc.** | ||
|
@@ -87,5 +89,3 @@ If you find [`cellfinder`](#cellfinder) useful, and use it in your research, ple | |
[https://doi.org/10.1371/journal.pcbi.1009074](https://doi.org/10.1371/journal.pcbi.1009074) | ||
> | ||
If you use any of the image registration functions in `cellfinder`, please also cite [`brainreg`](https://github.com/brainglobe/brainreg#citing-brainreg). | ||
|
||
--- |
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
4 changes: 2 additions & 2 deletions
4
...lows/cellfinder_brainreg/export/export.py → ...be_workflows/brainmapper/export/export.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
2 changes: 1 addition & 1 deletion
2
...ws/cellfinder_brainreg/figures/figures.py → ..._workflows/brainmapper/figures/figures.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters