Replies: 3 comments 1 reply
-
I already asked myself the same question. |
Beta Was this translation helpful? Give feedback.
-
If there are no special requirements for the logging, Also, I have to admit, that I have no personal experience with JUL. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your feedbacks. We agree that this is more of a development aid than a production aid. To me the questions are: |
Beta Was this translation helpful? Give feedback.
-
I wonder if it wouldn't be a good idea to use a log system, like SLF4J. To date, choco has a dummy log system, which allows you to display certain information about the model or the resolution (I think it's the latter that's used).
Mainly, they are defined in
IOutputFactory.java
.At the moment, it's pretty easy to display in the console (via
System.out
) the characteristics of the model, the resolution statistics, the decisions made, the solutions found and the failures encountered...However, it might be useful to plot more information, such as that relating to modelling or resolution configuration.
For instance, it's not always easy to know if a constraint has not been posted...
The difficulty is determining what should appear in the logs, what should appear in the console (by default), what can be activated/deactivated, etc.
But first of all, does such a need exist, or is what is there enough?
Beta Was this translation helpful? Give feedback.
All reactions