VizieR

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

VizieR

  
J/AJ/156/33
  Resonance sticking in the population of scattering TNOs (Yu+, 2018)
ReadMe+ftp
2018AJ....156...33Y
Similar Catalogs
Post annotation 		  
1.J/AJ/156/33/table3Summary of normalized transient resonance fractions and predicted absolute transient sticking populations for the range 30<a<100 au (194 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)
  p (char) p resonance (Note 1)   (stat.param)
  q (char) q resonance (Note 1)   (stat.param)
  a AU [0/99.26] Semimajor axis (phys.size.smajAxis)
  fsr   [2.362082e-06/0.4032886] Fraction of scattering+stuck population (stat.param)
  fr   [5.857051e-06/1] Fraction of stuck population (stat.param)
  fs   [3.958499e-06/0.6758519] Fraction of scattering population (stat.param)
  N ct [0/7434.4] Predicted number with an H-magnitude cut Hr<8.66 (meta.id;meta.main)

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_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/VR3299459.err (2026-06-09T12:54:52)
-3
-source=J/AJ/156/33/table3
-ref=VIZ6a280d1c325883
elapse time 2