feature: load detection class names from yaml file

[phinik]

• Added the possibility to load (detection) class names from a respective yaml file with key 'detection'

Proposed changes

added the possibility to load (detection) class names from a yaml file (key 'detection')

Necessary checks

• Update poetry package version semantically
• Write documentation
• Create issues for future work
• Test on your machine

[Flova]

Some minor comments. Otherwise it is fine imo.

[Flova]

One could also add the segmentation names to the printout in the evaluation:
This would be a bit more effort, but it would be nice now that they are available.

[jaagut]

Thank you @phinik for your nice contribution!

[jaagut]

We probably also want to adapt the path in

YOEO/config/261.data

Line 4 in bb22da1

names=data/261.names

to the new format.

Before we do that, I would suggest moving the TORSO.names / yoeo_name.yaml file from the data dir to the config dir?
Then, we would need to adapt the path also in the detect.py...

What is your opinion?

[phinik]

We probably also want to adapt the path in

YOEO/config/261.data

Line 4 in bb22da1

names=data/261.names

to the new format.
Before we do that, I would suggest moving the TORSO.names / yoeo_name.yaml file from the data dir to the config dir? Then, we would need to adapt the path also in the detect.py...

What is your opinion?

I leave it up to you and Flova to decide on this.

[Flova]

We probably also want to adapt the path in

YOEO/config/261.data

Line 4 in bb22da1

names=data/261.names

to the new format.

But the 261.names is not in the repo and I wonder why the 261.data file is in the config folder xD
The dataset was just used for local tests.

Before we do that, I would suggest moving the TORSO.names / yoeo_name.yaml file from the data dir to the config dir? Then, we would need to adapt the path also in the detect.py...

I also wonder a bit if we really want to do this, as the .data, as well as the .names file, are normally part of the dataset. But we should adapt the custom.data example file to the yaml version never the less.

We also need to adapt the README.md section that describes the expected data structure. Especially this section: https://github.com/bit-bots/YOEO/tree/main#classes
A sample yaml for TORSO could be added.

[jaagut]

We also need to adapt the README.md section that describes the expected data structure. Especially this section: https://github.com/bit-bots/YOEO/tree/main#classes
A sample yaml for TORSO could be added.

This should be another PR