Release notes for tiegcm1.93
June 3, 2010
The following summarizes changes to the TIEGCM model from
v1.92 (released 2/23/2009) to v1.93 (released 6/3/2010):
qinite.F : increase night-time ionization rates which is necessary
because the minimum electron density was removed in previous versions
dynamo.F subroutine threed: the E_lam wasn't mapped in the horizontal
plane which gave wrong results close to the geomagnetic equator at
higher pressure levels (as a consequence EXB drift was wrong)
efield.F in the mapping from magnetic to geographic grid real values
are put into integer w/o explicit conversion from real to integer.
This led to wrong mapping on 64-bit Linux systems.
addiag.F: Use glat(j) instead of float(j) in calculation of c2, sub calczg.
Sub calczg calculates gravity-varying geopotential (geometric height)
fft9.F: Add ntrigs argument to FFT99B call from sub FFT99
Weimer05 model:wei05sc.F: Fix error in f90 translation in sub interpol_quad
(see comments in wei05sc.F). Also add routines to work around non-ANSI
New namelist read parameter KP:
- KP can be specified either as a constant or multiple time-dependent values.
- If provided, empirical formulas will use the given KP to calculate CTPOTEN
Change calculation of the sun's location from dipole coordinates to apex.
- Update IGRF coefficients with IGRF11 in apex_subs.F
Option to write 4-byte floats or 8-byte doubles to secondary histories:
- New namelist input parameter SECH_NBYTE can be either 4 (to write
4-byte floats), or 8 (to write 8-byte doubles). Default is SECH_NBYTE = 4
Script changes to enable parallel runs on hao 64-bit Linux systems:
- Changes to tiegcm-linux.job and tgcm_config in the scripts directory.
- Add PGI/pgf90 MPI env vars to tiegcm-linux.job
- To build and execute an MPI run on a 64-bit Linux machine, set the
following in tiegcm-linux.job:
- set mpi = TRUE
- set nproc = 4 or 8
- Then execute "tiegcm-linux.job >! tiegcm-linux.out" as usual.
Minor changes to scripts/tiegcm-ibm.job to accomodate mpi=FALSE under AIX.
- Also minor change to imf.F for the same reason (4-byte vs 8-byte integers).
- Run to model time 366,0,0 (for non-leap years), or to 367,0,0 (for leap years)
This will be written to the history files as mtime 1,0,0 of the next year.
The 1,0,0 history can be used as the Source to start the following year.