Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Hybrid View

  1. #1

    Default ACP Log Analyzer

    Hi everyone

    I've been playing around over the last week or so writing a simple 'analyzer' for ACP logs.

    The idea is simple: point the app at a bunch of logs (or even a single log) and it provides a summary of your ACP-based activities for the period covered by the logs.
    For example, it can tell you what your average pointing error is when slewing to objects, what your avergage FWHM is, how many plate solves failed, how many times an auto-focus run succeeded/failed, etc.

    Jim McMillan has been helping me with additional logs, testing, and with suggestions for improvements.

    Right now I'd say the app is "in Beta", meaning that it seems to work OK as far as I can tell.
    There are still some improvements and additions to be made, however, I wanted to make it available to the wider ACP community to see if it was of any interest.

    The app ('ACP Log Analyzer') is a stand-alone .NET-based .exe (i.e. it's not an ACP script or add-on in the true sense).

    If you're interested in taking a look, the installer can be downloaded from here:
    http://rarcher.org/astro/acpLogAnalyzerHelp.html

    Russ
    Russell Archer
    LX200 ACF 12in, SXVR-H9, SX AO-LF, SX Lodestar, SX FW

  2. #2
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,949

    Default

    How neat, Russ! I can't wait to try it out.
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  3. #3
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    27,953

    Default

    Wow, this looks really great!!! When you declare it "production" I'll stick it here.
    -- Bob

  4. #4

    Default

    Russel

    I just tried the analyser out, Great work! One of the things I'm interested in indetifying and was wondering if you think this might be a feature is to be able to determine which pictures or runs had a guiding failure and the image run continued unguided. I see setup for focus failure and plate solve failure but nothing for guiding failure. Any thoughts?


    Todd

  5. #5

    Default

    Hi Todd

    Yes, that's a great idea - I'll add it to the list of new features I'm working my way through before I make the "version 1.00" release available.

    I've been getting some help with testing from Jim McMillan, and he's made a load of fantastic suggestions

    I'm hoping to make the 1.00 release available in a day or two,

    Best wishes

    Russ
    Russell Archer
    LX200 ACF 12in, SXVR-H9, SX AO-LF, SX Lodestar, SX FW

  6. #6

    Default

    Hi Todd

    I'm working on implementing the guiding failure report. I've been looking through my logs for examples and I've found this:

    21:57:50 (guider error n/a or too high, try #19)
    21:57:51 (ex=1.38 ey=2.60)
    21:57:51 (guider error n/a or too high, try #20)
    21:57:52 (stopping the autoguider)
    21:57:52 **Imaging error: **Excessive guiding errors just before image acquisition
    21:57:52 Will try image again, this time unguided.
    21:57:52 (taking 300 sec. exposure, Blue filter, binning = 2)

    Do you have any examples which fail differently from the above (e.g. that fail in the middle of imaging, or some other failure)? I just want to be sure I cover all the possible failure scenarios.

    Thanks

    Russ
    Russell Archer
    LX200 ACF 12in, SXVR-H9, SX AO-LF, SX Lodestar, SX FW

  7. #7

    Default

    Russell

    No Mine are the same issue. So far I've noticed them right after the dither process. I'm thinking the issue occurs if the star fades a bit due to cloud. I basically want to figure out which images would have been unguided so I can double check the image before trying to preprocess it.

    Todd

    Here are similar snips from my logs

    07:05:05 (guider error n/a or too high, try #49)
    07:05:07 (ex=0.50 ey=1.16)
    07:05:07 (guider error n/a or too high, try #50)
    07:05:07 (stopping the autoguider)
    07:05:07 **Imaging error: **Excessive guiding errors just before image acquisition
    07:05:07 Will try image again, this time unguided.
    07:05:07 (taking 600 sec. exposure, Lum filter, binning = 1)

    (guider error n/a or too high, try #47)
    08:09:31 (ex=0.25 ey=0.66)
    08:09:31 (guided dither, 1 good cycles)
    08:09:34 (ex=0.61 ey=0.76)
    08:09:34 (guided dither, 2 good cycles)
    08:09:36 (ex=0.18 ey=0.61)
    08:09:36 (guided dither, 3 good cycles)
    08:09:36 (stopping the autoguider)
    08:09:36 **Imaging error: **Excessive guiding errors just before image acquisition
    08:09:36 Will try image again, this time unguided.
    08:09:36 (taking 600 sec. exposure, Lum filter, binning = 1)

  8. #8

    Default

    Perfect! Thanks for the info Todd - I've implemented the feature and now you can see on a per-target basis how many times guiding failed. You can also see an overall count for the number of times guiding failed for a collection of logs.

    I've got a few other bits and pieces to complete (today hopefully) and then I'll post an updated version.

    Thanks again for the feedback.

    Russ
    Russell Archer
    LX200 ACF 12in, SXVR-H9, SX AO-LF, SX Lodestar, SX FW

  9. #9
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,949

    Default

    Russ, One of the differences I have implemented is to not count to 20 - I only count up to 8 before declaring a failure. So please don't rely on "20" for a trigger. Regards,
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  10. #10

    Default

    Hi Dick

    Thanks a lot for the heads-up, but actually I'm not relying on a specific number of retries to determine when guiding has failed.

    Also, I've just finished the first (1.00) release, which you can download from here:
    http://www.rarcher.org/astro/acpLogAnalyzerHelp.html

    Russ
    Russell Archer
    LX200 ACF 12in, SXVR-H9, SX AO-LF, SX Lodestar, SX FW

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Updated version of ACP Log Analyzer with support for ACP 7
    By Russell Archer in forum ACP Log Analyzer 2017
    Replies: 12
    Last Post: Mar 29, 2017, 05:00
  2. New version of Log Analyzer (with added graphs)
    By Russell Archer in forum Add-Ons, Enhancements, and Helper Components
    Replies: 19
    Last Post: Nov 16, 2012, 02:54
  3. ACP Run/Log Analyzer
    By Jim McMillan in forum Success Stories & Kind Words
    Replies: 3
    Last Post: Mar 2, 2012, 23:00
  4. Is there a Hot fix change log for ACP
    By Neil Chase in forum Customer and Pre-Sales Service (non-technical)
    Replies: 4
    Last Post: Jun 3, 2010, 16:26

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •