Explicit default arguments

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Improvement to JSON to YOLO conversion script with better configurability for COCO datasets.

📊 Key Changes

• Refactoring of the convert_coco_json function parameters to use named arguments for clarity.
• Introduction of two explicit parameters: use_segments and cls91to80.

🎯 Purpose & Impact

• 🎨 Enhances readability and maintainability of the code by using more descriptive function arguments.
• 🧩 Offers users the option to specify whether to use segmentation data (use_segments) and whether to convert COCO's original 91 classes to the 80 commonly used classes (cls91to80).
• 🔄 Potentially affects users who utilize the script for COCO dataset conversions, providing more tailored usage aligned with their specific needs.

[sourcery-ai]

Sourcery Code Quality Report

❌  Merging this PR will decrease code quality in the affected files by 0.03%.

Quality metrics	Before	After	Change
Complexity	26.34 😞	26.34 😞	0.00
Method Length	216.12 ⛔	216.62 ⛔	0.50 👎
Working memory	17.08 ⛔	17.08 ⛔	0.00
Quality	25.70% 😞	25.67% 😞	-0.03% 👎

Other metrics	Before	After	Change
Lines	324	326	2

Changed files	Quality Before	Quality After	Quality Change
general_json2yolo.py	25.70% 😞	25.67% 😞	-0.03% 👎

Here are some functions in these files that still need a tune-up:

File	Function	Complexity	Length	Working Memory	Quality	Recommendation
general_json2yolo.py	convert_ath_json	46 ⛔	523 ⛔	22 ⛔	7.40% ⛔	Refactor to reduce nesting. Try splitting into smaller methods. Extract out complex expressions
general_json2yolo.py	convert_vott_json	21 😞	413 ⛔	20 ⛔	20.02% ⛔	Refactor to reduce nesting. Try splitting into smaller methods. Extract out complex expressions
general_json2yolo.py	merge_multi_segment	25 😞	259 ⛔	11 😞	31.77% 😞	Refactor to reduce nesting. Try splitting into smaller methods. Extract out complex expressions
general_json2yolo.py	convert_infolks_json	9 🙂	362 ⛔	14 😞	36.25% 😞	Try splitting into smaller methods. Extract out complex expressions

Legend and Explanation

The emojis denote the absolute quality of the code:

• ⭐ excellent
• 🙂 good
• 😞 poor
• ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.

---

Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!