revisit simulation.find_next_active_node
revisit simulation.find_next_active_node

With the latest changes, find_next_active_node is once again taking up a sizable chunk of execution time (11%).
Removing list comprehensions makes the code a bit more unsightly, but it reduces the time share to just 4.5%.

geraintpalmer/Ciw,CiwPython/Ciw