Code Package Reference
A code package is not a switch—it is the combination of four things: section table data + material grades + load combination rules + verification clause references. It is entirely data, not hard-coding—so adding a new code is just adding a package, with no changes to the kernel.
This page documents the data sources of the three built-in packages item by item. Where the data comes from must be auditable, otherwise verification results can’t be traced to their basis.
1. GB (China)
Section titled “1. GB (China)”| Item | Content |
|---|---|
| Section tables | GB/T 11263 (hot-rolled H and split T sections), GB/T 706 (hot-rolled section steel), etc. |
| Section count | ~300 |
| Data source | Compiled by us from publicly published standard tables |
| Material grades | Q235 / Q355 / Q390 / Q420, values per GB 50017 |
| Load combinations | Combination rules of GB 50009 / GB 50011 |
Honesty statement: the GB tables were compiled by us, not taken from the standards publisher’s official digital edition. Every entry was cross-checked during data entry, but the current code edition always governs. For calculation reports used in formal deliverables, review the critical sections yourself.
2. AISC (US)
Section titled “2. AISC (US)”| Item | Content |
|---|---|
| Section tables | AISC Manual 16th |
| Data source | Open-source library steelpy (MIT license) |
| Includes | Includes the Zx plastic modulus—needed for plastic design and buckling analysis |
| Verification entries | Section classification, compression, flexure, and shear per AISC 360 |
The reason we chose steelpy rather than compiling our own tables is straightforward: the MIT license allows redistribution with the software, and its tables have been cross-validated by a large number of projects. Compiling 2000+ sections yourself means a single wrong entry is a hidden engineering failure.
3. Eurocode (Europe)
Section titled “3. Eurocode (Europe)”| Item | Content |
|---|---|
| Codes | EN 1992 (concrete) / EN 1993 (steel structures) / EN 1997 (geotechnical) |
| Data source | Open-source library blueprints (MIT license) |
| Section tables | European standard section series (IPE / HEA / HEB / HEM, etc.) |
| Verification entries | Section classification and resistance per EN 1993-1-1 |
4. Custom Code Packages
Section titled “4. Custom Code Packages”Parameterized entry with properties computed automatically—you only supply section dimensions and material parameters; A, Ix, Iy, Wx, Zx and the like are computed by the program, no hand-copying from tables.
This suits two situations: projects using non-standard sections, and regions using JIS / AS / Russian standards that have no built-in package yet.
5. What Happens When You Switch Code Packages
Section titled “5. What Happens When You Switch Code Packages”- The section selector is filtered by the active package—with GB active, only GB sections are listed; HEA sections won’t sneak in
- The unit system follows the package: AISC and Eurocode packages default to
mm-N-s, the GB package defaults tomm-kN-s - Existing models are not auto-converted: when switching packages, the software asks whether to “keep original values” or “convert to the new unit system”—it never decides for you
The cost of getting units wrong is huge—under mm-kN-s, steel density is 7.85e-12; entering 7.85e-9 makes modal frequencies off by a factor of 31.6. This pitfall gets its own page: Units & Quantities.
6. Code Basis in the Calculation Report
Section titled “6. Code Basis in the Calculation Report”The footer of every verification page always prints the code edition it relied on, such as AISC 16th or EN 2005+A1. This is not optional decoration—once a calculation report goes out, anyone reading it knows which edition the check was run against.
When a code is updated, older calculation reports are not retroactively updated to the new basis. Only a re-run verification does that.
7. Data Sources & Licenses Summary
Section titled “7. Data Sources & Licenses Summary”| Code package | Data source | License | Redistributable with the software |
|---|---|---|---|
| GB | Compiled from public standard tables | N/A (self-built data) | Yes, with attribution “compiled from public standards” |
| AISC | steelpy | MIT | Yes, copyright notice must be retained |
| Eurocode | blueprints | MIT | Yes, copyright notice must be retained |
| Custom | User-entered | Belongs to the user | Not applicable |
Kavvo itself is closed-source, but open-source data inside code packages keeps its original license—MIT-licensed data doesn’t become proprietary just because it ships inside closed-source software. The specific copyright notices for third-party data are distributed with the installer.