Changes between Version 27 and Version 28 of Doc/Tools/cpu_Monitoring_and_DMT


Ignore:
Timestamp:
02/11/22 17:07:40 (2 years ago)
Author:
edupont
Comment:

Divided the data acquisition step into 'first time' and 'actual process'

Legend:

Unmodified
Added
Removed
Modified

  • Doc/Tools/cpu_Monitoring_and_DMT

    v27 v28  
    113113 
    114114### Step 1 : Data Acquisition from IRENE ### 
    115  
    116115The first step for using the app is to log the output from the ccc_tree command at TGCC.  
     116 
     117#### Is it your first time doing this ? #### 
     118 
     119For the acquisition process you will run a bash script. There are a few things you need to prepare beforehand. 
     120 
     121You will need to : 
     122- know the path of the directory you want to inspect. Write it down on a side document. 
     123- create directory called `raw_logs` on one of your WORKDIRs.  
     124Create it using `mkdir` and write the full path down on a side document. (Example : $GENCMIP6_CCCWORKDIR/raw_logs)   
     125- Choose a descriptive name for your output file. 
     126For example if you are inspecting your workdir for project genxxx, you can use : `WORK_genxxx_<login>`. Write it down on a side document. 
     127The `_<date>.txt` will be added automatically. 
     128 
     129You will be able to use this `raw_logs` directory for your future data acquisitions. 
     130 
     131#### Acquiring Data : #### 
     132You are now ready to start the acquisition process. 
    117133 
    118134The script running 'ccc_tree' with the proper inputs is 'script_v2_manual.sh'. It can take a while to execute therefore it should be launched from IRENE computer in a screen session.  
    … …  
    121137 - `bash $GENCMIP6_CCCHOME/../dupontel/tests_DMP/script_v2_manual.sh` 
    122138 
    123 Provide the path of the directory to inspect, the path of the raw_logs directory where you bant to write the data (it must be in the WORK space) and and output file name (without the date). 
     139The script asks you for the information you wrote down on the previous step (path of the directory to inspect, path of the raw_logs directory in the WORK space where you want to write the data and output file name, without the date). 
    124140 
    125141 
    126142 - `Ctrl + a -- d ` to detach the screen session.  
    127143 
    128  The *screen session* is used to be able to logout from TGCC if the process is taking to long. 
    129  
    130 - Check if the thredds_cp command was ran correctly. If your output path was $GENCMIP6_CCCWORKDIR/raw_logs, does your output file has 2 inodes, and does it exists on your thredds/work directory ? 
     144 The '''screen session''' is used to be able to logout from TGCC if the process is taking to long. 
     145 
     146- Check if the thredds_cp command was ran correctly : your output file should use two inodes and exists on your thredds/work directory. 
    131147 
    132148{{{#!div style="font-size: 80%" 
    133 ls -l $GENCMIP6_CCCWORKDIR/raw_logs output  : 
     149ls -l $GENCMIP6_CCCWORKDIR/raw_logs/<filename> output  : 
    134150  {{{#!bash 
    135151  -rw-r--r-- 2 <user> <group>  <size> <date> <filename> 
    … …  
    147163 
    148164 
    149 If not you should re-run the last 'thredds_cp' of the 'script_v2_manual.sh' script. 
     165If this is not the case, you should re-run the last 'thredds_cp' command of the 'script_v2_manual.sh' script. 
    150166`thredds cp <path-to-file>  <path-to-thredds>/${LOGNAME}/raw_logs/` 
    151  
    152  
    153  '''Nota Bene :''' If this is the first time you carry out a data acquisition, you must create a 'raw_logs' directory in your WORKDIR. 
    154 {{{mkdir $CCCWORKDIR/raw_logs}}} 
    155  
    156  This is the path you will use to write the raw logs on your next acquisitions. It can take from seconds to few hours depending on where in the folder tree you are inspecting. 
    157  
    158  
    159167### Step 2 : Parse the raw log to get yaml file. ### 
    160168