Update: Aqua Anomaly recovery effort

[OB.DAACx - SeanBailey]

The attempt to reset the Formatter-Multiplexer Unit (FMU) onboard the Aqua spacecraft that was scheduled for earlier this week has been postponed until September 2nd, 2020.
As the direct broadcast data appears to be unaffected, an effort is underway to collect the raw Aqua data files captured by the global ground station network.   While it may be  challenging to piece together all this data into something resembling normal production, the EOS Data and Operations System (EDOS) is looking at various ways to ingest this data into the nominal 2-hour L0 product data sets. If successful, this will provide some coverage for the gap caused by this anomaly.

Regards,
Sean

[OB.DAACx - SeanBailey]

On September 2, 2020, the Aqua Flight Operation Team was successful in recovering the Formatter/Recorder and as of 246/20:12:00 UTC resumed nominal operations.

Efforts to compile as much direct broadcast data collected during the anomaly period continue. 

Regards,
Sean

[OB.DAACx - SeanBailey]

The effort to recover data lost during the Formatter/Recorder anomaly has completed.  Approximately 29% of the global coverage was successfully recovered, mostly in the northern hemisphere, where there is a higher density of direct broadcast receiving stations.  These data are now available for download.

Regards,
Sean

[kdraeder]

Thanks for this update. It seems that I should interpret it to mean that the files missing from
https://airsl2.gesdisc.eosdis.nasa.gov/ ... .006/2020/
for days 230-245 will not be filled in. Or are they in a special "recovered data" ___location?
Thanks,
Kevin

OB.DAAC - SeanBailey wrote:
> The effort to recover data lost during the Formatter/Recorder anomaly has
> completed.  Approximately 29% of the global coverage was successfully
> recovered, mostly in the northern hemisphere, where there is a higher
> density of direct broadcast receiving stations.  These data are now
> available for download.Regards,Sean

[OB.DAACx - amscott]

Hi Kevin,

Yes, since Sean's message confirms that the recovery effort has been completed, your interpretation is correct. OBDAAC does not have a special ___location where recovered data is placed. It is routed to it's nominal ___location. Any gaps that remain in the data could not be recovered.