[petsc-dev] Googling PetscMatlabEngine leads to 3.7 version

Googling PetscMatlabEngine leads to 3.7 version but PetscMatlabEngineDestroy leads to 3.13. Any idea why some of the manual pages don't point to the latest version? Barry

Re: [petsc-dev] Googling PetscMatlabEngine leads to 3.7 version

. Barry > On Jun 8, 2020, at 11:41 PM, Pierre Jolivet > wrote: > > Googling PCMG is no fun either (and there is no actual reference to the > current man page). > > Thanks, > Pierre > > > > >> On 9 Jun 2020, at 2:27 AM, Barry Smith > <mailto

Re: [petsc-dev] Googling PetscMatlabEngine leads to 3.7 version

tsc-current >> and petsc4py-current >> >> Wrt PetscMatlabEngine - duckduckgo finds >> https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/PETSC_MATLAB_ENGINE_.html >> >> <https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/PETSC_M

[petsc-dev] https://developer.nvidia.com/nccl

[petsc-dev] bash scripts to make PETSc development easier, less recompiles, less cut and pastes

A long time ago Oana asked me how come when you switched back to a previously built branch it sometimes had to recompile the libraries and could it be smart enough to use touch in some way to not have to recompile. So I made a bash script that automatically changed PETSC_ARCH with branch cha

[petsc-dev] Prediscusion of appropriate communication tool for discussion of PETSc 4 aka the Grand Refactorization

I'd like to start a discussion of PETSc 4.0 aka the Grand Refactorization but to have that discussion we need to discuss what tool to use for that discussion. So this discussion is not about PETSc 4.0, please don't discuss it here. What do people recommend to use for the discussion

Re: [petsc-dev] bash scripts to make PETSc development easier, less recompiles, less cut and pastes

> https://docs.gitlab.com/ce/user/project/push_options.html#push-options-for-merge-requests > > <https://docs.gitlab.com/ce/user/project/push_options.html#push-options-for-merge-requests> > > Barry Smith mailto:bsm...@petsc.dev>> writes: > >> A

Re: [petsc-dev] Prediscusion of appropriate communication tool for discussion of PETSc 4 aka the Grand Refactorization

t;>> 1. genuinely open to external participants, >>> 2. more async-friendly for those in different timezones and folks with >>> young kids, and >>> 3. searchable and externally linkable (e.g., from merge requests and issues) >>> >>> If we need sync

Re: [petsc-dev] Prediscusion of appropriate communication tool for discussion of PETSc 4 aka the Grand Refactorization

>> project status to activate it). I don't know if that feature helps >> facilitate what you envision. If using present features, I would have one >> outline issue and an issue for each major component. I'd rather not create a >> new repository. The institutional

Re: [petsc-dev] Prediscusion of appropriate communication tool for discussion of PETSc 4 aka the Grand Refactorization

could do so, but there should be a > summary back for those who couldn't participate synchronously. > > Barry Smith mailto:bsm...@petsc.dev>> writes: > > >I'd like to start a discussion of PETSc 4.0 aka the Grand > > Refactorization but to have that

[petsc-dev] make libs and make test do not run in parallel

while make all and make alltests do run in parallel. Is this intentional?

[petsc-dev] Release of communication system for discussion petsc-future

After our prediscussion on software tools for a discussion on future design plans for PETSc I have started to set up GitLab issues in the PETSc project to manage the discussion. They begin with https://gitlab.com/petsc/petsc/-/issues/643 Ea

[petsc-dev] Getting .gitlab.ci file out of repository? https://docs.gitlab.com/ee/ci/pipelines/settings.html

Should we get the .gitlab.ci yaml file out of the repository so people don't need to constantly monkey around with rebasing etc when something needs to change in the file? Seems to be number of ways of having out of the repository. What about the the examples/arch*.py files? Do we ha

Re: [petsc-dev] Getting .gitlab.ci file out of repository? https://docs.gitlab.com/ee/ci/pipelines/settings.html

handles both maint and master.] > > However - in some sense - the ability to modify .gitlab.ci in any feature > branch is not a good thing.. > > Satish > > On Mon, 22 Jun 2020, Barry Smith wrote: > >> >> Should we get the .gitlab.ci yaml file out of

Re: [petsc-dev] Solving systems with (K,M)AIJ

Pierre, This is not what you want but has the same flavor PCHMG. Here all the fields are in one giant matrix, it builds a preconditioner for a single field and then reuses it for all the fields. I think people have to start writing custom preconditioners for the structure of (K,M)

Re: [petsc-dev] Getting .gitlab.ci file out of repository? https://docs.gitlab.com/ee/ci/pipelines/settings.html

posing inlining the configure options into > .gitlab-ci.yml, which I think would work fine, but also don't clearly see a > point. > >> On Mon, 22 Jun 2020, Barry Smith wrote: >> >>> >>> I see, the way it is now each test case in the .gitlab file is hardwired >>> to an examples/*.py maybe we should just delete the examples/*.py and put >>> them directly in the yaml file.

[petsc-dev] added feature to petscgitbash for monitoring branches

I added a new feature to gitlab.com:petsc/petscgitbash.git you can now from the command line list the process your branches are in. I can finally keep track of my branches despite my total inability to remember anything. Barry $ git branches #=#=- ##

Re: [petsc-dev] Getting .gitlab.ci file out of repository? https://docs.gitlab.com/ee/ci/pipelines/settings.html

t; >>>>> This means the corresponding change should also be config/*.py - for >>>>> tests not to break. [but other branches would still have to use whats >>>>> valid for them]. >>>>> >>>>> So encoding examples/*.py a single/remote gitlab-ci.yaml just creates >>>>> more problems >>>> >>>> I thought Barry was just proposing inlining the configure options into >>>> .gitlab-ci.yml, which I think would work fine, but also don't clearly see >>>> a point. >>>> >>>>> On Mon, 22 Jun 2020, Barry Smith wrote: >>>>> >>>>>> >>>>>> I see, the way it is now each test case in the .gitlab file is hardwired >>>>>> to an examples/*.py maybe we should just delete the examples/*.py and >>>>>> put them directly in the yaml file. >>> >> >

[petsc-dev] testing with Pipelines before making merge request

One can test a branch with Pipelines (and fix it) before making a merge request. GitLab is smart enough to remember that branch has passed the pipeline and not require another test just because you make a MR (unless of course you change something based on MR feedback). This can prevent s

[petsc-dev] question on MatGolubKahanComputeExplicitOperator()

MatGolubKahanComputeExplicitOperator() first verifies that C is the transpose of B, it then computes the transpose of B to do the MatMatMult(). 1) Since C is the transpose of B isn't the second transpose not needed? Just use C instead of the BT? 2) If one knows the C = B' one can save the ex

[petsc-dev] clarification of merge request labels and process

The information for what each workflow: label means is given at https://gitlab.com/petsc/petsc/-/labels If everyone sets the labels correctly the merging will go easy and require less sending email or extra prompts to specific people. In pa

[petsc-dev] gitlab time tracking feature

https://gitlab.com/help/user/project/time_tracking.md I'm going to use it to replace my previous home-brew version

Re: [petsc-dev] git status to test list

I couldn't see how Jed can avoid doing the filename hacking since alltesttargets are the hacked filenames but probably I am missing something. Anyways this patch works for me based on Jed's email. Barry since.patch Description: Binary data > On Jul 6, 2020, at 9:40 AM, Jed Brown wrote

Re: [petsc-dev] git status to test list

ter) when testing. This gives you all the files that are > different between your branch and master. You can switch it out for maint if > needs be. > > Best regards, > > Jacob Faibussowitsch > (Jacob Fai - booss - oh - vitch) > Cell: (312) 694-3391 > >> On J

Re: [petsc-dev] git status to test list

ample, I find that I am quite often waiting on stage 2 freebsd > jobs to start in order to advance to stage 3, even after every other stage 2 > job has run its course. > > Best regards, > > Jacob Faibussowitsch > (Jacob Fai - booss - oh - vitch) > Cell: (312) 694-3391 >

Re: [petsc-dev] git status to test list

> On Jul 6, 2020, at 3:48 PM, Jed Brown wrote: > > Barry Smith writes: > >> We should be more clever than checking just examples but also check source >> code. If, for example, only KSP is changed then tests could skip the >> sys/vec/mat levels saving time.

Re: [petsc-dev] DMSWARM diffs

These should always have been there. If it doesn't have a . then it is diffed normally. My guess is someone added a new test: and forgot to filter out the "atomic size" line. See other swarm examples. Barry > On Jul 6, 2020, at 7:17 PM, Mark Adams wrote: > > I am getting these diff f

[petsc-dev] Sphinx error

Running Sphinx v3.0.4 Found DOT install: /usr/local/bin/dot Extension error: Could not import extension sphinxcontrib.bibtex (exception: No module named 'sphinxcontrib.bibtex')

Re: [petsc-dev] Sphinx error

make alldoc or whatever should help one with this. Not just send off a sphinx error. Barry > On Jul 6, 2020, at 8:20 PM, Jed Brown wrote: > > Gotta run > > pip install -r src/docs/sphinx_docs/requirements.txt > > Add --user if you aren't in a virtualenv

Re: [petsc-dev] Sphinx error

Brown wrote: > > Gotta run > > pip install -r src/docs/sphinx_docs/requirements.txt > > Add --user if you aren't in a virtualenv. > > Barry Smith writes: > >> Running Sphinx v3.0.4 >> >> Found DOT install: /usr/local/bin/dot >> >&

Re: [petsc-dev] Sphinx error

My fault, for some reason sphinx from brew installed its own private python so I had to do the pip at that. > On Jul 6, 2020, at 9:03 PM, Jed Brown wrote: > > Barry Smith writes: > >> Apple's python 2 doesn't use pip >> >> $ sudo easy_insta

Re: [petsc-dev] Sphinx error

s > underneath them. I still boggle at the fact that the clear majority of > people use operating systems that lack integrated package management. This > problem has been solved for 25 years. > > Barry Smith writes: > >> My fault, for some reason sphinx from brew ins

Re: [petsc-dev] Sphinx error

. It isn't really hard at all to make a Framework, just doesn't happen. > On Jul 6, 2020, at 11:01 PM, Jed Brown wrote: > > Barry Smith writes: > >> Apple introduced the concept of Framework for packaging long before >> Linux had half-way decent package managers

Re: [petsc-dev] Sphinx error

g on Apple of open source software. Or perhaps I misunderstand that line. Barry > On Jul 7, 2020, at 2:40 AM, Lisandro Dalcin wrote: > > > > On Tue, 7 Jul 2020 at 05:37, Barry Smith <mailto:bsm...@petsc.dev>> wrote: > > My fault, for some reason sphinx fr

Re: [petsc-dev] new Fortran error

The fix for this is to add PetscObjectSetName() to src/sys/f90-mod/petscsys.h90 with the * notation to allow any type. You will see in that file PetscObjectReference() etc. PetsFE is an INTEGER(8) in Fortran because no one has updated it yet to be a Fortran type. You will see in include

Re: [petsc-dev] Windows error in pipeline with cxx file

So you have includes for both ViennaCL and Kokkos in the same source file? Usually the error message shows two sets of lines, where it found the new one and where it found the old one. Is this the complete error message? Maybe you can compile in the problem directory with -E and sen

Re: [petsc-dev] gcc 10

I told everyone in that thread how it should be fixed. The fix for this is to add PetscObjectSetName() to src/sys/f90-mod/petscsys.h90 with the * notation to allow any type. You will see in that file PetscObjectReference() etc. PetsFE is an INTEGER(8) in Fortran because no one has updat

Re: [petsc-dev] gcc 10

The C++ complex thing and the gfortran thing are totally unrelated except they both come from Mark and involve the Gnu community. > On Jul 13, 2020, at 12:40 PM, Jed Brown wrote: > > I don't know what failure you're referring to. The C++ complex thing might > have been a matter of the an

Re: [petsc-dev] linking C++ mangling problem + Kokkos

My branch https://gitlab.com/petsc/petsc/-/merge_requests/2984 is in review, I have modified it with a kinder interface for users based on Jed's suggestion. Undergoing testing now. Once all the tests pass I will rebase and it will be ready for review again. Barry > On Jul 18, 2020,

Re: [petsc-dev] Question about MPICH device we use

Because nemesis does function in a reasonable way when the system is oversubscribed, that is there are more MPI ranks than cores. Many users getting started have whatever number of cores (4?) but want to run tests with a few more ranks, this is not feasible with nemesis. In addition with the

Re: [petsc-dev] [petsc-users] PETSc Make error

If PETSc requires distutils.sysconfig then ./Configure should check for it and print a very useful error message if it does not find it. We can't have python crashes off at build time with confusing error messages that users cannot decipher. Barry > On Jul 31, 2020, at 11:00 AM, Sati

Re: [petsc-dev] Configure --with-X-dir= Using Relative Path

Jacob, Since the reconfigure scripts are python you'll need to use python variables to access environmental variables like os.environ['PETSC_DIR'] Barry > On Aug 2, 2020, at 1:57 PM, Jacob Faibussowitsch wrote: > > Hello All, > > I am reconfiguring an arch within a docker using th

Re: [petsc-dev] TAOPDIPM

> On Aug 4, 2020, at 12:12 PM, Pierre Jolivet > wrote: > > Hello, > If I comment line 89 and 90 of src/tao/constrained/tutorials/ex1.c from > master, the example deadlocks with a single process. > Is this expected? > > Thanks, > Pierre > > $ ./ex1 -tao_monitor > Constrained Problem -

Re: [petsc-dev] How far should internal error checking go?

So long as the error checking is not much more expensive then the computation than I see no harm in including it with the if (debug) model. For example, checking a sorted array is sorted is less expensive than the sort so can be included at the end of sort algorithm. For the numerical sol

Re: [petsc-dev] Use -Wshadow on pipelines?

Agree > On Aug 9, 2020, at 6:55 PM, Jacob Faibussowitsch wrote: > > Hello All, > > I discovered a rather obscure set of compiler flags -Wshadow, -Wshadow=local, > -Wshadow=compatible-local while trying to track down a bug which warn about > local redefinition of a variable. Out of curiosi

Re: [petsc-dev] PetscContainerSetPointer

> On Aug 10, 2020, at 3:27 PM, Mark Adams wrote: > > I had some problems giving a container an PETSc object so I wrapped it in a > struct. > I forget what problem I had. Maybe ISColoringDestroy can't take a void*. > I'd like to check if I was just missing something. > Should something like

[petsc-dev] test harness failure make -f gmakefile.test test query='requires' queryval='kokkos'

Scott, Sometimes when I run the below test the harness mis-behaves. I cannot say what is different when this happens and doesn't because sometimes it also works. Thanks Barry make -f gmakefile.test test query='requires' queryval='kokkos' Traceback (most recent call last): File

[petsc-dev] Possible DMPLEX incorrect use of const

https://gitlab.com/petsc/petsc/-/jobs/696681024 CC arch-ci-opensolaris-cmplx-pkgs-dbg/tests/ts/tutorials/ex10.o 3680"/export/home/glci/builds/zxfiRCGf/0/petsc/petsc/include/petsc/private/sectionimpl.h", line 21: warning: operands have incompatible types: 3681 struct {pointer to

Re: [petsc-dev] Possible DMPLEX incorrect use of const

Solaris still rocks after all these years. > On Aug 21, 2020, at 7:22 AM, Matthew Knepley wrote: > > Yep. Fixing. > > Thanks, > > Matt > > On Thu, Aug 20, 2020 at 10:39 PM Barry Smith <mailto:bsm...@petsc.dev>> wrote: > > https://gitlab.

Re: [petsc-dev] Users manual update

Aren't we likely to keep using sowing to generate the manual pages and then our own scripts to clean them up and add the links for source code HTML etc? But use Sphinx for the users manual and all web pages we maintain ourselves, FAQ etc? So we will always have two "build" parts for docum

Re: [petsc-dev] Pause-for-approval Pipelines?

> On Aug 27, 2020, at 11:45 AM, Satish Balay via petsc-dev > wrote: > > On Thu, 27 Aug 2020, Jacob Faibussowitsch wrote: > >> Why does one pipeline request spawn two separate pipelines now? Specifically >> one is a normal pipeline whereas the other includes some sort of manual >> approval

Re: [petsc-dev] Pause-for-approval Pipelines?

> On Aug 27, 2020, at 4:55 PM, Jed Brown wrote: > > Barry Smith writes: > >>> - readdocs pipeline >>> - merge-pipeline - auto starts - does the pre stage and pauses. >> >> how are they related? > > Not at all. The ReadTheDocs pipeline i

Re: [petsc-dev] Pause-for-approval Pipelines?

Can't see where the test is that decides if a docs pipeline is needed and launched but presumably it is there somewhere in all the syntax. https://gitlab.com/gitlab-org/gitlab/-/blob/86bc0e2ed2fa32198a562e09bf36dab5821ece22/scripts/trigger-build

Re: [petsc-dev] Pause-for-approval Pipelines?

> On Aug 27, 2020, at 6:25 PM, Satish Balay wrote: > > On Thu, 27 Aug 2020, Satish Balay via petsc-dev wrote: > >> The above is hard for me to digest - so I think its best to frame this >> differently. >> >> 1. ReadTheDocs is not setup in .gitlab-ci.yml >> >> 2. We have merge_request pipe

[petsc-dev] PETSc issue I cannot post combine WaitForCUDA(); inside PetscLogGpuTimeEnd();

Since we cannot post issues (reported here https://forum.gitlab.com/t/creating-new-issue-gives-cannot-create-issue-getting-whoops-something-went-wrong-on-our-end/41966?u=bsmith

Re: [petsc-dev] PETSc issue I cannot post combine WaitForCUDA(); inside PetscLogGpuTimeEnd();

> On Aug 28, 2020, at 5:35 AM, Karl Rupp wrote: > > Hi, > >> Since we cannot post issues (reported here >> https://forum.gitlab.com/t/creating-new-issue-gives-cannot-create-issue-getting-whoops-something-went-wrong-on-our-end/41966?u=bsmith) >> here is my issue so I don't forget it. >>

Re: [petsc-dev] PETSc issue I cannot post combine WaitForCUDA(); inside PetscLogGpuTimeEnd();

> On Aug 28, 2020, at 10:26 AM, Stefano Zampini > wrote: > > > >> On Aug 28, 2020, at 5:18 PM, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >> >> >> >>> On Aug 28, 2020, at 5:35 AM, Karl Rupp >> <mailto:r...@iue.tuwi

Re: [petsc-dev] MacOS firewall annoyance while running tests + solution

Maybe you could make this a MR? Barry > On Aug 28, 2020, at 2:17 PM, Hapla Vaclav wrote: > > On MacOS, maybe you also have lots of firewall popups appearing/disappearing > when running tests like > Do you want the application "ex29" to accept incoming network connections? > > They ar

Re: [petsc-dev] MacOS firewall annoyance while running tests + solution

> On Aug 28, 2020, at 3:47 PM, Jed Brown wrote: > > "Hapla Vaclav" writes: > >> On MacOS, maybe you also have lots of firewall popups appearing/disappearing >> when running tests like >> Do you want the application "ex29" to accept incoming network connections? > > Is there a way to expre

Re: [petsc-dev] MacOS firewall annoyance while running tests + solution

> On Aug 28, 2020, at 3:47 PM, Jed Brown wrote: > > "Hapla Vaclav" writes: > >> On MacOS, maybe you also have lots of firewall popups appearing/disappearing >> when running tests like >> Do you want the application "ex29" to accept incoming network connections? > > Is there a way to expre

Re: [petsc-dev] PETSc issue I cannot post combine WaitForCUDA(); inside PetscLogGpuTimeEnd();

Karl, You are right. If we have some way of knowing the user callback is on the GPU then we will want to wrap the calling back in the GPU timing so the problem should be resolved but we would need to know which callbacks are on the GPU perhaps as our understanding of how through the

Re: [petsc-dev] MacOS firewall annoyance while running tests + solution

I would make your fix a configure option that is off by default. It is silly that Apple makes you use sudo to tell it that a compiled code SHOULD NOT accept outside connections but they have it all bundled together without enough thought for developers. Barry > On Aug 31, 2020, at 4:14 AM

Re: [petsc-dev] PetscMallocAlign for Cuda

Mark, Currently you use directly the Nvidia provided mallocs cudaMalloc for all mallocs on the GPU. See for example aijcusparse.cu. I will be using Stefano's work to start developing a unified PETSc based system for all memory management but don't wait for that. Barry > On Sep

[petsc-dev] testharness rerun test based on error condition; GPU; gitlab issues still broken

Scott, How difficult would it be for the test harness to run a failed test again if the return code has specific values? Instead of erroring out. I am thinking in particular about GPUs but it is general. If the GPU doesn't have he resources available it will error out thus crashing th

Re: [petsc-dev] Mat sub class

Why not just put the support in MatSeqAIJCUSPARSE ? No need for a new class. Barry > On Sep 7, 2020, at 6:28 PM, Mark Adams wrote: > > I am adding support for matrix assembly on the GPU. I made a new Mat class, > that is a "child" of MatSeqAIJCUSPARSE, but I am thinking that is the wron

Re: [petsc-dev] Statistics on the popularity of PETSc

It is essentially impossible to get good numbers. Satish can report the number of ftp downloads but that means little because the same people download multiple times, and demons download regularly plus many people use git to access the source code. Counts from git are also no useful because w

Re: [petsc-dev] Statistics on the popularity of PETSc

Jacob, Cool feature, $ brew info openmpi open-mpi: stable 4.0.5 (bottled), HEAD High performance message passing library https://www.open-mpi.org/ Conflicts with: mpich (because both install MPI compiler wrappers) Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/For

Re: [petsc-dev] PDIPDM questions

> On Sep 15, 2020, at 12:32 AM, Pierre Jolivet > wrote: > > > >> On 15 Sep 2020, at 2:21 AM, Abhyankar, Shrirang G >> mailto:shrirang.abhyan...@pnnl.gov>> wrote: >> >> Hello Pierre, >>PDIPM works in parallel so you can have distributed Hessian, Jacobians, >> constraints, variables, gr

Re: [petsc-dev] PDIPDM questions

Pierre, Based on my previous mail I am hoping that the PDIPM algorithm itself won't need a major refactorization to be scalable, only a custom matrix type is needed to store and compute with the Hessian in a scalable way. Barry > On Sep 15, 2020, at 12:50 PM, Pierre Jolivet > wro

Re: [petsc-dev] PDIPDM questions

pdipm->nci; i++) { row = rstart + pdipm->off_z + i; cols1[0] = rstart + pdipm->off_lambdai + i; cols1[1] = row; ierr = MatPreallocateSet(row,2,cols1,dnz,onz);CHKERRQ(ierr); } > On Sep 15, 2020, at 4:03 PM, Abhyankar, Shrirang G > wrote: > > There is s

Re: [petsc-dev] PDIPDM questions

> On Sep 16, 2020, at 12:58 AM, Pierre Jolivet > wrote: > > >> On 15 Sep 2020, at 11:18 PM, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >> >> >> I see now, the TaoSetup_PDIPM() code explicitly builds the large matrix by >>

Re: [petsc-dev] 3.9 Fortran changes

Maybe we should have a separate section at the bottom of the changes file for internal changes to PETSc that do not affect the user API. Barry > On Sep 19, 2020, at 2:40 PM, Satish Balay via petsc-dev > wrote: > > https://gitlab.com/petsc/petsc/commit/b7b8f77a1c31acd4cca9a56e02609d1df

[petsc-dev] Should everything in include be a symbolic link in the git repository?

The include directory is special because it contains source code from all components of PETSc but artificially collected together in a single directory tree because the C/C++/Fortran compilers like it this way to not require hundreds of -I and for distribution without the source. Should t

Re: [petsc-dev] Should everything in include be a symbolic link in the git repository?

tant enough to be a better system than just having git repository links for all of them. For application code portability there may be something said for always having all the includes visible to user code, even those not usable so users don't need to protect "optional" PETSc i

Re: [petsc-dev] Should everything in include be a symbolic link in the git repository?

> On Sep 21, 2020, at 5:17 AM, Matthew Knepley wrote: > > On Mon, Sep 21, 2020 at 3:05 AM Barry Smith <mailto:bsm...@petsc.dev>> wrote: > > > > On Sep 20, 2020, at 11:54 PM, Satish Balay > <mailto:ba...@mcs.anl.gov>> wrote: > > > > For

Re: [petsc-dev] Should everything in include be a symbolic link in the git repository?

d if that's net positive or not. Sure > one can always find some benefit and ignore or trivialize the negatives] > > Satish > > On Mon, 21 Sep 2020, Barry Smith wrote: > >> >> >>> On Sep 20, 2020, at 11:54 PM, Satish Balay wrote: >>> >>&

Re: [petsc-dev] requires !ctable

Do you mean for a test in the test harness? requires: !define(PETSC_USE_CTABLE) > On Sep 24, 2020, at 12:09 PM, Mark Adams wrote: > > Can I add a requirement for not using CTABLE.

Re: [petsc-dev] CI format failure

Everything in PETSc is open source and anyone is free to add/improve features. The only issue is that verifying the code is ok must be quick, if there are errors it is fine that the rule takes more time to nicely print out details of the problem. Barry > On Sep 24, 2020, at 12:25 PM,

[petsc-dev] Fwd: [Users] Call for Participation: First International Symposium on Checkpointing for Supercomputing (SuperCheck21)

Maybe we should implement check pointing for TS/Tao? It's silly to do it below TS. Barry > Begin forwarded message: > > From: Zhengji Zhao > Subject: [Users] Call for Participation: First International Symposium on > Checkpointing for Supercomputing (SuperCheck21) > Date: September 24,

Re: [petsc-dev] sm_70

Configure by default should find out the available GPU and build for that sm_* it should not require the user to set this (how the heck is the user going to know what to set?) If I remember correctly there is a utility available that gives this information. For generic builds like in pa

Re: [petsc-dev] sm_70

Barry > > Best regards, > > Jacob Faibussowitsch > (Jacob Fai - booss - oh - vitch) > Cell: (312) 694-3391 > >> On Sep 25, 2020, at 21:09, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >> >> >> Configure by default should find out the availa

Re: [petsc-dev] petsc release plan for Sept/2020

> !3219 by Junchao Zhang: Add vec Kokkos and mat Kokkos > !3249 by Barry Smith: Improve manual pages for PetscError() and the various > error handlers including... > !3191 by Jacob Faibussowitsch: Fortran custom bindings for > petsctimsort[witharray] Next is crucial bug fix >

Re: [petsc-dev] sm_70

> On Sep 27, 2020, at 11:55 AM, Zhang, Hong wrote: > > > >> On Sep 25, 2020, at 8:09 PM, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >> >> >> Configure by default should find out the available GPU and build for that >> sm_* it

Re: [petsc-dev] sm_70

https://gitlab.com/petsc/petsc/-/merge_requests/3252 <https://gitlab.com/petsc/petsc/-/merge_requests/3252> > On Sep 27, 2020, at 11:55 AM, Zhang, Hong wrote: > > > >> On Sep 25, 2020, at 8:09 PM, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >>

[petsc-dev] reminder on managing your merge requests MR

This is a reminder for everyone submitting MR. You are responsible to track the progress of the MR. Make sure you use the label workflow:review when you think it is ready to be reviewed for merge, add additional appropriate labels also assign some appropriate reviewers

Re: [petsc-dev] reminder on managing your merge requests MR

> On Sep 29, 2020, at 12:43 AM, Patrick Sanan wrote: > > > >> Am 29.09.2020 um 02:12 schrieb Barry Smith > <mailto:bsm...@petsc.dev>>: >> >> >> This is a reminder for everyone submitting MR. >> >> You are respon

[petsc-dev] PETSc 3.14 release available

better documentation in the future. This release includes contributions from Alejandro Otero Alexei Colin Alex Lindsay Alp Dener Aron Ahmadia Arthur Soprano Asbjørn Nilsen Riseth Barry Smith Ben Mather Brandon Whitchurch Chris Eldred Chris Hennekinne David A Ham David Ham Dmitry Karpe

Re: [petsc-dev] Kokkos error on SUMMIT

Mark, Looks like you are building Kokkos without CUDA.You don't have --with-cuda on configure line that is used by Kokkos to determine what version to build. Junchao, I guess you need to test Kokkos Kernels without CUDA and HIP and make a few changes. Barry #if defined(PE

Re: [petsc-dev] Scaling test with ex13 (snes)

Mark, There is a MATPARTITIONINGHIERARCH (man page) that Fande provided that helped scaling up problems he was working on significantly. Barry > On Oct 3, 2020, at 10:04 AM, Matthew Knepley wrote: > > On Sat, Oct 3, 2020 at 10:51 AM Stefano Zampini

Re: [petsc-dev] Scaling test with ex13 (snes)

> On Oct 3, 2020, at 12:48 PM, Stefano Zampini > wrote: > > > > > There is a MATPARTITIONINGHIERARCH (man page) that Fande provided that > helped scaling up problems he was working on significantly. > >Barry > > The scaling issue with DMPlex is the one-to-all pattern of communica

[petsc-dev] Fwd: [mpich-announce] Announcing the availability of MPICH 3.4b1

GPU support, so we should eventually try this out. Barry > Begin forwarded message: > > From: "Raffenetti, Kenneth J. via announce" > Subject: [mpich-announce] Announcing the availability of MPICH 3.4b1 > Date: October 5, 2020 at 10:11:43 PM CDT > To: "annou...@mpich.org" > Cc: "Raffene

[petsc-dev] Fwd: ArmPL - Batched interfaces

FYI > Begin forwarded message: > > From: Christopher Armstrong > Subject: ArmPL - Batched interfaces > Date: October 6, 2020 at 10:34:05 AM CDT > To: "bsm...@mcs.anl.gov" > Cc: Nicholas Dingle > Message-Id: > > > Hi Barry, > > I work on Arm Performance Libraries, which is the Arm vendor

Re: [petsc-dev] Failure of mergecov

git diff --name-only origin/master...' returned non-zero exit status 128. I did a retry, let's see if that works. I can protect this with a try so it won't crash CI and waste people's time. I'll look at the log more closely later and see if I guess the cause. Barry > On Oct 8, 2020

Re: [petsc-dev] Failure of mergecov

echo origin/${CI_MERGE_REQUEST_TARGET_BRANCH_NAME} > exit 0 > fi > > On Thu, 8 Oct 2020, Barry Smith wrote: > >> >> git diff --name-only origin/master...' returned non-zero exit status 128. >> >> >> I did a retry, let's see if that works

Re: [petsc-dev] Failure of mergecov

t: https://gitlab.com/petsc/petsc/-/merge_requests/3327 > <https://gitlab.com/petsc/petsc/-/merge_requests/3327> > > Satish > > On Thu, 8 Oct 2020, Barry Smith wrote: > > > > > Yes, I think Satish's fix is correct. > > > > Barry >

[petsc-dev] Fwd: [coin-or/ADOL-C] Swig's Setup.py will default to lib64 which is inappropriate if the u… (#30)

ctober 10, 2020 at 9:05:25 PM CDT > To: coin-or/ADOL-C > Cc: Barry Smith , Author > Reply-To: coin-or/ADOL-C > > Message-Id: > > > <https://cla-assistant.io/coin-or/ADOL-C?pullRequest=30> > Thank you for your submission! We really appreciate it. Lik

[petsc-dev] PETSc always recompiles mpi4py petsc4py even when it does not have too

I change a single PETSc file and do make all that single file gets compiled but all of mpi4py and petsc4py get recompiled even though I have not changed any thing to affect them. No include files for example *** Building mpi4py *** *** Installing mpi4py *** ==

[petsc-dev] speeding up testing by not always downloading external packages?

Satish, Do you think the time to download all the external packages for each job is significant? Would using super shallow clones on the external packages help much in time? Maybe we should to them anyways to stop wasting bandwidth? Currently we do full clones? but we don't need th

Re: [petsc-dev] PETSc always recompiles mpi4py petsc4py even when it does not have too

t to do make libs instead of make all? The problem is make libs is not parallel so much slower? Barry > > Thanks, > Pierre > >> On 11 Oct 2020, at 9:36 AM, Barry Smith > <mailto:bsm...@petsc.dev>> wrote: >> >> >> I change a single PETSc fil

Re: [petsc-dev] PETSc always recompiles mpi4py petsc4py even when it does not have too

rg>> wrote: > Not unless you pass -j (or export it in MAKEFLAGS). > > So just run make -f ./gmakefile -j 8 if you want a parallel build? > > Matt > > On Sun, Oct 11, 2020, at 6:51 AM, Matthew Knepley wrote: >> On Sun, Oct 11, 2020 at 4:35 AM Barry Smith > &l

  1   2   3   4   5   6   7   8   9   10   >