VizieR

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

VizieR


  
VI/153
  K-shell photoabsorption and photoionization (Mendoza+, 2016-18)
ReadMe+ftp
2018yCat.6153....0M
Similar Catalogs
database
Post annotation 		  
1.VI/153/table5Energy-level data for photon states (20≤N≤26) (392 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)
  Z   [22/30] Atomic number (meta.id;meta.main)
  N   [20/26] Target+e electron number (meta.id)
  i   [1/16] Target level i (meta.id)
  2S+1   [1/6] Spin multiplicity (phys.atmol.qn)
  L   [0/6] Total orbital angular momentum quantum number (phys.atmol.qn)
  Pi   [0/1] Parity quantum number (0= even, 1= odd) (phys.atmol.parity)
  Lev   [1/3] Level index with an (S,L,Pi) series (phys.atmol.qn)
  Conf (char) Electron configuration (phys.atmol.configuration)
  Term (char) Spectroscopic term assignment (phys.atmol.term)
  E Ry Level energy (phys.energy;phys.atmol.level)

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/VR4068291.err (2025-07-12T18:28:24)
-3
-source=VI/153/table5
-ref=VIZ6872a9493e13c3
elapse time 1