Skip to content

๐Ÿ“‚ Novel JSON Schema targeted at storing nuclear physics energy spectra (NPES) data.

License

Notifications You must be signed in to change notification settings

OpenGammaProject/NPES-JSON

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

65 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

NPES-JSON

GitHub release (latest by date) GitHub GitHub deployments

Novel JSON Schema targeted at storing Nuclear Physics Energy Spectra and meta data in a single data object to be parsed by an API or stored in files. Mainly used in gamma spectrometry for energy and background energy spectra, but it can be used for any kind of application where pulse height diagrams (i.e., histogram data) are used. This was originally inspired by the XML files used in the program BecqMoni (Japanese MCA) and strives to be an open, well-documented, smaller-in-size and easier-to-parse file standard for universal use. Based on JSON Schema Draft-07, therefore it can also be used to transfer data in an API context.

Why

Other than very simple CSV files there is no real widespread and universal file format in gamma spectrometry, especially one that also allows saving other meta data on top of the spectrum. Few programs use the XML files proposed by BecqMoni, but this is not a standardized format, but more of an informal aggreement on some parts of that format. On top of that, due to the nature of XML, files can quickly get unreasonably large in size. To solve these issues, IMHO the best solution is to use JSON with a JSON Schema, which is much smaller, partly even simpler to parse due to its widespread nature and can be validated too.

NPES JSON can also be used in web APIs to transfer spectra data between clients and/or servers. Due to it being JSON, parsing is trivial in JavaScript and very easy in any other web-related programming language. In this context you can also validate API requests, which makes data handling a breeze and is overall extremely helpful. It's also straight-forward to implement in Python, which is used a lot in data science and pretty much copies the entire data structure of JSON with its dictionary data types.

Due to its relative small size it is also suitable for embedded applications where you need more meta data than just the plain pulse height histogram (e.g. like a simple CSV file). It allows you to save all the relevant meta data in a compact format that can be opened with any of the supported programs.

Benefits for developers

  • Complete and open documentation on the data structure.
  • Files can be validated before exporting or importing/loading.
  • Can be used to transfer data in an API context or similar use cases.
  • JSON can be parsed easily in every major programming language and it is trivial to serialize/deserialize in JavaScript and Python.
  • Complete file compatibility with every other program adhering to this standard.

Benefits for end users

  • Much smaller file size compared to XML files containing the same information (around 10%).
  • Immediate interoperability between different programs - if it imports in one program you can be sure it will correctly import in any other piece of software that supports the standard.
  • If something goes wrong, you can validate files to see exactly what issues there are.
  • You can easily manipulate the data in 3rd party software or your own scripts (especially in Python for example) due to its simple structure.

Documentation

The Schema(s) can be found in schema.

Example files that validate can be found in examples.

For a full, human-readable documentation please head to https://opengammaproject.github.io/NPES-JSON/.

JSON Schema implementation docs can be found here: http://json-schema.org/implementations.html

The documentation has been generated using JSON Schema for Humans using the command generate-schema-doc .\schema\ index.html --config-file .\jsfh-conf.yaml.

Changes upon v1

  • It is now possible to store multiple spectra in one file in an array structure. There is basically no limit on the number of spectra, so you can for example use it to combine files or to store spectra in a data logger context as discussed in #2. This basically takes the v1 of the standard, puts a bracket around all instances except for schemaVersion and allows you to have multiple entries in that array.

Future Improvements

  • None at the moment :)

Supported Software

This is probably not a fully comprehensive list, so if you are using this data format, feel free to add your program and create a PR.

Supported Hardware

This is probably not a fully comprehensive list, so if you are using this data format, feel free to add your hardware/device and create a PR.