You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #118 I imposed a rather lazy fix for our incorrect calculation of dvds in spherical coordinates which meant that we now do an on the fly calculation of dvds in spherical coordinates only.
Ideally, we want to do an interpolation on v_grad here, which is stored at each cell vertex. This should be improved by figuring out out how the velocity gradient tensor ought to be rotated in order to give the right answer for spherical coordinates.
The mystery here is why changing the angle along which the grid is defined doesn't change the angle at which the answer is correct.
The text was updated successfully, but these errors were encountered:
I'm closing this. Ideally we should figure it out, but it's not really a good use of time. The spherical model works with the on the fly methody, and it will never be a production model anyway.
I'm closing this. Ideally we should figure it out, but it's not really a good use of time. The spherical model works with the on the fly methody, and it will never be a production model anyway.
—
Reply to this email directly or view it on GitHubhttps://github.com/agnwinds/python/issues/126#issuecomment-70686762.
In #118 I imposed a rather lazy fix for our incorrect calculation of dvds in spherical coordinates which meant that we now do an on the fly calculation of dvds in spherical coordinates only.
Ideally, we want to do an interpolation on v_grad here, which is stored at each cell vertex. This should be improved by figuring out out how the velocity gradient tensor ought to be rotated in order to give the right answer for spherical coordinates.
The mystery here is why changing the angle along which the grid is defined doesn't change the angle at which the answer is correct.
The text was updated successfully, but these errors were encountered: