Forum Replies Created
-
AuthorPosts
-
Tim Haymes
ParticipantJust a thought, that the 3.1 socket looks different to 3.0. Jeremy, you might like to check this for yourself on the machine you buy and if you need some sort of plug adapter to run the USB2 camera on USB 3.1. I dont have experience of this, i was checking out the specs after reading your question. I expect you will have 3.0 and 3.1 on a new machine.
Tim Haymes
ParticipantThe eagle eyed will notice the time stamp in the upper left of the image. This is because the camera was QHY174m-GPS (12/16bit) operated in SharpCap 3,2. and is not the WATEC 910HX video camera which the label indicates. I thought i should correct any confusion this might cause.
Tim Haymes
ParticipantGary, I was using the BL Lac field to test some video cameras on Aug 6th. I noticed BL was quite “obvious” but not being a strict VS observer the significance passed me by. Yes i estimate mag 13. Here is a frame taken from the video:
Pls note, there are hot pixels in the image which is uncorrected. The frame limit is about 15.5Tim Haymes
ParticipantSorry there is problem editing my message above. I will make contact via email
Basically the FITTING does not work. Although anaconda installation looks OKIt turns out that my data is causing a problem in W7 and W10 installations, while the WASP-12b test data is OK.
I hope to try another transit with a different camera.
Tim
Tim Haymes
ParticipantIve checked my installation I think my problem is different. The fact i can get to a preliminary light curve suggest the install is OK. When I type at the anaconda prompt: echo %PATH% the path includes C:Anaconda3. So im guessing that’s correct (It is the correct dir although not the one in the ARIEL notes, and python is there also). The problem I have in the work flow, is the FITTING routine. I get this message displayed for 1 second, then nothing. What does this imply?
Tim Haymes
ParticipantThanks for the correspondence – yes I also encounter this problem. I will check the installation in the light of what has been discussed. I have a data set for Qatar-1b that could be submitted if HOPS completes successfully. I thought it was caused by poor data quality. I will investigate further.
Tim Haymes
ParticipantI imaged the galaxy through thin cloud – on Aug 9th at 2100UT. Despite the poor transparency the stacked subs indicate the transient at about 16.5 mag. (C11 at f5.5, QHY174m)
Tim
21 June 2020 at 10:22 am in reply to: Observer’s Challenge – Occultation of Venus by the Moon, June 19 #582668Tim Haymes
ParticipantWhat wonderful images of the event – thanks for sharing.
Tim Haymes
ParticipantI had to look up how this could have been observed, as there was no solar eclipse. Appears Young’s slits were in use, and i had the pleasure of a tour at the Late Commander H Hatfield’s observatory which employed this method in the 1970/80s. My suggestion is that it could be caused by the Doppler shift making a prom appear fainter and darker perhaps.
http://articles.adsabs.harvard.edu//full/2011JBAA..121…54M/0000054.000.html
9 June 2020 at 10:58 am in reply to: Observer’s Challenge – Occultation of Venus by the Moon, June 19 #582628Tim Haymes
ParticipantApologies that this event is not listed on the BAA Handbook Lunar Occ page, it should have been. A prediction setting that i used was incorrect. (Fixed now!). The omission was only noticed after publication.
I will be using an IR pass filter for imaging. For my mobile goto telescope it should be possible to set up the alignment with stars before sunrise. I might do that and keep the rig running. Early acquisition of Venus would be a bonus.
Tim Haymes
ParticipantThanks Nick/All – this is encouraging. I will continue investigations with CMOS. My test images were not taken under best conditions. I hope the image above of PQ And (one of many) illustrates the image profile im using to learn HOPS. Not ideal but it works. It isnt saturated according to AstoArt
Tim
Tim Haymes
ParticipantHere goes. Ah! it seem to take a long time before its available to insert. I may have made a second comment…sorry
Tim Haymes
ParticipantPQ was at alt 8deg, and managed a sequence of FITS from 1.30 to 3 am BST. BUT I dont know what to do with the data. However i have a memamsured image giving a R mag of 10.5 using UCAC4. I dont know how one gets V mag with a filter. Where do you get the ensemble photometry data for V (or G)? My image is attached (single image in Astrometrica).. I hope
The browser is not playing ball.23 February 2020 at 12:14 pm in reply to: Occultation of (83) Beatrix and star TYC 1945-00656-1, 19 February 2020 #582048Tim Haymes
ParticipantThere were some other observers in England. I was just south of the path in Oxfordshire and Phil Denyer in N London who was on a close chord to myself. We observed no event by video. Simon Kidd north of Stevenage recorded a long positive of 8 sec as did a nearby colleague of his with 9 sec. (durations are preliminary)
Loughborough was expected to be in the shadow path, so it was a close appulse.
Tim
Tim Haymes
ParticipantI have measured it at 12.7 (unfiltered CCD) using the AAVSO chart (X25129DUM) and AstroArt 5. The telescope was the CHI-1 (Chile) on the Telescope Live network (Planewave CDK24, 60sec) – date 2020-02-03.360
Tim Haymes
ParticipantThanks for your input gentlemen. Yes, the observing slit and zenith view are on my query list. Also the view to the Southern horizon is a bit limited without some additional design work inside. I have a good horizon, and would like to make full use of it.
I now have an invite to visit a member’s 2.7m dome. The Scopedome 3m is also on my short list.
Thanks again for your general comments.
Tim
Tim Haymes
ParticipantI grabbed some frames last night between clouds and found the asteroid with 200mm F2,8 lens. Image show the rapid motion over about 20mins. Ive added it to my album on this site. Thanks to David and Nick for the thread on this interesting NEO.
Tim Haymes
ParticipantI saw one demonstrated at the Amateur Astronomy Centre, Todmorden. Visitors were able to take pictures of the moon easily through their 16″ Meade – Thanks to Peter Drew who invited me over.
Tim Haymes
ParticipantThank you Grant
UT: 2019-07-26, 0007Hr 53s RA 19h 44m 27s, DEC -06d 53′ 54″ (J2000)
rate of motion: 1’arc/min, magnitude 10 to 13 erraticTim Haymes
ParticipantThanks for the tip Grant. I need to ask around to see who has a copy, and who might offer to solve it for me.
I did download a command line program IDsat, but it assumes i know the ID. And the data input was hard going. So looking for a more user friendly solution.
Cheers, Tim
-
AuthorPosts