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

Transfer the "AutoDetection" of tunable parameters from Model-Only to General Use #25

Open
SomeoneInParticular opened this issue Jan 30, 2025 · 1 comment
Assignees
Labels
code quality Related to cleaning up the code base, rather than bug fixing or adding new features enhancement New feature or request

Comments

@SomeoneInParticular
Copy link
Collaborator

Specifically, the code used here can probably be generalized as a Mixin. This would allow it to be utilized by anything in the repository (such as data hooks), providing a universal pattern for how "tunable" elements should be defined by the user.

This would primarily benefit the data hooks, which currently have to define tunable parameters manually on a case by case basis.

@SomeoneInParticular SomeoneInParticular added code quality Related to cleaning up the code base, rather than bug fixing or adding new features enhancement New feature or request labels Jan 30, 2025
@SomeoneInParticular SomeoneInParticular self-assigned this Jan 30, 2025
@SomeoneInParticular
Copy link
Collaborator Author

SomeoneInParticular commented Jan 30, 2025

NOTE: This will probably be delayed until a major refactoring pass is done, such as the one required for #5. This is solely to prevent conflicts between the two

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Related to cleaning up the code base, rather than bug fixing or adding new features enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant