XPIC Features

XPIC(k) and FMPM(k) are two improved forms of MPM. The page explains how to use XPIC(k) and FMPM(k) features.

Introduction

The PIC method can be described as applying a projection operator that modifies (and filters) particle velocities before updating them with the grid acceleration. The problem with PIC is that its projection operator filters most problems too heavily resulting in significant dissipation of energy. XPIC(k) is a new method that solves the energy dissipation problem, enhances overall stability of MPM, and reduces noise. XPIC(k) defines a series of new projection operators that can significantly reduce the over damping of PIC simulations. XPIC(k) is defined by an order k, where k=1 is PIC, k>1 is XPIC, and large k approaches amethod with all null-space noise removed.

After deriving XPIC(k) methods, another improvement was to show that XPIC style calculations are equivalent to implementing an MPM method that approximates the inverse of the full mass matrix. Use this revised interpretation, the XPIC(k) scheme was modifed to derive another method denoted FMPM(k). FMPM(1) defines and improved form of PIC (compared to XPIC(1)) and higher orders also appear to further reduce dissipation compared to XPIC(k).

Performance

The drawback of XPIC(k)/FMPM(k) is that each higher order requires an extra extrapolation. The extra calculations scale with k*N where N is the number of particles in the problem. XPIC and FMPM are therefore less efficient than PIC or FLIP. In many problems, k=2 already provides much improvement over PIC and reduces undesirable energy dissipation with minimal extra calculations. Larger k is often better with k=4 appearing to provide much benefit without too much extra cost. Very high values of k (e.g., k>40) are typically unstable (due to too many additional extrapolations or to changes in effective eigenvalues for the equations).

XPIC(k) and FMPM(k) Commands

XPIC(k)and FMPM(k) simulations are created by scheduling a PeriodicXPIC Custom Task. In brief, this task selects the XPIC or FMPM order k and the frequency for using the calculations. See help on PeriodicXPIC Custom Task for more details. The remainder of this section describes prior methods for selecting XPIC(k) (but not FMPM(k)). They are no longer available in the latest code.

Eliminated XPIC Commands

Before the PeriodicXPIC Custom Task was added, XPIC(m) was selected using damping commands. Any old input files you have with this command should change those files to use a PeriodicXPIC Custom Task instead. The deleted command options are:

Damping (alphagVsT),<(fractionPIC)>,<(XPICOrder)>
PDamping (alphapVsT),<(fractionPIC)>,<(XPICOrder)>

where the relevant paramters for XPIC(m) are:

• (fractionPIC) is the fraction PIC to use in the simulation. It can vary from 1 for pure XPIC(m) to 0 for pure FLIP. The default is 0. Note that this option is inefficient and was therefore removed. You can replace a fraction XPIC(m) of φ in old calculations with XPIC(m) done every int(1/φ) time steps in the PeriodicXPIC Custom Task.
• (XPICOrder) to set the XPIC(m) order or m. It must be an integer and values less than 1 are set to 1. Note that this parameter is ignored unless PIC is activated with (fractionPIC) > 0. The default is 1, which is standard PIC.

Although (fractionPIC) and (XPICOrder) can be set in either the Damping or the PDamping command, only one setting for each is allowed; a simulation will use whichever setting comes last.

In XML input files, (fractionPIC) and (XPICOrder) can be set with commands in the <MPMHeader> element:

<Damping PIC='(fractionPIC)' function='(alphagVsT)'>(alphagNum)</Damping>
<XPIC order='(XPICOrder)'/>

Note that (XPICOrder) is ignored unless (fractionPIC) is greater than zero.