Aggregate Exception

Getting this Error whenever I try to run the OSM or IDF in HB:

Runtime error (AggregateException): One or more errors occurred.

Traceback:
line 174, in run_function_in_parallel, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\ladybug_rhino\grasshopper.py”
line 134, in script

The parallelization is preventing you from seeing the real error, which probably has to do with something un-simulate-able in your OSM or IDF. Try changing the _cpu_count_ to 1 and just plugging in one IDF or OSM. Then, the component should turn red with the real error and print out the full error report from EnergyPlus.

This is what I got:

Runtime error (TypeErrorException): expected string, got NoneType

Traceback:
line 37, in isfile, “C:\Program Files\Rhino 6\Plug-ins\IronPython\Lib\genericpath.py”
line 393, in prepare_idf_for_simulation, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 699, in _run_idf_windows, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 451, in run_idf, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 99, in run_osm_and_report_errors, “”
line 172, in run_function_in_parallel, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\ladybug_rhino\grasshopper.py”
line 134, in script

It looks like you’ve somehow got a null input for your IDF file. I can’t tell exactly what line the error is happening on since your aren’t using the latest version. Can you update and try again?

Thanks for your help Chris. I updated to the latest which necessitated updating my OpenStudio to 3.3.0. On a side note, my Ironbug components did not load correctly after the update, although that may be a @MingboPeng question.

The error now reads:

Runtime error (TypeErrorException): expected string, got NoneType

Traceback:
line 37, in isfile, “C:\Program Files\Rhino 6\Plug-ins\IronPython\Lib\genericpath.py”
line 404, in prepare_idf_for_simulation, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 710, in _run_idf_windows, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 462, in run_idf, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\honeybee_energy\run.py”
line 99, in run_osm_and_report_errors, “”
line 173, in run_function_in_parallel, “C:\Users\useg03905\ladybug_tools\python\Lib\site-packages\ladybug_rhino\grasshopper.py”
line 134, in script

Ah, I see what happened. For some reason, your OSM file is not valid and it cannot be successfully opened with the OpenStudio CLI. I’ll try to implement better error reporting for this but I imagine this is not an OSM that you can open or simulate in the OpenStudio Application. If you try opening your OSM in the OpenStudio App, it might tell you the “real” error of what is wrong with your OSM.

I also just improved the error reporting of those components in the latest development version of the plugin:

So this could also help you identify the real issue with your OSM.

The plot thickens… there is no OSM file that gets created, which way may be why its invalid. Not sure why, this is a single zone model used to test the script. and the IDF gets output.

image

Hi, I encountered the same error when attempting to run multiple simulations concurrently by modifying the CPU count via the HB Run IDF component:
Runtime error (AggregateException): One or more errors occurred.
Traceback:
line 202, in run_function_in_parallel, "C:\Program Files\ladybug_tools\python\Lib\site-packages\ladybug_rhino\grasshopper.py"
line 133, in script

I checked the eplusout.err files in the simulation folders, and all simulations show successful completion:
EnergyPlus Completed Successfully -- 13 Warning; 0 Severe Errors; Elapsed Time=00hr 00min 21.40sec.
However, the HB Run IDF component still displays a red error state.

When I set _cpu_count_ to 1, the component turns gray (no error).
I’d like to know if there’s a way to resolve this issue. Thank you very much!

Hi @zly ,

Your error seems different and seems to be the same thing that @AbrahamYezioro experienced here:

I still have not been able to recreate it on my machine so I don’t know what causes it. But let’s continue the conversation over there instead of on this old thread.

@zly if you decide to post in the link @chris mentioned, do you mind to check your runs with a USA EPW file?
Thanks,
-A.