Hello-
I get some weird results after increasing the number of rows or columns in a primitive, after I've used an edit node on that primitive. I think this is because the edit node is still just operating on the smaller number of rows or columns. So the new rows are columns are left unedited. There must be a way to get the editor to operate on the new rows or columns? If so, I'm having trouble finding it.

-Scott

The Edit sop simply stores change in point positions and uses the point indices to know which points to apply the differences to. If you change the number of incoming points, the Edit sop will apply the modifications to the “wrong” points.
If you have a small number of edits to apply, you might consider a more procedural approach where you define groups dynamically, and then have individual sops perform the edits using those groups. Something like the Transform sop, or SoftTransform.
If you have something more complex, then the other option would be to use your modified mesh as a deformer. The PointDeform sop, for example, will take the difference between a modified mesh and its rest mesh and apply that to a separate geometry.

Thanks. In the case of a simple edit, I may just delete the edit and apply a new edit. It's nice to know I had the right idea, though. -Scott