Evaluation Metrics, Fix-ups, Output Parsing for Evaluation

[alckasoc]

🤔 Reasoning

Explain the purpose of this PR...

🚧 Changes

Describe the changes made...

✅ PR Checklist

• [x] Using this PR template?
• [x] Linked issue?
• [x] Added feature?
  • [x] Added/updated docs?
  • [x] Added/updated tests?

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 96.28571% with 13 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
agential/eval/metrics/classification.py	92.13%	7 Missing :warning:
agential/prompting/cot/strategies/code.py	82.35%	3 Missing :warning:
agential/agents/base/agent.py	86.66%	2 Missing :warning:
agential/agents/lats/strategies/math.py	75.00%	1 Missing :warning:

Files with missing lines	Coverage Δ
agential/agents/base/modules/memory.py	73.33% <ø> (ø)
agential/agents/base/modules/reflect.py	81.81% <ø> (ø)
agential/agents/base/output.py	100.00% <100.00%> (ø)
agential/agents/base/strategies.py	100.00% <100.00%> (ø)
agential/agents/critic/agent.py	100.00% <100.00%> (ø)
agential/agents/critic/functional.py	100.00% <100.00%> (ø)
agential/agents/critic/output.py	100.00% <100.00%> (ø)
agential/agents/critic/strategies/code.py	100.00% <100.00%> (ø)
agential/agents/critic/strategies/general.py	92.10% <100.00%> (ø)
agential/agents/critic/strategies/math.py	100.00% <100.00%> (ø)
... and 66 more

[alckasoc]

Slack File: hotpot_dev_v1_simplified.json

[alckasoc]

https://www.hyperwriteai.com/

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13960463	Triggered	Google API Key	8c8433995b331665835d94c2ee546a168db73167	tmp.ipynb	View secret
13960463	Triggered	Google API Key	59800ef0c1275f23f8558b806652534504f342cd	tmp.ipynb	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}