In molecular modeling, a task that takes only a few minutes can become a source of friction when you have to repeat it across many structures, revisit it later, or share the steps with a colleague. Repeating actions by hand also makes it harder to keep a workflow consistent. A useful first step is to separate two needs: automating work you already do in SAMSON, and adding capabilities that are not currently available in your setup.
Start by identifying the kind of problem
If your goal is to reduce repeated manual work, make a workflow reproducible, or put Python scripts into a SAMSON document, begin with the Scripting guide. The documentation describes scripting as the foundational path for automation inside SAMSON. It covers using the integrated Python environment, managing packages, running scripts, and embedding scripts or apps in documents.
If instead you need to add capabilities or want to understand how SAMSON extensions are installed or developed, go to Extending SAMSON. That guide is the task-focused path for managing extensions and exploring the Software Development Kit (SDK) and extension distribution.
A practical way to plan automation
Before writing a script, describe the repeated task in plain language. What steps do you perform, and which parts are the same each time? This simple inventory helps clarify whether your problem is a good fit for scripting or whether it calls for an additional capability. It also gives you a concrete starting point when you consult the relevant guide.
Next, decide whether the workflow needs to travel with the document. If you want a scripted workflow to be packaged for reuse or shared with others, the documentation points to scripting and document-embedded scripts or apps as relevant topics. Thinking about this early can help you choose a workflow structure that makes sense for the way you intend to use it.
Finally, keep the scope manageable. Start with one repeated task rather than trying to automate an entire modeling process at once. Once you know what you want SAMSON to do, use the scripting guide to explore the integrated Python environment, package management, and script execution. The documentation does not prescribe a particular script or modeling procedure here; it provides the route to the tools and guidance for building your own workflow.
When you need more than a script
Automation and extensions solve different kinds of problems. A script is a sensible starting point when you want to automate an existing workflow or make it reproducible. An extension is the path to investigate when your immediate need is to add capabilities, manage installed extensions, or learn about development and distribution through the SDK.
You do not need to study both paths if only one applies. If you are not writing Python or embedding scripts, you can skip the scripting material for now. If you only need built-in capabilities and are not managing extensions, you can skip the extension material. This keeps the learning path focused on the problem you are actually trying to solve.
Choose your next step
- Automate a repeated task: start with Scripting.
- Package a reproducible scripted workflow: explore Scripting.
- Install or develop capabilities: continue to Extending SAMSON.
Once your automation or extension work is underway, the documentation also points to Simulate and analyze for scripted modeling, path generation, or analysis pipelines, and Share and collaborate for distributing scripted documents or collaborating around them.
For the complete overview and recommended reading order, visit the Automate and extend documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
