Reported by michelpons, 14 years ago.

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

Reported by michelpons, 14 years ago.

De: Michael Halloran [michaeljhalloran@…] Envoyé: Monday, August 17, 2009 11:03 PM À: technologyofficer@… Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics Michel,

Since the logs are so similar I think the debug messages are harmless. I agree they shouldn't be there but I think they are a consequence of you running a debug build. I think the first step is to re-run the test with a release build of 1.08.2 (or .3?) and to compare with 1.07 again.

Regards Michael ==================================================== De: technologyofficer@… Envoyé: Wednesday, August 12, 2009 7:46 AM À: Michael Halloran Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics

Michael,

I have not made any calculations in both examples. I just selected the Property Package and stopped there. Things may be fine with calculations afterwards but my point is that debug assertion failed messages should not pop up. By clicking on Ignore at each debug assertion failed message I am moving on. There is no such message with COLTT 1.07 enabled on COMThermo Thermo System.

Best regards

Michel =================================================== De: Ahsan Akhtar [ahsan.akhtar@…] Envoyé: Wednesday, August 12, 2009 6:17 AM À: 'Michael Halloran'; 'Michel Pons' Cc: malcolm.woodman@… Objet: RE: COLTT 09-016 COMThermo in Simulis Thermodynamics

Michael,

Yes, you are right, it is a debug build.

Best Regards

Ahsan ==================================================== De: Michael Halloran [michaeljhalloran@…] Envoyé: Wednesday, August 12, 2009 12:01 AM À: Michel Pons Cc: Ahsan Akhtar; malcolm.woodman@… Objet: Re: COLTT 09-016 COMThermo in Simulis Thermodynamics Michel,

The two logs look very similar, so it seems that the calculations proceed in both examples. Is that correct? Are you continuing through the debug messages?

Ahsan, do you know whether 1.08.2 is a debug build or a release build? Presumably 1.07 is a release build?

Regards Michael ================================================== De: Michel Pons [technologyofficer@…] Envoyé: Tuesday, August 11, 2009 11:32 AM À: 'Ahsan Akhtar'; 'Michael Halloran' Cc: 'malcolm.woodman@…' Objet: COLTT 09-016 COMThermo in Simulis Thermodynamics

Pièces jointes: excel_081109_105634_v107.log; excel_081109_110300_v1082.log; Screencopy110809.doc

Hi,

I get « Debug Assertion Failed » messages while making the selection of a COMThermo PP in Simulis Thermodynamics. This occurs with COLTT 1.08.02 while it does not occur with COLTT v1.07. You will find attached a Word document made of screen copies of the scenario performed as well as the log files obtained both with 1.07 and 1.08.02.

I have given number 09-016 to this issue.

Best regards

Michel

Reported by michelpons, 14 years ago.

De: Michel PONS via YouSendIt [delivery@…] Envoyé: Wednesday, August 26, 2009 10:48 AM À: technologyofficer@… Objet: File Sent: COLTT09-017.zip

youSENDit File Sent Thank you for trusting YouSendIt to send your important files. Want to send and track multiple files at once?

Upgrade Now

.......................................................................................................................................................................................................................

File sent: COLTT09-017.zip Recipients sent to: michaeljhalloran@… File will be stored for: 7 days

Link to file: ​http://download.yousendit.com/MnFqUWVsSWhsamV4dnc9PQ

YouSendIt Inc. | Terms of Service | Privacy Policy | DMCA Policy | Opt Out

1919 S. Bascom Avenue, 3rd Floor Campbell, CA 95008

============================================================== De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, August 26, 2009 10:43 AM À: 'Michael Halloran' Cc: 'malcolm.woodman@…' Objet: COLTT 09-017 Test3 in Aspen Plus v7.1.1

Michael,

You may want to log this issue through the bug tracking facility on SourceForge. I have not put yet SHMA in copy since I don’t know what is the on-going status with SHMA at this stage.

Within Aspen Plus 2006.5 I had logged an issue labeled 917841 that pertained to the fact that the flow property in Aspen Plus was not correctly implemented. This led to defect CQ00319371. I had documented this defect with a dedicated Fortran made UO that did not much except calling on this flow property to show it did not work properly.

This defect has been announced as resolved in Aspen Plus 7.1.

So I have reset the case in Aspen Plus 7.1 with Cumulative Patch 1. I will post you through yousendit the accompanying material meaning the installer for the UO, the bkp file used to start the case as well as the log files and the screenshots mentioned hereafter.

The scenario is rather simple. I start from an Aspen Plus file that presents two material streams (one for input, one for output). The inlet stream is fully configured. I select the Corentin_version3 UO (the CAPE-OPEN UO mentioned above) within the CAPE-OPEN library of UOs available and I drop it on the flowsheet. In Aspen Plus 2006.5 I was able to connect the streams and to launch calculation. In Aspen Plus 7.1.1 the UO looks dead meaning no ports available on the UO so I don’t get any further. I have relogged an issue with Aspentech Support on that one.

To try understanding the issue I first logged the scenario with COLTT 1.07 enabled on the UO. To my surprise, with COLTT enabled on the UO, the ports are appearing on the UO and the calculation is fine. I can even check that indeed the flow property is well returned by the MO. So I have an issue with COLTT: it changes the behaviour in between the PMC and the PME.

My next step has been to try COLTT 1.08.02 on this case. Here I have also a change a behaviour between the PMC and the PME since the ports are showing up and I may launch the calculation. However I have, within the Calculate method, a debug assertion failure message (see screenshots for that) that I chose to ignore and I have then Aspen Plus miserably crashing.

So there is also a different behaviour between 1.07 and 1.08.02. That does not help.

I have defined this as being issue COLTT 09-017 in order to track it on my side for the moment. There may be two issues there. One is making the ports appear and the second is the debug assertion failure in 1.08.02.

Best regards

Michel