SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Plastics to Oil - Pyrolysis and Secret Catalysts and Alterna

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: SteveF who wrote (5196)2/18/2011 1:55:16 PM
From: scionRead Replies (1) of 53574
 
Read the full reports!!! JBI's data restoration is not as flawless as shareholders were lead to believe either.

disc.sci.gsfc.nasa.gov

Interim Report
Nimbus IV Data Recovery
Status as of December 13, 2010
Version 1.1
Prepared by: Emily Zamkoff, GES DISC, 301-614-5964

Shipment 4 sent 15 BUV tapes to JBI.

1.1Data Restoration

A TAP file is a proprietary tape emulation format developed by JBI. A TAP file contains header records that indicate the length of the previous and next record. The Nimbus IV record format was not changed as part of the recovery effort. Each Nimbus IV TAP file delivered by JBI is an image of the original tape and so may contain several individual files. To avoid confusion and simplify processing, each file was extracted and stored on disk as a separate TAP disk file.

4.2.1 THIR Restoration

On April 6 2010, 18 Ch 6.7 THIR TAP files and 1064 Ch 11.5 THIR TAP files were received from JBI.

On June 1 2010, 946 Ch 6.7 THIR and 13 Ch 11.5 THIR TAP files were received from JBI.

For Ch 6.7, there were 156 Infinite Loop errors, 29 Memory Fault errors, 2 files excluded, 7 failed processing. The rest were processed and split, and 1282 files were renamed. 39 of these files were duplicates and thus were overwritten, 4 of these files failed, and one file failed to ingest, leaving 1242 Ch 6.7 files to be ingested.

For Ch 11.5, there were 237 Infinite Loop errors, 27 Memory Fault errors and 1 file was excluded. The rest were processed and split, and 1257 files were renamed. 32 of these files were duplicates and thus were overwritten and 1 file was excluded, leaving 1224 Ch 11.5 files to be ingested.

32 files came back with no associated TAP file.

On November 22, 2010, 1242 Ch 6.7 and 1224 Ch 11.5 files were ingested onto s4pa and put on the web for public use.
The two spreadsheets with the details are called: Nimbus IV Ch 67 Inventory 2010-12-06.xls and Nimbus IV Ch 115 Inventory 2010-12_01.xls. The Renamed Name column has the final name of the file. The Comments column lists those files that are excluded or were duplicates and thus overwritten. The Bad Files/Error Types column lists the files that failed to be renamed due to Memory Fault or Infinite Loop errors. The Ingested Y/N column has the date that the successful data was ingested into s4pa. The CSV results describe where the errors are in the data. These spreadsheets are on the web and thus are available to the public.

Of the 449 files that had memory fault or infinite loop errors, approximately one third of the errors were due to bad data and two thirds of the errors were due to formatting issues that could possibly be resolved.

4.2.2 SIRS Restoration
No data has been returned yet.
4.2.3 BUV Restoration
No data has been returned yet.
1.2 Data Integrity

After ingest into S4Pa, GES DISC scientists examined the Nimbus 4 data files and prepared a detailed file-by-file analysis that will be available on the website when it has been completed.

disc.sci.gsfc.nasa.gov
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext