-
Notifications
You must be signed in to change notification settings - Fork 92
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
add test for ieeg coord_frame read issue #961 #962
Conversation
Hello! 👋 Thanks for opening your first pull request here! ❤️ We will try to get back to you soon. 🚴🏽♂️ |
@timonmerk |
@timonmerk I pushed here to see the pb. I get:
you see you have 2 clear warnings. Does it help to address them? @alexrockhill thoughts? |
I left more verbose comments in #961 but in short, I think there is a small PR here to allow passing of the specific template coordinate frame to |
Hmmm, I looked into adding support for the standard template coordinate frames (https://bids-specification.readthedocs.io/en/stable/99-appendices/08-coordinate-systems.html#standard-template-identifiers) and the issue is that MNE-Python doesn't have representations for these internally (https://github.com/mne-tools/mne-python/blob/6d0aa2572221c9a710c5965fab96042f3cf9ad3c/mne/transforms.py#L33-L60). So MNE-BIDS could write out this field with a keyword argument such as I think support for the template coordinate frames is something that would be great to add, but it would take a bit of doing. For now, I think the best solution is to have the coordinate frame set to other upon reading and then you know that it's |
it's a bit too far from my present needs for me to fully understand what is
at stake here.
we could discuss this during a next mne dev meeting
… Message ID: ***@***.***>
|
Sounds good re discussing at a the next dev meeting. From a brief conversation with @larsoner, I think we could quickly add a PR to MNE-Python to make all the BIDS standard templates assignable to the montage but then the issue would be that the |
Ok, this PR should fully solve this issue/do what this PR had started #983, let me know if that works with your test data @timonmerk, I believe it should |
Hey @alexrockhill, thanks for working so hard on this problem! click details:
|
Looks like you're not using the new branch, that logger statement was deleted in an earlier PR. To get the new branch, you can do:
I think you might be missing the uninstall mne_bids bit and have an old version that's actually getting imported. |
Thanks a lot @alexrockhill! I did not know that the "manual" checkout is required to checkout a pull request. I did The result for the specific |
So on the issue (mne-tools/mne-python#10405) on the main MNE-Python, we decided that MNE-Python will not have coordinate frame integers for each of the templates because that will give the wrong impression that we fully support those when we don't. I explain it pretty thoroughly at the end of https://6099-89170358-gh.circle-artifacts.com/0/dev/auto_examples/convert_ieeg_to_bids.html, you might want to follow the steps there. |
@timonmerk could you please:
The last steps assume you have a git remote "upstream" -- check EDIT: Alternatively, you can invite me as a collaborator to your repo, and I'll do these steps myself :-) |
New Pull Request: #1051 |
@sappelhoff, thanks for those detailed instructions. I assume you wanted to change the branch name of the pull request through those steps? |
Yes, PRs should never be submitted from your main branch :) it'll screw up your workflow if you ever want to create more than one branch at a time. Practically you having this PR on your main branch meant that I got an email notification whenever the ci on your repo ran according to schedule (one a day). And I couldn't figure out how to change this manually. So two birds with one stone: stop the emails, and fix your workflow. :) Thanks for doing this. And yes, the issue is still relevant imho. |
Ahh ok, thanks @sappelhoff. That makes sense!
You can see that I added the upstream link, but the reset failed for some reason.. |
I'd love to improve that but I couldn't get any traction in the BIDS community making the changes needed over there to make it make any sense by the time it gets to mne. There's issues with licensing the T1 images if BIDS were to repost them is the main thing. I think it's a bit of a moot point anyway because I would recommend sharing in the patients' coordinate frame and not template so that data users can choose their own template (with a defaced T1). |
But step 4 worked, right? Perhaps you need to run If that doesn't work, try |
@timonmerk please let me know once you tried this and whether it works! as of now, your main branch is still out of sync: https://github.com/timonmerk/mne-bids |
@sappelhoff Now it worked, thanks!
|
Perfect, now you need to |
Ahh, forgot that last step. Now it should be up to date. |
PR Description
This PR serves as a unit test description for Issue #961. I uploaded a separate "ieeg_bids" dataset in
mne_bids\tests\data\
(since I did not find a fitting one on openneuro).As described in Issue #723 , mne_bids does not correctly read the "iEEGCoordinateSystem" and simply overwrites it with "other".