ExportFields

Type:section Appearance:simple Excludes:CartesianToFourierTransform, ConvertToPowerFlux, CreateReducedBasis, DensityIntegration, DipoleEmission, EvaluateReducedBasis, ExportGrid, FarField, FluxIntegration, FourierTransform, GridStatistics, IntegrationWeights, LayeredMediaSolver, ModeOverlap, MultipoleExpansion, OpticalImaging, PupilField, Radiation, ResonanceExpansion, ResonanceOverlap, ScatteringMatrix, Superposition, SurfaceDensityIntegration

Use this section to export a JCM fieldbag to a third-party of JCM format or to evaluate the fields on a regular grid.

An export definition to a Cartesian grid has the following syntax:

PostProcess {
  ExportFields {
    FieldBagPath = ... # load the |JCM| fieldbag
    OutputQuantity = ... # specify the quantity to be exported
    ...
    OutputFileName = ...
    Cartesian {
      ...
    }
  }
}

The dots stand for additional definitions, which are explained in the subsequent subsections.

Storage format

The format of the output file depends on the employed options:

• a JCM fieldbag by default (no other option set) of if the Unstructured section is filled

• a cartesian JCM fieldbag if a Cartesian export grid is defined

• a JCM table if a PointList is defined. The output table contains one row per requested evaluation point:

  • Columns 1–3: PointsX, PointsY, PointsZ

    Cartesian coordinates of the evaluation point.

  • Column 4: DomainId

    The physical-domain identifier containing the point.

  • Columns 5–…: <Quantity><Component>_<iF>

    The complex components of the exported tensor quantity. <Component> is X, Y, Z for a vector; two Cartesian component letters are used for a rank-two tensor. There is one consecutive component block for each requested field.

    The header metadata entry Polarization records the polarization used for the export.