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

Error in GDML parsing when using spack installation #422

Open
vvolkl opened this issue Nov 6, 2020 · 3 comments
Open

Error in GDML parsing when using spack installation #422

vvolkl opened this issue Nov 6, 2020 · 3 comments

Comments

@vvolkl
Copy link
Member

vvolkl commented Nov 6, 2020

The spack-installed geant4 tries to validate the schema when using GDMLDetectorConstructore, and fails with:

-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : InvalidRead
      issued by : G4GDMLRead::Read()
ERROR - Empty document or unable to validate schema!
        Check Internet connection is ON in case of schema
        validation enabled and location defined as URL in
        the GDML file - Sim/SimG4Common/gdml/example.xml - being imported!
        Otherwise, verify GDML schema server is reachable!
*** Fatal Exception *** core dump ***
 **** Track information is not available at this moment
 **** Step information is not available at this moment

-------- EEEE -------- G4Exception-END --------- EEEE -------


*** G4Exception: Aborting execution ***
Aborted (core dumped)

The geant4 from lcg either skips this validation or succeeds, not yet clear to me.

@gganis
Copy link
Member

gganis commented Nov 10, 2020

Perhaps we should report to G4 team? Gunter Folger or even Dmitri (Konstantinov)?

@vvolkl
Copy link
Member Author

vvolkl commented Nov 11, 2020

Yes, that's a good idea. It can be reproduced with the geant4 examples, so it should be possible for them to investigate it. I'll write an email.

@vvolkl
Copy link
Member Author

vvolkl commented Nov 12, 2020

There seems to be a difference in the way expat is configured in the geant4 installations. Investigating this now

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

2 participants