Loading of the database does the following:
1. allocate a single block of memory where coordinate/
magnitude info is stored (this way we don't need to iterate the
records later which would take too long)
2. convert polar coordinates to cartesian coordinates (involving
sin/cos).
The plan is to organise the location data in a QuadTree
structure, with more than one item per record. This way we
don't need to iterate over all stars just to check if they are in the
currently visible part. I still have to figure out if the QuadTree
should store the coords/mag info.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=18252
Loading of the database does the following:
1. allocate a single block of memory where coordinate/
magnitude info is stored (this way we don't need to iterate the
records later which would take too long)
2. convert polar coordinates to cartesian coordinates (involving
sin/cos).
The plan is to organise the location data in a QuadTree
structure, with more than one item per record. This way we
don't need to iterate over all stars just to check if they are in the
currently visible part. I still have to figure out if the QuadTree
should store the coords/mag info.
Logged In: YES
user_id=73968
Sounds like you already had plans to improve this. :-)
Great! I anxiously await the results.