ParaStore

Revised on Sep. 3rd, 2004
Modified on Sep. 22nd, 2004

計測情報開発タスク幹事

ParaStore is the public service to automatically save and register (using dbStore) the parameter files (comma separated verse [CSV] files), which are stored within a designated public directory, at a certain timing synchronized with an experiment sequence and messages.

Create parameter files to be stored in the ParaStore in the following procedure.

1. File name
   Make sure to remember adding "_p" at the end of the file. ("name of diagnostics_p")
   [e.g.]　Bolometer_p, GPCRADH_p, and so on
   
   These file names have to be the same with ones that were used when applying for the ParaStore data registration.
   *dbStore will be used to store the file.
   　
2. Location of the file
   Locate the file within the WINDOWS public folder \\ParaStore\parameters\ via the network.
   (In case that the public host cannot be recognized, use \\ParaStore.LHD.nifs.ac.jp\parameters\ instead.)
   
   To newly add or edit files, user authorization is required. To newly register the data, at least one person needs to be registered as an administrator of the data, who will be authorized to write on the file. If you wish to change the administrator afterwards, please apply for adding a new administrator by the ParaStore data registration form.
   *A writing authorization can only be given to the LHD domain user account. Therefore, to obtain the authorization requires one to have the LHD domain user account. If you don't have one yet, please first apply for the LHD domain user account registration. Then, Apply for the ParaStore data registration.
   　
3. File Layout and Layout tag
   Parameter files consist of comment lines that start with '#' and data lines that start with characters other than #. Among all the comment lines, only those lines that the Layout tag [***] is written following the beginning '#' and the comment line right after that have specific meanings as described below.
   Data lines are non-commenting lines after the layout tag [DATA], and they are written in the comma segmented verse (CSV) format.
    

   Valid layout tag are 4 of those shown below. All of the layout tags are NOT case sensitive. [NAME] = [Name]

   # [MailAddress]	<- e-mail address definition
   # foo@nifs.ac.jp	<- after '#' is the user's e-mail address. Only one mailing address can be specified.
   #	Only the user who is registered here is authorized to apply for the Data deletion .
   #
   # [NAME]	<- definition of the name of parameter variables
   # CH, CATEGORY, NAME, TAG, ...	<-names after '#' are the valid parameter variables; written in the CSV format.
   #
   # [TYPE]	<- definition of the parameter variable style (option: default is 6:DOUBLE)
   # 4, 1, 1, 4, ...	<-styles after '#' is the valid data style; written in the CSV format.
   #
   # [DATA]	<- start of the parameter data
   1, 100.000, ...	<- data to be stored; written in the CSV format.
   2, 101.000, ...
   ..., data lines will continue as necessary.

   　

4. Imperative parameter variable (column)
   To compile a series of diagnostic device related information like the compatibility of each channel to the devices (which channel is compatible to which device) as well as the attribution of each diagnostic device (amplifier gain, calibration coefficient, and such) in to the data base and keep their records, make sure to start the file with the following  4 imperative columns.
   　
   1. CH
      • Digitizer collection channel number like CAMAC (integer TYPE=4) 
      • Serial numbers starting from 1, only half-size numerical character
      • Even in the case of non-signal channels such as cables are not connected, as long as the data collection mode is ON and the non-signal data exists, make sure to create an appropriate line that at least specifies the 'CH' number.
      
      
   2. CATEGORY
      • Name of diagnostic category (null string TYPE=1)
      • Make sure that the name of diagnostic category is obvious to every one. (e.g.: ECE, Magnetic_Probe)
      • Usable only half-size alphabetical/numerical characters and +/-/*///_/(/)/&/</>/#/[/]/%/?. Blank space cannot be used.
      
      
   3. NAME
      • Identification name (null string TYPE=1) of diagnostic devices (small groups like the identical sensor groups)
      • Usable to identify within diagnostic groups. (e.g.: RADH_show) Serial numbers starting from 1.
      • Usable only half-size alphabetical/numerical characters and +/-/*///_/(/)/&/</>/#/[/]/%/?. Blank space cannot be used.
      
      
   4. TAG
      • Channel number (integer TYPE=4) of diagnostic devices (small groups like the identical sensor groups)
      • Usable only the half-size numerical characters

   　

5. Name of optional parameter variable (column)
   Columns after the 5th variable are available for writing and utilizing basically with no restrictions. However, it has been regulated so that users must share the already registered variable names (name of the column); therefore, please choose among the existing variable names.
    
   Following are the existing registered variable names.
    
   

   Variable_Name	Type	Type_Name	Comment
   CH	4	INT	unique and sequential channel no. of digitizers. Begin with 1.
   CATEGORY	1	STRING	category name of diagnostics
   NAME	1	STRING	measurement or sensor name(s) in its diagnostic category
   TAG	4	INT	channel no. within a measurement
   OBJECT	1	STRING	object of measurement
   PORT	1	STRING	LHD port no. where equipment are installed
   R(m)	5	FLOAT	sensor position in major radius direction
   Z(m)	5	FLOAT	sensor position in vertical direction
   PHI(deg)	5	FLOAT	sensor position in toroidal angular direction
   FREQ	5	FLOAT	sensing frequency
   WAVELENGTH	5	FLOAT	sensing wavelength
   ENERGY	5	FLOAT	sensing energy
   FILTER	5	FLOAT	filtering factor
   GAIN	5	FLOAT	amplifier's gain
   CALIB	5	FLOAT	calibration factor of the sensor
   UNIT	1	STRING	unit of physical value to be measured
   REMARKS	1	STRING	any comment(s) of this channel
   FIL	5	FLOAT	filament current
   CALDATA	4	INT	calibration data number
   SI	4	INT	sensitivity current
   GI	4	INT	gain current
   VOL	4	INT	voltage
   GV	1	STRING	Gatevalve open or close

   When variable names other than ones shown above, please apply as necessary.
   　

6. Sample of file contents

   A sample file for RADL diagnostics "RADL_p" is provided by Mr. Inagaki. (Click and jump to the link.)

7. Attentions

   • Values that explain a definition should be written in the line right after the definition. 
   • [Data] must be defined at the last. (Definitions of [MailAddress], [Name] and [TYPE] can be placed basically at a random order. )
   • When a parameter name does no exist, the parameter file in question cannot be stored.
   • When a parameter data type is not specified, the file will be stored in the default data type (6:DOUBLE).
     Following can be specified in [TYPE], and (☆) signifies a recommended data type.
     　1:  STRING  ...  Character set(☆)
     　2:  BYTE     ...  1-byte integer
     　3:  SHORT   ...  2-byte integer
     　4:  INT        ...  4-byte integer(☆)
     　5:  FLOAT   ...  4-byte floating decimal point (single precision actual value) (☆)
     　6:  DOUBLE ...  8-byte floating decimal point 
   • When the parameter data type are NOT specified within 1 to 6, storing of the entire parameter file in question will fail.
   • When the numbers of parameter data type definitions are less than the parameter names, the default file type (6:DOUBLE) will be applied for the excessive parameter names.
   • When the stored data section [Data] does not exist, the parameter file in question will NOT be stored.