-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Failure with the new version of **blockCV** #221
Comments
Thanks for the info. Any idea why numbers change with the new update? Does the updated code apply a different sorting of the results? I think it would be easiest if the sorting of the result would stay as before to avoid having to push an update just because of this. |
@pat-s yeah of course! Could you provide me with your example data so I can diagnose it? |
The data should not matter for this in my view. You can see what is being done starting here: https://github.com/mlr-org/mlr3spatiotempcv/blob/main/R/ResamplingSpCVBuffer.R#L119. The values going into the test can be found here: https://github.com/mlr-org/mlr3spatiotempcv/blob/main/tests/testthat/test-ResamplingSpCVBuffer.R#L57. |
@pat-s I checked and here are a few notes: |
fixed in #222 |
Hi,
I've updated
blockCV
with a major version. Although all function names have changed to more general names/arguments, the old functions should still work fine. While reverse dependency checking I got a failure withmlr3spatiotempcv
as shown below; could you please check and see if this response is expected? it seems the only issue is the numbers are switched!You can check the new update in blockCV's repo.
`* Source code: https://github.com/cran/mlr3spatiotempcv
Run
revdepcheck::revdep_details(, "mlr3spatiotempcv")
for more infoNewly broken
The text was updated successfully, but these errors were encountered: