Right now, PtypePNjunctionImpurityDensity and ThermalDiffusionLithiumDensity only allow for one contact (one contact ID) to be declared as the Lithium-drifted contact. There might be cases, in which the user might want to declare multiple contacts, as for example for the p-type segBEGe detector, that has 4 segments, each of which are Lithium drifted, or strip detectors.
Without judging the performance right now, we could probably allow for passing a Vector with contact IDs, and compose the Lithium-contact geometry as a CSGUnion or all individual contact geometries. Maybe it's a bit more complicated than that..
Right now,
PtypePNjunctionImpurityDensityandThermalDiffusionLithiumDensityonly allow for one contact (one contact ID) to be declared as the Lithium-drifted contact. There might be cases, in which the user might want to declare multiple contacts, as for example for the p-type segBEGe detector, that has 4 segments, each of which are Lithium drifted, or strip detectors.Without judging the performance right now, we could probably allow for passing a
Vectorwith contact IDs, and compose the Lithium-contact geometry as aCSGUnionor all individual contact geometries. Maybe it's a bit more complicated than that..