Simulate with complex geometries and complex physics
COMP_DoOrganizeOnlyAfterHowManyCycles
do the point cloud organization only after how many time cycles (UCV)
Default: COMP_DoOrganizeOnlyAfterHowManyCycles = 1
This feature enables skipping of the point cloud organization. The whole neighborhood relationship is kept. The points, however, are moved as usual with their transport velocity.
Point cloud organization that is skipped (subject to future changes): EVENT (see especially %EVENT_PerformAfterHowManyTimeCycles%), copying STANDBY points to a separate point cloud, DropletSource, MEMORIZE, standard organization of points (adding and removing of points, distance to boundary computation, free surface check, etc.), MONITORPOINTS (if executed at the beginning of the time step), organization of STANDBY point cloud, correction for interphase connections (see PHASE_distinction), PointCloudQualityCheck, preparation of numerics, redistribution of representative masses (see RepresentativeMass_iData)
This feature is especially useful if the point cloud moves only little compared to the local smoothing length. Reasons for this might be (among others):
- small value of COEFF_dt
- large values of surface tension, also here the time step size might drop considerably
- KOP using EULER or EULERIMPL instead of LAGRANGE with non-moving geometries
- Point cloud organization cannot be skipped in the first two time steps.
- This feature is especially helpful if LINEQN_solver and/or LINEQN_solver_ScalarSystems is set to 'SAMG'. As the neighborhood graphs are kept for several time steps, the matrix setup operations do not have to be executed for these time cycles, and so a lot of computation time can be saved.
- This parameter cannot be set chamberwise, i.e. if it is set to a value larger than 1 for a multiphase simulation, the point cloud organization is skipped for all phases.
- This parameter is ignored in time steps in which KOP_transition has transferred points to another chamber.
- Skipping of STANDBY point cloud organization steps is done automatically to ensure compatibility between STANDBY and classical point clouds.
- This parameter is ignored during USER_h_PC_refinement is active in the setup phase. During simulation time, the parameter is active again.
| This item is referenced in: | |
|---|---|
| common_variables | simple box driving through a channel of water: common_variables.dat |
| COMP_DoOrganizeOnlyAfterHowManyCycles | do the point cloud organization only after how many time cycles (CV) |
| COMP_DoOrganizePointsUntil | do the organization only until a certain amount of time steps |
| COMP_DoOrganizeOnlyAfterHowManyCycles | do the point cloud organization only after how many time cycles (UCVO) |
| COMP_DoOrganizeOnlyAfterHowManyCycles | do the point cloud organization only after how many time cycles (UCV) |
| SAMG_Setupreuse | accelerates SAMG solver for quasi-stationary point clouds (UCV) |
| %TOUCH_always% | boundary points always active |
| %TOUCH_always_force% | boundary points always active in a forced way |
| EVENT | events defined for the point cloud |
| %EVENT_PerformAfterHowManyTimeCycles% | cycle of event execution |
| USER_h_PC_refinement | Number of pointcloud refinement steps performed before start |
| Beta | Latest release notes for the MESHFREE beta executables |
| All | Complete release notes for the MESHFREE beta executables |