Mlflow eval - #26
Conversation
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
01aa932 to
844e97a
Compare
69e0180 to
a2cb527
Compare
a2cb527 to
6a60940
Compare
jerry-ng2
left a comment
There was a problem hiding this comment.
Are there any examples on the jumpbox?
| Load annotation_draft.json for a given job_id. | ||
|
|
||
| Args: | ||
| job_id: Job ID to load annotation for | ||
|
|
||
| Returns: | ||
| Annotation dict if successful, None on failure | ||
| """ | ||
| annotation_file = Path(".analysis") / job_id / "annotation_draft.json" |
There was a problem hiding this comment.
should be annotation.json
|
There should be a condition that checks if an eval already exists for a certain job_id. wdyt? Maybe look into |
Includes PR #14 (to allow for testing while its in WIP)
MLFlow Eval loads annotator.json files from jumpbox
Then logs this info onto MLFlow
These can be viewed in evaluation runs under the experiment name that was set.
Needs to include the Human expectations.