Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

Whirlwind

Members
  • Posts

    537
  • Joined

  • Last visited

Everything posted by Whirlwind

  1. You should be able to test this simply indoors by just taking exposures of the same length/temp and see what the darks look like and then undertake a meridian flip. That should at least determine whether it is something electronic before and after. I would agree though that it is probably some form of external factor that you are looking at. Were there any lights in the vicinity that might be impacted that might get into the telescope at certain angles?
  2. As a few thoughts. It might be worth mentioning Echelle spectrographs as well - or more importantly that these should be avoided to start with (they are generally expensive) but with "more money than sense" might be risked because of the potential higher resolution. It might be worth mentioning that higher resolution (greater number of lines/mm etc) will give more detailed spectra but at the cost of more imaging time as the light is spread out more. Also flats are needed if you want to completely flux calibrate your spectra. The flat corrects for the response of the optical system. In principle you can do this with the standard but relies on getting the standard spectrum on exactly the same pixel location as the target of object but that is nigh impossible. It's better to flat this out and then apply the standard calibration (strictly speaking there should be both a normal flat and a sky flat but generally you can get away with just the former!). If you are just looking at radial velocity changes etc, just a normalisation is fine. But to get temperatures you should fully flat calibrate the image. Yeah don't touch the grating, breath on it try and wipe it or otherwise anyway misuse it. You can use a filter to block out second order effects
  3. Sorry if I wasn't clear. Yes I know this, but was working on Danon's focal length aspirations of around 400mm to be able to the fit the targets of choice into the object. Hence the suggestion of the RASA 8" which is a similar focal length. I don't like the focal ratio 'myth' as it gives a false impression that you are gaining extra signal for the same aperture which is not what is happening - it's just how much you are spreading the light out by. By simply binning the camera to a similar resolution for a larger aperture telescope (that has a base longer focal length) would give you the same effect as the same aperture but at a shorter focal length at the 1x1 pixel size. In this case an 200mm F2 would capture lots more photons than an 80mm F5 even though they are the same focal length. You could get the same result by getting an 8"Edge F10 and binning by a, albeit, substantial amount. The disadvantage in the latter is that your field of view is small.
  4. Realistically if you want speed then the largest aperture is the way to go as it will collect more photons per pixel (for the same camera). You could get something like the RASA 8" with a ASI1600 which would really help maximise your imaging if you are limited by a few days per month. You would just need a filter drawer (or choose a colour CMOS).
  5. There's a lot of technical bits in all the responses but honestly I wouldn't worry too much about it all. You will having to learn so much to start with that in itself will be a challenge. You can make excellent images from most setups (realistically your mount is the most important part). You really want something that is relatively forgiving at this stage. That means a short focal length and larger pixels as it will mean tracking errors, polar alignment errors etc show up more slowly. Then you need to consider how you are going to guide the telescope. That's another smaller guide camera and either a small finder telescope or an off axis guider. Also with a mono camera you need filters and a filter wheel. The most important thing though is what you want to image. Galaxies/planetary nebulae tend to be small (except a few) which means smaller pixels, longer focal length telescope. Emission nebulae tend to be larger and need shorter focal length, larger pixel camera which would be just fine. The 8300 class cameras are just fine for imaging, they are a good workhorse. Their advantage is that CCDs tend to calibrate easier but are noisier (generally) but the Sony (460 etc) ones are relatively low noise. CMOS needs a bit more consideration on the calibration frames because of amp glow and walking floor noise, plus they tend to have smaller pixels needing better guiding. However CMOS tend to work better with shorter but many frames that puts less onus on guiding compared to CCD which tends to need more and longer images. So each option has its strengths and weaknesses, however from a beginners perspective they are all a challenge whichever way you look at it. Honestly from a beginners perspective I'd go with a CCD simply because there are tens of years of experience on these cameras and you will always find help. CMOS are still relatively new to the field and I still think people are working out how to get the best out of them. Therefore guidance might be a bit less on how to resolve certain issues.
  6. I would suggest cabling as well. The feature looks like something is increasingly resisting motion until it snaps back. That would suggest something is getting caught until such point as it is stretched to far and whatever is resisting it slips over and it releases the pressure. I'm thinking maybe the spiral wrap is snagging on something (e.g. polar scope cover etc) and it stretches until it is pulled so taught that it slips against whatever is holding it back.
  7. If you have a relatively large amount of backfocus to play with a thin helical focuser between the corrector and the imaging set up can work wonders...
  8. A better term for these would "active" optics rather than adaptive optics. They won't correct for seeing in the same way that scientific adaptive optics will do. However, they can be useful for fast guiding where that might be useful such as mirror movement, flexure etc or where you might have a mount that has rapid error changes that don't respond well to corrections (e.g. lots of backlash). This is because you only have small amount of glass to move rather than the whole mount. To get the ultrafast adjustments you do need a very bright guide star though which isn't always practical on longer focal telescopes. The SX AO does have a USB connection though. They tend not to update their images very frequently.
  9. That could probably be tested as you should see less difference at larger apertures and if you pick different comparison stars. To get such a discontinuity you need something to change the relative flux between the objects so that the apertures are no longer suitable to capture equivalent flux between pre and post flip (perhaps because one star is now no longer circular). If you expand the aperture used then this effect should reduce because you start capturing the flux that has been spread out because of 'some' movement. If it is, say, due to tilt then selecting comparison stars closer to the target object should also reduce this effect as all these stars will have similar optical defects. If none of these resolve the issue then it may not be due to the optical train and perhaps to do with the camera. If you don't place the star on exactly the same position then if there are any discontinuities on the camera then these would result in an absolute difference in your photometry. This is why for scientific work most people recommend higher grade cameras (although that's no protection against later discontinuities arising). It's very common even in professional set ups to see discontinuities where there is movement of the object onto another areas of the CCD and using differential photometry.
  10. Ah OK, so if you aren't saving the files in a certain format you might never get to see that option until you've entered your reference details. So to return your issue when you create your light curve do you determine the differential magnitudes separately pre- and post- flip or all at the same time. It's actually not that uncommon where a star has not been relocated back onto the same location to get some discontinuity. When you stated that every star has the same discontinuity is it the same difference in differential magnitude in each object?
  11. Sorry, I'm still unclear on how this is done. I can only see the differential magnitudes as an option. I guess this is selective blindness, where do you get to enter the magnitudes specifically? I'm just wondering how this is done. In particular do you state this in two separate files before and after the flip?
  12. On an aside how did you get the magnitudes out of Muniwin. I thought it just gave you relative magntiudes? I've never been able to see a function where you can astrometrically link your stars?
  13. I think the difference in benefit between mono and osc is more pronounced that that. If we assume some relatively arbitrary numbers:- Each pixel produces one photon per minute from non filtered (L) light (i.e. 60 per hour) Each filter (including the OSC coating) reduces the photons received at a pixel by a third The CCD is made up of 4 pixels As such if you were shooting 4 Hrs of OSC then the number of photons you would capture would be:- photons x number of hours x number of pixels x filter reduction factor = 60 x 4 x 4 x 1/3 = 320 photons captured For LRGB you have to do the above for each channel each being 1 hour in length L = 60 x 1 x 4 x 1 (no filter) = 240 photons RGB = 60 x 3 x 4 x 1/3 = 240 photons Total = 480 photons Factor difference = 480/320 = 1.5 So you capture at least 1.5 times more photons in the same time. The more you focus on L of the image the more pronounced this becomes so 2 Hrs Lum and 2 Hrs RGB would be 640 / 320 = double the photons captured. This would hence reinforce your argument that for faint objects mono is the way to go. This uses basic assumptions that camera sensitivity is the same in the same bands. This is generally an incorrect assumption as the coated OSC are substantially less sensitive over the total band colour band compared to the same filters (which usually have a 90 - 98% transmission range). However filters generally are much more specific in the wavelengths they pass (for example looking at the OSC above the colours overlap. So I'm balancing this out even though in reality you have red light in the green osc pixel. It assumes that the cut off of the L filters is similar to that of the osc coating. Generally for refractors this is correct as we cut at about 400nm - 700nm as lenses aren't well corrected after this point. However for reflector system (e.g. RC) where this isn't necessary and you can happily use a clear filter then there the mono can capture a lot more flux from outside this range. As such I'd argue that 1.5x might be the lower end of how much data you might be collecting.
  14. I've always this thought this argument depends on what you want to image and how often. OSC cameras definitely have benefits when you only have the opportunity relatively rarely to image, need to setup and strip down everything all the time and so forth. In these cases OSC helps because you get all the data at once and if clouds appear earlier than forecast then you still have data this is useable (and aren't stuck with the R and G but not the B! If you want to focus on galaxies then OSC can also work well (and works even better in non light polluted areas) On the other hand if you are looking at narrowband targets as your primary dish of the day then mono is the way to go as you can be much more selective as to how much data you want from each band and that some narrowband will overlap (SII Halpha will both trigger the red pixels in an OSC etc).
  15. It comes down to what halos are and what causes them. Baader are correct in this statement to some extent, although the commentary on professional telescopes also having halos isn't really relevant (professional telescope filters are set for maximising throughput not pictures). Halos are in effect defocussed images of the star. To get a halo off a filter you need it to reflect light from a source. This could be, for example light reflecting off the cover slip back on to the filter that then gets re-reflected back towards the CCD. The light path for this is much longer than the focal length and hence by the time the light gets to the CCD it is way out of focus (hence the halo). Alternatively the light may reflect off the filter onto a reducer/flattener glass and then be reflected back towards the CCD. The same effect is seen. A cover slip that transmits almost 100% of the light and has a very effective anti reflective coating hence shouldn't have halo issues with *any* filter as nothing is being reflected back on to the filter. On the other hand a filter with extremely effective anti-reflective coating would not reflect light as well and prevent the halos (e.g. astrodon). If both have anti reflection issues then you will get halos. As such it is not impossible that the some combinations work and some don't with any filter. I'm not sure of the set up here but it is some form of reflector so if there is a flattener/reducer/coma corrector in the way you could try removing this and seeing if you still have the halos. If they are still there then the chances the reflection is between the CCD cover slip and the filter. If it goes away then you may find that a flattener/reducer/coma corrector with excellent AR properties (or possibly longer back focus to spread the light so far that it is not visible) may solve the problem. If it is between the cover slip and the filter then you probably will need new filters or a camera with better anti-reflective characteristics (which might be cheaper given the price of astrodons!)
  16. You should consider the Sitech more as a mount controller than a GOTO system. You are correct in that is doesn't provide a hand controller option where you can slew to 'XX' target and you would need a computer for this (not sure whether it has wifi so you can run from an ipad etc). In fact on the old site they recommended the Argo Navis system (of which I have no knowledge). So if you want to have a local hand pad you need to factor this cost in (it's not excessive especially when you are looking at the 10Micron!). One thing to note is I can't see an autoguide input on the Sitech I just an Aux and RS232 port. Might be worth checking. Realistically the cost of the difference between the Sitech 1 and Sitech II is negligible compared to savings against the 10Micron so you might as ask whether it is an upgrade option?
  17. It was used to be called the OGEM mount because they were intending to use a different operating system called FreeGO2 but their testing in Spain showed it had some limitations to about +/-0.5". As such they redesigned it to use the Sitech controller which also meant a redesign to the mechanism so that is a fully friction surface - they call it a fully kinematic friction drive which apparently the Mesu is not and hence why might not be breaking any patents. 100kg is the instrument weight but the recommended payload is 75kg (obviously that depends on your moment as well). Note that plots are non-encoder guided version of the mount as well which is something to keep in mind (encoders are an upgrade). You can also upgrade to a hardened drive which they only generally recommend in areas with very high humidity (by the sea) or with lots of potential sharp, hard dusts (deserts etc). The price I think is a bit higher now than previously because of the improvements. They held the prices for the early birds to reward the patience. As for communication I think Mark freely admits he has not much clue when it comes to advertising. I think he prefers to be seen as a perfectionist engineer first. However, when communicating directly he is more than helpful. He's just used to dealing with astronomers more than the consumer. Astronomers are both easier and harder to get on with. They want everything to be perfect but will wait to get it! They are the type of company / person that it isn't very good to ask a generic question but will give you reams of detail if you have shown more thought in what you need.
  18. Some of the concepts in Astronomy and the maths used can still be 'basic' in its application. For example exoplanet work uses very basic principles of Newtons and Kepler's laws. You could try something like A student's guide to the mathematics of astronomy which has the basic concepts but is relatively calculus light and shows how you can measure distance by a very simplistic method (but is what is used by Gaia). The real trick with Astronomy is making sure you minimise your noise in the data and that's where a lot of fancy maths comes into play (assuming you aren't considering extreme physics objects).
  19. My understanding is that there are still two configurations as was originally advertised. You can choose to have either and is easily upgradable later to encoders if you want/need.
  20. The astronomical way of looking at this is to use your local sidereal time (LST), which to note is NOT your local time. Your LST is the RA at any given moment that is crossing the meridian (south in the northern hemisphere; north in the southern hemisphere). You can find your LST in sky safari pro under date & time settings tab under advanced. Therefore any object is highest when the RA of the object equals the LST. You can simply find out how long it will be until (or how long after) an object has passed this point by taking the LST and minus the RA of the object. So at the time of this post my LST is about 3hrs 30. The RA of the Saturn Nebula is 21hr 05. 21 - 3.5 = -17.5 hrs. In effect you are 17.5 hours from the point that the Saturn Nebula will again be highest in the sky. Alternatively by considering a 24 hr timeframe you are 6.5 hrs since it last passed the meridian. This is called the 'hour angle' which tells you how long until the object crosses the meridian or after; in this case your hour angle (HA) would be +6.5. If you take another case when your LST is 19.5 hrs then it would be 19.5 - 21.0 = -1.5 hrs. In this case your HA = -1.5hrs (i.e. you need to wait another 1.5 hrs until it is at its highest). To determine when an object would cross the meridian at your local midnight you need to consider when RA = 0 at local midnight. This happens on the 21st September (RA=12 hrs on 21st March). Now we know there are 24 hrs on the RA scale and roughly we have 12 equal months. That means for every month this equates to about 2 hours. Hence for every month after 21st September the RA that will be at the meridian at local midnight will have progressed 2 hours (so on 21st October the RA at midnight would be approximately 02:00:00*. On 21st August your RA at local midnight would be 2 hours earlier (i.e. approximately RA=22:00:00). Now we know the Saturn Nebula has an RA of 21hrs. That equates to about 1.5 months before 21st September. Therefore you should find that the highest point at local midnight is around 6th August. This is different to lenscap's time because of BST, his statement assumes local midnight is at 12am, but its not, its actually about 1am in the UK because BST is Universal Time +1 hour. I say 'about' because your local midnight will vary by a few minutes dependent on how far east or west of Greenwich your are. Generally you can use Greenwich in the UK as most places (barring perhaps Isles of Scilly) are close enough to Greenwich not to worry about this. You can see a much greater effect when you go to the Canary Islands. Their Local time is Spanish time but they are good deal further west and hence mean local time is 18 degrees or so west of this meaning astronomical cycles can happen about an hour later than your expect them to (e.g. setting /rising of the sun). Hence you can easily work out when *any* object will peak at midnight just by considering the RA of the object 0 Hrs RA - Late September 1 Hrs RA - Early October 2 Hrs RA - Late October 3 Hrs RA - Early November 4 Hrs RA - Late November 5 Hrs RA - Early December 6 Hrs RA - Late December 7 Hrs RA - Early January 8 Hrs RA - Late January 9 Hrs RA - Early February 10 Hrs RA - Late February 11 Hrs RA - Early March 12 Hrs RA - Late March 13 Hrs RA - Early April 14 Hrs RA - Late April 15 Hrs RA - Early May 16 Hrs RA - Late May 17 Hrs RA - Early June 18 Hrs RA - Late June 19 Hrs RA - Early July 20 hrs RA - Late July 21 Hrs RA - Early August 22 Hrs RA - Late August 23 Hrs RA - Early September *Note this isn't quite right because months aren't split equally across the year but is a close enough approximation
  21. So I've been keeping an eye on this mount for a while and they have recently posted some updates on the mount. The reason for the additional delay is that they have moved to the Sitech Servo II controller as the FreeGo2 wasn't performing to expectations on their test mount they had at E-Eye (with OS RH200). This has also meant they had to change some of the design so that everything works on friction surfaces to the motor. They have sent out a movie of the mount (as attached) they have been testing (note the rough finish is because it is a test version). According to the update I was sent they are now in the final stages of manufacturing to accommodate these changes. Thought this might be useful for anyone wondering about the mount. Edit does anyone know how I can resize this movie so it's not so huge? Thanks Pittman.mp4
  22. The TOA image is better I think when zoomed further in to look at the specific detail. However at the full image scale it really is barely perceptible. You are spreading the flux out in the TOA by a much greater margin so really to let the TOA really shine the total exposure should be longer. Both are great images though. The square shaped stars are from the CMOS microlens. You have a classic diffraction pattern around the stars which is making them look square. The small "/pixel in the TOA is likely masking this effect because each stars light is spread out over many more pixels.
  23. I'm guessing that was Sarah. Cool and all round good and supportive person.
  24. Top one. The colours look more natural to my eye - bottom one has a purplish cast.
  25. It's largely though to beat the weather/ligh pollution. If you have access to dark skies with regular periods of no clouds then that's great. But how is someone in the UK (and other places) able to produce the same quality images that other amateurs can create simply by the luck of where one or the other lives. The only real method is then some form of remote hosting (or move to another country which isn't necessarily viable). I do appreciate the loss of technical challenge but then it gets to the point when someone may have the Mach1, a QSI and high quality refractor and imaging then becomes limited not by the equipment which can be set up fairly accurately to the same set up each and every time (and hence is no challenge) but simply the lack of clear skies.
×
×
  • 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.