G4OCCT 0.1.0
Geant4 interface to Open CASCADE Technology (OCCT) geometry definitions
Loading...
Searching...
No Matches
G4OCCT_STEPAssembly.cc File Reference

DD4hep detector-element plugin: multi-part STEP assembly. More...

#include <DD4hep/DetFactoryHelper.h>
#include <DD4hep/Printout.h>
#include "G4OCCT_STEPAssembly_impl.hh"
#include <G4Material.hh>
#include <G4NistManager.hh>
#include <map>
#include <stdexcept>
#include <string>
#include <vector>

Go to the source code of this file.

Functions

static Ref_t create_step_assembly (Detector &description, xml_h e, SensitiveDetector)
 

Detailed Description

DD4hep detector-element plugin: multi-part STEP assembly.

Compact XML usage:

<detector id="2" name="Calorimeter" type="G4OCCT_STEPAssembly" readout="CaloHits">
<step_file path="geometry/calorimeter.step"/>
<position x="0" y="0" z="0"/>
<material_map>
<entry step_name="Lead" dd4hep_material="Lead"/>
<entry step_name="LiquidArgon" dd4hep_material="liquidArgon"/>
</material_map>
<sensitive_volumes>
<volume name="Gap"/>
<volume name="Absorber"/>
</sensitive_volumes>
</detector>

Phase 1 implementation notes

The plugin reads the material map from the compact XML and imports the STEP assembly via G4OCCTAssemblyVolume::FromSTEP (in a separate OCCT-side TU). The constituent G4LogicalVolumes are registered in the Geant4 volume store by FromSTEP() but are NOT placed into the dd4hep::Assembly here; the assembly is therefore empty from the TGeo/DD4hep perspective in Phase 1.

Todo:
Phase 2: return per-solid placement data from the OCCT-side TU and populate the dd4hep::Assembly with TGeo placeholder volumes so that DD4hep and visualisation tools can see the constituent geometry.

Definition in file G4OCCT_STEPAssembly.cc.

Function Documentation

◆ create_step_assembly()

static Ref_t create_step_assembly ( Detector &  description,
xml_h  e,
SensitiveDetector   
)
static

Definition at line 57 of file G4OCCT_STEPAssembly.cc.

References G4OCCT_ImportSTEPAssembly().