fstwn / cockatoo Goto Github PK

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_MakeGephiGraph.py#L4

implement second pass 'warp' connection routine where all nodes with fewer than four connections are revisited.

Create a dual-graph from the final network topology for deriving a pixel-pattern

https://github.com/fstwn/Cockatoo/blob/a007d5dd55fc3d6acda139e13c99695f2136bc62/src/COCKATOO_ExtractKnitMeshConstraintsFromMesh.py#L1

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_RelaxMeshIntoPlane.py#L2

https://github.com/fstwn/COCKATOO/blob/3a44fcce1f447395eb0137db76d7dda690d6e942/modules/Cockatoo/KnitMappingNetwork.py#L504
option to include 'end' nodes between segment contours in a chain and inject them into the creation routine for 'warp' edges.

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/modules/Cockatoo/KnitNetwork.py#L2041

https://github.com/fstwn/COCKATOO/blob/3a44fcce1f447395eb0137db76d7dda690d6e942/modules/Cockatoo/KnitMappingNetwork.py#L279
Enhance the routine with the forbidden vertices concept from KnitNetwork class to avoid crossing 'warp' edges.

Hello
I tried PipelineController but didn't work , can you please make a simple version to only detect changes when geometries added or removed without other settings like layers , colors ...etc

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_CreateFinalNetworkTopology.py#L5

https://github.com/fstwn/Cockatoo/blob/a007d5dd55fc3d6acda139e13c99695f2136bc62/src/COCKATOO_KnitContoursOnMesh.py#L1

Ensure that the final weft and especially warp edges are always connected with a consistent directionality

https://github.com/fstwn/Cockatoo/blob/a007d5dd55fc3d6acda139e13c99695f2136bc62/src/COCKATOO_RenderKnitMeshNetwork.py#L1

don't create weft and warp edges inside the mappingnetwork. instead really use it only for mapping and work on copies of the knitnetwork.
this could make the use of multigraph obsolete for KnitMappingNetwork

Review all classes and methods and define a consistent wording to avoid confusion.
A thing should only have one particular name.

Routine seems to be updated since Rhino 7. Component needs to sanitize inputs to avoid turning red and displaying intimidating error messages.

remove crossing edges by better window computation or forbidden node implemetation

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_BuildMappingNetwork.py#L5

make a component which uses iso curves as contours

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_BuildAutoknitModel.py#L1

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_BuildAutoknitConstraintFromPoints.py#L1

https://github.com/fstwn/Cockatoo/blob/a007d5dd55fc3d6acda139e13c99695f2136bc62/src/COCKATOO_ExtractKnitMeshConstraintsFromMesh.py#L1

I am getting an error where the icons don't appear, see attached. What have I installed incorrectly?

https://github.com/fstwn/Cockatoo/blob/03e31791966463e423354cdd4481c6849746b21a/usrobj_src/COCKATOO_RenderKnitContours.py#L2

https://github.com/fstwn/Cockatoo/blob/a007d5dd55fc3d6acda139e13c99695f2136bc62/src/COCKATOO_CreateWeftConnections.py#L1

Handling tubular meshes in constraint and network creation should not be too much of a problem:

• A tubular mesh has exactly two closed loops made up of naked edges
• A tubular mesh has no self intersections, no valence 3 edges

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_RenderKnitNetwork.py#L3

Horrible connection failures have been observed on a tubular test mesh.

• Behaviour seems to occur when creating final warp connections.
• Behaviour has been observed with ContinuousEnd setting but is not necessarily related.

it should be noted that on a nurbs surface of the same geometry the problem does not occur.

A relation to the difference in generation of KnitContours is possible.

KnitContours could be generated using the heat method. I started experimentation on this and the first results seem nice! For the next release there probably will be both versions available.

create standardized test scenarios to test implementation changes

Creation of weft edges called from IWAWE can be optimised a lot:

• If first all connections between contours with equal number of points are made, all these can be processed in parallel.
• See Popescu: KnitCrete p. 100 (see sources)

https://github.com/fstwn/Cockatoo/blob/03e31791966463e423354cdd4481c6849746b21a/usrobj_src/COCKATOO_RenderKnitContours.py#L2

https://github.com/fstwn/Cockatoo/blob/bf7231fb51acd3972619c3d98b736709a1c50425/usrobj_src/COCKATOO_MakeRenderGraph.py#L4

Implement an attribute that prevents calling certain methods on the network at the wrong time...?
Is there an alternative how this can be handled?

https://github.com/fstwn/COCKATOO/blob/3a44fcce1f447395eb0137db76d7dda690d6e942/modules/Cockatoo/KnitMappingNetwork.py#L504
Routine does not handle all cases. There are missing connections especially in 'leaf' node areas.
New approach: Try chaining in source and target chains.

include_leaves is not useful as an option. instead something like force_cast_on and force_cast_off should be implemented.
force_cast_on > connects all nodes at pos index 1 to one another (like a second row of leaf nodes at the start)
force_cast_off > connects all nodes at pos index -2 to one another (like a second row of leaf nodes at the end)

https://github.com/fstwn/COCKATOO/blob/3a44fcce1f447395eb0137db76d7dda690d6e942/modules/Cockatoo/KnitMappingNetwork.py#L504
Store all connection data as a mapping between segment chains and use this for the second pass loop.