We need to make a CAD model of ESTARs that can accurately be grown to a 48" diameter tube.

@Anishka99 let's see if we can write a nice LFOM hole pattern feature. Here are three permutations of the feature. Start with the first (the simplest), and work up to the most complex (but also the most versatile!)

1. Given a direction and a number of rows, pattern a hole (either a face pattern or a feature pattern) in that direction. To do this, just use a linear pattern written in featurescript.
2. Take in an array that specifies the number of holes on each "row". Now each row of the linear pattern should be patterned to have the number of holes specified in a circular pattern around the pipe.
3. Offset the rows such that each row up is 'nestled' between the holes of the row below.
4. Take in a hole diameter and spacing to the feature.

We need a function that takes the current design and performs a deep copy. This means copying all subassemblies. Can be done by exporting as an f3z, than importing as an f3z. See this video for an example.

We need to ensure that we are making drawings as well as models so that the designs auto document. This is really a job for aide_document.

We need something other than dp that will let us control features/components in greater detail. For instance, we need to be able to suppress features as in the LFOM, and we need to be able to do this dynamically. Now I don't want to manage all the little pieces of code required if we had a bunch of independent methods for handling different features. Instead, I want to expose a window from the aide_design yaml directly to the fusion api.

The first MVP will accomplish three things:

• Create a YAML file based on parameters in an assembly - this will hunt through all the sub-assemblies and pull out every single parameter and turn it into a nested YAML file.
• Sync that YAML file with the model - this only goes one way - bringing the model up to date such that you could have changed the parameters on the YAML, and the model will change correspondingly.
• The YAML needs to support referencing other parameters and simple mathematics.

The plant will rely on geometric relationships defined in templates. This means that keeping careful track of which templates are used for which AIDE version is critical. These templates need to be able to be packaged up and shipped along with the rest of the AIDE plugin. Some questions are:

• How do normal plugins ship template drawings?
• Does Fusion have a standard method for this? Maybe ask on some community forum if you can't find the answer online.

Afterwards, it might be useful to try creating such a plugin - perhaps just one that modifies the dimensions of a square that is defined in a template. This plugin seems to be highly relevant and a great place to start

This morning I spent about 2.5 hours to figure out whether or not we could use OnShape as another CAD system. It has a number of benefits - it is 100% cloud based, supports by default configurations, etc... The goal is to have an onshape system that can do exactly the same thing as aide_draw for Fusion. I explored with this repo. To do this, I think I'll need to make the following REST calls: Assembly: Assembly definition to figure out what instances are there and get the configuration strings example:

{
  "rootAssembly" : {
    "documentId" : "8ec353ba00f37f447b5a61f5",
    "documentMicroversion" : "e948bc1ade7c5ab16ae07f95",
    "elementId" : "1a1dbfb527f96cc00c05e2ed",
    "occurrences" : [ {
      "path" : [ "MLER6gjKXbnv2zVXS" ],
      "transform" : [ 1.0, 0.0, 0.0, -0.06718311458826065, 0.0, 1.0, 0.0, 0.0, 0.0, 0.0, 1.0, -0.6096, 0.0, 0.0, 0.0, 1.0 ],
      "fixed" : false,
      "hidden" : false
    } ],
    "instances" : [ {
      "id" : "MLER6gjKXbnv2zVXS",
      "name" : "Part 1 <1>",
      "partId" : "JHD",
      "isStandardContent" : false,
      "configuration" : "height=1.2192+meter;poo=true",
      "type" : "Part",
      "suppressed" : false,
      "documentId" : "8ec353ba00f37f447b5a61f5",
      "documentMicroversion" : "e948bc1ade7c5ab16ae07f95",
      "elementId" : "2918f0f5adfa39d3047f19d0"
    } ]
  },
  "subAssemblies" : [ ],
  "parts" : [ {
    "documentId" : "8ec353ba00f37f447b5a61f5",
    "documentMicroversion" : "e948bc1ade7c5ab16ae07f95",
    "elementId" : "2918f0f5adfa39d3047f19d0",
    "partId" : "JHD",
    "bodyType" : "solid",
    "configuration" : "height=1.2192+meter;poo=true",
    "isStandardContent" : false
  } ],
  "partStudioFeatures" : [ ]
}

Now I can insert another partstudio with whatever configuration I want with a call to "create assembly instance":

{
  "documentId": "8ec353ba00f37f447b5a61f5",
  "elementId": "2918f0f5adfa39d3047f19d0",
  "versionId": "",
  "microversionId": "",
  "isAssembly": false,
  "isWholePartStudio": true,
  "partId": "",
  "featureId": "",
  "configuration": "height=1+meter;poo=true"
}

Decode/Encode configuration String seem to be handy. To upload the new configuration to the assembly, we'll need to copy the elementID of the part, and then update the config...