Understanding SAMSON Extension Compatibility for Molecular Modeling

As a molecular modeler, you know how crucial it is for all your tools to function seamlessly. If you’ve ever been frustrated by incompatibilities between software versions and extensions, SAMSON has you covered with its clear approach to extension compatibility and versioning. In this blog post, we’ll delve into how SAMSON ensures that extensions match the platform’s version.

Why Compatibility Matters

Imagine spending hours setting up a molecular modeling task only to find that an extension is incompatible with your current software version. This is a common pain for many modelers. SAMSON addresses this challenge with a well-defined compatibility policy that leverages semantic versioning. Understanding this system can help you avoid downtime and ensure that your workflow is uninterrupted.

How SAMSON Manages Extension Compatibility

SAMSON compares its version number with the version of the Software Development Kit (SDK) that was used to build the extension. Extensions are only loaded if the SDK version is compatible with the SAMSON version. Here’s the compatibility rule:

  • Both the major version numbers (e.g., majorSDK and majorSAMSON) must be identical.
  • The minor version number of the SDK (minorSDK) must be smaller than or equal to the minor version number of SAMSON (minorSAMSON).

This ensures that extensions built with older SDKs remain functional with newer versions of SAMSON, as long as the major version number does not change. For example:

  • An SDK version 1.3.5 is compatible with SAMSON version 1.7.8, because the major versions match, and the minor version of the SDK (3) is smaller than the minor version of SAMSON (7).
  • An SDK version 2.0.0 is not compatible with SAMSON version 1.7.8, because the major version numbers differ.

Automatic Updates: A Time-Saver

SAMSON minimizes manual intervention by automatically updating extensions when newer, compatible versions are available on SAMSON Connect. For example, if you have SAMSON version 1.7.8 and an extension built with SDK version 1.5.2, SAMSON will load the extension during startup. If a newer version of the extension (built with SDK version 1.6.4) becomes available, SAMSON will update it automatically, ensuring you always have the latest features.

However, if SAMSON 2.0.0 is released and an updated extension is built with the corresponding SDK, the extension won’t be updated automatically unless you also update SAMSON to version 2.0.0. This approach safeguards against incompatibility issues while allowing extensions to evolve alongside the platform.

Tips to Stay Updated

To make the most of SAMSON’s features and extensions:

  • Update SAMSON frequently to access new features and bug fixes.
  • Check SAMSON Connect for updates to your favorite extensions.

By keeping your software up-to-date, you ensure a smoother modeling experience without compatibility headaches.

To learn more, visit the official documentation: https://documentation.samson-connect.net/users/latest/versioning/

SAMSON and all SAMSON Extensions are free for non-commercial use. You can get SAMSON at https://www.samson-connect.net.

Comments are closed.