Online and offline software overview status and plans
This presentation is the property of its rightful owner.
Sponsored Links
1 / 20

Online and offline software overview, status and plans PowerPoint PPT Presentation


  • 97 Views
  • Uploaded on
  • Presentation posted in: General

Online and offline software overview, status and plans. Status and Integration to STAR : Trigger DAQ Monitoring Slow Controls Online Databases Online/Offline/MC software. Trigger. FMS (and FPD and FPDSMD) are all connected to QT boards and DSM Tree

Download Presentation

Online and offline software overview, status and plans

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Online and offline software overview status and plans

Online and offline software overview, status and plans

Status and Integration to STAR :

Trigger

DAQ

Monitoring

Slow Controls

Online Databases

Online/Offline/MC software


Trigger

Trigger

FMS (and FPD and FPDSMD) are all connected to QT boards and DSM Tree

  • Full FMS/FPD trigger algorism document is available

    http://www.star.bnl.gov/public/trg/TSL/Software/fms_algorithm_2009.pdf

    • High Tower Trigger

    • Cluster Sum Trigger

    • Multi Cluster Trigger

    • Module Sum Trigger (FPD)

    • LED trigger

  • Test bed for new QT system (now used for other detectors)

  • Full bit-wise check of DSM Tree (now covers all DSM tree)

    Plan : Already fully integrated

    Improvements (Jet Trigger with FHC)


Online and offline software overview status and plans

DAQ

  • All QT and DSM Tree are read by L2

  • FMS (and FPD/FPD-SMD) data are part of trigger data bank

     DAQ file

     Trigger Data file (with pre/post data)

  • Trigger Data file analysis tool (trg2ntp) maintained by FMS group is essential and used by many subsystems

    Plan: Already fully integrated


Monitoring status

Monitoring Status

Few plots in Pplot as of run9

Because it samples only tiny fraction of data, it was almost useless

Experts running monitoring/reconstruction codes on trigger data file ~min after run is taken

  • Les’s online pi0 reconstrucitons

    (off TrgSscratch)

  • Chris’s bitwise check (off L2)

  • Hank’s monitor (off TrgSscratch)

    • Len monitor (off HPSS)

      http://drupal.star.bnl.gov/STAR/blog/leun/2009/may/09/fms-trigger-analysis

    • Steve’s analysis (off HPSS)

      http://drupal.star.bnl.gov/STAR/blog/heppel


Monitoring plan

Monitoring Plan

  • Improved Pplot to monitor LED signal

    Ensured bandwidth of LED trigger into EVPool(Jeff said its easy)

    This monitors everything : HV, gains, LED, Trigger and DAQ

  • Unified and systematic/automated reconstruction codes running

    Bottleneck is getting data to RCAS disks

    (Trigger Data file -> L2- -> TrgScratch -> Online farm & HPSS)

    HPSS -> “ntuple”s on RCAS

    Bottleneck will be HPSS->RCAS disk speed, and diskspace

    Minimal CPU ~1min / 10k event file * ~50files / run * 50 run / day = 250 CPU min / day

    gzipped ntuples ~400 G byte from run9

     User monitor codes (Like Len’s)

     Reconstruction iterations (Like Les’s and Steve’s)

  • Real-time fast stream MuDst with StTriggerData(raw trigger data) production??? (only if Jerome can be convinced after all those years)


Slow control online db status

Slow Control & Online DB Status

  • Console/command-line based system (No connection to STAR SC)

    Large cells: Shell scripts to communicate with LeCroy 1440a

    small cells: PSU software to communicate with PSU HV motherboard

  • Only expert(s) to turn on/off HV or change HV

    We do not turn on/off for beam dump/refill

    No HV trips to reset

    Zener Diode Issue

  • HV Alarm = Les Bland (No alarm to STAR alarm handler)

  • HV setting file on local disk

  • QT-LUT-Gain file on trigger local disk

  • HV log files on local disk every ~min = ~10 G bytes for run9 (no connection to Online DB)


Current fms hv system

Current FMS HV system

fmsserv.trg.bnl.local (terminal server)

LeCroy1440

fpd.daq.bnl.local

North Top Lg cells

LeCroy1440

North Bot Lg cells

LeCroy1440

South Top Lg cells

cwcontrol.trg.bnl.local

LeCroy1440

South Bot Lg cells

fpdswitch.trg.bnl.local

(network power switch)

LVs

PSU Motherboard

North Sml Cells

PUS Motherboard

South Sml Cells

HV Operation Manual / Documentation / HV setting file & logfile location

http://aquila.lbl.gov/FMS/electronics/FMS_HV_control.pdf

HV cable map

http://les.will.post.the.page.gov

QT-LUT-gain

[email protected]:~/trg/???


Slow control online db integration plan

Slow Control & Online DB integration Plan

  • No big change in HV system itself is planned

  • It should remain “experts” only to operate HV

    (Zener Diode issue, no trip, no on/off while dump)

  • Instruction to shift : Watch LED plots in Pplot, call expert if any change

    Do no turn on/off HV

    Who is “expert(s)” / who is allowed to change HV  See Les’s management talk

  • Sending log-files to Online-DB is not essential and not planned

    • trg.bnl.local bandwidth issue

    • LED monitor will do most of the job

    • low priority, but if required, need ~2FTE month

  • Messaging to STAR alarm system is not essential and not planned

    • It was stable (There was no HV trips)

    • LED monitor will do most of the job

    • low priority, but if required, need ~2FTE month


Fms reconstruction code

FMS reconstruction code

Raw Data (Encoded QT data)

QT decoder

Decoded QT data

MC cell list from GSTAR

Mapping & Calibration

Summing, mapping

Inverse-Calibration, Digitization & Calibration

Hit (Mapped & Calibrated Energy) list

Cluster Finder

Cluster list

Shower Shape fit

Photon list

Geometry & Cuts

User analysis

  • We’ll have 1st order calibration relatively quick (online pi0 reconstructions)

  • Final calibrations with energy dependence (none-linearity) & run dependence comes much later


Online and offline analysis code status

Online and Offline Analysis code Status

PYTHIA with specialized filter

Experiment

GSTAR (FPD & FMS geometry)

HBOOK ntuple (MC)

Trigger Data file

HBOOK ntuple (raw)

DAQ file

BNL package

HBOOK ntuple

(raw + EMC/TPC)

PSU package

StEvent (raw)

MuDST (raw)

Calibration text files

Geometry text files

Map text files

Parameter text files


Bemc model

BEMC model

GSTAR

Experiment

GSTAR file

DAQ file

EMC makers in BFC (DB + ClusterFinder + PointFinder)

g2r

StEvent (raw + cluster + point)

Offline DB (preliminary)

MuDST (raw + cluster + point)

Offline DB (updated)

Mudst2StEvent + EMC makers

StEvent on memory (raw + cluster + point)

MuDST on memory (raw + cluster + point)


Online and offline analysis code status1

Online and Offline Analysis code Status

  • Trigger Data file and ntuple from GSTAR  Analysis is NOT just “online” monitoring

  • Large volume of this analysis is happening just (~min) after run is taken

  • Used as “online” monitoring

  • Used as feedback to HV/LUT gain

  • Used as “offline” analysis for inclusive physics results, up to final papers

  • MC saves many CPU hours by not simulating particles into mid-rapidity/east

  • MuDST file  Analysis

  • MuDST is produced ~months later

  • Used for FMS-TPC or FMS-BEMC correlation analysis


Online and offline analysis code status2

Online and Offline Analysis code Status

BNL & PSU packages are based on the same reconstruction code (“Yiqun’s code”)

- Some differences because improvements made since code was split

- BNL package = fortran/hbook+paw wrapped

+ New cluster finder (Ermes’s work) for hole treatment

+ Energy dependence/Run dependence corrections

+ SMD reconstruction

Code is available : rcas://hank/put/the/file.tar

- PSU package = c++/root wrapped

+ Code cleanup/re-organization

+ New cluster finder

Code is available : rcas://Steve/put/the/file.tar


Analysis code plan

Analysis Code Plan

  • Preserve “Trigger Data file analysis” path

    • Established user codes/scripts

    • Light weight for quick turn around (Concern on speed / overhead if we switch)

  • We want one code to do “trigger data file analysis”, “MuDST analysis” and “MC analysis”

    • Re-merging “reconstruction (yiqun) code” in BNL and PSU package

    • One code in CVS, included in both Makers and “BNL/PSU packages”

    • Separate cluster finder and shower shape fitting

    • Add options/switches to have different code/versions

  • Define classes in StEvent/MuDST for

    • Raw Data

    • Hit (Mapped & calibrated energy) list

    • Cluster list

    • Photons list

  • Map, Geometry and Calibration in DB

  • g2r (Never needed correlated MC sample so far)

  • Man power


Online and offline software overview status and plans

Plan

PYTHIA with specialized filter

Experiment

GSTAR (FPD & FMS geometry)

HBOOK ntuple (MC)

Trigger Data file

HBOOK ntuple (raw)

DAQ file

BNL package

HBOOK ntuple

(raw + EMC/TPC)

PSU package

StEvent (raw)

MuDST (raw)

Calibration text files

Geometry text files

Map text files

Parameter text files


Online and offline software overview status and plans

Plan

GSTAR

Experiment

Trigger Data file

Trigger data file reader

GSTAR file

DAQ file

FMS makers in BFC (DB + ClusterFinder + Photon Fit)

g2r

StEvent (raw + cluster + photon)

Offline DB (preliminary)

MuDST (raw + cluster + photon)

Offline DB (updated)

Mudst2StEvent + FMS makers

StEvent on memory (raw + cluster + photon)

MuDST on memory (raw + cluster + photon)


Online and offline software overview status and plans

Plan

Experiment

GSTAR

Trigger Data file

GSTAR file

DAQ file

g2r

HBOOK ntuple (raw)

StEvent (raw)

Online Package(s)

MuDST (raw)

FMS analysis Maker(s)

(Hit + Cluster + Photon list)

Cluster Finder

Shower fit

text files

MuDST on memory (raw + hit + cluster + photons)

Offline DB


Summary of fsm integration plan

Summary of FSM integration plan

  • Trigger - Done

  • DAQ - Done

  • Monitor – LED

  • Slow Control / Online DB – No need

  • Software

    • Unify to one code

    • Preserve “fast” path

    • Bring FMS raw data, HIT, Cluster and Photon to MuDST


Backup

Backup


Analysis code plan1

Analysis Code Plan


  • Login