The following notes were taken by Elizabeth Rye. Corrections are welcome. (Notes in red indicate updates after the telecon.)
Planetary Data System Standards Teleconference
July 15, 2009 9-11 AM
THESE MINUTES ARE PRELIMINARY
Announcements:
None
Telecon Discussions:
1. SCR status:
- SCR3-1127: Pointer/Object Ambiguity in the Standards Reference
WG: R. Joyner (lead), M. Cayanan, L. Huber, S. Hughes, T. King, A. Raugh
- Updates were made by A. Raugh, D. Simpson, and R. Joyner.
- No objections from S. Hughes to changes in chapter 12.
- Version 6 posted online 07/15/09.
- Question from T. King: Is it clear with the proposed changes to sections 5.3.3.1 and 5.3.3.2 the context within which the names are required to be unique?
- For both 5.3.3.1 and 5.3.3.2, E. Rye to add "within the label" to the end of the change. Send out as version 7 for an e-vote.
- SCR3-1141: Increase DATA_QUALITY_ID to 16 characters
WG: R. Chen (lead), E. Rye
- Version 4 of the SCR was posted for discussion on 06/26/09.
- E. Rye noted that keyword originally had gendatatype = character before all "_ID" class words were changed to IDENTIFIER. (See PSDD v1r32.)
- SCR was voted on with the following results:
Node Voter Vote? Send to
MC?ATM L. Huber yes no GEO S. Slavney yes no IMG P. Garcia yes no NAIF B. Semenov absent absent PPI T. King yes no RINGS M. Gordon yes no RS D. Simpson abstain no SBN A. Raugh yes no EN E. Rye yes no
- SCR was approved by Tech Group; status will be updated and MC will be notified.
- SCR3-1145: PSDD Filename Length Clean-Up
WG: S. Slavney (lead), M. Gordon, R. Joyner, E. Rye
- Although version 2 of the SCR was posted on 06/02/09, it was mis-identified as being written by Dick Simpson on 10/15/08, making it appear to be identical to version 1. E. Rye has since updated the identifying information and sent the SCR to D. Simpson for review.
- D. Simpson has provided feedback including one comment that needs to be addressed (regarding case). E. Rye has forwarded comment to S. Slavney.
- Susie responded with version 3 of the SCR; E. Rye made slight edits and posted on 07/13/09. However, Anne had a follow-up comment that has not yet been addressed. (With regard to DATA_SET_LOCAL_ID: "None of these restrictions were in the original definition, nor do I believe it was ever limited to 8 characters.")
- Susie will remove references to DATA_SET_LOCAL_ID and issue version 4. E. Rye will distribute for discussion.
- SCR3-1146: Update reference format to handle DOIs
WG: A. Raugh (lead), P. Garcia, S. Hughes, R. Joyner, R. Simpson, S. Slavney, R. Walker (consult)
- D. Simpson has sent comments on v1 of SCR to A. Raugh
- Version 3 of SCR received from A. Raugh; posted on 07/13/09.
- Anne noted the following two points need discussion:
- Elizabeth has suggested that, since all references to the acronym "AGU" have now bee removed from the Standards Reference, the entry for "AGU" should be removed from Appendix F (Acronym List). (Todd suggests to remove.) Anne will update.
- In searching other documents for references to "AGU", I discovered that the definition for CITATION_DESC still mentions in. But this definition also refers readers to the REFERENCE object description in section B.31, which currently contains the PERSONNEL_INFORMATION object description. My opinion is that problems with the definition of CITATION_DESC are beyond the scope of this SCR, but of course others may disagree. Anne will add.
- Anne will make two modifications, resulting in version 4.
- SCR3-1148: Phoenix keywords
WG: E. Rye (lead), R. Alanis, S. Slavney, B. Sword
- Seven keyword templates have been submitted, but they still have a lot of problems; will have to be worked out with team before SCR can be distributed.
- E. Rye would like to change lead to Rafael Alanis.
- SCR3-1150: Change minimum value for detector_temperature
WG: R. Chen (lead), E. RyeLyle message c i Susie m c warning Patty m a w Todd conversion c w Mitch m b i Dick m c w Anne m a abstain Elizabeth m c w a) both non-default units, value outside of range b) non-default units c) non-default units and default range specified
- E. Rye has recollected conversation with P. Ramirez detailing his concerns about proposed solution and sent these to Tech Group for further comment.
- Options proposed by Elizabeth and others:
- Revert back to Paul's initial suggestion of issuing a warning whenever non-default units are detected
- Issue an informational message whenever non-default units are detected
- Stay with our suggestion (that messages are only issued when non-default units are detected AND values are outside the default range)
- Paul's suggestion: If non-default units are used and there is a default min/max, issue a warning; if non-default units are used and there is NO default min/max, ignore.
- Mitch's suggestion: If non-default units are used and there is a default min/max, issue an information message; if non-default units are used and there is NO default min/max, ignore.
- Josh's suggestion: If non-default units present and default range specified, perform conversion in validating software to determine if label values are valid.
- Summary of comments received:
Lyle ATM c, although d has merit Dick RS a Richard EN rank as c, d, a, b Mitch RINGS f,e Josh AMES f Betty EN favors warnings over info msgs Susie GEO f Todd PPI f - Sean (and EN) Ames and JPL/EN have agreed to use common tool library underlying validation tools; any changes will have to be made to this library. There is a tool release today (or tomorrow?), so any changes would have to go into queue for next release. Is this deemed high enough priority to make these significant changes?
Node Voter Message
or
Conversion?Option? Type
of
Message?ATM L. Huber message c informational GEO S. Slavney message c warning IMG P. Garcia message a warning NAIF B. Semenov absent absent absent PPI T. King conversion c warning RINGS M. Gordon message b informational RS D. Simpson message c warning SBN A. Raugh message a abstain EN E. Rye message c warning
- SCR3-1151: Change TELEMETRY_FORMAT_ID from STATIC to SUGGESTED
WG: R. Chen (lead), S. Joy, B. Sword, E. Rye
- Email sent to R. Chen asking him to research Dawn values and write up SCR; also sent to D. Simpson asking him to beef up keyword description based on information relayed during last telecon.
- R. Simpson responded that he was mainly guessing and that more research into how this is actually used by both Dawn and Galileo is necessary before changing keyword. E. Rye asked R. Chen to look into it.
- Rich contacted team; no response yet, so no update.
- SCR3-1152: Change STANDARD_VALUE_TYPE and MAXIMUM_LENGTH for SPACECRAFT_POINTING_MODE to SUGGESTED and 25 respectively
WG: P. Garcia (lead), B. Sword
- Draft SCR received from B. Sword and P. Garcia by E. Rye. E. Rye sent some comments back to them (and ask R. Joyner for his opinion).
- Would like a vote soon.
- Dick objects to handing this s/c pointing to missions, without proper definitions for values. Todd - as long as accompanying description is required, no point to having carefully prescribed value Anne - accompanying desc. is not to provide generic description but rather specific information Elizabeth - if description is only in accompanying keyword, we lose control; if in PSDD, we retain control over quality
- SCR3-1153: Approval of MSL Keywords
WG: E. Rye (lead), J. Diehl, S. Slavney, B. Sword
- (Note, E. Rye would like to add MSL_OPS sysclassid if multiple values permitted. (I asked John Ho about this. Yes, can be done but ingestion and search could be problems.) Also, need to alias SEQ_id to SEQUENCE_ID if I can figure out how to do it.) Why APPLICATION_PACKAGE_ID rather than simply SOFTWARE TELEMETRY_SOURCE_ID needs better definition, justification, and standard value list. SEQUENCE_ID remove specific reference to spacecraft or make specific SPACECRAFT_SEQUENCE_ID. Take out sentence "May replace older..." ROVER_MOTION_ "potentially unique location" "may" need more specific terminology ROVER_MOTION_COUNTER_NAME change "array" to "sequence of values" (more specific PDS terminology) Add MSL description.
2. Further Issues:
- None
Next telecon scheduled for 2009-07-29.