Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-34370

Analyze the Rotator Test Data

    XMLWordPrintable

    Details

    • Story Points:
      3
    • Epic Link:
    • Sprint:
      TSSW Sprint - Apr 25 - May 09, TSSW Sprint - May 09 - May 23, TSSW Sprint - May 23 - Jun 06
    • Team:
      Telescope and Site
    • Urgent?:
      No

      Description

      Analyze the rotator test data.

        Attachments

        1. Data_analysis_comments_hd.docx
          1.29 MB
        2. data analysis.docx
          1.28 MB
        3. jump_rotator_position.png
          jump_rotator_position.png
          201 kB
        4. reproduce_0.jpg
          reproduce_0.jpg
          312 kB
        5. reproduce_1.jpg
          reproduce_1.jpg
          301 kB

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-34854 Support the Rotator Test on Summit Part 4

          • Done
          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-35018 Analyze the Rotator Test Data Part 2

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment - - edited

            I can reproduce the Simulink error of transition from tracking to point-to-point movements in:
               

            I think the problem is because the trajectory generator does not clean the internal data from transition into the Fault state. In addition, for the simulation after tracking and Fault, the rotator actual position and position command are totally wrong basically (the simulation shows the position jumps):

            I send the email to Ander for this bug already.

            Show
            ttsai Te-Wei Tsai added a comment - - edited I can reproduce the Simulink error of transition from tracking to point-to-point movements in:     I think the problem is because the trajectory generator does not clean the internal data from transition into the Fault  state. In addition, for the simulation after tracking and Fault, the rotator actual position and position command are totally wrong basically (the simulation shows the position jumps): I send the email to Ander for this bug already.
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Analyze the data in data analysis.docx.

            Show
            ttsai Te-Wei Tsai added a comment - Analyze the data in  data analysis.docx .
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Please help to review the report and the PR:
            https://github.com/lsst-ts/ts_notebooks/pull/85

            Thanks!

            Show
            ttsai Te-Wei Tsai added a comment - Please help to review the report and the PR: https://github.com/lsst-ts/ts_notebooks/pull/85 Thanks!
            Hide
            Permalink
            hdrass Holger Drass added a comment -

            Thanks, Te-Wei for this great work and the explanations. I added the discussed change here: Data_analysis_comments_hd.docx

            Show
            hdrass Holger Drass added a comment - Thanks, Te-Wei for this great work and the explanations. I added the discussed change here: Data_analysis_comments_hd.docx
            Hide
            Permalink
            hdrass Holger Drass added a comment -

            I fully approve! Thanks Te-Wei!

            Show
            hdrass Holger Drass added a comment - I fully approve! Thanks Te-Wei!

              People

              Assignee:
              ttsai Te-Wei Tsai
              Reporter:
              ttsai Te-Wei Tsai
              Reviewers:
              Holger Drass
              Watchers:
              Holger Drass, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.