[MITgcm-support] Using gmredi parameterization in a different 'tutorial' directory

David Lewis sir_louie at hotmail.com
Fri Apr 9 02:41:37 EDT 2010


Ryan,
Awesome!  I'll be copying/editing the packages.conf file tomorrow so that the other packages won't build (don't need'em just yet).  I really appreciate for your help on this.  Thanks.
Cheers,David

From: rpa at MIT.EDU
To: mitgcm-support at mitgcm.org
Date: Thu, 8 Apr 2010 16:42:53 -0400
Subject: Re: [MITgcm-support] Using gmredi parameterization in a different	'tutorial' directory

Hi David,
The GM-Redi package is not built by default. You need to tell the compiler to build it when you compile. If you enable it in data.pkg (as you did) without actually building it into your executable, you will get that error.
It is easy to fix--in fact you already guessed the answer. Just put a packages.conf in your code directory that contains the line "gmredi", and repeat the build process. If you want to copy the file from tutorial_baroclinic_gyre/code/packages.conf, that will work fine. Just be aware that it will also build other packages such as ptracers and mnc. You can read about how package inclusion / exclusion works here:http://mitgcm.org/public/r2_manual/latest/online_documents/node226.html
The parameters for gmredi can all be controlled from the data.gmredi file, without having to re-compile anything.
If you need to modifiy the code, you can put modified versions of any of the source code files in your local "code" directory. If you do this, you have to re-build your executable again. The source files for gmredi are in pkg/gmredi/.
Good luck,__________________Ryan Abernatheyrpa at mit.eduMIT Ph.D. StudentProgram in Oceans Atmospheres & Climatehttp://web.mit.edu/rpa/


On Apr 8, 2010, at 4:25 PM, David Lewis wrote:Hello, I’m writing to request assistance in setting up MITgcm to run a global circulation model with the Gent-McWilliams-Redi parameterization.  While I have some basic understanding of the workings of MITgcm, I am not conversant in FORTRAN language (end user knowledge).  In trying to get my code to work I did the following:                 -I’m running out of ‘…/tutorial_baroclinic gyre/’ directory, compiling out of ‘build’ and running out of a revised ‘input’ directory.  -I copied the ‘data.gmredi’ baseline file from another tutorial directory (tutorial_global_oce_latlon/input) into my revised input directory.  -I modified the data.pkg file in my input directory to read:                   useGMRedi=.TRUE.,-when I did the ‘make depend’ and ‘make’ commands, and then ran from ‘input’ I got the following errors: (PID.TID 0000.0001) ** WARNING ** INI_PARMS:   phiMin no longer supported <= replaced by ygOrigin(PID.TID 0000.0001) *** ERROR *** from PACKAGES_CHECK: run-time control flag useGMRedi is set(PID.TID 0000.0001) *** ERROR *** but pkg/gmredi was not compiled (ALLOW_GMREDI undef).(PID.TID 0000.0001) *** ERROR *** ==> Re-compile with pkg "gmredi" in file "packages.conf" I did notice that in the ‘tutorial_global_oce_latlon/code’ directory, that there was a file named ‘packages.conf’.  Would a simple copy of this file into the ‘tutorial_baroclinic_gyre/code’ directory help solve this problem?  If I need to modify the code, what do I modify?  I can modify parameters once I get the general structure set up, just need to know how to get this to compile properly. Thanks for your help. V/r,David Lewis 
The New Busy is not the old busy. Search, chat and e-mail from your inbox. Get started._______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support

 
 		 	   		  
_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20100409/0df71fd2/attachment-0001.htm>


More information about the MITgcm-support mailing list