Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Records are out of order, cannot continue. #8

Open
regnans opened this issue Jan 11, 2021 · 3 comments
Open

Records are out of order, cannot continue. #8

regnans opened this issue Jan 11, 2021 · 3 comments

Comments

@regnans
Copy link

regnans commented Jan 11, 2021

Chamber 1 and 2 ran, Level0to1, but then it failed on Chamber 3. Could this be catching an error in the recording of the data, where the timestamp has been messed up? (BTW, the status messages for every line are really instructive. Nice one.)

2021-01-10 20:09:34,639 [INFO]: [Chamber 3 - Black_Min1.dat]    Checking record order...
2021-01-10 20:09:34,654 [INFO]: [Chamber 3 - Black_Min1.dat]            Records are out of order, cannot continue.
@amcmahon01
Copy link
Member

Glad it's helpful, I tried to make the logs very detailed enough to make the process relatively transparent. Yes, this error often happens early in the season when we're setting things up and the clocks aren't synced yet. I haven't figured out a good way to handle it programmatically, hence the full stop. It looks like it would be helpful for the script to provide a note with what line of the source it failed on though, so I'll add that to my to-do.

@regnans
Copy link
Author

regnans commented Jan 11, 2021

It turns out that the very first row was out of sync. However deleting that didn't help. Then there were around 10 data rows before a time break. I deleted that block, also no success. (I saved the original file in a separate folder).
A line number report on this error would be very useful indeed!

@regnans
Copy link
Author

regnans commented Jan 19, 2021

Looking at the 2019 chamber data in more detail, all of the chamber files have some issues from start of collection until end 21 June. Blocks of data are duplicated, and, for example, data from the 19th is duplicated after the first records from the 20th, so that would trigger the out of order warning.

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

No branches or pull requests

2 participants