Closed ablaom closed 3 years ago
Registration pull request created: JuliaRegistries/General/37848
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:
git tag -a v0.6.7 -m "<description of version>" da9364b4d6c13c96e2b0c37f8207e87569681e34
git push origin v0.6.7
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/38618
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:
git tag -a v0.6.8 -m "<description of version>" 17aa6c53f9c1477401af3a1b7afe4bc3df6543df
git push origin v0.6.8
@JuliaRegistrator register branch=master
cc @lhnguyen-vn
Registration pull request created: JuliaRegistries/General/40775
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:
git tag -a v0.6.9 -m "<description of version>" b1f8d191704143ddf67e4c8cb6428fc74ea45378
git push origin v0.6.9
@JuliaRegistrator register branch=master
release notes:
Explicit
strategy and provide a convenient syntax TundedModel(models=..., )
(#142) Registration pull request created: JuliaRegistries/General/41664
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:
git tag -a v0.6.10 -m "<description of version>" d5d7beb96ae04ccfcda60be1dd5a0e36c88f7c75
git push origin v0.6.10
@JuliaRegistrator register branch=master
release notes:
acceleration isa CPUThreads
(#126, #145) @lhnguyen-vn Registration pull request created: JuliaRegistries/General/44622
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:
git tag -a v0.6.11 -m "<description of version>" a819b50878abd2185da93f12a4a4984df7b1ce41
git push origin v0.6.11
@JuliaRegistrator register branch=master
release notes:
Registration pull request created: JuliaRegistries/General/45267
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:
git tag -a v0.6.12 -m "<description of version>" a47019becb7c9e32e2f2e3ee94d83c078d79667b
git push origin v0.6.12
@JuliaRegistrator register branch=master
Error while trying to register: "Tag with name v0.6.12
already exists and points to a different commit"
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/45394
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:
git tag -a v0.6.13 -m "<description of version>" afcd71977c4fbdb4ddd8db65b9f89f346bdd4665
git push origin v0.6.13
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/47910
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:
git tag -a v0.6.14 -m "<description of version>" a9f573253c865d304f60228a6f31b883c0210d73
git push origin v0.6.14
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/51150
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:
git tag -a v0.6.15 -m "<description of version>" 0b50093563a18b889bfda8ec12d97c2028706aeb
git push origin v0.6.15
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/51361
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:
git tag -a v0.6.16 -m "<description of version>" 31f0255cf79b61c3608f5b71c418ba6464fffcd6
git push origin v0.6.16
@JuliaRegistrator register branch=master
Release notes:
Grid
to RandomSearch()
(#147)learning_curve!
method (#151)TunedModel(model=...)
when model
is not pure Julia (#165) @olivierlabayle Registration pull request created: JuliaRegistries/General/58001
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:
git tag -a v0.7.0 -m "<description of version>" ebf09836b6950721e2c041a39c2c16fe4ebaee1a
git push origin v0.7.0
@JuliaRegistrator register branch=master
Release notes:
TunedModel
, for passing to measures (#172)TunedModel(model, tuning=...)
(#175)Registration pull request created: JuliaRegistries/General/60915
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:
git tag -a v0.7.1 -m "<description of version>" d87788a902ebb70b4ce794b2bb14737d3c4c2007
git push origin v0.7.1
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/62485
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:
git tag -a v0.7.2 -m "<description of version>" f9ad59dd8cade573779b165990484a5cbadd3ace
git push origin v0.7.2
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/67532
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:
git tag -a v0.7.3 -m "<description of version>" bfa9723175d419a3b1d746cae11e4b34225e8901
git push origin v0.7.3
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/71790
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:
git tag -a v0.7.4 -m "<description of version>" 094dbe85b74c23bd69525282db4e21a6516131d9
git push origin v0.7.4
@JuliaRegistrator register branch=master
Release notes:
Registration pull request created: JuliaRegistries/General/92206
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:
git tag -a v0.8.0 -m "<description of version>" b436f9748aadd0e77cb505323877e9e233e62d73
git push origin v0.8.0
@JuliaRegistrator register branch=master
Release notes:
Registration pull request updated: JuliaRegistries/General/92206
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:
git tag -a v0.8.0 -m "<description of version>" 7e4ae96aa6eebbf761f92b5772089617ef56077f
git push origin v0.8.0
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/99405
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.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
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:
git tag -a v0.8.1 -m "<description of version>" 60ad34450e6419e5a8491de03c4a0008e8a7144d
git push origin v0.8.1
@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/102482
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.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
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:
git tag -a v0.8.2 -m "<description of version>" 39d6cb46787d998aee5b7de315f8941142d231aa
git push origin v0.8.2
@JuliaRegistrator register branch=master
Release notes:
:evaluation
) in history entries (#210)Registration pull request created: JuliaRegistries/General/103060
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:
git tag -a v0.8.3 -m "<description of version>" 4f1dd7176078572979bba3b4e5c1ddb7af693a24
git push origin v0.8.3
@JuliaRegistrator register branch=master
Release notes:
Registration pull request created: JuliaRegistries/General/103528
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:
git tag -a v0.8.4 -m "<description of version>" 9fe1f52477c09e00c046e77e1533c11def060e49
git push origin v0.8.4
@JuliaRegistrator register branch=master
Release notes:
PerformanceEvaluation
objects computed for each model (hyper-parameter set) to the history, or write compact versions of the same (CompactPeformanceEvaluation
objects) by providing TunedModel(...)
a new option compact_history=true
. The evaluation objects are accessed like this: evaluation = report(mach).history[index].evaluation
, where mach
is a machine associated with the TunedModel
instance. For more on the differences between PerformanceEvaluation
and CompactPerformanceEvaluation
objects, refer to their document strings. (In MLJTuning 0.5.3 and 0.5.4 an experimental feature already introduced PerformanceEvalution
objects to the history, but with no option to write the compact form. In the current release, compact objects are written by default.)Registration pull request created: JuliaRegistries/General/106297
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:
git tag -a v0.8.5 -m "<description of version>" bac0ac9bdd4036ba4069b328dab914386a7e9975
git push origin v0.8.5
@JuliaRegistrator register branch=master
Release notes:
logger
option to TunedModel
wrapper, for logging internal model evaluations to an ML tracking platform, such as MLflow via MLJFlow.jl. Default should be nothing
for no logging (#193). The logger must support asynchronous messaging if TunedModel(model, ...)
is specified with the option acceleration=CPUThreads()
or CPUProcesses()
. Currently, CPU1()
(the default) is supported by MLJFlow.jl's loggers, while ansynchronous support is a work in progress; see https://github.com/JuliaAI/MLJFlow.jl/pull/41 #193.Registration pull request created: JuliaRegistries/General/107292
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.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
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:
git tag -a v0.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6
Registration pull request updated: JuliaRegistries/General/107292
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.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
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:
git tag -a v0.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6
Registration pull request updated: JuliaRegistries/General/107292
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:
git tag -a v0.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6
@JuliaRegistrator register branch=master
@JuliaRegistrator register