how to create alternative configs with a PSet switch

[slava77]

This is in connection with #24918 and is related to use cases of config switches https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideConfigurationValidationAndHelp#A%20%22Switch%22

The desired functionalities are:

• ability to create cfi files from fillDescriptions corresponding to different values of the switch
  • I have a bit awkward implementation in slava77/cmssw@slava77:CMSSW_10_4_0_pre1/sign1054/pull24918-aef474e...slava77:CMSSW_10_4_0_pre1/sign1054/pull24918-aef474e-configFix : here a small problem is a requirement to re-create a ParameterDescriptionCases object.
  • Is there a simpler alternative?
• ability to make a new cfi in python by specifying only the switch value
  • caseB = caseA.clone( switch = "B" ) does not work, one has to explicitly specify all different config parameters that are related to the new switch value.

[slava77]

assign core

[cmsbuild]

New categories assigned: core

@Dr15Jones,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

A new Issue was created by @slava77 Slava Krutelyov.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[Dr15Jones]

@makortel suggestions?

[makortel]

@slava77 We talked briefly with @Dr15Jones and think that your solution on the first bullet is the minimal that can be achieved (with the current API).

For the second bullet, we could think of adding a general mechanism for passing around metadata that would allow your example being written along

caseB = caseA.clone(**(caseA._aux()["switch_B"]))

with caseA._aux() being (e.g.)

dict(
    "switch_B" = dict(
        switch = "B",
        conf = cms.PSet(
            ba = cms.uint32(0),
            bb = cms.uint32(1)
        )
    )
)

such that the cfi generation will create the necessary python code to fill that. Slava, what do you think?

[slava77]

On 11/19/18 2:32 PM, Matti Kortelainen wrote: @slava77 We talked briefly with @Dr15Jones and think that your solution on the first bullet is the minimal that can be achieved (with the current API).

does it make sense to change the API?

For the second bullet, we could think of adding a general mechanism for passing around metadata that would allow your example being written along caseB = caseA.clone(**(caseA._aux()["switch_B"])) with |caseA._aux()| being (e.g.) dict( "switch_B" = dict( switch = "B", conf = cms.PSet( ba = cms.uint32(0), bb = cms.uint32(1) ) ) ) such that the |cfi| generation will create the necessary python code to fill that. Slava, what do you think?

this looks good. Thank you.

…

—