Skip to content

Commit

Permalink
remove bpod
Browse files Browse the repository at this point in the history
  • Loading branch information
CBroz1 committed Mar 1, 2022

Verified

This commit was signed with the committer’s verified signature.
frapell Franco Pellegrini
1 parent 9aacfec commit 38b38eb
Showing 6 changed files with 210 additions and 367 deletions.
194 changes: 0 additions & 194 deletions Background.md

This file was deleted.

2 changes: 1 addition & 1 deletion LICENSE
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2021 DataJoint
Copyright (c) 2022 DataJoint

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
25 changes: 16 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
@@ -3,13 +3,18 @@ This repository is a work in progress not yet ready for public release.
It serves as a draft of a DataJoint element for trialized experiments behavior
for our U24 itiative.

Work in progress.

## Element architecture

In both of the following diagrams, the trial element starts immediately downstream from ***Session***. In one case, Sessions are first segmented into trials, and then segmented into events. This might be appropriate, for example, in a paradigm with repeated conditions and response behaviors associated with different conditions. In the next, Sessions are directly upstream from Events. This might be appropropriate for a paradigm that recorded events within naturalistic free behavior.
We provide an [example workflow](https://github.com/datajoint/workflow-trial/) with a
[pipeline script](https://github.com/datajoint/workflow-trial/blob/main/workflow_trial/pipeline.py) that models combining this Element with the corresponding [Element-Session](https://github.com/datajoint/element-session).
In both of the following diagrams, the trial element starts immediately downstream from
***Session***. In one case, Sessions are first segmented into trials, and then aaa
segmented into events. This might be appropriate, for example, in a paradigm with
repeated conditions and response behaviors associated with different conditions. In the
next, Sessions are directly upstream from Events. This might be appropropriate for a
paradigm that recorded events within naturalistic free behavior. We provide an
[example workflow](https://github.com/datajoint/workflow-trial/) with a
[pipeline script](https://github.com/datajoint/workflow-trial/blob/main/workflow_trial/pipeline.py)
that models combining this Element with the corresponding
[Element-Session](https://github.com/datajoint/element-session).


<!---
@@ -32,7 +37,8 @@ We provide an [example workflow](https://github.com/datajoint/workflow-trial/)
<!---
+ Install `element-interface`
+ `element-interface` is a dependency of `element-trial`, however it is not contained within `requirements.txt`.
+ `element-interface` is a dependency of `element-trial`, however it is not
contained within `requirements.txt`.
```
pip install "element-interface @ git+https://github.com/datajoint/element-interface"
@@ -46,9 +52,10 @@ We provide an [example workflow](https://github.com/datajoint/workflow-trial/)
To activate the `element-trial`, one need to provide:
1. Schema names for the event or trial module
2. Upstream Session table: A set of keys identifying a recording session (see [Element-Session](https://github.com/datajoint/element-session)).
3. Utility functions. See example definitions here](https://github.com/datajoint/workflow-trial/blob/main/workflow_trial/paths...
2. Upstream Session table: A set of keys identifying a recording session (see [
Element-Session](https://github.com/datajoint/element-session)).
3. Utility functions. See
[example definitions here](https://github.com/datajoint/workflow-trial/blob/main/workflow_trial/paths.py)
For more detail, check the docstring of the `element-trial`:
```python
Loading

0 comments on commit 38b38eb

Please sign in to comment.