开源 是一个非盈利项目,旨在让所有用户都能轻松使用维达占星术。
VedAstro.Library on NuGetpip install VedAstroFree Open Source codeThe sage Parashara taught everybody the ways of astrology without asking money, as such VedAstro does the same.
Anybody who has studied Vedic Astrology knows well how accurate it can be. But also how complex it can get to make accurate predictions. It takes decades of experience to be able make accurate prediction. As such this knowledge only reaches a limited people. This project is an effort to change that. Read More
The first line of code for this project was written in late 2014 at Itä-Pasila. Started as a simple desktop software, with no UI and only text display. With continued support from users, this project has steadily grown to what it is today. Helping people from all over the world.
Thanks to B.V. Raman and his grandfather B. Suryanarain Rao for pioneering easy to read astrology books. Credit also goes to St. Jean-Baptiste de La Salle for proving the efficacy of free and open work for the benefit of all men...Read More.
This development style celebrates the methodology of chaotic development at the benefit of low cost and fast paced prototyping. Inspired by the concept of "Gonzo Journalism", pioneered by Hunter S. Thompson in the 1970s.
We favour this pattern for the development of VedAstro simply due to the volatile nature of this project. Other development styles like "Waterfall" and "Scrum" are equally good when the need is.
✅ We want to :
Hence the "gonzo development" pattern is best suited for this needs.
We would like to introduce in this project a novel UX concept called "Drunk Proofing". The idea is simple. All UI is designed to be operated by an alcoholically intoxicated person aka drunk.
Why? Because this forces the team to make a simple and intuitive UI design. It is all too easy during development to make a complicated UI that only coders understand. But it is far more difficult and rewarding to make the UI intuitive & easy. A "no manuals" and "no brainer" approach to design.
The wisdom of ages, once passed down by word,
Now stored in circuits, rarely heard.
Once this knowledge was held in minds so keen,
Now it's coded in machines unseen.
The human touch, that once gave knowledge birth,
Replaced by algorithms, shaping future's girth.
Leslie Choi
Believed in the project even when work was only half done.
JetBrains
Gave free "ReSharper License" that made coding life easier.
Just Like & Share our social pages and it'll be a big help already!
We discuss & share ideas on astrology and computation. And ways you can integrate VedAstro into your own project.
Philosophy's the scaffold we use when we build,
Without it, a mud hut, not a structure fulfilled.
For creating grand codes, like VedAstro's design,
Philosophy's essential, its role is divine.
The purpose of VedAstro, we must understand,
Born of joy, in development it must stand.
This project thrives on happiness, pure and bright,
Don't code till your heart feels the building's delight.
When your fingers can't keep up, joy fills the air,
You'll know that your code is placed right with care.
In the universe vast, it finds its own way,
Your work shines with brilliance, come what may.
The main part of the program is the prediction/event generator. It works by combining logic on how to calculate a prediction with data about that prediction. This is done everytime a "Calculate" button is clicked. Below you will see a brief explanation of this process. This method was chosen to easily accommodate the thousands of astrological calculation possibilities.
…+--------+ +------------------------+ +------------------+
| User | | API |
| | +------> | - Blazor WebAssembly | domain registra -> azure DNS -> azure cdn -> web blob storage
api **stable** : api.vedastro.org -> domain registra -> azure DNS -> azure cdn -> stable api server (render)
api **beta** : beta.api.vedastro.org -> domain registra -> azure DNS -> azure cdn -> beta api server (azure)
domain cert managed by Let's Encrypt ACME bot Azure Function
## API domain is routed # MAR 2023
via Azure CDN Rules Engine, this allows the use of ```api.vedastro.org/...``` & ```api.vedastro.org/nlp/...```
## Antaram > Sukshma > Prana > Avi Prana > Viprana # FEB 2023
Since not documented by BV. Raman, code here is created through experimentation by
repeating relationship between Dasa planet & Bhukti planet.
## Skipping EventDataList.xml # FEB 2023
Not all data regarding an event is hardwired. Generating gochara, antaram, sukshma and others is more efficient if the description was created by the astronomical calculator.
At the moment EventDataList.xml is the source of truth, meaning if an event exists in xml file, then it must exist in code.
## Direct Events Chart # NOV 2022
- Accessing events chart directly via API generated html
- CORS in Azure Website Storage needs to be disabled for this to work, outside of vedastro.org
## Events Chart default timezone # NOV 2022
The default timezone generated for all svg charts will be based on client timezone.
Timezone does not matter when full life charts are made, but will matter a lot when
short term muhurtha charts are generated. Since most users are not living where they were born,
it is only logical to default it client browser's timezone.
This timezone must be visible/changeable to users who need to use otherwise.
## Event Chart Notes : Life Events # APR 2022
- This feature is to store notes on the dasa report
- The notes are actually Events converted to XML and stored inside each person's record
- When rendering these events are placed on top dasa report view
## WEBSITE : Why astrological calculation done on API server and not in client (browser) via webassmebly?
- The calculations tested on Intel Xeon with parallel processing take about 1GB RAM & 30% CPU.
With these loads browsers with mobile CPU's are going to be probelmatic for sure.
So as not to waste time, the API route has been decided since it has been proven to work.
- There are places where all Astronomical computation is done in client, exp. Planet Info Box
## MUHURTHA : Notes On Gochara Prediction (from book ) # FEB 2022
- Built on reference to, Hindu Predictive Astrology pg. 254
- Asthavarga bindus are different from shadbala and it is to be implemented soon.
- Asthavarga bindus are not yet account for, asthavarga good or bad nature of the planet.
It is assumed that Shadbala system can compensate for it.
- This passage on page 255 needs to be clarified
"It must be noted that when passing through the first 10
degrees of a sign, Mars and the Sun produce results."
- It's interpreted that Vendha is an obstruction and not a reversal of the Gochara results
So as for now the design is that if a vedha is present than the result is simply nullified.
- In Horoscope predictions methods have "time" & "person" arguments available,
obvioulsy "time" is not needed, but for sake of semantic similarity
with Muhurtha methods this is maintained.
## Zoom functionality in Dasa View Box
- Option 1 : generate a high res image (svg/html) and zoom horitontally into it
- very fast
- image gets blurry
- Option 2 : Regenerate whole component in Blazor
- very slow
- hard to implement with touch screen
- Option 3 : Generate multiple preset zooms, than place them on top of each other,
and only make visible what is needed via selector
- complicated, needs documentation
- easy touch screen implimentation
- very fast
Thus Option 3 was chosen.
## Astrology Library: Use of Struct vs Class
- Structs are used to reduce overhead from large collections, exp. List<>
- When structs are part of a class, they are stored in the heap. An additional benefit is that structs need less memory than a class because they have no ObjectHeader or MethodTable. You should consider using a
struct when the size of the struct will be minimal (say around 16 bytes), the struct will be short-lived, or the struct will be immutable.
## Person Get Hash uses MD5
- default hashing is inconsistent, MD5 is use暂无开放 Issues,或尚未同步最近议题。