Friday, December 30, 2022

processed NGC 3079 in colour

Processed NGC 3079 in colour. A RASC Finest galaxy in Ursa Major.

This was captured back on 5 Feb '17.

Came out fair this time. No nasty gradients on the RGB frames. Visible gradient on the luminance but I cut the opacity and that helped a bit.

galaxy NGC 3079 in colour

FITS Liberator 4, Photoshop CS2.

The usual workflow steps but again I reduced the opacity of the luminance layer, as I had boosted it dramatically in FITS.

Did star shrinking. Photoshop crashed the first two times! Gar. Had to redo, remembering to save at key milestones.

Gaussian blur at the end to soften the pixels.

As I look at it now... I should have used GraXpert.

read about fuzzy dark matter

Read (to be honest, skimmed) the paper entitled On the Cosmic Web Elongation in Fuzzy Dark Matter Cosmologies: Effects on Density Profiles, Shapes and Alignments of Halos.

Tibor Dome et al discuss the fuzzy dark matter scenario over the Lambda cold dark matter (ΛCDM) cosmological model especially given that there is still no experimental evidence of particles.

Paper is available for download in PDF form from the Monthly Notices of the Royal Astronomical Society.

They expect FDM-like imprints on the internal properties of virialised halos to be strikingly visible in the high-z Universe which our new telescopes should reveal.

I don't fully understand all this but I'm encouraged to see more and more research being done to challenge the ΛCDM model. 'Cause in my old failing bones, it doesn't feel right.

Something's missing.

Maybe it's fuzzy dark matter.

set it in pen

We are a GO!

I set the date and time in Zoom meetings.

If you're a RASC member and you wanna learn how to use Backyard EOS, sign up now, sign up often.

Fill out the course registration form.

Space is limited...

found a bug

Noticed something odd in Backyard EOS the other day.

I think I found a bug...

My initial observation was on version 3.1.18 on John Repeat Dance.

But I just tried it now on John Kim Chi running version 3.2.2.

Still there.

When your apply a stretch to the image in Preview or Imaging mode to the photo in the Image Center and then transform the image, say using the flip or rotate buttons, the stretch gets re-applied. It accumulates. After a few clicks the image is blown out (assuming you boosted the shadows and highlights).

blown out image after stretch re-applied

Happily, you can quickly recover by clicking away to another image in the thumbnails and then clicking back on the original.

Reported this most recent datum point to the crew on the O'Telescope forums...

Thursday, December 29, 2022

remembered I reached minimum

Oh yeah.

Some time ago, during a trainers meeting, we had agreed to the minimum number for running a class.

6.

And today I loaded in participants 7 and 8 to the new Backyard EOS course.

We are a GO!

Guess I should pick a date!

Very exciting.

asked if I should cancel

My last calendar order has not been fulfilled and it's been 30 days. My friend Cam proactively updated me this time; I asked the last time.

Posted on the forum.

Messaged my national contact. Received the OOO. Right, office closed.

What a joke.

I asked if I should cancel.

Wednesday, December 28, 2022

apropos notepad

Donna grabbed a notepad and pen for me.

I jotted my current medications and forwarded what I needed to remember to take tomorrow.

Then I noticed the style of the paper sheets.

notepad sheet with the Moon and some stars

Moons and stars!

She hadn't noticed.

made the almanac

Popped into COELIX APEX.

Entered in a new station for my place in St Thomas, The Elevator. Ran the Graphic Almanac for the new year. Extracted portions.

Here's the graph for January only.

graphic almanac for January

And here's the list of notable events.

almanac events for Jan 2023

Didn't work it into the format I used before, with the legend.

The planets:

  • grey - Mercury
  • white - Venus
  • orange - Mars
  • yellow - Jupiter
  • green - Saturn
  • aquamarine - Uranus
  • dark blue - Neptune

Other:

  • light blue - midnight

There.

BANG

That didn't take long!

The first registration for the BYE training course is in!

announced the BYE course

It's live.

Pulled the trigger.

Launched the course.

Posted in the RASC general forum that the Backyard EOS course is available!

Shared the link to the course information page with link to the registration form.

Let's see what happens...

proofed a PDF

Proofed my Journal column.

Couple of issues.

updated BYE materials

Updated my QRC for new/different features in Backyard EOS, version 3.2.2!

Updated the the RASC web site.

Also made better notes around Premium features.

found BYE 3.2

Well. That was interesting.

Started up the old Dell, John Gomez, and found Backyard EOS 3.2 installed! Um, on a computer with a 64-bit OS!

Oh, oh yes, and ASCOM. (I use this machine for teach Stellarium including the level 2 intermediate course with the mount remote control topic.)

Uh huh. I had done this. I had used it before. And I had the upgraded version of BYE.

So, played around for a while. Took screen snaps. Noted the differences.

Got some homework to do...

But the thing that's confusing is that I thought for sure I read somewhere that this would not work on Windows 10 with an old camera and its old Canon drivers.

No issue for me!

Worked fine.

So I'll have to re-read those notes. Meh.

The good news, the reduced stress news, is that I have a good solution. I have a working late version of Backyard on a new (newish) computer. And that means I can lug around this beast of a laptop for imaging. More immediately, I can use this machine as the teaching platform.

tried to upgrade BYE

Another dead-end.

Double dead-end?

Is that a thing?

While doing all my Backyard EOS prep, I had noted the versions... and the delta.

I have BYE 3.1.18 installed on John Repeat Dance. This is the old-as-dirt ASUS Eee PC 1000 netbook running Windows XP, 32-bit no less. Backyard works fine. Though it is a slow processor. It works and it has served me well and I'd like to continue using it as long as possible.

On the O'Telescope website/forums, I noted the latest "official" stable version of BYE was 3.2.2. And there's some chatter about Release Candidate 3.2.3. So I couldn't help but wonder if I should use the latest version.

Downloaded 3.2.2 without incident.

Ran the installer. And it was almost done when it threw an error. A bit of a weird error. 

install error during BYE 3.2 install

I found a thread on forums by Santiago regarding a similar issue.

The response?

Your computer is too old.

But also noted some forum threads on issues with the Canon drivers. 

I have a feeling I cannot use the new (relatively new) John Grim computer. This is a Surface Laptop Go with Windows 10, 64-bit. I think I'm hearing that the drivers for the DSLR camera body I have are old. Too old. And won't work on Win10-64.

Old computer. Old camera.

If all this is true then there's no upgrade path at all. No way ahead on the XP. And no way on the Surface, disappointingly.

In another post, a camera owner was told they should sell their 20D.

Would they say the same to me? Get rid of that clunker 40D.

Gah.

After a bit of digging I found the release notes for the successor BYE versions. I examined these considering the impacts to my future (impending) training level 1 introductory course...

3.2.0   

  • NEW FEATURE: Added DARK_FLAT option in imaging session plan.
  • CHANGE: Serial cable test button moved closer to cable support pulldown.
  • CHANGE: Mirror lock field in capture plan is now hidden. See advance setting to enable it.

3.2.1

Nothing notable.

3.2.2

  • NEW FEATURE: Support for EOS M50m2 (mirrorless)
  • BUG FIX: 4k DPI resolution.

3.2.3 RC3

Nothing notable.

So, that was a little bit of good news. I had been worried that my development under 3.1.18 was asking for trouble if there had been major changes in the software up to 3.2.2.

I think I'm OK. For the training framework.

But there is the issue, a personal one. Gotta keep the ASUS alive... If some new fantastic feature appears in a future BYE version, it will make for some difficult decisions.

§

Wait a minute...

Dug through the blog. I do believe on 23 April 2021 I installed 3.2.2 to the one of my computers. Sounds like it was John Gomez, the Windows 10 laptop, 64-bit machine. And that it all worked. 

Hmmm. Maybe I should have a look at that bad boy... tomorrow.

Tuesday, December 27, 2022

made the BYE pages

I did a thing.

I made a web page.

Three, actually.

I made the Backyard EOS training pages on the RASC national web site. They are live. The hub page, the level 1 course page, and the L1E (level 1 EOS) registration form.

BYE level 1 course information page

There it is!

found a spherical shiny thing

"Light bulb." Say it like Gru does...

But as I wandered around lookin' for somethin' shiny, frustrated that some of my astro-gear is in storage, I suddenly remembered the Ikea lights.

I have a set of ceiling rail overhead lights. And some of the reflectors/holders still had bulbs. 

Bulbs like what I have in the bathroom over the vanity.

Not just any old bulb. Half-mirrored bulbs. Good I didn't get rid of this set, yet.

mirrored incandescent bulb

Ha ha, a mirrored smooth spherical surface. For my fake star.

That was a bit meta.

once and for all

Had another go at the weather feeder text box.

When playing with Backyard EOS on 23 Dec '22, I ran into a glitch with the text file edits.

Was confused for a while until I carefully set the length for the city field. Thought I had this all sorted from some digging around back on 14 Apr '20. {ed: Oops, had forgotten about the little observation made on 23 Apr '21.}

Got me thinking that if too long, if is read nulls from the file, it would cause it to fail.

So, did some testing today. And confirmed that. The length parameter can be less though it will truncate; but it cannot be more.

Here's the content of the final file I made:

made by bla on 2:39 PM 27/12/2022
Temp Humidity City
         1         2         3         4
1234567890123456789012345678901234567890
-003.8 068 The Elevator, Ontario

And learned (re-affirmed) some interesting stuff... I discovered the last line of the file is critical. It must have the air temperature, the relative humidity, and the city or location name.

Previously, I have made a 2-line file with the "Temp Humidity City" headings and then the data on the second row.

When I put my "made by" at the end, that data showed in the Weather Center in BYE. Whoops.

Moving the modification notes to the top was A-OK; those data were ignored. Again, this was something noted over a year ago... Last line must be weather and location data. Line above is ignored. Got it.

Today's other discovery was that MANY lines may precede the last line. So I added the ruler! And edited on documentation. {ed: I've since added a warning note inside the file and other handy documentation.}

Tested in Backyard EOS v 3.1.18 on Windows XP on John Repeat Dance.

trialed again

Ran another trial teach of the Backyard EOS course.

Came in about 2 hours again. Timed with the Stopwatch on my phone.

This time I used the new script, with emphasis on 2 focusing methods, after the significant re-write of the Quick Reference Card. No major issues. Happy. This script is in good shape!

I spoke to the slides from the new deck. Though I did not open up the show proper. Gotta figure out how to handle the camera type step after connecting. Have a standalone image maybe? Also in the slide pressie?

I tried to use a Y-mask on the camera lens. I made a crude one quickly with insulated wire taped to the kit lens shield. Couldn't see a clear pattern...

My various 'scope and camera masks are... somewhere. In a box. Out of sight, from the move.

I tried to use a mock star. Couldn't find my Christmas tree decorations so used a shiny spoon. And used my super-cool Aussie LED tester. Again, the Bahtinov mask pattern was not obvious in the software. The spoon had scratches with I think created a convoluted pattern. I also wondered if the light source was too close.

Regardless, I was able to get through the course material.

Battery died part-way. One of the new ones. Sheesh...

Everything seemed to work well. But at the end, the lens stopped moving. Huh. Not sure why. Restarted the app--no go. I did not reboot the camera.

Got more screen snaps. That was good. I needed a nice image for the web site.

did a bunch of BYE dev

Did a bunch of work on the Backyard EOS course.

Finished watching the demo by Guylain on YouTube. Picked up a few tips and tricks, some subtle things too.

Finally cracked the nut on how to train on focusing. There are a lot of permutations and it took me a while to get a handle on it. Bright stars, dim stars, electronic focusers, manual focusing, camera lenses, software editions... Many paths.

It expanded the QRC to 3 pages!

Wrote my official script. It's looking pretty good. I'm planning to show 2 focusing scenarios. I'll need to find my camera Y-mask for one...

title slide of new BYE deck

And then I made the slide deck.

Gettin' real.

Monday, December 26, 2022

uploaded an article

Submitted a special item for the Journal of the RASC.

Something of a recap. The birth of the Stellarium Training Series.

But mostly for props...

given a look behind the scenes

Huh. A little random...

The RASC Communications and Marketing Assistant messaged me at 4:14 AM.

Different time zone? Insomnia? Santa messed up her sleep patterns?

Anyhoo, she attached a screen snap from the Driven system for the message handler for pushing out the Bulletin. Interesting...

Ah ha!

I pointed out the the Subject field showed only the month.

I asked that she add the text "The RASC Bulletin."

That will help a great deal.

round-up backup

With the write-up for the procedures for backing up data from Stellarium on Mom's Mac, I now have the three platforms documented. 

I'm quite happy about this.

the good ole days of data backup

So if you're trying to protect your data, customisations, and various preference settings for the software, I think I have notes you'll find useful. Choose your weapon:

  • Windows - Windows 10 with Stellarium 1.1
  • Linux - Ubuntu 22.04 LTS "snap" with Stellarium 1.1
  • Apple Mac - Mac OS X 10.13 with Stellarium 0.18.3

The Windows post also examines the effect of upgrading from an old to a new version.

It still is kinda astonishing to me that this is not something they document in the official User Guide. Or better still, that there's not a one-click button inside the app that did it all... Alas, we're on our own.

Now there's no excuse...

§

Added to the lumpy companion Stellarium page.

circled weekends

Who knows what the future holds.

Who knows where I'll be.

I circled the new Moon weekends for 2023. Generally falling late in the month at the beginning of the year to mid-month...

phases of Luna

It'd be nice to get to some dark-sky sites...

backing up Stellarium - Macintosh

Here are my backup/restore testing notes for Stellarium on an Apple Macintosh.

The purpose of this document is to help anyone know where custom user data is stored by the Stellarium program. This can helpful in a variety scenarios such as recovering from a reinstall, reinstating data after an upgrade, and transferring to a different computer.

It's too bad we can't just backup everything in the Stellarium library folder. That'd be quick and easy but that would backup the large star catalogue files and other unnecessary files.

Testing was performed on my Mom's iMac computer, running OS X, 10.13 High Sierra, using her profile in which Stellarium 0.18.3 was installed.

Note: {NAME} in the folder path refers to the Apple Mac account name attached to the logged in user. 

The primary storage drive was assumed, Macintosh HD, but adjust accordingly if you have used a secondary or tertiary drive.


preamble on hidden files

Remember, the Library folder under a user's home folder is normally hidden. You'll need to enable the display of hidden files and folders in a Finder window or in a file dialogue.

This describes how to access the hidden files and folders in the context of Stellarium.

  1. open a new Finder window on the Macintosh HD
  2. press Cmd Shift . (period) to toggle on the display of hidden items (shown in light grey)
  3. click the Users folder
  4. click your profile folder (with the house icon) 
  5. click the Library folder (hidden, shown in a light grey font)
  6. click the Application Support folder
  7. click the Stellarium folder; note the various folders used by Stellarium:
    • data 
    • modules  
    • stars / default  
    • landscapes


scenario - uninstalling/reinstalling

Perhaps you are doing a refresh. Or migrating to a new computer. There's an assumption we're using the same version or near to the same version. 


* landscapes

This refers to custom landscapes, aka backgrounds or surroundings. A landscape is made up of one or more image files plus a text initialisation file.

Now, one shouldn't bother backing up the "stock" landscape files from the Stellarium website; of course, you can always get those again.

However, if you made your own custom landscape, you'll want to be sure to keep those related files. The INI file is where the hard work is done, configuring the landscape texture load.

folder:

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium / landscapes 

file(s):

Within the "landscapes" folder there should be unzipped subfolders here, e.g. "my back yard" or "Carr Observatory," one for each of the added landscape profiles.

landscape.ini

Each landscape profile has the all-important INI file and then PNG image file(s).


* additions to SSO objects

If you have added comets and asteroids to Stellarium, they are all saved in a particular file. Arguably, these can always be reloaded from official sources such as the MPC. Additionally, downloading and installing from the online source would accommodate for updated ephemeris data. The main rationale for backing up this file is when you have many modifications, when you made a significant number of adds, edits, and deletes. 

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium / data

file:

ssystem_minor.ini


* star catalogues

I recommend you do NOT backup the catalogue files proper as they are too large. And they are downloaded from a Stellarium repository. 

What you should do is note or record the file with the highest catalogue number. Then, inside Stellarium, you can load in the necessary catalogues after a restore.

Remember to offset given the first catalogue file Stellarium uses has the number 0 (zero). 

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium / stars / default

file(s):

stars_4_1v0_2.cat

starsConfig.json

The example "stars" file shown here means the catalogue file number 4 has been added. In other words, file number 4 is the 5th catalogue loaded.

The "stars config" file indicates which catalogues are active but this is a system generated file and does not need to be backed up. 

Again, none of the files in the \stars folder need to be saved...


* general settings

User settings and preferences are captured in a general configuration file. 

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium

file(s):

config.ini


* telescope-mount config

All the telescope-mount profiles as managed by the Telescope Control [SIC!] plug-in. And for each mount profile, its particulars and parameters, you'll want to backup.

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium  / modules / TelescopeControl

file(s):

telescopes.json

device_models.json

The "telescope" file is critical. It contains mount details, the communication ports, driver references, etc. Ensure this file is saved.

The other file here, "device models," is a system-generated file with the "standard" built-in drivers. It does not need to be backed up.


* custom equipment

All the data in the oculars module of Stellarium is saved in one file. All your custom eyepieces, telescopes, camera lenses, cameras/sensors, magnifiers, etc. and their parameters can be easily backed up. The user preferences for the oculars tool itself, such as mask transparency, is captured.

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium  / modules / Oculars

file(s):

ocular.ini


* custom locations

If you create custom locations for your different observing sites, especially if you have several, you will want to back them up.

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium / data

file(s): 

user_locations.txt


* observing lists

If you have created you own custom observing lists (formerly bookmarks) e.g. "tonight's campaign 7 Dec 2022," you will want to back them up. Pre-defined observing lists you have downloaded, presumably you don't need to copy them as you can procure them from the original source.

folder: 

Macintosh HD / Users / {NAME} / Library / Application Support / Stellarium / data

file(s): 

observingList.json

A note for users with older version of Stellarium, still using the Bookmarks feature. The implementation of bookmarks only allowed for one to be open and active. Multiple lists were supported via distinct files. If a user has many bookmark lists, such the four separate seasonal lists for the RASC Finest NGC, or extracts from the Astronomical Calculations window, then the user may want to back up all these JSON files. Their location is arbitrary so one most proactively seek them out.


a backup plan

The notes above shows that there are a handful of files to backup to safeguard one's custom data and the application's settings. 

Assuming you use these features in Stellarium, the files to back up (with rather obvious names) are:

  • ssystem_minor.ini 
  • config.ini 
  • telescopes.json
  • ocular.ini
  • user_locations.txt
  • observingList.json
  • custom landscape folders (with the image and INI files)

And make a note of the highest star catalogue loaded.

It's pretty easy to jump into the Finder and copy the individual files somewhere for safe keeping. 


the restore

A restoration process was attempted as part of this test. The following steps were performed:

  1. the user data was backed up/copied
  2. the Stellarium software was uninstalled with the option to remove all user data
  3. the software (same version) was reinstalled, i.e. "clean install"
  4. the program was launched and examined, where it was observed that no custom settings were preserved, there were no custom locations, landscapes, observing lists, solar system objects, custom oculars, etc.
  5. the program was shut down
  6. the user data was reinstated to the specific folders
  7. Stellarium was launched and examined, where it was noted that all the customisations were back! 
  8. the missing star catalogues were loaded

 

summary

It is quite easy and quick to manually backup the handful of files on the Mac, as needed, to protect for customised, personalised data in Stellarium and one's preferences for the appearance and operation of the software.

Saturday, December 24, 2022

tried to find files

After the cheesy and spicy Christmas Eve dinner at Mom's, I retired to the upper living room, sipped a oaky rye whiskey, and tried to figure out stuff regarding Stellarium.

So to work in the living with the fam nearby and enjoy comfortable seating, I decided to remote-in. 

But needed some numbers.

So I hobbled to Mom's office and snapped a few photos with my smartphone. Now I had the external IP, the internal IP, and the creds for stoopid TeamViewer.

Then, for the next hour, I tried to find the super-secret location for the Stellarium user files...

I really wanted to track down these files so to finish my big project on how to back up your Stellarium data.

No luck...

§

Figured it out!

Learned the super-secret shortcut on the Mac to expose the hidden files.

That let me proceed and write up my backup notes.

reflected on the big year

My brother-in-law said, during dinner, it's been a big year for science.

He's a closet nerd.

It sure has been a big year.

Big for NASA.

  • one step closer to Mr Fusion
  • a successful Artemis run around the Moon
  • the deployment of the James Webb telescope
  • the killer asteroid deflection experiment
  • extraordinary research and development into vaccines
  • the helicopter on Mars went further and higher
  • imaged the black hole(s) at the center of our galaxy
  • further improvements into battery energy density

Those are the ones I can think of, off the top of my head. There are many more...

Exciting times.

ran a mock teach

Did a test-run for my new level 1 introductory Backyard EOS training session. 

Huh, hit the 2-hour mark, on the nose. 

empty classroom

We have a course!

heard he liked the DSC list

Heard from Chris V today.

He was up at the farm with his "useless" telescope. Crazy weather.

Chris completed his review of my SkySafari list for RASC Deep-Sky Challenge. He used the Plus and Pro version 6 without the PGC galaxy and GAIA Extension add-ons. He said the list looked great and appeared complete. All right!

It worked fine given some of the catalogue issues. He noted that I used the nearest object to Mrk 205 and Abell 2065.

He agreed that some additional nomenclature would help observers taking on the program. I had shown Chris my special notes via a shared Evernote page.

I think this means I can share out the .skylist on the RASC website along with my addendum.

I'll ready that soon...

Friday, December 23, 2022

updated the BYE QRC

Did some course development today...

I am keen to offer a new course in the new year.

Over the last few days I have been thinking about it... What are members most interested in. If I had to guess, I bet there's a lot of people that have SkySafari. I know I've helped get SkyTools in the hands of a few RASCals. But I've been thinking about Backyard. 

For SkyTools and Backyard, I had some materials already built up. I have two full quick reference cards for SkyTools! I knew I had detailed procedural notes on Backyard. That meant it'd be relatively easy to get going with these. SkySafari? Ground zero. An impending new software version for Android is coming. I have some issues... with SS. I'm just not in the mood.

So I picked Backyard! Backyard EOS.

This afternoon after work I dug out my old write-ups in Evernote. A good set of topics.

Fired up Google Docs and started drafting a quick reference card. But one topic in I started to have a funny feeling. Perhaps my shoes were too tight... Haven't I done this before?!

Dove into the E hard drive of John Max and lo and behold I found a rough-and-tumble QRC in MS Word. How about that!

A weird lookin' thing too. Like something Emily the Strange would conjure up. I had formatted the document with red text on black pages. Astronomer-friendly format, ha ha!

Started up the old ASUS netbook, connected the nearby camera to it, and launched Backyard EOS 3.1.

I opened the DOCX on the lenovo laptop and started the update. Took screen snaps from BYE to capture the various icons, buttons, and toolbars.

After one lenovo crash and a fight with a wonky keyboard on the ASUS, after a couple of hours, after a wee bit of cursin', I had a much-improved document.

out of focus QRC

It is ready for testing. I can now do a walk-thru of the QRC topics in a simulated classroom delivery to see if there's enough material and content for a 2 hour course. I think there will be. Looking forward to that.

I then drafted "hub" copy and the level 1 course "copy" for the RASC web site...

Exciting. 

It'll be neat to launch this in a week or so. I'm very curious how much interest there might be.

In the meantime, I can say: Backyard EOS training is "coming soon!"

checked the chart

Had a look at the Clear Sky Chart for Fingal. Hoping for a clear patch during this new Moon phase.

Alas, we've a blizzard upon us.

lots of white squares

But to dream...

Thursday, December 22, 2022

submitted for the Bulletin

Submitted an article for the next RASC Bulletin.

From the Observing Committee.

The latest (and last for 2022) recipients of certificates for the visual observing programs.

§

If you're interested in the colophon...

I made an early draft in my Evernote.

Then I made a Google Doc.

I asked the communications and marketing contact at RASC if I might use this format going forwards. If they were OK with it, it would improve the workflow on my end. Improved access and visibility for my team on the Observing Committee.

No response. 

Radio silence.

Dead air.

Another unanswered email.

Fine.

Whatever.

I converted to a Word DOCX file first using office.com and then downloading to my local machine.

Chart images snapped from the screen from the Google Sheets master certificates database.

I actually showed the charts without the legend to keep them compact. 

Separately I grabbed the legend frame and superimposed it atop the chart. That's 'cause Google Sheets charting does not allow free-floating the legend. Meh.

Dropped the screen grabs into Windows Paint and saved as standalone PNGs.

Emailed all to RASC head office.

§

Done. In the can.

asked for a helper

Posted a note to the RASC national forums looking for assistance in testing SkySafari observing lists.

Hopefully I'll find someone tech savvy and keen to help.

That'll enable me to complete testing and development of .skylist files for all the RASC observing certificate programs.

I'm particularly interested in sorting out issues with LiveSky.

And getting things, in the end, to the Sim Curr online repository...

noted the next install

Astronauts installed another iROSA solar wing. Number 4 of 6.

See the article at SpaceFlightNow.

I misinterpreted information from the previous solar activity. The new panels (all 6) will provide 215 kilowatts themselves, which is a 30% increase over the current arrays.

no certs for a couple of weeks...

Heard from my contact at national office.

She updated me on the RASC certificates.

None will be processed or issued until the new year... So a week or two, I guess. I don't like it.

expect delays

There are about 6 members waiting.

I messaged the office manager two days ago. Never did hear from her. She did not acknowledge my email.

My contact CCed her and said the OM would update me on the sheets order.

Uh huh.

§

I updated the webpages with the recipient names. I've done everything I can do.

We wait...

resolved a certificate matter

Concluded a matter today.

Heard from a RASC member in Newfoundland a week ago. His initial communiqué to me, as the Chair of the national Observing Committee, was alarming. As I investigated, I uncovered a number of mysterious issues.

The crux of the matter was that the St John's member had submitted his Explore the Moon - Telescope certificate application in January and had not been served! I quickly approved his certificate and forwarded notes to the office for processing.

Along the way I got to know Robert B and I think we got things sorted. And we have a good plan going forwards.

I still don't have answers to all my questions but I think the east coast member is satisfied.

received the 35th

Hey hey. Another RASC visual observing certificate application came in! 

Just now I received an Explore the Universe application from a national member in Montana.

All right.

And that bumps us to 35 for the year.

That makes me happy.

Wednesday, December 21, 2022

tis the solstice

Received happy solstice greetings from Malcolm, Grace, and Rhonda. You as well. Go nuts.

Mom and I talked about the winter solstice, long dark nights, and daylight saving time.

the suspension of discipline

I am hoping for clear conditions.

It's one of the good things about this time of year: you can do a lot more astronomy in a single evening...

read Ursids article

I think he's getting better at this...

Could it be my criticisms got through?

Meteorologist and science writer Scott Sutherland of The Weather Network posted an article on the Ursid meteor shower.

Early on he noted the shower rate: 10 per hour. Pretty low. He reported that some estimated the shower might double this year...

He properly cautioned about the Moon phase and light pollution when meteor hunting. He spoke to dark adaptation with good advice like waiting 20 minutes or more and avoiding your smartphone.

Regardless, this is a weak meteor shower... Even if 20/h, it would require considerable dedication. Especially in cold conditions.

So, I still think this odd. 

received the renewal notice

A few days ago I received the Renewal Notice email from the Royal Astronomical Society of Canada. Standard form letter email. Exactly the same as the one from 2021.

Right...

It's the time of year again.

Of course, I'll renew. 

But where? How?

This opens wounds not healed unfortunately.

No way I'll join my old centre. It's still a mess. They did nothing demonstrable to fix the things that drove me away. They did little to address the bad things that happened to other members. It is a broken centre. It's too painful, too uncomfortable, too political, too dark to return. I have to protect my mental and physical health.

It saddens me given the many wonderful friends I have there.

But I'm in a different geographic place now. 

I should have a good look at the London Centre... 

Or remain rōnin.

Tuesday, December 20, 2022

backing up Stellarium - Ubuntu

Here are backup/restore notes for Stellarium on Linux.

The purpose of this document is to help anyone know where custom user data is stored by the Stellarium program. This can helpful in a variety scenarios such as reinstating data after a clean install or transferring to a different computer.

It's too bad we can't just backup everything in the .stellarium folder. That'd be quick and easy but that would backup the large star catalogue files and other unnecessary files.

Testing was performed on a Surface Book (first generation) laptop running Ubuntu. Stellarium version 1.1 used. 

The Ubuntu testing was under a "snap" configuration. This impacted the directory structure for the storage of the various user configuration files.

Note, a directory with a leading period is hidden. You'll need to enable the display of hidden files and folders in the file manager app.

 

scenario - uninstalling/reinstalling

Perhaps we are doing a refresh. Or transferring to a new computer. There's an assumption we're using the same version or near to the same version.

 

* landscapes

Custom user landscapes for background, surroundings. A landscape profile is made up of one or several image files (PNG) plus a text initialisation (INI) file.

Don't back up the "stock" landscape files from the Stellarium website.

folder: 

home/snap/stellarium-daily/common/.stellarium/landscapes
file(s):

Within the "landscapes" folder there will be subfolders, e.g. "my yard" or "Mew Lake campground," one for each of the added landscape profiles.

landscape.ini
Each landscape profile has an INI file and PNG image files.

 

* customisations to SSO objects

If you have added a great number of comets and asteroids to Stellarium, you'll want to back up the key file for convenience.

folder: 

home/snap/stellarium-daily/common/.stellarium/data

file(s):

ssystem_minor.ini

 

* star catalogues loaded

Do not backup the catalogue files proper as they are too large. And they are downloaded from a Stellarium repository. 

Record the file with the highest catalogue number. Then, inside Stellarium, you can load in the necessary catalogues.

Remember to offset given the first catalogue file Stellarium uses has the number 0 (zero).  

folder:

home/snap/stellarium-daily/common/.stellarium/stars/default

file(s):

stars_5_2v0_1.cat

starsConfig.json

The "stars" file shown here means the catalogue file number 5 has been added. In other words, file number 5 is the 6th catalogue loaded.

The system generated "stars config" file indicates which catalogues are active. 

None of the files in the \stars folder need to be saved... 


* general settings and preferences

Active buttons in the horizontal toolbar, Sky & View settings, fonts, line colours, FOV, direction at start-up... all the user settings or user preferences are recorded in the general configuration file for Stellarium program.

folder:

home/snap/stellarium-daily/common/.stellarium

file(s):

config.ini

* mount config

As managed by the Telescope Control plug-in. For each mount profile, the driver, the communications port, etc.

folder:

home/snap/stellarium-daily/common/.stellarium/modules/TelescopeControl

file(s):

telescopes.json

device_models.json

The "device models" system-generated file is the "standard" drivers. It does not need to be backed up.

The "telescopes" file is critical and has all custom mount information.


* custom equipment

All the data in the oculars module of Stellarium is saved in one file. So all your custom eyepieces, telescopes, camera lenses, cameras, sensors, magnifiers, etc. and their parameters can be easily backed up. The user settings for the oculars tool itself, such as mask transparency, is captured. 

folder:

home/snap/stellarium-daily/common/.stellarium/modules/Oculars

file(s):

ocular.ini


* custom locations

Back up your custom locations or different observing sites.

folder:

home/snap/stellarium-daily/common/.stellarium/data

file(s):

user_locations.txt

* observing lists

Backup your custom observing lists (formerly bookmark lists) e.g. "tonight's campaign 6 Dec 2022." 

folder:

home/snap/stellarium-daily/common/.stellarium/data

file(s):

observingList.json


* a backup plan

This listing shows that there are a handful of files to backup to safeguard one's custom data and the application's settings. 

Assuming you use these features in Stellarium, the files (with rather obvious names) to back up are:

  • custom landscape directories (with the image and INI files)
  • ssystem_minor.ini 
  • config.ini for the general preferences
  • telescopes.json
  • ocular.ini
  • user_locations.txt
  • observingList.json

And make a note of the highest star catalogue loaded.

It's pretty easy to jump into file manager tool and copy the individual files somewhere for safe keeping. You could script the process to do it frequently and quickly.


* the restore

A restoration process was attempted as part of this test, meaning:

  1. the user data was backed up/copied
  2. the Stellarium software was uninstalled with the option to remove all user data
  3. the software (same version) was reinstalled, i.e. "clean install"
  4. the program was launched and examined, where it was observed that no custom settings were preserved, there were no custom locations, landscapes, observing lists, solar system objects, custom oculars, etc.
  5. the program was shut down
  6. the user data was reinstated to the specific folders
  7. Stellarium was launched and examined, where it was noted that all the customisations were back! 
  8. the missing star catalogues were loaded
 

* summary

It is quite easy and quick to manually backup the handful of files in Linux, as needed, to protect for customised, personalised data in Stellarium and one's preferences for the appearance and operation of the software.

backing up Stellarium - Windows

Here are backup/restore testing notes for Stellarium on Windows.

The purpose of this document is to help anyone know where custom user data is stored by the Stellarium program. This can helpful in a variety scenarios such as recovering from a reinstall, reinstating data after an upgrade, and transferring to a different computer.

Testing was performed on the John Kim Chi computer, a Dell laptop running Windows 10.

Note: {NAME} in the folder path refers to the MS account name attached to the logged in user. 

The primary storage drive is assumed, C:, but adjust accordingly if you have used a secondary or tertiary drive.

Use %appdata% to quickly land in the Roaming folder...

Also remember, the AppData folder, the parent of Roaming, is normally hidden. You'll need to enable the display of hidden files and folders in Windows Explorer.


scenario 1 - uninstalling/reinstalling

We are doing a refresh. Or perhaps transferring to a new computer. There's an assumption we're using the same version or near to the same version. Stellarium 1.1 was used.


* landscapes

This refers to custom landscapes, aka backgrounds or surroundings. A landscape is made up of one or several image files plus a text initialisation file.

Now, one shouldn't bother backing up the "stock" landscape files from the Stellarium website; of course, you can always get those again.

But if you made your own custom landscape, you'll want to be sure to keep those related files. Arguably, the graphic files don't need to be saved, assuming your have your original photographic scenery shots somewhere else. But the INI file is where the hard work is done, configuring the landscape texture load.

folder:

C:\Users\{NAME}\AppData\Roaming\Stellarium\landscapes

file(s):

Within the "landscapes" folder there should be unzipped subfolders here, e.g. "my back yard" or "Mary's cottage," one for each of the added landscape profiles.

landscape.ini

Each landscape profile has the all-important INI file and then PNG image file(s).


* additions to SSO objects

If you have added comets and asteroids to Stellarium, they are all saved in a particular file. Arguably, these can always be reloaded from official sources such as the MPC. Additionally, downloading and installing from the official source would also accommodate for updated ephemeris data. The main rationale for backing up this file is when you have many modifications, made a significant number of adds, edits, and deletes. 

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\data

file:

ssystem_minor.ini


* star catalogues

It is recommended that you do NOT backup the catalogue files proper as they are too large. And they are system generated or downloaded from a Stellarium repository. 

What you should do is note or record the file with the highest catalogue number. Then, inside Stellarium, you can load in the necessary catalogues after a restore.

Remember to offset given the first catalogue file Stellarium uses has the number 0 (zero). 

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\stars\default

file(s):

stars_4_1v0_2.cat

starsConfig.json

The example "stars" file shown here means the catalogue file number 4 has been added. In other words, file number 4 is the 5th catalogue loaded.

The "stars config" file indicates which catalogues are active but this is a system generated file and does not need to be backed up. 

To recap, none of the files in the \stars folder need to be saved...


* general settings

Toggled settings and user preferences such as cardinal points and sky settings like star scales and the dynamic Moon option are saved by Stellarium in a general configuration file. Meteor radiants visibility, star names visibility. Which buttons show in the horizontal toolbar. Line colours, font colours and size. The start-up direction and FOV. Everything! All the user's preferences.

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium

file(s):

config.ini


* telescope-mount config

All the telescope-mount profiles as managed by the Telescope Control [SIC!] plug-in. And for each mount profile, its particulars and parameters, you'll want to backup.

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\
modules\TelescopeControl

file(s):

telescopes.json

device_models.json

The "telescope" file is critical. It contains mount details, the communication ports, driver references, etc. Ensure this file is saved.

The other file here, "device models," is a system-generated file with the "standard" built-in drivers. It does not need to be backed up.


* custom equipment

All the data in the oculars module of Stellarium is saved in one file. So all your custom eyepieces, telescopes, camera lenses, cameras/sensors, magnifiers, etc. and their parameters can be easily backed up. The user preferences for the oculars tool itself, such as mask transparency, is captured.

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\modules\Oculars

file(s):

ocular.ini

 

* custom locations

If you create custom locations for your different observing sites, especially if you have several, you will want to back them up.

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\data

file(s): 

user_locations.txt


* observing lists

If you have created you own custom observing lists (formerly bookmarks) e.g. "tonight's campaign 5 Dec 2022," you will want to back them up. Pre-defined observing lists you have downloaded, presumably you don't need to copy them as you can procure them from the original source.

folder: 

C:\Users\{NAME}\AppData\Roaming\Stellarium\data

file(s): 

observingList.json

A note for users with older version of Stellarium, still using the Bookmarks feature. The implementation of bookmarks only allowed for one to be open and active. Multiple lists were supported via distinct files. If a user has many bookmark lists, such the four separate seasonal lists for the RASC Finest NGC, or extracts from the Astronomical Calculations window, then the user may want to back up all these JSON files. Their location is arbitrary so one most proactively seek them out.

 

* a backup plan

The notes above shows that there are a handful of files to backup to safeguard one's custom data and the application's settings. 

Assuming you use these features in Stellarium, the files to back up (with rather obvious names) are:

  • custom landscape folders (with the image and INI files)
  • ssystem_minor.ini 
  • config.ini 
  • telescopes.json
  • ocular.ini
  • user_locations.txt
  • observingList.json

And make a note of the highest star catalogue loaded.

It's pretty easy to jump into File Exploder and copy the individual files somewhere for safe keeping. If you were good are scripting and wanted to do it frequently and quickly, you could write a DOS batch file.

Another approach is to back up specific folders. First, get to this starting point:

C:\Users\{NAME}\AppData\Roaming\Stellarium

then back up the subfolders: 

  • \landscapes for all the custom landscape files
  • \data for the SSO content, custom locations, and observing lists
  • \modules for all the plug-ins and their settings

But don't back up the \stars subfolder!

All the remains is to back up the config.ini file in the \Roaming\Stellarium folder. 

It's too bad we can't just backup everything in \Roaming\Stellarium. That'd be quick and easy but that would absorb the large star catalogue files...

As I consider it, the folder approach is awkward. 

 

* the restore

A restoration process was attempted as part of this test. The following steps were performed:

  1. the user data was backed up/copied
  2. the Stellarium software was uninstalled with the option to remove all user data
  3. the software (same version) was reinstalled, i.e. "clean install"
  4. the program was launched and examined, where it was observed that no custom settings were preserved, there were no custom locations, landscapes, observing lists, solar system objects, custom oculars, etc.
  5. the program was shut down
  6. the user data was reinstated to the specific folders
  7. Stellarium was launched and examined, where it was noted that all the customisations were back! 
  8. the missing star catalogues were loaded
 

* summary

It is quite easy and quick to manually backup the handful of files in Windows, as needed, to protect for customised, personalised data in Stellarium and one's preferences for the appearance and operation of the software.

 

scenario 2 - updating/upgrading

The situation simulated here was that a user has an old version of Stellarium on their computer and on the same computer they want to upgrade to the more current version of the software.

The approach tested here was the "place on top of" method. Meaning, the user downloads and installs the new version over top of the existing version. In the hopes of keeping what is already present. One does not uninstall the old version. Again, the new is simply downloaded and installed. 

While not tested explicitly, the software uninstall process prompts the human to keep or discard the user data. Not removing the user data may yield the same outcome as the "place on top of" approach.

For testing purposes, Stellarium version 0.20.4 was used as the "starting point." The software was upgraded to version 1.1. While running the installer program, a warning dialogue with Attention! in the title bar appeared:

The existing version of the configuration data for telescopes in the Telescope Control plugin is obsolete.

On launching the new version, there were no apparent on-screen warnings.

The following customisations and features where checked and found to be OK.

  • custom landscapes 
  • added solar system objects
  • star catalogues loaded
  • equipment lists in the oculars plug-in plus the user preferences
  • custom locations
  • observing lists/bookmarks

The general settings and preferences were, for the most part, fine. It was noted that the Observing Lists button did show in the horizontal toolbar after the upgrade. While the icon looks exactly the same, the old "bookmarks" button must be considered unique. One will need to add the "new" button.

Speaking of bookmarks... If there was a bookmark list in the old version, the observing lists window will show the items, i.e. the list content is preserved. The list will be titled "bookmarks list."

A significant instance of data loss occurred for the telescope mount configurations. Everything in the Telescope Control plug-in was gone! This is disappointing and means that a user needs to make manual records or take screen snapshots for settings in mount profiles. That said, the mount profile data is inside the telescopes.json file, which is a text file, thus, easily examined...

 

* summary

Upgrading transfers or keeps many settings in Stellarium for Windows. Don't expect it to be perfect.

It is to be expected that if software features are changed dramatically, it may not be possible to migrate settings. That appears to be the case for the Telescope Control plug-in. So users should bear that in mind when making "big jumps" in the versions.

That suggests taking a good backup before the upgrade, in case one wants to roll back. Or needs to "extract" old settings from the saved files.

asked for a subject line adjustment

A couple of days ago, I asked the RASC communications person if we could adjust the subject line for the Bulletin notices. I pointed out they used to include the word "Bulletin" but of late they omit that.

Makes it difficult to search one's mailbox by the subject field.

They responded and said the word Bulletin always appeared. But I think they were referring to the banner image within the message. They asked if I was looking at the Weekly.

inter-office memo

I explained again.

The OLD subject line field format was:
The RASC Bulletin MONTH YEAR

The NEW subject line field format is:
MONTH YEAR

I provided snapshots...

asked about the cert sheets again

I sent an email directly to the office manager asking for an update on the blank certificate pages.

About a week ago, I learned the office manager was back, after being away sick, catching up. 

Why did they not update us? Why did they not respond to our, at the time, somewhat pressing matter. It's now turned into an urgent matter.

I reminded her that I have certificate award winners that I'm trying to appease.

Coming up to a one-month delay.

another one lost

Asked again of Hil and Cam if a package had arrived.

Nope.

Cam said that they have never had a problem with porch pirates…

They work from home most of the time... 

He was a bit apologetic. I told him to not think that way.

It was definitely a problem with my supplier. Another problem!

So frustrating.

Monday, December 19, 2022

updated the L2C QRC

The recent Stellarium updates got me thinkin'...

Al, too. When we spoke recently, and when I said, "Bookmarks are back!", he wondered about how to address the matter in training.

The old Stellarium bookmarks feature we taught in the level 2 intermediate course until they broke. 

I recall in a trainers meeting we agreed to drop the topic. We hid the slide. We would not mention the feature (unless someone asked).

I was a little fuzzy on where and how we covered it. I double-checked the level 1 introductory materials. No mention of it anywhere.

Found in on the level 2 (computer) syllabus. In fact, the process of using a bookmark list was documented in the intermediate Quick Reference Card. It showed how to add a bookmark. We briefly discussed how to use existing bookmarks and how to highlight all in a list.

But the new way is Stellarium version 1.1 was quite different. So I started editing the L2C card. 

And it turned out to make for a big update! 

In the end, it was not possible to simply edit the existing content on the QRC; I needed to completely rewrite it. The improved "observing lists" feature demanded two topics! Import an Observing List and Use an Observing List. 

Also, while updating the QRC for 1.1 stuff, I revised the telescope-mount control "Slew" topic for the new Abort slew button in the Move window. 

Added telescope mount driver port information for Linux...

Misc. other clean-up and cosmetic changes. 

§

I updated the level 2/3 graduates in the Stellarium "classroom," suggesting they visit the Google shared folder drive. It should be obvious, the new PDF for the QRC.

§

It was good to get this sorted. Especially if we're not going to directly teach it in a course... It makes the QRC quite valuable.

§

This got me thinkin' again. Observing lists could be covered properly in an EPO course.

Maybe it's time to develop that course...

didn't know what I consumed

I clicked on a button I should not have clicked on...

When booking my train trip, when filling in the form, when choosing my meal requirements, I misread stuff. I didn't see "oh, just give me a regular meal," as part of my business class option so I clicked low-sodium. No harm in that, right?

I have no idea what I ate in the dim light of the morning trip into Toronto... But it was not... enjoyable. Was it oatmeal? Instant oats? Muesli? I dunno. Porridge? Eww.

It was a grey, gooey, sticky mess with green seeds with a purply gelatinous blob with small spheres in the middle.

meal time on the spaceship Discovery One

I flashed to 2001: A Space Odyssey, Bowman and Poole chowin' down. Yummy astronaut nutrient paste.

Wednesday, December 14, 2022

taken away

My good friend Tony dos Santos is gone.

He succumbed. 

After a long, long battle.

It saddens me deeply that I won't be able to enjoy his company. His infectious laugh. His boundless curiousity. His fine taste in food. Extraordinary generosity. 

His child-like fascination with objects in space.

I will miss him dearly.

Tuesday, December 13, 2022

received goodies

Cookies!

My buddy Cam arrived, bearing gifts. A couple of interesting hearty beers, good for winter. And some home-made sugar cookies.

star cookies!

I thanked Hilary.

Monday, December 12, 2022

taught the last 2022 course

Taught a level 2 Stellarium session tonight.

Went well. Lots of questions. No tech issues. My mount slewed as requested. Yeah.

The last course for the year...

learned of delay

Heard from head office, my certificates wrangler, after my earlier message.

She shared that the office manager was sick with COVID. Great, just great...

This meant our certificate pages replacement order was delayed.

She said she'd keep me posted.

She also offered to check to see if someone else could place the order...

asked about ETM certs

Started a conversation with the Observing Committee regarding a possible chink in the armour.

I asked if we might have a problem with someone completing the Explore the Moon-Telescope certificate and wanting, or expecting, at the same time, to immediately receive an Explore the Moon-Binoculars.

A few team members chimed in. Good to get different perspectives.

spotted new iOS version

While creating a new "useful links" document for the Stellarium Mobile training course participants, I spotted an updated version of the app at the Apple App Store. Knew something was up, as the Google Play store showed a new version of as 10 Dec...

The iOS number shows as 1.10.1. Also recently posted, from 8 Dec '22. 

Some bug fixes, it looks like. 

I'm trying to figure out the state for Android but I'm sure it is the same...

asked about sheets

I asked my office assistant for an update on the blank certificate sheets.

Another week has gone by.

I was keen to resume issuing (non Moon) paper certificates.

Sunday, December 11, 2022

another notch for 2022

Funny timing.

I had just begged for a last-minute entry to the RASC Weekly.

I wanted to pitch members to dust off their nearly complete observing certificate applications and get them in. The Obs Comm would love to issue a couple more awards before 2022 rapidly closes.

I considered the Weekly when I realised I missed the opportunity to post such a note in the Bulletin.

Reem was working late! Said she added it to the Weekly. All right.

And then I received a note from the Calgary crew. 

A member has completed their Finest NGC program. 

Fantastic!

Got a wish!

tested Stellarium shortcuts (0.22.1-1.1)

Today, I wanted to update my keyboard and mouse shortcuts listing to the latest version of Stellarium 1.1. Across the board!

Unfortunately, the Macintosh I have ready access to is running an old OS X, 10.12.x, which I cannot upgrade. That limited me to installing Stellarium version 0.22.1. All that said, I can't think of much that is different. 

Therefore I believe this document should be relevant for current editions of Stellarium on Apple computers. i.e. 0.22.2, 1.0 (0.22.3), and 1.1 (0.22.4). If I'm lucky, there are no differences at all.

Also, I have been using Stellarium 1.1 a good deal on the Ubuntu Linux OS. So I can confirm the operation of shortcuts for that environment too (which, in the end, is the same as Windows). 

Thanks are due.

Larry N, during a Stellarium level 2 intermediate training course in early July 2022, revealed a trick on a button in the horizontal toolbar. In Windows, he had randomly right-clicked his mouse on the Telescope Control plug-in to find it immediately opened the mount configuration window. I took that a step further and found his technique to work on all buttons associated with plug-ins. But only today did I find out how to do it on the Mac.

And also, somehow, I had overlooked a shortcut associated with the oculars. Probably due to my non-plussed attitude on an early implementation of the oculars feature. But, in fact, it is a great shortcut. It was Chris V using it in one of his Insider's Guide to the Galaxy talks that reminded me of it. It is included.

{ed. Update to the update! 12 Dec '22, I learned another technique! While asking people how to zoom in on an object, Susan S said, "double-click it." I was looking for the slash key method but as they offered this I tried it. Holy smokes. It centred. I didn't recall doing that before. So, there's another option now for centring! I'm assuming it works on the Mac but I'll have to test that... 14 Dec '22: Ian B verified the action on his Mac.}

If you're on a laptop without a mouse, using a frustratingly annoying touchpad, you'll want to be comfortable with the supported gestures on the touchpad to simulate an external three-button mouse.

If you're using a Mac, some shortcuts may be interfered with by OS and application global shortcuts. You are on own I'm afraid, having to research what is getting in the way and determining if it can be turned off to make Stellarium work as described. Can you still get an "extended" keyboard for an Apple? Once one of my favourite keyboards.

The "notes" column to the far right with numbers are keyed to the footnotes. For example, 1 is used to indicate newly added or recently changed items.

controlling the surroundings
Windows Ubuntu
Mac*
show Location window
F6
Fn F64
toggle cardinal compass points qq
toggle detailed compass marks Shift q⇧ q
toggle ground and buildings
g
g
toggle ground fog
f
f
toggle atmosphere or air
a
a
toggle sky glow/building lights
Shift g
⇧ g11
ground (mountain) labels
Ctrl Shift g
⌘ ⇧ g
return to "home" (start-up) view
Ctrl h
(none)2






controlling the sky - deep sky
Windows Ubuntu
Mac
toggle stars
s
s
toggle star labels
Alt s
⌥ s
toggle constellation lines
c
c
toggle constellation boundaries
b
b
toggle constellation labels
v
v
toggle constellation artwork
r
r
reload sky culture
Ctrl Alt i
⌘ ⌥ i
toggle asterism lines
Alt a
⌥ a
toggle asterism labels
Alt v
⌥ v
toggle ray helpers
Alt r
⌥ r14
toggle DSO/nebula labels
n or d
n or d
nebula background images
i
i
reload DSO background images
Ctrl i
⌘ i
toggle quasars
Ctrl Alt q
(none)1,3,5
toggle pulsars
Ctrl Alt p
⌘ ⌥ p5
toggle zodiacal light
Ctrl Shift z
⌘ ⇧ z
toggle Milky Way
m
m
toggle HiPS sky survey
Ctrl Alt d
(none)1,6,
19
exoplanet labels, indicators
Ctrl Alt e
⌘ ⌥ e5
show Sky and Viewing Options
F4
Fn F4






single constellation mode
Windows Ubuntu
Mac
remove previous constellations
w
w7
show all constellations
Alt w
⌥ w






the sky - solar system
Windows Ubuntu
Mac
toggle planets and Moon
p
p
toggle planet and Moon labels
Alt p
⌥ p
toggle planet markers
Ctrl p
⌘ p1,20
toggle planet orbits
o
o
toggle star-lore planet names
Ctrl Shift n
⌘ ⇧ n
toggle planet trails
Shift t
⇧ t
toggle planet surface labels
Alt n
⌥ n9
toggle meteor radiants
Ctrl Shift m
⌘ ⇧ m
toggle meteor radiant labels
Shift m
⇧ m
import data from MPC
Ctrl Alt s
⌘ ⌥ s5,17






controlling lines
Windows Ubuntu
Mac
toggle altitude/azimuth grid
z
z
toggle equatorial grid
e
e
toggle ecliptic line
, (comma)
, (comma)
toggle celestial equator
. (period)
. (period)
toggle meridian line
;
;
toggle horizon line
h
h






changing image presentation
Windows Ubuntu
Mac
flip horizontally
Ctrl Shift h
⌘ ⇧ h
flip vertically
Ctrl Shift v
⌘ ⇧ v
equatorial or azimuthal mode
Ctrl m
⌘ m
look to the north
Shift n
⇧ n
look to east
Shift e
⇧ e
look to west
Shift w
⇧ w
look to south
Shift s
⇧ s
look up to zenith
Shift z
⇧ z
look to north celestial pole
Alt Shift n
⌥ ⇧ n
look to SCP
Alt Shift s
⌥ ⇧  s






zooming
Windows Ubuntu
Mac
zoom in
PgUp or
Ctrl Up Arrow

Fn Up Arrow
zoom out
PgDn or
Ctrl Dn Arrow

Fn Down Arrow
zoom in or out slowly
Shift with keys
⇧ with keys
quickly zoom in/out w/ mouse
wheel
2 finger swipe
zoom close to selected object
/ (slash)
/ (slash)
zoom out fully
\ (backslash)
\ (backslash)
zoom very close to planet
/ twice
/ twice1,21
set field of view (FOV) to 180°
Ctrl Alt 1
⌘ ⌥ 1
set FOV to 90°
Ctrl Alt 2
⌘ ⌥ 2
set FOV to 60° (naturalistic)
Ctrl Alt 3
⌘ ⌥ 3
set FOV to 45°
Ctrl Alt 4
⌘ ⌥ 4
set FOV to 20°
Ctrl Alt 5
⌘ ⌥ 5
set FOV to 10° (binoculars)
Ctrl Alt 6
⌘ ⌥ 6
set FOV to 5° (binoculars)
Ctrl Alt 7
⌘ ⌥ 7
set FOV to 2°
Ctrl Alt 8
⌘ ⌥ 8
set to 1° (lo-power telescopic)
Ctrl Alt 9
⌘ ⌥ 9
to ½° (med-power telescopic)
Ctrl Alt 0 (zero)
⌘ ⌥ 0 (zero)






panning
Windows Ubuntu
Mac
quickly pan celestial sphere
left-drag
drag
pan right
Right Arrow
Right Arrow
pan left
Left Arrow
Left Arrow
pan up
Up Arrow
Up Arrow
pan down
Down Arrow
Down Arrow
pan a small amount slowly
Shift Arrow-key 
⇧ Arrow key






controlling time flow
Windows Ubuntu
Mac
set date/time to now
8
8
set time rate to zero
7
7
increase time flow
l (lower case L)
l (i.e. L)
decrease time flow
j
j
run time at normal rate
k
k
increase time flow a little
Shift l (that's L)
⇧ l (i.e. L)
decrease time flow a little
Shift j
⇧ j
drag for time
Ctrl drag
Control drag10
flip or reverse time direction
0 (zero)
0 (zero)






time with mouse... 
Windows Ubuntu
Mac15
increase/decrease by minutes
Ctrl

increase/decrease by hours
Ctrl Shift
⌘ ⇧ 
increase/decrease by days
Ctrl Alt
⌘ ⌥ 
increase/decrease by years
Ctrl Alt Shift
⌘ ⌥ ⇧ 1






controlling "regular" time
Windows Ubuntu
Mac
show date/time window
F5
Fn F5
forward 1 hour solar
Ctrl = (equal)
⌘ =
backward 1 hour
Ctrl - (hyphen)
⌘ -
forward 1 day solar
= (equal)
= (equal)
backward 1 day
- (hyphen)
- (hyphen)
forward 1 week solar
]
]
backward 1 week
[
[






controlling sidereal time
Windows Ubuntu
Mac
forward 1 day sidereal
Alt = (equal)
⌥ = (equal)
backward 1 day
Alt - (hyphen)
⌥ - (hyphen)
forward 1 year sidereal
Ctrl Alt Shift ]
⌘ ⌥ ⇧ ]
backward 1 year
Ctrl Alt Shift [
⌘ ⌥ ⇧ [1






working with objects
Windows Ubuntu
Mac
select an object
left-click
click
centre on selected object
spacebar
spacebar
select and centre object
double-click
double-click1
toggle tracking of object
t
t
deselect object
right-click or
Ctrl Spacebar

⌘-click or
⌘ Spacebar
16
display search dialogue box
Ctrl f or F3
⌘ f or Fn F3
go, i.e. travel, to a planet
Ctrl g
⌘ g
toggle angular measurement
Ctrl a
⌘ a5
copy object info to clipboard
Ctrl Shift c
⌘ ⇧ c
add custom marker
Shift click
⇧ click
remove custom marker
Shift right-click
Control ⇧ click
remove all custom markers
Alt Shift right-click
⌥ Control ⇧ click






working with satellites
Windows Ubuntu
Mac5
configure artificial satellites
Alt z
⌥ z
toggle satellite display or "hints"
Ctrl z
⌘ z
toggle satellite labels
Alt Shift z
⌥ ⇧ z






using oculars
Windows Ubuntu
Mac5
toggle ocular view
Ctrl o
⌘ o
toggle crosshairs
Alt c
⌥ c
show Telrad sight
Ctrl b
⌘ b
show oculars pop-up menu
Alt o
⌥ o1,22
rotate reticule clockwise
Alt m
⌥ m13
rotate reticule CCW
Alt Shift m
⌥ ⇧ m13






controlling the screen
Windows Ubuntu
Mac
toggle night (red light) mode
Ctrl n
⌘ n
toggle full-screen mode
F11
F118
toggle toolbars/menus, i.e. GUI
Ctrl t
⌘ t
save screenshot to disk
Ctrl s
⌘ s
toggle planet selection marker
Ctrl Shift p
⌘ ⇧ p
close a window/dialogue box
Esc
Esc






driving a mount
Windows Ubuntu
Mac5
slew to selected object
Ctrl + number
⌘ + number12
slew to middle of screen
Alt + number
Alt + number12
show move or slew
   telescope window

Ctrl 0 (zero)
⌘ 0 (zero)
abort slew
Ctrl Alt Shift + ...
⌘ ⌥ ⇧ + ...12
sync mount and software
Ctrl Shift + ...
⌘ ⇧ + ...1,12






scripting
Windows Ubuntu
Mac
show script console window
F12
Fn-F12
pause script
Ctrl d, p
⌘ d, p
resume script
Ctrl d, r
⌘ d, r
stop script
Ctrl d, s
⌘ d, s






controlling the application
Windows Ubuntu
Mac
show configuration window
F2
Fn F2
show help/about window
F1
Fn F1
keyboard shortcuts window
F7
Fn F7
show Astro. Calc. window
F10
Fn F10
update or calculate in AC
Shift F10
⇧ Fn F101,18
show Bookmarks window
Alt b
⌥ b24
show Exoplanets config window
Alt e
⌥ e5
show meteor settings window
Ctrl Alt Shift m
⌘ ⌥ ⇧ m5
show meteor search window
Ctrl Alt m
⌘ ⌥ m5
show plug-in config window
right-click
plug-in button

control-click
plug-in button
1,23
quit from Stellarium
Ctrl q
⌘ q


Notes:

  1. Recently added or changed shortcuts.
  2. On the Mac, the return-to-home shortcut ⌘ h hides the app. This is an operating system shortcut.
  3. On the Mac, the quasar shortcut ⌘ Option q causes Stellarium to quit. 
  4. The operation of function keys on both Windows and Mac computers may require the use of a function or Fn key.
  5. Keyboard shortcuts associated with a plug-in. They may not function if the plug-in is not active.
  6. The digital sky survey layering feature refers to the display as a "hierarchical progressive" sky survey.
  7. The "remove" constellation shortcut applies when "single constellation mode" is active, as triggered in Configuration, Tools.
  8. The F11 does not work on iMac 21.5 and 2011 wireless keyboard. It shows the Mac desktop. This is an operating system shortcut.
  9. Referred to as surface "nomenclature" labels. This marks detailed surface features on planets, for example, Olympus Mons on Mars.
  10. On the Mac, only works when mouse is dragged horizontally. Only changes seconds.
  11. This is referred to as the "illumination" in a compatible landscape file.
  12. The number used to slew refers to the mount profile in the Telescopes window. If there's only one profile, it is simply Ctrl 1 or ⌘ 1. If a user has four telescope profiles and the fourth is to be used, then the user must press Ctrl 4 or ⌘ 4.
  13. This assumes one is showing the CMG or Meade astrometric eyepiece.
  14. Ray helpers example... "Arc to Arcturus."
  15. On Windows, roll middle mouse wheel up or down with overlay keys. On Macintosh, use overlay keys while performing two-finder swipe up or down on mouse.
  16. On click on nothing, if you can...
  17. Opens the Solar System Editor display at the Import Data window.
  18. Use Shift F10 to update positions or calculate values inside the Astronomical Calculations window.
  19. On the Mac, the DSS shortcut ⌘ Option d toggles the Dock. This is an operating system shortcut. On Ubuntu, Ctrl Alt d shows the desktop.
  20. Planet markers only work when labels are active.
  21. Shortcut / (slash) "double zoom" works on Mars, Jupiter, Saturn, and Uranus only.
  22. Quickly switch the ocular, telescope, magnifier, etc. via on-screen menu which appears at the current mouse position.
  23. High-speed alternative than going through the general Stellarium config window. On the Mac, hold the Control key while clicking the plug-in button. All except Online Queries.
  24. aka the Observing Lists windows.

Some shortcuts were omitted. Very few now...

Finally, the Stellarium documentation and keyboard labelling for the Mac is inconsistent. We note the symbols below:

⌘ (cloverleaf) is the Command key,
      with the apple symbol on very old systems
⌃ (carat) is the Control key (though I elected to not use the symbol)
⌥ is the Option (alt) or alternate key
⇧ (up arrow) is the Shift key
⇪ (up arrow with segments) indicates that the Caps Lock is used
fn or Fn is the Function key

Please report errors in the comments below...

§

See my "top" list for a very short collection of most frequently used, most helpful, techniques. Handy if heading into a presentation. Inspired by Ron B.