> I've been using your postprocessors "tigcmloc" and "tigcmproc" to
> get out various fields from TIEGCM runs I've done.  At least I
> THOUGHT they were TIEGCM runs.  But when I try to get back 
> 
> all are /FESEN/CGF95/LT****   where ****   is   2001, 2002, 2003, etc
> 						3001, 3002, 3003, etc
> 						6001, 6002, 6003, etc

Cassandra:

The *first* history of each run is TIGCM but all remaining
histories are TIEGCM. This is because when SOURCE is specified
the first OUTPUT hiory is always a copy of the requested SOURCE
history, including info re TIGCM or TIEGCM. You probably started
each run from a SOURCE history that is TIGCM, so that was copied
over to first OUTPUT history, e.g., 5:0:0 of LT2001. All remaining
histories in LT2001 (5:1-6:1) are TIEGCM. Then you continued the
run without giving SOURCE, so all histories on 2002 are also TIEGCM.
I have'nt checked the other volumes, but I bet the same thing 
happened there.

You should not have to remake these runs. You should be able to
look at ion drifts or epot from all but first histories of each
run with tigcmproc, however tigcmloc is a bit of a problem. What
you should do is just leave off the first history in tigcmloc
runs. This may make the plot look a bit weird, esp local time axis,
but it should work. But if what I think is true, then there is
no electric potential (and therefore ion drifts cannot be calculated)
on the first histories only, so they cannot be included in a plot
of those fields. 

If this is really a problem, maybe you could make
a single 6-min step run, specifying the TIGCM history as SOURCE,
specify START as 4,23,54 and writing a TIEGCM output history at 
5,0,0. Then use that for the 5,0,0 (first) history in tigcmloc.

--Ben