What assumptions/rules define a "valid" synoptic recipe file?

[bberkeyU]

If we can define a set of rules of what makes a good ucomp file; we can add these rules to the warning.txt file.
Right now, the warning.txt file does an excellent job of catching missing recipe files, missing darks, and missing flats. Right now, the code doesn't inspect the recipe wavelengths (beyond checking for flats at that wavelength). Based on post-eclipse work, we found the need to check the wavelength values to make sure we can apply an analytic Gaussian fit.