Should say my print statement is

=== modified file 'src/common_cpp/DetModel/SciFi/SciFiPlane.cc'
--- src/common_cpp/DetModel/SciFi/SciFiPlane.cc    2012-10-01 10:56:38 +0000
+++ src/common_cpp/DetModel/SciFi/SciFiPlane.cc    2012-10-18 03:10:33 +0000
@@ -89,13 +89,13 @@
   // G4RotationMatrix* trot = new G4RotationMatrix();
   // G4ThreeVector dir(0, 1, 0);
   // dir = dir*(*trot);
-  /*
+  
   std::cerr << "Module name: " << doubletName << "\n" 
             << "Module rotation: " << *(trot) << "\n" 
-            // << "Plane direction: " << dir << "\n" 
+            << "Doublet length: " << doubletThickness << "\n" 
             << "Mother Logical Volume is: " << mlv->GetLogicalVolume()->GetName() << "\n" 
             << "Mothers rotation is: "      << *(mlv->GetRotation()) << "\n";
-  */
+  
   // this is a fibre
   solidDoublet = new G4Tubs(doubletName, 0.0,
                             tr, doubletThickness / 2.0,

I can't seem to recreate this error. I pulled down a new version of the MAUS trunk on Wed 24th, installed it using /thrid_party/install_build_test_geant4.9.5.p01.bash, and sourced it using env.sh followed by env_geant4.9.5.p01.sh. Tests did turn up errors that look to be style errors, but no geometry errors. I took a look at the tmp//test_geometry_Stage2.dat log file that was created, and didn't see any errors.

Advice?

Can you turn verbose_level to 0 and then look at the output, check that it says geant 4.9.5.p01 when it loads geant4? i.e. that the installation went okay...

Okay, I'll have a dig... not sure why your nosetests should fail with those funny errors though.

Humm. So on your test job, we have

Check that we can run simulate_mice, convert to root, convert back to ... Globals manager
Placing BeamLine.dat of type Box position: (0,0,-10283) rotationVector: (0,0,1) angle: 0 volume: 209.641 m^3  material: Galactic
Placing TrackerSolenoid0.dat of type Cylinder position: (0,0,-4783) rotationVector: (0,0,1) angle: 0 volume: 4.2312 m^3  material: Galactic
Placing AbsorberFocusCoil.dat68 of type Cylinder position: (0,0,-2750) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing RFCouplingCoilUp.dat of type Cylinder position: (0,0,-1375) rotationVector: (0,0,1) angle: 0 volume: 2.56453 m^3  material: Galactic
Placing AbsorberFocusCoil.dat87 of type Cylinder position: (0,0,0) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing RFCouplingCoilDown.dat of type Cylinder position: (0,0,1375) rotationVector: (0,0,1) angle: 0 volume: 2.56453 m^3  material: Galactic
Placing AbsorberFocusCoil.dat of type Cylinder position: (0,0,2750) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing SpecVirt.dat of type Cylinder position: (0,0,4783) rotationVector: (0,0,1) angle: 0 volume: 2.82743e-08 m^3  material: Galactic
Placing TrackerSolenoid1.dat of type Cylinder position: (0,0,4783) rotationVector: (0,0,1) angle: 0 volume: 4.2312 m^3  material: Galactic
Placing TOF2.dat of type Box position: (0,0,6524.5) rotationVector: (0,0,1) angle: 0 volume: 0.5625 m^3  material: AIR
Setting the phase ............

but on the test server we have

Check that we can run simulate_mice, convert to root, convert back to ... Placing BeamLine.dat of type Box position: (0,0,-10283) rotationVector: (0,0,1) angle: 0 volume: 209.641 m^3  material: Galactic
Placing TrackerSolenoid0.dat of type Cylinder position: (0,0,-4783) rotationVector: (0,0,1) angle: 0 volume: 4.2312 m^3  material: Galactic
Placing AbsorberFocusCoil.dat68 of type Cylinder position: (0,0,-2750) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing RFCouplingCoilUp.dat of type Cylinder position: (0,0,-1375) rotationVector: (0,0,1) angle: 0 volume: 2.56453 m^3  material: Galactic
Placing AbsorberFocusCoil.dat87 of type Cylinder position: (0,0,0) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing RFCouplingCoilDown.dat of type Cylinder position: (0,0,1375) rotationVector: (0,0,1) angle: 0 volume: 2.56453 m^3  material: Galactic
Placing AbsorberFocusCoil.dat of type Cylinder position: (0,0,2750) rotationVector: (0,0,1) angle: 0 volume: 1.53151 m^3  material: Galactic
Placing SpecVirt.dat of type Cylinder position: (0,0,4783) rotationVector: (0,0,1) angle: 0 volume: 2.82743e-08 m^3  material: Galactic
Placing TrackerSolenoid1.dat of type Cylinder position: (0,0,4783) rotationVector: (0,0,1) angle: 0 volume: 4.2312 m^3  material: Galactic
Placing TOF2.dat of type Box position: (0,0,6524.5) rotationVector: (0,0,1) angle: 0 volume: 0.5625 m^3  material: AIR
Setting the phase .
-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : GeomSolids0002
      issued by : G4Tubs::SetZHalfLength()
Invalid Z half-length.
Negative Z half-length (0), for solid: Stage6.dat/TrackerSolenoid0.dat/Tracker0.dat/TrackerStation5.dat/Tracker0Station5ViewU.datDoubletCores
*** Fatal Exception *** core dump ***
-------- EEEE -------- G4Exception-END --------- EEEE -------

Could you post the file tmp/test_geometry_Stage2.dat? I'm looking at the test server error message like:

======================================================================
FAIL: For each "Configuration" file, check that we can load it - by calling
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/workspace/MAUS_geant4.9.5.p01/tests/integration/test_simulation/test_geometry/test_geometry.py", line 85, in test_geometries
    self.__run_sim(my_file)
  File "/home/jenkins/workspace/MAUS_geant4.9.5.p01/tests/integration/test_simulation/test_geometry/test_geometry.py", line 65, in __run_sim
    str(proc.returncode)+". Output in "+outname)
AssertionError: Test geometry failed in Stage2.dat with return code -6. Output in /home/jenkins/workspace/MAUS_geant4.9.5.p01/tmp//test_geometry_Stage2.dat

----------------------------------------------------------------------

Nb: the test server command is

bash third_party/install_build_test_geant4.9.5.p01.bash

I disabled the build for now while we investigate (I was going to run some checks like valgrind server side)

Valgrind doesn't report anything fishy... hohum...

Just to be clear, branch name is

bzr+ssh://bazaar.launchpad.net/%2Bbranch/maus/merge/

Thanks, starting download.

Found the error, and think I've corrected it. The problem seems to be we were laying down fibers incorrectly. Instead of laying the fibers down one next to another, we were spacing them out to fill the total available space. A difference of only microns, but on caused the last fiber to over shoot the end of the plane a hair and default to 0 length.

I'm running test now, hopefully this checks out. If it does check out I'll then push to the merge branch and the tracker_devel branch.

Happy that you've fixed it - even happier that you found a physics bug! This would certainly effect track reconstruction in this fibre, maybe in the whole tracker (Geant4 behaviour is unpredictable when volumes overlap - it can cause G4 to ignore physics volumes, which is bad).

Passed the test at tests/integration/test_simulation/test_geometry/test_geometry.py, but a new error popped up when running tests/run_test.bash (see below). However, this seems unrelated to this issue, so I'm inclined to push my changes. I thought it would be better to wait and see if you agree with my assessment of this new issue before I went through with a push.

Check we can import libxml2 ... ok
Check we can import libxslt ... ok

======================================================================
FAIL: test_run_test_cpp_unit (test_cpp_unit.CppUnitTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/ppd/mice/heidt/geant_test/merge/build/test_cpp_unit.py", line 18, in test_run_test_cpp_unit
    self.assertEqual(cpp_test, 0, 'Failed cpp tests with '+str(cpp_test))
AssertionError: Failed cpp tests with 256

----------------------------------------------------------------------
Ran 411 tests in 596.399s

FAILED (failures=1)

This is a fail on one of the C++ unit tests. Could you include a full test log so I can see which test is failing?

The C++ unit tests are what come out from all of the green/black/red text like

[--------] some text
[RUN     ] also
[      OK] here

Cheers

Can you make a test job? Instructions at Jenkins and you may need a login to the test server, let me know and I can set one up.