Timestamp problem on some CSV data files from UKRAA Picomuon detector

This issue has affected some files written to SD cards on two PicoMuon detectors:

  1. Detector 56-501, running 0.1.26 software (John Savage)
  2. Detector 56-485-26, running 0.1.27 software (Andrew Thornett)

I attach some screenshots below from a short file as an example that shows the problem. The timestamp of 16:20:13 remains constant rather than changing as it ought to with each line.

I have tried to find a way of reliably reproducing the issue on the first detector by removing the SD card without unmounting it, several time. I have done this by just plucking the SD card from the unit and by unplugging the USB power. The SD card and files have survived this abuse and this abuse doesn’t seem to produce the static timestamp issue.

This raises the following questions:

  • Are any other units affected by this?
  • How important is unmounting the SD card really? – not that we should neglect this step, just asking.
  • Any ideas as to how the static timestamp issue arises and how to prevent it?
  • When the static timestamp issue arises, what time does the timestamp correspond to? E.g. the time when the recording started, or perhaps the time when the SD card was last removed?
  • I see the “ElapsedTime (ms)” field in the files and it looks as though timestamps can be reconstituted. Any comments?

John

By Admin

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.