Age | Commit message (Collapse) | Author |
|
|
|
specific, so now the example materials and surfaces are found in
chroma.demo.optics.
|
|
Not entirely effective for chroma-cam, since this does not catch
exceptions thrown in child processes.
|
|
|
|
experiment information.
|
|
|
|
|
|
|
|
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!.
|
|
|
|
|
|
|
|
|
|
|