-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Our customers might have a parametric KCL design -- e.g. a fn wheel(diameter, thickness, numBolts). What specific parameters should they use?
This is usually answered by analysis software. Right now, the engineers would have to:
- Instantiate a specific wheel like
myWheel = wheel(2.1cm, 13mm, 4) - Export it as wheel.step
- Import that into their analysis software
- Record its measurement
- Loop back to step 1, tweaking the measurements
- Repeat until the value in (4) is good enough
This could be automated. Imagine if you could just do:
- Load a KCL file with a parametric function like
zoo kcl export file.kcl --parametric --function=wheel diameter=2mm thickness=3mm numBolts=4 - That opens
file.kcl, calls thewheelfunction with the given parameters and exports it
Then it becomes very simple to write a shell script which makes some starting parameters, repeatedly calls zoo kcl command above with the current parameters, passes the exported file to the analysis software (called via CLI), measures the results, and then tweaks the parameters.
jtran
Metadata
Metadata
Assignees
Labels
No labels