Skip to content

Bug: fix MKRF bad curve cases before runtime generation #177

@gparadis

Description

@gparadis

Summary

Investigate and fix bad curve cases in the MKRF rebuild lane before continuing canonical runtime-package generation.

Parent issue: #173

Why this exists

The current rebuilt curve bundle has at least two clearly bad comparison cases:

  • tipsy_vdyp_tsamkrf-11-CWHvm1_CW+FDC.png
  • tipsy_vdyp_tsamkrf-12-CWHdmx_CW+FDC.png

In both cases the first-growth VDYP curve is effectively near-null while the managed curve is large, which indicates an upstream problem in source field choice, stand-to-unit assignment, unit definition, or curve fitting/aggregation. This needs to be resolved before we keep building the canonical runtime package.

Scope

  • audit the bad first-growth curve cases against raw VDYP source rows and assignment lineage;
  • determine whether the problem is source column choice, units, grouping, or fit/aggregation logic;
  • fix the curve-build lane and regenerate affected artifacts and plots;
  • record the acceptance rule for curve-quality gating before runtime generation continues.

Out of scope

  • full canonical runtime-package generation
  • broad model benchmarking after runtime generation

Immediate evidence

  • external/femic-mkrf-instance/data/model_input_bundle/first_growth_au_curves.csv
  • external/femic-mkrf-instance/data/model_input_bundle/first_growth_au_fit_diagnostics.csv
  • external/femic-mkrf-instance/data/model_input_bundle/managed_au_curves.csv
  • external/femic-mkrf-instance/plots/tipsy_vdyp_tsamkrf-11-CWHvm1_CW+FDC.png
  • external/femic-mkrf-instance/plots/tipsy_vdyp_tsamkrf-12-CWHdmx_CW+FDC.png

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions