| 18 | | * MEH: reprocessed the remaining 2 exposures still broken from before (o7023g0257o, o7023g0317o) so MOPS can get their data as soon as needed without further delays -- looks like the previous fix was still in an odd not-updated state in warp that pstamp could use, a normal cleanup cycle seems to have cleared and now those exposures with the broken LAP label can fully update. |
| 19 | | |
| | 18 | * MEH: reprocessed the remaining 2 exposures still broken from before (o7023g0257o, o7023g0317o) so MOPS can get their data as soon as needed without further delays -- looks like the previous fix was still in an odd not-updated state in warp that pstamp could use, a normal cleanup cycle seems to have cleared and now those exposures with the broken LAP label can fully update |
| | 19 | * the czars really shouldn't only do fixes partway when there is likelihood of other problems in other chips/skycells and asking them to let us know of problems -- that is an unnecessary delay for MOPS on what is a lower level IPP data problem and things may also then get into odd states for higher levels like the pstamp server, causing even further delays |
| | 20 | * MOPS really shouldn't have to be testers by default until all these broken files from the stsci shuffle are fixed -- to reduce as much of the unnecessary delay for MOPS, it would help if the czars would ensure that the entire exposure is clear of problems, the best way to do that is having the entire exposure stage in full state and letting them know after checking that is so -- typically this will involve both chip and warp stages -- reminder that ps_ud% cleanup happens daily 1800-1900 HST |
