Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
HCAL Operations | ||||||||
Added: | ||||||||
> > | HCAL Twiki: https://twiki.cern.ch/twiki/bin/viewauth/CMS/HCALWikiHome![]() ![]() ![]() ![]() | |||||||
On Call Cheat SheetSetting up Tunnels | ||||||||
Line: 40 to 46 | ||||||||
Run Control WebsitesP5: http://cmsrc-hcal.cms:16000/rcms/gui/servlet/RunGroupChooserServlet![]() | ||||||||
Added: | ||||||||
> > | CMS TOP: http://cmsrc-top.cms:10000/rcms/gui/servlet/RunGroupChooserServlet![]() | |||||||
904: http://cms904rc-hcal.cms904:16000/rcms/gui/servlet/RunGroupChooserServlet![]() | ||||||||
Added: | ||||||||
> > | H2: http://cmshcalTB02.cms904:16000/rcms/gui/servlet/RunGroupChooserServlet![]() | |||||||
Building 28: http://cmshcal21:16000/rcms/gui/servlet/RunningConfigurationServlet![]() | ||||||||
Added: | ||||||||
> > | Configuration Chooser sets up the run. Once to the configuration screen do: Set enable parameters initialized configure start Stop the run before killing the run | |||||||
uHTRThe 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 | ||||||||
Line: 53 to 72 | ||||||||
$ uHTRtool.exe -c crate:slot (uHTRtool.exe -c 52:10) Not sure yet what the shell script does (uHTRtool.sh) | ||||||||
Added: | ||||||||
> > | AMC13Connecting to an AMC13: There is a shell script at p5 and 904 that will use the connection file and then the -i option: AMC13Tool2.exe -c ~hcalsw/uTCA.connections.pro.xml -i hcal.crate$1.amc13 ${@:2} This is the p5 script. The 904 is almost identical but the location of the connection file is hcalsw/HcalCfg/uTCA/connections.xml. Just use this to connect: $ ~hcalsw/bin/AMC13Tool2.sh crate# 6/24/16 To add the AMC13Tool2.sh script to hcalsw used: $ sudo -u hcalsw then_a_command Example to edit the shell script: $ sudo -u hcalsw emacs AMC13Tool2.sh | |||||||
Log FilesGo to 904 or p5 network | ||||||||
Line: 70 to 105 | ||||||||
Once you have the log file, you can use Handsaw and less to look through them: $ Handsaw.pl logfile.xml | less -R | ||||||||
Added: | ||||||||
> > | Elog + ShiftliftMain Page: https://cmsonline.cern.ch/webcenter/portal/cmsonline/pages_common?wc.contentSource=![]() ![]() RandomKilling Stale Xdaq Processes When a run is destroyed there can be processes that were not destroyed. These will interfere with the next run and cause errors on initialize. Processes NOT to kill: root 35246 18.7 7.3 6499672 2399100 ? Ssl Apr20 11439:33 /opt/xdaq/bin/xdaq.exe -h srv-s2f17-19-01.cms -p 9950 -u file.append:/var/log/hcal.xaad.log -e /opt/xdaq/share/hcal/profile/xaad.profile -z hcal root 35247 8.2 0.2 4319652 91404 ? Ssl Apr20 5045:51 /opt/xdaq/bin/xdaq.exe -h srv-s2f17-19-01.cms -p 9999 -u file.append:/var/log/hcal.jobcontrol.log -e /opt/xdaq/share/hcal/profile/jobcontrol.profile -z hcal Example of stale xdaq process to kill: hcalpro 41955 9.1 0.2 4261576 93072 ? Sl 22:37 1:01 /opt/xdaq/bin/xdaq.exe -h hcalutca01.cms -p 15002 -s 294342 -u xml://cmsrc-hcal.cms:16010 -l INFO Stale XDAQ example: hcalpro 13038 4.1 0.3 2588468 122480 ? Sl Sep15 71:14 /opt/xdaq/bin/xdaq.exe -h hcalutca01.cms -p 16789 -u xml://cmsrc-hcal.cms:16010 -l INFO Do not kill things that are run under root like job control, controlhub, xaad, etc. Be careful with pkill and such that use the name xdaq since it will pick up those other ones as well. ~hcalsw/bin/dump_all.sh See if relevant card ispingable. If uHTR of AMC13 is not pingable: -Restart sysmgr: Using script on hcalutca01 machines: ~hcalsw/bin/restart_sysmgr.sh Basically ~hcalsw/bin/ contains all the magical scripts to do most things. Crate Locations and FEDS: http://cmsdoc.cern.ch/cms/HCAL/document/CountingHouse/Crates/Crate_interfaces_transition.htm![]() | |||||||
-- DanielArcaro - 21 Jun 2017 \ No newline at end of file |