A cloud calculation can finish successfully and still leave you with a frustrating question: where are the results, which job produced them, and who can see them? When protein predictions and molecular dynamics runs accumulate, tracking the files and context can become almost as important as launching the calculations.
SAMSON’s Job manager brings cloud jobs into one place. It lets you monitor jobs, control their execution, retrieve results, and keep useful identifying information with each job. A small amount of organization while a calculation is running can save time when you come back to it later.
Start with a clear job record
Open the Job manager from Interface > Job manager. You can also use Ctrl+6 on Windows or Cmd+6 on macOS. The manager is intended for jobs launched in the cloud from SAMSON by extensions that provide job functionality, including workflows such as AlphaFold, NVIDIA BioNeMo services, and GROMACS.
When you select a job, its details appear on the right. Use the job name and notes to distinguish it from similar calculations. A name that identifies the system or purpose, paired with a short note about what you want to remember, is more useful than relying on memory or a crowded folder. Job names and notes sync with your SAMSON Connect account, so the information is available there too.
Check status before looking for files
The Job manager lets you start, pause, and stop jobs, and monitor their progress. If you are returning to a calculation after a break, first select it and review its details rather than immediately searching your computer for output files. This helps connect the job record to the files and results you expect to retrieve.
Cloud calculations in SAMSON require Computing Credits. It is worth checking that requirement when planning cloud work. The documentation also describes a referral option for earning free credits; see the SAMSON Cloud Services referral page for details.
Retrieve results and know where they are
To download all files for a job, double-click the job. After downloading, the job’s context menu helps you distinguish between local files—files already downloaded—and remote files still stored in the cloud. It also provides access to the job’s view on SAMSON Connect.
This distinction is useful when troubleshooting a missing result: check whether the file is still remote before assuming it was not produced. And when you need the complete set of job files, use the documented download action rather than treating the job entry itself as the result.
Share the job, not just a filename
Cloud jobs launched from SAMSON can also be accessed from SAMSON Connect, where you can control who has access to them. That can make collaboration clearer: instead of passing around an isolated filename, you can direct a collaborator to the job view and manage its visibility. Before sharing, check the access settings so they match your intended audience.
A simple routine helps keep work findable: give each job a descriptive name, add a note with the context you will need later, monitor it in the Job manager, download files when you need them, and use the context menu to tell local from remote data. For shared work, check access on SAMSON Connect.
For more details, see the SAMSON cloud computations documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.