[petsc-dev] petsc release soon

[Stefano Zampini]

The same test should be used to run also other MATIS based preconditioners
as PCNN. I think PCNN is broken into petsc-dev (it doesn't preallocate for
coarse matrix if I remember well)

Regarding roughness/portability of PCBDDC: please let me know which parts
of code should I improve so I can put them in my todo list.

2012/3/13 Jed Brown <jedbrown at mcs.anl.gov>

> The code is still pretty rough/not entirely portable, so I don't think we
> will turn it on by default. Having a runable example is important. If you
> want to get it ready, I would try to do it in the next week or so.
> On Mar 13, 2012 8:15 AM, "Stefano Zampini" <stefano.zampini at gmail.com>
> wrote:
>
>> Are you planning to include pcbddc in the next release?
>>
>> It works, but some parts of PCBDDC code are not fully developed as we
>> decided with Jed (primarly, the MatPartitioning procedure for multilevel).
>>
>> In case you want to include it into the next release, how many days I
>> have to work on the code until the release ?
>>
>> 2012/3/12 Jed Brown <jedbrown at mcs.anl.gov>
>>
>>> On Mon, Mar 12, 2012 at 14:40, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>>
>>>>  I still like including the private in the name since it makes clear
>>>> they are private include files.
>>>
>>>
>>> Cool, glad that's out of the way.
>>>
>>> Now about namespacing all the variables in the makefiles. This is an
>>> opportunity to clarify/normalize variable names. I don't know what
>>> SL_LINKER is, for example.
>>>
>>> Also, should there be an "exported" version that makes some of the PETSC
>>> symbols public? (I think so, even just for internal use, because I don't
>>> want to type ${PETSC_MPIEXEC}, ${PETSC_DIFF}, ${PETSC_PYTHON}, etc in all
>>> the makefiles.)
>>>
>>
>>
>>
>> --
>> Stefano
>>
>


-- 
Stefano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120313/2b15aa1c/attachment.html>