VizieR

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

VizieR

  
J/ApJS/268/54
  Continuous opt. monitoring of BL Lac from 2009-2021 (Xu+, 2023)
ReadMe+ftp
2023ApJS..268...54X
Similar Catalogs
Objects
timeSerie
Post annotation 		  
1.J/ApJS/268/54/table2Flare parameters used to fit the data (1108 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)
  JD d [2455128.9/2459206.0] Julian Date (time.epoch)
  ID   [1/7] Flare index identifier (meta.id)
  Band (char) Observational band (V, R or I) (meta.code;instr.filter)
  Center h [-3.1/14.7] Central time of the flare (time.epoch)
  Amp mJy [0.039/19.41] Flare amplitude in Band (src.var.amplitude)
  dN 10-5/s/m3 [0.08/161.5] Enhanced electron number density (meta.number;phys.density;phys.electron)
  Width h [0.25/5.72] Flare width/duration, {tau}flare (time.interval)
  Size AU [2.88/65.54] Size of the radiation region, Scell (Equation 3) (phys.size.radius)

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/VR2491508.err (2026-01-28T13:30:44)
-3
-source=J/ApJS/268/54/table2
-ref=VIZ697a0f84260474
elapse time 1