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

2017-12-19 Thread 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

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

2017-12-19 Thread 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 >

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

2017-12-19 Thread 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

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

2017-12-19 Thread 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

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

2017-12-19 Thread 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: >

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

2017-12-19 Thread 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

[petsc-dev] pnetcdf is a big problem

2017-12-19 Thread 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

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

2017-12-19 Thread 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

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

2017-12-19 Thread 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