Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implemented coned sensors. #226

Open
wants to merge 8 commits into
base: develop
Choose a base branch
from
Open

Conversation

bk2w
Copy link

@bk2w bk2w commented Jan 16, 2014

Sensors are able to scan multiple cells if far enough away.
Addresses issue #106

@bk2w
Copy link
Author

bk2w commented Jan 16, 2014

Sensors include a new BeamWidth parameter that determines the angular width of the sensor beam, and affects how many cells are scanned at each interval. The sensor footprint is calculated based on true altitude, and compared against the size of the cells on the planetary body. This means that a given sensor at a given altitude can scan more cells on Gilly or Pol than on Eve.

This helps make the medium sensor much more appealing, despite its size and power consumption.

On most bodies, the small sensor can only scan one cell at a time. The one exception is Gilly, simply because of it's tiny size. At maximum altitude over Gilly (edge of SOI), the small sensor scans a cluster of 7 cells

The medium sensor is generally able to scan a cluster of multiple cells, but requires altitude to achieve this. At max altitude over Pol (1.042Mm, edge of SOI), the medium sensor can scan a hexagonal cluster of 217 cells 9-cells on a side; this is the largest cluster possible. Max cluster size on Minmus is 169, 8-cells on a side. On Kerbin-sized bodies, the medium sensor can only scan one cell at a time.

The sensor BeamWidths are part.cfg parameters and easily tweaked for balancing.

@bk2w
Copy link
Author

bk2w commented Jan 16, 2014

An additional factor that might be used for balancing a wide sensor be is increasing the power consumption based on altitude or number of cells that would be scanned.

bk2w and others added 7 commits January 17, 2014 15:55
Increased the speed on fetching neighbors by removing some duplicate
loops. The scanning speed is now limited by how quickly the scanned
cells could be updated.
Fix a bug with the GetNeighborhood function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants