Skip to content

Kinfile update 2#557

Open
mrcmor100 wants to merge 40 commits intomasterfrom
kinfile_update_2
Open

Kinfile update 2#557
mrcmor100 wants to merge 40 commits intomasterfrom
kinfile_update_2

Conversation

@mrcmor100
Copy link
Copy Markdown
Collaborator

Update targets and particle masses.

Provakar Datta and others added 30 commits August 4, 2025 21:57
…Panguin batch PNGs. Add a copy script to copy images to hydra_in. (#6)
…ODO scintillator. Add kinematic corrections for target mass and beam energy.
…ime dependent SHMS calorimeter parameter files generated by Ryan. Summary of the param files and their associated run ranges can be found at https://docs.google.com/spreadsheets/d/1zj3FFt7aVxanYuLRA706xopwNQ-cv-n_tBHreLU-Kuo/edit?gid=0#gid=0
Updated standard.database and the replay scripts to be able to read t…
…ure there is only one param file associated to a given run.
…nt SHMS CAL param for 5 pass data, last updated run list and std.kin at the end of R-SIDIS phase 1
…alibration workflow of HMS Hodoscope same as SHMS Hodoscope
…tion for ps5. Replaced scalerCut variables with scaler, so no BCM cut should be applied. With a quick check, I couldn't see any difference in the live time values!
To Make Calibration workflow of HMS Hodoscope same as SHMS Hodoscope
Updated the crentral mom values after cross checking against EPICS va…
Casey Morean and others added 10 commits October 5, 2025 15:29
…dat at start of junk runs. Update prescale values against run_prescales.dat file from logbook and report entries. I had to rebase this off of Provakar's updates with corrected momentum settings and corrected JUNK -> good runs. There were not too many updates.k
… are quite a few targets missing in the autodb JSON db. All of the errors were marked at transitions from one target to another. It is very plausible that the target was still moving or the run was pre-started while the target was still on a different target.
…the beam energy, SHMS / HMS angles, and SHMS / HMS momentum values. I added them to a new corrected.kinematics file for all runs in the rsidis_runlist. I did not check particle masses or target since those are a bit more difficult, and a larger study needs performed for targets. Following Dave's suggestion on making the replay code fail rather than use the wrong calibrations, any file that was marked JUNK in the runlist has been commented out. This will lead to the replay failing and the no gpbeam in database error. These can then be checked against what people expect to exist in the 'good' rsidis runlist / replays.
…d. (#14)

* Updated target names: Carbon -> C, Copper -> Cu, Aluminum -> Al, C-hole/C-HOLE -> HOLE.

* fixed target types by comparing with EPICS (hcBDSPOS)

* Updated the BCM current threshold index to match BCM2

* Marked the runs taken with 200Hz EDTM JUNK due to unstable yield.

---------

Co-authored-by: Hall C DAQ <cdaq@cdaql3.jlab.org>
…d target masses. It was decided that all runs that are NOT PI+SIDIS, PI-SIDIS or HEEP will be marked electron mass in BOTH arms. This was to simplify the check. This is generally correct, but for specific runs we may like to revisit this process in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants