If find the DP real-time mode very useful during a long time series. I setup a plot that I can glance at and quickly see if anything is going amiss.
I wonder if there is any way to easily access the data in the measurements table from another program so I could take some action. I confess - sometimes I fall asleep! I could trigger an alarm. Or, since I control the imaging with custom software, I could for example adjust focus if the FWHM started to drift. I set the mutli-aperture measurements so the plot and measurements table are updated after each image, but the measurements table is not available in a file until I save it. Clearly, you would not want the measurements to written after each image in normal operation, but is there a way to get this to happen in the DP real-time mode? Or perhaps I should look into the macro mechanism? Thanks for any suggestions, Cliff Kotnik
Cliff Kotnik
AAVSO KCLA |
Administrator
|
Hi Cliff,
As I was reading, I had planned to suggest the macro capability, but then saw that you had already thought of it as note in your last question. That is indeed the way to go for now. You should be able to read specific table values, and probably even save the table or generate system "beeps" if a parameter is found to be out of your defined range. Just google around for documentation on the ImageJ macro language and see if you can make it do what you want. I will also record your feature request to provide an option to auto-save the measurements table, but it would be pretty for down on the list of coding priorities. If you get something working and want to share it with other AIJ users, please post it here. Karen On 6/17/2018 7:17 PM, clkotnik [via AstroImageJ] wrote:
If find the DP real-time mode very useful during a long time series. I setup a plot that I can glance at and quickly see if anything is going amiss. |
RT_Save.ijm
I created a macro to use the getResult function to examine specific cells in the Measurements table and sound an alert. I used the IJ.renameResults(oldName,newName) function Alnair pointed out in 2014 to first rename the Measurements table to Results so that getResults actually worked. While this worked, it had two problems. The easy to access "beep()" is not very attention grabbing even when repeated. Worse, some system component started complaining about subsequent updates to the Measurements table apparently because of the rename. So I decided to fall back to periodically saving the Measurements table with the attached macro. Once started, it will save the measurements table at the rate set by the polling interval and exit when the Measurements table window is closed. I'll then watch this saved measurements table from my jupyter notebook controlling my imaging. I'm very happy for anyone to use this however and/or suggest improvements. best regards, Cliff
Cliff Kotnik
AAVSO KCLA |
Free forum by Nabble | Edit this page |