You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been a while since this issue was posted; I'm not sure why it's a problem that you can still click the button to "inject" after the simulation has finished, as it doesn't make any difference to the results and doesn't cause anything to crash.
this would likely cause a issue with multi run. think of this:
run
complete first run
inject....oh lets say 17 packets to a core on 0,0.
so now the buffer (i think is 16 in size) on the core is full, and 1 is bouncing back and forth from the router and the core. might get dropped, but might not
send new runtime, crashes due to that core being full of buffered injected packets that haven't been processed due to the core not receiving packets
or even worse, it doesnt fail, and now youve got a massive burst from that core when it starts up again in the second run.
either case is not ideal. I guess we just put the injector onto a safety check and blow up if you ask to inject when its in pause state
When the simulation finishes, I can still inject
The text was updated successfully, but these errors were encountered: