Conversation
…and system tests for them.
… the open source vizier.
…e confest.py test
|
|
||
| @classmethod | ||
| def from_uid( | ||
| def from_resource_name( |
There was a problem hiding this comment.
This is a change to the public interface. It could potentially break existing customers' code.
There was a problem hiding this comment.
We can create another function of it. If it makes more sense.
| ] | ||
|
|
||
| def materialize_study_config(self) -> vz.StudyConfig: | ||
| def materialize_problem_statement(self) -> vz.ProblemStatement: |
There was a problem hiding this comment.
same comment as the one I left for def from_resource_name. I think this constitutes a breaking change.
There was a problem hiding this comment.
We can create another function of it. If it makes more sense.
| cls, | ||
| display_name: str, | ||
| problem: vz.ProblemStatement, | ||
| problem: vz.StudyConfig, |
There was a problem hiding this comment.
Looks like ProblemStatement is imported in pyvizier/__init__.py. Is the class no longer being used and its features are now completely replaced and/or incapsulated in StudyConfig?
There was a problem hiding this comment.
The ProblemStatement is the rename of Study config.
There was a problem hiding this comment.
ProblemStatement is the base class for StudyConfig, so both can be used from a pytype perspective.
Using StudyConfig here means that we want the Vertex specific StudyConfig, and not any subclass of ProblemStatement.
We expect Vertex users to only create StudyConfig objects, not ProblemStatement objects.
| def from_resource_name( | ||
| cls: Type[_T], | ||
| uid: str, | ||
| name: str, |
There was a problem hiding this comment.
same comment as above. This is a breaking change for customers who use keyword arguments in their function calls
There was a problem hiding this comment.
Looks like the Vertex Vizier SDK is not used too much by the customers. I think it's fine to make the change on the API ? https://datastudio.google.com/c/u/0/reporting/d8a64931-8a91-4f07-9abc-93fece2e318d/page/p_n2odnmsgmc
|
|
||
| def should_stop(self) -> bool: | ||
| """Returns true if the Trial should stop.""" | ||
| def check_early_stopping(self) -> bool: |
There was a problem hiding this comment.
same comment as above. this is a breaking change
There was a problem hiding this comment.
Looks like the Vertex Vizier SDK is not used too much by the customers. I think it's fine to make the change on the API ? https://datastudio.google.com/c/u/0/reporting/d8a64931-8a91-4f07-9abc-93fece2e318d/page/p_n2odnmsgmc
sagipe
left a comment
There was a problem hiding this comment.
halio@ this LGTM from my side. Please address other comments.
|
We are doing maintenance on our repo starting today and need to close all open PRs. When this is done next week, you'll be able to open a new PR. |
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕