Replies: 3 comments 3 replies
-
Well, you could store an array of NPES-formatted data in a JSON file. Then you would just append the NPES data entry to your file whenever and how often you want to refresh it, not? You could then use the sample location and time fields, as well as the spectra, measurement time, etc. for your recordings in between the file saves. |
Beta Was this translation helpful? Give feedback.
-
Matthias,
Where did you send this message from?
At the moment I over write the json file with every loop, but yes it is also possible to append the files in a long list, this would allow you to scroll backwards, but I am not sure if it is worth the extra disk space.
Files would add up to around 14 MB per hour, so not really gigantic.
Steven
… On 7 Feb 2023, at 11:17 pm, NuclearPhoenix ***@***.***> wrote:
Well, you could store an array of NPES-formatted data in a JSON file. Then you would just append the NPES data entry to your file whenever and how often you want to refresh it, not?
—
Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR65OOTS66GPVP2LAXWRPM3WWI4MHANCNFSM6AAAAAAUT4NGOE>.
You are receiving this because you are subscribed to this thread.
|
Beta Was this translation helpful? Give feedback.
-
Revisiting this discussion since it's an interesting point. Basically if I understand you correctly you're asking about storing data like in an array to have a time-evolution of spectra with all of the misc telemetry and other things. Currently with v1, you can already store time, location and other sample info with the spectrum. Basically what I would have to do is add a feature to the standard that allows storing an array of multiple entries to allow for an arbitrary number of the current spectrum data types in one single file. What do you think? |
Beta Was this translation helpful? Give feedback.
-
I noticed that Gamma-MCA uses the NPES-JSON data schema to store measured values. That seems to be a great improvement to open-source scientific instruments!
It could be even more improved if there could be a possibility to store position and time (ad maybe some other metadata) according to the measured spectra.
The reference application for that situation is searching for some elements along a path e.g. to discover old traffic routes. The other option is to measure the radiation dose on board of aircraft, where both intensity and spectra or mixed radiation field could change significantly.
The ideal solution I think could be storing every measuring instrument message as a properly formatted JSON field.
Beta Was this translation helpful? Give feedback.
All reactions