Satellite Operations Language Metamodel Avatar
  1. OMG Specification

Satellite Operations Language Metamodel — Closed Issues

  • Acronym: SOLM
  • Issues Count: 6
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Procedure.description in SpacePython linked to wrong text

  • Key: SOLM11-1
  • Legacy Issue Number: 19657
  • Status: closed  
  • Source: Peraton ( Brad Kizzort)
  • Summary:

    The comments in SetMomentumWheelSpeed.py state that the <module>._doc_ text corresponds to the Procedure.description attribute in the metamodel. This text should correspond the HeaderComment in the metamodel instead, and the Procedure.description should correspond to <module>.invoke._doc_

  • Reported: SOLM 1.0 — Tue, 18 Nov 2014 05:00 GMT
  • Disposition: Resolved — SOLM 1.1
  • Disposition Summary:

    Change text within SetMomentumWheelSpeed.py

    Change the text comment within SetMomentumWheelSpeed.py.

  • Updated: Mon, 16 Sep 2024 14:14 GMT

Change copyright in SpacePython files

  • Key: SOLM11-7
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    The SpacePython files should point to the copyright information within the SOLM specification itself rather than a single vendor.

  • Reported: SOLM 1.0 — Wed, 6 Dec 2023 19:19 GMT
  • Disposition: Resolved — SOLM 1.1
  • Disposition Summary:

    Change copyright in files

    Change the copyright to be based on the Object Management Group's SOLM specification

  • Updated: Mon, 16 Sep 2024 14:14 GMT

Datatype for ulong in SOLM11-2 resolution is incorrect

  • Key: SOLM11-11
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    Within space/parameters.py, the ulong (an unsigned type) is mapped to an int (a signed type). Should be mapped to unsigned (an unsigned format).

  • Reported: SOLM 1.0 — Fri, 26 Apr 2024 20:39 GMT
  • Disposition: Resolved — SOLM 1.1
  • Disposition Summary:

    Change ulong mapping to be "unsigned"

    Within the typeNames assignment of space/parameters.py, change int to unsigned in:
    'uint': unsigned, 'long': int, 'ulong': int,\

  • Updated: Mon, 16 Sep 2024 14:14 GMT

SpacePython is not compatible with Python version 3

  • Key: SOLM11-2
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    SpacePython is not compatible with Python version 3. Multiple script errors are encountered. Python version 2 is no longer supported, so software should be updated to work with later version.

  • Reported: SOLM 1.0 — Wed, 9 Nov 2022 22:58 GMT
  • Disposition: Resolved — SOLM 1.1
  • Disposition Summary:

    Update reference of Python 2.6 and deliver Python3 version of SpacePython files

    Within spec document, update references of Python 2.6 to Python 3.

    Apply changes to Python files to incorporate changes to make it work under Python3. These changes were performed using Git and a patch file is provided of the changes.

  • Updated: Mon, 16 Sep 2024 14:14 GMT
  • Attachments:

Parameter value query missing some attributes

  • Key: SOLM11-3
  • Status: closed  
  • Source: Boeing ( Mr. David Overeem)
  • Summary:

    ... While doing this we think we’ve identified an omission in the mapping table.

    If you look at the SOLM you’ll see this model for the Parameter. Note the highlighted aggregate object. If we go to the table for the mapping we see:

    Parameter.value()
    Parameter.raw()

    Of course raw() doesn’t exist in the model, but there’s a description (note uncal doesn’t exist). But the but is there’s no mapping item to get the timestamp. However in the reference implementation in a section that should be normative there’s the report method that returns the time and the value (effectively a tuple that represents the InstantValue – see the 6.4.6 description).

    In my book this should be a bug report to add a Parameter.report() that returns the InstantValue data as a tuple of value, timestamp. So can we report this as a bug?

  • Reported: SOLM 1.0 — Wed, 22 Mar 2023 14:52 GMT
  • Disposition: Deferred — SOLM 1.1
  • Disposition Summary:

    Defer to future minor revision version

    Defer to future revision.

  • Updated: Mon, 16 Sep 2024 14:14 GMT

Specification should not be tied to XTCE and GEMS terms

  • Key: SOLM11-4
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    The terms XTCE and GEMS should not be part of the SOLM meta models or functions that are projected from it (like SpacePython).

    The specification should talk about Parameters that are being queried (possibly as Spacecraft or Ground Parameters), though the transport/method should be decoupled since there are multiple interfaces that could be used (direct integration with an end product, via GEMS, via SNMP, via a message bus/C2MS, or perhaps via a database).

  • Reported: SOLM 1.0 — Wed, 22 Mar 2023 15:09 GMT
  • Disposition: Deferred — SOLM 1.1
  • Disposition Summary:

    Defer to future minor revision version

    Defer implementation until future revision

  • Updated: Mon, 16 Sep 2024 14:14 GMT