Is there a way to run multiple versions of OpenStudio without having to re-scan for EnergyPlus?

asked 2014-09-17 10:35:30 -0500

updated 2014-09-18 08:12:14 -0500

I'm running two OSMs, the baseline is in version 1.2 and the proposed is in version 1.4 and every time I switch from one to the other I have to re-scan for tools to connect OpenStudio with EnergyPlus. I've tried deleting the unused version of EP from the Tools to allow the other version of OS access to it, but the connection is still being removed. I realize updating the 1.2 OSM to 1.4 would be an easy fix, but that's a separate issue. Thanks in advance...

edit retag flag offensive close merge delete

add a comment

answered 2014-09-18 11:56:16 -0500

macumber

11908 ●22 ●21 http://automaticmagic.com/

Hi Matt, unfortunately this is a bug in OpenStudio and there currently is no good work around. I've added some detail to the bug report and bumped up the priority.

https://github.com/NREL/OpenStudio/is...

Hope that helps, Dan

edit flag offensive delete link

Comments

Dan, Thinking on this it would be incredibly great if there were a way to have an OpenStudio install be portable with all the config files housed in the install directory structure. I've seen a number of large packages do this (the largest of which is probably winpython). Has there been any thought to this? I'm sure its low on the priority list if it has, but it would still be nice to know it is being considered.

Ralph Muehleisen ( 2014-10-20 13:25:17 -0500 )edit

Thanks @Ralph Muehleisen, this is a pretty straightforward bug, just hasn't raised priority enough to get to it. We were under the impression that most users only go forwards in version and don't spend a lot of time switching between versions, maybe that is incorrect?

https://github.com/NREL/OpenStudio/is...

macumber ( 2014-10-20 21:04:31 -0500 )edit

@macumber, thanks for responding.

I am thinking of a production workflow where you do design work for a particular building, it would be great to be able to take the entire OpenStudio system + models and archive them. That way, if you have to revisit, you just extract the archive and run OpenStudio again. This lets you keep a working system intact in the archive but update the OpenStudio for new projects. Similarly, I could do the same for individual projects/papers/reports.

Ralph

Ralph Muehleisen ( 2014-10-20 22:51:18 -0500 )edit

@Ralph Muehleisen yeah I understand that use case. Currently we are storing these paths in the registry, we could store them in some sort of text file in the user's directory, or in your case allow the user to import them from some other file location. All of this would just take time and effort, in the end it just saves you a little bit of time to not have to run scan for tools so I'm not sure it's worth it. However, anyone who feels this is important should vote the question up, that should show that it deserves a better answer!

macumber ( 2014-10-20 23:24:33 -0500 )edit

add a comment