Simulation Control doesn't match beetwen IDF and input component

Dear Mustopha,

I have a problem with value of Simulation control in the IDF file that have been generated by Honeybee, It doesn’t match with my setting in the honeybee component,It should be true, false, false, false, true but in the IDF the value is yes,yes, yes, no, yes. Even when I put another configuration in the input component, the value in the IDF file is the same. Is the anything I could do to fix the situation?

Thank you…

Agus

Hi Agus, Thank you for reporting this. It was a bug and now is fixed. Use Honeybee_Honeybee JUN_20_2014 and you will get what you want.

-Mostapha

Hi Mustapha, Thank you for your update, It worked now…

another question, why is the default Outside boundary condition for floor is surface (not ground)? And when I run It, the surface become adiabatic because there isn’t any surface…

And I’m interested in the issue “Fix naming process both for zones and surface #76” to let user naming surfaces especially which have “Outdoor” as Outside boundary condition…

Best Regards,

Agus

Hi Agus,

I fixed both issues this morning - or I think that I did :wink: - Do you want to replace the components with the newest version and give it a try.

If it is possible please send your EnergyPlus related questions to github until we officially release them.

Thanks,

Mostapha

Hi Mostapha,

This my EP file that I want to accomplished with gh definition. The outside boundary condition and surface name still didn’t work yet, at least on my first try… ;)- I’m still learning to understand your Honeybee, and It’s so fun…

Thanks,

Agus

hipotetik21jun2014.gh (163 KB)
Hipotetik_IDEAL_LOAD.idf (157 KB)

Hi Mostapha,

after I update my file, the definition not work, one of the problem was because the bldgProgram component can’t access the sub program…so How Can I access this sub program with the new component?Thanks,

Agus

Hi Agus,

I’ merging both into 1 but I haven’t finished the implementation (https://github.com/mostaphaRoudsari/Honeybee/issues/80). For now you can just use the old component. Except for Mass2Zone it should work fine. I will check your files once I have this implemented.

Mostapha

Hi Mostapha,

OK, got that…

If it is possible, I think It would be better for user to get notification for component in their current GH definition which has change after they update honeybee or ladybug, like old watermark in basic GH component… :wink:

Thanks,

agus

This is a great idea. I don’t know how to do it right now but I will definitely think about it. Thanks.