[Feature] Better versioning for ML model files

[agm-eratosth]

Is there an existing feature already?

• Yes, I have checked the existing features.

Description

Hi,

Can you please convert all pretrained models to safetensors? I noticed https://github.com/TorchDSP/torchsig/blob/main/examples/13_example_pretrained_models.ipynb contains .pth, .ckpt etc and it would be much better, logistically, if this was in safetensors.

Additionally, is there full list of all pretrained models? Are the models listed in 13_example_pretrained_models.ipynb the extensive list?

Thank you.

[MattCarrickPL]

Thanks for reporting, discussing internally now.

[MattCarrickPL]

Do YOLO models support safetensors? If there's a way to do this please let us know.

[MattCarrickPL]

Answering this part of your question:

Are the models listed in 13_example_pretrained_models.ipynb the extensive list?

Yes

[MattCarrickPL]

No response after a week so I'm closing this out. Happy to discuss conversion to safetensors but need some assistance to get there. If you have insights please let us know and we can discuss further.

[agm-eratosth]

Hi @MattCarrickPL - apologies. You brought up a valid point with the way the Ultralytics models/library works. It would likely need to be converted back. For now this format works until I can compare what might happen when converting to safetensors.

However this also brings up a couple of follows I have; how do you plan on versioning your pretrained files?

Do you think you could include a files like ubuntu has here: https://releases.ubuntu.com/24.10/ ? Basically:

https://bucket.ltsnet.net/torchsig/models/models.list

• this would contain all files in https://bucket.ltsnet.net/torchsig/models

then:
https://bucket.ltsnet.net/torchsig/SHA256SUMS

• would contain each model and a SHA256 or SHA512 checksum, e.g:
• 123456789ABCDEF *yolo_detect.pt

https://bucket.ltsnet.net/torchsig/models/SHA256SUMS.gpg

• would contain PGP signature

This would make it easier to verify downloads similar to: https://ubuntu.com/tutorials/how-to-verify-ubuntu

Even just starting with the models.list and checksums without pgp would be good so we can match versions up by hash.

Thanks.

[MattCarrickPL]

This is a good recommendation. I'm not sure if we will do checksums. Would adding a release number to the model filename get you the versioning you're looking for? We've still got something of a checklist for additional features we want to push into 1.0+ but I'll reopen this issue so we can revisit this later.

[agm-eratosth]

Hi @MattCarrickPL I think that might work, however I'll leave it to you for how to think through exactly with the implementation such that things don't break every time a new model will be released.

Could you also just confirm and double check all models that are in https://bucket.ltsnet.net/torchsig/models/ - there isn't a comprehensive place in the new 1.0 version it seems and don't want to miss any.

So far I have:
https://bucket.ltsnet.net/torchsig/models/11s.pt
https://bucket.ltsnet.net/torchsig/models/convit_narrowband.pth
https://bucket.ltsnet.net/torchsig/models/xcit.ckpt
https://bucket.ltsnet.net/torchsig/models/xcit_narrowband.ckpt
https://bucket.ltsnet.net/torchsig/models/yolo_classify.pt
https://bucket.ltsnet.net/torchsig/models/yolo_detect.pt

https://bucket.ltsnet.net/torchsig/models/detect.pt

Are all of these being used in v0.6.1 and v1.0 ?

Please let me know if I've missed any others.