[lpapamanolis]

• Removed scattered print statements and replaced them with print_state() functions
• Implemented box-drawing printing for structured output

Closes #16.

[ktbolt]

@lpapamanolis Very good replacing the print statements with a logger !

I didn't see it but are there various levels of detail for the logging ? I think that most times users will not want to see very much logging information.

[lpapamanolis]

@ktbolt I am planning to have 4 levels of detail: silent (no logging), warning (warnings only), info (default), debug (additional details for debugging). These are all already implemented in the CustomLogging class.

A lot of the scattered prints have already been replaced by the custom logger. Still some remain to be addressed in future issues.

Agreed that logging should be minimal. My plan for the info (default) logging level:

1. Print initialized state at the start of the simulation (what this issue is about). This will give users an opportunity to doublecheck their input parameter file and provides a reference in the terminal about the simulation currently running.
2. For each timestep, print single line with relevant columns (similar to svMultiphysics).