Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
module name, like chroma.detectors.cad_sno.
|
|
|
|
|
|
|
|
|
|
|
|
everything from the sub modules, so usage is the same.
|
|
|
|
the event data structure. No more writing files to chroma package directory.
|
|
|
|
|
|
context can be setup and torn down correctly around the test.
|
|
|
|
|
|
|
|
calculation of the path to the CUDA source code in one place.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
only run specific tests. Names currently include: ray, load, propagate, pdf, pdf_eval
|
|
|
|
|
|
|
|
with create_cuda_context().
|
|
|
|
|
|
of the event.
|
|
|
|
|
|
speed from 3.3M -> 3.45!.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the GPU, and run the DAQ multiple times on the same photons in a
likelihood calculation.
Propagating the same photons in a warp speeds up propagation by a
factor of 3 (and we could do this even better if we wanted), and this
improves the statistics in a likelihood evaluation quite a bit.
Running the DAQ multiple times is also an inexpensive way to improve
the quality of the PDF estimates.
|
|
|
|
|
|
|