VizieR

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

Catalog


Simple TargetList Of TargetsFast Xmatch with large catalogs or Simbad
Target Name (resolved by Sesame) or Position:
 Target dimension:
NB: The epoch used for the query is the original epoch of the table(s)Radius Box size

  
J/A+A/620/A55
  Magnetic flaring from PMS stars spectra (Flaccomio+, 2018)
ReadMe+ftp
2018A&A...620A..55F
Similar Catalogs
spectrum
Post annotation 		img(gal)
1.J/A+A/620/A55/table1List of flares, deduced physical quantities, and host-star properties[spectrum] (78 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)
  spOpt  Show the CoRoT spectrum (meta.ref.url)
spectrum
  spXbl  Show the Chandra fixed duration spectrum (meta.ref.url)
spectrum
  spXbi  Show the Chandra natural binning spectrum (meta.ref.url)
spectrum
  spmIR  Show the Spitzer spectrum (meta.ref.url)
spectrum
  Src  Source number (meta.id)
  n_Src (char) [*yzx] Note on Source (Note 1)   (meta.note)
  Mon  Idenfication number from Cody et al., 2014, Cat. J/AJ/147/82, CSIMon-NNNNNN in Simbad (meta.id;meta.main)
  Obs (char) Chandra observation id number(s) during which the flare occurred (meta.id;obs)
  EX 10+28J Total emitted X-ray energy (Chandra) (em.energy)
  u_EX (char) Uncertainty flag on EX (meta.code.error)

ALL cols		    
 (i)indexed column
  LXpk 10+25W (n) Flare peak X-ray luminosity (Chandra) (phys.luminosity;em.X-ray)
  u_LXpk (char) Uncertainty flag on LXpk (meta.code.error)
  EOpt 10+28J (n) Optical energy (CoRoT) (phys.energy)
  u_EOpt (char) Uncertainty flag on EOpt (meta.code.error)
  LOptpk 10+25W (n) Flare peak optical luminosity (CoRoT) (phys.luminosity;em.opt)
  u_LOptpk (char) Uncertainty flag on LOptpk (meta.code.error)
  EIR 10+28J (n) Infrared energy (Spitzer) (phys.energy)
  u_EIR (char) Uncertainty flag on EIR (meta.code.error)
  LIRpk 10+25W (n) Flare peak infrared luminosity (Spitzer) (phys.luminosity;em.IR)
  u_LIRpk (char) Uncertainty flag on LIRpk (meta.code.error)
  Class (char) Class (meta.code.class)
  EWHa 0.1nm (n) Hα equivalent width (spect.line.eqWidth;em.line.Halpha)
  AV mag (n) Absorption in V band (phot.mag;em.opt.V)

ALL cols		    
(n) indicates a possible blank or NULL column(i)indexed column
  NH 10+22cm-2(n) Hydrogen column density (phys.columnDensity)
  SpType (char) MK spectral type (src.spType)
  Vmag mag (n) V magnitude (phot.mag;em.opt.V)
  Rmag mag (n) R magnitude (phot.mag;em.opt.R)
  Imag mag (n) I magnitude (phot.mag;em.opt.I)
  CoRoT (char) CoRoT light curve type (meta.code)
  Prot d (n) Rotational period (time.period)
  FOpt (char) FileName of optical spectrum, in subdirectory opt (meta.id;meta.file)
  FXbi (char) FileName of Chandra spectrum fixed bin duration, in subdirectory xbi (meta.id;meta.file)
  FXbl (char) FileName of Chandra spectrum "natural binning", in subdirectory xbl (meta.id;meta.file)
  FmIR (char) FileName of Spitzer spectrum, in subdirectory mir (meta.id;meta.file)
  Simbad  ask the Simbad data-base about this object (meta.ref.url)
  _RA deg (n)(i) Right Ascension (J2000) from SIMBAD (not part of the original data) (pos.eq.ra;meta.main)
  _DE deg (n)(i) Declination (J2000) from SIMBAD (not part of the original data) (pos.eq.dec;meta.main)

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/VR663304.err (2025-07-13T00:40:36)
-2
-source=J/A+A/620/A55/table1
-ref=VIZ68730084a1f08
elapse time 1