| Age | Commit message (Collapse) | Author |
|---|
|
directory so you can read Chroma ROOT files.
|
|
the contents of sys.argv whether you want it to or not.
A simple hack is to blank out sys.argv around the point where you
import ROOT. As an additional requirement, you have to actually use
the ROOT module for something (even just looking up a class) in order
for the TApplication to be initialized, so you can't just replace
sys.argv with an empty array around the ROOT import.
To ensure this is always done correctly, all Chroma modules that need
ROOT should obtain it by:
from chroma.rootimport import ROOT
|
|
models directory
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
