You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It's a new project to support GPU processing in central production workflows, where WM system will be the bridge between Offline/CMSSW and the grid resources made available to CMS (through the glideinWMS layer).
Describe the solution you'd like
This GH issue depends on #10388, which contains all the specific details to be implemented in this ticket as well.
Then, the solution expected from this issue is to support the same RequiresGPU and GPUParams parameters at the StepChain spec. Those 2 parameters should also be supported at the Step dictionary level. In case the Step dictionary is missing these 2 parameters, they should be inherited from the top level specification (just as it's done for Multicore).
Note that the same validation should also apply to the Step level parameters.
Describe alternatives you've considered
Not to validate the optional parameters.
As discussed in different venues, StepChain requests are not suitable for different resource requirements among the different steps.
Having said that, the only option we have at the moment is to enforce the whole StepChain workflow to require GPU, whenever any of its steps requires GPU.
Impact of the new feature
ReqMgr2
Is your feature request related to a problem? Please describe.
It's a new project to support GPU processing in central production workflows, where WM system will be the bridge between Offline/CMSSW and the grid resources made available to CMS (through the glideinWMS layer).
Describe the solution you'd like
This GH issue depends on #10388, which contains all the specific details to be implemented in this ticket as well.
Then, the solution expected from this issue is to support the same
RequiresGPU
andGPUParams
parameters at the StepChain spec. Those 2 parameters should also be supported at the Step dictionary level. In case the Step dictionary is missing these 2 parameters, they should be inherited from the top level specification (just as it's done for Multicore).Note that the same validation should also apply to the Step level parameters.
Describe alternatives you've considered
Not to validate the optional parameters.
Additional context
Major discussion happened here: cms-sw/cmssw#33057
and description of these parameters: cms-sw/cmssw#33057 (comment)
Related to #11410
The text was updated successfully, but these errors were encountered: