-
Notifications
You must be signed in to change notification settings - Fork 404
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
Support multiple data fidelity dimensions in MultiFidelityGP models #1956
Closed
Closed
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
41b08e8
generalises SingleTaskMultiFidelityGP and FixedNoiseMultiFidelityGP t…
c3949d1
Merge remote-tracking branch 'upstream/main'
0b3cb6d
addresses PR comments
633d9c0
BOPE tutorial text edits (#1972)
esantorella 3506538
Merge SupervisedDataset & FixedNoiseDataset (#1945)
saitcakmak 52529e1
fix constraint handling in single objective MBM (#1973)
sdaulton 0a1cfbe
update changelog for 0.9.2
sdaulton b7258c8
Type signature fix for private methods of `qMultiStepLookahead`
SebastianAment fe122b0
bump py version in deploy on release
sdaulton b6e74ac
Don't allow unused **kwargs in input_constructors except for a define…
esantorella 814f522
Even more fixes to unused kwargs (#1985)
esantorella 36549fd
generalises SingleTaskMultiFidelityGP and FixedNoiseMultiFidelityGP t…
2b4c5e2
addresses PR comments
2d41c94
restores coverage to 100%
129251b
updates documentation for multi-fidelity GPs in tutorials
9a1a41f
merge changes from upstream/main
946f0b4
Dont use a Sphinx version later than 7.1.2 (#1990)
d245dd4
generalises SingleTaskMultiFidelityGP and FixedNoiseMultiFidelityGP t…
9bc46ca
addresses PR comments
1666b1d
restores coverage to 100%
db9b864
updates documentation for multi-fidelity GPs in tutorials
c56eb14
Merge remote-tracking branch 'refs/remotes/origin/main'
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I like this, the
|
operator only works in py3.10+, and we still need to be compatible with py3.9There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could also make sense to have a
data_fidelities
argument that only accepts lists (or tuples) and require people to use that even for the single-fidelity case, that way we wouldn't have to overload the arg types. This could be done nicely by keeping thedata_fidelity
arg around but marking it as deprecated (and raise a deprecation warning if used in the constructor). Wdyt?cc @saitcakmak, @esantorella for thoughts.