Is it possible to track "value explosions" and out of range errors
Posted: Thu Jul 23, 2020 9:43 pm
Hello,
I am working on creating my own mechanism .mod file and running into large value errors such as:
Without getting into too much detail, the mechanism works completely fine without any "out of range" errors when running on a single processor without any parallelization.
However, once I start simulating over a large neuronal network (across anywhere between 50 to 100 CPUs), I begin seeing multiple out of range errors. The main problem is that the errors are not specifying which variable is "exploding" making it difficult for me to know where the origin of the error is. I've tried using h.Vector() to record the different variables, but it seems that only some instantiations (over millions) of the mechanism are exploding making it hard to pinpoint the problem.
Is there anything I can do to help specify or print out where these out of range values are actually originating from? Thanks.
I am working on creating my own mechanism .mod file and running into large value errors such as:
Code: Select all
exp(1.86734e+184) out of range, returning exp(700)
No more errno warnings during this execution
However, once I start simulating over a large neuronal network (across anywhere between 50 to 100 CPUs), I begin seeing multiple out of range errors. The main problem is that the errors are not specifying which variable is "exploding" making it difficult for me to know where the origin of the error is. I've tried using h.Vector() to record the different variables, but it seems that only some instantiations (over millions) of the mechanism are exploding making it hard to pinpoint the problem.
Is there anything I can do to help specify or print out where these out of range values are actually originating from? Thanks.