Skip to content

Accessing outside computing resources

A tool runs in a tool session on the hub's execution hosts. The session carries the interface the user works in. Light calculations run in the session itself; heavier ones are sent to a cluster or a national resource with the submit command, which keeps the session responsive and returns the results when the job finishes.

Note

submit is part of the tool execution platform, which is separate software and is not in this repository. Nothing on these pages could be checked against the code here, and the CMS holds no trace of the command — the only mention left in com_tools is a migration that dropped an old submit sessions table. The material is kept as the written record, corrected where it contradicted itself, and submit --help on your own hub is the authority on what your client accepts.

The pages here

Most tools reach submit from a Jupyter notebook now, so Submitting from a Jupyter notebook is the page to read if you are writing a new tool; the submit command reference below explains what the options it sets actually do.

Related reading: Jupyter notebooks as tools for publishing a notebook in the first place, and registering a tool for the publishing option that marks a tool as a web application.

Reviewed against 2.4-main @ e097e0236d on 2026-09-10.