* Run 21 3p85 FXT [sqrt(s_NN) = 3.0 GeV] low luminosity (NOT high luminosity)
	- Following up on last week's report by Li-Ke Liu that P24iy and P25iy unexpectedly had different tracking results

	- Finding: despite the decision to exclude TPC SpaceCharge distortion corrections in production for this dataset, preliminary corrections were unintentionally applied
		+ BFC chain options were originally implemented as a switch to turn these corrections off/on in 2022 ( https://github.com/star-bnl/star-sw/pull/393 ), but these options are overridden under some conditions in libraries utilizing the "new TPC Alignment" (lines 321-324 of https://github.com/star-bnl/star-sw/commit/d152e4f72afb034778f4e74c5e2d5f5fd3eb9876#diff-68dbbee5068e1c42e57338c54bc7c37d31710844ae3f48e7d2d4513a084ba1fdR321 )

	- Because preliminary corrections were updated between the P24iy and P25iy productions, a different preliminary correction was applied for each
		+ Preliminary correction for P25iy was really just the calibration for high luminosity extrapolated down to low luminosity

	- Li-Ke's findings imply a need for reproduction of this dataset
		+ Now working with Li-Ke to see whether the P24iy version of the distortion corrections, or the originally intended (zeroed) distortion correction is better
		+ Test samples will be generated
			> Additional finding that CRS isn't yet functional since Monday's outage; working with SCDF to get this operational again

	- Discussed this topic with STAR Management, leading to the following guidance, with emphasis on addressing collaborative work:

1) When you are unsure of a calibration, you could enter it in the DB with a made up flavor (can always append Try1). This would protect from being picked up while still documenting things.
2) There should be no IMPLICIT options turned off/on without a message [option X turns Y off and Z on] OR [better] we summarize somewhere what we applied in a clear one time summary. One or a few lines of printout in a log would have caught your attention (perhaps)
3) Policy: Changes to another author's steering of on/off logic of calibration corrections require the calibration coordinator's sign-off
4) We need to reproduce (there is a major degradation of several signals) but not without re-aligning code behavior first to match what we wanted.

	- The above guidance implies some code changes before freezing SL26y.



	
* Run 22 pp500
	- st_physics, st_mtd, st_upc: cataloging of production continues
		+ required restoration of output & log files from HPSS, which is ongoing
		+ cataloging is a necessary step before clearing files from NFS to make room for next big production, and for placing output files on xrootd

	- st_fwd: still pending library (SL26a) freeze and/or decisions on staged processing (e.g. 10% first)




* Run 23 AuAu200
	- EPD calibrations continuing

	- Pending library (SL26y) freeze, including earlier-noted code changes

	


* Runs 20 & 21 7p7 GeV beam-beam and 26p5 GeV FXT [sqrt(s_NN) = 6.2 GeV]
	- Calibration samples needed for ETOF with new TPC alignment provided (as noted at last week's S&C meeting)

	- Check on SpaceCharge in Run 20 7p7 still to-do




* Libraries
	- Plan to involve analyzers in assessing SL16d_embed update for 64-bit

	- No other progress this past week