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

Problem with jplMURSST41, undetailed error #96

Closed
LuisLauM opened this issue Mar 3, 2021 · 4 comments
Closed

Problem with jplMURSST41, undetailed error #96

LuisLauM opened this issue Mar 3, 2021 · 4 comments

Comments

@LuisLauM
Copy link

LuisLauM commented Mar 3, 2021

When I try to use the griddap function with a specific source (MUR), it just returns the word ERROR, without any detail. It also happens with other sources, but after a while it works. I have tested from different PC and different networks.

varID <- "jplMURSST41"

info(datasetid = varID)

griddap(x = varID,
        time = c("2010-01-01", "2010-01-31"),
        latitude = c(-25, 10),
        longitude = c(-100, -70),
        fields = "analysed_sst",
        read = FALSE)
Session Info
 setting  value                       
 version  R version 4.0.4 (2021-02-15)
 os       Windows 10 x64              
 system   x86_64, mingw32             
 ui       RStudio                     
 language (EN)                        
 collate  Spanish_Peru.1252           
 ctype    Spanish_Peru.1252           
 tz       America/Bogota              
 date     2021-03-03  
@sckott
Copy link
Contributor

sckott commented Mar 3, 2021

Thanks, but that is not your R session info. Please share your R session info, output of sessioninfo::session_info()

@LuisLauM
Copy link
Author

LuisLauM commented Mar 3, 2021

My mistake, yes. I have edited my first post.

@sckott
Copy link
Contributor

sckott commented Mar 3, 2021

Should be fixed now. First, see cache_info()$path, go to that path and delete all files in there so that the next griddap request doesn't use the cached file.

Then try again and you should get a useful error message. Let me know what happens

@LuisLauM
Copy link
Author

LuisLauM commented Mar 4, 2021

Should be fixed now. First, see cache_info()$path, go to that path and delete all files in there so that the next griddap request doesn't use the cached file.

Then try again and you should get a useful error message. Let me know what happens

Yes, it is working properly now. Thank you.

@LuisLauM LuisLauM closed this as completed Mar 4, 2021
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

2 participants