base class, extends NXobject


Parameters for controlling external conditions


No symbol table

Groups cited:

NXgeometry, NXnote, NXsensor, NXtransformations


name: (optional) NX_CHAR

Apparatus identification code/model number; e.g. OC100 011

short_name: (optional) NX_CHAR

Alternative short name, perhaps for dashboard display like a present Seblock name

type: (optional) NX_CHAR

Type of apparatus. This could be the SE codes in scheduling database; e.g. OC/100

description: (optional) NX_CHAR

Description of the apparatus; e.g. 100mm bore orange cryostat with Roots pump

program: (optional) NX_CHAR

Program controlling the apparatus; e.g. LabView VI name

depends_on: (optional) NX_CHAR

NeXus positions components by applying a set of translations and rotations to apply to the component starting from 0, 0, 0. The order of these operations is critical and forms what NeXus calls a dependency chain. The depends_on field defines the path to the top most operation of the dependency chain or the string “.” if located in the origin. Usually these operations are stored in a NXtransformations group. But NeXus allows them to be stored anywhere.

position: (optional) NXgeometry

The position and orientation of the apparatus. Note, it is recommended to use NXtransformations instead.

TRANSFORMATIONS: (optional) NXtransformations

This is the group recommended for holding the chain of translation and rotation operations necessary to position the component within the instrument. The dependency chain may however traverse similar groups in other component groups.

NOTE: (optional) NXnote

Additional information, LabView logs, digital photographs, etc

SENSOR: (optional) NXsensor

Hypertext Anchors

List of hypertext anchors for all groups, fields, attributes, and links defined in this class.

NXDL Source: