Closed plutonium-239 closed 6 months ago
Nice idea!
Tracking as internal issue EXT-1331.
Workaround: you can now do this from cometx
:
cometx log WORKSPACE/PROJECT --query 'Other("optimizer_id") == "OLD-OPTIMIZER-ID"' --type other --set "optimizer_id:NEW-OPTIMIZER-ID"
You can set the name of the optimizer in the Optimizer config:
config = {
"algorithm": "random",
"name": "random-sweep-mar-24-2024",
...
}
optimizer = comet_ml.Optimizer(config)
...
Does that solve your issue?
Yes, I think a fully customisable name solves this and is even better! Thank you, I'll close this issue now.
Since optimizers are the way to go and we run a lot of them, manually finding the id of the last run optimizer in the experiments table seems.... unnecessary. (I use the grouping feature a lot but I need to open the terminal and scroll to see what was the optimizer id)
A very simple way to improve this and QOL is to use the optimizer.name field, just append the datetime string to it.
An alternative would be to add a optimizer.datetime field, but that requires a change in the api probably?