samgeo.hq_sam not working in docker about segment-geospatial

[MarcioDDCF]

Is this related to [https://github.com//issues/201] ?

[glemoine62]

No. Not related to #201. I want to run samgeo.hq_sam on the CPU in the same way you can run "normal" samgeo on the CPU.
The solution proposed in #173 does not work, whether you install locally or in a docker container.

The speed difference between running inference with samgeo on a GPU or a CPU is not too dramatic, esp. when testing (GPU order of 6 faster). The models require a pretty large GPU forcing you to move to cloud resources. I prefer running on CPU.

[flxcp]

Try adding device='cpu' when initializing SamGeo:

from samgeo.hq_sam import SamGeo

sam = SamGeo(model_type="vit_h", sam_kwargs=None, device='cpu')

See if it helps!

[glemoine62]

Thanks for the tip, but I tried that, and it doesn't work. The problem is in the sam_hq implementation, which does not check for the device key. To get this solved, you need to go into /opt/conda/lib/python3.11/site-packages/segment_anything_hq/build_sam.py

and edit line 160:

state_dict = torch.load(f, map_location=torch.device('cpu'))

which is for the vit_h model, you need to edit the equivalent statements for the other models. This is the quick and dirty solution, it would be better to do this on the basis of the device keyword.

(I assume use of the giswqs/segment-geospatial docker image. I (locally) commit the revised container to giswqs/segment-geospatial-cpu)