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

hello, how to add changemixin when use bitemporal supervised #8

Closed
csliuchang opened this issue Oct 25, 2021 · 3 comments
Closed

hello, how to add changemixin when use bitemporal supervised #8

csliuchang opened this issue Oct 25, 2021 · 3 comments

Comments

@csliuchang
Copy link

hello I have question about your repo:

  1. how to add changeminxin when use bitemporal supervised, i see it in your paper table 4 but i cant find in codes?
  2. could changestar use LEVIR-CD train Single-Temporal(another dataset is too big for train, i cant download it)
  3. are your bitemporal suprvised methods just use torch.cat in the final layer?
    sorry for ask these question,
@Z-Zheng
Copy link
Owner

Z-Zheng commented Oct 26, 2021

  1. see here https://github.com/Z-Zheng/ChangeStar/blob/master/module/changestar_bisup.py
  2. No, because there is no building label provided in LEVIR-CD. Maybe you can choose a small building segmentation dataset to try. But small dataset is difficult to guarantee the final performance under single-temporal supervision.
  3. Bitemporal model simplifies the temporal swap module and uses torch.cat + many convs, not only the torch.cat.

@Z-Zheng Z-Zheng closed this as completed Oct 26, 2021
@csliuchang
Copy link
Author

THANKS BRO

@csliuchang
Copy link
Author

i use the bitemporal suprvised methods for Industrial application,but i found the operation torch.cat may lost some small changes(this change is so important) of information that don't have obvious semantic features. so ask third question, dont mind, thanks again.

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

2 participants