Initializing help system before first use

Starting a Tuning Session

Complete the following steps to start tuning a Mosel model:

  1. In the Run Configurations drop-down list, select the Mosel source file that you want to tune.
  2. Click the Run Tools button (the fourth button to the right of the Run Configurations drop-down list).
  3. In the menu that appears, click Show Run Dialog.
  4. In the Run Model dialog, ensure that the Run Mode field is set to Tune the Model and configure the settings for the tuning session.

    See Tuner Settings for more information.

  5. Click Run.

    The tuner logs from will appear in an Output window at the bottom of the screen.

  6. When you see the message New tuner results at the top of the screen, click the link.
    A new tab will open, displaying the tuner results in a table.
    Note Tuner result files and log files are written to a directory named tuneroutput within the project. You can view the tuner results table for a previous tuner session by locating the XTR file in the Xpress Workbench file tree and double-clicking it.
    The columns of the tuner results table are as follows:
    Column Description
    Problem The name of the tuning session, as specified in the Tune Model dialog.
    Type The type of problem that was solved, e.g. MIP.
    Xpress Version The version of the Xpress that was used for the tuning session.
    Timestamp The date and time of each tuner run, in the form yyyymmdd.hhmmsss.micros.
    Logs Click in this cell to open the Xpress log file for the tuner run.
    Tuner Threads The number of times the tuner solved the problem as part of each run, including permutations.
    one or more columns... A column for each Xpress control which the tuner tried during the session.
    Code Click this cell to see the Mosel code which sets the Xpress controls as they were for this tuner run.
    Status The status of the tune run, e.g. whether or not the problem was solved within the time limit.
    Run Time The total time taken to solve the problem.
    Objective The value of the objective function at the end of the tuner run.
    For MIP problems, the following columns are also present:
    Column Description
    Bound The best bound at the end of the tuner run.
    Gap The gap at the end of the tuner run, as a percentage.
    Integral The integral at the end of the tuner run.
    Solutions The number of solutions found during the tuner run.
    Nodes The number of tree nodes searched during the tuner run.

© 2001-2020 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.