Testing

There are two ways to test WODEN. The first is to use the CMake testing suite which is more for developing WODEN, and contains unit/integration tests for Python, C, and GPU code. The second is via the test_installation directory which contains a number of commands that can be used to test the functionality of the local installation of WODEN. See below for details.

• Testing via ctest
  • Dependencies
  • Running tests
  • What do the tests actually do?
• Testing installation via scripts
  • Running the simulations
  • Imaging the simulations
  • Expected outcomes
  • Deleting test outputs

EveryBeam Testing

For testing everybeam functionality , I’ve made a number of notebooks that live in WODEN/test_installation/everybeam/. This is on top of normal unit testing, to do proper sanity checks and for full disclosure of what is happening. The integration tests in the notebooks are:

• EveryBeam Testing and Development
  • Defining and applying parallactic rotations
  • EveryBeam MWA integration tests
  • EveryBeam LOFAR LBA integration tests
  • EveryBeam LOFAR HBA integration tests
  • EveryBeam OSKAR “MWA” integration tests
  • EveryBeam OSKAR SKA integration tests
  • Installing EveryBeam
  • Work still to be done on EveryBeam in WODEN

pyuvdata UVBeam Testing

For testing UVBeam functionality , I’ve made a number of notebooks that live in WODEN/test_installation/pyuvbeam/. This is on top of normal unit testing, to do proper sanity checks and for full disclosure of what is happening. The integration tests in the notebooks are:

• UVBeam Testing and Development
  • pyuvdata UVBeam MWA integration tests
  • Work still to be done on UVBeam in WODEN