Differences

This shows you the differences between two versions of the page.

--- en:praktikum:photometrie [2021/04/06 15:58] – [Identify the stars in the field of view] rhainich
+++ en:praktikum:photometrie [2023/09/19 06:52] (current) – rhainich
@@ Line 1: / Line 1: @@
-====== N2 - Photometry of open star clusters ======
+====== N2 - Photometry of open star clusters (GDL) ======
 /*
@@ Line 199: / Line 199: @@
 ==== Preliminary color magnitude diagram (CMD) ====
-The next step is to write the dataset that will be used to plot the CMD, i.e. visual magnitude over color (blue minus visual magnitude). The CMD itself can be plotted with different tools, here the version with //gnuplot// is explained (please, don't use //Excel//), also //GDL// can create PostScript plots (see below). First write the data into a file named ''cmd.dat'':
+The next step is to write the dataset that will be used to plot the CMD, i.e. visual magnitude over color (blue minus visual magnitude). The CMD itself can be plotted with different tools, here the version with //Python// is explained (please, don't use //Excel//), also //GDL// can create PostScript plots (see below). First write the data into a file named ''cmd.dat'':
   openw, out, 'cmd.dat', /get_lun
   for i=0,num-1 do printf,out,i,(bmag[i]-vmag[i]),vmag[i]
@@ Line 240: / Line 240: @@
 The script can be executed in the terminal with the following command
-  ./plot_cmd.py
+  python plot_cmd.py
 Afterwards, a figure, showing the CMD, can be found in the current directory. The file type of this figure can be set via the variable ''filetype''.
@@ Line 254: / Line 254: @@
 ==== 1. Alternative ====
- There's a star in the field with known B and V magnitude. If it can be identified in the table, the magnitudes of the respective tables need to be shifted by the difference between the literature magnitude and the determined value.
+One finds stars on the image whose B and V magnitudes are known. Then you have to identify these stars in the table and shift the values of the whole table so that the identified stars get the nominal values.
 === Identify the stars in the field of view ===
@@ Line 267: / Line 266: @@
 === Identify possible calibration stars ===
-Once the field has been identified, find 3-4 stars in the center of the field for which both the B and V magnitudes are known. Note down these values for later use.
+Once the field has been identified, find 5-6 stars in the center of the field for which both the B and V magnitudes are known. Note down these values for later use. The magnitudes can be determined in different ways:
-  * To ease that process, use Simbad again: In the ''basic search'' use the ''query around'' (with radius...) and choose ''plot this list of objects'' to obtain a schematic map of the cluster with clickable stars. Click on the stars to see their magnitudes (B and V magnitudes are of interest).
+  - The easiest way is to select the option ''SIMBAD'' in the //Aladin-Lite// view on the right side under ''Catalogues''. This activates an overlay which shows all objects listed in //Simbad//. If you click on one of the objects, all parameters known to //Simbad// are listed in a table on the left. If you scroll down you will also find the magnitudes. However, not for all objects magnitudes are available.
+  - If you have //JAVA// installed you can also use the ''Aladin Java Applet'', which has similar functions as //Aladin-Lite//. Click on the highlighted stars to see their magnitudes.
-  * The same can be reached with the ''Aladin Java Applet'' but this tool requires //JAVA// to installed on your computer. Click on the highlighted stars to see their magnitudes. If you work with a computer of the computer pool or at home, this method is the easiest.
+  - Alternatively, you can get an overview of all objects in the star field by clicking on the option ''query around'' (with radius...) in the Simbad overview for the star cluster. If you select the option ''plot this list of objects'', a schematic map appears in which you can click on the stars marked there. If known, you get their names and B- and V -values.
+  - However, one can also compare the best exposed visual image with the [[http://skyview.gsfc.nasa.gov|Digitized Sky Survey]] of the area in question and identify the image section. Then use an overlay with the stars from important catalogs (Bonner Durchmusterung and Henry Draper (HD) Catalogue) to identify stars (note the scrollbar in the menus!). If there are catalog stars in the observed field, use [[http://simbad.u-strasbg.fr/Simbad|Simbad]] to find their B and V magnitudes.
-  * An alternative method (without Simbad) makes use of the [[http://skyview.gsfc.nasa.gov|Digitized Sky Survey]]. Compare the best visual exposure with the relevant sections (coordinates) of the sky to identify the region. Then use an overlay with the stars from important catalogs (Bonner Durchmusterung and Henry Draper (HD) Catalogue) to identify stars (note the scrollbar in the menus!). If there are catalog stars in the observed field, use [[http://simbad.u-strasbg.fr/Simbad|Simbad]] to find their B and V magnitudes.
+/*
 In any case check whether the given magnitudes are absolute or apparent ones. If the latter is true, check for the distance (modulus) to convert them.
+*/
+The just identified comparison stars have to be associated with our own results. A //Python// script (''plot_stars.py'') is available that helps with that task. It plots the stars identified with our //GDL// program. Copy ''~/scripts/n2/plot_stars.py'' to your current working directory and adjust the upper part
-A //Python// script is available which helps for that task. Copy ''~/scripts/n2/plot_stars.py'' to your current working directory and adjust the upper part
   # enter full path to your reduced fits-file
@@ Line 302: / Line 297: @@
 Afterwards, recompile and run your //GDL// program once more. Then save and run the //Python// script from a console:
-  ./plot_stars.py
+  python plot_stars.py
-An image "starmap.png" will be the result if all went well. It shows the image (e.g. ''vadd.fit'') as color-inverted background and all identified stars as overlays **(please include or attach this image to your report)**. This image can be compared with the calibration stars mentioned in the beginning. After one of the star's from the "starmap" has been matched to a calibration star, the number of the corresponding mark on the "starmap"  can be looked up in the file ''stars.dat'' to obtain the corresponding magnitude. The stars in the ''stars.dat'' file are ordered by increasing Y values. So you can search for the position of the star in your image which you used as background image for the star map and then you can search for the coordinates in the ''stars.dat'' file. The difference between this magnitude and the value given in //Simbad// is the calibration shift. Repeat this procedure for 3-4 stars and calculate the average of the calibration shifts. The variance should not be larger than 0.1 mag.
+An image "starmap.png" will be the result if all went well. It shows the image (e.g. ''vadd.fit'') as color-inverted background and all identified stars as overlays **(please include or attach this image to your report)**. This image can be compared with the calibration stars mentioned in the beginning. After one of the star's from the "starmap" has been matched to a calibration star, the number of the corresponding mark on the "starmap"  can be looked up in the file ''stars.dat'' to obtain the corresponding magnitude. The stars in the ''stars.dat'' file are ordered by increasing Y values. So you can search for the position of the star in your image which you used as background image for the star map and then you can search for the coordinates in the ''stars.dat'' file. The difference between this magnitude and the value given in //Simbad// is the calibration shift. Repeat this procedure for 5-6 stars and calculate the average of the calibration shifts. The variance should not be larger than 0.1 mag.
 ==== 2. Alternative ====
@@ Line 310: / Line 305: @@
   fluxb = fluxb / 440.
 After the conversion to magnitudes, the difference to the literature values can be calculated and as a correction applied to the observation of the star cluster.
+\\
+\\
+\\
 Either way, the B and V magnitudes need to be calibrated accordingly by the calculated shifts:
@@ Line 316: / Line 314: @@
   magvcal = magv - vcal
-With these values the final CMD can be plotted. To ease the output, the color can be calculated already at this point:
+With these values the calibrated CMD with apparent magnitudes can be plotted. For this we need the color, so we add the line:
   magbminusv = magbcal - magvcal
-In comparison with literature diagrams the main sequence is likely to be shifted. This occurs due to the interstellar medium which is spread between the stars of our Galaxy. Like all other baryonic matter, it can be excited by light. It will reemit  this energy usually at a longer wavelength. Therefore, this effect is called reddening (do not confuse it with redshift):
+==== Reddening & absolute magnitudes ====
+When comparing your apparent FHD to the literature, you will notice that the main sequence is likely to be shifted. This occurs due to the interstellar medium which is spread between the stars of our Galaxy. Like all other baryonic matter, it can be excited by light. It will reemit  this energy usually at a longer wavelength. Therefore, this effect is called reddening (do not confuse it with redshift):
 $(B-V)_{0} = (B-V) - E_{(B-V)}$
@@ Line 332: / Line 332: @@
 In the solar neighborhood $R_V$ usually is set to 3.1 ([[http://adsabs.harvard.edu/abs/1979MNRAS.187P..73S|Seaton 1979]]). Find an appropriate value for $E_{(B-V)}$ for the line of sight to the observed cluster, i.e. in //[[http://viz-old.u-strasbg.fr/viz-bin/VizieR-2|VizieR]]// or in //Simbad// by means of the papers that are associated with your object. In any case, refer to the used catalog or paper in your report! Apply this correction to your data and plot the CMD again.
-If the calibration was performed on apparent magnitudes, one need to account for dilution due to the distance of the cluster by applying the distance modulus.
+Finally the apparent magnitudes should be converted into absolute magnitudes, so that later a comparison with isochrons is possible. For this, the corresponding distance modulus or the distance of the star cluster must be looked up in papers (publications) and the corresponding correction must be applied.
-To plot the final CMD with the //gnuplot// script, write the corrected data again, e.g. overwrite the preliminary version of ''cmd.dat'':
+To plot the final CMD with the //Python// script, write the corrected data again, e.g. overwrite the preliminary version of ''cmd.dat'':
   openw, cmd, 'cmd.dat',/get_lun
@@ Line 349: / Line 349: @@
 As previously described, the file ''cmd.dat'' can be plotted with the script ''plot_cmd.py'', which can be run with
-   ./plot_cmd.py
+   python plot_cmd.py
 It also offers the possibility to include isochrones, which can be downloaded from the websites of various stellar evolution projects. The variables of the script ''plot_cmd.py'' need to be adjusted according to the requirements of the downloaded isochrone files. The script expects that the isochrones are given as individual files, which should be located in a single directory (''isoDir'').
@@ Line 421: / Line 421: @@
 ===== Report =====
+A usual report is to be handed in. See a general overview about the required structure and content [[https://polaris.astro.physik.uni-potsdam.de/wiki/doku.php?id=en:praktikum:protocol|here]].
+For this experiment, the theoretical overview in the report should describe open and globular cluster with emphasis on the observed kind, and their differences to other accumulations and groups of stars. Explain Hertzsprung-Russell diagrams (HRD) and the color-magnitude diagrams (CMD) and the difference between them. //Shortly// describe the evolution of stars of different masses in the context of a HRD. Explain the concepts of isochrones and the turn-off point and how one estimates the age of a cluster using them.
+In the methods section describe the observations and the data reduction, highlight points that deviate from general description in here and list all the parameters you set for the extraction. Further, include all the plots of the data reduction in the report (a few in the text, most of them in the appendix). Describe the calibration procedure and list the stars you use and the shifts you determine. Also include any parameters for reddening, extinction, and distance that you adopt from the literature.
+The results part presents the cluster CMDs and describes the observable features in it.
+The analysis of the CMDs contains the estimation of the cluster age based on the turn-off point and an isochrone fit.
+Finally, discuss your findings. Bring your results into a larger context and make a literature comparison when possible (i.e., for the cluster age). This also includes that you identify potential problems with the data, the data reduction, or the analysis (especially the isochrone fit) and possible solutions for them. Are their inconsistencies? Do you see specific and obvious features in the CMD you cannot explain, that do not match your expectations?
+//**Note:** The plots of the individual orders are in large files which generally do not fit into an email appendix. You may upload your report to the [[https://boxup.uni-potsdam.de/index.php/login|University cloud system (BoxUP)]] or send us the path to it on our lab course computer. //
+/*
+**OLD BELOW**
 Describe the difference between globular clusters and open clusters, with special emphasis on the character of the observed object. Discus the differences of stellar clusters and general accumulations/groups of stars. Shortly describe the evolution of a star and how it manifests in the Hertzsprung-Russell diagram and the color-magnitude diagram, respectively. Describe the age estimation of stellar clusters by means of the analysis of the turn-off point and by means of isochrones. Use these methods to determine the age of the observed clusters.  Write a normal laboratory-course report. Discuss your results and compare them to the literature. Address shortcomings in your results and discuss possible causes.
+*/
 [[en:praktikum:index|Overview: Laboratory Courses]]