Skip to content

64-bit nightly test logs have different StdEdxY2 messages #743

@genevb

Description

@genevb

I am not sure whether this leads to any actual differences in results, but the log files from nightly tests show some different messages from StdEdxY2Maker between 32-bit and 64-bit.

Some jobs have lines like this for 64-bit, but not 32-bit:

StdEdxY2Maker:WARN  - StTpcdEdxCorrection:           TpcEffectivedX/                      dEdx correction wrt Bichsel parameterization	Validity:20160207.000102 --- 20160618.000102
StdEdxY2Maker:WARN  - StTpcdEdxCorrection:   TpcLengthCorrectionMDF/  Variation vs Track length and <log2(dX)> and rel. error in dE/dx	Validity:20160207.000216 --- 20160512.000207

An example of this difference is seen like this:

diff -a /star/rcf/test/dev/daq_sl302.stica/Sat/year_2016/AuAu200_production_2016{,_64bit}/*log | grep StdEdxY2

or

diff -a /star/rcf/test/dev/daq_sl302.ittf/Sat/year_2007/2007ProductionMinBias{,_64bit}/*log | grep StdEdxY2

Other tables also have messages like these in some of the jobs, including TpcLengthCorrectionB, TpcPadCorrectionMDC, TpcLengthCorrectionMDN.

Some of the jobs have no such message differences, such as:

diff -a /star/rcf/test/dev/daq_sl302.stica/Sat/year_2021/production_3p85GeV_fixedTarget_2021{,_64bit}/*log | grep StdEdxY2

It would be good to understand the reason for the different messages, even if it is inconsequential for the output data.

-Gene

Metadata

Metadata

Assignees

Labels

64-bitSomething particular to 64-bit (vs. 23-bit)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions