Hi Junchao,I tested by commenting out the AOApplicationToPetsc calls as you suggest, but it doesn’t work because it doesn’t maintain the proper order of the elements in the scattered vectors.I attach a modified version of the test code where I put elements into the global vector, then carry out the
Il giorno mer 15 apr 2020 alle ore 22:14 Mark Adams ha
scritto:
>
> Lots of these:
> [ 0]32 bytes VecCUDAAllocateCheck() line 34 in
> /autofs/nccs-svm1_home1/adams/petsc/src/vec/vec/impls/seq/seqcuda/
> veccuda2.cu
> [ 0]32 bytes VecCUDAAllocateCheck() line 34 in
> /autofs/nccs-svm1_home1/adams/p
Satish Balay writes:
>> Crossing over to dev discussion, I wish we could make these names more
>> standard, like the following predefined ones (see `make -p`).
>>
>> COMPILE.F = $(FC) $(FFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c
>> %.o: %.F
>> # recipe to execute (built-in):
>> $(COMPILE.F)
On Fri, 24 Apr 2020, Jed Brown wrote:
> I'd say yes, that's the right thing. These are vestigial remnants of
> the legacy make system.
>
> I believe PETSc doesn't use this anywhere internally, and thus can be
> removed. I don't know if the following patch would break any existing
> correct usag
On Fri, Apr 24, 2020 at 10:47 AM Antoine Côté
wrote:
> Hi,
>
> Thanks for the fast response! An array of Vec would indeed solve my
> problem. I just don't know how to allocate it. Say I have a Vec U of the
> right size (created with a DMDA), and nlc = 4 load cases. How should I
> allocate and ini
Hi,
Thanks for the fast response! An array of Vec would indeed solve my problem. I
just don't know how to allocate it. Say I have a Vec U of the right size
(created with a DMDA), and nlc = 4 load cases. How should I allocate and
initialize the array?
Best regards
_
I'd say yes, that's the right thing. These are vestigial remnants of
the legacy make system.
I believe PETSc doesn't use this anywhere internally, and thus can be
removed. I don't know if the following patch would break any existing
correct usage.
diff --git i/lib/petsc/conf/variables w/lib/pet
On Fri, Apr 24, 2020 at 4:34 AM Aldo Bonfiglioli
wrote:
> Hi there,
>
> the makefile I have been using for ages (up to 11.4) now fails with 12.5.
>
Yep, it is not that easy to reconstruct. I believe that the Fortran build
rule used to be generated by configure. We
stopped doing that, and added a
Hi there,
the makefile I have been using for ages (up to 11.4) now fails with 12.5.
I noticed that there have been several changes in
include $(PETSC_DIR)/lib/petsc/conf/variables
include $(PETSC_DIR)/lib/petsc/conf/rules
btw. the two aforementioned versions.
If I'm not wrong, *.F files shoul
