Hello,

I have no idea about NEC-4 output file format. Is there any samples
for looking into or documentation?
Thanks for any hints.

Regards,
Aziz

On Oct 7, 12:18 pm, wrote:
Hello,

I have no idea about NEC-4 output file format. Is there any samples
for looking into or documentation?
Thanks for any hints.

Regards,
Aziz

Same as NEC-2

Hello,

On 7 Okt., 22:00, wrote:

Same as NEC-2

Really? If true, that would be fine.

Any small changes or is the format "exactly" the same?

wrote:
Hello,

On 7 Okt., 22:00, wrote:

Same as NEC-2


Really? If true, that would be fine.

Any small changes or is the format "exactly" the same?


Exactly the same, except where you're looking for something that is done
differently in NEC4 (e.g. NEC 4 supports catenaries, NEC2 doesn't, so
the "readback" of the source deck is different)

But for things like near and far fields or segment currents, the format
is the same.

If I remember correctly, position of the X-, Y- and Z-coordinates and
magnitudes/phase for the near-field data in the output file differ one
to three charcter-positions.

Arie.

Hello Arie,

before be confronted with unseen and unexpected data, I will support
on the first version only "NEC-2D" output files.

NEC2 Engine Booster is finished now. Everybody will be impressed about
the performance, that can be taken from multi-core / multi-processor
enhancements.
I have started the documentation for the web.

On the coming version, I will support near-field (NH, NE-cards) data
too. And when I can get a NEC-4 engine for evaluating and testing,
than it will also support NEC-4 engines.

Thanks everybody for the help.
Greetings,
Aziz

On 9 Okt., 16:35, 4nec2 wrote:
If I remember correctly, position of the X-, Y- and Z-coordinates and
magnitudes/phase for the near-field data in the output file differ one
to three charcter-positions.

Arie.

4nec2 wrote:
If I remember correctly, position of the X-, Y- and Z-coordinates and
magnitudes/phase for the near-field data in the output file differ one
to three charcter-positions.

Arie.


You're right... just compared NEC4 vs Nec2DXS

Here's NEC2 output (you'll have to unwrap it)
- LOCATION - - EX - -
EY - - EZ -
X Y Z MAGNITUDE PHASE
MAGNITUDE PHASE MAGNITUDE PHASE
METERS METERS METERS VOLTS/M DEGREES
VOLTS/M DEGREES VOLTS/M DEGREES
-10.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 1.4577E-01 89.07
12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890
-5.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 2.2855E-01 156.88
0.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 8.7109E+00 180.00

And NEC4

- LOCATION - - EX -
- EY - - EZ -
X Y Z MAGNITUDE PHASE
MAGNITUDE PHASE MAGNITUDE PHASE
METERS METERS METERS VOLTS/M DEGREES
VOLTS/M DEGREES VOLTS/M DEGREES
12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890
-10.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 1.4577E-01 89.09
-5.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 2.2854E-01 156.89
0.0000 0.0000 0.0000 0.0000E+00 0.00
0.0000E+00 0.00 8.7108E+00 180.00



It looks like the coordinates are each 1 character longer
X ends at 14 for N4, vs 13 for N2
Y ends at 26 for N4 vs 24 for N2
Z ends at 38 for N4 vs 35 for N2
The EX,EY,EZ appear to be the same width, so for N4 they start 3
characters farther over...

(Now I understand why my Matlab output file parser screwed up... Thanks,
Arie!)

Jim,

near-field data and NH/NE cards will be anyway not yet supported
(optimized) at the moment. I looked into the data records and found,
that they would be acceptable to my smart parser and it would not
cause any problems.
But I found another items on NEC-4 output data, that could cause
unpredictable results. These differencies have to be implemented and
could support on the next version of NEC Engine Booster.

Thanks for your help,
Aziz