<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Erik,<div><br></div><div>There is no averaging occuring when you use coordinate subscripting. You will get</div><div>actual values in your array, if a coordinate match is found.</div><div><br></div><div>NCL tries to find the closest coordinate values *within* the range of the coordinate subscript(s)</div><div>you give it, and then it returns the data values at those locations.</div><div><br></div><div>If you specify a coord range whose begin and end values are completely outside</div><div>the range of your actual coord values, you will get an error that looks like this:</div><div><br></div><div><div> fatal:NclOneDValGetClosestIndex: finish coordinate index out of range, can't continue</div><div> fatal:Could not obtain coordinate indexes, unable to perform subscript</div></div><div><br></div><div>If you use a single coordinate value that is not within the range, you will also get an error.</div><div><br></div><div>If your coordinate values are, say, (/1,2,3,4,5,6/), and you use a coordinate subscript range</div><div>of {2.5:5.5}, then this will correspond to the range represented by the coordinate</div><div>values (/3,4,5/), because 3 > 2.5, and 5 < 5.5.</div><div><br></div><div>The best way to learn this stuff is to just play around with a dummy array yourself. I've</div><div>created a start NCL script for you. Try running it and see if you understand the output</div><div>you're getting. Add your own coordinate subscripting to see what happens.</div><div><br></div><div>Run this script with:</div><div><br></div><div> ncl -n coords.ncl</div><div><br></div><div>so you don't get the annoying "(0)" at the beginning of every line.</div><div><br></div><div><br></div><div>--Mary</div><div></div></body></html>