PhiASE
PhiASE configures and runs the ASE calculation from domain-level Python
objects: a GainMedium, spectral data, and solver/backend settings. The backend transport data is built internally and is not part of the
frontend modeling interface.
from HASEonGPU import PhiASE
phi_ase = PhiASE(
spectralProperties=spectra,
minRaysPerSample=1000,
maxRaysPerSample=1000,
repetitions=1,
adaptiveSteps=1,
mseThreshold=0.005,
useReflections=True,
backend="Host_Cpu_CpuSerial",
parallelMode="single",
numDevices=1,
rngSeed=1234,
)
Run One PhiASE Step
ASE can be run once without a Simulation time loop:
phi_ase.run(gainMedium=medium, crossSections=spectra)
result = phi_ase.getResults()
phi = np.asarray(result.phiAse).reshape(
medium.get("betaCells").expectedShape,
order="F",
)
run(...) canonicalizes the domain objects for the openPMD transport,
launches the compiled calcPhiASE backend, stores the raw result, and
returns self. The returned result.phiAse values correspond to the ASE
flux \(\Phi_i\) described in the scientific background.
Sampling and Physics Settings
minRaysPerSampleMinimum number of Monte Carlo rays \(N\) used for each sample point.
maxRaysPerSampleMaximum number of Monte Carlo rays used for adaptive sampling.
mseThresholdTarget mean squared error threshold for the ASE estimate.
repetitionsMaximum number of repeated
PhiASEruns using the same number of rays if the MSE target is not reached. Since the importance-sampling distribution assigns rays to prisms stochastically, repeating the calculation can improve the estimate without increasing the number of rays per run.adaptiveStepsIf the MSE threshold is not reached for one backend run, HASEonGPU increases the rays per sample up to
maxRaysPerSample. This parameter controls how many ray-count steps are available betweenminRaysPerSampleandmaxRaysPerSample.useReflectionsEnables or disables reflections at the top and bottom surfaces.
monochromaticForces the ASE computation to use only the first absorption and emission cross-section samples instead of spectral interpolation.
rngSeedOptional unsigned RNG seed for reproducible Monte Carlo ray sampling. Set this explicitly for reproducible runs. If omitted, the Python wrapper initializes a process-local NumPy seed stream from
np.random.SeedSequence()and draws one unsigned 32-bit backend seed for each ASE invocation.
Backend and Parallel Settings
backendAlpaka backend name. The minimal example uses
"Host_Cpu_CpuSerial"because it is available in a plain CPU build. Query the installed build withAlpakaBackends.all()and pass one of the returned strings here. See Backend Selection.parallelModeBackend compute mode written to the openPMD
parallel_modemetadata."single"runs without MPI communication inside one launched process."mpi"makes the Python frontend launchcalcPhiASEthroughmpiexec. The number of ranks per allocated node comes fromnPerNode.numDevicesMaximum number of devices made available on each node for the compute run. In MPI execution, HASEonGPU distributes those devices across the MPI ranks that are active on the same node.
nPerNodeNumber of MPI ranks launched per allocated node when
parallelModeis"mpi". It is not serialized as a HASE openPMD transport attribute. See MPI Execution and openPMD Transport for the interaction between process launching,parallelMode, andnumDevices.minSampleRangeandmaxSampleRangeOptional inclusive sample-index range. When omitted, all beta samples \(\beta_i\) are processed.
openPMD Transport Options
The openPMD storage backend is selected separately from PhiASE.backend.
The default is auto: it selects adios-sst, then adios, then
hdf5 from backends supported by both the compiled and Python openPMD
providers. Set PhiASE.openpmdBackend in Python, use
openpmd_backend in YAML, or pass --openpmd-backend through the
command-line helper to choose a different runtime backend.
Accepted values are auto, adios-sst, adios, and hdf5.
For repeated or streaming use, the transport can keep a session open and write only dynamic fields after the first iteration. See openPMD Transport for the openPMD record layout, storage backend options, artifact-retention environment variables, and MPI command-prefix examples.
Configuration Helpers
PhiASE can read settings from a dictionary or YAML file. This is intended
for run-control values: sampling, convergence, reflection flags, Alpaka compute
backend selection, openPMD storage backend selection, MPI launcher settings,
and optional sample ranges.
Objects such as GainMedium, SpectralDecomposition, and pump solvers are
still passed from Python.
phi_ase = PhiASE({"minRaysPerSample": 1000, "backend": "Host_Cpu_CpuSerial"})
phi_ase = PhiASE.fromYaml(
"phi_ase.yaml",
spectralProperties=spectra,
gainMedium=medium,
)
A YAML file can keep experiment and compute settings together:
experiment:
min_rays_per_sample: 100000
max_rays_per_sample: 1000000
mse_threshold: 0.05
repetitions: 2
adaptive_steps: 4
use_reflections: true
monochromatic: false
compute:
backend: Host_Cpu_CpuSerial
parallel_mode: single
numDevices: 1
n_per_node: 1
min_sample_range: 0
max_sample_range: 999
rng_seed: 1234
YAML keys may be placed at the top level or under phiASE, phi_ase,
experiment, or compute. If the same setting appears more than once,
PhiASE applies sections in this order: phiASE, phi_ase,
experiment, compute, then the top-level mapping. Explicit keyword
overrides passed to fromYaml(...) are applied after the file is read.
Accepted setting names are the PhiASE attribute names plus these aliases:
minRays -> minRaysPerSample, maxRays ->
maxRaysPerSample, min_rays_per_sample, max_rays_per_sample,
mse_threshold, adaptive_steps, use_reflections,
parallel_mode, max_gpus -> numDevices, n_per_node,
min_sample_range, max_sample_range, and rng_seed.
Loading YAML requires PyYAML. The package installation installs this
dependency from pyproject.toml; source-tree usage must provide it in the
Python environment.
For command-line tools:
parser = PhiASE.addArguments(parser)
args = parser.parse_args()
phi_ase = PhiASE.fromArgs(args, spectralProperties=spectra)
The command-line helper accepts --phi-ase-config first and then applies
explicit command-line options such as --backend or
--min-rays-per-sample as overrides. It also accepts --rng-seed for
reproducible Monte Carlo sampling.
Inspection After a Run
After run(...), inspect the simulation result and the original domain
objects rather than backend adapter containers:
result = phi_ase.getResults()
points = medium.getPoints()
prisms = medium.getPrisms()
getResults() raises RuntimeError if the object has not been run yet.