Change History
Discuss your script development with others (bugs, optimizations, methods ...)
Message: Re: My trail / Cache chain
Changed By: magma1447
Change Date: February 04, 2018 10:59PM
Re: My trail / Cache chain
Would you find it reasonable, or would you say that it might be a bug, that the following tag runs in 4 seconds:
{ "unit": "km", "unitsize": 1000, "separation": 3, "required": 1000, "displayed": 1000, "property": "area", "polygon": "concave" }
But the following doesn't finish in 60 seconds?
{ "unit": "km", "unitsize": 1000, "separation": 2, "required": 1000, "displayed": 1000, "property": "area", "polygon": "concave" }
The above was tested several times on my own username.
Since I was curious if it was a scaling issue I wanted to test with 2.5 km and so on. I then realized that I actually can.
The following tag runs in 4 seconds as well:
{ "unit": "m", "unitsize": 1, "separation": 2400, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
And this one doesn't complete in 60 seconds:
{ "unit": "m", "unitsize": 1, "separation": 2380, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
This however completed in 42 seconds:
{ "unit": "m", "unitsize": 1, "separation": 2390, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
Further separation:2389 doesn't complete, while 2391 finishes in 4 seconds.
It's hard to make an assumption in my opinion. It all ends up with 2389 doesn't work, 2390 is slow, 2391+ is fast. It's an extreme difference for a very small distance difference. My impulsive guess is that it wouldn't be a bug, but I have a hard time to realize why it would be such huge difference in processing.
EDIT: Realized now that I could use floats for separation and didn't need to change unit size so that it became unreadable. :)
Original Message
Author: magma1447
Date: February 04, 2018 10:55PM
Re: My trail / Cache chain
Would you find it reasonable, or would you say that it might be a bug, that the following tag runs in 4 seconds:
{ "unit": "km", "unitsize": 1000, "separation": 3, "required": 1000, "displayed": 1000, "property": "area", "polygon": "concave" }
But the following doesn't finish in 60 seconds?
{ "unit": "km", "unitsize": 1000, "separation": 2, "required": 1000, "displayed": 1000, "property": "area", "polygon": "concave" }
The above was tested several times on my own username.
Since I was curious if it was a scaling issue I wanted to test with 2.5 km and so on. I then realized that I actually can.
The following tag runs in 4 seconds as well:
{ "unit": "m", "unitsize": 1, "separation": 2400, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
And this one doesn't complete in 60 seconds:
{ "unit": "m", "unitsize": 1, "separation": 2380, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
This however completed in 42 seconds:
{ "unit": "m", "unitsize": 1, "separation": 2390, "required": 1000000000, "displayed": 1000000000, "property": "area", "polygon": "concave" }
Further separation:2389 doesn't complete, while 2391 finishes in 4 seconds.
It's hard to make an assumption in my opinion. It all ends up with 2389 doesn't work, 2390 is slow, 2391+ is fast. It's an extreme difference for a very small distance difference. My impulsive guess is that it wouldn't be a bug, but I have a hard time to realize why it would be such huge difference in processing.