-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
editoast, front, core: remove gamma type #9887
Conversation
Signed-off-by: Pierre-Etienne Bougué <[email protected]>
952a63b
to
1dbe992
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #9887 +/- ##
==========================================
- Coverage 38.22% 38.18% -0.05%
==========================================
Files 995 997 +2
Lines 91893 92177 +284
Branches 1189 1192 +3
==========================================
+ Hits 35128 35195 +67
- Misses 56311 56526 +215
- Partials 454 456 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
1dbe992
to
5f606d7
Compare
rename gamma to const_gamma to reflect its use: constant gamma braking coefficient used when NOT circulating under ETCS/ERTMS signaling system in m/s^2. Signed-off-by: Pierre-Etienne Bougué <[email protected]>
5f606d7
to
b75d773
Compare
after OpenRailAssociation/osrd#9887 - [ ] To be merged once osrd's PR is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Core changes work for me :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR seems good. However, I'm missing some understanding about why it's fine to remove some (possibly not really well-supported) functionality: why removing MAX
? It'd be nice to at least explain in the PR description why it was there? Why we decided to remove it? Just put some tracing about this decision so "future us" understand why, at this point in time, we decided to remove MAX
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for front/
changes (not tested)
All use of braking is currently constant in code, and in database. So it is now explicit. Signed-off-by: Pierre-Etienne Bougué <[email protected]>
core/envelope-sim/src/main/java/fr/sncf/osrd/envelope_sim/PhysicsRollingStock.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Part of #9708
Rename
gamma
toconst_gamma
to reflect its use: constant gamma braking coefficient used when NOT circulating under ETCS/ERTMS signaling system in m/s^2.All rolling stock used are
CONST
, front always providedCONST
, thisMAX
variant was never used, and actually always constant in code use (and not sure if a max-check was missing in computeAcceleration)🔍 please review by commit.
To merge right after this: