HDF-EOS Workshop IV

171 views

Published on

Source:

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
171
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • LOGISTICS
    Registration/Sign-in
    Please sign in at the workshop reception desk and wear the badge while in the Raytheon facility.
    Messages:
    The workshop receptionists can take messages the telephone number is. They will post them on the message board.
    Copy services.
    If you need a few b&w copies of something, bring them to George Schwenke or to the reception desk. We won’t be able to make large numbers of copies
    Lunch
    Raytheon cafeteria in the building.
    Alternate lunch sites are listed in the reception package.
    Lavatories
    Left at the stairs, down the hall a little and on your left.
  • These action items are listed in the order they came up at last year’s workshop. The order does not imply relative importance. Remember that workshop actions have the force of “community recommendation”, but ESDIS cannot commit to resolving any particular action unless we can determine that it is a project requirement.
    Metcheck utility pre-Alpha was delivered to ESDIS August 31 but not yet independently checked. An alpha version was delivered yesterday.
  • Software IRD targeted for Aura teams, but generally applicable. Appendix C outlines metadata requirements.
    Some instrument teams such as MODIS have been very reluctant to version or create a new collection. They believe the creation of different ESDT versions will break PGEs and confuse users. ECS has gone to great lengths to support MODIS in this. Other instruments/DAACs such as MISR at LaRC have chosen the creation of new versions when making changes. This allows them to use configuration control. This policy may change as more users acquire the data, but, this has mainly been a DAAC and instrument team decision. Neither ECS nor ESDIS are dictating when new collections need to be created it is a science and operations decision.
  • But, I can’t find it. Ask George.
  • Not a user error but an "undocumented feature" of the library - the "clockwise" sweep convention. That is, if two points are close together in a polar plot the sequence they are entered into the degboxregion call is important because the code determines the appropriate region based on a clockwise sweep through longitudes between the two points. Also, if the points are 180deg apart, you don't get a square box but it still sweeps just one way because the test for 180deg apart is done by looking for a zero result in a floating point calculation. Which way it goes around the circle is determined by whether the result is positive or negative, which is determined by the machine and OS. This was determined to be a bug and has been fixed.
    Another related bug was also fixed, but I don’t have details.
  • We need to run lint on the site to fix broken links. We have quite a bit of stale material, as always. When will we ever have the time or attention?
  • The software Information Page is on broadneck.org. We need to bring it in house. It will require community input to make this listing useful.
  • Even if workshop expresses interest, we need to have EOS requirement before we can put it on the ECS contract. It may be possible to develop this capability and deliver it through a new process. ECS is to write a white paper on how to bring new functionality into HDF-EOS steps go from web advertised, to more formal “add-in”, to integrated into SCF version to final DAAC version.
  • The am under Klein has several ideas about how to improve the error messages and also about how to reference the errors in documentation. Proper documentation of error codes is a concern and will be addressed incrementally
  • Paper was found to have flaws when NCSA tried to implement a tool applying the paper to real data files. The mapping is better understood now and revision of the paper will be forthcoming. Experience porting CERES’ HDF products to HDF5 was positive.
  • We did not make a formal poll, but the HDF-EOS developers have consulted with all the EOS data providers. It is hoped that a tool, modeled after the NCSA mapping tool now under development can be made to facilitate the mapping of HDF-EOS 2 products to HDF-EOS 3
  • Clear statement:
    For the foreseeable future:
    ESDIS will develop an implementation of HDF-EOS built on HDF5. The implementation will be incorporated in the HDF-EOS 3 library and should be available by mid-winter. ESDIS will continue to support HDF4, including fixing bugs as they are discovered in HDF-EOS 2.x , however effort to develop new functionality will be focussed on HDF-EOS 3 based on HDF5 and not on HDF-EOS 2 based on HDF4.
    Is that is too long to be “clear”?
  • HDF-EOS Workshop IV

    1. 1. HDF-EOS Workshop IV September 19-21, 2000 Richard E. Ullman ESDIS Information Architect NASA/ GSFC, Code 423
    2. 2. Workshop IV Goals – Show where we are in application of HDF5 to the HDF-EOS “profile”. – Share progress in development of tools, both commercial and government sponsored that recognize HDF and the HDF-EOS profile of HDF. – Share lessons learned by the Terra Science data producers and others in applying HDF and HDFEOS to their particular science products. – Collect feedback from HDF-EOS community to help guide our continuing efforts. Ullman HDF-EOS Workshop IV Page 2
    3. 3. Workshop III Action Status 1. Develop a metadata validator tool to compare metadata to the ECS data model and to the collection descriptor. STATUS: RITSS has developed a stand-alone command line tool called “metcheck” for use by data producers – Alpha today. – Beta in the next month or so. Ullman HDF-EOS Workshop IV Page 3
    4. 4. Workshop III Action Status 2. Publish metadata policy statements. For example, the policy for deciding when changes to collection level metadata require creation of a new collection. STATUS: A data provider and DAAC issue supported by ECS, not an HDF-EOS issue. – Becoming better understood through experience – A Data Provider’s “Software IRD” in development. – ECS science office is best source for answering questions. Ullman HDF-EOS Workshop IV Page 4
    5. 5. Workshop III Action Status 3. Provide a link from the HDF-EOS site to the UAH subsetter. STATUS: Done Ullman HDF-EOS Workshop IV Page 5
    6. 6. Workshop III Action Status 4. Investigate Polar bounding box selection errors in HDF-EOS. Either correct code or correct documentation. STATUS: Done – Some confusion attributed to user misunderstanding. – Code bug found that affected certain selections. Bug fixed. Ullman HDF-EOS Workshop IV Page 6
    7. 7. Workshop III Action Status 5. Update HDF-EOS web site with presentations, attendance list, etc. STATUS: Always ongoing. – Complete for WS III Ullman HDF-EOS Workshop IV Page 7
    8. 8. Workshop III Action Status 6. Provide a web site to showcase tools. STATUS: Always ongoing. Links from http:/hdfeos.nasa.gov/ home page: – “How Do I View HDF-EOS Files?” http://hdfeos.gsfc.nasa.gov/hdfeos/viewingHDFEO S.html – “HDF-EOS Software Information Page/ Review Listed Software and Add New Software” URL under construction. Ullman HDF-EOS Workshop IV Page 8
    9. 9. Workshop III Action Status 7. Develop a set of suggested attributes (units, scale factors, axis labels) STATUS: DRAFT COMPLETE – The EOS Aura Data Systems Working Group has led this effort – Cheryl Craig will present status later in this workshop. Ullman HDF-EOS Workshop IV Page 9
    10. 10. Workshop III Action Status 8. Provide a tool to extract information from bit fields. STATUS: No ACTION – So far, we have not noted sufficient interest in this proposed functionality to make implementation a priority. Ullman HDF-EOS Workshop IV Page 10
    11. 11. Workshop III Action Status 9. Provide better error messages from HDFEOS. Make the bug tracking and fixing process more open. STATUS: Always ongoing – HDF-EOS library development team will be implementing some improvements in documentation of error codes and implementation in the next revision of HDF-EOS. Ullman HDF-EOS Workshop IV Page 11
    12. 12. Workshop III Action Status 10. Provide standard definition of HDF4 items using HDF5. That is, how do we use HDF5 to make the identical HDF4 item? STATUS:IN PROGRESS – NCSA (Mike Folk) has produced a paper describing this translation. Bob McGrath will present details later this morning. – A revision of the document will be forthcoming. Ullman HDF-EOS Workshop IV Page 12
    13. 13. Workshop III Action Status 11. Poll teams about the occurrence of hybrid HDF-EOS/HDF products. What HDF4 primitives are used? STATUS: COMPLETE – Nearly all HDF-EOS products defined to date also contain other HDF object within them. – Transition to HDF-EOS v3 will require attention of the data providers and is likely to take several years. Ullman HDF-EOS Workshop IV Page 13
    14. 14. Workshop III Action Status 12. Provide a clear schedule and strategy for HDF-EOS using HDF5 with recommendations for data migration and for new application development. STATUS: This Workshop will answer – HDF-EOS 3 is available in Beta today. – We will explain the design and API in the course of this workshop. – Stable release in late winter. Ullman HDF-EOS Workshop IV Page 14

    ×