home.social

Search

82 results for “jedbrown”

  1. @jedbrown
    > increase research income >10% by ignoring IP.

    So what you're saying is it is cheaper to account for getting sued for IP infringements and having to pay than to pay for it beforehand then?

    #NotLegalAdvice
    #law

  2. @jedbrown
    > increase research income >10% by ignoring IP.

    So what you're saying is it is cheaper to account for getting sued for IP infringements and having to pay than to pay for it beforehand then?

    #NotLegalAdvice
    #law

  3. @jedbrown
    > increase research income >10% by ignoring IP.

    So what you're saying is it is cheaper to account for getting sued for IP infringements and having to pay than to pay for it beforehand then?

    #NotLegalAdvice
    #law

  4. @jedbrown
    > increase research income >10% by ignoring IP.

    So what you're saying is it is cheaper to account for getting sued for IP infringements and having to pay than to pay for it beforehand then?

    #NotLegalAdvice
    #law

  5. @jedbrown
    > increase research income >10% by ignoring IP.

    So what you're saying is it is cheaper to account for getting sued for IP infringements and having to pay than to pay for it beforehand then?

    #NotLegalAdvice
    #law

  6. @gvwilson I mention numerical/scientific software because that's the area I work in, but also, our software lifecycle is long (many packages are over 30 years old) with a cultural appetite for excusing poor user and developer experience (cf. "Firetran" jedbrown.org/files/BrownKneple).

    Ex: For linear algebra, #PETSc represented a radical shift from the BLAS/LAPACK philosophy at the time. But PETSc has its share of baked-in architecture, as do mature packages throughout the ecosystem.

  7. @gvwilson I mention numerical/scientific software because that's the area I work in, but also, our software lifecycle is long (many packages are over 30 years old) with a cultural appetite for excusing poor user and developer experience (cf. "Firetran" jedbrown.org/files/BrownKneple).

    Ex: For linear algebra, #PETSc represented a radical shift from the BLAS/LAPACK philosophy at the time. But PETSc has its share of baked-in architecture, as do mature packages throughout the ecosystem.

  8. @gvwilson I mention numerical/scientific software because that's the area I work in, but also, our software lifecycle is long (many packages are over 30 years old) with a cultural appetite for excusing poor user and developer experience (cf. "Firetran" jedbrown.org/files/BrownKneple).

    Ex: For linear algebra, represented a radical shift from the BLAS/LAPACK philosophy at the time. But PETSc has its share of baked-in architecture, as do mature packages throughout the ecosystem.

  9. @gvwilson I mention numerical/scientific software because that's the area I work in, but also, our software lifecycle is long (many packages are over 30 years old) with a cultural appetite for excusing poor user and developer experience (cf. "Firetran" jedbrown.org/files/BrownKneple).

    Ex: For linear algebra, #PETSc represented a radical shift from the BLAS/LAPACK philosophy at the time. But PETSc has its share of baked-in architecture, as do mature packages throughout the ecosystem.

  10. @gvwilson I mention numerical/scientific software because that's the area I work in, but also, our software lifecycle is long (many packages are over 30 years old) with a cultural appetite for excusing poor user and developer experience (cf. "Firetran" jedbrown.org/files/BrownKneple).

    Ex: For linear algebra, #PETSc represented a radical shift from the BLAS/LAPACK philosophy at the time. But PETSc has its share of baked-in architecture, as do mature packages throughout the ecosystem.

  11. @[email protected] Indeed, upgrading the #RiemannSolver to #HLLC (which includes a contact wave) from #HLL (which only estimates the acoustic waves) fixes this problem. Here's a pair of oblique bubble simulations to campare HLLC (left) with HLL (right). Unlike most cases with finite volume methods (which use Riemann solvers at every grid interface), a high quality solver is important for continuous Galerkin FE boundary conditions.

  12. @[email protected] Indeed, upgrading the #RiemannSolver to #HLLC (which includes a contact wave) from #HLL (which only estimates the acoustic waves) fixes this problem. Here's a pair of oblique bubble simulations to campare HLLC (left) with HLL (right). Unlike most cases with finite volume methods (which use Riemann solvers at every grid interface), a high quality solver is important for continuous Galerkin FE boundary conditions.

  13. @[email protected] Indeed, upgrading the to (which includes a contact wave) from (which only estimates the acoustic waves) fixes this problem. Here's a pair of oblique bubble simulations to campare HLLC (left) with HLL (right). Unlike most cases with finite volume methods (which use Riemann solvers at every grid interface), a high quality solver is important for continuous Galerkin FE boundary conditions.

  14. @[email protected] Indeed, upgrading the #RiemannSolver to #HLLC (which includes a contact wave) from #HLL (which only estimates the acoustic waves) fixes this problem. Here's a pair of oblique bubble simulations to campare HLLC (left) with HLL (right). Unlike most cases with finite volume methods (which use Riemann solvers at every grid interface), a high quality solver is important for continuous Galerkin FE boundary conditions.

  15. Interesting paper by @jedbrown et al.

    doi.org/10.48550/arXiv.2401.13

    For computational mechanics/physics, if you code by just punching in the equations from the textbooks directly, the physics should work, but computationally the way you evaluate the quantities may be unstable. This paper lists some recipes to avoid these.

    Mostly small strain problem, but still feels icky to leave in.

    @mofem @likask @koehlerson

  16. @fclc @hattom @jedbrown this is great news ! Could you forward the thread to me ? I heard they were doing that but I would like to update the community build I am working on to reflect that .. #volunteersneeded

  17. Have just successfully evaluated a Green's fct. matrix via and on Apple Silicon GPU Cores. Holiday programming project coming along well 😃

    @jedbrown @mscroggs

  18. What if Everything is Free? Exploring The #LibraryOfThings Concept

    "Research has shown that people are increasingly open to collaborative consumption, with studies indicating a rising willingness to share goods instead of purchasing them outright."

    by Jed Brown, Feb 19, 2025

    "In today’s consumer-driven society, the idea of ownership is so deeply ingrained that imagining a world where everything is free can seem radical — if not downright impossible.

    Yet, emerging initiatives like the Library of Things invite us to reconsider our relationship with material goods. Rather than accumulating items, communities are experimenting with a model where objects are shared rather than owned."

    Read more:
    medium.com/@jedbrown99/what-if

    #SolarPunkSunday #SharingEconomy #LibrariesOfThings #BorrowDontBuy #Degrowth #LibrariesOfThings #Decapitalize

  19. What if Everything is Free? Exploring The #LibraryOfThings Concept

    "Research has shown that people are increasingly open to collaborative consumption, with studies indicating a rising willingness to share goods instead of purchasing them outright."

    by Jed Brown, Feb 19, 2025

    "In today’s consumer-driven society, the idea of ownership is so deeply ingrained that imagining a world where everything is free can seem radical — if not downright impossible.

    Yet, emerging initiatives like the Library of Things invite us to reconsider our relationship with material goods. Rather than accumulating items, communities are experimenting with a model where objects are shared rather than owned."

    Read more:
    medium.com/@jedbrown99/what-if

    #SolarPunkSunday #SharingEconomy #LibrariesOfThings #BorrowDontBuy #Degrowth #LibrariesOfThings #Decapitalize

  20. PSA: #ParkMobile either sells their address books to phishers or their databases were hacked and they haven't informed customers. It's a good thing they don't have a monopoly or anything.

    (I use a unique email address and recently started receiving low-budget phishing attempts at that address.)

  21. 🚀 #PETSc 3.21 was released today. There were a number of new contributors this release; thank you all.
    lists.mcs.anl.gov/pipermail/pe

    A few highlights:
    * VecMDot and (optionally) VecMAXPY can identify strided memory and use gemv when applicable. This is faster than home-rolled kernels on some GPUs.
    * GAMG: new filtering and smoothing options for algebraic multigrid.
    * Small subdomain (many per process) BDDC support
    * Trust region and quasi-Newton trust region improvements.

    petsc.org/release/changes/321/

  22. 🚀 #PETSc 3.21 was released today. There were a number of new contributors this release; thank you all.
    lists.mcs.anl.gov/pipermail/pe

    A few highlights:
    * VecMDot and (optionally) VecMAXPY can identify strided memory and use gemv when applicable. This is faster than home-rolled kernels on some GPUs.
    * GAMG: new filtering and smoothing options for algebraic multigrid.
    * Small subdomain (many per process) BDDC support
    * Trust region and quasi-Newton trust region improvements.

    petsc.org/release/changes/321/

  23. 🚀 3.21 was released today. There were a number of new contributors this release; thank you all.
    lists.mcs.anl.gov/pipermail/pe

    A few highlights:
    * VecMDot and (optionally) VecMAXPY can identify strided memory and use gemv when applicable. This is faster than home-rolled kernels on some GPUs.
    * GAMG: new filtering and smoothing options for algebraic multigrid.
    * Small subdomain (many per process) BDDC support
    * Trust region and quasi-Newton trust region improvements.

    petsc.org/release/changes/321/

  24. 🚀 #PETSc 3.21 was released today. There were a number of new contributors this release; thank you all.
    lists.mcs.anl.gov/pipermail/pe

    A few highlights:
    * VecMDot and (optionally) VecMAXPY can identify strided memory and use gemv when applicable. This is faster than home-rolled kernels on some GPUs.
    * GAMG: new filtering and smoothing options for algebraic multigrid.
    * Small subdomain (many per process) BDDC support
    * Trust region and quasi-Newton trust region improvements.

    petsc.org/release/changes/321/

  25. 🚀 #PETSc 3.21 was released today. There were a number of new contributors this release; thank you all.
    lists.mcs.anl.gov/pipermail/pe

    A few highlights:
    * VecMDot and (optionally) VecMAXPY can identify strided memory and use gemv when applicable. This is faster than home-rolled kernels on some GPUs.
    * GAMG: new filtering and smoothing options for algebraic multigrid.
    * Small subdomain (many per process) BDDC support
    * Trust region and quasi-Newton trust region improvements.

    petsc.org/release/changes/321/

  26. Amazing work from Sarah El-Kazdadi. #LibXSMM has become standard for applications needing small, dense matrix multiply/tensor contraction. It uses JIT, which was widely believed to be necessary to achieve high performance in this domain. Sarah's new library, #nanogemm, is competitive or better without JIT (modulo a caveat about padding). #Rust #HPC #GEMM

    sarah-ek.veganb.tw/blog/nano-g

  27. Amazing work from Sarah El-Kazdadi. #LibXSMM has become standard for applications needing small, dense matrix multiply/tensor contraction. It uses JIT, which was widely believed to be necessary to achieve high performance in this domain. Sarah's new library, #nanogemm, is competitive or better without JIT (modulo a caveat about padding). #Rust #HPC #GEMM

    sarah-ek.veganb.tw/blog/nano-g

  28. Amazing work from Sarah El-Kazdadi. has become standard for applications needing small, dense matrix multiply/tensor contraction. It uses JIT, which was widely believed to be necessary to achieve high performance in this domain. Sarah's new library, , is competitive or better without JIT (modulo a caveat about padding).

    sarah-ek.veganb.tw/blog/nano-g

  29. Amazing work from Sarah El-Kazdadi. #LibXSMM has become standard for applications needing small, dense matrix multiply/tensor contraction. It uses JIT, which was widely believed to be necessary to achieve high performance in this domain. Sarah's new library, #nanogemm, is competitive or better without JIT (modulo a caveat about padding). #Rust #HPC #GEMM

    sarah-ek.veganb.tw/blog/nano-g

  30. Amazing work from Sarah El-Kazdadi. #LibXSMM has become standard for applications needing small, dense matrix multiply/tensor contraction. It uses JIT, which was widely believed to be necessary to achieve high performance in this domain. Sarah's new library, #nanogemm, is competitive or better without JIT (modulo a caveat about padding). #Rust #HPC #GEMM

    sarah-ek.veganb.tw/blog/nano-g