VizieR

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

VizieR

  
J/ApJS/222/19
  KPNO spectroscopy of G & K dwarfs HIP stars (Kim+, 2016)
ReadMe+ftp
2016ApJS..222...19K
Similar Catalogs
Post annotation 		img(gal)
1.J/ApJS/222/19/table3*Stellar parameters derived using MOOG (Note) (87 rows)

Simple ConstraintList Of Constraints
 
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)
  HIP   [4907/118278] HIP number (meta.id;meta.main)
  f_HIP (char) [b] Flag on HIP (Note 1)   (meta.code)
  Teff K [4904/5949] Effective temperature (phys.temperature.effective)
  logg [cm/s2] [3.2/4.6] Log of surface gravity (phys.gravity)
  [Fe/H] [-] [-1.5/0.1] Abundance [Fe/H] (phys.abund.Fe)
  Vt km/s [0.8/1.7] Microturbulent velocity (phys.veloc)
  [Fe/H]c [-] [-1.4/0.2] Abundance [Fe/H] corrected (Note G1)   (phys.abund.Fe)
  e_[Fe/H] [-] [0.009/0.04] [Fe/H] uncertainty (stat.error;phys.abund.Fe)

ALL cols		    
 (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:
**** 
**** -- 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_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_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/VR1355780.err (2026-02-03T12:32:25)
-3
-source=J/ApJS/222/19/table3
-ref=VIZ6981ead914b004
elapse time 1