Analyze and AVW library
Which machines are licensed, how to set environment variables, and how to invoke the programmes?

At the Wolfson Molecular Imaging Centre of the University of Manchester, the Analyze Software System and the AVW Library are available for image processing.


Using Analyze and the AVW library on the networked Linux nodes at the WMIC

For the Analyze Software, currently five machines are licensed.

  1. mmic-node15 (An IBM Blade Server node with Xeon 3.06 GHz processors (4 cores) and 2.5 Gigabytes RAM running SuSe Linux Enterprise Server 11 SP1 - Kernel 2.6.32.12-0.7-pae), Analyze (2 floating licences) and AVW version 11.0.
  2. mmic-node16 (An IBM Blade Server node with Xeon 3.06 GHz processors (4 cores) and 2.5 Gigabytes RAM running SuSe Linux Enterprise Server 10 - Kernel 2.6.16.21-0.8-smp), Analyze (3 floating licences) and AVW version 10.0.
  3. wmic-node4 (An IBM Blade Server node with Xeon 3.06 GHz processors (4 cores) and 4 Gigabytes RAM running SuSe Linux Enterprise Server 10 SP1 - Kernel 2.6.16.46-0.12-bigsmp), licence currently linked to mmic-node16.
  4. mmic-node14 (An IBM Blade Server node with Xeon 3.06 GHz processors (4 cores) and 4 Gigabytes RAM running SuSe Linux Enterprise Server 11 SP1 - Kernel 2.6.32.13-0.5-pae), licence currently linked to mmic-node15.
  5. wmic-node2 (An IBM Blade Server node with Xeon 3.06 GHz processors (4 cores) and 4 Gigabytes RAM running SUSE Linux Enterprise Server 11 SP1 - Kernel 2.6.32.12-0.7-pae), licence currently linked to mmic-node16.

After logging into one of the machines, it is recommended to set the following environment variables

Then the Analyze programme can be called from the command line:
  $BIR/bin/Analyze &

The licence manager status can be requested by entering
  $BIR/BIRlic-11.0/PC_LINUX/bin/BIRlic status
The output lists the current user of the licence on the local system.


Using the AVW library on the networked Windows PCs at the WMIC

As the AVW licences on mmic-node15 and mmic-node16 are floating licences, any networked computer, including PCs running the Microsoft Windows operating system, can check out and check back in one of these licences.

Follow these step by step instructions using mmic-node15 as example:

  1. Open a Command Prompt window by pressing Start -> All Programs -> Accessories -> Command Prompt.

  2. Confirm that your computer can reach the licence server from its subnet by entering the command ping 130.88.14.118
    C:\> ping 130.88.14.118
    
    Pinging 130.88.14.118 with 32 bytes of data:
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    
    Ping statistics for 130.88.14.118:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    
    If the output says that the host is not reachable, then stop here and contact your network administrator.

  3. Confirm that your computer can resolve the name of the licence server by entering the command ping mmic-node15
    C:\> ping mmic-node15
    
    Pinging mmic-node15.mmic.man.ac.uk [130.88.14.118] with 32 bytes of data:
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    Reply from 130.88.14.118: bytes=32 time<1ms TTL=64
    
    Ping statistics for 130.88.14.118:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    
    If the output says Ping request could not find host mmic-node15. Please check the name and try again. then add the following line to the Windows host name database file %SystemRoot%\System32\drivers\etc\hosts using Notepad or another text editor
    130.88.14.118   mmic-node15
    
    separating the IP-address and the hostname by a SPACE or TAB character. The %SystemRoot% environment variable expands to the Windows installation directory, for example C:\Winnt or C:\Windows. To save the modified hosts file, administrator permission is required. Contact your system administrator if the access is denied.
    Repeat the command ping mmic-node15 to confirm that the host name mmic-node15 is now resolved.

  4. Modify the PATH variable in the Command Prompt window by entering
    C:\> set PATH=\\mmic-fs1\WMIC_Apps\AVW-11.0\PC_NT\lib;\\mmic-fs1\WMIC_Apps\BIRlic-11.0\PC_NT\bin;\\mmic-fs1\WMIC_Apps;%PATH%
    
    on 32-bit systems or
    C:\> set PATH=\\mmic-fs1\WMIC_Apps\AVW-11.0\PC_NT64\lib;\\mmic-fs1\WMIC_Apps\BIRlic-11.0\PC_NT64\bin;\\mmic-fs1\WMIC_Apps\win64;%PATH%
    
    on 64-bit systems.

  5. Check the status of the AVW licence by entering the command BIRlic Status
    C:\> BIRlic Status
    Status @ 12:25:04 11/22/2016
    
    Summary: 3 Licenses, 0 Used, 0 Products, 0 Systems, 0 Targets, 0 Processes, 0 Users
    
    confirms that the licence server is up and responding.

    On the contrary, if the output is
    C:\> BIRlic Status
    SendToServer: connection error
    SendToServer: connection error
    SendToServer: connection error
    
    then go back to steps 2. and 3. to resolve connection errors.

    An output
    C:\> BIRlic Status
    Connect Error
    
    indicates that the BIR licence server daemon on mmic-node15 is not running. Contact IT Support and request that the BIR licence server daemon process on mmic-node15 is restarted.

  6. Confirm that the programme CheckInLic is found on the path and executable by entering the command
    C:\> CheckInLic
    
    It should terminate quietly without error message. This is crucial because if CheckInLic cannot be run, then the AVW floating licence is not checked back in after completion of the user command on the Windows platform!

  7. Everything should now be ready to go. All executables requiring the AVW library, for example tacstats, panames, addimg or sthg2ana, are on the path and can be called from the command line as described on the Tools Help page.

    Best of luck!


@(#)analyzeavw.html 2.10 23/11/28 11:00:18 © Rainer Hinz, The University of Manchester.