-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drift time window #219
Comments
I wrote a function to retrieve the longest drift time from the response file; should we use this as the value of time_padding or time_window, so we don't need to modify the time window for each different response config; I don't see why we are having two different parameters time_padding and time_window, they seem to serve the same purpose in detsim.py; we may simply keep one? e.g. Lines 335 to 336 in 450b5b7
Lines 428 to 430 in 450b5b7
|
There are some small inconsistency on the same parameters among different functions: larnd-sim/larndsim/drifting.py Line 57 in 450b5b7
track["t_start"] = (shorter drift time) + track["t0"], but in detsim.py, tracks_current_mc, Line 300 in 450b5b7
so in drifting.py should we also subtract track["t0_start"]: track["t_start"] = (shorter drift time) + track["t0_start"] larnd-sim/larndsim/drifting.py Lines 57 to 58 in 450b5b7
and similarly: track["t_end"] = (longer drift time) + track["t0_end"] |
Line 39 in 450b5b7
What is this + 1 for? Looks like a very arb. padding value and not being used when calculating time elsewhere |
The drift time window is provided as a standalone parameter in the detector configuration file. It is not associated / calculated from the drift distance or electric field, which makes it rather inflexible to change to other detector configuration and prong to errors. To be improved.
The text was updated successfully, but these errors were encountered: