Custom Query (122 matches)
Results (118 - 120 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#127 | fixed | Warning message - compIds argument is empty | Michael Halloran | michelpons |
Description |
Using COLTT 2.1 Build June 5, 2012 I noticed in the attached log that many warning messages are written to the log file, within SetProp and GetProp method calls: Warning - compIds argument is empty I wonder if this is relevant since the compIds argument may be UNDEFINED. Does it mean that the way UNDEFINED is set is wrong wrt the argument type? Is this warning significant with respect to the PMC or is it related to COLTT? |
|||
#78 | fixed | When UO logged no connection on ports | michaelhalloran | michelpons |
Description |
The PME used is Aspen Plus 7.2. The PMC used is a UO in .NET made by DTU/CERE. The scenario is to start from a Aspen Plus case where two streams are defined, one to serve as input, the other as output. Without COLTT enabled on the UO, it is possible to connect the defined stream to the UO inlet and to connect the other stream to the outlet port. The UO is then considered as valid and calculation may be launched. Calculation ends up with an error: the material flow in the outlet stream is way too large compared to the material flow in the inlet stream. That calls for a look with COLTT. When COLTT is enabled on the UO, it is impossible to connect streams to ports, so it is impossible to reach the point where the calculation is made. |
|||
#156 | fixed | Worflow of new Controller version | Michael Halloran | michelpons |
Description |
Build 263 is used: when opening up Controller and selecting a given component, the \"Enable Logging\" box is appearing as non-ticked. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out. Then I tick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box remain ticked and are now ungreyed. Next I untick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box have then greyed out and unticked. I close the COLTT controller and then enters it again. When going to the same component as before, the \"Enable Logging\" box is unticked while The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out. I would think that ticking or unticking the \"Enable Logging\" box should not alter the two other boxes. Since by default these two boxes are ticked but greyed out, it means that they are partially independent from the \"Enable Logging\" box. Anyway they will be \"active\" only when a component is logged. Now I wonder if really the selection for these boxes is per component or rather is it for the entire set of components to be logged. I don't exactly how the implementation is done. If reference counting and error interface calls are not component dependent, the corresponding boxes should appear elsewhere than within a component detail. |