-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review of OpenMG: A New Multigrid Implementation in Python #14
Comments
Independent Review ReportReviewer: Bill Spotz Department/Center/Division: Computing Research Institution/University/Company: Sandia National Laboratories Field of interest / expertise: Scientific computing Country: USA Article reviewed: OpenMG: A New Multigrid Implementation in Python GENERAL EVALUATIONPlease rate the paper using the following criteria (please use the abbreviation below doesn't meet standards for academic publication
SPECIFIC EVALUATIONFor the following questions, please respond with 'yes' or 'no'. If you
|
Annotations from @wfspotz: https://dl.dropboxusercontent.com/u/41803709/SciPy12-02.pdf |
ping: @tsbertalan This is ready for author response. |
Reviewer: Hans Petter Langtangen
Department/Center/Division: Center for Biomedical Computing
Institution/University/Company: Simula Research Laboratory
Field of interest / expertise: Scientific Computing, Mathematical Modeling
Country: Norway
Article reviewed: See title.
Quality of the approach: meets
Quality of the writing: meets
Quality of the figures/tables: meets
SPECIFIC EVALUATION
For the following questions, please respond with 'yes' or 'no'. If you answer 'no', please provide a brief, one- to two-sentence explanation.
Please suggest specific improvements and indicate whether you think the article needs a significant rewrite (rather than a minor revision).
Review
OpenMG is a very nice tool for understanding how the multigrid method works. The article is well written and easy to follow, and can be published after a minor revision.
My main criticism is that there should be a closer relationship between the code and the corresponding mathematical description. Make sure the variable names mimic the symbols in the mathematics. Also be more consistent internally in the code (
problemshape
vsshape
,.size
vslen()
). The initialization of a list bylist(range(n))
is misleading - the idea is to make a list of a fixed length with uninitialized elements, more clearly obtained by[None]*n
.Minor points
The text was updated successfully, but these errors were encountered: