[Petsc-trilinos-discussion] Scope and requirements

[Bartlett, Roscoe A.]

Mike,

It might to facilitate the discussion if someone could construct a set of example use cases involving Trilinos and PETSc and demonstrate the problems associated with the status quo (which is very little coordination, common or compatible interfaces, etc.).  Have there been real application codes, university students, etc. that have complained or lamented that they have to chose Trilinos or PETSc and see a large investment in switching back and forth?  Note that a lot of application codes support Trilinos and PETSc data structures and solvers and can switch back and forth with just switches in their input files.  Obviously they have to do a lot of work to make this possible but they do it.  Are any of these people represented on this main list?

Also, if we are really serious about this, a mail list may not be sufficient for driving progress at some point.

-Ross

> -----Original Message-----
> From: petsc-trilinos-discussion-bounces at lists.mcs.anl.gov [mailto:petsc-
> trilinos-discussion-bounces at lists.mcs.anl.gov] On Behalf Of Heroux, Michael
> A
> Sent: Wednesday, November 20, 2013 1:46 PM
> To: petsc-trilinos-discussion at lists.mcs.anl.gov
> Subject: [Petsc-trilinos-discussion] Scope and requirements
> 
> It seems to me that we should start this discussion with scope and
> requirements.
> 
> What needs are we addressing?  What are the requirements?
> 
> Are we restricting our efforts to solvers?  Linear, nonlinear, eigen, transient,
> more?
> 
> What usage models are we supporting?
> 
> Mike
> _______________________________________________
> Petsc-trilinos-discussion mailing list
> Petsc-trilinos-discussion at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/petsc-trilinos-discussion