Aperture photometry output

[korborh]

Hi,
I noticed that the Aperture photometry script output files (.csv) are showing fewer columns now. Has it changed recently?
Also, I have a request for the .csv to be a csv - right now it is semi-colon separated and not comma-separated.
Thank you.

[Andres.Pozo]

I have not changed the output of this script since march 2014.

Andrés.

[CraigNZ]

I noticed that if you select the source extraction as 'catalog' then the PSF columns are null, but if you select 'image' then you get the psf information.

[korborh]

Thank you Andres, I really like this script. I am using it to extract the SDSS catalog magnitudes for my images with Sloan g'r'i' filters. It is saving me a lot of time.

Because the .csv is semi-colon separated, opening in Excel does not auto populate the columns. One has to either manually copy paste or convert the semi-colon to comma and then open.
So it would be great if the output .csv has comma instead of the semi-colon separator - or perhaps an option for the user to use a separator.

[Andres.Pozo]

Because the .csv is semi-colon separated, opening in Excel does not auto populate the columns. One has to either manually copy paste or convert the semi-colon to comma and then open.

Hi korborh,

comma-separated files are cumbersome to use in Excel when the language of the computer is not English since many languages use the comma as the decimal separator.

If you want to use the files of AperturePhotometry in Excel you can use the "Text to columns" tool in Excel that converts text to columns and allows to chose the separator.

Andrés

[korborh]

Andres,

Thank you - I did not think of that  . It makes sense - I can use the text to columns without problem.

[CraigNZ]

Another note, when I analyzed the output of the script (annotated images) I noticed that close binary stars were identified as a single star.  To fix this I changed the script:

In the function: FindStarCentersDPSF (line 2283)

Changed: DPSF.searchRadius = 4 (default is 8)

Added: DPSF.autoAperture = false;

Making these two changes I now get the close binary stars as two separate stars in the output.  The first change best matches the FWHM of my images.  The second change was needed because the binary stars were 'extracted' as an ellipitcal star instead of two stars.  This made sure it correctly resolved them into two stars.

I am also researching whether to stay with the DPSF.gaussianPSF = true or switching to DPSF.moffat4PSF.  Theoretically the moffat4 more closely matches atmospheric dispersion according to the papers I have read.  But that may not be necessarily true for my specific application.  I tried DPSF.autoPSF but the results were not as good as the gaussian option.  One of the changes I am planning to make is to add a tab for DSPF so these parameters can be changed.

There are several other changes I am planning to make, one of the most important is to somehow add a console logging function so I can trace an image result set back to through the processing chain to see what was done.