As part of PHY241, you will be expected to complete a simple observing project using the 16-inch telescope on the roof of the Hicks Building. This project is designed to give you basic hands-on experience of astronomical observing and data reduction, and can be completed in a few hours of telescope time. The observing must be done in groups of three students, so please find others interested in doing the same project as you. If you can't find a group to work with, I shall be happy to recommend some options. You must notify me by email of your final choice of partners by the deadline at the start of week 2: Monday, 9 October 2017. If you have not chosen a group by then, you shall be assigned to one by me!
There are 3 aspects to the observing project:
Planning: Well before your scheduled observing run, you must discuss with me or Paul Kerry (E26): which objects to observe, what time of night to observe, what filters you require, what sequence of exposures you require, etc. You will find the specifications of the Hicks Observatory useful in your planning. You will need to include a section on your planning in the final report. This section must contain a calculation of the transit time and the transit altitude of your chosen object. You may find the positional astronomy notes (here, here and here) of use.
Observing: Your observing sessions will be supervised by Paul Kerry and must be completed in a specified period: Mon 16 October - Friday, 8 December 2017 (weeks 3-11), although please note that observing is not possible over weekends and there may be short periods when Paul Kerry is unavailable.
Sign-up sheets will be posted on the Astronomy Noticeboard outside the Astronomy Lab (E36). Paul Kerry will contact you in advance if observing will be carried out; please read the full instructions on how observing works. Although you should be able to complete all your observations in a single session, to allow for the vagaries of British weather we expect you to sign up for at least two evenings per week until you have successfully completed your observing. If you cannot do this, you must discuss the problem with me or Paul Kerry before the start of the designated observing period, or as soon as the problem (e.g. illness) becomes apparent. Note that reading week is not a holiday. We expect you to sign up during reading week as usual.
Attendance at the observing is compulsory - you will not receive any marks for the project if you fail to show up or, if the weather is bad for part of the specified observing period, you have not made every effort to sign up for other time slots. Note that, unless previously agreed with me or Paul Kerry, if you are unable to attend a successful observing session with the other members of your group, it will not be possible for you to observe at a later date on your own. Note also that no resit of the observing project is possible, so missing it will make it much more difficult to pass the module.
We strongly advise signing up for observing as soon as possible: students who fail this module tend to be those who leave signing up until the last minute and then suffer from poor weather at the end of the observing period. This is no excuse, as there are usually clear periods at the start of the observing period which no students sign up for. Only if the entire period is unusable, or if you have genuinely serious reasons as to why you could not do the observations (which in most cases must be supported by documentary evidence), will this component not count towards the final mark.
Data reduction and report: After you have obtained your observations, you will need to reduce and analyse your data using the computers and software available in the Astronomy Lab. Note that this element of the project, and the subsequent write-up, must be your own work - do not work in your observing groups. You should be able to reduce your data using the skills you learn in this course. In case of difficulty, see myself or Paul Kerry for assistance.
Your write-up should be similar to a formal laboratory report. There must be sections describing the planning stage, the observations (a description of the equipment used, the observing conditions and the data that was taken), the data reduction and the data analysis. You will be penalised if you omit an analysis of the errors, and if you fail to compare your results with literature values. Some advice on how to write the report is here, and the rubric used to mark the report is here. I strongly recommend peer marking each other's reports with this advice and rubric in mind.
You may well want to prepare your reports using the Jupyter notebook - it is possible to produce PDF documents from the notebook. Please submit hard copies of your reports to the departmental office by the deadline: Friday 2nd February 2018 (16:00). In addition please do email your notebook (if you used it) to Stuart Littlefair. Note that this deadline is the final week of term, and has been set to make the observing window as long as possible. However, you will undoubtedly have other pieces of work to hand in around this time, so it is in your interests to complete your observing and hand in your report as early as possible in the semester.
Some examples of the data obtained for previous projects are given here. All students will attempt the same project, which is described below.
Hertzsprung-Russell (HR) diagram of an open cluster.
The aim here is to measure the distance and age of an open cluster. A list of open clusters is available here.
Make sure that you pick a cluster that is visible from Sheffield at the start of the night. You can do this using Cartes du Ciel on any University PC, Stellarium on your own PC, or the on-line ING Object Visibility page (where you must enter the longitude and latitude of Sheffield in the following format: 358 30 51 53 22 50 185). Even if you use an online tool to choose your cluster, you must manually calculate the transit time and altitude and present this calculation in your report.
The cluster you select must also:
isochronesPython library, which is installed on the Astronomy Python Server. The documentation for this library is found here, and instructions for creating an isochrone for a given age is located here.