-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Added to build properties #632
base: main
Are you sure you want to change the base?
Conversation
Note: The tests are failing - please review. |
We will need to verify the naming and integration with Machine.py before releasing. |
"complete" would be 1.0, not 0.5. |
Were you able to confirm that the values are updated in manual test? |
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.
Reviewed 9 of 9 files at r1, all commit messages.
Reviewable status: all files reviewed, 4 unresolved discussions (waiting on @mudiagaobrikisil)
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.
Reviewed 9 of 9 files at r1, all commit messages.
Reviewable status: all files reviewed, 10 unresolved discussions (waiting on @mudiagaobrikisil)
src/Machine/src/Serval.Machine.Shared/Services/ClearMLMonitorService.cs
line 101 at r1 (raw file):
step: 0, percentCompleted: 0.0, fineTuneProgress: 0.0,
ProgressStatus
is a general-purpose model from Machine, so we shouldn't add Serval-specific properties to it. We should create a new progress status model class. It could inherit from ProgressStatus
if that makes sense.
src/Serval/src/Serval.Grpc/Protos/serval/translation/v1/platform.proto
line 24 at r1 (raw file):
int32 step = 2; optional double percent_completed = 3; optional double fine_tune_progress = 4;
I would rename this to train_progress
.
src/Serval/src/Serval.Grpc/Protos/serval/translation/v1/platform.proto
line 25 at r1 (raw file):
optional double percent_completed = 3; optional double fine_tune_progress = 4; optional double inference_progress = 5;
I would rename this to pretranslate_progress
.
src/Serval/src/Serval.Translation/Models/Build.cs
line 13 at r1 (raw file):
public int Step { get; init; } public double? PercentCompleted { get; init; } public double? FineTuneProgress { get; init; }
I would rename this to TrainProgress
.
src/Serval/src/Serval.Translation/Models/Build.cs
line 14 at r1 (raw file):
public double? PercentCompleted { get; init; } public double? FineTuneProgress { get; init; } public double? InferenceProgress { get; init; }
I would rename this to PretranslateProgress
.
src/Serval/src/Serval.Translation/Models/Build.cs
line 21 at r1 (raw file):
public IReadOnlyDictionary<string, object>? Options { get; init; } public string? DeploymentVersion { get; init; } public IReadOnlyDictionary<string, string> ExecutionData { get; init; } = new Dictionary<string, string>();
@johnml1135 What do we think about putting the train and pretranslate progress in ExecutionData
? It could give us more flexibility, but it wouldn't be standardized.
Added and tested fineTuneProgress and InferenceProgress to the build object. I updated the UpdateStatusAsync test to test it.
This change is