You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: HISTORY.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,23 @@
1
+
# Release 0.37.2
2
+
3
+
DynamicPPL compatibility has been bumped to 0.36.
4
+
This brings with it a number of changes: the ones most likely to affect you are submodel prefixing and conditioning.
5
+
Variables in submodels are now represented correctly with field accessors.
6
+
For example:
7
+
8
+
```julia
9
+
using Turing
10
+
@modelinner() = x ~Normal()
11
+
@modelouter() = a ~to_submodel(inner())
12
+
```
13
+
14
+
`keys(VarInfo(outer()))` now returns `[@varname(a.x)]` instead of `[@varname(var"a.x")]`
15
+
16
+
Furthermore, you can now either condition on the outer model like `outer() | (@varname(a.x) => 1.0)`, or the inner model like `inner() | (@varname(x) => 1.0)`.
17
+
If you use the conditioned inner model as a submodel, the conditioning will still apply correctly.
18
+
19
+
Please see [the DynamicPPL release notes](https://github.com/TuringLang/DynamicPPL.jl/releases/tag/v0.36.0) for fuller details.
20
+
1
21
# Release 0.37.1
2
22
3
23
`maximum_a_posteriori` and `maximum_likelihood` now perform sanity checks on the model before running the optimisation.
0 commit comments