Access probes during the simulation (using NengoDL)

Yes, you should be able to replace 10 with simulation_time / dt to get the equivalent of sim.run(simluation_time).

In standard Nengo, I can confidently say that there shouldn’t be a performance difference between the two approaches. With NengoDL though, I am not as confident. Looking at the NengoDL code base, if you are using the NengoDL simulator like the Nengo simulator (i.e., you aren’t using it to do any batch runs, or have a non-default minibatch_size parameter), then it should have no performance difference. Otherwise, running sim.run may be faster than doing the for loop. I’ll have to double check with the author of NengoDL, but he’s on holiday and won’t be back until the new year.

If you do want to do batch runs, and think that there may be a performance impact, then you might have to modify the logging of data to use the Nengo process approach as I outlined in this post (see The more Nengo way).