-
Notifications
You must be signed in to change notification settings - Fork 22
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
Trigger and debugLevel 2 Bug #47
Comments
Hi Andy,
Those lines seem protected behind debuglevel>0. How is diaglevel>1
triggering them?
Dave
On Mon, Feb 28, 2022 at 06:03 Andrew Edmonds ***@***.***> wrote:
There is currently a bug that will throw an exception if you set:
physics.analyzers.TrkAnaNeg.FillTriggerInfo : true
physics.analyzers.TrkAnaNeg.diagLevel : 2
which causes the following error message:
%MSG-s ArtException: PostEndJob 28-Feb-2022 07:59:28 CST ModuleEndJob
---- EventProcessorFailure BEGIN
EventProcessor: an exception occurred during current event processing
---- EventProcessorFailure BEGIN
EndPathExecutor: an exception occurred during current event processing
---- ScheduleExecutionFailure BEGIN
Path: ProcessingStopped.
---- StdException BEGIN
An exception was thrown while processing module TrkAnaTreeMaker/TrkAnaNeg run: 1210 subRun: 0 event: 2
vector::_M_range_check: __n (which is 12) >= this->size() (which is 12)
---- StdException END
Exception going through path end_path
---- ScheduleExecutionFailure END
---- EventProcessorFailure END
---- EventProcessorFailure END
%MSG
Art has completed and will exit with status 1.
It comes from these lines here:
https://github.com/Mu2e/TrkAna/blob/514a2e62760f8727698f4cfcf79274fc20aa70f9/src/TrkAnaTreeMaker_module.cc#L692-L695
so I believe it's an issue with TriggerResultsNavigator. Once there is a
fix, I will close this issue
—
Reply to this email directly, view it on GitHub
<#47>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH57ZLHGRK4GHBIBYCR53U5N6D5ANCNFSM5PRFT7BA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
David Brown ***@***.***
Office Phone (510) 486-7261
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C) Berkeley, CA 94720
|
Thanks for catching this, Dave. It is debugLevel = 2 that causes the issue, not diagLevel = 2. I will update the issue name and the opening comment |
Hi. I'm trying to establish whether or not this is still an issue. If I naively append the lines
to @AndrewEdmonds11 do you happen to remember which fcl file you were using? Were you using a different trigger path to the one in Thanks. |
Thanks, Sam. I don't remember exactly which file this would have been for since it was a long time ago. Could you check whether the bug occurs when you change |
Ah, if I use:
Then I see a different error (related to the trigger info):
But if I set
|
Thanks, Sam. I guess for the first error we are just getting the wrong
I guess we want The second one is a bit more of a mystery, I guess that we are entering a bit of code we shouldn't be when |
There is currently a bug that will throw an exception if you set:
which causes the following error message:
It comes from these lines here: https://github.com/Mu2e/TrkAna/blob/514a2e62760f8727698f4cfcf79274fc20aa70f9/src/TrkAnaTreeMaker_module.cc#L692-L695
so I believe it's an issue with TriggerResultsNavigator. Once there is a fix, I will close this issue
The text was updated successfully, but these errors were encountered: