Am on the road and cannot back up the whole laptop. Is it possible to just back up EO version 3.7 and if so, could you advise how to do that?

Xavier Jubier Eclipse Timing vs Eclipse Orcestrator - off by 4+ seconds
#26
Posted 16 March 2024 - 03:08 PM
#27
Posted 16 March 2024 - 03:25 PM
Did you want to try a newer version of EO just for the updated Delta t value? If so can't you edit the file mentioned above? Or just delay things 4 or 5 seconds yourself?
#28
Posted 16 March 2024 - 04:37 PM
Jubier's map and calculator agree within half a second or so, if you enter the same coordinates. And they agree quite well with your EO table. You have to be careful about minutes/seconds/fractions of a degree.
Indeed I do . My error was entering fractional portion of the coordinates from Xavier's map into the calculator which it silently accepted but converted to a different position. Entering via the Lat/Lon DMS converter gives me the correct co-ordinates and I now match between the map, calculator and EO.
Thank you folks.
#29
Posted 17 March 2024 - 03:52 PM
Make a Windows Restore point. They can be made anytime and don't require external storage. Then install the new version. If it doesn't work, revert to the Restore point and you will have the old version installed again.
#30
Posted 17 March 2024 - 09:36 PM
Make a Windows Restore point. They can be made anytime and don't require external storage. Then install the new version. If it doesn't work, revert to the Restore point and you will have the old version installed again.
That rings a bell that I have done that before. On its face, unless you and I are missing something, that make sense.
#31
Posted 18 March 2024 - 01:24 PM
The estimates of C2 and C3 times between SEM and such authoritative sources like the Navy offers here: https://aa.usno.navy...lipse2024#forma also differ by about 3 or 4 seconds.
Small variations from changing the solar radius as Xavier recommends do not make up the difference. Nor does changing elevation. Have not yet checked limb corrections or looked into delta_T. Would like to have a definitive answer at some point ... like everyone else on this thread.
#32
Posted 18 March 2024 - 02:53 PM
Okay, it looks like the Navy eclipse calculator https://aa.usno.navy...a/SolarEclipses uses delta_T = 72.8 while SEM uses 69.2, a difference of 3.6, which is the difference in their estimates of the max-eclipse time to within 0.1s. However, SEM predictions differ from Jubier's analysis applied to a Google map, http://xjubier.free.....0&Zoom=17&LC=1 by a lot as well.
SEM C2 = 18:40:07.6; max = 18:42:02.9; C3 = 18:43:53.7
Jubier map with same coordinates C2 = 18:40:10.4; max = 18:42:06.1; C3 = 18:44:01.9
the differences being dC2 = 2.8 (SEM early); dmax = 3.2 (SEM early); dC3 = 8.2 (SEM early)
Oh well, until I hear otherwise, I'm going to use SEM calculations.
#33
Posted 18 March 2024 - 05:27 PM
It's a bit odd that that USNO calculator site uses such a large (presumably old) Delta t value, when it's the same USNO that supplies the latest Delta t values.
About SEM, Jubier's map website doesn't include lunar limb corrections, but I'm not sure about SEM. Can you switch off any limb corrections in SEM and see how that changes the timings?
#34
Posted 20 March 2024 - 06:39 AM
Using the default/recommended values for EO v3.9.1 and matching Jubier's Lat/Lon/Alt, I get the following differences:
---- EO----- ---Jubier--- -Dif-
C1: 17:11:30.3 17:11:31.3 +1.0
C2: 18:28:47.4 18:28:46.4 +1.0
Max: 18:30:55.4 18:30:55.5 +0.1
C3: 18:33:01.7 18:33:04.6 +2.9
C4: 19:52:24.3 19:52:23.4 -0.9
Big difference at C3, everything else is close. Should I be concerned?
JohnD
#35
Posted 20 March 2024 - 10:56 AM
#36
Posted 28 March 2024 - 12:58 AM
When it comes to deltaT, write this down.
deltaT = 69.184 - DUT1
The value of DUT1 currently equals -0.013213 (March 27, 2024)
Therefore, currently deltaT = 69.197213
The current value of DUT1 can be found here under UT1-UTC:
https://hpiers.obspm...op-pc/index.php
#37
Posted 28 March 2024 - 08:43 PM
I am confused with all these responses. Is there agreement amongst the posters that a setting in the last/ most recent version of Eclipse Orchestrator Pro should be changed and if so how? Thank you.
#38
Posted 28 March 2024 - 11:03 PM
A new version of Eclipse Orchestrator has just been released. It has current deltaT values. More info here:
https://www.cloudyni...-28/?p=13355453
#39
Posted 29 March 2024 - 10:13 PM
Do not want to dare installing a new version of EO now that I have the previous version working. That being said, is there a way to alter the Delta T value easily in the prior version?
#40
Posted 30 March 2024 - 12:26 AM
Did you try the procedure to edit the Delta t value in this post: https://www.cloudyni...nds/?p=13327968?
#41
Posted 30 March 2024 - 11:19 PM
So no one knows of a way to keep 2 different versions of Eclipse Orchestrator on the same laptop. I am scared to death with all of the problems I have had this time with EO getting to recognize my camera (compared to 2017), that if I install the newer version 3.9, that if 3.9 does not work and I try to uninstall it, I might not be able to remove all the remnants of it and not be able to get version 3.7 to work again.
I was having an issue with my computer and EO recognizing my 70D. I went into device manager and under USB removed the Canon camera (forget exact wording) and did the same under portable devices (if your camera is showing up there which it should be). Turn camera off, then turn it back on. Your computer should recognize the camera. Check in device manager again and it should show up in "portable devices".
Then see if EO sees the camera.
#42
Posted 31 March 2024 - 01:28 PM
I don’t really care about Bailey’s Beads so I’m thinking I might catch the diamond ring manually (with a remote) and then let SEM snap away during totality.
#43
Posted 08 April 2024 - 04:25 PM
I just discovered this thread after searching about my EO timing being off in this eclipse. It worked perfectly in 2017 but missed the crucial shots this time. I guess I should have known to look for an update.