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

about segfix #79

Open
wangdefour opened this issue Sep 16, 2021 · 3 comments
Open

about segfix #79

wangdefour opened this issue Sep 16, 2021 · 3 comments

Comments

@wangdefour
Copy link

Hi,Do you have instructions for segfix?

@hsfzxjy
Copy link
Contributor

hsfzxjy commented Sep 16, 2021

@wangdefour
Copy link
Author

@hsfzxjy Hello, I have some questions.
I run segfix directly using the "offset_semantic. Zip" file. I found that my label must have a corresponding file in "offset_semantic. Zip", as shown in line 83 of segfix.py:

def get_ offset(basename):
return io.loadmat(osp.join(offset_dir, basename + '.mat'))['mat'].astype(np.float32).transpose(2, 0, 1) * args.scale

If I want to generate an offset file, I must use the cityscapes format. My data is [0, 255]
Does this mean that I need to retrain the offset model?

@I3aer
Copy link

I3aer commented Feb 21, 2022

Segfix corrects minor errors on the boundary as long as the segmentation is reliable for other pixel locations. Therefore, in my view, it is a useless network. The most important issue is how well your segmentation network is generalized. Most segmentation datasets are small and probably large networks like OCR memorize the noise in datasets instead of learning. Instead of Segfix use an active contour segmentation or CRF.

Edit: Grammar

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

3 participants