Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenStudio Inspector does not recognize Imported EnergyPlus Idf Constructions and Schedules #7

Open
eomere opened this issue Mar 4, 2020 · 3 comments
Labels
Triage Issue needs to be assessed and labeled, further information on reported might be needed

Comments

@eomere
Copy link

eomere commented Mar 4, 2020

There are 2 features involved here. To access them:

  • Extensions/OpenStudio/Import/Import EnergyPlus Idf Constructions
  • Extensions/OpenStudio/Import/Import EnergyPlus Idf Schedules

After importing Constructions and Schedules from EnergyPlus Idfs, the number of OS:DefaultConstructionSet and OS:DefaultScheduleSet within the OpenStudio Inspector does not increase.

This issue is present within the Mac and Windows versions of the Plugin.

@jmarrec
Copy link
Contributor

jmarrec commented Mar 24, 2020

This works as expected IMHO.

It creates OS:Construction and OS:Schedule:XXX objects.

These can then be used in dropdowns that accept them, for eg by creating an OS:ConstructionSet yourself:

image

And assigning that to a field that expects an OS:Construction such as the Interior Partition Construction Name:

image

The downside for Schedule objects is that most IDF files use Schedule:Compact, and that's translated back to an OS:Schedule:Compact, while the OS:DefaultScheduleSet is looking for OS:Schedule:Ruleset instead.

@jmarrec
Copy link
Contributor

jmarrec commented Mar 24, 2020

Based on the above, can we close @eomere ?

@jmarrec jmarrec added the Triage Issue needs to be assessed and labeled, further information on reported might be needed label Mar 24, 2020
@eomere
Copy link
Author

eomere commented Mar 24, 2020

This is very useful information. I wonder how it can be more explicitly conveyed to a User.

Please close if you feel that a User will understand how it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage Issue needs to be assessed and labeled, further information on reported might be needed
Projects
None yet
Development

No branches or pull requests

2 participants