Point Cloud

the point cloud feature translates data into lattice parameters data driven lattices any data set that can be mapped to xyz coordinates can utilize the point cloud feature the goal is to correlate lattice parameters with the data to create variation across the lattice variation may be desired for multiple reasons performance, adaptivity (conforming to changes in geometry), or even aesthetics one common use case is to use pressure sensor data to define your lattice, utilizing personalized or aggregated data to build your applications as in the example below point cloud workflow video text obtain data set • csv file select strut lattice point cloud • select point cloud as lattice population type upload data as csv file edit mappings • add a row • enter input value • assign lattice parameters reference lattice parameter guidelines • add more rows for multiple input values and parameters generate and review strut lattice solidify generate csv file the data set must be converted to a csv, formatted for design engine alternate file types are not supported at this time ( doc, xlsx, png, etc ) https //archbee doc uploads s3 amazonaws com/3cesil2dymchpzvrjp8s0/z0hmghwisk0qlnm0ypync csv point cloud csv the file must contain four columns the first three columns must represent x, y, z coordinates , in that order the fourth column represents your point cloud data column headers should be labeled as follows without case sensitivity template x, y, z, \<any> example x, y, z, force example x, y, z, value x, y, z coordinates can be both positive or negative numbers decimal values are accepted values must be numerical only extra characters will result in an error input values are unit agnostic it is not necessary to specify the units of input values (n, lbf, etc) if data points are 2 dimensional, use a zero value for the z coordinate after uploading a csv, the file appears in the dropdown list under mappings users can upload multiple csv files all files appear in the dropdown users can only select one csv at a time model location ensure that the input model is in the same world coordinate location as the data set coordinates this can be done in your cad file or with the translate tool within the design engine (as shown here) point mappings enter data from the fourth column of your csv file as the input value and map that value to lattice parameters mapping basics non mapped areas in the design space will take on the parameters of the nearest defined point (blue, yellow and red in this example) enter a minimum of 2 rows for variation across your lattice all values in between will be linearly interpolated (a single row will create a uniform lattice) enter more rows/data points for greater granularity cell size factor of 2 all cell size inputs must be based on a factor of 2 relative to the top row 's cell size all viable options viable options for rows 2 and beyond are listed in a drop down menu options that exceed 25 mm will be grayed out grayed out if the top row value is changed top row value is changed to make another row's selection larger than recommended another row's selection larger than recommended (ie exceeds 25 mm), the lattice will generate, but it is recommended to review the results for production viability z coordinate if data points are 2 dimensional, use a zero value for the z coordinate multiple z coordinates can be used if data is 3 dimensional, or if different lattice parameters are desired in the z axis this example places points at z zero and points at z 16 (mm) the z zero points have lower input values than the points just below the design space surface in this example the resulting lattice uses thicker struts for the z zero points to give the lattice a stiffer base point cloud details point cloud visibility and details can be accessed in the sidebar standard menu options are available hover over points to see input value