Re: [petsc-dev] pnetcdf is a big problem

[Smith, Barry F.]

> On Dec 19, 2017, at 5:30 PM, Jed Brown  wrote:
> 
> Does ExodusII write pnetcdf?  It's a different interface from (parallel)
> NetCDF4.

   Shudder!

> 
> Matthew Knepley  writes:
> 
>> Blaise really wants to write in parallel. It would be better to use HDF5,
>> but evidently
>> it is broken in ExodusII. Thats what we get for using something from
>> Sandia. They
>> finally have their revenge.
>> 
>>   Matt
>> 
>> On Tue, Dec 19, 2017 at 5:53 PM, Smith, Barry F.  wrote:
>> 
>>> 
>>>  Do you really need to use pnetcdf? No one uses it and what usefulness
>>> does it really provide, best to be avoided.
>>> 
>>>   Barry
>>> 
>>> 
 On Dec 19, 2017, at 1:12 PM, Satish Balay  wrote:
 
 parallel-netcdf-1.9.0.pre1/INSTALL has:
 
>>> 
 
 4. Reporting Installation or Usage Problems
 ===
 
 Please send an email to parallel-net...@mcs.anl.gov
 
 <<
 
 We'll have to send in these bug reports.
 
 Satish
 
 
 On Tue, 19 Dec 2017, Matthew Knepley wrote:
 
> The configure is broken, perhaps beyond fixing. I need to give
>>> --with-mpi
> to get anything
> to work because the way it checks for MPI is screwed up. I will see if I
> can throw away all its idiotic configure stuff in favor of just telling
>>> it
> everything, but I am not eager to depend on something so rickety.
> 
>  Matt
> 
> 
 
>>> 
>>> 
>> 
>> 
>> -- 
>> 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
>> 
>> https://www.cse.buffalo.edu/~knepley/ 

Re: [petsc-dev] pnetcdf is a big problem

[Jed Brown]

Does ExodusII write pnetcdf?  It's a different interface from (parallel)
NetCDF4.

Matthew Knepley  writes:

> Blaise really wants to write in parallel. It would be better to use HDF5,
> but evidently
> it is broken in ExodusII. Thats what we get for using something from
> Sandia. They
> finally have their revenge.
>
>Matt
>
> On Tue, Dec 19, 2017 at 5:53 PM, Smith, Barry F.  wrote:
>
>>
>>   Do you really need to use pnetcdf? No one uses it and what usefulness
>> does it really provide, best to be avoided.
>>
>>Barry
>>
>>
>> > On Dec 19, 2017, at 1:12 PM, Satish Balay  wrote:
>> >
>> > parallel-netcdf-1.9.0.pre1/INSTALL has:
>> >
>> 
>> >
>> > 4. Reporting Installation or Usage Problems
>> > ===
>> >
>> > Please send an email to parallel-net...@mcs.anl.gov
>> >
>> > <<
>> >
>> > We'll have to send in these bug reports.
>> >
>> > Satish
>> >
>> >
>> > On Tue, 19 Dec 2017, Matthew Knepley wrote:
>> >
>> >> The configure is broken, perhaps beyond fixing. I need to give
>> --with-mpi
>> >> to get anything
>> >> to work because the way it checks for MPI is screwed up. I will see if I
>> >> can throw away all its idiotic configure stuff in favor of just telling
>> it
>> >> everything, but I am not eager to depend on something so rickety.
>> >>
>> >>   Matt
>> >>
>> >>
>> >
>>
>>
>
>
> -- 
> 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
>
> https://www.cse.buffalo.edu/~knepley/ 

Re: [petsc-dev] pnetcdf is a big problem

[Matthew Knepley]

Blaise really wants to write in parallel. It would be better to use HDF5,
but evidently
it is broken in ExodusII. Thats what we get for using something from
Sandia. They
finally have their revenge.

   Matt

On Tue, Dec 19, 2017 at 5:53 PM, Smith, Barry F.  wrote:

>
>   Do you really need to use pnetcdf? No one uses it and what usefulness
> does it really provide, best to be avoided.
>
>Barry
>
>
> > On Dec 19, 2017, at 1:12 PM, Satish Balay  wrote:
> >
> > parallel-netcdf-1.9.0.pre1/INSTALL has:
> >
> 
> >
> > 4. Reporting Installation or Usage Problems
> > ===
> >
> > Please send an email to parallel-net...@mcs.anl.gov
> >
> > <<
> >
> > We'll have to send in these bug reports.
> >
> > Satish
> >
> >
> > On Tue, 19 Dec 2017, Matthew Knepley wrote:
> >
> >> The configure is broken, perhaps beyond fixing. I need to give
> --with-mpi
> >> to get anything
> >> to work because the way it checks for MPI is screwed up. I will see if I
> >> can throw away all its idiotic configure stuff in favor of just telling
> it
> >> everything, but I am not eager to depend on something so rickety.
> >>
> >>   Matt
> >>
> >>
> >
>
>


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

https://www.cse.buffalo.edu/~knepley/ 

Re: [petsc-dev] pnetcdf is a big problem

[Smith, Barry F.]

  Do you really need to use pnetcdf? No one uses it and what usefulness does it 
really provide, best to be avoided.

   Barry


> On Dec 19, 2017, at 1:12 PM, Satish Balay  wrote:
> 
> parallel-netcdf-1.9.0.pre1/INSTALL has:
> 
 
> 
> 4. Reporting Installation or Usage Problems
> ===
> 
> Please send an email to parallel-net...@mcs.anl.gov
> 
> <<
> 
> We'll have to send in these bug reports.
> 
> Satish
> 
> 
> On Tue, 19 Dec 2017, Matthew Knepley wrote:
> 
>> The configure is broken, perhaps beyond fixing. I need to give --with-mpi
>> to get anything
>> to work because the way it checks for MPI is screwed up. I will see if I
>> can throw away all its idiotic configure stuff in favor of just telling it
>> everything, but I am not eager to depend on something so rickety.
>> 
>>   Matt
>> 
>> 
> 

Re: [petsc-dev] pnetcdf is a big problem

[Satish Balay]

parallel-netcdf-1.9.0.pre1/INSTALL has:

>>>

4. Reporting Installation or Usage Problems
===

Please send an email to parallel-net...@mcs.anl.gov

<<

We'll have to send in these bug reports.

Satish


On Tue, 19 Dec 2017, Matthew Knepley wrote:

> The configure is broken, perhaps beyond fixing. I need to give --with-mpi
> to get anything
> to work because the way it checks for MPI is screwed up. I will see if I
> can throw away all its idiotic configure stuff in favor of just telling it
> everything, but I am not eager to depend on something so rickety.
> 
>Matt
> 
> 

Re: [petsc-dev] pnetcdf is a big problem

[Matthew Knepley]

On Tue, Dec 19, 2017 at 1:54 PM, Matthew Knepley  wrote:

> The configure is broken, perhaps beyond fixing. I need to give --with-mpi
> to get anything
> to work because the way it checks for MPI is screwed up. I will see if I
> can throw away all its idiotic configure stuff in favor of just telling it
> everything, but I am not eager to depend on something so rickety.
>

Satish, can you go down to Rajiv's office and tell him that he makes too
much money to have a hopelessly broken configure? I should not be fixing
his broken crap.

Matt


>Matt
>
> --
> 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
>
> https://www.cse.buffalo.edu/~knepley/ 
>



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

https://www.cse.buffalo.edu/~knepley/ 

[petsc-dev] pnetcdf is a big problem

[Matthew Knepley]

The configure is broken, perhaps beyond fixing. I need to give --with-mpi
to get anything
to work because the way it checks for MPI is screwed up. I will see if I
can throw away all its idiotic configure stuff in favor of just telling it
everything, but I am not eager to depend on something so rickety.

   Matt

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

https://www.cse.buffalo.edu/~knepley/ 

Re: [petsc-dev] [SPAM *****] Re: Issue with Lapack names

[Jose E. Roman]

> El 18 dic 2017, a las 22:34, Karl Rupp  escribió:
> 
> 
> 
>> > > This is related to a message I sent 2 years ago to petsc-maint
>>"Inconsistent naming of one Lapack subroutine", where I advocated
>>renaming LAPACKungqr_ --> LAPACKorgqr_. But that thread did not end
>>up in any modification...
>> > >
>> > > I can't find the thread. I also do not understand the problem.
>>Are you saying that the check succeeds but the routines is still
>>missing?
>> >
>> > No, the opposite. The routines are there, but since configure
>>decided (wrongly) that they are missing, the check would fail at run
>>time complaining that the routines are missing.
>> >
>> > Ah. Why does the check fail? It does succeed for a number of them.
>>I don't know the exact reason, but it has to do with the names of
>>real/complex subroutines. I guess the test is checking for dungqr,
>>which does not exist - it should check for either dorgqr or zungqr.
>>Before that commit, there were only checks for "real" names, but
>>after the commit there are a mix of real and complex subroutines.
>> Now I really want to punch one of the LAPACK guys in the face. Which one...
>> Karl, I think it is enough right now to change the complex names, like ungqr 
>> to orgqr as Jose suggests. Will this work for you?
> 
> works for me, yes.
> If possible, I'd like to preserve the auto-generated nature of this list. If 
> 'dungqr' is the only exception, then please adjust the list of tests 
> accordingly *and* add a comment to BlasLapack.py saying why 'dungqr' is 
> special.
> 
> Best regards,
> Karli
> 

I have created a pull request for this.
https://bitbucket.org/petsc/petsc/pull-requests/826/fix-test-for-missing-lapack-subroutines/diff
Jose


> 
> 
>> >
>> >   Thanks,
>> >
>> > Matt
>> >
>> > Jose
>> >
>> > >
>> > >   Thanks,
>> > >
>> > >  Matt
>> > >
>> > >
>> > > Jose
>> > > --
>> > > 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
>> > >
>> > > https://www.cse.buffalo.edu/~knepley/
>>
>> >
>> >
>> >
>>>
>>> --
>>> 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
>>>
>>> https://www.cse.buffalo.edu/~knepley/
>>
>> -- 
>> 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
>> https://www.cse.buffalo.edu/~knepley/ 

Re: [petsc-dev] Add links to implementations from manual pages

[Patrick Sanan]

Thanks, Barry! I think in terms of quick usefulness this is a great one and
I'll try to get it done soon.



2017-12-18 13:08 GMT-08:00 Smith, Barry F. :

>
>Patrick,
>
>  Automatically adding links to the manual pages to implementations is
> actually pretty straight forward. In lib/petsc/conf/rules look at, for
> example,
> manconcepts. You can just make a copy of that and have it use something
> like
>
> git grep -n "^PetscErrorCode MatMult_"
>
> to generate the files and line numbers for all implementations and plop
> them into the manual page. It maybe require some tuning to get the ones you
> want but not the other ones. But remember don't let the perfect prevent the
> useful.
>
> Questions?
>
> Good luck,
>
> Barry
>
> This is how we build the manual pages. Unix style, many small utilities
> that add stuff to the manual pages. Not one big honking script that tries
> to do everything for the manual pages.
>
>
>
>
>