OpenMC/tests
2015-06-08 14:48:15 +07:00
..
test_basic Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_cmfd_feed Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_cmfd_nofeed Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_confidence_intervals Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_density_atombcm Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_density_atomcm3 Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_density_kgm3 Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_density_sum Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_eigenvalue_genperbatch Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_eigenvalue_no_inactive Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_energy_grid Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_entropy Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_cell Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_cellborn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_distribcell Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_energy Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_energyout Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_group_transfer Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_material Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_mesh_2d Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_mesh_3d Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_filter_universe Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_fixed_source Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_infinite_cell Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_lattice Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_lattice_hex Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_lattice_mixed Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_lattice_multiple Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_natural_element Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_output Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_particle_restart_eigval Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_particle_restart_fixed Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_plot_background Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_plot_basis Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_plot_colspec Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_plot_mask Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_ptables_off Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_reflective_cone Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_reflective_cylinder Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_reflective_plane Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_reflective_sphere Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_resonance_scattering Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_rotation Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_salphabeta Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_salphabeta_multiple Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_absorption Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_current Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_events Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_fission Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_flux Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_flux_yn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_kappafission Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_MT Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_nufission Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_nuscatter Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_nuscatter_n Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_nuscatter_pn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_nuscatter_yn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_scatter Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_scatter_n Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_scatter_pn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_scatter_yn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_total Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_score_total_yn Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_seed Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_source_angle_mono Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_source_energy_maxwell Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_source_energy_mono Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_source_file Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_source_point Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_sourcepoint_batch Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_sourcepoint_interval Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_sourcepoint_latest Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_sourcepoint_restart Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_statepoint_batch Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_statepoint_interval Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_statepoint_restart Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_statepoint_sourcesep Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_survival_biasing Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_tally_assumesep Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_tally_nuclides Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_trace Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_track_output Fix path to script in test_track_output 2015-06-08 14:48:15 +07:00
test_translation Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_trigger_batch_interval Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_trigger_no_batch_interval Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_trigger_no_status Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_trigger_tallies Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_uniform_fs Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_union_energy_grids Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_universe Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
test_void Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
cleanup added ppm files for cleanup 2014-04-03 08:20:31 -04:00
convert_precision.py PEP8 fixes on convert_precision.py 2013-09-02 17:11:30 -04:00
readme.rst updated documentation 2014-04-11 09:10:25 -04:00
run_tests.py Consistently use the same Python interpreter when running tests 2015-06-04 13:53:42 +07:00
travis.sh Run Travis with two parallel jobs instead of four. Maybe this will help with the 2015-06-04 22:23:25 +07:00
travis_install.sh Updated HDF5 version for Travis to 1.8.15 2015-05-28 14:08:00 -04:00
update_results.py squashed distribcells commits and merged to develop 2015-04-29 14:00:09 -04:00
valgrind.supp added valgrind suppressions for HDF5 create/open 2014-05-08 12:31:21 -04:00

=================
OpenMC Test Suite
=================

The purpose of this test suite is to ensure that OpenMC compiles using various
combinations of compiler flags and options and that all user input options can
be used successfully without breaking the code. The test suite is based on
regression or integrated testing where different types of input files are
configured and the full OpenMC code is executed. Results from simulations
are compared with expected results. The test suite is comprised of many
build configurations (e.g. debug, mpi, hdf5) and the actual tests which
reside in sub-directories in the tests directory.

The test suite is designed to integrate with cmake using ctest_. To run the
full test suite run:

.. code-block:: sh

    python run_tests.py

The test suite is configured to run with cross sections from NNDC_. To
download these cross sections please do the following:

.. code-block:: sh

    cd ../data
    python get_nndc.py
    export CROSS_SECTIONS=<path_to_data_folder>/nndc/cross_sections.xml

The environmental variable **CROSS_SECTIONS** can be used to quickly switch
between the cross sections  set for the test suite and cross section set for 
your simulations.

A subset of build configurations and/or tests can be run. To see how to use
the script run:

.. code-block:: sh

    python run_tests.py --help

As an example, say we want to run all tests with debug flags only on tests
that have cone and plot in their name. Also, we would like to run this on
4 processors. We can run:

.. code-block:: sh

    python run_tests.py -j 4 -C debug -R "cone|plot"

Note that standard regular expression syntax is used for selecting build
configurations and tests. To print out a list of build configurations, we
can run:

.. code-block:: sh

    python run_tests.py -p

.. _ctest: http://www.cmake.org/cmake/help/v2.8.12/ctest.html
.. _NNDC:  http://http://www.nndc.bnl.gov/endf/b7.1/acefiles.html