How to access hyper parameters that are in configuration objects for hyperparameter optimization
See original GitHub issueI am currently using MMDetection and tracking the results on Clearml. The hyper parameters are not located under <Hyperparameter>/<args or general>
but in <configuration objects>/<config>
instead.
Following the guide, i am stuck at this portion where i am having difficulty accessing them
Any solution/workaround to proceed on this? Thanks
Issue Analytics
- State:
- Created a year ago
- Comments:11
Top Results From Across the Web
How to Manage, Track, and Visualize Hyperparameters of ...
For hyperparameter tuning, the best practice is to have those hyperparameters in a single place as the results to make a good decision....
Read more >Parameters, Hyperparameters, Machine Learning
Hyperparameters are parameters whose values control the learning process and determine the values of model parameters that a learning algorithm ends up learning ......
Read more >Hyperparameter Optimization With Random Search and Grid ...
Hyperparameters are points of choice or configuration that allow a machine learning model to be customized for a specific task or dataset.
Read more >Hyperparameter Optimization Techniques to Improve Your ...
When working on a machine learning project, you need to follow a series of steps until you reach your goal.
Read more >Hyperparameters - ClearML
To get all of a task's parameters and properties (hyperparameters, configuration objects, and user properties), use the Task.get_parameters method, which will ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi you could retrieve what is logged in the configuration section using task.get_configuration_object_as_dict(name). The output should be an OrderedDict.
What I understand is that the parameters in MMDetection are saved in a configuration object and not in a hyperparameter. What I’m saying is that configuration object doesn’t impose a strict structure, you can put whatever text you want there. That being said, if the structure is json or yaml inside, we can parse it and in the future add support for doing parameter search on it.
I think your approach is better, it would support the built-in functionality of clearml and you could use HPO with this method.