Quick schema question: Should InversionTime support arrays like EchoTime does?

Hi everyone,

I’m a CS student currently working on understanding the BIDS codebase to help with some contributions, and I stumbled across something in the schema that I wanted to sanity check with you all.

While I was digging through the objects.yaml file, I noticed that fields like EchoTime and FlipAngle are defined to accept either a single number OR an array. That makes sense to me for handling multiple values in a sequence.

However, I noticed that InversionTime is currently restricted to just a single number.

Is there a specific scientific reason for that restriction? From a data structure perspective, it seemed a bit inconsistent. I assume that for things like MP2RAGE or T1 mapping, you might have multiple inversion times (e.g., [0.7, 2.5]), but right now the validator would technically flag that as a type error.

I’d be happy to open a small PR to allow arrays for InversionTime (just to match the pattern of the other fields), but I wanted to ask the domain experts here first in case I’m missing something obvious!

Thanks for the help!