http://pyamg.googlecode.com/svn/branches/1.0.x/Docs/html/pyamg.vis.html In the example forpyamg.vis.vis_coarse.vis_aggregate_group(), the line "from vis_coarse import vis_aggregate_groups" should be changed to "from pyamg.vis.vis_coarse import vis_aggregate_groups"
http://code.google.com/p/pyamg/wiki/PyAMGFunctionality There is a missing link in the sentence "Full documentation can be found here"
http://code.google.com/p/pyamg/wiki/Tutorial In a couple of paragraphs, the wording is weird/broken. (Please note that I am not a native English speaker, but) I guess the following paragraph: "Here we can see that 7 levels are constructed until a coarse level of 4 (<max_coarse=10) is found. The operator complexity (the total nnz on the fine grid compares to the total nnz on all levels) is moderates low, and the grid complexity (total dof on the finest level compared with the fine level) is low. Also the coarsest level solve set at a pseudo-inverse (pinv2).
Now we can start a places holder for the residuals, initialize a right-hand-side to Ax=b, and give the solver an initial guess x0:"
could be changed to something like: "Here we can see that 7 levels are constructed until a coarse level of 4 (<max_coarse=10) is achieved. The operator complexity (the total nnz on the fine grid compared to the total nnz on all levels) is moderately low, and the grid complexity (total dof on the finest level compared to the fine level) is low. Also the coarsest level solver is set to pseudo-inverse (pinv2).
Now we can initialize a place-holder for the residuals, set right-hand-side to Ax=b, and run the solver with initial guess x0:"
Comment #1
Posted on Sep 22, 2010 by Helpful RabbitThere were 19 duplicates of this issue, which I closed.
Comment #2
Posted on Sep 22, 2010 by Helpful PandaSorry about that! I found that my proxy connection had expired just when I hit the submit button. I guess by browser caused the the flood, while it was retrying to "Submit" the http request (and indeed the first thing I got after I re-logged in was an error page)
Comment #3
Posted on Sep 29, 2010 by Happy Elephant(No comment was entered for this change.)
Comment #4
Posted on Nov 6, 2010 by Helpful RabbitHi Ivan,
The documentation should now be fixed. I only changed the documentation related to your first suggestion in the SVN. The next release's documentation will then reflect this change.
Thanks for the help!
Jacob
Comment #5
Posted on Jul 8, 2013 by Happy Elephantmoved to github: https://github.com/pyamg/pyamg/issues
Status: Fixed
Labels:
Type-Other
Priority-Low
OpSys-All
Milestone-Release1.1
Component-Docs