Initializing help system before first use

Obtaining the Job Results

The run log for a running or completed job, or the job results for a completed job, can be obtained.

Obtaining the Run Log for a Mosel or a Solver job

The job details returned for a job with any status other than QUEUED will include a value for the runLogUrl property. This URL can be requested to retrieve the current run log content.

Obtaining the Results Zip for a Mosel job

The job details returned for a job with status of COMPLETED will include a value for the resultUrl property. Any files written to the results directory by your Mosel job will be picked up automatically and added to a zip file that incorporates the compute job id in the file name using the format [compute job id]-results.zip. The resultsUrl on the compute job response will then point to this zip.

Note: Your submitted Mosel job should create a directory named results and publish any result files you wish to retrieve to this directory.

Obtaining the Results Zip for a Solver job

The job details returned for a job with status of COMPLETED will include a value for the resultUrl property. This URL can be requested to retrieve a zip of the result files. The name of the results zip file includes the job id in the format [compute job id]-results.zip to help identify it after download.

The results zip for a job of type SOLVER will always include a file solution-status.json which contains a map of the name of the problem LP/MPS/SVF file to the solver status.

Example solution-status.json file 
{
  "problemName": "Optimal"
}
The possible solver status values are:
  • Optimal
  • No solution found
  • Solution available
  • Infeasible
  • Unbounded
  • Unfinished
  • Unsolved
The other files contained with the results zip will be dependent on what was requested in the original job submission with the resultsToInclude property. For a problem filename MyProblem.mps:
  • SOLUTION: Results zip will include a solution file MyProblem.slx containing the last solution.
  • BASIS: Results zip will include a basis file MyProblem.bas containing the basis for the last LP solve.
  • ATTRIBUTES: Results zip will include a file [problem name]-attributes.json which contains a JSON object referencing an array of solver attributes and their values at the end of the solving process.
    Example [problem name]-attributes.json file 
    { 
  "att1Name" : {
    "key": 1234,
    "name": "att1Name",
    "value": "value"	
    }...
}
  • SAVE: Results zip will include a save file MyProblem.svf created by called XPRSsave at the end of the solving.
  • IIS: Results zip will include the output of the IIS action as a file MyProblem.lp.
Parent Topic Compute Interface REST API

© 2001-2024 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.