Skip to content

update max_model when trial fails #6596

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

Merged
merged 3 commits into from
Mar 27, 2023

Conversation

LittleLittleCloud
Copy link
Contributor

@LittleLittleCloud LittleLittleCloud commented Mar 9, 2023

We are excited to review your PR.

So we can do the best job, please check:

  • There's a descriptive title that will make sense to other developers some time from now.
  • There's associated issues. All PR's should have issue(s) associated - unless a trivial self-evident change such as fixing a typo. You can use the format Fixes #nnnn in your description to cause GitHub to automatically close the issue(s) when your PR is merged.
  • Your change description explains what the change does, why you chose your approach, and anything else that reviewers should know.
  • You have included any necessary tests in the same PR.

also fix #6604

@@ -296,22 +296,8 @@ void handler(object o, EventArgs e)
tuner.Update(trialResult);
trialResultManager?.AddOrUpdateTrialResult(trialResult);
aggregateTrainingStopManager.Update(trialResult);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to update tuner/trialresultmanager/trainningStopManager even when a trial fails for any reasons as long as the experiment still continues

@codecov
Copy link

codecov bot commented Mar 22, 2023

Codecov Report

Merging #6596 (ddf7953) into main (db19715) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6596   +/-   ##
=======================================
  Coverage   68.38%   68.38%           
=======================================
  Files        1176     1176           
  Lines      248210   248210           
  Branches    25915    25915           
=======================================
+ Hits       169728   169734    +6     
+ Misses      71708    71705    -3     
+ Partials     6774     6771    -3     
Flag Coverage Δ
Debug 68.38% <ø> (+<0.01%) ⬆️
production 62.76% <ø> (+<0.01%) ⬆️
test 88.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 3 files with indirect coverage changes

{
logger.Trace($"trial cancelled - {JsonSerializer.Serialize(trialSettings)}, continue training");
logger.Trace($"catch exception when training trial {trialSettings.TrialId} - {JsonSerializer.Serialize(trialSettings)}, continue training");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exception thrown during Trial {trialSettings.TrialId} with configuration {JsonSerializer.Serialize(trialSettings)}

Exception Details: ex.Message

Abandoning Trial {trialSettings.TrialId} and continue training.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LittleLittleCloud is there a way to localization for these strings? Do we do it anywhere else in this repo?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@luisquintanilla thoughts on strings here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JakeRadMSFT I don't think strings are localized anywhere in mlnet, aren't they? @michaelgsharp

@LittleLittleCloud LittleLittleCloud merged commit cb7b724 into dotnet:main Mar 27, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Apr 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to use CostFrugalTuner in AutoML
2 participants