feat(simulation): define CongestionInput, implement congestion_score with trend, verify congestion_label and run_scenarios#327
Merged
Tinna23 merged 1 commit intoJun 26, 2026
Conversation
…, and verify congestion_label/run_scenarios - Update CongestionInput fields to match spec: recent_avg_fee, capacity_usage, spike_count_1h, trend (StellarCommons#246) - Update congestion_score to handle trend field with adjusted weights (StellarCommons#247) - Verify congestion_label already matches spec (StellarCommons#248) - Verify run_scenarios already accepts Vec<FeeModelConfig> (StellarCommons#249) Closes StellarCommons#246 Closes StellarCommons#247 Closes StellarCommons#248 Closes StellarCommons#249
|
@prismn Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Define and verify the congestion scoring API: struct fields, weighted score function with trend support, label mapping, and multi-config runner.
Changes
CongestionInputstruct fields to match specification (recent_avg_fee,capacity_usage,spike_count_1h,trend)congestion_scoreto accept the new fields and incorporate trend direction into the weighted calculationcongestion_labelcorrectly maps scores to Normal/Rising/Congested/Critical tiersrun_scenariosaccepts&[FeeModelConfig]and returns concatenatedFeePointstreamIssues Closed
Closes #246
Closes #247
Closes #248
Closes #249