...
| Location | Description |
|---|---|
| $HOME/public/itmdbimasdb/<machine_name>/<data_version>/<MDSPlus_tree_number>/ids_<shot><run>.* example: ~/public/imasdb/test/3/0/ids_120001.* | |
| <machine_name> example: test | defines the equipment used for acquiring the results; "test" - is most commonly used for artificial, test data |
| <data_version> example: 3 | Major Data Dictionary version |
| <MDSPlus_tree_number> example: 0 | Contains all the shot and runs for given data tree |
| Shot number | Shot number is represented by first digits in database file ids_SSSSRRRR.*; there is no limit for number of digits used |
| Run number | Run number is represented by last four digits in database file ids_SSSSRRRR.* |
ids_####.datafile, ids_####.tree, ids_####.characteristics | Contains data for given shot/run |
...
06.1.3.2 Dumping pulse files
To list the content (all data) of an IDS, use idsdump script
| Code Block |
|---|
shell> idsdump Usage: idsdump <USER> <TOKAMAK> <VERSION> <SHOT> <RUN> <IDS> |
...
Getting a subset of an IDS enables reading only a node (and its descendants if the node is a structure), making the GET operation much faster. To retrieve only requested node one should call the script idsdumppath . Path syntax: The path to requested node(s) is separated by slashes (“/path/to/node(s)”). Nodes representing arrays must contain indexes (“/path/to/array(idx)/field”) or “Fortran style” indices (“path/to/array(x:y)/field”) Limitation: In case of nested AoS, it is not allowed to specify set of indices for AoS ancestors. Only given values of AoS ancestors indices are handled: (e.g. “field/with/ancestorAoS(x:y)/field/AoS(n :m)” is not managed) Data query examples: “flux_loop(1)/flux/data(1:5)” “bpol_probe(2:3)/field/data” “loop(:)/current” “time(4:-1)” “profiles_1d(2)/grid/rho_tor_norm(2:4)” “ids_properties” occurrence is a number indicating the occurrence of the target IDS in the Data Entry
| Code Block |
|---|
idsdumppath Usage: idsdumppath <USER> <TOKAMAK> <VERSION> <SHOT> <RUN> <IDS> <DATA_PATH> |
...