Gradientfieldmap (phasediff) problem with TE and „:“ error in bidsmap.yaml file about bidscoin HOT 4 CLOSED

Hi Karl, Is that with the version I released a few hours ago? That would be super fast! ;-) Thanks for your feedback, here is what I can say about it now (I'm leaving for holidays tomorrow): 1. I'll look into it, it is a bit of a tricky problem because Siemens often (always?) writes both magnitude images into the same series. dcm2niix then produces two images for one series, whereas normally it onlly produces one image per series. I then fix this in the code by retrospectively searching for a magnitude2 image, then adding the TE's to it. It's possibly that a TE is lost there, I'll check.. 2. the run:<<1>> is something you normally shouldn't touch. The double brackets make it a dynamic label, meaning it will get incremented (from 1) during bidscoiner runtime if there already exists a file with run-1. Did you have problems with leaving <<1>> as it was? The IntendedFor searches for bidsnames after all files are converted to nifti, so it should pick up all the runs (unless you specify a run-index in your IntendedFor search term like IntendedFor: <<bold*run-1>> or just like IntendedFor: <<run-1>>) 3. That is a problem of the ruamel library that I use to read and write yaml-files. You still have that problem with v2.2? I believe it's caused by the comments in the file and I worked around it by moving the Plugin section to the top. That worked very well for me, but maybe I should drop yaml and move to json if these problems remain (or wait for a better yaml library) Cheers, Marcel Op do 11 jul. 2019 om 18:09 schreef karl-koschutnig < [email protected]>: