A molecular model can be difficult to reproduce even when the structure itself is easy to share. The steps that produced a result may live in a separate script, a researcher’s notes, or a sequence of interface actions that another person has to reconstruct. That creates friction for collaborators, students, and your future self.
SAMSON documents can hold more than molecular models: they can also embed scripts, files, and folders. This offers a practical way to keep a model and the materials needed to understand or continue its workflow together. Instead of sending several disconnected items, you can prepare one document that contains the project context and its accompanying resources.
Put the workflow beside the model
A useful starting point is to gather the materials that explain how to work with the model: relevant Python scripts, input or analysis files, and notes that describe the intended sequence of steps. In SAMSON, add files by dragging and dropping them into the application and choosing to embed them, or use Home > Embed files or Home > Embed folders.

Embedding stores the files and folders within the document, making it self-contained for transfer and sharing. A colleague can open the document and find the supporting materials alongside the model, rather than having to track down each file separately. An embedded Python script can be opened in the Code Editor by double-clicking it.
Make scripts approachable
A script is more useful to another person when its purpose is clear. Consider giving it a descriptive filename and adding comments or a short explanation of what it expects and what it does. These are general documentation practices, not special SAMSON features, but they can reduce guesswork when someone else opens the file.
SAMSON’s Code Editor can open and modify text files, including Python scripts, and run Python files. It integrates Monaco Editor and provides syntax highlighting and auto-completion. For a quick command or an exploratory step, the integrated Python Console is another option; open it through Interface > Python Console. Both give access to the SAMSON Python API through the Python Scripting Extension.

If you are beginning a script, the Code Editor includes Python templates demonstrating SAMSON Python API tasks. You can also copy Python code for supported commands, color palettes, and visual presets from their respective interface controls. Starting from generated or example code can be a helpful way to make an interface action part of a repeatable script, while keeping the resulting code available for review and editing.
Check the Python environment
Sharing a script does not automatically mean every recipient has the same Python packages installed. If a workflow uses additional packages, check the environment in SAMSON’s Python Package Manager, opened from the Python Console with Edit > Manage packages…. Packages can be installed by name, and version requirements can be specified in pip-style form, such as foo==1.2.0. The documentation also describes installing local packages, including an editable mode for active development.
For a shareable workflow, include enough context for recipients to identify any package requirements, and avoid assuming that a package installed on your computer will already be available on theirs. If you use editable installation while developing a local package, note that it points to the package’s source directory; moving that directory means the package needs to be installed again. The documentation also notes a possible editable-mode loading issue on some macOS installations.
A simple sharing checklist
- Embed the model’s related scripts and supporting files in the SAMSON document.
- Use clear filenames and explain the role of each script or data file.
- Tell recipients about any additional Python packages the workflow needs.
- Open the embedded script in the Code Editor and make sure the intended file is easy to identify.
- Share the SAMSON document through an appropriate channel, such as email, GitHub, or SAMSON Connect Documents.
This approach can help researchers attach analysis scripts to molecular models, teams share project files and workflow notes, and educators distribute interactive exercises. Most importantly, it gives the next person a clearer starting point: the model and its supporting materials travel together.
For details on the Python Console, package management, the Code Editor, and embedding files, see the SAMSON scripting documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
