Replies: 8 comments
-
|
Greetings! (1) I normally use meteorology files from READY ARL which are in pre-formatted for STILT/HYSPLIT. **Are you using a converter to ensure your WRF files are STILT compatible? ** (2) (see above) (3) Typically, I use X-STILT which is a slightly different version of the standard STILT model. For multiple receptors, I have rewritten (4) Are you wanting to generate the [@tartanrunner25 should be able to answer (1) and (2) better than I can.] |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Roten: |
Beta Was this translation helpful? Give feedback.
-
|
Hello, For number 1 and 2, WRF is independent of STILT in that the WRF grid does not matter. STILT will generate trajectories by interpolating winds from the WRF Lambert conformal grid and using the interpolated winds to create the backward trajectories. The trajectory positions and their corresponding footprint values are then gridded to generate the gridded STILT footprint. So long story short, just because WRF is on a Lambert conformal grid does not mean STILT's footprint needs to be on the same grid. For my own WRF runs, I typically use the same grid projection as you, and then run STILT and project the footprints on a standard lat/lon grid. The grid can also be at a completely different resolution. For number 3, yes you can have multiple locations. When you create a vector of the runs you want in the run_stilt.r code, your data table of the runs you want to generate should look like the following (just an example): run_time lati long zagl If you want there to be multiple locations you would just need reconstruct the data table such that the second location has its own row and time, for example: run_time lati long zagl As long as the run is in this data table format, the STILT wrapper is smart enough to set up a run for different locations. I've done this using 100+ receptors for one run_stilt.r job. For number 4, you will need to find your own emissions inventory and convolve is with the STILT footprint. The link that Dustin provided gives an example of how to convolve the emissions with the STILT footprint. For the US, we commonly use VULCAN for CO2 emissions. If you are looking for a global emission product, ODIAC might be a good place to start. I've also used STILT with fire emission inventories like FINN, really the options are pretty limitless =) -Derek |
Beta Was this translation helpful? Give feedback.
-
|
I see. Thank you for your help! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Professors: |
Beta Was this translation helpful? Give feedback.
-
|
In essence, it can be view as forward footprint, so yes you can still use the foot*.nc files. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, UCASY user Mr. Yang. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, professors:
I used the WRF output to driven the STILT model, I have 4 questions about it.
Receptor location(s)
lati <- 40.766189
long <- -111.847672
zagl <- 25
the receptor location only can set one in once simulation?
How it can set multiple locations in once simulation? Just like
lati <- 40.766189 38.0 …..
long <- -111.847672 -112.0 …
zagl <- 25 24 …
i got an error about it when set 2 locations
[1] "2021-04-01 12:00:00 UTC" "2021-04-01 13:00:00 UTC"
Error: unexpected numeric constant in "lati <- 43.88 44.0"
Execution halted
4. how to generate the emissions.rds file?
Beta Was this translation helpful? Give feedback.
All reactions