The error message is complaining that you have a . at the end of the command.
lon and lat are just used in the documentation examples. You will need to use 2-dimensional longitude and latitude coordinate variables from your dataset. There are several coordinate-variable pairs in your data. Often the attributes of the variables include a " coordinates" attribute. Try this,
yes? use wrfdaily.nc
yes? show attributes HGT
If there is a coordinates attribute, then it'll list which ones to use. If there are not coordinates attributes, then I would guess that XLONG, XLAT are the ones to use.
On 10/21/2015 2:26 AM, afwande juliet
wrote:
When I do as u say like below. The 3hourly data as averaged using CDO to daily using the "cdo daymean ifile ofile"yes? set data wrfdaily.nc
*** NOTE: Units on axis "time" are not recognized: day as %Y%m%d.%f
*** NOTE: They will not be convertible:
yes? show data
currently SET data sets:
1> ./wrfdaily.nc (default)
name title I J K L M N
XLONG longitude 1:279 1:239 ... ... ... ...
XLAT latitude 1:279 1:239 ... ... ... ...
XLONG_U longitude 1:280 1:239 ... ... ... ...
XLAT_U latitude 1:280 1:239 ... ... ... ...
XLONG_V longitude 1:279 1:240 ... ... ... ...
XLAT_V latitude 1:279 1:240 ... ... ... ...
LU_INDEX 1:279 1:239 ... 1:96 ... ...
ZNU 1:50 ... ... 1:96 ... ...
ZNW 1:51 ... ... 1:96 ... ...
ZS 1:4 ... ... 1:96 ... ...
DZS 1:4 ... ... 1:96 ... ...
VAR_SSO 1:279 1:239 ... 1:96 ... ...
LAP_HGT 1:279 1:239 ... 1:96 ... ...
U 1:280 1:239 1:50 1:96 ... ...
V 1:279 1:240 1:50 1:96 ... ...
W 1:279 1:239 1:51 1:96 ... ...
PH 1:279 1:239 1:51 1:96 ... ...
PHB 1:279 1:239 1:51 1:96 ... ...
T 1:279 1:239 1:50 1:96 ... ...
HFX_FORCE
... ... ... 1:96 ... ...
LH_FORCE ... ... ... 1:96 ... ...
TSK_FORCE
... ... ... 1:96 ... ...
HFX_FORCE_TEND
... ... ... 1:96 ... ...
LH_FORCE_TEND
... ... ... 1:96 ... ...
TSK_FORCE_TEND
... ... ... 1:96 ... ...
MU 1:279 1:239 ... 1:96 ... ...
MUB 1:279 1:239 ... 1:96 ... ...
NEST_POS 1:279 1:239 ... 1:96 ... ...
P 1:279 1:239 1:50 1:96 ... ...
PB 1:279 1:239 1:50 1:96 ... ...
FNM 1:50 ... ... 1:96 ... ...
FNP 1:50 ... ... 1:96 ... ...
RDNW 1:50 ... ... 1:96 ... ...
RDN 1:50 ... ... 1:96 ... ...
DNW 1:50 ... ... 1:96 ... ...
DN 1:50 ... ... 1:96 ... ...
AND WHEN I DO THE FILL COMAND I GET THE ERROR BELOW
yes? Fill/l=96/Hlim=21:54/Vlim=-12:22 HGT, "lon, lat".
**ERROR: command syntax: "lon, lat".
"lon, lat" before . is illegal
yes? Fill/l=96/Hlim=21:54/Vlim=-12:22 HGT, "xlon, xlat".
**ERROR: command syntax: "xlon, xlat".
"xlon, xlat" before . is illegal
On Wed, Oct 21, 2015 at 1:25 AM, Bruno Levier <bruno.levier@xxxxxxxxxxxxxxxxx> wrote:
Hi
Perhaps your grid is curvilinear (a "show data" would be usefull). If so, you can not use the "set region" to specify the longitude and latitude, and you have to add the longitude and latitude in the "fill" command. For instance if your longitude variable is named "lon" and your latitude is named "lat", try "Fill/l=96/Hlim=21:54/Vlim=-12:22 HGT, lon, lat".
More informations about curvilinear coordinates in the Ferret manual: http://ferret.pmel.noaa.gov/Ferret/documentation/users-guide/working-with-special-data-sets/CURVILINEAR-COORDINATE-DATA
Bruno
On 10/21/2015 04:24 AM, afwande juliet wrote:
Dear ferret usersI am plotting wrfoutput by typing
yes? fill/l=96 HGT
yes? go land 1 "" 1
yes? set region/y=-12:22.5/x=21:54
yes? fill/l=96 HGT
yes? go land 1 "" 1
yes? frame/file=hgt.gif
I get only half the domain size.Does someone have an idea how to go about thisattached is my figure.Could it be a problem with the grids??? I don't how to go about this
Click here to report this email as spam.
--
Bruno LEVIER
Monitoring and Forecasting Systems Evaluation Team
+33 5 61 39 38 51
bruno.levier@xxxxxxxxxxxxxxxxx
mercator-ocean.eu marine.copernicus.eu
