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

Project memory #19

Open
mriedel56 opened this issue Sep 10, 2018 · 6 comments
Open

Project memory #19

mriedel56 opened this issue Sep 10, 2018 · 6 comments

Comments

@mriedel56
Copy link
Member

Should we keep a running tally of project memory? i.e., raw storage, dset storage, derivatives storage (and subsequent folders within derivatives like mriqc, fmriprep, etc). could be more beneficial for more accurate estimates/reporting for storage needs in grants

@tsalo
Copy link
Member

tsalo commented Sep 10, 2018

I think that makes sense. What are you thinking? How about:

  • Total raw DICOM data (/data/nbc/DICOM/[project])
  • Mean raw DICOM data (/data/nbc/DICOM/[project])
  • Total raw nifti data (/data/nbc/[project]/dset/sub-*)
  • Mean raw nifti data per subject (/data/nbc/[project]/dset/sub-*)
  • Total MRIQC (/data/nbc/[project]/derivatives/mriqc)
  • Mean MRIQC (/data/nbc/[project]/derivatives/mriqc)
  • Total fMRIPrep (/data/nbc/[project]/derivatives/fmriprep)
  • Mean fMRIPrep (/data/nbc/[project]/derivatives/fmriprep)
  • Total Freesurfer, because it's run with fMRIPrep (/data/nbc/[project]/derivatives/freesurfer)
  • Mean Freesurfer (/data/nbc/[project]/derivatives/freesurfer)

We can extend to include projects from other labs as well.

@mriedel56
Copy link
Member Author

I was mainly thinking about totals for each project, but yeah, means would also be good.

@tsalo
Copy link
Member

tsalo commented Sep 15, 2018

I've got code working for this, and would like to add it to this repository so others can use it, but want to check how other labs plan to organize their datasets and derivatives. I am assuming that the derivatives (MRIQC, Freesurfer, and fMRIPrep) will go outside the BIDS datasets. The cis-processing code outputs the MRIQC derivatives to a folder inside the BIDS dataset (e.g., /home/data/lab/project/dset/derivatives/), but I would like to change that to a folder outside (e.g., /home/data/lab/project/derivatives/). How does that sound? Tagging @anthonystevendick @mattfeld and @adamkimbler for your thoughts.

Given that one current plan is to only download dicoms from XNAT only for conversion to BIDS format (and then to clean up the tar files after), my code currently doesn't look for dicoms.

@anthonystevendick
Copy link
Member

anthonystevendick commented Sep 16, 2018 via email

@tsalo
Copy link
Member

tsalo commented Sep 20, 2018

@anthonystevendick That seems like a good rationale to keep them separate. Currently, we output to within the dataset folder, so this will require a change to cis_proc.py, but won't affect the BIDSifier image.

@tsalo
Copy link
Member

tsalo commented Apr 24, 2020

I think we should move this to a separate repository. Something like cis-tracking. The check could be set up in separate cron jobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants