Installation questions
On Unix systems, you can also add the string with a regular text editor in /usr/local/svi/huygensLicense. On Mac OS X it might be in a different place, depending on where you installed the software. Typically that would be /Applications/SVI/huygensLicense. You probably need to have root access to edit this file. On a Windows PC it is by default 'Program Files\SVI\huygensLicense'. Best put the new license above the old ones.
On Unix systems you can also store the license in a text file named huygensLicense in your home directory. This is especially useful on Mac OS X.Huygens can be installed in a path of your choice. After installing the Huygens .deb or .rpm package in a customized path via dpkg, yum, etc., you can edit the Huygens bin wrapper files. For example, for Huygens Core, edit /customized/path/bin/hucore file and add the following two lines:
export SVIHOME="/customized/path/svi exec $SVIHOME/bin/hucore.bin "$@"
Then add a symbolic link: /usr/local/bin/hucore -> /customized/path/svi/hucore
e.g. HuEss-16.10-wcnp-d6-ftvp9-mp-eom2017Oct01-f2372e2f612c8cf3-{username@email.com}-ab80d315d5bf4aa89d2c
or
HuPro-16.10-wcnp-d6-ftvp9-mp-eom2017Oct01-f2372e2f612c8cf3-{username@email.com}-ab80d315d5bf4aa89d2c
or
HuScript-16.10-wcnp-d6-ftvp9-mp-eom2017Oct01-f2372e2f612c8cf3-{username@email.com}-ab80d315d5bf4aa89d2c
The above licenses are valid for the Huygens 16.10.XpX versions. Huygens version 17.04.XpX or higher will not work with 16.10 licenses or lower. When there's a new release customers with valid maintenance receive new licenses updated for the new Huygens version.
inst -f dist65 -r TestInstall
~/TestInstall/usr/sbin/huygens2
~/TestInstall/usr/local/svi
~/TestInstall/usr/sbin/huygens2
huOpt cpu ?-min integer? ?-max integer? ?-mode <compliant|ignore (compliant)>?
huOpt cpu -max 4
Environment variables:
- The number of threads to be used is controlled through OMP_NUM_THREADS, for example: 'setenv OMP_NUM_THREADS 2'
- Allow the operating system to dynamically adjust the number of threads depending on system load: OMP_DYNAMIC (TRUE, FALSE), for example 'setenv OMP_DYNAMIC TRUE'. If OMP_NUM_THREADS is set then the number of threads varies between 1 and OMP_NUM_THREADS.
Huygens-Tcl layer:
huOpt cpu ?-min <integer>? ?-max <integer>? ?-mode <compliant|ignore>? ?-query <system|min|max|mode>
This allows setting of the minimum and maximum to the number of threads. Mode compliant is equal to OMP_DYNAMIC TRUE. With -mode ignore
the CE tries to always use the max thread number. With the -query
mode the curent state can be queried.
huOpt cpu -max 4 -mode ignore
to run on four threads regardless of system load.- The string was not pasted in in its entirety.
- The string got corrupted, for instance because it got split into two lines, see below.
- There is a mismatch between the software release and your license.
- You do not have sufficient rights to install the license, usually you need administrator rights, see below.
- The system ID was for a different computer, see below.
- The system's clock is not set to the correct date.
Typical problems when copy/pasting license strings are:
- The email client has split the string in different lines. The license string must be a single line, without any space or line break.
- The email client has converted a double dash (-+--+-) into a single long dash (—). A valid license string contains only 7 bit ASCII characters: basic English letters (a-Z or A-Z), numbers (0-9), dashes (-+-+-), at signs (@), curly braces (-+{ }+-), dots (-+.+-) and maybe other very basic symbols like underscores (-+_+-).
Normally you must have 'administrator or root rights' to install the license and will get an error message if you try to install the license without the proper rights. However, some Windows versions do not give a warning while afterwards the message cannot find a valid license keeps popping up. Right-click on the Huygens icon, and then choose 'run as administrator' and log in. Installing the license now will be successful.
Maybe the license string you are using is syntactically valid, but not intended for your computer. License strings are restricted to work only on a single computer, identified by its System Id. This ID is generated based on serial numbers of some of your hardware components. If you change any of these the System ID may change and the License Strings generated for it no longer work. A typical problem is caused by the change of a Network card. Consult your maintenance contract and Contact Svi to see how to update your license strings in such a case.
Does your license string not enable all the expected functionalities? The license string as used by SVI has the same appearance on all supported platforms. For each product you need to have a license string installed. Select an installed license string in the License manager and press the Explain license button. All details for the current license will be listed. If you run into licensing problems you may use this information to analyze the problem.
See wiki article License String and License String Details.dpkg -i
, for rpm, this is rpm -i install
.