-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Careful handling of data types (Float32 & units) (#108)
* show u and sigma in MPRK43 during perform_step * more output * more output * more output * changed MPRK43II small_constant * removed addtional output * format * updated doc strings * added conversion to Float32 in SSPMPRK43 * Added small_constant_function_MPRK43II * revised docstrings * format * typo * Evaluation of PDSFunction and ConservativePDSFunction can handle units * structure runtest * bugfix runtest * additoinal tests * Use Unitful in tests * More functionality from StaticArrays * bugfixes * Reset evaluation of PDSFunctions with sparse prototyp * bugfix * Evaluation of PDSFunctions with sparse Prototype and units is working * format * Enable solution of PDS with unity by OrdinaryDiffEq solvers * test more OrdinaryDiffEq algorithms solving problems with units * Float32 test * removed tests for solving PDSProblems with units by implicit solvers * bugfix test Compatibility of OrdinarDiffEq solvers with (Conservative)PDSProblems and units * Don't use implicit OrdinaryDiffEq solvers with units in tests * Update src/mprk.jl Co-authored-by: Hendrik Ranocha <[email protected]> * Update src/mprk.jl Co-authored-by: Hendrik Ranocha <[email protected]> * Update src/proddest.jl Co-authored-by: Hendrik Ranocha <[email protected]> * Update src/sspmprk.jl Co-authored-by: Hendrik Ranocha <[email protected]> * Update test/runtests.jl Co-authored-by: Hendrik Ranocha <[email protected]> * use unitful.jl's ustirp in tests * Compare unitful data without ustrip * Use ustrip before comparing solutions with units in tests * Added missing test (SSPMPRK43 and Float32) * similar and oneunit * similar(P[:,1]) * set version to v0.2.6 --------- Co-authored-by: Hendrik Ranocha <[email protected]>
- Loading branch information
Showing
6 changed files
with
369 additions
and
49 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
ad47cfb
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.
@JuliaRegistrator register
ad47cfb
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.
Registration pull request created: JuliaRegistries/General/114150
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via: