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
While I don't think this option should be defaulted on. While running with sims with hardware in the loop it can be very useful to get the stack trace when a sim calls exec terminate. For the AA2 project we even had a special branch of trick that did this for us. A lot of times we end up taking sims we didn't write and have to include hardware interface into them. So we often run into exec terminate lines that aren't as useful as they could be. So getting the add information of the stack trace can give us more information to figure out what the issue is that caused the exec terminate to be called. This helps reduce the number of iterations needed to solve the problem. I doubt most people would want this feature on by default but I would consider it a best practices to use it with hardware in the loop type sims.
The text was updated successfully, but these errors were encountered:
While I don't think this option should be defaulted on. While running with sims with hardware in the loop it can be very useful to get the stack trace when a sim calls exec terminate. For the AA2 project we even had a special branch of trick that did this for us. A lot of times we end up taking sims we didn't write and have to include hardware interface into them. So we often run into exec terminate lines that aren't as useful as they could be. So getting the add information of the stack trace can give us more information to figure out what the issue is that caused the exec terminate to be called. This helps reduce the number of iterations needed to solve the problem. I doubt most people would want this feature on by default but I would consider it a best practices to use it with hardware in the loop type sims.
The text was updated successfully, but these errors were encountered: