KAUCIM.AI
Compare two BaZi charts
Record the inputs and conventions before deciding why the pillars differ. Leave unknown settings unresolved.
Print this worksheet or save it as a PDF with your browser. This file has no form submission or tracking scripts.
| Check | Chart A | Chart B |
|---|---|---|
| Gregorian or lunar input, including leap month | ||
| Time zone and historical daylight saving | ||
| Clock or solar time, adjusted date and hour | ||
| Year and month boundaries | ||
| Day boundary and late-Zi convention | ||
| Known, estimated, or unknown hour | ||
| Year / month / day / hour pillars |
Check in this order
- Match the original input. A lunar date entered as Gregorian, or a missed leap month, changes the calendar date. Keep the original record separate from any corrected date.
- Match the time basis. Check the birthplace, the historical time-zone offset, and daylight saving on the birth date. Solar time also adjusts for longitude and the equation of time. Review the corrected date and hour branch.
- Match the boundaries. Li Chun changes the BaZi year under our convention. Twelve Jie solar terms change the month. Midnight and 11 p.m. day-change conventions can produce different day or hour pillars.
Current kaucim.ai calculation limits
The pillar calculation uses the starting hour of the selected branch. Entered minutes help select the date and branch, but are not retained for the pillar or luck-cycle calculation. A solar-term change within that window can leave the year or month pillar on the earlier side of the boundary.
Late Zi, 11 p.m. to midnight, uses the same date's midnight pillars. On a solar-term transition day, its year or month pillar therefore needs a separate check. The calendar engine evaluates solar terms on its UTC+8 calendar coordinates; a match between two tools does not settle a boundary case.
An unknown hour omits the hour pillar. Near midnight, uncertainty can also affect the day. Mark estimated inputs clearly. Luck-cycle starting ages are estimates at hour-branch precision.