Dear all, now I meet a problem of running AMWG diagnose package. I have three years climate data. I run diag.csh , when running to COMPUTING MONTHLY CLIMOS FOR test, it is not work. It only create two monthly_wgt files: CAMwgt_Month.01.nc and CAMwgt_Month.02.nc(if it success,may be there are 12 CAMwgt_Month.nc),Now I don not know whether the half-baked wgt_Month.nc lead to COMPUTING MONTHLY CLIMOS FOR test failed. I don not have ways to check where is wrong? Hope you can give my a view. Thanks! Best wish for you!
the problem of AMWG diagnose package
- Thread starter xt2021
- Start date
Hi XuTing,
Apologies for the slow response! I assume that when you say you have three years of climate data that you have at least 12
Thanks, and have a great day!
Jesse
Apologies for the slow response! I assume that when you say you have three years of climate data that you have at least 12
*.cam.h0.* files for each year in the test case, one for each month? If so then can you attach your modified diag.csh file here? That could help us determine if anything is amiss, at least when it comes to the top-level script.Thanks, and have a great day!
Jesse
Hi Jesse,Thank you for your reply! Here is my diag.csh script. I modify the script according to the example of the user modify section. I running diag.csh to COMPUTING CASE ANNUAL AVERAGES FOR test , it remiand me" files:the subscript out of range", and then come a error GRIST_ANN_climo.nc NOT FOUND. I do not know where is wrong. Hopeyou can give me a idea! Thanks! I wish you have a good day!
Hi Xu Ting,
Based off the errors you received and your shell script my guess is that you are missing some monthly files needed to generate a complete annual climatology. I would recommend going through your files and making sure you have all twelve months for each year, and that they all have the file name format of "GRIST.year-month.nc", where "year" should look like 0001, 0002, 0003, etc. while "month" should look like 01, 02, 03, ..., 11, 12. You can also try reducing
Anyways, I hope that helps, and good luck!
Jesse
Based off the errors you received and your shell script my guess is that you are missing some monthly files needed to generate a complete annual climatology. I would recommend going through your files and making sure you have all twelve months for each year, and that they all have the file name format of "GRIST.year-month.nc", where "year" should look like 0001, 0002, 0003, etc. while "month" should look like 01, 02, 03, ..., 11, 12. You can also try reducing
test_nyrs in your csh script to see if that works, or you can take a screenshot of the directory listings if you would like us to take a look as well.Anyways, I hope that helps, and good luck!
Jesse
Hello Jesse, Thanks for your reply! According to your advice I check my data,and I find my data is complete. And I try to reduce nyrs=1 in my script it does't work. here is my script running log. Would you like to help me see where is the problem?
Hi Xu Ting,
Thanks for the diagnostics log! I think I better understand the error now (and I agree that your input files look fine).
Can you try a diagnostics run, but with
If the script still doesn't work when turning off monthly weighting then can you tell me what happens when you type:
If either of those commands return nothing then it means you are missing a required NCO command. Otherwise, can you attach the following script so I can examine it:
Thanks, and have a good weekend!
Jesse
Thanks for the diagnostics log! I think I better understand the error now (and I agree that your input files look fine).
Can you try a diagnostics run, but with
weight_months set to one (1)? If that works, then can you tell me what happens when you type:
Code:
which ncflintIf the script still doesn't work when turning off monthly weighting then can you tell me what happens when you type:
Code:
which nceaIf either of those commands return nothing then it means you are missing a required NCO command. Otherwise, can you attach the following script so I can examine it:
Thanks, and have a good weekend!
Jesse
Jesse,Thanks for your reply! I am sorry to bother you many times! After your reply, I set weight_momths=1, it can create ANN_climo.nc,MAM_climo.nc,JJA_climo.nc,SON_climo.nc,but it can't create DJF_climo.nc. Here is my log file(weight_months=1) and the screenshot of my dirctory of climo.And my compute_climo.csh script(After downloading it Idon't have any modify for it). I also check my ncflint and ncea, they are complete. I'm so sorry to bother you so many times！Thanks,and have a nice day!
Attachments
Jesse,Thanks for your reply! I am sorry to bother you many times! After your reply, I set weight_momths=1, it can create ANN_climo.nc,MAM_climo.nc,JJA_climo.nc,SON_climo.nc,but it can't create DJF_climo.nc. Here is my log file(weight_months=1) and the screenshot of my dirctory of climo.And my compute_climo.csh script(After downloading it Idon't have any modify for it). I also check my ncflint and ncea, they are complete. I'm so sorry to bother you so many times！Thanks,and have a nice day!
Attachments
Hello,Jesse!Thanks for your reply! I am sorry to bother you many times! After your reply, I set weight_momths=1, it can create ANN_climo.nc,MAM_climo.nc,JJA_climo.nc,SON_climo.nc,but it can't create DJF_climo.nc. Here is my log file(weight_months=1) and the screenshot of my dirctory of climo.And my compute_climo.csh script(After downloading it Idon't have any modify for it). I also check my ncflint and ncea, they are complete. I'm so sorry to bother you so many times！Thanks,and have a nice day!
Attachments
Hi Xu Ting,
It looks like the reason the DJF climo failed is because you are missing the
I might recommend setting
Finally, I also noticed that you are running as the "root" user, but in general that is dangerous to do, and can sometimes result in unexpected behavior. So I might also recommend trying to run this application as a "regular" user to see if you get different results.
Hope that helps, and good luck with the tests!
Jesse
It looks like the reason the DJF climo failed is because you are missing the
GRIST_*_climo_next.nc files needed to calculate the DJF averages (which should have automatically been calculated by the script earlier). I might recommend setting
strip_off_vars to one (1) to see if that helps. Otherwise it seems that your code is just randomly skipping certain sections of the shell script, which makes me concerned that there is an environment or system-level problem. Can you access the data using a different machine? If so then I might try the diagnostics on that other system to see if you get a different result. Finally, I also noticed that you are running as the "root" user, but in general that is dangerous to do, and can sometimes result in unexpected behavior. So I might also recommend trying to run this application as a "regular" user to see if you get different results.
Hope that helps, and good luck with the tests!
Jesse
Hello Jesse,
Thank for your reply! I try to set strip_off_vars=1 but it can't create DJF_climo.nc. As you saying I missing GRIST_*_climo_next.nc.what can I do to fix this problem? The problem of environment or system-level, I will check it.Besides environment or system_level problem , Are there other reasons for this problem? Thanks for your relpy, and wish you have a nice day! Thanks!
Hi Xu Ting,
Sadly there are no other obvious reasons for this problem, as the failing script is pretty simple, and seems to be failing in a semi-random location. So at this point I would suggest trying to run the script as a non-root user, and if that doesn't work then try running it on a different system (as the script certainly works on our systems, and as you mentioned before you didn't modify the script itself at all).
Of course if you run into a different error when running with a new system or environment then please feel free to let us know, as we at least might be able to help you with that new issue.
Thanks, and good luck trying out a new system and/or environment!
Jesse
Sadly there are no other obvious reasons for this problem, as the failing script is pretty simple, and seems to be failing in a semi-random location. So at this point I would suggest trying to run the script as a non-root user, and if that doesn't work then try running it on a different system (as the script certainly works on our systems, and as you mentioned before you didn't modify the script itself at all).
Of course if you run into a different error when running with a new system or environment then please feel free to let us know, as we at least might be able to help you with that new issue.
Thanks, and good luck trying out a new system and/or environment!
Jesse