Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

GreatAttractor

Members
  • Posts

    521
  • Joined

  • Last visited

Posts posted by GreatAttractor

  1. 9 hours ago, Kitsunegari said:

    I believe they are on the imx174 camera sensor and i do not really want to risk damaging it by wiping it down.

    Don't worry, it's not that fragile. I recommend one of those optics cleaning microfibre cloths - sweep the sensor (or the window glass if your camera has one) with minimal pressure (since we just want to catch the specks, not "scrape away a stain") a few times, that should do it. Also, when changing cameras / attaching C-mount lenses etc., minimize the time the sensor is exposed - have a cover ready and reattach it immediately.

    • Like 1
  2. ImPPG is written using cross-platform libraries, so it can be compiled as a native OS X application. I have plans to eventually get myself a Mac, iron out any potential incompatibilities and create an OS X binary version for download.

    For the time being, you could try running the Windows version via Wine (should work fine, at least in the non-GPU-accelerated mode).

    • Thanks 1
  3. ImPPG version 0.6.0 has been released. After some architectural cleanup, I added a GPU/OpenGL back end, that is, almost all processing (except image alignment) is now performed on the GPU. In practical terms, on most computers it means:

    • processing is faster by a factor of several or more
    • for quite big selection sizes and moderate L-R iteration counts, the results are rendered immediately as you move the "sigma" slider
    • no delay of image refresh when scrolling with zoom ≠ 100%
    • cubic interpolation does not cause a slow down

     

    You can see the new version in action in this short video:
    https://www.youtube.com/watch?v=giq4jCnC6KM

    Benchmarking result of my system - CPU: Ryzen 2700 (8 cores, 16 threads, 3.2 GHz base), GPU: Radeon R370. A typical workload - batch processing of 200 images, 1.2 Mpix each, 50 iterations of L-R deconvolution, unsharp masking and tone mapping. (Note that in CPU mode all cores are used.)

    • CPU mode: 2:20 min
    • GPU mode: 19 s

     

    Even on a 5-year old laptop with an integrated Intel GPU there is a noticeable speed-up.

    • Like 4
    • Thanks 3
  4. Image Post-Processor (ImPPG) version 0.6.0 is available at: https://github.com/GreatAttractor/imppg/releases

    New features:

    • GPU (OpenGL) back end for much faster processing

     

    Enhancements:

    • View scrolling by dragging with the right mouse button (previously: with the middle button)
    • Zooming in/out with the mouse wheel (previously: Ctrl + mouse wheel)

     

    If you experience issues running in GPU mode, make sure you have the latest graphics drivers. (The old CPU mode can still be used.)

  5. 14 hours ago, Rusted said:

    Last night I found a ~2 hour YT streamed video on solar image processing by Simon Tang @ Telescopes.net/Asteroid Hunters.
    Well worth watching and I intend to study it repeatedly until his exact methods sink in.
    The way he used iMPPG and other free softwares was quite startling in their immediate effect.

    Thanks, a very cool material indeed!

    Reminds me I should finally sit down to making a video tutorial myself.

     

    • Thanks 1
  6. 1 hour ago, Nigella Bryant said:

    You need to capture one for the surface details and then another with increased brightness for prominences and merge the two after processing. 

    To underline dim prominences, indeed it's best to combine two exposures. But it's not absolutely necessary if the prominences are bright; for example, in the right image below (4-pane mosaic made with Lunt 50), all that was needed was to gently "lift" the tone curve at the dark end (performed in ImPPG):

    get.jpg?insecure

     

    • Like 1
  7. Unfortunately, the reference point alignment phase is not yet as robust as I'd like (though usually works fine for my Hα material). In general, changing some of these processing settings may help:

    • search radius: try 5-10
    • structure threshold: try higher values
    • brightness threshold: try higher values
    • structure scale: try 2-3

    settings.thumb.png.f3e4962e0befbe06886525797f240069.png

    I have a few ideas for improving this, so stay tuned.

  8. 3 hours ago, MilwaukeeLion said:

    One image at a time (in order) I copied and pasted into prom1 to create another layer, lowered opacity of  new layer and lined up with first image, raised opacity back up. 

    Ouch! That's what I used to do (even with 200-frame time lapses). Got quite "fast" at it, say, 7-8 seconds per image… ;)

    So eventually I wrote ImPPG for:

    - quick batch-processing of multiple stacks

    - automatic alignment of sequences with sub-pixel precision

    Download and tutorial links available at https://greatattractor.github.io/imppg/

     

     

    Exporting the animation can be also done in GIMP:

    - open all aligned frames via File/Open as layers

    - crop/resize everything to taste

    - preview with Filters/Animation/Playback

    - make a GIF via File/Export As..., choose GIF, mark "As animation"

    • Like 4
  9. I had a Nikon D40 for a few years and loved it for regular photography (eventually replaced it with a more convenient Micro-4/3 Olympus).

    As for astrophotographic use, I did my first experiments with it (before transitioning to a modded webcam and then a planetary CCD). For simple Milky Way stacking and Solar System single-frame or a few-frame stacks it did the job:

    get.jpg?insecure

    get.jpg?insecure

    • Like 1
  10. Everything shot with 90 mm refractor + Lunt 50 etalon.

    Smoky prominences (~1 h total):

    42554605-a119-494b-be14-68bc2fc7390f.gif

    M5.3-class flare on 4/02 (0:46 h total):

    f9788239-0581-4fc3-8d54-c618df026184.gif

    AR 2661 on fast-forward (5 hours with 5-minute intervals), with a minor C2.1-class flare. Solar rotation clearly visible:

    fcd4bf4f-13fc-4e8d-b175-0158607f8602.gif

     

     

    7-pane mosaic:

    e24117bf6d946f95b74a3aeb08813e34.16536x1

     

    • Like 3
    • Thanks 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.