vlaiv

In principle it matters, but in reality there is a way to minimize impact. We put peak of the histogram to the right - meaning high values, because we want strong signal in flats to maximize signal to noise ratio (more signal - higher SNR). There is another way to improve SNR - that is stacking (which is very much like taking very long exposure and bypasses full well limit of the sensor). When doing OSC flats - aim for highest peak to be around 80-85%. This will put lowest peak at around 40ish % - or about half of highest one. That is difference of ~ x1.41 in SNR for high peak color vs low peak color. Doing twice as many flats improves SNR for same amount (stacking improves SNR by square root of number of frames - do twice as many and you will improve SNR by ~ x1.41). Most sensors these days are linear enough so you don't have to worry about that aspect. If you feel that your flats are noisy, just take more of them, it's that simple (I always recommend more calibration frames - more is better, simple as that - same as with lights - more lights better image). Don't be tempted to add additional filters when doing flats - it will mess up your flat calibration, and there certainly is no need to do it.

I think it is mostly practical for Alt/Az type of mount, and above is AzEq6 - it comes with this adapter. I've seen adapters to do it regardless, here is one for example: https://www.teleskop-express.de/shop/product_info.php/info/p229_TS-Optics-Piggyback-Camera-Holder-for-D-20-mm-Counterweight-Shafts.html (that one is for camera or maybe finderscope, or lightweight rig). Geoptik also makes "generic" ones like this: https://www.teleskop-express.de/shop/product_info.php/info/p5555_Geoptik-Counterweight-Shaft-Adapter---diameter-25mm.html

Actually in this context 4/3 sensor does specify diagonal size. One way of specifying diagonal of the sensor is to use fractions of the inch - 1/3", 1/2", 1/1.7, 2/3", etc. I don't think 4/3 means 4/3", but it is "legitimate" sensor size name - "Four thirds" or "Micro four thirds" - stands for diagonal of 21.60mm https://en.wikipedia.org/wiki/Image_sensor_format

Not likely that it would cause difference. Here is a little comparison of effects: Let's suppose that we have rather decent seeing at 1.5" FWMH and it affects both wavelengths the same (500nm and 650nm). Both are on the same mount that is decent in performance for such a focal length, and guides with 0.5" RMS error. What are expected FWHM of stars for each? 500nm: ~2.3" 650nm: ~2.52" Although there is something like 30% or more difference in the size of airy disk, given that convolution of PSFs (seeing, airy and guide error) adds FWHM as square root of sum of squares, and airy disk being the smallest of the three, result will be much less in total FWHM - in this case, there will be increase of about 9.5%. Once we take into account seeing impact vs wavelength, we should end up with roughly the same FWHM, or even small Ha having a small edge. This is of course for perfect aperture. Any aberrations will have blurring effect that will raise FWHM.

Yes, quite close to what it should be and you are right about green cast in center - lowering green component will create center of the galaxy more yellow like (red+green = yellow).

You are not far off ... Colors are a bit washed out due to the way you processed the image, but in principle it is fairly close to what it should look like. Don't be swayed by majority of renditions of this galaxy found online - most are just too saturated and generally not quite correct. Color renditions like these: are overly saturated and blue is pushed far more then it should be. On the other hand, renditions like these are closer to the real thing: Look at Hubble rendition of central part of this galaxy: Blue is rather scarce in outer arms, and mixed with Ha regions so its more "purplish" than pure blue, core is deep yellow / orange surrounded by ring of gas and Ha regions - which have deep red / brown look. Here is one of mine images where I was playing with getting correct color for this target:

There is a simpler test to perform rather than doing Roddier test - not that it is complicated, but will require a bit more processing. Try imaging without field flattener. Maybe optics of the scope is fine, and field flattener is poorly corrected at red part of the spectrum. You will have smaller usable field for your test, but stars close to optical axis should be a good indication - they will be sharp.

Here is a brief overview of how it is done, but there is much nicer explanation in document accompanying the software that is used: It would be best if you have access to NB filters - that way you can do exact measurement in certain wavelengths. I have OIII, Ha and also Baader solar continuum filter that is around 530nm or so, but have not done measurement with those. You can also do it with regular RGB filters but results will not be as precise - you will get a sort of "integrated" strehl ratio over respective bands. Same happens with OSC cameras. You will need WinRoddier 3.0 software (or any more recent version, last time I did this, it was with version 3.0). You will also need some sort of application for fast capture - like planetary imaging. Sharpcap will serve this purpose. Last you will need planetary stacking software - AS!3 for example. Measurement is done by recording defocused star pattern in particular wavelength (or filter). You should select fairly bright star - like mag 2-3, and high up in the sky to minimize seeing effects. Night of good seeing will give you more precision in your results (similar to planetary imaging). If you have OSC - you record all three bands at the same time, then split channels later and examine each R, G and B recordings. You proceed by doing short videos of about 1 to 2 minutes. You need one of in focus pattern and one of out focus pattern. There is method to calculate what diameter of defocused star pattern needs to be in pixels - depending on focal length of scope and size of pixels on camera, it is included as separate small piece of software and it is described in how to document / manual. When you finish your movies and calibrate them - you stack them in AS!3. It is important that you don't change intensity of image in any way, so avoid auto scaling of intensity and such. Also - no sharpening must be applied to image. Once you have your stacked images prepared you load them in WinRoddier, set wavelength (for NB filters - pick proper wavelength, and for RGB use wavelength in center of the band for each color). Software does the rest and prepares wavefront images, Zernike polynomials / coefficients and calculates strehl / star profile - look at images that I attached it is screen capture from WinRoddier software. This is process in the nutshell, for more detailed instructions - read the "manual" (or rather document describing workflow). All needed files (both program executables and manuals) can be obtained via Roddier yahoo group. You need to join the group (it might need permission from group maintainer/admin if I remember correctly - it took a day for me if I remember correctly). https://groups.yahoo.com/neo/groups/roddier/info Once you have joined the group look under Files / WinRoddier Ver. 3.0 (Latest)--Apps and User Manuals folder for pretty much everything you need. If you want to check out manuals and "how to" before joining the group - it looks like these are available on different urls on the net, so here are some to get you started: http://www.compubuild.com/astro/download/Roddier_Ver.3.0_Quick-Start_Guide.pdf http://www.compubuild.com/astro/download/New_WinRoddier_User_Manual.pdf

Ah yes - if filter causes blur when in front of focal point (converging light beam close to focus point) but not when placed between eye and eyepiece - than it is very poor quality filter in terms of parallelism of surfaces and polish (general optical quality). In front of your eye, image is already amplified and small aberrations on amplified image will not be resolved by your eye. In converging light cone before eyepiece any aberrations will be amplified by eyepiece (same as image) - and things will go blurry if you don't have decent optical quality filters.

Ususally I was expecting to have a cleaner Halpha channel than OIII, but it's the opposite. I also know that asiderom the optical color correction, in green, you get a better resolution and even better in blue than in red. I'm not going to question how good collimation is on this particular scope, but there might be an issue with correction. Although from your quote we can see that "The colors are very well balanced" - I'm not sure what it means. Triplets are tricky beasts with regards to collimation and proper lens spacing - and I for sure, have no clue about how it is properly done. What I do know is that there is no single strehl ratio for such a scope. If single strehl is quoted - then it is probably in single wavelength - usually around 550nm (or similar - peak of visual sensitivity in scotopic vision I think). Corrections in other wavelengths might and usually are different. Here is an example of strehl vs wavelength graph: This is result for a doublet scope, and while around 580nm it approaches respectable 98% strehl, at Ha this particular scope is going to have strehl around 65% or so. I "tested" my own TS80mm F/6 triplet with Roddier analysis - nothing fancy, RGB image split, and I for example got following results per "band": Blue was around 80% (let's say average), Green around 94% while Red was at around 98%. Such scope would have opposite characteristics - very sharp Ha, while OIII would be softer. Have a look at this post to see results of test: However, not sure if this is the cause of your issues with star bloat in Ha. No, actually, I'm not seeing it. I'm seeing what you are seeing and thinking that best focus position for small stars is as you said somewhere around 32407, but this is just a visual thing. You have no HFR for these stars, and because they are so dim - when not in perfect focus they will be even more dim and their "wings" (wings of star profile) will be below read noise. If you look carefully, you will actually be able to tell that it is spread around. it is very faint, but can be seen. I'll make a screen shot to point it out. Here it is - focus position 32407: Now the same image - ridiculous level of stretch - just look at noise distribution: Noise is more dense in rather large circle around central "tight" points - and this is also light from those stars but very low in intensity due to less than perfect focus, and being at the level of surrounding noise or below it, so it can't be easily spotted. Also compare how much the size of disk of large star increased (it is already stretched) and how much of those two tiny stars.

Not sure what you are finding to be an issue with this? Subs are certainly not over cooked, and stack looks just fine with regards to this (and pretty much everything else). There are some issues with the image, but nothing to do with camera or data - there is quite a bit of aberrations, like you said probably issues with focusing and spacing, maybe a bit of tilt - nothing that can't be sorted out. There is some scatter, and again this is not down to camera or the data - probably transparency issues, a bit more moisture in the air that creates scatter and glow around bright stars (at least with M31 that I examined). Here is quick & dirty stretch on M31 without any soft of additional processing:

Yes, for dark optimization to work - you need to have proper bias, and CMOS sensors don't have proper bias, so it's best to avoid dark optimization as it will cause issues - like you've shown.

Could be many reasons, but let's list a few: 1. changing seeing conditions between OIII, Ha/SII - you could analyze this maybe by examining what time of the night did you do each set, was it on same or successive nights and what was guiding like for each session. If OIII was first or last in single night - it is more likely that seeing had something to do with it, if it is in the middle of the night - it is still possible but less likely. If each was taken on a separate night - highly likely that it was the seeing. Poorer guide RMS often means that it was either the seeing or maybe wind? 2. Different signal levels will cause different level of "auto stretch" / "auto develop". If you want to see if stars are similar in size (or different), you should check actual FWHM of respective stars to see change in "bloat". 3. It might be that optics + flattener is better corrected in green than it is in red. I doubt that you would see this from scope alone, but with flattener - it might be an issue. 4. In principle it could also be due to filters, but I don't think Baader filters are to blame here. Many people use them and no one (including me) reported this. In general it is other way around - Ha/SII tends to be sharper than OIII because longer wavelengths are less impacted by seeing than shorter ones.

Maybe simplest way to try it is - to try it Read voltage from your mains adapter, and see how much amperage it is supposed to give (mine is something like 19.5V and 4.8A). You don't need as much amperage - can be a bit less, because these mains adapters are designed to both power laptop in work and charge at the same time - hopefully it won't do charging of the battery, just powering laptop. See if your step up converter can deliver enough power and set it to proper voltage that you read off mains adapter. Do be very careful about plug polarity - measure it on your current mains adapter. Get another plug like that and make a lead with it from step up (of course, again minding correct polarity). Then plug laptop into battery instead of mains and see if it will work. You can do it via 12V DC - > 240V AC and then use regular adapter. This way it will try to recharge your battery when it drops, so maybe remove laptop battery, or tell laptop in power management not to recharge battery (I don't even know if there is option for that) Total losses are unlikely to be better than something like 15% and can be as bad as 40% - depends on efficiency of converters. But let's use 20% losses. Mind you that using step up and doing 12V -> ~18V (or what ever lap top needs) will have similar performance, but might be smaller in size and easier for DIY. Laptop won't draw max current all the time, but it will certainly need something like 35-40W in normal working mode (no heavy processing or such). This in turn means about 50W load on battery, and at 12V it is about 4A. 4A from 75Ah battery in principle should be able to power laptop alone for about a 18h.. On the other hand, we can look at it like this: - mount power - 2A? - camera cooling - 2A? - laptop - 4A? - gadgets (flat panel, motor focuser, .... anything that uses just a bit of power - and not continuously) - this we won't count as others won't have continuous draw at max rating so there will be plenty of power to spare for these devices So we have something like 8A of draw (although not continuously). We want to be able to run 8hours in the field (should be enough for complete session together with setup and everything) - that is total of 64Ah - anything above 70Ah should be enough (providing it is deep cycle).

At the moment - just mains power Still don't have portable rig. However, I've found that for Dell laptops, if you provide needed voltage and current on adapter plug - it will work but will not charge (which is good - don't need to drain current from main battery to recharge laptop). I've found very cheap step up/step down DC/DC transformer - just need to try it out. It provides around 3A of current (my current charger is something like 4.8A - but it needs more power in order to charge laptop). I'm fairly confident that laptop will run on 19.5V / 3A (that is almost 60W of power - should be enough for just running computer). And need 7.4mm laptop power plug - don't want to cut into laptop mains adapter that I already have.

Here is some info on this barlow: - focal length of this barlow is 62.9mm - for magnification factor of x2.7 you need to place it 105mm "from the center of the last lens", or another way to put it - from "highest" point on the surface of the last lens (that being the center of lens of course). You can actually calculate required distance by using barlow formula: Magnification = 1 + D/F Where D is distance from the lens and F is focal length of the lens. If you plug in the numbers - you can work out distance from the "center" of the lens assembly (principal point)- not to be confused with center of last lens - it is "middle" of the lens assembly rather than point on surface of the lens. 2.7 = 1+D/F => 1.7 = D/F => D = 1.7*F 1.7 * 62.9 = 106.93mm This agrees well, so principal point to focal point is 106.93mm - that puts principal point about 1.93mm "inside" last lens. Anyway - here you have it. It should be about 104.1mm from shoulder because it is about 1.1mm "in front of the last lens". If you place your sensor further or closer - you will get different magnification - handy for adjusting sampling rate, however nothing to do with sensor size.

Wondered the same myself for my dell laptop. Ideally I'd like something like a car charger but without charging capability - just powering laptop after battery is low. Issue with dell is that it won't boot if charger is not "genuine" (there is some sort of identification protocol between laptop and charger). Another option that I considered is "dummy" battery - just empty battery slot without actual battery inside - connection to external power tank and appropriate voltage, but then again - battery is sort of "smart" battery - it reports level of charge and what not and I don't think simple connection to proper voltage will work.

For smaller sensors you don't need flattener. You might want one for APS-C sized sensor (I'm not sure). RCs have rather flat field, but not fully flat - for large sensors they need flattener. I use RC8" with ASI1600 without flattener and field is good on that size (21mm or so diagonal). This scope has 1370mm FL and with 460ex this will give you 0.68"/px - and that is rather high sampling rate and you will be oversampling natively. There are two things that you can do - add FF/FR, or bin. I think that you should bin x2 - that will give you 1.37"/px - and that should be rather good for HEQ5 and regular guiding results (something like 0.8" RMS). When you bin x2 it's like having twice shorter focal length so you will effectively have "F/4.5" scope - which will be fast enough (F/ratio and "speed" of scope is not measure of how fast you will take images - it's aperture at resolution, and in this case you will be using 6" at 1.37"/px - which will be quite fast). Here is an example for you - this is two hours of lum in rather heavy LP (mag 18.5 skies) - 8" scope (F/8 natively - also RC but 8") at ~1"/px: I would not call that slow ... You can "speed up your scope" with use of FF/FR, and a good one would be Riccardi x0.75 FF/FR - but that would give you 0.91"/px - and I think you will still oversample on this resolution. Binning with FF/FR will give you 1.82"/px - and that is going to be rather low resolution - comparable with 80ED - so you will gain nothing (apart from speed, because of almost x4 light gathering for same sampling rate).

Maybe this: https://www.rothervalleyoptics.co.uk/altair-astro-6-f9-ritchey-chretien-astrograph-telescope.html

Ah sorry I thought you were asking about IR pass filter (did not read what you've written properly). No, IR cut will not be much of a use for guiding. Even if stars are a bit bloated it does not matter for guiding. Anyway, you can use one of those adapters if you still want to try some sort of filtering on your guide scope (either IR/UV cut or IR pass filter).

In principle it might. Longer the wavelength of light - less bending there is, so in IR you should be affected by seeing the least. You will loose some of camera sensitivity, but that should not be an issue with longer guide exposures. You don't need any special T2 size filter - regular 1.25" filter is enough, you only need an adapter like this: https://www.firstlightoptics.com/zwo-filters/zwo-t2-to-125-filter-holder.html In fact, you might have received one with your camera already (I know I did for one of my ZWO cameras).

Depends on a cam. I did some 60s exposures with ASI185 and it worked to some extent. I don't remember going longer than that.

Yes, there is residual amp glow. Could you upload this light and set of darks that you used to calibrate it for inspection? There might be something that is causing this that could be solved?

Fancy an open cluster? M29 is nicely positioned and quite compact - framed nicely in your FOV. Globular - M15. Nebula - Maybe Crescent nebula? It is nicely framed. Cocoon is also good fit Galaxy - NGC7331 is always a nice target.

I did read once a review of this unit, and author did get tighter stars by using it, but can't remember what mount it was on. Will try to find it again and post a link Yes, you are right that some mounts are rather expensive, but why consider GM2000 and not something like Mesu 200? EQ8 + AO device will place you in Mesu 200 price range, and I have sneaky suspicion that Mesu 200 will deliver at least as good performance if not better without complexity of running an AO unit.