-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solar vector discrepancy #177
Comments
@ParametricMonkey , |
@chriswmackey |
I can't say that I know anything about the Revit sun position algorithm. Maybe it's worth a post to one of the Autodesk forums? |
I think our approach should be to ensure ladybug calculation matches NREL's output. @ParametricMonkey, back to Revit why don't you just Revit generated vectors as input for your study? |
I can verify with some recent tests that I did that the ladybug Sunpath is perfectly in line with the NOAA solar calculator when you ensure that the years are matching. It looks like Revit is still off from the NOAA calculator by a hundredth of a degree so I don't know if it's still going to give you visible shadows but it might be worth re-testing this after we merge in this PR: |
Further to this issue and the forum post, there appears to be a discrepancy between how Ladybug, Revit and NOAA calculate sun vectors.
In Revit you cannot specify a location by defining lat/long - you need to drag and drop a pin. So I am using the existing location in Revit to create a Ladybug location rather than trying to match an epw file.
Then I create views from the sun and enable the sun settings. As you can see, the altitude and azimuth of the sun vector is different.
I appreciate that this might be a rounding error, but it is enough to ‘see’ shadows when creating views from the sun.
Can this be fixed or are we dealing with rounding issues?
Attached files are Revit 2019 and Dynamo 2.0.3 with the latest Ladybug version (0.2.1?)
Ladybug issue.zip
The text was updated successfully, but these errors were encountered: