CometAlignment?

[ftherrmann]

I'm doing something incorrectly...

1.   Do star aligned prebatch processing w driz
2.   Create Integrated Star Aligned xisf file for use as Subtract Operand
2.5 Define dX and dY by clicking on comet locations
3.   Perform CometAlignment using operand file created in step 2.
4.   Perform driz integration using the _ca.drz files and I end up with what appears to be a negative, non registered image???

Would someone kindly point out where I'm screwing up?


Thank you,

Fred

PS:  I'm finding many comet alignment threads going back to 2011.  Is there a recent and concise, step by step thread? 

[ftherrmann]

I thought I had it figured out, but apparently not.

After doing the comet alignment I'm getting two sets of files.  one set which is comet aligned and one set that is apparently star aligned since I've checked off both comet and star drizzle save.

When trying to do a drizzle integration using these comet aligned files I'm getting a "no location vector" found.  I think I've defined the information in the parameter and subtract section correctly.

Confused....  Please see screen grab with error.


PS: Does a new operand file need to be created and defined for each color?

[AstroDude]

HI , this is no help but if you ever find out how to do it right could you please share your workflow !

Mitch. lost in Pixinsight, comet land !

[ftherrmann]

PixInsight's biggest problem is the cryptic method in which most things are done.

Example:  I've done enough object oriented programming to understand the basic user end model behind the PI interface.  However, oop isn't necessarily the friendliest user interface unless you already happen to be an oop programmer.  I've complained about this before and nothing ever seems to change.  If a user wants to name his process icon "ProcessIcon-FixMeUp" it should be allowed instead of having to use an underscore in place of the dash.  If it's a legal windows file name character it needs to be allowed.  I wonder how many people don't even know where the underscore character is?

Funky way the crop is implemented.  Define the process, but don't use it before you create another instance!  Then drag and drop the new instance.

Histogram process and just about any other process that ends up in you having to do an autostretch.  Why give the user a black 32 bit image after a process?  Why not just add one more instruction to the process that does adds an autostretch after execution?  If the user doesn't like the autostretch he can always change it, but NO it's got to be a black image...  Totally baffling..

These are just a couple of weird implementations.  But hey, I get to sell more copies of my "Astrophotography, Just the Facts!", Warren sells more video tutorials and Harry just keeps on YouTubing along!

A step 1, step 2, step 3 instruction would go along way in terms of showing how PI processes actually work.  A rethinking of the user interface would sell more copies.  But what the heck,,,  if the goal is to keep this amazing product for the few and not the masses, so be it!   Who wants to make money anyway?  It also helps if you live on the PI Forum...

My guess is that only about 2 or three people, including the guy who wrote the original script know how to actually use the cometalign.  At least that's what the number of reads vs replies ratio of this post tells me.

I'll eventually muddle through the pop up's and figure out how to use the cometalign after many hours of frustration, unless I finally say screw it and go back and do a manual registration of the comet which will take me about 10 minutes.

[ncwolfie]

Another lost soul trying to use comet alignment. Watched the tutorials, have read the chapter from Warren Kellers book and am no farther along from removing stars than when I started. A lot of wasted time on what should be relatively simple.