Skip to content
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

Geo-SAM and colab #36

Open
aloboa opened this issue Mar 1, 2024 · 1 comment
Open

Geo-SAM and colab #36

aloboa opened this issue Mar 1, 2024 · 1 comment

Comments

@aloboa
Copy link

aloboa commented Mar 1, 2024

Not having a local GPU, I wonder if the following approach is feasible/advised:

  1. Run the Geo-SAM python encoder step using colab (eg, modifying https://colab.research.google.com/github/coolzhao/Geo-SAM/blob/dev/GeoSAM-Image-Encoder/examples/geosam-image-encoder.ipynb
  2. RUn Geo-SAM Segmentation in QGIS (assuming no GPU is needed).

Also, can the encoder Co-pilot be run in colab?

@Fanchengyan
Copy link
Collaborator

Hi @aloboa ,

Yes, the image encoding process is known to be time-consuming, and we recommend using a high-performance GPU to run the Geo-SAM Encoder. The GeoSAM-Image-Encoder (Python package) is a standalone Python package that does not require QGIS as a dependency. You can directly run the Geo-SAM Encoder in Google Colab. Here is an example notebook: https://colab.research.google.com/github/coolzhao/Geo-SAM/blob/main/GeoSAM-Image-Encoder/examples/geosam-image-encoder.ipynb.

For Geo-SAM Segmentation and Copilot, the performance requirements are not high, and regular CPUs can handle them. They must be run in QGIS for a user-friendly GUI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants