Alejandro de la Vega

yep, pretty sure that's it. When I comment out the line that limits entities to `ALL_ENTITIES` , I get `RepetitionTime` as a meta-data entity: ``` In [16]: layout.get_collections(level='run', subject='NDARZY668NMV')[0].entities Out[16]:...

Is there a reason that entities for events are only allowed for `ALL_ENTITIES` then? This can definitely be worked around in fitlins. And as far as I'm concerned I'm fine...

It seems like part of the problem is that we are mashing together meta-data with entities. Entities are a strict set of reserved key words, which are defined as having...

Agreed its a spec problem, but can you elaborate what you mean by "shorthand queries"? Without flattening, if somebody said `.get(return_type='id', target='nested_metadata_field')`, that would still cause problems right?

Ah, sounds good to me. More generally, we could say that if the `target=` a reserved BIDS entity keyword, it will filter results to only those that match the corresponding...

Question: Would it ever make sense to specify a BIDS entity (i.e. `run`) only in a .json sidecar? Wouldn't that be illegal since it should necessarily already be specified in...

> Assuming the densification is done implicitly, I think you then won't need to do much else in `Convolve`; @adelavega's code should just treat the densified variable like any other...

Yep, I am adding at least a few tests for convolve as part of #411

I can't reproduce your problem using your example: ...: from pathlib import Path ...: from bids import BIDSLayout ...: import bids ...: ...: for i in range(10): ...: layout =...

Tried it on ds005 and I'm seeing something similar. I'll investigate.