Peano

Searching...

No Matches

Extension of the explicit Euler to support dynamic search radius adoption. More...

Inheritance diagram for swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius:

[legend]

Collaboration diagram for swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius:

[legend]

Public Member Functions
	__init__ (self, name, cfl_factor, initial_time_step_size, particle_particle_interaction_over_particle_sets_kernel="", touch_particles_of_set_first_time_kernel="", touch_particles_of_set_last_time_kernel="", number_of_interaction_partners=64, particles_per_cell=0, min_h=0.005, max_h=0.3)
	Initialise the particle.

	algorithm_steps (self)
	The explicit Euler basically consists of two steps per particle.

	initialisation_steps (self)
	No particular initialisation required.

Public Member Functions inherited from swift2.particle.Particle.Particle
	readme_descriptor (self)
	Create default readme descriptor.

Public Member Functions inherited from peano4.datamodel.DaStGen2.DaStGen2
	configure (self, namespace, association, subdirectory="")
	Configure output.

	additional_load_and_store_arguments (self)

	additional_load_and_store_arguments (self, new_arguments)

	hosts_smart_pointer_attribute (self)
	Does class host a smart pointer attribute.

Public Member Functions inherited from peano4.datamodel.DoF.DoF
	get_full_qualified_type (self)

	get_logical_type_name (self)
	What should the data type be called within the data repository, or within action sets.

	get_enumeration_type (self)
	What should the data type be called within the data repository.

	additional_load_and_store_arguments_for_other_dof (self, argument_name, use_dof_association=None)
	You can make Peano's store and load arguments of any DoF depend on other DoFs that you have loaded before.

	subnamespace (self)

Data Fields
	velocity

	accelerator

	cfl_factor

	initial_time_step_size

	particle_particle_interaction_over_particle_sets_kernel

	touch_particles_of_set_first_time_kernel

	touch_particles_of_set_last_time_kernel

	number_of_interaction_partners

Data Fields inherited from swift2.particle.Particle.Particle
	particles_per_cell

	min_h

	max_h

	name

Data Fields inherited from peano4.toolbox.particles.Particle.Particle
	name

	partid

Data Fields inherited from peano4.datamodel.DaStGen2.DaStGen2
	generator

	data

	peano4_mpi_and_storage_aspect

Data Fields inherited from peano4.datamodel.DoF.DoF
	association

	name

	namespace

	subdirectory

Additional Inherited Members
Static Public Attributes inherited from swift2.particle.Particle.Particle
str	DependencyChecks_Attribute_Prefix = "dependencyChecks"

list	DependencyChecks_Ifdefs = ["PeanoDebug > 0"]

Static Public Attributes inherited from peano4.datamodel.DaStGen2.DaStGen2
str	readme_package_descriptor

Protected Member Functions inherited from swift2.particle.Particle.Particle
	_dependency_checks_modify_steps (self, steplist, step_type_name, peano4_event_enum)
	Add dependency checks as well as mesh consistency checks to the algorithm steps.

	_add_dependency_checks (self)
	Add dependency (particle consistency) checks.

Protected Attributes inherited from swift2.particle.Particle.Particle
	_algorithm_steps

	_initialisation_steps

Protected Attributes inherited from peano4.datamodel.DaStGen2.DaStGen2
	_additional_load_and_store_arguments

Protected Attributes inherited from peano4.datamodel.DoF.DoF
	_additional_load_and_store_arguments

Detailed Description

Extension of the explicit Euler to support dynamic search radius adoption.

Attributes

Parameters

name	String To be in line with other conventions, I recommend you start with an uppercase letter. This has to be a valid C++ identifier, i.e. don't use any special symbols besides an underscore.

See also: swift2::kernels::adoptSearchRadiusAndTriggerRerun()

Definition at line 11 of file ExplicitEulerDynamicSearchRadius.py.

Constructor & Destructor Documentation

◆ init()

swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius.__init__	(	self,
		name,
		particles_per_cell,
		min_h,
		max_h = "",
		touch_particles_of_set_first_time_kernel = "",
		touch_particles_of_set_last_time_kernel = "",
		number_of_interaction_partners = 64,
		particles_per_cell = 0,
		min_h = 0.005,
		max_h = 0.3 )

Initialise the particle.

This is the baseclass for a particle, i.e. we only add the absolute minimum of information to a particle. As we inherit from the toolbox particle, we already have some attributes defined. These are the guys which are not explicitly visible from the code snippet below, i.e. they are introduced by the superclass constructor.

Here's an overview of pre-defined attributes that each and every particle hosts:

A position which is a double vector with Dimension entries.
A search radius which describes the range with which other particles a particle might theoretically interact. The effective interaction might be smaller if a code decides to ignore potential interaction partners, i.e. this is an absolute maximum. The search radius will decide on which resolution level within the tree a particle is held.
A MoveState flag. This flag is essential. We use it later to label those particles that have been moved to avoid that we move particles multiple times.
A flag that indicates if a particle has been updated within a cell. Consult our code release papers: In short, a particle does not uniquely belong to one cell but can belong to many cells. We nevertheless want to update them only once.

See also: swift2.actionsets.UpdateParticleMarker

Reimplemented from swift2.particle.Particle.Particle.

Definition at line 28 of file ExplicitEulerDynamicSearchRadius.py.

References swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius.__init__().

Referenced by swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius.__init__().

Here is the call graph for this function:

Here is the caller graph for this function:

Member Function Documentation

◆ algorithm_steps()

swift2.particle.ExplicitEulerDynamicSearchRadius.ExplicitEulerDynamicSearchRadius.algorithm_steps ( self )

The explicit Euler basically consists of two steps per particle.

We first determine the force. For this, we need access to the neighbours. The step solely alters the individual particle's state. In the next algorithm step, we need this state, as well as global data (the admissible time step size) to update position and velocity. We also determine the CFL condition here.

Reimplemented from swift2.particle.Particle.Particle.

Definition at line 69 of file ExplicitEulerDynamicSearchRadius.py.