johank

I'm having the same issue in v6.52. I'm simulating SAT with backtracking and ran a few comparisons, attached. Setting azimuth in the 3D Shading Scene alone appears to only affect IAM loss, leading to a small reduction in GlobEff. It does not appear to affect incident (POA) irradiance, GlobInc. This was unexpected. Changing GlobInc required this: - define 3d scene, use "position in scene" (ctrl+b) to set azimuth - compute shading factors table - set azimuth under "Orientation" (it says it's w.r.t. to 3d shadings but I suspect that's not the case) This prints the correct azimuth angle in the report. However, the value under "Orientation" resets to 0 after the simulation. The change in GlobInc starts to be fairly significant for larger azimuths. Please advise. The forum does not allow adding xlsx, happy to send via email if it would be helpful. Thank you!

Hello, Is it possible to vary the monthly soiling values when using batch mode, or to add this functionality if it does not yet exist? Thank you very much!

Hello, We use parameter matrices to guide our initial design. To generate the underlying data, it would be very useful to have the batch mode generate multiple sets of "8760" data (i.e. for every hour of the year) rather than just summary annual values. For instance, each column in the output .csv file could be the 8760 data for a particular configuration. Thanks! Johan