This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Mike, re: > There is a slight change in "shape" if I understand your usage correctly, > that's what I meant with some small differences in extent. I'm attaching > two samples of FED, one from the VLAB L3 set (made on the VM) and one from > the TTU set (made in production); you can see that region in real time > here: > https://weather.cod.edu/satrad/?parms=regional-southeast-02-24-0-100-1&checked=map-glm_fed&colorbar=undefined > > NB: Ignore the bad date on the VLAB sample. That's a result of my > scripting that I haven't fully converted over yet, not at all McIDAS > related. I would expect a change in extent/shape of features when comparing the L2 TTU products with L3 Vlab products since the L3 Vlab products have greater accumulations of values over time than the L2 TTU products. A more apples-to-apples comparison might be of an L2 TTU product with an L2 Vlab product of the same time. Then again, there is also the possibility that the Vlab products are not corrected for parallax. I'll need to ask Tiffany if she knows. re: > I vaguely recall parallax corrections being one of the differences in the > new data set. But looking back at some old emails I can't find anything to > back that up. But that's my hypothesis that I want to test. Eric made a point about his TTU products being parallax corrected. re: > Tell Eric and others I say hi! I don't know if I will get to see Eric before he leaves tomorrow evening. Unlike the Usercomm meetings, general staff is not invited to SAC meetings. re: we'll know more after getting some comparative samples. > Nor do I, at least not yet. I'll try to get some answers before the > weekend. Sounds good. I have to run now to get to ThAC :-) Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: USW-595984 Department: Support McIDAS Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.