> 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/sel-user-manual/calculation-modules/general/asce-seismic-wall-anchorage.md).

# ASCE 7-10/16 Seismic Wall Anchorage

How to design wall out-of-plane and anchorage forces for seismic loads per ASCE 7-10 and 7-16.

This module is an implementation of the provisions for design and anchorage of walls to resist seismic forces as per ASCE 7. The module currently supports calculations based on ASCE 7-10 and ASCE 7-16. Input parameters are taken directly from the nomenclature presented in ASCE 7.

The calculation produces:

* Out-of-Plane Force for Structural Wall Design
* Out-of-Plane Wall Anchorage Force

The module is configured to allow the definition of up to 20 different wall conditions. The user has the option to decide which (if any) of the calculations will be included in a Project Print.

![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-de213cf7f4b70fa3c50debdbeb1a9659dc10d23d%2Fclip0414_was_BMP.jpg?alt=media)


---

# 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/sel-user-manual/calculation-modules/general/asce-seismic-wall-anchorage.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.