Simulation of Test Arch Based on Concrete Damage Plasticity Model and Damage Evolution Analysis

Abstract

In light of the limited research on latent damages during the construction of large-span suspension arches, this study introduced a method to simulate structural damage utilizing random porosity. Initially, based on data from real-world engineering projects, the most susceptible areas within the arch structure were pinpointed. Subsequently, multiple test arch simulation models were constructed. Employing Python, commands for random porosity were implemented within ABAQUS and distinct mesh modules were devised to depict structures under varying degrees of damage. The current investigation delved into the structural responses of these susceptible areas under different damage rates, shedding light on damage progression patterns. Notably, our findings demonstrated that concealed damages on the top plate of the arch foot profoundly influenced structural integrity, whereas damages at the arch hance were comparatively minimal and predominantly manifest at the arch base. The pronounced localized damage at both the arch base and hance initiated and intensified at sectional corners, necessitating enhanced anti-crack measures in these regions. Moreover, depending on the stresses of the arch structure, diverse reinforcement strategies could be employed, optimizing the balance between load-bearing efficiency and cost considerations.

Flexural Performance of a Continuous Circular Tube Girder Bridge

“…The fb0-fc0 is the ratio of initial equibiaxial compressive yield stress to The filled concrete was modeled with C3D10, a three-dimensional solid element, using an elastic modulus of 30,000 MPa and a Poisson's ratio of 0.2 [23][24][25][26]. The concrete was modeled using a nonlinear model considering a concrete damaged plasticity model provided by ABAQUS [20,[27][28][29]. In the concrete damage plasticity model, the dilation angle was 31, flow potential eccentricity was 0.1, fb0/fc0 was 1.16, K c was 0.67, and the viscosity parameter was 0.…”