> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-verification-manual/examples-and-reference/references.md).

# References

List of textbooks, codes, and verification manuals referenced throughout the ENERCALC 3D Verifications Manual.

1. K.J. Bathe, “Finite Element Procedures” Prentice-Hall, Inc., 1996
2. O.C. Zinenkiewicz, “The Finite Element Method”, 3rd ed., McGraw-Hill Book Company (UK) Limited, 1983
3. R.C. Cook & D.S. Malkus & M.E. Plesha, “Concepts and Applications of Finite Element Analysis”, 3rd ed., John Wiley & Sons, Inc., 1989
4. R.H. Macneal & R.L. Harder, “A proposed Standard Set of Problems to Test Finite Element Accuracy”, pp3-20 of “Finite Elements in Analysis and Design”, North-Holland, 1985
5. J.P. Hartog, “Advanced Strength of Materials”, McGraw-Hill Book Company, 1952.
6. R.J. Roark & W\.C. Young, “Formulas for Stress and Strain”, 5th ed., McGraw-Hill Book Company, 1975.
7. W. McGuire & R.H. Gallagher & R.D. Ziemian, “Matrix Structural Analysis”, 2nd ed., John Wiley & Sons, Inc., 2000
8. J.S. Przemieniecki, “Theory of Matrix Structural Analysis”, McGraw-Hill, 1968
9. D. Breyer, “Design of Wood Structures”, 3rd ed, McGraw-Hill, 1993
10. J. MaCormac, “Structural Steel Design LRFD Method”, 2nd ed, HarperCollins College Publishers, 1995
11. A. Tamboli, “Steel Design Handbook LRFD Method”, McGraw-Hill, 1997
12. ACI, “Building Code Requirements for Reinforced Concrete (ACI 318-89) (Revised 1992)”, American Concrete Institute, Detroit, Michigan.
13. K. Leet & D. Bernal, “Reinforced Concrete Design”, 3rd ed, McGraw-Hill Book Company, 1997.
14. A. K. Chopra, “Dynamic of Structures – Theory and Applications to Earthquake Engineering”, 2nd ed, Prentice-Hall, 2001
15. Ansel Ugural, “Stresses in Plates and Shells” 2nd Edition, The GcGraw-Hill Companies, Inc., 1999
16. James G. MacGregor & James K. Wight, “Reinforced Concrete – Mechanics and Design” 4th Edition, Pearson Prentice Hall, 2005
17. “Notes on ACI 318-02 Building Code Requirements for Structural Concrete”, 8th Edition, Portland Cement Association, 2002
18. R. Park and W\.L. Gamble “Reinforced Concrete Slabs”, John Wiley & Sons, 1980
19. ACI, “Building Code Requirements for Structural Concrete (ACI 318-05) and Commentary (ACI 318R-05)”, American Concrete Institute, Detroit, Michigan, 2004
20. Arthur H. Nilson, David Darwin, Charles W. Dolan, “Design of Concrete Structures”, 13th Edition, McGraw-Hill Higher Education, 2004
21. AISC “Steel Construction Manual”, 14th Edition
22. Charles Salmon, John Johnson and Faris Malhas, “Steel Structures” 5th Edition, Pearson Prentice Hall, 2009
23. AISC “Design Examples”, Version 14.1
24. Abaqus Benchmarks Guide, Dassault Systemes, 2013
25. ADINA Verification Manual, ADINA R & D Inc., June 2001


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/e3d-verification-manual/examples-and-reference/references.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.