We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following #28840 (comment)
Review implementation of the following to see if the MuonServiceProxy::update call can be safely moved to the event processing (::produce calls).
If the update calls can be moved to just the event, the beginRun support for MuonServiceProxy can be dropped.
update
OTOH, perhaps by the time of the resolution of this issue the framework will consider handling both transitions in a more transparent way.
@dntaylor @Fedespring @cericeci
The text was updated successfully, but these errors were encountered:
assign reconstruction
@wddgit
Sorry, something went wrong.
New categories assigned: reconstruction
@slava77,@perrotta you have been requested to review this Pull request/Issue and eventually sign? Thanks
A new Issue was created by @slava77 Slava Krutelyov.
@Dr15Jones, @smuzaffar, @silviodonato, @makortel, @davidlange6, @fabiocos can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
No branches or pull requests
Following
#28840 (comment)
Review implementation of the following to see if the MuonServiceProxy::update call can be safely moved to the event processing (::produce calls).
If the
update
calls can be moved to just the event, the beginRun support for MuonServiceProxy can be dropped.OTOH, perhaps by the time of the resolution of this issue the framework will consider handling both transitions in a more transparent way.
@dntaylor @Fedespring @cericeci
The text was updated successfully, but these errors were encountered: