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

Pages: 1 [2] 3 4 ... 6
General / Re: Aperture Photometry error posPx is null
« on: 2018 January 03 14:15:51 »
Hi Andres,

Thank you heaps for jumping on this and fixing it so quickly.

Is there anything I need to do, or just wait for PI to auto update?


General / Re: Aperture Photometry error posPx is null
« on: 2018 January 02 15:46:20 »
Hi Andres,

I sent you a private message with the FTP details.


General / Re: Aperture Photometry error posPx is null
« on: 2018 January 02 09:43:53 »
Hi Andres,

I can upload the image to my FTP server if that helps, otherwise let me know if you prefer a different method.


General / Aperture Photometry error posPx is null
« on: 2018 January 01 15:54:19 »
Getting this error and am not sure what the problem is.  The log shows the image plate solved successfully, the script then downloads Vizier data from UCAC3 catalog, showing 3070 objects inside the image and 12,520 catalog stars, but then get the error:

*** Error: Failure to process image file 'F:/Temp/': TypeError: posPx is null.


General / Re: New Readout Mode
« on: 2016 December 21 11:53:53 »
If BITPIX=16 then the values read from the FITS file are signed 16 bit integers.  The problem is whether there is an offset applied.  In some images there is no offset and so a value of 1024 for the pixel should readout as 1024, it does not, an offset of 16378 is added to it.  The offset should only be added if specified in the FITS header (BZERO=13768).  If this keyword is not present then no offset should be added.

But, because the FITS file can have negative integers (I agree there shouldn't be any) then it must be carried through to the readout value.  I guess when they created the FITS standard they should have stayed with unsigned 16 bit rather than signed integers.  I guess they had a reason for it.

General / Re: 8 bit FITS images
« on: 2016 December 21 11:47:56 »
If the pixel values are maintained at the low level and only 'displayed' by readout option, then shouldn't the raw value be 64 and when displayed, regardless of the readout option, it should always show 64?

General / New Readout Mode
« on: 2016 December 20 23:45:34 »
Having learned that Readout affects how a pixel value is loaded from a FITS image and displayed then we need to add a new mode: 16 (32k).  In this mode the 16 bit pixel value loaded is a signed 16 bit number with no offset.  So the range is (-32k to +32k).  It means a value of 1024 is read and displayed as 1024.

This is different from the current readout mode of 16 (65k) where a 16 bit pixel value is loaded and 32768 is added to the value and has a range of 0 to 65k.  In this case of value of 1024 is displayed as 1024 + 32768 = 33792.

General / Re: 8 bit FITS images
« on: 2016 December 20 23:35:51 »
I'm surprised by that.  I thought readout was how a pixel value was displayed or formatted in internal memory, not how it was input from the FITS file.  I thought BITPIX defined the reading of the pixel and therefore the pixel value when it was loaded into the internal format (e.g. 64 bit floating point).  If BITPIX indicates 8 bit then the pixel value is 64, no matter how it is displayed (e.g., integer, floating point, etc).

But from your reply, Readout is exactly that "Read" "out", it defines how the FITS file is 'read' and displayed 'out', which means this can override the BITPIX setting.  Is that correct?

General / 8 bit FITS images
« on: 2016 December 20 10:53:57 »
When I open a FITS image with BITPIX=8, the values are treated as 16 bit numbers instead of 8 bit numbers.  For instance, if I have an image where all the pixels are 64 then PI displays them as 16448.  It should be 64.

New Scripts and Modules / Re: Networking in a Script
« on: 2016 December 08 20:46:50 »
Thanks Mike .. I'll check it out.

New Scripts and Modules / Re: Networking in a Script
« on: 2016 December 07 12:58:56 »
A possible alternative is use to use some form of file event scripting where the script monitors a folder and when a new file appears in the folder, it is read and processed similar to a UDP message.

Has anyone tried this?

New Scripts and Modules / Networking in a Script
« on: 2016 December 07 12:48:00 »
Has anyone written a script to receive and send UDP packets?  The idea here is for one or more external programs to send 'requests' to a script running on PI.  The script would process the script (e.g., running a calibration on an image) and return a result to the requestor.  UDP is much easier to use because you do not have to setup and maintain a TCP session.

If there is no script, is the Network class in SpiderMonkey available in PI?

General / Re: How to Add stars
« on: 2016 July 20 01:37:16 »
Thanks Andres.  I found another method, using StarMask.  This process looks to pull out the faint stars and 'magnify' them.  The number of stars brought out depends on the noise threshold.  Makes for a very nice 'mask'.  I then used PixelMath to add the stars back to the image and the net effect was leaving the extended objects untouched but bringing out the faint background stars.

General / How to Add stars
« on: 2016 July 19 19:02:45 »
I am doing an artistic image which needs some stars to an otherwise black background.  I was able to use ImageSolver to register the image and the star mask generated does show lots of other stars.  Question now is how do I use this to map the stars on to the image so that they look as if imaged.  In other words, I would like them to have a FWHM shape of say 3 arcsec and show as faint and bright by boosting their appearance.  I find lots of articles on how to remove stars but not necessarily how to add them back in.

General / Re: HDRComposition question
« on: 2016 July 19 03:16:24 »
After reading through the explanation of how HDRComposition works and after analyzing my images I decided to try 80, 20, and 5, by adding them in that order and then turning off the automatic exposure setting.  This worked and I got a good HDR.

Pages: 1 [2] 3 4 ... 6