VOSA. Help and Documentation

Version 7.5, July 2022

1. Introduction
2. Input files
2.1. Upload files
2.2. VOSA file format
2.3. Single object
2.4. Manage files
2.5. Archiving
2.6. Filters
3. Objects
3.1. Coordinates
3.2. Distances
3.3. Extinction
4. Build SEDs
4.1. VO photometry
4.2. SED
4.3. Excess
5. Analysis
5.1. Model Fit
5.2. Bayes analysis
5.3. Template Fit
5.4. Templates Bayes
5.5. Binary Fit
5.6. HR diagram
5.7. Upper Limits
5.8. Statistics
6. Save results
6.1. Download
6.2. SAMP
6.3. References
6.4. Log file
6.5. Plots
7. VOSA Architecture
8. Phys. Constants
9. FAQ
10. Use Case
11. Quality
11.1. Stellar libraries
11.2. VO photometry
11.3. Binary Fit Quality
12. Credits
12.1. VOSA
12.2. Th. Spectra
12.3. Templates
12.4. Isochrones
12.5. VO Photometry
12.6. Coordinates
12.7. Distances
12.8. Dereddening
12.9. Extinction
13. Helpdesk
14. About
. Excess calculation
. Total flux calculation
. VOphot quality info

SAMP: Send results to other VO tools

SAMP is a VO protocol that allows to share data between VO applications. It was initially designed to work between desktop applications but, thanks to Mark Taylor's sampjs library VOSA, being a web application, can share results with desktop applications too.

Thus, apart from just visualizing and downloading the final results, most of the tables can be broadcasted to any other VO application that is open in the final user computer and connected to the SAMP Hub. In particular, this is specially useful to send some results tables to Topcat for further analysis.

As far as you have an active SAMP Hub in your computer (for instance, if you have Topcat open) you will see a "Sent table to SAMP Hub" button in some of the VOSA results. For example, in a model fit, you can see it:

The SAMP Hub will request authorization to broadcast the file sent by VOSA: You can accept it safely.

The VO table sent by VOSA will be loaded into TopCat,

and you will be able to use Topcat functionalities to work with it.