13 |
michaesp |
1 |
1) In the Lagranto folder you shoud have the following files and directories:
|
|
|
2 |
|
|
|
3 |
rossby.ethz.ch[229]: ls -l
|
|
|
4 |
drwxr-xr-x 3 michaesp wheel 2048 Apr 5 13:31 bin/
|
|
|
5 |
drwxr-xr-x 3 michaesp wheel 1024 Apr 5 13:31 caltra/
|
|
|
6 |
drwxr-xr-x 7 michaesp wheel 1024 Apr 4 16:57 docu/
|
|
|
7 |
drwxr-xr-x 5 michaesp wheel 1024 Apr 4 16:57 figure/
|
|
|
8 |
drwxr-xr-x 3 michaesp wheel 4096 Apr 5 13:31 goodies/
|
|
|
9 |
-rwxr-xr-x 1 michaesp wheel 8738 Apr 5 12:01 install.csh*
|
|
|
10 |
drwxr-xr-x 3 michaesp wheel 1024 Apr 5 13:31 lib/
|
|
|
11 |
drwxr-xr-x 3 michaesp wheel 1024 Apr 5 13:31 select/
|
|
|
12 |
drwxr-xr-x 3 michaesp wheel 1024 Apr 5 13:31 trace/
|
|
|
13 |
|
|
|
14 |
|
|
|
15 |
2) If you haven't done so, you should then install Lagranto with
|
|
|
16 |
|
|
|
17 |
> ./install.csh all
|
|
|
18 |
|
|
|
19 |
and at the end all Fortran programs should be compiled and linked within the <bin> directory.
|
|
|
20 |
|
|
|
21 |
|
|
|
22 |
3) The next step is to prepare all files for a Lagranto run. In my case, this looks as follows:
|
|
|
23 |
|
|
|
24 |
rossby.ethz.ch[234]: ls -l
|
|
|
25 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:53 P20110826_12 -> wrfout_d01_2011-08-26_12:00:00
|
|
|
26 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:54 P20110826_13 -> wrfout_d01_2011-08-26_12:01:00
|
|
|
27 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:54 P20110826_14 -> wrfout_d01_2011-08-26_12:02:00
|
|
|
28 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:54 P20110826_15 -> wrfout_d01_2011-08-26_12:03:00
|
|
|
29 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:54 P20110826_16 -> wrfout_d01_2011-08-26_12:04:00
|
|
|
30 |
lrwxrwxrwx 1 michaesp wheel 30 Mar 25 14:54 P20110826_17 -> wrfout_d01_2011-08-26_12:05:00
|
|
|
31 |
-rw-r--r-- 1 michaesp wheel 11676728 Apr 5 13:31 wrfmap.nc
|
|
|
32 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:00:00
|
|
|
33 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:01:00
|
|
|
34 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:02:00
|
|
|
35 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:03:00
|
|
|
36 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:04:00
|
|
|
37 |
-rw-r--r-- 1 michaesp wheel 101793120 Mar 11 2013 wrfout_d01_2011-08-26_12:05:00
|
|
|
38 |
|
|
|
39 |
The files <wrfout*> are from WRF output; I link these files to the corresponding P{yyyymmdd_hh} files,
|
|
|
40 |
the format and naming requested by Lagranto. Finally, there is an important auxiliary file <wrfmap.nc> which
|
|
|
41 |
is needed for the conversion between latitude/longitude coordinates and WRF grid coordinates.
|
|
|
42 |
|
|
|
43 |
|
|
|
44 |
4) For tests you can find the files liste in 3) on our FTP server: <ftp://iacftp.ethz.ch/pub_read/sprenger/lagranto.wrf.test/>.
|
|
|
45 |
It might be worthwile to do a first sample run based on these files. Then we certainly know that the basic installation is ok :-)
|
|
|
46 |
|
|
|
47 |
|
|
|
48 |
5) An important file is the <wrfmap.nc> which includes the transformation between longitude/latitude and x/y coordinates.
|
|
|
49 |
All calculations are done in WRF's x/y space, but at the beginning or end of a calculation you might want to convert from
|
|
|
50 |
or to geographical lon/lat coordinates. Please consult the manual page for this command (included in the WRF docu folder):
|
|
|
51 |
|
|
|
52 |
> lagrantohelp wrfmap
|
|
|
53 |
|
|
|
54 |
or if this doesn't work:
|
|
|
55 |
|
|
|
56 |
> nroff -man lagranto.wrf/docu/man/wrfmap.0
|
|
|
57 |
|
|
|
58 |
|
|
|
59 |
6) Here are some first steps in running Lagranto with WRF. First, you have to create a start position file, which lists
|
|
|
60 |
the longitude, latitude and height of the starting position of the trajectory:
|
|
|
61 |
|
|
|
62 |
> more startf.ll
|
|
|
63 |
-70 45 5000
|
|
|
64 |
|
|
|
65 |
In a next step you should convert this start position into WRF coordinates:
|
|
|
66 |
|
|
|
67 |
> wrfmap -ll2xy startf.ll startf.xy
|
|
|
68 |
> more startf.xy
|
|
|
69 |
Reference date 00000_0000 / Time range 0 min
|
|
|
70 |
|
|
|
71 |
time x y z
|
|
|
72 |
-----------------------------
|
|
|
73 |
|
|
|
74 |
0.00 107.66 131.30 5000
|
|
|
75 |
|
|
|
76 |
At the moment the reference time (corresponding to time 0 of your trajectory) is not correctly set. Could you do this,
|
|
|
77 |
at the moment, manually. The modified file in my case looks then as follows:
|
|
|
78 |
|
|
|
79 |
> more startf.xy
|
|
|
80 |
Reference date 20110826_1200 / Time range 0 min
|
|
|
81 |
|
|
|
82 |
time x y z
|
|
|
83 |
-----------------------------
|
|
|
84 |
|
|
|
85 |
0.00 107.66 131.30 5000
|
|
|
86 |
|
|
|
87 |
Wit this minor correction Lagranto should run. Here is the call and the corresponding output:
|
|
|
88 |
|
|
|
89 |
> caltra 20110826_12 20110826_17 startf.xy trajectory.xy
|
|
|
90 |
> more trajectory.xy
|
|
|
91 |
Reference date 20110826_1200 / Time range 300 min
|
|
|
92 |
|
|
|
93 |
time x y z
|
|
|
94 |
-----------------------------
|
|
|
95 |
|
|
|
96 |
0.00 107.66 131.30 5000
|
|
|
97 |
1.00 109.71 130.91 4886
|
|
|
98 |
2.00 111.79 130.80 4746
|
|
|
99 |
3.00 113.89 130.98 4788
|
|
|
100 |
4.00 116.03 131.46 4847
|
|
|
101 |
5.00 118.21 132.26 4810
|
|
|
102 |
|
|
|
103 |
The position (x/y) of the air parcel is given in WRF coordinates; to get them back into lon/lat, you can use
|
|
|
104 |
again <wrfmap>:
|
|
|
105 |
|
|
|
106 |
> wrfmap -xy2ll trajectory.xy trajectory.ll
|
|
|
107 |
> more trajectory.ll
|
|
|
108 |
Reference date 20110826_1200 / Time range 300 min
|
|
|
109 |
|
|
|
110 |
time lon lat z
|
|
|
111 |
-----------------------------
|
|
|
112 |
|
|
|
113 |
0.00 -70.00 44.99 5000
|
|
|
114 |
1.00 -69.32 44.86 4886
|
|
|
115 |
2.00 -68.62 44.78 4746
|
|
|
116 |
3.00 -67.91 44.78 4788
|
|
|
117 |
4.00 -67.18 44.84 4847
|
|
|
118 |
5.00 -66.42 44.97 4810
|
|
|
119 |
|
|
|
120 |
That's it! Now would come tracing of fields along trajectories and/or selection of trajectories. But these
|
|
|
121 |
steps can wait until you could reproduce all steps above :-) Let me know about your progress ;-)
|
|
|
122 |
|