This will be fixed by the new release which will be out very soon. So you can do some work in the mean time if you edit ParentGeometryFile.dat and replace the block which relates to the tracker (the part which is similar to the code below but says TrackerSingleStation.dat instead) with the code below this should work.

Module Tracker/Tracker1Station1.dat
                            { 
                                Position 12634.4100 0.0000 0.0000 mm 
                                Rotation  0.0 90.0 0.0 deg 
                            }

If you also have two modules by the names of TDm1152m9336.dat and TDm1152m9334.dat in ParentGeometryFile.dat then replace them with these two modules as well,

                    Module Ckov/Cherenkov.dat
                            { 
                                Position 5841.7442 0.0127 -0.1016 mm 
                                Rotation  0.0 90.0 0.0 deg 
                            }

                    Module TOF/TOF0.dat
                            { 
                                Position 5276.3100 -0.0000 -0.0000 mm 
                                Rotation  0.0 90.0 0.0 deg 
                            }

Or you could wait for the release :-) let me know if you have any more problems. I think I'll create an issue to catch that nasty Assertion Error and try to make it a little friendlier

Matt, since you've done this before would you happen to have an example of how to wrap and rotate a configuration?

Just for reference I've attached the original and modified (see comment #1) parent geometry files.

Peter, have a look at this file. I've created a new volume and placed the parent geometry in there (this should be the one with the corrections which are already working) To change the rotation of the entire geometry you should change the angles in this file I've added. I'm not sure if the angle I've added is in the correct plane (i.e. x, y or z) but if it isn't you can change it to something like

Rotation 0.0 45.0 0.0 deg

Hope this helps :-)

Pavel also brought up an issue after he looked at my visualizations. The particle starts so far away that the geometry ought to include the pre-dipole focusing section of the lattice. Otherwise the particle should be fired from right before the dipole.

I'm including my configuration file as well as my top-level geometry file that rotates everything by 90 degrees. The rest of the configuration has been modified as per Matt's instructions above.

Peter,

I have made you a geometry with only detectors in it. Hopefully this will suit your needs until I have sorted out the beam rotation. This is my priority for the moment because it would be nice to have the official geometry in your simulations. :-) I'll update you with how I'm getting on. If there's anything else you need in this geometry please give me a shout.

OK, I've just tried running the following configuration file (see attached) all I've done is put the legacy model of the Tracker as a whole in there. I get a failure with this of the following

python: src/common_cpp/DetModel/SciFi/SciFiSD.cc:95: virtual G4bool SciFiSD::ProcessHits(G4Step*, G4TouchableHistory*): Assertion `abs(chanNo-old_chanNo) < 2' failed.
Aborted

This is a problem with the tracker SciFi senstive detector code which I don't know anything about. Apologies but I think this will need to be discussed with Ed and Adam as I'm sure they will be able to help. I have asked them before what model of the tracker they are using and they said it was this one in the attached file. If its different I'll be happy to change the file for you :-)

Above is what I meant by adding the tracker have a go with this new .dat file and see if it works. I'm a little baffled by your error

ErrorHandler.CppError: Couldn't find property Tracker in module Detectors.dat at MiceModule::propertyInt

This looks like you don't have the tracker file in the location $MAUS_ROOT_DIR/src/legacy/FILES/Models/Modules/Tracker

Would you have a look to see if there is a Tracker1Station1.dat file there?

Yes, the directory is there. So for documentation purposes, here is the configuration file and modified simulate_mice.py...

Peter, try this set up that I've attached. It works for me ....

OK, well try using my configuration file?

I've just run it here and it goes to 29 WRLs then it finishes and this is with the default beam. It seems that there are only 29 created. Would you mind attaching your ConfiguratioDefaults.py file? I think I may have seen this error before but not entirely sure.

Something in your config file solved the problem. I can try to step through it at some point to isolate the cause. At any rate, included is my config file.

My ConfigurationDefaults.py is the same as the trunk. Attached.

Hey Peter,

I owe you an apology when doing the rotation stuff to get the beam line correct I forgot a line of code which meant it was harder than it should have been. However, to get the correct rotation of the geometry using the file I've attached and replace the code at the top of ParentGeometryFile.dat with the following

Volume Box
Dimensions 50000.0 50000.0 50000.0 mm
PropertyString Material AIR  
PropertyDouble G4StepMax 5.0 mm
PropertyBool Invisible 1

this will rotate the axis so that the cooling channel axis is along the z axis. :-) Pavel has also created G4BL file of particles which are rotated so the fire into the centre of D2s aperture. I'm working on rotating the beam in maus as well and shall let you know when its ready.

Oh, simulate on the file that is attached because using this set up ParentGeomeryFile.dat is placed within this.

To answer you email to me about the single station geometry you sent me on Sat. This geometry isn't the CAD transferred geometry it is one I have made by hand just so we have something in the ConfigDB of the single station. The actual single station geometry is being created by Jason at the moment and should include TOF1 and the other points you raised in the email :-)

Hope this is ok.

forgot to add the G4BL file so here it is. The starting position is upstream of D2