On Thursday 14 July 2005 03:51 pm, Jian Tao wrote:
> On Thursday 14 July 2005 02:19 pm, Jian Tao wrote:
> > Josh and I talked about the AIFReader today. We were thinking about
> > adding a parameter "internal_mesh_structure" to MeshReader, which could
> > be moved
>> A second thought about "internal_mesh_structure". It should be related to
> or replaced by the differencing scheme diff_method=FEM/FVM, which should be
> a parameter of UMDriver.
>> Since the MeshReader will be scheduled by UMDriver in the future, it will
> read mesh into the correct format with given diff_shceme. I will add a
> keyword diff_scheme in MeshReader's param.ccl to get AIFReader started.
Why is UMDriver going to schedule MeshReader? Can't it just call the
UMT_ReadMesh() function directly?
You may add the parameter to UMDriver directly if you want, though perhaps you
don't want to activate that thorn in your parameter files yet...
Cheers,
David