Skip to content
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

Feature to reduce number of geometry related error messages not working anymore? #756

Open
sdobbs opened this issue Sep 28, 2023 · 1 comment
Assignees

Comments

@sdobbs
Copy link
Contributor

sdobbs commented Sep 28, 2023

So, we tend to get a lot of error messages like this when running hd_root:
src/JANA/JGeometryXML.cc:347 Node or attribute not found for xpath "//composition[@name='LeadTungstateFullRow']/mposX[@volume='LTBLwrapped']/@ncopy".
Awhile ago, we introduced the pattern below to get these to not print, since they just come from some detector element which is used for one detector configuration but not needed for the current one:

jgeom->SetVerbose(0); // don't print error messages for optional detector elements bool good = Get("//composition[@name='LeadTungstateFullRow']/mposX[@volume='LTBLwrapped']/@ncopy",insert_row_size); jgeom->SetVerbose(1); // reenable error messages

Now this seems to be only working in single-threaded mode?

The messages appear to always be printed when running with multiple threads, and I'm not sure why. I tried putting a simple-minded lock around one of these statements, but am still seeing the same problem. Any ideas are appreciated.

@sdobbs
Copy link
Contributor Author

sdobbs commented Aug 22, 2024

for the record - I'll look at this after the JANA2 transition, since that will doubtlessly have an effect

@sdobbs sdobbs self-assigned this Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant