| Table of Contents | |
|---|---|
|
...
3.1.
...
1 Changes
| CHEAT SHEET | ||
| DB creation | ITM | IMAS |
|---|---|---|
| DB creation | $ITMSCRIPTDIR/create_user_itm_dir | |
...
<machine> <version> | imasdb <machine> |
| DB switching |
...
source $ITMSCRIPTDIR/ |
...
ITMv2 |
...
At this point, you can check your public directory and browse through the database structure.
cd $HOME/public/itmdb/itm_trees
Explanation of the tree structure:
...
<machine> [<local_kepler_dir>] | imasdb <machine> | |
| pulse file listing | itmdbs | imasdbs |
| pulse files | euitm_<shot><run>.datafile,euitm_<shot><run>.tree,euitm_<shot><run>.characteristics | ids_<shot><run> |
...
.datafile,ids_ |
...
<shot><run>.tree, ids_ |
...
<shot><run>.characteristics |
...
| DB dir | $HOME/ |
2.2. Accessing MDSPlus database data
From the user's point of view, there are few characteristics that define single data tree:
| Parameter | Environment variable | Description |
|---|---|---|
| User name | $USER | Defines the name of the user who owns the data |
| Tokamak name | $TOKAMAKNAME | Defines the name of the machine that was used during simulation (test - contains testing data) |
| UAL database version | $DATAVERSION | Specifies UAL data version |
| Run number | not defined | Run number is represented by last four digits in database file ids_SSSSRRRR.* |
| Shot number | not defined | Shot number is represented by first digits in database file ids_SSSSRRRR.*; there is no limit for number of digits used |
| Info |
|---|
ITMv1 script source $ITMSCRIPTDIR/ITMv1 kepler test 4.10b > /dev/null
|
2.2.1 Listing pulse files
| Info | ||
|---|---|---|
| ||
Usage: itmdbs [OPTIONS] [COMMAND] This program lists existing ITM databases. Possible commands are: list <shot number>- list existing databases slices <shot number> <run number> - list existing databases, including number of timeslices and time range for time-dependent IDSes times <shot number> <run number> - list existing databases, including number of timeslices their time points for time-dependent IDSes tokamak - list existing tokamaks (with data versions) dataversion - list existing dataversions (with tokamaks) If the optional arguments shot number and run number are given, only databases with these numbers will be shown. If no command is given, the list command is performed. To see databases stored in the public itm database, use 'public' as the user name. Options: -h, --help show this help message and exit -u USER, --user=USER Show databases of specified user -t TOKAMAK, --tokamak=TOKAMAK Show only databases for specified tokamaks -v VERSION, --version=VERSION Show only databases for specified data version --backend=BACKEND Show databases written with given backend(s). Comma- separated list of backends (Currently supported: mdsplus, hdf5). By default all backends are shown. -c, --compact Compact/reduced output |
| Code Block |
|---|
shell> itmdbs -t test slices 14 4
Tokamak: test
Data version: 4.10b
UAL Backend: mdsplus
Shot 14
Run: 4
equilibrium: 100 slices ( 0.0 - 99.0) |
2.2.2 Copying database files directly
In case you know user name, machine name, shot number and run number, you can import users' database files copying them directly from the users' public directories. Database files are located inside:
...
public/itmdb/itm_trees/ |
...
<machine>/ |
...
<version>/mdsplus/0/ |
...
Take a look at the example below. We will copy data from user michalo, machine test, shot: 12 and run: 2
...
~g2bpalak/public/itmdb/itm_trees/test/4.10b/mdsplus/0/ |
...
$HOME/public/itmdb/itm_trees/ |
...
<machine>/ |
...
<version>/mdsplus/0/ |
...
~g2bpalak/public/ |
...
imasdb/ |
...
test/4.10b/mdsplus/0/ |
...
| Content | cpodump | idsdump |
| Copy | cpocopy | idscopy |