|Message: problems with specific particle and geometry||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)|
Hi- I'm having trouble debugging the following error: I have a simulation that works on average about half of the time. When it doesnt work, it returns the error
#1 0x006c8ff3 in __waitpid_nocancel () from /lib/tls/libc.so.6
Cannot access memory at address 0x1 WARNING - Attempt to delete the physical volume store while geometry closed ! WARNING - Attempt to delete the logical volume store while geometry closed ! WARNING - Attempt to delete the solid store while geometry closed !
for each run where it doesnt work, I've narrowed it down to one particle (the same particle in an ntuple always causes the problem) Kinematically, the offending particles do not seem to have anything in common, and as far as I can tell, the problem takes place at different geometric locations.
I've run the program with many points of output. and as far as I can tell, it must be happening at the end of or after "StackingAction" but before the next "SteppingAction"
It seems to be random, except for the fact that the -same- particle always causes the problem.
I'm not sure what to do next, because the amount of output I'm getting tracking this thing is getting excessive. Are the errors about the geometry indicative of anything other than the obvious?
|Inline Depth:||Outline Depth:||Add message:|