`check_completion` incorrectly flagging unstarted runs as "complete - 0%"

I believe this is because when the mesh is large (such as with HSOFS 120m) the initial NetCDF output files are also large because they contain the mesh

For example:

(coupledmodeldriver)  Zachary.Burnett@hfe08 � /scratch2/COASTAL/coastal/scrub/Zachary.Burnett/working/zach/nems_adcirc/florence2018_hsofs120m_atmesh�
 > check_completion runs/unperturbed --verbose
{
    "unperturbed": {
        "status": "completed",
        "progress": "0%"
    }
}