akyle

I have not gotten a chance to test your theory on multithreading, but wanted to go ahead and provide an example project for you. I've exported a project with 2 variants in the project folder: VC0 was created first and has the bug in it; I then created a copy of the variant, and did what I described above and the near shading loss/electrical shading loss increased by a combined 0.55%, as shown in VC1. It's not letting me upload a zip folder on this thread though, is there another way I can send it to you? Also, I thought it was worth noting that my suspicion is that it may have something to do with the .csv ground data in the shade scene because I was not able to recreate the bug without adding the surface in.

I've started to notice a consistent discrepancy in my shade loss values (both near shading and electrical shading losses) after going back into the shade scene and re-running the table. This has happened for both tracker and fixed tilt systems where I create the shade scene, run the simulation, go back into the shade scene and move 1 table off to the side and right back to its initial position, and then re-run table/simulation and the losses are different by about 0.2-0.4% cumulatively. I'm not sure why there is a discrepancy here because I am not changing anything about the shade scene, essentially just rerunning the same exact layout. I've also noticed that the discrepancy will only happen once. If I do the same process 2/3/4 more times, it gives the same result as the first re-run. It seems there is just a bug in the initial simulation and after that the results are solid. I've tested this on version 7.2.12 and 7.2.14 and the same bug seems to be present. Does anyone have a theory or explanation for this?