The 'smoketest' included in the Iris software package is available to help you verify that Iris has been installed correctly and is working properly on your computer platform.
To launch the Iris smoke test, type 'smoketest' on the Unix command line along with the full path to your Iris installation, like shown below:
The test will simulate user interaction with various components of Iris; e.g., it opens a SED in the SED Builder and then performs a fit to this SED using the Iris Fitting Tool.
If any of the actions executed by the test fail, an error message is displayed. In some cases, the message returned is very technical; this information should be included in a request for help from user support. In other cases, e.g., if the installed version of Iris is incompatible with your operating system, a more user-friendly message will be displayed.
In some rare instances, the smoke test will fail but will hang indefinitely without printing an error message and quitting; this could happen if one of the various components of Iris failed to load in time for the other components to communicate with it. In this case, you can specify a timeout in seconds when you launch the test, which will give the components of Iris this amount of time to communicate before exiting. Increasing the timeout value can help when installing Iris on a system with low memory or an older CPU.
unix% <basedir>/iris-2.0-<plat>-<arch>/Iris smoketest 20
It is also possible, but very unlikely, that the smoke test will fail if the user already has a SAMP hub open (when Iris is launched, it starts a SAMP hub of its own to allow the various components of the application to communicate). In this case, in lieu of the smoke test packaged with Iris, the user should verify that a SAMP client called "Sherpa" is attached to the existing hub when they launch Iris (this can take several seconds after starting the application).
The following is an example of a successful smoke test execution:
unix% <basedir>/iris-2.0-<plat>-<arch>/Iris smoketest This test will assess whether your installation is capable of performing some basic operations The test should take less than a minute. However, the actual time will depend on your system properties. ======================================== Starting Smoke Test with timeout: 10 ======================================== Waiting for the SAMP controller... Starting Sherpa... Pinging Sherpa... Sherpa response status: samp.ok Hub response status: samp.ok Creating a Setup for the SED Builder... Importing the file... Setting up a SAMP SED receiver... Waiting for the SAMP SED receiver... Broadcasting the SED... Sed received, and it looks good! Preparing the Sherpa call... Calling Sherpa and waiting for results... Verifying Sherpa response... =============================== Everything seems to be working! ===============================