| Message: Is it really kZAxis or kXAxis? exampleN04 at two files: ExN04DetectorConstruction && ExN04CalorimeterROGeometry | Not Logged In (login) |
|
Hi all,
I just would like to point out/verify this in exampleN04. I appended below the lines I am refereing. Question: Why not just use kXAxis? we know that the detector's common axis is the X-axis? But in the ROGeometry, it is using the Z-axis? What is really the big difference? Would this affect the result much if I just become consistent using the X-axis for both? Please explain. Thanks Zaldy BTW, am using geant4.9.1.p03 using gcc 4.3.2 at Debian 5(Lenny) Distribution ============================================================================ Inside FILENAME: ExN04CalorimeterROGeometry.cc
G4VPhysicalVolume* ExN04CalorimeterROGeometry::Build()
{
.............
.............
// -------------------------------
// Calorimeter readout division:
// -------------------------------
// Phi division first: 48 sectors
................
................
................
G4LogicalVolume * caloROcellLog
= new G4LogicalVolume(caloROcellTub, dummyMat, "caloROcellLogical",0,0,0);
// G4VPhysicalVolume * caloROcellPhys =
new G4PVReplica("caloROcellPhysical", caloROcellLog, caloROphiDivisionPhys,
kZAxis, segmentsinZ,2.*caloRing_dz);
^^^^^^
==============> THIS ONE above ***************************
........... .......... return ROWorldPhys; } Inside FILENAME: ExN04DetectorConstruction
G4VPhysicalVolume* ExN04DetectorConstruction::Construct()
{
..............
//------------------------------ calorimeter
G4VSolid * calorimeter_tubs
..............
//------------------------------- Lead layers
// As an example for Parameterised volume
// dummy values for G4Tubs -- modified by parameterised volume
G4VSolid * caloLayer_tubs
...............
...............
// dummy value : kXAxis -- modified by parameterised volume
// G4VPhysicalVolume * caloLayer_phys =
new G4PVParameterised("caloLayer_phys",caloLayer_log,calorimeter_log,
kXAxis, nocaloLayers, calorimeterParam);
^^^^^^^^
============> THIS ONE ABOVE *************************
.............. return experimentalHall_phys; }
|
|
to: |