Hints, tips and FAQ

This page lists general issues. For issues specific to the finite element interfaces, please refer to the Support / F.E. interfaces option on the left hand menu.

The rep file reports that crack front nodes are "closed" but a displaced mesh plot clearly shows the crack is open. Why?

What steps can I take to ensure that my cracked model is "correct"?

How can I visualise the calculated crack growth profiles?

How can I generate a vs N data for a node on the crack front?

How can I create crack growth animations?

How can I ensure that the crack region is loaded in the cracked model when I apply centrifugal load?

What units should I use for my crack growth data?

The boundary supports are missing from the crack region in my cracked model. Why?

My cracked mesh has inside out elements. Why?

Energy release rate values have been processed after the f.e. analysis but there are no stress intensity values. Why?

The evaluation version of Zencrack has limits on the job size. Are there any limits in the full version?

This is probably due to the tolerance value of TOLOPEN. When considering the crack face opening displacements Zencrack has a tolerance value below which a status of "closed" is defined. By default this is 1e-6. The reason that this is done is that sometimes there can be a small amout of noise in "zero" values and small positive values really should mean "closed" (this is more the case for complex crack geometries rather than simple one-sided mode I problems). A warning similar to this appears in the rep file:

 ***WARNING
 There are   86 crack face nodal positions with opening displacement
 between 0 and the tolerance value TOLopen = 1.000000E-06.
 These nodes are treated as being closed. Please check that the value
 of TOLopen is appropriate for this analysis. TOLopen can be reset in the zcr
 file by using:
 *CONTROLS,TOLOPEN=value

Depending upon the units and/or the load level, the default of 1e-6 may not be appropriate. You can change it in two ways:

• locally for the job - by adding a line to the zcr file as indicated in the above warning: *CONTROLS,TOLOPEN=value
• globally for all analyses - by editting the value of TOLOPEN in the file "Zencrack folder"\crack\tol.dat; this file contains defaults for a variety of tolerances.

The consequence of a closed crack front node is that a -ve sign is applied to the G and K values to indicate the closure. In a growth analysis there will be no growth for the node (an exception may be if there is a superposition load system). See page 193 of the v7.4a manual or page 214 of the v7.5 manual for further discussion.

Use the "3dmesh" utility program. This utility program reads the .shp file from a growth analysis and generates a mesh consisting of beam elements to represent the growth profiles. The initial open part of the crack face is also represented. This mesh can be read into a pre-processor to visualise the crack growth.

In Zencrack version 7 this utility is executed using "runzcr7x 3dmesh". Refer to section 16.1 of the User Manual for more information.

For v7.3 and later:

Use the "process" utility program. This utility program allows generation of csv file for results data at one or more crack front nodes. This can be used to generate a variety of plats including a vs N.

This utility is executed using "runzcr7x process". Refer to section 16.2 of the User Manual for more information.

For v7.2 and earlier:

Use the "growth" utility program. This utility program allows generation of a vs N data (for one or more nodes) by reading the .rep file (from one or more crack growth analyses). The output is an ASCII file containing the growth vs cycles data. An additional debug file is also generated containing, for example, SIF values at the node(s) through the growth. This allows creation of K vs a plots.

The "da" data generated by this program is obtained by summing the differences in nodal coordinates of a node from one crack profile to the next. Due to the shifting and re-distribution of nodes along a crack front during crack growth this may produce misleading results for nodes on the "interior" of a crack front. It is recommended that this utility is only used for surface node positions (and "deepest" node positions in symmetry models).

In Zencrack version 7.0-7.2 this utility is executed using "runzcr7x growth". Refer to section 16.2 of the User Manual for more information.

Animation options in post-processors are geared towards producing animations from results in a single f.e. results file. In this case we need to produce an animation by taking one snapshot from each of several results files.

• Firstly you need to save f.e. results files from each f.e. analysis of a crack growth run. This can be done using keyword SAVE and requesting the appropriate output file e.g. ODB=YES, T16=YES, DB=YES.
• Run the growth analysis.
• Load each of the result files into your post-processor in turn. For each one set the same viewpoint, scale factors etc. and save a screen image e.g. "print" to a .tiff or .gif file. The options for this depend upon the post-processor you are using.
• Use an animation package (such as Animation Shop from JASC) to import the sequence of still images and create an animation file from them.

For the Abaqus interface you need to define an element set that contains all the elements in the uncracked mesh and apply the load to that element set. When Zencrack generates the cracked mesh the element set is updated to include the new crack-block elements and so the load gets applied to the entire crack region.

For the Ansys interface there is no special requirement.

For the MSC.Marc interface you need to apply load type 100 to an element set that will exist in the cracked mesh. Zencrack always creates a set called CBLOCKS containing all the elements in the crack-blocks, so this set can be used.

Zencrack does not have any knowledge about the consistent units that are used for the finite element analysis. Therefore it is the user's responsibility to ensure that the crack growth data is in units that are consistent with the f.e. data. For example, if the f.e. model is defined with millimetre coordinates and MPa stress units, the crack growth data should be in terms of:

stress intensities : MPa mm^0.5
da/dn : mm per cycle

The greatest scope for error lies in conversion of the Paris and Walker constant, C, if those growth models are being used.

A unit conversion utility is supplied with the program documentation and is also available here.

In Zencrack there are special requirements for the way that boundary conditions are specified on the elements that are replaced by crack-blocks. These requirements are stated for different finite element interfaces in sub-sections of section 7 of the user manual. Check that your uncracked mesh satisfies these requirements.

If it is the initial cracked mesh:

• the initial crack may be too distorted e.g. large or small edge ratios or one large and one small edge ratio
• the uncracked element(s) may be too distorted
• you may have requested one stage mapping on the MAPPING keyword - usually two stage mapping (the default) is more reliable
• consider using the BOUNDARY SHIFT option to get a smaller or larger crack into the model.

If it is a cracked mesh part way into a growth analysis:

• it is likely that the crack has grown past the acceptable size limit in the crack-block; this typically occurs when the crack has grown 75%+ of the way into the crack-block.
• consider using the BOUNDARY SHIFT option to get more growth out of the model.

The Young's modulus and Poisson ratio were not available to Zencrack. Ensure that the *MATERIAL keyword is used.

For version 7.4 and later:

• Maximum number of elements in the cracked mesh = no limit^*
• Maximum number of nodes in the cracked mesh = no limit^*
• Maximum number of crack-blocks allowed in an analysis = 999
• Maximum number of finite element analyses in a crack growth run = 999

* - Subject to available memory and format restrictions - see section 12.1 of the User Manual.

For versions 7.3e and 7.3f:

• Maximum number of elements in the cracked mesh (during generation) = 75000
• Maximum number of nodes in the cracked mesh (during generation) = 375000
• Maximum number of crack-blocks allowed in an analysis = 999
• Maximum number of finite element analyses in a crack growth run = 999

For versions up to and including 7.3d:

• Maximum number of elements in the cracked mesh (during generation) = 50000
• Maximum number of nodes in the cracked mesh (during generation) = 250000
• Maximum number of crack-blocks allowed in an analysis = 999
• Maximum number of finite element analyses in a crack growth run = 999