With the new (to-be-finalized) tracker config schema it should be easy to add something specific to the raw BIDS data. At one point we wanted a BIDS bagel separate from the imaging (derivatives) bagel and the tabular bagel. If that's the case then I think this should be a separate command (nipoppy track-bids or something). And conceptually I think it makes sense to separate the bagels for the raw BIDS and the processed derivatives.
Implementation-wise this should not be hard to do as we would only have to specify file path patterns, so we only need to decide where this config should go. Also requires #226 to be done since the phases/stages granularity would be important here, otherwise the doughnut file can tell users True/False for if a participant/session has BIDS data.
With the new (to-be-finalized) tracker config schema it should be easy to add something specific to the raw BIDS data. At one point we wanted a BIDS bagel separate from the imaging (derivatives) bagel and the tabular bagel. If that's the case then I think this should be a separate command (
nipoppy track-bidsor something). And conceptually I think it makes sense to separate the bagels for the raw BIDS and the processed derivatives.Implementation-wise this should not be hard to do as we would only have to specify file path patterns, so we only need to decide where this config should go. Also requires #226 to be done since the phases/stages granularity would be important here, otherwise the doughnut file can tell users
True/Falsefor if a participant/session has BIDS data.