Releases: PALEOtoolkit/PALEOtutorials.jl
Releases · PALEOtoolkit/PALEOtutorials.jl
PALEOtutorials v0.2.16
What's Changed
- update [compat] for PALEOboxes v0.22, PALEOmodel v0.16, PR #35
Full Changelog: v0.2.15...v0.2.16
PALEOtutorials v0.2.15
What's Changed
Full Changelog: v0.2.14...v0.2.15
PALEOtutorials v0.2.14
What's Changed
Full Changelog: v0.2.13...v0.2.14
PALEOtutorials v0.2.13
What's Changed
- Add examples for PALEOaqchem configurable chemistry in #28
- Update and simplify README.md and install docs in #29
- Bump actions/checkout from 3 to 4 by @dependabot in #25
- Update for Documenter v1, DocumenterCitations v1 in #26
Full Changelog: v0.2.12...v0.2.13
PALEOtutorials v0.2.12
PALEOtutorials v0.2.11
What's Changed
Full Changelog: v0.2.10...v0.2.11
PALEOtutorials v0.2.10
What's Changed
- add minimal Alk-pH example by @ChanQaQ in #17
- Move Xiyuan's ocean chemistry example to a new folder in #19
- Bump actions/checkout from 2 to 3 by @dependabot in #16
Full Changelog: v0.2.9...v0.2.10
PALEOtutorials v0.2.9
Updates
- Add CPU_modular example PR #13
- Add examples of analyzing model structure and output, issue #14, PR #15
Full Changelog: v0.2.8...v0.2.9
PALEOtutorials v0.2.8
Updates
- Update [compat] for PALEOboxes v0.21
- Build docs using Julia 1.8
Full Changelog: v0.2.7...v0.2.8
PALEOtutorials v0.2.7
Updates
-
Update for Parameter-related updates in PALEOboxes v0.20.4 that make the syntax for Parameters similar to that of Variables, making code easier to read:
- Parameters values can now be read using
<par>[]
instead of<par>.v
- Optional
pars
argument to method functions
- Parameters values can now be read using
-
Earlier Parameter update from PALEOboxes v0.18.0:
- use 'external=true' to enable Reaction Parameters to be set from model-wide Parameters in the .yaml
(eg for isotope types that need to be changed across multiple reactions).
- use 'external=true' to enable Reaction Parameters to be set from model-wide Parameters in the .yaml
-
Robustness fixes: use
PALEOboxes.Model
in preference toPALEOmodel.Run
, in particular usePALEOmodel.initialize!(model)
instead ofPALEOmodel.initialize!(run)
.
This hopefully avoids potential issues where model and run could get out of sync.
Full Changelog: v0.2.6...v0.2.7