Add separate logging of global homotopy solver

[Francesco Casella]

When dealing with initialization of models, getting some feedback on the homotopy process (when it starts, the step it takes, if it succeeds) is crucial. Currently, you can only get it by turning on LOG_INIT, which however produces a lot of other information, which prevents us to get some information on the success of homotopy on the Jenkins test rus.

Can we introduce a LOG_GLOBAL_HOMOTOPY flag that only turns on the homotopy process information?

[Andreas Heuermann]

That's a good idea. I'd like to go a step further and introduce a LOG_INIT_V flag and rename your flag LOG_GLOBAL_HOMOTOPY to LOG_INIT_HOMOTOPY. So LOG_INIT tells the user what is happening and LOG_INIT_V will print the actual values of e.g. primary start-values. And everything regarding homotopy on initialization will be moved to LOG_INIT_HOMOTOPY.

So LOG_INIT and LOG_SOTI are subsets of LOG_INIT_V.
LOG_INIT_HOMOTOPY is a subset of LOG_INIT.

So when using only LOG_INIT_HOMOTOPY you get only the initialization infos for homotpy solvers.

[Andreas Heuermann]

See ​PR #654.

[Francesco Casella]

Sounds good. I'll try this ASAP on the next nightly build.

[Andreas Heuermann]

@casella Is this solution good or do you need more loging informations?

[Francesco Casella]

Just fine, thanks!