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 am working some MIMIC ECGs which are 10 second each and have a sampling rate of 500Hz with total 5000 data points for every lead. I applied ecg_clean followed by ecg_peaks and used the required results in ecg_delineate. Everything works decently except for R_Onsets and R_Offsets. The R_Onset is detected very near to the P peak and R_Offset is detected sometimes correct but most of the time detected before the S peaks. I am mainly trying to calculate ecg-related intervals and for PR interval I need the correct R_Onsets.
Find some examples below:
I also compared the PR interval calculated with the help of Neurokit2 against the original values from the ECG metadata and I get,
PR_interval_orig = 130 msec
PR_interval_neurokit = 52 msec
Is there a way I could overcome this problem with already available Neurokit functions or appreciate some suggestions for a workaround.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
I am working some MIMIC ECGs which are 10 second each and have a sampling rate of 500Hz with total 5000 data points for every lead. I applied
ecg_clean
followed byecg_peaks
and used the required results inecg_delineate
. Everything works decently except for R_Onsets and R_Offsets. TheR_Onset
is detected very near to the P peak andR_Offset
is detected sometimes correct but most of the time detected before the S peaks. I am mainly trying to calculate ecg-related intervals and for PR interval I need the correct R_Onsets.Find some examples below:
I also compared the PR interval calculated with the help of Neurokit2 against the original values from the ECG metadata and I get,
PR_interval_orig = 130 msec
PR_interval_neurokit = 52 msec
Is there a way I could overcome this problem with already available Neurokit functions or appreciate some suggestions for a workaround.
Thank you!
The text was updated successfully, but these errors were encountered: