Re: Sept 12 & July 20 (past) - (1036) Ganymed NEA
This is a good one, thanks for pointing it out, George.? I should be able to 3 stations for this one.? My only caveat is I do have to travel for work sometime in September--hopefully not that week.
Steve
?
From: George <georvisc@...>
To: OccultNEUS <[email protected]>
Date: Tuesday, 23 July 2024 4:26 PM EDT
Subject: [OccultNEUS] Sept 12 & July 20 (past) - (1036) Ganymed NEA
Who says you can't do interesting observations under a Full Moon...
?
On September 12th Steve Conard (and possibly Roxanne) have a shot at this interesting rock (see Occult4 path). (Others NEUS observers have shots, but they would need to go mobile). It's technically classified as an "NEO/NEA" but it actually comes much closer to Mars. It's also a rock on the ACROSS team list.
The Sept 12 conditions are:?
Combined mag = 9.2 / Max Dur = 4.8 sec / Pred Mag Drop = 0.43 / Alt 54d / Moon 60%, 86d away
?
Interestingly enough I was able to capture it on July 20th - the event being very similar to Sept 30th circumstances. My conditions were:
Combined mag = 10.2 / Max Dur = 4.6 sec / Pred Mag Drop = 0.38 / Alt 67d / Moon 98%, 77d away. (I got a duration of 4.50 sec and drop of 0.25 mag)
[I also got Pos events on July 21st, and 22nd - under the near-Full Moon].
?
(1036) has a highly inclined orbit and it was nice going after a rock that was just exiting the dense starfield of CYGNUS! It was nearly overhead for my observation!
?
It was captured with my 12-inch and using my Astrid (at 33fps - 0.00% timestamp error). Visually I could not see the drop on the computer monitor, but in the PyMovie/PyOTE analysis, the 0.25 mag drop I measured is unmistakable (and to the second of the prediction).
?
I'll also mention an interesting aspect when I went to send Norm my report... For QHY camera events I was told to always send the .log file the camera produces (helps verify the timing was accurate...). In sending my report and using an Astrid I'm also attaching the .log file the Astrid produces. In this case, for this important rock, I recorded for 1.5 minutes on each side of the predicted center-time (running at 33fps). This produced an Astrid.log file of over 14Mb. Some ISP mail systems only still allow attachments up to 10Mb in size. My full report with all needed files was about 17Mb. I have brought this to the attention of Mark Simpson (Astrid) and Steve Preston.
? ? -G
?
|
Re: Sept 12 & July 20 (past) - (1036) Ganymed NEA
Astrid folks:
?
Maybe useful info for some...
?
I had been told that for the QHY, submitting it's .log file was required in a Pos report. (There were times where the timing of the QHY needed to be verified). I wasn't sure if this pertained to the Astrid, so I had been including the Astrid.log file also with my reports.
?
And the official word is........................:
"In general, you should not need to include Astrid¡¯s log file with your report ¨C just archive it with the video file in case it is needed. Best to always keep [archive] the log file¡ to avoid any possible questions or concerns about timing. It is a small addition in size on top of the video file."
"It's only needed in the case where some [of the 4 status buttons] are Red [instead of green]."
?
??? -G
|
Sometimes a MISS can be a good thing...
Oc-folks:
?
Apologies for another post, but there CAN be times it's good to get a MISS (see attached - a "Finder Image" of 75 frames made in PyMovie). Doing analysis on a Pos event and I didn't at first notice this visitor... It just missed wrecking the measurement.
?
...And the other day I was doing an analysis on another Pos event and another (bright) satellite (Elon's?) quickly crossed exactly over a Tracking Star. This had the effect of dragging all the apertures I had set off their "targets" and up to the top of the image's FOV. Proof that PyMovie's tracking feature can work at Warp 9.
?
I fear for the upcoming Rubin Observatory.... There's a lot of debris up there folks.
?
? ? -G
|
Re: Sept 12 & July 20 (past) - (1036) Ganymed NEA
toggle quoted message
Show quoted text
On Tue, Jul 23, 2024 at 4:26?PM George Viscome via <georvisc= [email protected]> wrote:
Who says you can't do interesting observations under a Full Moon...
?
On September 12th Steve Conard (and possibly Roxanne) have a shot at this interesting rock (see Occult4 path). (Others NEUS observers have shots, but they would need to go mobile). It's technically classified as an "NEO/NEA" but it actually comes much closer to Mars. It's also a rock on the ACROSS team list.
The Sept 12 conditions are:?
Combined mag = 9.2 / Max Dur = 4.8 sec / Pred Mag Drop = 0.43 / Alt 54d / Moon 60%, 86d away
?
Interestingly enough I was able to capture it on July 20th - the event being very similar to Sept 30th circumstances. My conditions were:
Combined mag = 10.2 / Max Dur = 4.6 sec / Pred Mag Drop = 0.38 / Alt 67d / Moon 98%, 77d away. (I got a duration of 4.50 sec and drop of 0.25 mag)
[I also got Pos events on July 21st, and 22nd - under the near-Full Moon].
?
(1036) has a highly inclined orbit and it was nice going after a rock that was just exiting the dense starfield of CYGNUS! It was nearly overhead for my observation!
?
It was captured with my 12-inch and using my Astrid (at 33fps - 0.00% timestamp error). Visually I could not see the drop on the computer monitor, but in the PyMovie/PyOTE analysis, the 0.25 mag drop I measured is unmistakable (and to the second of the prediction).
?
I'll also mention an interesting aspect when I went to send Norm my report... For QHY camera events I was told to always send the .log file the camera produces (helps verify the timing was accurate...). In sending my report and using an Astrid I'm also attaching the .log file the Astrid produces. In this case, for this important rock, I recorded for 1.5 minutes on each side of the predicted center-time (running at 33fps). This produced an Astrid.log file of over 14Mb. Some ISP mail systems only still allow attachments up to 10Mb in size. My full report with all needed files was about 17Mb. I have brought this to the attention of Mark Simpson (Astrid) and Steve Preston.
? ? -G
?
|
Hi Rick:
?
Glad to have helped. If you ever have questions don't hesitate to send me a personal email. If I do more sessions I'll let you know.
?
Yes, Occult4 can/will generate good events that you won't find on your OW feeds. If you find an Occult4 event you want to go after, and would like others to see it on OW, then go to the OccultWatcher Cloud web site (do an online search for "OccultWatcher Cloud"), log in, Search for the event (it will probably be there, tho not "published"), Tag it (as a Personal Prediction), and place your observation site on the map. Then "Submit" your proposed observation.
?
Next time you "Resynchronize" your OW Desktop program you should see the site you submitted - as will others near the path.
?
?? -G
?
?
?
?
|
George, Apologies for taking so long to thank you for your occult4 session. Thanks to you, I am now able to generate predictions for myself. I don¡¯t yet know how to transfer a prediction to occult watcher, or even if I should, but the ability to generate predictions is like having my eyes opened. You really did a fantastic job teaching and demonstrating how to operate Occult4 software.
Also, if you do have a another session, I would like to be included. I¡¯m sure There¡¯s still things I could learn. Thanks, Rick Bria?
|
Sept 12 & July 20 (past) - (1036) Ganymed NEA
Who says you can't do interesting observations under a Full Moon...
?
On September 12th Steve Conard (and possibly Roxanne) have a shot at this interesting rock (see Occult4 path). (Others NEUS observers have shots, but they would need to go mobile). It's technically classified as an "NEO/NEA" but it actually comes much closer to Mars. It's also a rock on the ACROSS team list.
The Sept 12 conditions are:?
Combined mag = 9.2 / Max Dur = 4.8 sec / Pred Mag Drop = 0.43 / Alt 54d / Moon 60%, 86d away
?
Interestingly enough I was able to capture it on July 20th - the event being very similar to Sept 12th circumstances. My conditions were:
Combined mag = 10.2 / Max Dur = 4.6 sec / Pred Mag Drop = 0.38 / Alt 67d / Moon 98%, 77d away. (I got a duration of 4.50 sec and drop of 0.25 mag)
[I also got Pos events on July 21st, and 22nd - under the near-Full Moon].
?
(1036) has a highly inclined orbit and it was nice going after a rock that was just exiting the dense starfield of CYGNUS! It was nearly overhead for my observation!
?
It was captured with my 12-inch and using my Astrid (at 33fps - 0.00% timestamp error). Visually I could not see the drop on the computer monitor, but in the PyMovie/PyOTE analysis, the 0.25 mag drop I measured is unmistakable (and to the second of the prediction).
?
I'll also mention an interesting aspect when I went to send Norm my report... For QHY camera events I was told to always send the .log file the camera produces (helps verify the timing was accurate...). In sending my report and using an Astrid I'm also attaching the .log file the Astrid produces. In this case, for this important rock, I recorded for 1.5 minutes on each side of the predicted center-time (running at 33fps). This produced an Astrid.log file of over 14Mb. Some ISP mail systems only still allow attachments up to 10Mb in size. My full report with all needed files was about 17Mb. I have brought this to the attention of Mark Simpson (Astrid) and Steve Preston.
? ? -G
?
[Edited - corrected a typo on a date]
?
|
I'm up here in the Northwoods of Wisconsin (Chippewa Flowage).? The cool night sky has been beautiful and the calling Loons lull one to sleep,?? but alas, no scope this trip.? A small refractor will be at the top of the packing list for next time! - Roxanne
*
On Friday, July 19, 2024 at 11:25:05 AM EDT, Kevin Green via groups.io <greenkevin01@...> wrote:
We are struggling here in New Haven. Both stations were technical failures.?
?
Hopefully we are close to having them running smoothly. Hopefully.
?
|
When I fully processed the airport station data, I found that the fog and/or dewing started to really impact signal level just 20 seconds after the event ended--see the attached .jpg file.? Lucky break for a change!
?
?
Steve
?
From: Steve <conard@...>
To: OccultNEUS <[email protected]>
Date: Friday, 19 July 2024 10:22 AM EDT
Subject: [OccultNEUS] (2173) Maresjev
All,
?
I ran three stations for this event last night, under (mostly) good conditions.? Almost all went according to plan, and I did get 3 positives from this favorable event.? Quick summary (at least my version of quick, be glad I'm not giving the extended version!):
?
- I ran my home observatory, tracking rather than prepoint, as no meridian flip was nearby in time.? The SB MX+ mount tracks nearly perfectly with no meaningful drift--the target stayed centered for the hour and a half between set-up and the event.? The trick for me is I don't trust my dome to rotate on command, as it occasionally binds up (a TI Pro-Dome 10) unfortunately.? I get around this by "prepointing" the dome slot at the correct angle.? This involves all sorts of strange activities which I'll spare you from.? My only issue here was in checking the slot prepoint, I turned the Watec 910's integration up to 8x, and never turned it back down to 2x--resulting in a saturated target.? Still very good data for this long-ish event--so no great harm done.? This was a 4.6 sec positive.
- I set up my middle station at the local airport as I've done a number of times in the past.? I'm comfortable leaving my unattended equipment there, and they have very good horizons.? All went well there for set-up, but when I returned 20 minutes after the event to collect the hardware, it was heavily fogged up, and with the airport beacon lighting up the fog I was worried about getting any data.? When I looked at the C-5's corrector plate, it was also heavily dewed--despite using a heated dew cap (running at 50%).? I thought it was pretty hopeless, but I was able to fairly easily see the target star blink out at event time.? The bright target saved me here.? This was the longest positive at 4.9 s.
- My last station was at Leonard Harrison State Park, on the west rim of the (Pennsylvania) Grand Canyon.? They greatly enlarged their parking lot last year, taking down many trees.? Their renovation also included responsible lighting, so it has a very dark, completely empty parking lot, with good horizons.? This was the first use of my Astrid #2, also mounted to a C-5.? Stupidly, I had never tried that combination in the dark before (Astrid #1 I tried many times on the back porch before trying a remote event).? When I tried to prepoint, I kept getting no result.? Just as panic was ready to set in, I noted that I still had the gain at 1.? As soon as I changed it to 16, all worked as expected and I was able to get on field with no issue.? This one was 4.5 s.
- I was pretty happy with my pre-event time estimates--written out on a note-card in advance.? Set-up at home and the airport took exactly what I allowed, as did the driving (no traffic at 3 AM for some unknown reason).? Set-up at the last station was 10 minutes quicker than expected, but I had allowed extra time as I had not previously used that combination of telescope and Astrid.? Basically I started set-up 2 hours before the event, and I was back in bed after a quick look at the data 1.5 hours afterward.
- Since this was only my second attempt at 3 stations, I was very conservative with my spacing of stations.? Ideally I would have put the airport station elsewhere--either further south (splitting Kevin's Westport and my Harrison locations) or north (between Kevin's Main Campus station and the predicted shadow edge).? But that would have greatly increased my driving, and required me to leave equipment unattended in a location that isn't as secure.? Next time we have an event like this, I'll try to be more aggressive with my chosen locations.
?
?
Steve C
?
?
|
We are struggling here in New Haven. Both stations were technical failures.?
?
Hopefully we are close to having them running smoothly. Hopefully.
?
|
Congrats! Sounds like great planning and great results (despite the inevitable glitches). You learned a bunch too for future efforts.? ...Kevin
All,
?
I ran three stations for this event last night, under (mostly) good conditions.? Almost all went according to plan, and I did get 3 positives from this favorable event.? Quick summary (at least my version of quick, be glad I'm not giving the extended version!):
?
- I ran my home observatory, tracking rather than prepoint, as no meridian flip was nearby in time.? The SB MX+ mount tracks nearly perfectly with no meaningful drift--the target stayed centered for the hour and a half between set-up and the event.? The trick for me is I don't trust my dome to rotate on command, as it occasionally binds up (a TI Pro-Dome 10) unfortunately.? I get around this by "prepointing" the dome slot at the correct angle.? This involves all sorts of strange activities which I'll spare you from.? My only issue here was in checking the slot prepoint, I turned the Watec 910's integration up to 8x, and never turned it back down to 2x--resulting in a saturated target.? Still very good data for this long-ish event--so no great harm done.? This was a 4.6 sec positive.
- I set up my middle station at the local airport as I've done a number of times in the past.? I'm comfortable leaving my unattended equipment there, and they have very good horizons.? All went well there for set-up, but when I returned 20 minutes after the event to collect the hardware, it was heavily fogged up, and with the airport beacon lighting up the fog I was worried about getting any data.? When I looked at the C-5's corrector plate, it was also heavily dewed--despite using a heated dew cap (running at 50%).? I thought it was pretty hopeless, but I was able to fairly easily see the target star blink out at event time.? The bright target saved me here.? This was the longest positive at 4.9 s.
- My last station was at Leonard Harrison State Park, on the west rim of the (Pennsylvania) Grand Canyon.? They greatly enlarged their parking lot last year, taking down many trees.? Their renovation also included responsible lighting, so it has a very dark, completely empty parking lot, with good horizons.? This was the first use of my Astrid #2, also mounted to a C-5.? Stupidly, I had never tried that combination in the dark before (Astrid #1 I tried many times on the back porch before trying a remote event).? When I tried to prepoint, I kept getting no result.? Just as panic was ready to set in, I noted that I still had the gain at 1.? As soon as I changed it to 16, all worked as expected and I was able to get on field with no issue.? This one was 4.5 s.
- I was pretty happy with my pre-event time estimates--written out on a note-card in advance.? Set-up at home and the airport took exactly what I allowed, as did the driving (no traffic at 3 AM for some unknown reason).? Set-up at the last station was 10 minutes quicker than expected, but I had allowed extra time as I had not previously used that combination of telescope and Astrid.? Basically I started set-up 2 hours before the event, and I was back in bed after a quick look at the data 1.5 hours afterward.
- Since this was only my second attempt at 3 stations, I was very conservative with my spacing of stations.? Ideally I would have put the airport station elsewhere--either further south (splitting Kevin's Westport and my Harrison locations) or north (between Kevin's Main Campus station and the predicted shadow edge).? But that would have greatly increased my driving, and required me to leave equipment unattended in a location that isn't as secure.? Next time we have an event like this, I'll try to be more aggressive with my chosen locations.
?
?
Steve C
?
|
All,
?
I ran three stations for this event last night, under (mostly) good conditions.? Almost all went according to plan, and I did get 3 positives from this favorable event.? Quick summary (at least my version of quick, be glad I'm not giving the extended version!):
?
- I ran my home observatory, tracking rather than prepoint, as no meridian flip was nearby in time.? The SB MX+ mount tracks nearly perfectly with no meaningful drift--the target stayed centered for the hour and a half between set-up and the event.? The trick for me is I don't trust my dome to rotate on command, as it occasionally binds up (a TI Pro-Dome 10) unfortunately.? I get around this by "prepointing" the dome slot at the correct angle.? This involves all sorts of strange activities which I'll spare you from.? My only issue here was in checking the slot prepoint, I turned the Watec 910's integration up to 8x, and never turned it back down to 2x--resulting in a saturated target.? Still very good data for this long-ish event--so no great harm done.? This was a 4.6 sec positive.
- I set up my middle station at the local airport as I've done a number of times in the past.? I'm comfortable leaving my unattended equipment there, and they have very good horizons.? All went well there for set-up, but when I returned 20 minutes after the event to collect the hardware, it was heavily fogged up, and with the airport beacon lighting up the fog I was worried about getting any data.? When I looked at the C-5's corrector plate, it was also heavily dewed--despite using a heated dew cap (running at 50%).? I thought it was pretty hopeless, but I was able to fairly easily see the target star blink out at event time.? The bright target saved me here.? This was the longest positive at 4.9 s.
- My last station was at Leonard Harrison State Park, on the west rim of the (Pennsylvania) Grand Canyon.? They greatly enlarged their parking lot last year, taking down many trees.? Their renovation also included responsible lighting, so it has a very dark, completely empty parking lot, with good horizons.? This was the first use of my Astrid #2, also mounted to a C-5.? Stupidly, I had never tried that combination in the dark before (Astrid #1 I tried many times on the back porch before trying a remote event).? When I tried to prepoint, I kept getting no result.? Just as panic was ready to set in, I noted that I still had the gain at 1.? As soon as I changed it to 16, all worked as expected and I was able to get on field with no issue.? This one was 4.5 s.
- I was pretty happy with my pre-event time estimates--written out on a note-card in advance.? Set-up at home and the airport took exactly what I allowed, as did the driving (no traffic at 3 AM for some unknown reason).? Set-up at the last station was 10 minutes quicker than expected, but I had allowed extra time as I had not previously used that combination of telescope and Astrid.? Basically I started set-up 2 hours before the event, and I was back in bed after a quick look at the data 1.5 hours afterward.
- Since this was only my second attempt at 3 stations, I was very conservative with my spacing of stations.? Ideally I would have put the airport station elsewhere--either further south (splitting Kevin's Westport and my Harrison locations) or north (between Kevin's Main Campus station and the predicted shadow edge).? But that would have greatly increased my driving, and required me to leave equipment unattended in a location that isn't as secure.? Next time we have an event like this, I'll try to be more aggressive with my chosen locations.
?
?
Steve C
?
|
Re: Initial Comments on the Review Process
Steve:
Yes, big Thanks for offering to help - especially considering the current sizable backlog of events awaiting review. ...and this is the SLOW season! In August thru October the number of positives usually greatly increases. I would considering helping out if sometime the relentless craziness in my life would let up a bit. I currently have 13 positives awaiting review.
John Moore once gave me the info on doing reviews. There's quite a bit to it. He also sent me a video that describes the process step-by-step (tho I think it was a tad out of date), and also a program which processes some of the review data but it would not run for me. It seemed it was compiled to access specific folders and drives - so it was custom set-up just for just his computer.
In any case, Thanks for helping in the sizable backlog.
??? -G
|
Re: Initial Comments on the Review Process
WOW Steve. Thanks for taking that big next step. That is very generous of you, Rick Bria?
|
Initial Comments on the Review Process
I did the training on the Occultation Review process, "graduated", and have now reviewed 3 batches of 3 (total of 9, with only a single one with multi-chords) in the past week and a half.? What I'm seeing so far is it takes me nearly an hour to do each one (the first several took multi-hours, but I'm software challenged).? I think eventually I'll be able to get that down to between 30 and 45 minutes at best.? So the current rate of positive events (about 3.5 per day for North America) requires several hours per day of volunteer time, not including Norm's time riding herd on it all.? I can understand why they got behind, with only a handful of volunteers and the very quick ramp up in our rate of positives.
?
It is a very manual process--I have a spreadsheet with all the steps on it that I use as a checklist.? It has well over 100 steps, and each with each review I edit it with more detail or new steps depending on what I learn.??
?
?
Steve
?
?
?
|
Steve:
Well, thanks for being a Beta-tester for the newest version!! I was contemplating trying it to see if it might solve the issue I had. 'Guess maybe it might. But be advised that if you run into issues, there IS a way to "revert back". [...And it's one reason I hesitate on updating].
And always follow "George's Rule": Never update an astronomy-related program just before an upcoming clear night. ;-)
-G
|
I loaded the newest version, rebooted my computer, and started the process from scratch--now it works fine.? Another couple of hours of my life I'm not getting back...
?
?
Steve
?
From: George <georvisc@...>
To: OccultNEUS <[email protected]>
Date: Monday, 15 July 2024 1:09 PM EDT
Subject: Re: [OccultNEUS] Occult Problem
Steve:
I've also seen this happen before. However I have yet to get that 3rd line - "The request was aborted: ?Could not create SSL/TLS secure channel." That sounds like an Internet connection issue and not a Horizons issue.
...And I now see there is an even newer version - 2024.7.15. I haven't tried this yet.
I recently had issues with 2024.6.30 - when I ran a User File (generated from a List & Display of initial MPC rocks) and got Horizon-based predictions for the same rocks, it would "complete" (without errors), but I got a very shortened list - only 10% as many events as I would normally get.
I could not "fix" this so I dropped back to an earlier Occult4 version that was known to give me good outputs - 2024.5.27. After reverting back, I've had NO issues.
As a last resort, you can "revert back" to a previous version of Occult4.
Over a year ago I asked Dave Herald for a way to do this and he implemented a means to revert back to previous versions.
Essentially, each time you upgrade Occult4 it stores the original .ZIP file (containing files for the update) in the folder where Occult4 lives - under the subfolder "Updates". You simply copy the Zip file of a previous "good" version to a temporary folder somewhere on your computer, unzip its contents, then copy the unzipped files to the \Occult directory (parent folder of Occult). This will overwrite the new update and revert you back to the previous good version. From then on if you see a brand new update, you can simply update to that just like you normally would.
This may get you back up and running.
Also....... Since Occult4 now is storing all the .Zip files of all past updates, to save file space on your computer you may, every now and then, go to the \Update folder and manually delete very old .ZIP files of very old past updates.
You can see how many past updates are stored on your version of Occult4 by going to the Main Page and selecting "Updates...". For me it says, "8 previous versions are in the subdirectory 'Updates' "
George
|
Steve:
I've also seen this happen before. However I have yet to get that 3rd line - "The request was aborted: ?Could not create SSL/TLS secure channel." That sounds like an Internet connection issue and not a Horizons issue.
...And I now see there is an even newer version - 2024.7.15. I haven't tried this yet.
I recently had issues with 2024.6.30 - when I ran a User File (generated from a List & Display of initial MPC rocks) and got Horizon-based predictions for the same rocks, it would "complete" (without errors), but I got a very shortened list - only 10% as many events as I would normally get.
I could not "fix" this so I dropped back to an earlier Occult4 version that was known to give me good outputs - 2024.5.27. After reverting back, I've had NO issues.
As a last resort, you can "revert back" to a previous version of Occult4.
Over a year ago I asked Dave Herald for a way to do this and he implemented a means to revert back to previous versions.
Essentially, each time you upgrade Occult4 it stores the original .ZIP file (containing files for the update) in the folder where Occult4 lives - under the subfolder "Updates". You simply copy the Zip file of a previous "good" version to a temporary folder somewhere on your computer, unzip its contents, then copy the unzipped files to the \Occult directory (parent folder of Occult). This will overwrite the new update and revert you back to the previous good version. From then on if you see a brand new update, you can simply update to that just like you normally would.
This may get you back up and running.
Also....... Since Occult4 now is storing all the .Zip files of all past updates, to save file space on your computer you may, every now and then, go to the \Update folder and manually delete very old .ZIP files of very old past updates.
You can see how many past updates are stored on your version of Occult4 by going to the Main Page and selecting "Updates...". For me it says, "8 previous versions are in the subdirectory 'Updates' "
George
|
When I click the OK, it just pops up for the next asteroid on the list.? I'm going to try starting a new list from scratch (with reboot in between) and see if that helps--for now I'm dead in the water...
?
Steve C
?
From: Kevin <greenkevin01@...>
To: occultneus <[email protected]>
Date: Monday, 15 July 2024 10:18 AM EDT
Subject: Re: [OccultNEUS] Occult Problem
I get that Horizons notice frequently. It appears to be due to internet connection issues in my case. The screen is very annoying, because it halts the process until the "OK" button is clicked.
?
?
On Monday, July 15, 2024 at 08:54:57 AM EDT, Steve C via groups.io <conard@...> wrote:
?
?
Anyone else having an issue with refining predictions on Occult?? I'm on rev 4.2024.7.12.? When I try to go through the second round to refine the predictions using Horizons with the first list as an input, it pops up an error window saying:
?
Error requesting data from Horizons
Horizons will be skipped for next 20 secs
The request was aborted:? Could not create SSL/TLS secure channel.
?
This started Saturday.? I've tried rebooting, restarting Occult, etc., without success.? I guess the only thing I haven't tried yet is generating a new first list--I'll do that next.
?
Thanks.
?
?
Steve
?
|
I get that Horizons notice frequently. It appears to be due to internet connection issues in my case. The screen is very annoying, because it halts the process until the "OK" button is clicked.
On Monday, July 15, 2024 at 08:54:57 AM EDT, Steve C via groups.io <conard@...> wrote:
Anyone else having an issue with refining predictions on Occult?? I'm on rev 4.2024.7.12.? When I try to go through the second round to refine the predictions using Horizons with the first list as an input, it pops up an error window saying:
?
Error requesting data from Horizons
Horizons will be skipped for next 20 secs
The request was aborted:? Could not create SSL/TLS secure channel.
?
This started Saturday.? I've tried rebooting, restarting Occult, etc., without success.? I guess the only thing I haven't tried yet is generating a new first list--I'll do that next.
?
Thanks.
?
?
Steve
?
|
Steve C
George Viscome
Kevin Hartnett
rickbria22
