a6286293d8
Run black on IOS-Python
2024-07-26 12:00:57 +10:00
07060fc769
Replace all ifcopenshell.api.run with ifcopenshell.api static functions.
2024-06-28 12:36:31 +10:00
4a5d1eba0b
specify exported api methods in __all__
...
It's py.types requirement, similar to 6e2edbf
2024-06-03 17:44:05 +05:00
c05abc4d5b
ifc4x3 support for adding IfcQuantityCount #4776
...
In IFC4X3 IfcQuantityCount is now more strict and requires only interger values.
Error for a reference:
TypeError: attribute 'CountValue' for entity 'IFC4X3.IfcQuantityCount' is expecting value of type 'INT', got 'float'.
2024-05-31 18:20:46 +05:00
dacb3b101c
small docs fix
2024-05-31 18:20:46 +05:00
073e471305
typing
2024-05-23 18:45:30 +05:00
f2eb08a066
typing
2024-05-22 17:43:05 +05:00
382e028b90
csv to cost schedule - support more cases of 0 quantity #4704
...
Before - https://i.imgur.com/CYwSGxY.png
After - https://i.imgur.com/Wbe6Ij6.png
I'll attach example .csv and .ifc in #4704
What changed:
1) If query was provided but it didn't found any elements, then it will still autoassign quantity = 0 instead of cost item end up without quantities at all (which has a different meaning in ifc). Works both with Property provided and without it.
2) If provided quantity = 0, it will now load as quantity = 0 instead of not creating any quantities at all.
3) You can provide both Query and Quantity and they all will be added to the cost item. E.g. if Quantity = 15, Query = "IfcWall", Property="Prop" and there are 3 walls in the model each having Prop = 25 then final quantity will be 15+25*3=90. Previously Quantity would take the priority and the result would be just = 15.
Though this is still doesn't work with counting quantities due behaviour in cost.assign_cost_item_quantity.
E.g. if Quantity = 7, Query = "IfcWall", Property="" (to make sure it will just count them) and there are 3 walls in the model then final quantity will be not 7+3=10 but just = 3, as query will take the priority here.
2024-05-22 17:15:42 +05:00
bb8e84e5ec
typing
2024-05-15 17:18:33 +05:00
8ffb77551f
more tests for ifc2x3
2024-05-09 18:15:49 +05:00
2d35869c41
typing
2024-05-09 18:00:17 +05:00
cbf04546b8
fix many implicit ifcopenshell.guid imports
...
a bit related to 10d30b0de
2024-05-08 18:18:02 +05:00
10d30b0de7
Document api modules and require explicit imports of API submodules
2024-05-08 17:00:35 +10:00
d11ec67129
Generate functions for all API usecases for better static code features. See #2693 .
2024-05-06 14:43:43 +10:00
a213ab6760
Fix docstrings to reference datatype as it would be used for users
2024-05-06 08:39:48 +10:00
06b84cfa24
nest.unassign_object - support batching #4474
2024-04-09 18:33:25 +05:00
97db95085a
nest.assign_object - support batching #4474
2024-04-09 18:33:25 +05:00
d1bcec7a6a
typing
2024-04-09 18:33:25 +05:00
7b46c6a443
black format
2024-04-09 17:05:36 +05:00
8df40dc4a6
Fix #4203 . Fix bug where removing nested cost items left orphaned relationships.
2024-01-12 18:14:49 +11:00
b260bd3877
Record formula and resource name for cost values when calculating resource cost
2024-01-04 09:32:31 +01:00
cd6246c382
fix cost value calculation when using parent cost
2024-01-04 09:30:27 +01:00
46454c5c94
consider unit basis for calculating resource costs #4122
2023-12-20 14:19:16 +01:00
6e932ec2fb
Fix #3974 . Bug where orphaned histories would be left in API remove operations.
2023-11-28 10:46:03 +11:00
635dff73b4
fix typo
2023-09-26 16:35:31 +01:00
e74e824417
Proposal to use resource's parent cost, reducing manual insertions
2023-09-23 16:04:01 +01:00
438f35fe88
purge cost schedules
2023-09-18 20:20:23 +01:00
7dd20f69d7
ligten up add cost schedule UI
2023-08-21 01:13:17 +01:00
31a12faef1
woopsies
2023-08-13 12:18:48 +01:00
eb94c16465
fix the bug fix #07b5c49 - where counting objects controlled by a cost item stopped working
2023-08-13 12:16:29 +01:00
07b5c4918b
fix api logic where only quantities of the same type can be assignmed to a cost control
2023-08-12 15:17:32 +01:00
703f0a6b70
fix orphaned data when unassigning element quantities from cost item control
2023-08-12 14:57:01 +01:00
0c946fae36
fix removing cost item value
2023-06-02 00:31:50 +01:00
a4a6dce6de
BBIM D: Copy cost items, export Cost Schedules individually, start improving Cost Schedule UI
2023-05-21 12:42:50 +01:00
6c82e6f889
Fix assign cost value usecase
2023-02-10 21:28:49 +01:00
b3c7971ea9
Purge all data classes from API.
2023-02-01 15:44:08 +11:00
c8ba96cde8
Make syntax highlighting explicit in docs
2023-01-10 10:16:28 +11:00
11f772b5a3
Add documentation for cost module
2022-11-21 12:05:58 +09:00
f0a00cbc94
#2185 Set up auto generated API reference documentation via sphinx-autoapi
2022-05-09 15:35:52 +10:00
810c71dfa2
IfcOpenShell-python licensing and black. See #1082 .
2022-01-19 12:18:33 +11:00
c726e8feb9
You can now calculate costs from direct resources and indirect task-based resources
2021-08-28 18:21:22 +10:00
b272210a97
Resource base costs are now supported with all the features coming from the cost module.
2021-08-27 17:12:21 +10:00
b99c5036e6
You can now edit nested arithmetic cost values by using spreadsheet-like formulas
2021-08-27 14:45:14 +10:00
5e1fbacef7
Cost values are now serialised and shown as formulas
2021-08-26 21:37:25 +10:00
00f779fc49
You can now count elements, tasks, and resources parametrically for cost items
2021-08-26 15:48:04 +10:00
a6b8e40829
Cost subtotals that are calculated from per X units are now supported
2021-08-18 18:05:01 +10:00
912699e63c
You can now assign rates from a schedule of rates to a cost plan
2021-08-17 12:22:57 +10:00
f2aec9440f
UoM and unit rates are now shown for schedule of rates in costing
2021-08-17 09:44:43 +10:00
6ee0027f33
Import of CSV-based schedule of rates is now possible
2021-08-16 15:07:09 +10:00
2a6d6cfdbf
You can now edit the unit basis of a cost value for a schedule of rates
2021-08-13 11:56:33 +10:00
Dion Moult
