User:RA2lover/Sandbox/Satellite Dish Automation - Revision history

RA2lover: removed mention of contact movement because contact angle noise has been removed

2026-01-27T20:57:43Z

removed mention of contact movement because contact angle noise has been removed

← Older revision		Revision as of 20:57, 27 January 2026
Line 1:		Line 1:
	- No information on signal strength is provided until a signal is resolved.		* No information on signal strength is provided until a signal is resolved.
	- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.		* No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.
	- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.		* Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.
	~~- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.~~		* Contact celestial positions can be triangulated by taking scans from different orientations:
	- Contact celestial positions can be triangulated by taking scans from different orientations:		** 1 resolution constrains the target's position at a given timeframe to a [https://en.wikipedia.org/wiki/Spherical_circle spherical circle] in the sky.
	- 1 resolution constrains the target's position at a given timeframe to a [https://en.wikipedia.org/wiki/Spherical_circle spherical circle] in the sky.		** 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circles from both resolutions intersect).
	- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circles from both resolutions intersect).		** 3 resolutions from different orientations constrain the target's position to a point in the sky (assuming resolution orientations are not coplanar).
	- 3 resolutions from different orientations constrain the target's position to a point in the sky (assuming resolution orientations are not coplanar).

	Math can be used to track down those points. Our goal is to calculate the celestial angles at which the circumferences intersect, and point the dish at them. Even though the contact moves, as the error gets smaller resolutions can be made faster.		Math can be used to track down those points. Our goal is to calculate the celestial angles at which the circumferences intersect, and point the dish at them. Even though the contact moves, as the error gets smaller resolutions can be made faster.
Line 18:		Line 17:
	== 2 resolution tracking ==		== 2 resolution tracking ==

	With 2 resolutions from different directions, the contact is constrained to 2 planes, whose intersection results in a line. The intersection of this line with the celestial circle results in 2 possible points that the target may be in. Which of these still has to be picked at random, however.		With 2 resolutions from different directions, the contact is constrained to 2 planes, whose intersection results in a line. The intersection of this line with the celestial circle results in 2 possible points that the target may be in. Which of these still has to be picked at random, however - with the special exception of one of the points being below the horizon and discardable by virtue of being unpointable.

	== 3 resolution tracking ==		== 3 resolution tracking ==

	With 3 resolutions from different directions, the contact would be constrained to 3 lines resulting from 3 different 2-resolution tracking systems. This can be converted into a point by solving a least-squares problem, but an approximation reusing existing code for the 2 resolution tracking problem can be made by picking one of the two potential points from the 2 latest resolutions and using the first resolution to ignore the least-likely point.		With 3 resolutions from different directions, the contact would be constrained to 3 lines resulting from 3 different 2-resolution tracking systems. This can be converted into a point by solving a least-squares problem, but an approximation reusing existing code for the 2 resolution tracking problem can be made by picking one of the two potential points from the 2 latest resolutions and using the first resolution to ignore the least-likely point.

RA2lover at 00:19, 26 October 2025

2025-10-26T00:19:07Z

← Older revision		Revision as of 00:19, 26 October 2025
Line 1:		Line 1:
	- No information on signal strength is provided until a signal is resolved.		- No information on signal strength is provided until a signal is resolved.
	- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.		- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.
	- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.		- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.
	- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.		- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.
	- Contact celestial positions can be triangulated by taking scans from different orientations:		- Contact celestial positions can be triangulated by taking scans from different orientations:
	- 1 resolution constrains the target's position at a given timeframe to a ~~circumference~~ in the sky.		- 1 resolution constrains the target's position at a given timeframe to a [https://en.wikipedia.org/wiki/Spherical_circle spherical circle] in the sky.
	- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the ~~circumferences~~ from both resolutions intersect).		- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circles from both resolutions intersect).
	- 3 resolutions from different orientations constrain the target's position to a point in the sky (assuming resolution orientations are not coplanar).		- 3 resolutions from different orientations constrain the target's position to a point in the sky (assuming resolution orientations are not coplanar).

	Math can be used to track down those points. Our goal is to calculate the celestial angles at which the circumferences intersect, and point the dish at them. Even though the contact moves, as the error gets smaller resolutions can be made faster.		Math can be used to track down those points. Our goal is to calculate the celestial angles at which the circumferences intersect, and point the dish at them. Even though the contact moves, as the error gets smaller resolutions can be made faster.

			== 1 resolution tracking ==

			With 1 resolution, the contact is constrained to a plane normal to our celestial reference point. This can be thought as a unit-hypotenuse right-angled triangle where the hypotenuse goes between our celestial reference point and the contact, the side adjacent to the celestial reference point is offset at an angle equal to our signal strength angle, has a length of cos(said angle), and the opposite side has a length of sin(said angle).

			Once the resolution is complete, we know how far the dish is from the contact, but we do not know which direction to point the dish towards. The next step in triangulation is to point the dish into a random direction and pray we've pointed it closer, which may not always be the case.

			== 2 resolution tracking ==

			With 2 resolutions from different directions, the contact is constrained to 2 planes, whose intersection results in a line. The intersection of this line with the celestial circle results in 2 possible points that the target may be in. Which of these still has to be picked at random, however.

			== 3 resolution tracking ==

			With 3 resolutions from different directions, the contact would be constrained to 3 lines resulting from 3 different 2-resolution tracking systems. This can be converted into a point by solving a least-squares problem, but an approximation reusing existing code for the 2 resolution tracking problem can be made by picking one of the two potential points from the 2 latest resolutions and using the first resolution to ignore the least-likely point.

RA2lover at 22:09, 25 October 2025

2025-10-25T22:09:26Z

← Older revision		Revision as of 22:09, 25 October 2025
Line 1:		Line 1:
	- No information on signal strength is provided until a signal is resolved.		- No information on signal strength is provided until a signal is resolved.
	- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.		- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.
	- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.		- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.
	- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.		- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.
	- Contact celestial positions can be triangulated by taking scans from different orientations:		- Contact celestial positions can be triangulated by taking scans from different orientations:
	- 1 resolution constrains the target's position at a given timeframe to a circumference in the sky.		- 1 resolution constrains the target's position at a given timeframe to a circumference in the sky.
	- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circumferences from both resolutions intersect).		- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circumferences from both resolutions intersect).

RA2lover: Created page with "- No information on signal strength is provided until a signal is resolved. - No info on resolution progress is provided in a way accessible to logic automation. This is likel..."

2025-10-25T22:08:09Z

Created page with "- No information on signal strength is provided until a signal is resolved. - No info on resolution progress is provided in a way accessible to logic automation. This is likel..."

New page

- No information on signal strength is provided until a signal is resolved.
- No info on resolution progress is provided in a way accessible to logic automation. This is likely because resolution progress rate could be used to estimate contact angle indirectly resulting in resolution exploits.
- Once resolution is complete, the signal strength value is updated from -1 to the angle between the dish and its contact in degrees. Unlike pre-terrain-update guides, lower signal strength values after resolution result in faster resolution times.
- Contacts move (slowly) in the sky. Restarting a resolution process under the same dish angle will result in different contact angles being returned.
- Contact celestial positions can be triangulated by taking scans from different orientations:
- 1 resolution constrains the target's position at a given timeframe to a circumference in the sky.
- 2 resolutions from different orientations constrain the target's position to 2 points in the sky (assuming the circumferences from both resolutions intersect).
- 3 resolutions from different orientations constrain the target's position to a point in the sky (assuming resolution orientations are not coplanar).

Math can be used to track down those points. Our goal is to calculate the celestial angles at which the circumferences intersect, and point the dish at them. Even though the contact moves, as the error gets smaller resolutions can be made faster.