Skip to content
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

pbdb_temp_range and pbdb_richness on data downloaded through web interface #28

Closed
EmiliaJarochowska opened this issue Apr 4, 2016 · 2 comments

Comments

@EmiliaJarochowska
Copy link

Hi, and hope this is the right place to ask this question. First, many thanks for this package. It is really a great tool. But I seem to have a silly problem using the pbdb_temp_range() and pbdb_richness() with data downloaded through the PBDB interface (and I do need to use that). I get the following error:

Error in colnames(temporal_range) <- c("max", "min") : object 'temporal_range' not found

Even though I specified the temporal extent. Am I doing something wrong, or perhaps there is a simple way to fix it?

Many thanks!
Emilia

@SaraVarela
Copy link
Contributor

Hi Emilia,
sorry for the late reply. I was on maternity leave :-)
I think that the problem that you had should be related with the names of the variables that you are downloading from the PBDB interface. in the API they might have different names and for that reason our function doesnt work. You can check the names of our variables downloading a short example using our package, and then, change the names of your variables to be exactly the same before using pbdb_temp_range().
We are now uploading a new version of the package to the cran, so please, load it from github

install.packages("devtools")
library(devtools)
install_github("ropensci/paleobioDB")
library(paleobioDB)

I hope that this works,
best regards,
Sara

@javigzz
Copy link
Contributor

javigzz commented Feb 23, 2019

Closing since it is related to passing unexpected data to the function. In upcoming merge I am improving the error messages thrown by that function should this happen again.

@javigzz javigzz closed this as completed Feb 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants