You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+ Trigger packages used for neurophysiological data processing.
7
-
+ Functions common to the DataJoint Elements (e.g. search directory tree for data files).
3
+
DataJoint Element for interoperability with other software. DataJoint Elements
4
+
collectively standardize and automate data collection and analysis for neuroscience
5
+
experiments. Typical Elements are modular pipelines for data storage and processing with
6
+
corresponding database tables that can be combined with other Elements to assemble a
7
+
fully functional pipeline. Element Interface is home to a number of utilities that make
8
+
this possible.
8
9
9
-
+ See [DataJoint Elements](https://github.com/datajoint/datajoint-elements) for descriptions
10
-
of the `elements` and `workflows` developed as part of this initiative.
11
-
12
-
# Architecture
13
-
14
-
+ The functions for each acquisition and analysis package are stored within a separate module.
15
-
16
-
+ Acquisition packages
17
-
+`scanimage_utils.py`
18
-
19
-
+ Analysis packages
20
-
+`suite2p_loader.py`
21
-
+`caiman_loader.py`
22
-
+`run_caiman.py`
23
-
24
-
# Installation
25
-
26
-
+ Install `element-interface`:
27
-
```
28
-
pip install element-interface
29
-
```
30
-
31
-
+ This package is to be used in combination with the other DataJoint Elements (e.g. `element-calcium-imaging`). The installation of packages used for data processing (e.g. `Suite2p`) will be included within the respective DataJoint Element (e.g. `element-calcium-imaging`).
32
-
33
-
# Usage
34
-
35
-
+ See the [workflow-calcium-imaging](https://github.com/datajoint/workflow-calcium-imaging)
36
-
and [element-calcium-imaging](https://github.com/datajoint/element-calcium-imaging)
37
-
repositories for example usage of `element-interface`.
+ Suite2p wrapper functions for triggering analysis
64
-
65
-
+ Functions to independently run Suite2p's motion correction, segmentation, and deconvolution steps. These functions currently work for single plane tiff files. If running all Suite2p pre-processing steps concurrently, these functions are not required and one can run `suite2p.run_s2p()`.
66
-
67
-
+ These wrapper functions were developed primarily because `run_s2p` cannot individually run deconvolution using the `spikedetect` flag ([Suite2p Issue #718](https://github.com/MouseLand/suite2p/issues/718)).
+ Note that the ops dictionary returned from the `motion_correction_suite2p` and `segmentation_suite2p` functions is only a subset of the keys generated with the `suite2p.default_ops()` function.
0 commit comments