Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Starcruiser

Pages: 1 [2]
General / Re: GREEN Channel Vertical Banding
« on: 2018 March 25 15:22:40 »
I am sorry, then I have no idea what goes wrong here. Hope that Jim's suggestion will be helpful.


Yep this doesn't make any sense for me either.  Why can't PI process the Green just like it did Red and Blue instead of messing it up?

It worked great for this run:

Only difference now is I am using a QHY168C in place of the STF8300C on the 80mm scope.  Should only be a difference in the scaling calculations to me.

Thanks for the attempt!

Modify message

General / Re: GREEN Channel Vertical Banding
« on: 2018 March 25 13:46:55 »
Hi Bernd,

Yes, it is exactly as you have stated.  Only exception is Cosmetic Correction for the ST8300M and then on to Star Align.


General / Re: GREEN Channel Vertical Banding
« on: 2018 March 25 12:37:09 »
Hi Jim,

I used StarAlign on all 66 subs using the ST8300M Red as the reference image to scale and align to in one operation.   Red and Blue subs are normal after registration and scaling but all the Green subs still have the same patterning. I have visually inspected all Green subs prior to the operation and there is nothing I can see in any of them to throw things off.

Earlier I did an experiment and registered all the QHY168C Greens together and they looked right.  Did the same to the ST8300M Greens and they looked right.  So I then took one ST8300M Red sub and used it as the reference image and then one QHY168C Green sub and just aligned those two images and the Green output had the same patterning as reported at the beginning.  Just doesn't make sense why Red and Blue outputs register and scale fine but Green is abnormal.  No warnings are posted in the Process Console.

In addition, another experiment:

Loaded one ST8300M Red and made it the reference Image, loaded one QHY168C Green for a target image in StarAlign.  If I use F5 and resultant Green image in the workspace is normal, if I use F6 global and resultant image in the output directory is patterned.

Starting to go nutz with this...ack!


General / Re: GREEN Channel Vertical Banding
« on: 2018 March 25 11:58:35 »
Hi Jim,

Thanks for your response.

What I do is take all pre-processed RGB subs and use StarAlignment to register all the green subs for instance from both cameras with the reference image from the ST8300M for scaling the QHY168C to that image.  Same thing with the Red and Blue.  Everything worked fine with Red and Blue, just don't know why Green is misbehaving.  The relevant RGB masters are made from those stacks

I will try your suggestion and pick one of the Red subs as the reference image; I did not take luminance in this run.  And then run them all in one run.


General / GREEN Channel Vertical Banding
« on: 2018 March 25 06:19:06 »
Since I using a dual-rig and camera setup for simultaneous acquisition I have run into a problem in processing only the Green channel.  Blue and Red combine fine even though the scaling is different PI has been handling this fine until now.  The vertical banding in the Green channel only appears while using the StarAlignment module.  Separate and apart the Green channels from the ST8300M subs and 168C subs are fine.  Once I align and scale the QHY168C green subs with the ST8300M green subs then QHY168C green subs become banded.

I have run out of combinations I can think of to localize this issue but have come at a dead end.  I do not understand why my process works fine for Red and Blue but Green gets messed up.  Until I can get this corrected I cannot use ImageIntegration on the green channel.

Attached is my PI desktop screen cap, Green channel is on the far left.  As you can see Red and Blue have no banding.

Please let me know what else I can post to assist with this issue.


General / Re: Process Icons Not Visible After Loading
« on: 2017 September 22 16:10:50 »
Hi Steve,

Checked them all and they were located in workspace #7, not sure how they ended up in there as workspace #1 was enabled when I loaded them.


Check the different workspaces.


General / Process Icons Not Visible After Loading
« on: 2017 September 22 15:21:28 »
Allowed PI to do it's update after startup which appeared to be five files.  Restarted PI after the update installation all appeared fine at this point.

Went into Process to Load Process Icons and chose the file, Process Console Showed them being loaded into the workspace.  The are not visible on
the screen.  Tried again and PI gives me a warning that the current process icon set has been modified and is unsaved...Throw away all process icons?

So where are they hiding.  Process Console reports 6 icons are loaded.


All was fine until this morning's update.


General / Re: .xisf being changed back to .fit
« on: 2017 August 09 08:24:08 »
Thanks Juan,

Loaded a fresh instance of PI instead of project and sure enough StarAlignment maintained the .xisf file extensions.

General / .xisf being changed back to .fit
« on: 2017 August 07 13:59:59 »
Just started using v1.8.5 and after loading my .xisf image files into StarAlignment all the files are processed and saved with .fit extenders in the output directory.
What is causing the change?  I do not see any setting in StarAlignment that causes this change.


I have a ST8300M and just started using the STF8300C but I did save this information in my notebook from the CCDStack forum, so they appear to recommend around 33,000 average for the 8300"

"Well, 65535 is the max number possible in ADU. So we won't go into a lot of technical equations, not really needed.
Yes, you want to use Maxim, CCDStack or some program that will give you the average ADU of the flat and that is the ADU level that concerns you.
Try to get 33,000 average and that should give you a nice flat. The other number you want to try to get is a total of about 500,000 ADU. so you want to use 12-25 flats per filter, depending on your time you have to do flats. Then make a master flat from these exposures.
Due to the use of a mechanical shutter, you want to keep the exposure at 3 seconds or so, so the shutter does not show in the flat."

Pages: 1 [2]