Tried it with both parameter naming schemes ( "Hydra/*" and "General/*" ) but it didn’t work 😕

Yes, the screenshot is from one of the HPO child tasks

In the task hyper parameters section you have a section called Hydra. In that section there should be a configuration called _allow_omegaconf_edit_ , what is it set to?

WebApp: 1.6.0-213 • Server: 1.6.0-213 • API: 2.20
hydra-core 1.1.2

Please try setting it to True, that should fix it

Yep, looks like that for me as well

but sadly when you compare different experiments with different parameters, all the scalar graphs are identical which shouldn’t be the case

I mean the version of the SDK

That’s set to false (the default)

clearml 1.6.2 clearml-agent 1.3.0 hydra-core 1.1.2

Hi FranticLobster32 , what version of ClearML, of Agent & Hydra are you using?

Yes, the base task is the same, minus the parameters I’m trying to overwrite with the HPO. Here’s the screenshot from the base task

It should look something like this

It needs to be in the base task

What about the base task?

Aight. Thanks for the information. I'll take a look and see if it reproduces for me as well 🙂

CostlyOstrich36
I’m fully confident at this point that changing parameters on Hydra experiments doesn’t work with clearML. Thus I have reverted to converting Hydra hparams to normal hparams
` @hydra.main(config_path="conf", config_name="config")
def main(config: DictConfig):

task = Task.init(
    config.logging.trackerParams.project,
    config.logging.trackerParams.experimentName,
)

config = task.connect(OmegaConf.to_container(config)) `which seems to work.

All of this being said, I’d very much like Hydra + HPO to work as intended. So I am thinking should I escalate this to an issue on Github and provide a minimal example?

Just making sure we cover all bases - you changed updated the optimized to use a base task with _allow_omegaconf_edit_ : True

Cool, let me know if I can help in anyway. I can also try mocking up a small example on my side