Allow MEoH resume from a checkpoint path - #80
Open
er-s-an wants to merge 1 commit into
Open
Conversation
Signed-off-by: er-s-an <3137612974@qq.com>
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.
What changed
pathtoresume_meohWhy
resume_meohcurrently hard-codespf._log_dir, so callers cannot resume a MEoH run from a different checkpoint directory. EoH and ReEvo already accept an explicit resume path. This adds the same capability without breaking existing no-argument calls.Fixes #58.
Validation
python3 -m py_compile llm4ad/method/meoh/resume.pypf._log_dirA full package import was not used for the runtime test because the local environment does not have the optional
codebleumodule imported by MEoH population code.