Skip to content
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

Write a getting started with QuSpin OPM data #807

Open
robertoostenveld opened this issue Sep 20, 2024 · 6 comments
Open

Write a getting started with QuSpin OPM data #807

robertoostenveld opened this issue Sep 20, 2024 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@robertoostenveld
Copy link
Member

I am now discussing this with @dbobela406 and details will follow here. Note that this is not only about writing some documentation, but the supporting code should of course also be implemented.

@robertoostenveld
Copy link
Member Author

See also mne-tools/mne-python#8671

@robertoostenveld robertoostenveld self-assigned this Sep 20, 2024
@robertoostenveld robertoostenveld added the enhancement New feature or request label Sep 20, 2024
@dbobela406
Copy link

dbobela406 commented Sep 26, 2024

Hi Robert et al.

Dave Bobela here from QuSpin. To kick things off on this thread, I'm uploading some example data from the QuSpin Neuro-1 system, so that users can understand the formatting, and begin writing importer scripts for your application. This should cover the use case of saving data directly from QuSpin user interface.

I'm also uploading a pdf file that documents the data formatting--please refer to this for a general overview. If I've forgotten something, or if you need clarification, please reach out.

Briefly, the QuSpin N1 user interface generates two files when saving data: one file that contains sensor measurement data (a labview ".lvm" file), and one file containing sensor and system level information. Here are the example files (note, I had to attach a .txt extension to the .lvm file to satisfy GitHub's requirements. Remove this extension):

QuSpin Example N1 Dataset_10-14-24_array1.lvm.txt

QuSpin Example N1 Dataset_10-14-24_array1_calibrations.txt

QuSpin_Data_File_Format_Description.pdf

@Mettphysik
Copy link

To kick things off on this thread, I'm uploading some example data from the QuSpin Neuro-1 system, so that users can understand the formatting, and begin writing importer scripts for your application. This should cover the use case of saving data directly from QuSpin user interface.

Is it possible that the .lvm file is corrupted? I am using lvm-read (https://pypi.org/project/lvm-read/) which works fine with my own Neuro-1 data, but not with the provided file. It looks like there are 5 data points for the channels X1 to Y62 but only 4 data points for the remaining channels.

I'm not directly working on this issue, but I guess this might still be of interest here.

@dbobela406
Copy link

Thanks Mettphysik for pointing this out and indeed you were correct about the file. I updated the links from my September 26th post, above, with valid data that can be opened using lvm-read (https://pypi.org/project/lvm-read/).

@robertoostenveld
Copy link
Member Author

Dear Dave,

Sorry for not following this up as planned. At the moment I am sick at home and not able to work on this. I hope to be back to work soon and will then pick this up again.

best
Robert

@dbobela406
Copy link

dbobela406 commented Oct 15, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants