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 would be helpful (although not necessary for performance or other reasons) it QUDA could show some 'sign-of-life' while tuning (e.g. the unix. / - \ | / - \ | spinny, or just a '.' on the master node every now and again). This way, when there is a long tuning period, the users can tell that the code hasn't hung. Just an idea, but definitely not the most urgent thing.
The text was updated successfully, but these errors were encountered:
Most of the time we don't really want much output, especially when called from a third party app. Depending on the usage, I would be happy if we can have a stack trace printed after receiving a SIGUSR1.
It would be helpful (although not necessary for performance or other reasons) it QUDA could show some 'sign-of-life' while tuning (e.g. the unix. / - \ | / - \ | spinny, or just a '.' on the master node every now and again). This way, when there is a long tuning period, the users can tell that the code hasn't hung. Just an idea, but definitely not the most urgent thing.
The text was updated successfully, but these errors were encountered: