DetectorHistogrammer Output Clarrification?

Hello experts,

I want to know if there is documentation on exactly what the root file outputs correspond to what recorded quantities from the DetectorHistogrammer Module. I am looking for cluster size and was not sure where I can find that.

Thanks!

[AllPix]
log_level = "WARNING"
log_format = "LONG"
number_of_events = 1000000
detectors_file = "detector.conf"
model_paths = ./
multithreading = true
random_seed = 1234

[GeometryBuilderGeant4]
world_material = "vacuum"

[DepositionGeant4]
physics_list = FTFP_BERT_LIV
particle_type = "gamma"
source_energy = 122keV
source_position = 0 0 -20mm
source_type = "beam"
beam_direction = 0 0 1
number_of_particles = 1

[ElectricFieldReader]
model="linear"
bias_voltage=-500V
depletion_voltage=-100V

[GenericPropagation]
mobility_model = "constant"
mobility_electron = 1090cm*cm/V/s
mobility_hole = 110cm*cm/V/s
temperature = 293K
charge_per_step = 100

[SimpleTransfer]
max_depth_distance = 5um
output_plots = true

[DefaultDigitizer]
threshold = 600e
output_plots = true

# [VisualizationGeant4]
# mode = "gui"
# view_style = "wireframe"
# trajectories_color_mode = "generic"
# accumulate = 1
# accumulate_time_step = 2s

[DetectorHistogrammer]
name = "mydetector"
granularity = 100, 100

[ROOTObjectWriter]
include = PixelHit, MCParticle
file_name = "output_source_measurement_122keV.root"

Hi @oobie2142 ,

it is not documented beyond what is in the manual, but the easiest way to get an overview is to open the modules.root file (default name) with a TBrowser: in ROOT and have a look.
Here is how it looks for me

So I guess the confusion might come from looking at the output file from ROOTObjectWriter rather than the modules.root. Let me know if this doesn’t help, and we can figure it out!

Kind regards,
Håkan

Thanks @hwennlof that helped a ton, I guess I ignored the output. As for the output writer files, where would I be able to see what the outputs are for the ParticleHit Trees and other Trees?

Hi!

for this I would look at the manual under Objects and at the analysis examples in the repository (under tools/root_analysis_macros). These show how to read the objects back from the data file, and extract values from them.
Though this you get access to all the getter functions from the objects, which is why that’s the place to look to find what information is available.

Kind regards,
Håkan

Thank you for this @hwennlof. If I would to want to estimate the initial charge cloud diameter would I use the SensorCharge Object and use the global positions? Or is there another quantity I can use?

My apologies, would it be best to start a new thread for this discussion?