Originally reported by: Yung-Yu Chen (BitBucket: yungyuc, GitHub: yungyuc)
Currently solvcon.solver.MeshSolver.mesg() is the only and primitive message reporting facility available at the solver level. Also, there's no verbosity control.
The case-level message reporting (solvcon.case.MeshCase.out()) doesn't have verbosity control either. Verbosity control should be taken into consideration for both reporting levels.
The verbosity may use 5 or 7 levels. The lack of verbosity and the crippled solver-level reporting hinder code debugging a lot.
Originally reported by: Yung-Yu Chen (BitBucket: yungyuc, GitHub: yungyuc)
Currently solvcon.solver.MeshSolver.mesg() is the only and primitive message reporting facility available at the solver level. Also, there's no verbosity control.
The case-level message reporting (solvcon.case.MeshCase.out()) doesn't have verbosity control either. Verbosity control should be taken into consideration for both reporting levels.
The verbosity may use 5 or 7 levels. The lack of verbosity and the crippled solver-level reporting hinder code debugging a lot.