This is a planning session: create a plan and put it inside \plans\SOP2SVG.md
Ask user input if anything is unclear or multiple options exist
You are developing an existing TouchDesigner export node called SOPtoSVG that upon a button press will execute python code to take incoming data from a SOP Trace operator and export a SVG via the SVGwrite Library.
Workflow of SOP2SVG
User sets the dimension of the paper, these settings are used to calculate the screen pixel dimensions for the rest of the TouchDesigner sketch. User creates a shape inside RayTk, a raymarching library that runs inside of touchDesigner. The current method of edge detection is to use the Normals output from Raytk and output an edge. But Raytk has many render select output options including Worldpos, Depth map, normals and SDF
The output from ‘Normals Pass Edge Detect’ goes to a Trace SOP afterwards it goes into SOPtoSVG
When the user presses ‘Save SVG’ some python scripts executes, converts the data and saves a svg via the SVGwrite library.
The exported files are massive
Please review the code listed below and the screenshot of what the workflow of the SOPtoSVG tool looks like in use, View the sample Exported SVG and look at the bugs below, research all associated and mentioned technologies and create a plan to address these issues.
path to exported SVG: N:\Dropbox\Library\Curioid Library\Curioid 0116 - Noise Sphere cellular\SVG\0116 Noise Sphere.svg
Technologies: Python, SVGWrite, RayTK, TouchDesigner