VizieR

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

VizieR

  
J/AJ/132/1910
  HD 131861 radial velocities and VRI light curves (Fekel+, 2006)
ReadMe+ftp
2006AJ....132.1910F
Similar Catalogs
Objects
timeSerie
Post annotation 		  
1.J/AJ/132/1910/table1Radial velocities of HD 131861 [timeSerie](Plot of the Velocity Curve) (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)
  HJD d Heliocentric Julian date (time.epoch)
  n_HJD (char) [b] b: Lithium region ({lambda}=6700Å) (meta.note)
  phiL   [0/1] Phase in the long-period orbit (time.phase)
  phiS   ]0/1[ Phase in the short-period orbit (time.phase)
  RVAa km/s Aa component radial velocity (spect.dopplerVeloc;pos.heliocentric)
  (O-C)Aa km/s Aa component observed minus Computer radial velocity (phys.veloc;arith.diff)
  RVAb km/s (n) Ab component radial velocity (spect.dopplerVeloc;pos.heliocentric)
  n_RVAb (char) [a] a: 3{sigma} residual, velocity given zero weight. (meta.note)
  (O-C)Ab km/s (n) Ab component Observed minus Computer radial velocity (phys.veloc;arith.diff)
  Obs (char) Onservatory (HPO or KPNO) (meta.id;instr.obsty)

ALL cols		    
(n) indicates a possible blank or NULL column(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/VR494737.err (2025-12-06T18:43:06)
-3
-source=J/AJ/132/1910/table1
-ref=VIZ6934793a78c91
elapse time 1