Closed bendichter closed 5 years ago
As far as I understand MultiContainerInterface
is a class in PyNWB to help implement interface classes for NWBDataInterface
types that contain a collection of specific set of neurodata_types
, e.g., the LFP
type containing a set of ElectricalSeries
. From the perspective of the format specification, I don't think there is really anything particular about MultiContainerInterface
that is different from NWBDataInterface
. The difference lies really in functionality on the API side, rather than the structure in the spec. As such, I think the current structure makes sense, i.e.., in the format specification you have to inherit from NWBDataInterface
and then on the API side you can implement it via MultiContainerInterface
.
I was trying to get this working for auto-generation of classes with get_class
but now that I think about it I don't think it's necessary. Besides, matnwb manages to auto-generate these with the current schema, and I'd rather be similar to them where possible.
error:
Do we want types to be able to inherit from
MultiContainerInterface
? To fix this, we'd have to define it innwb.base.yaml
and register it incore.py