Es User: Susana

3381?size=160x160

Name: Susana

Joined: Tuesday 20 September 2011 10:55:41 (UTC)

Last seen: Wednesday 14 July 2021 09:04:36 (UTC)

Email (public): sse [at] iaa.es

Website: http://amiga.iaa.es/p/37-susana-sanchez.htm

Location: Spain

Susana has been credited 12 times

Susana has an average rating of:

4.8 / 5

(5 ratings in total)

for their items

Description/summary not set


Other contact details:

Not specified

Interests:

Not specified

Field/Industry: Not specified

Occupation/Role(s): Not specified

Organisation(s):

Not specified
 

Note: some items may not be visible to you, due to viewing permissions.


Contents (click to expand/contract)
Uploader

Workflow Kinematical modelling of a galaxy using a ... (1)

Thumb
No description

Created: 2015-03-20

Credits: User Susana

Uploader

Workflow Kinematical modelling of a galaxy using th... (1)

Thumb
No description

Created: 2015-03-20 | Last updated: 2015-03-20

Credits: User Susana

Uploader

Workflow Single service to calculate the rotation c... (3)

Thumb
No description

Created: 2015-03-20 | Last updated: 2015-11-20

Credits: User Susana

Uploader

Workflow Calculation of a rotation curve and densit... (2)

Thumb
No description

Created: 2015-03-20 | Last updated: 2015-03-23

Credits: User Susana

Uploader

Workflow Calculation of the rotation curve of a gal... (1)

Thumb
No description

Created: 2015-03-20 | Last updated: 2015-03-20

Credits: User Susana

Uploader

Workflow Querying SDSS DR8 to get magnitude properties (2)

Thumb
This workflow gets a VOTable with the RA and DEC among others values of a list of galaxies. The workflow queries the SDSS DR8 VO conesearch service, to extract the objID, specObjID, ra, dec, u, g, r, i, z.

Created: 2012-09-26 | Last updated: 2013-03-08

Credits: User Susana

Uploader

Workflow Searching for near galaxies in NED service (2)

Thumb
This workflow needs as input an ascii table with a list of galaxies. This table contains the PGC name of the galaxy, the CIG number, the radius of searching, Z1 and Z2. The workflow uses the radius, Z1, Z2 and the PGC name of the galaxy to query NED service and get the html with the list of companions. This html is parsed and it is built a VOTable with the RA, DEC, Magnitud, Redshift, Separation, Velocity of each companion.

Created: 2012-09-26 | Last updated: 2012-10-09

Credits: User Susana

Uploader

Workflow Gathering info from SDSS into a VOTable to... (4)

Thumb
This workflow joins two main nested workflows: - "Extract SDSS field information and PSF" workflow, which gathers information from SDSS VO service and from the header image in several VOtable. It also generates the psf files. - "Joining VOtables with information to execute Sextractor, Galfit and Ellipse" workflow, which joins the VOtables generated by the previous workflow to get only one VOtable with all the information

Created: 2012-08-13 | Last updated: 2013-03-08

Credits: User Susana

Uploader

Workflow Joining VOtables with information to execu... (3)

Thumb
This workflow join 13 votables, obtained from the workflow "Extract SDSS field information and PSF" in order to get a only one votable with all the information. Also it adds the columns "zp", "magzeropoint", xconvsize, yconvsize that are calculated from values provided in the inputs. The zp is -( aa + kk * airmass ), the magzeropoint is zp + 2.5 * log10(53.907456), the xconvsize is roundUp(nx/10) and the yconvsize is roundUp(ny/10)

Created: 2012-08-13 | Last updated: 2013-03-08

Credits: User Susana

Uploader

Workflow Convert a list into a VO Column (2)

Thumb
This workflow converts a list of values into a VO table with only one column. It receives two inputs: the list of values and the header name of the column to be built.

Created: 2012-08-13 | Last updated: 2013-03-08

Credits: User Susana

Uploader

Workflow Extract SDSS field information and PSF (5)

Thumb
This workflow gathers information needed by the execution of Sextractor, Galfit and Ellipse, from the SDSS VO service. It receives two inputs: 1) An ascii table with information about the image such as data of the field, name of the fits file or if it is barred or not. 2) A configuration file with the paths where the files needed by the workflow can be found and other paths where to store the files generated by the workflow This workflow extracts the band from the image header, and the info...

Created: 2012-07-26 | Last updated: 2012-09-07

Credits: User Susana

Uploader

Workflow Example of how to use Sesame service and V... (1)

Thumb
This workflow needs as input a list of names of galaxies. Then it queries Sesame services to get the coordinates of this galaxies, and finally with this coordinates queries a Virtual Observatory Services (a cone service).

Created: 2012-07-14

Uploader

Workflow Example of jdbc (1)

Thumb
No description

Created: 2012-05-24 | Last updated: 2012-05-24

Uploader

Workflow Calculating the internal extinction with d... (3)

Thumb
No description

Created: 2012-05-23 | Last updated: 2015-03-25

Uploader

Workflow Extract logr25 from LEDA service (1)

Thumb
No description

Created: 2012-05-23 | Last updated: 2012-05-24

Uploader

Workflow Getting information from LEDA service (1)

Thumb
No description

Created: 2012-05-23

Uploader

Workflow Sesame service to get the RA and DEC of a ... (1)

Thumb
No description

Created: 2012-05-23

Uploader

Workflow Comparison and update values (1)

Thumb
This workflow receives two files, the name of a table and the name of a field as input. One of the file should be contain a list of old values (name galaxy and value), and the other one should be a list of new values (name galaxy,value) The workflow makes a comparison between the two files. This comparison will be a list of 7 columns: name of the galaxy, old value, old error, new value, new error, difference of value, difference of error. In other hand, this workflow makes a sql script with ...

Created: 2011-11-30 | Last updated: 2011-11-30

Uploader

Workflow Gathering galaxy properties using HyperLEDA (2)

Thumb
The user provides an ASCII text file with a list of galaxy names, and the workflow queries the HyperLEDA database and parses the response with the help of regular expressions included in simple Python scripts. The result of the workflow is a series of ASCII text files with the values of the equatorial coordinates in J2000 epoch, the velocities in km/s, the dust extinction coefficient Ag, the axis ratio of the isophote 25 mag/arcsec2 logr25 and the apparent total B magnitude BT. The performanc...

Created: 2011-11-30 | Last updated: 2013-03-08

Uploader

Workflow Propagation of physical quantities in the ... (3)

Thumb
This workflow takes as input a file for each of this properties: J2000 Coordinates, velocity, galactic extinction, log of axis ratio, and the Total B-magnitude. With this properties it calculates the distance of the galaxy and, in other hand, the total apparent corrected B-magnitude. It takes account if the velocity of the galaxy is lower than a threshold (1000km/s), it can not be possible to calculate the distance so, in those cases the distance will be "NaN". At the end, it calculates the ...

Created: 2011-11-30 | Last updated: 2013-04-22

Uploader

Workflow Calculation of distances, magnitutes and l... (4)

Thumb
Calculation of distances, corrected apparent B magnitude mB-corr and luminosities with values gathered from the HyperLEDA database. This workflow receives a list of galaxy names (hyperLEDA names. ie: KIG0001) and a file with the morphological types of those galaxies Using the name of a galaxy, the workflow querys Hyperleda to extract some properties of this galaxy (J2000 Coordinates, velocity, galactic extinction,log of axis ratio, and the Total B-magnitude ). With this properties it calcula...

Created: 2011-11-14 | Last updated: 2012-01-11

Uploader

Workflow Extracting Quantities from HyperLEDA (1)

Thumb
This workflow receives the name of the property to compare and a file with a list of names of galaxies. The property name must be the same used in the HTML file returned by the HyperLEDA service. The workflow calls to HyperLEda service, using as input the names of the galaxies in order to get a HTML file with information about each galaxy. From each HTML file, it extracts the value of the property selected by the user. The workflow uses a python tool to parse the HTML file (one for each gala...

Created: 2011-10-05 | Last updated: 2011-10-05

Uploader

Workflow Comparing Quantities using HyperLEDA (1)

Thumb
This workflow receives the name of the property to compare, a file with a list of names of galaxies, and a file with the list of original values of that property. The property name must be typed in the same way used in the HTML returned by HyperLEDA The workflow calls to HyperLEDA using the names of the galaxies as input, and it returns a HTML file with information about the galaxy. This file is parsed by the python tool "ExtractPropertyValues", that extracts the value of the property introdu...

Created: 2011-10-03

Uploader

Workflow Calculating galaxies distances using data ... (1)

Thumb
This workflow needs two inputs: a file with the list of the names of galaxies whose distance are going to be calculated (name galaxy file), and a file with our values of velocity for each galaxy (local velocity file). This workflow is composed by 5 nested workflow. The first one is used to read line by line the name galaxy file. This list of names is the input for the following two nested workflows. One of them uses the line with the name of galaxy to call HyperLEDA and to extract the veloci...

Created: 2011-10-01 | Last updated: 2011-10-03

Uploader

Workflow Comparing Quantities (1)

Thumb
This workflow receives the name of the property to compare, a file with a list of names of galaxies, and a file with the list of original values of that property. The property name must be the same used in the VOtable returned by the Vizier service. The workflow calls to sesame name resolver using as input the names of the galaxies and gets the coordinates. Then it calls to Vizier service and provides to it with the coordinates as input, in order to get a VOTable with information about each ...

Created: 2011-09-23

Uploader

Workflow Name resolver of galaxies parsing the outp... (1)

Thumb
This workflow ask for text file using "Select_file" local services. This file is read by the "read_text_file", using "utf-8" as encoding. The result of "read_text_file" is splitted in lines by "split_string_into_string_list_by_regular_expression" and each of this lines is the input for the Rest_servise. The REST service search for each line (each line contains one name of one galaxy) some information about that galaxy. The string is like: target=cig+1 service=NED(nedwww.ipac.caltech.edu) coo...

Created: 2011-09-21

Uploader

Workflow Name resolver of galaxies parsing the outp... (1)

Thumb
This workflow ask for text file using "Select_file" local services. This file is read by the "read_text_file", using "utf-8" as encoding. The result of "read_text_file" is splitted in lines by "split_string_into_string_list_by_regular_expression" and each of this lines is the input for the Rest_servise. The REST service search for each line (each line contains one name of one galaxy) some information about that galaxy. The string is like: target=cig+1 service=NED(nedwww.ipac.caltech.edu) coo...

Created: 2011-09-21 | Last updated: 2011-09-21

What is this?

Linked Data

Non-Information Resource URI:


Alternative Formats

HTML
RDF
XML