VizieR

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

VizieR

  
J/AJ/164/3
  34 Low-mass comoving systems astrometry using NSC DR2 (Kiwy+, 2022)
ReadMe+ftp
2022AJ....164....3K
Similar Catalogs
Post annotation 		img(gal)
1.J/AJ/164/3/table5Total masses, mass ratios, and binding energies (34 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)
  Num   [1/34] System number ID (meta.id;meta.number)
  Name (char) System identifier (meta.id;meta.main)
  Sep AU [322/8487] Projected physical separation (pos.angDistance)
  Mass1 Msun [0.08/0.7] Primary mass (Note 1)   (phys.mass)
  Mass2 Msun [0.03/0.12] Secondary mass estimate (Note 1)   (phys.mass)
  Mass Msun [0.13/0.71] Total mass (phys.mass)
  M2/M1   [0.06/0.91] Mass2/Mass1 ratio (meta.note)
  Ebin   [0.23/19.6] Binding energy, 1041erg (Note 2)   (meta.bib)
  SpT (char) Spectral type used to derive the secondary mass (src.spType)

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/VR247935.err (2025-12-06T09:53:00)
-3
-source=J/AJ/164/3/table5
-ref=VIZ6933fcfc3c87f
elapse time 2