VizieR

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

VizieR

  
J/AJ/158/63
  Five new transiting hot Jupiters:HATS-54b-HATS-58b (Espinoza+, 2019)
ReadMe+ftp
2019AJ....158...63E
Similar Catalogs
Objects
Post annotation 		  
1.J/AJ/158/63/table4Relative radial velocities and bisector spans for HATS-54-HATS-58 (136 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)
  ID (char) Object identifier (HATS-54-HATS-58) (meta.id;meta.main)
  BJD d Barycentric Julian Date (Note G1)   (time.epoch)
  RV m/s [-515.34/482.36] Radial velocity (Note 1)   (phys.veloc;pos.heliocentric)
  e_RV m/s [6.6/59] The 1{sigma} uncertainty in RV (Note 2)   (stat.error)
  BS m/s [-129/197] Bisector span (phys.veloc)
  e_BS m/s [6/77] The 1{sigma} uncertainty in BS (stat.error)
  Phase  Orbital phase (time.phase)
  Inst (char) Instrument used (FEROS or HARPS) (instr.setup)

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/VR222495.err (2025-12-06T09:52:29)
-3
-source=J/AJ/158/63/table4
-ref=VIZ6933fcdd3651f
elapse time 1