🚀 go-pugleaf

Some additional commments about the fluid-structure interaction problem.

 . The static problem is an excellent candidate for domain decomposition - or
   substructuring as it was known in an earlier incarnation. The solution
   procedure I suggested is a simple form of domain decomposition with separate
   solvers for the fluid and structural domains and user-supplied programs for
   managing the interface conditions.

 . For the dynamic case the structural domain could be represented by its normal
   modes. What happens to the domain decomposition approach isn't clear but it
   might work. Any comments from out there?

 . An alternate approach might be to use Kron's method of tearing with the fluid
   and structural regions solved separately and the results (with corrections)
   pieced together. However, my knowledge of "tearing" is so limited that I
   can't speak reliably about it. Is anyone out there familiar enough with
   "tearing" to comment on this idea?

One of my reasons for this second poster is simply to raise the issue of domain
decomposition in this newsgroup again. A week ago I posted a request for
information about domain decomposition and got virtually no response. The one
response I did get was from within Boeing. Unfortunately, it seems that there is
little or no appreciation of the wide applicability of this approach. Having
said that, I'll take this opportunity to state my request again.

I am looking for domain decomposition information in three areas. To wit:

 . review and/or tutorial articles on domain decomposition methods
 . electronic newsletters devoted to domain decomposition
 . discussions and/or derivations of the Poincare-Steklov interface operators

Is there anyone out there that can provide information on these topics?

Happy trails !!
+---------------------------+--------------------------------------------+
| Larry Yeagley             |     "Life is just a long cul-de-sac."      |
| lry1219@cfdd42.boeing.com |                                            |
+---------------------------+--------------------------------------------+
|  The advice, opinions and mistakes expressed here are my own and       |
|  certainly not Boeing's.                                               |
+------------------------------------------------------------------------+