So I’ve been poking around trying to find all the simulation packages. I’ve got a virtual machine burning a hole in my pocket. Should’ve sprung for more ram. Let’s fill it with garbage.

How is a compilation ever successful. It seems beyond belief.

gmsh

code_aster – solid mechanics solving

moose – Sandia National Lab

Cubic

elmer

salome

openfoam- fluid mechanics stuff

A very interesting alternative is simscale, which now integrates with onshape. Simscale is sort of a web based wrapper for some opensource (I think code_aster, openfoam, and salome at least) stuff, but I am a big fan of convenience. Writing up the files and compiling this code is not entirely trivial.

So you pick your model from onshape or from an external file, mesh it with some mesh generator. AutomaticTetrahedral is from salome. SnappyHexMesh is from openfoam.

Then you need to set the simulation type and boundary conditions for faces. You need to hold some fixed, place loads on others.

Then you run. To visualize the solution you place filters. The Warp filter is a good one for bending. It warps the model in the direction of the displacement. It might be recommended while this part is in beta to download the paraview file and use paraview.

Coming back in I think monads make more sense? The pattern is for taking out boiler plate pass along data into a single location. For instance the Maybe monad takes the constant checking for if variables exist out into a single function instead of checking every single time you’re passing something that may throw an error.

For example (btw I can’t really confirm this is actually a monad since I’m groping in the dark here) a common pattern in javascript is to pass in two arguments to a callback function, the error and the actual data. And then every time you make a callback function you need to check if there is an error and if the data is non null before you do your real work. I’ve had a ton of server crashing from this because the database may not toss a null or error for a long time and I don’t notice I forgot. One could easily convert a callback function that doesn’t check for errors into one by passing it into and errorize function.

function errorize(cb){
return function(err,x){
if x != null && err == null
cb(x)
}
}

Now, this doesn’t really quite fit the monad paradigm, since cb should somehow return the combo (err, result) allowing for chaining, which we could do with an object for example, but that isn’t how the err is traditionally wired.

Some more interesting stuff. Haskell is confusing (Maybe intrinsically but mostly because of unfamiliarity) but check out these. Comforting familiar python, like mother’s bosom.

The pitch point is the point of contact between two gears that lies between their centers.

The pitch diameter is how far that point will be from the center of the gear. This tells you how far apart to mount the two gears

The diametral pitch is the number of teeth divided by the pitch diameter. What horrible terminology. It must have units of inverse inches typically. P * D = N

The circular pitch p is the distance between the same point on each tooth .

At the height of the pitch circle there is just as much tooth as tooth gap.

pressure angle is the angle between tooth profile and diameter at the pitch point.

If two gears have the same diametral pitch and pressure angle (and appropriate tooth profiles) they’ll mesh.

For a rack, the teeth are straight lines with the pressure angle with respect to the normal.

For full cut teeth

the outer diameter is Pitch Diameter + 2/P =

the root diameter is Pitch Diameter – 2/P =

For a rack, it’s much easier to work with p

Top of tooth is 1/P = p /

the root diameter is Pitch Diameter – 1/P =

Onshape instructions:

So make sketch. Draw the root circle, pitch circle, and outer diameter circle.

Now we need to find the base circle, the circle from which the involute is unrolled. Make a radial line. Make a perpendicular to that line touching the pitch circle. Make another radial line at the pressure angle from the first. Make a line at the pressure angle from the pitch perpendicular you drew. These two lines should intersect at 90 degrees. That point lies on the base circle. Make a circle that touches that point.

Now the involute. I decided to go with a spline. Write down the radius of the base circle. Make a radial and a perpendicular to that radial and tangent to the base circle.

Make the same thing a couple of times at intervals of 10 degrees or something. Now, set the length of each of the perpendiculars to the arc length away from the first point, i.e. 10*pi/90 * B, 20*pi/90 * B, 30*pi/90 * B, … where B is the diameter of the Base circle. Now draw a spline connecting the ends of all these lines. This is a good involute. You can stop when the involute crosses the outer diameter.

Draw a radial to the point where the involute touches the pitch circle. Draw another radial at 360/N/4 degrees away from that point where N is number of teethon the concave side of the involute. Now reflect the involute over this line. You have the other side of this tooth

Draw radials to connect to the root circle and a cap line or arc at the outer diameter.

Now extrude. Use some reasonable fillets on the ends and roots of the teeth. Use circular pattern to make the rest of the teeth.

For a rack, draw three horizontal lines at with spacing 1/P. Draw up from the root line a line at the pressure angle from the vertical. Mark where it crosses pitch line. Make a vertical line p/4 (circular pitch) away from it and reflect the line over it. Close off the top. This is a tooth.