Is this library still maintained?

[adamjstewart]

It's been almost a year since the last release, and most commits since then have been limited to auto-generated dependabot PRs. The outdated version of timm required to use smp now makes it incompatible with the latest release of lightly: microsoft/torchgeo#1824. PRs to update the version of timm have been ignored (#839), and requests to unpin the timm dependency have been rejected (#620). Our own contributions have been closed, and requests to reopen them have been ignored as well (#776).

Which begs the question: is this library still maintained?

If yes, then it would be incredibly helpful to unpin the timm dependency.

If no, then would you be willing to pass the torch (heh) on to someone else so this incredibly useful library does not become abandoned? Alternatively, does anyone know any alternatives that offer the same functionality and compatibility with modern timm releases as smp?

[WeisiX]

Same question.

[isaaccorley]

I made a fork that is a WIP but will be adding additional features and support and can be installed using pip install torchseg https://github.com/isaaccorley/torchseg

[kpierce8]

my models from a while ago all die at the utils section now. Was moving to torchgeo but now torchgeo is still having issues with this repo. I guess I'll look at torchseg.

[adamjstewart]

TorchGeo may switch to TorchSeg if smp is no longer maintained.

[ogencoglu]

Well analyzed @adamjstewart ! Would be great to hear the verdict on this.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[adamjstewart]

The irony is palpable