Compute
HPC Tasks
Follow the accelerated tool and pipeline jobs a Drylab chat submits to GPU and HPC hardware: status, cost, logs, output files and how to cancel a run.
When an analysis uses an accelerated tool (for example Boltz2 or DiffDock) or an nf-core pipeline, Drylab submits a job to dedicated GPU/HPC hardware instead of running it in your sandbox. HPC tasks lists those jobs for the current chat.
Open HPC tasks
As soon as a chat submits its first job, an HPC tasks tab appears in the chat's top bar, next to Result. Chats without jobs don't show the tab.
You can also reach your jobs from Activity in the left sidebar: under HPC jobs it lists your recent jobs with their status. Click one to open it in its chat.
Follow your jobs
The tab shows the list of jobs on the left and the selected job's details on the right.
- The list groups jobs into Needs attention, Running and Done. Runs of the same tool are folded into one row that shows how many runs there are, their total cost and when the latest one ran; open the row to see each run.
- Search runs finds a job by tool name, status or job ID.
- The details show when the job started (in your own time zone), how long it took, which GPU it Runs on, and its Cost in compute credits. Tool jobs have a Log and Output files; pipeline jobs add Tasks, Parameter and Metrics tabs. Click Copy job ID if support asks for it.
If a job fails, the details say why and what to do next, for example: "The job ran out of GPU memory. Ask the agent to rerun it with a smaller input or tile size, or on a larger GPU. Failed runs are billed for the time used."
Results are saved to your Storage. Drylab copies the key outputs into the chat's folder; full pipeline outputs are kept under the nextflow-pipelines folder.
Cancel a pipeline run
Open the run and click Cancel run, then confirm in Cancel this pipeline run?. Running steps stop and the run can't be resumed; finished steps keep their outputs. To stop a tool job, ask Drylab in the chat to cancel it.
Submitting a job
You don't submit jobs by hand. Mention the tool or pipeline, or just describe the task, and Drylab submits the job as part of the plan. For example:
- "@Boltz2 predict the structure of this protein with ATP bound."
- "Run @nf-core Rnaseq on the FASTQ files in my project with GRCh38."
Jobs are part of the plan Drylab proposes, so you see which tool or pipeline it will run before you approve the plan.
Access and cost
- Each tool and pipeline shows its price in the
@picker's Resource Preview, per run or per hour.
See Usage.