| Summary: | Parallel world navigation misbehaves if parallel world volume is identical to a physical world volume | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Sergio Losilla <sergio.losilla> |
| Component: | processes/transportation | Assignee: | John Apostolakis <John.Apostolakis> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | asai, Makoto.Asai |
| Priority: | P4 | ||
| Version: | 11.0 | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Sergio Losilla
2022-01-07 12:08:56 CET
If volumes in the "real" world and a parallel world share the volume boundary, the G4CoupledTransportation process is shown as the process that limits the step. This does NOT mean the volume in a parallel world is ignored. The following step is seen by both volumes in real world and the parallel world. Thus what you see is a correct behavior and nothing is misbehaving. If you would like to confirm, assign a sensitive detector to the volume in the parallel world and add G4cout to see. I added sensitive detectors and indeed you are right, I am sorry for wasting your time :-/ Has anything been fixed in recent versions? I recall that months ago I was getting wrong results with a more complicated setup involving replicas both in the physical world and the parallel world. Hi Sergio, if you experience any problem you should report them giving clear evidence and way to reproduce them (and possibly as a ticket in this system rather than through posts in the Forum). Generic statements don't help either. We are not aware of misbehaviours in this area; no issues have been reported to us. Apparently there was an issue like the one I meant to report, but it has already been fixed: https://geant4-forum.web.cern.ch/t/stepstatus-depending-on-scoring-mesh/6121/2 |