Simulation and Style Design of Bridge Stability Supported on Large Diameter Piles
Bibliographic record
Abstract
In this paper, two types of bridges were taken to carry out the analysis and design according to the AASHTO Code and the SAP2000 program, in the beginning, work is done using AASHTO Code and both bridges are designed and analyzed, the first one was the suspension bridge and the second was a bridge supported in the pier region only. The two models, 16 piles with a diameter of 3.8 m were carried out on each pier. After that, the two models are analyzed and designed according to the SAP2000 program to calculate moment, shear and deflection for both bridges. So that the two models are compared based on torque, shear, impact loads and deflection to find out which one of the two models is more suitable for use in a long girder span. The comparison between the AASHTO Code and the SAP2000 program is also made based on the loading to show its effect on the stability design. The AASHTO code and the SAP2000 program are the most appropriate when analyzing and designing for two models. There is a slight difference in moment where the proportions were approximately (6-9)%. As for shear for both methods, the values for the suspension bridge were greater than those of the supported bridge. The difference was about (27-26)%.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.006 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".