Page Comparison

RU 🇷🇺

The Hub allows users to download, install, and run every version that’s been released to their company. Multiple versions can be installed at the same time, and users can choose which version they wish to run. This empowers users to select which version they want to run, and are not forced to immediately upgrade when new features are released.

It’s important for you to understand how Alastri releases new versions, what the different version types mean, and what restrictions there are when choosing a version so you can choose the right version for your situation.

Version Number - Major Versions / Build Numbers

A build of the software has a version number, which looks something like 22.3.253. In this example, 22.3 is the major version, and 253 is the build number.

The major version looks something like 22.2 or 22.3 or 23.1. The 22 or 23 represents the year in which the version was released, and number after the “.” increments with each new major version released over the year.

The build number increments each time Alastri creates a new build. The build number increments globally across all versions, so it’s possible build 450 is for version 23.1, while build 451 is for version 22.3. Essentially the build number is a unique id of the build.

Major Version Types

Each major version is associated with one of four release types. These are based upon the level of testing that has gone into them, their purpose, and whether they continue to be supported with new releases for bug fixes.

Release Schedule

Alastri releases a new build usually several times a week. A build is a specific version of the software which can be downloaded, installed, and run. There are two main reasons for a new build to be released:

• The new build has a fix for a bug that was found.

• The new build has new features or functions which are being sought by clients.

There is no set day or time when new releases become available. Due to the frequency of updates, there are also no notifications provided to users when a new build is provided. Instead, immediately upon release, the new build is available in the user’s Hub - ready to be downloaded and installed.

Upgrading

Within the same Major Version

Upgrading from the major version to a later build of the same major version will almost always not require any changes on your part. As an example, you can open version 22.3.242 and upgrade to 22.3.278, and this will likely not require any changes on your part. When changes are required, it is because there was a bug which requires minor alterations to the model setup. As an example, there might be a bug which allowed the user to set up the model in an invalid way, and once that bug is fixed, the user will be required to fix the setup.

Between Major Versions

Upgrading between major versions may require some model changes. For models which use scripting, it’s also possible that script changes are required. First try to complete the upgrade yourself by opening the model in the new version, and working through any messages that are reported in the setup. The Alastri support team is ready to assist with upgrading between versions - it’s included as part of your company’s software subscription.

If you run into a bug after upgrading to a new version, and the old version didn’t have that bug - most likely you are running into a bug that actually did exist in the old version too; you just never encountered it. If you let us know how we can duplicate the problem, we can resolve it and we can tell you whether it was in the old version or not too.

Cross Compatibility

Alastri’s products are built to work together, but this is only possible if they’re all of the same version. Therefore, when upgrading one product to a specific version, you must upgrade the others to also be on the same version, if you wish to use them together. For example, if you upgrade RR to 22.2.152 and you want to use the output with APS, you need to upgrade HI to 22.2.152 and APS to 22.2.152. Then, if you want to use the output from APS with SC, then that will need to be on 22.2.152 as well.

An outcome of the above is that you should also work on the same version as the others you are working with, so the team as a whole needs to choose a specific version to work with.

Will my results change between versions?

Whenever we make a change to the engines that run our software, there is a possibility the results will change. This can happen between builds even with the same major version, as even a miniscule change can cause a cascade of changes which can cause relatively large changes in the final result.

For example:

• A small change in how a solid is created may change its volume by 0.01 cubic meters.

• In period 14, originally two blocks were released by dependencies at exactly the same time and the engine chose the second block.

• With the change in volume, the first block is now released earlier.

• The scheduling engine now chooses the first block instead of the second as it’s available first.

• This leads to a cascade of differing scheduling choices made by the scheduling engine.

If you’re wondering whether anything will change if you open the model in a new version, open the model in the new version and check. There are hundreds of thousands of ways of configuring a model and a change may or may not affect you - the only way to know is to check.

So which version do I choose?

• If you’re halfway through a plan: stick to the same major version unless there is an issue preventing you from proceeding.

• If you work at a company which has a central point of contact with Alastri: refer to that contact who will tell you which version to use.

• If you’re on a Legacy release: Upgrade to a Current release when you’ve got a chance.

• If you’re looking to get access to the latest and greatest features, and are not up against a planning deadline: Use an Experimental release.

• Do not use an Explosive Release, unless specifically instructed by Alastri.