Skip to content

Tags: JuliaAI/IterationControl.jl

Tags

v0.5.4

Toggle v0.5.4's commit message
## IterationControl v0.5.4

[Diff since v0.5.3](v0.5.3...v0.5.4)


**Merged pull requests:**
- Fix a `Warmup` trait (#60) (@ablaom)
- For a 0.5.4 release (#61) (@ablaom)

v0.5.3

Toggle v0.5.3's commit message
## IterationControl v0.5.3

[Diff since v0.5.2](v0.5.2...v0.5.3)


**Closed issues:**
- Something wrong with some control constructors? (#55)

**Merged pull requests:**
- Fix constructors (#56) (@ablaom)
- For a 0.5.3 release (#57) (@ablaom)

v0.5.2

Toggle v0.5.2's commit message
## IterationControl v0.5.2

[Diff since v0.5.1](v0.5.1...v0.5.2)



**Merged pull requests:**
- Better errors for no training loss (#53) (@ablaom)
- For a 0.5.2 release (#54) (@ablaom)

v0.5.1

Toggle v0.5.1's commit message
## IterationControl v0.5.1

[Diff since v0.5.0](v0.5.0...v0.5.1)



**Merged pull requests:**
- Add `needs_loss` and `needs_training_losses` control traits (#51) (@ablaom)
- For a 0.5.1 release (#52) (@ablaom)

v0.5.0

Toggle v0.5.0's commit message
## IterationControl v0.5.0

[Diff since v0.4.0](v0.4.0...v0.5.0)

- (**breaking**) Update compatibility requirement for EarlyStopping.jl to 0.2. Breaking as introduces slight behaviour in behaviour of `PQ` stopping criterion (see [these release notes](https://github.com/JuliaAI/EarlyStopping.jl/releases/tag/v0.2.0))

**Closed issues:**
- Issue to trigger new releases (#20)

**Merged pull requests:**
- Add new example. No new release. (#46) (@ablaom)
- Replace `debug` wrapper with more general `with_state_do` wrapper (#48) (@ablaom)
- Bump EarlyStopping version and fix tests (#49) (@ablaom)
- For a 0.5.0 release (#50) (@ablaom)

v0.4.0

Toggle v0.4.0's commit message
## IterationControl v0.4.0

[Diff since v0.3.3](v0.3.3...v0.4.0)

- [x] (**breaking**) Change the meaning of "number" in `WithNumberDo` to be the control cycle count, rather than the number of applications of that particular control (#38, PR #44).

**Closed issues:**
- What is the correct way to obtain the last step infomation when skip is applied to controls? (#38)
- Issues on using IterationControl.jl for iterative solvers (#41)

**Merged pull requests:**
- Make "number" in `WithNumberDo` the global control cycle count (#44) (@ablaom)
- For a 0.4.0 release (#45) (@ablaom)

v0.3.3

Toggle v0.3.3's commit message
## IterationControl v0.3.3

[Diff since v0.3.2](v0.3.2...v0.3.3)

- Add some extra data to the `state` of some controls, and make this information user-inspectable (via the return value of `train!`, as generated by the control's `takedown` method. In particular, make add the loss to the `WithLossDo` control `state` and the latest training loss available to the `WithTrainingLossesDo` control state (#39)
- Tweak some logging
- At the default logging level of `verbosity=1`, log to `Info` the final loss, and the final training loss, when available (resolves part of #38)
- Add a new control wrapper `IterationControl.louder(control, by=1)` to increase the verbosity of `control` (the value of `by` is added to the `verbosity` level, as passed to `IterationControl.train!(..., verbosity=....)`).


**Merged pull requests:**
- Added some stuff to `state` of select controls for user inspection (#39) (@ablaom)
- Move `SquareRooter` code from test/ to src/ (#40) (@ablaom)
- For a 0.3.3 release (#42) (@ablaom)
- Add a control wrapper to make logging more verbose (#43) (@ablaom)

v0.3.2

Toggle v0.3.2's commit message
## IterationControl v0.3.2

[Diff since v0.3.1](v0.3.1...v0.3.2)

- bump [compat] for EarlyStopping to 0.1.8


**Merged pull requests:**
- For a 0.3.2 release (#37) (@ablaom)

v0.3.1

Toggle v0.3.1's commit message
## IterationControl v0.3.1

[Diff since v0.3.0](v0.3.0...v0.3.1)

- [x] Fix a typo in logging: `Stepping ...` instead of `Steping...` (#36)


**Merged pull requests:**
- For a 0.3.1 release (#36) (@ablaom)

v0.3.0

Toggle v0.3.0's commit message
## IterationControl v0.3.0

[Diff since v0.2.2](v0.2.2...v0.3.0)

- [x] Don't lower  `verbosity` in `train!(...)` when passing to `update` calls. Breaks logging behaviour for controls but built-in controls have been fixed so that their use in `train!(...)` is unaffected. (#34)


**Merged pull requests:**
- Don't lower the verbosity level passed to update methods (#34) (@ablaom)
- For a 0.3.0 release (#35) (@ablaom)