In the current implementation we can define only 1 key for hdf5 data (in MESc files it is /MSession_0/MUnit_0/Channel_0). For multi channel measurement the further channels data access under /MSession_0/MUnit_0/Channel_1 /MSession_0/MUnit_0/Channel_2...
I have attached a sample MESc (hdf5) file tree structure.
Attempted alternative approaches:
I have tried to set the parent for the data (/MSession_0/MUnit_0) but it not works and also tried (/MSession_0/MUnit0/Channel*)
Feature you'd like to see:
In the current implementation we can define only 1 key for hdf5 data (in MESc files it is /MSession_0/MUnit_0/Channel_0). For multi channel measurement the further channels data access under /MSession_0/MUnit_0/Channel_1 /MSession_0/MUnit_0/Channel_2... I have attached a sample MESc (hdf5) file tree structure.
Attempted alternative approaches:
I have tried to set the parent for the data (/MSession_0/MUnit_0) but it not works and also tried (/MSession_0/MUnit0/Channel*)
Additional Context
No response