Annual daylight simulation extra data error

Hi,
I am running a very simple annual daylight simulation, however when i try to read the hourly results i get this error:

  1. Solution exception:Extra data: line 1 column 95659 - line 4 column 1 (char 95658 - 95832)

Does anybody know what is the reason for this error? How can i fix it?
Extra data Error.gh (220.9 KB)

Thanks,
Julio

Hi @mikkel,
I am sorry to disturb you with this. Maybe you know what could be the origin of this error? i tried to uninstall ladybug tools and install it again, but nothing changes, same error pops up. I tried in other computers with the same file and works perfect but not in mine.
Thanks

Could it be a version error? I see some components being 1.8.0 and some 1.8.1

Which version did you install? Did you run LB Versioner and update the components on the canvas if needed (use LB Sync Grasshopper File)?

I installed the pollination single click installer some time ago. It was LBT 1.8 version. I tried with other computers and the script runs perfect.

I try also running LB Versioner but a different error pops up. Now no component works. :man_facepalming:


I have updated Ladybug with the grasshopper installer to the newer version. The same problem ocurs. All components work but the annual results to data.


Furthermore, if i open the results folder with another computer it open the results without any issue. So the problem is clearly localized in the annual results to data component, everything else is working just fine (simulation results).
For other annual metrics such as irrandiance it works fine, it only happens with the daylight annual analysis results.

Any idea what could be provoking this error? how can i fix it?

Thanks

Hi @Julioamodia89,

Can you zip the results folder, and upload and share it somewhere?

Can you connect a panel to the report output so I can see the full error message? I want to know exactly which line it fails at.

FYI, the latest version of that component in the developer version (LB Versioner update) is 1.9.2, but updating the component will probably not fix your issue.

Hi @mikkel,
See attached results folder. This was read fine in other computers.
results.zip (38.6 KB)
The error:

  1. Solution exception:Extra data: line 1 column 90316 - line 4 column 1 (char 90315 - 90489)
    The report:
    Runtime error (ValueErrorException): Extra data: line 1 column 90316 - line 4 column 1 (char 90315 - 90489)

Traceback:
line 367, in decode, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\decoder.py”
line 339, in loads, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json_init_.py”
line 202, in script

Thanks

It also works fine for me. There is nothing wrong with the results folder. I am not sure what the issue is yet, but I can see that it fails when trying to read the results as data collections.

I have made a small change to the component that will write the data collections to a JSON file. Can you try to run it and share the output file? If the component still fails please check if it created datacollections.json in your results folder and share the JSON file.

annual_data_output_file.gh (9.4 KB)

Surprisingly that component works.
See datacollections.json file:
datacollections.json (88.2 KB)

Thank you. It seems that on your machine something else is also written to the standard output when the CLI command runs in the component.

Can you please try again with the attached component. This will write a .txt file of the standard output. This time the component will probably fail but it should still write datacollections.txt in your results folder – please share this file.

annual_data_output_file_txt.gh (8.4 KB)

Hi Mikkel,
It did report an error. This is the .txt file
datacollections.zip (25.7 KB)

FYI, @Julioamodia89 .

@mikkel alerted me to this issue and I think I know what is going on. Your “different error” above gave me the idea of the likely culprit.

I think you probably have a user standards library with some unconventional modifiers in it. Because of this, these modifiers get loaded up into honeybee-radiance upon initialization of anything honeybee-related. And that causes a warning about high specularity to be printed, which then interferes with grabbing the useful information from that the “HB Annual Results to Data” component wants.

So I think your unique user standards library is probably the reason why no one else on the forum has reported this issue yet and why you only have the issue on one of your machines. That said, I have come to see it is generally bad practice on our part to just print warnings in our core libraries without giving a clear way to silence them. So I removed the one that affected you here (along with a few others):

The change is now available via the LB Versioner component.

Let us know if you update and test the changes.

Thank you for reporting the issue, @Julioamodia89 , and thanks, @mikkel, for providing what we needed to figure out the issue. This is definitely one of those bugs that needed the expertise of the whole room of people to identify and fix.

2 Likes

Great, thanks for your help guys! I hope more people can benefit from this update.
I have indeed many custom rad modifiers files in the standard folder, so that is probably the source of the problem as you mentioned.

1 Like