pycba-tools 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- pycba_tools-0.1.0/LICENSE +201 -0
- pycba_tools-0.1.0/PKG-INFO +266 -0
- pycba_tools-0.1.0/README.md +251 -0
- pycba_tools-0.1.0/pyproject.toml +34 -0
- pycba_tools-0.1.0/src/pycba_tools/__init__.py +41 -0
- pycba_tools-0.1.0/src/pycba_tools/combos.py +31 -0
- pycba_tools-0.1.0/src/pycba_tools/envelope.py +86 -0
- pycba_tools-0.1.0/src/pycba_tools/model.py +806 -0
- pycba_tools-0.1.0/src/pycba_tools/reports.py +699 -0
- pycba_tools-0.1.0/src/pycba_tools/serialize.py +176 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: pycba-tools
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: pycba-tools: Serialization and bulk results extraction for pycba continuous beam models, interchangeable with pynite-tools.
|
|
5
|
+
Author-email: Connor Ferster <connor@structuralpython.com>
|
|
6
|
+
Requires-Python: >=3.11
|
|
7
|
+
Description-Content-Type: text/markdown
|
|
8
|
+
License-File: LICENSE
|
|
9
|
+
Requires-Dist: numpy>=2.0.2
|
|
10
|
+
Requires-Dist: pycba>=1.0.2
|
|
11
|
+
Requires-Dist: pydantic>=2.12.0
|
|
12
|
+
Requires-Dist: deepmerge>=2.0
|
|
13
|
+
Project-URL: Source, https://github.com/StructuralPython/pycba-tools
|
|
14
|
+
|
|
15
|
+
# pycba-tools
|
|
16
|
+
|
|
17
|
+
> Super-charge your pycba workflows (and swap them with Pynite)
|
|
18
|
+
|
|
19
|
+
[pycba](https://github.com/ccaprani/pycba) is a fast, accurate continuous beam analysis library.
|
|
20
|
+
The tools in this package give pycba the model-level features that
|
|
21
|
+
[pynite-tools](https://github.com/StructuralPython/pynite-tools) gives PyniteFEA: named load
|
|
22
|
+
cases and load combinations, JSON serialization of analysis-ready models, and bulk export of
|
|
23
|
+
structured results.
|
|
24
|
+
|
|
25
|
+
The public API mirrors pynite-tools: the same function names, the same signatures, and **the same
|
|
26
|
+
result trees, with the same names and sign conventions**. Code written against pynite-tools can
|
|
27
|
+
switch to pycba-tools for continuous beams by changing the import.
|
|
28
|
+
|
|
29
|
+
Modules included:
|
|
30
|
+
|
|
31
|
+
- `model`: `CBAModel`, a pycba beam with named load cases, load combinations and named nodes,
|
|
32
|
+
and Pynite-shaped result views (`model.nodes`, `model.members`)
|
|
33
|
+
- `reports`: Quickly export node and member results in structured dictionaries
|
|
34
|
+
- `serialize`: Export and import `CBAModel` objects to JSON
|
|
35
|
+
- `combos`: Convenience function for bulk-adding load combinations to `CBAModel` objects
|
|
36
|
+
|
|
37
|
+
## Installation
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
pip install pycba-tools
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
## Dependencies
|
|
44
|
+
|
|
45
|
+
- Python >= 3.11
|
|
46
|
+
- `pycba` >= 1.0.2
|
|
47
|
+
- `numpy` >= 2.0.0
|
|
48
|
+
- `deepmerge` >= 2.0.0
|
|
49
|
+
- `pydantic` >= 2.0.0
|
|
50
|
+
|
|
51
|
+
## Examples: `model`
|
|
52
|
+
|
|
53
|
+
pycba's `BeamAnalysis` analyses a single load matrix. `CBAModel` holds the beam definition, any
|
|
54
|
+
number of named load cases (stored as ordinary pycba load matrix rows) and load combinations,
|
|
55
|
+
and analyses every combination.
|
|
56
|
+
|
|
57
|
+
```python
|
|
58
|
+
import pycba_tools as pt
|
|
59
|
+
|
|
60
|
+
model = pt.CBAModel(
|
|
61
|
+
L=[4.0, 6.0, 2.5], # span lengths
|
|
62
|
+
EI=30e3, # one value, or one per span
|
|
63
|
+
supports=["pin", "roller", "roller", "free"], # or a raw pycba R vector
|
|
64
|
+
name="B1", # member name used in result trees
|
|
65
|
+
# node_names=["N0", "N1", "N2", "N3"], # default
|
|
66
|
+
# node_locations=[0.0, 4.0, 10.0, 12.5], # optional, instead of L
|
|
67
|
+
# eletype=["FF", "FF", "FF"], D=[...], GAv=..., kf=... # all pycba options
|
|
68
|
+
)
|
|
69
|
+
|
|
70
|
+
# Loads use pycba's convention: positive is downward, moments positive counter-clockwise.
|
|
71
|
+
# Global-coordinate helpers split loads at the nodes into pycba load matrix rows...
|
|
72
|
+
model.add_distributed_load(5.0, 5.0, case="D") # full length
|
|
73
|
+
model.add_distributed_load(2.0, 6.0, 2.0, 9.0, case="L") # trapezoidal, x1 to x2
|
|
74
|
+
model.add_point_load(10.0, 7.0, case="D")
|
|
75
|
+
model.add_moment_load(3.0, 7.0, case="D")
|
|
76
|
+
# ...or add raw pycba rows (1-based span number)
|
|
77
|
+
model.add_load([3, 2, 6.0, 2.5], case="L")
|
|
78
|
+
|
|
79
|
+
model.add_load_combo("1.25D+1.5L", {"D": 1.25, "L": 1.5})
|
|
80
|
+
model.add_load_combo("D+L", {"D": 1.0, "L": 1.0})
|
|
81
|
+
|
|
82
|
+
model.analyze()
|
|
83
|
+
|
|
84
|
+
# Pynite-style results...
|
|
85
|
+
model.nodes["N1"].RxnFY["1.25D+1.5L"]
|
|
86
|
+
model.members["B1"].max_moment("Mz", "D+L")
|
|
87
|
+
|
|
88
|
+
# ...and the pycba BeamAnalysis of every combination, for pycba's own tools
|
|
89
|
+
model.analyses["D+L"].plot_results()
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Existing pycba objects convert both ways:
|
|
93
|
+
|
|
94
|
+
```python
|
|
95
|
+
from pycba import BeamAnalysis
|
|
96
|
+
|
|
97
|
+
ba = BeamAnalysis([5.0, 5.0], 30e3, supports=["fixed", "roller", "roller"], LM=[[1, 1, 2.0]])
|
|
98
|
+
model = pt.CBAModel.from_beam_analysis(ba, case="D") # the load matrix becomes case "D"
|
|
99
|
+
combo_ba = model.to_beam_analysis(combo_name="1.25D+1.5L") # a fresh BeamAnalysis
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
### Sign conventions
|
|
103
|
+
|
|
104
|
+
Inputs use pycba's conventions. The result views and every `reports` function use Pynite's
|
|
105
|
+
conventions for a member along global X loaded in Y, so result trees can be swapped:
|
|
106
|
+
|
|
107
|
+
| Pynite name | pycba | Relationship |
|
|
108
|
+
|---------------|------------------|--------------------------|
|
|
109
|
+
| `RxnFY` | vertical reaction | same sign (up positive) |
|
|
110
|
+
| `RxnMZ` | moment reaction | same sign (CCW positive) |
|
|
111
|
+
| `DY`, `RZ` | nodal displacement, rotation | same sign |
|
|
112
|
+
| `Fy` (shear) | `V` | same sign |
|
|
113
|
+
| `Mz` (moment) | `M` | `Mz = -M` |
|
|
114
|
+
| `dy` | `D` | same sign |
|
|
115
|
+
|
|
116
|
+
A Pynite `Fy` load of `-w` (downward) is a pycba load of `+w`. pycba is a planar beam solver, so
|
|
117
|
+
the axial, torsional and out-of-plane results are always zero and are dropped from result trees
|
|
118
|
+
exactly as pynite-tools drops all-zero results.
|
|
119
|
+
|
|
120
|
+
## Examples: `reports`
|
|
121
|
+
|
|
122
|
+
```python
|
|
123
|
+
import pycba_tools as pr
|
|
124
|
+
|
|
125
|
+
model = pr.CBAModel(...) # Build and analyze your model here
|
|
126
|
+
|
|
127
|
+
# All the below functions optionally take a list of load combos
|
|
128
|
+
# and a results_key, exactly as in pynite-tools.
|
|
129
|
+
|
|
130
|
+
reactions = pr.extract_node_reactions(model)
|
|
131
|
+
node_displacements = pr.extract_node_displacements(model)
|
|
132
|
+
force_arrays = pr.extract_member_arrays(model, n_points=1000)
|
|
133
|
+
forces_minmax = pr.extract_member_envelopes(model)
|
|
134
|
+
forces_minmax_spans = pr.extract_span_envelopes(model)
|
|
135
|
+
forces_at_locations = pr.extract_member_actions_by_location(
|
|
136
|
+
model,
|
|
137
|
+
force_extraction_locations={"B1": [0, 2.0, 3.6]},
|
|
138
|
+
)
|
|
139
|
+
forces_at_location_ratios = pr.extract_member_actions_by_location(
|
|
140
|
+
model,
|
|
141
|
+
force_extraction_ratios={"B1": [0.25, 0.5, 0.75]},
|
|
142
|
+
by_span=True,
|
|
143
|
+
)
|
|
144
|
+
merged_tree = pr.merge_result_trees([force_arrays, forces_minmax, forces_at_locations])
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
pycba results are evaluated at `npts` stations per span (default 500, set on `CBAModel` or
|
|
148
|
+
`analyze(npts=...)`) and interpolated between them; stations are added either side of every
|
|
149
|
+
concentrated load so shear and moment jumps are captured.
|
|
150
|
+
|
|
151
|
+
## Examples: `serialize`
|
|
152
|
+
|
|
153
|
+
```python
|
|
154
|
+
import pycba_tools as ps
|
|
155
|
+
|
|
156
|
+
## Dumping/serializing functions
|
|
157
|
+
with open('model.json', 'w') as file:
|
|
158
|
+
ps.dump(model, file)
|
|
159
|
+
json_str = ps.dumps(model)
|
|
160
|
+
json_dict = ps.dump_dict(model)
|
|
161
|
+
ps.to_json(model, "model.json")
|
|
162
|
+
|
|
163
|
+
## Loading/de-serializing functions
|
|
164
|
+
with open('model.json', 'r') as file:
|
|
165
|
+
remodel = ps.load(file)
|
|
166
|
+
remodel = ps.loads(json_str)
|
|
167
|
+
remodel = ps.load_dict(json_dict)
|
|
168
|
+
remodel = ps.from_json("model.json")
|
|
169
|
+
|
|
170
|
+
remodel.analyze()
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
A pycba `BeamAnalysis` can also be passed to the dump functions; its load matrix is stored as load
|
|
174
|
+
case `"Case 1"`.
|
|
175
|
+
|
|
176
|
+
### What gets serialized
|
|
177
|
+
|
|
178
|
+
The JSON contains the model's *input* data: the member name, node names and locations, spans,
|
|
179
|
+
`EI`, the restraint vector `R` (supports and springs), element types, prescribed displacements,
|
|
180
|
+
`GAv` and `kf`, the number of evaluation points, load cases (as pycba load matrix rows) and load
|
|
181
|
+
combinations. It is tagged `"backend": "pycba"`.
|
|
182
|
+
|
|
183
|
+
Analysis results are not serialized: re-run the analysis after loading. Non-prismatic
|
|
184
|
+
(`SectionEI`) members are not supported yet.
|
|
185
|
+
|
|
186
|
+
## Examples: `combos`
|
|
187
|
+
|
|
188
|
+
```python
|
|
189
|
+
import json
|
|
190
|
+
import pycba_tools as pc
|
|
191
|
+
|
|
192
|
+
with open("load_combo_library/current_combos.json", 'r') as file:
|
|
193
|
+
load_combos = json.load(file)
|
|
194
|
+
|
|
195
|
+
pc.model_add_combos(load_combos, model) # in place
|
|
196
|
+
model = pc.model_add_combos(load_combos, model, as_copy=True) # on a copy
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
## Using pycba-tools in place of Pynite in loadtracer
|
|
200
|
+
|
|
201
|
+
loadtracer's frame model only needs a model it can build, analyse, read support reactions from
|
|
202
|
+
and serialize. `CBAModel` provides `load_combos`, `analyze_linear()` and nodes with `X` and
|
|
203
|
+
`RxnFX`...`RxnMZ`, so loadtracer's `get_support_reactions` works unchanged, and `pycba_tools`
|
|
204
|
+
provides the `dump`/`dump_dict`/`load`/`load_dict`/`from_json` functions that `PyniteFrame` calls.
|
|
205
|
+
The only new code is the model builder:
|
|
206
|
+
|
|
207
|
+
```python
|
|
208
|
+
import pycba_tools as pt
|
|
209
|
+
|
|
210
|
+
def build_pycba_frame_model(pm: dict, EI: float = 1.0) -> pt.CBAModel:
|
|
211
|
+
nodes = get_node_locations(pm) # loadtracer's helper
|
|
212
|
+
R = []
|
|
213
|
+
for _, constraints in nodes:
|
|
214
|
+
constraints = constraints or [0] * 6
|
|
215
|
+
R.extend([-1 if constraints[1] else 0, -1 if constraints[5] else 0])
|
|
216
|
+
model = pt.CBAModel(
|
|
217
|
+
node_locations=[location for location, _ in nodes],
|
|
218
|
+
EI=EI,
|
|
219
|
+
R=R,
|
|
220
|
+
name=pm["element_attributes"]["tag"],
|
|
221
|
+
)
|
|
222
|
+
load_cases = set()
|
|
223
|
+
for dist_load in pm["loads"]["distributed_loads"]:
|
|
224
|
+
for e in dist_load.get("expanded", []):
|
|
225
|
+
if e["dir"] not in ("Fy", "FY"):
|
|
226
|
+
raise ValueError(f"pycba cannot model distributed loads in '{e['dir']}'.")
|
|
227
|
+
load_cases.add(e["case"])
|
|
228
|
+
# loadtracer uses Pynite's sign convention: negate transverse loads
|
|
229
|
+
model.add_distributed_load(
|
|
230
|
+
-e["start_magnitude"], -e["end_magnitude"], e["start_loc"], e["end_loc"], case=e["case"]
|
|
231
|
+
)
|
|
232
|
+
for point_load in pm["loads"]["point_loads"]:
|
|
233
|
+
for e in point_load.get("expanded", []):
|
|
234
|
+
load_cases.add(e["case"])
|
|
235
|
+
if e["dir"] in ("Fy", "FY"):
|
|
236
|
+
model.add_point_load(-e["magnitude"], e["location"], case=e["case"])
|
|
237
|
+
elif e["dir"] in ("Mz", "MZ"):
|
|
238
|
+
model.add_moment_load(e["magnitude"], e["location"], case=e["case"])
|
|
239
|
+
else:
|
|
240
|
+
raise ValueError(f"pycba cannot model point loads in '{e['dir']}'.")
|
|
241
|
+
for load_case in sorted(load_cases):
|
|
242
|
+
model.add_load_combo(name=load_case, factors={load_case: 1.0})
|
|
243
|
+
return model
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
`tests/test_loadtracer_contract.py` runs loadtracer's own `get_support_reactions` against this
|
|
247
|
+
builder and against loadtracer's Pynite builder and checks they agree.
|
|
248
|
+
|
|
249
|
+
pycba models in-plane bending only: gravity (`Fy`/`FY`) loads and `Mz` moments. In-plane
|
|
250
|
+
(`Fx`) and out-of-plane (`Fz`) loads on beams are rejected rather than silently dropped.
|
|
251
|
+
|
|
252
|
+
## Testing
|
|
253
|
+
|
|
254
|
+
```
|
|
255
|
+
uv sync
|
|
256
|
+
uv run pytest
|
|
257
|
+
```
|
|
258
|
+
|
|
259
|
+
The test suite includes parity tests that analyse the same beams with PyniteFEA + pynite-tools and
|
|
260
|
+
with pycba + pycba-tools and compare the result trees.
|
|
261
|
+
|
|
262
|
+
## License
|
|
263
|
+
|
|
264
|
+
pycba-tools is licensed under the Apache License 2.0. Note that it depends on pycba, which is
|
|
265
|
+
licensed under the AGPL-3.0-or-later.
|
|
266
|
+
|