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
We need to catch and raise HOOMD errors instead of just logging them and proceeding.
Currently, not doing this gives no information relevant to where the actual failure occurred and instead failures somewhere in the RDF calculation when it realizes that there's no trajectory to read.
The text was updated successfully, but these errors were encountered:
We can use PIPE to get the results back into variables instead of logging to a file. I'm not exactly sure what happens to errors raised on subprocesses but I guess we'll find out.
We need to catch and raise HOOMD errors instead of just logging them and proceeding.
Currently, not doing this gives no information relevant to where the actual failure occurred and instead failures somewhere in the RDF calculation when it realizes that there's no trajectory to read.
The text was updated successfully, but these errors were encountered: