Skip to content

Conversation

@alexsayal
Copy link

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).

@alexsayal
Copy link
Author

also, the cardiac and respiratory files have a different number of channels.
PULS has only 1, but RESP has 5

@pvelasco
Copy link
Collaborator

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.

@alexsayal
Copy link
Author

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,

@alexsayal
Copy link
Author

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.

@alexsayal
Copy link
Author

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 StartTime field based only on these two files.

The fields LogStartMDHTime and LogStopMDHTime indicate the start and stop times of the recording of each physiological signal, which are not synced to the MRI acquisition (it is manual) but use the same clock (MDH).

We will need to fetch the MRI start time from the .json associated with each functional run (field AcquisitionTime) to extract the displacement between the physiological and MRI recordings.

I will propose a solution for this as soon as I find the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants