Pawel plesniak/absorber shift

[PawelPlesniak]

Clean up of the STM simulation production code, including generation of data products with a standardized naming format

[FNALbuild]

Hi @PawelPlesniak,
You have proposed changes to files in these packages:

• Scripts
• JobConfig

which require these tests: build.

@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.

⌛ The following tests have been triggered for a2e2f31: build (Build queue - API unavailable)

About FNALbuild. Code review on Mu2e/Offline.

[FNALbuild]

‼️ It was not possible to prepare the workspace for this test. This is often caused by merge conflicts - please check and try again.

> git diff --check | grep -i conflict
JobConfig/pileup/STM/BeamToVD.fcl:122: leftover conflict marker
JobConfig/pileup/STM/BeamToVD.fcl:127: leftover conflict marker
JobConfig/pileup/STM/BeamToVD.fcl:132: leftover conflict marker
JobConfig/pileup/STM/BeamToVD1809.fcl:138: leftover conflict marker
JobConfig/pileup/STM/BeamToVD1809.fcl:143: leftover conflict marker
JobConfig/pileup/STM/BeamToVD1809.fcl:148: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:112: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:118: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:142: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:186: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:189: leftover conflict marker
JobConfig/pileup/STM/STMResampler.fcl:193: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:13: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:15: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:192: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:246: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:264: leftover conflict marker
JobConfig/pileup/STM/prolog.fcl:322: leftover conflict marker

Test	Result	Details
test with	✅	Command did not list any other PRs to include
merge	❌	a2e2f31 into 173faea merge failed

[PawelPlesniak]

I leave this for review by @YongyiBWu and @AndrewEdmonds11

[PawelPlesniak]

Note - I will review any failures that the CI workflow raises

[PawelPlesniak]

@FNALbuild run build test

[FNALbuild]

⌛ The following tests have been triggered for 79419ad: build (Build queue - API unavailable)

[FNALbuild]

☀️ The build tests passed at 79419ad.

Test	Result	Details
test with	✅	Command did not list any other PRs to include
merge	✅	Merged 79419ad at 173faea
build (prof)	✅	Log file. Build time: 04 min 16 sec
ceSimReco	✅	Log file.
g4test_03MT	✅	Log file.
transportOnly	✅	Log file.
POT	✅	Log file.
g4study	✅	Log file.
cosmicSimReco	✅	Log file.
cosmicOffSpill	✅	Log file.
ceSteps	✅	Log file.
ceDigi	✅	Log file.
muDauSteps	✅	Log file.
ceMix	✅	Log file.
rootOverlaps	✅	Log file.
g4surfaceCheck	✅	Log file.
FIXME, TODO	✅	TODO (0) FIXME (0) in 0 files
clang-tidy	✅	0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 79419ad after being merged into the base branch at 173faea.

For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

[PawelPlesniak]

@YongyiBWu and @AndrewEdmonds11 The CI workflow issues have been addressed, this is now ready for review