Electron-Ion Collider Detectors: MPGD ECT
Experiments
Quark-Gluon Confinement and Strong QCD
- A Search for Hybrid Baryons in Hall B with CLAS12 (E12-16-010)
- Spokespersons: V. Burkert, D.S. Carman, A. D'Angelo, †E. Golovach, R. Gothe, V. Mokeev
- Hybrid wikipage
- Experimental Proposal
- Nucleon Resonance Structure Studies Via Exclusive KY Electroproduction at 6.6 GeV and 8.8 GeV (E12-16-010A)
- Spokespersons: D.S. Carman, R. Gothe, V. Mokeev
- Experimental Proposal
- DVCS with CLAS12 at 6.6 GeV and 8.8 GeV (E12-16-010B)
- Spokespersons: M. Defurne, L. Elouadrhiri, F.-X. Girod, F. Sabatié
- Experimental Proposal
Jeopardy Document
Quark-Gluon Confinement and Strong QCD
- Final Submitted Document
- Documents Exchanged with the Review Committee
- Presentation to the PAC48 committee
- Additional Notes on Data Analysis
Link to the pdf file RG-K Jeopardy PAC48
Cover Page RG-K Jeopardy Cover page
First Round Comments Document First Round Comments
Link to pdf document v2 Quark-Gluon Confinement & Strong QCD
First Round Comments Reply First Round Comments Reply
Link to the slides pdf version RGK_PAC48
Pass2 Review Documents
Pass 2 Readiness Review - August 16th 2023
- *** Direct link to the Zoom meeting
- RGK weekly meetings:
- Meetings are now on Wednesday at 10:30 am (JLab-time).
- Direct link to the Zoom meeting
- Link to the Calendar file
- Meetings are now on Wednesday at 10:30 am (JLab-time).
- CLAS Collaboration Review:
- [1] (February 7, 2022 - submitted version)
- Ad Hoc Review:
- Working Group Review:
- MM Fits:
- Asymmetry Fits:
- Documentation:
- Custom wagon skim21 (e'K+) [11]
- KY Event Generator Note (CLAS12-Note 2021-003)
- σLT' Analysis
- KY Analysis wikipage [12]
- KY Recoil Polarization
- Archival Information:
- RG-K internal review version (June 9, 2021)
- RG-K internal review reply document (June 28, 2021)
- PAC48 Jeopardy Documents: (posted May 23, 2020)
- RG-K internal review version (June 9, 2021)
- June 21, 2019: Preliminary study of ep -> e'p' pi+ pi- using 6.5 GeV runs and compare old/new cooking: [13] - K. Hicks
- August 09, 2019: Experimental efficiency study from ep -> e'p' pi+ pi- using 7.5 GeV, v13 run Slides - E. Golovach
- August 30, 2019: Missing masses .vs. kinematical variables Slides - E. Golovach
- September 6, 2019: Missing masses for data and simulation Slides - E. Golovach
- September 11, 2019: Generated and Reconstructed events Slides - E. Golovach
- October 25, 2019: Two pions and elastic peak Slides - E. Golovach
- December 20, 2019: Estimation of the electron reconstruction resolution Slides - E. Golovach
- January 17, 2020: Estimation of the electron momentum resolution Slides - E. Golovach
- March 6, 2020: Missing masses and data quality check Slides - E. Golovach
- July 3, 2020: 2 pion background Slides - E. Golovach
- July 31, 2020: 2 pion skimming. Additional MM2 cuts. Slides - E. Golovach
- Summary of RGK runs
- Pass2 and Pass1 DST and Train outputs
- old RGK trains
- Run Group K (Fall 18) Spreadsheet
- Helicity
- lund files
CHARGES |
---|
Charge #1: Is the quality of detector calibration and alignment adequate to achieve the performance specifications foreseen for CLAS12 or achievable at the current time, given the “state-of-the-art” calibration, alignment, and reconstruction algorithms? |
Charge #2: Is data quality as a function of run number or time for the data set proposed for cooking stable and understood? Have runs been classified in terms of type (empty target, calibration, special, production, …) and quality (golden run, known issues, …), and is a detailed list available? Based on validation studies, have all CLAS12 subsystem performances been understood and issues identified? |
Charge #3: Has a ‘Hardware (HW) status table (i.e., bad channel table) been compiled for use in the data and MC reconstructions? Has the efficiency versus beam current been studied? How does it compare to MC simulations with the merged background? Are the DAQ translation tables correcting for all known cable swaps? At what stage(s) in the software? |
Charge #4: Are analysis plans for the data set developed at adequate levels? Is the list of planned skims defined and tested running the analysis trains on preliminary data? Is all ancillary information helicity, Faraday Cup, … available and understood? |
Charge #5: Are the data processing tools that will be used adequate for the proposed processing task? Is the data management plan (staging area, tape destination, directory structure, logs, …) defined and appropriate given the available resources? Is the estimate of processing time per event available and resources needed to complete the task sound? |
Charge #6: Have the tools for monitoring the quality of the cooking output and identify/correct failures been defined and ready to be used? |
Charge #7: Is the person-power identified and in-place for the proposed data processing? |
Pass1 Review Documents
Pass 1 Readiness Review - June 5th
Bluejeans Link
- https://bluejeans.com/174945091
Program
Time | Topic | Speaker | |
---|---|---|---|
8:30-8:45 |
Annalisa | ||
Charge #1: Is the quality of detector calibration and alignment adequate to achieve the performance specifications foreseen for CLAS12 or achievable at the current time, given the « state of the art » calibration, alignment, and reconstruction algorithms? | |||
8:45-9:05 |
Daniel | ||
Charge #2: Is data quality as a function of run number or time for the data set that is proposed for pass1 cooking stable and understood? | |||
9:05-9:30 |
FX | ||
Charge #3: Are analysis plans for the data set developed at adequate levels? Is the list of planned skims defined and tested running analysis trains on preliminary data? Are preliminary analysis results for the main reaction channels and observable available and consistent with expectations? Is all ancillary information helicity, Faraday Cup, …) available and understood? | |||
Charge #4: Are data processing tools that will be used adequate for the proposed processing task? Is the data management plan ( staging area, tape destination, directory structure, logs, …) defined and appropriate given the available resources? Is the estimate of resources needed to complete the task sound? | |||
09:30-09:50 |
Nick | ||
9:50-10:20 |
Lucilla |
||
Charge #5: What are the plans for monitoring the quality of the cooking output and identify /correct failures? | |||
Charge #6: Is the manpower adequate for the proposed data processing? | |||
10:20-10:30 |
Annalisa |
Readiness Review Report
RG-K Pass1 Readiness Review Report
Link to the Overleaf Reply document
RG-K Pass1 Readiness Review Report Reply
Additional Documents and Links
RG-K Meeting Minutes
RG-K Meeting Minutes
Group meetings in 2024
Group meetings in 2023
Group meetings in 2022
Group meetings in 2021
Group meetings in 2020
Group meetings in 2019
Group meetings in 2017
January 6, 2017 | February 3, 2017 | March 3, 2017 |
Group meetings in 2016
September 9, 2016 | December 2, 2016 |
KY Analysis Work
Approach | Energy | Spectrum Fits |
Topology Summed 1D (2π bck) | 6.5 GeV | Q2, W, cthkcm |
Individual Topologies 1D (2π bck) | 6.5 GeV | Q2, W, cthkcm |
Topology Summed 1D (2π bck) | 7.5 GeV | Q2, W, cthkcm |
Individual Topologies 1D (2π bck) | 7.5 GeV | Q2, W, cthkcm |
Topology Summed 3D (2π bck) | 6.5 GeV | W |
Individual Topologies 3D (2π bck) | 6.5 GeV | W |
Topology Summed 3D (2π bck) | 7.5 GeV | W |
Individual Topologies 3D (2π bck) | 7.5 GeV | W |
Rome Approach 1D | 6.5 GeV | Q2, W, cthkcm |
Rome Approach 1D | 7.5 GeV | Q2, W, cthkcm |
Alt. Rome Approach 1D | 6.5 GeV | Q2, W, cthkcm |
Alt. Rome Approach 1D | 7.5 GeV | Q2, W, cthkcm |
Approach | Energy | Fits |
Topology Summed 1D | 6.5 GeV | ASM |
Individual Topologies 1D | 6.5 GeV | ASM |
Topology Summed 1D | 7.5 GeV | ASM |
Individual Topologies 1D | 7.5 GeV | ASM |
Topology Summed 3D | 6.5 GeV | ASM |
Individual Topologies 3D | 6.5 GeV | ASM |
Topology Summed 3D | 7.5 GeV | ASM |
Individual Topologies 3D | 7.5 GeV | ASM |
Rome Approach 1D | 6.5 GeV | ASM |
Rome Approach 1D | 7.5 GeV | ASM |
Alt. Rome Approach 1D | 6.5 GeV | ASM |
Alt. Rome Approach 1D | 7.5 GeV | ASM |
Two-Pion Analysis Work
RG-K Info
RG-K General Analysis Note:
RG-K analysis document pdf file October 19th 2021
RG-K analysis document pdf file April 22nd 2022 version
RG-K DVCS Analysis Note:
Target position
Target center coordinates: x=0 cm; y=0 cm; z=-3 cm
QA Timelines
https://clas12mon.jlab.org/rgk/pass1/qa/tlsummary/
RGK Chef
https://clasweb.jlab.org/wiki/index.php/RGK_chef_info
RGK Runs
RGK Chef
RGK chef
The RGK chef is Lucilla Lanza: the chef is responsible for data processing, including decoding, reconstruction, and trains. Please contact me for any issue, comment or question concerned with RGK data, lanza@jlab.org
How to login and reach the working directory
ssh clas12-4@ifarm cd users/user_name
To setup environment
source /group/clas12/packages/setup.csh module load clas12 module load workflow
Example of command
To decode file 5700:
clas12-workflow.py --runGroup rgk --tag pass1v0 --model dec --inputs "/mss/clas12/rg-k/data/clas_005700/clas_005700.evio.00*" --runs 5700 --decDir "/volatile/clas12/JLABNAME" --coatjava /group/clas12/packages/coatjava/6.5.13
where: /mss/clas12/rg-k/data/clas_*/*.0004* -> dec-> /cache/clas12/rg-k/production/decoded/6b.2.0/ -> rec -> /cache/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v0/dst/recon/-> ana -> /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v2/dst/train/
and
- outDir: final data location
- decDir: a directory for the decoded files, overrides outDir for decoding
- trainDir: a directory for the train files, overrides outDir for trains
As long as you run tests or some other temporary jobs (calibrations, timelines, etc), put everything on volatile, including rec and ana parts. Do not put anything on cache right now, pass2 will go there.
If you do not use option --submit, you will produce a json file that can be launched using commands:
swif2 import -file rgk-pass1v0.json
swif2 run rgk-pass1v0
To check the satus:
swif-status.py
IMPORTANT: You can exploit a config .json file, instead of writing all the information in the input line.
clas12-workflow.py --config calibRGK.json --runs 5733,5958
The config .json file contains the yaml file that is used for all the configuration. A list of yaml files employed for different tasks is reported at the end of this page. The yaml file has a "schema_dir" information. The selection of banks output during reconstruction is limited to those in the "schema_dir" defined in CLARA's YAML file. The analysis coordinator for your run group should know which schema to use (dst, dsthb, calibration, mon, full).
To establish state of works:
swif2 list
Or check the webpage: https://scicomp.jlab.org/scicomp/index.html#/farmJobs/activeJob
To see content of a jar file
jar -tvf ./myClara/plugins/grapes/lib/core/grapes-2.11-SNAPSHOT.jar
To cancel a failed job
swif2 cancel -delete -workflow rgk-ra-rgkCalibpass2-5733x2
Data files location
- Raw data
/mss/clas12/rg-k/data/
- Decoded
/lustre19/expphy/cache/clas12/rg-k/production/decoded/6b.2.0/
- Cooked
/cache/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v0/dst/recon/
/cache/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v0/dst/recon/
- Trains
- /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v9/train/
- /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v7/train/
What if Trains, Decoded or Cooked files get canceled?
A fundamental part of the JLab tape system is that the filesystem on tape and disk are presented the same except for the leading /mss (tape) and /cache (disk). If you list the corresponding directory on /mss, you can see if the files are there on tape. To restore canceled files you can copy them from tape to disk with the command:
jcache get /mss/clas12/rg-k/data/clas_005893/*
The json file that has been submitted to obtain tha trains is available as README.json in the directory where the trains are stored.
Yaml files location
Remember that the yaml file lines have to be alligned.
- Example of dst reco file:
/w/hallb-scifs17exp/clas12/rg-a/software/clara_data/modules/clara3p12-6p5p6/config/dst_06012020_1815.yaml
- Calib recon file:
/w/hallb-scifs17exp/clas12/rg-a/software/clara_data/modules/clara3p12-6bp5p1/config/calib_02042020_1200.yaml
/u/home/clas12-2/users/markov/configFiles/train_calib.yaml
/w/hallb-scifs17exp/clas12/rg-a/software/clara_data/modules/clara3p12-6bp5p1/config/monitor_02212020_1745.yaml
- and corresponding trains (only RF for "pass0" cook)
Timestamp variable inside YAML files
The timestamp variable has to take into account the last calibration constant into CCDB (calibration constant data base). Communication of updated variables should be provided by calibrators to the Run Coordinator and to the chef, who has to adjorn the timestamp of the relative detector into the yaml file. For instance if the new calibration constant of FT is produced on 07/18/2020-17:59:00, then the timestamp can be 07/18/2020-18:00:00. It is not necessary to adjorn all the other detectors timestamps as well, although different timestamps could be source of mistakes. A possible solution is to use a global definition of the timestamps. The timestamp that is corrently used is: 07/18/2020-18:00:00
Right now we have to use the timestamp that was used for the pass1 cooking, in order to capture all the final calibrations. Based on the configuration used for pass1 (see /cache/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v0/dst/recon/README.json and /cache/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV//pass1/v0/dst/recon/README.json) it seems the timestamp was set to 07/18/2020-18:00:00.
Updated timestamp
timestamp: 07/18/2020-18:00:00
How to test a custom wagon and run a workflow with it
If you want to test a new wagon, log in as clas12-4:
ssh clas12-4@ifarm
Go to the working directory:
cd users/user_name
Setup the environment:
module load clas12 source /group/clas12/packages/setup.csh module load workflow
Copy the directory with the list of the wagons in java (this is not always necessary):
git clone https://github.com/JeffersonLab/grapes
Insert the modified wagon into the proper directory and install:
cp TwoPionWagonRGK.java grapes/src/main/java/org/jlab/jnp/grapes/services/. cd grapes mvn install cd ..
Get clara directory into your working directory (this is not always necessary):
wget https://claraweb.jlab.org/clara/_downloads/install-claracre-clas.sh chmod +x install-claracre-clas.sh
Create and define other variables and directories that will be used in the procedure:
mkdir data mkdir data/log mkdir output setenv CLARA_HOME $PWD/myClara setenv CLARA_USER_DATA $PWD/data
Install clara with the proper version:
./install-claracre-clas.sh -f 5.0.2 -v 10.0.2 -g 2.15 -j 11
Insert the object with the new wagon into your new clara directory:
cp grapes/target/grapes-2.8-SNAPSHOT.jar myClara/plugins/grapes/lib/core/grapes-2.11-SNAPSHOT.jar
Test the new wagon you need to create a list of input files: files.txt (ex: rec_clas_005889.evio.00000-00004.hipo)
$CLARA_HOME/plugins/grapes/bin/clara-grapes train_test.clara
If this works you can try to run the train:
clas12-workflow.py --runGroup rgk --model ana --tag rgkTwoPion --inputs /cache/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v0/dst/recon/ --runs 5700 --outDir /volatile/clas12/rg-k/production/recon/pass0/calib/v71/ --clara $PWD/myClara/ --trainYaml /u/home/clas12-4/users/lanza/train_test.yaml
(note: ceate a new directory for the output files ex: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v5 in which the clas12-workflow will generate the train directory. You may add files only if the yaml configuration file is unchanged)
Other chef duties
Since a large part of data is saved in /cache and /volatile spaces, it is necessary to "refresh" files by command touch on /volatile:
touch file
and by pin on /cache:
jcache pin file1 file2 ... fileN [-D days] [-x] --- pin specified files for a given days (default 7 days).
In any case files from /cache can be taken again from silo.
If you need a customized schema (besides dst/calib/mon) you can create a directory with the banks you need copying from the proper directory (remember to add a -L or you will copy the link only and a SLURM_FAILED will result).
Problems
A list of issues is available here:
SWIF_INPUT_FAIL means the system couldn't get the input file and is something that should be assumed isn't going to just recover by retrying the job. In general AUGER problems may be resubmitted without changing anything with:
swif2 retry-jobs -workflow rgk-ra-rgkCalibPass2-5733x2 -problems AUGER-TIMEOUT
To have more details about the problems you can use:
swif-status.py --problems
Other info
Calibration teams: list.
Cooked Files History
What | json file | yaml file | CLARA | Coatjava | When | Runs | Exit Status | Note |
---|---|---|---|---|---|---|---|---|
cook and skim for calibration | file | file | 4.3.12 | 6.5.13 | 07/02/21 | 5733, 5958 | Failed, SWIF-USER-NON-ZERO, AUGER-TIMEOUT | First attempt to cook and skim for calibration the two files |
cook and skim for calibration | file | file | 4.3.12 | 6.5.13 | 07/04/21 | 5733, 5958 | Failed, SWIF-USER-NON-ZERO | Corrected timestamp and reconstruction yaml coatjava |
cook and skim for calibration | file | file | 4.3.12 | 6.5.13 | 07/05/21 | 5733, 5958 | Succeeded | Corrected decoded files location |
skim a new wagon "TwoPionRGK" | command line | file | 4.3.12 | 6.5.13 | 10/26/21 | 5700 | Failed, SWIF-USER-NON-ZERO | First attempt to run a new wagon |
skim a new wagon "TwoPionRGK" | command line | file | 4.3.12 | 6.5.13 | 10/26/21 | 5700 | Failed, SWIF-USER-NON-ZERO | Second attempt to run a new wagon, no changes, tried to reinstall Clara |
skim a new wagon "TwoPionRGK" | command line | file | 4.3.12 | 6.5.13 | 10/28/21 | 5700 | Succeeded | Corrected the yaml file, trains are accepted from (0-31) or from (1-32) |
modify wagon "TwoPionRGK" and run it with "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.13 | 11/11/21 | 5700 | Succeeded | Just two modifies with respect to the previous workflow: addition of a second train (that I called 29) and changed the electron selection in E. Golovach train. |
modify wagon "TwoPionRGK" to consider all the particles combinations, cut on MM2 and run it with "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.13 | 11/22/21 | 5700 (7.540 GeV), 5889-005905-5917-5935-5957 (6.53536 GeV) | Succeeded | Modified TwoPionRGK.java with respect to the previous workflow: added combinations to cut on MM2 (cuts introduced by E. Golovach). |
modify wagon "TwoPionRGK" to consider all the particles combinations, cut on MM2, limit on particles multiplicity and run it with "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.13 | 11/24/21 | 5700 (7.540 GeV), 5889-005905-5917-5935-5957 (6.53536 GeV) | Succeeded | Modified TwoPionRGK.java with respect to the previous workflow: added multiplicity cut (7 hadrons). |
modify wagon "TwoPionRGK" to consider all the particles combinations, cut on MM2, limit on particles multiplicity, chi2pid cut (5) and run it with "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.13 | 11/25/21 | 5700 (7.540 GeV), 5889 (6.53536 GeV) | Succeeded | Modified TwoPionRGK.java with respect to the previous workflow: added chi2pid cut (5) and excluded events without REC::Particle bank. |
re-run trains (missing runs in skims files) | 6.5 GeV file and 7.5 GeV file | 6.5 GeV file and 7.5 GeV file | 4.3.12 | 6.5.6.2 | 1/17/22 | all (7.540 GeV), all (6.53536 GeV) | Succeeded | Employed README.json file from directory. |
modify wagon "TwoPionRGK" to change the window around MM2(e pip pim) to 0.4 - 1.6 GeV2 (previously we had 0.6 - 1.3 GeV2 ) and run it with "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.13 | 02/03/22 | 5889-005905-5917-5935-5957 (6.53536 GeV) | Succeeded | Modified TwoPionRGK.java with respect to the previous workflow: changed the MM2(e pip pim) window. From this workflow we have also migrated to swif2. |
use the wagon "TwoPionRGK" with the window around MM2(e pip pim) to 0.6 - 1.3 GeV2 on all 6.5 GeV files. | command line | file | 4.3.12 | 6.5.13 | 05/14/22 | all 6.53536 GeV files | Bad Banks - removed | rgk-a-rgkTwoPion-5875x108.json.json workflow output directory: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v4/train/skim30/. |
use the wagons "TwoPionRGK" with the window around MM2(e pip pim) to 0.6 - 1.3 GeV2 and "TwoPion" from K. Neupane on all 6.5 GeV runs | command line | file | 4.3.12 | 6.5.6.2 | 06/16/22 | all 6.53536 GeV files | Succeeded | rgk-a-TwoPion65-5875x108.json workflow output directory: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v5/train/skim30/ and /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v5/train/skim29/ |
Re-run 6.5GeV trains | command line | file | 4.3.12 | 6.5.6.2 | 07/19/22 | all 6.53536 GeV files | Succeeded | rgk-a-TwoPion65-5875x108.json workflow output directory: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v7/train/ |
Re-run 7.5GeV trains | command line | file | 4.3.12 | 6.5.6.2 | 07/27/22 | all 7.546 GeV files | Succeeded | rgk-a-rgkTrains75-5674x154.json workflow output directory: /volatile/clas12/rg-k//production/recon/fall2018/torus+1/7546MeV/pass1/v7/train/ |
use the wagons "TwoPionRGK" with the window around MM2(e pip pim) to 0.6 - 1.3 GeV2 and "TwoPion" from K. Neupane on all 7.5 GeV runs | command line | twoPion_7.5.yaml file | 4.3.12 | 6.5.6.2 | 03/08/22 | all 7.546 GeV files | Succeeded | rgk-a-twoPion_75-5674x154.json workflow output directory: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v5/train/skim30/ and /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v5/train/skim29/ |
pass0 for 6.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 11/29/22 | 6.5 GeV 10 files per run, see filelist_65.sh | Succeeded | CVT alignment done. 6.5 GeV pass0. |
pass0 for 7.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 11/29/22 | 7.5 GeV 10 files per run, see filelist_75.sh | Succeeded | CVT alignment done. 7.5 GeV pass0. |
Timelines for 6.5 RGK data | --- | --- | --- | --- | 11/29/22 | --- | --- | Timelines for 6.5 GeV RGK data following instructions at https://github.com/JeffersonLab/clas12-timeline |
pass0 for 6.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/06/22 | 6.5 GeV 10 files per run, see filelist_65.sh | Succeeded | Modified data.yaml, CCDB table has been updated (https://logbooks.jlab.org/entry/4096591) |
pass0 for 7.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/06/22 | 7.5 GeV 10 files per run, see filelist_75.sh | Succeeded | Modified data.yaml, CCDB table has been updated (https://logbooks.jlab.org/entry/4096591) |
pass0 for 3 full files to be used for beam offset calibration | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/09/22 | 5733, 5958, 5997 | Succeeded | To produce Timelines with beam offset correction |
pass0 for 14 files to be used for DC calibration - first 3 files for each run | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/22/22 | 5715, 5735, 5740, 5761, 5813, 5835, 5844, 5851, 5866, 5897, 5941, 5953, 5965, 5984 | Succeeded | To extract DC calibration |
pass0 for 6.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/22/22 | 6.5 GeV files | Succeeded | Double check |
pass0 for 7.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 12/22/22 | 7.5 GeV files | Succeeded | Double check |
pass0 for 3 full files to be used for beam offset calibration (depends on luminosity) | command line | data.yaml file | 5.0.2 | 8.3.2 | 01/02/23 | 5875, 5885, 5813 | Succeeded | Jumps in the vz position due to changes in current in the timelines. Does this depend on luminosity? We cooked two runs at the extremes of luminosity to check. |
Iteration - pass0 for 14 files to be used for DC calibration - first 3 files for each run | command line | same data.yaml, timestamp updated: 12/21/2022-16:30:00 | 5.0.2 | 8.3.2 | 01/21/23 | 5715, 5735, 5740, 5761, 5813, 5835, 5844, 5851, 5866, 5897, 5941, 5953, 5965, 5984 | Succeeded | To extract DC calibration, iteration, logentry https://logbooks.jlab.org/entry/4112179 |
pass0 for 6.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 01/19/23 | 6.5 GeV files | Succeeded | After Florian's DC T00, iteration, logentry https://logbooks.jlab.org/entry/4112179 |
pass0 for 7.5 RGK data | command line | data.yaml file | 5.0.2 | 8.3.2 | 01/19/23 | 7.5 GeV files | Succeeded | After Florian's DC T00, iteration, logentry https://logbooks.jlab.org/entry/4112179 |
pass0 for 3 full files to be used for beam offset calibration | command line | same data.yaml, updated timestamp: 01/19/2023 | 5.0.2 | 8.3.2 | 01/19/23 | 5733, 5958, 5997 | Succeeded | Produced again files that were deleted on volatile |
cook and skim for calibration | file | file | 5.0.2 | 8.3.2 | 01/26/23 | 5715, 5735, 5740, 5761, 5813, 5835, 5844, 5851, 5866, 5897, 5941, 5953, 5965, 5984 | Succeeded | Cook and skim for DC calibration |
pass0 for 14 files to be used for DC calibration - first 3 files for each run | command line | same data.yaml, timestamp updated: 01/27/2023-14:00:00 | 5.0.2 | 8.3.2 | 01/27/23 | 5715, 5735, 5740, 5761, 5813, 5835, 5844, 5851, 5866, 5897, 5941, 5953, 5965, 5984 | Succeeded | To extract DC calibration - sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite |
pass0 for 6 full files to be used for beam offset calibration | command line | same data.yaml, updated timestamp:02/07/23 17:50:00 | 5.0.2 | 8.3.2 | 02/07/23 | 5733, 5958, 5997, 5875, 5885, 5813 | Succeeded | Updated CCDB (https://logbooks.jlab.org/entry/4126322), the 6 calibration runs are cooked for Mariana to perform a second calibration iteration. |
pass0 for 2 files of run 5733 to be used for beam offset calibration | command line | same data.yaml, updated timestamp: 02/15/2023-17:00:00 | 5.0.2 | 8.3.2 | 02/15/2023 and 02/18/2023 | 5733 | Succeeded | Produced both with mon and calib options in the data.yaml file |
skim a new wagon "resIncl", corresponding to skim23 | command line | file | 4.3.12 | 6.5.13 | 02/16/2023 | 5875-5880 | Succeeded | Following P. Chatagnon request |
pass0 for 2 files of run 5733 to be used for beam offset calibration | command line | same data.yaml, updated timestamp: 02/15/2023-17:00:00 | 5.0.2 | 8.5.0 | 02/20/2023 | 5733 | Succeeded | Attempt with new software release |
pass0 for 2 files of run 5733 to be used for beam offset calibration | command line | same data.yaml, updated timestamp: 02/15/2023-17:00:00 | 5.0.2 | 8.3.2 | 02/20/2023 | 5733 | Succeeded | To allow Mariana to extract new calibration constants |
pass0 for full run 5733 to be used for beam offset calibration | command line | same data.yaml, updated timestamp: 02/15/2023-17:00:00 | 5.0.2 | 8.3.2 | 02/22/2023 | 5733 | Succeeded | To allow Mariana to extract new calibration constants |
pass0 for 14 files to be used for DC calibration - first 3 files for each run | command line | same data.yaml, timestamp: 02/23/2023-04:00:00 | 5.0.2 | 8.3.2 | 02/23/23 | 5715, 5735, 5740, 5761, 5813, 5835, 5844, 5851, 5866, 5897, 5941, 5953, 5965, 5984 | Succeeded | To extract DC calibration - sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite |
pass0 for 6.5 GeV RGK dataset to be used for DC calibration | command line | same data.yaml, timestamp: 02/27/2023-10:00:00 | 5.0.2 | 8.3.2 | 02/27/23 | all 6.53536 GeV files | Succeeded | To extract DC calibration - sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite |
pass0 for 7.5 GeV RGK dataset to be used for DC calibration | command line | same data.yaml, timestamp: 02/27/2023-10:00:00 | 5.0.2 | 8.3.2 | 02/27/23 | all 7.546 GeV files | Succeeded | To extract DC calibration - sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite |
pass0 for 6.5 GeV RGK dataset to be used for DC calibration | command line | same data.yaml, timestamp: 02/28/2023-17:00:00 | 5.0.2 | 8.6.0 | 02/28/23 | all 6.53536 GeV files | Succeeded | To extract DC calibration |
pass0 for 7.5 GeV RGK dataset to be used for DC calibration | command line | same data.yaml, timestamp: 02/28/2023-17:00:00 | 5.0.2 | 8.6.0 | 02/28/23 | all 7.546 GeV files | Succeeded | To extract DC calibration |
pass0 for 6.5 GeV RGK dataset | command line | same data.yaml, timestamp: 03/05/2023-17:00:00, mon | 5.0.2 | 8.6.0 | 03/08/23 | all 6.53536 GeV files | Succeeded | To double check DC and CVT calibrations and to extract FTOF calibration |
pass0 for 7.5 GeV RGK dataset | command line | same data.yaml, timestamp: 03/05/2023-17:00:00, mon | 5.0.2 | 8.6.0 | 03/08/23 | all 7.546 GeV files | Succeeded | To double check DC and CVT calibrations and to extract FTOF calibration |
FTOF calibration | command line | same data.yaml, timestamp: 03/05/2023-17:00:00, mon | 5.0.2 | 8.6.0 | 03/08/23 | 5683, 5700, 5733, 5756, 5768, 5769, 5792, 5813, 5823, 5877, 5893, 5958, 5986, 5987, 5995, 5997 | Succeeded | To double check DC and CVT calibrations and to extract FTOF calibration |
Re-run 7.5GeV trains | command line | file | 4.3.12 | 6.5.6.2 | 09/03/23 | all 7.546 GeV files | Succeeded | rgk-a-rgkTrains75-5674x154.json workflow output directory: /volatile/clas12/rg-k//production/recon/fall2018/torus+1/7546MeV/pass1/v7/train/ |
pass0 for 6.5 GeV RGK dataset | command line v0.9 | same data.yaml, timestamp: 03/11/2023-17:00:00, mon | 5.0.2 | 8.6.0 | 03/11/23 | all 6.53536 GeV files | Succeeded | To double check FTOF calibration, https://logbooks.jlab.org/entry/4147797 |
pass0 for 7.5 GeV RGK dataset | command line v0.9 | same data.yaml, timestamp: 03/11/2023-17:00:00, mon | 5.0.2 | 8.6.0 | 03/11/23 | all 7.546 GeV files | Succeeded | To double check FTOF calibration, https://logbooks.jlab.org/entry/4147797 |
RF calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 03/17/23 | 5702, 5845, 5962 | Succeeded | high lumi runs for RF calibration, see logentry |
pass0 for 6.5 GeV RGK dataset | command line v0.10 | same data.yaml, timestamp: 03/20/2023-10:00:00, mon | 5.0.2 | 8.6.0 | 03/20/23 | all 6.53536 GeV files | Succeeded | To double check RF calibration |
pass0 for 7.5 GeV RGK dataset | command line v0.10 | same data.yaml, timestamp: 03/20/2023-10:00:00, mon | 5.0.2 | 8.6.0 | 03/20/23 | all 7.546 GeV files | Succeeded | To double check RF calibration |
CTOF calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 03/23/23 | 5681, 5700, 5733, 5756, 5768, 5769, 5794, 5813, 5877, 5879, 5893, 5940, 5980, 5987, 5997 | Succeeded | To extract CTOF calibration |
HTCC calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 03/24/23 | 5886, 5998, 5675 | Succeeded | To extract HTCC calibration, updated timestamp, see logentry |
pass0 for 6.5 GeV RGK dataset | command line v0.11 | same data.yaml, timestamp: 03/20/2023-10:00:00, mon | 5.0.2 | 8.6.0 | 03/20/23 | all 6.53536 GeV files | Succeeded | To double check HTCC calibration |
pass0 for 7.5 GeV RGK dataset | command line v0.11 | same data.yaml, timestamp: 03/20/2023-10:00:00, mon | 5.0.2 | 8.6.0 | 03/20/23 | all 7.546 GeV files | Succeeded | To double check HTCC calibration |
HTCC calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 03/24/23 | 5674, 5756, 5812, 5880, 5883 | Succeeded | To extract HTCC calibration, updated timestamp, see logentry |
SVT calibration | command line | data.yaml 04/02/2023-17:00:00 | 5.0.2 | 8.6.0 | 04/03/23 | 5689, 5690, 5691, 5692, 5693 | Succeeded | To extract SVT calibration |
FT calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/03/23 | 5698, 5699, 5700, 5701, 5702, 5703, 5704, 5705, 5706, 5707 | Succeeded | To extract FT calibration |
FT-Hodo calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/03/23 | 5756 | Succeeded | To extract FT-HODO calibration |
HTCC calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/03/23 | 5877, 5879 | Succeeded | To extract HTCC calibration |
6.5 GeV RGK dataset trains | config file | --- | 4.3.12 | 6.5.6.2 | 04/05/23 | all 6.53536 GeV files | Succeeded | To restore 6.5 GeV trains, output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v7/train/ |
pass0 for 6.5 GeV RGK dataset | command line | data.yaml | 5.0.2 | 8.6.0 | 04/05/2023-15:00:00 | all 6.53536 GeV files | Succeeded | To double check HTCC calibration |
pass0 for 7.5 GeV RGK dataset | command line | data.yaml | 5.0.2 | 8.6.0 | 04/05/2023-15:00:00 | all 7.546 GeV files | Succeeded | To double check HTCC calibration |
CND calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/11/2023-17:00:00 | 5689, 5690, 5691, 5692, 5693 | Succeeded | To extract CND calibration |
FT calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/12/2023-07:00:00 | 5698, 5699, 5700, 5701, 5702, 5703, 5704, 5705, 5706, 5707 | Succeeded | To extract FT calibration |
FT-Hodo calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/11/2023-17:00:00 | 5749 | Succeeded | To extract FT-HODO calibration |
FT calibration | command line | data.yaml | 5.0.2 | 8.6.0 | 04/15/2023-17:00:00 | 5681,5756,5813 | Succeeded | To extract FT calibration |
pass0 for 6.5 GeV RGK dataset | command line v0.13 | same data.yaml, timestamp: 04/17/2023-17:00:00, mon | 5.0.2 | 8.7.1 | 04/17/23 | all 6.53536 GeV files | Succeeded | New software version |
pass0 for 7.5 GeV RGK dataset | command line v0.13 | same data.yaml, timestamp: 04/17/2023-17:00:00, mon | 5.0.2 | 8.7.1 | 04/17/23 | all 7.546 GeV files | Succeeded | New software version |
rerun skim29 "TwoPion" from K. Neupane | command line | file | 4.3.12 | 6.5.6.2 | 04/18/23 | all 6.53536 GeV | Succeeded | output /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v10 |
Re-run 7.5GeV trains | command line | file | 4.3.12 | 6.5.6.2 | 04/18/23 | all 7.546 GeV files | Succeeded | output: /volatile/clas12/rg-k//production/recon/fall2018/torus+1/7546MeV/pass1/v7/train/ |
AI training, see instructions | command line | file | 5.0.2 | 8.7.1 | 04/19/23 | 5700, 5901 | Succeeded | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/AItraining |
pass0 for 6.5 GeV RGK dataset | command line | data.yaml data.yaml | 5.0.2 | 8.7.1 | 04/27/23 | all 6.53536 GeV files | Succeeded | New software version |
pass0 for 7.5 GeV RGK dataset | command line | data.yaml | 5.0.2 | 8.7.1 | 04/27/23 | all 7.546 GeV files | Succeeded | New software version |
rerun skim11 "ElecFTkaonWagon" | command line | file | 5.0.2 | 8.7.1 | 04/27/23 | 5700 | Failed, SITE_PREP_FAIL, rerunned in two steps | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v11 |
AI training, see instructions | command line | file | 5.0.2 | 8.7.1 | 05/02/23 | 5993, 5683 | Succeeded | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/AItraining1 |
CND calibration | command line | data.yaml | 5.0.2 | 8.7.1 | 05/01/23 | 5879 | Succeeded | To extract CND calibration for one lumi scan run |
AI training proceeds, see instructions | command line | file | 5.0.2 | 9.0.0 | 05/04/23 | 5884 | Succeeded | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_AI/ |
rerun 7.5 GeV trains | command line | file | 5.0.2 | 8.7.1 | 05/04/23 | 5700 | Succeeded | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v11 |
rerun skim11 "rgk-ra-skim11try2-5704x4" | command line | file | 5.0.2 | 9.0.0 | 05/09/23 | 5704, 5708, 5718, 5720 | Failed, SITE_PREP_FAIL, rerunned in two steps | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v12/mon/recon/ |
rerun 7.5 GeV trains | command line | file | 5.0.2 | 9.0.0 | 05/09/23 | 5704, 5708, 5718, 5720 | Succeeded | output: /volatile/clas12//rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v12/ |
pass0 for 6.5 GeV RGK dataset | command line v0.16 | data.yaml, timestamp: 05/10/2023-05:00:00, mon | 5.0.2 | 9.0.0 | 05/10/23 | all 6.53536 GeV files | Succeeded | New software version |
pass0 for 7.5 GeV RGK dataset | command line v0.16 | data.yaml, timestamp: 05/10/2023-05:00:00, mon | 5.0.2 | 9.0.0 | 05/10/23 | all 7.546 GeV files | Succeeded | New software version |
rerun skim11 "rgk-r-skim11try3-5704x4" | command line | file | 5.0.2 | 9.0.0 | 05/10/23 | 5704, 5708, 5718, 5720 | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass1/v13/ | |
rerun 7.5 GeV trains | command line | file | 5.0.2 | 9.0.0 | 05/11/23 | 5704, 5708, 5718, 5720 | Succeeded | output: /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass1/v13 |
AI | command line | [ file] | 5.0.2 | 9.0.0 | 05/22/23 | 5700, 5901, 5983, 5883, rgb run | Succeeded | forgot bank in directory rerunned AI |
SIDIS 7.5 GeV | command line | file | --- | --- | 05/29/23 | 5700 | Succeeded | SIDIS |
AI | command line | recana | 5.0.2 | 9.0.0 | 05/22/23 | 5700, 5901, 5983, 5883, rgb run | Succeeded | yaml file name must be different for each workflow |
AI | command line | recana | 5.0.2 | 9.0.0 | 05/30/23 | Networks: 5700, 5901, 5983, 5883, rgb run, Files: 5856, 5920, 5986 | Succeeded | The procedure has been repeated for runs having different beam energy and current. |
Florian | command line | yaml file | 5.0.2 | 9.0.0 | 06/22/23 | SITE_PREP_FAIL | We did not wait the AI to be completed. The full schema is too large. | |
DVCS trains | command line | file | --- | --- | 06/16/23 | 5700, 5901 | Succeeded | 19 and 24 |
denoise | command line | file | --- | 9.0.1 | 06/29/23 | 5920 | Succeeded | neural network 5901 |
denoise | command line | file | --- | 9.0.1 | 07/02/23 | 5704 | Succeeded | neural network 5901 |
pass0 | command line | file | 5.0.2 | 9.0.1 | 07/14/23 | all 6.5 and 7.5 datasets | Succeeded | attempting last pass0 |
cook and skim no denoising | command line | file | 5.0.2 | 9.0.1 | 07/14/23 | 5682,5696,5700,5708,5734,5791,5901,5906,5913,5920,5986,5990 | Succeeded | wrong coatjava version |
cook and skim denoising | command line | file | 5.0.2 | 9.0.1 | 07/14/23 | 5901,5906,5913,5920,5986,5990 | Succeeded | wrong coatjava version |
pass0 | command line | file | 5.0.2 | 10.0.2 | 07/15/23 | all 6.5 and 7.5 datasets | Succeeded | attempting last pass0 |
cook and skim no denoising | command line | file | 5.0.2 | 10.0.2 | 07/15/23 | 5682,5696,5700,5708,5734,5791,5901,5906,5913,5920,5986,5990 | Succeeded | Skim was not successful |
cook and skim denoising | command line | file | 5.0.2 | 10.0.2 | 07/15/23 | 5901,5906,5913,5920,5986,5990 | Succeeded | Skim was not successful |
skim denoising and no denoising | command line | - | - | - | 07/19/23 | - | Succeeded | Skim was not successful previously. New attempt. |
skim denoising and no denoising | command line | - | 5.0.2 | 10.0.2 | 07/26/23 | - | Succeeded | Skim was not successful previously. New attempt. |
Gagik | command line | - | 5.0.2 | 10.0.2 | 07/28/23 | 5700,5901 | Succeeded | ... |
Florian | command line | - | 5.0.2 | 10.0.2 | 07/28/23 | 5700, 5901 | Succeeded | ... |
pass0 | command line | file | 5.0.2 | 10.0.2 | 08/05/23 | all 6.5 and 7.5 datasets | Succeeded | attempting last pass0 with double events |
Validation | command line | - | 5.0.2 | 10.0.2 | 08/09/23 | 5689,5690,5691,5692,5693,5707,5848,5875,5877,5879,5885,5913 | Succeeded | ... |
Pass2 | command line | - | 5.0.2 | 10.0.2 | 08/30/23 | all the runs | Succeeded | ... |
Neupane and SIDIS test | command line | 6gev 7gev | 5.0.2 | 10.0.2 | 10/30/23 | 5700, 5901 | Succeeded | ... |
Neupane and SIDIS test | command line | 6gev 7gev | 5.0.2 | 10.0.2 | 11/02/23 | all the runs | Succeeded | ... |
Random Trigger Runs | command line | reconYaml | 5.0.2 | 10.0.5 | 12/16/23 | 19204, 19205, 19206, 19208 | Succeeded | ... |
DC HV Runs | command line | reconYaml | 5.0.2 | 10.0.5 | 12/17/23 | 19220 | Succeeded | timestamp: 12/16/2023-02:00:00 |
Pin Runs To be Calibrated | command line | reconYaml | 5.0.2 | 10.0.5 | 12/18/23 | 19220, 19222, 19223, 19224, 19225, 19226, 19228, 19229 | Succeeded | timestamp: 12/17/2023-16:00:00 |
pass0 and timelines | command line | mon | 5.0.2 | 10.0.5 | 12/18/23 | 19209,19210,19211,19212,19213,19214,19215,19216,
19217,19218,19219,19231,19232,19233,19234,19235 |
Succeeded | --- |
Random Trigger Runs | command line | [timestamp: 12/18/23:16:00:00] | 5.0.2 | 10.0.5 | 12/19/23 | 19254 | Succeeded | |
First 10m runs of run 19239 | command line | calib | 5.0.2 | 10.0.5 | 12/20/23 | 19239 | Succeeded | timestamp: 12/20/23:06:00:00 |
DC HV Runs for DC T2D calibration | command line | calib | 5.0.2 | 10.0.5 | 12/20/23 | 19220-19224 | Succeeded | timestamp: 12/20/23:06:00:00 |
HTCC behavior with inverted solenoid polarity | command line | calib | 5.0.2 | 10.0.5 | 12/24/23 | 19259 | Succeeded | timestamp: 12/24/23:06:00:00 |
Cooking after T0 calibration is updated in the CCDB | command line | calib | 5.0.2 | 10.0.5 | 12/29/23 | 19239 | Succeeded | timestamp: 12/29/23:06:00:00 |
pass0 and timelines | command line | mon | 5.0.2 | 10.0.5 | 12/29/23 | 19209,19210,19211,19212,19213,19214,19215,
19216,19217,19218,19219,19231,19232,19233,19234, 19235,19220,19223,19221,19222,19224,19249,19250, 19252,19257,19256,19258,19259,19260,19239 |
Succeeded | timestamp: 12/29/23:06:00:00 |
pass0 and timelines | command line | mon | 5.0.2 | 10.0.5 | 01/03/24 | 19220, 19222, 19223, 19224,19239 | Succeeded | timestamp: 01/03/24:06:00:00 |
Run 19239 cooked with a local sqlite file to investigate weird behavior of residuals in R3 | command line | calib | 5.0.2 | 10.0.5 | 01/04/24 | 19239 | Succeeded | timestamp: 01/04/24:06:00:00 |
full run cooking with denoise and AI | command line | command line | 5.0.2 | 10.0.5 | 01/07/24 | 19220-19224, 19239, 19234, 19259 | Succeeded | timestamp: 01/07/24:06:00:00, dst schema |
full run cooking with denoise and AI | command line | command line | 5.0.2 | 10.0.5 | 01/07/24 | 19220-19224, 19239, 19234, 19259 | Succeeded | timestamp: 01/07/24:06:00:00, dcalign schema |
pass0 | command line | command line | 5.0.2 | 10.0.5 | 01/07/24 | 19324,19325,19326 | Succeeded | timestamp: 01/13/24:06:00:00, mon schema |
Cooking for DC, custom schema | command line | calib+ DC:tdc | 5.0.2 | 10.0.5 | 1/14/24 | 19327,19328,19329 | Succeeded | timestamp: 01/13/2024-06:00:00 |
Cooking for Raffaella | command line | calib | 5.0.2 | 10.0.5 | 01/15/24 | 19220,19258 | Succeeded | timestamp: 01/15/2024-06:00:00 |
Cooking for Raffaella | command line | calib | 5.0.2 | 10.0.5 | 01/15/24 | 19333 | Succeeded | timestamp: 01/15/2024-06:00:00 |
Cooking for Florian | command line | full, decrec | 5.0.2 | 10.0.5 | 01/16/24 | 19327,19328,19329 | Succeeded | timestamp: 01/16/2024-06:00:00 |
Cooking for Axel | command line | calib, decrecana | 5.0.2 | 10.0.5 | 01/17/24 | 19353 | Succeeded | timestamp: 01/17/2024-06:00:00, in a following cooking we used physics trains and dust as schema |
Cooking for Florian | command line | calib, decrecana | 5.0.2 | 10.0.5 | 01/18/24 | 19220,19258,19326,19333 | Succeeded | timestamp: 01/18/2024-12:00:00 |
pass0 for timelines | command line | calib, decrecana | 5.0.2 | 10.0.5 | 01/19/24 | all | Succeeded | timestamp: 01/19/2024-18:00:00 |
pass0 for timelines | command line | mon, decrecqtl | 5.0.2 | 10.0.5 | 01/29/24 | January runs | Succeeded | timestamp: 01/29/2024-06:00:00 |
Calib for Florian | command line | cali, decrecana | 5.0.2 | 10.0.5 | 01/31/24 | January runs | Succeeded | timestamp: 01/31/2024-12:00:00 |
Cooking for Josh, elastic train file 5700 | command line | customwagon, physics, ana | --- | --- | 02/05/24 | 5700 | Succeeded | --- |
Cooking for Josh, elastic train file 5700 | command line | customwagon, physics, ana | 5.0.2 | 10.0.2 | 02/15/24 | 5700 | Succeeded | --- |
Cooking for Dan | command line | decrecana, calib | 5.0.2 | 10.0.6 | 02/15/24 | 19669 | Succeeded | timestamp: 02/15/2024-12:00:00 |
Cooking for Tyson | command line | decrecana, calib | 5.0.2 | 10.0.6 | 02/15/24 | 19623,19624,19626 | Succeeded | timestamp: 02/15/2024-12:00:00 |
Elastic skim for Josh | command line | 6gev, 7gev | 5.0.2 | 10.0.2 | 02/17/24 | all the runs | Never launched | CustomWagon, ana |
Cook and Skim physics 6.4 GeV | command line | decrecana,dcalign | 5.0.2 | 10.0.6 | 02/17/24 | 19334, 19335, 19336, 19337, 19339, 19340, 19341, 19343, 19348, 19349 | Failed | timestamp: 02/17/2024-12:00:00, wrong schema |
Cook and Skim physics 6.4 GeV | command line | decrecana,dst | 5.0.2 | 10.0.6 | 02/18/24 | 19334, 19335, 19336, 19337, 19339, 19340, 19341, 19343, 19348, 19349 | Succeeded | timestamp: 02/18/2024-12:00:00 |
Cooking for Josh, elastic train file 5700 | command line | customwagon, physics, ana | 5.0.2 | 10.0.2 | 02/18/24 | 5700 | Succeeded | --- |
Cooking for Josh, elastic train file 5901 | command line | customwagon, physics, ana | 5.0.2 | 10.0.2 | 02/19/24 | 5901 | Succeeded | --- |
Elastic skim for Josh | command line | 6gev, 7gev | 5.0.2 | 10.0.2 | 02/27/24 | 10 6.5 GeV runs, 15 7.5 GeV runs | Succeeded | CustomWagon, ana |
Cooking for Daniel | command line | decrecana, calib | 5.0.2 | 10.0.6 | 02/27/24 | 19669 | Succeeded | timestamp: 02/27/2024-12:00:00 |
Assessing 4 passes high current run | command line | decrecana, calib | 5.0.2 | 10.0.6 | 03/04/24 | 19850 | Succeeded | timestamp: 03/04/2024-16:00:00 |
Cook and Skim physics 8.5 GeV | command line | decrecana,dst | 5.0.2 | 10.0.6 | 03/08/24 | 19676,19677,19678,19685,19688,19689,19690,19694,19699,19706 | Succeeded | timestamp: 03/08/2024-06:00:00 |
Corrupted Files
Which file | Quality | hipo-utils -dump | dimension | user |
---|---|---|---|---|
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005718/dst_clas_005718.evio.00790-00794.hipo | golden | corrupted | clas12-2 | ... |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005702/dst_clas_005702.evio.00915-00919.hipo | LossFT[1] | ok | clas12-2 | 145K |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005702/dst_clas_005702.evio.00935-00939.hipo | LossFT[1] | corrupted | clas12-2 | ... |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005702/dst_clas_005702.evio.01030-01034.hipo | LossFT[1] | corrupted | clas12-2 | ... |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005702/dst_clas_005702.evio.01020-01024.hipo | LossFT[1] | corrupted | clas12-2 | ... |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005702/dst_clas_005702.evio.00770-00774.hipo | LossFT[1] | corrupted | clas12-2 | ... |
/lustre19/expphy/cache/clas12/rg-k/production/reconstructed/Fall2018/Torus+1/pass1/v1/005732/dst_clas_005732.evio.00235-00239.hipo | golden | ok | clas12-2 | 177K |
Back to the RG-K wikipage
Link to Cheffing Info wikipage
Link to Calibration Procedure page
Data Calibration
Pass0 Calibration Timelines
Link to the pass0 timelines for pass1 Readiness Review RG-K timelines
Link to the RGK chef page [14].
Instructions for online analysis fall 2023
clas12-workflow.py --runGroup rgk --model decmrgrecanaqtl --tag monitoring --inputs /cache/clas12/rgk/data/ --runs 19200 --outDir /volatile/clas12/rg-k/production/pass0.0/study_type/ --coatjava 10.0.5 --reconYaml /u/home/clas12-4/users/lanza/rgk_monitoring.yaml --trainYaml calib
where:
--inputs: there are two types of files here directly copied from SILO (i.e. mss), the pin ones are full runs, the other ones are only the first 10 files for the run that are useful for pass0 only. --reconYaml: variation rgd_fall2023
Consider the list of yaml files at https://github.com/JeffersonLab/clas12-config/tree/rgdChef/workflow/rgd/10.0.4. and at https://github.com/JeffersonLab/clas12-config/tree/rgk/coatjava/10.0.5 You will find cv (conventional, not ai) and data (not mc) yaml that are important for our studies. Moreover you will find calib/mon/trigger reconYaml. Regarding the stock yamls for trains you do not have to use them in the case of mon, you can use the calib for calib schema and you can use the trigger stock train for trigger schema:
- mon decrecqtl -monYaml
- calib decrecanaqtl -reconYaml - calib (STOCK TRAIN)
- trigger decrecqtl -triggerYaml -trigger
Use dcalign instead of dst.
Physics Timelines
Instructions have moved to
in the `qa-physics` directory.
git clone https://github.com/JeffersonLab/clas12-timeline.git
cd clas12-timeline
mvn package
bash
./bin/run-monitoring.sh -d rgk_6_pass2_test /cache/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass2/v0/dst/recon
ln -s epochs.rgk_6.txt qa-physics/epochs/epochs.rgk_6_pass2_test.txt
sbatch ./slurm/job.rgk_6_pass2_test.physics.slurm
bin/run-physics-timelines.sh -d rgk_6_pass2_test
bin/deploy-timelines.sh -d rgk_6_pass2_test -t lanza
And you can find the output at:
https://clas12mon.jlab.org/lanza/rgk_6_pass2_test/tlsummary
Pass2 Calibration
- 10/04/22 Coatjava Release: 8.3.1.
- 10/04/22 Clara Release: 5.0.2.
The yaml file template to go from dec to rec is into the directory:
/group/clas12/packages/clara/5.0.2_8.2.4/plugins/clas12/config/data.yaml
The yaml has too any banks. The variation has to be updated to rga_fall2018 with the new drift chamber alignment and with the new CVT alignment. The timestamp has to be put in the past (also 10 minutes in the past is enough).
clas12-workflow.py --runGroup rgk --tag prova --model dec --inputs "/mss/clas12/rg-k/data/clas_005700/clas_005700.evio.00*" --runs 5700 --decDir "/volatile/clas12/lanza" --coatjava /group/clas12/packages/coatjava/8.3.1
File list: 10 for each run (two files).
Once the workflow is ready you have to check outputs.
1) Make histograms
Run on the farm, one job per run:
https://github.com/JeffersonLab/clas12_monitoring
2) Create timelines
https://github.com/JeffersonLab/clas12-timeline
3) Script to launch the monitoring
https://gist.github.com/drewkenjo/397d5d10d795c1ddfea508847ca0128a
The exact list of commands is the following:
LAUNCH PASS-0 clas12-workflow.py --runGroup rgk --model rec --tag rgkRecPass0_65 --inputs /u/home/clas12-4/users/lanza/filelist_65.txt --runs /u/home/clas12-4/users/lanza/runlist_65.txt --outDir /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0 --coatjava 8.3.2 --reconYaml /u/home/clas12-4/users/lanza/data.yaml clas12-workflow.py --runGroup rgk --model rec --tag rgkRecPass0_75 --inputs /u/home/clas12-4/users/lanza/filelist_75.txt --runs /u/home/clas12-4/users/lanza/runlist_75.txt --outDir /volatile/clas12/rg-k/production/recon/fall2018/torus+1/7546MeV/pass0/v0 --coatjava 8.3.2 --reconYaml /u/home/clas12-4/users/lanza/data.yaml LAUNCH TIMELINES git clone https://github.com/JeffersonLab/clas12-timeline.git 1)MONITORING ./bin/build-all.sh ./bin/slurm-mon12.sh v0 /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0/mon/recon/00*/ #path to the pass-0 files to be monitored, I wrote a file with the full list of runs 2)TIMELINE ./bin/build-all.sh ./bin/detectors.sh rgk pass0v0.0 ./plots/ mv rgk_pass0v0.0/ v0.0/ cp -r v0.0/ /group/clas/www/clas12mon/html/hipo/rgk/pass0/v0.0 cp /volatile/clas12/rg-b/offline_monitoring/pass0/2022/ListOfTimelines.json /group/clas/www/clas12mon/html/hipo/rgk/pass0/v0.0/ 3)CALIBRATION ./bin/qa.sh rgk/pass0/v0.0 cp /volatile/clas12/rg-b/offline_monitoring/pass0/2022/ListOfTimelines.json /group/clas/www/clas12mon/html/hipo/rgk/pass0/v0.0_qa/
Pass2 Calibration: steps
Steps performed to the pass-2:
- CVT correction (Taya), see log entry on Mon, 11/28/2022 - 11:55.
- DC correction (Florian), CCDB table has been updated, see log entry: use a timestamp after 17:55 ET from Dec 5 so that the cooking can pick up the constants.
- pass-0 done: first 10 files for each run taken from
- /mss/clas12/rg-k/production/decoded/6b.2.0/
using the data.yaml file.
- Timelines and QA Timelines for pass-0:
- Calibration for pass-2: Mariana Pita performs beam offset calibration for three runs (5733, 5958, 5997),
- /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_cvt_cal
that have been completely cooked.
- Pass0 and Timelines have been produced again:
- DC calibration: 14 pressure dependence runs have been cooked (first 3 files) and are located at at:
/volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/calib/recon/
- Pass0 and Timelines have been produced and give a photograph of T0 status for DC calibration:
- Timelines show jumps in vz corresponding to changes in luminosity. We cook other two runs (high and low luminosity) to assess a dependence and a third file for the 45 ns 7.5 GeV run range.
- Florian provides T00 update, see log entry on Wed, 01/18/2023 - 09:48. The 14 runs are recooked accordingly (after DC time offsets update, timestamp: 01/23/2023-10:00:00, see /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/iteration3/calib/recon/) and a new pass-0 is done. Timelines for pass-0:
- For the T2D calibration I also create a train with DC wagon for the files. Just with the standard calibration skim. See,
- /volatile/clas12/rg-k/production/recon/pass0/calib/v71/train/
- Timelines for the new iterated 14 runs for DC calibration, located at /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/iteration3/calib/recon/ :
- We want to do a check to investigate the shift in means in the latest RGK timelines. We cooked the 14 runs again and make a timeline but using the sqlite file (sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite) and the timestamp: 01/27/2023-14:00:00. The sqlite file has the new T00 corrections but only one T2D calibration for all runs compared to the current CCDB entries from pass1.
Hence new iteration 14 runs for DC calibration, based upon /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/iteration4/calib/recon/
- Calibration for pass-2: Mariana Pita performs beam offset calibration for run 5733,
- /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_cvt_cal
that has been completely cooked.
- New iteration 14 runs for DC calibration, using the updated sqlite file (sqlite:////work/clas12/users/hauenst/RGKtestfile/rgk_testfile.sqlite) and the timestamp: 02/23/2023-04:00:00 and based upon /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/iteration5/calib/recon/
- New iteration 14 runs for DC calibration, corrected github clas12-software directory, based upon /volatile/clas12/rg-k/production/recon/fall2018/torus+1/6535MeV/pass0/v0_dc_cal/iteration5/calib/recon/
- Pass0 and Timelines have been produced with DC calibration and CVT corrections applied (also new coatjava tag 8.6.0):
- First iteration 16 runs for FTOF calibration
- Pass0 and Timelines have been produced with FTOF corrections applied (also new coatjava tag 8.6.0):
- First iteration 3 runs for RF calibration
- Pass0 and Timelines have been produced with RF corrections applied:
- First iteration 15 runs for CTOF calibration, see logentry
- First iteration 3 runs for HTCC calibration (for pass2 calibrations, the way HTCC time is calculated was modified slightly - these constants have been updated in the ccdb)
- First iteration for SVT
- First iteration for FT
- Second iteration 3 runs for HTCC
- First iteration for FT-Hodo
- CND calibration
- Second iteration for FT
- Second iteration for FT-Hodo
- Third iteration for FT
- Pass0 and Timelines have been produced (new software version 8.7.1):
- AI training (04/19/23): trained neural networks 5700,5901,5993,5683.
- AI training (05/04/23-05/30/23): 5884,5856,5920,5986
- Pass0 and Timelines have been produced (new software version 9.0.0) - 05/10/23:
- Test DC cable swap 06/22/23
- AI training: comparison between combinations of neural networks and cooked runs. RGK chooses as neural network the one trained on run 5901, see slides.
- Denoising 06/29/23: comparison between AI assisted and AI assisted + denoising reconstruction of runs 5920 and 5704, see slides.
- Pass0 and Timelines have been produced again 07/18/2023:
Back to the RG-K wikipage
Link to Cheffing Info wikipage
Link to RGK chef page
Link to the Timelines
RGK FALL 2023 / SPRING 2024
Run Coordinator Schedule
Run List (Quick Reference)
Run K trigger studies
- Run Group K Trigger Performance (by Valery Kubarovsky)
Daily RC Meeting Minutes
in person and on ZOOM
Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room and on ZOOM Wednesdays at 3 PM, ZOOM only Weekends upon agreement
- Jan. 10 -- Jan. 16, 2024, RC: Axel Schmidt
- Jan. 17 -- Jan. 23, 2024, RC: Susan Schadmand
- Jan. 24 -- Jan. 31, 2024, RC: Susan Schadmand
- Jan. 31 -- Feb. 07, 2024, RC: Bill Briscoe
- Feb. 08 -- Feb. 14, 2024, RC: Susan Schadmand
- Feb. 15 -- Feb. 21, 2024, RC: Bill Briscoe
- Feb. 22 -- Feb. 28, 2024, RC: Daniel Carman
- Feb. 29 -- Mar. 6, 2024, RC: Daniel Carman
- Mar. 7 -- Mar. 11, 2024, RC: Daniel Carman
Useful Links
|
<headertabs/>