Re: [petsc-dev] [petsc-users] compiler related error (configuring Petsc)

2023-08-01 Thread Barry Smith via petsc-dev
Only four more years of this nonsense! One of the (now ancient) selling points of Unix was that it could be more nimble and evolve more rapidly than IBM's mainframe operating systems. Jacob, Can't we have configure tell users explicitly the situation when they encounter this case

Re: [petsc-dev] fixing bugs in resolution of TSEvent's

2023-07-18 Thread Barry Smith via petsc-dev
We are aware of "issues" with TSEvent and appreciate you working on it. Another user reported problems last week https://gitlab.com/petsc/petsc/-/issues/1414 which we resolved in an associated MR, you might want to check those changes to see how/if they would interact with your MR. As

Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?

2022-07-31 Thread Barry Smith via petsc-dev
> On Jul 31, 2022, at 12:49 PM, Jacob Faibussowitsch > wrote: > > Sorry, hit send too early :) > >> It may be worth it if there are significant benefits in safety and static >> analysis or if the tooling means contributors really have fewer moving parts. > > Well for one, C ships with

Re: [petsc-dev] Kokkos/Crusher perforance

2022-01-23 Thread Barry Smith via petsc-dev
> On Jan 23, 2022, at 10:47 PM, Jacob Faibussowitsch > wrote: > >> The outer LogEventBegin/End captures the entire time, including copies, >> kernel launches etc. > > Not if the GPU call is asynchronous. To time the call the stream must also be > synchronized with the host. The only way to

[petsc-dev] Contest models highlight inherent inefficiencies of scientific funding competitions

2020-02-09 Thread Barry Smith via petsc-dev
https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.365 Sent from my iPad