If no problem type is specified in .config file, "EISMINT" error occurs about cism HOT 2 OPEN

From @whlipscomb on July 28, 2015 23:11

@matthewhoffman , I've never liked this old Glimmer feature. My preference would be (1): If no problem type is supplied by the user, then the model runs on without doing anything special.

from cism.

From @DanFMartin on July 29, 2015 4:52

I'd concur with Bill -- One of the issues we ran into when coupling CISM
to BISICLES and running our own problems was figuring out what the
problem type needed to be when we were setting up our own problems. At
some point in the process, things changed under us, and I had to just
try various problem types until I found one which worked again.

A generic problem type would have simplified that.

Dan

On 07/28/2015 04:11 PM, William Lipscomb wrote:

@matthewhoffman https://github.com/matthewhoffman , I've never liked
this old Glimmer feature. My preference would be (1): If no problem type
is supplied by the uses, then the model runs on without doing anything
special.

—
Reply to this email directly or view it on GitHub
https://github.com/ACME-Climate/cism-piscees/issues/38#issuecomment-125778630.

Dan Martin email: [email protected]
Mail Stop 50A-1148 phone: (510) 495-2852
Lawrence Berkeley National Laboratory fax: (510) 486-6900
1 Cyclotron Rd.
Berkeley, CA 94720

from cism.