-
Notifications
You must be signed in to change notification settings - Fork 20
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
Edge case process is, actually, completely broken #64
Comments
@Ckster are you considering working on this issue at all, once the low-hanging fruit bugs are tackled? I'm also starting to look into seeing if I can find someone here to work on it, since we might be able to use work study to get someone from CSU. @EllieLindrooth got started on it and I think she was close to figuring it out, so there might be a branch that has it half done somewhere on this repo. |
Hey @admahood sorry did not see this until now. Yes I will be trying to solve this as I work on the 2.0.0 branch |
@admahood do you remember what you ran for this? I.e., can we try to reproduce it to work on it? At least which tile that is? |
It's Queensland, Australia, FID == 59228 (That info is actually also in the screenshot). It was in 2004, so it might be easier to process only that year to reproduce the error and do checks. Australia has a LOT of fires so it takes a long time. It might be worth it to explore other, smaller countries that fall along a lot of tile intersections and see if you can find edge-related errors there, so you don’t have to do such a resource intensive operation to reproduce errors. |
file:///home/a/Desktop/edge_case_process_is_completely_broken.png
Check out this figure... this is supposed to be spatial parameter of 1, and a temporal parameter of 2. Whatever that edge case process is doing is not working.
The text was updated successfully, but these errors were encountered: