Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple Ensemble Step from ML Step #163

Closed
ntalluri opened this issue Jun 20, 2024 · 2 comments
Closed

Decouple Ensemble Step from ML Step #163

ntalluri opened this issue Jun 20, 2024 · 2 comments

Comments

@ntalluri
Copy link
Collaborator

ntalluri commented Jun 20, 2024

With the updates to the code in #160, algorithms with multiple parameter combinations will now run aggregate per-algorithm ML code. As a result, we won't be able to run ensemble code for algorithms with one or fewer parameter combinations. To ensure we have ensemble networks for all algorithms, we need to create a new rule that uses the ensembling code per algorithm, rather than running all the ML code for each algorithm.

@ntalluri
Copy link
Collaborator Author

For later iterations of the evaluation code, having the decoupled ensemble step will be beneficial for implementing the ensemble evaluation idea.

@agitter
Copy link
Collaborator

agitter commented Sep 22, 2024

Closed by #175

@agitter agitter closed this as completed Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants