When a molecular modeling task has to be repeated, the manual steps can become a workflow of their own: perform the same actions, check the same results, and try to remember exactly what you did last time. That repetition takes attention away from the scientific question—and makes it harder to share a process clearly with a colleague.
SAMSON’s scripting and extension tools offer two different ways to address that friction. Python scripting is the natural starting point when you want to automate work inside SAMSON or package a scripted workflow in a document. Extensions are the route to explore when you want to add capabilities or learn about development and distribution through the SDK.
First, identify the kind of problem you have
Before choosing a tool, separate two common needs:
- Repeating a task: If you are doing the same operations again and again, start with Scripting. The documentation identifies it as the foundational path for automation, reproducibility, and Python workflows embedded in SAMSON documents.
- Adding capabilities: If your goal is to install extensions or understand how to develop and distribute them, go to Extending SAMSON.
This distinction can save time. A script addresses repeated work; an extension is the path to investigate when the need is for additional capabilities. You do not have to learn both tracks just because they appear together in the documentation.
A practical way to approach automation
Begin by describing the task you repeat in plain language. What part is done manually? Is the aim to automate it, make a scripted workflow reproducible, or embed a script or app in a document? These are all goals covered by the scripting track. Writing down the task first helps you focus on the actual source of repetition rather than starting with tools you may not need.
Next, use the integrated Python environment as the entry point for scripting in SAMSON. The documentation also covers managing packages and running scripts, so package management is part of the scripting path—not a reason to jump immediately to extension development. If your intended workflow is meant to travel with a document, the same track covers embedding scripts or apps in documents.
Think of these as useful stages rather than a requirement to do everything at once: explore scripting, work with the Python environment and packages, then consider whether a script or app should be embedded in a document. That gives you a clear route from an individual automation need toward a workflow you can organize and share. The documentation page does not prescribe a particular scientific procedure, so the details of what your script does depend on your modeling task.
When to follow the extension path
If you only need built-in capabilities and are not managing extensions, you can skip the extension track for now. If you want to install or remove extensions, or you are a developer exploring the SDK and distribution, continue to Extending SAMSON. Keeping this distinction in mind prevents a common detour: exploring development topics before you have established whether a script can address the immediate need.
Choose the next step that fits
- For Python automation or a reproducible scripted workflow, read Scripting.
- For installing or developing capabilities, read Extending SAMSON.
- For scripted modeling, path generation, or analysis pipelines, continue to Simulate and analyze.
- For distributing scripted documents or collaborating around them, see Share and collaborate.
The useful outcome is not automation for its own sake. It is a clearer choice about what to learn next: use Python when the pain is repeated work, and explore extensions when the need is to add or manage capabilities. For the full overview and reading order, visit Automate and extend.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
