You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to express my gratitude for your efforts. I've encountered an issue when attempting to run both ViT and ViTST models. Specifically, I'm encountering an error when executing the following command:
python spot_deepfakes.py --media_type video --data_dir /DFSpot-Deepfake-Recognition/sample_videos/dfdc/fake/ --dataset dfdc --model ViT --model_dir /DFSpot-Deepfake-Recognition/models --annotate True --output_dir /DFSpot-Deepfake-Recognition/src/output --video_id 0
The error message I'm receiving is as follows:
RuntimeError: mat1 and mat2 shapes cannot be multiplied (300x201728 and 1024x1)
Interestingly, I am able to run the same command successfully with both TimmV2 and Timmvst models. However, I face this error exclusively when attempting to run ViT and ViTST models. It's worth noting that the video input remains consistent across all four models.
Any assistance with resolving this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hello,
I want to express my gratitude for your efforts. I've encountered an issue when attempting to run both ViT and ViTST models. Specifically, I'm encountering an error when executing the following command:
python spot_deepfakes.py --media_type video --data_dir /DFSpot-Deepfake-Recognition/sample_videos/dfdc/fake/ --dataset dfdc --model ViT --model_dir /DFSpot-Deepfake-Recognition/models --annotate True --output_dir /DFSpot-Deepfake-Recognition/src/output --video_id 0
The error message I'm receiving is as follows:
RuntimeError: mat1 and mat2 shapes cannot be multiplied (300x201728 and 1024x1)
Interestingly, I am able to run the same command successfully with both TimmV2 and Timmvst models. However, I face this error exclusively when attempting to run ViT and ViTST models. It's worth noting that the video input remains consistent across all four models.
Any assistance with resolving this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: