Electric / Magnetic Near Fields (.EFE / .HFE)
The data structure for the .efe and .hfe files are described.
The following fields are available in the header block:
Key  Required  Description 

File Type  Yes  Describes the type of the file. The file type can be any of the following:

File Format  Yes  Denotes the file syntax version (such a “4”). If not present, it defaults to version 1 (files predating Feko 6.1). 
Source  Optional  Denotes the base filename of the source where this data comes from. 
Date  Optional  Date and time of data export in format “YYYYMMDD hh:mm:ss” (that is 24hour format) 
The following fields are available in the solution block header:
Key  Required  Description 

Configuration Name  Optional  The configuration name, if present. 
Request Name  Optional  The explicit name given to that solution request (as denoted in the
.pre file). If none is
specified, POSTFEKO uses a default name of
request_N (where _N is replaced with a number
for each unnamed request) during import. 
Frequency  Yes  Frequency in Hz for which the following data was measured/computed. 
Coordinate System  Optional  Coordinate system in which the axes are defined:

Origin  Optional  Origin of the data coordinate system in form (x, y, z) (always in Cartesian coordinates; based on global origin). If no origin is provided, assume (x, y, z) = (0, 0, 0). 
UVector  Optional  Indicates a point on the U axis relative to the Origin. If none is specified, it is assumed that the U axis coincides with the X axis. 
VVector  Optional  Indicates a point on the V axis relative to the origin. If none is specified, it is assumed that the V axis coincides with the Y axis. 
No. of [$$$] Samples  Yes  The number of samples in each axis direction. The “[$$$]” term is replaced
by the following:

Result Type  Optional  For electric near fields (.efe), this specifies whether the output is one of the following:

Excluded Faces Key  Only applicable to Cartesian near field boundary request.  Specify an integer that is a bitwise interpretation of the following:

Spatial Units  Optional  Specify the units in which the position is defined. 
Result Units  Optional  Specify the units in which the results are given. 
No. of Header Lines  Optional  Number of header lines to read. The column header lines must follow this line. If this value is not specified, assume a value of “1”. 
Yes  For header lines, the following format should be
used:

X Y Z Re($$$x) Im($$$x) Re($$$y) Im($$$y) Re($$$z) Im($$$z)
X Y Z Re($$$) Im($$$)
Rho Phi X Re($$$rho) Im($$$rho) Re($$$phi) Im($$$phi) Re($$$x) Im($$$x)
Rho Phi X Re($$$) Im($$$)
Rho Phi Y Re($$$rho) Im($$$rho) Re($$$phi) Im($$$phi) Re($$$y) Im($$$y)
Rho Phi Y Re($$$) Im($$$)
Rho Phi Z Re($$$rho) Im($$$rho) Re($$$phi) Im($$$phi) Re($$$z) Im($$$z)
Rho Phi Z Re($$$) Im($$$)
Radius Theta Phi Re($$$r) Im($$$r) Re($$$theta) Im($$$theta) Re($$$phi) Im($$$phi)
Radius Theta Phi Re($$$) Im($$$)
Rho Phi Z Re($$$rho) Im($$$rho) Re($$$phi) Im($$$phi) Re($$$z) Im($$$z)
Rho Phi Z Re($$$) Im($$$)
.efe  Electric Near Field Files 

E  for electric field values 
A  for magnetic vector potential values 
grad(PHI)  for gradient of the scalar electric potential values 
PHI  for scalar electric potential values 
.hfe  Magnetic Near Field Files 

H  for magnetic field values 
F  for electric vector potential values 
grad(PSI)  for gradient of the scalar magnetic potential values 
PSI  for scalar magnetic potential values 
Cartesian Near Field Boundary
The sampling order is as follows for a Cartesian near field boundary request:
Xmin → Xmax → Ymin → Ymax → Zmin → Zmax
...
#Coordinate System: Cartesian Boundary
...
#Excluded Faces Key: 1
...
# "X" "Y" "Z" ...
0 0 0 ... ** X_min
0 1 0 ...
0 0 1 ...
0 1 1 ...
1 0 0 ... ** X_max
1 1 0 ...
1 0 1 ...
1 1 1 ...
0 0 0 ... ** Y_min
1 0 0 ...
0 0 1 ...
1 0 1 ...
0 1 0 ... ** Y_max
1 1 0 ...
0 1 1 ...
1 1 1 ...
0 0 0 ... ** Z_min
1 0 0 ...
0 1 0 ...
1 1 0 ...