BLIP-2 dependency resolution #20
Merged
Conversation
This file contains 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
…file, allow loading in pointnav weight checkpoint used in previous experiments
bernadettekb
requested review from
jiuguangw,
kashton-bdai and
naokiyokoyama
jiuguangw
approved these changes
Dec 19, 2023
mobiiin
pushed a commit
to mobiiin/vlfm
that referenced
this pull request
Feb 7, 2025
The transformers version in VLFM conflicts with the versions in the bdai requirements. I originally fixed them here, but due to some other dependency conflicts in the integration, this will break some VLFM functionality without some more substantial code changes which need to happen after moving the code. --------- Co-authored-by: Katrina Ashton <kashton@theaiinstitute.com>
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.
The transformers version in VLFM conflicts with the versions in the bdai requirements. I originally fixed them here, but due to some other dependency conflicts in the integration, this will break some VLFM functionality without some more substantial code changes which need to happen after moving the code.