Daylight Factor error report (ver. LBT 1.2)

grasshopper honeybee
1

Dear Ladybuggers,

I try a Daylight Factor analysis with the new LBT 1.2 component, but I run into this error, which I cannot resolve:
Runtime error (DecoderFallbackException): Die Bytes [E4] im Index 0 können nicht von der angegebenen Codepage in Unicode übersetzt werden.

Traceback:
line 47, in py_encode_basestring_ascii, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 390, in _iterencode_dict, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 332, in _iterencode_list, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 408, in _iterencode_dict, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 408, in _iterencode_dict, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 408, in _iterencode_dict, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 434, in iterencode, “C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json\encoder.py”
line 189, in dump, "C:\Program Files\Rhino 7\Plug-ins\IronPython\Lib\json_init.py"
line 31, in model_to_json, “C:\Users\rvg\ladybug_tools\python\Lib\site-packages\pollination_handlers\inputs\model.py”
line 442, in handle_value, “C:\Users\rvg\ladybug_tools\python\Lib\site-packages\lbt_recipes\recipe.py”
line 76, in script
line 169, in write_inputs_json, “C:\Users\rvg\ladybug_tools\python\Lib\site-packages\lbt_recipes\recipe.py”
line 240, in run, “C:\Users\rvg\ladybug_tools\python\Lib\site-packages\lbt_recipes\recipe.py”

Hier the attached File with the internalised geometries
LBT_1.2-DF.gh (896.5 KB)

could someone explain to me where the mistake could be?

Thanks

2

From the error message, it’s probably a non-ascii character in one of your inputs. Is that the case here?

@chris and @MingboPeng, this is something that we probably want to support by default.

1 Like
4

Dear @mostapha
You’re right, the name of the material and from the HBface had an Ä.
By removing the “umlaut” it works

Very very thanks

5

Hi @LaFleur, thank you for letting us know. As I said I think we should handle such cases by default. Good to know that there is an easy workaround for now.

6

if it is of interest, the component HBFace that had linked the name containing a Non-ASCII letter, could not be updated by the GH Sync. Without the Non-ASCII letter, could be!!

Best regards