Reduce predict tests

[zhixiangteoh]

Remove tests that test mostly already-tested code.

Fixes #876.

[codecov]

Codecov Report

Merging #877 (938063f) into master (8cd2ee0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #877   +/-   ##
=======================================
  Coverage   95.65%   95.65%           
=======================================
  Files          21       21           
  Lines        2256     2256           
=======================================
  Hits         2158     2158           
  Misses         98       98           

Flag	Coverage Δ
unittests	95.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[jeff-regier]

Looks like the tests are still taking > 20 minutes, with ~12 minutes consumed test_predict_decals_multiple_bricks alone. (And another 3 minutes consumed by test_predict_sdss_multiple_rcfs.)

Could we add some (optional) configuration settings to process just subimages within bricks/fields. i.e., for each brick/field, process just on a region (perhaps an 80x80-pixel box) specified in the config? This could be useful for users too, not just for testing. Users may only be interested in a particular bounding box.

384.15s call     tests/test_predict.py::TestPredict::test_predict_decals_multiple_bricks
99.43s call     tests/test_predict.py::TestPredict::test_predict_sdss_multiple_rcfs

[jeff-regier]

Definitely an improvement, but I still hope we can get runtime below 10 minutes--see comment above.

[zhixiangteoh]

Looks like the tests are still taking > 20 minutes, with ~12 minutes consumed test_predict_decals_multiple_bricks alone. (And another 3 minutes consumed by test_predict_sdss_multiple_rcfs.)

Could we add some (optional) configuration settings to process just subimages within bricks/fields. i.e., for each brick/field, process just on a region (perhaps an 80x80-pixel box) specified in the config? This could be useful for users too, not just for testing. Users may only be interested in a particular bounding box.

384.15s call     tests/test_predict.py::TestPredict::test_predict_decals_multiple_bricks
99.43s call     tests/test_predict.py::TestPredict::test_predict_sdss_multiple_rcfs

Predictions are already being done on 160x160 pixel box (testing_config.predict.crop.width|height), and profiling shows that 80x80 doesn't cut runtime much. Overriding align now which cuts a chunk of time.

[jeff-regier]

Excellent! Test finish in 8 minutes with no drop in test coverage.