Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

registry of already processed directories #10

Open
yarikoptic opened this issue Feb 24, 2017 · 1 comment
Open

registry of already processed directories #10

yarikoptic opened this issue Feb 24, 2017 · 1 comment

Comments

@yarikoptic
Copy link
Member

yarikoptic commented Feb 24, 2017

we probably want also to be able to be able to

  • re-process directory (probably just rerun with --overwrite)
  • annotate that a directory X
    • was processed already
    • should not be processed
  • given a DBIC dataset with .heudiconv/ report which Accession numbers were already processed (which subject/session)
  • for a given study ID, report which accessions were processed (and to where stored) and which weren't, and possibly run a conversion on those which weren't yet
    (current ad-hoc line to execute is grep -B1 1018_model ~/heudiconv-ls001-20170227.txt | grep DICOM/ | sed -e 's,/001.*,,g' | xargs heudiconv -o ~/test-1018_model)
@yarikoptic
Copy link
Member Author

yarikoptic commented Mar 8, 2017

so the WiP heudiconv_monitor already creates such a database. We should prepopulate it and make use of it also within heudiconv or our specific wrapper around (currently a shell script, bleh, at ~/bin/heudiconv) it to ignore/warning when some directory which was already processed ... we should store it in /inbox/BIDS/.heudiconv/statusdb.json or smth like that.

yarikoptic pushed a commit that referenced this issue Feb 24, 2022
Two quick and dirty patches while I have tried to use that branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant