this is for holding javascript data
Jamie Budynkiewicz edited everyday_seds.tex
about 10 years ago
Commit id: 2cdb112393d922985f1ab17062422b677d59398d
deletions | additions
diff --git a/everyday_seds.tex b/everyday_seds.tex
index 56e1291..91d9ddb 100644
--- a/everyday_seds.tex
+++ b/everyday_seds.tex
...
The astronomer may also want to inspect the SED, for example plotting it against different units, normalizing some of points or spectral segments, shifting the SED to another redshift, and performing other simple visualization tasks.
This inconvenience -- building SEDs from multiple sources -- drove a part of Iris' SED analysis design. Following VO efforts to seamlessly combine data services and applications, Iris offers a standard means of building large broadband SEDs from different sources in various data formats, while providing robust fitting methods and interactive visualization capabilities. Users can input SED data from file (with high leniency on the data format), a URL, another VO-enabled application, or directly from VO-enabled data archive services. If the data
format follows the IVOA Spectrum Data Model v1.03
(i.e. \cite{http://labs.adsabs.harvard.edu/adsabs/abs/2012arXiv1204.3055M}, or is a VO-compliant VOTable or FITS
file), file, the data is read-in without any input by the user; otherwise, the user supplies the units and mapping to the spectral-flux coordinates in the file. How this method works is described in Section \ref{sec:components}.
If Iris is missing a certain functionality, the user may develop a plugin for that functionality and add it to Iris. Thus, a user can employ Iris' SED building capabilites while using their own fitting procedure. We explore this possibility in detail in Section \ref{sec:plugins}