You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of different run types that can be defined:
Serial: A normal serial calculation, jobs are simply spawned to the batch system and are run when computation nodes have availability. Could be used for parameters scans to vary input data.
HTC: High Throughput Computation, a normally serial calculation is split into a number of jobs. This is done by submitting the same input file N times, with each file running NPS/N particles. In maintain the RN sequence, the each run is seeded with the same RN seed, but each run starts on history such that the RN sequence isnt used twice
HPC: High Performance Computing, a standard mode of operation for most HPC cluster systems. N cpu's work collectively on the same problem, communicating initialisation and output data using MPI (or OMP).
HTPC: High Throughput Parallel Computation, like HPC but provisioned through an HTCondor scheduler on an opportunistic resource rather than a dedicated scheduler
HyPC - Hybrid Parallel Computation, a combination of HTC and HTPC, the granularity of the calculation is set such that a number of inputs are created which appropriately stride through the RN seed, however each input is operated upon in parallel using MPI
There are also a number of calculation modes that must be tested,
Nat. Geom - Nat(ive) Geometry, an MCNP input deck
DAG Geom - Direct Accelerated Geometry, tracking of particles upon faceted CAD models, can have more stringent RAM requirements over Native Geometry; also needs to transport more files
There are also a number of scoring modes that must be tested
Simple Tallies - A small number of uncomplicated tallies, several tallies of same types with no energy binning
Complex Tallies - A large number of complex tallies, energy dependence, fm card multipliers, dose response functions, traditional mesh tally (additional file handling)
Advanced Tallies - Newer style, using tetmesh and KDE tallies (additional file handling)
I'm updating this table rather than the README since we get nice issue hyperlinks, can we create "sticky issues" that would better serve this purpose or just leave this issue open for the duration?
I think we can go through a number of different issues, have them linked to each other in some sense, and put the current issue that is blocking progress in the table above? Too much work?
There are a number of different run types that can be defined:
There are also a number of calculation modes that must be tested,
There are also a number of scoring modes that must be tested
The text was updated successfully, but these errors were encountered: