Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix nymaType, NXidentifier, NXcomponent instead of NXobject where nee… #349

Open
wants to merge 6 commits into
base: fairmat
Choose a base branch
from

Conversation

RubelMozumder
Copy link

@RubelMozumder RubelMozumder commented Mar 6, 2025

Fix issue for nameType Open enumeration, NXcomponent instead of the NXobject where needed and remove NXidentifier instead use a field inplace

  • SPM domain app defs and base classes
  • xrd_pan
  • specialize NXsts

Copy link
Collaborator

@lukaspie lukaspie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was expecting here also changes to the base classes used in SPM like NXlock_in, NXrcs, etc. that should inherit from NXcomponent as well.

enumeration: [contact mode, tapping mode, non-contact mode, Kelvin probe, electric force]
enumeration:
open_enum: true
items: [contact mode, tapping mode, non-contact mode, Kelvin probe, electric force]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What other modes are possible? Is an open enum needed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A single mode can be referred by more than one name e.g. contact mode can come in two flavor such as static force mode (sometime called as contact mode as well) and Letheral force mode. Most of the common modes are included here. I just kept open if any other modes are not be there or mode are included in the list but coming with a different name.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But that is the whole point of standardization though, that the community agrees on one term for a concept if multiple have been used so far.

I would suggest to at least expand this list if it is expected that people use things like lateral force mode as well.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see now that lateral force mode has been added. Are there more of such modes that are commonly used? Should be added here as well.

Link to the group
ENTRY[entry]/experiment_instrument/height_piezo_sensor.

Note: group name (e.g. entry in ENTRY[entry]) inside the square bracket would be the exact instancename of the base class (e.g. NXentry).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note: group name (e.g. entry in ENTRY[entry]) inside the square bracket would be the exact instancename of the base class (e.g. NXentry).
Note: the name of the NXentry group, which is written inside the square bracket (i.e., entry in ENTRY[entry]), must be the exact name of the instance in the NeXus file (e.g., "my_entry").

And similar in all places this is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants