You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frequency describes the levels to be labeled. If the frequency is
positive, the labels are plotted on the right/top of the color bar.
If it is negative, the labels are plotted on the left/bottom of the
color bar. The default is -1.
The +/- value is still honored for the sake of specifying which side the labels are on. However, the value is ignored for many Nexrad products; the frequency interval is hard-coded into Gempak: gempak/source/gemlib/im/imcbar.f A quick peak at that file starting at line 216 spills the beans:
C* Label Frequency Not Implemented - Label All
C* Special handling for NEXRAD 256-level products
Unhandled products look like this, which is not ideal:
#73 includes handling for the new Super-Res products, at least for plotting labels on the left side, but the right side still needs a little love:
But again, once the products have handling in imcbar.f, it's hard-coded into the software and the passed frequency value is ignored. The only way to adjust the frequency is to edit those values and remake the software, which is also not ideal.
The text was updated successfully, but these errors were encountered:
The Gempak 7.5.1 documentation states:
The +/- value is still honored for the sake of specifying which side the labels are on. However, the value is ignored for many Nexrad products; the frequency interval is hard-coded into Gempak:
gempak/source/gemlib/im/imcbar.f
A quick peak at that file starting at line 216 spills the beans:Unhandled products look like this, which is not ideal:
#73 includes handling for the new Super-Res products, at least for plotting labels on the left side, but the right side still needs a little love:
But again, once the products have handling in imcbar.f, it's hard-coded into the software and the passed frequency value is ignored. The only way to adjust the frequency is to edit those values and remake the software, which is also not ideal.
The text was updated successfully, but these errors were encountered: