Re: Looking for cause of unmatched node messages from gsn_csm_contour_map

From: David Brown <dbrown_at_nyahnyahspammersnyahnyah>
Date: Tue Jun 25 2013 - 15:37:09 MDT

Hi Craig,
These are debugging messages that probably should not appear in the way they do to the user. The algorithm for hexagonal grids sorts the vertices (nodes) of all the cells and then matches them in groups of 3. This particular sample is interesting and suggests a problem with the algorithm because it looks like it should have found 2 sets of three nodes rather than claiming these nodes are "unmatched".

I wonder if you can provide this data and your script. See if you have questions about how to upload your files.
I have been working on some upgrades that are somewhat related to this code and it would definitely be useful to recreate this scenario.
Also I will try to ensure that the next release prints out more user-friendly warnings in this part of the code, if and when needed.

On Jun 25, 2013, at 2:42 PM, Craig Tierney - NOAA Affiliate <> wrote:

> I am plotting results from an icosahedral via NCL. The plots look correct as far as I can tell. However, I am getting messages like:
> unmatched node 631901 2 0.000187 -33.094330
> unmatched node 631902 0 0.000187 -33.094330
> unmatched node 631865 4 0.000187 -33.094330
> unmatched node 529215 4 0.000582 53.780632
> unmatched node 529253 0 0.000582 53.780632
> unmatched node 529252 2 0.000582 53.780632
> These account for a very small percentage of the total points on my grid. What do these messages mean?
> Thanks,
> Craig
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:

ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
Received on Tue Jun 25 15:37:18 2013

This archive was generated by hypermail 2.1.8 : Mon Jul 01 2013 - 12:35:42 MDT