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
When experimenting with NodeFileCompose on ocean model data, it seems that snap_lon and snap_lat are not registered correctly. This might have to do with some oddities of the ocean grid (in the x direction, longitude ranges from -200 to 160 instead of more conventional values; in the y direction, the grid is equatorially refined so is non-uniform). But the snapshots themselves and the composite look reasonable/tracked in the right position. Are there ways to register snap_lon and snap_lat from the track file instead of the data file, perhaps as one way to circumvent this issue? Thanks for any suggestions!
The text was updated successfully, but these errors were encountered:
When experimenting with NodeFileCompose on ocean model data, it seems that snap_lon and snap_lat are not registered correctly. This might have to do with some oddities of the ocean grid (in the x direction, longitude ranges from -200 to 160 instead of more conventional values; in the y direction, the grid is equatorially refined so is non-uniform). But the snapshots themselves and the composite look reasonable/tracked in the right position. Are there ways to register snap_lon and snap_lat from the track file instead of the data file, perhaps as one way to circumvent this issue? Thanks for any suggestions!
The text was updated successfully, but these errors were encountered: