HCAL Operations
On Call Cheat Sheet
Setting up Tunnels
Follow the
HCAL Connectivity
twiki to get tunnels working for lxplus,904, and p5 networks. The best choice for windows is to use linux with a virtual box. If you are on lxplus already at cern with a windows computer putty works well too.
Setup Environment
Bash files
Snippets
Getting the Hcal config files point 5: (should be the same for 904)
$ cfgcvs checkout
HcalCfg
Very similar to svn
$ cvs commit -m "Comment here"
$ cvs tag -F pro DTC.cfg
MCH Commands
telnet hcal-mch-20 (the hcal-mch-20 is like in HcalCfg/uTCA/connection.xml with hcal-card-crate-additionaloption)
>> show_fru
(M4 is on)
>> shutdown <fru_number>
(Probably do show_fru again to make sure the state goes to M1 of the particular card)
>> fru_start <fru_number>
>> exit
To shut down all cards:
>>shutdown all
To reboot ( this also restart the MCH so you will be disconnected. Wait ten seconds or so and then telnet back in to see status)
>> reboot
Run Control Websites
P5:
http://cmsrc-hcal.cms:16000/rcms/gui/servlet/RunGroupChooserServlet
904:
http://cms904rc-hcal.cms904:16000/rcms/gui/servlet/RunGroupChooserServlet
Building 28:
http://cmshcal21:16000/rcms/gui/servlet/RunningConfigurationServlet
uHTR
The uHTR tool is pretty straightforward. The only thing to watch out for is that the back and front fpga firmware should not be mixed up (and they can be…). Also, the versions should match between front and back. This should be both the detector part (HF, HBHE) and the number after it which is the speed (1600 = 1.6Gbps, 4800 = 4.8Gbps). Examples match below:
uhtr_front_HBHE1600_1_00_07.mcs.xz
uhtr_back_HBHE1600_1_00_00.mcs.xz
Correct Use for P5/904:
$ uHTRtool.exe -c crate:slot (uHTRtool.exe -c 52:10)
Not sure yet what the shell script does (uHTRtool.sh)
Log Files
Go to 904 or p5 network
Ssh cms904rc-hcal (for 904)
Ssh cmsrc-hcal (for p5)
Run the handsaw script (this is located in ~hcalsw/bin/):
$ Handsaw.pl /var/log/rcms/hcalpro/Logs_hcalpro.xml]
$ tail -f /var/log/rcms/hcalpro/Logs_hcalpro.xml | Handsaw.pl
Tail streams the errors out. Probably the best to look at.
Parsing through old Logs:
Copy the log file you want to look at. They are usually in a compressed (.gz). To open them:
$ gunzip file.gz
Once you have the log file, you can use Handsaw and less to look through them:
$ Handsaw.pl logfile.xml | less -R
--
DanielArcaro - 21 Jun 2017