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

create a docker-compose file #24

Open
satra opened this issue Nov 30, 2018 · 4 comments
Open

create a docker-compose file #24

satra opened this issue Nov 30, 2018 · 4 comments

Comments

@satra
Copy link

satra commented Nov 30, 2018

we should create a docker compose file for people to test out sending dicoms to a dicom receiver and have it automatically be converted to bids, and perhaps run mriqc on the bids dataset.

@yarikoptic
Copy link
Member

we definitely should or even must ;) We even have an old TODO for some reason depicted in the README only: https://github.com/ReproNim/reproin/#todoswiprelated to "add a pre-configured DICOM receiver for fully turnkey deployments"

  • I thought at some point to give a shot/try to https://www.orthanc-server.com/ since seems to be more or less lightweight, in Debian proper etc
  • I believe it is possible to configure transmission so DICOMs from the console are sent to multiple PACS so I could potentially test it locally

@satra
Copy link
Author

satra commented Dec 6, 2018

@mgxd - can you take on this issue. if you haven't created a docker-compose file before, this could be a good learning experience. essentially we will want a dicom receiver that triggers a heudiconv conversion to bids using reproin. while a lot of bells and whistles can be created. a setup where either a user triggers a job, or a cron job would be fine to start with.

@satra
Copy link
Author

satra commented Dec 6, 2018

assume that the dicoms and the converted data need to be stored in a mounted volume.

@satra
Copy link
Author

satra commented Jan 19, 2019

@mgxd - where is your docker-compose stuff? shouldn't that be a PR to reproin?

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

2 participants