|Message: Track stuck warnings, only when using primitive scoring||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hello, I noticed a very odd behavior. My Geometry is now basically long tubes of iron, filled with low density gas to represent a vacuum(i.e. beampipes) and a magnetic field map from -7 to plus 7 meters in Z and a few meters in radius as well. (I removed all the other detector parts.) Now when I turn on a scoring volume like this: /score/create/boxMesh boxMesh_1 /score/mesh/boxSize 10 10 0.1 cm /score/mesh/nBin 10 10 1 /score/mesh/translate/xyz 0 0 100 cm /score/quantity/passageCellCurrent passcellcur /score/close I get warnings like the following. WARNING - G4Navigator::ComputeStep() Track stuck, not moving for 10 steps in volume -tube_BeamCalInnerDnstream1- at point (3.629185133,2.42492601,3353.139749) direction: (0.07986325831,0.9463373312,0.3131573336). Potential geometry or navigation problem ! Trying pushing it of 9e-10 mm ... The odd thing is, that these warning do not appear, if I don't create the scoring mesh. As far as I can tell, the scoring mesh is also far away from the geometry where the track is stuck. So I can not explain, why this should appear only if I declare the scoring mesh. In both cases I use Geant4 9.3 patch 1 the QGSP_BERT physics list and a range cut of 0.005 mm (also happens for a 0.5 mm rangeCut) I understand that the warning is normally caused by geometry problems, but why is it only issued when a scoring mesh is declared? Thanks, André
|Inline Depth:||Outline Depth:||Add message:|