Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Question on default POP2 diagnostic on Yellowstone

S

shineng_hu@gmail_com

New Member
Hi,I am now trying to run CESM POP2 diagnostic package on Yellowstone, but it failed to find the model output. I have already modified CASE, MSROOT, etc. Could anyone help look at the script and output (attached) to see what is the problem?Thanks a lot!Shineng
 
N

njn01

Member
It looks to me as if the problem arises from the link you have in your home directory, where you basically redefine your scratch directory location.  I think if you change the line in the popdiagdiff.csh script from     setenv WORKDIR /glade/scratch/.....to    setenv WORKDIR /glade/u/home/shinengh/scratch/your script will have a better chance of working.Be careful, though: make sure that you have back-up copies of all of your original pop2 output data (the $CASE.pop.h*" files) stored somewhere else before you begin processing with the pop2 diagnostics scripts, because there are some versions that assume that these files can be removed after processing -- and do!
 
N

njn01

Member
It looks to me as if the problem arises from the link you have in your home directory, where you basically redefine your scratch directory location.  I think if you change the line in the popdiagdiff.csh script from     setenv WORKDIR /glade/scratch/.....to    setenv WORKDIR /glade/u/home/shinengh/scratch/your script will have a better chance of working.Be careful, though: make sure that you have back-up copies of all of your original pop2 output data (the $CASE.pop.h*" files) stored somewhere else before you begin processing with the pop2 diagnostics scripts, because there are some versions that assume that these files can be removed after processing -- and do!
 
N

njn01

Member
It looks to me as if the problem arises from the link you have in your home directory, where you basically redefine your scratch directory location.  I think if you change the line in the popdiagdiff.csh script from     setenv WORKDIR /glade/scratch/.....to    setenv WORKDIR /glade/u/home/shinengh/scratch/your script will have a better chance of working.Be careful, though: make sure that you have back-up copies of all of your original pop2 output data (the $CASE.pop.h*" files) stored somewhere else before you begin processing with the pop2 diagnostics scripts, because there are some versions that assume that these files can be removed after processing -- and do!
 
N

njn01

Member
Also, do not run the diagnostics on the yellowstone login nodes.  Instead, use caldera.  If you are unfamiliar with caldera, please see the CISL documentation.
 
N

njn01

Member
Also, do not run the diagnostics on the yellowstone login nodes.  Instead, use caldera.  If you are unfamiliar with caldera, please see the CISL documentation.
 
N

njn01

Member
Also, do not run the diagnostics on the yellowstone login nodes.  Instead, use caldera.  If you are unfamiliar with caldera, please see the CISL documentation.
 
S

santos

Member
Since this is a run-time abort in POP, I've moved this post to the software and run-time issues section.
 
S

santos

Member
Since this is a run-time abort in POP, I've moved this post to the software and run-time issues section.
 
S

santos

Member
Oops, actually, it looks like the last post above was just unrelated to the original topic.Adv, when you run into a new issue, rather than commenting on an existing post, please create a new post. In this case, you should create a new post by going to this link and hitting the "New topic" button at the top of the page:https://bb.cgd.ucar.edu/forums/software-and-run-time-issues-2
 
S

santos

Member
Oops, actually, it looks like the last post above was just unrelated to the original topic.Adv, when you run into a new issue, rather than commenting on an existing post, please create a new post. In this case, you should create a new post by going to this link and hitting the "New topic" button at the top of the page:https://bb.cgd.ucar.edu/forums/software-and-run-time-issues-2
 
S

santos

Member
Oops, actually, it looks like the last post above was just unrelated to the original topic.Adv, when you run into a new issue, rather than commenting on an existing post, please create a new post. In this case, you should create a new post by going to this link and hitting the "New topic" button at the top of the page:https://bb.cgd.ucar.edu/forums/software-and-run-time-issues-2
 
You must log in or register to reply here.
Top