segmentation_models.pytorch VS ultralytics

Also, I’d suggest considering switching to the segmentation-models library - it provides U-Net models with a variety of pretrained backbones of as encoders. The author also put out a PyTorch version. https://github.com/qubvel/segmentation_models.pytorch https://github.com/qubvel/segmentation_models

SMP offers a wide variety of segmentation models with the option to use pre-trained weights.

SMP has a lot of different choices for architecture other than unet, and a ton of different encoders. I like deeplabv3+/unet with regnety encoder, works well for most things https://github.com/qubvel/segmentation_models.pytorch

This basic example from segmentation models PyTorch repo would be good tutorial to start with. The library is very good, I like the unet, fpn and deeplabv3+ architectures with regnety as encoder https://github.com/qubvel/segmentation_models.pytorch/blob/master/examples/binary_segmentation_intro.ipynb

Sounds like a good semantic segmentation problem, I like this repo: https://github.com/qubvel/segmentation_models.pytorch

When i pass the CT-Scans and the masks to the Loss Function, which is the Jaccard-Loss from the segmentation_models.pytorch library, the value does not decrease but stay in the range of 1.0-0.9 over 50 epochs training on only one batch of 32 images. As far as I have understood, my network should overfit and the loss should decrease since I am only training on one batch of a small amount of images. However this does not happen. I also tried more batches with all the data over 100 epochs, but the loss does not decrease either obviously. Does anyone have an idea what I might have done wrong? Do I have to change anything when passing the masks to my loss function?

I know there is a decent one in segmentation models python (MA-Net: A Multi-Scale Attention Network for Liver and Tumor Segmentation)

You could also use qubvel's segmentation models if you would like to explore semantic segmentation.

Check out segmentation models pytorch, really easy to use, has a great interface.

Have you tried another implementation? For example: qubvel/segmentation_models.pytorch

Yep, I noticed this a while ago. It posts easily identifiable ChatGPT responses. It also posts garbage wrong answers which makes it worse than useless. Totally disrespectful to the userbase.

https://github.com/ultralytics/ultralytics/issues/5748#issue...

There are obvious places it is being used that I have noticed organically. For instance, check out the answers in this repo:

https://github.com/ultralytics/ultralytics/issues/5748#issue...

If you read the answers there, the style of answering is always to repeat the question in a very specific way. Once you see it you can’t in-see it.

When browsing the state-of-the-art in object detection on Papers with Code, I found the YOLO model to be one of the most popular, accurate, and fastest. That being said, I would recommend having a look at Ultralytics, which provides the tools to evaluate, predict, and export the latest versions of YOLO models with only a few lines of code.

YOLOv8 (You Only Look Once) is an open-source Computer Vision AI model released on January 10th, 2023. It’s called YOLO because it detects everything inside an image in a single pass. The new version can perform image detection, classification, instance segmentation, tracking, and pose estimation tasks.

Next, I needed to figure out, how can I access the stream, recognize an animal, then let Max know? There are tons of examples of recognizing an object via camera frames, but I ultimately found this python library called ultralytics that supports RTSP streams and classifying objects in the video frames using pre-built models. The docs looked like it would be pretty low effort, so after some experimentation, I was successful in having the ultralytics library recognize objects from my cheap camera!

I have created an issue in their Github as well but so far not much help has been recieved. You can check that here

And the target models include: * YOLOv8 (You Only Look Once) * YOLO-NAS * YOLOv5 * and DETR