For molecular modelers using SAMSON, ensuring compatibility between extensions and the platform itself is critical. The seamless functionality of SAMSON depends on its strict semantic versioning policy, which ensures that incompatible extensions are not loaded. Let’s explore how SAMSON manages compatibility and how it impacts your workflow.
How SAMSON Ensures Compatibility
SAMSON extensions are built using a specific version of the SAMSON Software Development Kit (SDK). During startup, SAMSON checks the version of the SDK used to build each installed extension and determines compatibility based on the major and minor version numbers. This ensures that extensions only work if they are compatible with SAMSON’s own version number, avoiding potential issues.
Here’s the precise criteria used by SAMSON:
majorSDK(the major number of the SDK version) must matchmajorSAMSON(the major number of the SAMSON version).minorSDK(the minor number of the SDK version) must be equal to or smaller thanminorSAMSON(the minor number of the SAMSON version).
For example, if your SAMSON version is 1.7.8, extensions built with SDK versions 1.3.5 or 1.7.7 are compatible because they comply with the above criteria. However, an extension built with SDK version 1.8.5 would not be loaded because its minor version exceeds that of SAMSON.
Why Compatibility Matters
Extensions developed with newer SDK versions often use updated features or functions that might not exist in earlier SAMSON releases. By enforcing compatibility checks, SAMSON ensures that you don’t encounter disruptions or errors caused by loading incompatible extensions. This also encourages users to update SAMSON regularly to take advantage of the latest features and fixes.
Automatic Updates for Peace of Mind
SAMSON comes with an automatic update functionality for extensions. When an Internet connection is available, SAMSON will automatically update your extensions if new compatible versions are detected on SAMSON Connect. This way, you can always benefit from improvements in the tools you use without manual intervention or compatibility concerns.
For instance, let’s say you’re using SAMSON version 1.7.8 with an extension built on SDK version 1.5.2. This extension will work seamlessly. If a new extension version, built with SDK version 1.6.4, becomes available on SAMSON Connect, SAMSON will update your extension automatically. But if SAMSON version 2.0.0 is released, and the developer updates the extension for this new major version, you will need to update SAMSON to continue using its latest features.
Takeaways for Molecular Modelers
As a molecular modeler, ensuring the compatibility of your tools is essential for a smooth workflow. Here are some practical tips:
- Update SAMSON regularly to access the latest features and ensure extension compatibility.
- Use SAMSON’s automatic update feature to simplify extension management.
- Check the compatibility of new extensions before installation, especially when using older SAMSON versions.
By staying updated and understanding how SAMSON’s versioning and compatibility system works, you can focus on your molecular modeling work without interruptions.
Learn more about SAMSON’s versioning and compatibility policies in the official documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. You can download SAMSON from SAMSON Connect.