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
logger.debug('No wind available to calculate Stokes drift')
checks the current set of variables for the presence of x_wind and if it isn't present, the log message is written. But, the first two times this code is called, the variables were:
variables
['land_binary_mask']
and then
variables
['sea_floor_depth_below_sea_level']
which caused the message to be written, but subsequently when the code was called that line wasn't written because x_wind was present in variables. Could the logic of that section be improved to know that while the wind isn't present in variables at the moment, it also shouldn't be? I am not sure what to suggest, not being very familiar with this section of code yet.
The text was updated successfully, but these errors were encountered:
Hi again. This is a small issue but I think I have investigated it multiple times unnecessarily so it would be nice to avoid in the future.
My understanding is that the code here:
opendrift/opendrift/models/basemodel/environment.py
Lines 859 to 860 in 6689864
checks the current set of variables for the presence of
x_wind
and if it isn't present, the log message is written. But, the first two times this code is called, the variables were:and then
which caused the message to be written, but subsequently when the code was called that line wasn't written because
x_wind
was present invariables
. Could the logic of that section be improved to know that while the wind isn't present invariables
at the moment, it also shouldn't be? I am not sure what to suggest, not being very familiar with this section of code yet.The text was updated successfully, but these errors were encountered: