search

microsoft / CameraTraps

PyTorch Wildlife: a Collaborative Deep Learning Framework for Conservation.
https://cameratraps.readthedocs.io/en/latest/
MIT License
763 stars 241 forks source link

Issue with accessing MegaDetector weight file #355

Closed ronbitonn closed 10 months ago

ronbitonn commented 1 year ago

I am experiencing difficulties accessing the MegaDetector weight file when running the following command in Google Colab notebook:

ruby Copy code !wget https://lilablobssc.blob.core.windows.net/models/camera_traps/megadetector/md_v4.1.0/md_v4.1.0.pb Previously, this command worked fine, allowing me to download the MegaDetector weight file (md_v4.1.0.pb) from the specified URL. However, I now receive the following error message:

vbnet Copy code --2023-07-03 09:36:45-- https://lilablobssc.blob.core.windows.net/models/camera_traps/megadetector/md_v4.1.0/md_v4.1.0.pb Resolving lilablobssc.blob.core.windows.net (lilablobssc.blob.core.windows.net)... 20.60.149.97 Connecting to lilablobssc.blob.core.windows.net (lilablobssc.blob.core.windows.net)|20.60.149.97|:443... connected. HTTP request sent, awaiting response... 409 Public access is not permitted on this storage account. 2023-07-03 09:36:45 ERROR 409: Public access is not permitted on this storage account. The error indicates that public access is not allowed on the storage account hosting the MegaDetector weight file. I tried this command around a month ago, and it worked without any issues.

I kindly request assistance in resolving this issue. Is there an alternative source where I can access the MegaDetector weight file (md_v4.1.0.pb), or could you provide guidance on how to obtain it?

If needed, I can share my Google Colab notebook via email for further investigation.

Thank you for your support!

aa-hernandez commented 10 months ago

Thank you for your valuable input. We've moved to a new codebase with the release of Pytorch-Wildlife v1.0. The issue you mentioned might not exist anymore or it might be resolved in the new codebase. We encourage you to try the new release here and share any further feedback or concerns. If the issue still persists, please let us know through this channel and we will work on it!

If you're still interested in working with the previous version, you can take a look at Dan Morris' fork. The issue may or may not be resolved in that codebase.