-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
CTF data loading with non-zero compensation grade error #6488
Comments
Can you upload this dataset somewhere? It's weird that there is a reference magnetometer channel that has had gradient compensation applied to it. Do you know where this dataset was acquired, and with which CTF acquisition software version? |
Eric this issue comes from one of our attendees in Gasgow. We can try to take this offline if data sharing would turn out to be difficult. Perhaps we should also try reading it with MNE-C. |
+1 to try with mne-c
… |
Thank you all very much. This data has both MEG and EEG recorded, I guess the problem is might because the EEG channel. Let me check the validation of data with fieldtrip first tomorrow. |
Hi! I got the same error with a mixed EEG/MEG dataset. Maybe the CTF system uses the eeg as a ref and thus all magnetometers are compensated, even the REF ones. |
@bloyl as our CTF expert do you have any thought on this? do we some tiny dataset to replicate this? |
I agree that it seems odd that a ref magnetometer would have gradient compensation applied. Is there a dataset available? |
Hi! I have the same error with a dataset containing only MEG data. |
I didn't think the reference channels changed when you applied gradient
compensation. So I'm not sure how/why the reference channels get marked as
having compensation applied. Our data that is acquired with 3rd order
compensation turned on doesn't have this problem. Maybe if I turn it on/off
on processing I could get a dataset in this state.
Nichalas, is this raw ctf data or has it been processed at all? If so what
software did you use to do the processing.
I'll try this week to open this dataset using ctf's software and see what
happens.
…On Sun, Jul 5, 2020, 10:26 AM Alexandre Gramfort ***@***.***> wrote:
I can replicate the problem too. I have no clue why we impose a
compensation grade of 0 for reference channels.
in the shared dataset there are 27 reference channels with a compensation
grade of 1 and makes our reader crash.
@bloyl <https://github.com/bloyl> or @larsoner
<https://github.com/larsoner> any idea?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6488 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKTXHL5M4XGWYSOD3JJXITR2CEP5ANCNFSM4H3JZ4SA>
.
|
We tried to apply an offline 3rd order compensation and the error remained. dataset: https://drive.google.com/file/d/16yZ0fdT24i3lK3D6jvgpn70VWBmZXFG1/view?usp=sharing |
so you have a pb with data recorded using 1st order without any
processing applied.
If so we should fix this. Can you read the files easily with
Brainstorm or Fieldtrip?
|
Yes, I think this is the case. |
I added this back in #3440. Perhaps we can try disabling the check and check to see if forwards computed in both cases match...? |
I was trying to load CTF data. I only put the .ds dir as the first parameter, all other parameters are default value. Then meet a runtime error that "RuntimeError: Reference magnetometer channel with non-zero compensation grade 1".
the code and the results are in the below
Example:
Actual results
The text was updated successfully, but these errors were encountered: