-
Notifications
You must be signed in to change notification settings - Fork 8
XA30 compatibility #9
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
base: master
Are you sure you want to change the base?
Conversation
|
also, the cardiac and respiratory files have a different number of channels. |
do not damage other file types
|
Hi @alexsayal , Apologies for the delays in responding. Thanks a lot for your work on the PR. I assume you tried your new proposed version to convert both new XA30 and VE11C files. Did it work properly? Unfortunately, I don't have time to check this at the moment, but if you did run it successfully, I will merge your PR. Thanks. |
|
Hello! I still have to test if these files are correctly read by the toolbox that processes them. As soon as I verify that I will let you know. Yes, I tested also with the VE11C files and it worked. The solution I used to distinguish them is not super elegant, but the physio files aren’t either, so… All the best, |
|
Right now, I believe this correctly converts the signals (.puls and .resp). However, trigger detection is not implemented, and as such the start times are incorrect. I can't be sure right now if these triggers can be retrieved from the .puls file or if we need to add the .ext file to help. |
|
Just a small update: I now understand that the .puls and .resp files alone do not contain the necessary information to extract the MRI acquisition start time. As such, it is not ok to infer the JSON The fields We will need to fetch the MRI start time from the .json associated with each functional run (field I will propose a solution for this as soon as I find the time. |
Hello,
I have started the pull request to read the new files generated by XA30.
Now the issue is the discrepancy between the log times and actual number of points (much larger than expected).