¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Tale of 2 Occultations (subtitle - Occult4 201)


 

George,
?
Thanks for this.? It ties in well with my goal of automating the observatory for data collection.? Here's where I think I'm going.
?
The basic equipment list is a TI PD10 dome, Paramount MX+ mount, C-14 operating at about f/4, and either Watec 910 or QHY174M-GPS cameras.
?
Phase 1, which is almost complete, is to be able to collect data without going outside at night.? It will still be man-in-the-loop.? My dome is 20 yards out the back door, so getting to it isn't that hard if issues arise.? The dome reliably opens/closes its shutter remotely with the 20+ year old salvaged windlass mechanism.? It "semi-reliably" rotates--but has one sticky spot when pointing north (thankfully).? If it gets stuck, you can usually reverse to unstick it, and take the long way around if necessary.? Some fraction of the time I have to go outside to unjam it.? The dome reliably tracks the telescope pointing via file transfer from TSX (latest and greatest 64-bit) and DDW (circa 2002 technology) except with some logic issues at meridian crossing.? Other than the rotation issue, the two remaining problems are (1) issues with both cameras (the Watec 910 as-is requires in person button pressing to change exposure/gain) and the QHY 174 isn't reliable connecting over the USB 3 that goes through my Pegasus Ultimate Power box and (2) my point to point WiFi antenna link to the observatory has quirks (often reverts to the very slow regular WiFi, forcing me to turn that off).? So far I am 3 for 4 operating "remotely"--meaning one of the times I had to go out to the observatory to fix something,
?
Phase 2 is next.? That is a three part problem--camera, telescope, and dome.? If I use the Watec camera, I can use Russ's software to control that by scheduling observations (the issue with buttons still applies).? With the QHY, I think you can use the sequence editor in SharpCap to collect images at the required time.? The telescope would just run independently using TSX--I assume that functionality is in there, but I haven't tried to find it yet.? For phase 2, I don't think plate solving is necessary--the MX+ is amazing about getting targets well within the system FOV.? That leaves the big issue how to wake the dome, open the shutter, tell it to follow the telescope and shut back down.? If I can't come up with a way to do that, I may have to break down and pay for the TSX dome control add-in.
?
Phase 3 will be to do plate solves and perhaps adding in some weather monitoring.
?
Once phase 2 is in place, I will no longer be the limiting factor--and I'll want to try as many with reasonable probability as I can.? If only we could get OW files to drive it all (this is where someone tells me you can already do that).
?
BTW, my Astrid kit was lost in the US mail for a week.? Last Tuesday it left Los Angeles for Pennsylvania, and then was not scanned again until today--when it arrived in (drum beat, please) Los Angeles!? But at least it is no longer listed as missing.? When that arrives, it will allow me to do an easier second station locally or to do moderate travel to support other NEUS events.
?
?
Steve
?


From: George <georvisc@...>
To: OccultNEUS <[email protected]>
Date: Tuesday, 14 November 2023 11:37 AM EST
Subject: [OccultNEUS] Tale of 2 Occultations (subtitle - Occult4 201)

All:

It's a 'good' thing to know how to generate your own predictions in Occult4. Here's a couple reasons why...

Several days ago I noticed a nice early-evening event (7:03pm) when I generated a nightly run of Occult4 for Nov 13th UT. This? involved a 12.2 mag star and 16.2 mag (1349) Bechuana. The JPL/Horizons-based centerline ran nearly over my house, giving me a stated Probability of 100% (see attached).

In that same nightly run Occult4 listed another event - tho this one was more of a challenge. In this case the Target Star was about mag 15.1, and the asteroid - (463) Lola - was mag 15.8, and the event occurred at 8:46 UT (3:46am). Occult4 gave me a JPL/Horizons-based Probability of 65%.

Although I subscribe to nearly all the feeds in OccultWatcher Desktop (and set my search criteria very "wide"), OW did not list _EITHER_ event.

Turns out I had a RARE clear night on the 13th UT.
The event involving (1349) was only 12 degrees up in the SSW which required me to 'Go Mobile' (to get away from tall trees at home), so I drove about a mile from home to a wide open, dark field. I used my RunCam NE2AE and my 12-inch Sky-Watcher 300P SynScan GoTo / WiFi-controllable Dob. It was a bit of a challenge as the outside temp was only 19 degrees F. Due to the cold, I had the scope outside the passenger door of my pickup (warm-inside), with the computer propped-up above the passenger seat, with the screen facing out the window. To operate the computer I briefly opened the passenger door. A Bluetti EB70S inside the truck provided both 120VAC and 12VDC power. Just before the event, I hopped in the truck's driver's seat, turned the computer screen around observed the event in comfort.
Anyway...
????? === BINGO! === Got it! - A nice occultation.

I observed quite a distinct event with a duration of 0.83 seconds (maximum was predicted as 0.74 seconds). There are 2 shape models for the asteroid in Occult4 and I can see how it was likely that I got just a bit more than the maximum.

So after this Pos, I drove home, set up the same RunCam in my home observatory, and consulted my nightly Occult4 list of events. [OW Desktop listed nothing worth trying for during the night].
My Occult4 run listed a couple potential 'nicely placed in the sky' events (for which their predicted paths ran quite close to me):
2:17 UT - I recorded a Miss
4:34 UT - Another Miss
6:19 UT - Another Miss
7:00 UT - Another Miss (tho Occult4 gave me a decent probability of 42%)
8:46 UT......... This involved the above mentioned (463) Lola.
(In between events I went inside an watched a couple movies, and videos on YouTube - )
[As I RARELY get clear nights, I tend to pull "long nights" when it's clear. I know there will be PLENTY of upcoming nights to catch up on sleep!].

Finally (Amen!).... Time for the last event - (463)...
By this time (about 3:40am) the outside temp had dropped to about 11 degrees F. The computer was running in the observatory's warm room (which was about 60dF).
I would have liked to have used my QHY174M-GPS camera for this event, but I'm hesitant to subject a $1300 camera to heavy frost and such brutal temps - so I used my RunCam NE2AE (and I own a spare).
This event (combined mag of just under __15__) would push the RunCam to it's limits - but it helped that the event was 79 degrees up (nearly overhead). The max duration was 2.5 seconds so I figured I would set the RunCam at NS3 (due to the cold temps, I saw little thermal noise at NS3).
And...
????? === BINGO! === Got it! - A bit faint, but a distinct occultation (easily passes as a Pos in PyOTE)

[See the attached for some info/images regarding these 2 positives].

Suffice it to say......... I would have never known about these events if I didn't run my own nightly occultation searches in Occult4. I'd say at least 75% of my positive events are/were never listed on OW.
I do think the Northeast is... quite "overlooked" - as far as predictions.
[...And there's the old addage... "If you are going to do it right, DO IT YOURSELF"].

Disclaimer -- I will admit I didn't search OW Cloud to see if the (1349) and (463) were listed there (still haven't looked) - and then possibly "tagged" them. (I'll try to do this in the future ---- maybe). But... I __DID__ look to see if any experienced observers I knew of were near the predicted paths for these events -- and nobody was.

Moral of the Story --- OW is a Great tool for Coordinating observers, and there's certainly nothing wrong with just trying for events that OW informs you of (it's definitely less effort than running Occult4).... but... be prepared to miss some nice ones.

Sorry for the novel....

Happy Shadows,

George

George Viscome
Rand Obs II - MPC W71
Lake Placid, NY

Join [email protected] to automatically receive all group messages.