dorsal team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Wed, Mar 07, 2012 at 04:24:13PM +0100, Fredrik Heffer Valdmanis wrote:
> >
> > I am interested in this, but I am going to wait until after Dorsal is
> >> thoroughly tested to build FEniCS 1.0.
> >>
> >> There are lot of other interesting things waiting to be merged too,
> >> including support for Intel compilers and the ability to build other
> >> FEMy projects like Deal.II and Dune. Everything in good time.
> >>
> >> Thanks. I was a bit unclear in my previous email, I wasn't hoping for a
> > merge anytime soon. What I wanted to know is what you think about this way
> > of doing it? Do you have any suggestions for improvements? It would be good
> > for me to improve on the design so that it is more or less ready for
> > merging when my Dolfin code gets released sometime in the distant future.
> > If the timing is bad we can discuss it later, I just wanted to air my
> > thoughts about it :)
> >
> > Garth, I see your point about the complications. That requires some
> > thinking.
> >
>
> >
> I think it might be a good time to bring this thread up again now. My
> Dorsal branch is still working fine, but there are a couple of issues that
> should be discussed before merging:
>
> 1: As mentioned in my first email, the user has to set "default
> CUDA_DIR=<path to cuda installation>" in the platform file, and add the
> packages cusp and thrust to the beginning of the list of packages to build
> PETSc with Cusp support. This might not be the best way to solve this. One
> could of course set CUDA_DIR in dorsal/local.cfg instead, but the list of
> packages to install still has to be modified. Any opinions? Could this be
> (semi) automated?

How about making a new package file called petscwithcuda or petsc-cuda or
whatever naming schem Harish suggests.

I think it is OK to require the user to set the environment variable
CUDA_DIR before running Dorsal, either as part of the user's
environment setup or in local.cfg.

> 2: Thrust and Cusp only comes packaged in .zip-files, which Dorsal doesn't
> support as far as I can see. To get around this this, {thrust,
> cusp}.package currently pull the latest hg repositories from Google Code.
> To make these development versions play nice with petsc-3.2-p6, I have had
> to add a patch to PETSc. A possible solution would be to package stable
> versions of cusp and thrust ourselves and host them on
> fenicsproject.org. PETSc-dev
> works fine with these development versions, so we can skip the patching
> once 3.2-p7 is released.

I don't fully understand. Are there stable Thrust and Cusp packages
available which work with stable PETsc?

--
Anders


> My branch could be merged into Dorsal trunk anytime, but I am happy to make
> changes if you have any suggestions for improvements.
>
> It's still at lp:~fredva/dorsal/dorsal-gpu.




> _______________________________________________
> Mailing list: https://launchpad.net/~dorsal
> Post to     : dorsal@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dorsal
> More help   : https://help.launchpad.net/ListHelp