fix fragmentation/bruchmueller/unresolved command
Syntax
fix id group fragmentation/bruchmueller/unresolved keyword value ...
ID, group-ID are documented in fix command
fragmentation/bruchmueller/unresolved = style name of this fix command
keywords = verbose or number_psd_classes or number_fragment_size_classes
verbose value = yes or no or file yes = report on occurrence of fragmentation and resulting changes in the fragment PSD no = suppress output on fragmentation file = write report to separate file number_psd_classes value value = max number of sizes in PSD, thus limits the size of the smallest fragment number_fragment_size_classes value value = number of fragment sizes created upon fragmentation
Examples
fix fragmentation all fragmentation/bruchmueller/unresolved
fix fragmentation all fragmentation/bruchmueller/unresolved verbose on &
number_psd_classes 11 number_fragment_size_classes 6
Description
Fix fragmentation/bruchmueller/unresolved treats particle fragmentation upon collisions in an unresolved manner as described in gran model hertz/fragmentation/bruchmueller.
This fix requires the definition of several material properties:
fix id all property/global breakageE0timesD peratomtype value_1 value_2 ...
(value_i=value for E_impact_0 * particle diameter of atom type i)
fix id all property/global breakageProbabilityParam peratomtype value_1 value_2 ...
(value_i=value for breakage probability parameter of atom type i)
fix id all property/global breakageSizeParam peratomtype value_1 value_2 ...
(value_i=value for breakage size parameter of atom type i)
Upon fragmentation, fragments of different sizes are created. The number of the sizes is controlled by the argument number_fragment_size_classes which must be chosen between one and six.
With verbose file the fragmentation report of each individual processor is
written to a separate file named log_fragmentation.txt.<procNr> or
log_fragmentation.txt if running on a single core.
The report written to the separate file contains slightly more information than
the verbose output – namely the time, id, and original diameter of the fragmented
particle are printed before the collision energy, t10, the resulting PSD, and the
resulting Sauter diameter.
Restart, fix_modify, output, run start/stop, minimize info
All of the quantities used by this fix are written to binary restart files so simulations can continue properly. None of the fix_modify options are relevant to this fix.
No parameter of this fix can be used with the start/stop keywords of the run command.
Restrictions
none
Default
verbose = off, psd_length = 10, n_fragment_sizes = 6