Ultra-short reference for the MTCC-shifter arriving in USC55

Transcription

1 Ultra-short reference for the MTCC-shifter arriving in USC55 (12 th July 2007) MTCC machines vs USC55 machines cmsdaquser0 cmsusr0 login as dtdqm passwd dtfed0 cms-dt-dcs-yb0.cern.ch login as dcs passwd dtfed1 frlpcs1d12-20 login as xdaq passwd or (new DAQ) frlpcs1d12-19 login as xdaq passwd In the following, frlpcs1d12-20 (old DAQ) is referred to. If you run with the new DAQ, use the -19 machine. Most of the operations are the same; basically only the DAQ interfaces are a bit different. 0. User PCs Four PCs are reserved to the DT cloud for commissioning operations: usc55ucr11 DT commissioning DAQ, Trigger, DCS login as dtdqm passwd pccmscr18 DT commissioning HV/LV login as mudcs passwd usc55ucr09 DQM login as dtdqm passwd usc55ucr10 general login as passwd 1. ELOG Remember to log good runs in the electronic logbook. Use a browser with access to the outer world. This can be your notebook on DHCP or you can open a firefox from a shell on cmsusr0. Go to Click on Sector Tests, and choose the sector. View the run list and check the last comments to know what was going on. Remember to ask always the status of the operations to experts and to the previous shift crew! To post new log entries you need to log in as sx5 with password dttests. Please, shifters should also post comments on the elog to record the operations done and status comments. 2. DAQ / Run control Start the xdaq application for the TTCci (please before launching it, check if it is already running!) ssh ttc-dt./start-xdaq.py Then use a browser to access the run control GUI

2 Launch firefox from the shortcut on the task bar. The old DAQ links open automatically. If you need to use the new DAQ, look in the bookmarks menu for the links. The data files must be saved into /cmsdisk1/data1/dt_data/yb0/ The filename must be of the form DT_W0S##_chambers_config_Tech, where: o ## is the sector number, with two digits, i.e. 03, 10 etc. o chambers means the chambers in the trigger: usually you write ALL if all chambers are in. Otherwise, specify the chambers that are in; for instance, if MB3 is excluded from the trigger, you put MB1MB2MB4 o config is the minicrate configuration; for cosmics, we use HanyTheta, and you write HanyT in the filename. It can be (depending on what is going on) HHHL or default. o Tech means we are triggering with the DTTF technical trigger. If you go to standard trigger, remember to remove this appendix. If you have DAQ giving errors because it is not able to write data to disk, you can remount it: o ssh xdaq@frlpcs1d12-20 (or use any shell on this machine) o sudo mount -a 3. DCS Minicrate DCS ssh Y cmsusr0 ssh X dcs@cms-dt-dcs-yb0.cern.ch usual status/control commands available, i.e. o dt_config <partition> <config-set> (minicrate configuration) o dt_monitor <partition> (mc temperature monitor) o mc_status <port> <ccbid> (single mc status display) o mc_config <port> <configfile> <dataset> (old style configuration) TDC must be configured before running. The command o mc_config <port> <filename> 1 must be executed for each chamber. Look for filenames into the directory for the configuration you need (note that different chambers have different configuration files). The following directories are available: o /home/dcs/configs/tdc_cosmics_8 (use for cosmics runs) o /home/dcs/configs/tdc_tp_128 (use for test-pulse runs) o /home/dcs/configs/tdc_noise_128 (use for noise runs) o /home/dcs/configs/tdc_noise_8 (use for noise if you have fifo full errors) To change the thresholds, go to o /home/dcs/configs/thr and use (for each chamber you want to set) the command mc_config <port> <filename> 1 choosing the file you need (threshold setting in the filename!) to save a configuration into the minicrate, use o mc_saveconf <port> If the DCS machine is not reachable (the following operations should be done by experts): o Check the Ethernet cables in S1D12 and S1G00 o Reboot the machine and turn off the minicrates o Kill the ccb process o sudo./startccb o Turn on the minicrates and check the DCS is running correctly

3 Sector Collector temperature monitor o ssh xdaq@frlpcs1d12-20 o TSC o nice n19./sc_monitor.exe Edit the file ConfigurationParameter.txt to include/exclude boards from monitoring. 4. Sector Collector Sector Collector control ssh xdaq@frlpcs1d12-20 TSC./sector_collector_manager.exe Choose the sector number, use command [1]to power up and configure. Please note the line Check VME access: if it fails, there are problems with the VME access, usually this is due to the VME driver being screwed. See how to reload it below. Check the status with the command [3]. If you want to refresh the errors memory, answer y to the question. Then wait for a few seconds, and choose [3] again answering n this time. Important status bits are the following ones: ***_Fault 0 (*** = MB1,2,3,4 ad OPTO) ***_novercurrent 1 (*** = MB1,2,3,4 ad OPTO) QPLL_not_locked 0 GOL_x_not_ready 0 (with x = 1.. 6) nlock_err_mby 0 (with y = 1.. 4) Parity_err_MBy 0 (with y = 1.. 4) Internal_PLL1_lock 1 Internal_PLL2_lock 1 If the status differ from this reference one (also after a reset of the flags) contact experts! 5. Track Finder (mask/unmask chambers) ssh Y dtdqm@vmepcs2g18-22 cd Tcl_Tk_x/phtf_mtcc halcaen2 phtf_mtcc.tk & On the window named parwin, select PHTF_LP0 and click OK Click the button Open near to the line Optical Input Card Control Window On the new window, you can use the buttons under the line Mask Chamber to maskunmask each station. Green means the chamber is NOT masked, red means it is masked. Note that the buttons range from 0 to 3, they are mapped to stations 1 to 4. Note that if the system is being restarted from scratch (i.e., after a power cut) there are more expert operations that must be done. Please contact the experts.

4 6. TTCci Configuration files - Remember the Start BGO Sequence after loading the test pulse configuration TTCciYB0Configuration.txt Configuration for cosmic data taking with Barrel Sorter trigger (note: no automatic EC0 is sent) TTCciYB0Configuration_techTrig_TTCclock_EC0.txt Configuration for cosmic data taking with the technical trigger TTCciYB0Confuguration_testpulse_EC0_bgo14.txt Configuration for the test pulse runs (remember to go to Cyclic Gen. and click on the button Send BGO-Start after having loaded the configuration) TTCciConfiguration_RandomTriggers_100Hz_TTCck_EC0.txt Configuration for the noise runs Configuration-TP-SCSynchro.txt Configuration for the test pulse runs for the SC synchronization process (remember to go to Cyclic Gen. and click on the button Send BGO-Start after having loaded the configuration) 7. DQM Do the following in two shells: o ssh Y usc55ucr02 (also are usable) o source setdqm 0 <sector> On one shell do o rundqm <parameters> where the optional parameters are the following ones: o copy to force the file copying from cmsdisk1 o sync to remove type-3 noise events from the timeboxes o olddaq to force unpacking in old DAQ style (with no option, old/new DAQ are automatically recognized) when prompted, insert the password for xdaq@frlpcs1d12-20 o answer no to calibration and noise questions (unless calibration data are available) On the second shell (better if you wait until the first 1000 events have been processed) o runiguana 8. Event Display Open one shell and run the following commands o ssh Y usc55ucr04 o source setdqm 0 <sector> o runvisual you may need use the copy or the olddaq options insert the run number when prompted, insert the password for xdaq@frlpcs1d12-20

5 answer no to the calibration question 9. Reload the VME driver In case you have errors in configuring the DAQ or when powering on the tsc, it could be a problem of the VME driver. Use the command [1] into the sector_collector_manager.exe to check the VME access. If it fails the test, you need to reload the driver. The procedure is different on the frlpcs1d12-20 and on frlpcs1d12-19 machines with the new DAQ the new Linco VME bridge is used for the Sector Collector crate: frlpcs1d12-19 (new DAQ) logged on frlpcs1d12-19 as xdaq, do the following steps: o sudo /sbin/service caenvme restart o sudo ~/loadlincodrv you can check the status with the commands o cat /proc/linco_0 o cat /proc/a2818 if you decide for a reboot or a shutdown use the commands o sudo /sbin/reboot o sudo /sbin/shutdown h now frlpcs1d12-20 (old DAQ) logged on frlpcs1d12-20 as xdaq, do the following steps: o cd /usr/local/caen/caen-vme/linux/driver/v2718 o sudo /sbin/rmmod a2818 o sudo./a2818_load.2.4 to check the status, type o cat /proc/a2818 (you should read 2 CAEN A2818 board(s) found at the end) check the VME access from the sector_collector_manager again; if it still doesn t work, repeat the unload/reload a second time and try again if it still doesn t work, sometimes the only solution is to reboot the machine with the command o sudo /sbin/reboot 10. Shutdown When you shutdown the system, remember to do (at least) the following steps: Halt the run. Stop the sc_monitor pressing Q and the choose the option [0] to exit the program. Power off the tsc choosing [5] in the sector_collector_manager.exe, then exit the program with option [0]. Stop the minicrate DCS (dt_monitor program) if it was running. Switch off the chambers (right-click and then choose switch off LV). Switch off the easycrate of the sector. Switch off the sector collector crate(s). Please write notes to update this short reference here below

6