You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose to integrate the definition of web regions into the FUSED-Wind parametrization. The parameters would serve as input for a cross section structure 2D mesher (not for shellexpander, but any other mesher) as well as for a 3D mesher.
Considering the input data files we would add the web DPs to the *.dp3d file extending it by relative positions between the two web's DPs (i.e.: 0.0 0.25 0.75 1.0). Between two webXXDPXX's we would have a webXXregionXX:
Further, additional *_webXXregionXX.st3d files are required to set the material and the thicknesses at the positions along span. The existing *_webXX.st3d files would be optional in case the webXXregionXX strings in the *.dp3d file are not present.
Any other suggestions?
Should this extension still go into version 2?
The text was updated successfully, but these errors were encountered:
Is this meant to address topologies where the webs are not at the edges of the caps or what is the use of it? simply adding a narrow pair of regions and attaching the webs to these would make this topology, so I guess your suggested change addresses another use?
I propose to integrate the definition of web regions into the FUSED-Wind parametrization. The parameters would serve as input for a cross section structure 2D mesher (not for shellexpander, but any other mesher) as well as for a 3D mesher.
Considering the input data files we would add the web DPs to the
*.dp3d
file extending it by relative positions between the two web's DPs (i.e.: 0.0 0.25 0.75 1.0). Between two webXXDPXX's we would have a webXXregionXX:Further, additional
*_webXXregionXX.st3d
files are required to set the material and the thicknesses at the positions along span. The existing*_webXX.st3d
files would be optional in case the webXXregionXX strings in the*.dp3d
file are not present.Any other suggestions?
Should this extension still go into version 2?
The text was updated successfully, but these errors were encountered: