-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
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
UnexpectedMagneticField message in Pixel2D template (Run3 data at 0T) #31956
Comments
A new Issue was created by @boudoul boudoul. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign reconstruction |
Adding @amassiro |
assign alca it looks more like an alca topic for GT content |
New categories assigned: alca @christopheralanwest,@tlampen,@pohsun,@yuanchao,@tocheng you have been requested to review this Pull request/Issue and eventually sign? Thanks |
For now this is WONTFIX:
For more discussion: Will eventually be fixed before start of data-taking for collisions. |
+alca
|
Hi @slava77 , can you please sign this? thanks! |
+reconstruction |
This issue is fully signed and ready to be closed. |
Hello
I noticed when reconstructing a run from MWGR this message :
%MSG-w UnexpectedMagneticFieldUsingNonIdealPixel2DTemplate: PostModuleEvent 27-Oct-2020 15:14:15 CET Run: 334393 Event: 9562884
Magnetic field is 0 Template Magnetic field is 3.8
I'm just reporting here in case this is the sign that something needs to be fixed in order to have the right config when taking data at 0T (= the current case at P5 and will be important when commisioning the full detector during CRUZET later in 2021). Is this a known problem ?
How to reproduce ? Easy : running on 1 event of the workflow 138.1 (with a valid certificate to access data)
runTheMatrix.py -l 138.1 --command "-n 1"
Thanks.
The text was updated successfully, but these errors were encountered: