The invention is neither a work for hire or Federally-sponsored.
Popular in newspapers and on the internet, at web portals and dedicated web sites, are daily horoscopes. These horoscopes are written by a human author, wherein for each day, the author writes twelve different horoscopes, one for each of the twelve zodiac Sun signs (Aries, Taurus, Gemini, Cancer, Leo, Virgo, Libra, Scorpio, Sagittarius, Capricorn, Aquarius and Pisces). By doing so, that method, and its results, divide all people into one of twelve groups, wherein each person of a specific group (Sun sign) receives the exact same horoscope. Common sense states that, to provide each twelfth of the human population with the exact same horoscope, it can not accurately predict or render a unique and suitable horoscope for each and every individual.
Personalized astrology is based on the unique natal data of the individual, comprising the individual's birth date (day, month and year), birth place, and birth time. These are the input requirements for generating an individual's unique astrological data (the exact locations of the ten “planets” of astrology, which comprise the Sun, the eight non-Earth planets of the solar system, and the Earth's Moon), from which charts, tables and aspect grids for the individual can be accurately manufactured. Hence, a daily horoscope for each person should also be generated along these lines, using each person's unique birth input data.
The invention builds a computational program, resident on a computer or electronic device, the results of which are displayed, or are sent automatically to subscriber/user e-mail addresses, or are accessible at a dedicated web site. The program generates, automatically and without human intervention, the unique and individualized daily horoscope for each subscriber/user, based on each user's specific birth data inputs. Each day's horoscope is generated for each subscriber each day.
The program takes each user's input of user's birth date, and parallel, the input of the horoscope date, and computes the planetary locations for user birth date and for horoscope date. These computations are made using complex mathematical and scientific algorithms which are available as public information. Then, the geometric relations (aspects) between the two sets of planetary data are determined, eg. using if/else type logic. Each determined relation (aspect) then calls to the database which stores the complete set of interpretative comments for each type of aspect between each possible planet to planet consideration. The appropriate interpretative comment for each applicable aspect is called and, together with all called applicable aspects, the horoscope comprises a set of compiled interpretative comments.
The method is extensible to non-computerized environments and application, wherein the manufacturing party manually renders the same set of results, using a printed-matter type database.
Three systems for processing and delivery are described.
The invention provides a functional and effective program that takes personal information and delivers a highly accurate and individualized daily horoscope—without human intervention.
Using highly individualized data, being the personally unique data of the user's birth date, of day, month and year, and of birth time, the program employs scientifically accurate determinations respective planetary placements, both for the birth data set and for the horoscope date, and employs innovative determination of astrological information, comprising the relevant aspects made between the planetary placements of the two data sets, the interpretations of the determined aspects, and the compilation of the interpretations, rendering a daily horoscope.
Because the invented method and consequent generator program rely on the fundament of planetary locations determined by their ecliptic positions to degree of 360, and not determined, or requiring to be determined, by any system of astrological sign, and utilize geometric aspects to trigger interpretations, this facilitates universal application across all astrological forms.
Truly, this method and program execute the most accurate and compelling means to achieve a personalized daily horoscope, for, as per Webster's New Collegiate Dictionary definition, astrology is “the divination of the supposed influences of the stars and planets on human affairs and terrestrial events by their positions and aspects”. This focus is wholly and solely achieved.
The invented daily horoscope generating method and program begin by establishing the inputs of the subscriber/user, which comprises the user's birth date, of day, month and year. As a secondary user input, the birth time, of hour and minutes, AM or PM, can be separately lodged. The input of the horoscope date is also established, comprising its day, month and year. As a secondary or alternative assignment, the horoscope date may be “today” or “tomorrow”, or a date which can be selected by user.
The next step of the invented method, and the calculations performed by the invented horoscope generator program, utilizes the set of birth date position data, and, respective the set of horoscope date position data, calculates, for each birth date planet respective each horoscope date planet, all aspects formed. At a minimum the aspects calculated are the group of conjunction (an aspect of equivalent degree, and an orb of about 8 degrees), opposition (a 180 degree separation, an orb of about 8 degrees), trine (a 120 degree separation, an orb of about 6 degrees), and square (a 90 degree separation, and an orb of about 6 degrees). The operator, “orb”, indicates the range around the separation. If none of these aspects are made, then no aspect is determined.
Three further types of aspects can be calculated, the group of quincunx (a 150 degree separation, an orb of about 4 degrees), sextile (a 60 degree separation, an orb of about 2 degrees), and semi-sextile (a 30 degree separation, an orb of about 2 degrees). For completeness, all seven types of angular aspects are sought.
As described in
“How to Compute Planetary Positions”, by Paul Schlyter; and
“Computing Planetary Positions—a Tutorial with Worked Examples”, by Paul Schlyter, at www.stjarnhimlen.se/comp.
However, a more personalized compilation utilizes the user's birth date time to determine the respective lunar sign and its longitude field, yielding the user's horoscope ascendant field. Respective the horoscope ascendant field, the compilation of the aspect interpretations commences with the identified aspects of user's birth date planets in user's horoscope ascendant field.
Further, from the user's birth date year, the respective sign and longitude field is determined, yielding user's horoscope ruling field. Respective the horoscope ruling field, the compilation of the aspect interpretation concludes with the identified aspects of birth date planets in the horoscope ruling field. Should the two horoscope fields be identical, then the use and placement of the horoscope ascendant field is appropriate.
Absent of any aspects in the horoscope ascendant or ruling fields, and after any ascendant field aspect interpretations, the remaining aspect interpretations proceed, are compiled, in order starting with user's Sun, then user's eight non-Earth planets in order proceeding from the Sun, and user's Moon, based on and as determined by the user/subscriber's set of birth date positions.
In
Utilizing these two sets of planetary position data, all possible aspects are searched for, and the actual aspects being formed between the planets of these two data sets are identified,
There are means to adjusting or calibrating the amount of interpretative remarks which are generated per daily horoscope. For instance, the orb for each or any of the aspects can be adjusted to have a greater or lesser range, whereby increasing or decreasing the likelihood of determining aspects, respectively. Another manner is to use a random chance, e.g. one in two, to trigger a particular aspect interpretation where an aspect has indeed been identified. From an astrological perspective, this makes sense for slow moving aspects, i.e. for aspects formed by the horoscope date's “outer” planets (Uranus, Neptune, and Pluto) to the user's birth planets. Another manner,
Another factor which can affect the selection or application of which planets of the user's planet set to include, pertains to the fact that many people do not know the time they are born. While knowing one's birth date is sufficient to determine, with an accuracy of one degree longitude, the positions of the user's Sun and eight non-Earth planets, the birth date alone, without an accurate input of time of birth, cannot sufficiently determine the position of the user's Moon. The Moon moves through a zodiac Sign (about 30 degrees longitude) about every two days, with the result that a span of some 15 degrees occurs by the Moon's travel each day. Consequently, due to the limitations of many users' knowledge regarding their birth time, the use of the user's Moon in determining aspects may not be feasible in many instances. The minimum planets useable for the user's birth date for aspect identification can, or may, be limited to Sun, Mercury, Venus, Mars, Jupiter and Saturn, as shown in
taking inputs of a user's birth date and a horoscope date;
calculating the set of birth date planet positions from the user's birth date, and calculating the set of horoscope date planet positions from the horoscope date;
searching, determining and identifying the angular aspects, by type, which are made from each birth date planet with respect to each horoscope date planet, by calculating aspect formation;
triggering an interpretation for each determined aspect, specific to the type of aspect and specific planets involved;
compiling or collecting each triggered aspect interpretation into a compiled interpretation, forming user's daily horoscope;
rendering, printing or transmitting user's daily horoscope.
Should the processing of aspect determination be made by if/elseif/else type logic, it is possible to directly couple an interpretation to each type of aspect between each and every planet to planet consideration, by way of a print or send type command. The command effects the applicable interpretation (see
It is also possible to have each identified aspect trigger its applicable interpretation from an interpretation database, wherein the identified aspect is linked to call its applicable interpretation, arrow (1). Such an interpretation database is depicted in basic form in
Arrow (2) represents the path directly from the aspect testing/identifying processor to an interpretation compiler. The interpretation compiler is also reached via the interpretation database. The compiler's purpose is to collect and organize the group of all applicable interpretative statements. Per
From either the interpretation compiler, or directly from the aspect identifying processor, the user's daily horoscope, which comprises the compiled set of applicable interpretations, is rendered as output. The program renders the output to computer screen or printer, or via the internet or by telecommunications.
The middle schematic of the bottom portion of
The bottom schematic of the bottom portion of
Division of application Ser. No. 11/013,275, filed on Dec. 15, 2004, now U.S. Pat. No. 7,083,415, which is a Division of application Ser. No. 10/671,415, filed on Sep. 25, 2003, now U.S. Pat. No. 6,974,325, which is a Division of application Ser. No. 09/849,582, filed on May 5, 2001, now U.S. Pat. No. 6,776,618, which is a continuation of application Ser. No. PCT/US00/28828, filed on Oct. 18, 2000, and a continuation of application Ser. No. 09/421,192, filed on Oct. 18, 1999, now abandoned, which is a continuation of application Ser. No. PCT/US98/13383, filed on Jun. 26, 1998, and a continuation of application Ser. No. 08/883,753, filed on Jun. 27, 1997, now abandoned, said application Ser. No. 09/849,582, filed on May 5, 2001. Provisional Application No. 60/695,027, filed on Jun. 29, 2005, provisional Application No. 60/212,694, filed on Jun. 19, 2000, provisional Application No. 60/208,580, filed on Jun. 2, 2000, provisional Application No. 60/207,450, filed on May 30, 2000, provisional Application No. 60/207,415, filed on May 30, 2000, provisional Application No. 60/207,310, filed on May 30, 2000, provisional Application No. 60/206,603, filed on May 25, 2000, provisional Application No. 60/206,536, filed on May 21, 2000, provisional Application No. 60/205,290, filed on May 19, 2000, provisional Application No. 60/202,038, filed on May 5, 2000, provisional Application No. 60/189,332, filed on Mar. 14, 2000, provisional Application No. 60/181,502, filed on Feb. 10, 2000, provisional Application No. 60/172,651, filed on Dec. 20, 1999, provisional Application No. 60/158,065, filed on Oct. 7, 1999, provisional Application No. 60/144,056, filed on Jul. 16, 1999, provisional Application No. 60/040,442, filed on Mar. 12, 1997.
Number | Name | Date | Kind |
---|---|---|---|
4711632 | Detrick | Dec 1987 | A |
5516289 | Quigley et al. | May 1996 | A |
5775695 | Byers | Jul 1998 | A |
6015295 | Winks, Jr. | Jan 2000 | A |
6108277 | Whitmore | Aug 2000 | A |
Number | Date | Country | |
---|---|---|---|
20060281055 A1 | Dec 2006 | US |
Number | Date | Country | |
---|---|---|---|
60695027 | Jun 2005 | US | |
60212694 | Jun 2000 | US | |
60208580 | Jun 2000 | US | |
60207450 | May 2000 | US | |
60207415 | May 2000 | US | |
60207310 | May 2000 | US | |
60206603 | May 2000 | US | |
60206536 | May 2000 | US | |
60205290 | May 2000 | US | |
60202038 | May 2000 | US | |
60189332 | Mar 2000 | US | |
60181502 | Feb 2000 | US | |
60172651 | Dec 1999 | US | |
60158065 | Oct 1999 | US | |
60144056 | Jul 1999 | US | |
60040442 | Mar 1997 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11013275 | Dec 2004 | US |
Child | 11455901 | US | |
Parent | 10671415 | Sep 2003 | US |
Child | 11013275 | US | |
Parent | 09849582 | May 2001 | US |
Child | 10671415 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US00/28838 | Oct 2000 | US |
Child | 09849582 | US | |
Parent | 09421192 | Oct 1999 | US |
Child | PCT/US00/28838 | US | |
Parent | PCT/US98/13383 | Jun 1998 | US |
Child | 09421192 | US | |
Parent | 08883753 | Jun 1997 | US |
Child | PCT/US98/13383 | US | |
Parent | 11455901 | Jun 2006 | US |
Child | PCT/US98/13383 | US |