VizieR

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

VizieR

  
J/MNRAS/368/253
  Faint emission lines in M16, M20, NGC 3603 (Garcia-Rojas+, 2006)
ReadMe+ftp
2006MNRAS.368..253G
Similar Catalogs
Objects
Post annotation 		  
1.J/MNRAS/368/253/table2Observed and reddening-corrected relative line fluxes F(Lambda) and I(Lambda), respectively. (754 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)
  Cluster (char) Cluster name (meta.id;meta.main)
  Lambda0 0.1nm (n) Laboratory wavelength (em.wl)
  Ion (char) Ion (phys.atmol.ionStage)
  Mult (char) Multiplet number (meta.id)
  LambdaObs 0.1nm (n) Observed wavelength in the heliocentric rest frame (em.wl;pos.heliocentric)
  F(Lambda)  (n) Observed flux relative to Hbeta (Note 1)   (phot.flux;arith.ratio)
  I(Lambda)  (n) Reddening-corrected flux relative to Hbeta (Note 1)   (phot.flux;arith.ratio)
  e_F(Lambda) % (n) Fractional error (1sigma) in the line intensities (stat.error)
  u_F(Lambda) (char) Uncertainty flag on F(Lambda) (meta.code.error)
  Notes (char) [b-g] Notes (Note 2)   (meta.note)

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/VR3961706.err (2026-01-28T15:12:16)
-3
-source=J/MNRAS/368/253
-ref=VIZ697a27503c736a
elapse time 1