add timestamps to cached UME checkpoints#145
Merged
Conversation
…to k/ume-checkpoint-timestamp
…onfig/manage_ume_checkpoints.yaml
ncfrey
approved these changes
Jul 14, 2025
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
2 participants
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.
Description
Added S3 timestamp to local/cached UME checkpoint filenames. We now retrieve the
LastModifiedtimestamp from S3 objects and includes it in the local cached filename format. This provides better traceability and helps with conflicts when UME models are updated in S3.Example:
INFO:lobster.model.utils_checkpoint:Downloading checkpoint to ../models/ume-small-base-90M-20250711-061718.ckptSomewhat solves issue #117 though there could be a more robust solution.
Type of Change
Testing
Checklist