The model is only half the handoff: make your molecular workflow travel with it

A molecular project can be difficult to reproduce even when the structure itself is easy to share. The analysis script may be in a separate folder, input data may live on another computer, and a colleague may not know which steps to run—or which Python packages are needed. That creates friction for collaborators, students, and your future self.

SAMSON documents offer one practical way to keep project materials together: a document can contain molecular models as well as embedded files and folders, including Python scripts and app files. The aim is not to claim that every software dependency disappears. Rather, it is to make the project’s materials and instructions easier to carry, inspect, and share.

Build a handoff that explains itself

Before sharing a project, identify the files someone would need to understand or repeat the work. Depending on your workflow, that might include a Python script, input data, notes describing the analysis, or supporting files used by an app. Keep the contents organized so a recipient can tell what belongs together.

To add files or folders to a SAMSON document, drag and drop them into SAMSON and respond to the prompt, or use Home > Embed files or Home > Embed folders. The files are stored within the document, so you can transfer that document and its embedded materials together.

Dialog for embedding a file in a SAMSON document

A useful project handoff should also tell the next person what to do. For example, include a short note that identifies the script to run, the expected input, and the kind of output to look for. This small bit of context can save a collaborator from having to reconstruct your process from filenames alone.

Make the script easy to find and run

SAMSON’s Code Editor can open and run Python files. To open it, choose Interface > Code editor. You can run a script using Run in the editor, or use the integrated Python Console for quick execution. SAMSON’s Python Scripting Extension provides access to the SAMSON Python API, which can be used to automate workflows and work with models and simulations.

When a Python script is embedded in a document, double-click it to open it in the Code Editor. This creates a straightforward path from receiving the document to inspecting the script. For a recipient who wants to try the workflow, make the script’s purpose and any important assumptions clear in comments or accompanying notes.

SAMSON Code Editor interface

Check Python packages before sharing

A script may rely on Python packages beyond the SAMSON API. SAMSON provides a Python Package Manager, available from the Python Console through Edit > Manage packages…. It lets you review installed packages and install or uninstall packages using pip. You can specify versions—for example, foo==1.2.0—when a particular version matters.

Do not assume that embedding a script also installs its dependencies for whoever opens the document. Make a note of packages your script requires, and, when useful, include version information so the recipient knows what to check in the Package Manager. If you are developing a local package, SAMSON also supports installing it in editable/develop mode; that is useful during development, but the documentation notes that editable installs can fail to load on some macOS installations after restarting SAMSON.

A quick sharing checklist

  • Put the relevant scripts, data, and supporting files into a clear folder structure.
  • Embed the files or folders in the SAMSON document.
  • Add a short explanation of the workflow, including what to run and what it should do.
  • List external Python packages and any version requirements.
  • Open the embedded script in the Code Editor and review it before sharing.
  • Share the document through a method that suits your team, such as email, GitHub, or SAMSON Connect Documents.

This approach is useful for research handoffs, teaching exercises, and collaborative projects: the model and its related working materials can travel together, while the script remains available to inspect and run. For further details on the Python environment, package management, and embedding files, see the SAMSON Scripting documentation.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.