Welcome back to AWIPS Tips, where it’s time to talk about time! Specifically, we'll talk about how CAVE handles displaying multiple datasets with different temporal resolutions. For example, during a storm, radar volumes might get updated every 2 to 3 minutes, whereas METAR reports might come in every 20 to 60 minutes.
CAVE handles this temporal disparity by assigning the first dataset loaded into a display as the Time Match Basis. This means subsequently loaded datasets will only display frames with times closest to the Time Match Basis dataset. The Time Match Basis can be changed in the hold-right-click context menu for the desired dataset in the Resource Stack.
TIP: Load the dataset with the finest temporal resolution first to get the best temporal matching.
To see the Time Match Basis in action, follow along with this video demo:
That’s all the time we have for today! Catch us again in two weeks for the next blog post, in which we’ll discuss data access with Python-AWIPS.
To view archived blogs, visit the AWIPS Tips blog tag, and get notified of the latest updates from the AWIPS team by signing up for the AWIPS mailing list. Questions or suggestions for the team on future topics? Let us know at firstname.lastname@example.org
This blog was posted in reference to v18.1.1 of NSF Unidata AWIPS