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

Document Labview Steps & other steps

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_documentation
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      TSSW Sprint - Nov 25 - Dec 6, TSSW Sprint - Dec 9 - Dec 20, TSSW Sprint - Jan 06 - Jan 17
    • Team:
      Telescope and Site

      Description

      Begin the documentation on the ts_sal repository. Currently there only exists PDF's outside of the repo. This is to create the SAL User Guide which will exist as a tech note. 

        Attachments

          Activity

          Hide
          aheyer Andrew Heyer [X] (Inactive) added a comment -

          Also document the steps for getting the cabinet turned on and the EUI software running.

          Show
          aheyer Andrew Heyer [X] (Inactive) added a comment - Also document the steps for getting the cabinet turned on and the EUI software running.
          Hide
          aheyer Andrew Heyer [X] (Inactive) added a comment -

          This is to remind myself to also include the documentation for the different acknowledgements here is a snippet of an email that Te-Wei wants,

          Hi Bo,

          I checked with Dave for the standard SAL mechanism for command.

          If a client sends a SAL command to a CSC, the CSC will use the command
          acknowledgement (ackCmd) to notify the client the receive of command. If
          the CSC failed this command (reject or fail the execution), it will use
          the ackCmd (the same as the previous one) with different error code and
          arguments to notify the client for the failure.

          Dave mentioned Andrew should have a confluence page to explain this.

          To Andrew, could you help to provide that confluence page to Bo?

          Thank you!

          Te-Wei Tsai

          Show
          aheyer Andrew Heyer [X] (Inactive) added a comment - This is to remind myself to also include the documentation for the different acknowledgements here is a snippet of an email that Te-Wei wants, Hi Bo, I checked with Dave for the standard SAL mechanism for command. If a client sends a SAL command to a CSC, the CSC will use the command acknowledgement (ackCmd) to notify the client the receive of command. If the CSC failed this command (reject or fail the execution), it will use the ackCmd (the same as the previous one) with different error code and arguments to notify the client for the failure. Dave mentioned Andrew should have a confluence page to explain this. To Andrew, could you help to provide that confluence page to Bo? Thank you! Te-Wei Tsai
          Hide
          aheyer Andrew Heyer [X] (Inactive) added a comment -

          ts_sal now is configured to hold  tech note. You can see the page here https://github.com/lsst-ts/ts_sal/tree/feature/andrewheyer/DM-22407

          and the lsst.io page for it is here https://ts-sal.lsst.io/v/feature-andrewheyer-DM-22407/index.html

          Show
          aheyer Andrew Heyer [X] (Inactive) added a comment - ts_sal now is configured to hold  tech note. You can see the page here  https://github.com/lsst-ts/ts_sal/tree/feature/andrewheyer/DM-22407 and the lsst.io page for it is here  https://ts-sal.lsst.io/v/feature-andrewheyer-DM-22407/index.html
          Hide
          ecoughlin Eric Coughlin added a comment -

          Can see that its published.

          Show
          ecoughlin Eric Coughlin added a comment - Can see that its published.

            People

            Assignee:
            aheyer Andrew Heyer [X] (Inactive)
            Reporter:
            aheyer Andrew Heyer [X] (Inactive)
            Reviewers:
            Eric Coughlin
            Watchers:
            Andrew Heyer [X] (Inactive), Eric Coughlin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.