1. LANCE Processing at the AMSR-E SIPS Presented by Kathryn Regner Information Technology and Systems Center at the University of Alabama in Huntsville Joint AMSR-E Science Team Meeting June 2-3, 2010 Huntsville, AL kregner@itsc.uah.edukregner@itsc.uah.edu www.itsc.uah.edu http://ghrc.msfc.nasa.gov 256.961.7791www.itsc.uah.edu http://ghrc.msfc.nasa.gov

2. Outline Overview System Configuration –Hardware –Software Architecture System Status and Accomplishments Planned Work Schedule AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 2

3. 3 UAHuntsville ITSC (Staff shared with GHRC DAAC): Management: Dr. Sara Graves, Director, ITSC Development: Helen Conover, Lead Bruce Beaumont Lamar Hawkins Mary Nair Matt Smith Engineering: Kathryn Regner Sandra Harper Data Management: Steve Jones User Services: Sherry Harrison Systems Administration: Will Ellett, Lead Michele Garrett AMSR-E LANCE Personnel

4. LANCE AMSR-E Overview Co-located with the AMSR-E SIPS, TLSCF, and GHRC; well established relationships with the AMSR-E Science Team. The AMSR-E SIPS currently produces the L2 & L3 standard products. Two fully redundant processing and distribution strings, at separate locations, on separate networks Seven day rolling archive Ingest of L0 data directly from EDOS Products generated within 20 min from acquisition at SIPS, in support of three hour latency requirement AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 4

5. LANCE AMSR-E Data Flow AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 5

6. 6 LANCE AMSR-E First Processing String National Space Science and Technology Center

7. LANCE AMSR-E Second Processing String Olin B. King Technology Hall AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 7

8. Software Architecture AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 8

9. System Status Hardware (four servers total for two strings of equipment) has been specified and is in the UAHuntsville procurement process. Network Interfaces for both strings of equipment have been identified. A list of firewall exceptions to request from NASA MSFC was submitted on Friday, 4/23. –Firewall exceptions are in place for BBFTP and LDAP. BBFTP is installed on the LANCE AMSR-E interim ingest and processing server, GWEN. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 9

10. Network Interfaces AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 10

11. Network Interfaces (2) AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 11

12. Development Status LANCE MODIS software downloaded and installed on temporary platform (existing AMSR-E SIPS reprocessing server). We are now able to generate all AMSR-E LANCE products. –L1A and L1B, using the same code that JAXA delivered to NSIDC for use by NOAA. –Level-2A, using RSS code obtained from NSIDC and adapted by NOAA. –Level-2B and Level-3 daily processing, using the same standard product algorithms currently in production at the SIPS. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 12

13. Development Status (2) Beginning routine LANCE processing in an extended test mode to evaluate error handling, metrics collection processes, etc. –ingesting and processing IERB data, utcpole.dat, leapsec.dat, orbital events, and other external files via cron as needed Ready to begin external interface testing to verify connectivity and procedures –Interface testing with EDOS for real-time receipt of RBD and GBAD data and with the ESDIS LDAP server for user registration/authentication. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 13

14. Development Status (3) Initial validation has been performed using a few sample L2A files. –L2A files generated at LANCE-MODAPS and LANCE AMSR- E are virtually identical, with very small differences attributed to the differences in compilers and operating systems (64-bit versus 32-bit). –Differences between L2A files generated at LANCE AMSR-E and at the AMSR-E SIPS are more significant, but appear to be due to the fact that different versions of the L2A algorithm are used; LANCE is using V9 and SIPS is using the more current V10. We are working with the AMSR-E TLSCF to evaluate these differences. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 14

15. Development Status (4) File naming convention –To distinguish standard products from near real time products, we will use the existing “product maturity code” within the file name, e.g., AMSR_E_L2_Rain_R10_200905281123_A.hdf AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 15

16. Near Term Tasks End-to-end processing and validation Implement data distribution to users Move all processing to production Prepare DIF entries for the ASMR-E LANCE products to submit to NASA’s Global Change Master Directory (GCMD) Define and implement metrics process AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 16

17. Schedule AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 17  Phase1 (April 1 – June 30): Implement initial AMSR-E NRT capability equivalent to NOAA & MODAPS on processing hardware borrowed from the SIPS and distribution via the GHRC web ftp server. Includes preliminary validation, initial user registration/authentication, and metrics  Phase 2 (July 1 – August 30): Implement initial AMSR-E NRT capability on target hardware at both locations

18. Schedule (2)  Phase 3 (September 1 – January 30) Implement latest AMSR-E standard products algorithms Implement L2A near real time algorithm from RSS. Provide subscription service, web-based monitoring, ESDIS User registration. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 18

19. Summary LANCE AMSR-E processing system is on schedule to become operational in early 2010. –procuring two strings of hardware –leveraging existing SIPS personnel, processes and procedures and software algorithms from the NSIDC DAAC. AMSR-E Joint Science Team Meeting Huntsville June 2-3, 2010 19