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
The date_created field in the .continuous file header has a format which is both hard to parse and is ambiguous. The date format seems to be "d-u-yyyy hmms" where d is the day of the month, u is the three letter abbreviation for the month, yyyy is the year, h is one or two digit hour, mm is the two digit minute, and s is the one or two digit second. Times can therefore be four to six digits long, and many five digit times can have two interpretations. For example the time "11111" could be parsed as either 11:11:01 or 01:11:11.
The text was updated successfully, but these errors were encountered:
galenlynch
added a commit
to galenlynch/plugin-GUI
that referenced
this issue
Apr 26, 2017
As discussed in open-ephys#129, the date_created field of .continuous file headers does
not have fixed width days of the month, hours, or seconds, which makes parsing
the header difficult and often ambiguous. I have changed the RecordNode class
to produce fixed width datestrings, which should fix this problem.
I was unable to compile with these changes, but the previous commit (226bfab)
won't compile for me either. However, I can make these changes to an earlier
commit and compile successfully.
Hi,
The date_created field in the .continuous file header has a format which is both hard to parse and is ambiguous. The date format seems to be "d-u-yyyy hmms" where d is the day of the month, u is the three letter abbreviation for the month, yyyy is the year, h is one or two digit hour, mm is the two digit minute, and s is the one or two digit second. Times can therefore be four to six digits long, and many five digit times can have two interpretations. For example the time "11111" could be parsed as either 11:11:01 or 01:11:11.
The text was updated successfully, but these errors were encountered: