VizieR

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

VizieR

  
J/A+A/363/1081
  Non-linear limb-darkening law for LTE models (Claret 2000)
ReadMe+ftp
2000A&A...363.1081C
Similar Catalogs
Post annotation 		  
1.J/A+A/363/1081/phoenibcLimb-darkening coefficients, PHOENIX models- bolometric, log [M/H] = 0.0, v.tu= 2 km/s (976 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)
  Coeff (char) [a-f u] Limb-darkening coefficient (Note G1)   (phot.limbDark)
  VT km/s microturbulent velocity (phys.veloc.microTurb)
  logg [cm/s+2] Surface gravity (phys.gravity)
  Teff K Effective temperature (phys.temperature.effective)
  log[M/H] [Sun] log [metal/H] (phys.abund.Z)
  Limb  Limb-darkening coefficient (Note 1)   (phot.limbDark)
  All  find limb-darkening coefficient in all models around these parameters (meta.ref)

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/VR2635699.err (2025-12-06T01:36:12)
-3
-source=J/A+A/363/1081/phoenibc
-ref=VIZ6933888c2837b3
elapse time 2