"Solution Exception: Invalid result folder" on AnnualDaylight

[chris]

I just wanted to say that, even though all of these issues here give the same error message, in all likelihood, they are each different from one another. The error message being reported is just the generic failure message for a luigi recipe that didn’t finish successfully. If you want to find the real error, you need to set report_out_ to True on the Run Settings and then you’ll have to wade through the luigi logs that get output from the component report.

To put forward a guess as to why some of these cases are failing, it sounds like some cases just have incorrectly formatted radiance parameters. In other cases like Kit’s, it sounds a little like the installed version of the core libraries might not match the version of components. After using the “LB Sync Grasshopper File” on Kit’s file, I don’t have any issues getting results.

[MaxMarschall]

Hi @chris , I tried the “LB Sync Grasshopper File” method but it didn’t work for me.

unnamed.gh (42.5 KB)

I’m having trouble understanding the Luigi log report, but the summary does appear to indicate that the error is coming from writing the directory?
luigi.txt (16.3 KB)

Here is the directory

[chris]

Thanks for uploading the file, @MaxMarschall . It’s very clear what your error is now. Here’s the problem:

You plugged a whole model into an input that is only supposed to take Rooms. I probably should have had the component throw an error for this case. In any event, it all runs fine when you use the component as it was intended:

I will add the capability in now for the _rooms input to take a Model but, for future reference, if an input description doesn’t say that you can input a model, then you’re not supposed to input a Model.

[MaxMarschall]

Thanks @chris! And thanks for adding that feature

[chris]

I added the ability to take a Model as input for the component:

fix(basic): Add support for generating grids from Model rooms

And you’ll see that the component input description has changed to say that a Model is acceptable. So that’s the type of input description that you’ll see for a case where both Rooms or a Model are acceptable.

[MaxMarschall]

WOW…that’s quite an impressive responsive time, thanks!

[SWalters]

I’m experiencing the same top level error ; although the logs reveal another symptom/cause?
PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: ‘C:\Users\swalt\AppData\Local\Temp\tmpn4k3pyhr’

Runtime error (ValueErrorException): Invalid result folder: C:\Users\swalt\simulation\DaylightTest\annual_daylight\metrics/da

[Romain]

Hi all,
Just solved the problem for my case → be careful to not give an absolute folder path to the “folder” input of the HB Recipe Settings (just as in the honeybee legacy), but simply a folder name (without space or slash), which will be saved in the same folder than the grasshopper file.

[blmasand]

Thanks @chris - I had a similar issue - appreciate your solution on this.

[JG]

I get the same error when using the annual daylight sample file. I specificaly get it only when I use BSDF modifier to define the glass. This error happens only with the Annual daylight component. The direct sun hours component appeared to work, but no matter what xml file I used it gave the same results.

[chris]

BSDF modifiers were not supported in the LBT 1.2 stable release but they are currently available in the development version of the plugin (which you can get using the “LB Versioner” component) and they will be available in the soon-to-come LBT 1.3 release.

[JG]

Thank you Chris. Apologies for my late response. I upgraded to LBT 1.2. However the BSDF modifier still creates issues with the Annual Daylight component and the Point View analysis. All the components are up to date.

With Point view analysis, no images were created for luminance.
With the annual daylight component, this is the error I get when I use a BSDF modifier.
"1. Solution exception:The recipe failed to run with the following summary:

Scheduled 435 tasks of which:

• 147 ran successfully:
  • 1 CreateDirectSky(…)
  • 1 CreateOctree(…)
  • 1 CreateOctreeWithSuns(…)
  • 1 CreateRadFolder(…)
  • 1 CreateSkyDome(…)
    …
• 274 failed:
  • 137 DirectSkyLoop(…)
  • 137 TotalSkyLoop(…)
• 14 were left pending, among these:
  • 4 were missing external dependencies:
    • 1 AnnualDaylightRaytracing(…)
    • 1 AnnualDaylightRaytracingLoop(…)
    • 1 DirectSky(…)
    • 1 TotalSky(…)
  • 6 had missing dependencies:
    • 1 CalculateAnnualMetrics(…)
    • 1 LetAnnualDaylightFly(…)
    • 1 MergeRawResults(…)
    • 1 OutputMatrixMath(…)
    • 1 _AnnualDaylightRayTracing_5cabed59Orchestrator(…)
      …
  • 4 was not granted run permission by the scheduler:
    • 1 AnnualDaylightRaytracing(…)
    • 1 AnnualDaylightRaytracingLoop(…)
    • 1 DirectSky(…)
    • 1 TotalSky(…)
      This progress looks because there were failed tasks
      Use the report_out attribute of recipe settings to see a full report."

21-0820 cleaned up.gh (129.9 KB)Doubleclearwithwhitefrit_50.xml (136.4 KB)

[chris]

@JG ,

Glad to see that you are using a newer development version of the plugin. I cannot run your file as you didn’t internalize any of the geometry but I just ran a test and I can see that the BSDF capability of the recipes has been broken in the latest development version of the plugin. I’m working towards a fix now. In the meantime, you can use the “LB Versioner” to go back to version 1.2.76 of the plugin and the BSDF modifiers will work for that version.

[chris]

@JG ,

So I just merged a fix that should ensure BSDF modifiers work for all of the latest recipes except point-in-time-view. We’re working on this last case but your original error with the annual-daylight recipe has been addressed.

[chris]

The point-in-time-view recipe has now also been fixed. So this bug is no more!

[JG]

This is great, thank you Chris!

[mica.micillo]

Hi all,

Thanks for this useful post.
I am having the same issue but I can’t find out why. The strange thing is that it was working fine with no errors and suddenly this started happening.
This is the message I get from the report:

Can someone please help? Much appreciated!

[chris]

You should upgrade to LBT 1.3. You’ll see in the Release Notes that we have much better reporting for when the simulation fails like this. You’ll get a report like what @JG posted. There’s also a high chance that your issue was already solved thanks to bug fixes in the LBT 1.3 release.

[rastermadre]

Unfortunately just installed 1.3 and got a similar error while running one of the sample files (comfort_mapping.gh)

      {0;0}

0. Runtime error (PythonException): The recipe failed to run with the following summary:

Scheduled 27 tasks of which:

• 16 ran successfully:
  • 2 CopyGridInfo(…)
  • 1 CopySunUpHours(…)
  • 1 CreateModelOccSchedules(…)
  • 1 CreateOctree(…)
  • 1 CreateOctreeWithSuns(…)
    …
• 3 failed:
  • 1 CreateDirectSky(…)
  • 1 CreateTotalSky(…)
  • 1 RunEnergySimulation(…)
• 8 were left pending, among these:
  • 1 were missing external dependencies:
    • 1 RunIrradianceSimulation(…)
  • 6 had failed dependencies:
    • 1 AnnualIrradianceRaytracing(…)
    • 1 ComputeTcp(…)
    • 1 LetPmvComfortMapFly(…)
    • 1 RunComfortMap(…)
    • 1 _AnnualIrradianceEntryPoint_6d4da049Orchestrator(…)
      …
  • 4 had missing dependencies:
    • 1 ComputeTcp(…)
    • 1 LetPmvComfortMapFly(…)
    • 1 RunComfortMap(…)
    • 1 _Main_6d4da049Orchestrator(…)
  • 1 was not granted run permission by the scheduler:
    • 1 RunIrradianceSimulation(…)

This progress looks because there were failed tasks

Use the report_out attribute of recipe settings to see a full report.

Traceback:
line 171, in script

[mica.micillo]

@JG

BSDF modifier

Hi Chris,
Thanks so much for the fast reply!! I will try upgrading.
Can I just ask, if a simulation was set up with say version 1.2, and the components are then updated to a later version, should the simulation be run again? Could there be inconsistencies between previous results (from when the script was working) and new results because of the upgrade?
Thank you!