Closed relyativist closed 5 years ago
Can’ t believe that nobody faces the same problem...
The whole workflow in mind you have is not clear to me... you said that "i compose heursitic.py for 1 subject" -- as soon as you have a heuristic, you could use it for other subjects. So it wouldn't be "heudiconv to automatically (on 1 step) composing a heuristic ". "all incoming dcm" could vary so wildly that besides may be determining modality (anat/func) it would be hard to full deduce the file naming. So I guess you would need to provide more description of your "problem" here
“...as soon as you have heuristic, you could use it for other subjects” - but if every subject have different Params in dicominfo.tsv, what I mean is there an “universal” heuristic py, not to compose it every time as dicom come in?
you must not hardcode any subject specific information into your heuristic file, and as you can see from other heuristics, see e.g. https://github.com/nipy/heudiconv/blob/master/heudiconv/heuristics/uc_bids.py#L18 .
So if you provide converter -c dcm2niix
if would at once use heuristic, create that dicominfo.tsv etc files, and proceed to conversion while possibly (depending on your heuristic) placing new files under new subject-specific locations.
Good, could please point whole command for this “so if you provide converter -c dcm 2niix...”?
actually I was wrong -- you do not even need -c dcm2niix
any longer since it is the default now ;-) !
examples: can look at https://github.com/repronim/reproin#conversion
@relyativist is this still an issue? If so, please re-open
I will try to point an issue on example: