Simplified NPESv2 Scheme

[ssesselmann]

Mattias,

Can you confirm if the following scheme would be compliant with your v2 scheme, if so I will add a few new fields to IMPULSE so users can add sample info.

Steven

{
"schemaVersion":"NPESv2", 
"deviceData":{
                   "softwareName":"IMPULSE",
	           "deviceName": "AUDIO-CODEC",
			   },
"sampleInfo":{
                 "name": " ", 
                 "location":" ",
                 "note": " ",
	},
},
	"resultData":{
		"startTime":1703299940.711352,
		"endTime":1703299944.724111,
		"energySpectrum":{
			"numberOfChannels":1024,
			"energyCalibration":{
				"polynomialOrder":2,
				"coefficients":[0,3,0]
			},
		"validPulseCount":155,
		"measurementTime":4,
		"spectrum":[0,0,0,0,....]
		}
	}
}

[NuclearPhoenixx]

Hi Steven,

thanks for taking the time to look into this.

There are a two issues with your data:

• deviceData, sampleInfo and resultData need to be in a separate object (noted by the extra {}) and that in turn has to be inside the data array (this is the "data": [] part). This is the new thing about the v2 schema, you can have an arbitrary amount of objects inside this "data" array.
• startTime and endTime need to be a RFC 3339 date-time string (ISO8601 format), same like with the v1 schema.

Other than that, it validates so I fixed the issues for you. Don't mind the extra line breaks or similar cosmetic formatting, but here are the "correct" contents:

{
  "schemaVersion": "NPESv2",
  "data": [
    {
      "deviceData": {
        "softwareName": "IMPULSE",
        "deviceName": "AUDIO-CODEC"
      },
      "sampleInfo": {
        "name": " ",
        "location": " ",
        "note": " "
      },
      "resultData": {
        "startTime": "2023-12-23T13:01:32+00:00",
        "endTime": "2023-12-23T13:01:32+00:00",
        "energySpectrum": {
          "numberOfChannels": 1024,
          "energyCalibration": {
            "polynomialOrder": 2,
            "coefficients": [
              0,
              3,
              0
            ]
          },
          "validPulseCount": 155,
          "measurementTime": 4,
          "spectrum": [
            0,
            0,
            0,
            0
          ]
        }
      }
    }
  ]
}

You can also double-check that it validates on this website if you like: https://www.jsonschemavalidator.net/

Just copy and paste your file contents to the right text box and the schema contents to the left one.

[ssesselmann]

Thanks Mattias,

Have a few of the usual family functions to attend over Christmas, but should have some time to implement this in a few days. Do you know if the NPESv2 is backwards compatible?

Steven

[NuclearPhoenixx]

Do you know if the NPESv2 is backwards compatible?

No, unfortunately it's not. Like I described in an earlier post, the fact that the data array is new makes it not fully backwards compatible. So the files won't load if you try to load it exactly like a v1 schema file.

However, the objects inside the data array are identical (except for the schemaVersion code) to the v1 schema, so it's very easy to adapt for loading both types. For example, for Gamma MCA literally the only thing I had to add was a function before the old NPESv1 loading that pulls the individual data objects out of the array. From there on it's the same procedure just like before.

[ssesselmann]

Mattias,

I have upgraded the 2D file type on IMPULSE to NPESv2 json and made itr backwards compatible so users can still open NPESv1 files.

I don't see any need in Impulse, to save multiple spectra in one file so to make it backwards compatible was just a simple if stetement.

if schemaVersion == "NPESv2": data = data["data"][0] # This makes it backwards compatible

Steven

[NuclearPhoenixx]

Neat, sounds great!