Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4224

Enable non-sidereal tracking in the TMC Mid

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      Enables the telescopes to track non-sidereal objects, which is a gap in their current functionality.

      Show
      Enables the telescopes to track non-sidereal objects, which is a gap in their current functionality.
    • Hide
      • TMC Mid implements the interface agreed between OSO and TMC to process observation of non-sidereal object
      • TMC Mid can be demonstrated to issue the required control commands to allow the MID telescope to track non-sidereal objects.
      • The functionality is tested with BDD test scenario
      Show
      TMC Mid implements the interface agreed between OSO and TMC to process observation of non-sidereal object TMC Mid can be demonstrated to issue the required control commands to allow the MID telescope to track non-sidereal objects. The functionality is tested with BDD test scenario
    • 3
    • 3
    • 0
    • Team_HIMALAYA
    • Sprint 3
    • Hide

      As per updated scope, TMC Mid supports tracking of non-sidereal object.

      The changes in JSON format between OSO and TMC are identified, agreed and implemented. TMC validates the JSON schema using CDM which internally uses telmodel. This deviation was agreed between the teams early in the PI due to ease of validation at TMC side using CDM.

      TMC mid uses KATPoint to fetch the trajectory details of non-sidereal objects in solar system and calculates AzEl coordinates accordingly.

      Integration with real Dish is not completed due to a bug on dish side (SKB-514) reported during testing. This bug will be fixed in PI 24.

      The work on TMC Low is pushed to PI 24. Separate feature SP-4506 is created to account the work.

      Show
      As per updated scope, TMC Mid supports tracking of non-sidereal object. The changes in JSON format between OSO and TMC are identified, agreed and implemented. TMC validates the JSON schema using CDM which internally uses telmodel. This deviation was agreed between the teams early in the PI due to ease of validation at TMC side using CDM. TMC mid uses KATPoint to fetch the trajectory details of non-sidereal objects in solar system and calculates AzEl coordinates accordingly. Integration with real Dish is not completed due to a bug on dish side (SKB-514) reported during testing. This bug will be fixed in PI 24. The work on TMC Low is pushed to PI 24. Separate feature SP-4506 is created to account the work.
    • 23.6
    • Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI24 - UNCOVERED

    • Team_HIMALAYA Team_SAHYADRI

    Description

      What & Why?

      Currently the TMC is only capable of controlling the MID and LOW telescopes to observe celestial objects which move in a sidereal manner (e.g. motion consistent with the rotation of the Earth). There are multiple uses for tracking objects which have non-sidereal motion (planets, satellites etc). 

      The key feature of non-sidereal targets is that they are not at a fixed RA/Dec or Alt/Az, but instead have continually changing positions in both of those coordinate systems.

      For many solar system bodies (Sun, Moon, planets and their satellites) there is support in katpoint's Target - this may be used to calculate positions at given times and to derive delays. For artificial satellites in earth orbit some are supported in katpoint (TBC) or a "Two Line Element" with orbital elements may be specified.

      To track a non-sidereal target this may be used to provide the RA/Dec or Alt/Az input as a function of time.

      For LOW the tracking position in RA/Dec sent to MCCS should be updated at required timestamps.

      For MID the position in AltAz can be generated from Target for sending to dish.

      Where does the target name or ephemeris table or tle table come from? For the targets supported by katpoint the OSO software will simply send the name of the required target. For less common targets the table will originate with the user and arrive via OSO. (This is lower priority at present).

      The further step in this is that the celestial position used in the delay polynomial calculations also needs to be updated. Again common targets are in katpoint and that support can be used. At the moment it should be assumed that current polynomial update rates and validity periods may be used.

       

      Who?

      • Science Operations.
      • Commissioning Science.
      • Astronomical Community.

      Attachments

        Issue Links

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                Adam.Avison Avison, Adam
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (86.67%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   12.0
                  Complete513.0
                  Total615.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel