fix(model): use in instead of == for metric comparison in HIST and IGMTF#2164
Open
warren618 wants to merge 1 commit intomicrosoft:mainfrom
Open
fix(model): use in instead of == for metric comparison in HIST and IGMTF#2164warren618 wants to merge 1 commit intomicrosoft:mainfrom
in instead of == for metric comparison in HIST and IGMTF#2164warren618 wants to merge 1 commit intomicrosoft:mainfrom
Conversation
…d IGMTF
The metric_fn() in pytorch_hist.py and pytorch_igmtf.py compares
self.metric against the tuple ("", "loss") using `==`, which only
matches when self.metric is exactly that tuple. Since self.metric
is always a string (e.g. "" or "loss"), this condition is never true,
causing the function to raise ValueError("unknown metric") instead
of returning the loss-based metric.
All other models (ALSTM, GRU, LSTM, etc.) correctly use `in ("", "loss")`.
Fixes the default metric path for HIST and IGMTF models.
|
@warren618 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Author
|
@microsoft-github-policy-service agree |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Fixes #2163
metric_fn()inpytorch_hist.pyandpytorch_igmtf.pycomparesself.metricagainst the tuple("", "loss")using==. Sinceself.metricis always a string, this condition is never true, causingValueError("unknown metric")on the default metric path.All other models (ALSTM, GRU, LSTM, ALSTM_TS) correctly use
in ("", "loss").Changes
qlib/contrib/model/pytorch_hist.py:==→in(line 173)qlib/contrib/model/pytorch_igmtf.py:==→in(line 166)Before / After