You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a researcher I would like all my config.json hyper parameters logged as mlflow tags as soon as possible
So, I would be able to compare between my job runs even if pipeline didn't finish to run (failed / long time running).
note:
today only few properties are being tagged in mlflow and many parameters are missing.
The content you are editing has changed. Please copy your edits and refresh the page.
closes#480
### This PR includes
- Log all hyper parameters to mlflow
- Config refactoring - lowercase for all attributes as those are not constants (match coding conventions)
- Print azure ml monitoring URL right after its creation to allow easy access to monitoring (ctrl + left click)
- Fix issues with experiment and job names, allowing azure ml commands open experiment and mlflow runs automatically, while locally we create those manually.
- Remove unused experiment settings from `.env` sample file
- Hide warning azureml warnings by using `CliV2AnonymousEnvironment` as Azure ML environment name
- Temporary solution for wrong json format in Q&A Gen step with current CI generation model version by removing all "..."` strings from the model response
### WIP
#540
As a researcher I would like all my
config.json
hyper parameters logged asmlflow
tags as soon as possibleSo, I would be able to compare between my job runs even if pipeline didn't finish to run (failed / long time running).
note:
today only few properties are being tagged in mlflow and many parameters are missing.
Tasks
The text was updated successfully, but these errors were encountered: