-
Notifications
You must be signed in to change notification settings - Fork 8
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
base: fairmat
Are you sure you want to change the base?
Conversation
…ded and eneumeration open2
There was a problem hiding this 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] |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Fix issue for
nameType
Open enumeration
,NXcomponent instead of the NXobject where needed
andremove NXidentifier instead use a field inplace
xrd_pan
NXsts