Jim Edwards

Results 58 comments of Jim Edwards

GET_REFCASE should only be true for the specific compsets that have refcases in inputdata, do not set it in general or we will be getting lots of requests for data...

@drmikemills I think that the only issue is that after you change RUN_REFCASE you need to run ./preview_namelists to update the refcase information in Buildconf

We should be able to check hashes and let the user know if the sandbox has changed.

Alper, We use manage externals with the ufs project where there is a hierarchy of git submodules and it works there - have you tried it with Mom lately? If...

@shenhan173 Can you Document this PR - what changes do you want to make to the License file and why?

My plan is to fork this repo and add a cime_config subdirectory with a buildlib and Makefile which will use the Macros file from a cime case. But FMS seems...

@gold2718 @alperaltuntas can you identify what parts of fms you each need?

Ward, Looking at this closer - the problem isn't the cpp macros in the file. It's the c-style comments /\* */ which the compiler doesn't recognize. And in fact there...

From: Bob Walkup [email protected] Date: Fri, Dec 4, 2015 at 11:39 AM Subject: Re: c-style comments in fortran include files To: Jim Edwards [email protected] I checked the doc, and tried...

Sdoc is a pointer. I was able to work around it by explicitly exposing the destroyNode subroutine and calling it directly. PGI compilers (now nvidia) are available here https://developer.nvidia.com/hpc-sdk