-
Notifications
You must be signed in to change notification settings - Fork 2
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
Scans appearing on distiller out of sequence #1195
Comments
Interesting, so we sort the scans by their creation time. The creation time is obtained by running stat on the status file generated by the receiver code. So my guess is that during the time between the scan being detected and stat being run on the file, the file gets updated again ( the receiver code keep write the file ), although I am not sure if that would things to get out of order with the next scan. Is the |
The most recent JSON status file is continuously updated by the receiver code. So,
The I vote for using the |
OK, we put together a PR that uses the time` field. |
Scans occasionally appear on distiller out of sequence (e.g. ID no 22062, 22063, acquired 15/11/2024). This usually happens when we are taking data rapidly, such as with the multiscan acquisition. This issue is mostly cosmetic and I believe that the correct data populates the correct scans, but this issue affects the system for determining whether a scan has finished acquiring as the most recently acquired scan won't appear as the first entry in the list when this happens.
The text was updated successfully, but these errors were encountered: