Add imaging_preprocess module

CHANGELOG.md

@@ -2,6 +2,10 @@
 
 Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) convention.
 
+## [0.2.0] - 2022-07-01
+
++ Add - Imaging module (imaging_preprocess.py) for pre-processing steps
+
 ## [0.1.0] - 2022-06-29
 
 + Add - Support for element-interface
@@ -28,6 +32,7 @@ Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and
 + Add - `scan` and `imaging` modules
 + Add - Readers for `ScanImage`, `ScanBox`, `Suite2p`, `CaImAn`
 
+[0.2.0]: https://github.com/datajoint/element-calcium-imaging/releases/tag/0.2.0
 [0.1.0]: https://github.com/datajoint/element-calcium-imaging/releases/tag/0.1.0
 [0.1.0b0]: https://github.com/datajoint/element-calcium-imaging/releases/tag/0.1.0b0
 [0.1.0a4]: https://github.com/datajoint/element-calcium-imaging/releases/tag/0.1.0a4

README.md

@@ -16,13 +16,31 @@ a fully functional calcium imaging workflow.
 
 ## Element architecture
 
-![element-calcium-imaging diagram](images/attached_calcium_imaging_element.svg)
+`element-calcium-imaging` is comprised of two schemas, `scan` and `imaging`.  To handle
+several use cases of this pipeline, we have designed several `imaging` schemas,
+including `imaging`, `imaging_no_curation`, and `imaging_preprocess`.
+
++ `imaging` - Multiple scans are acquired during each session and each scan is processed
+              independently.
+
++ `imaging_preprocess` - Multiple scans are acquired during each session and each scan
+                         is processed independently.  And pre-processing steps can be
+                         performed on each scan prior to processing with Suite2p or
+                         CaImAn.
+
+### `imaging` module
+
+![imaging diagram](images/attached_calcium_imaging_element.svg)
+
+### `imaging_preprocess` module
+
+![imaging-preprocess diagram](images/attached_calcium_imaging_element_preprocess.svg)
 
 + As the diagram depicts, the imaging element starts immediately downstream from `Session`, and also requires some notion of:
 
-     + `Scanner` for equipment/device
+    + `Scanner` for equipment/device
 
-     + `Location` as a dependency for `ScanLocation`
+    + `Location` as a dependency for `ScanLocation`
 
 ## Table definitions