-
Notifications
You must be signed in to change notification settings - Fork 990
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
How do I evaluate the results after stage-1 of training BLIP2? #774
Comments
Hey @hawkiyc I want to train the BLIP2, however i am getting issues like this :
because, some of the packages are not being installed properly due to compatiblity. For example :
I am running it on colab with A100. Can you provide the solution? |
Hi @parth1313, the cached_download is removed after transformer_hub v0.26. Downgrade your huggingface_hub to 0.25.* shall solve this problem. |
Thank you for the reply @hawkiyc Still getting the issue. I am using salesforce-lavis==1.0.2 and all other libraries as given in the requirements.txt:
Here is what i am getting when installing
And following error while running
|
Hi @parth1313, Lavis framework needs specific versions of transformer; please install your transformer with |
Thank you for the help @hawkiyc But,
And if i try to install Moreover, none of the downgraded version of albucore 0.0.19 is compatible with opencv-python-headless 4.5.5.64. can you further calrify? |
Hi, @parth1313 |
Hi, developers,
I am revising your code to build a modified BLIP2 model for time-series input. Now, I am trying to figure out the architecture of this framework. I have tested the
bash run_scripts/blip2/train/pretrain_stage1.sh
command with the coco dataset (btw, there are mismatches between images and annotations in the vg dataset, so I removed it), and it seems to work fine. However, I cannot find any script or .yaml file for evaluation of the result of stage 1. I have checked thelavis/configs/datasets/coco/defaults_cap.yaml
file, and there is information for train, val, and test subsets.defaults_cap.yaml
Here is the printed result in the terminal:
Output log file
The text was updated successfully, but these errors were encountered: