Skip to content

[codex] Standardize report KPI precision#9443

Draft
aiSynergy37 wants to merge 1 commit intoQuantConnect:masterfrom
aiSynergy37:codex/fix-report-kpi-decimals
Draft

[codex] Standardize report KPI precision#9443
aiSynergy37 wants to merge 1 commit intoQuantConnect:masterfrom
aiSynergy37:codex/fix-report-kpi-decimals

Conversation

@aiSynergy37
Copy link
Copy Markdown
Contributor

Resolves #8468.

Description

  • Adds shared report KPI formatting helpers for fixed three-decimal numeric and percentage display.
  • Applies the shared formatting to key report statistics that previously used mixed precisions (P0, P1, F1, F2).
  • Adds a regression check that rendered key statistics use three decimal places while serialized report statistics preserve raw numeric values.

Validation

  • dotnet build Report\QuantConnect.Report.csproj --no-restore --nologo -v:q -clp:ErrorsOnly -m:1 -p:UseSharedCompilation=false
  • dotnet build Tests\QuantConnect.Tests.csproj --no-restore --nologo -v:q -clp:ErrorsOnly -p:RunAnalyzers=false -m:1 -p:UseSharedCompilation=false

Focused test attempted:

  • dotnet test Tests\QuantConnect.Tests.csproj --no-build --nologo --filter "FullyQualifiedName~QuantConnect.Tests.Report.ReportChartTests.KeyStatisticsRenderWithThreeDecimalPlaces" -v:n

The focused test host aborted in the local environment with the existing pythonnet finalizer error: GIL must always be released, and it must be released from the same thread that acquired it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Increase Report Key Statistics Decimal Places

2 participants