Quick question while sitting in an airport transit lounge: my classes start Monday next week and I have asked whether we could update to v1.9
Tech has asked, due to issues previously, what version of Ironbug is installed as this may wreck compatibility.
I recall @Nicholaskerr had issues earlier this year with finding the right Open Studio App version with which to edit IronBug output in order to visualise and thus ross check the HVAC systems he was working on.
@MingboPeng - any recommendations?
Hello @MichaelDonn
The IronBug version forthe new release of Pollination ``1.65.2’’ is IronBug 1.19.2
The updates for the IronBug do not follow the same speed. If there is an update for the IronBug in this link you can download and update it using the installer; it will update only IronBug components.
(I can see that the HVAC visualization component specifically designed by the IronBug team is not included in the new version (1.19.2))
I moved this to a new discussion with a clear title so that people can find it.
The compatibility matrix is always a good reference for this type of thing:
And thanks for binging this up since I forgot to add a row for version 1.9 (I just added it).
But you can see that LBT 1.9 works with OpenStudio SDK 3.9, which works with OpenStudio Application 1.9.
Thanks for this @behnammmohseni .
We look forward to that visualiser.
The technician’s concern was that remote deployment of Ironbug when we added it for one course in one classroom (for grad students) had been a pain to get right. If he was deploying a new version of LBT (with Ironbug) install selected between Friday per my request and Monday start time of our new trimester he did not want to screw up the Masters students’ ironbug.
I was in transit Europe to New Zealand so was reaching out.
We are reassured.
In terms of your statement about running the installer to update ironbug, good to know. However, i have a problem in terms of consistency of versions if you mean the Ironbug installer. Remote deployment of that was somewhat problematic for the tech team as i recall. Also i worry about consistency of versions.
If you sre talking about the pollination installer, i have a bigger concern. We use LBT via packaged scripts, for classes of >300 first year, >200 second year and ask ~50 third year students to build their own analyses in a combination of personal and school computers consistency of versions is critical. For example, i have found tiny little differences (1.8.36 to 1.8.76 for example) can cause some bits of scripts not to work. As a workaround in the past for those students who leave things 'til the last moment, i have crested a tjny version converter gh script to downgrade to a version compatible across the school. A colleague has built his own scripts that install everything consistently on both Apple and Windows environments and does not tell students about the LBT official installers!
Essentially, I’d be wary in a multi class environment just to run the pollination script to update Ironbug as i’d have to ask all 500 some people to also update their laptops just so we could use Ironbug at a senior level.
Thanks for your information @MichaelDonn
I faced that mismatch below:
The challenge is that IB is developed with a different style compared with LB/HB. A component like IB Versioner, similar to LB Versioner, is not developed to cover this challenge.
However, in general, HB/LB/IB being installed with the One Click Pollination file are completely synced and working. As a suggestion for your class, you could inform and set up your students to install the latest available version of Pollination. Then, for teaching them using previous simulation files, they need to run one component: LB Sync Grasshopper File.
This component updates all the components from the old simulation file to the version of installed Pollination on the machine (except those for IronBug).
For the IB components, as long as there is no red color, they function properly; however, it is recommended to manually replace them with newer versions.
@MingboPeng I guess some similar components of LB Sync Grasshopper File and LB Versioner for Ironbug tools need to be developed, something like:
IB Sync Grasshopper File and LB Versioner.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
@MichaelDonn there is also another component: LB Versioner
With this component, if the version_ is blank, this component updates all the LB/HB, except Ironbug, in the simulation file to the latest released version. By joining a description describing the desired version for the component, you can downgrade to the version that you are interested in having.
Just to give a little more insight into how Ironbug scripts are meant to be updated, once you replace your old Ironbug .gha file with a new one, your Ironbug scripts are automatically updated the next time that you open them in Grasshopper.
Granted, it is possible that you might need to replace the ObjParams component in some of your scripts if OpenStudio SDK had major changes to an object that you are using in Ironbug. But, for most Ironbug scripts that are not using bleeding-edge HVAC components, just opening them in Grasshopper after you have updated your Ironbug is all that is needed.
