Hemisphere:  Northern  ·  Contains:  NGC 6883  ·  NGC6883
Getting plate-solving status, please wait...
WR134  Ha/OIII Medium Field, 


Powered byPixInsight

WR134 Ha/OIII Medium Field

Imaging telescopes or lenses: Teleskop-Service ONTC 8" f4

Imaging cameras: ZWO ASI1600MM-Cool

Mounts: Astro-Physics Mach1GTO

Guiding telescopes or lenses: Teleskop-Service ONTC 8" f4

Guiding cameras: SXV Lodestar

Software: Aries Productions Astro Pixel Precessor  ·  PixInsight  ·  Self Developed RASS  ·  Photoshop CS3

Filters: Astrodon OIII 1.25 3nm  ·  Astrodon Ha 1.25 5nm

Accessory: Skywatcher Coma corrector

Dates:July 29, 2019July 30, 2019Aug. 3, 2019Aug. 5, 2019Aug. 12, 2019

Astrodon Ha 1.25 5nm: 44x300" (gain: 139.00) -10C bin 1x1
Astrodon OIII 1.25 3nm: 146x300" (gain: 139.00) -10C bin 1x1

Integration: 15.8 hours

Avg. Moon age: 14.81 days

Avg. Moon phase: 27.83%

Astrometry.net job: 2859575

RA center: 20h 10' 13"

DEC center: +36° 10' 12"

Pixel scale: 1.962 arcsec/pixel

Orientation: -33.981 degrees

Field radius: 0.784 degrees

Resolution: 2306x1716

Data source: Backyard


This is an experiment of sorts. I took the Ha and OIII data and stretched them with the Delinear script in Pixinsight. Then I loaded each as layer in Photoshop and then used GradientMap to map the OIII data to a bluish color I liked and then mapped the Ha data to a golden color. I set each layer to 'Linear Dodge' and blended them with a background solid layer set to (18/18/18) RGB.

After lots of futzing around with minimizing stars and using the high pass filter to enhance contrast I settled on this version.

I feel I was able to better present the faint tendrils of WR134 by mapping directly to a bluish color compared to when I tried variations of HOO with the Green channel being a linear combination of Ha and OIII. The output of those tests always needed considerable SelectiveColor help in Photoshop that eventually degraded the tendrils in WR134.

It was a fun experiment.

All the data with collected with RASS which is an automation suite I've written in Python. There is no GUI like traditional programs. I have a "sequence server" that connects to all the hardware and accepts sequence requests. It handles pre-pointing, focusing, pier flipping, etc.

I have another program that I feed in project definitions and it schedules the requested observations and feeds them to the sequence server.

A project definition is just a list of targets with priorities and a list of observations for each filter for each target, also with optional priories. You can also set constraints on altitude and start/end time. All of this is stored in YAML files which are quick and easy to edit by hand.



License: None (All rights reserved)

Sky plot

Sky plot


WR134  Ha/OIII Medium Field,