The way things are implemented now: a "footprint" in which the stars are found is used as the reference throughout the pipeline for referring back to the stars. (Every table carries a "footprint hash" key)
But this footprint does not include the filtering (which can be changed by user) on stars (magnitude range, max astrometric or photometric noise).
Possible solutions:
- include the limits in the hash representing the "footprint" (but risk of collision?)
- find an all new way of referring back to stars, even though everything now is built around querying by the hash of the footprint
First steps:
- given that the calculation of the hash of the footprint turned out to be the same throughout the pipeline, refactor it to see more clearly
The way things are implemented now: a "footprint" in which the stars are found is used as the reference throughout the pipeline for referring back to the stars. (Every table carries a "footprint hash" key)
But this footprint does not include the filtering (which can be changed by user) on stars (magnitude range, max astrometric or photometric noise).
Possible solutions:
First steps: