Hi Eh,

If this is hard to fix, then this should be low priority. Mark Turner and
I can obviously work around this problem.

Mike

>
> Eh Tan <tan2@geodynamics.org> added the comment:
>
> It will be hard to fix.
>
> The pid file is written very early in the setup stage. When the coor_file
> is
> read in (and the correct values of radius_outer, radius_inner, theta_min,
> theta_max, fi_min, are fi_max are defined), the pid file is written
> already.
>
> I can disable the output of those parameters when coor=1 to avoid the
> confusion.
> But the user will still need to write a code to find out the correct
> values of
> radius_outer, radius_inner, theta_min, theta_max, fi_min, are fi_max.
>
> ----------
> assignedto:  -> tan2
> nosy: +tan2 -root
>
> _____________________________________________________
> Roundup issue tracker <issue_tracker@geodynamics.org>
> <http://geodynamics.org/roundup/issues/issue82>
> _____________________________________________________
>

It will be hard to fix.

The pid file is written very early in the setup stage. When the coor_file is
read in (and the correct values of radius_outer, radius_inner, theta_min,
theta_max, fi_min, are fi_max are defined), the pid file is written already.

I can disable the output of those parameters when coor=1 to avoid the confusion.
But the user will still need to write a code to find out the correct values of
radius_outer, radius_inner, theta_min, theta_max, fi_min, are fi_max.

For CitcomS for regional models, when coor = 1
 a coordinate file is read in with minimum and maximum coordinates in 3
directions. However, these limits do not change the variables in the codes that
are output in the pid file, such as 
[CitcomS.solver.mesher]
radius_outer=1.000000
radius_inner=0.550000
theta_min=1.070800
theta_max=2.070800
fi_min=0.000000
fi_max=1.000000

Essentially, the default values continue to get output and are incocnisistent
with the coor file.