LB_ENVI-Met

Hi all,

I'm glad to share some useful tools with those people who use ENVI-Met v.4.0 for their researches. (a software that is very slow but accurate enough, XD).
I have written two LB components which let you visualize and manipulate data that come from ENVI-Met simulations. These component are based on a research with ENVI-Met v.3.0 and Ladybug that I did in 2015:

https://www.researchgate.net/publication/281031049_Outdoor_Comfort_...

It is possible to combine LB_ENVI-Met Grid with other LB component, such as: Ladybug_Mesh Threshold Selector, Ladybug_Countour Mesh, Ladybug_Recolor Mesh, Ladybug_Outdoor Comfort Calculator, Ladybug_Thermal Comfort Indices.

- Antonello

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Devang Chauhan on February 5, 2017 at 3:15am

Excellent Antonello!

Would try these as soon as possible. Thanks a lot.

Permalink Reply by Abraham Yezioro on February 5, 2017 at 5:54am

Hi Antonello,

This is good news.

The Reader component is giving this error when you just insert it:

1. Solution exception:'unicodeescape' codec can't decode bytes in position 383: malformed \N character escape

Good job ... :-)

-A.

Permalink Reply by Antonello Di Nunzio on February 5, 2017 at 6:27am

Hi Abraham,

thanks for your check!
I can't replicate the error you posted, could you share one *.EDX, one *.EDT and *.INX? thanks!

- Antonello

Permalink Reply by Abraham Yezioro on February 5, 2017 at 6:33am

Hi Antonello,

This happens when i just insert the component. It is not related to any input file.

Testing the code i get:

Runtime error (SystemException): 'unicodeescape' codec can't decode bytes in position 383: malformed \N character escape
Traceback (most recent call last):
SystemError: 'unicodeescape' codec can't decode bytes in position 383: malformed \N character escape

See image both components, one connected and one not connected.

Thanks,

-A.

Permalink Reply by Abraham Yezioro on February 5, 2017 at 8:41am

One more thing:

If you use Biomet then you have another directory at the level of other output directories (i.e. atmosphere, radiation, etc). Inside it you'll find another set of directories (PMV, PET, UTCI) depending which comfort standard you asked for (could be all of them).

Hope it helps to get all results that were missing.

-A.

Permalink Reply by Antonello Di Nunzio on February 5, 2017 at 3:58pm

hi Abraham,

This looks similar to an issue of compatibility between python 2 and python 3.

Python 2.7.12
>>> print 'TEST\N\N'
TEST\N\N
>>>

Python 3.6.0
>>> print('TEST\N\N')
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 4-5: malformed \N character escape

>>> print(r'TEST\N\N')
TEST\N\N
>>>

I should find a solution. Please, if you have occasion, let me know if it gives the same issue also with other computers.

Thanks for the hint about Biomet folder, it should be a good opportunity to compare results comes from envimet and ladybug.

Antonello

Permalink Reply by Abraham Yezioro on February 5, 2017 at 11:32pm

Hi Antonello,

Sorry to say that i have the same problem on my other computer :-(

Uninstalled Python 3.5 and installed 2.7 but no change.

Thanks,

-A.

Permalink Reply by Giulio Piacentino on February 6, 2017 at 6:56am

Hi guys

Rhino does not use independent installations of IronPython, but they can conflict with the version loaded from Rhino's installation folder. As such, you should not install different IronPython versions to begin with. See more information.

If required, then rather install the exact version that you are using with Rhino, or disable the GAC option while installing.

Besides, \N is not a good character escape. It should be \n. \n is a new line escape. \N is undefined, even in Python 2.0, and as such, can create issues. I am not an expert regarding under which conditions an error will be raised for this problem, rather than being silently ignored.

Permalink Reply by Abraham Yezioro on February 6, 2017 at 8:04am

Hi Antonello and Giulio,

Following Giulio's recommendation i replaced all "\N" for "\n" and now it works!!

Looks great!!

I'll keep checking.

-A.

Permalink Reply by Antonello Di Nunzio on February 6, 2017 at 8:24am

Hi Giulio,

thank you for your precious contribute! Yes, I know that \N is not an escape character ;), but believe me I didn't know where it was hidden inside the code...

Hi Abraham,

thanks for your work! send a pull request and mainly, can you show me where these "\N" are in the code? XD

- Antonello

Permalink Reply by Abraham Yezioro on February 6, 2017 at 8:42am

Hi Antonello,

There are only 2 "\N" at lines 35 and 117. If you change them to "\n" or "\\N" then it works.

Waiting for the Biomet/UTCI, PMV, PET to be included in the studyFolder input :-)

Thanks,

-A.

Permalink Reply by djordje on February 5, 2017 at 9:41am

This looks fantastic Antonello !!

Thank you for developing it, and sharing the link to your publication!!!

Is is possible to attach some *.edx, .edt example files?