Internal Server Error if no saturations occur before lockloss

It looks like one of the recent updates calls saturations.csv where the previous one had first checked if it exists (no file gets saved if there are no saturations). This should be an easy fix, but since the issue was brought up via email I figured it couldn't hurt to add it here before submitting a merge request.