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.

3 catalogs found

	J/ApJ/791/107	1641		Parameters of NGC 5139 SGBs stars (Villanova+, 2014) ReadMe+ftp 2014ApJ...791..107V Similar Catalogs
	J/ApJ/791/107/table3		^(c)Parameters of the observed stars (172 rows)
	J/AJ/154/57	7241		New SDSS and Washington photometry in Segue 3 (Hughes+, 2017) ReadMe+ftp 2017AJ....154...57H Similar Catalogs
	J/AJ/156/191	1867		The ages of M31 star clusters: SED versus CMD (Fan+, 2018) ReadMe+ftp 2018AJ....156..191F Similar Catalogs
	J/AJ/156/191/table1		^(c)Ages of our sample star clusters derived from SED fits of different passband combinations with BC03 models and Padova 2000 stellar evolutionary tracks (32 rows)
	J/AJ/156/191/table2		Same as Table 1 but for fixed-Z from the literature (32 rows)
	J/AJ/156/191/table3		Same as Table 1 but for the GALEV models and a Kroupa (2001MNRAS.322..231K) initial mass function (IMF) (32 rows)
	J/AJ/156/191/table4		Same as Table 3 but for fixed-Z from the literature (32 rows)
	J/AJ/156/191/table5		Same as Table 1 but for the ASPS bsp-SSPs models (32 rows)
	J/AJ/156/191/table6		Same as Table 5 but for fixed-Z from the literature (32 rows)
ALL
			^(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
**** 
**** -- 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

If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR702743.err (2025-12-06T00:32:36)
-2
-kw.cat=17910107
-ref=VIZ693379a4ab917

elapse time 2