Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressed problem description
If you want to build a Gordon surface (by use of "Surface from NURBS Curves Net" node), it is required that your curves intersect exactly. If your curves are not generated, but manually created (and introduced into Sverchok tree by use of "Bezier In" or "NURBS Input" nodes), it is hard to adjust curves manually so that they would exactly intersect.
Solution description
With this new node, you may say that, for example, U curves are "primary", and the surface should follow them exactly, and V curves are "secondary", they provide only approximate shape. Then the node will slightly adjust your V curves so that they would exactly intersect your U curves. Or vice versa, you can say that V curves are primary.
Initial curves net (note that curves do not intersect exactly):
Here we say that U curves are primary. Black curves are original, red and blue curves are result of adjustment by the node. Note that now the curves intersect exactly.
And here we say that V curves are primary:
Simple example with "Crop" disabled:
And the same with "Crop" enabled:
Preflight checklist
Put an x letter in each brackets when you're done this item: