Setting of Workset Size in input file for ATO::2Matl tests does not appear to be working about albany HOT 7 CLOSED

I think you should consider it a separate bug that you get a different answer with a different workset size. Is there any known reason why workset size could affect results at all ? Anyway, I'll look at the input parameter issue.

from albany.

I agree. This is a question for @jrobbin, the author of ATO. I'll take this up with him. It looks to me like the solutions are slightly off in the 4th decimal point with the different workset size. I don't know enough about the physics and gold file to say if this is significant and why this is workset dependent. If you could look at the input issue for now, that would be great. We want the user to be able to control the workset size from the input file for all physics in Albany, if this is desired.

from albany.

from albany.

Why are these tests only active if Albany is not in 64-bit mode ? This is the fifth time I've had to rebuild Albany trying to compile ATO...

from albany.

@jrobbin is the author of ATO and the one who put in that logic so he can best answer this question. My guess is the logic was put in as a precaution, since the original Epetra-only code was not meant to run for huge problem requiring 64-bit int GOs. I will check if the examples can be activated in a 64-bit build, and turn them on there, if they work. Sorry for the frustrations this is causing, @ibaned ....

from albany.

@ikalash it looks like the parameter was just in the wrong place in the input file. ATO is confusing because it has "Discretization" lists for all the subproblems, and then a separate one outside of "Problem". Commit 04592a5 should fix this.

from albany.

I see -- I missed this detail. Thanks for fixing it, @ibaned !

from albany.