If the Sun steps here

It occurred to me, while I was watching Sisyphus roll his boulder, the Sun, up the hill of the ecliptic through February into March, that on that slope I could mark annual events such as holidays, a.k.a. festivals. They are tied to positions in our solar calendar, even though for many of them those positions are determined by the Moon as well as the Sun.

So here is how the Sun chart in Astronomical Calendar 2024 could have looked.

– with some dates that fall in the southerly half of the Sun’s year: Ash Wednesday (which is the day after tomorrow), the first day of Ramadan, and Rosh Hashanah (Jewish new year). In 2025 they will be at different dates: March 5, March 1, and September 22.

There are of course many other annual events. They can be divided into several kinds according to the way they have to be calculated: fixed days in the year (such as Christmas); the “weekday in month” type (such as Thanksgiving and the clock-changing dates); Easter and those that are determined by its date (such as Ash Wednesday); days in other calendars, such as the Jewish and Muslim.

I at first thought of including many kinds in the chart, color-coded as to their kinds – gray for fixed dates, green for Muslim? But that makes crowing and overlapping.

You would scarcely believe – I can scarcely believe  – the intricacy of the programming it took to add this seemingly simple feature to the chart – mainly because I insisted on breaking the labels for the names of the events into two if they consist of more than one word, and positioning them on the other side of the ecliptic if there is more space there, as in the other half of the Sun chart.

The most powerful word in the programming language, perhaps in any language – the word that has most consequences – is IF.

I think I read that there is a sort of purist version of Fortran called IfTran, in which “go to” statements are avoid and all branching in the program is handled by “if” statements.

__________

This weblog maintains its right to be about astronomy or anything under the sun.

ILLUSTRATIONS in these posts are made with precision but have to be inserted in another format. You may be able to enlarge them on your monitor.

One way: right-click, and choose ”View image” or ”Open image in new tab”, then enlarge. Or choose ”Copy image”, then put it on your desktop, then open it. On an iPad or phone, use the finger gesture that enlarges (spreading with two fingers, or tapping and dragging with three fingers). Other methods have been suggested, such as dragging the image to the desktop and opening it in other ways.

Sometimes I make improvements or corrections to a post after publishing it.  If you click on the title, rather than on ‘Read more’, I think you are sure to see the latest version. Or you can click ‘Refresh’ to get the latest version.

 

3 thoughts on “If the Sun steps here”

    1. t may be Fortran 77, but I have no easy way to find out. I am hazy about that terminology and don’t have to think about it any more.
      After leaving Furman, whose computer department used some powerful form of Fortran, I was using a Microsoft Fortran, which in 2014 became unusable (as did the Basic I was using) in Windows 7 because of a change to 64-bit, whatever that means.
      I had to search around, and acquired Simply Fortran from Jeffrey Armstrong, who calls his enterprise Approximatrix. I think that has its own compiler, called gfortran.
      I constructed a short batch file (which I call batfor.bat), with abbreviations learned from helpful Jeffrey for the operations. So all I have to do when creating or re-creating an executable program is to type at the command prompt e.g.: batfor tim. The compityer will then read and interpret my source file tim.for, and tyoing “tim” will run it.

  1. “Real Programmers Don’t Use Pascal” said the article published way back in 1983. At that time we used to say that real programmers only used Fortran, even for things where other languages were better. Hey, if it worked for NASA…

    Yet I still recall the many hours spent pouring over highly cryptic printouts littered with GO TO statements. For the same reason IFTRAN’s author decided to create this variant I too did the same thing. Obviously when FORTRAN-77 came out we all converged to that.

    I enjoy seeing the contortions you have to go through to make the graphs and drawings perfect to your liking. These days I’ve moved to the latest JavaScript version and P5.js as my goto (pun intended) toolbox.

Write a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.