Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
dumux
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dumux-repositories
dumux
Commits
013363f3
Commit
013363f3
authored
8 years ago
by
Timo Koch
Browse files
Options
Downloads
Patches
Plain Diff
[changelog] Mention added method maxTimeStepSize
parent
8630cf6a
Loading
Loading
1 merge request
!163
[changelog] Mention added method maxTimeStepSize
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+4
-0
4 additions, 0 deletions
CHANGELOG.md
with
4 additions
and
0 deletions
CHANGELOG.md
+
4
−
0
View file @
013363f3
...
@@ -14,6 +14,10 @@ Differences Between DuMuX 2.9 and DuMuX 2.10
...
@@ -14,6 +14,10 @@ Differences Between DuMuX 2.9 and DuMuX 2.10
-
multidomain should now work with all compilers (optimzed) without segfaults
-
multidomain should now work with all compilers (optimzed) without segfaults
*
IMMEDIATE INTERFACE CHANGES not allowing/requiring a deprecation period:
*
IMMEDIATE INTERFACE CHANGES not allowing/requiring a deprecation period:
-
The problem class interface needs to provide the method maxTimeStepSize().
This is important if you implement problem classes not deriving from the base
problem classes in Dumux (ImplicitProblem, OneModelProblem,
ImpetProblem, and MultidomainProblem).
*
Deprecated PROPERTY and PARAMETER NAMES, to be removed after 2.10: BEWARE: The
*
Deprecated PROPERTY and PARAMETER NAMES, to be removed after 2.10: BEWARE: The
compiler will not print any warning if a deprecated property or parameter name
compiler will not print any warning if a deprecated property or parameter name
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment