Alejandro de la Vega

I tried this with the database off, and this error persists, so at least we can rule out the loading/saving as being the problem. ...: for i in range(10): ...:...

I think just going off the base layout is a reasonable compromise. Isn't this what we decided on for the `__repr__` also?

Awesome. I think a full integration test using `BIDSLayoutV2` would be most informative. That is, is those of use that use `BIDSLayout` heavily try to use `BIDSLayoutV2` instead in our...

Agree, seems clunky. I think incremental setup could be the solution. As is my temporary solution was going to be to do setup separately for each run, but that might...

Great thanks. Definitely not worth it if its too much work, as I can just set up a new BIDSAnalysis instance for each run/design matrix i need to create. Not...

This issue is cropping up again-- now in Fitlins. cc: @effigies @tyarkoni For example, in the `ReadingBrainProject`, subject `24` only has runs 1-4, whereas all other subjects have 5 runs....

Just had a chat with @rwblair about this, and we thought that in the end a wizard is still of limited use to most people. Maybe I'm crazy and wildly...

It's possible this is fixed with the `modeling` module but I want to fix this for a maintenance pybids branch (and in general I think we should maintain that for...

@effigies do you know if this is still a problem? Seems important if by default pybids can't open fmriprep outputs

I'm a little confused: where did `PipelineDescription.Name` come from if its not in the spec? Was it just a proposal for BIDS-Derivatives that was over-written by `GeneratedBy`?