This was moved to the seacism/builds directory.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1463 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 21460c2467aa4507936c170ff99d21bbcb723043
slightly tweak ordering of module commands -- unload everthing first, then do loads (to avoid any inconsistent states along the way)



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1466 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: bbec0189a502b0073136c1ee8ec2f4f61a33f849
reset BISICLES_INTERFACE location back to Doug's directories



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1467 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: ab80c1027d7a05f431d7e20d839e66cbd5a1a442
Merging seacism_timestep_reordering into the main seacism branch.

***NOTE: This commit will change answers in the seacism branch.***


This commit introduces substantial changes to glissade.F90, glide.F90 and simple_glide.F90 and some minor changes to other modules.  The purpose of this commit is to put various fields at the proper time level in the output.  For the most part it does not change calculations but some fields will be written at a different time level than before.

This resolves two separate issues related to time-stepping:
1. Diagnostic solve for initial time.  Previously output at time 0 was of a state advanced in time from the state passed in by the input file.  Now there is a diagnostic solve (of velocity and other diagnostic fields like usrf, lsrf) prior to time-stepping.  For a run where tend=tstart, the time-stepping loop is not entered at all.  This was accommodated by changing the looping condition and by adding diagnostic solve subroutines for both glissade and glide that are called in simple_glide prior to time-stepping.  

2. Within a time step there were inconsistencies in the time level in the output between the various variables in glissade.  Specifically, thickness was advanced one dt in time relative to velocity and temperature in the output.  This has been fixed by reordering when various calculations are made.  At the highest level, the new order is: 1. evolve column temperature, 2. evolve thickness/tracer advection, 3. diagnostic solve of velocity (and other stuff).

I have tested both glissade and glide to confirm that answers change only in the expected way due to the reordering.  With constant temperature or no temperature evolution, this means the same values just occur at a different time level of the output for some variables (for e.g. thickness, velocity).  With a changing temperature fields, there are some small changes to the answers.



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1468 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 8a68ba07111e4fabf6250fafdfa2173b29b77ae7
The comment lines were too long and did not compile on PGI with default settings or -Mextend. I edited these lines to compile with existing scripts for PGI.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1470 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: cc5564b18ad44370c9981e4a7ddeb7835e2c62ef
Shortened some long lines in glimmer_ncio.F90 to make some compilers
happy (mod from Bill Lipscomb, previously implemented in cism1 repo
within cesm).

Fixed memory leak in glint_climate.F90 (previously implemented in
cism1 repo within cesm).

git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1471 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: fb47f11f3ce680ed593ec12e085d8054b39e32c1
Changing the error message to something more informative.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1474 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 22380a93c2b24f983ac5c6d2a33d0eb3db59c40b
Included here are "cyclic" BC's. When there is ice on the edge, I get the same problem as closed BC's for 1 and 2 processors where something is going wacky in the trilinos solver and breaking. But for 4 or more processors, things seem to work well with the exception that conservation is broken. I think conservation is mainly broken because the ice profile isn't truly cyclic as I'm initializing it. But with no ice at the edges, it gives the same answer as before, so no harm to the cases we're running in this commit. 


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1475 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 9e26ff95c8f5e1dec4ecbfcbe68e2888e02edeba
In this commit, I improved the MPI implementation for cyclic boundaries for correctness and keeping from hangs, and I added routines to remap staggered thickness and staggered mask. This appears to solve *some* of my problems but not all of them. 


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1476 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: e2a94f7da3b85259702f38fac9eea19e1d15cf8b
Changed this build script to work with the cmake build.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1477 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 17c811b178b857b5a16b8d5450cc6c08e0c519d0
Added dycore interface sources to dependency list for dycoretoglimmer library build.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1478 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 9bcb4bdf87337116fdd94822e414a80fa1fd56f2
This is not a long term solution, but until I figure out how to automagically switch the glimmer_horiz_bcs.F90 that uses mpi for a version that does not (for a serial build), this is a non-automatic way to do it.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1480 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 7c9776a54bd50758f02ac2261aef503eb5e10d92
Adding warnings if you try to run the glide dycore with a parallel build and for the ADI and linear diffusion evolution schemes.  Some or all of these should become fatal errors at some point, but leaving them as warnings for now.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1484 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: e69d6e6efee738aadb1788adee7a9c7dc46ae413
Commenting out the use of HO_diagnostic and HO_prognostic in the glide dycore.  They can eventually be deleted.



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1485 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 18f203687adefa5c2fd21c4de7e18f059aec64bc
Using parallel_mpi.F90's comm variable instead of mpi_comm_world. Required for merging into CESM.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1486 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 81723a6c241a98c830b7c5c456d98a6d7e4f70a2
Modifying Makefile.am and filenames to allow automatic switching between serial and parallel versions of the glimmer_horiz_bcs module during configure based on the presence of the --enable-mpi flag.  

This probably breaks the cmake build!

1. Can anyone confirm this is the proper way to do this?
2. Can someone make a similar change for the cmake build system?




git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1487 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 4aaa010493b40efdf675bdd59b1cf79d3e651dcd
Checking in what I hope is a robust fix for the size(tempcor) issue in subroutine calcflwa.
I made tempcor an allocatable variable and allocated tempcor(size(flwa,1)).

Could someone at ORNL please check that this works on jaguar's gcc compiler?



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1488 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 3205cd46919101b76581cd4bc59d7f5baff8cf4e
Checking in my latest work on the finite-element solver (glissade_velo_higher.F90).

In glide_setup.F90 and glide_types.F90 I created a new dycore option.  The options are now
* DYCORE_GLIDE = 0 (the old Glimmer dycore),
* DYCORE_GLAM = 1 (the current seacism finite-difference solver), and
* DYCORE_GLISSADE = 2 (the new finite-element solver under construction).

The higher-order tests are still set to	use the glam dycore (dycore = 1).

In glide_types.F90 I removed the HO_DIAG and HO_PROG options, which are	no longer used.

I made very minor changes (comments and indentation) in a few other modules.



git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1489 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 35fc835cd838c5d984794ef4dd9cf754f3d4e5c9
Had a compilation error with the last commit because linearsolvetime and totallinearsolvetime were not declared. I took a guess here that it was desired to use the variables already declared in glam_strs2.F90, so I did a use only: from that module. It compiles now. I also added implicit none to the subroutines & functions of this module.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1490 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 6ca5b62810f326526b8bae3f4aa07b6ddf9e0fdf
Added a couple new routines for future horiz_bcs_calls. a couple more to come, and then I'll place the calls thorughout the code.


git-svn-id: https://svn-cism-model.cgd.ucar.edu/glimmer-cism2/branches/seacism@1491 2cfc7cc4-626f-0410-8325-f6cb4dace9bf

Former-commit-id: 1cad4bd46211e307e7ca584096d1271fdc4db1f7