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 ... 7
16
General / BPP "Add Folder" option?
« on: 2018 April 09 18:31:40 »
Is there an enhancement to BPP which adds a "Add Folder" button, where all the subfolders and FITS files within those folders are added?

17
General / Re: Bias,Dark,Flats artifact removal question
« on: 2018 February 02 01:47:51 »
Hi Adam,

Thank you for the detailed reply.  I will run some tests using the methods from your reply.  I have some dark frames that have cosmic ray hits on a few images, I'll check to see that they are removed and not contributing to the Master Dark.

Craig

18
General / Bias,Dark,Flats artifact removal question
« on: 2018 February 01 11:26:18 »
Is there a process or script which can scan a collection of Bias, Dark or Flat frames and remove artifacts that appear in only one frame but not others.  For example, if there is a cosmic ray hit at a location on one image but does not appear on subsequent images then the damaged pixels could be repaired using the surrounding pixels or pixels from subsequent images.  This method would insure hot pixels, which appear in each image, are correctly allowed for and not simply removed.

19
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?

Craig

20
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.

Craig

21
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.

Craig

22
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/Image_300.000secs_00000520.fit': TypeError: posPx is null.

Craig

23
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.

24
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?

25
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.


26
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?

27
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.

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

29
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?

30
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?

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