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
Description:
We are looking to refactor our current SLURM job submission implementation, which writes to a temporary sbatch script, to use the --wrap option directly within Python's subprocess.run(). This change aims to simplify the process by avoiding the creation of temporary files.
Current Implementation:
The existing code writes an sbatch script to a temporary file and submits it using subprocess.run(). The job submission details like memory, time, output, and error file paths are set within this script, along with the command to be executed.
Proposed Change:
We want to eliminate the temporary script file and use the --wrap argument to pass the command directly to sbatch via subprocess.run().
The text was updated successfully, but these errors were encountered:
Description:
We are looking to refactor our current SLURM job submission implementation, which writes to a temporary sbatch script, to use the
--wrap
option directly within Python'ssubprocess.run()
. This change aims to simplify the process by avoiding the creation of temporary files.Current Implementation:
The existing code writes an sbatch script to a temporary file and submits it using
subprocess.run()
. The job submission details like memory, time, output, and error file paths are set within this script, along with the command to be executed.Proposed Change:
We want to eliminate the temporary script file and use the
--wrap
argument to pass the command directly tosbatch
viasubprocess.run()
.The text was updated successfully, but these errors were encountered: