Details
-
Type:
Improvement
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_auxiliary_telescope
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:TSSW Sprint - Mar 18 - Mar 30, TSSW Sprint - May 28 - Jun 8, TSSW Sprint - Jun 10 - Jun 22
-
Team:Telescope and Site
Description
Each script available to the queue have different sets of configuration parameters. To know them, we currently have to look into the code… It would be very helpful to be able to “ask the queue” what are the parameters of a specific script are. Ideally, when the queue receives such a command it would not put the script to run on the queue, but rather, read the configuration parameters from it and publish it through an event.
I think that it would suffice to get the docstring from the configure method and output that to SAL.
In [1]: from lsst.ts.scriptqueue.test_utils import TestScript |
Could not import lsstcppimport; please ensure the base package has been built (not just setup). |
|
|
In [2]: print(TestScript.configure.__doc__) |
Configure the script.
|
|
Parameters
|
---------- |
wait_time : `float` |
Time to wait, in seconds |
fail_run : `bool` |
If True then raise an exception in `run` after the "start" |
checkpoint but before waiting.
|
fail_cleanup : `bool` |
If True then raise an exception in `cleanup`. |
|
Raises
|
------ |
`salobj.ExpectedError`
|
If ``wait_time < 0``. This can be used to make config fail. |
Although I'm not sure how that would work for non-python scripts.
In addition to the change specified I also did two other things:
Pull requests:
Rob Bovill could you please review the ts_xml ticket branch? I'll ask Tiago Ribeiro to review the other pull requests.