Yaroslav Halchenko

Probably could be setup to be done on travis or any other CI, or could be a local host which would do it and push daily (if any changes)

ReproNim related ones: - [ ] simple_workflow - [ ] neurodocker - [ ] reproin Should probably not be placed under repronim collection: - [ ] datalad - [ ]...

ATM it is singularity only, but we could support docker as well. Largely to make the setup usable "natively" on OSX and Windows

we ran into a situation ```shell bids@rolando:/inbox/BIDS/Wager/Wager/1076_spacetop$ ls -l /inbox/DICOM/2021/12/16/A004300 | grep 00.*cout drwxr-x--- 2 193119 wager 130 Dec 16 2021 001-anat-scout_ses-01 drwxr-x--- 2 193119 wager 130 Dec 16 2021...

in _scans.tsv we have a record of all acquired/converted dates. Assuming that we would want to consider only new ones, we can add a mode to look at the dates...

Similarly to https://github.com/ReproNim/containers/#a-typical-workflow but for reproin. An example dataset which uses such setup is http://datasets.datalad.org/?dir=/dbic/QA (AKA `///dbic/QA`) where you can see https://datasets.datalad.org/dbic/QA/.datalad/config containing ``` [datalad "containers.repronim-reproin"] image = code/containers/images/repronim/repronim-reproin--0.13.1.sing cmdexec...

would be handy for others cons: might be stuck using outdated one.

ATM `_run+` would increment throughout all sequences, ie. for `_acq-1_run+`, `_acq-2_run+`, `_acq-1_run+`, `_acq-2_run+` we would get `_acq-1_run-1`, `_acq-2_run-2`, `_acq-1_run-3`, `_acq-2_run-4`, whenever what we really want is `_acq-1_run-1`, `_acq-2_run-1`, `_acq-1_run-2`, `_acq-2_run-2`....

We should work to assist with converting the eye tracking data. This is to collect notes - BIDS BEP PR: - EyeLink device has an API which ppl use to...

If ses markers are found to be `alpha` and start at `int(1)` -- they are likely to be strictly `+1` for each subsequent one, e.g. ``` # /inbox/DICOM/DATE/A003591 done SID0XXX...