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 JobLauncher interface for launch_run() is ambiguous in that some launchers require the list of nodes to run on (like aprun and mpirun) while others take the list of nodes to avoid (like srun and jsrun). For proper polymorphism, we need to settle on one approach so that the interface is consistent across all implementations.
Additionally, let's create a JobLauncherRun class to be returned by launch_run() which will later be passed to wait_run() or kill_run(). This class will represent a launched parallel run, and it will encapsulate the details of the proc and jobid values currently returned by launch_run. It could also provide stdout(), stderr(), and rc() functions so one can query the results of the parallel run.
The text was updated successfully, but these errors were encountered:
The
JobLauncher
interface forlaunch_run()
is ambiguous in that some launchers require the list of nodes to run on (likeaprun
andmpirun
) while others take the list of nodes to avoid (likesrun
andjsrun
). For proper polymorphism, we need to settle on one approach so that the interface is consistent across all implementations.Additionally, let's create a
JobLauncherRun
class to be returned bylaunch_run()
which will later be passed towait_run()
orkill_run()
. This class will represent a launched parallel run, and it will encapsulate the details of theproc
andjobid
values currently returned bylaunch_run
. It could also providestdout()
,stderr()
, andrc()
functions so one can query the results of the parallel run.The text was updated successfully, but these errors were encountered: