STAR QA Board

["Ray, Robert L" <ray@physics.utexas.edu>]

Hi All:

It turns out that I was mistaken about the nomenclature for

B field direction in STAR. I assumed the field was changing from

normal (Full) to reversed, then back to normal. I was 180 deg. out

of phase. The runlog's B field values and trigger Ids are correct.

My apologies,

Lanny

---

From: STAR-QAboard-l <star-qaboard-l-bounces@lists.bnl.gov> on behalf of Van Buren, Gene via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov>
Sent: Friday, March 5, 2021 12:26 PM
To: Frank Geurts via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov>
Subject: Re: [STAR-QAboard] Run21 QA meeting, tomorrow (Friday) at noon

 

A couple follow-ups to today's QA meeting and discussions....

FastOffline:

Logs are here: /star/rcf/prodlog/dev/log/daq/

Reconstruction chain is: "P2021a,StiCA,BEmcChkStat,-hitfilt "

Output are on /star/data{09,10,11,12}/reco

QA Issue Dashboard:

https://www.star.bnl.gov/devcgi/qa/QAShiftReport/issueDashboard.php

People are welcome to look at this, play with it, use it, provide feedback, etc. I do believe it would be straightforward to use the Offline QA's issue system for issues beyond what the Offline QA shift crew reports. The system offers issues:

- categories (e.g. specific subsystems, tracking, ...)

- keywords (e.g. dead channels, asymmetry, ...)

- names (short description)

- long description

- follow-up comments

- closure/resolution

- image attachments

  => there's an automated system for this for the shift crew, but there's a separate upload functionality regardless

- run tagging

  => gain automated for shift crew, but no manual interface at the moment, though this will be easy for me to add

- hyperlink directly to issue

The dashboard I showed today is nothing more than a front-end display to content that's been available for years, so it only took me a few hours yesterday to write. We can certainly explore ways to enhance or leverage this system further.

Thanks,

-Gene