Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ABer

Pages: 1 2 3 [4] 5 6 ... 36
46
Planetdance for windows / Re: Tyl-Chart-Synthesis
« on: April 10, 2022, 07:27:09 AM »
Hi there - if you are a regular user of this module please update. I have released a bug fix.

v.2.03 - bug fix for Aries Midpoints routine.

Thanks Volker.

Ed

47
Classic, Medieval, Vedic / Re: New Horary Module
« on: April 07, 2022, 10:00:07 PM »
Thanks Jean - for reference its v.4.56 released today.

49
Classic, Medieval, Vedic / Re: New Horary Module
« on: April 07, 2022, 08:54:11 PM »
Hi Jeremy - I have fixed the bug you found. Jean will release the update soon. Thanks. Ed

50
Classic, Medieval, Vedic / Re: New Horary Module
« on: April 07, 2022, 08:01:05 PM »
Hi Jeremy - thanks for the feedback again. I'm not in a position to make major changes to this module at the moment.

I can look at the potential bug with the latitude calculation.

I don't quite understand whether you are interested in a separate election module or not. This is something I have planned to do but I don't see it happening for quite a while.

Ed

51
Classic, Medieval, Vedic / Re: New Horary Module
« on: April 06, 2022, 08:50:36 AM »
Hi Jeremy - thanks for the feedback. However I am not quite sure what you mean by your comments. I have been working on this significant update to the horary module for a long time. There has been a separate horary module in PD for a number of years now, but the original versions were always quite basic as the programming is complicated in some areas. I've now improved it, but recognise that there may be some further work to do.

Ed

52
Astrobasic / Re: getplanet
« on: April 01, 2022, 10:27:08 PM »
Hi Jean - I've got it working, but the script needs a lot of sorting out. Overly complicated really. Ed

53
Astrobasic / Re: getplanet
« on: April 01, 2022, 09:00:34 PM »
Thanks Jean - I'll take a look at it. Ed

54
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);}

55
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

56
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

57
Astrobasic / Re: getplanet
« on: March 31, 2022, 09:16:13 PM »
Thanks Jean. Ed

58
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

59
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

60
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.

Pages: 1 2 3 [4] 5 6 ... 36