[Solved]HB Direct sun hour component went red when timestep greater than 2 (bug, update to the latest version)

grasshopper honeybee
, ,
1

Here is the report and the file.

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

Scheduled 24 tasks of which:

  • 7 ran successfully:
    • 1 ConvertWeaToConstant(…)
    • 1 CopyGridInfo(…)
    • 1 CreateOctree(…)
    • 1 CreateRadFolder(…)
    • 1 GenerateSunpath(…)
      …
  • 1 failed:
    • 1 DirectIrradianceCalculation(…)
  • 16 were left pending, among these:
    • 4 were missing external dependencies:
      • 1 DirectSunHoursRaytracing(…)
      • 1 DirectSunHoursRaytracingLoop(…)
      • 1 DirectSunlight(…)
      • 1 DirectSunlightLoop(…)
    • 3 had failed dependencies:
      • 1 CalculateCumulativeHours(…)
      • 1 ConvertToSunHours(…)
      • 1 _DirectSunHoursCalculation_04f49a1bOrchestrator(…)
    • 5 had missing dependencies:
      • 1 LetDirectSunHoursFly(…)
      • 1 MergeCumulativeSunHours(…)
      • 1 MergeDirectSunHours(…)
      • 1 _DirectSunHoursEntryLoop_04f49a1bOrchestrator(…)
      • 1 _Main_04f49a1bOrchestrator(…)
    • 4 was not granted run permission by the scheduler:
      • 1 DirectSunHoursRaytracing(…)
      • 1 DirectSunHoursRaytracingLoop(…)
      • 1 DirectSunlight(…)
      • 1 DirectSunlightLoop(…)

This progress looks :frowning: because there were failed tasks

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

Traceback:
line 91, in script
problem.gh (39.6 KB)

2

everything went well after I turned off the timestep slide, but when the number was greater than 1 (2 or 3 ) the component went red…

3

I wanted to gather a line of probes on the surface of a building to save the calculation time in the direct sunhour test, so the grid looks like point line rather than grids

4

Hi @Zed ,

Thanks for reporting the issue. The issue appears to be linked to your use of the hoys_ input on the “Wea from EPW” component. The timestep works as intended if you apply the analysis_period after the simulation has completed like so:

image
image1533×783 138 KB

I’ll see if I can figure out what is going wrong with the hoys_ input when I get the chance.

1 Like
5

Digging into the issue further, the issue seems to be with timesteps that aren’t a factor of 2. Everything is fine when I use a timestep of 2, 4, or 8:

image
image1773×569 190 KB

I’ll see if I can get to the bottom of the weirdness but it seems related to Radiance not liking factors of anything other than 2.

6

Ah, nevermind. The bug was on the LBT end but it was just deep on the LBT end. I included a fix as part of this commit:

… and you should be able to get it on your end with the LB Versioner within an hour or so. With the fix, I confirmed that everything is working when the timesteps are a multiple of 3 now:

image
image1762×522 183 KB

Thanks for reporting the issue, @Zed !

1 Like
7

Thank you, Chris! Things work well now.