Repository navigation
Conversation
|
Thanks, looks great! I think it's ok to leave CUDA out, not sure if GIS+GPU is a common thing (honestly don't know -- @jelletreep)? |
1 similar comment
|
Thanks, looks great! I think it's ok to leave CUDA out, not sure if GIS+GPU is a common thing (honestly don't know -- @jelletreep)? |
|
In general, GPU is used in combination with GIS datasets for faster rendering, however jupyterGIS doesn't seem to support GPU. However it might be useful if someone would use e.g. pytorch in combination with jupyterGIS in a workflow? |
|
So we do want GPU option for this workspace? Do I need to change anything to the component? |
|
Yes, we could add a version of the Catalog Item with GPU (we keep GPU and non-GPU in separate catalog items), and add it to the "Utrecht University GPU" Catalog Item collection -- then the docs could be updated to reflect that a GPU flavour is availalbe (as also for other catalog items in the docs, e.g. VRE Lab). |
Did that! Created a GPU catalog item, updated the other one, mentioned the GPU catalog item in the docs. |
Closes #153
@dometto, not sure if I put the correct things in the table. For example, workspace_cuda, do I need to change this to JupyterGIS GPU? Or do I leave CUDA out?