If the user supplies information which returns an empty table from the RSP or the SQL database (for example, the SSObjectID is wrong or illegitimate, or there simply aren't any observations in the filter(s) the user chose), then the code gracefully fails with an informative error message.
Wrote unit tests to ensure this behaviour.
Fixes #88.
If any of the SQL queries on the RSP or a SQL database return an empty table, the code no longer fails quietly and instead errors out gracefully with an informative error message.
Wrote unit tests to ensure this behaviour.
Fixes #116.
If there are no observations for the object in the user's requested filters, the code prints a warning and then eliminates that filter from the list, so no information for that filter will be populated.
This can very easily be seen with DP0.3, which lacks u- and y-filter observations. Now, if you run asking for ugrizy, the code will cheerfully inform you that no observations exist in u or y and will no longer attempt to store information for those filters.
Wrote a unit test to cover this behaviour.
Review Checklist for Source Code Changes
[x] Does pip install still work?
[x] Have you written a unit test for any new functions?
[x] Do all the units tests run successfully?
[x] Does adler run successfully on a test set of input files/databases?
[x] Have you used black on the files you have updated to confirm python programming style guide enforcement?
Fixes #86.
Fixes #88.
Fixes #116.
Review Checklist for Source Code Changes