Difference: CscTf (1 vs. 136)

Revision 1362015-03-02 - PierluigiBortignon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Added:
>
>
This is the main CSCTrackFinderExpert page.
 

General Information

For a thorough overview of the CSCTF, please consult Commissioning of the CSC Track Finder

Revision 1352015-02-27 - PierluigiBortignon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 547 to 547
 
  • Basic instructions are also in the file $CSCTF/ts/scripts/writePtLuts/README
Added:
>
>

How to check the CSCTF configurations stored in a database

In case you want to check the CSCTF configurations stored in the database and used for a certain CMSSW release and a certain global tag, start checking out the CMSSW release you are interested in - as example I take 7_3_1_patch2. Then check out the relevant packages

cmsrel CMSSW_7_3_1_patch2
cd CMSSW_7_3_1_patch2/src
git-cms-addpkg L1Trigger/Configuration
git-cms-addpkg L1TriggerConfig/CSCTFConfigProducers
scramv1 b -j 8

The relevant file are

L1Trigger/Configuration/test/L1GlobalTagTest_cfg.py

where you set the global tag and the run number or the file you want to run on - and you better set to True only the print of CSCTF if you don't want a huge print out.

In case you want to dump also the pt LUT you have to modify

L1TriggerConfig/CSCTFConfigProducers/src/L1MuCSCTFParamatersTester.cc

Where you want to include

#include "CondFormats/L1TObjects/interface/L1MuCSCPtLut.h"
#include "CondFormats/DataRecord/interface/L1MuCSCPtLutRcd.h"

and add the following lines

edm::ESHandle< L1MuCSCPtLut > ptLUT;
evSetup.get< L1MuCSCPtLutRcd >().get(ptLUT);
L1MuCSCPtLut myConfigPt_ = *ptLUT.product();

for(unsigned int i =0; i < (1<<21); i++){ std::cout << myConfigPt_.lut()[i] << std::endl; }

and then recompile!

Running the same cfg (L1Trigger/Configuration/test/L1GlobalTagTest_cfg.py) will print out now the 2M lines of the LUT - so you better redirect the output to a file.

 

How To Check the CAEN VME Bridge Firmware Version

Revision 1342014-11-17 - RenJieWang

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 873 to 873
 make
sudo /sbin/service xdaqd restart
Added:
>
>

How to run onlineDQM plots locally

set up:
setenv SCRAM_ARCH slc6_amd64_gcc481
scramv1 project CMSSW CMSSW_7_2_1
cd CMSSW_7_2_1/src
cmsenv
git clone git@github.com:rjwang/CSCTFDQM.git DQM/L1TMonitor

run DQM plot for a single run:

edit python/inputsource_file_cfi.py
change sampleIdentifier and related config:
elif sampleIdentifier == '226144' :
    runNumber = 'XXXXXX'
    dataset = 'None'
    dataType = 'RAW'
    useDAS = False
    readFiles.extend( [
            'file:/PATH/local_run_XXXXXX_csctf.root'
            ]);
go to test/Makefile, change the variable to the correct run number
make;         // will create a root file
make plot;  // will run a macro: plotter.cc to give out all plots 

 

General CSCTF Troubleshooting

Out of Sync in Link Masking Panel

Revision 1332014-06-30 - MicheleDegruttola

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 355 to 355
 
  • eta2_config.txt -> if you modify any register for eta cuts configuration

Changed:
<
<
The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309
>
>
The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309 (please note that 0 in front are not registered... so 010714 will be 10714)
  This script simply calls other scripts to perform the key writing on the database.

Revision 1322014-02-27 - MicheleDegruttola

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 838 to 838
  For simpler wrapper-oriented tests use TestSPconsole. Build the same as above, but use ./TestSPconsole -s in bin.
Added:
>
>

How to check crate trigger links

to check the correct links (in terms of ordering) from FPGA to SP you can run the binary $CSCTF/SPFunctions/bin/readCrate_triggerLinkIDs
 

How to update TS at 904

(1) Edit the version number of TS in the repo:

Revision 1312014-01-23 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 330 to 330
 

How to Create a Configuration Key

Changed:
<
<
A configuration key is a set of values assigned to the various registers in the SP. You should create a new configuration key for each version of the SP firmware released and any time you decide that a new register value is more beneficial than a previous one (e.g. timing improvements, tuning parameters based on physics studies, etc).
>
>
  • A configuration key is a set of values assigned to the various registers in the SP. You should create a new configuration key for each version of the SP firmware released and/or for LUTs changes and/or any time it is decided that a new register value is more beneficial than a previous one (e.g. timing improvements, tuning parameters based on physics studies, etc).
  • Prerequisites: have the community aware of the upcoming change. Generally any change in the hardware has to be agreed in the csctf-working meeting and then propagated to the CSC and L1 Trigger community
 
Changed:
<
<
The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine
>
>
  • Location of the scripts: The scripts to create a configuration key are located in $CSCTF/ts/scripts/newMezzanine
ssh -X cmsusr # cms904usr in 904
xsudo -H -u csctfts bash -login
cd $CSCTF/ts/scripts/newMezzanine
  The files to change before writing the new key according to the change you want perform are in the same folder:

Line: 356 to 362
 When you created new Key you have to:

  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...
Deleted:
<
<
 
  • upload new information at CSC and Trigger elog
  • call the L1Doc (16-1958). If the phone # changes, the phone is available at Main Trigger Page -> Contacts
Changed:
<
<
>
>
 
  • modify cosmics key at $CSCTF/ts/worker/src/common/MTCCIIConfiguration.cc, compile at $CSCTF and restart csctf-cell:

Changed:
<
<
cd $CSCTF && make clean && make
>
>
ssh -X cmsusr # cms904usr in 904 ssh -X l1ts-csctf xsudo -H -u csctfts bash -login # $CSCTF/ts/worker/src/common/MTCCIIConfiguration.cc cd $CSCTF && make
 sudo /sbin/service triggerd restart csctf-cell
Changed:
<
<
N.B.: whenever a new key is created, it is important to keep the csctf web site updated; to do so you can use the CERN webservices web site.

You can check the key/register values when you are finished here

>
>
N.B.: You can check the key/register values when you are finished with the L1CE. Moreover this tool allows one to compare different configuration keys
 
Added:
>
>
<!--
 To Change Key In RCMS @904:

To change the TF key for cscdev:

Line: 386 to 393
 2) Edit /home/cscpro/config/fm/Local/Local.xml to change 'TrackFinderKey'. 3) Upload the modified Local configuration by issuing: RCMS_HOME=/home/cscdev/RunControl ~cscdev/bin/duckLoader cscdev /home/cscpro/config/fm/Local/Local.duck
Changed:
<
<
>
>
-->
 

How To Create LUTs

Line: 519 to 526
  When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.
Added:
>
>

How To Write the pT LUT into DBS

  • If a new pT LUT is loaded into the hardware and the configuration key updated, one needs to update the table CSCTF_PTLUTS, writing the entire LUT as a CLOB
  • Prerequisites: you must have created the file L1CSCPtLUT.dat
  • The scripts needed are in $CSCTF/ts/scripts/writePtLuts/

ssh -X cmsusr #( or cms904usr)
xsudo -H -u csctfts bash -login
cd $CSCTF/ts/scripts/writePtLuts/
mkdir PtLUTfiles chuncks # if they do not exist already
cp yourpath/L1CSCPtLUT.dat  PtLUTfiles/PtLUT_versionXX.dat # where XX is the version, say 33

createPtLutChuncks.py PtLUTfiles/PtLUT_versionXX.dat # It will break the ptLUT in 5992 pieces to be written in the dbs separately as a CLOB afterwards
createPtLutSQL.py XX #the output will create a file called qwe.sql, which is a sequence of sql command to write the CLOB into the DBS

sqlplus cms_csc_tf/xxxxxx@CMS_OMDS_LB @qwe.sql # where xxxxxx is the passwd :-)

  • Basic instructions are also in the file $CSCTF/ts/scripts/writePtLuts/README
 

How To Check the CAEN VME Bridge Firmware Version

Revision 1302014-01-22 - MicheleDegruttola

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 391 to 391
 

How To Create LUTs


Changed:
<
<
cvs co L1Trigger/CSCTrackFinder
>
>
cvs co L1Trigger/CSCTrackFinder # (or git cms-addpkg L1Trigger/CSCTrackFinder )
 cmsenv scram b

Revision 1292014-01-06 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 393 to 393
 
cvs co L1Trigger/CSCTrackFinder
cmsenv

Changed:
<
<
scramv1 b
>
>
scram b
 
Changed:
<
<
In L1Trigger/CSCTrackFinder/test/BuildFile.xml if you want create PTLUTs uncomment:
>
>
If you want create a new PTLUT file, please uncomment the following lines in L1Trigger/CSCTrackFinder/test/BuildFile.xml:
 
<library file="analysis/CSCMakePTLUT.cc" name="CSCMakePTLUT"!>

Line: 404 to 404
 </library>
Changed:
<
<
If you wnat create SRLUTs uncomment:
>
>
If you want create SRLUT files, please uncomment:
 
<library file="analysis/CSCMakeSRLUT.cc" name="CSCMakeSRLUT">

Line: 412 to 412
 </library>
Changed:
<
<
If you want create both PTLUTs an SRLUTs then uncomment both of them. And compile again:
>
>
If you want create both PTLUTs an SRLUTs then simply uncomment both of them :-).

At this point you need to compile again:

 

Changed:
<
<
scramv1 b
>
>
scram b
 
Changed:
<
<
After that you are ready to run program to create LUTs in L1Trigger/CSCTrackFinder/test:
>
>
After that you are ready to run the script which creates LUTs.
Please make sure you set a globaltag which is valid for the CMSSW release you use, otherwise you will get an error.
Remember to comment out one the paths in case you want to generate only a specific set of LUTs (SR or PT).
 

Changed:
<
<
make makeLUTs.py
>
>
cd L1Trigger/CSCTrackFinder/test cmsRun makeLUTs.py
 
Changed:
<
<
Inside this makeLUTs.py for Point 5 you need ".bin" format. You also could change PtMethod for PTLUTs, which is defined here:
>
>
The job will take a while (especially if you are creating the SRLUTs) and dump a lot of warnings. Generally they are harmless, so if you are using bash you would prefer a command like:

cmsRun makeLUTs.py >& logfile < /dev/null &

The expect size of the files (in total 146 *.bin + 1 *.dat) is:

  • 1048576 bytes for GlobalEtaM*End*Sec*LUT (5 files per EndXSecY(12) = 60) or GlobalPhiM*End*Sec*LUT (7 files per EndXSecY(12) = 84) and LocalPhiLUT.bin (1 file)
  • 4194304 bytes for L1CSCPtLUT.bin (1 file)
  • 12582912 bytes for L1CSCPtLUT.dat (1 file)

The default script will generate PTLUTs in both .bin and .dat (simple text) format. The .bin file is needed to upload the LUTs into the hardware. The text format is needed for writing them into the database.

Important: inside the makeLUTs.py you could change the PtMethod for PTLUTs, which is defined here:

 
PtMethod = cms.untracked.uint32(29)
Changed:
<
<
Description of PtMethod you could find at L1Trigger/CSCTrackFinder/src/CSCTFPtLUT.cc
>
>
The full description of what a specific PtMethod does is readable into L1Trigger/CSCTrackFinder/src/CSCTFPtLUT.cc
 

How To Load LUTs

Revision 1282013-12-03 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 388 to 388
  RCMS_HOME=/home/cscdev/RunControl ~cscdev/bin/duckLoader cscdev /home/cscpro/config/fm/Local/Local.duck
Added:
>
>

How To Create LUTs

cvs co L1Trigger/CSCTrackFinder
cmsenv
scramv1 b

In L1Trigger/CSCTrackFinder/test/BuildFile.xml if you want create PTLUTs uncomment:

<library file="analysis/CSCMakePTLUT.cc" name="CSCMakePTLUT"!>
     <flags EDM_PLUGIN="1"/>
</library>

If you wnat create SRLUTs uncomment:

<library file="analysis/CSCMakeSRLUT.cc" name="CSCMakeSRLUT">
     <flags EDM_PLUGIN="1"/>
</library>

If you want create both PTLUTs an SRLUTs then uncomment both of them. And compile again:

scramv1 b

After that you are ready to run program to create LUTs in L1Trigger/CSCTrackFinder/test:

make makeLUTs.py

Inside this makeLUTs.py for Point 5 you need ".bin" format. You also could change PtMethod for PTLUTs, which is defined here:

PtMethod = cms.untracked.uint32(29)

Description of PtMethod you could find at L1Trigger/CSCTrackFinder/src/CSCTFPtLUT.cc

 

How To Load LUTs

N.B.: In this example I will be using LUTs which are in *.bin version.

Revision 1272012-10-25 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 457 to 457
  When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.
Added:
>
>

How To Check the CAEN VME Bridge Firmware Version

  • The tool was made available by Karoly after the pixel incident reported at http://cmsonline.cern.ch/cms-elog/787686
  • Important note from Karoly: "This program should only be run if no other program accesses the VME bridge. Otherwise data corruption or program crashes could occur." This means the TriggerSupervisor should be stopped before reading the firmware and started after the operation is done.

  • The instructions are:
ssh cmsusr
ssh csc-tf
sudo /sbin/service triggerd stop
cd  /nfshome0/csctfts/TriDAS/trigger/csctf/caen-firmware-version
./firmware
sudo /sbin/service triggerd start
 

How to add a register to monitor to OSW

* Create a file $CSCTF/ts/src/worker/MonitorSource_RegisterName.cc (header file in /interface)

Revision 1262012-09-10 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 32 to 32
 
  • SP1->SP12: 890->901
  • TF DDU:760 (to be double checked)
Added:
>
>

CSR_AF WordCount Values

When monitoring the timing system of the CSCTF SP's we should read the value of the CSR_AF WC register. Logs in the folder /var/log/ on the csc-tf machine contain the most recent values of this register. It's nominal values when enabled are:

<!--/twistyPlugin twikiMakeVisibleInline-->
SP NUM LINK NUM CSR_AF WC VALUE
1 1 13
1 2 13
1 3 14
1 4 14
1 5 14
1 6 13
1 7 17
1 8 17
1 9 17
1 10 17
1 11 17
1 12 17
1 13 15
1 14 15
1 15 15
2 1 10
2 2 10
2 3 10
2 4 11
2 5 11
2 6 10
2 7 13
2 8 13
2 9 13
2 10 13
2 11 13
2 12 13
2 13 12
2 14 11
2 15 11
3 1 11
3 2 11
3 3 11
3 4 11
3 5 11
3 6 11
3 7 15
3 8 14
3 9 14
3 10 14
3 11 14
3 12 15
3 13 9
3 14 9
3 15 8
4 1 15
4 2 15
4 3 14
4 4 15
4 5 14
4 6 15
4 7 16
4 8 16
4 9 16
4 10 16
4 11 16
4 12 16
4 13 12
4 14 12
4 15 12
5 1 19
5 2 19
5 3 19
5 4 20
5 5 20
5 6 20
5 7 20
5 8 20
5 9 20
5 10 20
5 11 20
5 12 20
5 13 17
5 14 17
5 15 17
6 1 16
6 2 16
6 3 16
6 4 16
6 5 16
6 6 16
6 7 18
6 8 18
6 9 19
6 10 19
6 11 19
6 12 19
6 13 18
6 14 18
6 15 18
7 1 12
7 2 12
7 3 12
7 4 12
7 5 12
7 6 12
7 7 15
7 8 16
7 9 16
7 10 15
7 11 15
7 12 15
7 13 15
7 14 15
7 15 15
8 1 8
8 2 8
8 3 8
8 4 8
8 5 8
8 6 8
8 7 12
8 8 12
8 9 12
8 10 12
8 11 12
8 12 12
8 13 11
8 14 11
8 15 11
9 1 9
9 2 9
9 3 9
9 4 9
9 5 9
9 6 9
9 7 13
9 8 12
9 9 13
9 10 13
9 11 12
9 12 12
9 13 8
9 14 9
9 15 8
10 1 13
10 2 13
10 3 12
10 4 13
10 5 13
10 6 13
10 7 15
10 8 15
10 9 15
10 10 15
10 11 15
10 12 15
10 13 10
10 14 11
10 15 11
11 1 17
11 2 17
11 3 17
11 4 17
11 5 17
11 6 17
11 7 19
11 8 19
11 9 19
11 10 19
11 11 19
11 12 19
11 13 15
11 14 15
11 15 15
12 1 15
12 2 15
12 3 15
12 4 15
12 5 15
12 6 15
12 7 19
12 8 19
12 9 19
12 10 19
12 11 19
12 12 19
12 13 17
12 14 17
12 15 17
<!--/twistyPlugin-->

 

Relevant Web Pages for 904

Calendar To Book Your working Time Slot: http://www.google.com/calendar/embed?src=vkkpfe7oatq38kbs6gm3isb7nk%40group.calendar.google.com&ctz=Europe/Zurich

Revision 1252012-09-03 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 827 to 827
 

Other Information

Added:
>
>

How to Change Password for cms_csc_tf_mon user

  • Ask Marc (or whoever has rights) to modify the password stored in /nfshome0/centraltspro/secure/csctf-store.profile
  • Change the password on the database (from cmsusr):
    • sqlplus cms_csc_tf_mon/old_password@CMS_OMDS_LB
    • alter user cms_csc_tf_mon identified by new_password replace old_password;
  • restart the csctf-store from the process controller (http://l1page.cms/main/ProcessController)
 

Useful DBS Queries

HISTORY:

Revision 1242012-09-01 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 1086 to 1084
 
META FILEATTACHMENT attachment="hotspot.xml" attr="" comment="" date="1274268368" name="hotspot.xml" path="hotspot.xml" size="30" stream="hotspot.xml" tmpFilename="/usr/tmp/CGItemp43723" user="kkotov_40phys_2eufl_2eedu" version="1"
META FILEATTACHMENT attachment="cms_proxy.pac" attr="" comment="" date="1279804327" name="cms_proxy.pac" path="cms_proxy.pac" size="1028" stream="cms_proxy.pac" tmpFilename="/usr/tmp/CGItemp59205" user="kropiv" version="1"
META FILEATTACHMENT attachment="p5and904.pac" attr="" comment=".pac file for connecting to both P5 and 904 private networks" date="1330614819" name="p5and904.pac" path="p5and904.pac" size="585" stream="p5and904.pac" tmpFilename="/usr/tmp/CGItemp44386" user="jhugon" version="1"
Added:
>
>
META FILEATTACHMENT attachment="csctfDiagrams.zip" attr="" comment="CSC Trigger Data-Flow Diagram and CSCTF Trigger Data-Flow Diagram" date="1346517077" name="csctfDiagrams.zip" path="csctfDiagrams.zip" size="1135129" user="jhugon" version="1"

Revision 1232012-08-07 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 947 to 947
 
-->

  • Organize CSCTF working meeting, which is running every Tuesday at 18:00 (in most cases by EVO only):
Changed:
<
<
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
>
>
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone. Make sure the meeting is accessible to PUBLIC, and managers include the group cms-web-access (the same group allowed to see CMS Physics Indico pages).
 
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
    • (When it is requested by the group) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting. Some days we have booked room 40-R-B10. Availability of the room you could check here: booked days.
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.

Revision 1222012-06-26 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 1049 to 1049
 /
Added:
>
>

CSCTF To-Do List

* Fix DT Timing Plots: Label says DT-CSC, but code says CSC-DT

 

Relevant Websites

List of web pages:

Revision 1212012-05-07 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 938 to 938
  * 8 May 2012 - 15 May 2012 - Matt Fisher - UF - big grin * 15 May 2012 - 22 May 2012 - Laria Redjiimi - Rice - smile * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 29 May 2012 - 5 June 2012 - Matt Fisher - UF - big grin
>
>
* 29 May 2012 - 5 June 2012 - Anna Kropivnitskaya - UF - Radioactive
  * 5 June 2012 - 12 June 2012 - G.P. Di Giovanni - UF - Radioactive * 12 June 2012 - 19 June 2012 - Justin Hugon - UF - cool! * 12 June 2012 - 2 July 2012 - CERN car - UF - yes

Revision 1202012-04-25 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 934 to 934
  * 17 April 2012 - 24 April 2012 - Matt Fisher - UF - big grin * 24 April 2012 - 1 May 2012 - Laria Redjiimi - Rice - smile * 1 May 2012 - 8 May 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 15 May 2012 - 25 May 2012 - CERN car - UF - yes
>
>
* 14 May 2012 - 25 May 2012 - CERN car - UF - yes
  * 8 May 2012 - 15 May 2012 - Matt Fisher - UF - big grin * 15 May 2012 - 22 May 2012 - Laria Redjiimi - Rice - smile * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool!

Revision 1192012-04-25 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 930 to 930
  * 27 March 2012 - 3 April 2012 - G.P. Di Giovanni - UF - Radioactive * 3 April 2012 - 10 April 2012 - Laria Redjiimi - Rice - smile * 10 April 2012 - 17 April 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 10 April 2012 - 26 April 2012 - CERN car - UF - yes
>
>
* 10 April 2012 - 20 April 2012 - CERN car - UF - yes
  * 17 April 2012 - 24 April 2012 - Matt Fisher - UF - big grin * 24 April 2012 - 1 May 2012 - Laria Redjiimi - Rice - smile * 1 May 2012 - 8 May 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 1 May 2012 - 17 May 2012 - CERN car - UF - yes
>
>
* 15 May 2012 - 25 May 2012 - CERN car - UF - yes
  * 8 May 2012 - 15 May 2012 - Matt Fisher - UF - big grin * 15 May 2012 - 22 May 2012 - Laria Redjiimi - Rice - smile * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool!
Deleted:
<
<
* 22 May 2012 - 29 May 2012 - CERN car - UF - yes
  * 29 May 2012 - 5 June 2012 - Matt Fisher - UF - big grin * 5 June 2012 - 12 June 2012 - G.P. Di Giovanni - UF - Radioactive * 12 June 2012 - 19 June 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 12 June 2012 - 19 June 2012 - CERN car - UF - yes
>
>
* 12 June 2012 - 2 July 2012 - CERN car - UF - yes
 
  * 19 June 2012 - 26 June 2012 - Matt Fisher - UF - big grin
  * 26 June 2012 - 3 July 2012 - Laria Redjiimi - Rice - smile
-->

Revision 1182012-04-24 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 940 to 940
  * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool! * 22 May 2012 - 29 May 2012 - CERN car - UF - yes * 29 May 2012 - 5 June 2012 - Matt Fisher - UF - big grin
Changed:
<
<
* 5 June 2012 - 12 June 2012 - Laria Redjiimi - Rice - smile
>
>
* 5 June 2012 - 12 June 2012 - G.P. Di Giovanni - UF - Radioactive
  * 12 June 2012 - 19 June 2012 - Justin Hugon - UF - cool! * 12 June 2012 - 19 June 2012 - CERN car - UF - yes * 19 June 2012 - 26 June 2012 - Matt Fisher - UF - big grin

Revision 1172012-04-17 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 880 to 880
 ssh -Y @cms904usr
Changed:
<
<
The CSCTF Machine is named vmepc-e1x07-27-01, with alias l1ts904-csctf
>
>
The CSCTF Machine is named vmepc-e1x07-27-01, with alias l1ts-csctf
  The URL for the cell is http://vmepc-e1x07-27-01.cms904:2974

Revision 1162012-04-10 - LariaRedjimi

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 991 to 991
  Please note: to use CSCTF CERN car your name has to be in car documents.

You are allowed to drive inside the CERN perimeter. If you need to go out the default perimeter limitations you need a "Job Order" (via EDH).

Added:
>
>

How to access to CSCTF WBM

First of all you need to get wbm account you can ask:

  • Juan Lopaz

After that you need to access as the following:

  • ssh cmswbmdev3
  • cd wbm
  • source scripts/tomcat_cmswbm
  • make

In order to make any changes for csctf wbm you will find the code at: * wbm/cmsdb/CSCSummary.java * wbm/htdocs/applet/CSCSummaryApplet.java

In order to install the new changes on the cmswbmdev server, the user must also be in the wbmdevsudoers user group, and type:

  • sudo make install

Saving new counters in WBM

  • ssh cmsusr
  • ssh cmswbmdev
  • export TNS_ADMIN=/etc
  • sqlplus CMS_CSC_TF_MON@cms_omds_lb
  • pswd ask "Gian Piero"

  • to create a table you need to have three things: "value", "time stamp" and "sub-channel"
CREATE TABLE LASTVALUE AS
  SELECT DISTINCT
         HALO_RATE
        ,STUB_RATE
        ,TRACK_RATE
        ,SYS_EXTRACT_UTC(SYSTIMESTAMP) TIME
  FROM   CMS_CSC_TF_MON.CSCTF_RATES_T
  WHERE  CSCTF_CSCTF_RATES_UNIQUEID =
         (
          SELECT MAX(UNIQUEID) KEEP (DENSE_RANK LAST ORDER BY "TIMESTAMP")
          FROM   CMS_CSC_TF_MON.CSCTF_CSCTF_RATEST
         )
/

GRANT SELECT ON LASTVALUE TO PUBLIC
/
CREATE OR REPLACE TRIGGER CSCTF_RATES_T_INSERT
  BEFORE INSERT ON CSCTF_RATES_T
  FOR EACH ROW
BEGIN
  UPDATE LASTVALUE SET
    HALO_RATE = :NEW.HALO_RATE,
    STUB_RATE = :NEW.STUB_RATE,
    TRACK_RATE = :NEW.TRACK_RATE,
    TIME = SYS_EXTRACT_UTC(SYSTIMESTAMP);
END CSCTF_RATES_T_INSERT;
/
 

Relevant Websites

List of web pages:

Revision 1152012-04-05 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 204 to 204
  N.B.: In this example I will be using LUTs which are in *.bin version.
Changed:
<
<
Get the LUTs (which in general someone, could be also you :P) and plave the into a folder. In general we put them in SPLUTsAndFirmWare/LUTs/bin/.
>
>
Get the LUTs (which in general someone, could be also you :P) and save the into the proper folder.

DEFAULT FOLDER = $CSCTF/SPLUTsAndFirmWare/LUTs/bin/

 Next, check that only appropriate LUTs have changed by running $CSCTF/misc/diffLUTs.py oldLUTsDir/ newLUTsDir/. Only changed files should not match.
Changed:
<
<
Now you have to recompile the code of the binary which upload the LUTs. It is in SPLUTsAndFirmWare/test/crateLoadLUTs.cpp.
>
>
Now you have to recompile the code of the binary which upload the LUTs.

Edit: $CSCTF/SPLUTsAndFirmWare/test/crateLoadLUTs.cpp.

  The change is just to tell the code where to pick the LUTs: the line to modify is
std::string vers = "your_folder"; 
(in this case the code will look in SPLUTsAndFirmWare/LUTs/bin/your_folder).

Revision 1142012-03-28 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 229 to 229
 cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/
Added:
>
>
and rename them appropriately (SP1.dat SP2.dat, SP3.dat ... etc)
 Test the LUTs are correctly loaded modify crateRunCRC before using:
 emacs $CSCTF/SPLUTsAndFirmWare//test/crateRunCRC.cpp 
the line to modify is
std::string vers = "your_folder"; 

Revision 1132012-03-26 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 1002 to 1002
 
Added:
>
>
  CSCTF emulator:

Revision 1122012-03-23 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 534 to 534
  Extract the headers to: $CSCTF/SPValidation/include/
Extract the cpp files to: $CSCTF/SPValidation/src/common/
Added:
>
>
Extract the .dat files to: $CSCTF/SPValidation/bin/
  For simpler wrapper-oriented tests use TestSPconsole. Build the same as above, but use ./TestSPconsole -s in bin.

Revision 1112012-03-23 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 204 to 204
  N.B.: In this example I will be using LUTs which are in *.bin version.
Changed:
<
<
Get the LUts (which in general someone, could be also you :P) and plave the into a folder. In general we put them in SPLUTsAndFirmWare/LUTs/bin/.
>
>
Get the LUTs (which in general someone, could be also you :P) and plave the into a folder. In general we put them in SPLUTsAndFirmWare/LUTs/bin/. Next, check that only appropriate LUTs have changed by running $CSCTF/misc/diffLUTs.py oldLUTsDir/ newLUTsDir/. Only changed files should not match.
 Now you have to recompile the code of the binary which upload the LUTs. It is in SPLUTsAndFirmWare/test/crateLoadLUTs.cpp.

The change is just to tell the code where to pick the LUTs: the line to modify is

std::string vers = "your_folder"; 
(in this case the code will look in SPLUTsAndFirmWare/LUTs/bin/your_folder).
Line: 873 to 874
  The CSCTF Machine is named vmepc-e1x07-27-01, with alias l1ts904-csctf
Changed:
<
<
The URL for the cell is vmepc-e1x07-27-01.cms904:2974
>
>
The URL for the cell is http://vmepc-e1x07-27-01.cms904:2974
  You will need a tunnel to 904 to access the cell via web: ssh -t -L 9999:localhost:1081 lxplus.cern.ch ssh -ND 1081 cms904usr

Revision 1102012-03-08 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 170 to 170
 
Changed:
<
<
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
>
>
 

Revision 1092012-03-08 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 168 to 168
 When you created new Key you have to:

  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...
Added:
>
>
 
  • upload new information at CSC and Trigger elog
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
  • call Jinghua Liu (165930) to change comics key at RCMS
Line: 224 to 225
 The executable will dump some *.dat files which will be used in the configuration process to check the LUTs are properly loaded in the SPs. These files will be indeed have to be put in the database when you create a configuration key. IF THE DAT FILE FOR A SPECIFIC KEY IN THE DBS WON'T MATCH THE ONE DUMPED FROM THE SCRIPT THE CONFIGURATION OF THE SPs WILL FAIL!


Changed:
<
<
cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/904
>
>
cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/
 

Test the LUTs are correctly loaded modify crateRunCRC before using:

Line: 247 to 248
 Change information about new LUTs in configuration key:


Changed:
<
<
emacs $CSCTF/ts/scripts/newMezzanine/904/dbSPadd_grun.sh
>
>
emacs $CSCTF/ts/scripts/newMezzanine/dbSPadd_grun.sh
 

Line to modify:

 LUT_ROOT="bin/your_folder/"; 

Revision 1082012-03-08 - LariaRedjimi

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 144 to 144
  A configuration key is a set of values assigned to the various registers in the SP. You should create a new configuration key for each version of the SP firmware released and any time you decide that a new register value is more beneficial than a previous one (e.g. timing improvements, tuning parameters based on physics studies, etc).
Changed:
<
<
The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904
>
>
The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine
  The files to change before writing the new key according to the change you want perform are in the same folder:

  • firmwareVersions -> if you updated the firmware version of SP, CCB or MS
  • SP$i.dat, $i=1,2,...,12 -> if you updated new LUTs
    (you should get these from the MONITOR files in $CSCTF/SPLUTsAndFirmWare/LUTs/bin/cmssw_x_x_x/monitorData/ and overwrite accordingly: ie SP7_cmssw_3_6_3_MonitorData.dat would become SP7.dat)
Added:
>
>
* Edit the "dbSPadd_grun.sh" script and rename the right static2_config.....txt file wich located at:

* STATIC_CONFIG= "...." = We should check if really the on  call expert needs to touch the below three lines??? ==

 
  • static2_config.txt -> if you modify any register for static configuration
  • timing2_config.txt -> if you modify any register for timing configuration
  • eta2_config.txt -> if you modify any register for eta cuts configuration

Revision 1072012-03-01 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 855 to 855
 SPValidation/bin/TestSPconsole -s16
Changed:
<
<

How to Take a Local Run in 904 With SLC5X

>
>

New 904 With SLC5X

904 With SLC5 Basics:

  To Log into 904 from CERN network (lxplus):
Changed:
<
<

>
>
 ssh -Y @cms904usr
Changed:
<
<
>
>
  The CSCTF Machine is named vmepc-e1x07-27-01, with alias l1ts904-csctf
Added:
>
>
The URL for the cell is vmepc-e1x07-27-01.cms904:2974

You will need a tunnel to 904 to access the cell via web: ssh -t -L 9999:localhost:1081 lxplus.cern.ch ssh -ND 1081 cms904usr

  • p5and904.pac: This .pac file allows connections to both P5 and 904 private networks (may require lots of reloading!)

How to Take a Local Run in 904 With SLC5X

 Disclaimer: hopefully these instructions will change and made consistent with P5 setup, but as of today (29/02/2012) the 904 SLC5X migration is still a work in progress and the situation is very fluid right now.

  • TF Cell is running inside the .cms904 private network, and the Supervisor (and the rest of the apps) outside. We need to do some port forwarding for the two to talk to each other:
Line: 880 to 890
 
Deleted:
<
<
Additional Hints: The CSCTF computer is aliased as l1ts904-csctf
 

Responsibility of pager expert

CSCTF On Call Experts Shifts
Name
|<
<>>|
NovDec
Tu
12
We
13
Th
14
Fr
15
  Mo
18
Tu
19
We
20
Th
21
Fr
22
  Mo
25
Tu
26
We
27
Th
28
Fr
29
  Mo
2
Tu
3
We
4
Th
5
Fr
6
  Mo
9
Tu
10
We
11
Line: 997 to 1007
 
META FILEATTACHMENT attachment="gdbCommands" attr="" comment="gdb commands" date="1249921346" name="gdbCommands" path="gdbCommands" size="45" stream="gdbCommands" user="Main.GianPieroDiGiovanni" version="1"
META FILEATTACHMENT attachment="hotspot.xml" attr="" comment="" date="1274268368" name="hotspot.xml" path="hotspot.xml" size="30" stream="hotspot.xml" tmpFilename="/usr/tmp/CGItemp43723" user="kkotov_40phys_2eufl_2eedu" version="1"
META FILEATTACHMENT attachment="cms_proxy.pac" attr="" comment="" date="1279804327" name="cms_proxy.pac" path="cms_proxy.pac" size="1028" stream="cms_proxy.pac" tmpFilename="/usr/tmp/CGItemp59205" user="kropiv" version="1"
Added:
>
>
META FILEATTACHMENT attachment="p5and904.pac" attr="" comment=".pac file for connecting to both P5 and 904 private networks" date="1330614819" name="p5and904.pac" path="p5and904.pac" size="585" stream="p5and904.pac" tmpFilename="/usr/tmp/CGItemp44386" user="jhugon" version="1"

Revision 1062012-03-01 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 857 to 857
 

How to Take a Local Run in 904 With SLC5X

Added:
>
>
To Log into 904 from CERN network (lxplus):

ssh -Y @cms904usr

The CSCTF Machine is named vmepc-e1x07-27-01, with alias l1ts904-csctf

 Disclaimer: hopefully these instructions will change and made consistent with P5 setup, but as of today (29/02/2012) the 904 SLC5X migration is still a work in progress and the situation is very fluid right now.

  • TF Cell is running inside the .cms904 private network, and the Supervisor (and the rest of the apps) outside. We need to do some port forwarding for the two to talk to each other:

Revision 1052012-02-29 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 528 to 528
 Extract the headers to: $CSCTF/SPValidation/include/
Extract the cpp files to: $CSCTF/SPValidation/src/common/
Added:
>
>
For simpler wrapper-oriented tests use TestSPconsole. Build the same as above, but use ./TestSPconsole -s in bin.
 

How to update TS at 904

Line: 871 to 872
 
Added:
>
>
Additional Hints: The CSCTF computer is aliased as l1ts904-csctf
 

Responsibility of pager expert

CSCTF On Call Experts Shifts
Name
|<
<>>|
NovDec
Tu
12
We
13
Th
14
Fr
15
  Mo
18
Tu
19
We
20
Th
21
Fr
22
  Mo
25
Tu
26
We
27
Th
28
Fr
29
  Mo
2
Tu
3
We
4
Th
5
Fr
6
  Mo
9
Tu
10
We
11

Revision 1042012-02-29 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 854 to 854
 SPValidation/bin/TestSPconsole -s16
Added:
>
>

How to Take a Local Run in 904 With SLC5X

Disclaimer: hopefully these instructions will change and made consistent with P5 setup, but as of today (29/02/2012) the 904 SLC5X migration is still a work in progress and the situation is very fluid right now.

  • TF Cell is running inside the .cms904 private network, and the Supervisor (and the rest of the apps) outside. We need to do some port forwarding for the two to talk to each other:

  • RCMS interface is not available in the usual format. To run the supervisor please use the link at http://vmepc-e1x07-25-01.cern.ch:20000. From there you have all the buttons you need to configure/start/stop/reset the system.

 

Responsibility of pager expert

CSCTF On Call Experts Shifts
Name
|<
<>>|
NovDec
Tu
12
We
13
Th
14
Fr
15
  Mo
18
Tu
19
We
20
Th
21
Fr
22
  Mo
25
Tu
26
We
27
Th
28
Fr
29
  Mo
2
Tu
3
We
4
Th
5
Fr
6
  Mo
9
Tu
10
We
11

Revision 1032012-02-28 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 957 to 957
 
Added:
>
>
  CSCTF emulator:

Revision 1022012-02-15 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 162 to 162
  When you created new Key you have to:
Changed:
<
<
  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...
>
>
  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...
 
  • upload new information at CSC and Trigger elog
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
  • call Jinghua Liu (165930) to change comics key at RCMS

Revision 1012012-02-14 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 311 to 311
  https://twiki.cern.ch/twiki/bin/viewauth/CMS/HowToReadTheLogsOnlineAndOffline
Added:
>
>

How to Take a Local Run at P5

Follow the instructions here:

https://twiki.cern.ch/twiki/bin/view/CMS/CSCOperations#Local_Runs

This is the link to RCMS: http://cmsrc-csc.cms:12000/rcms/gui/servlet/RunGroupChooserServlet

(username: cscpro)

 

How to take data at 904

See Links:

Revision 1002012-02-14 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 455 to 455
  the output will be saved in a file called output. Look through it and find the leaks that are definitely/indirectly lost, as valgrind will give you the line numbers of the offending memory leaks.
Added:
>
>

How To Test Raw Data Format

To set up the raw analyzer (ie in CMSSW_4_2_1):


cmsrel CMSSW_4_2_1
cd CMSSW_4_2_1
cd src
cvs co EventFilter/CSCTFRawToDigi
cvs co IORawData/CSCCommissioning
cvs co L1Trigger/CSCTrackFinder
cmsenv
scram build -c
scramv1 b

now overwrite src/EventFilter/CSCTFRawToDigi/plugins/CSCTFAnalyzer.cc with the one from:

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/UserCode/madfish/CSCTF/EventChecker/?sortby=log&sortdir=down

(CSCTFAnalyzer.h goes to src/EventFilter/CSCTFRawToDigi/interface)
 
and from the same link copy 

analyzer.py, myanalyzer.py, dumpraw.py, and mydump.py to src/EventFiler/CSCTFRawToDigi/test 

edit myanalyzer.py to the raw data file from csc-daq10 /data folder.  

To make a tunnel: ssh -L 2999:csc-daq10.cms:22 user@cmsusr
and then use scp -P 2999 localhost:/data/file .

 

How To Run The SPTester Tool

First, for more information about how these programs were written please consult:

Revision 992012-02-10 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 877 to 877
  so talk before to come at Point 5 with shift leader if he could provide you person, who has access to USC. If he couldn't then contact with another CSCTF expert which are listed at table above and ask for help. If other CSCTF expert are not available ask help from CSC-DOC or CSC experts (Misha...).
Changed:
<
<
If you don't fill safe to do this changes without another CSCTF expert then don't hesitate to contact he/she event during night.
>
>
If you don't fill safe to do this changes without another CSCTF expert then don't hesitate to contact he/she even during night.
 
    • Upload and tested firmware at 904 or Point 5 if it is requested by CSCTF group. Take local run.
    • Create CSCTF key if it is requested.
Changed:
<
<
    • If it is urgent situation and you don't know what to do please don't hesitate to contact another CSCTF expert event during night.
>
>
    • If it is urgent situation and you don't know what to do please don't hesitate to contact another CSCTF expert even during night.
 
  • Other notes:
    • If you want to go to vacation then you have to agree with another expert on-call to change dates and announce it on the CSCTF meeting.

Revision 982012-02-10 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 822 to 822
  * 25 Dec 2006 - Antony Adair * 25 Dec 2006 - Anna Kropivnitskaya * 25 Dec 2006 - G.P. Di Giovanni
Added:
>
>
* 25 Dec 2006 - CERN car
  * 7 February 2012 - 14 February 2012 - Justin Hugon - UF - cool! * 14 February 2012 - 21 February 2012 - Matt Fisher - UF - big grin * 21 February 2012 - 28 February 2012 - Laria Redjiimi - Rice - smile * 28 February 2012 - 6 March 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 2 March 2012 - 6 March 2012 - CERN car - UF - yes
  * 6 March 2012 - 13 March 2012 - Matt Fisher - UF - big grin * 13 March 2012 - 20 March 2012 - Laria Redjiimi - Rice - smile * 20 March 2012 - 27 March 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 20 March 2012 - 5 April 2012 - CERN car - UF - yes
  * 27 March 2012 - 3 April 2012 - G.P. Di Giovanni - UF - Radioactive * 3 April 2012 - 10 April 2012 - Laria Redjiimi - Rice - smile * 10 April 2012 - 17 April 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 10 April 2012 - 26 April 2012 - CERN car - UF - yes
  * 17 April 2012 - 24 April 2012 - Matt Fisher - UF - big grin * 24 April 2012 - 1 May 2012 - Laria Redjiimi - Rice - smile * 1 May 2012 - 8 May 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 1 May 2012 - 17 May 2012 - CERN car - UF - yes
  * 8 May 2012 - 15 May 2012 - Matt Fisher - UF - big grin * 15 May 2012 - 22 May 2012 - Laria Redjiimi - Rice - smile * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 22 May 2012 - 29 May 2012 - CERN car - UF - yes
  * 29 May 2012 - 5 June 2012 - Matt Fisher - UF - big grin * 5 June 2012 - 12 June 2012 - Laria Redjiimi - Rice - smile * 12 June 2012 - 19 June 2012 - Justin Hugon - UF - cool!
Added:
>
>
* 12 June 2012 - 19 June 2012 - CERN car - UF - yes
 
  * 19 June 2012 - 26 June 2012 - Matt Fisher - UF - big grin
  * 26 June 2012 - 3 July 2012 - Laria Redjiimi - Rice - smile
-->
Line: 866 to 873
  If you want to change phone at another time, day or place, please agree with another expert and do it if only he/she agrees (especial if there is holidays).
    • Each morning check CSCTF plots at online DQM for collision runs: dqm Work space -> Trigger/Lumi -> L1T -> Top -> L1T -> L1CSCTF
    • CSCTF expert on-call has to have car and be ready to come at Point 5 and any time if necessary during shifts.
Changed:
<
<
    • Change SP board at Point 5 if it broken. 2 people has to do it. It is better to contact with another CSCTF expert which are listed at table above and ask for help.
>
>
    • Change SP board at Point 5 if it broken. 2 people has to be underground, so talk before to come at Point 5 with shift leader if he could provide you person, who has access to USC. If he couldn't then contact with another CSCTF expert which are listed at table above and ask for help.
  If other CSCTF expert are not available ask help from CSC-DOC or CSC experts (Misha...).
Added:
>
>
If you don't fill safe to do this changes without another CSCTF expert then don't hesitate to contact he/she event during night.
 
    • Upload and tested firmware at 904 or Point 5 if it is requested by CSCTF group. Take local run.
    • Create CSCTF key if it is requested.
Added:
>
>
    • If it is urgent situation and you don't know what to do please don't hesitate to contact another CSCTF expert event during night.
 
  • Other notes:
    • If you want to go to vacation then you have to agree with another expert on-call to change dates and announce it on the CSCTF meeting.

Revision 972012-02-07 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 903 to 903
 
Added:
>
>
CSCTF emulator:

 -- GianPieroDiGiovanni - 08-Mar-2010 /s

Revision 962012-02-07 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 830 to 830
  * 6 March 2012 - 13 March 2012 - Matt Fisher - UF - big grin * 13 March 2012 - 20 March 2012 - Laria Redjiimi - Rice - smile * 20 March 2012 - 27 March 2012 - Justin Hugon - UF - cool!
Changed:
<
<
* 27 March 2012 - 3 April 2012 - G.P. Di Giovanni - UF - thumbs up
>
>
* 27 March 2012 - 3 April 2012 - G.P. Di Giovanni - UF - Radioactive
  * 3 April 2012 - 10 April 2012 - Laria Redjiimi - Rice - smile * 10 April 2012 - 17 April 2012 - Justin Hugon - UF - cool! * 17 April 2012 - 24 April 2012 - Matt Fisher - UF - big grin

Revision 952012-02-07 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 846 to 846
 
  * 26 June 2012 - 3 July 2012 - Laria Redjiimi - Rice - smile
-->
Changed:
<
<
  • Participation in the daily (even during weekends) CSC phone meeting at 18:00
    • you have to be subscribe to hn-cms-csc-ops@cernNOSPAMPLEASE.ch. Every day it is announced phone meeting, sometimes it cancels.
    • phone meeting could be reachable at EVO -> CMS -> CMS Muon Operations

  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
>
>
  • Organize CSCTF working meeting, which is running every Tuesday at 18:00 (in most cases by EVO only):
 
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
Changed:
<
<
    • (When Darin/Ivan are at CERN) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting. Some days we have booked room 40-R-B10. Availability of the room you could check here: booked days.
>
>
    • (When it is requested by the group) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting. Some days we have booked room 40-R-B10. Availability of the room you could check here: booked days.
 
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.
    • Prepare pager report for the last week.
Changed:
<
<
    • To run meeting.
    • Also Attend the Daily CSC Operations Meetings at 18:00 pm and prepare/present a 10 minute talk for the CSC Operations+DPG Meeting Wednesday at 18:00
    • It is recommended to all CSCTF experts (Laria, Matt and Anna) attend each CSCTF meeting if possible.
>
>
    • Run meeting.
    • It is recommended to all CSCTF experts (Antony, Justin, Laria and Matt) attend each CSCTF meeting if possible.

  • Other meetings:
    • Participation in the daily (even during weekends) CSC phone meeting at 18:00.
      • you have to be subscribe to hn-cms-csc-ops@cernNOSPAMPLEASE.ch. Every day it is announced phone meeting, sometimes it cancels.
      • phone meeting could be reachable at EVO -> CMS -> CMS Muon Operations.
    • CSC Operations+DPG Meeting Wednesday at 18:00: prepare/present a 10 minute CSCTF status talk for it.

  • Service work during on-call time:
    • Expert CSCTF Phone should be rotated every Tuesday after lunch time at CERN. New expert should be available and pick up his/her phone. If you want to change phone at another time, day or place, please agree with another expert and do it if only he/she agrees (especial if there is holidays).
 
    • Each morning check CSCTF plots at online DQM for collision runs: dqm Work space -> Trigger/Lumi -> L1T -> Top -> L1T -> L1CSCTF
Added:
>
>
    • CSCTF expert on-call has to have car and be ready to come at Point 5 and any time if necessary during shifts.
    • Change SP board at Point 5 if it broken. 2 people has to do it. It is better to contact with another CSCTF expert which are listed at table above and ask for help. If other CSCTF expert are not available ask help from CSC-DOC or CSC experts (Misha...).
    • Upload and tested firmware at 904 or Point 5 if it is requested by CSCTF group. Take local run.
    • Create CSCTF key if it is requested.

  • Other notes:
    • If you want to go to vacation then you have to agree with another expert on-call to change dates and announce it on the CSCTF meeting.
 
Changed:
<
<
If you have any question, proposal or need help, please contact to Anna Kropivnitskaya
>
>
If you have any question, proposal or need help in training, please contact to Anna Kropivnitskaya.
 

CSCTF CERN car

Revision 942012-02-07 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 824 to 824
  * 25 Dec 2006 - G.P. Di Giovanni

* 7 February 2012 - 14 February 2012 - Justin Hugon - UF - cool!

Changed:
<
<
* 14 February 2012 - 21 February 2012 - Matt Fisher - UF - 9-) * 21 February 2012 - 28 February 2012 - Laria Redjiimi - UF - smile
>
>
* 14 February 2012 - 21 February 2012 - Matt Fisher - UF - big grin * 21 February 2012 - 28 February 2012 - Laria Redjiimi - Rice - smile * 28 February 2012 - 6 March 2012 - Justin Hugon - UF - cool! * 6 March 2012 - 13 March 2012 - Matt Fisher - UF - big grin * 13 March 2012 - 20 March 2012 - Laria Redjiimi - Rice - smile * 20 March 2012 - 27 March 2012 - Justin Hugon - UF - cool! * 27 March 2012 - 3 April 2012 - G.P. Di Giovanni - UF - thumbs up * 3 April 2012 - 10 April 2012 - Laria Redjiimi - Rice - smile * 10 April 2012 - 17 April 2012 - Justin Hugon - UF - cool! * 17 April 2012 - 24 April 2012 - Matt Fisher - UF - big grin * 24 April 2012 - 1 May 2012 - Laria Redjiimi - Rice - smile * 1 May 2012 - 8 May 2012 - Justin Hugon - UF - cool! * 8 May 2012 - 15 May 2012 - Matt Fisher - UF - big grin * 15 May 2012 - 22 May 2012 - Laria Redjiimi - Rice - smile * 22 May 2012 - 29 May 2012 - Justin Hugon - UF - cool! * 29 May 2012 - 5 June 2012 - Matt Fisher - UF - big grin * 5 June 2012 - 12 June 2012 - Laria Redjiimi - Rice - smile * 12 June 2012 - 19 June 2012 - Justin Hugon - UF - cool! * 19 June 2012 - 26 June 2012 - Matt Fisher - UF - big grin * 26 June 2012 - 3 July 2012 - Laria Redjiimi - Rice - smile
 
-->

Revision 932012-02-06 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 813 to 813
 

Responsibility of pager expert

Added:
>
>
CSCTF On Call Experts Shifts
Name
|<
<>>|
NovDec
Tu
12
We
13
Th
14
Fr
15
  Mo
18
Tu
19
We
20
Th
21
Fr
22
  Mo
25
Tu
26
We
27
Th
28
Fr
29
  Mo
2
Tu
3
We
4
Th
5
Fr
6
  Mo
9
Tu
10
We
11
Anna Kropivnitskaya                              
Antony Adair                              
G.P. Di Giovanni                              
Justin Hugon                              
Laria Redjiimi                              
Matt Fisher                              

<!-- Just Place holders:
  * 25 Dec 2006 - Matt Fisher
  * 25 Dec 2006 - Justin Hugon
  * 25 Dec 2006 - Laria Redjiimi
  * 25 Dec 2006 - Antony Adair
  * 25 Dec 2006 - Anna Kropivnitskaya
  * 25 Dec 2006 - G.P. Di Giovanni

* 7 February 2012 - 14 February 2012 - Justin Hugon - UF - cool! * 14 February 2012 - 21 February 2012 - Matt Fisher - UF - 9-) * 21 February 2012 - 28 February 2012 - Laria Redjiimi - UF - smile -->

 
  • Participation in the daily (even during weekends) CSC phone meeting at 18:00
    • you have to be subscribe to hn-cms-csc-ops@cernNOSPAMPLEASE.ch. Every day it is announced phone meeting, sometimes it cancels.
    • phone meeting could be reachable at EVO -> CMS -> CMS Muon Operations

Revision 922012-02-06 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 824 to 824
 
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.
    • Prepare pager report for the last week.
    • To run meeting.
Changed:
<
<
    • Also Attend the Daily CSC Operations Meetings at 18:00 pm and prepare/present a 10 minute talk for the L1 DPG Meeting Wednesday at 18:00
>
>
    • Also Attend the Daily CSC Operations Meetings at 18:00 pm and prepare/present a 10 minute talk for the CSC Operations+DPG Meeting Wednesday at 18:00
 
    • It is recommended to all CSCTF experts (Laria, Matt and Anna) attend each CSCTF meeting if possible.
    • Each morning check CSCTF plots at online DQM for collision runs: dqm Work space -> Trigger/Lumi -> L1T -> Top -> L1T -> L1CSCTF

Revision 912012-02-03 - JustinHugon

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 52 to 52
  Howto on Firefox:
  • go to Edit -> Preferences -> Advanced -> Connection Settings -> Select "Automatic proxy configuration URL" and give the location of your pac file, e.g. file:///home/username/cms.pac
Added:
>
>
  • On Firefox 9, Edit -> Preferences -> Advanced -> Network -> (Connection) Settings ; and do above.
 
Commands to open a tunnel:

Revision 902012-02-03 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 55 to 55
 
Commands to open a tunnel:
Changed:
<
<
  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr1
>
>
  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr
 

Revision 892012-01-28 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 737 to 737
 
    • check if the service is still up and running: ps aux | grep csctf-store. If an instance of it exist, this is the cause of your problem: KILL IT MANUALLY, "sudo kill jobid"
    • start the service again: sudo /sbin/service triggerd start csctf-store
Added:
>
>

How to read data format

cp ~gilmore/jason/connectionsDB.dat ./
~gilmore/jason/eop2008 /data/file.raw |less

in less finde * = /*\*\* * or ** is worning

more then 2 * is error

Live DMB Flags = 7e3fh.

73ef = 0111 1110 0011 1111 -> 12 links are one like 12 SP

If you fine error in program the you could look more detailed in file with

hexdump /data/file.raw

DDU data formart you could find here:

http://www.physics.ohio-state.edu/~cms/ddu/#DDU-Format

 

Other Information

Useful DBS Queries

Revision 882011-12-07 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 263 to 263
 * You can check database push counts at http://emulab03.cern.ch:5007/urn:xdaq-application:lid=10/
* Add Logging to a file if you wish (see CSR_TTCRQ_LLCK example)

Added:
>
>
see: https://twiki.cern.ch/twiki/bin/view/Main/CsctfTriggerSupervisor#How_to_add_a_register_to_monitor
 

How to Check How Many file descriptors are open by the csctf-cell

From vmepcS2G18-10 connected with your username (do not switch to csctfts as you need sudo right) type

Revision 872011-11-10 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 109 to 109
  CSCTF SPs have two firmware kind:
Changed:
<
<
  • "chain 0" firmware: it is to be loaded in the Main FPGA mounted on the mezzanine card
  • "chain 1" firmware: it is to be loaded in the Front FPGA (F1,F2,...,F5)
>
>
  • "chain 0" firmware: it is to be loaded in the Main FPGA mounted on the mezzanine card (takes ~ 15 min. per SP)
  • "chain 1" firmware: it is to be loaded in the Front FPGA (F1,F2,...,F5) (takes ~ 5 min. per SP)
  The script to load the firmware is $CSCTF/SPLUTsAndFirmWare/scripts/loadFirmware.sh; it is actually a bash script. Open it and change the options inside to point to the right files. There are 2 blocks: the first for "chain 1" firmware and the second one for "chain 0". If you load chain 0 fw, the chain 1 block should be all commented out (and viceversa).

Revision 862011-11-09 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 415 to 415
  - the release manager (me for 3.11.x, andrea.bocci, Shahzad.Malik.Muzaffar and Adeel.Adeel-Ur-Rehman for 4.2.x)

How to turn off/on local DAQ at P5

Changed:
<
<
Global DAQ should be configured and ready to start run. CSC and may be CSCTF should be reconfigure during DAQ configuration otherwise script will not work:
>
>
Make sure that DAQ_Write_Y_Build_N shows up at RCMS http://cmsrc-csc.cms:12000/rcms/gui/servlet/RunGroupChooserServlet
Global DAQ should be configured and ready to start run (have the DAQ Shifter call you when they are ready to start the run):
  Turn ON local DAQ writing:
cd $CSCTF
./TFRUIWriteAllEvents
Changed:
<
<
Turn off local DAQ (write bad events only) :
cd $CSCTF
./TFRUIWriteAllEventsOFF
>
>
  Check that file are written at local DAQ data pc: csc-daq10 in the folder /data. You will see a new RUI00 file if the local DAQ is enabled. Use "ls -ltr" to see last file created!
Line: 433 to 433
  Be careful data could be written only with rate not more then 2 kHz. In case if L1_Physics rate is greater than 2 kHz then it will be prescales at local DAQ.
Added:
>
>
To turn off local DAQ full file logging :
cd $CSCTF
./TFRUIWriteAllEventsOFF
 

How to Run Valgrind To Check For Memory Leaks

To get information about the cell profile:

Revision 852011-11-04 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 428 to 428
 Check that file are written at local DAQ data pc: csc-daq10 in the folder /data. You will see a new RUI00 file if the local DAQ is enabled. Use "ls -ltr" to see last file created!
Added:
>
>
http://csc-daq10.cms:20300/urn:xdaq-application:lid=18/
check that writeBadEventsOnly = false
 Be careful data could be written only with rate not more then 2 kHz. In case if L1_Physics rate is greater than 2 kHz then it will be prescales at local DAQ.

How to Run Valgrind To Check For Memory Leaks

Revision 842011-11-02 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 254 to 254
  When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.
Added:
>
>

How to add a register to monitor to OSW

* Create a file $CSCTF/ts/src/worker/MonitorSource_RegisterName.cc (header file in /interface)
* Structure it according to examples in the same directory, ie MonitorSource_CSR_LNK_RXSD.cc 
* Edit CellContext.cc
* Edit $CSCTF/../setup/csctf (/flash and pulser)
* You can check database push counts at http://emulab03.cern.ch:5007/urn:xdaq-application:lid=10/
* Add Logging to a file if you wish (see CSR_TTCRQ_LLCK example)

 

How to Check How Many file descriptors are open by the csctf-cell

From vmepcS2G18-10 connected with your username (do not switch to csctfts as you need sudo right) type

Revision 832011-11-01 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 145 to 145
  The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904
Deleted:
<
<
The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309

This script simply calls other scripts to perform the key writing on the database.

 The files to change before writing the new key according to the change you want perform are in the same folder:

  • firmwareVersions -> if you updated the firmware version of SP, CCB or MS
Line: 159 to 155
 
  • eta2_config.txt -> if you modify any register for eta cuts configuration

Added:
>
>
The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309

This script simply calls other scripts to perform the key writing on the database.

 When you created new Key you have to:

  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...

Revision 822011-10-26 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 48 to 48
  To access the web page at P5 you need to open a tunnel to P5.

Changed:
<
<
Prerequisite to visualize the web pages after having open the tunnel is to download the cms.pac into your browser.
>
>
Prerequisite to visualize the web pages after having open the tunnel is to download the pac file cms_proxy.pac
  Howto on Firefox:
  • go to Edit -> Preferences -> Advanced -> Connection Settings -> Select "Automatic proxy configuration URL" and give the location of your pac file, e.g. file:///home/username/cms.pac

Commands to open a tunnel:
Deleted:
<
<
  • From the internal CERN network: ssh -ND 1080 username@cmsusrX, X=0,1
  • From outside the CERN network: ssh -t username@lxplus.cern.ch -L 1080:localhost:1081 "ssh -D 1081 username@cmsusr1.cern.ch"

 
Deleted:
<
<
If you have problem with upper tunnel (some site below are not reachable) then use another pac file cms_proxy.pac and the following command for tunnel:
 
  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr1
Added:
>
>

 

On Windows:

download and run Putty.

Revision 812011-10-17 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 692 to 692
 

How to Attach GDB To A Running Executable

Changed:
<
<
Example with the csctf-cell running on the l1ts-csctf machine and listening to port 2974:
>
>
There are two ways:

  • using the following script
    • ssh -X username@cmsusr1NOSPAMPLEASE.cern.ch
    • ssh -X csc-tf (do not switch to csctfts user as you need "sudo" permission to run gdb)
    • cd /nfshome0/csctfts/TriDAS/trigger/csctf/misc/gdbDumps
    • gdb_attach.py -v csctf-cell > file_yearmonthday

  • Manually (example with the csctf-cell running on the l1ts-csctf machine and listening to port 2974):
 
  • ssh l1ts-csctf
Changed:
<
<
  • pgrep -f "xdaq.*2974" e.g., you get =5283
>
>
    • pgrep -f "xdaq.*2974" (e.g., you get =5283)
 
  • sudo gdb
  • handle SIG33 nostop noprint noignore pass
  • attach (in our example one should type "attach 5283")

Revision 802011-09-15 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 779 to 779
 

CSCTF CERN car

CSCTF group has a CERN car for CSCTF issues in period 12 August 2010 - 23 December 2010. The main contact person is Anna Kropivnitskaya.

Changed:
<
<
If you want to use it please contract to Anna to clarify if car is available to prevent any over crossing. Availability of CSCTF car you could find at Google Calendar for CSCTF CERN car
>
>
If you want to use it, please contact Anna to clarify if a car is available and to prevent any over crossing. You could find the availability of the CSCTF car at Google Calendar for CSCTF CERN car
  Please note: to use CSCTF CERN car your name has to be in car documents.
Added:
>
>
You are allowed to drive inside the CERN perimeter. If you need to go out the default perimeter limitations you need a "Job Order" (via EDH).
 

Relevant Websites

List of web pages:

Revision 792011-08-25 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 406 to 406
  - the release manager (me for 3.11.x, andrea.bocci, Shahzad.Malik.Muzaffar and Adeel.Adeel-Ur-Rehman for 4.2.x)

How to turn off/on local DAQ at P5

Added:
>
>
Global DAQ should be configured and ready to start run. CSC and may be CSCTF should be reconfigure during DAQ configuration otherwise script will not work:
  Turn ON local DAQ writing:
cd $CSCTF
Line: 415 to 416
 cd $CSCTF
./TFRUIWriteAllEventsOFF
Changed:
<
<
local DAQ data is written to the pc: csc-daq10 in the folder /data. You will see a new RUI00 file if the local DAQ is enabled. Use "ls -ltrh" to see last file created!
>
>
Check that file are written at local DAQ data pc: csc-daq10 in the folder /data. You will see a new RUI00 file if the local DAQ is enabled. Use "ls -ltr" to see last file created!
 
Added:
>
>
Be careful data could be written only with rate not more then 2 kHz. In case if L1_Physics rate is greater than 2 kHz then it will be prescales at local DAQ.
 

How to Run Valgrind To Check For Memory Leaks

Revision 782011-08-24 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 405 to 405
  - the L2 reconstruction coordinators (Jean-Roch.Vlimant, and David.Lange)
- the release manager (me for 3.11.x, andrea.bocci, Shahzad.Malik.Muzaffar and Adeel.Adeel-Ur-Rehman for 4.2.x)
Added:
>
>

How to turn off/on local DAQ at P5

Turn ON local DAQ writing:
cd $CSCTF
./TFRUIWriteAllEvents

Turn off local DAQ (write bad events only) :
cd $CSCTF
./TFRUIWriteAllEventsOFF

local DAQ data is written to the pc: csc-daq10 in the folder /data. You will see a new RUI00 file if the local DAQ is enabled. Use "ls -ltrh" to see last file created!

 

How to Run Valgrind To Check For Memory Leaks

Revision 772011-08-15 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 757 to 757
 
    • To run meeting.
    • Also Attend the Daily CSC Operations Meetings at 18:00 pm and prepare/present a 10 minute talk for the L1 DPG Meeting Wednesday at 18:00
    • It is recommended to all CSCTF experts (Laria, Matt and Anna) attend each CSCTF meeting if possible.
Added:
>
>
    • Each morning check CSCTF plots at online DQM for collision runs: dqm Work space -> Trigger/Lumi -> L1T -> Top -> L1T -> L1CSCTF
  If you have any question, proposal or need help, please contact to Anna Kropivnitskaya

Revision 762011-08-09 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 784 to 784
 
Added:
>
>
  -- GianPieroDiGiovanni - 08-Mar-2010 /s

Revision 752011-08-03 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 587 to 587
 sudo /sbin/service triggerd start csctf-store
Added:
>
>

xdaq-flashlist variables don't appeared in CSCTF CELL

Restart (stop all 1st and start them after) the following processes with sudo /sbin/service triggerd:

'csctf-tstore'
'csctf-ws-eventing'
'csctf-las'
'csctf-pulser'
'csctf-sensor'
'csctf-store'
'csctf-cell'
'csctf-spotlight'

It is necessary to do if even they look ok. It could happen after csc-tf computer was off. Possibly problem in csctf-pulser and csctf-sensor processes which are sent information how often xdaq-flashlist variables should be updated.

 

Trigger Supervisor Troubleshooting

Revision 742011-07-06 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 161 to 161
  When you created new Key you have to:
Changed:
<
<
  • upload new information about keys at OnlineWBTrigger: go Main Trigger Page -> Documentation -> Online Workbook -> Updated version of OnlineWBL1TriggerKeys...
>
>
  • upload new information about keys at OnlineWBTrigger: go Here to update OnlineWBL1TriggerKeys...
 
  • upload new information at CSC and Trigger elog
Changed:
<
<
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
>
>
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
 

Revision 732011-03-16 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 735 to 735
 
  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
Changed:
<
<
    • (When Darin/Ivan are at CERN) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting.
>
>
    • (When Darin/Ivan are at CERN) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting. Some days we have booked room 40-R-B10. Availability of the room you could check here: booked days.
 
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.
    • Prepare pager report for the last week.
    • To run meeting.

Revision 722011-03-07 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 176 to 176
  You can check the key/register values when you are finished here
Added:
>
>
To Change Key In RCMS @904:

To change the TF key for cscdev:

1) Log in as cscdev@emuslice02 2) Edit /home/cscdev/config/fm/Local/Local.xml to change 'TrackFinderKey'. 3) Upload the modified Local configuration by issuing: RCMS_HOME=/home/cscdev/RunControl ~cscdev/bin/duckLoader cscdev /home/cscdev/config/fm/Local/Local.duck

For cscpro:

1) Log in as cscpro@emuslice02 2) Edit /home/cscpro/config/fm/Local/Local.xml to change 'TrackFinderKey'. 3) Upload the modified Local configuration by issuing: RCMS_HOME=/home/cscdev/RunControl ~cscdev/bin/duckLoader cscdev /home/cscpro/config/fm/Local/Local.duck

 

How To Load LUTs

N.B.: In this example I will be using LUTs which are in *.bin version.

Revision 712011-03-07 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 469 to 469
 

Out of Sync in Link Masking Panel

Changed:
<
<
At 904, if the CSCTF shows up "Out of Sync" in the link masking panel, and you notice that the FED lights are not on, or the Muon1, Muon2, Muon3 lights are not blinking on the TMB, you need to do some extra steps to configure the system.
>
>
At 904, if the CSCTF shows up "Out of Sync" in the link masking panel, and you notice that the FED lights are not on, or the Muon1, Muon2, Muon3 lights are not blinking on the MPC, you need to do some extra steps to configure the system.
  Step 1: Destroy all configurations in the 904 RCMS. If the most of the FED lights are on skip to Step 3. If they are off: Add the configurations Commissioning/startFED and proceed to Step 2.

Revision 702011-02-25 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 421 to 421
 the source code is: $CSCTF/SPValidation/test/SPtester_new.cpp
and executed in $CSCTF/SPValidaion/bin using the command ./SPtester_new -u -s16 -c20 -gc
the u uploads the pt LUTs specified in the source code, the s16 specifies slot 16 and the gc turns off singles, c20 runs the program for 20 cycles
Added:
>
>
to copy output to log file:

 
./SPtester_new -u -s16 -c20 -gc > log.txt 2>&1
(./SPtester_new -u -s16 -c20 -gc | grep Mode..Mismatch)> log.txt 2>&1
  if you need to update the core, download the proper vpp package from
http://www.phys.ufl.edu/~madorsky/sp/

Revision 692011-02-25 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 418 to 418
 cd test
make bin
Changed:
<
<
the source code is: $CSCTF/SPValidation/test/SPTester_new.cpp
>
>
the source code is: $CSCTF/SPValidation/test/SPtester_new.cpp
 and executed in $CSCTF/SPValidaion/bin using the command ./SPtester_new -u -s16 -c20 -gc
the u uploads the pt LUTs specified in the source code, the s16 specifies slot 16 and the gc turns off singles, c20 runs the program for 20 cycles

Revision 682011-02-25 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 419 to 419
 make bin

the source code is: $CSCTF/SPValidation/test/SPTester_new.cpp

Changed:
<
<
and executed in $CSCTF/SPValidaion/bin using the command ./SPTester_new -u -s16 -c20 -gc
>
>
and executed in $CSCTF/SPValidaion/bin using the command ./SPtester_new -u -s16 -c20 -gc
 the u uploads the pt LUTs specified in the source code, the s16 specifies slot 16 and the gc turns off singles, c20 runs the program for 20 cycles

if you need to update the core, download the proper vpp package from

Revision 672011-02-25 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 413 to 413
  To compile it:
Changed:
<
<
cd SPValidation make cd test make bin
>
>
cd SPValidation
make
cd test
make bin

the source code is: $CSCTF/SPValidation/test/SPTester_new.cpp
and executed in $CSCTF/SPValidaion/bin using the command ./SPTester_new -u -s16 -c20 -gc
the u uploads the pt LUTs specified in the source code, the s16 specifies slot 16 and the gc turns off singles, c20 runs the program for 20 cycles

  if you need to update the core, download the proper vpp package from
http://www.phys.ufl.edu/~madorsky/sp/
Line: 424 to 428
 Extract the headers to: $CSCTF/SPValidation/include/
Extract the cpp files to: $CSCTF/SPValidation/src/common/
Deleted:
<
<
if you need to update the PTLUTs, copy the files from the proper folder (ie: /home.local/csctf/ts1100/TriDAS/trigger/csctf/SPLUTsAndFirmWare/LUTs/bin/cmssw_latest_version) to the $CSCTF/SPValidation/bin folder.

See the ./SPtester-u option to upload these lookup tables.

 

How to update TS at 904

Revision 662011-02-16 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 428 to 428
  See the ./SPtester-u option to upload these lookup tables.
Added:
>
>

How to update TS at 904

(1) Edit the version number of TS in the repo:
sudo vim /etc/yum.repos.d/ts.repo
(2) Remove the old software:
sudo yum groupremove "triggersupervisor"
(3) Install the new copy:
sudo yum groupinstall "triggersupervisor"
(4) Verify the new installation:
rpm -qa | grep trigger
(5) Erase the old rpm:
ie: sudo rpm -e trigger-csctf-1.10.0-1.cmsos10.slc4
(6) Make changes necessary in the TS release notes (usually provided by Marc/TS people):
ie: for TS 10->11 we have to remove functions "ending()" in MTCCIIConfiguation.cc and make changes to Cell.cc for CellOperationFactory
(7) Edit version number in the Makefile:
vim $CSCTF/../setup/csctf
(8) Make the rpm:
make rpm
(9) Remove the old RPM (in this case version 10):
rm rpm/trigger-csctf-1.10.0-1.cmsos10.slc4.i386.rpm
(10) Check to see if there are any other packages that need an update:
sudo yum update
(11) Install new rpm:
./reinstall.sh
(12) make new code and restart cell:
cd $CSCTF
make clean
make
sudo /sbin/service xdaqd restart

 

General CSCTF Troubleshooting

Out of Sync in Link Masking Panel

Revision 652011-02-14 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 681 to 681
 
  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
Changed:
<
<
    • Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting.
>
>
    • (When Darin/Ivan are at CERN) Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting.
 
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.
    • Prepare pager report for the last week.
    • To run meeting.
Added:
>
>
    • Also Attend the Daily CSC Operations Meetings at 18:00 pm and prepare/present a 10 minute talk for the L1 DPG Meeting Wednesday at 18:00
 
    • It is recommended to all CSCTF experts (Laria, Matt and Anna) attend each CSCTF meeting if possible.

If you have any question, proposal or need help, please contact to Anna Kropivnitskaya

Revision 642011-02-11 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 418 to 418
 cd test make bin
Changed:
<
<
if you need to update the core, download the proper tar from
>
>
if you need to update the core, download the proper vpp package from
 http://www.phys.ufl.edu/~madorsky/sp/
Changed:
<
<
Untar the headers to: $CSCTF/SPValidation/include/
Untar the cpp files to: $CSCTF/SPValidation/src/common/
>
>
Extract the headers to: $CSCTF/SPValidation/include/
Extract the cpp files to: $CSCTF/SPValidation/src/common/
  if you need to update the PTLUTs, copy the files from the proper folder (ie: /home.local/csctf/ts1100/TriDAS/trigger/csctf/SPLUTsAndFirmWare/LUTs/bin/cmssw_latest_version) to the $CSCTF/SPValidation/bin folder.

Revision 632011-02-11 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"

General Information

Added:
>
>
For a thorough overview of the CSCTF, please consult Commissioning of the CSC Track Finder
 

Logging in to P5

All the actions described below require as first operation to log into the csc-tf machine and change from your user to csctfts user (you need to be granted the right to do so).

Line: 402 to 404
  the output will be saved in a file called output. Look through it and find the leaks that are definitely/indirectly lost, as valgrind will give you the line numbers of the offending memory leaks.
Added:
>
>

How To Run The SPTester Tool

First, for more information about how these programs were written please consult:
Control Software for the CSC Track Finder

The SPTester tool is a validation programs that tests an SP's functionality by filling its registers with random input values and then reading the SP's output registers for proper content.

To compile it:

cd SPValidation make cd test make bin

if you need to update the core, download the proper tar from
http://www.phys.ufl.edu/~madorsky/sp/

Untar the headers to: $CSCTF/SPValidation/include/
Untar the cpp files to: $CSCTF/SPValidation/src/common/

if you need to update the PTLUTs, copy the files from the proper folder (ie: /home.local/csctf/ts1100/TriDAS/trigger/csctf/SPLUTsAndFirmWare/LUTs/bin/cmssw_latest_version) to the $CSCTF/SPValidation/bin folder.

See the ./SPtester-u option to upload these lookup tables.

 

General CSCTF Troubleshooting

Revision 622011-02-08 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 101 to 101
 to the folder:


Changed:
<
<
$CSCTF/TrigData/TrackFinderCrate/SectorProcessor2002/firmware/
>
>
cd $CSCTF/TrigData/TrackFinderCrate/SectorProcessor2002/firmware/ wget http://link
 

CSCTF SPs have two firmware kind:

Line: 201 to 202
 cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/904
Changed:
<
<
Test the LUTs are correctly loaded:
>
>
Test the LUTs are correctly loaded modify crateRunCRC before using:
 emacs $CSCTF/SPLUTsAndFirmWare//test/crateRunCRC.cpp 
the line to modify is
std::string vers = "your_folder"; 

compile:

cd $CSCTF/SPLUTsAndFirmWare && make && cd test && make bin 

and test it:

 
  
cd $CSCTF/SPLUTsAndFirmWare/bin
./crateRunCRC
Deleted:
<
<
Modify crateRunCRC before using:
 emacs ../test/crateRunCRC.cpp 
the line to modify is
std::string vers = "your_folder"; 
 
Changed:
<
<
Compile:
>
>
Change information about new LUTs in configuration key:
 

Changed:
<
<
cd $CSCTF/SPLUTsAndFirmWare && make && cd test && make bin
>
>
emacs $CSCTF/ts/scripts/newMezzanine/904/dbSPadd_grun.sh
 
Added:
>
>
Line to modify:
 LUT_ROOT="bin/your_folder/"; 
and:
 PTLUT_VERSION='new_version'; 

Inform Gian Piero (gian.piero.di.giovanni@cernSPAMNOTNOSPAMPLEASE.ch) about "new_version" of PTLUTs and provide him dat-format of PTLUTs or ask expert (Anna: kropiv@cernSPAMNOTNOSPAMPLEASE.ch) to do it. Gian Piero will deliver it to O2O.

 Prepare a new configuration key...

When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.

Revision 612011-02-05 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"

Revision 602011-02-05 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 198 to 198
 The executable will dump some *.dat files which will be used in the configuration process to check the LUTs are properly loaded in the SPs. These files will be indeed have to be put in the database when you create a configuration key. IF THE DAT FILE FOR A SPECIFIC KEY IN THE DBS WON'T MATCH THE ONE DUMPED FROM THE SCRIPT THE CONFIGURATION OF THE SPs WILL FAIL!


Changed:
<
<
cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/904/SP*.dat
>
>
cp $CSCTF/SPLUTsAndFirmWare/LUTs/bin/your_folder/monitorData/*.dat $CSCTF/ts/scripts/newMezzanine/904
 

Test the LUTs are correctly loaded:

Revision 592011-02-04 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 364 to 364
 let Vasile know.
Put Ivan and Darin in cc as well.
Added:
>
>
If it is urgent, after doing above:

- the DPG/POG coordinator or reco contact (Vasile.Mihai.Ghete)
- the L2 reconstruction coordinators (Jean-Roch.Vlimant, and David.Lange)
- the release manager (me for 3.11.x, andrea.bocci, Shahzad.Malik.Muzaffar and Adeel.Adeel-Ur-Rehman for 4.2.x)

 

How to Run Valgrind To Check For Memory Leaks

To get information about the cell profile:

Revision 582011-02-01 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 30 to 30
 
  • SP1->SP12: 890->901
  • TF DDU:760 (to be double checked)
Deleted:
<
<
List of web pages:
 

Relevant Web Pages for 904

Calendar To Book Your working Time Slot: http://www.google.com/calendar/embed?src=vkkpfe7oatq38kbs6gm3isb7nk%40group.calendar.google.com&ctz=Europe/Zurich
Line: 185 to 171
  N.B.: whenever a new key is created, it is important to keep the csctf web site updated; to do so you can use the CERN webservices web site.
Added:
>
>
You can check the key/register values when you are finished here
 

How To Load LUTs

N.B.: In this example I will be using LUTs which are in *.bin version.

Line: 661 to 649
  Please note: to use CSCTF CERN car your name has to be in car documents.
Added:
>
>

Relevant Websites

List of web pages:

 -- GianPieroDiGiovanni - 08-Mar-2010 /s

Revision 572011-01-28 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 384 to 384
  at 904:
Changed:
<
<
sudo /sbin/service xdaqd stop csctf-cell
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes /opt/xdaq/bin/xdaq.exe -z $XDAQ_ZONE -e /opt/xdaq/share/csctf/profile/csctf-cell.profile -c /opt/xdaq/share/csctf/profile/csctf.configure -p 2974 -h emulab03.cern.ch ps aux
>
>
sudo /sbin/service xdaqd stop csctf-cell
script output
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes /opt/xdaq/bin/xdaq.exe -z $XDAQ_ZONE -e /opt/xdaq/share/csctf/profile/csctf-cell.profile -c /opt/xdaq/share/csctf/profile/csctf.configure -p 2974 -h emulab03.cern.ch
exit

the output will be saved in a file called output. Look through it and find the leaks that are definitely/indirectly lost, as valgrind will give you the line numbers of the offending memory leaks.

 

General CSCTF Troubleshooting

Revision 562011-01-27 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 376 to 376
 let Vasile know.
Put Ivan and Darin in cc as well.
Added:
>
>

How to Run Valgrind To Check For Memory Leaks

To get information about the cell profile:

ps aux | grep csctf-cell

at 904:

sudo /sbin/service xdaqd stop csctf-cell
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes /opt/xdaq/bin/xdaq.exe -z $XDAQ_ZONE -e /opt/xdaq/share/csctf/profile/csctf-cell.profile -c /opt/xdaq/share/csctf/profile/csctf.configure -p 2974 -h emulab03.cern.ch ps aux

 

General CSCTF Troubleshooting

Revision 552011-01-25 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 30 to 30
 
  • SP1->SP12: 890->901
  • TF DDU:760 (to be double checked)
Deleted:
<
<

Relevant Web Pages for P5

To access the web page at P5 you need to open a tunnel to P5.

Prerequisite to visualize the web pages after having open the tunnel is to download the cms.pac into your browser.

Howto on Firefox:

  • go to Edit -> Preferences -> Advanced -> Connection Settings -> Select "Automatic proxy configuration URL" and give the location of your pac file, e.g. file:///home/username/cms.pac

Commands to open a tunnel:
  • From the internal CERN network: ssh -ND 1080 username@cmsusrX, X=0,1
  • From outside the CERN network: ssh -t username@lxplus.cern.ch -L 1080:localhost:1081 "ssh -D 1081 username@cmsusr1.cern.ch"

If you have problem with upper tunnel (some site below are not reachable) then use another pac file cms_proxy.pac and the following command for tunnel:

  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr1

For more information on tunnelling, or to tunnel with windows using Putty, see: https://twiki.cern.ch/twiki/bin/view/XdaqWiki/SOCKSTunneling

 List of web pages:
Line: 70 to 51
 
Deleted:
<
<
 

How Tos

Added:
>
>

How to tunnel to P5

On Linux/Mac:

To access the web page at P5 you need to open a tunnel to P5.

Prerequisite to visualize the web pages after having open the tunnel is to download the cms.pac into your browser.

Howto on Firefox:

  • go to Edit -> Preferences -> Advanced -> Connection Settings -> Select "Automatic proxy configuration URL" and give the location of your pac file, e.g. file:///home/username/cms.pac

Commands to open a tunnel:
  • From the internal CERN network: ssh -ND 1080 username@cmsusrX, X=0,1
  • From outside the CERN network: ssh -t username@lxplus.cern.ch -L 1080:localhost:1081 "ssh -D 1081 username@cmsusr1.cern.ch"

If you have problem with upper tunnel (some site below are not reachable) then use another pac file cms_proxy.pac and the following command for tunnel:

  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr1

On Windows:

download and run Putty.

Create New Sesstion to "lxplus5.cern.ch" port 22

Connection->SSH->Tunnels

Enter "50000" in the "Source port" text field, "cmsusr0.cern.ch:22" in the "Destination" text field. Make sure the "Local" and "Auto" radio buttons are enabled and click the "Add" button

Save Session With Name "Tunnel 1"

Create New Sesstion to "madfish@localhost" port 50000

Connection->SSH->Tunnels

Enter "9999" in the "Source port" text field and enable the "Dynamic" radio button. Make sure the "Auto" radio button is enabled and click the "Add" button.

Save Session With Name "Tunnel 2"

Connect to Tunnel 1 then to Tunnel 2

Configure Firefox by:

(1) Download cms_proxy.pac to C:
(2) Open Firefox and go to Tools->Options->Advanced->Network->Settings
(3) Check radio button for Automatic Proxy Configuration URL and Enter: file:///c:/cms_proxy.pac

For more information on tunnelling, see:

https://twiki.cern.ch/twiki/bin/view/XdaqWiki/SOCKSTunneling

 

How to Load Firmware

Copy file from the Lev Uvarov's page:

Line: 321 to 355
  see here for latest procedure: https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideDevelopersGuide
Changed:
<
<
cd CMSSW_3_8_3 (for example) cd MySubsystem/MyPackage cvs status -v BuildFile to see the list of tags cvs tag Vxx-yy-zz . Compared with the previous tag you should increase, the zz number for patches, the yy number for a feature addition, the xx number for a (backward incompatible) change in interface. For small changes just add 1 to whatever zz is. cvs commit -m "List Updates Here"
>
>
to see a list of files that have changed since the last commit do: cvs -nq up
when you are ready to commit: cvs commit -m "List Updates Here" PathToFileNameOrDirectory
to see the list of tags: cvs status -v FileName | grep V
when you are ready to tag your new release (so it is used in the next CMSSW Cycle do:
 
Changed:
<
<
let Vasile know. Put Ivan and Darin in cc as well.
>
>
cvs tag Vxx-yy-zz

Compared with the previous tag you should increase, the zz number for patches, the yy number for a feature addition, the xx number for a (backward incompatible) change in interface. For small changes just add 1 to whatever zz is.

to delete tag: cvs -d tagname

to test the tag: cvs co -r Vxx-yy-zz MySubsystem/MyPackage

 
Changed:
<
<
to test the tag: cvs co -r Vxx-yy-zz ~MySubsystem/MyPackage to delete tag: cvs -d tagname
>
>
When you are ready and happy with the new tag, do the following:

  • Go to the CmsTC
  • Go to Package Publication that is on the left menu bar , and fill the line with MySubsystem/MyPackage Vxx-yy-zz. Tick the radio button corresponding to the releases for which you want to submit the new tag.

let Vasile know.
Put Ivan and Darin in cc as well.

 

General CSCTF Troubleshooting

Revision 542011-01-25 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 47 to 47
 If you have problem with upper tunnel (some site below are not reachable) then use another pac file cms_proxy.pac and the following command for tunnel:
  • ssh -t -L 9999:localhost:11010 lxplus.cern.ch ssh -ND 11010 cmsusr1
Added:
>
>
For more information on tunnelling, or to tunnel with windows using Putty, see: https://twiki.cern.ch/twiki/bin/view/XdaqWiki/SOCKSTunneling
  List of web pages:

Revision 532011-01-24 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 266 to 266
 cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s16 -cSP -mMA -rCSR_PFD -pW -v0x40 cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s16 -cFA -mMA -rCSR_PFD -pW -v0x40
Added:
>
>
You can convert the text dump into the raw format with vme2ddu.cc: http://isscvs.cern.ch/cgi-bin/cvsweb.cgi/TriDAS/emu/emuDQM/EmuTFMonitor/test/common/vme2ddu.cpp?rev=1.2;cvsroot=tridas

You can then read the raw files and unpack it in CMSSW using for example:

  1. ) checkout from cvs EventFilter/CSCTFRawToDigi & IORawData/CSCCommissioning

  1. ) change RUI00 source following file:

EventFilter/CSCTFRawToDigi/test/analyzer.py to path to the newly converted raw file.

  1. ) Run analyzer.py

 

How to Read/Write register values

To look at the register configuration

Revision 522011-01-24 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 301 to 301
  sudo /sbin/service triggerd restart csctf-cell
Added:
>
>

How to Update CMSSW Files to deploy at P5

see here for latest procedure: https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideDevelopersGuide

cd CMSSW_3_8_3 (for example) cd MySubsystem/MyPackage cvs status -v BuildFile to see the list of tags cvs tag Vxx-yy-zz . Compared with the previous tag you should increase, the zz number for patches, the yy number for a feature addition, the xx number for a (backward incompatible) change in interface. For small changes just add 1 to whatever zz is. cvs commit -m "List Updates Here"

let Vasile know. Put Ivan and Darin in cc as well.

to test the tag: cvs co -r Vxx-yy-zz ~MySubsystem/MyPackage to delete tag: cvs -d tagname

 

General CSCTF Troubleshooting

Out of Sync in Link Masking Panel

Revision 512011-01-19 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 276 to 276
 Read from DD/MA/CSR_DFC : 0xfff
Added:
>
>

How to Make/Test RPM at P5 (for TriDAS/trigger/setup/l1ts)

ssh cmsusr1

ssh l1ts-csctf

sudo rpm -ev trigger-l1ts

#now change to csctfts user

cd $BUILD_HOME/trigger/setup/l1ts

make rpm

#now change to your username

su username

cd rpm

sudo rpm -iv trigger-l1ts-xyz.rpm

sudo /sbin/service triggerd restart csctf-cell

 

General CSCTF Troubleshooting

Out of Sync in Link Masking Panel

Revision 502010-12-16 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 67 to 67
 http://www.google.com/calendar/embed?src=vkkpfe7oatq38kbs6gm3isb7nk%40group.calendar.google.com&ctz=Europe/Zurich If you wish to be added to the Calendar, please send Gregory.Rakness (at cern.ch) your gmail account username.
Deleted:
<
<
See link:

 
Line: 94 to 90
  The script to load the firmware is $CSCTF/SPLUTsAndFirmWare/scripts/loadFirmware.sh; it is actually a bash script. Open it and change the options inside to point to the right files. There are 2 blocks: the first for "chain 1" firmware and the second one for "chain 0". If you load chain 0 fw, the chain 1 block should be all commented out (and viceversa).
Changed:
<
<
Example of fw loading in SP 6 (slot 11):
  • ./loadFirmware.sh 11
>
>
Example of fw loading in SP 7 (slot 16):
  • ./loadFirmware.sh 16
  After loading new firmware we have to change version of firmware at file:

Line: 117 to 113
 sudo /sbin/service xdaqd restart csctf-cell
Added:
>
>
Now you will most likely need to create a new configuration key that can be used with the new firmware.
 

How to Create a Configuration Key

Added:
>
>
A configuration key is a set of values assigned to the various registers in the SP. You should create a new configuration key for each version of the SP firmware released and any time you decide that a new register value is more beneficial than a previous one (e.g. timing improvements, tuning parameters based on physics studies, etc).
 The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904

The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309

Line: 261 to 261
  At 904 we have 4 SP: SP2, SP4, SP7 and SP9.
Added:
>
>
if you notice that there are no LCTs in the data, you should change the Pipeline FIFO Delay register such that the VME is in sync. You can play with the values, but 0x43 is the default for Point 5 and 0x40 currently works nicely at 904:

cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s16 -cSP -mMA -rCSR_PFD -pW -v0x40 cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s16 -cFA -mMA -rCSR_PFD -pW -v0x40

 

How to Read/Write register values

To look at the register configuration

Revision 492010-12-15 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 275 to 275
 

Out of Sync in Link Masking Panel

Changed:
<
<
At 904, if the CSCTF shows up "Out of Sync" in the link masking panel, and you notice that the Muon1, Muon2, Muon3 lights are not blinking on the TMB, you need to do some extra steps to configure the system.
>
>
At 904, if the CSCTF shows up "Out of Sync" in the link masking panel, and you notice that the FED lights are not on, or the Muon1, Muon2, Muon3 lights are not blinking on the TMB, you need to do some extra steps to configure the system.
  Step 1:
Changed:
<
<
Add the configurations Comissioning/startPCrate and Commissioning/startTTC in the 904 RCMS
>
>
Destroy all configurations in the 904 RCMS. If the most of the FED lights are on skip to Step 3. If they are off: Add the configurations Commissioning/startFED and proceed to Step 2.
  Step 2:
Changed:
<
<
Go to the Yellow Page and click the button Write FLASH All Crates
>
>
Initialize the startFED and configure. Once it is configured you should check the FED crate and see that its many lights turn on. You should now destroy the startFED configuration process.
  Step 3:
Added:
>
>
add Comissioning/startPCrate and Commissioning/startTTC in the 904 RCMS configuration manager. Initialize them both!

Step 4: Go to the Yellow Page and click the button Write FLASH All Crates. This will not be available unless the processes were initialized in the previous step.

Step 5:

 Go to the TTCi Page and click "Configure"
Changed:
<
<
Go to the LTC Page and click "Configure" then "Halt" then "HardReset" then "Resync."
>
>
Go to the LTC Page and click "Configure" then "Halt" then "HardReset" then "Resync" and "Enable."

Step 6: Check to see that the MPC, MS, SP and TMB LEDs blink synchronously with high voltage and gas on (if not, go back and check the previous steps/power cycle everything and try again). If they do, you may destroy all the processes you have created in this procedure and everything should configure and work as normal.

 

EEPROM CORRUPTIONS

Line: 531 to 540
  Please note: to use CSCTF CERN car your name has to be in car documents.

-- GianPieroDiGiovanni - 08-Mar-2010

Added:
>
>
/s
 
META FILEATTACHMENT attachment="gdbCommands" attr="" comment="gdb commands" date="1249921346" name="gdbCommands" path="gdbCommands" size="45" stream="gdbCommands" user="Main.GianPieroDiGiovanni" version="1"
META FILEATTACHMENT attachment="hotspot.xml" attr="" comment="" date="1274268368" name="hotspot.xml" path="hotspot.xml" size="30" stream="hotspot.xml" tmpFilename="/usr/tmp/CGItemp43723" user="kkotov_40phys_2eufl_2eedu" version="1"

Revision 482010-12-15 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 76 to 76
 

How Tos

Changed:
<
<

Firmware Loading

>
>

How to Load Firmware

  Copy file from the Lev Uvarov's page: http://www.phys.ufl.edu/~uvarov/SP05/SP05.htm
Line: 117 to 117
 sudo /sbin/service xdaqd restart csctf-cell
Changed:
<
<

LUTs Loading

>
>

How to Create a Configuration Key

The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904

The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309

This script simply calls other scripts to perform the key writing on the database.

The files to change before writing the new key according to the change you want perform are in the same folder:

  • firmwareVersions -> if you updated the firmware version of SP, CCB or MS
  • SP$i.dat, $i=1,2,...,12 -> if you updated new LUTs
    (you should get these from the MONITOR files in $CSCTF/SPLUTsAndFirmWare/LUTs/bin/cmssw_x_x_x/monitorData/ and overwrite accordingly: ie SP7_cmssw_3_6_3_MonitorData.dat would become SP7.dat)
  • static2_config.txt -> if you modify any register for static configuration
  • timing2_config.txt -> if you modify any register for timing configuration
  • eta2_config.txt -> if you modify any register for eta cuts configuration

When you created new Key you have to:

  • upload new information about keys at OnlineWBTrigger: go Main Trigger Page -> Documentation -> Online Workbook -> Updated version of OnlineWBL1TriggerKeys...
  • upload new information at CSC and Trigger elog
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
  • call Jinghua Liu (165930) to change comics key at RCMS
  • modify CSCTF Adjustments (what was changed at P5): https://twiki.cern.ch/twiki/bin/viewauth/CMS/CSCTrigger2010
  • modify cosmics key at $CSCTF/ts/worker/src/common/MTCCIIConfiguration.cc, compile at $CSCTF and restart csctf-cell:
cd $CSCTF && make clean && make
sudo /sbin/service triggerd restart csctf-cell 

N.B.: whenever a new key is created, it is important to keep the csctf web site updated; to do so you can use the CERN webservices web site.

How To Load LUTs

  N.B.: In this example I will be using LUTs which are in *.bin version.
Line: 164 to 197
  When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.
Changed:
<
<

Crate Configuration Key

The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904

The main script is insertkeys.sh. As parameter you need to pass a name for the key. The CSCTF convention is to use the day when we perform the upgrade, e.g., 310309 == 31st March 2009 => ./insertkeys.sh 310309

This script simply calls other scripts to perform the key writing on the database.

The files to change before writing the new key according to the change you want perform are in the same folder:

  • firmwareVersions -> if you updated the firmware version of SP, CCB or MS
  • SP$i.dat, $i=1,2,...,12 -> if you updated new LUTs
    (you should get these from the MONITOR files in $CSCTF/SPLUTsAndFirmWare/LUTs/bin/cmssw_x_x_x/monitorData/ and overwrite accordingly: ie SP7_cmssw_3_6_3_MonitorData.dat would become SP7.dat)
  • static2_config.txt -> if you modify any register for static configuration
  • timing2_config.txt -> if you modify any register for timing configuration
  • eta2_config.txt -> if you modify any register for eta cuts configuration

When you created new Key you have to:

  • upload new information about keys at OnlineWBTrigger: go Main Trigger Page -> Documentation -> Online Workbook -> Updated version of OnlineWBL1TriggerKeys...
  • upload new information at CSC and Trigger elog
  • call the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
  • call Jinghua Liu (165930) to change comics key at RCMS
  • modify CSCTF Adjustments (what was changed at P5): https://twiki.cern.ch/twiki/bin/viewauth/CMS/CSCTrigger2010
  • modify cosmics key at $CSCTF/ts/worker/src/common/MTCCIIConfiguration.cc, compile at $CSCTF and restart csctf-cell:
cd $CSCTF && make clean && make
sudo /sbin/service triggerd restart csctf-cell 

N.B.: whenever a new key is created, it is fundamental to keep the csctf web site updated; to do so you can use the CERN webservices web site.

Check How Many file descriptors are open by the csctf-cell

>
>

How to Check How Many file descriptors are open by the csctf-cell

  From vmepcS2G18-10 connected with your username (do not switch to csctfts as you need sudo right) type
  • ps aux | grep "csctf-cell\.profile" | awk '{print "sudo ls /proc/"$2"/fd | wc -l"}'
Line: 224 to 224
 
    • start local run with proper key and check that everything works fine.
    • try to stop and start new local run. You need it just to check that stop/start procedure works fine.
Added:
>
>

How to check CSCTF Logs

AT 904:

Configuration log:

tail -f $CSCTF/localConditions/localConditions.log

Out of Sync Errors and General Hardware Errors log:

/var/log/csctf-cell.log

AT P5:

Out of Sync Errors and General Hardware Errors log:

https://twiki.cern.ch/twiki/bin/viewauth/CMS/HowToReadTheLogsOnlineAndOffline

 

How to take data at 904

See Links:

Revision 472010-12-15 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Changed:
<
<

Basic Actions

>
>

General Information

Logging in to P5

  All the actions described below require as first operation to log into the csc-tf machine and change from your user to csctfts user (you need to be granted the right to do so).
Line: 70 to 72
 

Changed:
<
<

Firmware Loading

>
>

How Tos

Firmware Loading

  Copy file from the Lev Uvarov's page: http://www.phys.ufl.edu/~uvarov/SP05/SP05.htm
Line: 111 to 117
 sudo /sbin/service xdaqd restart csctf-cell
Changed:
<
<

LUTs Loading

>
>

LUTs Loading

  N.B.: In this example I will be using LUTs which are in *.bin version.
Line: 158 to 164
  When configuring the first time perform heavy check on LUTs by checking the Force_Configure check box.
Changed:
<
<

Crate Configuration Key

>
>

Crate Configuration Key

  The scripts to create a #ConfKeyAnchor configuration key are located in $CSCTF/ts/scripts/newMezzanine/904
Line: 191 to 197
  N.B.: whenever a new key is created, it is fundamental to keep the csctf web site updated; to do so you can use the CERN webservices web site.
Changed:
<
<

Crate Masking

>
>

Check How Many file descriptors are open by the csctf-cell

 
Changed:
<
<

Trigger Supervisor Problems

>
>
From vmepcS2G18-10 connected with your username (do not switch to csctfts as you need sudo right) type
  • ps aux | grep "csctf-cell\.profile" | awk '{print "sudo ls /proc/"$2"/fd | wc -l"}'
 
Changed:
<
<

Basic Checks

Where to web-monitor the csctf-cell:
>
>
If more than one line appears it means there is more than one csctf-cell process. This is bad. Investigate the reason or, if you are in panic mode, kill all the process and restart the cell via sudo /sbin/service triggerd restart csctf-cell.
 
Changed:
<
<
If everything works fine you can access the web pages above and surf into it, plus see a green light in the main trigger web page.
>
>
If one line appears, everything is good. Paste the output command in your shell. Press enter. Check the results.
 
Added:
>
>
NOTE: file descriptors should not grow much. If they do most likely there are files open and never closed. Find them out and fix the bug(s). The upper limit is 1024 fd per process. If the quota is exceeded this will cause the csctf-cell to hang and you will get paged...
 
Changed:
<
<
How to monitor the csctf-cell status on csc-tf machine:
  • Log into csc-tf machine without switching to csctfts user:
    • > whoami
      digiovan
>
>

How to change Sector Processor (SP)

 
Changed:
<
<
  • then type:
    • > sudo /sbin/service triggerd status
>
>
  • Take a new SP at 904: switch of power and only after it extract SP from crate; don't forget to switch on power after extraction
 
Changed:
<
<
The output will be
 
Status of XDAQ service 'csctf-tstore':                     [  OK  ]
Status of XDAQ service 'csctf-ws-eventing':                [  OK  ]
Status of XDAQ service 'csctf-las':                        [  OK  ]
Status of XDAQ service 'csctf-pulser':                     [  OK  ]
Status of XDAQ service 'csctf-sensor':                     [  OK  ]
Status of XDAQ service 'xdaq-jc':                          [  OK  ]
Status of XDAQ service 'csctf-cell':                       [  OK  ]
Status of XDAQ service 'csctf-spotlight':                  [  OK  ]
>
>
  • Bring SP to Point 5:
    • swith of power
    • disconnect all cables from broken SP (maybe you need to disconnect extra cables from other SPs to extract broken SP). Before disconnecting cables check correct hardware mapping: mapping.
    • extract broken SP and put a new one. Connect cables with mapping.
    • during switch of power we could loose our firmware. Check firmware with EEPROM CORRUPTIONS. If you have errors download firmware to problematic SPs.
    • check that all links (cables are connected propely) with ....
    • check LUTs with ...
    • restart CELL
    • reconfigure CSCTF
    • start local run with proper key and check that everything works fine.
    • try to stop and start new local run. You need it just to check that stop/start procedure works fine.
 
Changed:
<
<
If the cell crashed your output will report:
Status of XDAQ service 'csctf-cell':                       [Failed]
>
>

How to take data at 904

 
Added:
>
>
See Links:
 
Changed:
<
<
How to restart the csctf-cell:
  • > sudo /sbin/service triggerd restart csctf-cell
>
>
https://twiki.cern.ch/twiki/bin/view/CMS/CSCOperations#Local_Runs
 
Added:
>
>
https://twiki.cern.ch/twiki/bin/view/CMS/CSCCosmicSlice#Running_the_System_from_RCMS
 
Changed:
<
<
Debugging the problem:
>
>
RCMS at B904: http://emuslice02:12000/rcms/gui/servlet/RunningConfigurationServlet
 
Added:
>
>
To take data (VME Dump) you have to run the following program with SP Slot = 16
cd $CSCTF/SPFunctions/bin && ./takeVMEData 16
 
Changed:
<
<
The reasons of a cell crash can be several. In general, it is useful to debug further using gdb, although it could have happened occasionally:
>
>
you will get DAQ_data_out.dat with data to analyze.
 
Changed:
<
<
  • Identify the PID in the core looking in /tmp/core.PID
  • run gdb:
    • sudo gdb /opt/xdaq/bin/xdaq.exe /tmp/core.PID
    • thread apply all bt full
>
>
At 904 we have 4 SP: SP2, SP4, SP7 and SP9.
 
Changed:
<
<
P.S.: even better is to run this command from emacs after launching gdb with M-x gdb; you will have the output saved in a file without copying and been able to use the emacs tool to surf the output
>
>

How to Read/Write register values

To look at the register configuration
cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s18 -cDD -mMA -rCSR_DFC
you will get something like this:
Read from DD/MA/CSR_DFC : 0xfff
 
Added:
>
>

General CSCTF Troubleshooting

 
Changed:
<
<
Links on how to use gdb are:
>
>

Out of Sync in Link Masking Panel

 
Added:
>
>
At 904, if the CSCTF shows up "Out of Sync" in the link masking panel, and you notice that the Muon1, Muon2, Muon3 lights are not blinking on the TMB, you need to do some extra steps to configure the system.
 
Changed:
<
<

How to Dump The GDB Output Into A File

>
>
Step 1: Add the configurations Comissioning/startPCrate and Commissioning/startTTC in the 904 RCMS
 
Changed:
<
<
sudo gdb /opt/xdaq/bin/xdaq.exe /tmp/core.10484 -x gdbCommands -batch >> outputFile
>
>
Step 2: Go to the Yellow Page and click the button Write FLASH All Crates
 
Changed:
<
<
gdbCommands file contains the list of commands we want gdb to execute. In our case:
  • set height 0 [This command removes the gdb command ---Type to continue, or q to quit---]
  • thread apply all backtrace full
>
>
Step 3: Go to the TTCi Page and click "Configure" Go to the LTC Page and click "Configure" then "Halt" then "HardReset" then "Resync."
 
Changed:
<
<
NB: If something interesting or not understood is found from the debug, please post it as savannah bug since you need to tell the responsible for the Trigger Supervisor (TS) framework (Marc Magrans De Abril)
>
>

EEPROM CORRUPTIONS

 
Changed:
<
<

How to Attach GDB To A Running Executable

>
>
  • SYMPTOMS: so far they occurred or identified only after the crate is restarted from being off (e.g., cooling issue, shutdown, etc). The synptoms is the board not getting configured. Issue the configuration command from the TS gui and monitor the file localConditions/localConditions.log. Whenever the CSCTF does not have a board configured, it is the first check performed.
 
Changed:
<
<
Example with the csctf-cell running on the l1ts-csctf machine and listening to port 2974:
  • ssh l1ts-csctf
  • pgrep -f "xdaq.*2974" e.g., you get =5283
  • sudo gdb
  • handle SIG33 nostop noprint noignore pass
  • attach (in our example one should type "attach 5283")
  • thread apply all bt full
  • detach
>
>
  • DIAGNOSIS: from $CSCTF run the script misc/checkEEPROM.sh with argument the slot in the crate with the board you want to investigate, e.g. misc/checkEEPROM.sh 6 (for SP1).
 
Added:
>
>
You will get an output like:
 
Changed:
<
<

A Service Keeps FAILING After Restart Command

>
>
Read from SP/MA/CSR_CID : 0x99f6
 
Changed:
<
<
  • This problem is due to triggerd daemon. The latter does look in /var/run/ for the pid file corresponding to the service to kill. If it does not find it, it cannot kill so when restarting the port will be busy and the service does FAIL.
>
>
Read from VM/MA/CSR_CID : 0x9515
 
Changed:
<
<
  • How To Fix It (e.g. csctf-store keep FAILING):
    • stop the service: sudo /sbin/service triggerd stop csctf-store
    • check if the service is still up and running: ps aux | grep csctf-store. If an instance of it exist, this is the cause of your problem: KILL IT MANUALLY, "sudo kill jobid"
    • start the service again: sudo /sbin/service triggerd start csctf-store
>
>
Read from DD/MA/CSR_CID : 0x95d5
 
Changed:
<
<

>
>
Read from F1/MA/CSR_CID : 0x*****hardware access exception, FPGAobject::Read::Could not read from CAEN BusAdapter
unknown exception, not hardware access.. check addr path etc..
Read from F2/MA/CSR_CID : 0x9555
 
Changed:
<
<

Check How Many file descriptors are open by the csctf-cell

>
>
Read from F3/MA/CSR_CID : 0x9575
 
Changed:
<
<
From vmepcS2G18-10 connected with your username (do not switch to csctfts as you need sudo right) type
  • ps aux | grep "csctf-cell\.profile" | awk '{print "sudo ls /proc/"$2"/fd | wc -l"}'
>
>
Read from F4/MA/CSR_CID : 0x9595
 
Changed:
<
<
If more than one line appears it means there is more than one csctf-cell process. This is bad. Investigate the reason or, if you are in panic mode, kill all the process and restart the cell via sudo /sbin/service triggerd restart csctf-cell.
>
>
Read from F5/MA/CSR_CID : 0x95b5
 
Changed:
<
<
If one line appears, everything is good. Paste the output command in your shell. Press enter. Check the results.
>
>
At that point you know that the problematic chip is SP1/F1
 
Changed:
<
<
NOTE: file descriptors should not grow much. If they do most likely there are files open and never closed. Find them out and fix the bug(s). The upper limit is 1024 fd per process. If the quota is exceeded this will cause the csctf-cell to hang and you will get paged...
>
>
 
Changed:
<
<

CSCSummary Does NOT Update CSCTF Rates

>
>

CSCSummary Does NOT Update CSCTF Rates

  Where to web-monitor the CSCSummary:
Line: 353 to 350
 
Changed:
<
<

EEPROM CORRUPTIONS

>
>

Trigger Supervisor Troubleshooting

 
Changed:
<
<
  • SYMPTOMS: so far they occurred or identified only after the crate is restarted from being off (e.g., cooling issue, shutdown, etc). The synptoms is the board not getting configured. Issue the configuration command from the TS gui and monitor the file localConditions/localConditions.log. Whenever the CSCTF does not have a board configured, it is the first check performed.
>
>

Basic Checks

Where to web-monitor the csctf-cell:
 
Changed:
<
<
  • DIAGNOSIS: from $CSCTF run the script misc/checkEEPROM.sh with argument the slot in the crate with the board you want to investigate, e.g. misc/checkEEPROM.sh 6 (for SP1).
>
>
If everything works fine you can access the web pages above and surf into it, plus see a green light in the main trigger web page.
 
Deleted:
<
<
You will get an output like:
 
Changed:
<
<
Read from SP/MA/CSR_CID : 0x99f6
>
>
How to monitor the csctf-cell status on csc-tf machine:
  • Log into csc-tf machine without switching to csctfts user:
    • > whoami
      digiovan
 
Changed:
<
<
Read from VM/MA/CSR_CID : 0x9515
>
>
  • then type:
    • > sudo /sbin/service triggerd status
 
Changed:
<
<
Read from DD/MA/CSR_CID : 0x95d5
>
>
The output will be
 
Status of XDAQ service 'csctf-tstore':                     [  OK  ]
Status of XDAQ service 'csctf-ws-eventing':                [  OK  ]
Status of XDAQ service 'csctf-las':                        [  OK  ]
Status of XDAQ service 'csctf-pulser':                     [  OK  ]
Status of XDAQ service 'csctf-sensor':                     [  OK  ]
Status of XDAQ service 'xdaq-jc':                          [  OK  ]
Status of XDAQ service 'csctf-cell':                       [  OK  ]
Status of XDAQ service 'csctf-spotlight':                  [  OK  ]
 
Changed:
<
<
Read from F1/MA/CSR_CID : 0x*****hardware access exception, FPGAobject::Read::Could not read from CAEN BusAdapter
unknown exception, not hardware access.. check addr path etc..
Read from F2/MA/CSR_CID : 0x9555
>
>
If the cell crashed your output will report:
Status of XDAQ service 'csctf-cell':                       [Failed]
 
Deleted:
<
<
Read from F3/MA/CSR_CID : 0x9575
 
Changed:
<
<
Read from F4/MA/CSR_CID : 0x9595
>
>
How to restart the csctf-cell:
  • > sudo /sbin/service triggerd restart csctf-cell
 
Deleted:
<
<
Read from F5/MA/CSR_CID : 0x95b5
 
Changed:
<
<
At that point you know that the problematic chip is SP1/F1
>
>
Debugging the problem:
 
Deleted:
<
<
 
Changed:
<
<

How to change Sector Processor (SP)

>
>
The reasons of a cell crash can be several. In general, it is useful to debug further using gdb, although it could have happened occasionally:
 
Changed:
<
<
  • Take a new SP at 904: switch of power and only after it extract SP from crate; don't forget to switch on power after extraction
>
>
  • Identify the PID in the core looking in /tmp/core.PID
  • run gdb:
    • sudo gdb /opt/xdaq/bin/xdaq.exe /tmp/core.PID
    • thread apply all bt full
 
Changed:
<
<
  • Bring SP to Point 5:
    • swith of power
    • disconnect all cables from broken SP (maybe you need to disconnect extra cables from other SPs to extract broken SP). Before disconnecting cables check correct hardware mapping: mapping.
    • extract broken SP and put a new one. Connect cables with mapping.
    • during switch of power we could loose our firmware. Check firmware with EEPROM CORRUPTIONS. If you have errors download firmware to problematic SPs.
    • check that all links (cables are connected propely) with ....
    • check LUTs with ...
    • restart CELL
    • reconfigure CSCTF
    • start local run with proper key and check that everything works fine.
    • try to stop and start new local run. You need it just to check that stop/start procedure works fine.
>
>
P.S.: even better is to run this command from emacs after launching gdb with M-x gdb; you will have the output saved in a file without copying and been able to use the emacs tool to surf the output
 
Deleted:
<
<

How to take data at 904

 
Changed:
<
<
See Links:
>
>
Links on how to use gdb are:
 
Deleted:
<
<
https://twiki.cern.ch/twiki/bin/view/CMS/CSCOperations#Local_Runs
 
Changed:
<
<
https://twiki.cern.ch/twiki/bin/view/CMS/CSCCosmicSlice#Running_the_System_from_RCMS
>
>

How to Dump The GDB Output Into A File

 
Changed:
<
<
RCMS at B904: http://emuslice02:12000/rcms/gui/servlet/RunningConfigurationServlet
>
>
sudo gdb /opt/xdaq/bin/xdaq.exe /tmp/core.10484 -x gdbCommands -batch >> outputFile
 
Changed:
<
<
At 904 we have 4 SP: SP2, SP4, SP7 and SP9.
>
>
gdbCommands file contains the list of commands we want gdb to execute. In our case:
  • set height 0 [This command removes the gdb command ---Type to continue, or q to quit---]
  • thread apply all backtrace full
 
Changed:
<
<
To look at the register configuration
cd $CSCTF/SPStandAlones/bin && ./readwriteRegister -s18 -cDD -mMA -rCSR_DFC
you will get something like this:
Read from DD/MA/CSR_DFC : 0xfff
>
>
NB: If something interesting or not understood is found from the debug, please post it as savannah bug since you need to tell the responsible for the Trigger Supervisor (TS) framework (Marc Magrans De Abril)
 
Changed:
<
<
To take data you have to run the following program with SP Slot = 18
cd $CSCTF/SPFunctions/bin && ./takeVMEData 18
>
>

How to Attach GDB To A Running Executable

 
Changed:
<
<
you will get DAQ_data_out.dat with data to analyze.
>
>
Example with the csctf-cell running on the l1ts-csctf machine and listening to port 2974:
  • ssh l1ts-csctf
  • pgrep -f "xdaq.*2974" e.g., you get =5283
  • sudo gdb
  • handle SIG33 nostop noprint noignore pass
  • attach (in our example one should type "attach 5283")
  • thread apply all bt full
  • detach

A Service Keeps FAILING After Restart Command

  • This problem is due to triggerd daemon. The latter does look in /var/run/ for the pid file corresponding to the service to kill. If it does not find it, it cannot kill so when restarting the port will be busy and the service does FAIL.

  • How To Fix It (e.g. csctf-store keep FAILING):
    • stop the service: sudo /sbin/service triggerd stop csctf-store
    • check if the service is still up and running: ps aux | grep csctf-store. If an instance of it exist, this is the cause of your problem: KILL IT MANUALLY, "sudo kill jobid"
    • start the service again: sudo /sbin/service triggerd start csctf-store

Other Information

 
Changed:
<
<

Useful DBS Queries

>
>

Useful DBS Queries

  HISTORY:
Line: 454 to 473
 select a.RUNNUMBER, b.CSCTF_KEY, c.FIRMWARE from cms_wbm.RUNSUMMARY a, CMS_TRG_L1_CONF.TRIGGERSUP_CONF b, CMS_CSC_TF.CSCTF_SP_CONF c where (a.TSCKEY = b.TS_KEY and a.RUNNUMBER>132440 and c.SP_KEY=b.CSCTF_KEY || '0001') order by a.RUNNUMBER desc
Changed:
<
<

Extra help

>
>

Extra help

  To find 'something' in files in all directories:

Line: 468 to 487
 SPValidation/bin/TestSPconsole -s16
Changed:
<
<

Responsibility of pager expert

>
>

Responsibility of pager expert

 
  • Participation in the daily (even during weekends) CSC phone meeting at 18:00
Line: 485 to 504
  If you have any question, proposal or need help, please contact to Anna Kropivnitskaya
Changed:
<
<

CSCTF CERN car

>
>

CSCTF CERN car

  CSCTF group has a CERN car for CSCTF issues in period 12 August 2010 - 23 December 2010. The main contact person is Anna Kropivnitskaya. If you want to use it please contract to Anna to clarify if car is available to prevent any over crossing. Availability of CSCTF car you could find at

Revision 462010-12-14 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 405 to 405
  https://twiki.cern.ch/twiki/bin/view/CMS/CSCCosmicSlice#Running_the_System_from_RCMS
Added:
>
>
RCMS at B904: http://emuslice02:12000/rcms/gui/servlet/RunningConfigurationServlet

 At 904 we have 4 SP: SP2, SP4, SP7 and SP9.

To look at the register configuration

Revision 452010-12-06 - MattFisher

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 67 to 67
  See link:
Changed:
<
<
https://twiki.cern.ch/twiki/bin/view/CMS/CSCCosmicSlice#Running_the_System_from_RCMS
>
>
 

Firmware Loading

Line: 399 to 399
 

How to take data at 904

Added:
>
>
See Links:

https://twiki.cern.ch/twiki/bin/view/CMS/CSCOperations#Local_Runs

https://twiki.cern.ch/twiki/bin/view/CMS/CSCCosmicSlice#Running_the_System_from_RCMS

 At 904 we have 4 SP: SP2, SP4, SP7 and SP9.

To look at the register configuration

Revision 442010-11-14 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 441 to 441
 order by a.RUNNUMBER desc;
Added:
>
>
  • List of runs, CSCTF configuration keys and firmware
select a.RUNNUMBER, b.CSCTF_KEY, c.FIRMWARE from cms_wbm.RUNSUMMARY a, CMS_TRG_L1_CONF.TRIGGERSUP_CONF b, CMS_CSC_TF.CSCTF_SP_CONF c where (a.TSCKEY = b.TS_KEY and a.RUNNUMBER>132440 and c.SP_KEY=b.CSCTF_KEY || '0001') order by a.RUNNUMBER desc
 

Extra help

Revision 432010-09-17 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 180 to 180
 
  • upload new information about keys at OnlineWBTrigger: go Main Trigger Page -> Documentation -> Online Workbook -> Updated version of OnlineWBL1TriggerKeys...
  • upload new information at CSC and Trigger elog
Changed:
<
<
  • call to the Trigger Field Manager. The phone is available at Main Trigger Page -> Contacts
>
>
cd $CSCTF && make clean && make
sudo /sbin/service triggerd restart csctf-cell 
  N.B.: whenever a new key is created, it is fundamental to keep the csctf web site updated; to do so you can use the CERN webservices web site.

Revision 422010-09-07 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 426 to 426
 order by a.RUNNUMBER desc;
Added:
>
>
OR

select a.RUNNUMBER, b.CSCTF_KEY from cms_wbm.RUNSUMMARY a, CMS_TRG_L1_CONF.TRIGGERSUP_CONF b
where (a.TSCKEY = b.TS_KEY AND RUNNUMBER=132440)
order by a.RUNNUMBER desc;
 

Extra help

Revision 412010-08-19 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 435 to 435
 find . -type f -exec grep -H -n 'f/w verification failed' {} \;
Added:
>
>
Check status of Slot:

SPValidation/bin/TestSPconsole -s16
 

Responsibility of pager expert

Revision 402010-08-17 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 47 to 47
 

List of web pages:

Added:
>
>
 
Line: 57 to 58
 
Changed:
<
<
>
>
 

Relevant Web Pages for 904

Calendar To Book Your working Time Slot: http://www.google.com/calendar/embed?src=vkkpfe7oatq38kbs6gm3isb7nk%40group.calendar.google.com&ctz=Europe/Zurich

Revision 392010-08-17 - GianPieroDiGiovanni

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 23 to 23
 
  • MS is in Slot 14
  • SP 7->12 are in Slots 16->21

Added:
>
>

FED Numbering

  • SP1->SP12: 890->901
  • TF DDU:760 (to be double checked)
 

Relevant Web Pages for P5

To access the web page at P5 you need to open a tunnel to P5.

Revision 382010-08-13 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 431 to 431
 

Responsibility of pager expert

Added:
>
>
  • Participation in the daily (even during weekends) CSC phone meeting at 18:00
    • you have to be subscribe to hn-cms-csc-ops@cernNOSPAMPLEASE.ch. Every day it is announced phone meeting, sometimes it cancels.
    • phone meeting could be reachable at EVO -> CMS -> CMS Muon Operations

 
  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
Line: 442 to 446
  If you have any question, proposal or need help, please contact to Anna Kropivnitskaya

Added:
>
>

CSCTF CERN car

CSCTF group has a CERN car for CSCTF issues in period 12 August 2010 - 23 December 2010. The main contact person is Anna Kropivnitskaya. If you want to use it please contract to Anna to clarify if car is available to prevent any over crossing. Availability of CSCTF car you could find at Google Calendar for CSCTF CERN car

Please note: to use CSCTF CERN car your name has to be in car documents.

 -- GianPieroDiGiovanni - 08-Mar-2010

META FILEATTACHMENT attachment="gdbCommands" attr="" comment="gdb commands" date="1249921346" name="gdbCommands" path="gdbCommands" size="45" stream="gdbCommands" user="Main.GianPieroDiGiovanni" version="1"

Revision 372010-08-04 - AnnaKropivnitskaya

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 431 to 431
 

Responsibility of pager expert

Deleted:
<
<
CSCTF meeting
 
  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.

Revision 362010-08-04 - LariaRedjimi

Line: 1 to 1
 
META TOPICPARENT name="GianPieroDiGiovanni"
Line: 434 to 434
  CSCTF meeting

  • Organize CSCTF working meeting, which is running every Tuesday at 18:00:
Changed:
<
<
    • Create indigo page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
>
>
    • Create indico page at MUON - Muon Detector. Just select the last meeting in Indigo and create clone.
 
    • Create EVO with title CSCTF meeting and password which is sent in e-mail.
    • Make booking for a room at Room reservation. You have to find a room with "Video conference" and reserve it. It is better to do till Friday to have time to find free room for the meeting.
    • Send remind e-mail about meeting to the CSCTF e-mail list: csctf-working-meeting@cernNOSPAMPLEASE.ch. It is better to sent e-mail in 12-24 ours before starting meeting.