All around white mast light

Forward facing mast light. Two if > 50m.

White over Red.

Flag: Red, white

Two forward white. Yellow aft

Flag: rhombus

Red White Red. Flag: Rhombus between two circles

Three red. Black cylinder flag

Green over white. Sandclock flag

Red over white.

Flag: sandclock

Red White Red, RR on danger side, GG on the non-danger side.

Passage of a cold front shifts the wind direction to be more clockwise direction -- veering wind in the NH.

SH: a more anticlockwise direction -- a backing wind.

The change is not gradual essentially

sets up a thermal gradiet

Movement of water

Local currents: tidal ones which switch direction.

minimum depth.

Dynamic depth of the water.

~1/7, the length of the boat here.

Waves are just transfer of momentum. And they continue if there's nothing to sap its momentum -- ex wind or subsurface structure.

Maybe the origination was distant storms or tsunami etc.

Interaction of waves with wind (besides construction)

wave power is a function of amplitude

This is relatively straightforward but took me quite a lot of time to get.

There are two points of interest: 1. top of the sail -- influenced by the leech and the slack therein. 2. bottom of the sail -- influenced by the slack in the foot.

Structure created by slack in (1): a twist/pouch at the top. This pouch exposes the exterior region to higher wind and shields the interior region from wind.

Structure created by slack in (2): the bulging of the sail. And again you might or might not want this on the interior or the exterior sides.

fairlead forward \(\implies\) fills out the inner sail.

Help with the inner flutter of the tales. Should help the outer flutter as well -- but towards the bottom, not the top.

This means, increased tension all the way on the leech -- limiting its freedom with wind. Not letting it twist on the top -- where the wind is high -- quite as much for instance. This also means the wind at the top would behave similarly to the rest of the sail.

The foot has decreased tension which means it can inflate to port (if on-starboard), or starboard (if on-port).

Mid level slack on the jibsheet.

Mid-left fairlead leds to top two port tales fulltering. Not enough wind on the inside top. Loosening the leech would do it. (no, it's the opposite.)

Loosening the foot allows the sail to fully inflate leading to the port geting more wind.

Notable bit: how this helps the port side.

This allows the sail to twist out more upwards, which given the wind is from starboard allows more wind to flow on the outer side.

Implies: not enough wind on the port side up top.

If the foot has low tension, then the bottom would inflate out, but the top wouldn't be.

So increase foot tension (pull back) and give the leech some slack.

"Putting more tension on the foot, easing out the leech."

"leech would twist out and away downwind". Especially at the top.

Trim: length of sheet to the sail.

Over trim: pulled in too much Under trim: given too much slack

So either a barrier via IBPB or IBRS=any?

after case: the IBRS, presumably walks and cleans up context specific state? already set: checks for it on control change?

What if the guest resets it? Where do we handle that?

Nightfall -- night every 5000 (or whatever years) lead to the fall of civilizations. Helliconian winter did the same thing (I think).

The amazing thing is that there the event was actually unexpected.

In Florida and similar places, we repeat these mistakes, inspite of knowing that they are mistakes, because we've built structures [0] that almost compel them.

Those structures were built because other structures -- political, capitalistic, whatever.

How would you create peano numbers like this?

Or alternately functions in their math sense (morphisms).

Just like operational definition

Polymorphic functions, like foldr, id, map are functions which can act on a multiple types of sets.

Higher level functions are arrows in categories whose objects are other categories.

The circularity here comes in because higher order functions reference themselves -- via reduction sequences.

Going back to cat-theory for a bit, we had objects and we had arrows.

Arrows are morphisms -- structure preserving map between objects. Now, we are talking about categorization of objects into separate sets.

Design the types, the structure, essentially the surface of the program.

Then fill in the implementation, the volume and let the compiler take care of validating the implementation.

Types enforce structure, which enables composability.

From wikipedia:

morphism: *structure preserving map from one mathematical structure to another

structure is an aggregate thing -- about the domain not about any one object in the domain.

In set theory, morphisms are functions; in linear algebra, linear transformations; in group theory, group homomorphisms; in topology, continuous functions

So, in set-theory functions are structure preserving maps from a set to another.

In linear algebra, linear transformations are structure preserving maps from ...

In group theory, group homomorphisms are structure preserving maps from elements of the group (?) to ...

In Topology, continuous functions are structure preserving maps from one /region/ (?) to another.

In category theory, morphism is a broadly similar idea, but somewhat more abstract: the mathematical objects involved need not be sets, and the relationship between them may be something more general than a map.

Based on the arrow being a morphism/function (see below), it seems that the domain and the co-domain should be able to be disjoint.

Also, here A->B and A->C; the dual map means that an arrow is not a function.

Alternately stated: All you can do with categories is composition?

which changes with process. But, perhaps slower now.

But it does illustrate how much you design to a process.

Opteron was 2003. Nehalem, 2009.

That's a long gap. But of course they messed up with Barcelona.

That clears that. Arrow A->B and arrow B->C are not necessarily the same arrow (function).

Okay, so what are we doing here? Category is a set (?) of objects with arbitrary functions between them. The only property that this needs to satisfy is one of transitivity.

They don't commute sure, but what if we are really careful with them and make sure there are no cycles.

Of course you could have locks where they protect overlapping regions -- that seems problematic.

This seems to refer to my last comment: composition is not just about composing function and ADTs, but also makes concurrency composable.

From this first lvar paper: http://lambda-the-ultimate.org/node/4823, if two sets of modifications can be structured to commute, then they are guaranteed to be thread safe and thus can be composed.

TL;DR version.

Why would Oracle build custom hardware?

Oracle does have few large customers. Note that the public cloud efforts of MSFT, GOOG, AMZN are trying the same thing -- just with different set of technologies.