Add DevContainers + Codespaces tutorial #173
Conversation
element_array_ephys/__init__.py
Outdated
There was a problem hiding this comment.
I think all of these new changes should belong in tutorial_pipeline.py
Same is true for the calcium-imaging and deeplabcut elements - let's discuss further
| @@ -22,19 +21,66 @@ to assemble a fully functional pipeline. | |||
|
|
|||
|  | |||
|
|
|||
| + We have designed variations of the pipeline to handle different use cases. Displayed | |||
| above is the `ephys_acute` schema for acute electrophysiology recordings. Details on | |||
| all `ephys` schemas can be found in the documentation. | |||
There was a problem hiding this comment.
The documentation can be hyperlinked here to https://datajoint.com/docs/elements/element-array-ephys/0.2/
|
|
||
| + [Documentation](https://datajoint.com/docs/elements/element-array-ephys) | ||
|
|
||
| ## Support | ||
|
|
||
| + If you need help getting started or run into any errors, please contact our team by email at [email protected]. | ||
| + If you need help getting started or run into any errors, please contact our team by | ||
| email at [email protected]. |
There was a problem hiding this comment.
Are we not including the "open a GitHub Issue" option here?
There was a problem hiding this comment.
Given that this is a jupyter notebook, it will be more convenient to create a minor PR to be merged into this PR for the review for this tutorial.
There was a problem hiding this comment.
Thank you, @MilagrosMarin. That sounds good.
There was a problem hiding this comment.
I will merge this PR and updates on the proposed tutorial will be included in an upcoming PR since the scope of updates is very large.
|
I've checked the creation of a codespace and have run the entire tutorial notebook with successful results. |
This PR adds DevContainers configured to run Codespaces for tutorials and workshops. The proposed changes will include the following:
setup.pyversion.pyand CHANGELOGThe scope for this PR has been altered slightly. Documentation updates will be included in a separate PR since the scope of updates is very large.