I've implemented this by treating the TI volume (4d timeseries) as an ASLImage object. That way, we can call the same methods as the ASL data itself to group it by PLD, rearrange for multi-time, etc etc, which will hopefully avoid bugs caused by mismatching the TI data with the data timepoints.
When a TI volume is supplied, the code will print warnings to explain that this overrides all other timing data, but it won't throw an explicit error if the user has also set TIs, PLDs via the normal route. In fact, the user still needs to do that for the sake of checking the time series has the right length.
I've implemented this by treating the TI volume (4d timeseries) as an ASLImage object. That way, we can call the same methods as the ASL data itself to group it by PLD, rearrange for multi-time, etc etc, which will hopefully avoid bugs caused by mismatching the TI data with the data timepoints.
When a TI volume is supplied, the code will print warnings to explain that this overrides all other timing data, but it won't throw an explicit error if the user has also set TIs, PLDs via the normal route. In fact, the user still needs to do that for the sake of checking the time series has the right length.