Satrajit Ghosh
Satrajit Ghosh
most people already have dicom receivers. but our collabs at northeastern wanted an easy to use setup. docker-compose allows us to use different docker images without worrying about interactions within...
i don't think they ended up doing this, but still worth a setup i think both for testing, but also for people to potentially use. not a super high priority...
@jdkent - the focus of reproin is really about metadata inside the dicom file, rather than any organization that would be output by xnat. so as long as the dicom...
@jdkent - an additional possibility is to add reproin as an automation pipeline for xnat (using docker). this should then allow exporting xnat dicoms as bids (obviously a few xnat...
@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...
assume that the dicoms and the converted data need to be stored in a mounted volume.
@mgxd - where is your docker-compose stuff? shouldn't that be a PR to reproin?
yes - completely forgot about heudiconv! apache 2 protects against companies using it and then suing the project
apache 2 makes it very explicit and from people i have spoken to that helps were it to ever get to such a state. also given that many major products...
this page helps clarify: https://choosealicense.com/