Hi TimelyPenguin76 , I'm not getting the behavior mentioned above.. I am doing the following:
I clone some "baseline" config from a task I run I edit the OmegConf Configuration Object and adjust one of the values in the yaml enqueue the run, however I'm getting the same config as before... without the changes..what am I missing?

Yey!

AgitatedDove14 sounds great I'm going to give it ago

worked like a charm

hi DepressedChimpanzee34 . once you change the parameters in the cloned task from the UI, those will be the parameters your task will use when running with the ClearML agent.

The configuration you see in the UI will be the actual running configuration for task

hi TimelyPenguin76 thanks, for some reason it didn't show up in my search or maybe I missed it..
I was wondering specifically about the following case:
lets say I'm cloning the task you created above, now I am editing some of the hyper parameters in the UI and enqueueing it.
would the config be "automatically" synced? I assume not, if not what would be a recommended way to sync it?
I especially wondered if there is a "smart" sync (with parsing) that can take advantage of the type hinting in the OmegaConf\Hydra config object

TimelyPenguin76 thanks for the answer, so for example (to make sure I understand) with the example you gave above when I'll print the config I'll see the new edited parameters?
What about the second part of the question, would it be parsed according to the type hinting?

Hi DepressedChimpanzee34 ,

Hydra should be auto patched, did you try this example?
https://github.com/allegroai/clearml/blob/master/examples/frameworks/hydra/hydra_example.py

Hi 

, if you don't mind having a look too,

With pleasure :)

according to the above I was expecting the config to be auto-magically updated with the new yaml config I edited in the UI, however it seems like an additional step is required.. probably connect_dict? or am I missing something

Notice the OmegaConf section description :
Full OmegaConf YAML configuration. This is a read-only section, unless 'Hydra/_allow_omegaconf_edit_' is set to TrueBy default it will always be "read0-only" meaning it will store the configuration based on the conf files and the --overrides (See the args section, you can change them there)
If you want to full edit the OmegaConf and Use it, go to the Configuration "Hydra" Section, and change _allow_omegaconf_edit_ to True.
Now the OmegaConf from the UI will override the one created in runtime.
Sounds good ?

Hi AgitatedDove14 , if you don't mind having a look too, I think its probably just a small misunderstanding
according to the above I was expecting the config to be auto-magically updated with the new yaml config I edited in the UI, however it seems like an additional step is required.. probably connect_dict? or am I missing something

 thanks for the answer, so for example (to make sure I understand) with the example you gave above when I’ll print the config I’ll see the new edited parameters?

Correct

What about the second part of the question, would it be parsed according to the type hinting?

It should