start with numa scaler 1, will be set to real value on EPN

[shahor02]

No description provided.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2022-pp-apass4
async-2023-pbpb-apass
async-2023-pp-apass1
async-data
async-mc
async-2022-pp-apass6

[davidrohr]

See my comment in #1505 1505

[shahor02]

@davidrohr I don't see where the RECO_NUM_NODES_WORKFLOW and NUMAGPUIDS are defined, isn't parser running for epns only?

[davidrohr]

RECO_NUM_NODES_WORKFLOW is defined in dpl-workflow.sh, and NUMAGPUIDS is defined in setenv.sh, so both should be available.
And the default should not be 1, it should be 230. If you set it to one, it will assume it has to do the load of all EPN nodes, so will multiply multiplicities by 230 with some cuts.

Anyhow, I would just move up the RECO_NUM_NODES_WORKFLOW_CMP definition, as I remarked in Chiara's PR.

[shahor02]

ok, thanks

[chiarazampolli]

Hello @shahor02 ,

Why did you add the labels? The problem was introduced by #1483, which is not in stable-async.

Chiara

[shahor02]

I thought it should be ported. Removed the labels.