Open mattcieslak opened 7 months ago
the "requirements" file for completeness is really only useful for bookkeeping. This could be optional, and doesn't really impact the evaluation of whether processing was incomplete.
for part 3, we can use bids filters to find files that will produce outputs. Then we can use these files to predict outputs
also thinking about accounting for runs in completeness - how would we treat run 1 versus run 2 cases?
Part 1: Assumptions
Part 2: do we want to wade into the territory of deciding what "completeness" means?
Part 3: How do we represent "a unit of input" in code? We have _bold, _dwi and _asl inputs. In dwi specifically, they will almost certainly (although not guaranteed) be concatenated. There are also numerous auxiliary files that can go with the input images (_sbref, _part-, etc) that we don't expect outputs to be created for.
Ideally, the "unit of input" is all we'll need to figure out what the expected outputs are in the derivatives.