[CIG-MC] [Fwd: geoid in citcomS 2.2.1]

[Eh Tan]

Scott King reports that there is a bug in CitcomS geoid calculation. The 
buoyancy
contribution on geoid was not correctly zeroed before every geoid 
calculation.
This caused the geoid at former timestep accumulated over the later 
timestep.

This bug affects CitcomS v2.1.0, v2.2.0 and v2.2.1. A new release of CitcomS
containing a bug fix will be released soon. All user are encouraged to 
upgrade.


--
Eh Tan

Staff Scientist
Computational Infrastructure for Geodynamics
2750 E. Washington Blvd. Suite 210
Pasadena, CA 91107
(626) 395-1693
http://www.geodynamics.org




-------- Original Message --------
Subject: 	geoid in citcomS 2.2.1
Date: 	Tue, 12 Jun 2007 13:35:23 -0400
From: 	Scott King <sking at purdue.edu>
To: 	Eh Tan <tan2 at gps.caltech.edu>



Eh;

I *think* there is a problem with the geoid in the newest release.    
In "compute_geoid_from_buoyancy" there is a line

harm_geoid[0][p] += con1*con2*geoid[0][p]

It doesn't look like harm_geoid (which is really  
harm_geoid_from_bncy) ever gets re-zeroed at the beginning of a time  
step, so what I see is the geoid between timestep 0 and 2 and 4  
almost doubles each time I print it out.      Maybe I'm missing  
something.    My cluster is somewhere between here and Virginia, so I  
can't test this yet.

Cheers,

Scott