Problem 1319 - Numerous warnings using /score/create/cylinderMesh
Summary: Numerous warnings using /score/create/cylinderMesh
Status: RESOLVED WONTFIX
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/scoring (show other problems)
Version: 9.5
Hardware: All All
: P5 trivial
Assignee: asai
URL:
Depends on:
Blocks:
 
Reported: 2012-05-22 03:08 CEST by Iwan Cornelius
Modified: 2012-10-27 02:32 CEST (History)
0 users

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 Iwan Cornelius 2012-05-22 03:08:31 CEST 
Hello, 

I am currently trying to use the UI scoring manager to create a cylindrical scoring mesh in a homogeneous volume. I have been using the cartesian 3D dose scorer with great results; however, the cylindrical scorer is producing these warnings, and generating unusual results. 

I will keep investigating, just thought that I'd bring it to the developers' attention. 

If you require any further information, please do not hesitate to contact me. 

Best Regards, 
Iwan Cornelius


-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
      issued by : G4Navigator::ComputeStep()
Track stuck or not moving.
          Track stuck, not moving for 10 steps
          in volume -cylMesh_mesh3- at point (10,0,-0.000381318)
          direction: (-0.397293,-0.132703,-0.908046).
          Potential geometry or navigation problem !
          Trying pushing it of 1e-07 mm ...Potential overlap in geometry!

*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
Comment 1 asai 2012-07-11 18:20:02 CEST 
Hi,
Thank you for reporting your issue.
We are aware of rather frequent warning messages for cylindrical mesh, and we are addressing to solve it. For example, Patch-01 should have solved many of the problems.
On the other hand, we believe these warning messages are harmless (except for annoying amount of print-outs) to the simulation results. Could you please explain a bit more detail, how you identify your results are incorrect? 
Kind regards,
Makoto Asai
One additional comment is that if you are using regular navigation for voxels in your geometry, as it is documented, regular navigation and mesh scoring cannot currently coexist.
Comment 2 asai 2012-10-27 02:32:55 CEST 
As we do not receive any additional information, we close this issue. You may re-open it and provide us any further information.