On 22 March 2018 at 15:31, Matthew Knepley wrote:
> On Thu, Mar 22, 2018 at 8:28 AM, Jed Brown wrote:
>>
>
> What I imagined was just mapping each Petsc typedef (do we list them all
> anywhere),
> to an MPI type, creating those that are missing (as we do for
On Thu, 22 Mar 2018, Smith, Barry F. wrote:
> This was all fine in the past for prefix builds on the Mac all the
> recent messing around broke it.
>
>Is there a branch that fixes the problem or has the problem just been
> commented on for a few days?
This issue is with changes
On Thu, 22 Mar 2018, Satish Balay wrote:
> On Thu, 22 Mar 2018, Smith, Barry F. wrote:
>
> >
> > Satish,
> >
> >Where did you find this error message on the web? I couldn't find any
> > building of the manual from the Dashboard.
> >
>
> per src/docs/tex/manual/makefile
>
> # Run
On Thu, 22 Mar 2018, Smith, Barry F. wrote:
>
> Satish,
>
>Where did you find this error message on the web? I couldn't find any
> building of the manual from the Dashboard.
>
per src/docs/tex/manual/makefile
# Run make manual.pdf LOC=$PETSC_DIR GONULL="" to display all the error
I've pushed this fix to master.
Satish
On Thu, 22 Mar 2018, Satish Balay wrote:
> >
> petsc@thwomp:/sandbox/petsc/petsc.clone/src/docs/tex/manual$ /usr/bin/make
> --no-print-directory manual.pdf LOC=/sandbox/petsc/petsc.clone GONULL=
>
>
> aTeX Warning: Reference `ch_index' on page
Satish,
Where did you find this error message on the web? I couldn't find any
building of the manual from the Dashboard.
> On Mar 22, 2018, at 11:05 AM, Balay, Satish wrote:
>
>>
> petsc@thwomp:/sandbox/petsc/petsc.clone/src/docs/tex/manual$ /usr/bin/make
Thanks! I should have caught this myself by rebuilding all my local docs
instead of just the manual.
2018-03-22 17:05 GMT+01:00 Satish Balay :
> >
> petsc@thwomp:/sandbox/petsc/petsc.clone/src/docs/tex/manual$
> /usr/bin/make --no-print-directory manual.pdf
>
I'll talk to Satish, it is now unclear (at least to me) where the manual is
actually built and the output stored.
> On Mar 22, 2018, at 5:17 AM, Patrick Sanan wrote:
>
> The manual and dev manual automated builds are failing on master, but I can't
> reproduce on
On Thu, Mar 22, 2018 at 11:45 AM, Saurabh Chawdhary
wrote:
> Thank you Tobin. I was actually more interested in repartitioning after
> the mesh has been dynamically changed (say, after refinement in certain
> portions of mesh).
>
That kinds of repartitioning in p4est is
Thank you Tobin. I was actually more interested in repartitioning after
the mesh has been dynamically changed (say, after refinement in certain
portions of mesh).
On 03/22/2018 07:10 AM, Tobin Isaac wrote:
On March 21, 2018 11:26:35 AM MDT, Saurabh Chawdhary wrote:
On Thu, Mar 22, 2018 at 8:28 AM, Jed Brown wrote:
> Matthew Knepley writes:
>
> > On Thu, Mar 22, 2018 at 7:09 AM, Jed Brown wrote:
> >
> >> Matthew Knepley writes:
> >>
> >> > On Thu, Mar 22, 2018 at 6:15 AM,
Matthew Knepley writes:
> On Thu, Mar 22, 2018 at 7:09 AM, Jed Brown wrote:
>
>> Matthew Knepley writes:
>>
>> > On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin
>> wrote:
>> >
>> >> On 22 March 2018 at 12:51, Matthew
On Thu, Mar 22, 2018 at 7:09 AM, Jed Brown wrote:
> Matthew Knepley writes:
>
> > On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin
> wrote:
> >
> >> On 22 March 2018 at 12:51, Matthew Knepley wrote:
> >> > On Thu, Mar
On March 21, 2018 11:26:35 AM MDT, Saurabh Chawdhary wrote:
>Hello team,
>
>I haven't used petsc since DMFOREST was released but I have a question
>regarding repartitioning of DMFOREST mesh. How is the repartitioning of
>
>mesh over processors done after some mesh
Matthew Knepley writes:
> On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin wrote:
>
>> On 22 March 2018 at 12:51, Matthew Knepley wrote:
>> > On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin
>> wrote:
>> >>
>> >>
>>
On Thu, Mar 22, 2018 at 6:09 AM, Lawrence Mitchell wrote:
> > On 22 Mar 2018, at 09:47, Matthew Knepley wrote:
> >
> > On Wed, Mar 21, 2018 at 10:00 PM, Satish Balay
> wrote:
> > Works for me..
> >
> > Well, I am not kidding when I say it
On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin wrote:
> On 22 March 2018 at 12:51, Matthew Knepley wrote:
> > On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin
> wrote:
> >>
> >>
> >> ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
The manual and dev manual automated builds are failing on master, but I
can't reproduce on any of my local builds and the output is now very terse,
so it's not obvious to me how to debug. There were some updates recently to
the manual make process, which could be related.
I'd move to re-introduce
On 22 March 2018 at 12:51, Matthew Knepley wrote:
> On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin wrote:
>>
>>
>> ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/21/examples_master_arch-linux-cxx-cmplx-pkgs-64idx_churn.log
>>
>> The thing is,
> On 22 Mar 2018, at 09:47, Matthew Knepley wrote:
>
> On Wed, Mar 21, 2018 at 10:00 PM, Satish Balay wrote:
> Works for me..
>
> Well, I am not kidding when I say it fails for me. How do I debug this?
Is the problem that urllib.urlretrieve fails for
On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin wrote:
> ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/03/21/examples_master_arch-linux-cxx-cmplx-pkgs-64idx_churn.log
>
> The thing is, PETSc does not currently have a way of mapping a plain C
> `int` type to a
On Wed, Mar 21, 2018 at 10:00 PM, Satish Balay wrote:
> Works for me..
>
Well, I am not kidding when I say it fails for me. How do I debug this?
Matt
> Satish
>
>
>
> On linux:
>
> balay@asterix /home/balay/petsc (master=)
> $ ./configure --download-gmp
On 22 March 2018 at 11:10, Lisandro Dalcin wrote:
> On 22 March 2018 at 10:44, Lisandro Dalcin wrote:
>>
>> @Barry or anyone: the only issue for me is to decide on the name, I'll
>> call it PETSC_C_INT (and maybe also add PETSC_C_LONG along the way).
>> If
On 22 March 2018 at 10:44, Lisandro Dalcin wrote:
>
> @Barry or anyone: the only issue for me is to decide on the name, I'll
> call it PETSC_C_INT (and maybe also add PETSC_C_LONG along the way).
> If you don't like and have a better naming convention to suggest,
> please let
ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/21/examples_master_arch-linux-cxx-cmplx-pkgs-64idx_churn.log
The thing is, PETSc does not currently have a way of mapping a plain C
`int` type to a PETSc datatype. I'm wiling to take the required work
to fix this issue.
@Barry or
25 matches
Mail list logo