Revision history [back]

Can reproduce the crash with OpenStudioApplication v1.8.0 (App), when accessing the Geometry tab for instance.

However, one can set an EPW/DDY pair and attempt a launch with the App. The App doesn't crash - it (safely) hals its forward translation to EnergyPlus and reports the same OpenStudio CLI failure discussed here (missing thermal zone ports). The fix discussed in the link should work.

If you do succeed in fixing the OSM, you should consider filing an issue - the App shouldn't crash. This seems to be a recurring thing (see here and here).

Hope this helps.

Can reproduce the crash with OpenStudioApplication v1.8.0 (App), when accessing the Geometry tab for instance.

However, one can set an EPW/DDY pair and attempt a launch with the App. The App doesn't crash - it (safely) hals its halts forward translation to EnergyPlus and reports the same OpenStudio CLI failure discussed here (missing thermal zone ports). The fix discussed in the link should work.

If you do succeed in fixing the OSM, you should consider filing an issue - the App shouldn't crash. This seems to be a recurring thing (see here and here).

Hope this helps.

Can reproduce the crash with OpenStudioApplication v1.8.0 (App), when accessing the Geometry tab for instance.

However, one can set an EPW/DDY pair and attempt a launch with the App. The App doesn't crash - it (safely) halts forward translation to EnergyPlus and reports the same OpenStudio CLI failure discussed here (missing thermal zone ports). The fix discussed in the link should work.

If you do succeed in fixing fixing/running the OSM, you should consider filing an issue (possibly two):

• If you used a built-in OpenStudio Application Plugin tool or utility to generate (unfortunately incomplete) thermal zones, maybe file an issue for the Plugin. If you instead used the App's FloorspaceJS to generate thermal zones, consider filing an issue here. I can't see how/why any OS:ThermalZone object can/should be instantiated in an incomplete state.
• The App crash is separate, IMHO. Ideally, it shouldn't crash when encountering an incomplete OSM - the App shouldn't crash. it should simply halt its processes and inform the user (as described above). This seems to be a recurring thing (see since 2021 - see here (v3.2.0) and here and here).
  (v3.4.0).

Hope this helps.

Can reproduce the crash with OpenStudioApplication v1.8.0 (App), when accessing the Geometry tab for instance.

However, one can set an EPW/DDY pair and attempt a launch with the App. The App doesn't crash - it (safely) halts forward translation to EnergyPlus and reports the same OpenStudio CLI failure discussed here (missing thermal zone ports). The fix discussed in the link should work.

If you do succeed in fixing/running the OSM, you should consider filing an issue (possibly two):

• If you used a built-in OpenStudio Application Plugin tool or utility to generate (unfortunately incomplete) thermal zones, maybe file an issue for the Plugin. If you instead used the App's FloorspaceJS to generate thermal zones, consider filing an issue here. I can't see how/why any OS:ThermalZone object can/should be instantiated in an incomplete state.
• The App crash is separate, IMHO. Ideally, it shouldn't crash when encountering an incomplete OSM - it should simply halt its processes and inform the user (as described above). This seems to be a recurring thing since 2021 - see here (v3.2.0) (v1.2.0) and here (v3.4.0).(v1.4.0).

Hope this helps.