VizieR

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

VizieR


  
J/A+A/695/A42
  Data collected for 4 ILRTs (Valerin+, 2025)
ReadMe+ftp
2025A&A...695A..42V
Similar Catalogs
Objects
Post annotation 		  
1.J/A+A/695/A42/tablea3Decline rates of AT 2019ahd (7 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)
  Name (char) SN name (meta.id;meta.main)
  Band (char) Name of the band (instr.bandpass)
  G1 10-2mag/dDecline rate between 0 and 45 days (src.var.amplitude)
  e_G1 10-2mag/dError on G1 (stat.error)
  G2 10-2mag/d(n) Decline rate between 45 and 105 days (src.var.amplitude)
  e_G2 10-2mag/d(n) Error on G2 (stat.error)
  G3 10-2mag/d(n) Decline rate beyond 105 days (src.var.amplitude)
  e_G3 10-2mag/d(n) Error on G3 (stat.error)

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/VR1930498.err (2025-07-12T19:32:24)
-3
-source=J/A+A/695/A42/tablea3
-ref=VIZ6872b8481d7502
elapse time 0