Author Topic: PI 1.5 Rocks  (Read 6033 times)

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
PI 1.5 Rocks
« on: 2009 May 18 09:22:52 »
Am starting to process some new Narrowband data and with the exception of  dark and flat field calibration am doing the entire image in PixInsight.  Registartion, hot/cold pixel removal, Image Integration and final processing with Histo, DBE, HDR, etc. Hopefully will have a finished example in a couple of days.  This is pretty exciting!
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline Nocturnal

  • PixInsight Jedi Council Member
  • *******
  • Posts: 2727
    • http://www.carpephoton.com
Re: PI 1.5 Rocks
« Reply #1 on: 2009 May 18 10:31:46 »

Hi Jack,

How are you doing hot/cold pixel removal?
Best,

    Sander
---
Edge HD 1100
QHY-8 for imaging, IMG0H mono for guiding, video cameras for occulations
ASI224, QHY5L-IIc
HyperStar3
WO-M110ED+FR-III/TRF-2008
Takahashi EM-400
PIxInsight, DeepSkyStacker, PHD, Nebulosity

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
Re: PI 1.5 Rocks
« Reply #2 on: 2009 May 18 13:50:36 »
There is that option in Image Integration -pixel rejection
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline Nocturnal

  • PixInsight Jedi Council Member
  • *******
  • Posts: 2727
    • http://www.carpephoton.com
Re: PI 1.5 Rocks
« Reply #3 on: 2009 May 18 14:01:40 »
Ah, thanks. I thought it was a separate step. I'll have to compare how it works next to my own hot pixel reject code that's based on dark frame analysis.
Best,

    Sander
---
Edge HD 1100
QHY-8 for imaging, IMG0H mono for guiding, video cameras for occulations
ASI224, QHY5L-IIc
HyperStar3
WO-M110ED+FR-III/TRF-2008
Takahashi EM-400
PIxInsight, DeepSkyStacker, PHD, Nebulosity

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
Re: PI 1.5 Rocks
« Reply #4 on: 2009 May 18 14:20:27 »
Please give me your thoughts as to which algorithm and settings work best.
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
Re: PI 1.5 Rocks
« Reply #5 on: 2009 May 18 14:28:49 »
BTW enable the generation of the pixel reject maps and you can readily see what you rejected
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PI 1.5 Rocks
« Reply #6 on: 2009 May 18 16:01:57 »
Jack, I look forward to see that image. The object (if it's the same you've sent by private email) is extremely nice!

ImageIntegration's pixel rejection won't work for hot/cold pixels if they are CCD defects, since these are present at the same location on all images. Indeed we would love to have a good hot/cold pixel removal tool (er, Sander?  ;D)

A script to detect single (isolated) hot/cold pixels is very easy to write. I may write one if I find a free while (probability < 0.25) :)
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
Re: PI 1.5 Rocks
« Reply #7 on: 2009 May 18 16:48:19 »
Hmmm  If that is the case why did the program identify and reject a column defect present on the chip?
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline mmirot

  • PixInsight Padawan
  • ****
  • Posts: 881
Re: PI 1.5 Rocks
« Reply #8 on: 2009 May 18 21:26:46 »
It would be nice generate a defect map to apply after calibration.

Also, 1.5 rocks!

Max

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PI 1.5 Rocks
« Reply #9 on: 2009 May 19 00:22:13 »
Hmmm  If that is the case why did the program identify and reject a column defect present on the chip?

 :-[ Because what I've said is not true, of course.  :D These things happen when one is up at 1 am after a hard day... (and yesterday I was testing integration of flat frames, where sensor defects can't be rejected).

Please ignore my comment; of course hot/cold pixels and other sensor defects are rejected because you have registered the images, and physical pixels don't match since you've dithered between exposures.
« Last Edit: 2009 May 19 00:26:06 by Juan Conejero »
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline Jack Harvey

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 975
    • PegasusAstronomy.com & Starshadows.com
Re: PI 1.5 Rocks
« Reply #10 on: 2009 May 19 05:33:31 »
Juan  Thanks for the update.  Appreciate all your help!  When is the vacation so you can get some rest<G>

Looking on the bright side, now you don't have to worry about writing a script for hot pixel reject - which you dont have time for anyway<G>.
« Last Edit: 2009 May 19 06:03:06 by Jharvey »
Jack Harvey, PTeam Member
Team Leader, SSRO/PROMPT Imaging Team, CTIO

Offline mmirot

  • PixInsight Padawan
  • ****
  • Posts: 881
Re: PI 1.5 Rocks
« Reply #11 on: 2009 May 19 09:22:17 »
I should send you a set of my kaf 9000 images. It has number of cold/cool columns.
Most, software I have tried don't do a good just of rejecting these type of artifacts even with aggressive dithering. This includes MaxIM, DSS, and CCDstack. I apply interpolation for the bad columns prior to stacking them to fix this. I can never figure out why they are so hard to id and reject.

Max