Skip to content

SSE Unit Tests

Evren Imre edited this page Jul 26, 2021 · 4 revisions

SSE Unit Tests

  • Unit test data is created by running AMUSE.SSE over the mass and metallicity combinations stated in Hurley00. The mass values are approximate, but should be close. See the script at here.
  • The script uses two attributes for versioning
    • Version: Version of the XML document. New version number when there is a semantic or a structural change.
    • UUID: Indicates a new run of the generator. This could be, for example, due to running AMUSE.SSE with different parameters.
    • There is also a timestamp in ISO 8601 format
  • For convenience, arguments for generating the test data are -m 0.5 0.64 0.8 0.9 1 1.12 1.25 1.4 1.6 1.77 2 2.5 3.16 4 5 6.35 8 10 12.6 16 20 25 31 40 50 -z 0.0001 0.0003 0.001 0.004 0.01 0.02 0.03 -a 13800

Updating Datasets

  • Unit tests use version and UUID to prevent unexpected updates to the dataset.
  • When there is a new version of a dataset, just run the unit tests, and amend expected version/UUID numbers for the failing tests

ZAMS Unit Tests

  • ZAMS unit test data is created from the first track points of evolutionary tracks generated for SSE unit tests. Each track point belongs to the ZAMS state of a different star.
Clone this wiki locally