Current

Needs

• Enhancements to address product feedback and limitations 
• Prototyping
  • Stop Gaps that interact with Rhino GUI
  • STL Checks
  • Organization
  • Repeatability 
• QA
• Change Database to metric (mm)

Goals

• organize
• readability and maintainability 
  • for current team
  • coders
  • scaling of team
  • Able to read and write
• Code Quality 
  • QA to Launch
  • Peer review
  • Automated tests
• More incorporated structure to change code based on feedback and learnings 

Design

• Rhino

  • hierarchical  System: 

    • Split into grid, points

    • Auto build surface solid

    • Config files for features

    • Modular testing to validate each stage

  • Enhanced Exception handling to reduce manual intervention

  • Enhanced Automated tests to validate inputs and outputs 

Plan

Gen princ:

Reuse as much code as possible

Test as much as possible 

Usability assurance with Team

• redefine poorly designed geometry based on feedback and learnings 
• Create Base SOLS 
• Expand to independent features
• Combine features
• Prototype new features
• Akanksha SOLS and drinks