Seg fault when fitness gets too high
anyaevostinar opened this issue · comments
When fitness gets crazy, the scheduler can throw a seg fault.
What kind of behavior would you like aside from "halt and catch fire?" We could make merit larger, but its max value is pretty large as it stands.
A more intentional (and informative) version of "halt and catch fire" would be ideal.
(assuming I'm correct that it's already a double?)
Yeah, it's a double.
Probably the easiest way to handle this is to make sure that nothing enters the scheduler if it has a non-finite double-valued merit. We can't consider all the cases where merit will be used or abused, but during an actual experiment, it'll definitely hit the scheduler and break it. Since the scheduling is done at a base-level in the code I can just send a simple error feedback message and terminate.