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.

4 catalogs found

	J/ApJ/822/105	226		Chemical evolution in the SMC (Acharyya+, 2016) ReadMe+ftp 2016ApJ...822..105A Similar Catalogs Objects
	J/ApJ/822/105/table7		Abundances of assorted gas-phase species (261 rows)
	J/ApJ/841/84	3722		Theoretical framework for RR Lyrae. II. MIR data (Neeley+, 2017) ReadMe+ftp 2017ApJ...841...84N Similar Catalogs
	J/ApJ/841/84/table6		^(c)Galactic RR Lyrae sample (55 rows)
	J/ApJ/841/84/table7		^(c)Updated photometry for RR Lyrae in M4 (43 rows)
	J/ApJ/847/18	245		Mass, Z, dust attenuation, and SFR relations (Zahid+, 2017) ReadMe+ftp 2017ApJ...847...18Z Similar Catalogs
	J/ApJ/847/18/table2		MZ_* relation and attenuation data (Interactive plot) (25 rows)
	J/ApJ/847/18/table4		MZ_-SFR relation data (125 rows)*
	J/MNRAS/494/3342	4153		Stellar parameters from GALANTE (Lorenzo-Gutierrez+, 2020) ReadMe+ftp 2020MNRAS.494.3342L Similar Catalogs
	J/MNRAS/494/3342/tablea1		^(c)NGSL table (291 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

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

.errorfile=/tmp/VR4047327.err (2024-12-25T15:24:27)
-2
-kw.cat=18220105
-ref=VIZ676c23ac3dc1df

elapse time 1