You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The run method should be able to take in both the Executable and the command line arguments as a list, following e.g. wxflow's Htar class.
What are the requirements for the new functionality?
Marine DA Executable instances should not specify default_args except when those executables are reused.
Acceptance Criteria
DA job outputs are unchanged.
Suggest a solution (optional)
Something like
to something like
defrun(self, arg_list: list, silent: bool=False) ->str:
# Remove any empty arguments which can cause issues for running an Executablearg_list= [argforarginarg_listifarg!=""]
ifsilent:
output=self.exe(*arg_list, output=str, error=str)
else:
output=self.exe(*arg_list, output=str.split, error=str.split)
returnoutput
The text was updated successfully, but these errors were encountered:
When I incorporate the Jedi class into the marine jobs (see #2931), it will be using the execute from that class for running JEDI-based applications. (see
What new functionality do you need?
The
run
method should be able to take in both theExecutable
and the command line arguments as a list, following e.g. wxflow's Htar class.What are the requirements for the new functionality?
Marine DA
Executable
instances should not specifydefault_args
except when those executables are reused.Acceptance Criteria
DA job outputs are unchanged.
Suggest a solution (optional)
Something like
to something like
The text was updated successfully, but these errors were encountered: