Re: [Vo]:Cold Fusion is Back (there's just one problem)

H LV wrote: Since she is respected astrophysicist with nearly 600 000 subscribers and > probably many more followers this video could potentially make cold fusion > research part of mainstream science. > It sure could help! I think a much bigger help would be if the X-Prize people follow throug

Re: [Vo]:Cold Fusion is Back (there's just one problem)

This video is not bad. But I posted one one complaint in the comment section: "Hossenfelder says that no one was able to replicate several experiments. Some of those were replicated. No one has tried to replicate the others." My point is that if several people try to replicate an experiment but

Re: [petsc-users] suppress CUDA warning & choose MCA parameter for mpirun during make PETSC_ARCH=arch-linux-c-debug check

Barry Smith writes: >I hate these kinds of make rules that hide what the compiler is doing (in > the name of having less output, I guess) it makes it difficult to figure out > what is going wrong. You can make VERBOSE=1 with CMake-generated makefiles.

[Vo]:Copy of "Novum Organum" uploaded

This is somewhat off topic but -- I uploaded a copy of the book by Francis Bacon, "Novum Organum" (A New Instrument) written in 1620. It is here: https://lenr-canr.org/Collections/Novum%20Organum.docx You may want to download a copy. Let me explain what this is and why I uploaded it. Thomas Jef

Re: [VOTE] Airflow Providers prepared on October 04, 2022

+1 (binding) Checked signatures, checksums, and licences.

CVE-2022-41672: Apache Airflow: Session still functional after user is deactivated

Description: In Apache Airflow, prior to version 2.4.1, deactivating a user wouldn't prevent an already authenticated user from being able to continue using the UI or API. Credit: The Apache Airflow PMC would like to thank Axel Chong (@Haxatron) for reporting this issue. References: https://gi

[ANNOUNCE] Apache Airflow 2.4.1 Released

lease notes here for more details: https://airflow.apache.org/docs/apache-airflow/2.4.1/release_notes.html Container images are published at: https://hub.docker.com/r/apache/airflow/tags?page=1&name=2.4.1 Thanks, Jed

[ANNOUNCE] Apache Airflow 2.4.1 Released

lease notes here for more details: https://airflow.apache.org/docs/apache-airflow/2.4.1/release_notes.html Container images are published at: https://hub.docker.com/r/apache/airflow/tags?page=1&name=2.4.1 Thanks, Jed

[RESULT][VOTE] Release Airflow 2.4.1 from 2.4.1rc1

Hello, Apache Airflow 2.4.1 (based on RC1) has been accepted. 4 "+1" binding votes received: - Jed Cunningham - Ephraim Anierobi - Daniel Standish - Ash Berlin-Taylor 1 "+1" non-binding votes received: - Josh Fell Vote thread:https://lists.apache.org/thread/p3t3blytbktx

Re: [VOTE] Release Airflow 2.4.1 from 2.4.1rc1

Kind bump, I need 1 more vote on this release.

Re: [VOTE] Airflow Providers prepared on September 28, 2022

+1 (binding) Checked signatures, checksums, and licences.

Re: facebook app question

Oh man, what would be the best way to turn off screen recognition? On 9/29/22, Sieghard Weitzel wrote: > You may have accidently turned on screen recognition, it really messes up > the Facebook as well as other apps. > > -Original Message- > From: jedbar...@gmail.com O

facebook app question

Hey guys, question, is something wrong with the facebook app? When I load it and keep swiping, it keeps saying suggested for you, suggested for you. How do I get rid of this, it's super annoying. -- The following information is important for all members of the V iPhone list. If you have any qu

[VOTE] Release Airflow 2.4.1 from 2.4.1rc1

Fix invalid RST in dataset concepts doc (#26434) - Document the ``non-sensitive-only`` option for ``expose_config`` (#26507) - Fix ``example_datasets`` dag names (#26495) - Zip-like effect is now possible in task mapping (#26435) - Use task decorator in docs instead of classic operators (#25711) Thanks, Jed

Re: [VOTE] September 2022 PR of the Month

Tough month, a lot of good choices!

Re: [VOTE] September 2022 PR of the Month

My write-in is ExternalPythonOperator: https://github.com/apache/airflow/pull/25780

Re: [petsc-users] Solve Linear System with Field Split Preconditioner

>> Are there other approaches to solve this kind of systems in PETSc except >> for field-split methods? >> >> Thanks, >> Xiaofeng >> >> On Sep 26, 2022, at 14:13, Jed Brown wrote: >> >> This is the joy of factorization field-split methods. The actu

Re: [petsc-users] Solve Linear System with Field Split Preconditioner

This is the joy of factorization field-split methods. The actual Schur complement is dense, so we represent it implicitly. A common strategy is to assemble the mass matrix and drop it in the 11 block of the Pmat. You can check out some examples in the repository for incompressible flow (Stokes p

Re: [petsc-users] Solve Linear System with Field Split Preconditioner

The usual issue is that you need a preconditioner for the Schur complement S = A11 - A01 A00^{-1} A10. For incompressible elasticity, this S is spectrally equivalent to a scaled mass matrix. 晓峰 何 writes: > Hi all, > > I have a linear system formed from structural mechanics, and there exists >

Re: [DISCUSS] string normalization in black

I'd be in favor of turning it on. I tend to prefer double quotes, but I'd rather have it on and have single quotes. If we do get enough support for this, I'd like to wait until we are closer to 2.5 to reduce conflicts when cherry-picking for 2.4.x's.

CVE fixes in Airflow 2.4.0 and Airflow 2.3.4

/zn8mbbb1j2od5nc9zhrvb7rpsrg1vvzv Thanks, Jed

Re: [petsc-dev] PetscLogEventRegister() is problematic since it must be call in exactly the same order on all ranks

onBegin; > PetscCall(SNESInitializePackage()); > PetscFunctionReturn(0); > } > > Everything gets initialized when the libraries are loaded so they can be in > the same order. > > I believe Jed found some nonstandard magic that when using shared? classic? > libraries triggering an

Re: [VOTE] Release Airflow 2.4.0 from 2.4.0rc1

Of course, I meant the vote will last until Sunday, September 18, *2022* (not 2021) at 8:00 pm UTC. Sorry about that!

[VOTE] Release Airflow 2.4.0 from 2.4.0rc1

) - Add note on subtle logical date change in ``2.2.0`` (#24413) - Add missing import in best-practices code example (#25391) Thanks, Jed

Re: [petsc-users] Read and write HDF5 files

It sounds like the PETSc inside your container was not built with --download-hdf5 (or --with-hdf5). That can be fixed by updating the Dockerfile and rebuilding the image. Quentin Chevalier writes: > Hello PETSc users ! > > I'm trying to use PETSc routine to read and write complex vectors to bi

Re: CVE-2022-38170: Apache Airflow: Overly permissive umask for deamons

And shoutout to Drew Hubl for noticing the "deamon" typo 🤦‍♂️. I've already fixed it so it'll be correct when the CVE is published.

Re: [petsc-dev] Fwd: Pending configuration of custom domain docs.petsc.org

don't need to update anything on readthedocs. > > [perhaps Jed can confirm] > > Satish > > On Tue, 30 Aug 2022, Matthew Knepley wrote: > >> Is someone looking at this? >> >> Thanks, >> >> Matt >> >> -- Forwarded mes

[Vo]:Di Stefano preprint

See: Di Stefano, A. *Experimental Observation on the Lattice Energy Converter, preprint and PowerPoint slides*. in *ICCF24 Solid-state Energy Summit*. 2022. Mountain View, CA. https://www.lenr-canr.org/acrobat/DiStefanoAexperiment.pdf This includes links to the video and to papers and a video by

Re: [Vo]:weight and uniform motion on a horizontal surface

H LV wrote: Lets assume the earth is not rotating. > Will our assumption stop it from rotating? WWII Admiral Willis Lee was one of the world's top experts in artillery. He would calculate battleship gun trajectories including the effects of the earth's rotation. He would include so many factors

Re: [petsc-users] Scaling of PETSc example ex2f.F90

Your observed performance is explained by the number of iterations, which varies based on a number of factors, plus imperfect memory bandwidth scaling (https://petsc.org/release/faq/#what-kind-of-parallel-computers-or-clusters-are-needed-to-use-petsc-or-why-do-i-get-little-speedup). Problems lik

Re: [petsc-dev] tests coverage

We should report coverage to GitLab, in which case it'll annotate the diff. For example, this MR shows a red mark on this line that isn't covered by the tests, versus green marks for the covered changes. https://gitlab.com/micromorph/ratel/-/merge_requests/199/diffs#9f067f1470c81c8dda08481fdd5c6

Re: [petsc-users] 3D Model Coupled to 0D Model

Have you considered PCFieldSplit? The SCHUR variant gives you all sorts of approximate factorization schemes, though you might find that an additive or multiplicative split is almost as good for this problem. "Karabelas, Elias (elias.karabe...@uni-graz.at)" writes: > Hey all, > > so I

Re: [petsc-dev] How to update tests output

make test search=... REPLACE=1 see `make help-test` for more Blaise Bourdin writes: > Silly question, but I can’t find the answer in my notes or on the petsc > developer pages: How do I automatically update the output of a series of > tests without running them all by hand, one at a time? >

Re: [DISCUSS] Trimming down Airlfow Versions in issues

oach in the PR >> https://github.com/apache/airflow/pull/25542 >> >> >> >> On Thu, Aug 4, 2022 at 12:40 PM Jarek Potiuk wrote: >> >>> Love it. >>> >>> On Thu, Aug 4, 2022 at 9:28 PM Jed Cunningham >>> wrote: >>> >>

Re: request for unsubscribing.

Hi Rohan, You can unsubscribe by sending an email to dev-unsubscr...@airflow.apache.org (and users-unsubscr...@airflow.apache.org if you happen to be subscribed to that list as well). Jed On Thu, Aug 4, 2022 at 10:58 PM Rohan Khanna wrote: > Hi, > > I would like to unsubscribe this e

Re: Auto-registering of DAGs in DAG file? (no `as dag` needed?)

+1. I view it as adding a feature vs breaking compatibility. On Thu, Aug 4, 2022 at 4:15 PM Ferruzzi, Dennis wrote: > I definitely like it, I love reducing boilerplate code like that. > > > -- > *From:* Ash Berlin-Taylor > *Sent:* Tuesday, August 2, 2022 3:43 AM > *T

Re: [DISCUSS] consolidate dag scheduling params

sk*, so there is less to change with than some other >>>>>>> deprecations. And being kwargs-only, it's an easy find and replace that >>>>>>> could be automated with an `upgrade-check` script. It's very easy to >>>>>>> detect, either to warn about, or ultimately, after upgrade, to fail the >>>>>>> DAG >>>>>>> parse (which forces user to fix). Perhaps we could even experiment with >>>>>>> a >>>>>>> deprecation fix tool, so that users could get help fixing deprecations, >>>>>>> not >>>>>>> necessarily in the context of an upgrade, since we're not looking at 3.0 >>>>>>> any time soon. >>>>>>> >>>>>>> We could compare with execution_date, if execution_date is to be >>>>>>> removed in 3.0. I think the deprecation of execution_date will be a more >>>>>>> difficult thing for users to handle. For one, potentially higher >>>>>>> cardinality, since it is used in tasks. But also, the use of >>>>>>> execution_date >>>>>>> can be harder to detect, since it can be in templates and elsewhere in >>>>>>> custom operators. *(With schedule_interval, since it's a top-level >>>>>>> dag kwarg, it will be easier.)* And execution_date was replaced >>>>>>> with `logical_date` for similar reasons -- avoiding user confusion. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jul 29, 2022 at 2:42 PM Vikram Koka >>>>>>> wrote: >>>>>>> >>>>>>>> -1 from me. >>>>>>>> >>>>>>>> Though I agree in principle with the idea of consolidation, I don't >>>>>>>> think we should be doing this yet until we understand the implications >>>>>>>> completely. >>>>>>>> I am really not in favor of deprecation of the existing params, >>>>>>>> unless there is really no alternative. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jul 29, 2022 at 2:37 PM Daniel Standish >>>>>>>> wrote: >>>>>>>> >>>>>>>>> So far, seems all in favor. >>>>>>>>> >>>>>>>>> I will just highlight, in case it's not clear when we release >>>>>>>>> this (presumably 2.4), basically every single dag in existence will >>>>>>>>> start >>>>>>>>> emitting deprecation warnings, and prior to 3.0, basically every dag >>>>>>>>> in >>>>>>>>> existence will need to be updated. >>>>>>>>> >>>>>>>>> Thankfully, for most people, this should be an easy update since >>>>>>>>> DAG is kwargs only, IIRC. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Jul 29, 2022, 2:27 PM Brent Bovenzi >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> +1 to consolidating and "schedule". >>>>>>>>>> >>>>>>>>>> On Fri, Jul 29, 2022, 10:12 PM Drew Hubl >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> +1 for ‘schedule', and another +1 to the importance of >>>>>>>>>>> consolidating to one being more important than the name of that one >>>>>>>>>>> >>>>>>>>>>> On Jul 29, 2022, at 1:58 PM, Josh Fell < >>>>>>>>>>> josh.d.f...@astronomer.io.INVALID> wrote: >>>>>>>>>>> >>>>>>>>>>> Consolidating to a single scheduling parameter is a big +1 from >>>>>>>>>>> me. `schedule` seems like a nice catch-all. >>>>>>>>>>> >>>>>>>>>>> On Fri, Jul 29, 2022 at 9:10 AM Jed Cunningham < >>>>>>>>>>> jedcunning...@apache.org> wrote: >>>>>>>>>>> >>>>>>>>>>>> +1 on moving to a single `schedule` param. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>

Re: [DISCUSS] Trimming down Airlfow Versions in issues

Sorry, coming to this a little late. I tend to agree with Elad that we might be better off not even having 2.0/2.1, and I'll go further that we should consider only listing main/latest/possibly n-1(e.g. 2.3.2). I'm also concerned only showing the latest in every minor may imply those are all getti

Re: [Vo]:Very low power levels are worth TONS of money

Larry Forsley just uploaded the final Short Course video which is about glow discharge reactions: > https://www.youtube.com/watch?v=_4QBbgJyk7w

Re: [Vo]:Very low power levels are worth TONS of money

I do not recall an experiment that produced a lot of steam. Maybe the glow discharge ones? They went for 15 minutes before the electrode dissolved. They did produce a lot of steam. >

[Vo]:ICCF24 paper, How to fix global warming with cold fusion

Here is the first draft of my presentation at ICCF24: Rothwell, J. *How to fix global warming with cold fusion.* in *ICCF24 Solid-state Energy Summit.* 2022. Mountain View, CA. https://www.lenr-canr.org/acrobat/RothwellJhowtofixgl.pdf Suggestions and corrections are welcome. If anyone else

Re: [Vo]:Very low power levels are worth TONS of money

Jonathan Berry wrote: Wrist watches of course don't need such frequent replacement, but more-over > there are both kinetic and solar solutions. > That's true. There are probably some small devices similar to wrist watches that are not moved or left in sunlight that could use a long-lived battery

Re: [petsc-users] DMPlex PETSCViewer for Surface Component

I would create a sub-DM containing only the part you want to view. Mike Michell writes: > Hi, > > I am a user of DMPlex object in 3D grid topology. Currently the solution > field is printed out using viewer PETSCVIEWERVTK in .vtu format. By doing > that the entire volume components are written i

[Vo]:Very low power levels are worth TONS of money

way, when you present the LEC to venture capitalists, you should not say that 1 kW is the lowest "practical" level of power. 10 microwatts is a practical power level. Not only practical, but per watt, is it is worth thousands to millions of times more than power company electricity. - Jed

Re: [petsc-dev] GPU performance of MatSOR()

t; parallelism on GPUs but at the cost of multiple phases and slower >> convergence rates. Unless someone already has one coded for CUDA or Kokkos >> it would take a good amount of code to produce one that offers (but does >> not necessarily guarantee) reasonable perfor

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

Jacob, would you consider VTK to be "Modern C++"? It was designed in the 90s and I think C++11 isn't widely used (architecturally) since it was first allowed a few years ago. I feel like changing languages (or adopting a second essential implementation language) is a significant complexity step

Bug#1016363: More info about the fvwm deadlock with libx11-6 1.8.1

t;_pred_weed_handle_expose>, arg=arg@entry=0x0) at FEvent.c:527 #12 0x55ca7248cfba in handle_all_expose () at events.c:4545 #13 0x55ca724be911 in __raise_or_lower_window (t=t@entry=0x55ca7361c250, mode=mode@entry=SM_RAISE, allow_recursion=allow_recursion@entry=1, is_new_window=is_new_window@entry=0, is_client_request=is_client_request@entry=0) at stack.c:1141 --Jed

Bug#1016363: More info about the fvwm deadlock with libx11-6 1.8.1

t;_pred_weed_handle_expose>, arg=arg@entry=0x0) at FEvent.c:527 #12 0x55ca7248cfba in handle_all_expose () at events.c:4545 #13 0x55ca724be911 in __raise_or_lower_window (t=t@entry=0x55ca7361c250, mode=mode@entry=SM_RAISE, allow_recursion=allow_recursion@entry=1, is_new_window=is_new_window@entry=0, is_client_request=is_client_request@entry=0) at stack.c:1141 --Jed

Bug#1016363: More info about the fvwm deadlock with libx11-6 1.8.1

t;_pred_weed_handle_expose>, arg=arg@entry=0x0) at FEvent.c:527 #12 0x55ca7248cfba in handle_all_expose () at events.c:4545 #13 0x55ca724be911 in __raise_or_lower_window (t=t@entry=0x55ca7361c250, mode=mode@entry=SM_RAISE, allow_recursion=allow_recursion@entry=1, is_new_window=is_new_window@entry=0, is_client_request=is_client_request@entry=0) at stack.c:1141 --Jed

Re: [petsc-users] Import Matlab matrix

You can use share/petsc/matlab/PetscBinaryWrite.m. matlab> PetscBinaryWrite('matrix.petsc', sparse(A)) Then load it with MatLoad in PETSc. Ahmed Mansur writes: > How to import a sparse matrix from Matlab using C++ and PETSC , if anyone > has any example code, thanks

Re: [DISCUSS] consolidate dag scheduling params

+1 on moving to a single `schedule` param.

[Vo]:IE coverage of ICCF-24

Thank you Christy! http://www.infinite-energy.com/resources/ICCF24-Solid-State-Energy-Summit.html

Re: [petsc-dev] GPU performance of MatSOR()

Unfortunately, MatSOR is a really bad operation for GPUs. We can make it use sparse triangular primitives from cuSPARSE, but those run on GPU at about 20x slower than MatMult with the same sparse matrix. So unless MatSOR reduces iteration count by 20x compared to your next-best preconditioning o

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

eems difficult to provide multiple language APIs that properly > utilize each language's object oriented features automatically from one given > starting language? Without a lot of thought and effort. > > > >> On Jul 27, 2022, at 3:12 PM, Jed Brown wrote: >> &g

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

the most pragmatic choice today >> and for the foreseeable future. And it could become even more important on >> tomorrow’s heterogeneous hardware architectures. >> >> On Tue, Jul 26, 2022 at 11:09 AM Barry Smith wrote: >>> >>> >>>> On Jul 2

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

These ownership patterns need to be addressed for reliable interfaces in any language, the compiler just forces you to do it (or use the unsafe escape hatch) in Rust. I think it's necessary in any incremental porting effort for "old" code to call "new" code, due to the nature of our composition

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

I have to put in a good word for Rust. There are many parallels in capability with modern C++, but the compiler enforces many good practices (and guarantees safety), compiler error and warning messages are really useful, and the tooling is phenomenal on multiple fronts, from packaging to refacto

Re: [VOTE] July 2022 PR of the Month

If it's not too late, #24989 adding `expand_kwargs` is my vote. On Mon, Jul 25, 2022 at 5:25 PM Ferruzzi, Dennis wrote: > Limiting it to a non-committer PR in the future seems to be a good idea to > me. It could act like a "Newcomer Spotlight" or something like that. > > > -

Re: [Vo]:Brillouin Energy Corp demonstration at ICCF-24

8:54 AM Jones Beene wrote: > For many years they have claimed modest COP but nothing commercializable > > Can they now demonstrate net real gain? > Any gain is real, even 0.1%. Perhaps you mean "significant gain" or "gain enough for practical or economic use." I think Steve Krivit and some oth

[Vo]:Brillouin Energy Corp demonstration at ICCF-24

QUOTE: Brillouin Energy Corp Demonstrates CleanTech Licensable Solid State Fusion Boiler System at the 24th Annual International Conference on Cold Fusion ( www.iccf24.org) July 25th – 28th at the Computer History Museum in Mountain View, California Breakthrough boiler system uses hydrogen to pro

Re: [petsc-users] Install PETSc with other libraries via package manager

Looks like the Debian package is built with PTScotch, which is a partitioner similar to ParMETIS that has better license. (ParMETIS has a non-free license and is flagged as such on Debian.) All PETSc builds have LAPACK. If you get it from your package manager, you'll be stuck with a somewhat old

Re: [VOTE] Airflow Providers prepared on July 17, 2022

+1 (binding) Checked signatures, checksums, and licences.

Re: [DISCUSS] "Magic Loop" as fist class citizen in Airflow ?

I think we should only document the "DAG author friendly" approach (env var or otherwise) and hold the existing PR until it is ready. My 2c.

Re: [petsc-users] PETSc / AMRex

Matthew Knepley writes: >> I currently set up a 3D DMDA using a box stencil and a stencil width of 2. >> The i,j,k coordinates refer both to the cell (where there is a physical >> value assigned) and to the 3 edges of the cell at the top SW corner. >> For local computations, I need to be able to

Re: [VOTE] Airflow Providers prepared on July 13, 2022

+1 (binding) Checked signatures, checksums, and licences.

Re: [VOTE] Release Airflow 2.3.3 from 2.3.3rc3

+1 (binding) Gave it a quick spin with the helm chart.

Re: [petsc-users] Using matrix-free with KSP

You'll usually have a GlobalToLocal operation for each rank to get the halo data it needs, then either a LocalToGlobal to collect the result (e.g., finite element methods) or the local compute will write directly into the owned portion of the global vector. If you're doing the communication "raw

Re: [DISCUSS] Migrate airflow code to use PEP 563 (postponed evaluation of annotations) MAYBE?

Overall this sounds good to me. I'll echo waiting until after the last planned 2.3 release. It'd be great if we could keep the empty inits empty (and it sounds like isort will do that for us .

Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus

David Andrs writes: > Hi Matt! > > On Jun 26, 2022, at 10:39, Matthew Knepley wrote: >> >> On Sun, Jun 26, 2022 at 8:31 AM David Andrs > <mailto:and...@gmail.com>> wrote: >> Hi Jed! >> >> I have been thinking about this and I think more c

[Vo]:ICCF24 program revised

The program has been revised. It is gigantic! This is probably the biggest conference since ICCF3. https://www.iccf24.org/program

Re: [PROPOSAL] Remove "Label when reviewed" workflow

+1 for removing it.

Re: Please vote on the PR of the Month for this month's Airflow Newsletter!

My write in is 24249, which adds viewing task logs in the new Grid UI: https://github.com/apache/airflow/pull/24249 If we are doing this rank choice style, my next choice would be 24496.

Re: [petsc-users] Load mesh as DMPlex along with Solution Fields obtained from External Codes

(Sorry you didn't get a reply earlier.) That's generally right: DM gives what is basically a distributed "function space". Actual fields in that space are Vecs. You can have one or more Vecs. The implementation of VecLoad will depend on the file format. Mike Michell writes: > Dear PETSc devel

Re: [petsc-dev] Fortran binding for VecGetValuesSection

Sorry about our late reply. Isn't VecGetValues similar? Note that VecGetValuesSection currently leaks a mutable pointer and really shouldn't exist like this without a matching VecRestoreValuesSection. PetscCall(VecGetArray(v, &baseArray)); *values = &baseArray[s->atlasOff[p]]; PetscCall(Ve

Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus

Do you think this is more correct than just using "Face Sets", which gives you a numbered index? There is curently some inconsistency between file formats in whether various sets show up as stand-alone labels or values under Face Sets. And there's this lingering issue to have a way to name Face

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > I take it that the photo is not the best so doesn't show everything; and > heat was so bad at one time that it spread a long way. > You mean the heat magically jumped 70 feet, and then spread past two bunkers which were not on fire. That is physically impossible. > Well

Re: [Vo]:Bearden dead and cheniere.org gone

a 30' streak would be life-threatening to everyone on board. It will fill the whole ship with smoke. Especially a streak that magically appears 70' away from the fire, with no streak near the fire! That would upset sailors because they tend to be superstitious. It would bewilder them.

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > It wasn't as massive a fire as you are trying to make out. > I have read about shipboard fires, shipwrecks, storms and other disasters. I have heard about such things directly from people who sailed on ships made before WWI. Any fire large enough to leave a 30' black strea

Re: [Vo]:Bearden dead and cheniere.org gone

crew and passengers, who would have refused to board. > Jed: The people running Fukushima were also first class. Japanese > engineering is some of the best in the world. > > > And they didn't think about building a bigger sea wall? > They did think of it, and it was recommen

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: definition 2 > > to act in harmony toward a common end > > https://www.merriam-webster.com/dictionary/conspire > > > --> nothing about a conspiracy has to be unlawful or illegal > > > -> not your definition > You misunderstand. Definition 2 only applies to inanimate objects

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: *Stigmergy* (/ˈstɪɡmərdʒi/ > *STIG-mər-jee* > ) is a > mechanism of indirect coordination > , through the environmen

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > Jed: There were many coal bunker fires in the ships of that era. They > never sank a ship as far as I know. > > > So, as far as you know. > > > As far as you know > Which is probably farther than you know. As I said, I happen to know about shi

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > There are open conspiracies - > That is a contradiction of terms. The dictionary definition of "conspiracy" is: "a secret plan by a group to do something unlawful or harmful." Dictionary.com "1 · a secret agreement to do something harmful or unlawful ; 2 · the act of pl

Re: [Vo]:Bearden dead and cheniere.org gone

Chris Zell wrote: > Many of these things are technically not conspiracies, just stigmergy. That is a great word! I have never heard it. You learn something new every day. Here is another definition: https://wiki.p2pfoundation.net/Stigmergy Yes, the opposition to cold fusion was stigmergy. It

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > Titanic sounds to me a conspiracy fact - it left port with a fire in its > coal bunker that could not be put out - that sounds to me that didn't want > the Titanic to survive the journey. > There were many coal bunker fires in the ships of that era. They never sank a ship

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > This is getting too diverted. What you were saying sounded like a > conspiracy theory. > Perhaps it did sound like that, but it was not. Because -- 1. A conspiracy is organized and surreptitious. The opposition to cold fusion was unorganized and very much in the open. Opp

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > sounded like conspiracy theory. > What sounded like a conspiracy theory? What do you refer to? As I said, not everything that sounds like a conspiracy theory, is a conspiracy theory. Not everything that sounds implausible is false. The Titanic disaster was caused by a w

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > Please provide proof. > You don't need me to do that. There are many authoritative sources on line, at places like the FBI and the Senate Committee. If you don't believe them, you will not believe anything else that I provide. The difference between a conspiracy theory an

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > Some of the people who spread conspiracy theories are themselves corrupt. >> Some work for the Russian government. . . . > > > Is that a conspiracy theory? > Nope. It is a fact. Well documented. Proven to a fair-thee-well. If it were a conspiracy theory, there would be

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: conspiracy theories are about pattern recognition in human behaviour, and > there are conspiracy facts - > > e.g. > Tuskegee Experiment: The Infamous Syphilis Study > There are indeed, but they are few and far between. Just because some small number of conspiracy theories tu

Re: [VOTE] Airflow Providers prepared on June 15, 2022

Sorry Jarek, I was gone for a few days. +1 (binding) - checked sigs, licenses, and checksums

Re: [Vo]:Bearden dead and cheniere.org gone

I wrote: > Regarding fission reactor power density, I finally found this, by the way: > > https://aris.iaea.org/sites/core.html > > I think one of the column headings is incorrect. It says: > > Average core power density [kW/kgU] > > I think it should say: > > Average Core power density [kW/l] >

Re: [Vo]:Bearden dead and cheniere.org gone

ROGER ANDERTON wrote: > I think a lot of things are going to disappear. > I doubt it. I think you are repeating groundless conspiracy theories. No one gives a damn about Beardon's theories or disputes about relativity. No one would bother to censor these things or make them disappear. It used to

Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP?

Note this from the FAQ: Can I also use this license for projects that aren't open source, or to host private projects? No. You may use the GitLab license you receive from the GitLab for Open Source Program only for the public

Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP?

I think it's just links and screenshots. Barry Smith writes: > Crap, do you have any documents you used in the submission process so I can > reuse them? > > >> On Jun 20, 2022, at 3:41 PM, Jed Brown wrote: >> >> I submitted in February and never he

Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP?

I submitted in February and never heard back. Feel free to submit again. Barry Smith writes: > Benefits of the GitLab for Open Source Program apply to a namespace. To > qualify, every project in an applicant’s namespace must carry an OSI-approved > open source license. > > Again, GitLab when y

Re: [Vo]:Bearden dead and cheniere.org gone

Chris Zell wrote: > Google often does this in ignoring search terms, as happened to me > recently in looking for a chain saw part. Yes. I have a strange feeling Google has this problem more than it used to. I wonder if they need to tweak their algorithm? The other day I was looking for "fissio

Re: [Vo]:Bearden dead and cheniere.org gone

The ISP, Worldnic.com, appears to be offline. It can't be reached. That could be the problem. Then again, net sleuths say that worldnic.com changed its name to netsol.com, and it may now be part of networksolutions.com, which is still active. https://www.networksolutions.com/ That is who hosts t

Re: [Vo]:Bearden dead and cheniere.org gone

Whois says the Domain is still active. It is paid for through 2024. Probably, the ISP was not paid. As I said, the ISP will probably not delete the content from its servers for a while. If someone contacts them, they may help with reviving the site or transferring the data. Here is the Whois data:

Re: [Vo]:Reversing global warming and removing carbon from the atmosphere with cold fusion

Andrew Meulenberg wrote: > On the other hand, with uncontrolled population growth . . . > Population growth is not uncontrolled. On the contrary, it has largely stopped. What I mean is, the only age cohort that is growing is people in the Third World over age 40. Their numbers are increasing be

<    1   2   3   4   5   6   7   8   9   10   >