standardize file name as per framework name in metric#76
standardize file name as per framework name in metric#76tisnik merged 1 commit intolightspeed-core:mainfrom
Conversation
WalkthroughUpdated documentation and refactored imports to point ScriptEvalMetrics to the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
🧰 Additional context used🧬 Code graph analysis (2)src/lightspeed_evaluation/core/metrics/__init__.py (1)
src/lightspeed_evaluation/pipeline/evaluation/evaluator.py (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
🔇 Additional comments (3)
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 |
|
@VladimirKadlec @tisnik PTAL |
standardize file name as per framework name in metric.
Example
metric name is
ragas:faithfulness -> file name ragas.pyit is better keep same for script
metric_name is
script:action_eval -> file renamed from script_eval.py to script.pySummary by CodeRabbit
New Features
Documentation
Refactor