-
Notifications
You must be signed in to change notification settings - Fork 10
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
k.read.base doesn't work with vector data in R v3.5.0 #129
Comments
Thanks @nrlottig. I confirm this is an issue in R v3.5 and not in R v3.4 |
Apologies for my terrible 2012 R coding |
@nrlottig could you please test and confirm the fix. To test, install from my fork install.packages('devtools')
devtools::install_github('lawinslow/LakeMetabolizer') Please let us know if that solved the v3.5 issue! |
@lawinslow it runs as expected now on my mac with v3.5. Do you want us to run this version of LakeMetab as we process stuff to see if we find anything else. We can always keep one computer downgraded to 3.4 to check. |
Yup, go for it. If you find more bugs post them here. |
Luke's update works, just needs to be pulled into the parent repo. |
Hi, It only worked if I compute inside a loop on the temporal dimension, timestep after timestep. However, this issue persists for |
Hi @camilleminaudo , We'll get up the newest version on CRAN soon. Let us know if there are any existing issues. |
These fixes solved all my issues, thanks! |
I've been working on training up an undergrad to work on processing LTER metabolism data. I had her go through the workshop materials @hdugan provided at GLEON a couple of years ago. When trying to use k.read.base, she got an error about coercing to dbl. I tried the code on my mac and it ran fine with R v3.4.4. I upgraded to 3.5.0 and it kicked back the same error, downgraded and it ran fine. Downgrade the PC to v3.4.4 and it ran fine. Here is a link to our saved workspace and the script. Line 76 is the call to k.read.base that fails in v.3.5.0
https://www.dropbox.com/sh/xh2xhp5uh8cpztd/AAB6hRzYJ-F4I3PNn7fqVevla?dl=0
The text was updated successfully, but these errors were encountered: