cape-open compliant interface for sundials ?

View: New views
1 Messages — Rating Filter:   Alert me  

cape-open compliant interface for sundials ?

by by way of Carol Woodward <cswoodward@llnl.gov> :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


From: "Ian Washington" <idwashin@...>
To: <sundials-users@...>
Subject: cape-open compliant interface for sundials ?
Date: Fri, 11 Sep 2009 01:47:20 -0400
Organization: University of Waterloo
Message-ID: <000001ca32a3$5cf700f0$16e502d0$@...>
MIME-Version: 1.0

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01CA3281.D5E560F0
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello Sundials users,



I was wondering if anyone has created the necessary wrappers for the
Sundials solvers, so that they could be used within CAPE-OPEN compliant
software. I would like to use the Sundials solvers in high end process
modeling languages like gPROMS or Aspen Custom Modeler. If anyone has
developed the necessary interfaces and would be willing to share, it would
be very much appreciated.  Of course, I could develop the interface myself,
but first I thought I'd ask the expert users out there if anyone has any
previous experiences or advice.



Thanks,



Ian.


------=_NextPart_000_0001_01CA3281.D5E560F0
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Sundials users,



I was wondering if anyone has created the necessary wr= appers for
the Sundials solvers, so that they could be used within CAPE-OPEN
compl= iant software. I would like to use the Sundials solvers in
high end process mode= ling languages like gPROMS or Aspen Custom
Modeler. If anyone has developed the = necessary interfaces and would
be willing to share, it would be very much appreciated= .  Of course,
I could develop the interface myself, but first I thought I'd= ask
the expert users out there if anyone has any previous experiences or advice= .



Thanks,



Ian.

------=_NextPart_000_0001_01CA3281.D5E560F0--