09-017 Test3UO in Aspen Plus 7.1.1

[michelpons]

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

[michelpons]

Log file obtained with COLTT 1.07

[michelpons]

Log file obtained with COLTT 1.08.02

[michelpons]

Word document with screen copies of scenario

[michelpons]

I have rerun this combination with COLTT 1.08.03 (Build Oct 19, 2009) enabled on the Test3 UO. The behaviour observed is now the same as with COLTT 1.07: the simulation runs fine while the connection of streams to ports can't take place when COLTT is not enabled on the UO. The attached log file apmain_102309_171628_v10803.log shows what kind of log is obtained.

Consequently the issue about a difference of behaviour with COLTT 1.07 of more recent versions of COLTT is resolved. Remains the issue that COLTT modifies the interaction between PME and PMC in that case. Should that be left in this ticket or a new one created?

[michelpons]

Log file obtained with COLTT 1.08.03

[michelpons]

I have retested the case with COLTT 1.08.3 Build Oct 27, 2009. It shows the samz behavior as with COLTT 1.07. See attached the log obtained (apmain_110409_112202.log). So I am closing the ticket which was related to the difference of behaviour between version 1.07 and 1.08. I am creating a new one about the misbehaviour provided by COLTT.

[michelpons]

Log file obtained with COLTT 1.08.3 Build Oct 27, 2009