Check runtime warning, error, "INFO" messages, and establish BG standard

[bobleesj]

Problem

We want to re-visit run-time warning/info/error messages since the following comment was provided by @sbillinge:

---

This is supposed to be an info not a warning. I think we want INFO and change wmsg to imsg in the name. Make sure it is a print and not a warning.warn in the code.

The group standard could be that a warning means that something is wrong, albeit not error generating.

Here it is "expected" that we will have infinities sometimes and we want to handle them if possible. So nothing is wrong but we want the user to alerted so they understand any magic.

Not sure if that all makes sense.

Originally posted by @sbillinge in #255 (comment)

---

Proposed solution

For all runtime messages, review and document how our group wants to write effective runtime messages.

[bobleesj]

@sbillinge I think you've already fixed in one of the PRs:

print used for "i"

warn used for wmsg

raise used for emsg

I will close this