Closed pat-s closed 1 year ago
Based on tests it was the same. This shouldn't be a big problem. I'll fix it.
@rvalavi Just checking in, were you able to do some tests already? Or can you give a rough outline when you might be able to take a look?
@pat-s sorry, caught again in a busy time. I'll fix it this week.
It seems to be in the way set.seed
is internally implemented. Last time I checked with the latest update of the code and it was ok, but it seems that code was already updated. I'm checking to see how I can make them identical.
@pat-s after a few attempts the results finally match. It was not a difficult problem but tricky to find. I also increased the iteration
default to 100 to match the v2.1.4
If all is good I go ahead and make an update to CRAN.
Thanks! I was just about to check but seems #37 needs to be resolved first. It looks like a valid error to me on the first look but I might be wrong.
Hi Roozbeh,
I've taken another look and my tests show indeed reproducibility with v2! I haven't checked all subfunctions yet (Only spatialBlock and spatialEnv) but I think it's good now :) Otherwise I'll comment here again but I think you can go ahead WRT to a new release.
Thanks again for your patience and understanding!
Hi Patrick,
I'm glad that the new version worked. I'm always up for promoting reproducibility. Thanks again for checking and reporting issues.
(sorry for opening another issue but I can't reopen the old one)
@rvalavi I've done some testing on my side and atm I think there is no reproducibility between v2 and v3 yet. I've created the below reprex to showcase it.
Also I see in the release notes of 3.1.1 that
spatialBlock()
usescv_spatial()
now internally. This sounds like it uses the new version in it's core and only wraps it - and is not actually executing the function in the way it was done in v2.1.4? Arguably, this is even more troublesome for users as they might assume thatspatialBlock()
yields the "old" results still while in fact it doesn't and instead "only" wrapscv_spatial()
and does something else.The reprex below sets
seed = 42
andhexagon=FALSE
which are two defaults that have changed in the new version but were not specifically highlighted in the changelog. But even with these I am unable to reproduce the old indices.Am I doing something wrong? How can I reproduce the v2 results using the toy SF data in the reprex?
Created on 2023-04-13 with reprex v2.0.2