Conversation
Remove pre-release tag for 1.7.1
…ts for first measure are being computed (this can take a long time in failure case). Catch all std::exceptions instead of just RubyExceptions which prevents crash. Fixes #656
Don't use classic mode for measure manager Don't auto update openstudio_results from BCL
|
@jmarrec when updating a model with the old results measure, we probably need to swap the new one out, currently there is a crash due to this. The exception is caught in this branch now at least. However, there are going to be many measures that might need to be updated. So maybe it's best to not update the results measure, we can just show the errors and make users delete/replace measures themselves. This is going to be something we need to address in the release notes. |
…Mac with updated xcode
…s by version id and timestamp
# Conflicts: # ConanInstall.cmake # src/openstudio_lib/OSDocument.cpp
|
@jmarrec if you have a chance to review this that would be good, the PR is not too big if you ignore |
|
I'd probably have liked if the "Example > Shoebox Model" was isolated into its own PR. |
v1.7.2 patch to not automatically download results measure
Agreed, sorry I was in a rush, I can move it to a new PR if you'd like FYI, I did merge openstudiocoalition/openstudio-coalition-measures#3 and release https://github.com/openstudiocoalition/openstudio-coalition-measures/releases/tag/v1.8.0 to support this |
| QTranslator m_qtTranslator; | ||
| QTranslator m_qtBaseTranslator; | ||
| QString m_currLang; | ||
| bool m_useClassicCLI; |
There was a problem hiding this comment.
"Remove unused m_useClassicCLI, cannot use classic CLI for MeasureManager any more" (65af11b)
why?
There was a problem hiding this comment.
This issue prevents using the classic CLI for the measure manager now: NatLabRockies/OpenStudio#5212
I figure it's probably not really worth supporting using classic for the measure manager in the future either, what do you think? You can still use the classic option for the run though.
There was a problem hiding this comment.
I don't really like seeing these files here. Should we rely on the BCL to download these as needed?
There was a problem hiding this comment.
I wanted to make these measures/example models part of the installer, so it is just ready to go with no download needed. We could fetch the measures/example models from https://github.com/openstudiocoalition/openstudio-coalition-measures at build time and keep them in the build directory rather than checking them in to this repo. They'd still be duplicates in the installer. Does that sound better?
There was a problem hiding this comment.
I removed these measures from this repo, they are now pulled from https://github.com/openstudiocoalition/openstudio-coalition-measures at configure time
There was a problem hiding this comment.
Now we have two copies of the openstudio_results measure in source: in the Resources/ and Resources/ShoeboxExample/measures folders
There was a problem hiding this comment.
I guess we could add the report measure to the ShoeboxExample model at run time. I had wanted to keep the model exactly the same as in https://github.com/openstudiocoalition/openstudio-coalition-measures/tree/main/models/ShoeboxExample, that way it would be simple to extend to other example models in the future.
There was a problem hiding this comment.
I removed these measures from this repo, they are now pulled from https://github.com/openstudiocoalition/openstudio-coalition-measures at configure time
…dio-coalition-measures
…to measures_dir. Use both for now in case that changes.
# Conflicts: # translations/OpenStudioApp_ar.ts # translations/OpenStudioApp_ca.ts # translations/OpenStudioApp_de.ts # translations/OpenStudioApp_el.ts # translations/OpenStudioApp_es.ts # translations/OpenStudioApp_fa.ts # translations/OpenStudioApp_fr.ts # translations/OpenStudioApp_he.ts # translations/OpenStudioApp_hi.ts # translations/OpenStudioApp_it.ts # translations/OpenStudioApp_ja.ts # translations/OpenStudioApp_pl.ts # translations/OpenStudioApp_vi.ts # translations/OpenStudioApp_zh_CN.ts
# Conflicts: # src/openstudio_lib/OSDocument.cpp
|
Ping @jmarrec, do you want to give this a review? If not, I think we could merge and push out an RC1. What do you think? |
An RC1 for 1.8.0? I'd like to see if we can get an updated CLI with NatLabRockies/OpenStudio#5230 fixed first |
|
I don't think we need an updated 1.8.0 package. After I tested, the main issue was with the OpenStudio Results measure which gets downloaded and added to each model by default at startup. I fixed that in the 1.7.2 release. The other BCL menus have some filtering built into them, I think I have handled all the needed cases in this PR such that we don't have to have an update to OS SDK. |
sync project measures with librarydoes not work as before #620