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 - Martin

Pages: [1] 2
1
General / Gradient Merge Mosaic
« on: 2012 June 08 04:31:27 »
Hello all
I am attempting to use this process for the first time, and I am following the video tutorial.  I have got so far,but have come to an abrupt halt.
I have created the master mosaic image and all 6 panels are in.  Now, when I load those 6 panels to align them to this master frame (register/match), 3 of the frames just will not align. So I am stuck and cant go on.

Any pointers please?
thanks
martin

2
Yes please.  The pictures are no longer loading.

cheers
Martin

3
New Scripts and Modules / Re: My little scripts repository
« on: 2012 April 25 06:01:44 »
Hello Enzo

have you taken off this link?  It doesnt appear to work any more.

thanks
Martin

4
General / Re: Triangular stars from Star Alignment
« on: 2012 April 25 05:15:48 »
Hi Juan
wish I could upload the entire set of images, but the full frame FITS files are 21Mb each and there are dozens of them.

I think Lex might have a point...what parameters in the star alignment process affect pixel rejection?

Otherwise, If you could please indicate some parameters I can try - quite simply, the data is undersampled, stars are quite blocky, and the alignment takes these blocky stars and turns them into diamond shaped stars.

thanks!
Martin

5
General / Re: Triangular stars from Star Alignment
« on: 2012 April 15 06:05:49 »
Sure, two files attached.  The file was aligned used the defaults in StarAlignment, but all of the parameters I have changed so far, has a similar result.

thanks
Martin

6
General / Triangular stars from Star Alignment
« on: 2012 April 15 04:40:45 »
Hello
I am trying to register image data taken with an FSQ106/STL11K, which has a resolution of 3.5 arcsecs/pixel - undersampled.

The problem I am finding is that the result of the alignment from PI is triangular stars.  I have 'blinked' the original data and the aligned data to confirm this.  I have used both the defaults, and various algorithims in the 'interpolation' dialogue box to no avail.

So what values do I need to adjust to overcome this? Otherwise,PI does a great job of alignment, but is distorting the result.

thanks
Martin

7
General / Re: Repository Error
« on: 2011 August 21 18:11:23 »
Yes, that fixed it.

Thanks for the reply.

Martin

8
General / Repository Error
« on: 2011 August 20 17:32:51 »
Hello all
since the last update, I am now getting this error when I open PI.
"http://update.pixinsight.com/: Parsing repository update information: Invalid platform 'version' attribute value: 1.7.0:1.7.9 (line=16,column=58)"

So, I am not getting any updates.

Any thoughts?
thanks
Martin

9
General / Re: Registration Fails
« on: 2010 December 06 16:34:55 »
Thanks for the post and the information George.

Martin

10
General / Registration Fails
« on: 2010 December 03 18:38:48 »
Hello
Really struggling to get PI to register individual frames to a large reference frame.
What I have is a 4 panel mosaic reference frame, and I am trying to register all of the RGB frames for all 4 panels against this reference frame.
PI reports registration successful, but fails to properly register the frames and there is always some residual misalignment at the edges of each frame.
The data is 3.5 arsecs per pixel and the FOV is 4 degs x 4 degs, so it is widefield data.

Even if I try to create a mosaic in PI, rather than aligning to a reference frame, I get the same misalignment at the edges.

Are there particular settings I can tweak to make this work?
thanks
Martin

11
General / Re: Saving Combined Files
« on: 2010 May 09 18:24:15 »
Hi Niall...I will get those images to you.

Jack, I did as you suggested.  Took my PI aligned images, saved them all as IEEE Float, combined them in PI, saved the resultant file as 32bit float but every single background value was zero, and star values were extremely low...so you have nothing to work with.

Martin

12
General / Re: Saving Combined Files
« on: 2010 May 04 19:47:32 »
Gents
thanks for your replies, and sorry for the belated response.

So, my images are first calibrated in Maxim DL and saved as a 16bit signed FITS image.
I then open these calibrated images in PI, and perform alignment, and the alignment saves those aligned images also in 16bit signed FITS format.  If I then open those aligned images individually, they are fine, background in tact.

It is when I then take those PI aligned and saved images and combine them in PI that this 'error' occurs i.e when using 32bit FP format.

I am using PI versin 1.06.592 and I am using the Image Integration settings pretty much as per Harry's tutorial.

thanks
Martin

13
General / Saving Combined Files
« on: 2010 April 18 14:51:53 »
Hello Group.
When I go to save a combined image as a FIT, I have several options.

If I save the combined image as a 16bit FIT (signed) the resultant image is fine, but if I want to save my image in a larger space, and select 32bit IEEE 754 Floating Point, PI strips the background out.  I mean, the resultant ADU value of the background is zero....so you have nothing to work with.  In the 16bit image, the background is in tact.  Why does PI do this?

cheers
Martin

14
Off-topic / Re: New user question
« on: 2010 February 21 16:19:02 »
Thanks Niall for the additional explanation.

So, when a 16bit unsigned FIT created in Maxim does not open correctly in CCDSTACK (saturated areas are black e.g star cores), then is this likely to be how Maxim writes the files or how CCDSTACK reads it?

thanks
Martin


15
Off-topic / Re: New user question
« on: 2010 February 21 16:03:44 »
Thanks all

I have resaved everything as 16 bit and image alignment and integration now works in PI.
The only thing odd now, is that 16 bit unsigned FITS files from Maxim, do not open in CCDSTACK (a BZERO problem somewhere) - but that's CCDSTACK/Maxim issue.

I can understand now how/why PI treats the data and hence the black image. 
I will have to go and recreate all of my master calibration frames, as they were saved as 32bit files - so when you calibrate a 16bit image with a 32bit calibration file, the image is now in the 32bit space  - this is particularly true in CCDSTACK and when you try to save that image, it tells you that you are going to compress the dataspace from 32bit back down to 16bit unless you choose a 32bit option.

So as you can see - the FITS standard is loosely interpretated by the different softwares.

thanks for the help
Martin

Pages: [1] 2