You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each grid resolution, I am currently creating a separate file from BedMachine by using gdal's averaging method. This results in a large amount of input files, often duplicated across projects.
gdal's averaging method is very fast, and I'm thus wondering if we could implement a similar approach to regrid spatial fields (basically bedrock and ice thickness).
If memory serves me well, we once had a python script that could do averaging but I cannot find it anymore.
Ideally, PISM should be able to bootstrap from BedMachine directly, with some limitations. This would also facilitate cloud computing.
The text was updated successfully, but these errors were encountered:
For each grid resolution, I am currently creating a separate file from BedMachine by using
gdal
's averaging method. This results in a large amount of input files, often duplicated across projects.gdal
's averaging method is very fast, and I'm thus wondering if we could implement a similar approach to regrid spatial fields (basically bedrock and ice thickness).If memory serves me well, we once had a python script that could do averaging but I cannot find it anymore.
Ideally, PISM should be able to
bootstrap
fromBedMachine
directly, with some limitations. This would also facilitate cloud computing.The text was updated successfully, but these errors were encountered: