theTreeSpyder
TreeHouser
- Joined
- Feb 12, 2016
- Messages
- 691
That was always going to be the tile of this for quite some time now.
Originally meaning cosine, as my friend; but then here now to friends in dual meaning as well.
A column with weight on top capitalizes on cosine in this model as the alignment of load to support
>>while at 90degrees from this line capitalize on sine across column like Samson or wrench across a linear column
>>column @pure vertical uses all length for reach, but can't use full length nor strength vertically @ lean
to this model a stone drop is cosine benchmark axis all rest of sine rings are measured from that benchmark etc.
Cosine is the simpler to start with; and has been my friend once got to know(and quit kicking my azz) as a decoder to events.
>>often taught as visible lengths/distance usually, but applies to force (as a distance reciprocal so one always implies the other)
Several ways of using the measuring stick tools of cos/sin to decode the changes all to same end, just how much work between..
Many find cosine as horizontal axis only from school, and can only see that way.
While builders etc. may only see it as gravity load bearing vertical aspect, as a Greek column of support.
Quite a chase trying to self teach.. Is best to be able to use cosine in any direction more fluently i think.
i walk it around a scenario like a measuring tape/stick, and claim one primary axis of scenario as the benchmark cosine.
>>to judge rest of scenario from this benchmark line of simplest 1D, for a scenario MUST have dimension(or no place to change to).
Cosine is a linear 1D so i align it to a similar 1D in scenario(force line or support against usually) for least calculations
Cosine can be seen as a remaining virtual column of support in a tree lean as support work achieved against weight and space(height)
>>the side force byproduct as the leverage making a triangle actual lean, and the vertical and horizontal EXPRRESSIONS of length and force in the actual lean as the total potential that can be expressed.
The main work i still seen as support CoG but can't do as well in strength nor height with present fixed assets:
We can capitalize on the leveraged byproduct of lean to fall tree in this chess game tho.
Cosine is a graduated scale, but of unequal graduations per degree for a 1Dimensional axis benchmark line.
Easiest to L-earn as gravity load for our work i think, i look at it as a Greek column, co(lumn)sine i say(sine as the sin against laterally/crosswise) as memory aids
A slanted pillar can't hold as much weight as pure inline, and can read effect as cosine dropping as the precise scale of change to loss of efficient usage of strength and length potentials.
Cosine ranges as a multiplier from 0 to 1; i look at as 0-100% multiplier of efficiency of benchmark alignment.
Pure vertical is 100% strength and length potentials used, 30degrees deflection for support and is only now efficiently:
able to use 86.6% of full length (as a potential) for rise AND able to use 86.6% full strength(as a potential)for support.
A rigid device can internally resist on at least 1 cross axis, but rope/flexible devices cannot resist against on any cross axis.
>>so need an external imposer of side force or will self adjsut to none
>>the green rope below @250# is that, or another opposing support leg side force in opposite direction , pulley in center
.
BUT>>incurs a byproduct side load of 50%, a big jump from Zer0 vs. 13.4% drop in cosine each in 1/3 the travel
>>cos/sin give us these numbers,
>>but (in my imagery) the primal FFF caveman preprocessor brain assUmes different numbers to hand to brain mainframe(prev.discussion)..
>>does not expect the 250# side force below nor the slight loss in vertical drop at 1/3rd travel, must retrain/intercept that process and force new look.
.
This is as a system of balances, the above configurations MUST give these numbers; cos/sin is the key decoder to define change like it was a balance scale !
i used to look at cosine from the column of support perspective, as pictured Greeks did to hold up roof
>>but have 'evolved' to generally setting the initial force as cosine as flows to that column support,
>>to same numbers but think is more correct , at any angle, like used in electric/wind/water/light etc. waveforms as concept is consistent even to those depths
(from same numbers found decoded the stars movements) youtube.com/watch?v=rd4tY3brjT4 child's coin slam force transference:
These are all the same cos/sin to decode, the same rules just expressed in water, tree, rope, pulse wave examples of same things etc.
As are all displacements against physical space and against physical force, so must be able to define most pivotally as cos/sin.
>>as even the stars are commanded to do and so all below the Ancients found, we could never prove them wrong on that.
Originally meaning cosine, as my friend; but then here now to friends in dual meaning as well.
i look at cosine as directness and sine as deflection >>any potential connected to scenario is 1 of the 2
A column with weight on top capitalizes on cosine in this model as the alignment of load to support
>>while at 90degrees from this line capitalize on sine across column like Samson or wrench across a linear column
>>column @pure vertical uses all length for reach, but can't use full length nor strength vertically @ lean
to this model a stone drop is cosine benchmark axis all rest of sine rings are measured from that benchmark etc.
Cosine is the simpler to start with; and has been my friend once got to know(and quit kicking my azz) as a decoder to events.
>>often taught as visible lengths/distance usually, but applies to force (as a distance reciprocal so one always implies the other)
Several ways of using the measuring stick tools of cos/sin to decode the changes all to same end, just how much work between..
Many find cosine as horizontal axis only from school, and can only see that way.
While builders etc. may only see it as gravity load bearing vertical aspect, as a Greek column of support.
Quite a chase trying to self teach.. Is best to be able to use cosine in any direction more fluently i think.
i walk it around a scenario like a measuring tape/stick, and claim one primary axis of scenario as the benchmark cosine.
>>to judge rest of scenario from this benchmark line of simplest 1D, for a scenario MUST have dimension(or no place to change to).
Cosine is a linear 1D so i align it to a similar 1D in scenario(force line or support against usually) for least calculations
Cosine can be seen as a remaining virtual column of support in a tree lean as support work achieved against weight and space(height)
>>the side force byproduct as the leverage making a triangle actual lean, and the vertical and horizontal EXPRRESSIONS of length and force in the actual lean as the total potential that can be expressed.
The main work i still seen as support CoG but can't do as well in strength nor height with present fixed assets:
We can capitalize on the leveraged byproduct of lean to fall tree in this chess game tho.
Cosine is a graduated scale, but of unequal graduations per degree for a 1Dimensional axis benchmark line.
Easiest to L-earn as gravity load for our work i think, i look at it as a Greek column, co(lumn)sine i say(sine as the sin against laterally/crosswise) as memory aids
A slanted pillar can't hold as much weight as pure inline, and can read effect as cosine dropping as the precise scale of change to loss of efficient usage of strength and length potentials.
Cosine ranges as a multiplier from 0 to 1; i look at as 0-100% multiplier of efficiency of benchmark alignment.
Pure vertical is 100% strength and length potentials used, 30degrees deflection for support and is only now efficiently:
able to use 86.6% of full length (as a potential) for rise AND able to use 86.6% full strength(as a potential)for support.
A rigid device can internally resist on at least 1 cross axis, but rope/flexible devices cannot resist against on any cross axis.
>>so need an external imposer of side force or will self adjsut to none
>>the green rope below @250# is that, or another opposing support leg side force in opposite direction , pulley in center
BUT>>incurs a byproduct side load of 50%, a big jump from Zer0 vs. 13.4% drop in cosine each in 1/3 the travel
>>cos/sin give us these numbers,
>>but (in my imagery) the primal FFF caveman preprocessor brain assUmes different numbers to hand to brain mainframe(prev.discussion)..
>>does not expect the 250# side force below nor the slight loss in vertical drop at 1/3rd travel, must retrain/intercept that process and force new look.
.
This is as a system of balances, the above configurations MUST give these numbers; cos/sin is the key decoder to define change like it was a balance scale !
i used to look at cosine from the column of support perspective, as pictured Greeks did to hold up roof
>>but have 'evolved' to generally setting the initial force as cosine as flows to that column support,
>>to same numbers but think is more correct , at any angle, like used in electric/wind/water/light etc. waveforms as concept is consistent even to those depths
(from same numbers found decoded the stars movements) youtube.com/watch?v=rd4tY3brjT4 child's coin slam force transference:
These are all the same cos/sin to decode, the same rules just expressed in water, tree, rope, pulse wave examples of same things etc.
As are all displacements against physical space and against physical force, so must be able to define most pivotally as cos/sin.
>>as even the stars are commanded to do and so all below the Ancients found, we could never prove them wrong on that.
Last edited:
