You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one trait is on the boundary assembly generate an error because of the function nmkb in maximize_logspace. As stated in the documentation of dfoptim::nmkb the starting value (of the traits for the optimisation of the fitness) should be stricly between the lower and upper bounds (A starting vector of parameter values. Must be feasible, i.e. lie strictly between
lower and upper bounds.).
One solution could be to had an exception handling in 'community_new_types_maximum_fitness ' as it is done for other convergence problem such as
if (attr(ret, "fitness") < eps_positive_fitness) {
plant_log_max_fitness(paste0("Best point had nonpositive fitness: ",
attr(ret, "fitness")))
return(empty(sys, ret))
}
The text was updated successfully, but these errors were encountered:
kunstler
changed the title
Error in find_max_fitness_2d if traits value on the boundary
Error in find_max_fitness_2d if trait value on the boundary
Jan 4, 2018
dfalster
changed the title
Error in find_max_fitness_2d if trait value on the boundary
[evol assembly] Error in find_max_fitness_2d if trait value on the boundary
Jun 18, 2024
If one trait is on the boundary assembly generate an error because of the function
nmkb
inmaximize_logspace
. As stated in the documentation ofdfoptim::nmkb
the starting value (of the traits for the optimisation of the fitness) should be stricly between the lower and upper bounds (A starting vector of parameter values. Must be feasible, i.e. lie strictly betweenlower and upper bounds.).
see https://github.com/traitecoevo/trait_gradients/issues/38
One solution could be to had an exception handling in 'community_new_types_maximum_fitness ' as it is done for other convergence problem such as
The text was updated successfully, but these errors were encountered: