February 6, 2019 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* trigger files 2,3: mc-based roads and gsim-based roads, road-pcal match, road-htcc match if ready - 2 validation runs against electron events, do not need random runs | * trigger files 2,3: mc-based roads and gsim-based roads, road-pcal match, road-htcc match if ready - 2 validation runs against electron events, do not need random runs | ||
* decide on production trigger | * after testing trigger 1,2,3 we'll decide on production trigger | ||
* multi-stream ER will be ready in case we need higher data rate (higher beam current possible | * multi-stream ER will be ready in case we need higher data rate (higher beam current possible | ||
* official run period name - 'rg-b', Sergey will fix cron jobs | * official run period name - 'rg-b', Sergey will fix cron jobs | ||
Latest revision as of 11:05, 6 February 2019
present: Sergey Boyarinov, vpk, Raffaella, Graham, Ben, Iordanka, Silvia, Eugene, Nathan, Stepan
Run preparations were discussed:
- level3 and helicity correction: implemented, will be tested tomorrow
- triggers will be ready with following running strategy:
- trigger file 1: basic trigger (with new htcc !) without roads, all from Dec run is there including dc super layers multiplicity; data-based roads and dc-pcal geom match in tagging mode - random run 150Mevents for validation
- trigger files 2,3: mc-based roads and gsim-based roads, road-pcal match, road-htcc match if ready - 2 validation runs against electron events, do not need random runs
- after testing trigger 1,2,3 we'll decide on production trigger
- multi-stream ER will be ready in case we need higher data rate (higher beam current possible
- official run period name - 'rg-b', Sergey will fix cron jobs