@@ -21,7 +21,7 @@ All the DCS-related functionality is optional. The SO provides scripts based on
This repository includes the following independent tools:
-`libDCS/iviscan.py`: safely performs sensor IV and module VI scans
-`libDCS/qaqc.py`: Controls and monitors a power supply. Optionally uploads PS data to influxDB until killed
-`libDCS/psOperator.py`: Controls and monitors a power supply. Optionally uploads PS data to influxDB until killed
-`libDCS/parameterOptimizer.py`: Performs trim scans, tap scans, etc on a selected chip to find its best configuration.
More on this tools [here](#useful-independent-tools).
...
...
@@ -79,6 +79,7 @@ Start from `./ScanOperator.sh` to see a complete list of options.
The cfg files are created in the Scan Operator's folder, so everything you have under Yarr's one remains untouched
-`-s:` Doesn't look for changes in the config. Can be useful when runing the SO without having modified `so_modules.json`. Saves some time.
-`-j:` Just updates the module configs according to `so_modules.json`, and exits before interacting with the module or the PS at all.
-`-W:` This one is equivalent to the `-W` option used when calling Yarr's ScanConsole
-`-Q:` This one is equivalent to the `-Q` option you use when calling Yarr's ScanConsole
...
...
@@ -126,7 +127,7 @@ If you want to use the SO to monitor DCS (`-d`) and synchronize the DCS data and
```
#### *Monitoring DCS with an external tool*
Say you are using your own tool (e.g. `libDCS/qaqc.py`) to constantly upload DCS data to InfluxDB, while using the SO to run all the scans.
Say you are using your own tool (e.g. `libDCS/psOperator.py`) to constantly upload DCS data to InfluxDB, while using the SO to run all the scans.
Then you can omit -d
```bash
...
...
@@ -258,7 +259,7 @@ You can specify the number of measurements per step and the sleeping time betwee
## PS Controller / monitor tool
-`python3 libDCS/qaqc.py -h` for a complete set of options.
-`python3 libDCS/psOperator.py -h` for a complete set of options.
This script can be used to remotely control a power supply. (set/get-voltage, power on/off, etc). It can also be left running in the background (e.g. in a `screen`) constantly monitoring a single channel and uploading the data to influxDB.
The numbers in the matrix indicate the number of failing pixels (0's in the enMask) from a digital.
The default config file for this script is `so_optimizer.json`. There, the target chip number starts from 1. 1 is the first chip, 2 is the 2nd, ... as you have them ordered in your SO config. To check the order you can also look at the connectivity file displayed on the terminal when calling `./ScanOperator.sh -m your_module -j`.
The script tries to look for the best region by itself. Once found, you can wait for the whole matrix to get filled, or just kill the script at any stage. After using this script run the SO once, just to reset the configuration to its original state.
