System settings can only be managed by system administrators. |
System settings are managed on the Administration > System settings page.
By default, the Store multiple engine versions setting is off. This means that whenever an existing engine is re-trained, its previous version gets replaced with the new version.
When this setting is turned on:
From this point onwards, every existing engine that gets re-trained will have exactly one active version and one inactive version. (Note that this means you will need to re-train your engines before you can see the benefits of this setting.)
You can choose the policy for activating new versions of the same engine (see below).
When this setting is turned off:
There is only one version for each engine, which means Globalese will work as before version 4.4, i.e. when an existing engine is re-trained, the previous version is lost, and the new one takes its place.
Turn this setting on if you:
want to experiment with a new version of an engine without deploying it to production;
want to be able to revert an engine to its previously trained state.
By default, the Activate latest engine versions automatically setting is on. You can only change this setting if the the Store multiple engine versions setting has been turned on.
When this setting is turned on:
This is the default behaviour. Whenever an existing engine gets re-trained, the new one becomes the active version of the engine. However (because the Store multiple engine versions setting is on), the previously active engine version becomes the inactive one, which can be re-activated if needed.
When this setting is turned off:
When an existing engine get re-trained, the new version will become the inactive version, and the previously active version remains the active version.
You will need to manually activate the newly trained version of an engine before you can use it.
Turn this setting off if you want to have control over when a new engine version replaces the previous one.