Ensuring Compatibility of SAMSON Extensions: A Guide for Molecular Modelers

One of the most frustrating scenarios for molecular modelers is when a computational tool or its extensions fail to function properly due to version incompatibilities. If you’re using SAMSON, the integrative molecular design platform, understanding how version compatibility works can save you time and eliminate potential headaches. Let’s take a closer look at how SAMSON ensures compatibility between its core platform and its extensions.

Why Version Compatibility Matters 🔑

SAMSON Extensions are additional tools that expand the platform’s capabilities, enabling you to perform specialized tasks for molecular modeling and design. However, extensions rely on a specific version of SAMSON’s Software Development Kit (SDK) to function correctly. Misaligned versions can lead to issues that prevent extensions from operating or cause unexpected behavior. That’s why SAMSON carefully adheres to semantic versioning conventions to minimize these risks.

How Compatibility is Managed

When you start SAMSON, the platform checks the version number of its own SDK against the version used to build each extension. Extensions are only loaded if their SDK version is compatible with the installed SAMSON version. Here’s how compatibility is determined:

  • Major version: The major version of the SDK used for the extension must match the major version of SAMSON itself. If these differ, the extension won’t be loaded.
  • Minor version: The minor version of the SDK for the extension must be less than or equal to SAMSON’s SDK minor version. This ensures that the extension doesn’t expect features that might not yet exist in SAMSON.

For instance, an SDK version 1.3.5 would be compatible with SAMSON version 1.7.8, but an SDK version 1.8.5 would not. This system ensures that extensions work seamlessly with the version of SAMSON you have installed.

Automatic Updates of Extensions

Keeping extensions up-to-date is crucial for accessing new features or bug fixes. SAMSON makes this process easy by automatically updating extensions when compatible versions become available on SAMSON Connect (assuming you’re connected to the Internet). Here’s how it works:

  • If an updated extension built with a compatible SDK version is released, SAMSON will download and install it automatically during startup.
  • If an incompatible version of the extension (e.g., built with a newer major version of the SDK) becomes available, SAMSON will retain the most recently installed compatible version to prevent disruptions.

For example, if SAMSON version 1.7.8 is installed and an extension built with SDK version 1.6.4 is released, the extension will be updated. However, if the extension is later updated to SDK version 2.0.0, SAMSON will not load the new version unless you update SAMSON to a compatible version.

What You Can Do

To ensure smooth operation and make the most of your SAMSON Extensions, remember these tips:

  • Regularly update SAMSON to the latest version to access new features and maintain compatibility with updated extensions.
  • Use the automatic update feature to effortlessly keep your extensions up-to-date.

To learn more about managing version compatibility in SAMSON, visit the official documentation page.

SAMSON and all SAMSON Extensions are free for non-commercial use. Start designing and innovating today by downloading SAMSON from SAMSON Connect.

Comments are closed.