Tons of messages for background simulations.
The drift messages from LArVoxelReadout completely saturate the output of radiological simulations due to charge regularly being made outside the active volume.
Can we make this message a debug message so it doesn't spam the logs?
%MSG-w LArVoxelReadout: LArG4:largeant@BeginModule 25-Apr-2019 21:06:47 CDT run: 20000061 subRun: 0 event: 1 unable to drift electrons from point (136.377,-513.393,231.755) with exception ---- Geometry BEGIN Can't find nearest wire for position (3.00155,-513.478,231.628) in plane C:0 T:5 P:2 approx wire number # 0 (capped from -2) ---- Geometry END
#1 Updated by Kyle Knoepfel over 1 year ago
- Status changed from New to Feedback
- Description updated (diff)
Jason, are you able to make a feature branch with the desired change? If this type of message indicates a normal situation, then changing the logging to MF_LOG_DEBUG is reasonable. Otherwise, some more thought should go into it. If this is not an exceptional circumstance, then throwing/catching an exception is not the best solution.
#3 Updated by Jason Stock over 1 year ago
No. I haven't done any work on this. I have not worked with this piece of the simulation, and reported the issue to solicit help/feedback from the maintainers responsible for LArVoxelReadout.
I don't think this is exceptional, as any charge generated outside the active region will not drift to a wire and any charge in the dead region will not drift to a wire. As I didn't introduce the warning however, I am not sure how important the author thinks this warning is.