-
Notifications
You must be signed in to change notification settings - Fork 448
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
Add missing form fields to new UI #1463
Add missing form fields to new UI #1463
Conversation
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.
Thanks for this update, it's looks great @kimwnasptd.
I left few comments.
...new-ui/v1beta1/frontend/src/app/pages/experiment-creation/experiment-creation.component.html
Outdated
Show resolved
Hide resolved
pkg/new-ui/v1beta1/frontend/src/app/services/experiment-form.service.ts
Outdated
Show resolved
Hide resolved
Ι see the
I'll try to rebase on top of the latest master to see if this resolves the issue |
03b0efc
to
43ff140
Compare
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
Hmm the error seems to persist. Why does the Lastly, @andreyvelich could you also write the |
@googlebot I consent. |
@kimwnasptd GitHub actions should be fixed in this PR: #1465. |
ACK! I also pushed another small commit, because there was a small error with building the frontend. I've explained the reason behind it in the commit message as well, but the verdict is that Angular could not detect that formGroup.get('trialParameters').controls Is a FormArray and has a property controls. This happens when we use this in the html file. In any case I believe this is another indication that the next thing to work on is the tests and having a CI process that at least checks that the UI can be build. |
The form will be showing a dynamic list of trial parameters that the users will need to configure. This list is affected from the yaml content. The JS parses the yaml contents to find the trial parameters. Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
Create a common component for the algorithm settings. We will need this for Early Stopping, which also has algorithm settings. Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
Add a distinct section for Early Stopping, when the Search Algorithm is for Hyper Parameter tuning. Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
* The algorithm settings got applied in the form only after the user selected a different algorithm. The preselected value would not have the list of settings assigned once the form loads. * Use null everywhere for the `random_state` parameter Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
Co-authored-by: Andrey Velichkevich <andrey.velichkevich@gmail.com>
Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
Using "formGroup.get('trialParameters').controls" in the html results in an error, during the build process. This is because Angular can't deduce that the control returned from the get() method is a form array. We will define a FormArray variable and use it directly instead of get()ing it from he form group. Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
0527881
to
560a767
Compare
@kimwnasptd As I can see the CI passed. |
Yeap, we should be good to go! |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreyvelich, kimwnasptd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
It adds support to the new UI's #1421 form for
With this PR the form will be exposing all of the fields required to create a new Experiment. But, at the same time the only limitation I bumped into is the fact that the new UI doesn't currently allow us to edit the
source
of the Metric Collector. I'll comment this on our issue where we track the missing features.Videos of the changes
algorithm-settings.mp4
early-stopping.mp4
trial-parameters.mp4
Which issue(s) this PR fixes
It's a first step for #1443. As mentioned above it won't close the issue because the new UI's form still doesn't allow us to configure the
source
of the Metrics Collector.Special notes for your reviewer:
Since the PR is a bit big I'll also try to document my changes here, as well as in the commits.
random_state
setting for theRandom
HP algorithm [ which the value selected once the form loads ]None
for therandom_state
. I should use an empty value instead/cc @andreyvelich @gaocegege @johnugeorge