-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Command
and Command not run
events
#308
Conversation
I'm a little confused by the twiki documentation for Commands that says "Additional command parameters PARAM=VALUE are separated by space. These should be upper case." |
@@ -194,6 +189,8 @@ def cmd_set_end_scs(*args, date=None): | |||
|
|||
def cmd_set_command_not_run(*args, date=None): | |||
(cmd,) = cmd_set_command(*args, date=date) | |||
# Save original type which gets used later in CommandTable.remove_not_run_cmds(). | |||
cmd["params"]["__type__"] = cmd["type"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine, though the name __type__
wasn't intuitive for me. But I suppose anything else would get pretty long __not_run_orig_type__
etc.
The inclusion of utils/make_hrc_disable_events.py isn't really explained in the description (and maybe belong in a different PR at this point?). But it is a good idea to get that script into the project even if already OBE with https://github.com/sot/kadi/pull/309/files . And the functional test makes more sense to me on the second reading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me with a lien to update the twiki "Additional command parameters PARAM=VALUE are separated by space" text (if I've understood correctly that is defunct as of this PR).
bbe73f8
to
9649618
Compare
I rebased to fix the merge conflict in new tests from #309 and fixed the TWiki docs. |
Description
This improves the
Command
andCommand not run
event types in the Command Events Sheet.The documentation states that a
Command
orCommand not run
can be copy/pasted from the backstop file. In that format the parameters are comma-delimited, but the code was expecting space-delimited. In the flight Sheet we had only previously used a single parameterTLMSID=...
so it never came up. The code now uses theparse_cm
backstop parser and thus requires comma-delimited parameters.This PR adds the capability (along with a number of tests) to include multiple parameters in the
Command not run
event to match only a single command. Previously only thedate
andTLMSID
were actually being used to select the command(s) to ignore. For disabling HRC this turns out to select an additional unwanted command 1.Note: this PR requires a
masters
environment to pass tests. (Test fails are unrelated to this PR, however).Interface impacts
Format for
Command
andCommand not run
eventParams
changed to match the existing documentation (see link in the Sheet).Testing
Unit tests
Independent check of unit tests by Jean
Functional tests
Footnotes
This ends up being benign but still not desirable. ↩