design.js

var DESIGN = {
  panelNumber: 3, // how many panels total
  overallWidth: 198, // inches
  overallHeight: 72, // inches
  panelWidth: 42, // inches, 33 for zinc
  panelHeight: 138, // inches
  crop: false, // stretch
  gridSize: 2, // inches, [0.1 - 2.0]
  gridType: "staggered", // [staggered, square]
  perfShape: "circle", // [circle, diamond, square, hexagon]
  reductionType: "none", // [none, linear, random, radial]
  reductionPercent: 10,
  panelMaterial: "starBlueCopper", // [
  structureMaterial: "painted", // [painted, anodized, raw]
  city: "Chicago", // for distance calc
  system: "angleAnchor", // [singleScreen, doubleScreen, angleAnchor, pieAnchor, ceiling]
  mullionWidth: 1, // inches
  mullionDepth: 2, // inches
  anchorDepth: 3, // inches
  distance: 509, // miles, distance to KC
  
  // Used on for javascript app to render or calculate
  // system needed
  windDesignLoad: 100,
  minPerf: 0.20, // inches
  maxPerf: 0.80, // inches
  invert: false,
  reductionAngle: 5,
  searchBitmap: "",
  uploadBitmap: "",
  perfBitmap: "imagewall.imgix.com/map.jpg",
  environment: "outdoor", // [outdoor, indoor]
  application: "wall", // [wall, facade, screen, ceiling]
  panelsOnly: false,
  panelColor: "#000000",
  structureColor: "#000000",
}

gridType, perfShape, reductionType, system
I thought the result of our discussion today was that these would have string values? Either way, I need to know what strings/numbers are for each.
materialColor: "#333333", // Hex??
Sounds good to me!
lattitude: "39.1034774", longitude: "-94.5645158,15", // Lat Long??
Cool, though do we need this in addition to the locationInput?
substrate: "concrete",
Shouldn't need this.
depth: "3" // inches
Number instead of string?
finish: "painted", finishColor: "black"
What are these for? Structure? If I'm not missing something, shouldn't we have something like panelMaterial, panelColor, structureMaterial (aluminum - bare, painted, anodized), and structureColor?

Also,

• What happens to info that is calculated from the base inputs? Are you planning to just calculate that every time? I think that's ok, though it might be handy not to have to recalculate some of these if we have just the json. In particular:
  • Do you want an application field in addition to system? So, for example, application: wall, system: fins? Or does system mean application and the structural system is always calculated and not stored?
  • The other outputs of the system selection code are mullion width, mullion height, and anchor depth. The cost spreadsheet will also need these.
  • Also wind design load, panel width, and panel height - calculated by the app, needed for the cost spreadsheet, and might be useful to have stored (The spreadsheet could calculate panel width and height, and even structural system, though I'd prefer to have the numbers for maximum panel size, and especially the logic for structural system selection, in just one place to prevent confusion.)
• We do need to add a 'number of sides' (sides?) input for the screen application.

It's a minor thing, but can we make all length units inches? (So, overall width and height would be stored in inches.) Only if it doesn't blow things up.

One more, can you add # of panels?

Also I think mullionHeight might get confusing. Maybe mullionDepth?