Changes between Version 13 and Version 14 of OptimizationProblems

Timestamp:

07/17/07 14:57:02 (6 years ago)

Author:

aisaac

Comment:

--

OptimizationProblems

@@ -61 +61 @@
 
 == Milestone 2 ==
- 1. Improve constrained NLP solver and/or add one more. Add 2nd derivatives where possible.
- 1. Add constraints to nonsmooth ralg solver (c<0, h=0, lb, ub, A, Aeq), as well as their derivatives
- 1. Add nonSmoothSolve - fsolve equivalent for non-smooth & noisy functions
- 1. Add GNLP (global NLP) class with solver(s) # I intend to add GRASP-based solver
- 1. Add (numerically) parallel gradient/subgradient obtaining 
+Milestone 2 is broken into four parts:
 
-After reaching the first milestone you will have familiarized yourself with !SciPy and should be able to see how to integrate your more innovative work
-into the !SciPy project.  You propose an environment that direction more.  From your proposal:  "will provide scaling, unified convinient text & graphics output, checking user-supplied analitical derivatives, parallel calculations (for example for numerical gradient/subgradient obtaining), easy comparison & unified for all solvers.)"
+1. Work on the following tickets to closure, with priority given to 296.
+   (Note that work on 296 has already started and since you are familiar
+   with tnc this should be pretty easy for you to complete.)
 
-{{{
-We need you as soon as possible to be much more specific about this. Please suggest some concrete deliverables, which we can use to affirm that you have met this milestone.
-}}}
+        http://projects.scipy.org/scipy/scipy/ticket/234
+        http://projects.scipy.org/scipy/scipy/ticket/285
+        http://projects.scipy.org/scipy/scipy/ticket/296
+        http://projects.scipy.org/scipy/scipy/ticket/377
+        http://projects.scipy.org/scipy/scipy/ticket/390
+        http://projects.scipy.org/scipy/scipy/ticket/399
+        http://projects.scipy.org/scipy/scipy/ticket/416
+        http://projects.scipy.org/scipy/scipy/ticket/344
+        http://projects.scipy.org/scipy/scipy/ticket/384
+        http://projects.scipy.org/scipy/scipy/ticket/389
+        http://projects.scipy.org/scipy/scipy/ticket/388
+   Note that you are expected to bring questions and difficulties
+   concerning these tickets to the developers list asap!  Not
+   all questions are answered the first time: rephrase and try
+   again!  If you think a ticket should be closed as "won't fix",
+   bring it before the developer community with your reasoning.
 
-For this project summer project, your should focus your environment development on the use of Scipy solvers (including the new solvers that you contribute).
+2. Make existing openopt code usable by adding docstrings, unit tests, and documented sample scripts.
+   Docstrings must conform to the standard.
+   http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines
+   Tests must conform to the TestingGuidelines
+   http://projects.scipy.org/scipy/scipy/wiki/TestingGuidelines
+   Make sure ralg and lincher are fully functional, tested, and documented,
+   completing as much as possible of your projected work on ralg
+   (i.e., constraints to nonsmooth ralg solver (c<0, h=0, lb, ub, A, Aeq),
+   as well as their derivatives).
+
+3. Improve test coverage and docstrings of existing scipy.optimize libraries.
+   Change docstrings to conform to the standard.
+   http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines
+   Tests must conform to the TestingGuidelines
+   http://projects.scipy.org/scipy/scipy/wiki/TestingGuidelines
+   Again, bring questions to the developers list in a timely fashion.
+
+4. Write some step and line search objects for the generic optimizer code.
+   (Matthieu has checked the current code base into openopt/solvers.)
+   Specifics on task will follow next week.  This will add
+   functionality to both openopt and to the optimizer as a standalone.
+   Include appropriate docstrings and unit tests.
 
 Due *August 20.*
+
+For reasons discussed elsewhere, these milestone markers replace the previous
+markers for milestone 2.  Advance on those markers is of course welcome,
+but progress will be judged by the milestones above.
+
+Since you have passed the first milestone,
+you should be familiar enough with !SciPy and that you can see how to integrate your more work
+into the !SciPy project.  
+
+
+From your proposal:  "will provide scaling, unified convinient text & graphics output, checking user-supplied analitical derivatives, parallel calculations (for example for numerical gradient/subgradient obtaining), easy comparison & unified for all solvers.)"
+As stated from the beginning,
+for this summer project,
+your should focus your development on the use of Scipy solvers (including the new solvers that you contribute).
+This now includes the generalized optimization framework contributed by Matthieu Brucher.
+
 
 = Documentation and development methodology =