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
Is there a way to configure the executor so job logs to the log locations specified in my rules? (i.e. just like when running my workflow locally outside of SLURM). So instead of everything going to .snakemake/slurm_logs
The text was updated successfully, but these errors were encountered:
In hindsight it actually makes sense to me the way it is, SLURM specific snakemake logging, job info and e.g. restarts/retries etc go into .snakemake/slurm_logs and the regular rule log output of the successful execution of the rule goes into the rule log path. It's less clutter and you don't need to see the rule regular logging from failed execution attempts mixed in with SLURM specific logging if the job needed to restart for any reason.
absolutely, that was the intend. However, the reason, why I leave this issue open is
that the feature was requested multiple times
that i want to feature optional deletion of SLURM outputs (they are mostly redundant and if a workflow suceeds, they can go away as the logging information by Snakemake contains all valuable info, plus the report, etc.)
Is there a way to configure the executor so job logs to the log locations specified in my rules? (i.e. just like when running my workflow locally outside of SLURM). So instead of everything going to
.snakemake/slurm_logs
The text was updated successfully, but these errors were encountered: