Usefulness of COCO 3 Error Messages

[nrgeng]

COCO 3 message contains no useful debugging information

COCO 3 Error Message

Initial Guess Message (C3).jpg (228.12 KiB) Viewed 24781 times

COCO 2 message contains offending Stream name and Unit which is useful for debugging

COCO 2 Error Message

Initial Guess Message (C2).jpg (218.13 KiB) Viewed 24781 times

The COCO 3 message seems to be new as it provides less (no) useful debugging information. I assumed that successful code in COCO 2 would just be copied and inserted into COCO 3. Was COCO 3 a complete rewrite?

Could more useful information be added to all of the COCO 3 error messages as required to aid in debugging?

[jasper]

What COCO 2 lists is the units in the partition, and the cut streams in the partition. You can get these if you put the verbosity level to Debug, or Verbose. Nevertheless, I will add these to the message in the next update.

[jasper]

Please update from CUP, and you will find this information added in the message.

[jasper]

Note that more useful diagnostics information you will find the log is which unit failed, and why.

[nrgeng]

Problem: Difference Between Verbose and Debug Info Levels

Flowsheet Log and Unit Status Log Report show no differences between Verbose and Debug modes that I can see. What is the difference?

How to clear Unit Status Log Report? The report is very long so I cannot tell which part of the report is relevant to the latest solve attempt.

[jasper]

The debug log contains more information. Typically when things fail, such as perturbations that fail to give an answer.

The unit status log is cleared prior to each run and contains only information from the last run.

[nrgeng]

Problem: Difference Between Verbose and Debug Info Levels

While trying to understand and use the Debug Info Level, two files were created to save the Flowsheet Log and the Unit Status Log Report for analysis. A Verbose mode file and a Debug mode file are attached.

There is a difference in the Flowsheet Log between Verbose and Debug modes.

The Unit Status Log Report seems to be the same for either Verbose or Debug modes. Page 19 in both are similar in what is reported. Is that what was intended?

The solver seems to be repeating the same loop over and over again for 20 pages. If the solver encounters an error, why repeat the solve process?

In summary, the only debugging information is contained in the Flowsheet Log with nothing contained in the Unit Status Log Report. Is that correct?

Does some other location contain additional debugging information?

[jasper]

The solver seems to be repeating the same loop over and over again for 20 pages. If the solver encounters an error, why repeat the solve process?

The solver dos not get anywhere because there are units with errors:

Unit "COFE Flowsheet Unit Operation SUB": error: " must be part of a recycle

It does not even get to an initial guess. It is trying different initial guesses because a units fails. It cannot see that the unit fails because of another reason than a problem with the initial guess.

In summary, the only debugging information is contained in the Flowsheet Log with nothing contained in the Unit Status Log Report. Is that correct?

Yes. That is, the unit log for the flowsheet unit "COFE Flowsheet Unit Operation SUB" itself is a flowsheet log. You can also set that one to verbose.

Does some other location contain additional debugging information?

Yes - crash logs (if you have them) and a developer with symbol information and a debugger (i.e. myself). But I would need sufficient information to reproduce a problem.