Nope, not yet. It is on my list of things to do...
When I put this data into 4NEC2 I get a run segment check message and when I run a segment check I get this text as a result..
[CODE]eddie.nec wavelength=11.02 mtr.
Warn.: Wire 8, seg 110 (tag 8), EX-src: Nearby segm-length or radius differs too much.
Warn.: Wire 1, seg 1 (tag 1), len/rad at junction (4.013) below 6.
Warn.: Wire 1, seg 85 (tag 1), len/rad at junction (4.013) below 6.
Warn.: Wire 2 (tag 2), seg-len (2.4) below 2 * radius (4)
Error: Wire 2, seg 86 (tag 2), len/rad at junction (1.2) below 2.
Error: Wire 2, seg 90 (tag 2), len/rad at junction (1.2) below 2.
Warn.: Wire 8, seg 110 (tag 8), len/rad at junction (5.331) below 6.
Warn.: Wire 8, seg 110 (tag 8), len/rad at junction (5.331) below 6.
Warn.: Wire 9, seg 111 (tag 9), len/rad at junction (5.774) below 6.
Warn.: Wire 9, seg 113 (tag 9), len/rad at junction (5.774) below 6.
Warn.: Wire 22, seg 391, len/rad at junction (2.405) below 6.
[/CODE]
I also still get skewing, but the pattern does come close to matching yours.
Also, 4NEC2 shows an AGT of 1.251 with this as well, which is no where near desirable.
Assuming you didn't have any of these problems in EZNEC, I wonder if there are differences in how both programs treat the same data?
The DB
