Time Matters 0.6.0a Alpha Pre-Release - Windows

[Jim Eshelman]

This may be part of the wider "some midpoint things are known to be not right yet," but thought I'd give a specific while I had it.

The 10/31/24 Liblunar for Washington has the following at the end of the Cosmic State report:

Code: Select all

Ne Pi+ F |
Pl Cp    |

         |    
Angle    |    Sa/Ne 45'd      Ve/Ju 60'd      

[Jim Eshelman]

I've lost track... this one isn't fixed yet, right? (Just recreated it on my U.S.A. chart, also in LAT.) Just making sure it's not a "thought fixed, still there" bug. - It just doesn't like "LAT" in that field. I can spell out "Local Apparent Time" and it's fine with it. (Mistaking a string for a value called LAT?)

Same on Queen Elizabeth I. Is it the OS flag? (No, I recalculate the same chart, marking it Temporary, and unchecking OS, and I get the same error.) NOTE: Just saw the same with John Milton (1608 OS). I'm beginning to think it's the date range itself??

No, wait. I've got it. It's the LAT value in the Time Zone field. I thought this field was purely a label (it obviously doesn't give any numerical information) and previously I've been able to mark a chart LMT and adjust the h/m/s below it. Not now. For some reason, it's rejecting the label LAT.

----------2024-09-22 13:18:18----------
Traceback (most recent call last):
File "C:\Users\mikep\miniconda3\envs\py312_32\lib\tkinter\__init__.py", line 1921, in __call__
File "C:\Users\mikep\miniconda3\envs\py312_32\lib\tkinter\__init__.py", line 839, in callit
File "C:\Users\mikep\Documents\tmsa_git\src\user_interfaces\new_chart.py", line 903, in calculate
File "C:\Users\mikep\Documents\tmsa_git\src\user_interfaces\chart.py", line 123, in __init__
File "C:\Users\mikep\Documents\tmsa_git\src\user_interfaces\chart.py", line 179, in save_and_print
File "C:\Users\mikep\Documents\tmsa_git\src\models\charts.py", line 398, in __init__
AttributeError: 'ChartObject' object has no attribute 'jd'

[Jim Eshelman]

Did inconjuncts (semi-sextile and quincunx) get dropped in some of the refactoring of the aspectarian? I turned them on to check something (with orbs at 1.25/2/3) and they don't appear in my aspectarian. I get this:

Code: Select all

   Class 1 Aspects             Class 2 Aspects             Class 3 Aspects    
Mo sx Ma  1°31'  95%        Mo tr Ve  4°29'  62%        Mo tr Ju  6°13'  29%  
Me co Sa  2°24'  94%        Mo sq Pl  1°57'  56% p      Mo oc Sa  2°33'  26%  
Ve sx Ma  2°57'  83%        Ma op Ju  4°41'  76%        Mo tr Ur  5°56'  35%  
Ve tr Ju  1°44'  94%        Ma op Ur  4°25'  79%        Su sq Ma  6°28'  24%  
Ve tr Ur  1°27'  96%                                    Su co Ne  8°14'  30% M
Ve sq Pl  0°13' 100%                                                          
Ma sq Ne  0° 7' 100% M                                                        
Ju co Ur  0°17' 100%                                                          
Ju sq Ne  2°16'  90%                                                          
Ur sq Ne  2° 0'  92%                                                          
Ne sx Pl  0°46'  99%

With these settings, there should also be:

Venus-Neptune in 0°32'
Uranus-Pluto in 1°14'
Jupiter-Pluto in 1°31'

[Mike V]

I've lost track... this one isn't fixed yet, right? (Just recreated it on my U.S.A. chart, also in LAT.) Just making sure it's not a "thought fixed, still there" bug. - It just doesn't like "LAT" in that field. I can spell out "Local Apparent Time" and it's fine with it. (Mistaking a string for a value called LAT?)

Correct, that is not fixed yet.

Did inconjuncts (semi-sextile and quincunx) get dropped in some of the refactoring of the aspectarian? I turned them on to check something (with orbs at 1.25/2/3) and they don't appear in my aspectarian. I get this...

I totally forgot that these existed because I never use them. I'll have to add these into the aspect calculation.

[Jim Eshelman]

I never use them either (except today when I was going to use them LOL). They were added simply because they're part of the larger aspect paradigm that a lot of people still use, so they should be an option.

Art the moment, I'm curious to watch for a while to see how easily the orb can be discerned between the closest (which are really 10° multiple Novien-based aspects) and the anti-aspect characteristic of the inconjunct. I'd never watched that super-closely even though the components of that have been evident enough.)

[Mike V]

Here's a small patch, 0.6.0a8. https://mega.nz/file/gXskUCQI#qjgCfwion ... wQb4gFOsPs

This fixes:
Planets on Av are no longer mistakenly listed as being on Vx.
Entering "LAT" in the timezone field now correctly calculates LMT.
PVP aspects are now turned on by default for ingresses.

Bugfixes still pending:
- A bunch of miscellaneous midpoint bugs that I haven't had brainpower to tackle
- Precess natal angles in return charts (it's not the calculations that are making this take longer; it's finding a logical way to model and access this stuff without breaking backwards compatibility in the data files)
- Add semi-sextile and quincunx back into aspect calculation
- Set default ingress options to have "other partile" off by default (sorry I missed this one before uploading alpha 8 here)
- Add stationary to Cosmic State - coming back to it again, I think I agree with having Stat. in the dignity row instead of an S in the planet section header thingy.

[Mike V]

Added a button on the main page to show the error file...

Nice! (Like real software <g>.) -- I'm curious, when does this clear? (Perhaps at each new version install it's deleted? I doubt it times out.)

I realize I never answered this question. Currently, there's no code to automatically clear that file, although it can easily be done manually (just CTRL + A and then delete, and save it... or delete the file). I can look into wiping it on install if that seems like the best cleanup cadence. I'll have to get a little creative with that.

[Jim Eshelman]

I'm curious, when does this clear? (Perhaps at each new version install it's deleted? I doubt it times out.)

I realize I never answered this question. Currently, there's no code to automatically clear that file, although it can easily be done manually (just CTRL + A and then delete, and save it... or delete the file). I can look into wiping it on install if that seems like the best cleanup cadence. I'll have to get a little creative with that.

I don't think this is high priority, especially if you have to get creative with it. (I thought it would be simple: Near the top of the install process, delete the file.)

It's unlikely to get too large for the hard drive or for Notepad to manage, especially after 1.0 is stable. My suggestion was more a matter of "rightness." As all errors are necessarily version specific, it seemed "right' that each version installed begins with a clean error slate.

So don't worry about it. - One suggestion, though (since all errors are necessarily version specific and some people - like you and me - could start wandering through old error logs), perhaps output the version number into the log entry? (Am I paying too much attention to this thinking that some people are going to go digging through the error logs out of curiosity?)

I just installed alpha-8 and updated the link. Off to test.

[Jim Eshelman]

Checking alpha-8. (Thanks for the quick patch.)

Planets on Av are no longer mistakenly listed as being on Vx.

Confirmed on my natal.

Entering "LAT" in the timezone field now correctly calculates LMT.

Confirmed fixed on U.S.A. chart. (To be picky, it doesn't calculate in LMT but in LAT .) Also confirmed on natus of Queen Elizabeth I.

PVP aspects are now turned on by default for ingresses.

Confirmed: Deleted Ingress_Default.opt, closed and relaunched program. New file created with PVP aspects enabled.

Bugfixes still pending:
A bunch of miscellaneous midpoint bugs that I haven't had brainpower to tackle

If you need any help "clarifying the question," ask.

Add stationary to Cosmic State - coming back to it again, I think I agree with having Stat. in the dignity row instead of an S in the planet section header thingy.

Planet section header thingy? You mean the leader label (I just made that up! <g>) in each CS row?

Another thing still off is that RA of MC and EP are 180° off. (We're seeing RA IC and WP.) In practice, this isn't a problem since my brain drops all but the last digit to do the mental subtraction, but of course it needs to be fixed at some point. (This popped up when you fixed RA EP to be 90° more than RA MC - which it is! - and, somehow, RA MC got the 180° added before that calculation.)

E.g., MC of 2° Gemini is Tropical 26° Gemini, so it's RA will be a few degrees earlier than 6h = 90°. Center of chart wheel correctly gives RAMC 85°31'. Here's the table. - Declination is wrong on all but MC.

Code: Select all

      Long     Lat   Speed    RA     Dec    Azi     Alt      ML     PVL    Ang  
Mc  1Ge46'20" ............. 265°31' 23N23 180° 0' +72°19' ....... 270° 0'  ...
As  2Vi20'25" ..................... 10N39 .......   0° 0' .......   0° 0'  ...
Ep  1Vi 0' 7" ............. 355°31' 11N 7 ....................................
Vx 26Aq12' 1" ..................... 12S47 270° 0' - 5°51' ....................

[Mike V]

I don't think this is high priority, especially if you have to get creative with it. (I thought it would be simple: Near the top of the install process, delete the file.)

It's unlikely to get too large for the hard drive or for Notepad to manage, especially after 1.0 is stable. My suggestion was more a matter of "rightness." As all errors are necessarily version specific, it seemed "right' that each version installed begins with a clean error slate.

So don't worry about it. - One suggestion, though (since all errors are necessarily version specific and some people - like you and me - could start wandering through old error logs), perhaps output the version number into the log entry? (Am I paying too much attention to this thinking that some people are going to go digging through the error logs out of curiosity?)

It's the "near the top of the install process" part that makes this a bit more challenging - I don't actually directly control the installer. cx_freeze creates an installer based off of some setup that I give it, so I don't believe that I can run arbitrary code very easily using it. I'm sure there's some way to do things like this, but it's not clear to me how.

I think adding the version number would be great. There's no harm in it, only help. People can certainly go down that rabbit hole!

[Jim Eshelman]

Rev. Jim Jones, May 13, 1931, 10:00 PM CST. Lynn, IN

In the main data section, Saturn is correctly marked "Ea" and 97% strength: It is the most angular planet, 1°01' from EP in RA.

In the Cosmic State report, it is marked background, though the Needs Hierarchy score gives it full credit for the 97% strength from the angularity.

Code: Select all

      Long     Lat   Speed    RA     Dec    Azi     Alt      ML     PVL    Ang  
Sa 29Sg24'27"  0N14 - 1' 2" 294°59' 21S14 107°10' -12°44' 356°11'  13°19'  97% Ea
Ep  0Cp19'24" ............. 116° 0' 23S27 ....................................
---------------------------------------------------------------------------------
                                  Cosmic State                                   
Sa Sg  B  97%| Su Ar-
             | tr Su  0°47'    sq Ve  1°32'    op Pl  2°20'M   op Ju  3°41'M   
             | sq Me  3°41'M   sq Ur  5°47'    

[Jim Eshelman]

As you know, I almost never consult Moon's Node (so I hadn't had a chance to check this). I just noticed that TM current version doesn't display the node.

Donald Trump was born at a lunar eclipse. I wanted to see how close Node was, so I went into Temporary and added true node. On recalculating... it's not there. (Confirmed on a couple of other charts.)

Mean Node - same thing.

The .dat file has both Mean and True Node regardless of whether they are requested. (I'm not sure where the flag is that determines if they are displayed.)

Code: Select all

"Mean Node": [
        56.76908464938329,
        0.0,
        -0.05299205622629489,
        79.94106604351146,
        23.12422685343077,
        118.30541977158265,
        60.69435202630059,
        40.19007154855939,
        296.29811329718444
    ],
    "True Node": [
        56.81616868658274,
        -4.4801628733903814e-18,
        -6.46472473060865e-05,
        79.99214097358123,
        23.12749079987455,
        118.23462237746423,
        60.6624948331266,
        40.08842151191527,
        296.34289695846746
    ]

[Mike V]

By the way, thank you (all, but especially Jim) for being patient with this last suite of bugs. I have been very busy in my personal life, and also super burnt out on dev work, so all of my focus has been going towards keeping the lights on at work so to speak. I always recover from running out of dev fuel in a relatively short amount of time, so I'll get back to this soon.

As a reminder for everyone, you can see the current status of bugs and features on my Trello board - https://trello.com/b/NpRZTYxh/tmsa-roadmap

As you know, I almost never consult Moon's Node (so I hadn't had a chance to check this). I just noticed that TM current version doesn't display the node.

Donald Trump was born at a lunar eclipse. I wanted to see how close Node was, so I went into Temporary and added true node. On recalculating... it's not there. (Confirmed on a couple of other charts.)

Mean Node - same thing.

Yeah, now that you say that, I see that I totally forgot to wire up Node into the list of calculated planets when I refactored how that code worked. I'll include that one when I get back to bugfixing; should be very easy.