Jump to content



  • Content Count

  • Joined

  • Last visited

Community Reputation

143 Excellent

1 Follower

About Annehouw

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Location
    The Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Resurrecting this old thread... Shortly after I first published this image of M63 showing the tidal stream, I was graciously given many hours of images by Oliver Penrice. Thank you very much, Olly! At that time, I was experiencing sort of a processing burnout. I had spent way to many hours behind the screen to bring out M63 and its halo and tidal stream. I have recovered though and I integrated this data into my earlier image. I have attached a inverted black and white version here for the sake of visibitity. To celebrate this occasion, I did a fairly extensive astrophysical wr
  2. Hi ramxis Have a look here https://darksitefinder.com/maps/world.html#8/50.179/9.877 Even better here: https://www.lightpollutionmap.info/#zoom=7.80&lat=50.1755&lon=9.2515&layers=B0FFFFFTFFFFFFFFFF Frankfurt is bad, but if you go to the east a bit, it gets a lot better. Have fun! For your smartphone, there is also this: https://www.darkskymap.com/ Fun thing about an app is that you can turn on your gps and see how far you have to go from your current position. White is bad, red is bad, yellow is better, shades of green are quite OK, blue is even bet
  3. Hi Dave, Yes I did try that. It was my first go at this and it would work well once you have isolated the Ha excess signal. Without doing that...since the core of the galaxy is quite bright in Ha, just adding the Ha image to the RGB image resulted in a red core area. So that was a dead-end for me. I guess you could do the continuum subtraction in PS through a set of subtract blend mode operations, but I suspect that this is one area where PI is less complicated than PS I do use PS in my workflow as some things are (like you say) just so simple in PS. First of all to clean up mask
  4. I have written a short description based on this image and the physics happening around the core region of M106: https://www.astrobin.com/uk8p8v/ It is for those that are interested in the physics of outer space (as I am). In this forum, I would like to say a bit about the image processing part as that might be of interest to some of you using PixInsight. Note that I also posted this on CN....... The goal This image was processed with the plan to show the main features of the interesting activity that M106 shows around the core. As such, saturation and color contrast have
  5. Let me give you a contrarian view and advise you against the L-extreme. Looking at the fact that you are planning to image with the hyperstar, you will be living in fast focal ratio land. And everything is a little bit different there (and sometimes a lot...battling tilt comes to mid). In the case of narrowband filters there is the issue of bandpass shift and resulting drop of transmission off center. The L-extreme has narrow bandpasses that wil make it's transmission at f/2 severely impacted. This is a subject that comes along every so often. An authorative discussion on this
  6. Holy smokes! That must be one beast of a machine. A stacking run of 400 subs in APP can easily take 4 hours on my machine (i5-2500k / 32gb ram), 16MB subs.
  7. As an add-on to the original question: APP has promised GPU support to speed up processing. Currently, it only uses the GPU for (re)drawing the image. There is no pointer as to when real GPU support will be implemented. PI has promised GPU support (since 2015). Currently it has none, but I found a reference from Juan (the developer) to "hopefully" before the end of this year. StarTools has GPU support (1.7 alpha) PS/Affinity Photo all have very limited GPU support as far as I know CPU performance still is very significant if you want speedy processing across the boa
  8. Thanks for the suggestion, Ivo Actually it is LGA1155 (with i5-2500K). I had never thought about upgrading it with a Xeon processor. Since Moore's law stalled I have not really looked into speed, aside from SSD and extra memory. It is my professional production machine and runs very stable, so not so inclined to tinker with it. Recent developments (as in Zen3 today) might however persuade me to plan a motherboard/CPU/memory upgrade at some time in the near future.
  9. One of the best insights into filter performance I know of is from Jim Thompson. Here: http://karmalimbo.com/aro/reports/reports.htm you can download (the link "multinarrowband filters") actual spectral measurements of bandpasses and transmission percentages as a function of angle of incidence (page 16: translated to f/ratio). It is specifically for multinarrowbandfilters, but the same principles apply. At the bottom of the page I linked above, you can find a comparison between the popular Optolong L-Enhance and L-Extreme filters (the latter currently made of unobtanium). At page 11 of said re
  10. I couldn't resist and did the comparison, but had to bin the image 50% to keep my sanity. So now, on a 2420x1520 image: Startools 1.7 non-GPU.: Deconvolution default settings: 165 seconds Startools 1.7 GPU edition: Deconvolution default settings 15 seconds That is a massive 11 fold speed increase.
  11. It is probably a good idea to forgo the GPU utilisation discussion and look at what it means in practice. To that end, I loaded this image (4851 x 3044 pixels) and measured two actions with a stopwatch: Startools 1.6 ( CPU only: 10 years old Intel i5 ) Autodev (with ROI): 13 seconds. Deconvolution (PSF Moffat Beta=4,765, radius=2px, 7 iterations, rest default) 132 seconds Startools 1.7 (CPU i5 + GPU: NVidia GTX1070) Autodev (with ROI): 3 seconds. Deconvolution (same settings as above, rest default) 39 seconds So on my system 1.7 is 3 to 4 times faster than 1.6. Really Impressi
  12. Hello Ivo, Nice of you to comment from down under! I do not know if a full discussion on the internals of Startools is appropriate here or better on the Startools forum. I have not posted my comments there. What I see can still be novice user error. The main takeaway here was that I was impressed with Startools. Having said that: GPU support First of all: other software developers have promised GPU support for some time; you are delivering. I am aware that it is not a trivial undertaking. So hats of for that! Having measured non-GPU-assisted Starne
  13. I have always been interested in Startools. It has a very distinct philosphy of how to process astro images. I have a license since version 1.3 (many years ago), but have never been in love with the product. At the time I was imaging with a 50 megapixel dslr and that was way too much for the processor hog that Startools is. It does a lot of computational analyses and it just froze. Now, with version 1.7 (Alpha at the moment), there is GPU support. I have a decent GPU (GTX1070) for video editing and I decided to give it another look. I am proficient in Photoshop; am somewhat intermediate i
  14. Thanks, all! @Craney: As this practice of long-boating and flaming has used up most of the original forests on Iceland, I took the remnants home and I Frankensteined it (super glue, no stiches). Unfortunately its character was not as benign as the original, so I had to kill it off unceremoniously.
  15. A bit of a sentimental title, agreed. I used to go to Iceland in winter quite regularly. Walking through ice caves and hunting the northern lights. Maybe this routine will return some day. Anyway: If you have witnessed the aurora you know that it can change quite rapidly. In this picture some highlights from a particularly active night at the shores of the glacial lake Jökulsárlón in Iceland I changed the position a bit to capture the action in the sky and as the intensity varied quite a lot, I also changed ISO. The top image is 20s at ISO 3200, the middle and bottom image ar
  • 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.