Hello Andrea,

Currently im working on a project using muqarnas as element to aggregate. As you can see it needs a very high iteration number. Then I saw this PREV input that i wonder if it would help my work to become more smooth? Can u show me an example where u set up the PREV? Does it save the old parts somehow? What does it do?

Best,

Henrik

Hi Henrik,

the PREV input is there to allow you to add a previous aggregation as a base on top of which to aggregate new modules. However, as these modules are still computed in the aggregation process, using it will not make your code faster.

Currently, the best way to achieve aggregations made of large groups is to split the aggregation in smaller sub-areas with small overlaps, and aggregate them independently, always providing the last parts as starting points for the next aggregation. I can send you a file, if you are interested.

In the new version of Wasp (will release it hopefully this weekend) there is the possibility of setting a threshold on the Field component, which allows, depending on your field, to speed up calculations, of couse sacrificing the precision of the field approximation.
If you want to take a look, you can download the work in progess components on the Github page: https://github.com/ar0551/Wasp/tree/master/userObjects

I am working on a "probabilistic" field aggregation, which should be much faster, but I am not sure of when I will have something usable. If you send me a PM with your email, I can keep you in the loop and let you know as soon as I have something.

Hi Andrea,How do I control the starting point of growth in aggregation process ?

Hi Ali,

you can use the TransformPart component to position one part in a specific location, and then provide this transformed part in the PREV input of the Aggregation components. In this way, the aggregation will start from that position.

I am working at finalizing the last touches to the new version of Wasp, and will add example files also for this.

Hi Andrea,

Thanks for this amazing tool.

I was wonderig if there is a way to make restrictions rules?

Hi Cesar,

thank you!

I am not sure I understand your question. Could you exaplin me what do you mean by restriction rules?

With a small field sometimes geometry faces end up touching without a rule and I was wondering if there's a way of restricting this combinations.

Hi Cesar,

not sure if I understand, but if I do, it is not possible with the current version of Wasp, as each part is aware of the connection it is attached to, but not of the other ones. And to keep track of that, would add a quite significant computational load to the aggregation process.

But, just to make sure I understand, could you maybe post a screenshot of the problem here, or create a topic in the discussion forum above, so we can discuss how such feature could be implemented?

Thanks!

Hi Andrea,

I was hoping you could help me develop my Aggregation script.

there's a couple of things i want it to do, but am struggling to do so.

1) Origin point of aggregation 

2) Hierarchy in connections

3) Vertical aggregation over Horizontal 

4) Change points in Field Aggregation

Hope to hear from you soon,

kind regards,

Bi

Hi Bi,

for the origin point of the aggregation you can use a TransformPart component to place one part in the position where you want the aggregation to start, and then feed that part in the PREV input of the Aggregation component.

For your other questions, I am not 100% sure I understand what you mean. Would be best if you would create a new post in the discussion forum above, and post some images/files explaining your problems.

Hello!

I wonder if you can please help me with the following issue:

I use the wasp 'part to geo' component and the output I get is multipale mesh faces,
[Mesh: (V:44 F:30)]

but I want that every face of a cube will be single mesh so I could work with the boundary curves.

Thank you,
Anna.

Hi Anna,

if you want to replace the aggregated geometry with the orginal BRep, you can deconstruct the part, get the TR output (which contains the transformation matrix applied to the part), and use a Transform component to place the original geometry instead of the mesh geometry.
You can see how to do that in the example file "0_04_Part_Geometry_Replacement", which you can find here: Github

Hey!

I´m haveing trouble with the installation of wasp. Although I have the python script in the right folder I still doesn´t work. 

I think I´m overlooking something obvious. Can someone help please?

Thank you very much in advance.