Closed dzemanov closed 8 months ago
So there are still issues, I thought we tackled them all by now :-). I somehow have the feeling your fix is not the optimal place for fixing this problem. But then again, I don't see what kind of data can lead up to this situation. I'll think about it a bit more
Did check_runindices()
warn about this?
Does this work for you? (sorry, I shelved and unshelved and then things didn't commit properly)
I merged it and will go ahead with the new release, but would like to be reassured that it works for your data :-)
Ok, it's more complicated then I thought, I'll get back to you on this (after I finished the scans.tsv problem)
Yes, its never ending story :D.
This is working for the issue I found, amazing! What is problem with scans.tsv?
That needed the same update as targets
, all seems to work fine now, I'm releasing a new version now :-)
(the bids-validator still gives an error but it seems that's because it doesn't support BIDS 1.9 yet (not fully at least, the echo
entity for my T1w image was falsely classified as invalid)
FYI, I added a troubleshooting item to help others when dealing with the complex interaction between using a dynamic run-index and dcm2niix adding all sorts of post-fixes:
It can happen that
run_2
is added within dcm2niixfiles loop indcm2niix2bids.py
when dealing with postfixes. Functionincrement_runindex
renames runless file to run1 file but targets in dcm2niix2bids are not updated, and file stays runless.