Hi Juan, currently the simulator will be terminated immediately after encountering overflow floating point exception when evaluating the node/edge/element value.
I think it would be better if the devsim.solve function can return the overflow information and continue to the next statement instead of quitting.
This feature will benefit the sweeping. Because sometimes the overflow is induced by too large step size. And once got the overflow exception, the program can go back and try a smaller step. Just like the following process:
while v_prev < target: result=devsim.solve(type="dc", absolute_error=1e10, relative_error=1e-3, maximum_iterations=30,info=True) if result['is_overflow'] : v_step *= decr_factor if v_step<v_step_min : [...] break v = v_prev + v_step continue else: [...] step_size *= incr_factor v_prev = v v = v_prev + step_size