feat: Support in RT Trainer for multiple entities.

[NicolaiRee]

Solving #143 by expanding the Regression Transformer trainer to support multi-entity discriminations, i.e., support the multientity_cg collator from the RT repo.

Signed-off-by: Nicolai Ree Ree@sunray

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Nicolai Ree.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[jannisborn]

Cool, great stuff @NicolaiRee! I expanded the docstrings a bit, see my comments. The only remaining thing to add is a test for this new feature (see src/gt4sd/training_pipelines/tests

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Nicolai Ree.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Nicolai Ree.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Nicolai Ree.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Nicolai Ree.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[jannisborn]

Hey @NicolaiRee,
Cool, the tests are passing now. Did you follow the steps suggested by the CLA bot to make the verification checks passing?

[NicolaiRee]

Hey @jannisborn, I have followed the direct instruction about the email and made the issue for getting on the contribution list, but I do not know why the verification still fails. Do you have any suggestions?

[drugilsberg]

Hey @jannisborn, I have followed the direct instruction about the email and made the issue for getting on the contribution list, but I do not know why the verification still fails. Do you have any suggestions?

I think the problem is the first commit that is associated to an unverified account (see image).

At this point it's probably easy to:

• close this PR
• fork gt4sd:main again and apply all changes in a single commit with the verified account
• open another PR

[NicolaiRee]

Okay lets try that