This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
itk:calibration_with_hsio [2017/02/06 19:20] dfrizzell |
itk:calibration_with_hsio [2017/02/06 21:00] (current) dfrizzell This is essentially the initial commit. Everything up to this point has been preperation. |
||
---|---|---|---|
Line 4: | Line 4: | ||
https:// | https:// | ||
+ | |||
+ | The bold font indicates action items and regular text gives supplemental information. | ||
====== Setting up Calibration GUI ====== | ====== Setting up Calibration GUI ====== | ||
Line 19: | Line 21: | ||
$>cd ~/daq/rce #move to rce directory | $>cd ~/daq/rce #move to rce directory | ||
- | $>source ./ | + | $>source ./ |
$> | $> | ||
| | ||
Line 27: | Line 29: | ||
===== Single Scan to Verify Everything is Working (Optional) ===== | ===== Single Scan to Verify Everything is Working (Optional) ===== | ||
- | **On the GUI select Save As and select a location for the log file to be saved. I simply make a directory ($>mkdir ~/ | + | **On the GUI select Save As and select a location for the log file to be saved. I simply make a directory ($>mkdir ~/ |
+ | |||
+ | {{: | ||
+ | {{ : | ||
The default configuration file, (94-22-04_25__cern__6999.cfg) is not setup for the chip geometry currently at ANL-ASC (02-06-2016). To fix this open the file and edit the ' | The default configuration file, (94-22-04_25__cern__6999.cfg) is not setup for the chip geometry currently at ANL-ASC (02-06-2016). To fix this open the file and edit the ' | ||
To communicate with the rce you may need to add a line into the /etc/hosts file. Add the line: " | To communicate with the rce you may need to add a line into the /etc/hosts file. Add the line: " | ||
+ | |||
+ | |||
+ | **Once the test run is complete you will be able to go into the ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If for example, I ran a FDAC_TUNE there would be a folder in the calibData directory ' | ||
+ | |||
+ | It useful to note that the .cfg file isn't actually what gets changed during calibration. It is merely a pointer to a series of .dat files under the fei4bexample directory substructure. | ||
+ | |||
+ | ===== Calibrations Using Primlist ===== | ||
+ | In order to fully calibrate the pixel frontend chips one simply has to run a series of calibration scans each incrementally altering configuration files until the chip becomes optimally tuned as the user desires. The Primlist feature of the calibGUI does this automatically by way of loading in a file with the desired calibration scans and their parameters. | ||
+ | |||
+ | **On the GUI select Save As and select a location for the log file to be saved. I simply make a directory ($>mkdir ~/ | ||
+ | |||
+ | DIGITAL_TEST, | ||
+ | DIGITAL_TEST, | ||
+ | ANALOG_TEST, | ||
+ | GDAC_COARSE_FAST_TUNE, | ||
+ | GDAC_FAST_TUNE, | ||
+ | IF_TUNE, | ||
+ | GDAC_FAST_TUNE, | ||
+ | TDAC_FAST_TUNE, | ||
+ | IF_TUNE, | ||
+ | FDAC_TUNE, | ||
+ | TDAC_FAST_TUNE, | ||
+ | FDAC_TUNE, | ||
+ | THRESHOLD_SCAN, | ||
+ | TOT_TEST, | ||
+ | NOISESCAN, | ||
+ | NOISESCAN, | ||
+ | NOISESCAN, | ||
+ | NOISESCAN, | ||
+ | | ||
+ | **On the ' | ||
+ | |||
+ | |||
+ | To run further tests you may simply ' | ||
+ | |||
+ | Sometimes unexpected crashes of the calibserver on the rce can occur. Simply restart this server and try again. | ||
+ | |||
+ | The logic behind the primlist file is fairly obvious and can be manipulated and altered as the user desires different parameters, orderings, or scans. | ||
+ | |||
+ | **It is most instructive to run a diagnostic scan such as the THRESHOLD_SCAN on the default .cfg file, then again on the last .cfg file after the primlist has run (for example in the ~/ | ||
+ | |||
+ | {{: | ||
+ | {{ : | ||
+ | |||
+ | |||
+ | |||
+ | ===== Questions, Comments, or Corrections ===== | ||
+ | [email protected] | ||
+ | |||
- | //Under construction// |