opened
white238
username_0
* Adds SLIC logging functionality
* Add an exit function that cleans stuff up (serac::exit_gracefully(bool error=false)
* Starts using the new serac C++ namespace

I haven't gone through any of the code other than the driver yet but wanted to open this up for discussion.  This can and should be iterated over.  There is a lot of formatting of information in SLIC calls that can be done.

**Example error** (notice the automatic and human readable stacktrace, filename and line number, so fancy):

```
[ERROR (/usr/WS2/username_0/serac/repo/src/drivers/serac.cpp:130)]

Can not open mesh file: fake
** StackTrace of 4 frames **
Frame 1: bin/serac() [0x95bf93]
Frame 2: bin/serac() [0x40bfd7]
Frame 3: __libc_start_main
Frame 4: bin/serac() [0x40b5a4]
=====
```

**Example info message:**

```
[INFO]: Opening mesh file: fake
```

If you run with more than one rank, a limited amount of ranks will show up at the beginning of the line like this:

```
[0,1,2][INFO]: Opening mesh file: fake
```
Add basic logging functionality
issue
created
joshessman-llnl
username_1
Attempting to reopen, renaming of `master` branch to `main` triggered automatic closure of PR.
comment
created
white238
username_0
I noticed this might be confusing what is the actual warning message:

```
[WARNING (/usr/WS2/username_0/serac/repo/src/solvers/nonlinear_solid_solver.cpp:175)]
Attempting to use BoomerAMG with nodal ordering.
step 1, t = 0.25
Newton iteration  0 : ||r|| = 0.000125
Newton iteration  1 : ||r|| = 0.0453958, ||r||/||r_0|| = 363.166
Newton iteration  2 : ||r|| = 0.000147888, ||r||/||r_0|| = 1.18311
Newton iteration  3 : ||r|| = 2.50446e-08, ||r||/||r_0|| = 0.000200356
```

Thoughts on how to clarify that "Attempting ... ordering" is the warning? [ENDWARNING]? extra newline?
comment
created
jamiebramwell
username_2
I think an extra newline would be sufficient.
comment
created
jamiebramwell
username_2
LGTM
comment
created
white238
username_0
LGTM
comment
created
white238
username_0
LGTM
comment
created
white238
username_0
As a first cut of the SLIC logging functionality this is good to go.  @samuelpmishLLNL or @username_1 can one or both of you review this and voice your opinion?
comment
created
joshessman-llnl
username_1
LGTM
comment