Refactor e2e_eval function for modularity

[sweep-nightly[bot]]

Description

This PR refactors the e2e_eval function in tools/end2end/eval_end2end.py to improve its modularity. The function was previously quite large and performed multiple tasks, making it difficult to understand and maintain. The changes in this PR break down the e2e_eval function into smaller, more manageable functions, each performing a specific task.

Summary of Changes

1. Extracted the part of the e2e_eval function that calculates the Intersection over Union (IoU) into a new function named calculate_iou.
2. Extracted the part of the e2e_eval function that calculates the edit distance into a new function named calculate_edit_distance.
3. Extracted the part of the e2e_eval function that calculates the precision, recall, and f-measure into a new function named calculate_metrics.
4. Extracted the part of the e2e_eval function that calculates the average edit distance per image and per field into a new function named calculate_avg_edit_distance.

These changes make the e2e_eval function easier to understand and maintain, and allow for better testing and reuse of the individual tasks performed by the function.

Fixes #1.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the library rope to refactor Python! Check out Large Language Models are Bad at Refactoring Code.
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly[bot]]

Sandbox Executions

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

[sweep-nightly[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: There should be no trailing whitespace at the end of lines.
• [ ] Apply: Indentation should be consistent throughout the codebase.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: There should be no commented out code in the codebase.
• [ ] Apply: There should be no unused imports in the codebase.