...
| Warning |
|---|
codesUI is still work-in-progress, but is being made available for selected users to test. |
Starting codesUI
The command to start the application on Leap42 and OpenSUSE13.1 workstations at ECMWF is:
...
This panel is located on the left and contains the list of input files
Click on a given file in the list to load it into codesUi (only one file can be loaded at a time).
To add a new file to the list use the File → Add file ... menu (or press Ctrl+N).
The file list panel It can be shown/hidden with the
...
button in the toolbar.
Inspecting BUFR messages
Key profiles
When a BUFR file is loaded codesUI scans the header of all the messages and displays the message list in the message list panel.
In this list a set of ecCodes BUFR header keys are displayed for each message. The column heading only display an abbreviation defined for the actual key. We can figure out the full key name from the tooltip when hovering over the table heading.
The header keys are grouped into key profiles. When a new key profile is selected in the Key profile combobox in the toolbar:
codesUI rescans all the messages and re-populates the message list according to the new key profile.
Key profiles can be added, removed and edited from the Key profile manager dialogue (Profiles → Manage profiles ... menu):
The default key profile
By default a profile called "Default" is loaded with the following contents:
This profile is actually a copy of the System:Default profile that, in contrast to any other profiles, as a fail-safe solution cannot be edited.
Subset navigation
A BUFR message can contain multiple subsets in either compressed or uncompressed format. The actual number of subsets is defined by the numberOfSubsets key in the message header. Whether a muti-subset message is compressed or not is determined by the compressedData key (also in the header).
No subsets
When numberOfSubsets = 1 the message does not have subsets and the message panel header looks like this.
Uncompressed subsets
When numberOfSubsets >= 1 and compressedData = 0 1 the message contains uncompressed subsets. In this case there are two modes to navigate through the subsets. This mode is defined in the Settings menu:
By default this option is unchecked meaning that the data dump shows all the subsets in one go like this:
On the other hand, when this option is checked the subsets can be navigated through with the Subset interface in the message panel header. In this way the data dump only shows the values of the selected subset. This is how our message looks like for subset 1:
and this how it looks like for subset 2:
