pycnal_toolbox remapping_bound bug #13
Description
The Bering example is supposed to show how to remap from ROMS to ROMS when the grids are aligned. This is from Ken Coyle who was trying it out:
could not get the make_weight_files.py program to accept irange and jrange values so I just ran it for the whole grid. Apparently, it does not appear to recognize those arguments. It seems to make the remap_weights_NEP5_to_CGOA...nc files OK without the ranges.
However, I did run into an issue when running the remapping_bound program. I was using the argument rotate_uv = False and ran into a problem because the if the rotate_uv is false, the code skips the part where dst_u and dst_v are defined (lines 423-423, 434-435, 443-444, 449-450) because they are in the if loop (if rotate_uv is True:, lines 239-457). There is no "else" option to define dst_v and dst_u when rotate_uv is False. Therefore, when it tries to define dst_ubar and dst_vbar, it returns and error message because it cannot get the dimensions for the arrays (lines 485-486):
dst_ubar = np.zeros((dst_u.shape[1], dst_u.shape[2]))
dst_vbar = np.zeros((dst_v.shape[1], dst_v.shape[2]))
So I have to either set rotate_uv = True, or come up with an alternative method to compute dst_u and dst_v. Do you have a suggestion? Should the u and v values be rotated when using the NEP5 average files to compute the boundaries for the CGOA grid?
I told him to rotate for now...