Ensuring Compatibility for Your SAMSON Extensions

Molecular modelers rely on software like SAMSON to design and simulate complex molecular systems. A key aspect of using SAMSON effectively is ensuring that its Extensions are compatible with the current software version. Let’s explore how SAMSON handles this process and how its versioning system can help you avoid compatibility issues.

Why Compatibility Matters

SAMSON Extensions provide powerful tools to extend the platform’s capabilities, from customized simulations to additional analysis modules. However, these Extensions are built with specific versions of the SAMSON Software Development Kit (SDK). If the version of SAMSON you’re using doesn’t align with the SDK version of an Extension, the Extension won’t load, and you may miss out on its functionality.

Understanding SAMSON’s Versioning System

SAMSON uses a semantic versioning policy to ensure compatibility, making it easier for users to understand which Extensions will work with their current installation. Here’s how it works:

  • Major Version: Indicates non-backwards-compatible updates. If the major version of SAMSON differs from the SDK version used to build an Extension, the Extension won’t load.
  • Minor Version: Represents backwards-compatible updates with added features. Extensions built with SDK versions where the minor version is smaller than SAMSON’s minor version are compatible.
  • Patch Version: Indicates backwards-compatible bug fixes. Patch versions do not affect compatibility.

How SAMSON Ensures Compatibility

When SAMSON starts up, it checks the SDK version used to build each installed Extension. It loads the Extension only if:

  • The major version of the SDK matches SAMSON’s major version.
  • The minor version of the SDK is less than or equal to SAMSON’s minor version.

This system guarantees that Extensions built with older, compatible SDKs will continue to function as SAMSON evolves with new features and fixes.

Automatic Updates for Extensions

SAMSON features automatic updates for Extensions, ensuring you always have access to the latest compatible versions. For example, let’s consider a scenario:

  • Your current SAMSON version is 1.7.8, and an Extension is built with SDK version 1.5.2; this Extension will load without issues.
  • Later, if a new Extension version built with SDK 1.6.4 becomes available, SAMSON will update to this version, provided it’s compatible with your existing SAMSON installation.

However, if a new version of SAMSON (e.g., 2.0.0) and its SDK is released, Extensions built with this latest SDK will not auto-update unless SAMSON itself is updated to the corresponding major version. This ensures system stability and avoids potential errors due to incompatible features.

Conclusion

By understanding SAMSON’s compatibility checks and semantic versioning policy, molecular modelers can ensure a seamless experience while using Extensions. Remember to update your SAMSON platform regularly to access the latest features and avoid compatibility concerns. For further details, you can visit the full documentation at this page.

SAMSON and all SAMSON Extensions are free for non-commercial use. You can download SAMSON at SAMSON Connect.

Comments are closed.