Initializing help system before first use

Developer Responsibilities

Best practice recommends that the main model of an app should honour the threads assigned to it by the scheduler. If an execution mode implementation requires a fixed number of threads then that number should be declared in the execution mode annotation so the requirement is visible to the scheduler.
If an execution mode can work with a variable number of threads then the main model should abide by both of the following rules:
  1. It should not declare a thread requirement with the execution annotation
  2. It should honour the number of threads assigned to the job by the scheduler

The number of threads assigned is passed to the model as the xprs_threads parameter and applied automatically to the Solver. For most use cases, there is no other action for the developer to perform. However, if the implementation of the exec mode creates threads in some way other than via the Solver (for example, sub models), then the developer should read the value of the xprs_threads parameter and use it to govern how many threads to allow their code to use.

Parent Topic The Model and Scenario Data Management

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