Synchronizing the Magnetic and Electric fields

In the finite-difference time-domain method, the electric and magnetic fields are stored at different times (and different positions in space), in a leapfrog fashion. At any given time-step during the simulation, the and fields are stored at time , but the and fields are stored at time (where is the time-step size).

This means that when you output the electric and magnetic fields from a given time step, for example, the fields actually correspond to times apart. For most purposes, this slight difference in time doesn't actually matter much, but it makes a difference when you compute quantities like the Poynting flux that combine electric and magnetic fields together, e.g. for the output_poynting (Python) or output-poynting (Scheme) function. If what you really want is the Poynting flux at time t, then computing is slightly off from this — the error is of order , or first-order accuracy. This is unfortunate, because the underlying FDTD method ideally can have second-order accuracy.

To improve the accuracy for computations involving both electric and magnetic fields, Meep provides a facility to synchronize the and fields with the and fields in time. Technically, what it does is to compute the magnetic fields at time by performing part of a timestep, and then averaging those fields with the fields at time . This produces the magnetic fields at time t to second-order accuracy , which is the best we can do in second-order FDTD. Meep also saves a copy of the magnetic fields at , so that it can restore those fields for subsequent timestepping.

Synchronization Functions

All of this process is handled for you in Meep by a single step function: synchronized_magnetic (Python) or synchronized-magnetic (Scheme). By wrapping this around your step functions, it ensures that those step functions are called with synchronized electric and magnetic fields (to second-order accuracy), while restoring the magnetic fields automatically for subsequent timestepping.

For example, if you do:



(run-until 200 output-poynting output-tot-pwr)

it outputs the Poynting vector and the total energy density in the electric and magnetic fields at each timestep, but it only does so to first-order accuracy because those computations combine unsynchronized electric and magnetic fields. Instead, if you do



(run-until 200 (synchronized-magnetic output-poynting output-tot-pwr))

it will output the same quantities, but more accurately because the fields will be synchronized. Of course, there is a price: synchronizing the fields takes time, and also increases the memory usage in order to backup the unsynchronized fields.

Alternatively, if you want to synchronize the magnetic and electric fields in some context other than that of a step function, e.g. you are doing some computation like integrate_field_function (Python) or integrate-field-function (Scheme) outside of the timestepping, you can instead call two lower-level functions. Before doing your computations, you should call meep.Simulation.fields.synchronize_magnetic_fields() (Python) or (meep-fields-synchronize-magnetic-fields fields) (Scheme) to synchronize the magnetic fields with the electric fields, and after your computation you should call meep.Simulation.fields.restore_magnetic_fields() (Python) or (meep-fields-restore-magnetic-fields fields) (Scheme) to restore the fields to their unsynchronized state for timestepping. In the C++ interface, these correspond to fields::synchronize_magnetic_fields and fields::restore_magnetic_fields. If you don't call meep.Simulation.fields.restore_magnetic_fields or meep-fields-restore-magnetic-fields before timestepping, then the fields will be re-synchronized after every timestep, which will greatly increase the cost of timestepping.

In future versions, the fields may be synchronized automatically whenever you output something like the Poynting vector or do another field computation that involves both magnetic and electric fields, but currently you must do this manually (Issue #719). In any case, Meep does no additional work when you nest synchronization calls, so it is harmless to insert redundant field synchronizations. The flux_in_box (Python) or flux-in-box (Scheme) and field_energy_in_box (Python) or field-energy-in-box (Scheme) routines are already automatically synchronized, however.