Closed white238 closed 1 year ago
@dawson6 Do we want to have "ATS" as a prefix to our printed and logged statements? Is it a common problem to have many error or warning messages that are mixed from different codes and it isn't clear who/what is causing the issue?
Based on Chris' suggestion the statements can be fairly simple, so maybe there isn't much confusion between codes and log/print messages.
We also have raise/except AtsError, should that be used in some way so that we aren't printing and logging Error by hand?
I think standardizing on ATS as the prefix for messages sounds fine.
@MishaZakharchanka has addressed this with a MR.
Having a consistent prefix for logging messages across ATS is helpful when searching logs. Something like:
"ERROR:"
"WARNING: "