Re: Fine tuning PHD2 settings for 1100 with Encoders

Andrew J

Just a quick follow up. Roland was nice enough to annotate one of my unguided PHD2 graphs to illustrate how he measures Seeing. He explained that he uses this measurement to help determine the initial MinMo settings in PHD2. In my case, the maximum Peak-to-Peak values between two consecutive points on the graph were around 1.5 arc seconds, My guide camera has a resolution of around 2 arc seconds per pixel. This translates into an initial MinMo setting of around 0.8 - 0.9 pixels if you add a small buffer to the 0.75 pixel variation for Seeing. Initially I thought he was looking at the variation over the entire time period of the graph. It was a "light bulb moment" when he demonstrated he was just looking at 2 (maybe 3) consecutive points on the graph.

Note that this was on a night with particularly bad Seeing. Normally, you would expect the variation between consecutive points to be much smaller.

Another interesting point came up during our discussion related to the MinMo for RA vs. DEC. I never really understood why PHD2 Guiding Assistant (GA) always recommended a more aggressive (smaller) MinMo for RA vs. DEC. Brian provided the following quote from Bruce (author of PHD2) to help explain why these numbers are different.

Initially, the GA used the high-frequency statistics you are talking about but we weren't happy with that. Those statistics rely on a high-pass filter implementation and it's hard to know how to tune that for a broad range of image scales. So a replacement algorithm was developed using the standard deviation of the drift-corrected Dec movement as the statistical basis.  Using Dec motion in this way makes sense because the Dec motor isn't running - the movement should arise from polar mis-alignment and seeing.  Once the standard deviation value is calculated, a scalar term is applied that should produce a guiding activity level of only 10-20% for Dec.  A different, smaller scalar value is used for RA because there are no potential direction-reversal/backlash problems present in RA and a higher level of guiding activity is often needed because of tracking errors in the RA drive system.

The last sentence is key. The reason GA recommends a more aggressive MinMo for RA is because "a higher level of guiding activity is often needed because of tracking errors in the RA drive system". Roland indicated that this is not the case for mounts with encoders as the tracking errors should be miminal and recommended using the same MinMo setting for both RA and DEC axis.

I found both of these points enlightening and wanted to pass them along here for anyone else who might benefit from these explainations.

I want to thank both Roland and Brian for patiently taking the time to explain these points.

Andrew

Edit: Sorry for the multiple post. Stupid groups.io deleted the image when i tried to edit for typos.

Re: Cartes du Ciel Loses Mount Connection When APPM Launches

Peter Nagy

Hi John,

You shouldn't have to do this but have you tried using ASCOM Device Hub? It's pretty easy. It's already part of ASCOM. When you select ASCOM mount driver, instead of choosing A-P V2 ASCOM mount driver, choose ASCOM Device Hub (or something like that), it will open another window and you can choose A-P mount, your planetarium software and anything related to controlling the mount there. I'm writing this with a tablet so I'm writing from memory.

https://ascom-standards.org/FAQs/DevHub.htm

Peter

Re: New JPL Format for Horizons Ephemeris #APCC - Format Causes Issue

Michael 'Mikey' Mangieri

Thanks for the insight. I had verified both and they are OK. What I did find is that the problem is with Stellarium. A photo of where Ceres should be according to Stellarium didn’t show the dwarf planet. When I slewed to the coordinates given by JPL she was in the field; not perfect but well within the FOV. So now I guess it’s time to contact the Stellarium folks. Maybe the Solar System plug-in isn’t all that accurate for asteroids and comets.

On Nov 20, 2021, at 1:27 AM, Brian Valente <bvalente@...> wrote:

﻿
Two things come to mind

First is to make sure you solve and recal ahead of time so your pointing is is as accurate as possible

Second is Comet/satellite tracking is very sensitive to accurate time, many people (myself included) invest in a gps system with realtime clock updates using something like NMEATime

On Fri, Nov 19, 2021 at 8:25 PM Michael 'Mikey' Mangieri <mjmangieri@...> wrote:
Well, after some trial and error I finally got Horizons to work using the beta release of APCC and the instructions given by Ray to change the header text.  But now I have an interesting question ...
In testing out this feature I decided to target Ceres since it was placed high in the sky during the early evening hours. I wanted to test out the horizons tracking for comet Leonard but it doesn't rise above my tree line until 2:30-3:00 in the morning.  I ran the JPL ephemeris for Ceres and loaded it into APCC.  All went well. I then set my mount (AP1100) to track Ceres starting at 10:30pm.  When the mount slewed to Ceres it was not at the correct location according to Stelarium which I use to target objects and control the mount's initial slew. The location given by Stellarium is RA:  04h 23m 37.6s;  DEC:  +16d 45m 16.2s.  But the JPL data is giving  RA: 04h 22m 57.7s;  DEC:  +16d 39m 30.4s.  This is a considerable discrepancy. APCC Horizons thus points the telescope to a location well out of the FOV of the camera.
Not sure this is the proper place to discuss this, but has anyone experienced this issue?  This makes setting up a planned tracking impossible since the coordinates are not correct.  I've checked my location (Lat/Lon), and the settings on all the software and they are correct. J2000 vs 'on date' may contribute some of the error, but not nearly the amount I'm seeing.

--
Brian

Brian Valente

Re: One spot config for portable setup

DFisch

Greg, brilliant proposal!, thank you

On Sat, Nov 20, 2021 at 02:12 Greg McCall <emailgregnow@...> wrote:
I've been waiting for the upcoming suggestions for enhancements but as it has not yet appeared, I'm going to suggest something now, particularly when I notice some upgrades are being built (between APCC and NINA)
I'm always portable and I have a mixture of OTAs and cameras.
I'm suggesting that we should have a one spot configuration for all AP software config (APCC & APPM) and that it be single profile based.

I'd like site specific stuff (GPS/location and horison) in a single screen (select something and it's all there for a site and I should not have to go anywhere else)
Close by, an OTA and camera combination setup screen all in one screen with the ability to save as a single file profile.

(a bit like SGPro config screen(s) in one spot and being saved as a single profile file.

--
TJF MOBILE

Re: Testing SkyTrack continuous tracking with the Mach2

David Johnson

APCC 1.9.0.11

I’m also using an APPM model, although in this case I was using an older all-sky model since I didn’t have time to do a new model prior to the ISS pass.  It was for the same setup, although I had taken it down and put it back up.  The model was probably pretty good but not perfect.

One spot config for portable setup

Greg McCall

I've been waiting for the upcoming suggestions for enhancements but as it has not yet appeared, I'm going to suggest something now, particularly when I notice some upgrades are being built (between APCC and NINA)
I'm always portable and I have a mixture of OTAs and cameras.
I'm suggesting that we should have a one spot configuration for all AP software config (APCC & APPM) and that it be single profile based.

I'd like site specific stuff (GPS/location and horison) in a single screen (select something and it's all there for a site and I should not have to go anywhere else)
Close by, an OTA and camera combination setup screen all in one screen with the ability to save as a single file profile.

(a bit like SGPro config screen(s) in one spot and being saved as a single profile file.

Re: New JPL Format for Horizons Ephemeris #APCC - Format Causes Issue

Two things come to mind

First is to make sure you solve and recal ahead of time so your pointing is is as accurate as possible

Second is Comet/satellite tracking is very sensitive to accurate time, many people (myself included) invest in a gps system with realtime clock updates using something like NMEATime

On Fri, Nov 19, 2021 at 8:25 PM Michael 'Mikey' Mangieri <mjmangieri@...> wrote:
Well, after some trial and error I finally got Horizons to work using the beta release of APCC and the instructions given by Ray to change the header text.  But now I have an interesting question ...
In testing out this feature I decided to target Ceres since it was placed high in the sky during the early evening hours. I wanted to test out the horizons tracking for comet Leonard but it doesn't rise above my tree line until 2:30-3:00 in the morning.  I ran the JPL ephemeris for Ceres and loaded it into APCC.  All went well. I then set my mount (AP1100) to track Ceres starting at 10:30pm.  When the mount slewed to Ceres it was not at the correct location according to Stelarium which I use to target objects and control the mount's initial slew. The location given by Stellarium is RA:  04h 23m 37.6s;  DEC:  +16d 45m 16.2s.  But the JPL data is giving  RA: 04h 22m 57.7s;  DEC:  +16d 39m 30.4s.  This is a considerable discrepancy. APCC Horizons thus points the telescope to a location well out of the FOV of the camera.
Not sure this is the proper place to discuss this, but has anyone experienced this issue?  This makes setting up a planned tracking impossible since the coordinates are not correct.  I've checked my location (Lat/Lon), and the settings on all the software and they are correct. J2000 vs 'on date' may contribute some of the error, but not nearly the amount I'm seeing.

--
Brian

Brian Valente

Re: New JPL Format for Horizons Ephemeris #APCC - Format Causes Issue

Michael 'Mikey' Mangieri

Well, after some trial and error I finally got Horizons to work using the beta release of APCC and the instructions given by Ray to change the header text.  But now I have an interesting question ...
In testing out this feature I decided to target Ceres since it was placed high in the sky during the early evening hours. I wanted to test out the horizons tracking for comet Leonard but it doesn't rise above my tree line until 2:30-3:00 in the morning.  I ran the JPL ephemeris for Ceres and loaded it into APCC.  All went well. I then set my mount (AP1100) to track Ceres starting at 10:30pm.  When the mount slewed to Ceres it was not at the correct location according to Stelarium which I use to target objects and control the mount's initial slew. The location given by Stellarium is RA:  04h 23m 37.6s;  DEC:  +16d 45m 16.2s.  But the JPL data is giving  RA: 04h 22m 57.7s;  DEC:  +16d 39m 30.4s.  This is a considerable discrepancy. APCC Horizons thus points the telescope to a location well out of the FOV of the camera.
Not sure this is the proper place to discuss this, but has anyone experienced this issue?  This makes setting up a planned tracking impossible since the coordinates are not correct.  I've checked my location (Lat/Lon), and the settings on all the software and they are correct. J2000 vs 'on date' may contribute some of the error, but not nearly the amount I'm seeing.

Re: Testing SkyTrack continuous tracking with the Mach2

Brent Boshart

Hi David,

Nice video!  Are you running APCC and what version number?

Cartes du Ciel Loses Mount Connection When APPM Launches

John Upton

Hi Astro Nuts,

This is probably a setting issue but I have noticed the past few outings that my Cartes du Ciel planetarium program (version 4.2.1) loses its connection to the AP-V2 mount driver whenever I first launch APPM from APCC (version 1.9.0.11). (The mount in the AP Mach2.)

I usually launch application is the following order:
• APCC
• Cartes du Ciel
• PHD2
• NINA
I then make the following connections in this order:
• APCC to Scope via TCP and USB COM3 backup
• AP-V2 ASCOM Driver via APCC
• Cartes du Ciel to AP-V2 driver
• PHD2 to AP-V2 Driver and guide camera
• NINA to Imaging camera (ASI2600Mx)
• NINA to AP-V2 driver
• NINA to other equipment (MoonLight Focuser, PHD2)
Under this ordering everything works well until I launch APPM from APPC. As soon as that happens Cartes due Ciel throws multiple errors saying that it has lost its connection to the AP-V2 driver and that no mount is connected. I can connect APPM to the mount driver and NINA and then reconnect Cartes du Ciel and all are happy and play well together.

Has anyone else observed something similar? Is this a known issue? Could it be something that I have set up incorrectly in APPM, APCC, or Cartes du Ciel itself? It is not a catastrophic error and seems to cause no harm but if I can avoid it, so much the better.

John

Re: Testing SkyTrack continuous tracking with the Mach2

David Johnson

Latest ISS effort.  Getting better.

Re: November 2021 Red Beaver Moon

Roland Christen

Great, very nice! You got a nice eclipsed Moon there.

Rolando

-----Original Message-----
From: eja24601 via groups.io <eja24601@...>
To: main@ap-gto.groups.io
Sent: Fri, Nov 19, 2021 4:51 pm
Subject: [ap-gto] November 2021 Red Beaver Moon

November 18 was started off mostly cloudy, but the forecasts (TV meteorologists included) all pointed to clear skies for the eclipse. With that in mind, I got up at 1AM to start preparing for a go at capturing a sequence. Unfortunately, despite forecasts (Astrospheric and the Clear Sky Clock included) for a partly cloudy sky at that time, it was overcast. The Beaver Moon did punch through some sucker holes and thinning layers long enough for me to come to focus with my telescope/camera. However, the clouds stubbornly hung around. 2:30 came and went with no signs of the clouds dispersing. I finally decided to try and nap until 3:30. I tossed and turned restlessly and finally decided to check conditions around 3:20. Lo and behold, the clouds had parted, with the eclipse partway through.

I hurried to our telescope, consoling myself that if I wouldn't be able to capture a sequence, I would at least attempt an HDR composite. Other than a thin cloud that seemed to mock my first attempt at bracketed exposures, the sky remained clear for the rest of the night. I shot a sequence of bracketed exposures all the way through about 5:45AM, so I have a lot of data to play with as I attempt other HDR composites.

In between capturing images, I thought for a change to view the eclipse visually with a scope. Binoculars views were good but shaky (hand-held, no surprise). So I brought out a Borg 76ED and gazed visually. The view with a 15mm TV Plossl was mesmerizing. My HDR composite is a weak attempt at capturing what I saw through the eyepiece.

That said, here is an attempt at an HDR composite of the eclipse near maximum (taken around 4:05AM). This was taken with a Canon Digital Rebel t6i through a TMB-152 scope riding on an Astro-Physics AP1200GTO mount. This is radically reduced from the original 4000 x 6000-sized image.

Enjoy,
Eric

--
Roland Christen
Astro-Physics

Re: New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

Mauricio Guerra

Great, many thanks for the time spent on finding the root cause. Your guidance will for sure help others too!

Best regards and have a good weekend.

Mauricio Guerra

San Diego, CA.

Sent from Mail for Windows

From: Ray Gralak
Sent: Friday, November 19, 2021 12:59 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

Hi Mauricio,

Thanks for the file.

It looks like the field names can change slightly depending on the selected options. I'm going to look into how to make this work better in Horizons, but for now try replacing line 69 with this line:

Date__(UT)__HR:MN:SC.fff     R.A.__(a-apparent)__DEC  dRA*cosD d(DEC)/dt   Azi_(a-appr)_Elev     L_Ap_Sid_Time   T-Mag   N-mag

The problem is that the field that starts with "Azi" is different from what Horizon expects. You'll need to replace this line in any future Horizon ephemeris files you create until I can produce a fix. I've attached the full edited file as well.

-Ray

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Mauricio Guerra via groups.io

> Sent: Friday, November 19, 2021 10:33 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

>

> Ray, thanks.

>

>

>

> The text file that fails to load is attached.

>

>

>

> Thanks,

>

>

>

> Mauricio Guerra

>

> San Diego, CA.

>

>

>

>

>

> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows

>

>

>

> From: Ray Gralak <mailto:iogroups@...>

> Sent: Thursday, November 18, 2021 9:53 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

>

>

>

> Mauricio,

>

>

>

> > I narrowed down to 1-hour duration and 1-minute interval (there is no option for 1-sec intervals in the

> dropdown box).

>

>

>

> Sorry, I thought I sent the explanation of how to do this earlier, but I see I didn't actually click send. :-)

>

>

>

> You can increase the time resolution by specifying a one-hour time interval and setting a step size of 3600

> "equal units (unitless)", which would produce one-second entries in the ephemeris results table. Your first

> video shows a one-minute intervals for a month duration. This may not be the problem but one-minute

> sampling is not going to provide a very accurate calculation for the ISS.

>

>

>

> And, rather than this back and forth trial and error, please attach the text file that fails to load. That will make it

> much easier to determine the problem.

>

>

>

> Thanks,

>

>

>

> -Ray

>

>

>

>

>

>

>

> > -----Original Message-----

>

> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Mauricio Guerra via groups.io

>

> > Sent: Thursday, November 18, 2021 8:50 PM

>

> > To: main@ap-gto.groups.io

>

> > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

>

> >

>

> > Ray:

>

> >

>

> >

>

> >

>

> > I narrowed down to 1-hour duration and 1-minute interval (there is no option for 1-sec intervals in the

> dropdown

>

> > box).

>

> >

>

> >

>

> >

>

> > https://youtu.be/QhnU1o9lDM8

>

> >

>

> >

>

> >

>

> > I also tried this setting: meaning one-second intervals (assuming you were referring to that). I did not see a

>

> > difference. Same error.

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> > Thanks!

>

> >

>

> >

>

> >

>

> > Mauricio Guerra

>

> >

>

> > San Diego, CA.

>

> >

>

> >

>

> >

>

> > From: Ray Gralak <mailto:iogroups@...>

>

> > Sent: Thursday, November 18, 2021 5:40 PM

>

> > To: main@ap-gto.groups.io

>

> > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0)andPro(1.9.1.1)

>

> >

>

> >

>

> >

>

> > You  have a full month of time range. Can you try narrowing it down to one hour and the 1-second effective

>

> > time interval?

>

> >

>

> >

>

> >

>

> > > -----Original Message-----

>

> >

>

> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Mauricio Guerra via

> groups.io

>

> >

>

> > > Sent: Thursday, November 18, 2021 5:11 PM

>

> >

>

> > > To: main@ap-gto.groups.io

>

> >

>

> > > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) andPro(1.9.1.1)

>

> >

>

> > >

>

> >

>

> > > Ray, thanks.

>

> >

>

> > >

>

> >

>

> > > I tried selecting on 2,3,4,7, and 9. But I keep getting the same result:

>

> >

>

> > >

>

> >

>

> > > The sequence ending in error is shown here:

>

> >

>

> > >

>

> >

>

> > > https://youtu.be/8ewIGj9ImkE

>

> >

>

> > >

>

> >

>

> > > I  can for sure try other options based on your guidance.

>

> >

>

> > >

>

> >

>

> > > *         I guess the browser is not an issue. I use Chrome

>

> >

>

> > > *         I have Windows 10

>

> >

>

> > > *         I tried the process without connecting to the mount

>

> >

>

> > >

>

> >

>

> > > Thanks for your time.

>

> >

>

> > >

>

> >

>

> > > Mauricio Guerra

>

> >

>

> > >

>

> >

>

> > > San Diego, CA.

>

> >

>

> > >

>

> >

>

> > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows

>

> >

>

> > >

>

> >

>

> > > From: Ray Gralak <mailto:iogroups@...>

>

> >

>

> > > Sent: Thursday, November 18, 2021 4:08 PM

>

> >

>

> > > To: main@ap-gto.groups.io

>

> >

>

> > > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) andPro(1.9.1.1)

>

> >

>

> > >

>

> >

>

> > > Hi Mauricio,

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > Try selecting only these five check boxes in the Observer Table Settings:

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > 2,3,4,7, and 9.

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > -Ray

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > > -----Original Message-----

>

> >

>

> > >

>

> >

>

> > > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Mauricio Guerra via

>

> > groups.io

>

> >

>

> > >

>

> >

>

> > > > Sent: Thursday, November 18, 2021 1:29 PM

>

> >

>

> > >

>

> >

>

> > > > To: main@ap-gto.groups.io

>

> >

>

> > >

>

> >

>

> > > > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) and Pro(1.9.1.1)

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Geert, thanks. Yeah, I used those recommended settings.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > I captured the sequence in this brief clip (in 1080p quality, it should show a clear image of the sequence

>

> > and

>

> >

>

> > >

>

> >

>

> > > > settings):

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > https://youtu.be/8y3BsvMrAaI

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Is it working for all who verified?

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Thanks all for your time!

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Mauricio Guerra

>

> >

>

> > >

>

> >

>

> > > > San Diego, CA.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > From: Geert <mailto:geert.vandenbulcke@...>

>

> >

>

> > >

>

> >

>

> > > > Sent: Thursday, November 18, 2021 1:00 PM

>

> >

>

> > >

>

> >

>

> > > > To: main@ap-gto.groups.io

>

> >

>

> > >

>

> >

>

> > > > Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) and Pro(1.9.1.1)

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Mauricio,

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Did you check that the necessary table settings are selected (2, 3, 4, 7, 9) ? Check Edit Table Settings

> on

>

> >

>

> > > the

>

> >

>

> > >

>

> >

>

> > > > Horizons web page.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Geert

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > > Op do 18 nov. 2021 om 21:12 schreef moguerra via groups.io <moguerra@...>:

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         I did tried one more time  today using the BETA version you provided above (Pro 1.9.1.1). I did set

>

> > the

>

> >

>

> > >

>

> >

>

> > > > proper settings and used the buttons to download the data within JPL site and the "Load JPL File"

> button

>

> > in

>

> >

>

> > >

>

> >

>

> > > > Horizons. Unfortunately, I still get the same behavior/error.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         I use windows 10, in case it is important.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         Hopefully my observation is consistent with other.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         Thanks for the help getting this resolved.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         Regards,

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >         Mauricio Guerra

>

> >

>

> > >

>

> >

>

> > > >         San Diego, CA.

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

>

>

>

>

>

>

>

>

>

>

>

>

>

Re: November 2021 Red Beaver Moon

Howard Ritter

I missed my guess about the significance of the numbers in your screen name! Are you anywhere near Oxford, where I grew up? I’m in the Toledo area now.

—howard

On Nov 19, 2021, at 6:23 PM, eja24601 via groups.io <eja24601@...> wrote:

Thanks, all! This was my first attempt at an HDR composite. Hopefully I can improve my techniques over time. Howard, I live in southwest Ohio. I don't know how VA fared.

Tony, I can relate. I recall being at a dark sky site in NM during one well-placed early morning eclipse, and of course it was clouded over during the event! Fortunately, I was there for a different reason and the eclipse (had I caught it) would have been a bonus.

Re: November 2021 Red Beaver Moon

eja24601

Thanks, all! This was my first attempt at an HDR composite. Hopefully I can improve my techniques over time. Howard, I live in southwest Ohio. I don't know how VA fared.

Tony, I can relate. I recall being at a dark sky site in NM during one well-placed early morning eclipse, and of course it was clouded over during the event! Fortunately, I was there for a different reason and the eclipse (had I caught it) would have been a bonus.

Re: November 2021 Red Beaver Moon

Harley Davidson

Beautiful image Eric!

All I had was big, huge clouds :(   Wouldn't you know the skies cleared after sunrise.

tony

On 11/19/2021 5:51 PM, eja24601 via groups.io wrote:
November 18 was started off mostly cloudy, but the forecasts (TV meteorologists included) all pointed to clear skies for the eclipse. With that in mind, I got up at 1AM to start preparing for a go at capturing a sequence. Unfortunately, despite forecasts (Astrospheric and the Clear Sky Clock included) for a partly cloudy sky at that time, it was overcast. The Beaver Moon did punch through some sucker holes and thinning layers long enough for me to come to focus with my telescope/camera. However, the clouds stubbornly hung around. 2:30 came and went with no signs of the clouds dispersing. I finally decided to try and nap until 3:30. I tossed and turned restlessly and finally decided to check conditions around 3:20. Lo and behold, the clouds had parted, with the eclipse partway through.

I hurried to our telescope, consoling myself that if I wouldn't be able to capture a sequence, I would at least attempt an HDR composite. Other than a thin cloud that seemed to mock my first attempt at bracketed exposures, the sky remained clear for the rest of the night. I shot a sequence of bracketed exposures all the way through about 5:45AM, so I have a lot of data to play with as I attempt other HDR composites.

In between capturing images, I thought for a change to view the eclipse visually with a scope. Binoculars views were good but shaky (hand-held, no surprise). So I brought out a Borg 76ED and gazed visually. The view with a 15mm TV Plossl was mesmerizing. My HDR composite is a weak attempt at capturing what I saw through the eyepiece.

That said, here is an attempt at an HDR composite of the eclipse near maximum (taken around 4:05AM). This was taken with a Canon Digital Rebel t6i through a TMB-152 scope riding on an Astro-Physics AP1200GTO mount. This is radically reduced from the original 4000 x 6000-sized image.

Enjoy,
Eric

Re: November 2021 Red Beaver Moon

Howard Ritter

Very nice capture, Eric. I’ve been hoping that someone in one of the groups I belong to would post a decent HDR image. This is the first I’ve seen. Thanks for posting.

Do you live in western VA? I want to tweak my brother in Lexington (VA) for not bothering to get up to see it if he had the same clearing skies.

—howard

On Nov 19, 2021, at 5:51 PM, eja24601 via groups.io <eja24601@...> wrote:

November 18 was started off mostly cloudy, but the forecasts (TV meteorologists included) all pointed to clear skies for the eclipse. With that in mind, I got up at 1AM to start preparing for a go at capturing a sequence. Unfortunately, despite forecasts (Astrospheric and the Clear Sky Clock included) for a partly cloudy sky at that time, it was overcast. The Beaver Moon did punch through some sucker holes and thinning layers long enough for me to come to focus with my telescope/camera. However, the clouds stubbornly hung around. 2:30 came and went with no signs of the clouds dispersing. I finally decided to try and nap until 3:30. I tossed and turned restlessly and finally decided to check conditions around 3:20. Lo and behold, the clouds had parted, with the eclipse partway through.

I hurried to our telescope, consoling myself that if I wouldn't be able to capture a sequence, I would at least attempt an HDR composite. Other than a thin cloud that seemed to mock my first attempt at bracketed exposures, the sky remained clear for the rest of the night. I shot a sequence of bracketed exposures all the way through about 5:45AM, so I have a lot of data to play with as I attempt other HDR composites.

In between capturing images, I thought for a change to view the eclipse visually with a scope. Binoculars views were good but shaky (hand-held, no surprise). So I brought out a Borg 76ED and gazed visually. The view with a 15mm TV Plossl was mesmerizing. My HDR composite is a weak attempt at capturing what I saw through the eyepiece.

That said, here is an attempt at an HDR composite of the eclipse near maximum (taken around 4:05AM). This was taken with a Canon Digital Rebel t6i through a TMB-152 scope riding on an Astro-Physics AP1200GTO mount. This is radically reduced from the original 4000 x 6000-sized image.

Enjoy,
Eric <MaxEclipse.jpg>

Re: November 2021 Red Beaver Moon

Manusfisch

Eric , what a nice blend of colors, The silver gray of the moon really stands out on the left-hand side and blend so nicely with the blood red moon

TJF Mobile

On Nov 19, 2021, at 17:51, eja24601 via groups.io <eja24601@...> wrote:

﻿November 18 was started off mostly cloudy, but the forecasts (TV meteorologists included) all pointed to clear skies for the eclipse. With that in mind, I got up at 1AM to start preparing for a go at capturing a sequence. Unfortunately, despite forecasts (Astrospheric and the Clear Sky Clock included) for a partly cloudy sky at that time, it was overcast. The Beaver Moon did punch through some sucker holes and thinning layers long enough for me to come to focus with my telescope/camera. However, the clouds stubbornly hung around. 2:30 came and went with no signs of the clouds dispersing. I finally decided to try and nap until 3:30. I tossed and turned restlessly and finally decided to check conditions around 3:20. Lo and behold, the clouds had parted, with the eclipse partway through.

I hurried to our telescope, consoling myself that if I wouldn't be able to capture a sequence, I would at least attempt an HDR composite. Other than a thin cloud that seemed to mock my first attempt at bracketed exposures, the sky remained clear for the rest of the night. I shot a sequence of bracketed exposures all the way through about 5:45AM, so I have a lot of data to play with as I attempt other HDR composites.

In between capturing images, I thought for a change to view the eclipse visually with a scope. Binoculars views were good but shaky (hand-held, no surprise). So I brought out a Borg 76ED and gazed visually. The view with a 15mm TV Plossl was mesmerizing. My HDR composite is a weak attempt at capturing what I saw through the eyepiece.

That said, here is an attempt at an HDR composite of the eclipse near maximum (taken around 4:05AM). This was taken with a Canon Digital Rebel t6i through a TMB-152 scope riding on an Astro-Physics AP1200GTO mount. This is radically reduced from the original 4000 x 6000-sized image.

Enjoy,
Eric
<MaxEclipse.jpg>

November 2021 Red Beaver Moon

eja24601

November 18 was started off mostly cloudy, but the forecasts (TV meteorologists included) all pointed to clear skies for the eclipse. With that in mind, I got up at 1AM to start preparing for a go at capturing a sequence. Unfortunately, despite forecasts (Astrospheric and the Clear Sky Clock included) for a partly cloudy sky at that time, it was overcast. The Beaver Moon did punch through some sucker holes and thinning layers long enough for me to come to focus with my telescope/camera. However, the clouds stubbornly hung around. 2:30 came and went with no signs of the clouds dispersing. I finally decided to try and nap until 3:30. I tossed and turned restlessly and finally decided to check conditions around 3:20. Lo and behold, the clouds had parted, with the eclipse partway through.

I hurried to our telescope, consoling myself that if I wouldn't be able to capture a sequence, I would at least attempt an HDR composite. Other than a thin cloud that seemed to mock my first attempt at bracketed exposures, the sky remained clear for the rest of the night. I shot a sequence of bracketed exposures all the way through about 5:45AM, so I have a lot of data to play with as I attempt other HDR composites.

In between capturing images, I thought for a change to view the eclipse visually with a scope. Binoculars views were good but shaky (hand-held, no surprise). So I brought out a Borg 76ED and gazed visually. The view with a 15mm TV Plossl was mesmerizing. My HDR composite is a weak attempt at capturing what I saw through the eyepiece.

That said, here is an attempt at an HDR composite of the eclipse near maximum (taken around 4:05AM). This was taken with a Canon Digital Rebel t6i through a TMB-152 scope riding on an Astro-Physics AP1200GTO mount. This is radically reduced from the original 4000 x 6000-sized image.

Enjoy,
Eric

Re: Heavy piggyback considerations

eja24601

Thanks for the replies! I don't recognize the TMB's rings; they might be APM/TMB rings of the era (the scope is an actual TMB-152 from the early-mid 2000's). The FSQ is using Socal Astro rings (no longer made, but pretty beefy). I definitely have no plans on using flimsy inexpensive rings.

Chip, that's a great idea to mount the FSQ on the TMB's rings without the scope! Yes, I agree that a tandem arrangement is the better approach long-term. This piggyback idea is not meant for occasional use, not long-term (FSQ riding semi-permanently on the TMB).

Regards,
Eric

 3921 - 3940 of 86904