Support was recently added for montage section and frameset mdoc files in #10 and #11
In an effort to continue with the 'single dataframe' model I added extra fields to the section data but this means we have two incompatible data types in the dataframe and a lot of nans
It seems like ZValue is used across all types of mdoc files when there are sets of images.
For FrameSet/MontSection files would it be better to return a dict[str, pd.DataFrame] with one df stored under ZValue and one stored at FrameSet/MontSection?
Given that there only ever seems to be one entry for FrameSet/MontSection maybe that table is better as a dict than a dataframe?
Thoughts @jojoelfe @m-albert?
Support was recently added for montage section and frameset mdoc files in #10 and #11
In an effort to continue with the 'single dataframe' model I added extra fields to the section data but this means we have two incompatible data types in the dataframe and a lot of nans
It seems like
ZValueis used across all types of mdoc files when there are sets of images.For
FrameSet/MontSectionfiles would it be better to return adict[str, pd.DataFrame]with one df stored underZValueand one stored atFrameSet/MontSection?Given that there only ever seems to be one entry for
FrameSet/MontSectionmaybe that table is better as a dict than a dataframe?Thoughts @jojoelfe @m-albert?