Ladybug energy analysis error - calccoordinatetransformation: invalid dot product

Grasshopper
,
1
  1. The simulation has not run correctly because of this severe error:
    ** Severe ** CalcCoordinateTransformation: Invalid dot product, surface=“Mir-SHDSURFACE_0_1”:
    error
    error1365×732 266 KB
2

I have used the default hydra script for Full Building energy analysis…

Here is the detail of the OS component
{0;0;0}
0. Current document units is in Meters

  1. Conversion to Meters will be applied = 1.000
  2. Current working directory is set to: c:\ladybug\NahantModel\OpenStudio
  3. Model saved to: c:\ladybug\NahantModel\OpenStudio\NahantModel.osm
  4. OSM > IDF: c:/ladybug/NahantModel/OpenStudio/NahantModel/ModelToIdf/in.idf
  5. Program Version,EnergyPlus, Version 8.9.0-eba93e8e1b, YMD=2021.03.21 16:24,
  7. ** Warning ** ProcessScheduleInput: Schedule:Constant=“ALWAYS OFF DISCRETE”, Blank Schedule Type Limits Name input – will not be validated.
  9. ** Warning ** ProcessScheduleInput: Schedule:Constant=“ALWAYS ON CONTINUOUS”, Blank Schedule Type Limits Name input – will not be validated.
  11. ************* Beginning Zone Sizing Calculations
  13. ** Warning ** GetSurfaceData: InterZone Surface Areas do not match as expected and might not satisfy conservation of energy:
  15. ** ~~~ ** …use Output:Diagnostics,DisplayExtraWarnings; to show more details on individual mismatches.
  17. ** Warning ** CalcSurfaceCentroid: 1746 Surfaces have the Z coordinate < 0.
  19. ** ~~~ ** …in any calculations, Wind Speed will be 0.0 for these surfaces.
  21. ** ~~~ ** …in any calculations, Outside temperatures will be the outside temperature + 9.750E-003 for these surfaces.
  23. ** ~~~ ** …that is, these surfaces will have conditions as though at ground level.
  25. ** Warning ** GetSurfaceData: There are 99528 coincident/collinear vertices; These have been deleted unless the deletion would bring the number of surface sides < 3.
  27. ** ~~~ ** For explicit details on each problem surface, use Output:Diagnostics,DisplayExtraWarnings;
  29. ** Warning ** ProcessSurfaceVertices: Possible non-planar surface:“SHDSURFACE_0_1”, Max “out of line”=1.16972E-003 at Vertex # 2
  31. ** Severe ** CalcCoordinateTransformation: Invalid dot product, surface=“Mir-SHDSURFACE_0_1”:
  33. ** ~~~ ** (-385.413,-264.264, 2.075)
  35. ** ~~~ ** (-378.035,-264.264, 1.950)
  37. ** ~~~ ** (-378.035,-264.264, 1.950)
  39. ** ~~~ ** (-378.035,-271.641, 1.952)
  41. ** ~~~ ** (-385.413,-271.641, 2.081)
  43. ** Fatal ** CalcCoordinateTransformation: Program terminates due to preceding condition.
  45. …Summary of Errors that led to program termination:
  47. … Reference severe error count=1
  49. … Last severe error=CalcCoordinateTransformation: Invalid dot product, surface=“Mir-SHDSURFACE_0_1”:
  51. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
  53. ************* Fatal error – final processing. Program exited before simulations began. See previous error messages.
  57. ************* ===== Final Error Summary =====
  59. ************* The following error categories occurred. Consider correcting or noting.
  61. ************* InterZone Surface Areas – mismatch
  63. ************* …Area mismatch errors happen when the interzone surface in zone A is
  65. ************* …not the same size as it’s companion in zone B.
  69. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
  71. ************* EnergyPlus Sizing Error Summary. During Sizing: 5 Warning; 1 Severe Errors.
  73. ************* EnergyPlus Terminated–Fatal Error Detected. 99533 Warning; 1 Severe Errors; Elapsed Time=00hr 06min 5.09sec
3

Hi - please visit https://discourse.ladybug.tools/ for questions related to the Ladybug Tools.
-wim

4

Hi, I got the same error with you, how did you solve this error?

5

Hi Shijie,
I dont remember exactly how I solved it since it was 1 year ago. Maybe I dint define the zones correctly, that’s why that error occurred. Please let me know if it gets fixed with defining zones or else I can try to troubleshoot it over zoom.
Best Regards,
Porus