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
I have a simple test case that starts at 19500 s, with boundary data saved starting at the same time. The format of the boundary data saved is native (as netcdf still seems to be really slow). I have added a few print statements right before the assert to try to debug it, and this is what I got:
--- DEBUG: m_in_times[0] is 19500
--- DEBUG: m_in_times.back is 19530.3
--- DEBUG: time is 19500
--- DEBUG: time-m_in_times[0] is -2.391971066e-08
Given the value of time-m_in_times[0], it seems like a tolerance issue and something like an eps is needed somewhere in that assert statement. The case runs fine if I manually add, say, 19499.7 to the boundary data.
One additional piece of information: The simulation that saved the boundary data was split into two parts, the first ending at 19500 and the second starting at the same time. Since m_in_times[0] seem to be slightly (tolerance) higher than 19500, that could be one of the causes of the problem.
The text was updated successfully, but these errors were encountered:
When running a case that takes boundary data as input, it fails on this assert:
amr-wind/amr-wind/wind_energy/ABLBoundaryPlane.cpp
Line 766 in add85b1
I have a simple test case that starts at 19500 s, with boundary data saved starting at the same time. The format of the boundary data saved is
native
(asnetcdf
still seems to be really slow). I have added a few print statements right before the assert to try to debug it, and this is what I got:Given the value of
time-m_in_times[0]
, it seems like a tolerance issue and something like aneps
is needed somewhere in that assert statement. The case runs fine if I manually add, say,19499.7
to the boundary data.One additional piece of information: The simulation that saved the boundary data was split into two parts, the first ending at
19500
and the second starting at the same time. Sincem_in_times[0]
seem to be slightly (tolerance) higher than19500
, that could be one of the causes of the problem.The text was updated successfully, but these errors were encountered: