XTCE 1.1 RTF Avatar
  1. OMG Issue

XTCE11 — JPL-022

  • Key: XTCE11-312
  • Legacy Issue Number: 10228
  • Status: closed  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    DESCRIPTION OF REQUESTED CHANGE
    6. Elaborate on the "fixed" uplink bit-stream format … information from constant updates, as telemetry channel/evr/product information is changed, and unmanageably large file sizes.I think this has to do with Custom Stream sets. The concern is how does XTCE affect the file sizes of elemetry streams. Does XTCE impose an overhead on this? Using XTCE to generate telemetry stream would be interesting … is it efficient?
    RID RESPONSE:
    It would only DESCRIBE a telemetry stream and what it can describe about streams themselves is pretty minimal. Unless I misunderstand things I don't think there should be any problems here.There is no overhead imposed by XTCE, it is just the description of data..
    RID STATE: CLOSE

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Disposition: Resolved — XTCE 1.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT