-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MontSection
and FrameSet
files are incompatible with single df model
#13
Comments
At least for the
becomes this:
|
@alisterburt thanks for the ping :) @jojoelfe I might be misunderstanding the design you mention, but wouldn't sections other than I think I like the option of returning a
|
Thanks for the feedback both! It's great to see what everyone would want @jojoelfe replicating the data from the Some options
I think I prefer option 1 of these two as it's less magical and more predictable @m-albert because the Final question would be on how we handle single If we've got consensus here I'll go ahead and implement, unless either of you particularly wants to submit a PR? Happy either way, just let me know |
Solution 1 would definitely be okay with me, thanks for asking :) |
Number 1 is definitely ok. I wonder if it would make sense to check if the values are the same for a column in
This is not necessarily true. SerialEM allows for multiple montages in one mrc files. I've submitted PR #14 to add a test for such a case. Not sure what would be the best way there. I still think merging and presenting a flat |
brill - I'll have a play around this weekend then! Thanks again both |
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 adict[str, pd.DataFrame]
with one df stored underZValue
and one stored atFrameSet
/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?
The text was updated successfully, but these errors were encountered: