Focuser temperature availablility in log file

Hello,
I am looking for the temperature in the log file, and could not locate that. Is it even written in the file?
In order to check the Auto-Focus routine with my setup, I am planning on running a full night of autofocus runs, rotating through all my filters, and compiling all that in a spreadsheet, in order to eventually check the accuracy of the Auto-Focus method with my setup, check the step delta for each filter, the temperature compensation, etc…
My issue is that I can not locate the focuser temperature value in the log file? Could that value be logged in the file as well?
Thanks!
Olivier

Attached: last night log file. sg_logfile_20160204210609.zip (118.9 KB)

Temperature and focus position is logged as part of the auto focus results. Your log doesn’t contain any auto focus runs so this data doesn’t exist.

Thanks,
Jared

The Autofocus ran at 10:17pm, 11:17pm, 11:58pm, 12:59am, 1:41am and 2:47an (I got the times from the AFPack folders that are logged) and the extract from the log file below.
I am trying to look around these time for temperature information.
Thanks,
Olivier

2/4/2016 22:17 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3486; HFR 1.07)…
2/4/2016 23:17 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3528; HFR 1.14)…
2/4/2016 23:58 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3335; HFR 1.15)…
2/5/2016 0:59 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3335; HFR 1.15)…
2/5/2016 1:41 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3735; HFR 1.89)…
2/5/2016 2:47 [DEBUG] [Camera Thread] Auto focus is complete (weighted avg method: 3972; HFR 1.58)…

Sure enough, not sure how I missed that. If you look above you can see lines like:

[2/4/2016 10:17:01 PM] [DEBUG] [Camera Thread] New focus position is at 3486 (@5.00C). Moving focuser…
[2/4/2016 11:17:19 PM] [DEBUG] [Camera Thread] New focus position is at 3528 (@4.00C). Moving focuser…
[2/4/2016 11:58:39 PM] [DEBUG] [Camera Thread] New focus position is at 3335 (@3.27C). Moving focuser…
[2/5/2016 12:59:00 AM] [DEBUG] [Camera Thread] New focus position is at 3335 (@2.61C). Moving focuser…
[2/5/2016 1:41:16 AM] [DEBUG] [Camera Thread] New focus position is at 3735 (@2.48C). Moving focuser…
[2/5/2016 2:47:05 AM] [DEBUG] [Camera Thread] New focus position is at 3972 (@1.59C). Moving focuser…

Thanks,
Jared

I think what @oguerrea is proposing might be an idea for a focus wizard in SGP rather than doing it manually.

I think I proposed that in some thread or other a while back. Basically a wizard that would look at any log file or set of log files and record and graph the focuser position vs temp.

Would not have to be the SGP guys that do this, any decent programmer should be able to do this pretty easily. Heck, even just extracting the info to a CSV that could be brought into a spreadsheet would be enough.

So… this seems like you are all describing something similar to Image History where for every light frame, it logs the image name, HFR, focuser pos and temperature. The one piece missing is maybe some tool to export this data (so you have it for your own records). In this case the data would look slightly different (no file name to log, just info about each AF run… maybe the trigger type might be of some interest too).

CCDMan,

I have a script that does that but it is not very user-friendly. It is a command-line script that runs under cygwin. If you have a local astrometry.net installation, you could use that cygwin instance to run it. It reads one or more sg log files and creates CSV output which you can then paste into excel.

sample output:
$ ./sg_log_get_focus_pos sg_logfile_20160204185916.txt 2/4/2016 7:11:05 PM,Lum,5.23,8030,0.59 2/4/2016 8:45:50 PM,Lum,5.36,8000,0.60 2/4/2016 10:21:35 PM,Lum,4.48,7965,0.65 2/4/2016 11:34:31 PM,Lum,3.40,7959,0.63 2/4/2016 11:46:42 PM,Lum,2.72,7955,0.62 2/5/2016 12:24:56 AM,Lum,3.11,7949,0.63 2/5/2016 12:37:15 AM,Lum,2.70,7941,0.56 2/5/2016 1:17:37 AM,Lum,1.24,7940,0.58 2/5/2016 1:52:59 AM,Lum,0.69,7941,0.62 2/5/2016 2:17:46 AM,Lum,1.29,7941,0.65 2/5/2016 3:49:28 AM,Lum,0.75,7928,0.71 2/5/2016 4:35:38 AM,Lum,1.22,7926,0.61

The columns are: date-time, filter name, temperature, focus pos, HFR.

Here’s the script if you want it. http://adgsoftware.com/misc/sg_log_get_focus_pos

Sorry, this is not very useful unless you are prepared to run a command in a cygwin shell, but throwing it out there anyway. If I get some free time I will try to put together a more user-friendly version of this, perhaps a web-based thing.

Andy

Thanks Andy,
I manage to run cygwin, by basically running cygwin.bat in a cmd shell in the cygwin directory, and I have the $ prompt.
Where/how do I save your sg_log_get_focus_pos script?
Thanks!
Olivier

if you save the script to your cygwin home directory and put the log file also in the cygwin home directory you can open the cygwin shell and at the $ prompt run
sh sg_log_get_focus_pos sg_logfile_nnnnnn.txt
In case you do not know the location of the cygwin home directory, open a cygwin shell and run:
cygpath -w ~

oguerrea,

If you want to avoid the cygwin commands, here is an easier way.

http://adgsoftware.com/misc/sgfocus/

Select your log file and click “Extract”. The page will extract the focus information and download it as a CSV file.

Caveat: I only tested the tool with recent SGP log files. If the SGP log file format changes, the tool will probably fail to extract the information correctly. I’m pretty sure it will not work with log files from older versions of SGP. The log file is not really meant for this kind of thing, so we should probably expect that this extraction tool will break from time to time and we will have to fix it.

Andy

There is also this item sitting in the feature request category: Focus history module. The feature request was suggesting displaying AF info, but it would be great to have an Export button to save the info as CSV too.

Andy

http://adgsoftware.com/misc/sgfocus/

sorry but this address is not working anymore, any other option?

Sorry, it looks like that tool got lost a while ago when I updated my server. The only other option at this point would be to use the script that is mentioned earlier in this thread.

Thank you @Andy , I will try that.