Skip to content

Commit 2a38c83

Browse files
committed
fix documentation and sqa errors
1 parent 4e5cd57 commit 2a38c83

2 files changed

Lines changed: 1 addition & 2 deletions

File tree

modules/solid_mechanics/doc/content/source/actions/DomainIntegralAction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,6 @@ Details on the theory behind the computation of the various fracture integrals a
3333

3434
### Output with `crack_front_points_provider`
3535

36-
The [!param](crack_front_points_provider) parameter references a UserObject that defines a set of surface points at the edge of a cutting plane used by the XFEM module to define the crack. One of its primary purposes is to define the discrete locations where fracture integrals are computed when XFEM is used to define the crack. In XFEM, a crack can be described purely by geometric primitives or by a lower-dimensional mesh. When [!param](crack_front_points_provider) is specified, the `DomainInegral` action can create output at the crack front points, which are not at node locations. By default (`output_vpp=true`), the vectorpostprocessors will always be created and will be dynamically sized as the number of crack front points changes throughout the simulation. The Postprocessor and AuxKernel output will only be created if [!param](number_points_from_provider) is specified.
36+
The [!param](/DomainIntegral/DomainIntegralAction/crack_front_points_provider) parameter references a UserObject that defines a set of surface points at the edge of a cutting plane used by the XFEM module to define the crack. One of its primary purposes is to define the discrete locations where fracture integrals are computed when XFEM is used to define the crack. In XFEM, a crack can be described purely by geometric primitives or by a lower-dimensional mesh. When [!param](/DomainIntegral/DomainIntegralAction/crack_front_points_provider) is specified, the `DomainIntegral` action can create output at the crack front points, which are not at node locations. By default (`output_vpp=true`), the vectorpostprocessors will always be created and will be dynamically sized as the number of crack front points changes throughout the simulation. The Postprocessor and AuxKernel output will only be created if [!param](/DomainIntegral/DomainIntegralAction/number_points_from_provider) is specified.
3737

3838
!syntax parameters /DomainIntegral/DomainIntegralAction

modules/xfem/test/tests/solid_mechanics_basic/tests

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,6 @@
114114
[]
115115
[num_points_error]
116116
type = RunException
117-
issues = '#32418'
118117
input = 'edge_crack_3d_domain.i edge_crack_3d_mhs.i'
119118
cli_args = 'DomainIntegral/number_points_from_provider=3'
120119
expect_err = 'This must match the number of points provided by the XFEM mesh cutter object.'

0 commit comments

Comments
 (0)