Tamas Vami
Tamas Vami
> should we be testing code development on all geometries I think we really should do this! I hope the github actions will be able to take a few more...
> are tracked elsewhere for completeness maybe you could point to where?
OK I agree it's better to remove this now instead of re-introducing it
Hi @pbutti is this the same as like an on-track rechit?
I did the following on UCSB's cluster which uses `bash`: ``` module load singularity git clone https://github.com/LDMX-Software/ldmx-sw.git git checkout 1232-use-denv-in-ldmx-env denv --clean-env --name "ldmx" "ldmx/dev:latest" "${LDMX_BASE}" ``` leads to ```...
OK this worked now for the environment, however, ``` denv fire .github/validation_samples/ecal_pn/config.py sh: 1: fire: not found ``` Doing ``` denv init ldmx/pro:v3.3.3 denv fire .github/validation_samples/ecal_pn/config.py ``` then leads to...
Does this mean to have all the `cout`-s replaced with ``` ldmx_log(info) ``` ? Do you wanna break this up to subdirectory level and divide the work among ourselves?
ok I see, then there is not much dividing to be done! And I also agree it would be good to have just one logging system and not to use...
Do we really need the `disableBeamSpotSmear` function? People who dont want smearing could just do ``` sim = simulator.simulator("mySim") sim.beamSpotSmear = [0., 0., 0.] ``` right?
Yeah I think we should just go ahead with ``` self.beamSpotSmear = [ 20., 80., 0. ] ``` in the default