List view
Define the Continuous Integration system for the development of branches. Implement a pipeline to run automated tests during pushes and merge requests. The CI pipeline will run when code changes and should make sure all of the changes work with the rest of the code when it’s integrated. It should also compile the code, run tests, and check that it’s functional.
Due by December 20, 2023•3/3 issues closedThis milestone contains two types of issues: 1) development of the framework to run benchmarking tests for AstroHACK and 2) development of benchmarking tests to monitor the performance of the repository. Use-cases are initially defined in below: * To characterize trends in performance metrics across AstroHACK repository history (after releases are published from the main trunk). * To detect code causing performance issues during verification of development branches (before changes are merged with the main trunk). The implementation should be based on the work done in casabench that makes use of airspeed-velocity. The main difference is that where casabench is a separate repository from CASA6 the AstroHACK benchmarking code can be incorporated into the same repository.
Due by December 20, 2023•2/2 issues closedFill in the initial tests based on the public API of AstroHACK specified in https://astrohack.readthedocs.io/en/latest/api.html. User stories and test cases will be defined for the test development. User stories will be collected in here https://github.com/casangi/astrohack/wiki/Test-Development#unit-tests. This milestone contains the issues to be implemented in branches for the API test development.
Due by December 20, 2023•11/11 issues closedInitial rapid-development phase (Oct 2022 - April 2023) of Astro-Hack, leading up to a release that demonstrates the ability to do data extraction, aperture map generation and panel adjustment with at least one observatory-supplied holography dataset.
No due date•9/9 issues closed