Lo L1C L2 - Maps use pset variable with sc velocity which may be predicted

[tmplummer]

Algorithm Description:

The Lo PSET was updated to include the spacecraft position and velocity. The L2 code was updated to use the variables present in the PSET when doing the CG correction. This is handy for users except that typically, a PSET will be generated using predicted ephemeris. This means when making the map, if the PSET has not been reprocessed with reconstructed ephemeris, the map and CG correction will use stale data.

Possible solutions:

• Trigger PSET reprocessing when reconstructed ephemeris arrives. This is slightly problematic because the reconstructed ephemeris, so far, covers the entire mission. This means that we will do a full mission reprocess every time the reconstructed ephemeris is delivered. Is that desired?
• Change the Lo L2 code back so that it updates the sc velocity in the PSET at processing time. This would mean the map is generated with the best ephemeris data available.