Closed combet closed 1 year ago
The CI system is failing this PR because it is now requiring that new code have sufficient test coverage. I will take a look at the new code and start adding tests. This might entail some refactoring of the code, if that is needed to make the code more testable.
Thanks for the heads up @marcpaterno. Discussing with @eduardojsbarroso, we'd like to move this new SACC-for-cluster module into the SACC github repo, rather than having it stay in FireCrown. It will still need testing, but maybe we should only do this once in the SACC github repo? What do you think? Also pinging @vitenti.
Sandro and I agree with the goal of moving what is now in firecrown/sacc_support.py
, and the tests we write for it, to SACC itself. Having the tests in place should help that transition.
Tests are still needed for ClusterSurveyTracer
. Currently, the documentation for its to_tables
method says one table is created per instance passed to to_tables
. But the implementation actually returns a list with only one table; that table may have many “rows”, one for each tracer instance. Is the documentation correct, or is the implementation correct?
This addresses issue #276.
sacc_support.py
examples/cluster_number_counts/demo_sacc_for_clusters.ipynb
).