Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 14 01:33
    poulson closed #276
  • May 14 01:33
    poulson commented #276
  • May 14 01:30

    poulson on master

    Update README.md (compare)

  • May 14 01:24

    poulson on master

    added logo (compare)

  • May 10 21:37
    jedbrown commented #276
  • May 10 21:25
    poulson commented #276
  • May 10 21:21
    jedbrown commented #276
  • May 10 17:08
    poulson commented #276
  • May 10 17:03
    tesch1 opened #276
  • Apr 10 13:18
    JM1 commented #275
  • Apr 10 13:16
    JM1 synchronize #275
  • Apr 10 08:56
    JM1 opened #275
  • Mar 06 03:47
    Raviteja1996 closed #274
  • Mar 05 05:46
    Raviteja1996 opened #274
  • Feb 11 21:53
    BenBrock commented #228
  • Feb 11 21:52
    BenBrock commented #228
  • Feb 11 21:51
    poulson commented #228
  • Feb 11 21:50
    poulson commented #228
  • Feb 11 21:45
    BenBrock commented #228
  • Jan 23 23:57
    adambaskerville commented #273
Ryan H. Lewis
@rhl-
its not really high quality
you presumably have a distributed hessenberg already
Jack Poulson
@poulson
even if it isn't, it's an impressive goal
yes, Elemental has distributed blocked algorithms for reducing to Hessenberg form
Ryan H. Lewis
@rhl-
this used boost::ublas
i didn't know about elemental then
Jack Poulson
@poulson
there are sequential Aggressive Early Deflation Hessenberg QR algorithms but not yet a distributed version
Ryan H. Lewis
@rhl-
yeah so the QR iteration looks like its only serial, and the hessenberg is distributed
Ryan H. Lewis
@rhl-
So, I wanted to take a stab at the documentation
i was wondering if you have seen/considered cldoc ?
Jack Poulson
@poulson
does it support LaTeX?
ReadTheDocs is the gold standard ATM
Ryan H. Lewis
@rhl-
im not sure
the thing is that it autogenerates documentation with a doc coverage report
I was just wondering how to get a sense of what is needed and what is missing
also I was looking the ADMM solver for logisitic regression
do you know what is needed there?
and do you have an LBFGS?
Jack Poulson
@poulson
what is needed in the docs is well-designed tutorials and content
autogeneration is not very helpful IMO
it is helpful as a reference but not as an introduction
Ryan H. Lewis
@rhl-
i guess I was just thinking about understanding what is missing
Jack Poulson
@poulson
what is missing is a complete rewrite
Ryan H. Lewis
@rhl-
well, a reference for the API's is super useful
Jack Poulson
@poulson
that's what the header files are
Ryan H. Lewis
@rhl-
and the stuff you have looks good
no, thats not the same
there are things like preconditions and post conditions
and the Latex statements of the equations you solve inform you what the headers do
why do you want a complete rewrite, for me, most of the content has been largely accurate
Jack Poulson
@poulson
huge amounts of things are completely undocumented
and huge amounts are out of date
there is virtually nothing there on the sparse functionality
there is nothing on the lattice reduction
there is nothing on the support for higher precision
Ryan H. Lewis
@rhl-
right, so, thats why documentation coverage is useful, right?
Jack Poulson
@poulson
there is nothing on the D&C SVD or EVD
there is nothing on the AED Hessenberg QR implementation
there is nothing on the number theory support
Ryan H. Lewis
@rhl-
right, so, you see what I am saying?
generating coverage is a good first step
so autogeneration could perhaps give us a sense of where we are missing stuff
Jack Poulson
@poulson
perhaps, but I do not consider autogenerated things to be documentation
it is more so scaffolding for documentation
Ryan H. Lewis
@rhl-
yeah, exactly
Jack Poulson
@poulson
but it doesn't suggest any path for the user to learn how to use the library
Ryan H. Lewis
@rhl-
yeah, that makes sense
its likely that more people would be interested in tutorials for the bindings
than tutorials for C++ code itself