Expression Gate Documentation

[Razara]

Also messed around with your vector funktion, NICE.

N@Vector test
I@X1 X2 Y1 Y2 Z1 Z2
O@Pitch Yaw Distance

V1=vector(X2-X1, Y2-Y1, Z2-Z1)
Pitch=(vecpitch(V1)>180?-360+vecpitch(V1):vecpitch(V1))
Yaw=vecyaw(V1)-180
Distance=veclength(V1)

Will make a -180 to 180 pitch and yaw out of two points in space. And distance between them.[/b]

Wow, you just solved the troubles I had with coming up with a working code like that for my turret, thank you so much!


Syranide:
For some reason my clamp function is not working properly.

N@Test
I@A Reset
O@C
interval(1000)
A->clk()->B+=1;;
C=clamp(5,B,10)
Reset->B=0;

The clamp works for the lower limit since C at the lowest is 5, however the upper limit does not work since C goes past 10. Is there an error in my code perhaps?

[Shandolum]

You should see the vector calculations that I have made for my spacecraft, they are really something that I am proud of having made, since I have needed a new delta-pitch, -yaw, -roll with several of my creations. And Now I finally have them by the use of three GPSs.

[Syranide]

Wow, you just solved the troubles I had with coming up with a working code like that for my turret, thank you so much!
Syranide:
For some reason my clamp function is not working properly.

N@Test
I@A Reset
O@C
interval(1000)
A->clk()->B+=1;;
C=clamp(5,B,10)
Reset->B=0;

The clamp works for the lower limit since C at the lowest is 5, however the upper limit does not work since C goes past 10. Is there an error in my code perhaps?[/b]

"C=clamp(B,5,10)", is the proper syntax, and by the way.
"A->clk()->B+=1;;" is the same as "A & clk()->B+=1;"

You should see the vector calculations that I have made for my spacecraft, they are really something that I am proud of having made, since I have needed a new delta-pitch, -yaw, -roll with several of my creations. And Now I finally have them by the use of three GPSs.[/b]

I bet they are, you seem to be really profficient with the expression gate

[EntropyGuardian]

...
Messed around some more:

N@Vector test 2
I@X1 X2 Y1 Y2 Z1 Z2 Length
O@DX DY DZ

#First the vectors for the two GPS
VA****= vector(X1, Y1, Z1)
VB****= vector(X2, Y2, Z2)

#Then making the vector
V1****= vecsub(VA, VB) #Subtracting them

#Now for the normalization of the vector
V2****= vecnormalize(V1) #The normalized vector

#Now to put it to good use (hoverdrive)
V3****= vecsmul(V2, Length) #Length = distance in units the vector will be. Multiplying the normalized vector with the length.
Destination = vecadd(V3, VA) #Adding the new vector to the original position (point of origin).
DX****= vecx(Destination) #The X value for the destination
DY****= vecy(Destination) #The Y value for the destination
DZ****= vecz(Destination) #The Z value for the destination

And now you have a good hover drive expression-gate that teleports you a set distance forward.
This would be better if you could use the X Y Z values from the hover drive as the point of origin.[/b]

Heh, maybe you can help me. In this thread [ http://www.wiremod.com/showthread.php?t=974 ] I was asking how to do something similar (before vectors) and came up with this mess:

N@Point Master
I@X1 X2 Y1 Y2 Z1 Z2 F R U
O@X3 Y3 Z3
M = (Y2 - Y1) / (X2 - X1)
D = sqrt((X2 - X1)^2 + (Y2 - Y1)^2)
B = Y1 - M * X1
X3R = R * ((Y2 - Y1) / D) + X2
Y3R = -R * ((X2 - X1) / D) + Y2
X3D = (F + D) * ((X2-X1) / D) + X1
Y3D = (F + D) * ((Y2-Y1)/D) + Y1
X3 = X3D + X3R - X2
Y3 = Y3D + Y3R - Y2
Z3 = Z2 + U

That will give you, given two GPS points, and how much you want to move forward, right, and up (or reverse for the opposites), where that third point is relative to how the gps's are facing. It blatantly cheats to go up since it just really is working on the 2-D XY coordinate plane and hell if those formulae were going to get any longer by adding another set of coordinates.

Apparently I took analytical geometry and cal 2 in college but I don't remember a drip of vector math.

[Shandolum]

Try checking my spacecraft. it includes both the things you seek.

[E_net4]

I found an error on the Inputs and Outputs section:

# GOOD! Break will revert to 0 once Speed is less than 50
Break = 0, Speed >= 50 -> Break = 0;

The correct version is:

# GOOD! Break will revert to 0 once Speed is less than 50
Break = 0, Speed >= 50 -> Break = 1;

I just hope I'm right, as I'm new to "wiring". :/

[Syranide]

Ah, thank you, you are correct.

[CBBP]

Not real short how you would make a pulser from that internal clock. like.. how would I make it dance form 1 to 0 to 1 over and over.

[Core Xii]

O@Out
first() -> interval(1000);
clk() -> Out = !Out;

Square pulse with length 1 sec.

[Syranide]

O@Out
interval(1000);
clk() -> Out = !Out;

Just a little flaw Core Xii, it would only flip once (first() -> ... ;)
And while I'm at it, IF you do not add inputs to the gate, you can also remove "clk() -> ... ;", but for all other uses it has to be there.