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
#Creator: wfdb2mat
#Source: record 12063/ Start: [11:04:21.104]
The "start time", however, is deceptive: it's actually just the base time of the output record, as returned by mstimstr(0). (This, of course, makes no sense: the base time is recorded at the start of the header file, there's no need to put it in an info string.)
What would make sense - and what I'm sure was the original intention - would be for the comment to record the starting time relative to the original input record (i.e., the "-f" argument to wfdb2mat.) This is not equivalent to the base time of the new record if there is no base time, or if there's no base date and the new record begins after the first day of the original record.
The text was updated successfully, but these errors were encountered:
wfdb2mat adds info strings along the lines of
The "start time", however, is deceptive: it's actually just the base time of the output record, as returned by mstimstr(0). (This, of course, makes no sense: the base time is recorded at the start of the header file, there's no need to put it in an info string.)
What would make sense - and what I'm sure was the original intention - would be for the comment to record the starting time relative to the original input record (i.e., the "-f" argument to wfdb2mat.) This is not equivalent to the base time of the new record if there is no base time, or if there's no base date and the new record begins after the first day of the original record.
The text was updated successfully, but these errors were encountered: