| Tasks which can be defined and executed by MDSplus. Used for data acquisition or automatic analysis.
| Application Program Interface
| A type of node which contains only structural information, it's USAGE is "structure"
| CURRENT SHOT
| The tree instance or shot accessed when the tree is opened using the special shot number specification of 0. This is usually the most recent experiment cycle or analysis run. Automated analysis jobs or visualization tools can use shot number 0 to access the most recent data.
| Can refer to the currently open tree (tree name and shot) or to the currently defined node default within that tree.
| A collection of nodes which is used to associate setup parameters, actions (task descriptions), and data for data acquisition or automated analysis
| Independent axes for SIGNALS
| The process of issuing ACTIONS to SERVERS for execution
| DISPATCH TABLE
| A collection of ACTIONS organized for execution by a SCHEDULER
| DISTRIBUTED TREES
| MDSplus client/server data access model where expression evaluation, data compression and decompression are performed by the client. Low level tree file access is performed by the mdsip server. This mode is activated by defining the tree paths using host[:port]::directory. This mode supports distributed subtrees (tree files residing on different hosts). This mode is not available for either client or server on OpenVMS.
| A global message issued by the MDSplus command SETEVENT. Events are used to synchronize data acquisition and analysis.
| A text string containing commands in the TDI language. All interfaces to MDSplus data are based on the evaluation of expressions
| EXTERNAL ROUTINES
| Routines written in standard programming languages, compiled and built into shared libraries. These can be called in TDI expressions.
| FULL PATH
| A text string which specifies an absolute reference to a node from the top of it's tree
| TDI functions. Procedures written in the TDI language which can be called by name in any expression.
| An important TDI function which allows users to retrieve metadata
| A Java version of SCOPE
| LOCAL ACCESS
| Access to tree files on a local file system or one on which files are directly accessible. Applications using local access do all tree file access, expression evaluation, data compression and decompression within the context of the application. No mdsip server is involved when using local access.
| MDSplus client/server data access protocol based on the Internet TCPIP protocol. Also the name of the MDSplus server daemon which receives connections from remote clients.
| Model Data System
| Call to close MDSplus tree or trees
| Call to connect user process to MDSplus server
| Call to disconnect user process from MDSplus server
| Call to open MDSplus tree
| Call to put data into MDSplus trees
| Call to evaluate MDSplus expressions - the basic call to retrieve data
| A type of node which can contain data. (A confusing feature of MDSplus is that MEMBERS may have CHILDREN or other MEMBERS as subnodes.)
| Data about data. In MDSplus this includes the size, shape, and type of arrays, when the data was stored, by who, the structural relations of the data etc. This data is accessed through TDI functions.
| A special type of TREE used as a template for SHOT trees. The model is always designated by shot = -1
| Numerical node ID. A long word which uniquely identifies each node in a tree.
| The basic constituent of MDSplus TREES. Nodes come in two basic types; CHILDREN, which embody the structure of the tree and MEMBERS which contain data.
| NODE CHARACTERISTICS
| Metadata for each node including the size and type of data, when it was stored, by who, its structural relation to other nodes, etc.
| The next higher level NODE in the TREE hierarchy.
| RELATIVE PATH
| A text string which specifies a node reference relative to the current DEFAULT
| REMOTE ACCESS
| Access to tree files on a remote machine through the MDSplus client/server interface
| The process of collection actions from an MDSplus TREE and organizing them into a DISPATCH TABLE for subsequent execution by SERVERS
| An X-windows/motif based tool for quick plotting of X-Y data from MDSplus TREES
| Computer which interprets MDSplus instructions and interacts directly with data structures
| An instance of an MDSplus tree. The shot number is incorporated into the tree file name
| A widely used composite data type consisting of multi-dimensional data and its independent axes.
| STATUS CODES
| Most MDSplus calls return status codes where the lowest bit indicates success or failure. The codes can be interpreted by the mdsgetmsg function
| MDSplus TREEs which are part of the hierarchy of another tree. Subtrees are stored as three separate files just like standalone trees.
| TAG NAMES
| An alias or short pathname for an MDSplus node. Tag names (or tags) can be up to 23 characters and must be unique within each tree.
| Tree command language. A set of commands for viewing or changing the structure of MDSplus trees.
| Tree Data Interface - the basic language for expressions in MDSplus
| TDI VARIABLES
| Data structures which cache the results of expressions in memory. These variables always start with the underscore "_" character.
| THICK CLIENT
| MDSplus client/server data access model where all expression evaluation, data compression and decompression is performed by the client. Tree access is performed by the mdsip server. This mode is used when tree paths are defined as host[:port]::. This mode does not support distributed subtrees.
| THIN CLIENT
| MDSplus client/server data access model where all expression evaluation, data compression and decompression is performed by an mdsip server. The client code is a very thin layer which does nothing but send and receive messages to and from the server. This mode is entered when the client application issues an mdsconnect call.
| An X-windows/motif based tool for exploring and editing MDSplus TREES
| The basic MDSplus data structure consisting of a hierarchical arrangement of NODES which contain data, metadata and structural information. Trees are stored as three files, each containing one of these types of information. Trees are specified by a tree name and shot number
| Each node is assigned a usage when it is created. This generally defines how a node may be used. Common types are STRUCTURE, NUMERIC, SIGNAL, DEVICE, SUBTREE, and TEXT