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

Rename scriptQueue to Queue

    XMLWordPrintable

    Details

    • Team:
      Telescope and Site
    • Urgent?:
      No

      Description

      The scriptQueue has now been used on sky and is beginning to prove useful. It was also the first time we tried to use it in an operational setting and it provided insight into how to make it better. 

      This ticket is to rename the scriptQueue to Queue, and to rename scripts as "Jobs"

      See comment for explanation.

      jobsQueue was also suggested as one could imagine there will be other Queue's that might cause confusion.

       

        Attachments

          Activity

          Hide
          pingraham Patrick Ingraham added a comment -

          One issue that constantly arose was how overloaded the word "script" is in the community. It's generally considered something that's often "quick" to make and does not adhere to any strict format. It also is often used for data reduction etc. It became confusing very quickly when someone would say, "We can script that." what one was referring to. 

          Renaming the scriptQueue to "Queue" and scripts to "Jobs" alleviates this confusion. The Queue does so much more than run unstructured scripts. It (along with salobj) provides the basis for the job to be written, command formatting, logging, passing meta-data to promote clarity, checkpoints, and providing more elegant interruption solutions than Ctrl+C! "Jobs" can then also be better defined to differentiate between production jobs (e.g. standard visit) and one-off's (e.g. try some weird test), which will come with different requirements in terms of required testing etc.

          Show
          pingraham Patrick Ingraham added a comment - One issue that constantly arose was how overloaded the word "script" is in the community. It's generally considered something that's often "quick" to make and does not adhere to any strict format. It also is often used for data reduction etc. It became confusing very quickly when someone would say, "We can script that." what one was referring to.  Renaming the scriptQueue to "Queue" and scripts to "Jobs" alleviates this confusion. The Queue does so much more than run unstructured scripts. It (along with salobj) provides the basis for the job to be written, command formatting, logging, passing meta-data to promote clarity, checkpoints, and providing more elegant interruption solutions than Ctrl+C! "Jobs" can then also be better defined to differentiate between production jobs (e.g. standard visit) and one-off's (e.g. try some weird test), which will come with different requirements in terms of required testing etc.
          Hide
          rowen Russell Owen added a comment -

          I think the old name is too entrenched to change it, and have not come up with a better name. I apologize for the confusion.

          Show
          rowen Russell Owen added a comment - I think the old name is too entrenched to change it, and have not come up with a better name. I apologize for the confusion.

            People

            Assignee:
            rowen Russell Owen
            Reporter:
            pingraham Patrick Ingraham
            Reviewers:
            Patrick Ingraham
            Watchers:
            Andy Clements, Michael Reuter, Patrick Ingraham, Robert Lupton, Russell Owen, Tiago Ribeiro
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.