Sunday, December 16, 2018

did not see ISS (Bradford)

Tried to image the International Space Station from the backyard but it was too low and too faint. The flyover was from 5:17 PM for about 10 minutes. I did not see anything visually.

clear skies from backyard

Canon 40D, Rokinon 8mm manually focused, ISO 100, f/22, 10 seconds, daylight white balance, barn door tracker, Neewer intervalometer.

Thursday, December 13, 2018

gone (Bradford)

Saw stars when I when out to fill up with cheap gas. Clouds when I got home.

Monday, December 10, 2018

the long journey to the Sculptor (Stillwater Lake)

The journey to the Sculptor galaxy was long. I'm indebted to Dave Lane.

It all started, of course, with my harebrained idea to image all the RASC Finest NGC objects. This was the project I decided to set myself 'round the time I started learning and using the Burke-Gaffney Observatory in February 2016. I didn't consider however at the outset that some objects might be out of range...

I first encountered this issue in May 2016 when I tried to capture NGC 6520. Despite my efforts, my requests were rejected. I was disappointed but not entirely surprised with the open cluster never rising over 18 degrees above the horizon.

I was using the MINALT setting from the beginning to (indirectly) control how long I wanted the system to wait before imaging a target. I.e. I wanted to image higher vs. lower. Ideally, to shoot targets at an elevation of 45° or above.

On NGC 6520 I used MINALT=15 but didn't fully understand the matter of altitude constraints at the time.

In June 2016, I made a new page in Evernote for targets "too low" for BGO. It was probably around then I made an analogous list in SkyTools (on John Charles). As I transferred more targets to this note, I lamented. I would not able to photograph all the objects in the RASC list.

(A curious example: I initially thought the nebula NGC 6445 would be inaccessible and my fumbles with parameters even though it hovered around 25 degrees preventing lodging a successful request; happily I snared the peculiar planetary in April this year.)

Sculptor constellation due south over a perfect horizon

Late in the summer of 2016 I set my sights on the fine galaxy in the Sculptor constellation. On 25 August at 5:43 PM EDT, I asked BGO to listen to me while I submitted the job using "#request object=NGC253 special= LUM,60,10,RED,60,5,GRN,60,5,BLU,60,5 comment=RASCFinest". The 'bot replied "Sorry, NGC253 never rises high enough to be observed at the BGO!"

I can't remember if I tried again at the time but it is likely I just picked other targets, moving on, as I had many candidates still early in the process.

Year Bar graph from SkyTools

But in December last year it showed on my radar again. A Finest NGC not yet captured. I was better at planning now. I paid more attention to the Year Bar in SkyTools. I paid more attention to the transit or culmination time. It would peak around 7:15 PM AST. Looked good although I knew with was extremely low. So BGO and I had a little chat:
bla:  #lookup object=NGC253
 
robot:  Fixed object NGC253 found at position RA=00:47:36.3 DEC=-25d17'58", and it can be requested now
 
bla:  #request object=NGC253 special=LUM,60,10, RED,60,5,GRN,60,5,BLU,60,5 minalt=20 comment=Finest
 
robot:  Sorry, NGC253 never rises high enough to be observed at the BGO!
What? Huh? I was confused. The LOOKUP command suggested it could be added.

I remarked while imaging The Antenna Galaxies in late December 2017 that I had a "better understanding of the MINALT." Finally I clearly understood the parameter. I learned the default minimum altitude for BGO was 25° yet it could be overridden and forced lower. But only down to 20. That was it. This knowledge helped me bag galaxy NGC 1232 in Eridanus.

Yet it still did not explain why the 253rd NGC wouldn't take.

I resigned myself to getting all but two of the Finest.

Well. With BGO I'd be able to get to all but two. I had optically viewed Sculptor way back on 1 September 2008. So that one was "done" in a sense. Then, happily, I finally viewed NGC 6520 on 12 June 2018. That for me was a milestone: I had seen all the Finest, directly or indirectly. Fun.

Sometime in the fall of 2018 I hatched an idea. I don't remember exactly when or where but the broad strokes were to use another robotic system. That philosophically felt right. Using another robotic system to get the other two NGCs felt right.

During my Burke-Gaffney Observatory presentation at the Ontario Science Centre early October, I mentioned that the Abbey Ridge Observatory "would be open" to RASCals. Dave corrected me: it already was. I think a couple of people joined after seeing my prez. And I started thinking seriously about it.

On 28 October I sent a note to Dave. I said I was entertaining the idea of asking for an account at ARO particularly if it had lower altitude/elevation limits than BGO. I felt it would be neat to image every Finest with a rig accessible via social media.

Not directly related to this endeavor was the use of the new Communicator app created by Dave Lane. I downloaded the Android and Windows apps on November 26 partly to help him test the beta release. For me a most interesting aspect of using the little tool was the instantaneous response. The direct access to the robot meant turnaround time was significantly faster. Dave VIII and I chatted via Facebook Messenger, trying various things in the new app. During the conversation, I asked Dave if he had thought more on my ARO question.

the ARO obstructed horizon

He sent me a snapshot of the obstructed horizon for ARO. The simulation showed the Sculptor galaxy below the tree line at the time of 8 PM. That said, Dave noted the trees were "leafy" so it might work. But it might also require he make a "notch" in the horizon file.

I mimicked the horizon in SkyTools so I could put it into motion. I found NGC 253 would peek over the trees, in the little dip to the south-south-west, in a couple of weeks. Dave told me to touch base shortly before.

That meant I needed to configure for using the Abbey Ridge system. I submitted an ARO request on 27 November but didn't get a response. Later I discovered it was malformed. RTFWP. I composed a properly formatted membership request on 5 December. Dave reminded me to create a password so I could use the Communicator app. Done.

On 9 December, I reached out to Dave. I noted the Sculptor galaxy would culminate around 7:45 PM AST over the next little while. The true altitude would be +20°10'; the altitude above visible horizon would be +20°34' (at least, that's what showed in SkyTools for my BGO SMU profile). The Moon set Monday and Tuesday nights around 8:00 PM. It looked like the Tuesday night weather might cooperate. The CSC for Abbey Ridge looked promising. Clear Outside said both Monday and Tuesday 8-10 PM time slots were fair to good. The Weather Network said both nights would be partly cloud (and really cold)! Astrospheric was not encouraging. I asked if he could help.

On Monday afternoon I checked the weather. It still looked somewhat promising. I pinged Dave on Facebook and apologised for bugging him. He said "no worries" and then sent an email message. "Both observatories will accept ngc253 now even at minalt=25 and its clear NOW!!!! Submit and let me know and I'll bump the priority."

That was very nice of him to help me so.

Wait?! It was clear?! The weather predictions were off. Dave was looking out his window and it was looking good. Oh my Universe! This was great news. I needed to get jobs in queues ASAP.

Hurry! Hurry hard.

I formed an order in Evernote.
#request object=NGC253 special=LUM,60,10,RED,60,5, GRN,60,5,BLU,60,5 minalt=20 comment=Finest
I submitted it via the Android app to BGO and ARO.

Both failed. The 'ole "never rises high enough" response. Oh boy. Told Dave. "Ack. Stand by... the lookup command worked which puzzles me." Indeed. A long outstanding issue for me. 

A few minutes later, Dave replied: "Try ARO now. Don't use exposure longer that 15 minutes per request." He went on to say:
There are 3 constraints, the actual horizon, a minimum altitude regardless of horizon, being "reasonably" observable in the next 30 days, and a lowest dec (this one is just to avoid searching serviceability if its hopeless.
I relayed the good news. My simplified task "#request object=NGC253 special=LUM,60,10 comment=Finest" was accepted and I was assigned job ID 1373.

I sent a "#weather" query at 17:57 AST. ARO said "The sky is CLEAR (temp=-8C, wind=0 km/h)." Look at that.

Started noting emails with the subject "ARO: The operator has edited your request ID 1373 (NGC253)." The human was tuning my request. A couple more came in. I checked Requested Observations pages at ARO. I noted the lower minimum altitude (18°) and the elevated priority. I also saw the FULL SIZE parameter was active. Cool!

Wondered if I was interrupting Dave's dinner when he sent a report.
It is starting up.  Some fluffy clouds around so we'll see.
 
Dome was initially frozen (global warming? its -8C!).
Yes! This was gonna happen! I was excited!

Oh. Sounds like he had to trudge through the snow in the cold to persuade things...

Another email arrived. "ARO: The operator has edited your request ID 1373 (NGC253)." I think he set the MINALT even lower.

At 6:16 PM AST, Dave suggested I submit a second time. He provided recommended parameters, "som=w minalt=15 fullsize=yes", noting that "som" would force it to the west side of the meridian.

I didn't get it, at first. A little fuzzy. In my brain, a fuzzy. I asked if he was suggesting that, his edits notwithstanding, I send a second job. Moments later I thought, what the heck. Sure. Two jobs. I didn't think ordinarily I could do that, be on the same target in the same night, but hey. I submitted another job as per his instructions. It was my first use of the "som" option.

ARO queued the ask at 6:30 PM AST and assigned ID 1374.

I sent an email to the Abbey Ridge machine with the #satellite hash tag.

satellite image sent from ARO

It did not look great at the moment. But I saw that if the wind was coming from the north-west, the red blotch would move over the observatory west of Halifax. Good.

At 5:38 PM EST, I received a reply from Dave. "A second one, just to give it two tries." And finally the light bulb went off. Get more eggs in more baskets. Ask the observatory to try more than once to cover more bases. To dodge potential clouds. To simply make more attempts as we literally pushed the envelope.

He then updated me: "It is taking forever to get over the 18 degrees I set, but it should run in a few mins..." I was on the edge of my seat.

5:48 PM EST. Told Dave I had added the second request. I asked to bump the priority but he was already on it. "ARO: The operator has edited your request ID 1374 (NGC253)." OK! Good to go.

Two minutes later, Dave said, "Slewing..." Oh, the anticipation. I thanked Dave.

He said, "I might need to go hold some branches aside!" Told him I wanted a picture of that! Super-low I imagined. Just skimming the southern trees of the Stillwater Lake community.

At 6:53 PM AST, Dave forwarded an image. The "sync" image.

sync image of NGC 253 from ARO

There it is! We got it! I was so happy. It looked pretty good too! The thing is huge! I forgot how big NGC 253 was. (And that's why Dave told me to use the full frame.)

It was then I remember the specs for this system. A long focal length given a C14 was being used. It also jostled me that I had yet to build a profile in SkyTools.

6:59 PM AST. Dave forwarded 1 minute raw image. It was fantastic to see the Sculptor galaxy centred.

He shared that it was a "good thing the trees are mostly maples. I must take peek and see what its looking through. Maybe I need summer and winter horizons!" Sounded like even he was surprised. Told him I did some visual observing in the winter and enjoyed pushing lower around deciduous trees. He shared he had trimmed some trees since the horizon was measured.

And then, at 6:07 PM EST, I received an email that I thought, for a long time, that I'd never get. The ARO robot updated me with the missive "ARO: #aroreplies I have taken your special observation of NGC253 (ID 1373)!" w00t!

It was done. I finally had a image of one of the lowest selections from the RASC Finest list. Acquired by remote control (well, initiated by commands I had submitted from Ontario, then fine-tuned by the operator in Nova Scotia). Pretty neat.

Finest NGC Sculptor galaxy in luminance east of meridian

Luminance only, 60 seconds subexposures, 10 stacked shots. FITS Liberator, Paint.NET. North is up; east is left. Gradient on the top of the frame. Satellite at the top-right. S'OK.

6:19 PM EST. I checked my weather resources.

pessimistic Clear Sky Chart for Abbey Ridge

I recorded the Clear Sky Chart values. The predicted numbers were surprisingly poor. Cloud: 70% covered. Transparency: too cloudy. Seeing: 2, poor. The Moon altitude as around 2°. I'm a big fan of the CSC system but it was way off. I snapped the the Clear Outside site: it showed much better conditions. Dave's on-site reports showed that CO's prediction to be better. More current.

edited queue at ARO

Noticed another edit of a queued job. High priority for 1374. Low elevation setting. Ooh. West side.

I continued to monitor the twitter feed but there were not a lot of updates. Then at 7:02 PM EST another email came in. Subject: ARO: #aroreplies I have taken your special observation of NGC253 (ID 1374)! All right. The other side of the meridian. I had followed Dave's good advice and doubled down.

Finest NGC Sculptor galaxy in luminance west of meridian

Gradient at the bottom this time—flipped of course.

Happy happy joy joy. Twice the data!

A great feeling. Lots of things came together this evening.

To top it all off, this undertaking marked my first capture with the ARO rig! The robotic Abbey Ridge Observatory is home to a Celestron 14-inch Schmidt Cassegrain Telescope with an SBIG ST-8XME CCD camera. There's a focal reducer that changes the imaging parameters to about 60%.

§

11:28 PM AST. The 'bot relayed the message "ARO: Your observations taken overnight are ready..." I downloaded the ZIP files and opened the luminance frames in FITS Liberator. Good data. Not surprised to see a gradient given the extreme elevation. Converted, opened the TIFS in Paint.NET, and made the JPEGs for this post.

I thanked Dave again. Wow.

§

I learned tonight that NGC 253 is also known as the Silver Coin or Silver Dollar Galaxy. Also, it is in the Caldwell catalogue as entry number 65.

§

Wikipedia link: Sculptor Galaxy.

Saturday, December 08, 2018

there be dragons!

Ha ha. Love this photo from Space Station.

dragons at the ISS

Lots of dragons in low Earth orbit.

I like too how the Canadarm is at the ready.

stumped

What? Clouds? The north is blotted out. So much for that. I wanted to get an image of the International Space Station with David Saint-Jacques aboard...

Oh my. Clear Outside paints a poor picture.

Clear Outside chart for Sat 8 Dec '18

Maybe my planned 10 PM run won't work...

My walk to and from the drug store suggested the sky was improving.

The CSC has thrown me off. It is very optimistic.

Clear Sky Chart for Sat 8 Dec '18

OK. I'll leave the Space Station for another day...

snagged

Frickin' computers!

Had fiddled unnecessarily with Heavens Above. Every time I went to change the location it switched to a latin language. Gilipollas!

Returned to my desk to find the mouse pointer frozen. Whiskey tango foxtrot. I had recently tested the space USB cable at the John Max Windows computer as I cannot find my regular tether.

Here I was accelerating with the idea of imaging the ISS pass at 5:48.

Don't need this.

he shot 46P widefield

Enjoyed Malcolm's photo of comet 46P/Wirtanen, from his online photo gallery, shared on Facebook. DSLR shot with a short refractor. I noted his settings and I'll try as soon as I can. Jealous of his dark skies though. Visit Mr Park's SmugMug gallery for stunning photographs. The comet is (currently) in the Recent Pics area.

Friday, December 07, 2018

tried for Pal 1 (Halifax)

Another image that took a while to get was for Palomar 1 in Cepheus. And in the end, was it worth it? I can barely see anything. Hover over the image to get the location of the dim globular. Magnitude 13.6? I dunno.

This was an attempt to improve on the result from about a year ago.

very dim and small globular cluster Palomar 1 with red filter

Red filter only, 60 seconds subexposures, 10 stacked shots. FITS Liberator, Paint.NET. North is up; east is left. Annotated.

Again, it took some effort to get this.

Submitted the first request on Nov 12, centred on the star GSC 04517 01909. But I goofed with very short exposures, at 10 seconds.

Resubmitted, asking for 60 seconds each. Also, I decided to drop the LUM.

I broke Ralph! Something happened. I still don't know what exactly. Mr Lane forwarded the log. "! In script 'sm-proc-request.dtl' (line=202) - Fatal error - uncaught application error." Yikes. Crashed it good.

Dave suggested I "try again" so I submitted another job (using the exact same content) which was accepted... Assigned ID number 7013.

Meanwhile job 7007 appeared. Same request. Maybe Dave tried it again. 

So I had two asks in the job jar. Normally you can't do that.

This morning both were processed! Double data! Curiously, the first set, from 3:37 AM AST, looked better. The second set was captured at 04:16 AST.

Why do I bother? Maybe it's silly going after these with a tiny telescope. The Palomar Sky Survey was completed in the 1950s with a 48-inch instrument. Π r squared so 4 times the light gathering power. In a less light polluted world.

§

Wikipedia link: Palomar 1 and National Geographic Society – Palomar Observatory Sky Survey.

captured colour data for STT 54 (Halifax)

The BGO imaged multi-star system Otto Struve 54 in Cam (aiming to GSC 04074 00075). Seeing was poor but I was after the colours...

The idea of STT 54 aka HD 21476 came from reviewing Haas's double star book. Her colour descriptions were intriguing. I get "pure white." But what's "bluish khaki?"

multi-star system STT 54 in colour

L 1x12 RGB 3x12 each. FITS Liberator, Photoshop. North is up; east is left.

STT 54 is the triad to the north, near the top of the image. A, the brighter of the close pair, is clearly white. The slightly dimmer partner to the north is... bluish. Yes, blue. It's a triple. Dim C is to the east-south-east. It's white or grey.

When I hear khaki in the context of colour, I think light brown. I have khaki style pants that come in all kinds of colours. The blue ones are dark. I checked artist Ingrid Sundberg's Color Thesaurus. I don't see "khaki" there. I might use "sky" or "sapphire" for the B star's colour.

The other stars in the field are very interesting. To the west, the solo dark orange ember. That's SAO 12785 with a B-V of 1.80.

The triangle to the south is made up of HD 21477 to the west, a K0 star, with a B-V of 1.27; SAO 12795 at the apex, B-V 1.83; and along the eastern shore PPM 14345, B-V 1.75.

§

Readjusted things a bit. I didn't like how dark the first result was. And I was a tad enthusiastic on the saturation.

multi-star system STT 54 in colour less instense

A little better. I like that more field stars show.

acquired all U Cam data (Halifax)

Took a while...

For fun, I wanted to image U Camelopardalis. It is a very red star, spectral class N! And a multi-star system to boot.

I first submitted a job on Nov 21, aiming at the nearby star TYC 40660 1091 1. The Burke-Gaffney Observatory robot accepted my request and queued me up. Then two nights later, BGO had a crack at it. But as I noted, it did not gather all the data, and this time I needed all the colour data. Dang. That said, the seeing was poor and the Moon was high.

I resubmitted the request with the exact same settings (I just copied the first message). It was put into the queue again without fanfare. Happily, that evening, the automated 'scope at SMU tried again. But, sadly, I was clouded out for a second time! Brother! Still, it was Moonie.

Sent in another ask. And this time, success! Gathered all the colour data for the carbon star. Not great seeing but no Moon around. I'll take it!

For all, FITS Liberator. North is up; east is left.

N-class star U Cam in luminance

Luminance only, 1 second subexposures, 12 stacked shots. Paint.NET. 

Glomed together the data for the red dwarf. Wow.

N-class star U Cam in full colour

Full colour processed image. LRGB. L at 1 second; colours at 3 seconds. Each channel 12 shots stacked. Total 2 minutes exposure time. FITS Liberator, Photoshop.

Look at that colour!

Also, U Cam aka BLL 12 is a double star. A, of course, is the bright orange-red furnace near the centre of the image; the B consort is to the north, above, the dimmer but still bright blue-white star. Well away (209 seconds of arc according to SkyTools). A fascinating contrast.

§

Wikipedia link: U Camelopardalis.

Wednesday, December 05, 2018

not tonight

Clouds. No chance to redeem myself.

did doubles checks

Did some follow up on the double stars from last night.



ARY 8

From the Washington Double Star database, I found two lines, suggesting a triple. Curiously, the first reported discoveries for both were in 1910. Both updated in 2015. I show the latest values.

00108+5846ARY   8
AB    100  39.1  8.13  8.63 B3IV
AC    43 104.3  8.13  8.29 B7V

The plotted position in SkyTools 3 Pro of B to A is 100° and 39". Good.

The plotted position to the other similar star to A was 43° and 104". Well look at that. So I did see the C comrade! OK.

The magnitudes inside ST3P matched too. Equal stars. Same stellar classes too.

I don't understand why the software didn't show it as a triple.



Struve 196

From the WDS. I was after the magnitude values this time.

01596+2100STF 196
AB    2015   41   1.8  9.36 10.92 G5
AC    2013   146  21.1  9.36 10.18 G5
AD    2015   9  199.7  9.36  6.01 K0III-IV
BC    2016   154  20.9 10.92 10.18
CD    2015   5  217.3 10.18  6.01

So, a quad system with magnitudes:

A 9.4
B 10.9
C 10.2
D 6.0

Interesting. A multi-star system where A is not the brightest. Not the first time I've encountered something like this. But intriguing that the brightest accomplice is the fourth star.



Sharatan

Huh. A fairly recent discovery with the first entry in 1988.

01546+2049MKT   3   
1988 93 0.1 
2005   113   0.0
2.6   5.2  A5V

But the separation values? 0.1 noted 30 years ago down to 0.0 a dozen years ago?! Wow. Nothing like was SkyTools shows. The PA is not bad but it is definitely not 69 arcseconds away.

I also check Stelladoppie for MKT 3. Confirmed it is a very tight pair, spectroscopic really. The rho or separation is never shown more than 0.065".

It is fast! 107 days... But too bad I will never see it.

the wrong comet (Bradford)

The comet photos on Facebook this morning, the Go call by the RASC Toronto Centre observing team for the dark sky session, another comet alert from Clear Sky Alarm Clock, and the rather optimistic Clear Sky Chart prompted me to put together a quick observing session. Let Rhonda know that I would be trying for a comet.

I updated SkyTools 3 Professional with the latest comet data. It showed 46P/Wirtanen would be magnitude 4.3. Wow. But it was 94 arc-minutes in size! Whoa, spread out. Located in Eridanus tonight, culminating between 10 and 11 PM. Some suggested it was a binocular target. The little ETX 'scope would be good.

At 6:32 PM, Tue 4 Dec 2018, I began preparations in earnest. Readied the Sony voice recorder. Noticed it was still on daylight saving time so 1 hour ahead. I compared the recorded time to the Windows 10 computer. The ICD-SX750D DVR voice recorder was about 1 hour and 5 minutes faster than John Max. Verified there was lots of space: 8 hours of time left. Noted the battery level was at the half-way mark.

Grabbed a basket to carry stuff out.

Switched to red lighting. Powered my LED desk light. Put red film on all the monitors. Forgot I brought home a pre-cut piece for "new" 19-inch i-INC monitors from CAO. It fit perfectly. The Lee Filter red film cut for my old 22-inch Dell monitor worked fine with a little bit of overhang. Put the smartphone into red mode too. Red LED flex USB keyboard light.

Got the ASUS netbook ready. Made a new SkyTools list with comet 46P as the first entry. Added a bunch of things, including some showpieces for Rhonda, and some doubles from my candidate list. Set the pairs as high priority. Noted a couple of other bright comets, brighter than mag 10. Planned to operate John Repeat Dance from the touchpad so to reduce equipment needed outside. About 8 high priority items.

Installed some AA batteries in the ETX mount. Keeping it simple and fast. No external power. Tested it: whir whir whir.

It was already feeling cold. The air temperature had dropped dramatically from daytime. My desktop Rainmeter applet was showing -6°C. Wow. Fortunately the wind speed was low at 3 km/h. I noted that Astrospheric predicted the ambient temp dropping to -9.

Clear Sky Chart - I'll take what I can get

The Clear Sky Chart showed the cloud cover to be low (clear), the transparency fair (below average), and the seeing would be good (4/5 or good). The numbers were specifically for 10 PM. Sounded like a good night for double stars!

I grabbed weather site data. Saved the CSC. Grabbed the Clear Outside report. Wow: Astrospheric showed us in a pocket. The rest of the province was socked in. Clipped it to Evernote too. I played with the Good To Stargaze parameters a bit but in the end it suggested the good times would end around midnight with increasing cloud cover.

It was 7:10 PM and I did some set up for the hand warmers. I started charging the electronic ones. I got out the butane one so it would be ready to fill. I checked the fuel requirements. I had previously noted 20mL I could go higher. OK. I would try that.

OK. At 7:22 I activated the high-contrast mode in Windows 10, something a RASC member had suggested a short time ago. Actually I found it pretty impressive. I wasn't expecting a good result but it acts a lot like what happens when I turn on red light mode in SkyTools. For programs that behave like Notepad and Windows Explorer (the file manager) and even Microsoft Word, they switched to light text on a dark background. Browser pages of course do what they damn well want to do. And Evernote for Windows does not offer dark mode (yet). Still I wouldn't use Windows high contrast mode without red film.

That let me do more work, quick reference card development, and get deeply dark adapted.

8:21. Noted the electronic hand warmers were fully charged. That was quick.

Around 9:30, I suited up. Long johns. Many layers for the torso including RASC vest. Dug out the ole winter coat with hood and the Baffin boots. Damn Pigeon toque.

Filled the butane heater. Used 2½ syringes, 25 mL, this time! I wasn't sure if the new fabric element would work. Couldn't remember if I had used it before. Used a candle to light it. Wasn't sure it was working at first but it seemed to be getting warmer. Did not burn down the kitchen.

Set up in the backyard. Adjustable height chair. Big metal Mamiya tripod with hex plate. ETX. Eyepiece case. Carry-all bag with misc. stuff. Netbook. Red (laser level) wrap-around glasses. Deep red flashlight. I even had the Pocket Sky Atlas in case of emergency.

Neighbours had their Christmas lights up. Dang. It flooded the backyard with light. White LEDs all along their deck railing...

Enjoyed the Seven Sisters naked eye.

Polar aligned the forks. Put the Celestron 26mm Plössl in the telescope. That would produce a magnification of 48 times.

And off we go.

Even 48 times magnification is too much for the Pleiades. Still I enjoyed the tight faint pale orange pair in the centre, two of the stars in CHR 12.

Where are my specs? Returned to the house for old specs, old eyeglasses strap, and simple dew shield. Brought out my telescopic pointer in lieu of a killer laser beam. Should have consulted my backyard checklist... Would have saved me a trip or two.

10:34. Was missing my voice recorder. Thought I left it inside. I'd get it on the next trip...

Sorted my observing list by the Optimum column. First up? Tried for V640.

Using the 3-panel "telescope" view or Visual Sky Simulation in SkyTools, I started my star hop in Cassiopeia. Successfully targeted Caph aka β (beta) Cassiopeiae. Noted double star HD 594, spotted it right away. Near Caph, HD 594 aka ARY 8 was nearly due south. Two equal stars, oriented east-west. They were near another star, similar colour and brightness, making it seem like a triple. I saw 2 other stars, fainter, to the north and west, in fact making it look like a quintuple system. Dim. Soft white or pale white-blue, all. Attractive. Carried on...

[ed: Didn't notice any shimmering!]

10:41. Ugh. With a separation of 1.55", V640 aka STF 3062 would not be splittable. It was on my double star candidate list but needs to be removed. It is a fast mover, it can stay on that list, as I should be able to split it in good conditions with a big 'scope. [ed: Haas says it is "grand."] But it is too hard for a primer programme, I think.

Next up was π (pi) And...

Rhonda returned home. I readied to view the comet. Spotted the Andromeda constellation, Aries. Oh, and Triangulum. Started at the β and γ (gamma) stars of Tri. It was taking a while, a challenging star hop. Told her I'd call when I found it. When I sure I was on the right star, I went to let her know. Coincidentally, she was getting ready to pop out again. I warned her I couldn't see anything. Hawk Eye did not see any fuzziness or aquamarine colour.

She was expecting the big OTA...

Briefly considered the camera on the barn door tracker...

The view through the 'scope was poor and the stars seemed to fade out. She noticed it too. It was the eyepiece fogging. The humidity was high. I had already seen a lot of frost. Gah. So much for a quick setup. Brought out the Kendrick dew heaters to combat the problem. Powered with the small NOCO lithium.

Remember in fact I had brought out the digital audio recorder... Fired it up.

I had another look at 11:25 PM. Confirmed I was in right area. Confirmed ST3P was in real time. Viewed SAO 55051, a mag 8.9 star, right where the comet should be.

I just remembered the transparency was supposed to be poor... Was that a factor? Probably.

[ed: It would help if you choose the correct comet. At the time, I accidentally aimed to 64P in Triangulum, not 46P! Crikey.]

11:27. Decided to move on.

Considered Sharatan aka β Arietis. Fairly close to where I was. Began the star hopping... Should be easy, such a bright star, at the bend in the simple constellation stick figure.

11:37. Stumbled across. HR 577 in Aries. Near Sharatan. Looked like a triangle, a flattened triangle. There was a bright bluish star at the top. Then two tight stars below or to my 7 o'clock, i.e. south. They formed a hockey stick. The two faint ones were much fainter and I thought orange. A quad system according to SkyTools. Sorry, the parent was Struve 196 or SAO 75075. The A and the D were wide, at 196 seconds of arc. Seemed odd. A and B were 1.8". Not possible in this little light bucket. A and C 21.8". Confusing. Where was the A star? It was not the bright one. The faint one at the bend! Weird. Strange designation.

[ed: Checked the the magnitudes in the software.]

starObject Infochart displayimpression
A10.8410.8dim-same as C
B12.0010.8n/a
C10.6010.1dim-same as A
D11.945.9bright

Regardless, a neat multi-star system for a small telescope.

[ed: Little surprised this is not in Sissy Haas's book.]

My eyes were watering like crazy. Frustrating. Missed my bifocals.

The butane heater was working great. The old Zippo fuel was OK!

11:42. I finally made it to Sharatan (or Sheratan). I saw a faint diffraction ring. I closely examined the field.

I decided there must be something wrong with SkyTools. There is no equally bright star 69" away. No way. I saw the pair of stars (not a double) to the north east, rather faint stars. That was a yard stick: they were about the same separation as what ST3P said the A and B stars of beta Ari would be. Sharatan would be a bit less. Verified I was in real time mode. Nope, nothing there. I'll have to look stuff up in the WDS...

Noted the skyward lens of the finder scope is dirty. Should be cleaned.

It was interesting to discover that the 8x21 finder diameter is a bit smaller than an old film tube. Huh. Could use one of those to keep the finder covered. Where did I put all those extras?

12:01 AM, Wed 5 Dec 2018. Was getting frustrated with the finder. Nearly useless.

A camera? What about a teenie tiny camera?

12:07 AM. At last, landed on 37 and 39 Tauri. A long hop sequence from the Pleiades, essentially starting at 28 and 27. A long drive to the east, eyepiece hopping. I found two doubles. A double double, actually. Cool. 37 was on the west. Yellow, bright. North was up for me. South of A was a much dimmer star and it was orange. Right or east was 39. Dimmer than 37. Blue or white. Wait! Pale yellow? No blue-white. It's companion was above or north. Orange. 39 A and B were wider than the 37 pair. Cool view. Two in the view. Two for one. SkyTools said 37 aka STT 558 was 134"; 39 or STT 559 was 177". Not on my candidate list. It would be great entry! I had copied this form a binocular list. This would work at low power and high power.

Rhonda popped out before heading to bed. Anything to look at? No comets, sadly. A pretty double double. "Oh, nice! Wow, bright." She liked it. She saw the dew heaters were working. Yeh.

I returned to the ocular. 37 yellow and blue. 39 white and orange. Some other field stars made for an attractive view.

My legs were starting to feel cold.

Keep going!

12:23. Landed at Menkib or ξ (xi) Persei. Sheesh. About a finder field away from my next target. There was a pair nearby (not noted in ST3P).

Nearly at ζ (zeta)...

12:29. Spotted Burnham 540 or HD 24601. I thought it was a pair; it is a triple. A and B very tight at 1.4". Did not split. Not in this little tube. A and C, 57.1" apart. Easy. Mag 8.7 and 9.9. Pretty dim. Right beside my target. A little bit north east. No pronounced colours.

Ho. Noted the tighter fainter pair to the east, HD 281382 aka SEE 33, with mags 9.2 and 10.4. About 26" apart. Angled toward the aforementioned pair. Yes. Saw them. Wow.

Last leg. On my way to ζ Persei now. Another candidate system to test.

12:33. Immediately saw a pair, dim, to the south. Those were the D and E stars. Tried to dig out others. I knew there were others but I was trying to find them without hints from the software. Nothing... nothing obvious.

[ed: Haas has but one entry in double stars for small telescopes, a pair at 12.7". That's the AB pair which I could not see.]

The eyepiece was fogging again. Whiskey tango foxtrot?

Damn! The NOCO battery was off. No lights. What happened? It was dead! Ugh. It went down fast! Well, that means I'm done... [ed: About 1 hour!]

Upped the power with the Tele Vue 9mm (139x), trying to coax out more stars. No joy. The diffraction rings were very pronounced. And I don't think perfectly round. Alas, I could not see additional companions. Still, it was a good test. It works at low power; it'll work at high mag. OK. That's it. Cold and perturbed.

Packed up.

Took in the whole sky to the south. Orion at the meridian. Meissa. Sirius in Canis Major. Canis Minor off to the east. Gemini up high. Oh, yeah, the Winter Football! So big. Hey, and the rabbit ears below Orion's feet.

High cloud in the south, streamers. Rather cold. Saw bright Sirius flicker for a moment but then stop. Right. It was very good seeing tonight.

Hauled the gear inside. Mixed feelings about tonight. Frustrating using the ETX and the ridiculous finder scope. It is so incredibly annoying. I've got to figure out a better way. The controls are challenging to operate especially when viewing near the zenith. The dew was a challenge.

Comedy of errors tonight, forgetting things, sitting in a perfect spot for a street light a block away to shine in my face, the touchpad not working on the computer, bringing outside a corded mouse, and then getting caught in cords, eyeglasses strap not working, still irked I can't find my good ones, the computer mouse falling to the ground repeatedly, battery dying, dying so quickly. It was a little discouraging.

But... But! I knocked down a few more doubles!

Thought of the RASCals down at Long Sault tonight freezing their oculars off.

[ed: Forgot to look for the ISS with Canadian on board... But that was at dusk.]

I didn't trip the motion sensor light once tonight despite all my trips to and fro.

1:06. Inside, warming up, I pulled the current wx data.

From Environment Canada for Newmarket. No Alerts in effect. Clear, -7°C. Observed at: Toronto Buttonville Municipal Airport. Date: 1:00 AM EST Wednesday 5 December 2018. Condition: Clear. Pressure: 101.9 kPa, falling. Temperature: -6.6°C. Dew point: -8.5°C. Humidity: 86%. Wind: N 2 km/h. Wind Chill: -8.

Detailed Forecast issued: 3:30 PM EST Tuesday 4 December 2018. Tonight, Partly cloudy with 30 percent chance of flurries. Wind up to 15 km/h. Low minus 7. Wind chill minus 4 in the evening and minus 10 overnight.

§

Oh oh. Learned my big mistake. Too late... Went to the wrong comet! Brother... Realised this as I transcribed and compiled my notes. Damn it!

§

The butane heater was going strong as I went to bed. So 25 mL of fuel was plenty offering over 6 hours of high heat.

§

Looked into some of the double star issues...

Monday, December 03, 2018

to infinity

Saint-Jacques away!

Monday, November 26, 2018

InSight lands

The NASA InSight probe successfully landed on Mars.

InSight landing location according to Eyes

Now waiting for solar panel deploy and a first camera image.

§

An amazing part of this mission was the use of cube sats flying in tandem to relay data.

§

The first image was received at 15:00 EST. Up is up and left is left! ;-)

Friday, November 23, 2018

tried for U Cam

I had also loaded a request for BGO to capture U Cam, a very red star. Sadly, the job didn't complete, due to stoopid clouds, so I'll have another go later.

§

Collected all colour data on 7 Dec.

aimed at HD 20588 (Halifax)

Fantastic! I had selected this Camelopardalis target from Sissy Haas's book partly for the interesting colour descriptions... "Gloss white, peach white, bluish khaki." OK. She shows the labels OΣ 373 (for AB) and OΣΣ 33 (for AC). For fun I requested HD 20588 and BGO captured the data.

multi-star system STF 373 / STTA 33 in luminance

North is up; east is left. Luminance only, 1 second sub, a stack of a dozen shots. FITS Liberator, Paint.NET.

Now SkyTools 3 Professional refers to these stars as STF 373 and STTA 33. Who is right?

Clearly a quadruple system. Haas only notes 3 stars.

A is the brightest element in the centre of the image.

B is the tight companion to the east-south-east. The dimmest of all in the group.

C is the bright star further along, past B.

D is to the south of the partnership, less than A and C in luminance but brighter than B. ST3P shows this star is designated STU 1.

Looking forward to working this in colour...

There are other neat groupings of stars in the field.

§

Checked the Washington Double Star catalogue and found:
03221+6244STF 373AB
03221+6244STTA 33AC
03221+6244STU   1AD
So it's a little mistake in the book and ST3P is right.

§

Assembled in colour on 12 Dec '18.

HD 20588 in colour

RGB 3x12 each. FITS Liberator, Photoshop.

A is a soft pale orange. B is a touch darker orange. C and D are a dusty pale light blue.

imaged Struve 219 (Halifax)

Full Moon. So I asked for a double star. HD 13247 aka STF 219 in Tri. For fun. The BGO returned this:

double star STF 219 in Triangulum in luminance

Luminance only, 1 second subexposure, 12 in the stack. FITS Liberator, Paint.NET. North is up; east is left.

The B companion is slightly dimmer and nearly due south. Interesting field stars...

My SkyTools software shows three tight stars on the chart but that must be an error. I don't see anything between the bright pair. At the same time the planning app says HD 13247 is a double with a mag 8 and 9 star separated by 11 seconds of arc. The software allow shows a colourful star to the south-west. It will be interesting to work this in colour...

Oh, the pair was on my DS candidate list... I'll have to check it visually.

There's a faint pair of equal stars, even tighter, to the north-east. No designation. Neat.

The zig zag of stars to the south, to the edge of the image frame, is intriguing. There are two sets of three stars aligned...

Wednesday, November 21, 2018

darkness

Dark mode arrived to Evernote! Woo hoo! Well, for iOS and Android. Still waiting for Windows and the web. A lot of us (including Robert Sawyer) have been asking for this, for years.

screen snapshot of Evernote in dark mode

This will improve on dark adaptation when I need to check my notes while at the telescope.

Once they deploy this for the other platforms, I can finally transition from using Windows Notepad for live logging...

your monthly double stars

Issued my double star "bulletin" for November. It is a short list of suggested double and multi-star targets. I shared this on the RASC Toronto Centre forums. And I post here for all.

§

I don't know why I bother, really. I mean, we're not going to see stars at night until May 2019, right?!

Anyhoo, if you're lucky to get the odd clear night between now and then, pop into the back garden or onto the deck and have a look. Double stars are visible from anywhere, even in the city, and any time, even with a bright Moon.

Here are some suggestions:

staralso known asalternate catalogue 
59 AndΣ222SAO 55330
32 Eri(Struve) Σ470SAO 130806
γ (lambda) AriMesarthim or Σ180SAO 75051
66 Cet(STF) Σ231SAO 129752
77 PscΣ90SAO 109666

Happy hunting. Let me know how you did!

Blake Nancarrow
astronomy at computer-ease dot com

Wednesday, November 14, 2018

Binary Universe: checking sidereal time

The December 2018 edition of the RASC Journal celebrates our 150 years looking back to its early days and origins to current activities today. I look forward to reading every piece within.

cover of the Dec 2018 edition of the Journal
Whoa! A greeting from the only governor general who has flown in space, Her Excellency the Right Honourable Julie Payette! Very cool!

The article by Mr Rosenfeld on art inspired by astronomical things looks fascinating.

Mr MacDonald has returned to masks in photographic image manipulation. I still struggle with this.

In my Binary Universe column, I discuss time, specifically determining sidereal time (as I need to do now when calibrating the DDO's 74-inch mount). I talk about Stellarium, SkySafari, Polar Finder, MySiderealTime, SkyTime, Astro Clock Widget, and Emerald.

found the December Journal

Wait a second. If Jeff was thanking me for referring him to the Astro Clock Widget, then that meant he had read the RASC Journal December edition! Oh. It's been released. I hadn't seen a notice anywhere... I surfed into the national web site, logged in, and spotted the latest. OK.

Jeff thanked me re. ACW

Jeff pinged me via email. Thanked me for the tip on the Astro Clock Widget. No worries.

Tuesday, November 13, 2018

a moon, a planet, a star (Bradford)

Spotted the young Moon as I walked from the train station.

Quite far to the left I tagged a tiny but intense orange point. Ah. Mars.

I briefly considered setting up. But it was late. I hadn't had dinner. My stomach was growling. It wasn't perfectly clear...

And then, while northbound on Toronto Street, shimmering Capella.

Bad seeing.

rockets!

There was a bowl at reception filled with candy from Hallowe'en. "Rockets!" I exclaimed. I was encouraged to take some. I stuffed my pockets!

Rockets candy

Did you know that Rockets were made by Eddie Dee? The Ce De Candy Company Limited, now known as Rockets Candy Company, started making Rockets on Queen Street, Toronto in 1963.

Monday, November 12, 2018

received OH 2019

Woo hoo! Found the RASC Observer's Handbook 2019 in the mailbox!

Observer's Handbook 2019 edition

Rhonda asked what was on the cover. The Flying Bat and the Squid apparently.

imaged Palomar 1 (Halifax)

I continue to try to "see" the Palomar globular clusters. This is Palomar 1 in Cepheus.

Centering on the star GSC 04517 01909, I commanded the Burke-Gaffney Observatory to gather some photons. Can you see it?

faint Palomar 1 cluster in luminance

Luminance frame, 10 seconds, 10 subexposures. Apogee camera.

The globular is the small, faint, gathering of dim stars slightly below and right of centre.

These objects are extremely challenging. So I don't know what I was thinking exactly with respect to the exposure settings. 10 seconds?! Will try again with a much longer exposure time.

Sunday, November 11, 2018

more operator training

We did more training on the 74-inch telescope. There were about a dozen in the session. We spent some time working on our presentation, conveying science information and some history of the David Dunlap Observatory facility. Chilly in the dome!

Saturday, November 10, 2018

helped at musical astronomical evening

Helped at the RASC Toronto Centre special event Beyond the Skies held at the David Dunlap Observatory.

This was an unique evening with jazz music by The Calderons, regular alcoholic beverages along with themed cocktails, and some astronomy. Amazingly, we had clear skies. I wore a few hats. I helped with audio-visual setup and teardown for the band and the speakers Ian W and Bhairavi. With my new Smart Serve certification, I assisted Reanu at the bar. And I helped with general tasks too.

I was surprised to get asked to debug an issue for Denise and Chris with the 74-inch telescope. Busy night, long, but lots of fun.

Peter V shot photos and loaded them up to a Facebook album.

interesting astro-beers served at special event

We offered a couple of science-themed beers. In addition to Space Invader and Cosmic and Corona, we had a couple I hadn't heard of: Thrust! An IPA and Lost In Orbit. Thrust! is by Great Lakes Brewery while Lost in Orbit, an IPA session beer, is by Nickel Brook Brewing.

Monday, November 05, 2018

shot Spirograph in narrowband (Halifax)

Along with the LRGB information, I retrieved narrowband data on the Spirograph planetary in the constellation Lepus.

Spirograph planetary nebula with H-alpha filter

Hydrogen-alpha, 60 seconds subexposures, 10 stacked shots.

Spirograph planetary nebula with O-III filter

Ionised oxygen, 60 seconds subexposures, 10 stacked shots.

For both, FITS Liberator and Paint.NET. North is up; east is left.

shot Spirograph in colour (Halifax)

Sort of. I wanted to image the Spirograph Nebula, IC 418, again. I overexposed the small planetary nebula in my first attempt in January 2017. So, shot 4 times faster this time.

Spirograph planetary nebula in luminance

Luminance only, 15 seconds subexposures, 10 stacked shots. FITS Liberator, Paint.NET. North is up; east is left.

I also wanted to get narrowband data.

Won't see this in full colour of course until I do some work in a photo editor...

Sunday, November 04, 2018

tried NGC 281 again (Halifax)

Shot the Pac-Man Nebula (NGC 281) again, aimed at TYC 36630 06351. I was hoping to avoid gradient and satellites in the colour data...

Pac-Man in luminance

Luminance frame at 30 seconds and 10 subexposures. FITS Liberator and Paint.NET. North is up and left is right.

Finally got some good LUM data! No nasty gradient at the bottom. No airplanes. No satellites. No tumblers. Pretty good registration. I'll take it.

I had last worked on this object in August 2016.

captured tangled galaxies (Halifax)

For fun, I asked the Burke-Gaffney Observatory to image the two entangled galaxies in Arp 278.

interacting galaxies in Arp 287 in luminance

Luminance frame at 60 seconds, 10 subexposures, FITS Liberator, Paint.NET. North is up and east is left.

These are interacting galaxies NGC 7253A and NGC 7253B.

§

I tried to visually observe this pair on 24 Sep '17.

real not real

As the crew departed the International Space Station in early October, they did a fly-around, something not done since the shuttle missions. They acquired some amazing imagery. But one really struck me, reminding me of one of the iconic images from 2001: A Space Odyssey.

Fiction:

orbital station from 2001: A Space Odyssey

Non-fiction:

orbital station by international partners

Now, admittedly, it's not an apples to apples comparison on a number of levels.

It's the imagery that impressed me, the composition, the similarities in the framing.

Copyrights and credits by the respective parties.

See the whole set at SpaceflightNow.

§

NASA made their own comparison a few years back...

proofed

Proof read my next Journal article.

Thursday, November 01, 2018

fuzzy Moon (Bradford)

Spotted a fuzzy old crescent Moon in the sky while walking to the train station. Surprisingly high up. Couldn't see anything else. No bright points of light could punch through the cloud.

§

Stellarium said it was about 56° in altitude.

Sunday, October 28, 2018

the first astrokitty

Everyone knows about the first barker in orbit, Laika. But did you know about the first kitty?

1963 rocket launch with cat Félicette

Félicette was the first cat in space launched on 18 October 1963. Just over 55 years ago.

Sheesh. Can you imagine?! Every kitty I've had hated, I mean H-A-T-E-D, car travel. Can you imagine the howling inside the space capsule?!

Saturday, October 27, 2018

reviewed CTC suggestion

I heard back from Canadian Tire Customer Relations yesterday. I had resubmitted my query (from May) about a replacement battery for the Sealake FM12330 inside the Nautilus power tank.

Their direct remark:
Thank you for your further correspondence on your battery inquiry.

We reviewed the response sent to you on May 9, 2018.  We had forwarded our buyer's response to your exact inquiry.  He detailed what battery we stock could work but suggested you bring your old battery and power pack to the store to insure an exact fit.  It was also suggested that if the battery did not fit that the next best option was to search online.

The buying [SIC] further indicated that they are considering adding replacement batteries to our assortment and future models for this product line to be more accessible for replacement.

We thank you for providing us with the opportunity to respond.
The buyer response:
Our 010-2051 battery may fit as a replacement.  I say may because, sometimes, even the slightest variance between batteries (1-2 mm L or W or H, or slightly different position of terminals, or some other obstruction like a vent cap, etc.) can make all the difference.  I suggest the customer take his old battery AND power pack with him to the store to ensure the 010-2051 will fit perfectly before he buys it.

If our 010-2051 battery does not work, the customer may search online of other options – essentially he's looking for a Group Size U1 SLA battery.  They go for around $100-130 (which is why most people don't bother repairing when you can buy an entirely new power pack for about $150-200 on sale).  I have included specs of the original battery in the Nautilus power pack for his reference.

We are considering adding replacement batteries to our assortment.  In our future models, we are looking at making the batteries more user-accessible for easier replacement.
I reviewed the CTC 010-2051 battery details. I note differences and particular items here...
  • it is an AGM sealed lead acid battery but I don't think it is specifically a deep cycle so, even if it fits, I'm not sure it will work per se
  • it is rated at 32 Ah vs 33
  • its size 184 x 130 x 152 mm thus smaller in width and height but... I do not yet know if the measures include height of posts/terminals
  • the terminal posts are different, thicker than the thin ones on the Sealake
  • it is heavier by 1.5 kilos than the Sealake (maybe it is a deep discharge...)
  • I do not know the terminal orientation...
I'll take the old Sealake into my local to do a head-to-head comparison of size and terminal orientation.

§

Forgot to provide a link to the battery product page at CTC...

§

Looks like someone from Canadian Tire responded (on 9 Nov) to my question! The height of the battery INCLUDES the height of the terminals. This again suggests this battery would fit inside the case... I still plan to do a visual comparison though.

Sunday, October 21, 2018

helped at the CAO

Helped at the Carr Astronomical Observatory work party. Rhonda too. Amazingly, the weather cooperated.

Started off Friday night deploying a new wireless access point (donated by Bruce Street Technologies). I worked, as usual, on small motors. Maintained the generator. Maintained Blade Runner and Green Flash, the walk-behind and ride-on mowers, respectively, while Stargrazer was hauled to our local mechanic for an assessment. Examined another small motor unit that I had previously overlooked. Updated our motors parts and supplies inventory. I installed a new uninterruptible power supply in the main observatory so to support the local area network for the MODL users. Tested the Tony Horvatin Observatory roof rotation and the Sue Lora Observatory roof sliding. As others upgraded the cameras, I installed and configured the new surveillance appliance. As the first in line for worker support, I took a lot of questions. I also had a chance to photograph the printed circuit board inside the Paramount ME.

This on top of the weekend supervisor duties.

Rhonda was captain of team Algieba. They finished all their tasks included the trenching job!

§

Ian D shot some shots, which he shared via his flickr account.

upgraded Arnold's paddle

Friday

When I saw that Arnold was heading to the CAO for the work party, I reached out. Asked if he wanted to upgrade his NANJING IDEA GoToStar hand controller. He had been thinking the same thing.

I packed my Vixen Super Polaris mount bag sans counterweights, Prolific USB-serial converter, and ASUS netbook computer. I pre-installed all the software bits including iOptron "downloader" firmware transfer program, the Chinese version of the GTS downloader, and my copy of the 2009 firmware binary .BIN file. Tried to access the English version of the old version 1.0 GoToStar downloader but Yahoo!Groups decided to be cranky.

Saturday

Around dinner time Arnold brought in his mount kit from his trailer and asked where I wanted it. Ah, anywhere. That was a little odd. And then when I was available, he was nowhere to be found. He had gone to bed, leaving me to do that task. Huh. OK. I thought he might want to help and observe. Alas, I readied to apply the update.

I first connected my supercharged Vixen mount to all the iOptron gear and connected to the John Repeat Dance computer and drove the mount from SkyTools. All was well.

I unpacked Arnold's gear. An EQ mount I didn't recognise with GoToStar motors attached. Same white hand controller. Clearly strained cables with internal leads visible. Ugh. He did not have an AC adapter so I used mine. Connected my computer-control cable. Fired up his system. The HC showed version 060714. Right.

I tried the GoToStar downloader 1.0.1, Chinese version. No joy.

Tried the Yahoo!Groups again. Success. The file server was up and running. I downloaded the GoToStar downloader 1.0.1 Global in Anglais. No joy connecting to the hand controller.

Weird. The paddle said "Comm. with PC" and the PC app said transferring, wait, but nothing happened. The progress bar did not advance.

Not hopeful, I tried the iOptron downloader v2.0. Nothing.

I tried different serial port references. Initially COM6 and then COM5 and COM2. No joy.

To verify general comms were good overall, I fired up SkyTools. I could slew his mount. Strange. Discouraging. I packed everything up and prepared to relay the bad news.

Sunday 

When Arnold appeared late-morning, I gave him my report. He thanked me for trying. But I told him I had one more idea. Perhaps we could avoid serial-USB conversion.

I had Arnold help me with set up...

I used CAO GBO Dell laptop with its built-in standard serial COM port. Progress bar! It worked! Well. Partly.

We were able to install "08" version but NOT the "09" versions. Tried mine and the W from Yahoo to no avail. So, not ideal, but this gave him beep control, fixed the spelling of "electric," gave him three-star alignment. I also noted the new "upgrade firmware" from within the handset.

The firmware loader software must have been sensitive to the USB-serial chip...

Good enough, we agreed.

Friday, October 19, 2018

never tried in 35 years

Tom sent a note on the RASC TC forums...
Keep the lists coming - just got a copy of Sissy Hass's book devoted to doubles for small telescopes - absolutely invaluable!

Seeing your presentation a few members nights ago opened up this aspect of our 'hobby' I had never really considered in 35 years of visual observation.
Wow. That's neat that he's pursuing new targets after all these years.

got books?

Peter sent a note in response to my double star prompt: "I'm sure the Blake will be happy with my latest purchase." He shared a photo of the Pocket Sky Atlas Jumbo Edition and double stars for small telescopes. Yes. Yes, I am happy.

your monthly double stars

Issued my double star "bulletin" for October. It is a short list of suggested double and multi-star targets. I shared this on the RASC Toronto Centre forums. And I post here for all.

§

With the Moon all full and bright and moony again, it's time to take in fantastic double stars.

Here's a short selection of doubles from my life list, ones I find rather interesting. I did not include terribly tight targets.

staralso known asalternate catalogue 
Σ2819 CepHD 206482SAO 33652
Σ2816 CepHR 8281SAO 33626
Σ2902 LacHD 212468HIP 110539
η (eta) PerMiramSAO 23655
94 AqrSTF 2998SAO 165625

Be sure to add doubles to your observing list. They resist light pollution, are easy, colourful, and fun. Let me know how you did!

Blake Nancarrow
astronomy at computer-ease dot com

Thursday, October 18, 2018

double take on Mars (Bradford)

Noted the Moon and Mars about 5° apart during the walk home from the GO station. Gibbous Moon. Mars to the right (east). In fact, it was fairly clear. Lots of stars visible.

Tuesday, October 16, 2018

streethenge (Bradford)

Walking home from the GO station, through the old part of town, I noticed the alignment. Welcome to Bradfordhenge.

Sun aligned with old Bradford streets

alcatel somewhat smartphone, 4mm, Open Camera app, f/2.8, 1/303th of a second, ISO 76, automatic white balance, Paint.NET.

Monday, October 15, 2018

imaged the amazing Pisces Cloud (Halifax)

It's filled with galaxies.

For fun, I commanded the BGO to aim at the Pisces Cloud, a galaxy group also known as Arp 331, centring on New General Catalogue object 383. Wow.

the centre of the Pisces Cloud galaxy group in luminanance

Luminance only, 60 seconds subexposures, 10 stacked shots. FITS Liberator, Paint. North is up; east is left.

There are so many galaxies in this shot. I can see many in my long exposure... But only a few are identified in Aladin/SIMBAD and my SkyTools 3 Pro software.

ST3P calls NGC 383 the Pisces Cloud. That's a little odd. It also shows NGC 383 may be referred to as MCG 5-3-53 or PGC 3982.

The bright elliptical galaxy north-north-west of NGC 383 is NGC 380. 380 is also known as Arp 331, MCG 5-3-51, and PGC 3969.

Due north of 383 and due east of 380 is the tiny nearly-round LEDA 1998992 galaxy.

Between 380 and 1998992 is LEDA 1999066, a small smudge. Dimmer than 1998992 but about the same size.

North of 380 is NGC 379. This looks like a canted spiral galaxy. Or maybe a lenticular. ST3P says aka Arp 331, MCG 5-3-50, and PGC 3966.

There's a flattened triangle of bright stars north of 379. Above or north of the brightest star is the elongated smudge of 2MFGC 815. SkyTools calls it LEDA 2003479.

It sure looks like there are a bunch of faint galaxies here... oriented horizontally.

West of this same triangle is a very dim shape, small. 2MASX J01065374+3234434. Also called LEDA 2003331 according to ST3P.

North-west of 383, nearby, is medium-sized oval fuzzy. That's 2MASX J01071798+3225281. ST3P calls this LEDA 197570.

Nearly due west of the 383, well away, below the tight triangle of stars is the stretched smudge of LEDA 1995971.

Between but a bit south is the edge-on spiral galaxy UGC 679. ST3P also notes this as MCG 5-3-49 and PGC 3950.

LEDA 1993906 is the small non-round blotch south-west of 679.

Further along, further south-west is another similarly sized oval: LEDA 1992085.

NGC 382 is the round small but bright galaxy near 383 to the south-south-west. ST3P: Arp 331, MCG 5-3-52, and PGC 3981.

Further out is 2MASX J01071026+3220485, a soft blob. It's to the west of the right-angle triangle of stars. Known as LEDA 1992625 in ST3P.

West of the aforementioned galaxy is a bright fuzzy, round, but still quite small: NGC 375 aka PGC 3953.

And further still is another round small elliptical: NGC 373. Or PGC 3946.

Nearly due south of NGC 383 are two more ellipticals, practically the same size, but at slightly different angles. NGC 385 (Arp 331, MCG 5-3-56, and PGC 3984) is to the north and NGC 384 (Arp 331, MCG 5-3-55, and PGC 3983) is to the south.

NGC 386 is about half the distance of 385 but slightly east. Smaller and dimmer. SkyTools also calls this Arp 331, MCG 5-3-57, and PGC 3989.

2MASX J01075199+3215217 is much further away but inline with 386. Very dim. Round. SkyTools says it is LEDA 197572.

Aladin notes 2MASX J01073307+3223282 to the south-east of NGC 383. It is dimmer than 386. Smaller. But the core is slightly dimmer. SkyTools calls this NGC 387 or PGC 3987.

NGC 388 looks like a spiral galaxy, canted at an angle, due east of 385 and 384. aka Arp 331, MCG 5-3-59, and PGC 4005.

East-north-east of 383 is NGC 390. Another galaxy disc tilted. SkyTools called this PGC 4021.

North of 390 is 2MASX J01081590+3229567. It looks like a clone of 390 but smaller and dimmer. Maybe further away. ST3P also notes LEDA 1999738.

The curving string, from north to south, of NGC 379, 380, 383, 382, 387, 386, 385, and 384, is really neat, pearls on an necklace.

A dozen total NGCs in one shot. Wow.

§

Wikipedia links: NGC 383 and Arp 331 (en Français).

[ed: "a dozen" corrects from "ten."]

Saturday, October 13, 2018

fluffy dark matter

Watched Dr Laura Parker's talk on the dark universe recorded at the 26 Sep RASC meeting. She's an excellent speaker. I was most impressed at her answers in the Q&A after. Parker clearly has a very deep knowledge of this incredible domain.

Chris asked an interesting question (around the 44 minute mark). He noted an inverse relationship between the luminous and dark matter in the rotational speed graphic. He asked if dark matter doesn't like regular matter or doesn't want to occupy the same space.

Parker shared that there's a good relationship with matter distribution. But at large radii the dark matter becomes more prevalent than the visible matter. And there's good physics to explain this. The regular matter collapses and sinks to the middle of the galactic region so to form the galaxy and in the process radiates energy. Meanwhile the big ball of dark matter does not collapse, in can't shrink, it cannot give off radiation, so the dark matter remains fluffy and big.

I took lots of questions from Rhonda hopefully clarifying things about dark matter and dark energy.

captured Keid (Halifax)

I was a little surprised to see a couple of emails from the BGO robot this morning. There must have been a break in the clouds. Or better conditions than predicted.

I had had a request for ο (omicron) Eridani aka Keid, the multi-star system. The SMU observatory gathered good data, after aiming at GSC 05313 00997. Looks like a lovely triple!

multi-star Keid in luminance

Luminance only, ½ second subexposures, 20 stacked shots. FITS Liberator, Paint.NET. North is up; east is left.

The part of the reason for imaging this system (Struve 518) was because I wanted to double-check positions. When I last viewed this target on 19 Mar '18 from the backyard, I had noted the B star in a very different position than it was noted in SkyTools 3 Professional. ST3P shows B at a position angle of 65°. At the time I thought it approx. 60° different from that, counterclockwise in my SCT, therefore an increase in the PA, perhaps 125°. It is obvious in the image above that B (and C) are to the east-south-east. That's a PA of roughly 100°. Curiously, ST3P states in the Object Information box that the AB angle is 104° as of 2002. Here's an instance where the visual chart is very different than the OI data and it threw me off back in March.

Also, SkyTools notes another pair: Aa. With a PA of 97 and separation of 77.9. But it seems, early in 2018, I did not see this companion either.

The Washington Double Star database shows the Keid is a 5-star system with the following data:

pair first last PA1 PA2 sep1 sep2
A,BC 1783 2016 108 102 89.2 83.7
AC 1987 2011 117 97 79.4 77.3
AD 1850 1998 197 38 128.3 481.4
AE 1850 1998 279 24 99.4 569.9
BC 1851 2017 160 331 3.0 8.3
BD 1922 1999 196 28 147.0 457.0
BE 1922 1999 356 16 279.5 563.7

SkyTools lists the A, B, and C stars. The D and E stars from the WDS are mag 12-13 stars well away. They are visible to the north-north-east in the image. I'm curious why the bright, closer star beyond BC is not included.

The BC, BD, and BE alternate measures support the main entries.

plot of Keid stars for 2018

A plot, using the current or most recent positions, from my Excel mapper tool. Good correspondence to the image.

It looks like for the A-to-B data, there's been little movement. It seems the C is moving about B. SkyTools and other sources quote the B-C orbital period around 250 years.

But the D and E values are kinda crazy. I'll consider that this is not real motion but errors in the original observations.

The SkyTools Aa entry looks suspiciously like the WDS AC datum. I think therefore I should discard it.

By the way, Wikipedia says 40 Eri is a triple.

§

Wikipedia link: 40 Eridani.