Custom Query (122 matches)
Results (106 - 108 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#57 | fixed | UO and PPM/PP logging not on same level in report | MichaelHalloran | michelpons |
Description |
The attached log has been obtained while enabling simultaneously logging on a UO PMC and on a PPM PMC. The PPM and the PP appears to be logged at the same level in the log through the Viewer while the UO operation calls are below the level of the PP. Normally the UO and the PP should be on the same level at least for the first calls. |
|||
#81 | fixed | UniSim Design crashes at reload with AixCAPE UO logged | michaelhalloran | michelpons |
Description |
I have set up a case that involves the Shortcut Distillation UO from AixCAPE e.V. in UniSim Design. I have saved the case. When I reload it, while the Shortcut Distillation UO is logged with COLTT, Unisim Design crashes. It does not happen when the Shorcut Distillation UO is not logged. |
|||
#46 | fixed | Unsufficient message content | michaelhalloran | michelpons |
Description |
I am using the GLCC UO in PRO/II 8.3 Patch 1. It relates to a case raised with SimSci-Esscor Support. I have a scenario that calls fro dropping the GLCC UO on the PRO/II flowsheet, to connect inlet and outlet ports, to edit the UO in order to choose the location for its output file, then to calculate the process model made of this UO. Examining the log made with COLTT, I see that get_Values calls on the integer parameters of the UO are at first looking good. Then, after the Edit call, the get_Values calls for integer parameters return a message \"An Invalid Argument\". What is not clear is who is sending this message and then what it means exactly. The only argument of such a call is the returned value. There is no error raised and no means for the call to pass a message. So my educated guess is that COLTT is posting the message but on what grounds. Plus, if it is indeed COLTT which is posting the message, it should be made obvious. Here, as it is posted, one may think that get_Value returns this message. Would it be possible to get more info on what is going on? |