Merge pull request #102 from kushalbakshi/main

Added docs + docstrings

Author: CBroz1

.github/workflows/u24_element_release_call.yml

@@ -17,6 +17,7 @@ jobs:
     secrets:
       TWINE_USERNAME: ${{secrets.TWINE_TEST_USERNAME}}
       TWINE_PASSWORD: ${{secrets.TWINE_TEST_PASSWORD}}
+      GOOGLE_ANALYTICS_KEY: ${{secrets.GOOGLE_ANALYTICS_KEY}}
   call_u24_elements_release_alpine:
     if: >-
       github.event.workflow_run.conclusion == 'success' && github.repository_owner == 'datajoint' && !contains(github.event.workflow_run.head_branch, 'test')
@@ -26,3 +27,5 @@ jobs:
     secrets:
       TWINE_USERNAME: ${{secrets.TWINE_USERNAME}}
       TWINE_PASSWORD: ${{secrets.TWINE_PASSWORD}}
+      GOOGLE_ANALYTICS_KEY: ${{secrets.GOOGLE_ANALYTICS_KEY}}
+

CHANGELOG.md

@@ -7,7 +7,10 @@ Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and
 
 + Add - New schema `ephys_report` to compute and store figures from results
 + Add - Widget to display figures
-+ Add - Add `ephys_no_curation` and routines to trigger spike-sorting analysis using Kilosort (2.0, 2.5)
++ Add - Add `ephys_no_curation` and routines to trigger spike-sorting analysis
+  using Kilosort (2.0, 2.5)
++ Add - mkdocs for Element Documentation
+
 
 ## 0.1.5 - 2022-09-29
 
@@ -55,10 +58,10 @@ Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and
 + Add - Probe table supporting: Neuropixels probes 1.0 - 3A, 1.0 - 3B, 2.0 - SS, 2.0 - MS
 
 [0.2.0]: https://github.com/datajoint/element-array-ephys/releases/tag/0.2.0
-[0.1.4]: https://github.com/datajoint/element-array-ephys/compare/0.1.3...0.1.4
-[0.1.3]: https://github.com/datajoint/element-array-ephys/compare/0.1.2...0.1.3
-[0.1.2]: https://github.com/datajoint/element-array-ephys/compare/0.1.1...0.1.2
-[0.1.1]: https://github.com/datajoint/element-array-ephys/compare/0.1.0...0.1.1
-[0.1.0]: https://github.com/datajoint/element-array-ephys/compare/0.1.0b0...0.1.0
-[0.1.0b0]: https://github.com/datajoint/element-array-ephys/compare/0.1.0a5...0.1.0b0
+[0.1.4]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.4
+[0.1.3]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.3
+[0.1.2]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.2
+[0.1.1]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.1
+[0.1.0]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.0
+[0.1.0b0]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.0b0
 [0.1.0a5]: https://github.com/datajoint/element-array-ephys/releases/tag/0.1.0a5

README.md

@@ -1,177 +1,9 @@
 # DataJoint Element - Array Electrophysiology Element
 
-+ This repository features DataJoint pipeline design for extracellular array electrophysiology, 
-with Neuropixels probe and Kilosort spike sorting method. 
+DataJoint Element for extracellular array electrophysiology. 
+DataJoint Elements collectively standardize and automate data collection and analysis for neuroscience experiments.  Each Element is a modular pipeline for data storage and processing with corresponding database tables that can be combined with other Elements to assemble a fully functional pipeline.
 
-+ This module is designed to be integrated into a complete data pipeline and provides
-data tables and computational dependencies specific to extracellular electrophysiology
-processing and analysis.
+Installation and usage instructions can be found at the 
+[Element documentation](datajoint.com/docs/elements/element-array-ephys).
 
-+ This modular pipeline element can be flexibly attached downstream 
-to any particular design of experiment session, thus assembling a fully functional 
-ephys pipeline.
-
-+ This Element provides three schema options, selected via the DataJoint config file, with `dj.config['custom']['ephys_mode']`
-  + `acute` probe insertion, with curated clustering
-  + `chronic` probe insertion, with curated clustering
-  + `no-curation`, with kilosort triggered clustering
-
-+ See the [Element Array Electrophysiology documentation](https://elements.datajoint.org/description/array_ephys/) for the background information and development timeline.
-
-+ For more information on the DataJoint Elements project, please visit https://elements.datajoint.org.  This work is supported by the National Institutes of Health.
-
-## Element architecture
-
-`element-array-ephys` is comprised of two schemas, `probe` and `ephys`.  To handle 
-several use cases of this pipeline, we have designed several `ephys` schemas, including 
-`ephys_acute`, `ephys_chronic`, and `ephys_precluster`.
-
-+ `ephys_acute` - A probe(s) is inserted into a new location during each session.
-
-+ `ephys_chronic` - A probe(s) is inserted once and used to record across multiple 
-sessions.
-
-+ `ephys_precluster` - A probe(s) is inserted into a new location during each session.  
-And pre-clustering steps (e.g. CatGT) are performed on the data from each probe prior 
-to Kilosort analysis.
-
-### `ephys_acute` module
-![element-array-ephys acute diagram](images/attached_array_ephys_element_acute.svg)
-
-
-### `ephys_chronic` module
-![element-array-ephys chronic diagram](images/attached_array_ephys_element_chronic.svg)
-
-### `ephys_precluster` module
-![element-array-ephys precluster diagram](
-    images/attached_array_ephys_element_precluster.svg)
-
-
-As the diagram depicts, the array ephys element starts immediately downstream from `Session`, 
-and also requires some notion of `Location` as a dependency for `InsertionLocation`. We 
-provide an [example workflow](https://github.com/datajoint/workflow-array-ephys/) with a 
-[pipeline script](https://github.com/datajoint/workflow-array-ephys/blob/main/workflow_array_ephys/pipeline.py)
-that models (a) combining this Element with the corresponding [Element-Session](https://github.com/datajoint/element-session)
-, and (b) declaring a `SkullReference` table to provide Location.
-
-## Table descriptions
-
-### Probe & electrodes
-
-The `probe` schema contains information regarding the Neuropixels probe and electrode configuration.
-
-<details>
-<summary>Click to expand details</summary>
-
-+ `ProbeType` - a lookup table specifying the type of Neuropixels probe (e.g. "neuropixels 1.0", "neuropixels 2.0 single-shank")
-
-+ `ProbeType.Electrode` - all electrode and their properties for a particular probe type
-    + An electrode here refers to one recordable electrode site on the Neuropixels probe (e.g. for Neuropixels 1.0, there are 960 sites per shank)
-
-+ `Probe` - record of an actual physical probe, identifiable by some unique ID (e.g. probe's serial number)
-
-+ `ElectrodeConfig` - particular electrode configuration to be used for ephys recording
-
-+ `ElectrodeConfig.Electrode` - corresponding electrodes in `ProbeType.Electrode` that are used for recording in this electrode configuration (e.g. for Neuropixels 1.0 or 2.0, there can be at most 384 electrodes usable for recording per probe)
-
-</details>
-
-### Extracellular electrophysiology recording
-
-The `ephys` schema stores information regarding the recording from a probe for a given session.
-
-<details>
-<summary>Click to expand details</summary>
-
-+ `ProbeInsertion` - a surgical insertion of a probe in the brain. Every experimental session consists of one or more entries in `ProbeInsertion` with a corresponding `InsertionLocation` each
-
-+ `EphysRecording` - each `ProbeInsertion` is accompanied by a corresponding `EphysRecording`, specifying the `ElectrodeConfig` used for the recording from the `Probe` defined in such `ProbeInsertion`
-
-</details>
-
-### Clusters and spikes
-
-The `ephys` schema features automatic ingestion of spike sorting results from the `Kilosort` analysis method. 
-
-<details>
-<summary>Click to expand details</summary>
-
-+ `Clustering` - specify instance(s) of clustering on an `EphysRecording`, by some `ClusteringMethod`
-
-+ `Curation` - specify instance(s) of curations performed on the output of a given `Clustering`
-
-+ `CuratedClustering` - set of results from a particular round of clustering/curation
-    + `CuratedClustering.Unit` - Identified unit(s) from one `Curation`, and the associated properties (e.g. cluster quality, spike times, spike depths, etc.)
-    + `WaveformSet` - A set of spike waveforms for units from a given CuratedClustering
-
-</details>
-
-## Installation
-<details>
-<summary>Click to expand details</summary>
-
-+ Install `element-array-ephys`
-    ```
-    pip install element-array-ephys
-    ```
-
-+ Upgrade `element-array-ephys` previously installed with `pip`
-    ```
-    pip install --upgrade element-array-ephys
-    ```
-
-+ Install `element-interface`
-    + `element-interface` is a dependency of `element-array-ephys`, however it is not contained within `requirements.txt`.
-    ```
-    pip install "element-interface @ git+https://github.com/datajoint/element-interface"
-    ```
-
-</details>
-
-## Usage
-
-### Element activation
-
-When using this Element, one needs to run `ephys.activate` to declare the schemas and tables on the database.
-
-<details>
-<summary>Click to expand details</summary>
-
-To activate the `element-array-ephys`, ones need to provide:
-
-1. Schema names
-    + schema name for the probe module
-    + schema name for the ephys module
-
-2. Upstream tables
-    + Session table: A set of keys identifying a recording session (see [Element-Session](https://github.com/datajoint/element-session)).
-    + SkullReference table: A reference table for InsertionLocation, specifying the skull reference (see [example pipeline](https://github.com/datajoint/workflow-array-ephys/blob/main/workflow_array_ephys/pipeline.py)).
-
-3. Utility functions. See [example definitions here](https://github.com/datajoint/workflow-array-ephys/blob/main/workflow_array_ephys/paths.py)
-    + get_ephys_root_data_dir(): Returns your root data directory.
-    + get_session_directory(): Returns the path of the session data relative to the root.
-
-For more detail, check the docstring of the `element-array-ephys`:
-
-    help(probe.activate)
-    help(ephys.activate)
-
-</details>
-
-### Example usage
-
-See [this project](https://github.com/datajoint/workflow-array-ephys) for an example usage of this Array Electrophysiology Element.
-
-## Citation
-
-+ If your work uses DataJoint and DataJoint Elements, please cite the respective Research Resource Identifiers (RRIDs) and manuscripts.
-
-+ DataJoint for Python or MATLAB
-    + Yatsenko D, Reimer J, Ecker AS, Walker EY, Sinz F, Berens P, Hoenselaar A, Cotton RJ, Siapas AS, Tolias AS. DataJoint: managing big scientific data using MATLAB or Python. bioRxiv. 2015 Jan 1:031658. doi: https://doi.org/10.1101/031658
-
-    + DataJoint ([RRID:SCR_014543](https://scicrunch.org/resolver/SCR_014543)) - DataJoint for `<Select Python or MATLAB>` (version `<Enter version number>`)
-
-+ DataJoint Elements
-    + Yatsenko D, Nguyen T, Shen S, Gunalan K, Turner CA, Guzman R, Sasaki M, Sitonic D, Reimer J, Walker EY, Tolias AS. DataJoint Elements: Data Workflows for Neurophysiology. bioRxiv. 2021 Jan 1. doi: https://doi.org/10.1101/2021.03.30.437358
-
-    + DataJoint Elements ([RRID:SCR_021894](https://scicrunch.org/resolver/SCR_021894)) - Element Array Electrophysiology (version `<Enter version number>`)
+![element-array-ephys diagram](https://raw.githubusercontent.com/datajoint/element-array-ephys/main/images/attached_array_ephys_element_acute.svg)

docs/.docker/Dockerfile

@@ -4,12 +4,14 @@ WORKDIR /main
 COPY --chown=anaconda:anaconda ./docs/.docker/apk_requirements.txt ${APK_REQUIREMENTS}
 COPY --chown=anaconda:anaconda ./docs/.docker/pip_requirements.txt ${PIP_REQUIREMENTS}
 RUN \
+    umask u+rwx,g+rwx,o-rwx && \
     /entrypoint.sh echo "Dependencies installed" && \
+    rm ${APK_REQUIREMENTS} ${PIP_REQUIREMENTS} && \
     git config --global user.name "GitHub Action" && \
     git config --global user.email "[email protected]"&& \
     git config --global pull.rebase false && \
     git init
 COPY --chown=anaconda:anaconda ./${PACKAGE} /main/${PACKAGE}
 COPY --chown=anaconda:anaconda ./docs/mkdocs.yaml /main/docs/mkdocs.yaml
 COPY --chown=anaconda:anaconda ./docs/src /main/docs/src
-COPY --chown=anaconda:anaconda ./CHANGELOG.md /main/docs/src/about/changelog.md
+COPY --chown=anaconda:anaconda ./CHANGELOG.md /main/

docs/.docker/pip_requirements.txt

@@ -7,3 +7,4 @@ mdx-truly-sane-lists
 mkdocs-gen-files
 mkdocs-literate-nav
 mkdocs-exclude-search
+mkdocs-markdownextradata-plugin

docs/docker-compose.yaml

@@ -1,4 +1,4 @@
-# MODE="LIVE|QA|BUILD" PACKAGE=element_array_ephys UPSTREAM_REPO=https://github.com/datajoint/element-array-ephys.git HOST_UID=$(id -u) docker compose -f docs/docker-compose.yaml up --build
+# MODE="LIVE|QA|PUSH" PACKAGE=element_array_ephys UPSTREAM_REPO=https://github.com/datajoint/element-array-ephys.git HOST_UID=$(id -u) docker compose -f docs/docker-compose.yaml up --build
 #
 # navigate to http://localhost/
 version: "2.4"
@@ -14,27 +14,39 @@ services:
       - PACKAGE
       - UPSTREAM_REPO
       - MODE
+      - GOOGLE_ANALYTICS_KEY
+      - PATCH_VERSION
     volumes:
-      - ..:/main
+      - ../docs:/main/docs
+      - ../${PACKAGE}:/main/${PACKAGE}
     user: ${HOST_UID}:anaconda
     ports:
       - 80:80
     command:
       - sh
       - -c
       - |
+        git config --global --add safe.directory /main
         set -e
+        export PATCH_VERSION=$$(cat /main/$${PACKAGE}/version.py | grep -oE '\d+\.\d+\.[a-z0-9]+')
         if echo "$${MODE}" | grep -i live &>/dev/null; then
             mkdocs serve --config-file ./docs/mkdocs.yaml -a 0.0.0.0:80
-        elif echo "$${MODE}" | grep -iE "qa|build" &>/dev/null; then
+        elif echo "$${MODE}" | grep -iE "qa|push" &>/dev/null; then
+            echo "INFO::Delete gh-pages branch"
             git branch -D gh-pages || true
-            git fetch $${UPSTREAM_REPO} gh-pages:gh-pages || true
+            echo "INFO::Fetch upstream gh-pages"
+            git fetch $${UPSTREAM_REPO} gh-pages:gh-pages && git switch gh-pages || git switch --orphan gh-pages && git commit --allow-empty -m "init commit"
+            echo "INFO::mike"
             mike deploy --config-file ./docs/mkdocs.yaml -u $$(grep -oE '\d+\.\d+' /main/$${PACKAGE}/version.py) latest
             mike set-default --config-file ./docs/mkdocs.yaml latest
             if echo "$${MODE}" | grep -i qa &>/dev/null; then
                 mike serve --config-file ./docs/mkdocs.yaml -a 0.0.0.0:80
+            elif echo "$${MODE}" | grep -i push &>/dev/null; then
+                echo "INFO::Push gh-pages to upstream"
+                git push $${UPSTREAM_REPO} gh-pages
             fi
         else
             echo "Unexpected mode..."
             exit 1
         fi
+