Changes between Initial Version and Version 1 of Ticket #1423, comment 20
- Timestamp:
- 04/30/13 11:12:35 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1423, comment 20
initial v1 1 Please consider following points:2 * LbfgsAlgorithm3 * The solution creator should be casted to an `IRealVectorCreator` instead of the concrete implementation `RealVectorCreator`4 * Assigning `name` and `description` from `Item(Name|Description)` in the default ctor usually needs to be done only if directly derived from NamedItem.1 r9408:9409: 2 * ~~LbfgsAlgorithm~~ 3 * ~~The solution creator should be casted to an `IRealVectorCreator` instead of the concrete implementation `RealVectorCreator`~~ 4 * ~~Assigning `name` and `description` from `Item(Name|Description)` in the default ctor usually needs to be done only if directly derived from NamedItem.~~ 5 5 * The problem specific analyzers are not run on the solution. In the case of test functions it could be interesting to e.g. view the trajectory of the solution in 2D problems. 6 * You don't need to append "(placeholder)" to the operator's name. The type will be shown in the graph view if the name deviates, just put the name in braces "(Evaluator)" to have some distinction.7 * You could add another hidden parameter "GradientCheckStepSize", if it's > 0 you could enable gradient check in the initializer.8 * LbfgsInitializer9 * check if "GradientCheckStepSize" exists and is > 0 to enable gradient check6 * ~~You don't need to append "(placeholder)" to the operator's name. The type will be shown in the graph view if the name deviates, just put the name in braces "(Evaluator)" to have some distinction.~~ 7 * ~~You could add another hidden parameter "GradientCheckStepSize", if it's > 0 you could enable gradient check in the initializer.~~ 8 * ~~LbfgsInitializer~~ 9 * ~~check if "GradientCheckStepSize" exists and is > 0 to enable gradient check~~ 10 10 11 11 r9405:9406: … … 14 14 * ~~-7 gradient verification failed~~ 15 15 * ~~-1 incorrect parameters~~ 16
