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

BUG: temporary remapping files are not cleaned immediately after use. #75

Open
jhamman opened this issue Oct 29, 2015 · 2 comments
Open
Assignees
Labels

Comments

@jhamman
Copy link
Member

jhamman commented Oct 29, 2015

I've been using the RVIC parameters generation tool to generate parameters on a 10km grid in the Arctic. The temporary remap files are pretty large (16GB each) and are not being cleaned fast enough to save enough disk space for the next file to be able to fit on the disk (200 GB in total).

For large domains with many outlets, we may need to rethink the workflow when using REMAP=TRUE and multiprocessing. For now, the work around seems that we need to use less processors so the total temporary file load remains less than the disk space.

@jhamman jhamman added the bug label Oct 29, 2015
@jhamman jhamman self-assigned this Oct 29, 2015
@lizaclark
Copy link
Contributor

I'm using cdo v. 1.7.1rc1 for my command line cdo, and I find that when I run cdo remapcon,file1.nc file2.nc, I get *** Error in cdo: malloc(): memory corruption: 0x0000000002e5f6d0 ***; however, if I use a grid file, I am able to get remapcon to finish. That workflow looks like:

cdo griddes file1.nc > gridfile
cdo remapcon,gridfile file2.nc

Perhaps adding an intermediate griddes step would allow RVIC to work on the temporary remap files.

@bartnijssen
Copy link
Member

Is that a known bug in newer versions of cdo? May be good to file a bug report with them as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants