Catalog

JavaScript is used, and should be enabled to get full functionality.

Looking for catalogs ..

The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.

6 catalogs found


	17860113 J/ApJ/786/113	1889	^(c) 76 76	Extinction law in the Cep OB3b young cluster (Allen+, 2014) ReadMe+ftp 2014ApJ...786..113A	0
	17940036 J/ApJ/794/36	10502	^(c) 0	{sigma} Orionis cluster stellar population (Hernandez+, 2014) ReadMe+ftp 2014ApJ...794...36H	0
	19230278 J/ApJ/923/278	3206	^(c) 0	Massive star cluster in LIRGs in GOALS. II. (Linden+, 2021) ReadMe+ftp 2021ApJ...923..278L	0
	36680019 J/A+A/668/A19	5124	^(c) 210k 210613	Stellar population of Rosette Nebula and NGC 2244 (Muzic+, 2022) ReadMe+ftp 2022A&A...668A..19M	0
	51440095 J/AJ/144/95	2704	^(c) 492 492	Abundance in stars of the outer galactic disk. IV. (Yong+, 2012) ReadMe+ftp 2012AJ....144...95Y	0
	75420703 J/MNRAS/542/703	2381	^(c) 562 562	Stellar evolution in NGC 663 (Marco+, 2025) ReadMe+ftp 2025MNRAS.542..703M	0
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/VR3552124.err (2026-02-03T18:44:05)
-2
-kw.cat=75420703
-ref=VIZ698241f536337c

elapse time 2