Currently we have a somewhat confusing default value for -q, basically,
- If left unspecified, we use localhost as the default queue, which is by default a process queue but can be PBS queue as well.
- If we set
-q none, the tasks are handled as part of substep and no queue is used.
- if we set
-q host, we use host, and -q localhost is allowed.
- Under a cluster environment, we say the default is
-q none.
Because unspecified -q is usually understood as -q None, the selection of default value seems to be confusing. It would perhaps make more sense to
- If
-q is unspecified, namely if a None queue is specified, we disregard task keyword.
- For the use of any queue, even localhost,
-q is needed. This is the point of change where -q localhost will be needed for all our examples that use localhost.
I feel that this is more consistent and we do not need to have different default behavior for cluster and non-cluster environments.
Currently we have a somewhat confusing default value for
-q, basically,-q none, the tasks are handled as part of substep and no queue is used.-q host, we usehost, and-q localhostis allowed.-q none.Because unspecified
-qis usually understood as-q None, the selection of default value seems to be confusing. It would perhaps make more sense to-qis unspecified, namely if aNonequeue is specified, we disregardtaskkeyword.-qis needed. This is the point of change where-q localhostwill be needed for all our examples that use localhost.I feel that this is more consistent and we do not need to have different default behavior for cluster and non-cluster environments.