Changed lines 70-71 from:
* Either "compile and build then stop" as in compiling or "Run from existing exec" as in running should be selected
to:
* Either "compile and build then stop" as in compiling '''OR''' "Run from existing exec" as in running should be selected
Changed lines 78-79 from:
* Either "at for other unix" as in compiling or "qsub for supporting platforms" as in running should be selected
to:
* Either "at for other unix" as in compiling '''OR''' "qsub for supporting platforms" as in running should be selected
Changed lines 236-237 from:
* Either "compile and build then stop" as in compiling or "Run from existing exec" as in running should be selected
to:
* Either "compile and build then stop" as in compiling '''OR''' "Run from existing exec" as in running should be selected
Changed lines 240-241 from:
* Either "at for other unix" as in compiling or "qsub for supporting platforms" as in running should be selected
to:
* Either "at for other unix" as in compiling '''OR''' "qsub for supporting platforms" as in running should be selected
Changed lines 472-477 from:
** Specify these dumps as initial dumps in 1.5 and 2.5
** Change the start year to the year of the dump files
** Don't worry about the trouble shooting 1.T.(2). I got a right astart file in the first attempt.
to:
** Skip 1.2 and you don't have to worry about the trouble shooting 1.T.(2). I get a proper .astart file in my first attempt.
** Specify these dumps as initial dumps in 1.5 and 2.5.
** Change the start year to the year of the dump files (and the run length accordingly).
Changed lines 168-169 from:
* modify @@~/DUMP2HOLD/um/$jobid/code/exec_build/qxrecon_dump_dir/control1.f@@ (lines near 5760) as blow;
to:
* modify @@quest:~/DUMP2HOLD/um/$jobid/code/exec_build/qxrecon_dump_dir/control1.f@@ (lines near 5760) as blow;
Deleted lines 307-308:
If started from atmospheric and oceanic reconfigurations 1&2 should already be set correctly.
Changed lines 310-311 from:
* "compile and build then stop" should be selected
to:
* Select "compile and build then stop"
Changed lines 314-315 from:
* "at for other unix" should be selected
to:
* Select "at for other unix"
Changed lines 322-323 from:
* the created .astart file: $MY_DUMPS/$RUNID.astart.ini should be specified as the "initial dump"
to:
* The created .astart file: $MY_DUMPS/$RUNID.astart.ini should be specified as the "initial dump"
Changed lines 70-71 from:
* select "compile and build then stop" (but later I heard this wouldn't matter)
to:
* Either "compile and build then stop" as in compiling or "Run from existing exec" as in running should be selected
Changed lines 78-79 from:
* select "at for other unix" (but later I heard this wouldn't matter)
to:
* Either "at for other unix" as in compiling or "qsub for supporting platforms" as in running should be selected
Changed lines 236-237 from:
* "compile and build then stop" should be selected (but later I heard this wouldn't matter)
to:
* Either "compile and build then stop" as in compiling or "Run from existing exec" as in running should be selected
Changed lines 240-241 from:
* "at for other unix" should be selected (but later I heard this wouldn't matter)
to:
* Either "at for other unix" as in compiling or "qsub for supporting platforms" as in running should be selected
Changed lines 134-136 from:
!!!1.T. trouble shooting[[#t1]]
to:
!!![[#t1]]1.T. trouble shooting
Changed lines 354-355 from:
to:
Changed lines 440-441 from:
[[#t4]]'''4.T.''' trouble shooting in running the model
to:
----
!!![[#t4]]4.T. trouble shooting in running the model
Changed lines 482-483 from:
to:
Added line 285:
Changed lines 287-289 from:
!!!2.T. trouble shooting in ocean reconfiguration[[#t2]]
to:
!!![[#t2]]2.T. trouble shooting in ocean reconfiguration
Changed lines 303-304 from:
to:
Changed lines 285-286 from:
[[#t2]]'''2.T.''' trouble shooting in ocean reconfiguration
to:
----
!!!2.T. trouble shooting in ocean reconfiguration[[#t2]]
Changed lines 228-229 from:
to:
Changed lines 135-136 from:
to:
Changed lines 135-136 from:
to:
Changed lines 134-135 from:
[[#t1]]!!!1.T. trouble shooting
to:
!!!1.T. trouble shooting[[#t1]]
Changed lines 134-135 from:
[[#t1]]'''1.T.''' trouble shooting
to:
[[#t1]]!!!1.T. trouble shooting
Added line 9:
Added line 41:
Added line 64:
Added line 133:
Added line 229:
Added line 303:
Added line 354:
Added line 481:
Changed lines 468-469 from:
** Don't worry about steps 3 and 5. The same executable can be used. Job can simply be submitted as a new run with the same jobid.
to:
** Don't worry about steps 3 and 5. The same executable can be used. Simply submit the job as a new run with the same jobid.
Changed lines 456-457 from:
So basically what you can do is use the latest atmospheric and ocean dumps as initial dumps and reconfigure and run again;
to:
So basically what you can do is use the latest atmospheric and ocean dumps as initial dumps, reconfigure, and run again;
Changed lines 450-451 from:
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.
to:
->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.
Changed lines 454-455 from:
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.
to:
->Robin continues: (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.
Changed lines 460-461 from:
* Go back and do steps 1, 2, and 4
to:
* Go back and do steps 1, 2 and 4
Changed lines 466-468 from:
** You don't have to submit as a continuation run.
to:
** Don't worry about the trouble shooting 1.T.(2). I got a right astart file in the first attempt.
** Don't worry about steps 3 and 5. The same executable can be used. Job can simply be submitted as a new run with the same jobid.
Changed lines 458-462 from:
* Copy the latest atmosphere and ocean dumps (i.e., dump2hold/$jobid/${jobid}[a|o]#da00000yyyyc1+) to MY_DUMPS.
* Go back and do steps 1, 2, and 4 specifying these dumps as initial dumps in 1.5 and 2.5. In this case you don't have to submit as a continuation run.
to:
* Copy the latest atmosphere and ocean dumps (quest1:~dump2hold/$jobid/${jobid}[a|o]#da00000yyyyc1+) to the directory where you save your dump files (it is MY_DUMPS in my case)
* Go back and do steps 1, 2, and 4
** Specify these dumps as initial dumps in 1.5 and 2.5
** Change the start year to the year of the dump files
** You don't have to submit as a continuation run.
Changed lines 458-459 from:
* Copy the latest atmospheric and ocean dumps (i.e., dump2hold/$jobid/${jobid}[a|o]#da00000yyyyc1+) to MY_DUMPS.
to:
* Copy the latest atmosphere and ocean dumps (i.e., dump2hold/$jobid/${jobid}[a|o]#da00000yyyyc1+) to MY_DUMPS.
Changed lines 454-455 from:
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.
to:
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.
Changed lines 460-462 from:
* Go back and do steps 1, 2, and 4 specifying these dumps as initial dumps in 1.5 and 2.5.
to:
* Go back and do steps 1, 2, and 4 specifying these dumps as initial dumps in 1.5 and 2.5. In this case you don't have to submit as a continuation run.
Changed lines 452-453 from:
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.
to:
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.
Changed lines 442-462 from:
to:
[[#t42]]'''(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;
* Copy the latest atmospheric and ocean dumps (i.e., dump2hold/$jobid/${jobid}[a|o]#da00000yyyyc1+) to MY_DUMPS.
* Go back and do steps 1, 2, and 4 specifying these dumps as initial dumps in 1.5 and 2.5.
Changed lines 450-451 from:
By now I have heard of a few ways to submit a continuation run.
to:
I have heard of a few ways to submit a continuation run.
Added lines 406-407:
* it should start the run so you can SKIP 4.9!!!
Deleted lines 409-410:
* This should start the run so you can SKIP 4.9!!!
Changed lines 385-386 from:
* In Bristol @@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.
to:
* In Bristol @@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.
Changed lines 402-403 from:
* THIS WILL NOT START THE RUN. SO GO ON TO 4.6!!!
to:
* THIS WILL NOT START THE RUN. SO GO ON TO 4.9!!!
Changed lines 408-409 from:
* This should start the run so you can SKIP 4.6!!!
to:
* This should start the run so you can SKIP 4.9!!!
Changed lines 359-360 from:
'''4.3.''' UMUI: [submodel indep]-[Gen config control]
to:
'''4.3.''' (same as 3.3) UMUI: [submodel indep]-[Gen config control]
Changed lines 363-364 from:
'''4.4.''' UMUI: [Atmos]-[Ancil+input]-[start dump]
to:
'''4.4.''' (same as 3.4) UMUI: [Atmos]-[Ancil+input]-[start dump]
Changed lines 369-370 from:
'''4.5.''' UMUI: [Ocean]-[input files]-[start dump]
to:
'''4.5.''' (same as 3.5) UMUI: [Ocean]-[input files]-[start dump]
Changed lines 359-364 from:
'''4.3.''' UMUI: press <save> and then <process>
'''4.4.''' manually post process on puma if necessary (see '''[[#s18|1.8]]''')
'''4.5.''' Submit
to:
'''4.3.''' UMUI: [submodel indep]-[Gen config control]
* "perform reconfig step only" should be unchecked
'''4.4.''' UMUI: [Atmos]-[Ancil+input]-[start dump]
* the created .astart file: $MY_DUMPS/$RUNID.astart.ini should be specified as the "initial dump"
* "using the reconfiguration" should be checked or unchecked depending on your purpose. so far I have never turned on atmospheric reconfiguration.
'''4.5.''' UMUI: [Ocean]-[input files]-[start dump]
* the created .ostart file: $MY_DUMPS/$RUNID.ostart.ini should be specified as the "initial dump"
* "using the reconfiguration" should be checked or unchecked depending on your purpose. now I turn ON ocean reconfiguration to make effective the freshwater ancillary file and vfdrift modification.
'''4.6.''' UMUI: press <save> and then <process>
'''4.7.''' manually post process on puma if necessary (see '''[[#s18|1.8]]''')
'''4.8.''' Submit
Changed lines 410-411 from:
to:
Changed lines 427-428 from:
'''4.7.''' check the status of the run on quest
to:
'''4.10.''' check the status of the run on quest
Changed lines 448-449 from:
to:
Changed lines 454-455 from:
to:
Changed lines 475-476 from:
to:
Changed lines 480-481 from:
to:
Changed line 448 from:
to:
Changed line 453 from:
to:
Changed line 473 from:
to:
Changed line 477 from:
to:
Changed lines 449-450 from:
[@
puma; clustersubmit -c y -s y -r quest $jobid@]
to:
[@puma; clustersubmit -c y -s y -r quest $jobid@]
Changed lines 453-454 from:
to:
Changed line 436 from:
to:
!!!Common for all methods
Added line 440:
Changed lines 454-455 from:
to:
Changed lines 474-475 from:
!!!(3) Do the same thing but on puma.
to:
!!!(3) Do the same thing but on puma
Added line 479:
Changed lines 40-42 from:
!!![[#s0]]0. set environmental constants
to:
!![[#s0]]0. set environmental constants
Changed lines 62-64 from:
!!![[#s1]]1. Reconfigure Atmosphere
to:
!![[#s1]]1. Reconfigure Atmosphere
Changed lines 225-226 from:
!!![[#s2]]2. Reconfigure Ocean
to:
!![[#s2]]2. Reconfigure Ocean
Changed lines 298-299 from:
to:
Changed lines 348-350 from:
to:
Changed lines 431-433 from:
!!![[#s5]]5. Submit a continuation run
to:
!![[#s5]]5. Submit a continuation run
Changed lines 446-447 from:
!!(1) Use @@clustersubmit@@
to:
!!!(1) Use @@clustersubmit@@
Changed lines 450-453 from:
->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.)]
!!(2) Modify @@qsubmit.quest#@@
to:
->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.))
!!!(2) Modify @@qsubmit.quest#@@
Changed lines 471-474 from:
[[#alternatives]]\\
\\
''(3) Do the same thing but on puma.
to:
!!!(3) Do the same thing but on puma.
Changed line 475 from:
''(4) Add a post processing script
to:
!!!(4) Add a post processing script
Changed lines 434-435 from:
By now I have heard of three ways to submit a continuation run. Below shows one of them. [[#alternatives | '''Here are alternative ways.''']]
to:
By now I have heard of a few ways to submit a continuation run.
!!Common for all methods
Do 5.1 and 5.2 if necessary.
Changed lines 440-443 from:
\\\
if you don't have to do this, (for example because the original run stopped in the middle of the specified simulation period for any reason and you just want to complete the originally specified length,) probably you can skip 5.2 as well. just do 5.3 and 5.4.
to:
* set a longer length as you like
Changed lines 444-446 from:
'''5.3.''' modify @@qsubmit.quest#@@
* just like 4.6, on quest cd to the most recent directory in $HOME/umui_runs
to:
Then do one of (1)~(4).
!!(1) Use @@clustersubmit@@
Added lines 449-457:
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.)]
!!(2) Modify @@qsubmit.quest#@@
'''5.3.''' modify @@qsubmit.quest#@@
* just like 4.6, on quest cd to the most recent directory in $HOME/umui_runs
[@
Changed lines 471-472 from:
'''Alternative ways to submit a continuation run'''
to:
Changed lines 474-476 from:
* You can do the same thing on puma. cd to @@~/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.
* The easiest way might be just include the following hand-edit in the post processing.
to:
''(3) Do the same thing but on puma.
* cd to @@~/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
* Include the following in the post processing.
Changed lines 481-487 from:
->By doing this UMUI will automatically do the same thing as the point above.
* Maybe the clustersubmit can be used but I haven't tried yet.
[@
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.)]
to:
->By doing this UMUI will automatically do the same thing as (3).
Changed lines 369-370 from:
* In Bristol @@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.
to:
* In Bristol @@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.
Added lines 382-383:
'''If UMUI [SUBMIT] button is clicked or @@umsubmit@@ is used'''
Changed lines 386-387 from:
* If [SUBMIT] is clicked on UMUI or @@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.
to:
* THIS WILL NOT START THE RUN. SO GO ON TO 4.6!!!
'''If @@clustersubmit@@ is used'''
* the output file (quest:~/umui_out/***.leave) will be created after the run is stopped or finished.
* This should start the run so you can SKIP 4.6!!!
Changed lines 369-370 from:
* Among these options, @@clustersubmit@@ is preferable because you can skip the step 4.6. @@clustersubmit@@ also has more control.
to:
* In Bristol @@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.
Added lines 369-370:
* Among these options, @@clustersubmit@@ is preferable because you can skip the step 4.6. @@clustersubmit@@ also has more control.
Changed lines 384-385 from:
* If [SUBMIT] is clicked on UMUI or @@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.
to:
* If [SUBMIT] is clicked on UMUI or @@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.
Changed lines 382-383 from:
* THIS WILL NOT START THE RUN. GO ON TO THE NEXT STEP!
to:
* If [SUBMIT] is clicked on UMUI or @@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.
Changed line 126 from:
* @@quest:$MY_DUMPS/$jobid.astart/@@
to:
Changed lines 127-128 from:
[@ cp $jobid.astart $jobid.astart.ini@]
to:
[@
cp $jobid.astart $jobid.astart.ini@]
Changed lines 127-128 from:
cp $jobid.astart $jobid.astart.ini
to:
[@ cp $jobid.astart $jobid.astart.ini@]
Changed lines 123-124 from:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#t12|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#t12|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
* @@~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon@@ is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#t12|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#t12|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed line 126 from:
to:
* @@quest:$MY_DUMPS/$jobid.astart/@@
Changed lines 120-122 from:
(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 '''[[#t12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#t12|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.
to:
(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 '''[[#t12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#t12|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.
Changed lines 182-183 from:
* copy it to @@/exports/gpfsbig/home/$USER/DUMP2HOLD/um/$jobid/dataw/@@ and rename it @@$jobid.recon@@
to:
* copy @@qxrecon_dump@@ to @@/exports/gpfsbig/home/$USER/DUMP2HOLD/um/$jobid/dataw/@@ and rename it @@$jobid.recon@@
Changed lines 171-174 from:
if (ICODE.eq.1501) then
& //' This is probably not a problem.'
else
to:
if (ICODE.eq.1501) then !!!
write(6,*) ' Polar rows not constant in T*.' !!!
& //' This is probably not a problem.' !!!
else !!!
Changed line 177 from:
to:
Changed lines 171-174 from:
'''if (ICODE.eq.1501) then'''
'''write(6,*) ' Polar rows not constant in T*.'
& //' This is probably not a problem.' '''
else%%
to:
if (ICODE.eq.1501) then
write(6,*) ' Polar rows not constant in T*.'
& //' This is probably not a problem.'
else
Changed line 177 from:
to:
Changed lines 171-173 from:
%red%if (ICODE.eq.1501) then
& //' This is probably not a problem.'
to:
'''if (ICODE.eq.1501) then'''
'''write(6,*) ' Polar rows not constant in T*.'
& //' This is probably not a problem.' '''
Changed line 177 from:
to:
Changed line 171 from:
%red% if (ICODE.eq.1501) then
to:
%red%if (ICODE.eq.1501) then
Changed line 173 from:
% //' This is probably not a problem.'
to:
& //' This is probably not a problem.'
Changed line 177 from:
to:
Changed lines 171-174 from:
if (ICODE.eq.1501) then
write(6,*)"Polar rows not constant in T*"
write(6,*)"This may, or may not, be a problem"
else
to:
%red% if (ICODE.eq.1501) then
write(6,*) ' Polar rows not constant in T*.'
% //' This is probably not a problem.'
else%%
Changed line 177 from:
to:
Changed lines 461-463 from:
[@ 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.)]
to:
[@
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.)]
Added lines 460-463:
* Maybe the clustersubmit can be used but I haven't tried yet.
[@ 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.)]
Changed lines 335-337 from:
UMUI: press [SUBMIT] OR
puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
to:
[@ 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@]
Changed lines 364-366 from:
UMUI: press [SUBMIT] OR
puma: ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
to:
[@ 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@]
Changed lines 262-264 from:
UMUI: press [SUBMIT] OR\\
puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid
to:
[@ 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@]
Changed lines 111-113 from:
[@ UMUI: press [SUBMIT] OR
puma; ~jeff/bin/umsubmit -h quest-hpc.bris.ac.uk -u $USER -r scp $jobid@]
to:
[@ 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@]
Changed line 12 from:
[[#s0|'''0. set environmental constants''']]
to:
!!![[#s0|0. set environmental constants]]
Changed line 15 from:
[[#s1|'''1. Reconfigure Atmosphere''']]
to:
!!![[#s1|1. Reconfigure Atmosphere]]
Changed line 12 from:
!!![[#s0|0. set environmental constants]]
to:
[[#s0|'''0. set environmental constants''']]
Changed line 15 from:
!!![[#s1|1. Reconfigure Atmosphere]]
to:
[[#s1|'''1. Reconfigure Atmosphere''']]
Changed lines 377-378 from:
* THIS DOES NOT START THE RUN. GO ON TO THE NEXT STEP!
to:
* THIS WILL NOT START THE RUN. GO ON TO THE NEXT STEP!
Changed lines 377-378 from:
%center% '''{+THIS DOES NOT START THE RUN. GO ON TO THE NEXT STEP+}!'''
to:
* THIS DOES NOT START THE RUN. GO ON TO THE NEXT STEP!
Changed line 18 from:
->[[#t1|!!!1.T. trouble shooting in atmospheric reconfiguration]]
to:
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
Changed line 33 from:
->[[#t4|'''4.T.''' trouble shooting in running the model]]
to:
->[[#t4|'''4.T. trouble shooting in running the model''']]
Changed line 18 from:
->[[#t1|1.T. trouble shooting in atmospheric reconfiguration]]!!!
to:
->[[#t1|!!!1.T. trouble shooting in atmospheric reconfiguration]]
Changed line 18 from:
!!!->[[#t1|1.T. trouble shooting in atmospheric reconfiguration]]
to:
->[[#t1|1.T. trouble shooting in atmospheric reconfiguration]]!!!
Changed line 18 from:
->[[#t1|!!!1.T. trouble shooting in atmospheric reconfiguration]]
to:
!!!->[[#t1|1.T. trouble shooting in atmospheric reconfiguration]]
Changed line 18 from:
->!!![[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
to:
->[[#t1|!!!1.T. trouble shooting in atmospheric reconfiguration]]
Changed line 18 from:
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
to:
->!!![[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
Changed lines 12-16 from:
!!![[#s0|0. set environmental constants]]\\
!!![[#s1|1. Reconfigure Atmosphere]]\\
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
to:
!!![[#s0|0. set environmental constants]]
Changed lines 14-15 from:
!!![[#s2|2. Reconfigure Ocean]]
to:
!!![[#s1|1. Reconfigure Atmosphere]]
Changed lines 17-18 from:
->[[#t2|'''2.T. trouble shooting in ocean reconfiguration''']]
to:
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
Changed lines 20-21 from:
to:
!!![[#s2|2. Reconfigure Ocean]]
Changed lines 23-24 from:
to:
->[[#t2|'''2.T. trouble shooting in ocean reconfiguration''']]
Changed lines 26-27 from:
->[[#t4|'''4.T.''' trouble shooting in running the model]]
to:
Changed lines 29-30 from:
!!![[#s5|5. Submit a continuation run]]
to:
Added lines 32-33:
->[[#t4|'''4.T.''' trouble shooting in running the model]]
Added lines 36-39:
!!![[#s5|5. Submit a continuation run]]
\\
\\
Changed lines 12-16 from:
!!![[#s0|0. set environmental constants]]
to:
!!![[#s0|0. set environmental constants]]\\
!!![[#s1|1. Reconfigure Atmosphere]]\\
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
Changed line 18 from:
!!![[#s1|1. Reconfigure Atmosphere]]
to:
!!![[#s2|2. Reconfigure Ocean]]
Changed line 20 from:
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
to:
->[[#t2|'''2.T. trouble shooting in ocean reconfiguration''']]
Changed line 22 from:
!!![[#s2|2. Reconfigure Ocean]]
to:
Changed line 24 from:
->[[#t2|'''2.T. trouble shooting in ocean reconfiguration''']]
to:
Changed line 26 from:
to:
->[[#t4|'''4.T.''' trouble shooting in running the model]]
Changed line 28 from:
to:
!!![[#s5|5. Submit a continuation run]]
Deleted line 29:
->[[#t4|'''4.T.''' trouble shooting in running the model]]
Changed lines 31-34 from:
!!![[#s5|5. Submit a continuation run]]
\\
\\
to:
Changed lines 9-10 from:
to:
Changed line 12 from:
to:
Changed lines 14-16 from:
''' trouble shooting]]
to:
\\
->[[#t1|'''1.T. trouble shooting in atmospheric reconfiguration''']]
\\
Changed lines 18-20 from:
''' trouble shooting in ocean reconfiguration]]
to:
\\
->[[#t2|'''2.T. trouble shooting in ocean reconfiguration''']]
\\
Changed line 22 from:
to:
Changed line 24 from:
to:
Changed line 26 from:
to:
Changed lines 28-30 from:
to:
Added line 10:
Added line 12:
Changed lines 15-30 from:
to:
->[[#t1|'''1.T.''' trouble shooting]]
!!![[#s2|2. Reconfigure Ocean]]
->[[#t2|'''2.T.''' trouble shooting in ocean reconfiguration]]
!!![[#s3|3. Compile]]
!!![[#s4|4. Run]]
->[[#t4|'''4.T.''' trouble shooting in running the model]]
!!![[#s5|5. Submit a continuation run]]
Changed lines 214-215 from:
[[#s2]]!!!2. Reconfigure Ocean
to:
!!![[#s2]]2. Reconfigure Ocean
Changed lines 286-287 from:
to:
Changed lines 335-337 from:
to:
Changed lines 407-409 from:
[[#s5]]!!!5. Submit a continuation run
to:
!!![[#s5]]5. Submit a continuation run
Changed lines 11-13 from:
to:
!!![[#s1|1. Reconfigure Atmosphere]]
Changed lines 36-38 from:
[[#s1]]!!!1. Reconfigure Atmosphere
to:
!!![[#s1]]1. Reconfigure Atmosphere
Changed lines 102-103 from:
'''1.T.''' trouble shooting
to:
[[#t1]]'''1.T.''' trouble shooting
Changed lines 14-16 from:
!!!0. set environmental constants[[#s0]]
to:
!!![[#s0]]0. set environmental constants
Changed lines 9-11 from:
!!!]]0. set environmental constants
to:
!!!Contents
!!![[#s0|0. set environmental constants]]
!!!0. set environmental constants[[#s0]]
Changed lines 9-11 from:
[[#s0]]!!!0. set environmental constants
to:
!!![[#s0]]0. set environmental constants
Changed lines 237-240 from:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) If successful the size should be 15253504B when the ocean chemistry is turned on, or 7274496B when it is turned off and extra tracers are disabled (see [[#ts2|trouble shooting 2.T.(1)]]).
* check [[#ts2|trouble shooting]] if you have a problem here
to:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) If successful the size should be 15253504B when the ocean chemistry is turned on, or 7274496B when it is turned off and extra tracers are disabled (see [[#t21|trouble shooting 2.T.(1)]]).
* check [[#t2|trouble shooting]] if you have a problem here
Changed lines 246-247 from:
[[#ts2]]'''2.T.''' trouble shooting in ocean reconfiguration
to:
[[#t2]]'''2.T.''' trouble shooting in ocean reconfiguration
Changed lines 9-11 from:
!!!0. set environmental constants
to:
[[#s0]]!!!0. set environmental constants
Changed lines 31-33 from:
!!!1. Reconfigure Atmosphere
to:
[[#s1]]!!!1. Reconfigure Atmosphere
Changed lines 89-92 from:
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 '''[[#ts12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#ts12|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#ts12|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
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 '''[[#t12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#t12|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.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#t12|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#t12|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed lines 99-100 from:
'''(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;
to:
[[#t11]]'''(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;
Changed lines 112-114 from:
[[#ts12]]
'''(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;
to:
[[#t12]]'''(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;
Changed lines 173-174 from:
'''(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;
to:
[[#t13]]'''(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;
Changed lines 192-193 from:
to:
[[#s2]]!!!2. Reconfigure Ocean
Changed line 248 from:
'''(1)''' $jobid.ostart has only about 2.8MB and completion code in the .leave file is 134.
to:
[[#t21]]'''(1)''' $jobid.ostart has only about 2.8MB and completion code in the .leave file is 134.
Changed lines 264-265 from:
to:
Changed lines 313-315 from:
to:
Changed lines 370-373 from:
[[#ts4]]'''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."
to:
[[#t4]]'''4.T.''' trouble shooting in running the model
[[#t41]]'''(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."
Changed lines 385-387 from:
!!!5. Submit a continuation run
to:
[[#s5]]!!!5. Submit a continuation run
Changed lines 5-6 from:
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.
to:
This page is meant to be as foolproof as possible and so inevitably lengthy. Don't tell me to tidy it up.
Changed lines 378-380 from:
* Just repeat this section (actually 4.5+4.6 only). The model started to run.
to:
* Just repeat this section and the model started to run.
Changed lines 378-380 from:
* Just repeat this section (actually 4.5+4.6 only). The model ran.
to:
* Just repeat this section (actually 4.5+4.6 only). The model started to run.
Changed lines 376-378 from:
* 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.
to:
* In UMUI:[Ocean]-[Scientific Parameters]-[Fourier Filtering], change "Maximum number of start and end indices" to 7 or more.
* Just repeat this section (actually 4.5+4.6 only). The model ran.
Changed lines 370-371 from:
[[#ts4]]'''4.T.''' trouble shooting in ocean reconfiguration
to:
[[#ts4]]'''4.T.''' trouble shooting in running the model
Changed lines 187-188 from:
%blue%[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]%%
to:
%blue%[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.]%%
Changed lines 259-260 from:
%blue%[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]%%
to:
%blue%[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.]%%
Changed lines 378-379 from:
%blue%[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]%%
to:
%blue%[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.]%%
Changed lines 187-188 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 258-259 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 376-377 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 372-373 from:
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.
to:
->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.
Changed lines 372-375 from:
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.
to:
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.
* 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.
Changed lines 1-2 from:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']] that might be worth looking at.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so.
Added lines 419-420:
There is also some information about resubmission in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/ | '''NCAS-CMS website''']].
Changed lines 1-2 from:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']]that might be worth looking at.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']] that might be worth looking at.
Changed lines 1-2 from:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']] that might be worth looking at.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']]that might be worth looking at.
Changed lines 1-2 from:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/ | '''NCAS-CMS website''']] that might be worth looking at.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/|'''NCAS-CMS website''']] that might be worth looking at.
Changed lines 1-2 from:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so. There is also some information in the [[http://ncas-cms.nerc.ac.uk/content/view/37/50/ | '''NCAS-CMS website''']] that might be worth looking at.
Changed lines 383-384 from:
By now I have heard of three ways to submit a continuation run. Below shows one of them. [[#alternatives | '''Click here for alternative ways.''']]
to:
By now I have heard of three ways to submit a continuation run. Below shows one of them. [[#alternatives | '''Here are alternative ways.''']]
Deleted lines 418-419:
There's also [[http://ncas-cms.nerc.ac.uk/content/view/37/50/ | '''a section on the NCAS-CMS website''']] that might be worth looking at.
Changed lines 187-188 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 258-259 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 376-377 from:
%blue%[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]%%
to:
%blue%[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]%%
Changed lines 187-188 from:
%red%[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]%%
to:
%blue%[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]%%
Changed lines 258-259 from:
%red%[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]%%
to:
%blue%[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]%%
Changed lines 376-377 from:
%red%[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]%%
to:
%blue%[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]%%
Changed lines 187-188 from:
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]%%
to:
%red%[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]%%
Changed lines 258-259 from:
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]%%
to:
%red%[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]%%
Changed lines 370-373 from:
'''(1)'''
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE
to:
'''(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.
%red%[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]%%
Added lines 187-188:
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]%%
Added lines 258-259:
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]%%
Added lines 368-373:
[[#ts4]]'''4.T.''' trouble shooting in ocean reconfiguration
'''(1)'''
%red%[IF YOU HAD A DIFFERENT KIND OF TROUBLE AND IT IS RESOLVED, PLEASE ADD THE INFORMATION ABOUT IT TO SHARE WITH OTHER USERS]%%
Changed lines 234-235 from:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) If successful the size should be 15253504B when the ocean chemistry is turned on, or 7274496B when it is turned off and extra tracers are disabled (see trouble shooting 2.T.(1)).
to:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) If successful the size should be 15253504B when the ocean chemistry is turned on, or 7274496B when it is turned off and extra tracers are disabled (see [[#ts2|trouble shooting 2.T.(1)]]).
Changed lines 252-253 from:
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.
to:
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.
Changed lines 234-235 from:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) the size should be 15253504B when successful
to:
* $jobid.ostart file is created as you set in [Ocean]-[input files]-[start dump] (in my case it is $MY_DUMPS/$jobid.ostart = ~/um/dumps/$jobid.ostart) If successful the size should be 15253504B when the ocean chemistry is turned on, or 7274496B when it is turned off and extra tracers are disabled (see trouble shooting 2.T.(1)).
Changed lines 245-247 from:
'''(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.
to:
'''(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.
Changed lines 252-255 from:
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.
to:
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.
Changed line 401 from:
* The easiest way might be just to include the following hand-edit in the post processing.
to:
* The easiest way might be just include the following hand-edit in the post processing.
Changed lines 404-405 from:
->By doing this UMUI will do the same thing as the point above automatically.
to:
->By doing this UMUI will automatically do the same thing as the point above.
Changed line 401 from:
* Probably the easiest way might be just to include the following hand-edit.
to:
* The easiest way might be just to include the following hand-edit in the post processing.
Changed lines 404-405 from:
->By doing this UMUI will do the same thing as the previous point automatically.
to:
->By doing this UMUI will do the same thing as the point above automatically.
Changed lines 29-30 from:
to:
Added lines 187-188:
Added lines 256-257:
Changed lines 305-306 from:
to:
Changed lines 364-365 from:
to:
Deleted line 370:
Changed lines 7-8 from:
to:
Changed lines 8-10 from:
to:
!!!0. set environmental constants
Added line 30:
Changed lines 1-7 from:
This page is dedicated for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|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.
to:
This page is dedicated to running FAMOUS using reconfigurations although it might help in more general cases. Please refer to general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|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.
Changed lines 1-4 from:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so.
to:
This page is dedicated for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|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.
Changed line 238 from:
(1) $jobid.ostart has only about 2.8MB
to:
'''(1)''' $jobid.ostart has only about 2.8MB
Added lines 88-91:
'''1.10.''' Save the original astart file
cp $jobid.astart $jobid.astart.ini
Deleted lines 181-185:
'''1.10.''' Save the original astart file
cp $jobid.astart $jobid.astart.ini
Changed lines 236-238 from:
[[#ts2]]
'''2.T.''' trouble shooting in ocean reconfiguration
to:
[[#ts2]]'''2.T.''' trouble shooting in ocean reconfiguration
Changed lines 88-89 from:
'''1.t.''' trouble shooting
to:
'''1.T.''' trouble shooting
Changed lines 238-239 from:
2.t. trouble shooting in ocean reconfiguration
to:
'''2.T.''' trouble shooting in ocean reconfiguration
Changed lines 12-13 from:
jobid=xxxxx (this page is based on tcmid)@]
to:
jobid=xxxxx (this page is based on tcmid and tcmie)@]
Changed lines 84-85 from:
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 '''{+[[#ts12|trouble shooting (2)]]+}''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
to:
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 '''[[#ts12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
Changed lines 84-85 from:
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 '''[[#ts12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
to:
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 '''{+[[#ts12|trouble shooting (2)]]+}''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
Changed lines 84-87 from:
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 '''[[#ts2|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts2|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.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#ts2|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#ts2|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
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 '''[[#ts12|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts12|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.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#ts12|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#ts12|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed line 103 from:
to:
Added lines 230-231:
* check [[#ts2|trouble shooting]] if you have a problem here
Changed lines 237-250 from:
to:
[[#ts2]]
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.
Changed lines 59-60 from:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ or qrparm.ocean.restart etc.) (this only matters in the next step though)
to:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ , qrparm.ocean.restart etc.) (this only matters in the next step though)
Changed lines 207-208 from:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ or qrparm.ocean.restart etc.)
to:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ , qrparm.ocean.restart etc.)
Changed lines 59-60 from:
* use a proper start dump eg: $MY_DUMPS/xbyvqo#da000002541c1+ (this only matters in the next step though)
to:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ or qrparm.ocean.restart etc.) (this only matters in the next step though)
Changed lines 207-208 from:
* use a proper start dump (eg: $MY_DUMPS/qrparm.ocean.restart)
to:
* use a proper start dump ($MY_DUMPS/ xbyvqo#da000002541c1+ or qrparm.ocean.restart etc.)
Changed lines 84-85 from:
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 '''[[#ts2|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts2|trouble shooting (2)]]''' and fix the problem, and try again%%.
to:
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 '''[[#ts2|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts2|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.
Changed lines 104-105 from:
'''(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;
to:
'''(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;
Changed line 103 from:
to:
Changed lines 84-87 from:
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 [[#ts2|trouble shooting (2)]] below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the [[#ts2|trouble shooting (2)]] and fix the problem, and try again%%.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE [[#ts2|TROUBLE SHOOTING (2)]] UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the [[#ts2|trouble shooting (2)]], or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
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 '''[[#ts2|trouble shooting (2)]]''' below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the '''[[#ts2|trouble shooting (2)]]''' and fix the problem, and try again%%.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE '''[[#ts2|TROUBLE SHOOTING (2)]]''' UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the '''[[#ts2|trouble shooting (2)]]''', or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed lines 84-87 from:
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 %red%submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again%%.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE TROUBLE SHOOTING 1.t.(2) UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the trouble shooting 1.t.(2), or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
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 [[#ts2|trouble shooting (2)]] below. I have not come across a way to preemptively avoid this problem. So what you do is %red%submit, get a wrong .astart file, go through the [[#ts2|trouble shooting (2)]] and fix the problem, and try again%%.
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE [[#ts2|TROUBLE SHOOTING (2)]] UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the [[#ts2|trouble shooting (2)]], or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed lines 84-85 from:
the size should be 2080768B when successful (if 2064384B that's not quite right!)
to:
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 %red%submit, get a wrong .astart file, go through the trouble shooting (2) and fix the problem, and try again%%.
Changed lines 90-91 from:
'''(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;
to:
'''(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;
Changed lines 104-105 from:
'''(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;
to:
'''(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;
Changed lines 86-87 from:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in the first run that crashes (LET IT CRASH AND DO THE TROUBLE SHOOTING 1.t.(2) UNTIL WE FIND A BETTER WAY TO RUN!!!). This will not be created after going through the trouble shooting 1.t.(2), or in other words, the one created manually in the trouble shooting should not be overwritten.
to:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in %red%the first run that crashes (LET IT CRASH AND DO THE TROUBLE SHOOTING 1.t.(2) UNTIL WE FIND A BETTER WAY TO RUN!!!)%%. This will not be created after going through the trouble shooting 1.t.(2), or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed lines 86-87 from:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in the first run that crushes. This should not be created (new one should not overwrite the existing one) after going through trouble shooting 1.t.(2)
to:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in the first run that crashes (LET IT CRASH AND DO THE TROUBLE SHOOTING 1.t.(2) UNTIL WE FIND A BETTER WAY TO RUN!!!). This will not be created after going through the trouble shooting 1.t.(2), or in other words, the one created manually in the trouble shooting should not be overwritten.
Changed lines 86-87 from:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in the first run that crushes. This should not be created (new one should not overwrite the existing one) after going through trouble shooting 18t(2)
to:
* ~/DUMP2HOLD/um/$jobid/dataw/$RUNID.recon is newly created in the first run that crushes. This should not be created (new one should not overwrite the existing one) after going through trouble shooting 1.t.(2)
Changed line 82 from:
* $jobid.astart file is created as you set in [Atmos]-[Ancil+input]-[start dump]\\
to:
* $jobid.astart file is created as you specified in [Atmos]-[Ancil+input]-[start dump]\\
Changed lines 61-62 from:
* "using the reconfiguration" should be UNCHECKED
to:
* "using the reconfiguration" should be UNCHECKED (this is probably important)
Changed lines 47-48 from:
* use the usual start dump eg: $MY_DUMPS/xbyvqa#da000002541c1+
to:
* use a regular start dump eg: $MY_DUMPS/xbyvqa#da000002541c1+
Changed lines 35-36 from:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.t (2) and (3) below.
to:
* select "Compile and build the executable named below". this is related to trouble shooting 1.t (2) and (3) below.
Changed lines 35-36 from:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.9.t (2) and (3) below.
to:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.t (2) and (3) below.
Changed lines 88-89 from:
'''1.9.t.''' trouble shooting
to:
'''1.t.''' trouble shooting
Changed lines 35-36 from:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.8.t (2) and (3) below.
to:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.9.t (2) and (3) below.
Changed line 65 from:
to:
Changed lines 217-218 from:
'''2.7.''' manually post process on puma if necessary (see '''1.8''')
to:
'''2.7.''' manually post process on puma if necessary (see '''[[#s18|1.8]]''')
Changed lines 270-271 from:
'''3.7.''' manually post process on puma if necessary (see '''1.8''')
to:
'''3.7.''' manually post process on puma if necessary (see '''[[#s18|1.8]]''')
Changed lines 297-298 from:
'''4.4.''' manually post process on puma if necessary (see '''1.8''')
to:
'''4.4.''' manually post process on puma if necessary (see '''[[#s18|1.8]]''')
Changed line 65 from:
to:
Changed line 65 from:
to:
Changed line 65 from:
'''1.8.''' manually post process on puma if it is necessary for you (see section [2] of '''[[NoteFamousQuest]]''')
to:
'''1.8.''' manually post process on puma if it is necessary for you (see '''[[NoteFamousQuest#sec2|section [2] of NoteFamousQuest]]''')
Changed lines 216-223 from:
'''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
to:
'''2.7.''' manually post process on puma if necessary (see '''1.8''')
Changed lines 269-276 from:
'''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
to:
'''3.7.''' manually post process on puma if necessary (see '''1.8''')
Changed lines 296-303 from:
'''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
to:
'''4.4.''' manually post process on puma if necessary (see '''1.8''')
Changed line 1 from:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory [[RunningQuest|gudes]] and [[NoteFamousQuest|notes]] if you haven't done so.
to:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory '''[[RunningQuest|gudes]]''' and '''[[NoteFamousQuest|notes]]''' if you haven't done so.
Changed line 65 from:
'''1.8.''' manually post process on puma if necessary
to:
'''1.8.''' manually post process on puma if it is necessary for you (see section [2] of '''[[NoteFamousQuest]]''')
Changed line 1 from:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory [[RunningQuest|gudes]]and [[NoteFamousQuest|notes]] if you haven't done so.
to:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory [[RunningQuest|gudes]] and [[NoteFamousQuest|notes]] if you haven't done so.
Changed line 1 from:
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 [[RunningQuest|here]] and [[NoteFamousQuest|here]].
to:
This page is devoted for running FAMOUS using reconfigurations although this may help in other cases. Please refer to more general and introductory [[RunningQuest|gudes]]and [[NoteFamousQuest|notes]] if you haven't done so.
Changed lines 1-2 from:
This page is devoted for running FAMOUS using reconfigurations. More general and introductory gudes and notes can be found [[RunningQuest|here]] and NoteFamousQuest|here]].
to:
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 [[RunningQuest|here]] and [[NoteFamousQuest|here]].
Changed lines 1-2 from:
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found [[RunningQuest|here]] and [[NoteFamousQuest|here]].
to:
This page is devoted for running FAMOUS using reconfigurations. More general and introductory gudes and notes can be found [[RunningQuest|here]] and [[NoteFamousQuest|here]].
Changed lines 1-3 from:
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found [[RunningQuest|here]]. This page is meant to be as foolproof as possible and so inevitably lengthy. Don't tell me to tidy it up.
to:
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found [[RunningQuest|here]] and [[NoteFamousQuest|here]].
This page is meant to be as foolproof as possible and so inevitably lengthy. Don't tell me to tidy it up.
Changed lines 1-3 from:
This page is meant to be as foolproof as possible and so inevitably lengthy. Don't tell me to tidy it up.
to:
This page is devoted for running FAMOUS using reconfigurations. A more general and introductory note can be found [[RunningQuest|here]]. This page is meant to be as foolproof as possible and so inevitably lengthy. Don't tell me to tidy it up.
Changed line 64 from:
'''1.8.''' manually post process on puma;
to:
'''1.8.''' manually post process on puma if necessary
Changed lines 42-43 from:
* check "perform reconfig step only" (this is important)
to:
* CHECK "perform reconfig step only" (this is important)
Changed lines 48-51 from:
* check "using the reconfiguration"
* check "Resetting data time to verification time" (and maybe "override..." also) if starting date given in UMUI (above in the same page) is different from the date in atmospheric start dump
to:
* CHECK "using the reconfiguration"
* CHECK "Resetting data time to verification time" (and maybe "override..." also) if starting date given in UMUI (above in the same page) is different from the date in atmospheric start dump
Changed lines 58-59 from:
* use the usual start dump eg: $MY_DUMPS/xbyvqo#da000002541c1+
to:
* use a proper start dump eg: $MY_DUMPS/xbyvqo#da000002541c1+ (this only matters in the next step though)
Changed lines 201-202 from:
* UNcheck "using the reconfiguration"
to:
* UNCHECK "using the reconfiguration"
Changed lines 205-210 from:
* the usual start dump (eg: $MY_DUMPS/xbyvqo#da000002541c1+) should be used. if you started from atmospheric reconfiguration this should already be specified.
* check "using the reconfiguration"
* check "Resetting data time to verification time" (and maybe "override..." also) if starting date given in UMUI (above in the same page) is different from the date in the oceanic start dump
to:
* use a proper start dump (eg: $MY_DUMPS/qrparm.ocean.restart)
* CHECK "using the reconfiguration"
* CHECK "Resetting data time to verification time" (and maybe "override..." also) if starting date given in UMUI (above in the same page) is different from the date in the oceanic start dump
Changed lines 254-255 from:
* UNcheck "perform reconfig step only"
to:
* UNCHECK "perform reconfig step only"
Changed lines 267-268 from:
* UNcheck "Resetting data time to verification time" ????
to:
* UNCHECK "Resetting data time to verification time" ????
Changed lines 187-188 from:
* "compile and build then stop" should be selected
to:
* "compile and build then stop" should be selected (but later I heard this wouldn't matter)
Changed lines 191-192 from:
* "at for other unix" should be selected
to:
* "at for other unix" should be selected (but later I heard this wouldn't matter)
Changed lines 195-196 from:
* "perform reconfig step only" should be checked
to:
* "perform reconfig step only" should be checked (this is important!)
Changed lines 30-31 from:
* select "compile and build then stop" (but later I heard this doesn't matter)
to:
* select "compile and build then stop" (but later I heard this wouldn't matter)
Changed lines 34-35 from:
* select "Compile and build the executable named below" (but later I heard this doesn't matter). this is related to trouble shooting 1.8.t (2) and (3) below.
to:
* select "Compile and build the executable named below" (but later I heard this wouldn't matter). this is related to trouble shooting 1.8.t (2) and (3) below.
Changed lines 38-39 from:
* select "at for other unix" (but later I heard this doesn't matter)
to:
* select "at for other unix" (but later I heard this wouldn't matter)
Changed lines 30-31 from:
* select "compile and build then stop"
to:
* select "compile and build then stop" (but later I heard this doesn't matter)
Changed lines 34-35 from:
* select "Compile and build the executable named below". this is related to trouble shooting 1.8.t (2) and (3) below.
to:
* select "Compile and build the executable named below" (but later I heard this doesn't matter). this is related to trouble shooting 1.8.t (2) and (3) below.
Changed lines 38-39 from:
* select "at for other unix"
to:
* select "at for other unix" (but later I heard this doesn't matter)
Changed lines 42-43 from:
* check "perform reconfig step only"
to:
* check "perform reconfig step only" (this is important)