VizieR

CfA VizieR . ADAC VizieR . CADC VizieR . Cambridge (UK) VizieR . IUCAA VizieR . Beijing (Ch) VizieR .

Catalog

Looking for catalogs ..
Simple TargetList Of TargetsFast Xmatch with large catalogs or Simbad
Target Name (resolved by Sesame) or Position:

  
Target dimension:

Radius Box size

  
J/AJ/135/1917
  Photometric search for transients in galaxy clusters (Sand+, 2008)
Post annotation
img(gal)
1.J/AJ/135/1917/tablesList of identified variables from Cluster centered chip 1 (table3) and Background chip 3 (table4) (340 rows)

 
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)
  Chip (char) 1 for Cluster centered chip 1 (table3) or 3 for Background chip 3 (table4) (meta.code)
  Name (char) Cluster name (meta.id;meta.main)
  RAJ2000 "h:m:s" (i) Hour of Right Ascension (J2000) (Note 1)   (pos.eq.ra;meta.main)
  DEJ2000 "d:m:s" (i) Degree of Declination (J2000) (Note 1)   (pos.eq.dec;meta.main)
  gmag mag SDSS g band magnitude (phot.mag;em.opt.B)
  e_gmag mag Uncertainty in gmag (stat.error;phot.mag;em.opt.B)
  Dist kpc Distance from Brightest Cluster Galaxy (pos.distance;pos.heliocentric)
  Notes (char) Additional notes (Note 2)   (meta.note)
  Obs s (n)Date of the observation (time.epoch)

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:
**** -bg is an obsolete option
**** -bg is an obsolete option
**** -bg is an obsolete option
**** 
**** -- 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_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/VR34234.err (2018-09-19T22:57:52)
-2
-source=J/AJ/135/1917
-ref=VIZ5ba2d47085ba
elapse time 1

Thanks for acknowledging the VizieR Service
Rules of usage of VizieR data

© Université de Strasbourg/CNRS

    • Contact