A simple tool to find auspicious times for various occasions and endeavors.
$ # Setup.
$ sh ./setup.sh
$ # Simple run.
$ python3 main.py ./examples/config.yml
$ # Using presets. Configs to the right have more priority.
$ python3 main.py ./presets/biz.yml ./examples/presetExtensions.yml- Jagannatha Hora, a vedic astrology software by P. V. R. Narasimmha Rao.
- JyotishApp, an android app by Vishnuvardhana SV.
- JyotishyaMitra, a python package by Shyam Bhat.
- Accuracy of the computations are affected by the chosen Ayanamsa.
- The preferred ayanamsa is "raman" as it's closer to the Pushya at 16Cn, suggested by PVN Rao.
- Jagannatha Hora seems to be more stable in handling higher latitudes than JyotishApp.
- Astrology software in general seem to have at least a few minor bugs in handling sunrise and sunset times at higher latitudes.
- Some names are in English and other in Sanskrit. This is a temporary situation for operational efficiency.
- AbdaBala and MaasaBala calculations doesn't seem to be precise, as the length of an year (based Jupiter's movement across signs) is considered to be 360 days, instead of ~361.08333 days. The same anchors are used for computing MaasaBala too. This might render the values incorrect. This might need some new calculation methods by analyzing Astro Data Banks.
- Rise and Set calculations of polar regions could be imprecise.
- Explore True Pushya Nakshatra Ayanamsa by PVRNR (swe.SIDM_TRUE_PUSHYA).
- Make the config, fieldSets, a dictionary to ease the selection of columns. The keys are to be the name of the filedSets, where as the values could be all, none or a list of fields to be included in the final result. Note that, this would render the config, skipColumns redundant.
- Thinks of moving the computations to Julian Dates, for ease.
- Introduce charts to analyze trends.
- Think about introduce endTime config as an option, to allow the skipping of period config.
- Think of introducing startDate (2024-07-25), startTime (18:00:00), endDate and endTime configs.
- Use planetary short forms (IE: Me, Ju, etc) as the default.
- Replace periods with a single period config, with values with same type as frequency.
- Check whether muhurtaYoga effects depend upon Pakshatithis.
- Validate the presets with experts.
- Get popular reference locations cross regions, from experts.
- Try adding more muhurta yoga combinations.
- Introduce proper package management.
- Make the configuration a bit more human readable.
- Support DMS notation for latitudes and longitudes.
- Improve the accuracy of Tithi Calculations.
- Try to depend on chart objects, rather than python datetime for weekday calculations.
- Prefer numbers over strings for calculations. Have a translation layer at the tail to make things readable. This could be done as a part of performance improvements, post initial development. This could lead to moving some data dependent decisions to calculations.
- Standardize naming conventions across languages. IE: Don't use Wednesday and Budha together.
- Find the correct name for the muhurta yoga recorded as apaduddharaka.
- Handle tripushkara and tripushkara yogas appropriately.
- Add individual impacts of weekdays, tithis and nakshatras to muhurta effects. Refer: https://www.astrojyoti.com/naksatratithiyogainfo.htm
- Bring in the effects of other time scales like maasa, yoga, karana, chowgadiya, hora etc. These might need a different CSV file as the format is different, as their effects are not tied to other scales.
- When possible include personal natal charts to find muhurta fitment.
- Fine tune the analysis with input from: https://astrologerjolly.tripod.com/muhurtha.htm
- Understand the impact of altitude on charts, as the sunrise time would be different.
- Krakacha yoga is formed when tithi + vaara = 13.
- Amritasiddhi Muhurtayoga is a subset of Sarvarthasiddhi yoga.
- JH: Jagannatha Hora.
- JA: JyotishApp.
- 2406250100 - Found out that the difference between the Saptavargaja Calculation of JH and JA are due the differences in calculating D2 chart. JH by default doesn't use the traditional Parasara Hora. And also found out that there are many systems of calculating divisional charts.
- 2406250100 - The varga computation used here ended up to be really closer the the Custom Divisional Chart from JH.
- 2406270340 - Got the Saptavargaja calculation right, after a long struggle due to not understanding some fundamental concepts.
- 2406300355 - Discovered that there are some minute differences in the positions of fast moving planets between JA and siderealib, when the ayanamsa is set to BV. Raman.
- 2407250725 - Decided not to use the Chesta Bala computation used in JH and JA as the anchor date of 01-01-1900 seems arbitrary and changing the anchor impacts the balas of fast moving planets, significantly.