Skip to content
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

AugmentCmd should be clamped to [0.0..1.0] for 'augmentation method two' #1090

Conversation

cbirkhold
Copy link
Contributor

this avoid conflicts with potential future augmentation modes while
keeping the thrust produced for 'method two' within the range configured
for the turbine.
@cbirkhold cbirkhold changed the title AugmentCmd should be clamped to [0.0..1.0] AugmentCmd should be clamped to [0.0..1.0] for 'augmentation method two' May 18, 2024
Copy link

codecov bot commented May 30, 2024

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 24.91%. Comparing base (56c6662) to head (ec69698).
Report is 2 commits behind head on master.

Files Patch % Lines
src/models/propulsion/FGTurbine.cpp 0.00% 2 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1090   +/-   ##
=======================================
  Coverage   24.91%   24.91%           
=======================================
  Files         168      168           
  Lines       18104    18105    +1     
=======================================
+ Hits         4510     4511    +1     
  Misses      13594    13594           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@bcoconni bcoconni merged commit 90755f7 into JSBSim-Team:master May 30, 2024
30 checks passed
@cbirkhold cbirkhold deleted the feature/issue/1089-augmentcmd-should-be-clamped branch June 7, 2024 05:37
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.

2 participants