Chris Markiewicz

Does this occur when using the same version of pybids in each database, or could this be a problem of version mismatch?

Ah, here's a reproduction: ```python import bids layout = bids.BIDSLayout('/data/openneuro/ds000001') layout.save('/tmp/ds000001.db') layout.save('/tmp/ds000001.db') ``` I can't make it not fail in this way, going back to 0.14.0. So I'm not sure...

Needs to be resolved in BIDS: https://github.com/bids-standard/bids-specification/issues/1906

Agreed a more configurable solution would be nice. But I think that can wait until we depend on the BIDS schema, which does indicate extensions of data "files" that are...

If that's the case, then what you probably need to do is register a serializer for the type: ```python from pydra.utils.hash import register_serializer, Cache @register_serializer(torch.tensor) def bytes_repr_tensor(obj: torch.tensor, cache: Cache)...

You'll need to fork the repository, push to a branch on your own fork, and then create a pull request. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.

C extension objects are going to be difficult, as they may not be introspectable (or differentiable) in the same way as pure Python objects, using `__dict__` or `__slots__`. I believe...

You will need to use `validate=False` in `BIDSLayout()`. If `validate=True`, then files that do not pass the BIDS validator regular expressions are dropped.

If you call `layout.get()` and take the index of one of those files, you should be able to use `file.get_entities()` to see what BIDS attached to it.

Oh, I think this may be a bug where the configs are getting reset when you descend into derivatives. Try the following: ```Python add_config_paths(**{'bidsafq':'full/path/to/bids.json'}) layout = BIDSLayout(root_dir) layout.add_derivatives(Path(root_dir) / 'derivatives'...