by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 02 14:21
    ernstbrunr51 commented #278
  • Apr 29 20:49
    yurivict opened #278
  • Apr 24 18:55
    ernstbrunr51 closed #277
  • Apr 24 18:55
    ernstbrunr51 commented #277
  • Apr 24 18:04
    poulson commented #277
  • Apr 24 10:34
    ernstbrunr51 opened #277
  • May 14 2019 01:33
    poulson closed #276
  • May 14 2019 01:33
    poulson commented #276
  • May 14 2019 01:30

    poulson on master

    Update README.md (compare)

  • May 14 2019 01:24

    poulson on master

    added logo (compare)

  • May 10 2019 21:37
    jedbrown commented #276
  • May 10 2019 21:25
    poulson commented #276
  • May 10 2019 21:21
    jedbrown commented #276
  • May 10 2019 17:08
    poulson commented #276
  • May 10 2019 17:03
    tesch1 opened #276
  • Apr 10 2019 13:18
    JM1 commented #275
  • Apr 10 2019 13:16
    JM1 synchronize #275
  • Apr 10 2019 08:56
    JM1 opened #275
  • Mar 06 2019 03:47
    Raviteja1996 closed #274
  • Mar 05 2019 05:46
    Raviteja1996 opened #274
Jack Poulson
@poulson
it has been a while since the switch was made to a separate elemental-web page, which was more general and for the whole website
it used to be that the GitHub repo served the docs as well
Ryan H. Lewis
@rhl-
ah, I see
that is not necessary :)
we can use jenkins to update the docs nightly
Jack Poulson
@poulson
there still needs to be a repo for the website itself
and it's useful to have the docs there
Ryan H. Lewis
@rhl-
yeah, that can stay where it is
Jack Poulson
@poulson
unless the website repo is supposed to pull from the main repo
Ryan H. Lewis
@rhl-
you can use jenkins to do all of this
exactly how its setup is somewhat irrelevant
you can compile and copy and commit or use git submodules
Jack Poulson
@poulson
git submodules should be avoided at all costs due to not being supported by GitHub
Ryan H. Lewis
@rhl-
ok, I mean, all I am saying is that its just a small bash script
whatever it is
and it can be stuck in jenkins
Jack Poulson
@poulson
sounds fine to me now that there is a Jenkins
Ryan H. Lewis
@rhl-
is the next release v 0.87 ?
Jack Poulson
@poulson
yes, given the mess around releasing 0.86, let's 86 the 0.86 release
Ryan H. Lewis
@rhl-
want to say we will release Sep 3?
Jack Poulson
@poulson
we should release when we have packages ready
Ryan H. Lewis
@rhl-
debian packages?
Jack Poulson
@poulson
which seems to require ditching ScaLAPACK
which seems to require me implementing a distributed Hessenberg QR
Ryan H. Lewis
@rhl-
ok
I think we should follow a "train leaving the station" model
Jack Poulson
@poulson
METIS and ParMETIS will still cause headaches
Elemental needs its own AMD reorderings anyway
Ryan H. Lewis
@rhl-
I've created the GitHub Milestone, and i'm adding issues.
Jack Poulson
@poulson
thanks!
Ryan H. Lewis
@rhl-
What was the thing you added recently? was there an issue for it?
the D&C SVD?
Jack Poulson
@poulson
something in the middle of my preference to add functionality forever and your desire to release every day is likely the right compromise
Ryan H. Lewis
@rhl-
lol
Jack Poulson
@poulson
the D&C SVD was to greatly improve the distributed SVD performance
and also the high-precision sequential SVD perf.
Ryan H. Lewis
@rhl-
Distributed D&C ?
Jack Poulson
@poulson
yes, distributed D&C EVD and SVD needs to be stress tested
Ryan H. Lewis
@rhl-
what is EVD?
Jack Poulson
@poulson
eigenvalue decomposition
Ryan H. Lewis
@rhl-
ah
Jack Poulson
@poulson
the Travis tests are completely irrelevant when it comes to testing the distributed functionality
Ryan H. Lewis
@rhl-
was there already issues for D&C ?
Jack Poulson
@poulson
there was no D&C support in Elemental until a week or two ago
jedbrown @jedbrown cheers impending removal of ScaLAPACK.
Jack Poulson
@poulson
I don't recall creating an issue for it
LOL
yes, distributed Hessenberg QR is the last step
the coda will be a faster implementation of the element-wise <-> block-wise redistributions
why did you create and immediately close an issue?