This research object implements the propagation of properties extracted from the HyperLEDA database in the calculation of luminosities of galaxies. (See README.txt) (A) HOW TO GET THE MOST UPDATED LUMINOSITY VALUES FOR A GALAXY SAMPLE USING HYPERLEDA DATABASE _________________________________________________________________________________________ This recipe shows how to get up-to-date luminosity values using HyperLEDA database as source for the basic properties. This is the first step in the propagation quantities Research Object. After calculating the values for the luminosity, the user can compare with the current values of the group database and decide whether to update it or not. 1)WORKFLOW: ./workflows/luminosities.t2flow. This workflow queries Hyperleda to extract the properties needed to calculate the distance of the galaxy, the corrected apparent B magnitude, and the luminosity. 2)INPUTS: This workflow receives a text file with the list of galaxy names of the sample (./data/input/names/NamesLEDA.txt) and a file with the morphological types of those galaxies (./data/input/properties/morphoOld.txt) 3)OUTPUTS: (The output of this workflow must be stored in ./data/output/properties) * A text file with three columns: name of the galaxy, J2000 coordinates of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, dust extinction coefficient of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, heliocentric velocity of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, axis ratio of the isophote 25 of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, apparent total B magnitude of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, calculated distance of the galaxy and value error of the coordinates (if no error, will be NaN) * A text file with three columns: name of the galaxy, calculated corrected apparent B magnitude of the galaxy and value error of the coordinates (if no error, will be NaN) * A text file with three columns: name of the galaxy, optical luminosity in B-band of the galaxy and value error of the coordinates (if no error, will be NaN) (B) HOW TO MAKE A COMPARISON OF RETRIEVED AND FINAL CALCULATED PHISICAL PROPERTIES _____________________________________________________________________________________________ This recipe shows how to compare the values retrieved from HyperLEDA or calculated using the values from HyperLEDA, with the values stored in the group database. As well as comparing file, a sql script file will be got, which can be used to update the database. 1)WORKFLOW: ./workflows/comparing_updating.t2flow 2)INPUTS: * Two text files. Both files have three columns: name of the galaxy, value of the property and value of the error. One file must have the current property values stored in the group database (i.e ./data/input/properties/distancesOld.txt), and the other file must have the most updated property (this file can be obtained following the recipe A (i.e. ./data/output/properties/distancesNew.txt). * The name of the field of the table to create/update * The name of the table to create/update 3)OUTPUTS: * A text file with the SQL commands to update / create the database using the most updated values of the property. This text file must be stored in ./data/sql (i.e ./data/sql/distances.sql) * A text file with 9 columns: Name of the galaxy, property value of the group database, property error value of the group database, most updated property value, most updated property error value, difference between both property values, difference between both property error values. The 8th columns is a flag that indicates whether the group database does not have a value for this property, while the last release of HyperLEDA does have this value. The 9th columns is the opposite flag: it indicates whether the group database does have a value for this property, but the last release of HyperLEDA does not have it. This text file must be stored in ./data/output/diffs/ (i.e. ./data/output/diff/diff_distances.txt) (C)HOW TO CREATE A SET OF SQL SCRIPTS TO UPDATE THE GROUP DATABASE. See recipe (B) (D)HOW TO OBTAIN THE DATA FROM HYPERLEDA NEEDED TO CALCULATE THE LUMINOSITY FROM HYPERLEDA _______________________________________________________________________________________________ This recipe shows how to extract the values of the properties needed to calculate the luminosity. These properties are the equatorial coordinates in J2000 epoch, the velocities in km/s (v), the dust extinction coefficient (ag), the axis ratio of the isophote 25 mag/arcsec2 (logr25) and the apparent total B magnitude (BT). 1) WORKFLOW: ./workflows/gathering.t2flow 2) INPUTS: a text file with the list of galaxy names of the sample (./data/input/names/NamesLEDA.txt) 3) OUTPUTS: * A text file with three columns: name of the galaxy, J2000 coordinates of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, dust extinction coefficient of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, heliocentric velocity of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, axis ratio of the isophote 25 of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). * A text file with three columns: name of the galaxy, apparent total B magnitude of the galaxy extracted from HyperLEDA, and value error of the coordinates (if no error, will be NaN). (E) HOW TO REPRODUCE THE RESULTS OF THIS RO? _________________________________________________________ This recipe shows how to get the same values of the calculated properties (distances, corrected apparent B magnitude, optical luminosity in B-band) re-executing the proper workflow of the RO. This is a method to check the reproducibility of the RO in different conditions as, for example, different configurations of Python environment. Since the data in HyperLEDA are continuosly changing, we have to use the data extracted from HyperLEDA in the moment of the calculation of these properties, to make sure, if the RO is well done, we will get the same results. 1) WORKFLOW: ./workflows/propagation.t2flow. This workflow, unlike luminositiesVO.t2flow, receives as input the files with the values of the properties, instead of querying HyperLEDA database. 2) INPUTS: To get the same results stored in ./data/output, we have to use the files stored in ./data/output/properties. Particularly: * ./data/output/properties/logr25New.txt, as the file with the axis ratio of the isophote 25 values * ./data/output/properties/btNew.txt, as the file with the apparent total B magnitude values * ./data/input/properties/morphoOld.txt as the file with the morphological types . Noticed morphological types is **not** a property extracted from HyperLEDA. This property is stored in the group database. * ./data/output/properties/agNew.txt as the file with the dust extinction coefficients * ./data/output/properties/velocityNew.txt as the file with the velocities * ./data/output/properties/j2000Coords.txt as the file with the J2000 coordinates. 3) OUTPUTS: The output will be the values of the three calculated properties: distances, corrected apparent B magnitude, optical luminosity in B-band. They must to be equals to: * ./data/output/properties/distancesNew.txt * ./data/output/properties/btcNew.txt * ./data/output/properties/lbNew.txt (F) HOW TO CALCULATE THE LUMINOSITY USING A NEW SET OF MORPHOLOGICAL TYPES. This recipe is very similar to the previous one (recipe E). In this case we are going to use the current values of the properties in the group database to calculate the distances, the corrected apparent B-magnitude and the luminosity, using a different set of morphological types. 1) WORKFLOW: ./workflows/propagation.t2flow. This workflow, unlike luminositiesVO.t2flow, receives as input the files with the values of the properties, instead of querying HyperLEDA database. 2) INPUTS: We are going to use the current values in the group database. Particularly: * ./data/output/properties/logr25Old.txt, as the file with the axis ratio of the isophote 25 values * ./data/output/properties/btOld.txt, as the file with the apparent total B magnitude values * ./data/input/properties/morphoNew.txt as the file with the **NEW** morphological types * ./data/output/properties/agOld.txt as the file with the dust extinction coefficients * ./data/output/properties/velocityOld.txt as the file with the velocities * ./data/output/properties/j2000Coords.txt as the file with the J2000 coordinates. 3) OUTPUTS: The output will be the values of the three calculated properties: distances, corrected apparent B magnitude and optical luminosity in B-band. The resulting files must be stored in ./data/output/properties, with a proper suffix denoting how this files have been calculated (i.e. ./data/output/properties/distances_newMorphology.txt) NOTES ___________________________________________________ Our internal data are in: MySQL BDD: http://amiga.iaa.es/CIG/db_structure.php?db=RELEASE_CIG_JUN10 Table: RESULTS_LB_CIG