PSFEstimation script

[mschuster]

Yes Dave, 0.33 is the latest, thanks.
Mike

[mschuster]

Here is a link to a batch version of the script.

https://dl.dropbox.com/u/109232477/SubframeSelector.0.4.zip

You can add the script to the menu by selecting the src directory in Feature Scripts, or choose SubframeSelector.0.4.js in Execute Script File. You will find documentation in the doc/scripts/SubframeSelector.0.4 directory, open the html file in your browser. The tool tip of the info icon at the bottom of the script's dialog has helpful information. You can also install the documentation by running the complier on the pidoc file, but for some unknown reason the resulting documentation is not available from within PixInsight, so please open the html file.

The script presents subframe measurements in a table and in plots. You can also save the measurements in a csv file for postprocessing. The script also has features for subframe approval and weighting, these are optional.

Thank you  Hans Pleijsier, Georg Viehoever and Juan for your help and code.

Thanks,
Mike

[Alejandro Tombolini]

Mike, it is a fantastic scrip. Thanks you! 

I have installed it and works perfect. I tried it a set of 94 images from differents days and I could reject the images that are far form the media in FWHM and SNRWeight and now i am trying to understand how to determinate the best images to use in StarAlignment. Thanks for the documentation, it is very clear.

Saludos. Alejandro.

[mschuster]

Alejandro thank you for the comments. 

It is safe now to install the documentation. I made a change a while ago to fix a typo and did not realize that this change also fixed the doc install problem.

Run Scripts>Development>Documentation Compiler, click Add Files, select SubframeSelector.0.4.pidoc in the script's pidoc directory and click OK. Now docs will be avaliable in Process Explorer>Scripts>Batch Processing>SubframeSelector.0.4. (Note that you can't access Process Explorer when the script is running due to the modal nature of PJSR.)

Mike

[Alejandro Tombolini]

Hi Mike, installed perfectly. Thanks again!
Saludos, Alejandro.

[Geoff]

Hi Mike
Script seems to work fine, but when I try to install the documentation I get an "Access Denied" message.  Any suggestions?
Geoff

[mschuster]

Geoff, maybe an admin account premissions issue? Can you run PI as an administrator?
Mike

[Geoff]

Geoff, maybe an admin account premissions issue? Can you run PI as an administrator?
Mike

That works.
 Thanks Mike

[vicent_peris]

Hi,

I'm just testing now this tool. I've found it would be very useful to set a cropping parameter for all the images. Usually you need only a small crop of all the frames to decide which are the best ones. In my case, I have about 500 frames and each one is a 16-megapixel image. So processing the images at original size is not a good idea... Now I'm cropping the images to 512x1536 with an image container, just after processing them. But this doesn't allow to automatically rename the files, of course.

Regards,
Vicent.

[vicent_peris]

Another idea. Could it be possible to automate this script with a watch dog pointing to a folder? The idea is to have the script running and, every time there's a new image, measure the PSF and update a text file in the hard drive with the PSF readings.

Regards,
Vicent.

[vicent_peris]

A plot a just made from the 541 image data set:



Could it be possible to choose the graph size in pixel?


Thank you,
Vicent.

[mschuster]

Wow. Cropping is a good idea, I will add this. Also, I will add something Juan suggested that will help performance.

Yes, a graph size is needed and maybe a scroll bar also. I will add this. I will think about a watch dog too.

Thank you,
Mike

[vicent_peris]

Thank you,

A watch dog would be very useful for real-time monitoring of your image session. Also, for professional observatories, this could be useful to compare image seeing to seeing monitor measurements. The trick is to output a text document to let the user to graph himself the values (in Linux with GNUPlot, for example).


Regards,
Vicent.

[pfile]

holy smokes, this is great, thanks for the batch version. also i just realized the original version is something of a replacement for CCDInspector.

i hate to make feature requests but i wonder if the script could move bad frames into a different directory rather than copying good frames? unless something's gone horribly wrong i usually only have a few bad frames. this would save on disk space. or maybe it already does this and i did not notice.

[mschuster]

Thanks pfile.

I will add options so you will be able to copy/move the good/bad frames in any combination that you want. I hope to post a new version at the end of this month that will include your idea and also Vicent's requests, or at least as many of them as I have time for.

Thanks,
Mike