Hide minor edits - Show changes to markup
~/DUMP2HOLD/um/$jobid/code/exec_build/qxrecon_dump_dir/control1.f
(lines near 5760) as blow;
quest:~/DUMP2HOLD/um/$jobid/code/exec_build/qxrecon_dump_dir/control1.f
(lines near 5760) as blow;
If started from atmospheric and oceanic reconfigurations 1&2 should already be set correctly.
2.T. trouble shooting in ocean reconfiguration
!!!1.T. trouble shooting
1.T. trouble shooting
!!!1.T. trouble shooting
So basically what you can do is use the latest atmospheric and ocean dumps as initial dumps and reconfigure and run again;
So basically what you can do is use the latest atmospheric and ocean dumps as initial dumps, reconfigure, and run again;
Robin says: Often this means that something in the boundary conditions has pushed the climate past the model’s capability - either too hot, or too cold somewhere. Carefully check the model output fields and look for things that are out of place. Sometimes, however, this seems to happen in FAMOUS with perfectly normal climates - we’ve never worked out why.
Robin says: (If there is nothing wrong in the climate,) make a small perturbation to the climate and restart, and it’ll run fine. The easiest way to do this is to reconfigure the atmosphere dump (this adjusts some of the coastal tiling fields), although sometimes I change the date on the previous year’s ocean dump (again, by reconfiguring) and use that to restart.
Robin says: In this case, if you make a small perturbation to the climate and restart it’ll run fine. The easiest way to do this is to reconfigure the atmosphere dump (this adjusts some of the coastal tiling fields), although sometimes I change the date on the previous year’s ocean dump (again, by reconfiguring) and use that to restart.
Robin says: (If there is nothing wrong in the climate,) make a small perturbation to the climate and restart, and it’ll run fine. The easiest way to do this is to reconfigure the atmosphere dump (this adjusts some of the coastal tiling fields), although sometimes I change the date on the previous year’s ocean dump (again, by reconfiguring) and use that to restart.
In the previous versions of FAMOUS, this problem can be overcome simply by resubmitting the job. However, this version is bit-reproducing, so simply resubmitting will result in exactly the same error.
In the previous versions of FAMOUS, this problem can be overcome simply by resubmitting the job. However, this version is bit-reproducing, so simply resubmitting the job will result in exactly the same error.
(2) Run stopped after tens of years of simulation time
As always look in the output file ([jobid]000.o1234 or [jobid]***.leave). I got the following message;
Model aborted with error code - 1 Routine and message:- P_TH_ADJ : NEGATIVE PRESSURE VALUE CREATED.
This is a common error and I have had it many times. It seems the simulated climate went unstable and the simulation died.
Robin says: Often this means that something in the boundary conditions has pushed the climate past the model’s capability - either too hot, or too cold somewhere. Carefully check the model output fields and look for things that are out of place. Sometimes, however, this seems to happen in FAMOUS with perfectly normal climates - we’ve never worked out why.
In the previous versions of FAMOUS, this problem can be overcome simply by resubmitting the job. However, this version is bit-reproducing, so simply resubmitting will result in exactly the same error.
Robin says: In this case, if you make a small perturbation to the climate and restart it’ll run fine. The easiest way to do this is to reconfigure the atmosphere dump (this adjusts some of the coastal tiling fields), although sometimes I change the date on the previous year’s ocean dump (again, by reconfiguring) and use that to restart.
So basically what you can do is use the latest atmospheric and ocean dumps as initial dumps and reconfigure and run again;
By now I have heard of a few ways to submit a continuation run.
I have heard of a few ways to submit a continuation run.
clustersubmit
is said to be preferable. It generally has more control and the advantage in this particular case is that you can skip step 4.6.
clustersubmit
is said to be preferable. It generally has more control and the advantage in this particular case is that you can skip step 4.9.
4.3. UMUI: [submodel indep]-[Gen config control]
4.3. (same as 3.3) UMUI: [submodel indep]-[Gen config control]
4.4. UMUI: [Atmos]-[Ancil+input]-[start dump]
4.4. (same as 3.4) UMUI: [Atmos]-[Ancil+input]-[start dump]
4.5. UMUI: [Ocean]-[input files]-[start dump]
4.5. (same as 3.5) UMUI: [Ocean]-[input files]-[start dump]
4.3. UMUI: press <save> and then <process>
4.4. manually post process on puma if necessary (see 1.8)
4.5. Submit
4.3. UMUI: [submodel indep]-[Gen config control]
4.4. UMUI: [Atmos]-[Ancil+input]-[start dump]
4.5. UMUI: [Ocean]-[input files]-[start dump]
4.6. UMUI: press <save> and then <process>
4.7. manually post process on puma if necessary (see 1.8)
4.8. Submit
4.6. Run
4.9. Run
4.7. check the status of the run on quest
4.10. check the status of the run on quest
\\
\\
\\
\\
\\
\\
\\
\\
puma; clustersubmit -c y -s y -r quest $jobid
puma; clustersubmit -c y -s y -r quest $jobid
clustersubmit
clustersubmit
-c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
qsubmit.quest#
-c
is to specify whether this is a continuation run (y
) or not (n
). (-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.))
qsubmit.quest#
‘’(4) Add a post processing script
By now I have heard of three ways to submit a continuation run. Below shows one of them. Here are alternative ways.
By now I have heard of a few ways to submit a continuation run.
Do 5.1 and 5.2 if necessary.
5.3. modify qsubmit.quest#
Then do one of (1)~(4).
clustersubmit
puma; clustersubmit -c y -s y -r quest $jobid@]
-c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
qsubmit.quest#
5.3. modify qsubmit.quest#
Alternative ways to submit a continuation run \\
\\
~/umui_jobs/$jobid
, edit SUBMIT
as shown in 5.3 above and then run umsubmit
to copy the new scripts across. Then submit using qsub-um
on quest as 5.4.
‘’(3) Do the same thing but on puma.
~/umui_jobs/$jobid
, edit SUBMIT
as shown in 5.3 above and then run umsubmit
to copy the new scripts across. Then submit using qsub-um
on quest as 5.4.
‘’(4) Add a post processing script
puma; clustersubmit -c y -s y -r quest $jobid
-c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
clustersubmit
is said to be preferable. It generally has more control and the advantage in this run is that you can skip step 4.6.
clustersubmit
is said to be preferable. It generally has more control and the advantage in this particular case is that you can skip step 4.6.
If UMUI [SUBMIT] button is clicked or umsubmit
is used
umsubmit
is used, THAT WILL NOT START THE RUN, SO GO ON TO 4.6! If clustersubmit
is used, it should start the run so you can SKIP 4.6.
If clustersubmit
is used
clustersubmit
is preferable because you can skip the step 4.6. clustersubmit
also has more control.
clustersubmit
is said to be preferable. It generally has more control and the advantage in this run is that you can skip step 4.6.
clustersubmit
is preferable because you can skip the step 4.6. clustersubmit
also has more control.
umsubmit
is used, THAT WILL NOT START THE RUN, SO GO ON TO 4.6! If clustersubmit
is used, it should start the run so YOU CAN SKIP 4.6.
umsubmit
is used, THAT WILL NOT START THE RUN, SO GO ON TO 4.6! If clustersubmit
is used, it should start the run so you can SKIP 4.6.
umsubmit
is used, THAT WILL NOT START THE RUN, SO GO ON TO 4.6! If clustersubmit
is used, it should start the run so YOU CAN SKIP 4.6.
quest:$MY_DUMPS/$jobid.astart/
quest:$MY_DUMPS/
cp $jobid.astart $jobid.astart.ini
cp $jobid.astart $jobid.astart.ini
cp $jobid.astart $jobid.astart.ini
cp $jobid.astart $jobid.astart.ini
~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon
is newly created in the first run that crashes (LET IT CRASH AND DO THE TROUBLE SHOOTING (2) UNTIL WE FIND A BETTER WAY TO RUN!!!). This will not be created after going through the trouble shooting (2), or in other words, the one created manually in the trouble shooting should not be overwritten.
(in my case it is $MY_DUMPS/$jobid.astart = ~/um/dumps/$jobid.astart)
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
(in my case it is$MY_DUMPS/$jobid.astart = ~/um/dumps/$jobid.astart
)
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
/exports/gpfsbig/home/$USER/DUMP2HOLD/um/$jobid/dataw/
and rename it $jobid.recon
qxrecon_dump
to /exports/gpfsbig/home/$USER/DUMP2HOLD/um/$jobid/dataw/
and rename it $jobid.recon
if (ICODE.eq.1501) then write(6,*) ‘ Polar rows not constant in T*.’ & //’ This is probably not a problem.’ else
if (ICODE.eq.1501) then !!! write(6,*) ‘ Polar rows not constant in T*.’ !!! & //’ This is probably not a problem.’ !!! else !!!
end if
end if !!!
if (ICODE.eq.1501) then ‘’‘write(6,*) ‘ Polar rows not constant in T*.’ & //’ This is probably not a problem.’ ‘’‘ else
if (ICODE.eq.1501) then write(6,*) ‘ Polar rows not constant in T*.’ & //’ This is probably not a problem.’ else
end if
end if
if (ICODE.eq.1501) then
write(6,*) ‘ Polar rows not constant in T*.’
& //’ This is probably not a problem.’
if (ICODE.eq.1501) then ‘’‘write(6,*) ‘ Polar rows not constant in T*.’ & //’ This is probably not a problem.’ ‘’‘
end if
end if
if (ICODE.eq.1501) then
if (ICODE.eq.1501) then
% //’ This is probably not a problem.’
& //’ This is probably not a problem.’
end if
end if
if (ICODE.eq.1501) then write(6,*)”Polar rows not constant in T*” write(6,*)”This may, or may not, be a problem” else
if (ICODE.eq.1501) then
write(6,*) ‘ Polar rows not constant in T*.’ % //’ This is probably not a problem.’ else
end if
end if
puma; clustersubmit -c y -s y -r quest $jobid
Here the flag -c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
puma; clustersubmit -c y -s y -r quest $jobid
-c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
puma; clustersubmit -c y -s y -r quest $jobid
Here the flag -c
is to specify whether this is a continuation run (y
) or not (n
). [-s
is to specify whether to submit (y
) or copy files over (n
), and -r
is to specify the target machine (e.g. quest
, ormen
, etc.)]
UMUI: press [SUBMIT] OR puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
UMUI: press [SUBMIT] , puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid , OR puma; clustersubmit -c n -s y -r quest $jobid
UMUI: press [SUBMIT] OR puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
UMUI: press [SUBMIT] , puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid , OR puma; clustersubmit -c n -s y -r quest $jobid
UMUI: press [SUBMIT] OR
puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
UMUI: press [SUBMIT] , puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid , OR puma; clustersubmit -c n -s y -r quest $jobid
UMUI: press [SUBMIT] OR puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
UMUI: press [SUBMIT] , puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid , OR puma; clustersubmit -c n -s y -r quest $jobid
THIS DOES NOT START THE RUN. GO ON TO THE NEXT STEP!
!!!Contents
\\
\\
\\
\\
\\
!!!2. Reconfigure Ocean
!!!3. Compile
!!!4. Run
!!!5. Submit a continuation run
!!!1. Reconfigure Atmosphere
1.T. trouble shooting
1.T. trouble shooting
!!!0. set environmental constants
2.T. trouble shooting in ocean reconfiguration
!!!0. set environmental constants
!!!1. Reconfigure Atmosphere
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
(1) in my initial attempts, a $jobid.astart file was not created. .leave file looked as normal in terms of the size. However, looking in the .leave file revealed some problems. “Completion code” was 134 and I suppose anything other than 0 suggests an error. just above that there are lines like;
(1) in my initial attempts, a $jobid.astart file was not created. .leave file looked as normal in terms of the size. However, looking in the .leave file revealed some problems. “Completion code” was 134 and I suppose anything other than 0 suggests an error. just above that there are lines like;
(2) (1) is fixed and .astart file of larger size (2064384B and later found this is not quite the right size; the right size is 2080768B) is created, which looks ‘mostly’ alright, but .leave file still doesn’t seem quite happy;
(2) (1) is fixed and .astart file of larger size (2064384B and later found this is not quite the right size; the right size is 2080768B) is created, which looks ‘mostly’ alright, but .leave file still doesn’t seem quite happy;
(3) I was successful in the previous job but in the new job .astart file is not created. This seems a different problem from (1) or (2). .leave file says;
(3) I was successful in the previous job but in the new job .astart file is not created. This seems a different problem from (1) or (2). .leave file says;
!!!2. Reconfigure Ocean
(1) $jobid.ostart has only about 2.8MB and completion code in the .leave file is 134.
!!!3. Compile
!!!4. Run
4.T. trouble shooting in running the model
(1) Run stopped after couple tens of seconds. Near (not quite at) the end of the output (~/umui_runs/[jobid]−012345678/[jobid]000.o1234) said “LSEGF NOT LARGE ENOUGH.”
4.T. trouble shooting in running the model
(1) Run stopped after couple tens of seconds. Near (not quite at) the end of the output (~/umui_runs/[jobid]−012345678/[jobid]000.o1234) said “LSEGF NOT LARGE ENOUGH.”
!!!5. Submit a continuation run
This page is meant to be as foolproof as possible and so inevitably lengthy. Please understand that and don’t tell me to tidy it up.
This page is meant to be as foolproof as possible and so inevitably lengthy. Don’t tell me to tidy it up.
4.T. trouble shooting in ocean reconfiguration
4.T. trouble shooting in running the model
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
[If you had a different kind of trouble in atmospheric reconfiguration and resolved it, please add the information about it here (or anywhere else) and share it with other users.]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
[If you had a different kind of trouble in ocean reconfiguration and resolved it, please add the information about it here (or anywhere else) and share it with other users.]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
[If you had a different kind of trouble in running the model and resolved it, please add the information about it here (or anywhere else) and share it with other users.]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE (OR ANYWHERE ELSE) AND SHARE WITH OTHER USERS]
Robin says: This comes from the subroutine that sorts out some basic stuff for the fourier filtering of the high latitude lines. It looks like the relevant loop goes through the map line by line, looking for separate areas. The maximum number of areas allowed for this procedure is set in the UMUI - it was 6, but the map has one line that needs 7.
Robin says: This comes from the subroutine that sorts out some basic stuff for the fourier filtering of the high latitude lines. I know nothing about this, but it looks like the relevant loop goes through the map line by line, looking for separate areas. The maximum number of areas allowed for this procedure is set in the UMUI - it was 6, but the map has one line that needs 7.
In UMUI:[Ocean]-[Scientific Parameters]-[Fourier Filtering], change “Maximum number of start and end indices” to 7 or more. That allowed the model to run.
Robin says: This comes from the subroutine that sorts out some basic stuff for the fourier filtering of the high latitude lines. It looks like the relevant loop goes through the map line by line, looking for separate areas. The maximum number of areas allowed for this procedure is set in the UMUI - it was 6, but the map has one line that needs 7.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so. There is also some information in the NCAS-CMS website that might be worth looking at.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so.
There is also some information about resubmission in the NCAS-CMS website.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so. There is also some information in the NCAS-CMS websitethat might be worth looking at.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so. There is also some information in the NCAS-CMS website that might be worth looking at.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so. There is also some information in the NCAS-CMS website that might be worth looking at.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so. There is also some information in the NCAS-CMS website that might be worth looking at.
By now I have heard of three ways to submit a continuation run. Below shows one of them. Click here for alternative ways.
By now I have heard of three ways to submit a continuation run. Below shows one of them. Here are alternative ways.
There’s also a section on the NCAS-CMS website that might be worth looking at.
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT HERE AND SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN ATMOSPHERIC RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN OCEAN RECONFIGURATION AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
(1)
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
(1) Run stopped after couple tens of seconds. Near (not quite at) the end of the output (~/umui_runs/[jobid]−012345678/[jobid]000.o1234) said “LSEGF NOT LARGE ENOUGH.”
Robin says: This comes from the subroutine that sorts out some basic stuff for the fourier filtering of the high latitude lines. I know nothing about this, but it looks like the relevant loop goes through the map line by line, looking for separate areas. The maximum number of areas allowed for this procedure is set in the UMUI - it was 6, but the map has one line that needs 7.
In UMUI:[Ocean]-[Scientific Parameters]-[Fourier Filtering], change “Maximum number of start and end indices” to 7 or more. That allowed the model to run.
[IF YOU HAD A DIFFERENT KIND OF TROUBLE IN RUNNING THE MODEL AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
4.T. trouble shooting in ocean reconfiguration
(1)
[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]
This error occurred because the ocean chemistry was turned on in the model but was not in the ocean start dump file. If it is Ok to turn off ocean chemistry, do so in UMUI:[Ocean]-[Scientific Parameters]-[Carbon Cycle]. Also disable extra tracers in UMUI:[Ocean]-[Tracers]-[User Defined Tracers]. Then go back to 2.6 and try again. I got a .ostart of 7274496B, which is much smaller than the case with ocean chemistry turned on (~15MB), but turned out to be correct.
This error occurred because the ocean chemistry was turned on in the model but was not in the ocean start dump file. If it is Ok to turn off ocean chemistry, do so in UMUI:[Ocean]-[Scientific Parameters]-[Carbon Cycle]. Also disable extra tracers in UMUI:[Ocean]-[Tracers]-[User Defined Tracers]. Then go back to 2.6 and try again. I got a .ostart of 7274496B, which is much smaller than the case with ocean chemistry turned on (~15MB), but this turned out to be correct.
(1) $jobid.ostart has only about 2.8MB
In the .leave file completion code was 134, so clearly it was not successful. Near the bottom found the line indicating what was wrong.
(1) $jobid.ostart has only about 2.8MB and completion code in the .leave file is 134.
The completion code suggest it was clearly unsuccessful. Near the bottom found a line indicating what was wrong.
This error occurred because the ocean chemistry was turned on in the model but was not in the ocean start dump file. If it is Ok to turn off ocean chemistry, do so in UMUI:[Ocean]-[Scientific Parameters]-[Carbon Cycle]. Also disable extra tracers in UMUI:[Ocean]-[Tracers]-[User Defined Tracers]. Then go back to 2.6 and try again. I got a .ostart of 7274496B.
If you do want the chemistry, you’ll need some fields compatible with the rest of the restart.
This error occurred because the ocean chemistry was turned on in the model but was not in the ocean start dump file. If it is Ok to turn off ocean chemistry, do so in UMUI:[Ocean]-[Scientific Parameters]-[Carbon Cycle]. Also disable extra tracers in UMUI:[Ocean]-[Tracers]-[User Defined Tracers]. Then go back to 2.6 and try again. I got a .ostart of 7274496B, which is much smaller than the case with ocean chemistry turned on (~15MB), but turned out to be correct.
If you do need the chemistry, you’ll need some fields compatible with the rest of the restart.
This page is dedicated for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudes and notes if you haven’t done so.
Most information written in this page came from answers to my questions by Robin Smith and Annette Osprey. Lots of thanks to both of them.
This page is meant to be as foolproof as possible and so inevitably lengthy. Don’t tell me to tidy it up.
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory gudes and notes if you haven’t done so.
A large part of information written in this page is based on the answers to my questions by Robin Smith and Annette Osprey. Lots of thanks to both of them.
This page is meant to be as foolproof as possible and so inevitably lengthy. Please understand that and don’t tell me to tidy it up.
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudes and notes if you haven’t done so.
This page is dedicated for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudes and notes if you haven’t done so.
Most information written in this page came from answers to my questions by Robin Smith and Annette Osprey. Lots of thanks to both of them.
(1) $jobid.ostart has only about 2.8MB
(1) $jobid.ostart has only about 2.8MB
1.10. Save the original astart file
cp $jobid.astart $jobid.astart.ini
1.10. Save the original astart file
cp $jobid.astart $jobid.astart.ini
2.T. trouble shooting in ocean reconfiguration
2.T. trouble shooting in ocean reconfiguration
1.t. trouble shooting
1.T. trouble shooting
2.t. trouble shooting in ocean reconfiguration
2.T. trouble shooting in ocean reconfiguration
jobid=xxxxx (this page is based on tcmid)@]
jobid=xxxxx (this page is based on tcmid and tcmie)@]
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
2.t. trouble shooting in ocean reconfiguration
(1) $jobid.ostart has only about 2.8MB
In the .leave file completion code was 134, so clearly it was not successful. Near the bottom found the line indicating what was wrong.
*ERROR* Stash code 103 not found on input file
If you look at stash (UMUI:[Ocean]-[STASH]-[STASH. Specification…]) you will see what is 103 for (it is ‘OCN EXTRASER 1: CONVEN TCO2′).
This error occurred because the ocean chemistry was turned on in the model but was not in the ocean start dump file. If it is Ok to turn off ocean chemistry, do so in UMUI:[Ocean]-[Scientific Parameters]-[Carbon Cycle]. Also disable extra tracers in UMUI:[Ocean]-[Tracers]-[User Defined Tracers]. Then go back to 2.6 and try again. I got a .ostart of 7274496B.
If you do want the chemistry, you’ll need some fields compatible with the rest of the restart.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again. I get a file of the right size in my second attempt after going through the trouble shooting.
(2) (1) is fixed and .astart file of larger size (2064384B and later found this is not quite the right size; the right size is 2080768B) is created, which looks mostly alright, but .leave file still doesn’t seem quite happy;
(2) (1) is fixed and .astart file of larger size (2064384B and later found this is not quite the right size; the right size is 2080768B) is created, which looks ‘mostly’ alright, but .leave file still doesn’t seem quite happy;
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not a quite right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2). I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not quite the right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2) below. I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
the size should be 2080768B when successful (if 2064384B that’s not quite right!)
the size should be 2080768B when successful. but in my first attempts for new jobs I never get a file of this size but a one of 2064384B which is not a quite right size. If this happens to you look carefully the .leave file and look if it is the case described in the trouble shooting (2). I have not come across a way to preemptively avoid this problem. So what you do is submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again.
(1) in my initial attempts, a $jobid.astart file was not created. .leave file looked as normal in terms of the size (2064384B and later found this is not quite the right size; the right size is 2080768B). However, looking in the .leave file revealed some problems. “Completion code” was 134 and I suppose anything other than 0 suggests an error. just above that there are lines like;
(1) in my initial attempts, a $jobid.astart file was not created. .leave file looked as normal in terms of the size. However, looking in the .leave file revealed some problems. “Completion code” was 134 and I suppose anything other than 0 suggests an error. just above that there are lines like;
(2) (1) is fixed and .astart file of larger size is created, which looks mostly alright, but .leave file still doesn’t seem quite happy;
(2) (1) is fixed and .astart file of larger size (2064384B and later found this is not quite the right size; the right size is 2080768B) is created, which looks mostly alright, but .leave file still doesn’t seem quite happy;
1.9.t. trouble shooting
1.t. trouble shooting
2.7. manually post process on puma if necessary (see 1.8)
2.7. manually post process on puma if necessary (see 1.8)
3.7. manually post process on puma if necessary (see 1.8)
3.7. manually post process on puma if necessary (see 1.8)
4.4. manually post process on puma if necessary (see 1.8)
4.4. manually post process on puma if necessary (see 1.8)
1.8. manually post process on puma if it is necessary for you (see section [2] of NoteFamousQuest)
1.8. manually post process on puma if it is necessary for you (see section [2] of NoteFamousQuest)
2.7. manually post process on puma;
echo $jobid #chk jobid! /home/famous/bin/he_namelist_new_phase5 $jobid /home/famous/bin/vfdrift_pp.sh $jobid /home/famous/bin/quest_queue.sh $jobid
2.7. manually post process on puma if necessary (see 1.8)
3.7. manually post process on puma;
echo $jobid #chk jobid! /home/famous/bin/he_namelist_new_phase5 $jobid /home/famous/bin/vfdrift_pp.sh $jobid /home/famous/bin/quest_queue.sh $jobid
3.7. manually post process on puma if necessary (see 1.8)
4.4. manually post process on puma;
echo $jobid #chk jobid! /home/famous/bin/he_namelist_new_phase5 $jobid /home/famous/bin/vfdrift_pp.sh $jobid /home/famous/bin/quest_queue.sh $jobid
4.4. manually post process on puma if necessary (see 1.8)
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudes and notes if you haven’t done so.
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudes and notes if you haven’t done so.
1.8. manually post process on puma if necessary
1.8. manually post process on puma if it is necessary for you (see section [2] of NoteFamousQuest)
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory gudesand notes if you haven’t done so.
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. More general and introductory gudes and notes can be found here and here.
This page is devoted for running FAMOUS using reconfigurations. More general and introductory gudes and notes can be found here and here.
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found here and here.
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found here. This page is meant to be as foolproof as possible and so inevitably lengthy. Don’t tell me to tidy it up.
This page is meant to be as foolproof as possible and so inevitably lengthy. Don’t tell me to tidy it up.
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found here. This page is meant to be as foolproof as possible and so inevitably lengthy. Don’t tell me to tidy it up.
1.8. manually post process on puma;
1.8. manually post process on puma if necessary