Fix wrong integer conversion when computing xpmax in norver function#281
Merged
corentin-prigent merged 1 commit intodevelopfrom Sep 14, 2024
Merged
Conversation
…during analysis step.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #281 +/- ##
========================================
Coverage 50.44% 50.44%
========================================
Files 177 177
Lines 47236 47236
Branches 10276 10276
========================================
Hits 23830 23830
Misses 15674 15674
Partials 7732 7732 ☔ View full report in Codecov by Sentry. |
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.
As
mesh->xpmax, mesh->xp and mesh->npmaxareMMG5_int(since the adding ofint64_tintegers support), we have to cast the double value computed into aMMG5_intvalue and not along longone.