VizieR

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

Catalog

Looking for catalogs ..
The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.
8 catalogs found
  
    
J/ApJ/842/83
(c)
1k
Praesepe members rotational periods from K2 LCs (Douglas+, 2017)
img(gal)
    
J/ApJ/879/100
(c)
K2 rotation periods for Hyades & Praesepe members (Douglas+, 2019)
img(gal)
    
J/AJ/150/16
(c)
Speckle-interferometry in Melotte 111 (Guerrero+, 2015)
img(gal)
    
J/AJ/154/69
(c)
437
ACRONYM II. The {beta} Pictoris Moving Group (Shkolnik+, 2017)
img(gal)
    
J/AJ/154/195
(c)
106
New binaries in the {epsilon} Cha association (Briceno+, 2017)
img(gal)
    
J/AJ/155/51
(c)
506
Robo-AO binary star systems in 3 open clusters (Hillenbrand+, 2018)
img(gal)
    
J/AJ/165/6
6k
BD+37 410 & DS And light curve and radial velocity (Sandquist+, 2023)
timeSerie
  
    
J/AJ/165/45
(c)
3k
(H-W2)-W1 vs W2-(BP-K) for 4 open cluster members (Malofeeva+, 2023)
spectrum
img(gal)

ALL
       or   
       (c)  indicates tables which contain celestial coordinates 


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_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- 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
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR4153088.err (2025-12-06T18:14:27)
-2
-kw.cat=51650045
-ref=VIZ693472833f5f00
elapse time 2