Hi all, I am experiencing a bug after updating to the latest version of Ladybug -
We have a compute server set up through AWS where our scripts live.
I have a hop that has a RunIDF component. The SQL output of that component is connected to multiple CustomResult components where I then do some work to postprocess the data.
On the previous version (I believe 1.6.something) this was working fine, but after updating to 1.9.0, the RunIDF component doesn’t actually seem to block grasshopper execution anymore - it seems that it generates output for SQL, which is then connected to these CustomResults that try to read the database, winding up in a corruption.
I get a sqlite.err file out, with thousands of lines of:
SQLite3 message, sqlite3_step message: database disk image is malformed.
The eplusout.sql file itself is also about 4mb smaller than the one that I can generate manually. Even the eplusout.err file that is generated seems to be corrupted.
I have tried a workaround where I’ve split running the IDF and processing the SQL into different scripts so that I only run the SQL processor after EnergyPlus has completed, but to no luck.
Any advice would be greatly appreciated, thanks 