You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using the toolbox for many years, but I'm facing a new problem. In this dataset, Physiological recordings (finger pulse sensor + belt for the resp) and EMG data were recorded simultaneously, leading to a very high sampling rate (2500Hz).
I've used "custom" option with a .txt file for puls, resp and time and I get no error when I run the script.
When look into the phase calculation, I saw some weird results and in this participant for example, you can see 0 values in the phase calculation of the respiratory data (while the raw data is very good).
When I down sampled x10 (250Hz) the problem seems to disappear.
Do you think that it can be related to the sampling rate of the data or did I miss something else? Thank you in advance!
Thank you for being a loyal PhysIO user - I am happy to hear it has been a useful tool to you for many years.
Also, my apologies for the delayed reply. This is an interesting behavior. What strikes me is that there are only a few sections of the time series affected, for example, between scan 60 and 80. Would you be able to provide the Matlab figs or even the complete physio_out folder for the analysis with and without downsampling, so that I can have a closer look at the data and zoom into these regions?
Dear developers,
I've been using the toolbox for many years, but I'm facing a new problem. In this dataset, Physiological recordings (finger pulse sensor + belt for the resp) and EMG data were recorded simultaneously, leading to a very high sampling rate (2500Hz).
I've used "custom" option with a .txt file for puls, resp and time and I get no error when I run the script.
When look into the phase calculation, I saw some weird results and in this participant for example, you can see 0 values in the phase calculation of the respiratory data (while the raw data is very good).
When I down sampled x10 (250Hz) the problem seems to disappear.
Do you think that it can be related to the sampling rate of the data or did I miss something else? Thank you in advance!
Caroline
output_Tapas_fmri_CL.pdf
The text was updated successfully, but these errors were encountered: