[Bldg-sim] Tall Bldg Pressurization & Stack Effect

[Chris Yates]

As I understand it Comis is credited in the e+ documentation and portions
of it appear to be used but the airflow network is largely a new model.
I have heard that some trnsys users use comis still.
Chris
On 2 May 2012 21:26, "Pallavi Mantha" <pmantha at swinter.com> wrote:

> I don’t think CONTAM is currently related to any energy program.****
>
> ** **
>
> *Pallavi Mantha, LEED AP BD+C
> *Building Systems Analyst*
> *212.564.5800 x144 (direct)*
> *212.741.8673 (fax)
> pmantha at swinter.com* *
>
> ** **
>
> ** **
>
> *From:* Varkie C Thomas [mailto:thomasv at iit.edu]
> *Sent:* Wednesday, May 02, 2012 3:01 PM
> *To:* bldg-sim at lists.onebuilding.org
> *Subject:* [Bldg-sim] Tall Bldg Pressurization & Stack Effect****
>
> ** **
>
> Is COMIS still active?  How is it used within EnergyPlus? Can it be used
> to evaluate building pressurization and stack effect infiltration in
> multiuse (retail, office, hotel with fixed windows and apts at the top with
> operable windows) tall and super-tall bldgs (ex. 160 storey Burj Khalifa
> and proposed Jeddah Kingdom Tower)?  Can ESPr and IESVE be used to
>  evaluate bldg pressurization and stack effect infiltration in super-tall
> bldgs?  Is CONTAM linked with an energy program?
>
>
> ****
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> _______________________________________________
> Bldg-sim mailing list
> http://lists.onebuilding.org/listinfo.cgi/bldg-sim-onebuilding.org
> To unsubscribe from this mailing list send  a blank message to
> BLDG-SIM-UNSUBSCRIBE at ONEBUILDING.ORG
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/bldg-sim-onebuilding.org/attachments/20120502/c95314a5/attachment-0002.htm>