rebar2
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
rebar2
A few times I stated the FreeCAD rebar base code should be improved. IMHO the rebar class should be split in two classes:
- the rebar shape marked by a mark number
- the disribution of this rebar shape in the model
- may be more than one distribution
- means in tree view there will be two objects too. The distributions are childs of the marked rebar shape
- for the user it should be possible to create those two separate, thus separate class
- There are use cases where this is not needed, like most existing FreeCAD rebar tools and the rebar add-ond from GSoC. They should automaticly create these both objects with one tool instead of one object ATM. The idea is to let this happen inside the current module. Means the existing add ons does not need to be changed. But this needs to be disscussed.
- see readme in the repository
- ATM it is a standard FreeCAD AddOn. Thus it is easy to give it a try.
- https://github.com/berndhahnebach/rebar2
- since I am lazy I wrote a importer which creates the above objects for reinforcement ifc exported from Allplan.
- four ifc attached in the code
- Furthermore code to copy to create the objects by Python and code to import the example files:
https://github.com/berndhahnebach/rebar ... t_rebar.py
Bernd
EDIT:
Still two objects but they where renamed here https://forum.freecadweb.org/viewtopic. ... 10#p384310
- base rebar is the base reinforcement bar (rebar=reinforcement bar) object.
- reinforcement will be made from a base rebar and places the base rebars to make some path reinforcement.
- the rebar shape marked by a mark number
- the disribution of this rebar shape in the model
- may be more than one distribution
- means in tree view there will be two objects too. The distributions are childs of the marked rebar shape
- for the user it should be possible to create those two separate, thus separate class
- There are use cases where this is not needed, like most existing FreeCAD rebar tools and the rebar add-ond from GSoC. They should automaticly create these both objects with one tool instead of one object ATM. The idea is to let this happen inside the current module. Means the existing add ons does not need to be changed. But this needs to be disscussed.
- see readme in the repository
- ATM it is a standard FreeCAD AddOn. Thus it is easy to give it a try.
- https://github.com/berndhahnebach/rebar2
- since I am lazy I wrote a importer which creates the above objects for reinforcement ifc exported from Allplan.
- four ifc attached in the code
- Furthermore code to copy to create the objects by Python and code to import the example files:
https://github.com/berndhahnebach/rebar ... t_rebar.py
Bernd
EDIT:
Still two objects but they where renamed here https://forum.freecadweb.org/viewtopic. ... 10#p384310
- base rebar is the base reinforcement bar (rebar=reinforcement bar) object.
- reinforcement will be made from a base rebar and places the base rebars to make some path reinforcement.
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: rebar2
Great work @berndbernd wrote: ↑Thu Apr 02, 2020 9:02 pm A few times I stated the FreeCAD rebar base code should be improved. IMHO the rebar class should be split in two classes:
- the rebar shape marked by a mark number
- the disribution of this rebar shape in the model
- may be more than one distribution
- means in tree view there will be two objects too. The distributions are childs of the marked rebar shape
- for the user it should be possible to create those two separate, thus separate class
- There are use cases where this is not needed, like most existing FreeCAD rebar tools and the rebar add-ond from GSoC. They should automaticly create these both objects with one tool instead of one object ATM. The idea is to let this happen inside the current module. Means the existing add ons does not need to be changed. But this needs to be disscussed.
- see readme in the repository
- ATM it is a standard FreeCAD AddOn. Thus it is easy to give it a try.
- https://github.com/berndhahnebach/rebar2
- since I am lazy I wrote a importer which creates the above objects for reinforcement ifc exported from Allplan.
- four ifc attached in the code
- Furthermore code to copy to create the objects by Python and code to import the example files:
https://github.com/berndhahnebach/rebar ... t_rebar.py
Bernd
I will start its integration into Rebar Addon after modifying BOM function as stated here. And getting confirmation from you.
Thanks,
Re: rebar2
My idea is not to integrate this into Rebar Addon but to integrate this into FreeCAD rebar implementation at all !!!
Would be coold if you could give it a try to get an idea what I mean in the regard of the two objects, one for rebar shape and one for the rebar distribution.
bernd
Would be coold if you could give it a try to get an idea what I mean in the regard of the two objects, one for rebar shape and one for the rebar distribution.
bernd
Re: rebar2
fixed import of the cran foundation rebar ifc into rebar2 ... All ifc reinforcement files exported with Allplan should work with rebar2 ifc reinforcement import.
Re: rebar2
Amazing!
Re: rebar2
It now really works the way I would like to have it working. One rebar base shape could have multiple distributions. See TreeView in the screen!
Re: rebar2
improved examples. These examples are included ... They use lattice2 placements to create the rebar distribution. See TreeView.
Re: rebar2
As a start it would be cool if your BOM would be able to use the rebar objects created with rebar2 as well. Than it would not matter how the rebar is created, either with FreeCAD rebar tools and FreeCAD rebar AddOn or with rebar2 tools. BTW you do not neet to use the rebar base shape object. You need to use the Rebar Distribution object.Suraj Dadral wrote: ↑Fri Apr 03, 2020 8:52 am I will start its integration into Rebar Addon after modifying BOM function as stated
I will continue to think about integration of rebar2 in FreeCAD Arch and FreeCAD Rebar module.