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

Change BMS to take in priors and ops together #29

Open
TheLemonPig opened this issue Jan 6, 2023 · 1 comment
Open

Change BMS to take in priors and ops together #29

TheLemonPig opened this issue Jan 6, 2023 · 1 comment
Labels
enhancement New feature or request.

Comments

@TheLemonPig
Copy link
Contributor

I realised that because BMS requires both and that they must match. If we allow the user to input their own priors then we need to make sure there is a matching ops dictionary. The simplest way I can see this is to require the user to input both themselves

@TheLemonPig
Copy link
Contributor Author

Having worked with inputting custom functions, I now believe this change isn't necessary. This is because whenever the user wishes to add their own function to the primitives or to the priors, they would be required to point towards a callable function. Callable functions have the number of arguments as a built-in attribute so we wouldn't need to specify this.

@hollandjg hollandjg transferred this issue from AutoResearch/autora Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request.
Projects
None yet
Development

No branches or pull requests

2 participants