Define FEA inline in Round 1 description#83
Merged
Conversation
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
1 participant
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
Round 1's description surfaces "FEA safety requirements" on the home category card, the round detail page, and the
GET /rounds/activeAPI response. First-time readers don't know what FEA is.Changes
data/rounds/round_001.json: "Minimize mass while meeting FEA safety requirements" → "Minimize mass while passing structural simulation (FEA = Finite Element Analysis) — your bracket must survive the rated load with the required safety margin."app/main.py: version 0.15.7 → 0.15.8CHANGELOG.md: 0.15.8 entryRound 2 and 3 don't mention FEA in their descriptions, so no change needed there. Tests: 139/139.