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

Anyone came across that the upper left corner of the image appears "purple". #18

Closed
xiaozhi2015 opened this issue Sep 26, 2019 · 12 comments

Comments

@xiaozhi2015
Copy link

image
image

@xiaozhi2015
Copy link
Author

And it appears in almost every result image.

@KupynOrest
Copy link
Collaborator

There is a bug in the inference, will be updated soon

@xiaozhi2015
Copy link
Author

Thx for your quick reply, looking forward to the update...

@vgg4resnet
Copy link

vgg4resnet commented Oct 8, 2019

yes,same issue here,has this been solved? I test my images ,purple filled in full image, not only the corner of images, is it this caused by np.transpose function?

@vgg4resnet
Copy link

so is that caused by the network is not converged?my predict result images were like this
image

@vgg4resnet
Copy link

vgg4resnet commented Oct 9, 2019

my training images are gray ,I convert them to BGR format,I also remove the hsv,rgb,transform part by changing the config.yaml

image
the result keep the same ,anywhere maybe lead the problem?By the way I also remove sharpen part,we are bluring the images,why do we need that?I am confused about that

@t-martyniuk
Copy link
Contributor

please check the updated links to models (latest changes to readme).
should work fine now

@xiaozhi2015
Copy link
Author

Much thx.

@vlee-harmonicinc
Copy link
Contributor

There is still some purple artifact on images with new pre-trained model.
For example:
image
image
image
image
image

It seems that relatively dark region/texture prone to have this artifact. When generating video, it trend to have artifact on same object (but not every frames)
Do anyone have idea why this issue happen?

@Sandbox3aster
Copy link
Contributor

@htleeab Which image in GoPro did you test on and which model did you use? Let me see if i can reproduce that

@vlee-harmonicinc
Copy link
Contributor

vlee-harmonicinc commented Jul 20, 2020

@Sandbox3aster
Those image are my own test assets, not GoPro dataset. I used the pretrained InceptionResNet-v2 (md5sum: 96f747f38a0119669265cbb5fc7b3c5c)
05APR_955
05APR_1993
05APR_1903
05APR_1425
05APR_1176
05APR_1085
Thanks.

@Johnreidsilver
Copy link

Johnreidsilver commented Nov 15, 2020

Same problem here, using cpu and same model
96f747f38a0119669265cbb5fc7b3c5c best_fpn.h5

Ubuntu 18.04.02, python 3.6.9
torch==1.5.0
torchsummary==1.5.1
torchvision==0.6.0
numpy==1.17.4
opencv-python-headless==4.2.0.34
joblib==0.14.0
albumentations==0.4.5
scikit-image==0.17.2
tqdm==4.46.0
tensorboard==2.1.1
fire==0.3.1

Perhaps the newer torch version is acting up?

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

7 participants