Re: [ferret_users] Fill and

Yes, the ndigits argument to CONTOUR/LEVELS is what I meant in mentioning that.

I have also seen very small changes to the CONSET parameter DSLAB (distance between labels) lead to a big change in the resulting plot. That is, you can adjust DSLAB slightly, then gradually increase the adjustment, but get no change to the plot. Then another small change suddenly makes a big difference. I don't understand this but it is something to play with if nothing else works. Again, choosing the "right" number of contour levels given the available space along each contour and closeness to nearby contours is a hard thing to program.

Billy

On Tue, Jun 21, 2022 at 9:25 AM Serena Illig <serena.illig.ird@xxxxxxxxx> wrote:

Dear William,
Thanks for your answer. I definitely agree with you that Ferret is doing a wonderful job for contours, and plotting in general (especially time).
Concerning the contour, I did try CONSET at one point, but I did not play with SHAKEY because I only plot contours.
PPL CONSET did not solve my problem:
use coads_climatology.cdf
contour/x=50w:20e/y=30s:30n/lev=(20,23,1)/set SST[l=@ave]
ppl CONSET 0.08 1 1 0.04 0.04 0.0
ppl contour

Vijith indicated me a nice solution based on the ndigit inputs in /LEVELS=(lo, hi, delta, ndigits)
"ndigits (applies to CONTOUR command only) is the number of decimal places to use when labeling the level on individual contour lines as: -1 for integer format or -3 to omit numerical labels"
It works perfectly.

For the FILL/SHADE commands, I discovered it when I plotted some symmetric color scale for wind stress anomalies, which were not symmetric because of the missing last level... To obtain the right plot, I just added an extra level in the /LEVELS command, such as:

shade/x=50w:20e/y=30s:30n/levels=(0.014,0.030,0.001) SST[l=@ave]/1000
plots a color scale starting at 0.014 and ending at 0.029.

I do not understand why some specifications work and some do not. I will pay extra attention to my color scale, just in case the top-level disappears.

Many thanks,

Serena

.¸. , . .·´¯`·
><(((º>    `·.¸.·´¯`·...¸><(((º>¸.¸. , . .·´¯`· ><(((º> .
`·.¸.·´¯`·...¸><(((º> d by qualifiers to CONTOUR, or by its /LEVELS options; see CONTOUR)

With respect to occasional missing end values in the colorbar, I think this may be the result of rounding somewhere in the calculation (???). You can often work around this by tweaking the upper or lower bound by a tiny amount. E.g.,

If the original command fails:
shade/x=50w:20e/y=30s:30n/levels=(0.014,0.029,0.001) SST[l=@ave]/1000
Try:
shade/x=50w:20e/y=30s:30n/levels=(0.013999,0.029,0.001) SST[l=@ave]/1000
or:
shade/x=50w:20e/y=30s:30n/levels=(0.014,0.029001,0.001) SST[l=@ave]/1000

I don't know why these sometimes succeed when the apparently correct specification fails!

Billy

On Tue, Jun 21, 2022 at 4:52 AM Serena Illig <serena.illig.ird@xxxxxxxxx> wrote:
Dear Ferret users,

I hope this email finds you well.

I am writing regardi ;                                      .
                                           <º)))><..·