Comment 30 for bug 1710443

Revision history for this message
vishvAs vAsuki (vvasuki) wrote :

I catch the drift from both @alexwolf and tanmoy's comments that you feel that the desired partition boundaries should not be implemented as nakShatra boundaries (based on conceptual ugliness in the force-fit, rather than any user inconvenience). This is reasonable. Perhaps we can use separate imaginary nakShatra-s as a stop-gap solution, as proposed.

Even that is unsatisfactory because:
* One needs to define these imaginary nakShatra-s.
* The actual boundaries (even having fixed the ayanAmsha regime) moves with time (dependent partly on the speed of the vernal point). The imaginary-nakShatra-boundary will only be good for today, but not for some other far-away time.

So what one really needs is support for defining ayanAmsha-based partition of the sky into 27 equal strips. What is the best way to accomplish this? (some script perhaps?) And how about the imaginary nakShatra solution for now?