Skip to content

trim confusing load.op weight keys from config.yaml dumps#118

Merged
mikehorgan-dell merged 1 commit into
mainfrom
fix/config-yaml-trim-load-op-weights
May 19, 2026
Merged

trim confusing load.op weight keys from config.yaml dumps#118
mikehorgan-dell merged 1 commit into
mainfrom
fix/config-yaml-trim-load-op-weights

Conversation

@mikehorgan-dell
Copy link
Copy Markdown
Member

@mikehorgan-dell mikehorgan-dell commented May 19, 2026

Summary

  • apply step-type-aware config dump trimming in ConfigUtil to reduce confusing load.op keys in config.yaml
    • MixedLoad keeps load.op.weights and drops scalar load.op.weight
    • non-MixedLoad keeps scalar load.op.weight, drops load.op.weights, and removes legacy mixed-style map values under load.op.weight
  • pass step type through LoadStepBase when serializing config dumps
  • update weighted sub-step config serialization to use the same step-type-aware serializer
  • add ConfigUtilTest coverage for mixed/non-mixed behavior plus guard-return paths

Config dumps include merged extension defaults, which made CreateLoad and MixedLoad hard to distinguish in config.yaml.

Apply step-type-aware trimming at serialization time so MixedLoad keeps load.op.weights while non-mixed steps keep scalar load.op.weight and drop mixed-only maps. Also cover guard paths with unit tests and keep weighted sub-step config logging consistent with the same serializer.
@mikehorgan-dell mikehorgan-dell merged commit 0eefd14 into main May 19, 2026
6 checks passed
@mikehorgan-dell mikehorgan-dell deleted the fix/config-yaml-trim-load-op-weights branch May 19, 2026 20:09
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.

1 participant