13 | | * ~~Some properties (e.g., Weights, PC, ... ) are compared by == although they contain reference types like double[] or double[,]. Therefore, a change event is fired even if the values are the same.~~ |
14 | | |
15 | | I removed change notification altogether. |
| 13 | * ~~Some properties (e.g., Weights, PC, ... ) are compared by == although they contain reference types like double[] or double[,]. Therefore, a change event is fired even if the values are the same.~~ - //I removed change notification altogether.// |
19 | | * Line 129: Is it intentional that the real vector gets only corrected if MaxTries > 1? And why exactly was 1 chosen as comparison value? |
20 | | * IMHO the behavior that out of bounds dimension are resampled is OK and also the truncation is reasonable. Maybe the number of maximum tries could be reduced to 100 to save some execution time. |
21 | | |
22 | | I added an extra parameter that controls if you want to always truncate the point at the bounds or if you allow sampled points outside the bounds. The second way is preferred if your evaluation function can handle such points through penalties. |
| 17 | * ~~Line 129: Is it intentional that the real vector gets only corrected if MaxTries > 1? And why exactly was 1 chosen as comparison value?~~ - //I added an extra parameter that controls if you want to always truncate the point at the bounds or if you allow sampled points outside the bounds. The second way is preferred if your evaluation function can handle such points through penalties.// |
| 18 | * ~~IMHO the behavior that out of bounds dimension are resampled is OK and also the truncation is reasonable. Maybe the number of maximum tries could be reduced to 100 to save some execution time.~~ |