Currently, function missing_Pids_outputDB checks an output table against the header view for missing entries.
There are cases where this is insufficient: the project didn't build the output database (at all; didn't build it correctly; or the user removed it) even though it is designed for (additional) runs; for instance, if the output database failed to setup correctly (as sometimes happens during code development), but the test project code continues to call check_outputDB_completeness, then check_outputDB_completeness reports (misleadingly) that all is complete.
function missing_Pids_outputDB should additionally check against dbWork if present and against SFSW2_prj_meta[["sim_size"]] if present
Currently, function
missing_Pids_outputDBchecks an output table against theheaderview for missing entries.There are cases where this is insufficient: the project didn't build the output database (at all; didn't build it correctly; or the user removed it) even though it is designed for (additional) runs; for instance, if the output database failed to setup correctly (as sometimes happens during code development), but the test project code continues to call
check_outputDB_completeness, thencheck_outputDB_completenessreports (misleadingly) that all is complete.missing_Pids_outputDBshould additionally check againstdbWorkif present and againstSFSW2_prj_meta[["sim_size"]]if present