Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 122)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#15 fixed Return message from CheckEquilibriumSpec Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

De: Michel Pons [technologyofficer@…] Envoyé: Friday, May 08, 2009 10:43 AM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: COLTT 09-008 CheckEquilibriumSpec

Pièces jointes: hysys_050809_103340.log

Ahsan,

I transferred the modified COLoggersST.dll file to the VM hosting the 09-008 case and I reran it with logging enabled on the Thrm11PP.

I get now the attached log file but Aspen Hysys is still crashing.

For sure the log now shows:

PropertyPackage <Anonymous> : Call to CheckEquilibriumSpec

CheckEquilibriumSpec takes input arguments:

Specification1 Specification2 Solution Type

Property temperature pressure Unspecified Basis (null) (null) Phase Overall Overall CompoundId (null) (null)

MaterialObject <Anonymous> : Call to GetPresentPhases

Instead of:

PropertyPackage <Anonymous> : Call to CheckEquilibriumSpec

CheckEquilibriumSpec takes input arguments:

Specification1 Specification2 Solution Type

MaterialObject <Anonymous> : Call to GetPresentPhases

But for the return call, there is still:

CheckEquilibriumSpec returns:

Specification1 Specification2 Solution Type isSupported

PropertyPackage <Anonymous> : Return from CheckEquilibriumSpec - No Error

Aren’t the specifications and solution type meant to be rewritten in the log file at exit of CheckEquilibriumSpec? At least it was done so in COLTT v1.07:

CheckEquilibriumSpec returns: Specification1 Specification2 Solution Type isSupported

Property pressure enthalpy Unspecified True Basis (null) (null) Phase Overall Overall CompoundId (null) (null)

PropertyPackage <Thrm11PPack> : Return from CheckEquilibriumSpec - No Error

So if something has been resolved at calling time of CheckEquilibriumSpec, I think there is still an issue at exit.

Best regards

Michel ========================================================== De: Michel Pons [technologyofficer@…] Envoyé: Thursday, May 07, 2009 6:48 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: RE: PCNow Session

Ahsan,

OK for a session tomorrow morning, May 8.

I have a virtual machine set up for COLTT issue 09-006 with VS2008 Express edition installed as well as TOTAL HDPEReactor and Aspen Plus 7.1. However I don’t know where to get the proper version of the 1.08.02 COLTT source code. Could you send me a link from which I could download the source code before the session takes place?

I have also virtual machines for issues 09-008 and 09-009.

Best regards

Michel =========================================================== De: Ahsan Akhtar [ahsan.akhtar@…] Envoyé: Thursday, May 07, 2009 10:59 AM À: 'Michel Pons' Objet: PCNow Session

Michel,

Is it possible for you to have a session tomorrow morning at 8.00 am Paris time?

I want to debug and fix the issue 09-006. I will need TOTAL HDPEReactor and Aspen Plus v7.1 components installed on the machine. I will also need VS2008 and COLTT source code on that machine.

I will also run 09-008 and 09-009 issues to check if these are fixed.

Best Regards

Ahsan ===================================================== De: Michel Pons [technologyofficer@…] Envoyé: Tuesday, April 21, 2009 12:10 PM À: 'Ahsan Akhtar' Cc: 'michaeljhalloran@…' Objet: ThrmPP11 in Aspen Hysys

Pièces jointes: hysys_042109_113225v1.07.log; hysys_042109_113929v10802.log

Ahsan,

While checking an issue with Aspen Hysys, I ran with COLTT v1.07 and COLTT v1.08.02 the following scenario and I got two different behaviours.

The scenario is quite simple. Open up Aspen Hysys v7.1, go for a new case. Then Add a FluidPkg. Choose COMThermo, then CAPE-OPEN 1.1 for vapor, CAPE-OPEN 1.1 for liquid. Select the Thrm11PP as Property package. Accept the selection. Then proceed with the Extended Property Package setup process.

Then leaves the part about choosing a Fluid Package. Aspen Hysys will scream because of some missing property for an hypothetical compound and will refuse to let you go to the Simulation Environment. That’s fine. You can exit from Aspen Hysys at that point.

Well you can with COLTT v1.07 enabled on the Property Package. The behaviour observed with COLTT v1.07 enabled is not different than without COLTT enabled. The situation is completely different with COLTT 1.08.02. Aspen Hysys crashes after the selection of the Property Package.

While with COLTT 1.07, the first CheckEquilibriumSpec call is logged as:

PropertyPackage <Thrm11PPack> : Call to CheckEquilibriumSpec

CheckEquilibriumSpec takes input arguments:

Specification1 Specification2 Solution Type

Property temperature pressure Unspecified Basis (null) (null) Phase Overall Overall CompoundId (null) (null)

The same in COLTT v1.08.02 displays:

PropertyPackage <Anonymous> : Call to CheckEquilibriumSpec

CheckEquilibriumSpec takes input arguments:

Specification1 Specification2 Solution Type

So the specifications do not appear. The two log files are attached. This is making use of version ThermoPack11-1_02 of the Thermo Pack. Don’t think it matters.

I intend to log that as issue 09-008 if you have no earlier reference of such an issue.

Best regards

Michel

#17 fixed 09-011 GLCC UO in Aspen Hysys 7.1 Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

De: Michel Pons [technologyofficer@…] Envoyé: Sunday, April 26, 2009 10:26 PM À: 'Michael Halloran' Cc: 'Ahsan Akhtar' Objet: RE: GLCC UO In Aspen Hysys v7.1

Pièces jointes: COLTT09_011_Screenshots.doc

Michael,

Please find attached a Word file with screenshots obtained with the scenario of COLTT issue 09-011. I ignore the assertion failed error and then Aspen Hysys crashes.

Best regards

Michel ======================================================= De: Michael Halloran [michaeljhalloran@…] Envoyé: Saturday, April 25, 2009 11:35 PM À: Michel Pons Cc: Ahsan Akhtar Objet: Re: GLCC UO In Aspen Hysys v7.1 Michael,

Can you add information about the assertion? When you get an assertion do you try to ignore it and continue the run?

I don't understand the logs here. The 1.07 log should show the calls to get_ComponentName in the same places as the 1.08 log. The 1.07 logger is logging them and they must have been called or the name shown in the log wouldn't have changed to Check for the 1st parameter. So that looks like a 1.07 problem to me; the 1.08 log is what I would expect.

Regards Michael ========================================================== De: Michel Pons [technologyofficer@…] Envoyé: Thursday, April 23, 2009 10:15 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: GLCC UO In Aspen Hysys v7.1

Pièces jointes: hysys_042309_215826v107.log; hysys_042309_215412v1082.log

Ahsan,

I have ran a combination involving a CAPE-OPEN UO using Thermo 1.0 and Aspen Hysys v7.1. The UO comes from TOTAL and has been made with the Visual Basic Wizard.

The scenario starts from an Unconnected case file that displays three streams, one to be used as inlet and two as outlets to the UO. I use “Add Operation” then Extensions the CAPE-OPEN 1.0 and select GLCC UO. Then I accept this choice. Things are differing from then on with/wothout COLTT and between COLTT versions.

Without COLTT enabled on the GLCC UO, I get message boxes from Aspen Hysys of the type “Error in ExposeCOParstoHysys(13)”. This has been documented to Aspentech Support and is in the process of being solved. Several of these message boxes have to be Okeyed before arriving at the point where connections between ports and material streams can be made. I stop the scenario here.

With COLTT v1.07 enabled on the GLCC UO, I get first the same error message as above and then I have a message box repeated quite a number of times “ActiveXtender Error setting cell color (SetFontCellColor).

With COLTT v1.08.02 (after changing the COLoggersST.dll file) I get, after accepting the UO, a debug assertion failed message and then Aspen Hysys crashes.

I have joined to this message the two log files obtained. I am surprised that the two logs do not show exactly the same sequence.

COLTT v1.07

Parameter Collection <Unnamed> : Call to Item requesting Item 1 Parameter Collection Item returns : 0x569a84 Parameter Collection <Unnamed> : Return from Item - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56e97c

Parameter <Check> : Return from get_Specification - No Error

COLTT v1.08.02 ParameterCollection <Anonymous> : Call to Item requesting Item 1 ParameterCollection Item returns : 0x5698ec ParameterCollection <Anonymous> : Return from Item - No Error Parameter <Anonymous> : Call to ICapeIdentification.get_ComponentName Parameter <Anonymous> : Return from ICapeIdentification.get_ComponentName - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56ccfc

Parameter <Check> : Return from get_Specification - No Error

I have logged this issue as 09-011 in the meantime.

Best regards

Michel

#18 fixed 09-013 COULIS in PROII Michael Halloran michelpons

Reported by michelpons, 13 years ago.

Description

De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, June 24, 2009 9:25 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: COLTT Issue 09-013 COULIS in PROII

Pièces jointes: Mylog240609.olg; proii_062409_211137_10802.log

Hi,

I have tried the following scenario : in PRO/II 8.3 I am creating a new case by inserting a CAPE-OPEN UO in the flowsheet (no thermodynamic model defined yet). PRO/II opens up a message box that lets one choose which CAPE-OPEN UO to select. I select COULIS from AmsterCHEM. With COLTT 1.08.02 enabled on COULIS, I get an immediate crash leading to the attached log file. With COLTT 1.07 I get also a crash but without any log file appearing in the destination folder.

Without COLTT enabled on COULIS, I am able to select which UO to log in COULIS, here GLCC. The attached olg file coming from COULIS shows that.

This issue has been numbered 09-013. let me know if you need me to install Visual Studio 2008 in the corresponding VM.

Best regards

Michel

1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.