I've used Flarenet (Aspen Flare System Analyzer) off and on for many years, starting with v7.3. I'm now using v9.0. With each new release I find maddening bugs and quirks with this program. The pattern I've seen is that they fix some bugs and problems, and create new ones at the same rate. I'm starting to wonder whether anyone at Aspen actually runs the software after their programmers say it's done!
One problem I've seen for many years, and many versions, is the problem with specifying the different mass flow rates (scenario specific required flowrates) for operating scenarios and fire scenarios. I recall, from years ago, finding that my specified values would sometimes mysteriously change. I'm now running a file (v9.0) and my latest frustration is that the Relief Valve Editor window doesn't show the different flowrates that I entered for the fire and operating scenario. Clicking back and forth shows the same #%&@*&$ value. It just displays the last value entered, regardless of whether that was for fire or an operating scenario. Fortunately, when I ran the file and switched from fire to operating scenarios, I found that the program did actually store the different values that I'd entered - it just won't show them correctly on the input window. *&#$ !!
I could go on.....
Just venting!! .......... OK, I'm feeling better now. Thanks.
One problem I've seen for many years, and many versions, is the problem with specifying the different mass flow rates (scenario specific required flowrates) for operating scenarios and fire scenarios. I recall, from years ago, finding that my specified values would sometimes mysteriously change. I'm now running a file (v9.0) and my latest frustration is that the Relief Valve Editor window doesn't show the different flowrates that I entered for the fire and operating scenario. Clicking back and forth shows the same #%&@*&$ value. It just displays the last value entered, regardless of whether that was for fire or an operating scenario. Fortunately, when I ran the file and switched from fire to operating scenarios, I found that the program did actually store the different values that I'd entered - it just won't show them correctly on the input window. *&#$ !!
I could go on.....
Just venting!! .......... OK, I'm feeling better now. Thanks.
