Processing C/2020 F3 Neowise

Questions and answers about processing in StarTools and how to accomplish certain tasks.
Post Reply
sandconp
Posts: 20
Joined: Tue Dec 03, 2019 6:59 pm

Processing C/2020 F3 Neowise

Post by sandconp »

I am trying to process the Comet Neowise using Star Tools and I am running into some issues. I have taken the same stacked fits file into Pixinsight with pretty good results.

I am started out by doing a Autodev to find the artifacts, then binning 50% and doing a wipe. I did not go any further because I feel that my results will only get worse. The wipe only fixed a part of the image the rest is white.

Would somebody be willing to take my image and provide a tutorial to process my image using Star Tools?

Here is the link via Dropbox.

https://www.dropbox.com/s/k49ytqgz46qcg ... .fits?dl=0
User avatar
admin
Site Admin
Posts: 2494
Joined: Thu Dec 02, 2010 10:51 pm
Location: Melbourne
Contact:

Re: Processing C/2020 F3 Neowise

Post by admin »

Hi,

I just had a quick look, but cannot replicate the problem you are describing? :think:

Did you maybe forget to crop out stacking artifacts before running WIpe?
Ivo Jager
StarTools creator and astronomy enthusiast
sandconp
Posts: 20
Joined: Tue Dec 03, 2019 6:59 pm

Re: Processing C/2020 F3 Neowise

Post by sandconp »

Hi Ivo,

Can you tell me the steps that you did to start the process?

Did you use AutoDev or Dev?
User avatar
admin
Site Admin
Posts: 2494
Joined: Thu Dec 02, 2010 10:51 pm
Location: Melbourne
Contact:

Re: Processing C/2020 F3 Neowise

Post by admin »

sandconp wrote:Hi Ivo,

Can you tell me the steps that you did to start the process?

Did you use AutoDev or Dev?
I did as you did;

AutoDev to find artifacts/evaluate, Bin 50%, crop artefacts (X1: 13px, X2 -4px, Y1 39px, Y2 -4px), Wipe.

A subsequent AutoDev should get you this;
StarTools_169.png
StarTools_169.png (565.78 KiB) Viewed 853 times
Does this not work for you?

Generally, if Wipe is leaving in gradients, there is an artefact located near them.
Ivo Jager
StarTools creator and astronomy enthusiast
sandconp
Posts: 20
Joined: Tue Dec 03, 2019 6:59 pm

Re: Processing C/2020 F3 Neowise

Post by sandconp »

Ivo,

I am kind of stuck here. I did an Autodev and then a Bin @ 50%

Those values X1: 13px x2-4px Y1 39px, and Y2-4Px) are very low. They hardly include any of the image.

Do your values x1-x2 Y1 and y1-y2 get put into those four boxes before proceeding to the subsequent AutoDev?
Attachments
autodev.png
autodev.png (388.87 KiB) Viewed 852 times
User avatar
admin
Site Admin
Posts: 2494
Joined: Thu Dec 02, 2010 10:51 pm
Location: Melbourne
Contact:

Re: Processing C/2020 F3 Neowise

Post by admin »

The negative numbers for X2 and Y2 are the offsets from the maximum (e.g. the second number between brackets).
Regardless, I am really confused as to why you cannot see/detect the stacking artifacts visually? E.g you should not need to guess or anything like that. The AutoDev should make them readily visible when zooming in and inspecting the edges.
It goes without saying that those observations as to their location are meant to inform the values for the Crop...
Ivo Jager
StarTools creator and astronomy enthusiast
sandconp
Posts: 20
Joined: Tue Dec 03, 2019 6:59 pm

Re: Processing C/2020 F3 Neowise

Post by sandconp »

Ivo,

Ok I now see the artifacts on the top and on the left side and I understand the x1,x2,y1 and y2 settings.

So here is where I am after the second autodev and first wipe.

What are the next steps may I ask?

I just did a keep and I am ready for the next step(s).
Attachments
autodev2.png
autodev2.png (430.28 KiB) Viewed 844 times
User avatar
admin
Site Admin
Posts: 2494
Joined: Thu Dec 02, 2010 10:51 pm
Location: Melbourne
Contact:

Re: Processing C/2020 F3 Neowise

Post by admin »

Excellent. :) Sadly, it doesn't seem any calibration frames (flats) or dithering were applied, so the image suffers from vignetting and walking noise.

The Vignetting preset may or may not be more appropriate.

From there I would keep it really simple, given there is usually not much to enhance in the way of detail. So, I'd do an AutoDev again for final stretch, run the Color module (you'd be looking for a green core/C2 and beige/white tail with for the sunlight reflected dust, as well as an ionised blue CO streak), then switch Tracking off with a pretty aggressive noise reduction to catch most of the walking noise. You may want to bin more than 50%.

E.g. something like this;
Stack_32bits_124frames_248s.jpg
Stack_32bits_124frames_248s.jpg (65.33 KiB) Viewed 843 times
Hope this helps!
Ivo Jager
StarTools creator and astronomy enthusiast
Post Reply