In molecular modeling, a task that takes only a few minutes can become a persistent source of friction when it has to be repeated across many structures, documents, or analysis sessions. Repeating the same manual steps also makes it harder to remember exactly what was done. A useful first step is to separate the work into two questions: Can I automate this task? and Do I need to add capabilities to SAMSON?
The SAMSON documentation points to two related paths: Scripting for Python automation and document-embedded workflows, and Extending SAMSON for installing extensions or exploring the SDK and extension development. Choosing the right path early can save time: scripting is the place to start when the goal is to automate work with the capabilities already available; extensions are relevant when the goal is to add capabilities or understand how SAMSON can be extended.
Start with the repeated task
Before writing a script, describe the task in ordinary language. For example: “I repeat the same preparation steps for each model,” or “I need to run the same analysis after each change.” Then identify which parts are consistent and which require a decision or visual inspection. The consistent steps are the best candidates for automation. Keeping judgment calls explicit helps avoid treating an automated workflow as if it were making scientific decisions on your behalf.
A simple planning checklist can make the first scripting attempt more focused:
- Inputs: What model, document, or other information does the task begin with?
- Repeated actions: Which steps do you perform in the same order each time?
- Choices: Which steps depend on your interpretation or on the particular model?
- Result: What should be produced or changed when the workflow finishes?
- Reuse: Would it help to keep the script or app in a document so the workflow is available with the work?
This checklist is not a substitute for learning SAMSON’s scripting tools. It helps you arrive at the documentation with a clearly defined problem, which makes it easier to decide what to automate and to check whether the result matches your intent.
Use scripting when the goal is repeatability
The scripting path covers SAMSON’s integrated Python environment, package management, running scripts, and embedding scripts or apps in documents. These are useful options when you want to reduce repeated manual work or keep a scripted workflow connected to a document. If reproducibility is your main concern, think beyond “make the steps run”: also consider what someone else—or you, several weeks later—would need to understand the workflow. A clear name, a short explanation of the purpose, and a note about the expected inputs and outputs can make a script easier to revisit.
Start small. Choose one repeated sequence rather than attempting to automate an entire modeling process at once. Run the workflow on a case you can inspect, compare the result with what you expect, and refine it before relying on it for broader use. This incremental approach makes unexpected behavior easier to locate and keeps the script’s purpose understandable.
Know when to explore extensions
Not every workflow problem is a scripting problem. If you need capabilities that are not available in your current setup, the extension path is the more relevant one. The documentation describes it as a place to learn about adding capabilities, managing extensions, and understanding the SDK and extension distribution path. You can go directly there if that is your immediate goal; there is no need to work through scripting first.
On the other hand, if you only need built-in capabilities and are not managing extensions, the extension material can wait. This distinction keeps the learning path practical: focus first on the tool that addresses the current bottleneck, then explore the other track when your needs change.
A practical route through the documentation
- Open Scripting if you want to automate tasks, run Python scripts, or explore document-embedded workflows.
- Move to Extending SAMSON if you want to install or develop capabilities, or learn about the SDK path.
- For scripted modeling or analysis pipelines, continue to Simulate and analyze. If you want to distribute scripted documents or work with others around them, see Share and collaborate.
The key is to begin with the pain you are trying to remove: repeated actions, a need to keep a workflow with a document, or a missing capability. That makes it easier to choose between scripting and extensions—and to learn only what you need next.
For the complete overview and suggested reading paths, visit Automate and extend.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
