[petsc-dev] petsc release soon

[Matthew Knepley]

This looks broken:

virsaug.c: In function 'SNESSolveVI_SS':

                                                 virsaug.c:784: error:
'struct _SNESOps' has no member named 'computefunction'

                          virsaug.c:785: error: 'struct _SNESOps' has no
member named 'computefunction'

  virsaug.c:807: error: 'struct _SNESOps' has no member named
'computefunction'

virsaug.c:828: error: 'struct _SNESOps' has no member named
'computefunction'

virsaug.c:883: error: 'struct _SNESOps' has no member named
'computefunction'

virsaug.c:916: error: 'struct _SNESOps' has no member named
'computefunction'



                                    ('ERROR: Missing object file',
'virsaug.o')

Am I missing something?

   Matt

On Tue, Mar 13, 2012 at 8:47 AM, Stefano Zampini
<stefano.zampini at gmail.com>wrote:

> 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
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120313/a62d4328/attachment.html>