[mnc2bids] Erroneous "should be a number" warning

[maximemulder]

While trying to convert some dataset to the BIDS format, I encounter the following warning:

WARNING: Cannot compute EffectiveEchoSpacing & TotalReadoutTime for bic_372712_Q1K_dwi_acq_b0_PA_002.mnc
                'dicom_0x0019:el_0x1028' should be a number. Its value is 19.778
                'dicom_0x0051:el_0x100b' should be a number. Its value is 192
                => This is unfortunately the result of a bad dcm2mnc conversion...

This looks obviously wrong. I am on the up-to-date main branch (so this is not the problem fixed by #1127).

[maximemulder]

Pinging @cmadjar so you get this on your radar.

[cmadjar]

@maximemulder I am confused by should be a number. Its value is 19.778. How can you get a should be a number when the value appears to be a number?

[maximemulder]

I haven't looked into it in details yet, but I would bet it probably stores or saves some number as a string somewhere, and when it expects a number, it gets this string and is confused. I guess adding a parseInt / parseFloat somewhere would fix the bug, although if the problem is with dcm2mnc, it would likely better to fix it on their side.