LEGEND-200 deployments

legend-pygeom-l200 supports the geometry of multiple LEGEND-200 deployments.

If you manage your own legend-metadata checkout, it is strictly necessary to have a legend-metadata checkout that already contains the channelmap for this deployment. For still untagged or pre-relase versions of legend-metadata, you have to manually perform the checkout.

timestamp after

legend-metadata

p03–p09

20230311T235840Z

>= v1.0.0

p13

20241210T225016Z

>= v1.0.1

p14

20250425T180115Z

>= v1.0.2

p15

20250716T161517Z

>= v1.0.2

the timestamp can be selected in the config file:

metadata_timestamp: 20250425T180115Z # example: p14

Tip

adding the geometries for new deployments to legend-pygeom-l200 require only a few number of changes:

  1. a channelmap in legend-metadata (not managed by the simulation team)

  2. a new extra_meta file in legend-pygeom-l200 that contains

    • string positions & parameters such as for minishrouds

    • copper rod lengths for each detector unit

    • pen plate sizes

    • calibration tube parameters

  3. an implementation of any geometry change that cannot be configured in the extra metadata.