Messages

31

Astrobasic / Re: getplanet

« on: April 01, 2022, 08:20:34 PM »

Hi Jean - this works now:

move(planet, planetsPlus, PLANETS * REAL);
 
  ` getplanet array
  i = 0; for (i < 8 ){
    getplanet(i + 37, 3, hold);
    r = hold[0];
    planetsPlus[i + 16] = r;}
   
  `  solar arc - horoscope #3
  sethoroscopetime(3, jd + 20000, zone);
  progression(0, 3, 1);
  getplanets(3, saPlanet);
  move(saPlanet, dirPlusTNPsSA, PLANETS * REAL);
 
  ` r = arc of sun
  r = normalize(dirPlusTNPsSA[0] - planetsPlus[0]);

  ` add arc sun to original position of tnps
  i = 0; for (i < 8 )
    dirPlusTNPsSA[i + 16] = normalize(planetsPlus[i + 16] + r);
   
  i = 0; for (i < 24){
    if (i < PLANETS)
       putplanet(10, 10 + i * 20, i);
    else
        objectsymbol(10, 10 + i * 20, i + 5);
    putrealnumber(40, 10 + i * 20, planetsPlus, 4);
    putrealnumber(140, 10 + i * 20, dirPlusTNPsSA, 4);
    ` for solar arc this difference should be the same for all planets
    r = normalize(dirPlusTNPsSA - planetsPlus);
    putrealnumber(240, 10 + i * 20, r, 4);}

32

Astrobasic / Re: getplanet

« on: April 01, 2022, 06:23:34 PM »

Hi Jean - I'd come to the same conclusion, here is a test file to look at. You will note that all planets are directed by solar arc by the same amount, but when it comes to the TNPs they don't seem to match. Not sure what's going on.

window(800, 600);
menu(0, "Close", close);
menu(0, "Help", NULL);
menu(2, "English", help);
menu(2, "Dutch", helpnl);
real planet[PLANETS], house[HOUSES], planetsPlus[24], saPlanet[PLANETS], dirPlusTNPsSA[24], hold[6], jd, lon, lat, r;
int time[6], i;
char inifile[256] = "xxx.ini", s[99];
@load;
onclose(save);
copyhoroscope(-1, 0);
getname(0, s);
setcaption(s);
gethoroscopetime(0, time, jd);
real zone = gethoroscopetimezone(0);
getlonlat(0, lon, lat);
getplanets(0, planet);
gethouses(0, house);
@go;
run;

:go;
  visible(0);
  fill(0, 0, width, height, -2);
 
  move(planet, planetsPlus, PLANETS * REAL);
 
  ` getplanet array
  i = 0; for (i < 8 ){
    getplanet(i + 37, 3, hold);
    r = hold[0];
    planetsPlus[i + 16] = r;}
   
  `  solar arc - horoscope #3
  sethoroscopetime(3, jd + 20000, zone);
  progression(0, 3, 1);
  getplanets(3, saPlanet);
  move(saPlanet, dirPlusTNPsSA, PLANETS * REAL);

  ` getplanet array
  i = 0; for (i < 8 ){
    getplanet(i + 37, 3, hold);
    r = hold[0];
    dirPlusTNPsSA[i + 16] = r;}
   
  i = 0; for (i < 24){
    if (i < PLANETS)
       putplanet(10, 10 + i * 20, i);
    else
        objectsymbol(10, 10 + i * 20, i + 5);
    putrealnumber(40, 10 + i * 20, planetsPlus, 4);
    putrealnumber(140, 10 + i * 20, dirPlusTNPsSA, 4);
    ` for solar arc this difference should be the same for all planets but it doesn't seem to be
    r = normalize(dirPlusTNPsSA - planetsPlus);
    putrealnumber(240, 10 + i * 20, r, 4);}
   
  visible(1);
  return;

:close;
  quit;

:help;
  help("Help ", "");
  return;
:helpnl;
  help("NL Help", "");
  return;

:load;
  fileopen(inifile, FILEREADAB);
  fileread(time);
  fileclose;
  return;

:save;
  fileopen(inifile, FILEWRITEAB);
  filewrite(time);
  fileclose;
  return;

Ed

33

Astrobasic / Re: getplanet

« on: April 01, 2022, 09:19:58 AM »

Hi Jean - thanks for the feedback. I'm going to have another go at this. I've got a new idea. Ed

34

Astrobasic / Re: getplanet

« on: March 31, 2022, 09:16:13 PM »

Thanks Jean. Ed

35

Astrobasic / getplanet

« on: March 31, 2022, 09:09:00 PM »

Hi there - I'd be grateful for any comments on the following code. I am working on script for Uranian astrologers that will be distributed outside Jean's main download. I need to get the directed solar arc positions of the eight trans-neptunian planets used by Alfred Witte. These are:

37 Cupido
38 Hades
39 Zeus
40 Kronos
41 Apollon
42 Admetos
43 Vulkanus
44 Poseidon

(from the getplanet function help).

Firstly the code gets the directed ('progressed') positions for the main PLANET array and moves them to an array called dirPlusTNPs which has 24 positions.

set(dirPlusTNPs, -1000); ` sets each of 24 positions in the array to -1000

` solar arc - horoscope #3
  sethoroscopetime(3, jdDir, zone);
  progression(0, 3, 1);
  getplanets(3, saPlanet);
  move(saPlanet, dirPlusTNPs, PLANETS * REAL); 

Then using the getplanet function, the eight TNPs are put into an 8 x 6 array. The horoscope used is #3, the one calculated by the first progression function (progression(0, 3, 1).

  ` getplanet array
  i = 0; for ( i < 8  )
    getplanet(i + 37, 3, tnpDirOutput);

The third part of the code, moves the eight TNPs into the last eight positions in the dirPlusTNPs array based on identify those remaining positions that are occupied by the value -1000.

  ` put tnps into array, last eight positions are -1000
  i = 0; for (i < 24){
    if (dirPlusTNPs < -500)
        dirPlusTNPs = tnpDirOutput[i - 16][0];}

The longitude position in the getplanet array is 0.

This works, in the sense that it runs, but it doesn't appear to identify the correct longitudes for the eight directed positions of the TNPs.

Does anybody have any advice on whether getplanet can be used for this purpose, or do I have to do something else, or is there an error in the code?

Thanks.

Ed

36

Planetdance for windows / Re: Astrocartography questions

« on: March 25, 2022, 10:16:10 PM »

HI Lisha - the 'correct' chart for the US has been contested by astrologers for years. It is an area of great controversy. The 17:10 chart is known as the Sibly variant. It is a popular one. I am less familiar with the variant used in the video. If you want to know more about the range of charts for the US, I refer you to Nicholas Campion's Book of World Horoscopes, where he covers the subject in great detail. I also refer you to the volume Astrological American (AFA Research Bulletin no. 3), where a number of topics relating to the astrology of the US are covered. In this volume they describe this 2.00PM horoscope as the Gaillard Hunt variant.

A further difficulty in calculating the orbit of Pluto, and hence it's return to any particular degree, is that it has a highly elliptical orbit and has only been observed since 1930, so there is some uncertainty in the algorithms used to calculate its position. Planetdance uses the Swiss Ephemeris, which is very accurate, but in relation to Pluto the programmers say: With the outer planets, Standish's diagrams show that there are large differences of several ” (seconds) around 1600, and he says that these deviations are due to the inherent uncertainty of extrapolating the orbits beyond the period of accurate observational data. The uncertainty of Pluto exceeds 1” before 1910 and after 2010, and increases rapidly in more remote past or future.

So the further one goes back into the past, or further into the future, the more inaccurate the position of Pluto becomes, and more uncertainty surrounds calculations of things like return positions.

It's a very complicated subject.

With respect to adding maps to PD, it's also complicated because they have to use a certain projection. A map is the sphere squashed into two dimensions, and the way that this is done influences the way the landmasses are shown and the relationships between places. The PD astro-mapping module is really designed to be a basic introduction to the subject and it would be extremely complicated to develop the script further.

Ed

37

Planetdance for windows / Re: Astrocartography questions

« on: March 25, 2022, 09:04:20 PM »

Using the 6.27AM time for the return, I get the same as the alternative software. My is that this is not about the software, whichever you use, but variation in the time for the natal chart and the time for the return.

38

Planetdance for windows / Re: Astrocartography questions

« on: March 25, 2022, 08:59:57 PM »

Hi Lisha - first thing to check is that we are using the same natal chart. See attachment.

I get Pluto in this chart at 27 CP 33 18.

39

Planetdance for windows / Re: Adding TNPs to Cosmobiology Module

« on: March 25, 2022, 08:02:55 PM »

HI there - thanks for using Planetdance. At the moment I don't intend to add the fictional planets to the Cosmobiology Module. This is intended to be a pure representation of Ebertin's methods, at least as far as I understand them, and he did not use the TNPs.

I'll bear it in mind, but it's not something that would be a high priority.

Ed

40

Planetdance for windows / Re: Astrocartography questions

« on: March 25, 2022, 08:00:59 PM »

Hi there - it's difficult to answer without the chart data. Could you post the date/time etc of the two charts.

Also, it would be helpful to know the data you are using for the US chart.

The other factor is that Pluto is a slow moving planet and, hence, pinning down the exact moment of the return is much more difficult.

Thanks. Ed

41

Planetdance for windows / Re: Harmonic Chart Analysis - Significant New Update

« on: March 21, 2022, 12:49:06 PM »

Hi again - there is minor improvement to one of the data tables in the latest release just updated. Thanks. Ed

42

Planetdance for windows / Harmonic Chart Analysis - Significant New Update

« on: March 20, 2022, 07:30:05 PM »

Hi there - this was one of my earliest scripts and very much due for an update.

20 March 2022

Horoscope-Harmonics-Harmonic Chart Analysis: v. 5.38 - major update, includes harmonic chart display, removed graphs, graphic ephemeris, aspect table, dynamic date change, includes data tables.

The module includes a new helpfile and has been totally re-written.

If you are a regular user of harmonic charts please update your installation to get the latest version of this script.

See attachments for screenshots.

From the Helpfile:

This routine calculates the first 15 harmonics, including the natal chart (harmonic one), and presents data in a tabular format and harmonic charts.

Users can also display a graphic ephemeris for each harmonic, focusing on the six months before and six months after the chosen date. The date may be altered by adding the preferred day, month and year in the boxes in the top right of the screen and clicking Calculate.

Harmonic transit postions for the chosen harmonic are shown around the outer wheel.

Two chart scopes are shown in the bottom left: the natal positions scope and the harmonic positions scope.

The table on the main screen shows the angular distances between planets and points in the natal chart that are relevant to the chosen harmonic.

A further data table can be shown from the menu - click Harmonic Aspect Summary. This table shows the number of times the planet pairing appears in harmonics 1-15. The colour coding is as follows:

Yellow - 1-5 times
Red - 6-10 times
Green - more than 10 times.

A high number of appearances in this table shows a planet pairing that is very exact in the natal chart (less than 1 degree orb).

Users can also examine the Harmonic Pairs Summary table. This identifies the specific harmonic charts in which each pair of planets/points appears.

Thanks for your interest.

43

Planetdance for windows / Re: Astrocartography questions

« on: March 17, 2022, 05:50:48 PM »

Hi Lisha - thanks for your interest in this module. To answer your questions:

The three green horizontal lines are (from top to bottom): the Tropic of Cancer, the equator, the Tropic of Capricorn.

The scale running through the centre of the display represent lines of longitude east and west of the Greenwich meridian.

I am not actively developing this module at present so I don't see that I would be adding the TNPs in the future.

All the best. Ed

44

Astrobasic / Re: I wish for a new video this year

« on: March 07, 2022, 08:50:39 PM »

Thanks for the tip Jean!

45

Astrobasic / Re: I wish for a new video this year

« on: March 06, 2022, 10:17:18 AM »

Thanks Jean.

Volker - here is an alternative for you to compare to Jean's code. Jean's code is much more sophisticated than mine!

window(1200, 800);
circle(600, 400, 360, -1);

int x, y, m, n, i, j;

visible(0);

i = 0; for (i < 4){
  j = 0; for (j < 7){
    if (j % 7 = 0){
       m += 10 * 3;
       putnumber(0, n * 20, 10 * 3);}
    else
        {m += 10;
         putnumber(0, n * 20, 10);}
    getcirclepos(600, 400, 360, m, x, y);
    line(600, 400, x, y, -1);
    getcirclepos(600, 400, 375, m, x, y);
    putnumber(x - 10, y - 10, m % 360);
    n += 1;}}
   
visible(1);
 
run;