Hope that will work … Cheers, Martin

Calibration processing code

https://gitlab.cern.ch/atlas-l1calo/CalibrationProcessing

CPM Input scan

• taken from the calibration panel (few minutes) If there are errors about the CMX doesn't matter (becaue the CPM changes the clock). Results can be found in the crate (e.g. ccc02 in /logs/tdaq-06-01-01/L1CaloCalibration/results)

CP Run2

JeM Input scan

• again taken from calib pael. Same as befre fr CMX errors. Results from the L1Calo twiki, Calib --> Status --> and i can find the log file or the pdf with results. Red is the band forbidden. Blue bands are missing chanels

Calibration

• Silvia's twiki page with calibration stuffs: https://twiki.cern.ch/twiki/bin/view/Main/L1CaloCalibrationSilvia

Tile CIS

• Tile calibration updates link
• Tile calibration System (Arely Nov 17): https://indico.cern.ch/event/678290/contributions/2784913/attachments/1569370/2474819/TileCalibration_arelycg.pdf
• Tile calbration energy reconstruction: with RampMaker we use UPD4
• Tile laser scan results: http://pcata007.cern.ch/commissioning/level1/
• Mapping PMT to Trigger tower: http://hep.uchicago.edu/atlas/tilecal/level1/geometry.html

Sanya's instructions:

asetup 21.0.71,Athena
ReadCalibFromCool.py --folder=/TILE/OFL02/CALIB/LAS/LIN --module=LBA10
--chan=20 --gain=0 --pmt --begin=343000

TileCalibTools : INFO     Resolved globalTag 'CONDBR2-BLKPA-2018-06' to
folderTag 'TileOfl02CalibLasLin-RUN2-UPD4-16'

(341222,0)  LBA10 pm 21 ch 20 LG    0.944506  646.900024
(345808,0)  LBA10 pm 21 ch 20 LG    1.000000  -1.000000
(347606,0)  LBA10 pm 21 ch 20 LG    1.017112  646.900024
(348534,0)  LBA10 pm 21 ch 20 LG    1.013614  646.900024
(349137,0)  LBA10 pm 21 ch 20 LG    0.989601  646.900024
(349712,0)  LBA10 pm 21 ch 20 LG    0.968799  646.900024
(350144,0)  LBA10 pm 21 ch 20 LG    0.957218  646.900024

ReadCalibFromCool.py --folder=/TILE/OFL02/CALIB/LAS/LIN
--tag=CONDBR2-BLKPA-2018-03 --module=LBA10 --chan=20 --gain=0 --pmt
--begin=343000

TileCalibTools : INFO     Resolved globalTag 'CONDBR2-BLKPA-2018-03' to
folderTag 'TileOfl02CalibLasLin-RUN2-UPD4-16'

--folder=/TILE/OFL02/CALIB/CIS/LIN
--folder=/TILE/OFL02/CALIB/CES

--tag=UPD1   or --tag=UPD4

Check masked Tile channels

ReadBchFromCool.py --tag=UPD4 --module=LBC56 --chan=10 --pmt --begin=300000

ReadBchFromCool.py --module=LBC56 --pmt --begin=300000 | grep -v good

http://zenis.dnp.fmph.uniba.sk/tile.html

Receivers

https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloReceiversExpert

HV correction

https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloOnCallManual#Updating_Receiver_gains_and_LAr

Change receivers gains

• with the new sqlite file from juraj: (instruction here: /det/l1calo/doc) *Juraj provides files (update: from analysis authomatic, force: values put by hand because problematic channels). to be copied in

   /det/l1calo/coolData/gains

   cd /det/l1calo/coolData/gains

   ../../scripts/updateGains.sh updateLAr_mar16_v1.sqlite

• To revert or change some channel, go in P1, setup l1calo, ace, open DB, search for receiver folder and look for the channel (name of receiver channels, not TT).

Show ACE screenshot Show ACE screenshot

Monitor receivers inputs

https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloReceiversExpert#How_to_configure_the_Monitoring

Change Firmware

PPROTEST OLD VERSION

There is a version already installed in P1 in

 /det/l1calo/ppmTools/pprotest 

CALIPPR FW

• Get the new version of PPROTESTatCERN from Jan (if it has been changed recently), copy in lxplus and compile it (after setup_pprotest)
• compress the folder, copy in P1 and decompress

 tar -zcvf archive.tar.gz directory/   

 tar -zxvf archive.tar.gz  

• Jan's twiki here: https://wiki.kip.uni-heidelberg.de/KIPwiki/index.php/Atlas_Privat:JJ_HowTo_P1FWupdate
• bit files are (the most recent) in the folder:

   /afs/cern.ch/work/j/jjongman/public/bitFiles 

  . Take the needed verion and put in the pprotest package in

   bitFiles/ 

• Check in the file:

    ppmServices/src/PpmFpga.cxx  

  at the very end, that the FW version is the wanted one (Currently used End 2016: RemFPGA_6.a.0.bit, Calippr_2.4.5.bit
• If need to come back to another FW version: reput in the cxx file the new bit files, recompile, make tar, move to P1, untar, upload in the sbcs
• Check the currect PPM slot mask in the file

   PPROTESTatCERN/ppmServices/apps/EepromProgramming.cxx 

  
 // Board SlotNR Mask         5  6  7  8  9 10 11 12  13 14 15 16 17 18 19 20
      unsigned char ppmMask[16] = {1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1}; // P1
//    unsigned char ppmMask[16] = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 0, 1, 0};    // ZDC P1
//   unsigned char ppmMask[16] = {0, 0, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, 0, 0};    // TestRig
//    unsigned char ppmMask[16] = {0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 0, 0, 0, 0};    // TestRig - L1CaloTest Partition only
   unsigned char mcmMask[16] = {1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1};

• enter in P1 network. Create 8 xterm and in each of them log in the sbcs:

   sbc-l1c-pcc-0(0-7) 

  (or use the alias

   pcc0n 

• In each of them:

   setup_pprotest 

  and cd

  PPROTESTatCERN 

•  ./EepromProgramming 

  . It come out a menu like this one:
• to load CALIPP FW:
  • select (1) and give 16, all PPM.
  • select (6) load CALIPP to EPROM, give nMCm number; 16 (all)
  • Insert the magic key (58).
• It starts to program and take ~ 45 min. Once it is done (check it did 16 PPM otherwise the mask was wrong!).
• Once it is done:
  • Select (7): reload CALIPP from EPROM to FPGA.
  • After that one can check that everything went fine:
  • Select again all PPM and do (9). One should read the correct version in each of the 16 PPMs
• Never do the JTAG programming! it takes forever because it does in series ever MCM. (once I did by mistake, need to stop it, load the FW in the FPGA (only in the first PPM ) with 7 and then restart with 6 and then 7
• I I cannot communicate with the VME crate maybe is becuse the crate has been shutdown, I need to reload the REM first (it does automatically when I run the standalone partition, but If I don't do it, I can do with the Eeprogramming)
  • Select (2) : Load REM firmware
  • Load from FLASH memory of from softare? (f/s)? Select s
  • then I can update the Calipp or read the info from the crate

REM Firmware

./FlashProgramming

http://franchin.web.cern.ch/franchin/L1calo/Tests_FW_Jan/REM_ipload/REM_upload_options

Chose the options. The first time you chose all PMTs, then need to first do option (3) that loads the FW in one of the 6 slots. Select option 0: REM and select the wanted slot. (End 2017 in use is slot 5 with REM verson 6.b.0 (in 2016: 6.a.0 in slot 4)). Is OKS who choses which slot to use for the run, the others once uploaded with a version can keep the version for next use. If I do th option (4) I move the FW in the FPGA but this will be reset at the next configire of the run because will read from OKS which oe to use. If I do option (6) I read what is in the FPGA, so if I upload the FW in the FLASH but without moving to the FPGA it doesn't read it. The OKS file can be seen in git here (search for flash-blockN, whith N from 0 to 5). N.B in the pprotest the counting is between 1 to 6 so pay attention of shifting by one what is in OKS wrt to the REM slot! LCD = lvds cable driver, it does some precompensation and fan-out of the lvds signals coming from the nMCMs going out to the CP & JEP, it is the bottom right daughterboard on the ppm

If there are VME errors, try loading the ReM FPGA using the ./EepromProgramming tool and the 'via software' option, then using the VME reset. This brings the modules into a cleanly configured state where you have access to all the memory modules.

NEW PPROTEST.GIT

• Change the crate configuration and mapping in this file:

   dbFiles/crateConfiguration/cern_crate.cfg 

• There are some executable files, the ones that start as INFO to display info about one PPM (configured in the previously described file), two called PROGRAM (PROGR_McmEeproms for programming CALIPPR FW and PROGR_PpmFlash for programming he flash with the REM firmware). Follow the instructions, see instruction example below. Before reading info is better do a VME_Reset first.

File contents File contents

PROGR_MmcmEeproms PROGR_MmcmEeproms

PROGR_PpmFlash PROGR_PpmFlash

./PROGR_McmEeproms

http://franchin.web.cern.ch/franchin/L1calo/Tests_FW_Jan/LoadFW/PROGRAM_McmEeproms

http://franchin.web.cern.ch/franchin/L1calo/Tests_FW_Jan/LoadFW/PROGRAM_McmEeproms

• REM:

/.PROGR_FPGAs

PPM

PPM Mapping

• EM
• HEC
• Tile
• FCAL: 4 PPMs: (crates 4 & 5, PPMs 0 & 8)
• SPARES: 4 PPMs:

PPM Calibration

• DAC scan The pedestal is adjusted and measured on regular basis by the combination of DAC scans and pedestal runs. First the linear dependency between the DAC setting (0-255) and the ADC value is measured by scanning the DAC range and measuring the ADC output for each point. An analysis determines for each tower the slope and offset of the linear function and stores them in the database. Using these parameters, the DAC setting is determined and loaded at CONFIGURE in order to result in a pedestal of 32. The DAC calibration is needed to compensate for differences of the ADCs.
• PED scan Since the precision of the DAC is coarse than the precision of the ADC (approximately factor of 2) we cannot rely on the DAC calibration alone in order to ‘predict’ the pedestal precisely enough to be used as zero-line in the LUT. Hence in second step after the DAC calibration we take a pedestal run which simple measures the pedestal, histograms it and determines mean and rms.

Hardware

• KIP database: http://www.kip.uni-heidelberg.de/atlas/db/DbPPr/signin2.php

Power cycle single PPM

ppmOff #

L1Calo Readout modes

• Default: 5+1 (7+1 used for filter coefficient calculation, 15+1 80MHz used for timing purposes, special runs)
• COOL datbase with parameters elog
• Deadtime settings for each readout mode: l1whiteboard
• Parameters: NumSamples40, ADC_latency, NumAdcSamples elog

Change Low-High mu settings: AC (high mu), matched filters (low mu)

oncall manual

https://atlasop.cern.ch/oncall/l1calo/L1CaloModStat.php

(Instructions from Martin for 2016 run, how to do manually)

• Loading low-mu matched filters, LUT slopes and noise cuts:
  • (a) First step is usually to upload the three coolinit files to the corresponding results folders. In this case I have done this already so you can directly proceed with the validation in (b). However, when reverting to high-mu settings you will have to do this step with proper high-mu files of course, and instructions are given below. Nevertheless, for completeness and emergencies, the files for low-mu

/det/l1calo/coolData/acfirsglb_physics/single_bunch  

- PprFirFilterResults_Physics_single_bunch.coolinit
- PprLutValuesResults_Physics_single_bunch.coolinit
- PprNoiseCutResults_Physics_single_bunch.coolinit

• • (b) Validation of results. In this step the matching attributes of the specified results folders are copied to the validated folder PprChanCalib (or PprChanExtra, respectively). The latter folders are used to configure the system, so this step will have impact on the performance. Hence, before running the validation it might also be a good idea to dump the previous status of PprChanCalib (PprChanExtra) which could make reversion in case of accidents easier. For this I usually create a 'work' folder. Below an example sequence of commands.

> cd /det/l1calo/coolData/acfirsglb_physics/single_bunch
> mkdir work_201609xx
> cd work_201609xx
> dumpfolder.py -f Physics -i PprChanCalib
> mv PprChanCalib_Physics.coolinit PprChanCalib_Physics_201609xx_before.coolinit

> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprFirFilterResults
> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprLutValuesResults
> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprNoiseCutResults

• II. Loading high-mu AC filters, LUT slopes and noise cuts:

(a) Upload the three coolinit files to the corresponding results folders. The results folders are used for storing calibration results without actually using them. So no changes to the performance of the system are done in this step. The coolinit files with the AC filters can be found in /det/l1calo/coolData/acfir25ns_physics/20160726/acMu29.

> cd /det/l1calo/coolData/acfir25ns_physics/20160726/acMu29
> loadfolder.py -d "$L1CALO_DB_CONNECT" -f Physics PprFirFilterResults_Physics_20160721_ACmu29.coolinit
> loadfolder.py -d "$L1CALO_DB_CONNECT" -f Physics PprLutValuesResults_Physics_20160721_ACmu29.coolinit
> loadfolder.py -d "$L1CALO_DB_CONNECT" -f Physics PprNoiseCutResults_Physics_20160721_ACmu29.coolinit

• (b) Validate the results. In this step the matching attributes of the specified results folders are copied to the validated folder PprChanCalib (or PprChanExtra, respectively). The latter folders are used to configure the system, so this step will have impact on the performance. Hence, before running the validation it might also be a good idea to dump the previous status of PprChanCalib (PprChanExtra) which could make reversion in case of accidents easier. For this I usually create a 'work' folder. Below an example sequence of commands.

> cd /det/l1calo/coolData/acfir25ns_physics/20160721/
> mkdir work_201609xx
> cd work_201609xx
> dumpfolder.py -f Physics -i PprChanCalib
> mv PprChanCalib_Physics.coolinit PprChanCalib_Physics_201609xx_before.coolinit

> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprFirFilterResults
> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprLutValuesResults
> useCalib -d "$L1CALO_DB_CONNECT" -f Physics -v PprChanCalib -r PprNoiseCutResults

PPM COOL ID

PPM test, software patches

• Usually Martin put the patches in P1 here:

    /det/l1calo/ppmTools/patches  

• Using su l1calo copy the interesting libray (renaming it without the extension, in

    /det/l1calo/releases/tdaq-06-01-01/l1calo/pro/installed/patches/x86_64-slc6-gcc49-opt/lib/  

• log files are in each sbc crates (sbc-l1c-pcc-0n) here:

  /logs/tdaq<version>/<partition>  

HDMC (Hardware Diagnostic Monitoring and Control system)

• From the sbc open it with

   dbhdmc 

  and open the correct ppm crate (depending from which sbc it is lounched)
• The igui will open, File --> LoadDBcrate --> Select the ppm crate, ppm, mcm and channel. Open the interested register and click on Read

Show Screeshots Show Screeshots

Make some hot towers via LUT

• login in the correct sbc in P1 while the test run in ongoing (ssh -Y sbc-l1c-pcc-0c)

•  dbhdmc 

  after having setup_l1calo
• chose the right MCM, and channel, and chose either the lutCP or lutJEP. Open. Read values, There is a list of them. take the last value with zeroes and fill with ffff. The point

• It should be suddenly effective and no need to put back. once the PPM is configured in the next run it reads from the DB the correct value
• The tower should become hot in the mapping tool.

Show Screeshots Show Screeshots

Pedestal Corrections

  TRIGGER/L1Calo/V2/Configuration/PprChanDefaults/CR43_PedCorrEnable  

CPM-JEP

Overflows

Event with 6 jets Event with 6 jets

CMX Ovrflows

https://atlasdaq.cern.ch/info/mda/db/ATLAS/365304/Histogramming.l1calo-athenaHLT./L1Calo/CPM_CMX/Input/cmx_2d_tob_Overflow

L1Topo

CTP rates Topo CTP rates Topo

• Validation Topo plots, run from AOD, can be configurble on the fly (from Sara Alderweireld): https://salderwe.web.cern.ch/salderwe/tmp/topotest/

Topo Caldo

connect to pc-l1c-topo-00

either go in /atlas-home/0/simoniel/executables/DANGEROUSTOOLS
or copy /atlas-home/0/simoniel/executables/DANGEROUSTOOLS/topoCaldo.py in your home

for test with LAr no need of any special keys or any special configuration (they already set up ATLAS as they need)

run: python topoCaldo.py
from the menu “Partition” select “ATLAS”
from the menu “Pattern” select “TwoEm90” - when you select the pattern the hot tower will start *automatically* to stop it you need to select “None” from the “Pattern" menu. This process will cause a lot of errors messages to the run control but it is exactly what LAr people want ;)

Not necessary but if you are curious: the time stamp on when you activate any pattern can be monitor from or L1Calo on-call page in the ERS messages filtering for “Undefined” for the application ID

Errors while running

L1Calo webpages links

• Official l1calo known problem page: https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloKnownProblems
• Hardware interventions twikii; https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloHardwareInterventions

some encountered errors

• Nov 17, Stopless removal of ROS-TDQ-CALPP-01, https://atlasop.cern.ch/elisa/display/367662

•  ERROR l1calo-check-status-app cs::BadModuleStatus Bad module status seen for l1calo-cp3-cam

  https://atlasop.cern.ch/elisa/display/281077 problem with relative timing of clocks arriving at input of different boards in the crate. Error appeared in 2016: 19.03.16, 28.04.16
• 100% Busy topo. https://atlasop.cern.ch/elisa/display/301457
• 100% topo busy start of run, TTC restart should help https://atlasop.cern.ch/elisa/display/301713
• TWIKI https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloMrsMessages
• Error cs:BadModStatus seen for l1calo-roc0-rod0. See also in the error plot in tier 0 and online. If the error repeats the shifter should call. Look online ine in the OncallPage

• PP0 not responding and giving stoppless removal. Problem with the sbc. reboot sbc worked. https://atlasop.cern.ch/elisa/display/308361 https://atlasop.cern.ch/elisa/display/308340
• If a monitoring pc dies need to be replaced with another one (there are 4 in total, two are used, two spares) but we need to change in OKS the address. The same if we replace an sbc. Need to learn how to modify oks
• TRP not publishing rate anymore because aplication died. Need to be restarted by run control: https://atlasop.cern.ch/elisa/display/317134
• Calibration panel not starting. Close, exist restart X. https://atlasop.cern.ch/elisa/display/316878
• Noise burst at adjust phase. tipically they will be quet during stable beam. Noise Killer might intervene and kill noisy cells https://atlasop.cern.ch/elisa/display/317096
• Topo busy for ~ 1min due to clock swithches (usually outside stable beam) elog
• Psare PPM causing busy L1CAlo https://atlasop.cern.ch/elisa/display/316026
• jep0-jem03, occasional Parity errors on LVDS link (October 2016) https://atlasop.cern.ch/elisa/display/325741
• check-status on cp0-cam (October 2016) https://atlasop.cern.ch/elisa/display/325739
• Problems with L1Mu2Topo_RCD app: in it living on a TGC PC (pc-tgc-mon-rod-01), but is also related to MUCTPi and L1Topo. If TGC PC is down it gives errors on our side..
• JEM simulation error (1/min). Oct 17. Solved reloading the JEM FW after end f the run. Tolerable defect affecting Ex calculation. https://its.cern.ch/jira/browse/ATLLONECAL-109
• crsh monitor application at end run, https://atlasop.cern.ch/elisa/display/364236

Topo (2017)

• FATAL due to IPbus transition failure (error at CONNECT): 1/2 time per week. to go down and up again with the ATLAS partition.
• l1calo-topo-l1topo1 error (Access attempted on non-validated memory). --> This is not an issue regardless the status of the partition. It likely happend during a lock switch. During clock switch there is a sequence of resets to re-synchronize the various part of L1Calo and L1topo is last, and subjected to a rather long resets: if the monitoring application try to read number (registers), the IPbus would not be responding due the on-going reset. Therefore the error. Topo input/output mismatches with CMX/CTP
• Topo busy and stopless removal at ramp down: https://atlasop.cern.ch/elisa/display/357928
• Everytime Topo RoIB is busy, TTC restart doesn't help, need to reload topo fw (and go to shutdown with the run before)

L1Calo Busy

• HLT backpressure physics related or generated by a very hot tower (look for hot towers TOBs)
  • HLT backpressure should be visible by the Busy Panel RoIB XOFFS and also from pbeast: https://atlasop.cern.ch/tdaq/pbeast_dashboard/#/dashboard/file/Dashboard_ATLAS_Complete

• Sometimes topo get busy at beginning of the run. Solved with a TTC restart

Operation

Dead Times

https://indico.cern.ch/event/708589/contributions/2909405/subcontributions/249519/attachments/1638435/2615082/L1CT.pdf

CTP deadtime and project tag settings:

• New CTP webpage with deadtimes per run: https://atlas-l1ct.cern.ch/pbeast_plots/

For STABLE BEAMS (data16_13TeV): Simple 7, Complex: b0=6/811 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=2/400 (PIX/IBL)

For beam commissioning (data16_comm): Simple 16, Complex: b0=15/370 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=1/400 (PIX/IBL)

For cosmics running (data16_cos): Simple 16, Complex: b0=15/370 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=1/400 (PIX/IBL)

For beam splashes (data16_1beam): Simple 2500 (LAr in 32 samples mode), Complex: b0=6/811 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=1/400 (PIX/IBL)

For high-rate running (data16_comm): Simple 6, Complex: b0=15/370 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=7/260 (PIX/IBL) NB: WITHOUT Pixels

For high-rate (100 kHz) running (data16_comm): Simple 4, Complex: b0=15/370 (L1Calo ); b1=42/381 (TRT); b2=9/351 (LAr); b3=7/260 (PIX/IBL) NB: WITHOUT Pixels

For low-rate ID cosmics running (data16_comm): Simple 16, Complex: b0=15/370, b1=42/381, b2=9/351, b3=1/400; SMK: 2297, L1PSK : 6495, HLTPSK: 4830, BGK: 1003; NB: ONLY WITH Pixels, SCT and TRT (using FastOR trigger); include also other sub-systems

DATABASES

L1Calo Databases https://twiki.cern.ch/twiki/bin/viewauth/Atlas/LevelOneCaloDatabases

OKS (with all hardware configurations)

• https://atlasop.cern.ch/twiki/bin/view/Main/L1CaloOksDatabase
• https://twiki.cern.ch/twiki/bin/viewauth/Atlas/DaqHltOks

oks_data_editor filename.xml 

Martin, Bruce modify manually the xmls file. To do it: in P1 create a tmp folder (and then you will erase after having done, to dont do mistakes next time, or remember to update it next time, before modifying with

oks-update.sh 

• For example to change the address of the REM formware version :

oks-checkout.sh /atlas/oks/tdaq-06-01-01/l1calo/sw/l1calo_firmware.data.xml 

  "PpmFpgaProgram" "PpmRemFPGA-flash-block3" 

example example

  

<obj class="PpmFpgaProgram" id="PpmRemFPGA-flash-block2">
 <attr name="BinaryName" type="string">"FlashMemory"</attr>
 <attr name="Description" type="string">""</attr>
 <attr name="Authors" type="string" num="0"></attr>
 <attr name="HelpURL" type="string">"http://"</attr>
 <attr name="VersionID" type="u32">0x60907</attr>
 <attr name="CadProject" type="string">""</attr>
 <attr name="CheckString" type="string">""</attr>
 <attr name="Checksum" type="u32">0</attr>
 <attr name="ChipType" type="string">"XCV1000E"</attr>
 <attr name="FlashRamBlock" type="u32">0x2</attr>
 <attr name="SourceURL" type="string">""</attr>
 <attr name="ProgramType" type="enum">"RemFpgaDefault"</attr>
 <attr name="DeviceName" type="enum">"RemFpga"</attr>
 <rel name="Needs" num="0"></rel>
 <rel name="BelongsTo">"FpgaConfiguration" "ppm-rev6-flash"</rel>
 <rel name="Uses" num="0"></rel>
</obj>

<obj class="PpmFpgaProgram" id="PpmRemFPGA-flash-block3">
 <attr name="BinaryName" type="string">"FlashMemory"</attr>
 <attr name="Description" type="string">""</attr>
 <attr name="Authors" type="string" num="0"></attr>
 <attr name="HelpURL" type="string">"http://"</attr>
 <attr name="VersionID" type="u32">0x60a00</attr>
 <attr name="CadProject" type="string">""</attr>
 <attr name="CheckString" type="string">""</attr>
 <attr name="Checksum" type="u32">0</attr>
 <attr name="ChipType" type="string">"XCV1000E"</attr>
 <attr name="FlashRamBlock" type="u32">0x3</attr>
 <attr name="SourceURL" type="string">""</attr>
 <attr name="ProgramType" type="enum">"RemFpgaDefault"</attr>
 <attr name="DeviceName" type="enum">"RemFpga"</attr>
 <rel name="Needs" num="0"></rel>
 <rel name="BelongsTo">"FpgaConfiguration" "ppm-rev6-flash"</rel>
 <rel name="Uses" num="0"></rel>
</obj>

If we want the new one we will upload it with Jan's code in slot 4, and then wen we want to use it we have to change the fw version in the slot and the line here

  PpmFpgaProgram" "PpmRemFPGA-flash-block4"  

oks-commit.sh -u l1calo_firmware.data.xml   -m "comments that goes in cvs"

• To disable a PPM , checkout the following file:

 /atlas/oks/tdaq-06-01-02/hw/l1calo_crates.data.xml

COOL (with calibration stuff)

ACE config in P1

• How to configure the database opening:

Show Screeshots ACE Show Screeshots ACE

• Full L1Calo chain cools database example :

Screeshot Screeshot

• Example on how to open it : If on wants to see the db changing vs time:

Screeshot Screeshot

• Full PPrChanCalib:

Screeshot Screeshot

Other stuff

• Setting proxy to edit P1 twiki pages:

https://atlasop.cern.ch/twiki/bin/view/Main/EditTwikiFromAnywhere#ProxySetup

https://atlasop.cern.ch/twiki/bin/view/Main/LArOperationManualExpert

Mainteinance

• Tile parallel elog: https://pcata007.cern.ch/elog/Maintenance/

HLT releases and merge requests

https://gitlab.cern.ch/atlas/athena/merge_requests/12888

Online Software

• Tile towers warnings: /atlas/moncfg/tdaq-06-01-01/combined/triggerMonitor/BeamStatesToIgnore.dat

Online Software

• Oct16 Murrough's presentation CMake, seful links: slides, twiki with instructions

Isolation and Noise Cuts

• Queen Mary Git: https://gitlab.cern.ch/QMUL/TrigEff

Phase2

• Tile demonstrator installed in 2019 in LBA14

L1Calo Results

• L1Calo Public Results https://twiki.cern.ch/twiki/bin/view/AtlasPublic/L1CaloTriggerPublicResults
• Performance Trigger 2015 https://cds.cern.ch/record/2140103/files/

Interesting talks

• L1Calo Joint meeting twiki; link
• Jan:
  • Feb 2016 Joint: PPM HW/FW and Sat BCID: link
  • Sept 2015 Joint: PPm HW/FW: link
  • June 2014: Joint: HW/FW status: link
  • 2016 high RR school, summary PPM: link
  • 2016 KIP HW: Finding Sat BCID Thresholds: link
  • 2016 KIP Analysis meeting: BCID L1calo: link
  • 2014 Pedestal Corrections: link
• Claire
  • Feb 2016: PPM performance: link
  • Sept 15: BCID 80: link
  • Sept 15: Timing update (40 MHz runs)
  • Nov 16, Sat80 performances: https://indico.cern.ch/event/588576/contributions/2372909/attachments/1373169/2083748/analysiscontribution_17Nov2016.pdf

• Sebastian Feb 16: Mistimed BCID analysis: link
• Stanislav
  • Feb 16: improvedLUT jets: link
  • Oct 15: Miss Et, Jet calib link
  • Nov 15 TGM: Et, jet calib: link

• Timing talks
  • Fabrizio JM July 17: talk

• Calibration:
  • https://indico.cern.ch/event/510610/contributions/2143238/attachments/1263029/1868011/250416_summaryCalib_Silvia.pdf
  • MartinK OFC LAr: https://indico.cern.ch/event/772504/contributions/3210032/attachments/1788150/2912115/OFCs_Calibration_EMEC.pdf https://indico.cern.ch/event/777509/contributions/3280846/attachments/1786280/2908374/New_Physics-to-Pulser-Corrections_in_EMEC.pdf

• • 2019 tests with calorimeters: https://indico.cern.ch/event/793457/

• KIP meetings, PPM related talks
  • Francesco BCID pulser runs: link

• Ben ATLAS weekly, L1 general (may 2016): link
• Martin ATLAS weekly Sat BCID (March 2016) link
• Trigger Operation, ATLAS weekly (May 2016) link
• Rainer ATLAS weekly mistriggered events in 2015: https://indico.cern.ch/event/434823/contributions/1080859/attachments/1132872/1619897/150728_ATLASWeekly_L1Calo_stamen.pdf

• Trigger talks
  • https://indico.cern.ch/event/541088/contributions/2201697/attachments/1290872/1922542/20160614_trigger_menu.pdf
  • https://indico.cern.ch/event/517101/contributions/2030723/attachments/1256623/1855315/Menus_20160412.pdf

• General L1Calo Talks
  • Oct 2015 M. Polka: https://cds.cern.ch/record/2059328/files/ATL-DAQ-SLIDE-2015-780.pdf
  • Nov 15. Kate TDAQ week link

• Topo Talks
  • Eduard ATLAS weekly Sept16: link
  • Imma Oct16: link

• LHC Status Summary
  • Martin 5Oct2017: Martin Talk Gruffalo

• Mistriggered events
• Steve: 7June16, 25Nov15

• Filters
• Poster Andrew: http://epweb2.ph.bham.ac.uk/user/daniells/Talks/L1Calo/RALPoster.pdf
• Andrew 2013 talk1, talk2 talk 2012 25 vs 50 ns (2012)

• *Noise Cuts optimization * 2015 Steve https://indico.cern.ch/event/446823/contributions/1110657/attachments/1157457/1664633/lowmute150921.pdf

• FCAL Geometry https://indico.cern.ch/event/165077/contributions/1417357/attachments/198964/279273/l1c_111207_lar.pdf

• MBTS noise https://indico.cern.ch/event/131301/contributions/1350605/attachments/95271/136141/mbtsxtalk110607.pdf

• Mistimed Streams: talk1 , talk2

ATLAS Software tutorial

• Computing tutorial link
• Software tutorial link
• Python twiki link
• Sw basis https://twiki.cern.ch/twiki/bin/view/AtlasComputing/SoftwareTutorialSoftwareBasics#Grid_Certificates

PileUp

LHC Stuff

• 8b4e schema (from October 2017): to cope with 16L2 problem, instead of a continuous train of bunches spaced by 25 nanoseconds, this beam consists of mini-trains of eight bunches spaced by 25 nanoseconds and four empty bunch slots. This irregular beam pattern suppresses the formation of electron clouds compared to the standard beam. While the LHC operated with up to 2556 bunches in July, operation with "8b4e" limits the number of bunches to around 1920.
• Reduction of Crossing angle: http://home.cern/cern-people/updates/2017/09/lhc-report-colliding-angle
• Filling Schema Web Site (user lpc) http://lpc.web.cern.ch/SchemeEditor.htm
• LPC Evian Dec17: https://indico.cern.ch/event/663598/contributions/2782518/attachments/1573604/2487449/Evian2017_ExperimentsInput2018_final.pdf

Emittance scans

• 22 March Ale: https://indico.cern.ch/event/708578/contributions/2909361/subcontributions/252147/attachments/1621316/2579771/2018-03-22-dailyrun.pdf
• 27 March, ATLAS weekly, Nicoletta: https://indico.cern.ch/event/716501/contributions/2945291/attachments/1623629/2584759/Weekly_27032018.pdf

Heavy Ions

• Spread in TE: https://atlasop.cern.ch/elisa/display/361073

Pulse shape Oscilloscope

• https://twiki.cern.ch/twiki/bin/viewauth/Atlas/LevelOneCaloPulseShapes

L1Calo documents

• Readout https://edms.cern.ch/ui/file/761046/5/PPM_S-Link_data_formats_v2.1.pdf
• Hardware specifications https://atlas-l1calo.web.cern.ch/atlas-l1calo/html/orgweb/Modules/Modules.html

Simulation

Overlay Simulation

• https://indico.cern.ch/event/590779/contributions/2383766/attachments/1376860/2091072/L1Calib_20161124.pdf
• https://indico.cern.ch/event/279530/contributions/634995/attachments/511924/706533/Haas_ATLAS_PileupOverlay_3-19-2014.pdf

Data Quality

• Murrough's fixes of Ped Correction Histos: https://atlasop.cern.ch/elisa/display/367375

L1Calo pictures

• KIP server: http://www.kip.uni-heidelberg.de/atlas/docs/l1calo/plots

L1Calo Upgrade documentation

• Twiki Reviews: https://twiki.cern.ch/twiki/bin/view/Atlas/LevelOneCaloUpgradeModules
• FOX https://cds.cern.ch/record/2286379/files/ATL-COM-UPGRADE-2017-014.pdf?version=4
• TREX https://edms.cern.ch/ui/file/1533071/0.2/TREX_TechSpecs_v0.2.pdf,

https://cds.cern.ch/record/2646164/files/ATL-COM-DAQ-2018-175.1.pdf?version=3

CTP

• Multi partitions for commissioning: https://twiki.cern.ch/twiki/bin/viewauth/Atlas/LevelOneCentralTriggerMultipartitions

Other Links

• Jan's twiki at KIP: https://wiki.kip.uni-heidelberg.de/KIPwiki/index.php/Atlas_Privat:JJ_Base

Upgrade Studd

-- SilviaFranchino - 2015-11-16