Telco 20261026

Date

Monday, 26th Oct, 15:00 UTC

Connect

Agenda

  • Validator demo (RO)

  • NXxas

  • PRs

  • is there anyone that the NIAC thinks should be invited to the Zulip channel that hasn’t been?

Present

NIAC - RB, FD, RO, WdN, AB, HB, Other - Marius Retegen, Sebastian Busch, Iryna Lypova, Lukas P

Minutes

1. WdN: NXDL technical sub meeting

- motivation is dont want to bog down general NIAC meeting to talk about technical NXDL topics
- Zulip will be used to take a poll of when interested parties can meet, and then a meeting will be scheduled

2. RO: Demo of validator in in builtin api of NeXpy

  • demo’d interactive validate, from NeXypy and also has nxvalidate CLI tool

3. Followup on in person meeting regarding NXxas

  • NXxas

    • WdN: review of NXxas discussion from in face to face meeting

    • MR: How do we move forward from the old definition to the new

      • first create a file that validated against current NXxas definition

      • Used nxvalidate that RO just presented to validate the file

        • element and edge which did not exist in old definition, but now exist in new definition

    • WdN: names that do/dont exist in the old and new definitions

    • AB: we need to deprecate fields that no longer have desired meaning in new definition

    • HB: all defs have meaning over time, defs will exist with deprecated fields forever

      • validators will need to be able to handle deprecated fields by indicating what should be done with the deprecated fields

      • should be a way to find all deprecated fields in our files and indicate what to do with them, maybe in the docstring for the deprecated field

    • MR: how does a file generated with the old definition get validated against the new definition

    • AB: we asked back at the face to face “is anyone using this current def”? and we found out there was

    • FD: we could indicate that older files (with deprecated fields) will not validate against the new definition,

    • HB: there shouldnt be “old “ and “new” there should be a single “always changing def” and the validator should inform the user

      • there should be documentation to telling the user how to deal with deprecated field

    • AB: we would use the “reason” field

    • AB: this will all voted on at the face to face so as soon as comments are resolved it can be merged

    • MR: AB can you resolve your comments on this PR

    • AB: will do in next day or two

  • MR: NXcollection is used for raw_data because it is not validated, we would like to keep raw_data and keep the processing step because it adds meaning to the raw_data

    • so both need to exist, so this is my question can we use NXcollection for this purpose

  • AB: nothing I have heard negates the use of NXdata for this purpose because it is not structured

  • MR: I want to store the output of the computational code, the format is unknown

  • AB: ok its a binary blob so maybe NXcollection is the right choice, if down the road you find a pattern in its use over the next 10 years you could move this into something that has meaning because it is understood then

4. FD: Backlog from f2f meeting