-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FVCOM unstructured reader - variables not longer in default output #1385
Comments
Ok. I am not using FVCOM files myself, and do not have much insight into the unstructured reader. Is there any other information available in this file that can serve the same purpose? Or are these variables stored somewhere else, so that this file is not self-contained? |
Looking at the reader code, it seems that https://opendrift.github.io/_modules/opendrift/readers/reader_netCDF_CF_unstructured.html#Reader.__nearest_node_sigma__ However the This might perhaps sound a little unlogical? The challenge with the unstructured format is that output from different models have historically been quite different. Thus there are presently several unstructured readers (ideally one would have just the generic one), but also the generic unstructured reader might be adapted to much to some specific model/version. A pull request would be welcome if you could make it work for your output (from FVCOM 5.1.0), but without breaking compatibility with earlier version (i.e. existing unit-tests and examples) |
Hi,
I have been trying to run OceanDrift with results from FVCOM v.5.1.0 (latest) and getting the reader discarded because the variable "siglay_center" is not found. See the attached screenshot.
After checking the file you use for the example in readthedocs (AkvaplanNiva_sample_lonlat_fixed.nc) I notice that that file includes the variables "siglay_center", "siglev_center" and "h_center" (all refering to the centroid of the triangle) which, at least in the newer versions of FVCOM, are not included in the output files. Maybe this is something that was included in old versions or something that was pre-processed in the file from AkvaplanNiva, but it generates a conflict with the newest FVCOM outputs. Worth correcting.
The text was updated successfully, but these errors were encountered: