VizieR

CfA VizieR . ADAC VizieR . Cambridge (UK) VizieR . IUCAA VizieR . INASAN VizieR .

Catalog

Looking for catalogs ..
  
J/ApJ/775/84
  Polarization from stars behind IC63 nebula (Andersson+, 2013)
ReadMe+ftp
2013ApJ...775...84A
Similar Catalogs
spectrum/polarization
Post annotation 		img(gal)
1.J/ApJ/775/84/table2Polarimetry results (169 rows)

Simple ConstraintList Of Constraints
 
Query by Constraints constraints help applied on Columns (Output Order: + - )
ShowSortColumn  Constraint Explain   (UCD)
  recno  Record number assigned by the VizieR team. Should Not be used for identification. (meta.record)
  Star   [5/76] Star identifier (meta.id;meta.main)
  f_Star (char) [1] Synthesized photometry (Note 1)   (meta.code)
  Filt (char) Filter identifier (UBVRI or H) (meta.id;instr.filter)
  lambda um [0.3/1.7] Central wavelength of filter ({lambda}c) (em.wl.central;instr.filter)
  Width um (n) [0.02/0.08] Filter width ({Delta}{lambda}) (instr.bandwidth)
  Pol % (n) [0.2/9.5] Polarization (p) (phys.polarization)
  e_Pol % (n) [0.05/4] Uncertainty in Pol (stat.error)
  polPA deg (n) [61/140] Position angle ({theta}); E of N (pos.posAng;phys.polarization)
  e_polPA deg (n) [1/23] Uncertainty in PA (stat.error)

ALL cols		    
(n) indicates a possible blank or NULL column(i)indexed column
Adapt form
 Display your selection only Reset to default columns
usage  Display UCD1+    UCD1  

The following problems were encountered in this VizieR run:
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR2952715.err (2026-01-14T13:24:09)
-2
-source=J/ApJ/775/84/table2
-ref=VIZ696798fa2d0e0b
elapse time 2