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

RCP 6.0 Period 2050 #2

Open
fabiolexcastro opened this issue Jul 3, 2019 · 3 comments
Open

RCP 6.0 Period 2050 #2

fabiolexcastro opened this issue Jul 3, 2019 · 3 comments

Comments

@fabiolexcastro
Copy link

fabiolexcastro commented Jul 3, 2019

There is a problem when I want to use the period 2050, it make appear 0 GCMs to make the analysis, but when I choose 2070 it works.

Thanks for any solution for this.

Best regards,
Fabio Castro
Palmira / Colombia

@javierfajnolla
Copy link
Collaborator

Hi Fabio, and thanks for the feedback!

You are absolutely right. As you noticed, layers for the year 2050 are currently not available for use due to some difficulties with storage. We will upload these layers as soon as possible, and tweak the user interface meanwhile so this option is not displayed until layers are available.
I am sorry for any inconvenience that this may cause you. I hope that, meanwhile, results for 2070 are also interesting for your interest while we upload all layers...

Regards,
Javier

@fabiolexcastro
Copy link
Author

Hello Javier,

Thanks for the reply. I understand what you mean, the shinny app has a limitation about the ram, we only can access to 1 gb (free version) or 8 gb (standard versión o higher), and the data for climate change it's very big, although we work with a resolution of 5 minutes or 10 minutes.

Anyway, I'm very gratefull with the app, it's very useful when we work with climate change data.

Best regards from CIAT - Palmira
Fabio Castro

@javierfajnolla
Copy link
Collaborator

In this case it is not so much about the RAM, but about the storage...
GCM compareR is shared through an RStudio Server instance installed in a server, instead of using shinnyapps.io directly. This is precisely for the reason that you said, shinnyapps.io would limit the amount of RAM available. And the app analyses, which need to load many raster layers at the same time, need a lot of RAM...

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