Calculations

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

Studio saves that strategy’s dirty files before submission. The job uses saved source and the engine’s current simulation configuration, including settings newer than the manifest. Check instrument, period, initial funds and execution first.

Each job retains its identifier and originating project. Its row shows work type, state, stage and available progress; simulation time, trade count and equity may also appear. Progress is not a strategy-quality score.

Queued means the job is waiting for capacity; its position distinguishes waiting from execution. Running means work is executing. Stopping… means cancellation was requested but the job has not yet finished.

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

Completed describes execution finishing. Failed, Cancelled and Interrupted retain their own causes and are not successful results. For a paused job or one waiting for an answer, inspect its question and stage first.

Running, Queued and Recent Results separate active work from history. Refresh if an action no longer matches a row’s current state. Do not submit duplicate work merely because its percentage has not changed recently.

Parallel Calculations… accepts a whole-number limit from 1 to 16. This is a ceiling: available CPU and memory can reduce the effective number running at once.

If the application becomes sluggish, lower the limit for subsequent scheduling and let resources become free. Lowering it does not interrupt jobs already running. Raising it does not by itself accelerate a particular individual calculation.

Choose Open Calculation Report for a completed ordinary backtest. It opens that job’s saved report; a missing or unreadable file must not be replaced by an unrelated interactive result.

An eligible completed result can be saved to Strategy Laboratory. If it was funded by starting balances, the application explains that it is not saved there: use the report and review funding conditions.

Opening research, saving and checking robustness require the original strategy folder. Return to that project if prompted. Editing another strategy does not change the origin of an existing result.

Cancel Calculation applies to a current active job. Wait for its terminal state after requesting it: Stopping… does not yet mean Cancelled. A finished job cannot be cancelled retroactively.

Remove from History applies to terminal jobs and requires confirmation. It dismisses the queue entry while retaining reports and Strategy Laboratory research. This differs from deleting a project or its files.

Engine offline: check EngineHost startup and output. Queued while other jobs run: inspect capacity and resources. Waiting for an answer: read the specific question instead of automatically approving unknown data or a model.

Completed without an expected action: check job type, originating project and saved report/inputs. An old result without captured inputs cannot supply a new passport; after resolving capture issues, run a new baseline.

For diagnosis keep jobId, originating project, state, stage and the exact XTester Engine message. Do not substitute another run’s runId or jobId.