Solution exception:index out of range: 0

Replies to This Discussion

Permalink Reply by Abraham Yezioro on April 10, 2016 at 11:27pm

You forgot to internalise the geometry.

-A.

Permalink Reply by Mia Sheperd on April 10, 2016 at 11:43pm

This might be a dumb question... but how would I go about doing that?

Permalink Reply by Abraham Yezioro on April 10, 2016 at 11:48pm

At the same place where you add the geometry to the component there is an item "internalise".

-A.

Permalink Reply by Tim on April 11, 2016 at 11:00pm

Abraham said it right, I'd just add an image (just in case))):

Permalink Reply by Mia Sheperd on April 12, 2016 at 11:31am

Thank you this was very helpful!!!

Permalink Reply by Ben Street on February 16, 2017 at 4:38pm

Did you ever work out how to solve this problem??

Permalink Reply by Julia T on February 17, 2017 at 2:20am

Hi Ben,

When I had this problem it usually was because I had a problem in the context. The component was looking ok, but then some surfaces or meshes were giving problems. Try to unplug it and see if the error remain.

Nevertheless, without seeing your file it is quite difficult to know which may be your problem

Permalink Reply by Ben Street on February 17, 2017 at 12:14pm

Hi Julia,

Thanks so much for the quick reply, not entirely sure what you mean by unplugging the surfaqce and seeing if the error remains, here's my file & thanks in advance for any help you can offer.

(you might have to relink the 'annual_analysis_files' output from the runDaylightAnalysis componant to the _illFilesAddress input of the readAnnualResults I componant, as I have linked mine directly with a panel and copy pasted path due to another error earlier on)

Permalink Reply by Ben Street on February 17, 2017 at 2:13pm

File:

Attachments:

• Daylight Optimized lightwells_Error.gh, 558 KB