Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

118 Excellent

About jimjam11

  • Rank
    Star Forming
  1. No, normalised real and scientific notation. They are then directly comparable with the noise evaluation output...
  2. I used this link: https://pixinsight.com/forum/index.php?topic=7388.0 Basically a combination of the Statistics process and Noise Evaluation script...
  3. Whilst we went on a bit of a detour I think we have shown a couple of things: 1. The SNR improvement is measurable and visible. 2. The benefits of binning post acquisition massively outweigh the cons because it gives you choices; I see this in the same way I see RAW vs jpg with a dslr...
  4. Thanks, That was relatively easy to do and produced the following numbers: No binning - SNR: 3.59, FWHM: 2.706px = 3.14" Bin2 before integration - SNR: 6.09, FWHM: 1.599 = 3.69" Bin2 after integration - SNR: 6.18, FWHM: 1.598 = 3.69" SiftBin - SNR: 6.27, FWHM: 1.572 = 3.63" It definitely works, it gave tighter stars and a better SNR! Was this the tool you used to downsize your example image higher up without any resampling?
  5. Never used it before. Would it be simple to run over a set of files and produce the sub-divided subs? Using auto, never even looked that far down the star alignment process before! Specifying Lanczos-3 I get a FWHM in the integrated stack of 1.594px = 3.68"
  6. Original sampling rate was 1.16" pp More research required to see if I can split bin! Is there another tool which does this easily?
  7. Just ran an experiment on some of my IC1396 data. For a stack of 59x300s subs I get: No binning - SNR: 3.59, FWHM: 2.706px = 3.14" Bin2 before integration - SNR: 6.09, FWHM: 1.599 = 3.69" Bin2 after integration - SNR: 6.18, FWHM: 1.598 = 3.69" I got SNR by getting the AvgDev for each image as S, and the noise value from the NoiseEvaluation script as per this link Both of the binned images look cleaner but they are much less sharp bin2.fit NoBin.fit NoBin_int_Bin2.fit
  8. There is an example here which can be easily modified to batch bin: http://pixinsight.com.ar/en/info/articles/23/batch-processing.html The only problem with this approach is if your image has WCS coordinates PI will raise an alert for every file that you need to dismiss! Edit: If you change the xisf file treatment you can get around this as well: https://pixinsight.com/forum/index.php?topic=11616.0
  9. My understanding is that this is not optimal. There is limited benefit to binning cmos at capture time because there is no read noise gain. If you had excellent seeing but captured binned then you are effectively throwing away resolution (especially up at 2.8" pp). You also get more control of the binning by doing it post-capture. (You do of course gain in data volume by software binning but hard disks are cheap)
  10. CLS CCD now reduced to £70 including postage...
  11. If that is typical then you are already pretty close? Assuming a guidescope your MnMo looks high, I would expect 0.2 or below with a typical 180mm focal length. Also not sure what a realistic expectation is for a heq5, I suspect around 1”...
  12. Next time you are out, use the guidescope and run a new calibration. Once complete run the guiding assistant for 7+ mins and it will give you a wealth of information you can then act upon...
  13. What is the problem you are trying to solve? It doesn’t matter what phd looks like as long as it is working. If you tell phd to auto select a guide star it will pick the best one so you don’t need to worry about them being too bright. A 50mm guidescope will easily be enough for 550mm with an asi1600...
  14. Had one of these for a couple of days and I think this is the first piece of astro equipment I can use when it is cloudy and raining! I notice the app has a record function whereby it can write the data to a csv which could then be analysed. Has anyone ever done this as a way of measuring the number of clear hours we get per week/month etc? This seems like it could be very useful information???
  15. I do similar, I use 76 for LRGB and 200 for narrowband. I get 30s L, 60s RGB and 300s for Narrowband. I then interleave the frames in SGPro so I capture LRGBL before a dither...
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.