You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why NX_FLOAT rather than NX_NUMBER?
Something dimensionless is required to have units. Something unitless is
dimensionless, but also does
not have a units attribute. If this is to have units, what are they?
I was looking at the definition of attenuator_transmission in NXattenuator, which has NX_FLOAT. Since it is defined as
The nominal amount of the beam that gets through (transmitted intensity)/(incident intensity)
it seems as if it should be NX_DIMENSIONLESS ("units for fields where the units cancel out"). But in principle I don't mind - as long as it is consistent with NXattenuator/attenuator_transmission, right?
Instead of
NX_NUMBER {units=NX_UNITLESS}
it should be
NX_FLOAT {units=NX_DIMENSIONLESS}
as in
http://hdrmx.medsbio.org/manual/build/html/classes/base_classes/NXattenuator.html#nxattenuator
Vote with thumbs up/down
The text was updated successfully, but these errors were encountered: