Difference between revisions of "PeriodicXPIC Custom Task"

From OSUPDOCS
Jump to navigation Jump to search
Line 56: Line 56:
  <Parameter name='periodicCFLDiffusion'>(CFLfactor)</Parameter>
  <Parameter name='periodicCFLDiffusion'>(CFLfactor)</Parameter>


The meanings of values <tt>(stepInterval)</tt>, <tt>(timeInterval)</tt> and <tt>(CFLfactor)<tt> are given in the [[#Using XPIC(m) For Particle Velocities|previous section]].
The meanings of values <tt>(stepInterval)</tt>, <tt>(timeInterval)</tt> and <tt>(CFLfactor)<//tt> are given in the [[#Using XPIC(m) For Particle Velocities|previous section]].


When using XPIC(m) for transport equations, you should never pick <tt>m=1</tt> because it causes too much numerical diffusion. Any higher order works, unless it XPIC(m) filtering is done too frequently. Because transport time step is usually much longer then mechanics time step, it is usually best to pick transport XPIC(m) frequency using the CFL parameter options.
When using XPIC(m) for transport equations, you should never pick <tt>m=1</tt> because it causes too much numerical diffusion. Any higher order works, unless it XPIC(m) filtering is done too frequently. Because transport time step is usually much longer then mechanics time step, it is usually best to pick transport XPIC(m) frequency using the CFL parameter options.

Revision as of 20:56, 11 February 2018

A custom task to use XPIC(m) method on selected time steps

Introduction

The XPIC(m) method is an advanced damping method that filters out unwanted noise (in the null space) without damping out useful information. Its drawback is that it adds calculation time as m in XPIC(m) increases. In some simulations, it may not be necessary to use XPIC(m) update methods on every time step. This custom tasks lets you convert such simulations to use XPIC(m) periodically instead of on every time step. Note that both the XPIC(m) method and this custom tasks are only available in OSParticulas.

Using XPIC(m) For Particle Velocities

The first step is to select default update method. Normally, the default method would be a standard FLIP method selected by using Damping commands and setting (fractionPIC) to 1. Next, you schedule this task and use it to select an XPIC order (the m in XPIC(m)) and frequency to run the XPIC(m) calculations. In scripted files, a PeriodicXPIC custom task is scheduled with

CustomTask PeriodicXPIC
Parameter XPICOrder,(order)
Parameter fractionPIC,(fractionPIC)
Parameter periodicSteps,(stepInterval)
Parameter periodicTime,(timeInterval)
Parameter periodicCFL,(CFLfactor)
Parameter verbose,{verbose}

In XML files, this task is scheduled using a <Schedule> element, which must be within the single <CustomTasks> block:

<Schedule name='PeriodicXPIC'>
   <Parameter name='XPICOrder'>(order)</Parameter>
   <Parameter name='fractionPIC'>(fractionPIC)</Parameter>
   <Parameter name='periodicSteps'>(stepInterval)</Parameter>
   <Parameter name='periodicTime'>(timeInterval)</Parameter>
   <Parameter name='periodicCFL'>(CFLfactor)</Parameter>
   <Parameter name='verbose'>(verbose)</Parameter>
</Schedule>

where the parameters are:

  • (XPICOrder) and (fractionPIC) - Enter XPIC order (the m in XPIC(m)) and fraction XPIC(m) (0 to 1) to use when doing periodic XPIC(m) calculations. See Damping Options for details on these settings. The defaults are(XPICOrder)=5 with (fractionPIC)=1.
  • (stepInterval), (timeInterval), and (CFLfactor) - sets the frequency for running periodic XPIC(m) calculations for mechanics. The (stepInterval) option sets number of time steps between each XPIC(m) calculation, (timeInterval) sets frequency in alt time units, and (CFLfactor) sets frequency relative to the basic time step for the momentum equation. If (stepInterval) is used, it is used and the other two are ignored. If (stepInterval) is not used, the time step is found from the (CFLfactor) (if provided) or from (timeInterval). One of these three parameters is required to enable periodic XPIC calculations.
  • (verbose) - If a non-zero integer, a comment line is printed in the output file every time XPIC(m) calculations are done. The default is 0.

Using XPIC(m) For Transport Properties

You can also use XPIC(m) for temperature (when doing conduction calculations) or for concentration (when doing diffusion calculations). XPIC(m) seems to provide significant improvement of transport modeling and can eliminate oscillations sometimes seen for temperature or concentration for particles within one cell.

To use XPIC(m) for transport equations, select order and fracture PIC (using parameters in previous section) and then select periodicity of XPIC(m) for conduction and/or diffusion with following task parameters:

Parameter periodicStepsConduction,(stepInterval)
Parameter periodicTimeConduction,(timeInterval)
Parameter periodicCFLConduction,(CFLfactor)
Parameter periodicStepsDiffusion,(stepInterval)
Parameter periodicTimeDiffusion,(timeInterval)
Parameter periodicCFLDiffusion,(CFLfactor)

In XML files, this new parameter options within the <CustomTasks> block are

<Parameter name='periodicStepsConduction'>(stepInterval)</Parameter>
<Parameter name='periodicTimeConduction'>(timeInterval)</Parameter>
<Parameter name='periodicCFLConduction'>(CFLfactor)</Parameter>
<Parameter name='periodicStepsDiffusion'>(stepInterval)</Parameter>
<Parameter name='periodicTimeDiffusion'>(timeInterval)</Parameter>
<Parameter name='periodicCFLDiffusion'>(CFLfactor)</Parameter>

The meanings of values (stepInterval), (timeInterval) and (CFLfactor)<//tt> are given in the previous section.

When using XPIC(m) for transport equations, you should never pick m=1 because it causes too much numerical diffusion. Any higher order works, unless it XPIC(m) filtering is done too frequently. Because transport time step is usually much longer then mechanics time step, it is usually best to pick transport XPIC(m) frequency using the CFL parameter options.