Skip to content

GPU: write settings.dump from the standalone event generator - #16074

Open
ktf wants to merge 1 commit into
AliceO2Group:devfrom
ktf:pr16074
Open

ktf wants to merge 1 commit into
AliceO2Group:devfrom
ktf:pr16074

Conversation

@ktf

@ktf ktf commented Nov 7, 2026

Copy link
Copy Markdown
Member

GPUChainTracking::DumpSettings only writes the calibration objects, the
GRP settings.dump is written by GPUReconstruction::DumpSettings, so a
dataset produced with --eventGenerator could not be read back.

@ktf
ktf requested a review from davidrohr as a code owner November 7, 2026 13:19
Comment thread GPU/GPUTracking/qa/genEvents.cxx Resolved
@alibuild

alibuild commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

Error while checking build/O2/fullCI_slc9 for 4147dbf at 2026-11-09 13:03:

## sw/BUILD/O2-latest/log
/sw/SOURCES/O2/slc9_x86-64-slc9_x86-64/0/GPU/GPUTracking/qa/genEvents.cxx:360:3: error: invalid use of member 'o2::gpu::genEvents::mRec' in static member function
ninja: build stopped: subcommand failed.

Full log here.

@davidrohr

Copy link
Copy Markdown
Collaborator

ok, sorry, that function is static, I should have tried myself. Can you move the mRec->DumpSettings to the end of InitEventGenerator.

GPUChainTracking::DumpSettings only writes the calibration objects, the
GRP settings.dump is written by GPUReconstruction::DumpSettings, so a
dataset produced with --eventGenerator could not be read back.
mClusterError[i][j]->GetXaxis()->SetTitle("Cluster Error [cm]");
}
}
mRec->rec()->DumpSettings(dir.c_str()); // the chain's own override does not write settings.dump

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think now you can use mRec->DumpSettings(...) directly, this was the point of the change in the first place.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants