Problem 2219 - G4Exception comes up with Vecgeom+Parameterisation
Summary: G4Exception comes up with Vecgeom+Parameterisation
Status: RESOLVED DUPLICATE of problem 2209
Alias: None
Product: Geant4
Classification: Unclassified
Component: parameterisations (show other problems)
Version: 10.6
Hardware: All All
: P4 minor
Assignee: Marc.Verderi
URL:
Depends on:
Blocks:
 
Reported: 2020-01-27 07:09 CET by Haegin Han
Modified: 2020-02-03 15:49 CET (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description Haegin Han 2020-01-27 07:09:55 CET 
Hi, as I have mentioned in Geant4 forum (https://geant4-forum.web.cern.ch/t/compile-error-for-vector-t-erase-geant-10-6/1545/5?u=haeginh), when I try to use Parameterised geometry with Geant4.10.06 built with VecGeom 1.1.5, the exception message comes up as below.

-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : GeomSolids0003
      issued by : G4UAdapter::ComputeDimensions()
Illegal call to G4UAdapter::ComputeDimensions()
Method not overloaded by derived class !
*** Fatal Exception *** core dump ***
 **** Track information is not available at this moment
 **** Step information is not available at this moment

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

In compute solids, I return G4Tet, and I am not sure if this is same for other solids. Actually, Geant4.10.06 built without VecGeom 1.1.5 also had a similar problem, but this could be solved with the modified G4Tet files provided by Dr. Evgueni Tcherniaev (https://geant4-forum.web.cern.ch/t/g4tet-with-g4vpvparameterisation-in-10-6/1481/6?u=haeginh).

Best regards,
Haegin
Comment 1 Evgueni.Tcherniaev 2020-02-03 09:00:20 CET 
This issue is similar to the issue #2209 (https://bugzilla-geant4.kek.jp/show_bug.cgi?id=2209). The exception was introduced by mistake and will be fixed in the next patch release.
Comment 2 Gabriele Cosmo 2020-02-03 15:49:01 CET 

*** This problem has been marked as a duplicate of problem 2209 ***