You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
How to assimilate remote sensing retrieval results using WRFDA
- Thread starter hyx98
- Start date
Hello hyx98,
I would have to say it depends on which data you're trying to assimilate into the model. If you're trying to assimilate temperature at a certain altitude or other meteorological variables, then it should be simple. What are you trying to assimilate? In the guide for reading a little r file, there are multiple lists of variables that little r reads in (as well as ones it doesn't read in).
Thank you,
JeremyB
I would have to say it depends on which data you're trying to assimilate into the model. If you're trying to assimilate temperature at a certain altitude or other meteorological variables, then it should be simple. What are you trying to assimilate? In the guide for reading a little r file, there are multiple lists of variables that little r reads in (as well as ones it doesn't read in).
Thank you,
JeremyB
Hello JeremyB,
I hope this message finds you well. I would like to take this opportunity to respond to your inquiry. Indeed, I am preparing to assimilate satellite-derived land surface temperature(LST). The data I plan to use includes latitude, longitude, LST value and altitude information.
Recently, after reading more about Little_R, I have an idea that I'm not sure is feasible, and I would greatly appreciate your guidance on this matter. My question is whether it would be possible to set the FM-Code in Little_r to FM-35, which would allow me to assimilate satellite-derived LST as station temperatures. If so, would it then be necessary to output a separate Little_r for each remote sensing pixel?
Thank you in advance for your time and consideration. I look forward to your response.
Best regards,
hyx98
I hope this message finds you well. I would like to take this opportunity to respond to your inquiry. Indeed, I am preparing to assimilate satellite-derived land surface temperature(LST). The data I plan to use includes latitude, longitude, LST value and altitude information.
Recently, after reading more about Little_R, I have an idea that I'm not sure is feasible, and I would greatly appreciate your guidance on this matter. My question is whether it would be possible to set the FM-Code in Little_r to FM-35, which would allow me to assimilate satellite-derived LST as station temperatures. If so, would it then be necessary to output a separate Little_r for each remote sensing pixel?
Thank you in advance for your time and consideration. I look forward to your response.
Best regards,
hyx98
Hello hyx98,Hello JeremyB,
I hope this message finds you well. I would like to take this opportunity to respond to your inquiry. Indeed, I am preparing to assimilate satellite-derived land surface temperature(LST). The data I plan to use includes latitude, longitude, LST value and altitude information.
Recently, after reading more about Little_R, I have an idea that I'm not sure is feasible, and I would greatly appreciate your guidance on this matter. My question is whether it would be possible to set the FM-Code in Little_r to FM-35, which would allow me to assimilate satellite-derived LST as station temperatures. If so, would it then be necessary to output a separate Little_r for each remote sensing pixel?
Thank you in advance for your time and consideration. I look forward to your response.
Best regards,
hyx98
I suppose you could do it that way if you want. So long as you have the elevation and the rest of the remaining variables. There may be a better code to use on this website: WRFDA little r. As for outputting separate little r files, I don't think that's necessary unless the timestamps are more than an hour apart. I should also mention, I am unable to help create little r files. The best advice I can give with that is to create a code with your language of choice and AI is a great help with it.
Thank you,
JeremyB
Dear JeremyB,
With your help, I have gained a better understanding of the little_r format, but I still have a small confusion, which may also be due to my unclear description earlier. From the Little_r webpage, I learned that the header line contains only a single line, which means it only includes one set of latitude and longitude information. However, remote sensing retrieval products usually have multiple pixels. Therefore, for the assimilation of such data, like the FM-135 mentioned on the webpage, would multiple Little_r files be needed? And how should these Little_r files be named? I would appreciate if you could explain this further.
Happy new year and I am looking forward for your reply.
Best wishes,
hyx98
With your help, I have gained a better understanding of the little_r format, but I still have a small confusion, which may also be due to my unclear description earlier. From the Little_r webpage, I learned that the header line contains only a single line, which means it only includes one set of latitude and longitude information. However, remote sensing retrieval products usually have multiple pixels. Therefore, for the assimilation of such data, like the FM-135 mentioned on the webpage, would multiple Little_r files be needed? And how should these Little_r files be named? I would appreciate if you could explain this further.
Happy new year and I am looking forward for your reply.
Best wishes,
hyx98