This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 22 05.09 +44 08 44.5 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS 3656996,2461146.9499,9.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 3656996 20260416.4499 9.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 10 54.80 +48 15 31.2 10.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
LD 323,2461146.9499,10.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
LD 323 20260416.4499 10.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 10 37.61 +49 23 31.4 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,12.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 12.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 13 57.74 +43 42 19.8 11.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 385455039732447488,2461146.9499,11.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 385455039732447488 20260416.4499 11.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 06 40.09 +46 03 37.2 11.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 50 38.16 +47 30 33.1 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.6529+47.5164,2461146.9499,11.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.6529+47.5164 20260416.4499 11.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 05 31.34 +48 29 21.7 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 393374787630869888,2461146.9499,11.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 393374787630869888 20260416.4499 11.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 05 48.13 +45 47 26.4 11.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 09 56.69 +46 22 44.1 11.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 50 07.88 +47 35 52.2 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.5345+47.5961,2461146.9499,11.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.5345+47.5961 20260416.4499 11.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 18 30.30 +43 59 39.7 11.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.6157+43.9987,2461146.9499,11.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J004.6157+43.9987 20260416.4499 11.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 16 48.15 +49 29 26.7 11.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 01 31.88 +47 56 36.0 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 05 50.27 +49 36 52.8 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 06 30.22 +47 25 00.8 11.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 393033492346401536,2461146.9499,11.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 393033492346401536 20260416.4499 11.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 54 40.31 +49 16 56.3 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1940649572198432128,2461146.9499,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1940649572198432128 20260416.4499 11.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 02 17.43 +44 32 06.3 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 10 11.79 +47 19 01.2 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 04 29.49 +46 25 05.3 11.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 387081183070276096,2461146.9499,11.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 387081183070276096 20260416.4499 11.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 06 11.64 +47 44 10.0 12.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,12.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 12.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 05 35.17 +43 22 52.9 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 05 30.39 +46 40 47.3 12.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,11.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 11.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 53 48.05 +50 06 35.6 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,12.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 12.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 51 41.04 +50 05 56.0 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1940901910117535232,2461146.9499,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1940901910117535232 20260416.4499 12.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 08 32.23 +46 07 25.2 12.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9499,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4499 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 26 51.23 +49 10 15.0 9.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 391213216488083712,2461146.9499,9.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 391213216488083712 20260416.4499 9.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 13 52.39 +45 26 33.0 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0456 And,2461146.9499,9.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0456 And 20260416.4499 9.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 20 45.33 +43 21 20.4 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J002045.50+432119.4,2461146.9499,9.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J002045.50+432119.4 20260416.4499 9.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 17 10.59 +42 14 42.3 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J001710.77+421440.5,2461146.9499,11.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J001710.77+421440.5 20260416.4499 11.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 21 48.83 +44 52 18.2 10.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0021489+445219,2461146.9499,10.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0021489+445219 20260416.4499 10.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 19 50.19 +47 42 37.5 10.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0960 Cas,2461146.9499,10.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0960 Cas 20260416.4499 10.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 23 50 36.36 +47 31 26.2 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.6529+47.5164,2461146.9499,10.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.6529+47.5164 20260416.4499 10.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 14 20.20 +44 20 30.1 9.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS 3649712,2461146.9499,8.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 3649712 20260416.4499 8.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4499* 00 13 17.38 +46 24 54.9 8.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J001317.58+462456.0,2461146.9499,8.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J001317.58+462456.0 20260416.4499 8.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461146.95017204 16.04.2026 10:48:04.864 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 12
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.88
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 6 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 19932
Objects passed selection criteria: 19866
Measurements per detected object (mean, median, min, max): 2.8 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.8 2.0 2 4
Average stars detected per image: 14731
Average stars matched: 13244.2 (89.9073 %)
Memory usage VmPeak: 121820 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 16 05:53:00 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461146.95017204 16.04.2026 10:48:04.864 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 110
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.48
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 70 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 2.0 # minimum number of pixels above threshold
DETECT_THRESH 3.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 3.0 # or , in mag.arcsec-2
SATUR_LEVEL 57000.0 # level (in ADUs) at which arises saturation
GAIN 0.83 # detector gain in e-/ADU
WEIGHT_TYPE BACKGROUND
Total objects detected (at least 2 times): 119775
Objects passed selection criteria: 119431
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 87631.2
Average stars matched: 79269.5 (90.458 %)
Memory usage VmPeak: 1941720 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 16 05:56:11 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_onlybrightstars_v1
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461146.94953944
Re-using ../asassn_transients_list.txt
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
Re-using ../tocp_transients_list.txt
'../tocp_transients_list.txt' -> 'tocp_transients_list.txt'
Re-using ../tns_transients_list.txt
'../tns_transients_list.txt' -> 'tns_transients_list.txt'
Plate-solving the images
wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
Saving wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits to local_wcs_cache/
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
Saving wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits to local_wcs_cache/
'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits exists and is non-empty
Saving wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits to local_wcs_cache/
'wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits'
wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits exists and is non-empty
Saving wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits to local_wcs_cache/
'wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits (1st new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Image size: 903.1'x622.3' 15.1(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.66"/pix along the X axis and 5.85"/pix along the Y axis
Image center: 00:00:00.311 +45:59:52.87 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:00.311 +45:59:52.87
Angular distance between the image centers 0.0625 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits (2nd new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Image size: 938.8'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 00:00:03.207 +45:59:58.98 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:03.207 +45:59:58.98
Angular distance between the image centers 0.0561 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 00:00:00.311 +45:59:52.87
Second-epoch second image center 00:00:03.207 +45:59:58.98
Angular distance between the image centers 0.00855 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.5G2iOIlmIm
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.vcIqMy6Egc
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits &> /tmp/tmp.I1tQLSLefP
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits &> /tmp/tmp.tBmzmgb525
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 21978 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0038 to 359.9998 deg, Dec +39.9518 to +51.2135 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0038 to 359.9998 deg, Dec 39.9518 to 51.2135 deg
Loaded 169717 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 58 out of 66 total matches.
Matched with Tycho-2 66 out of 21978 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.835338
a=0.000000 b=1.000000 c=22.835338
From vast_summary.log: estimated ref. image limiting mag.: -7.88
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.96
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.96
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 10 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.5 pix And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.5 pix And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
3.2 pix fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
3.2 pix fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Limiting magnitude estimates:
15.0 mag. And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
15.0 mag. And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
14.4 mag. fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
14.4 mag. fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
All-image limiting magnitude estimate: 14.4 (SNR ) 11.7 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.5G2iOIlmIm (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2256, passed=21978
Got 21978 stars (including 19693 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 21978 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4507 through 0 to 12.6948, gap 12.6948 to 348.4507
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 203 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 146 matched stars entering correct_measured_positions(), 68 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.79"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 2320 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.33"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4573 through 0 to 12.6998, gap 12.6998 to 348.4573
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 230 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2338 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.32"
Accuracy estimation diagnostic: 173 matched stars entering correct_measured_positions(), 3009 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.42"
Excluding outliers - 173 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.vcIqMy6Egc (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2250, passed=22050
Got 22050 stars (including 19777 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 22050 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4512 through 0 to 12.6947, gap 12.6947 to 348.4512
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 202 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 142 matched stars entering correct_measured_positions(), 69 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.99"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 135 matched stars entering correct_measured_positions(), 2248 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.05"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4583 through 0 to 12.7006, gap 12.7006 to 348.4583
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 223 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2273 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.04"
Accuracy estimation diagnostic: 172 matched stars entering correct_measured_positions(), 3100 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.65"
Excluding outliers - 172 stars left (next iteration limit 148)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.I1tQLSLefP (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat
SExtractor catalog parsing summary: zero_flux=1, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1107, passed=15224
Got 15224 stars (including 14111 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat
util/solve_plate_with_UCAC5 got 15224 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 903.1'
Seting catalog search parameters based on the expected field of view 903.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012543 (45.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010034 (36.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.0181 through 0 to 12.0350, gap 12.0350 to 348.0181
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 497 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 462 matched stars entering correct_measured_positions(), 405 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 460 matched stars entering correct_measured_positions(), 6823 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.75"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.0100 through 0 to 12.0356, gap 12.0356 to 348.0100
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 519 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 495 matched stars entering correct_measured_positions(), 6838 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.59"
Accuracy estimation diagnostic: 495 matched stars entering correct_measured_positions(), 7334 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.83"
Excluding outliers - 495 stars left (next iteration limit 506)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits -region wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.tBmzmgb525 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1162, passed=15260
Got 15260 stars (including 14090 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat
util/solve_plate_with_UCAC5 got 15260 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.8'
Seting catalog search parameters based on the expected field of view 938.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013039 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010431 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.5539 through 0 to 12.1248, gap 12.1248 to 347.5539
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 916 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 14766 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.00"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.5537 through 0 to 12.1281, gap 12.1281 to 347.5537
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.2 to 51.3)
Done reading UCAC5 zone files...
Matched 938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 14763 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.00"
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 14749 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.07"
Excluding outliers - 937 stars left (next iteration limit 1031)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits -region wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits'
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits'
Preparing the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_gaiadr2.txt__out31747.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out34647.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out07730.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out15590.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 5s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 2s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31672_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 31672_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (228.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31747_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 31747_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:12:06.52 +48:12:19.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=10.11, MAG_FAINT_SEARCH_LIMIT=11.09)GAIADR2_OUTPUT=# 3.917 393128015988361216 003.02811802971 +48.20624549159 9.0607 7.6189 VARIABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.917#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32670_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 32670_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (141.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33456_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 33456_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (212.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34647_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 34647_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:07:16.98 +50:09:15.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.85, MAG_FAINT_SEARCH_LIMIT=12.83)GAIADR2_OUTPUT=# 4.142 393772913918680576 001.82106204253 +50.15554967586 10.9894 9.6130 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.142#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 12192_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 12192_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (191.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15590_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 15590_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18018_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 18018_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (79.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 19449_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 19449_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:04:30.21 +42:07:14.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 07730_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 07730_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 7s
Prepared the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:10:54.80 +48:15:31.2
00:22:05.09 +44:08:44.5
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Creating symlink local_wcs_cache/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Creating symlink local_wcs_cache/exclusion_list.txt
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
Plate-solving the images
wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits exists and is non-empty
wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits (1st new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Image size: 903.1'x622.3' 15.1(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.66"/pix along the X axis and 5.85"/pix along the Y axis
Image center: 00:00:00.311 +45:59:52.87 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:00.311 +45:59:52.87
Angular distance between the image centers 0.0625 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits (2nd new image)
verification OK: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Image size: 938.8'x624.2' 15.6(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.86"/pix along the Y axis
Image center: 00:00:03.207 +45:59:58.98 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:03.207 +45:59:58.98
Angular distance between the image centers 0.0561 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 00:00:00.311 +45:59:52.87
Second-epoch second image center 00:00:03.207 +45:59:58.98
Angular distance between the image centers 0.00855 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.iSxkPN52jP
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.4D3yL6Jmts
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits &> /tmp/tmp.viJMe7cyb0
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits &> /tmp/tmp.9gJog6WDzD
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 142009 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 359.9998 deg, Dec +39.9057 to +51.2155 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0001 to 359.9998 deg, Dec 39.9057 to 51.2155 deg
Loaded 170564 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 91 out of 117 total matches.
Matched with Tycho-2 117 out of 142009 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 21.227567
a=0.000000 b=1.000000 c=21.227567
From vast_summary.log: estimated ref. image limiting mag.: -7.48
Updating vast_summary.log: Estimated ref. image limiting mag.: 13.75
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 13.75
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 79 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.2 pix And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.2 pix And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
3.3 pix fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
3.2 pix fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Limiting magnitude estimates:
13.7 mag. And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
13.7 mag. And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
12.9 mag. fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
12.9 mag. fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
All-image limiting magnitude estimate: 12.9 (SNR ) 12.3 (80% of stars) with default.sex.telephoto_lens_vSTL
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.iSxkPN52jP (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=47, blended=18012, passed=141962
Got 141962 stars (including 123722 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 141962 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4418 through 0 to 12.7147, gap 12.7147 to 348.4418
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 204 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 151 matched stars entering correct_measured_positions(), 79 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 145 matched stars entering correct_measured_positions(), 15623 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.14"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4528 through 0 to 12.7273, gap 12.7273 to 348.4528
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 220 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 178 matched stars entering correct_measured_positions(), 15632 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.13"
Accuracy estimation diagnostic: 177 matched stars entering correct_measured_positions(), 18852 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.12"
Excluding outliers - 177 stars left (next iteration limit 159)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.4D3yL6Jmts (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=51, blended=18105, passed=141752
Got 141752 stars (including 123429 good ones) from the SExtractor catalog wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 141752 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4216 through 0 to 12.6947, gap 12.6947 to 348.4216
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 199 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 147 matched stars entering correct_measured_positions(), 78 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.76"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 15342 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.76"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4333 through 0 to 12.6945, gap 12.6945 to 348.4333
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 222 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 177 matched stars entering correct_measured_positions(), 15356 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.73"
Accuracy estimation diagnostic: 176 matched stars entering correct_measured_positions(), 20031 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.04"
Excluding outliers - 176 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.viJMe7cyb0 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=6, blended=8447, passed=73797
Got 73797 stars (including 65285 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat
util/solve_plate_with_UCAC5 got 73797 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 903.1'
Seting catalog search parameters based on the expected field of view 903.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012543 (45.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010034 (36.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.9589 through 0 to 12.0879, gap 12.0879 to 347.9589
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 472 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 441 matched stars entering correct_measured_positions(), 386 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.64"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 440 matched stars entering correct_measured_positions(), 31757 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.41"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.9502 through 0 to 12.0880, gap 12.0880 to 347.9502
Reading UCAC5 zone files...
Searching UCAC5 zones 651 to 708 (Dec 40.3 to 51.3)
Done reading UCAC5 zone files...
Matched 489 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 464 matched stars entering correct_measured_positions(), 31772 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.40"
Accuracy estimation diagnostic: 464 matched stars entering correct_measured_positions(), 35008 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.80"
Excluding outliers - 464 stars left (next iteration limit 484)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits -region wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.9gJog6WDzD (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS-calibrated image found: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Checking if the catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat corresponding to the image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
WCS catalog name: wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=6, blended=8833, passed=75096
Got 75096 stars (including 66201 good ones) from the SExtractor catalog wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat
util/solve_plate_with_UCAC5 got 75096 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.8'
Seting catalog search parameters based on the expected field of view 938.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013039 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010431 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.5276 through 0 to 12.2262, gap 12.2262 to 347.5276
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.1 to 51.3)
Done reading UCAC5 zone files...
Matched 935 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 935 matched stars entering correct_measured_positions(), 908 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 935 matched stars entering correct_measured_positions(), 72784 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.94"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 347.5270 through 0 to 12.2272, gap 12.2272 to 347.5270
Reading UCAC5 zone files...
Searching UCAC5 zones 650 to 708 (Dec 40.1 to 51.3)
Done reading UCAC5 zone files...
Matched 935 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 72786 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.94"
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 72742 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.04"
Excluding outliers - 934 stars left (next iteration limit 1028)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits -region wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_And-01-Q2b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Saving fully-calibrated image wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_And-01-Q2b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_fd_And-01-Q2b1x1_2026-04-16_05-47-10_20.00sec_-4.90C_LIGHT_0436.fits
Saving fully-calibrated image wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q2b1x1_054849_TTUQ2b1x1_20827_evG3WOlY/wcs_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437.fits
Preparing the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_gaiadr2.txt__out162613.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out108598.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out125310.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out137934.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161718.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161730.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out161740.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out168094.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out168507.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out171268.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172539.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out173412.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174113.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174719.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out174889.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175163.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175469.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176424.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176554.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176556.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176717.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177203.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177340.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177595.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177762.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178018.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out179059.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out24383.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52886.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out59955.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out70846.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out85909.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out91789.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 64s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 19s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161714_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 161714_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (272.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161718_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 161718_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161725_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 161725_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (68.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161730_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 161730_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161740_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 161740_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161744_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 161744_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (223.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161745_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 161745_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (159.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 162586_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 162586_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (228.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 162613_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 162613_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:12:06.52 +48:12:20.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN= 8.70, MAG_FAINT_SEARCH_LIMIT=9.68)GAIADR2_OUTPUT=# 3.300 393128015988361216 003.02811802971 +48.20624549159 9.0607 7.6189 VARIABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.300#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 163510_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 163510_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (141.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166623_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 166623_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (296.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167509_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 167509_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (86.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167893_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 167893_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (411.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168094_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 168094_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168475_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 168475_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (476.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168507_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 168507_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 169862_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 169862_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (147.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170216_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 170216_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (64.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170264_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 170264_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (284.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171268_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 171268_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171536_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 171536_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (416.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171673_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 171673_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (305.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172539_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 172539_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172645_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 172645_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (162.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173000_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 173000_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (38.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173142_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 173142_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (146.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173156_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 173156_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (85.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173412_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 173412_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173628_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 173628_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:13:03.09 +49:56:52.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173768_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 173768_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (304.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174113_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 174113_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174344_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 174344_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (522.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174645_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 174645_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (30.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174676_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 174676_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (45.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174719_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 174719_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174889_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 174889_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175163_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 175163_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175332_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 175332_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175469_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 175469_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176075_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 176075_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (277.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176179_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 176179_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (153.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176424_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 176424_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176554_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 176554_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176556_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 176556_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176702_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 176702_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176717_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 176717_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177060_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177060_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177098_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177098_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (175.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177203_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 177203_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177204_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177204_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:17:16.74 +47:55:48.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177215_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177215_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (197.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177297_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177297_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (228.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177313_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177313_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (320.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177340_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 177340_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177595_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 177595_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177762_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 177762_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177795_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177795_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (295.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177819_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177819_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (191.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177882_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 177882_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (387.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178018_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 178018_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179059_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 179059_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24383_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 24383_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46096_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 46096_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:10:55.11 +48:15:29.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 85909_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 85909_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137188_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 137188_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:22:04.62 +44:08:42.8 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125310_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 125310_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 108598_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 108598_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91789_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 91789_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52886_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 52886_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 59955_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 59955_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 126089_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 126089_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (153.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 116114_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 116114_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (145.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137934_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 137934_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 76104_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 76104_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (191.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57324_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 57324_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (197.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 70846_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
Preparing report for the candidate 70846_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 77205_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 77205_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (403.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 118010_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 118010_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
Rejecting candidate due to large distance (79.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 117622_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437
The candidate 117622_fd_And-01-Q2b1x1_2026-04-16_05-48-04_20.00sec_-5.00C_LIGHT_0437 did not pass the final checks
**** FOUND 00:04:30.43 +42:07:13.9 in the exclusion list exclusion_list_bsc.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 1s
make_report_in_HTML.sh TOTAL: 84s
Prepared the HTML report for the field And-01-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:10:54.80 +48:15:31.2
00:22:05.09 +44:08:44.5
00:17:10.59 +42:14:42.3
00:20:45.33 +43:21:20.4
00:14:20.20 +44:20:30.1
00:10:37.61 +49:23:31.4
00:13:57.74 +43:42:19.8
00:06:40.09 +46:03:37.2
23:50:38.16 +47:30:33.1
00:05:31.34 +48:29:21.7
00:05:48.13 +45:47:26.4
00:09:56.69 +46:22:44.1
23:50:07.88 +47:35:52.2
00:18:30.30 +43:59:39.7
00:16:48.15 +49:29:26.7
00:01:31.88 +47:56:36.0
00:05:50.27 +49:36:52.8
00:06:30.22 +47:25:00.8
23:54:40.31 +49:16:56.3
00:02:17.43 +44:32:06.3
00:10:11.79 +47:19:01.2
00:04:29.49 +46:25:05.3
00:06:11.64 +47:44:10.0
00:05:35.17 +43:22:52.9
00:05:30.39 +46:40:47.3
23:53:48.05 +50:06:35.6
23:51:41.04 +50:05:56.0
00:08:32.23 +46:07:25.2
00:26:51.23 +49:10:15.0
00:19:50.19 +47:42:37.5
23:50:36.36 +47:31:26.2
00:13:17.38 +46:24:54.9
00:13:52.39 +45:26:33.0
00:21:48.83 +44:52:18.2
########### Completed And-01-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
00:22:05.09 +44:08:44.5
00:10:54.80 +48:15:31.2
00:10:37.61 +49:23:31.4
00:13:57.74 +43:42:19.8
00:06:40.09 +46:03:37.2
23:50:38.16 +47:30:33.1
00:05:31.34 +48:29:21.7
00:05:48.13 +45:47:26.4
00:09:56.69 +46:22:44.1
23:50:07.88 +47:35:52.2
00:18:30.30 +43:59:39.7
00:16:48.15 +49:29:26.7
00:01:31.88 +47:56:36.0
00:05:50.27 +49:36:52.8
00:06:30.22 +47:25:00.8
23:54:40.31 +49:16:56.3
00:02:17.43 +44:32:06.3
00:10:11.79 +47:19:01.2
00:04:29.49 +46:25:05.3
00:06:11.64 +47:44:10.0
00:05:35.17 +43:22:52.9
00:05:30.39 +46:40:47.3
23:53:48.05 +50:06:35.6
23:51:41.04 +50:05:56.0
00:08:32.23 +46:07:25.2
00:26:51.23 +49:10:15.0
00:13:52.39 +45:26:33.0
00:20:45.33 +43:21:20.4
00:17:10.59 +42:14:42.3
00:21:48.83 +44:52:18.2
00:19:50.19 +47:42:37.5
23:50:36.36 +47:31:26.2
00:14:20.20 +44:20:30.1
00:13:17.38 +46:24:54.9
###################################################################################
00:22:05.09 +44:08:44.5 -- not an asteroid (will add it to exclusion list)
00:10:54.80 +48:15:31.2 -- not an asteroid (will add it to exclusion list)
00:10:37.61 +49:23:31.4 -- not an asteroid (will add it to exclusion list)
00:13:57.74 +43:42:19.8 -- not an asteroid (will add it to exclusion list)
00:06:40.09 +46:03:37.2 -- not an asteroid (will add it to exclusion list)
23:50:38.16 +47:30:33.1 -- not an asteroid (will add it to exclusion list)
00:05:31.34 +48:29:21.7 -- not an asteroid (will add it to exclusion list)
00:05:48.13 +45:47:26.4 -- not an asteroid (will add it to exclusion list)
00:09:56.69 +46:22:44.1 -- not an asteroid (will add it to exclusion list)
23:50:07.88 +47:35:52.2 -- not an asteroid (will add it to exclusion list)
00:18:30.30 +43:59:39.7 -- not an asteroid (will add it to exclusion list)
00:16:48.15 +49:29:26.7 -- not an asteroid (will add it to exclusion list)
00:01:31.88 +47:56:36.0 -- not an asteroid (will add it to exclusion list)
00:05:50.27 +49:36:52.8 -- not an asteroid (will add it to exclusion list)
00:06:30.22 +47:25:00.8 -- not an asteroid (will add it to exclusion list)
23:54:40.31 +49:16:56.3 -- not an asteroid (will add it to exclusion list)
00:02:17.43 +44:32:06.3 -- not an asteroid (will add it to exclusion list)
00:10:11.79 +47:19:01.2 -- not an asteroid (will add it to exclusion list)
00:04:29.49 +46:25:05.3 -- not an asteroid (will add it to exclusion list)
00:06:11.64 +47:44:10.0 -- not an asteroid (will add it to exclusion list)
00:05:35.17 +43:22:52.9 -- not an asteroid (will add it to exclusion list)
00:05:30.39 +46:40:47.3 -- not an asteroid (will add it to exclusion list)
23:53:48.05 +50:06:35.6 -- not an asteroid (will add it to exclusion list)
23:51:41.04 +50:05:56.0 -- not an asteroid (will add it to exclusion list)
00:08:32.23 +46:07:25.2 -- not an asteroid (will add it to exclusion list)
00:26:51.23 +49:10:15.0 -- not an asteroid (will add it to exclusion list)
00:13:52.39 +45:26:33.0 -- not an asteroid (will add it to exclusion list)
00:20:45.33 +43:21:20.4 -- not an asteroid (will add it to exclusion list)
00:17:10.59 +42:14:42.3 -- not an asteroid (will add it to exclusion list)
00:21:48.83 +44:52:18.2 -- not an asteroid (will add it to exclusion list)
00:19:50.19 +47:42:37.5 -- not an asteroid (will add it to exclusion list)
23:50:36.36 +47:31:26.2 -- not an asteroid (will add it to exclusion list)
00:14:20.20 +44:20:30.1 -- not an asteroid (will add it to exclusion list)
00:13:17.38 +46:24:54.9 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:01:31.88 +47:56:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:17.43 +44:32:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:29.49 +46:25:05.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:30.39 +46:40:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:31.34 +48:29:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:35.17 +43:22:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:48.13 +45:47:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:50.27 +49:36:52.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:11.64 +47:44:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:30.22 +47:25:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:40.09 +46:03:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:32.23 +46:07:25.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:56.69 +46:22:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:11.79 +47:19:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:37.61 +49:23:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:54.80 +48:15:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:17.38 +46:24:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:52.39 +45:26:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:57.74 +43:42:19.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:20.20 +44:20:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:48.15 +49:29:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:10.59 +42:14:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:30.30 +43:59:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:50.19 +47:42:37.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:45.33 +43:21:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:48.83 +44:52:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:05.09 +44:08:44.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:51.23 +49:10:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:07.88 +47:35:52.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:36.36 +47:31:26.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:38.16 +47:30:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:41.04 +50:05:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:48.05 +50:06:35.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:40.31 +49:16:56.3 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:01:31.88 +47:56:36.0 -- not a known variable star
00:02:17.43 +44:32:06.3 -- not a known variable star
00:04:29.49 +46:25:05.3 -- not a known variable star
00:05:30.39 +46:40:47.3 -- not a known variable star
00:05:31.34 +48:29:21.7 -- not a known variable star
00:05:35.17 +43:22:52.9 -- not a known variable star
00:05:48.13 +45:47:26.4 -- not a known variable star
00:05:50.27 +49:36:52.8 -- not a known variable star
00:06:11.64 +47:44:10.0 -- not a known variable star
00:06:30.22 +47:25:00.8 -- a known variable star
00:06:40.09 +46:03:37.2 -- not a known variable star
00:08:32.23 +46:07:25.2 -- not a known variable star
00:09:56.69 +46:22:44.1 -- not a known variable star
00:10:11.79 +47:19:01.2 -- not a known variable star
00:10:37.61 +49:23:31.4 -- not a known variable star
00:10:54.80 +48:15:31.2 -- a known variable star
00:13:17.38 +46:24:54.9 -- a known variable star
00:13:52.39 +45:26:33.0 -- a known variable star
00:13:57.74 +43:42:19.8 -- a known variable star
00:14:20.20 +44:20:30.1 -- a known variable star
00:16:48.15 +49:29:26.7 -- not a known variable star
00:17:10.59 +42:14:42.3 -- a known variable star
00:18:30.30 +43:59:39.7 -- not a known variable star
00:19:50.19 +47:42:37.5 -- a known variable star
00:20:45.33 +43:21:20.4 -- a known variable star
00:21:48.83 +44:52:18.2 -- a known variable star
00:22:05.09 +44:08:44.5 -- a known variable star
00:26:51.23 +49:10:15.0 -- a known variable star
23:50:07.88 +47:35:52.2 -- not a known variable star
23:50:36.36 +47:31:26.2 -- not a known variable star
23:50:38.16 +47:30:33.1 -- not a known variable star
23:51:41.04 +50:05:56.0 -- not a known variable star
23:53:48.05 +50:06:35.6 -- not a known variable star
23:54:40.31 +49:16:56.3 -- a known variable star
Found 21 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
34 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
###################################################################################
Adding identified Gaia sources from exclusion_list_gaiadr2.txt
exclusion_list_apass.txt NOT FOUND
IS_THIS_TEST_RUN= NO ALLOW_EXCLUSION_LIST_UPDATE= YES
#### Adding the following to the exclusion list ####
00:01:31.88 +47:56:36.0
00:02:17.43 +44:32:06.3
00:04:29.49 +46:25:05.3
00:05:30.39 +46:40:47.3
00:05:31.34 +48:29:21.7
00:05:35.17 +43:22:52.9
00:05:48.13 +45:47:26.4
00:05:50.27 +49:36:52.8
00:06:11.64 +47:44:10.0
00:06:30.22 +47:25:00.8
00:06:40.09 +46:03:37.2
00:08:32.23 +46:07:25.2
00:09:56.69 +46:22:44.1
00:10:11.79 +47:19:01.2
00:10:37.61 +49:23:31.4
00:10:54.80 +48:15:31.2
00:13:17.38 +46:24:54.9
00:13:52.39 +45:26:33.0
00:13:57.74 +43:42:19.8
00:14:20.20 +44:20:30.1
00:16:48.15 +49:29:26.7
00:17:10.59 +42:14:42.3
00:18:30.30 +43:59:39.7
00:19:50.19 +47:42:37.5
00:20:45.33 +43:21:20.4
00:21:48.83 +44:52:18.2
00:22:05.09 +44:08:44.5
00:26:51.23 +49:10:15.0
23:50:07.88 +47:35:52.2
23:50:36.36 +47:31:26.2
23:50:38.16 +47:30:33.1
23:51:41.04 +50:05:56.0
23:53:48.05 +50:06:35.6
23:54:40.31 +49:16:56.3
00:12:06.52 +48:12:19.3
00:07:16.98 +50:09:15.9
00:12:06.52 +48:12:20.1
####################################################
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461146.94953944 -observatory V36
00:09:40.76 -01:48:34.9 Mercury (0.0mag)
03:10:51.16 +18:01:30.9 Venus (-3.9mag)
00:19:07.38 +01:00:19.0 Mars (1.2mag)
07:12:50.14 +22:45:52.9 Jupiter (-2.1mag)
00:29:22.96 +00:50:13.7 Saturn (0.9mag)
03:47:47.52 +19:47:46.6 Uranus (5.8mag)
00:10:53.97 -00:15:00.1 Neptune (7.8mag)
20:33:46.47 -22:52:37.2 Pluto (14.5mag)
00:42:26.21 +06:48:05.3 Moon (-8.4mag)
-rw-r--r-- 1 apache apache 361 Apr 16 05:53 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461146.94953944:
07:12:57.94 +22:45:37.3 Io (5.8mag)
07:13:00.97 +22:45:31.2 Europa (5.9mag)
07:13:03.41 +22:45:19.7 Ganymede (5.4mag)
07:13:25.33 +22:44:39.7 Callisto (6.6mag)
07:16:09.22 +22:33:17.9 Himalia (15.3mag)
07:12:52.42 +22:45:49.8 Thebe (16.2mag)
07:16:21.18 +23:03:31.3 Elara (17.3mag)
07:11:44.90 +23:25:39.1 Pasiphae (17.4mag)
07:21:09.27 +22:43:56.8 Carme (18.5mag)
00:29:22.13 +00:50:40.8 Titan (8.8mag)
00:29:23.38 +00:50:14.6 Rhea (10.1mag)
00:29:02.21 +00:50:18.8 Iapetus (11.5mag)
00:29:29.66 +00:50:35.5 Hyperion (14.8mag)
00:30:59.49 +00:58:59.0 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 16 05:53 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461146.94953944:
15:39:11.60 -16:36:27.8 JWST
15:31:40.11 +52:46:55.4 Chandra
09:08:23.58 -52:07:47.4 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 16 05:53 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461146.94953944 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:52:10.98 -28:48:21.1 13.9mag P/2010 H2 (Vales)
05:07:03.61 -69:38:25.8 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:32:32.68 +31:26:25.2 17.2mag C/2017 K2 (PANSTARRS)
17:30:23.35 +10:36:03.2 17.6mag C/2021 G2 (ATLAS)
23:10:20.65 +29:14:48.9 17.1mag C/2022 E2 (ATLAS)
04:29:45.75 +26:03:01.6 16.0mag C/2022 N2 (PANSTARRS)
09:03:31.06 +32:01:11.5 16.2mag C/2022 QE78 (ATLAS)
08:31:08.60 -00:06:20.6 17.3mag C/2022 R6 (PANSTARRS)
18:53:37.38 +18:34:12.7 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:40:31.57 -11:30:54.2 17.5mag P/2023 B1 (PANSTARRS)
09:07:25.75 -11:48:40.7 17.6mag C/2023 F3 (ATLAS)
21:54:39.95 +62:55:59.5 17.5mag C/2023 H5 (Lemmon)
19:18:48.35 -03:44:24.4 14.1mag C/2023 R1 (PANSTARRS)
21:31:36.65 +85:58:27.7 17.8mag C/2023 X2 (Lemmon)
06:18:06.77 +63:30:38.2 17.2mag C/2024 A1 (ATLAS)
05:14:14.41 +18:27:21.7 11.1mag C/2024 E1 (Wierzchos)
16:18:59.06 +06:27:50.8 17.4mag C/2024 G6 (ATLAS)
20:20:56.17 +15:23:48.8 14.6mag C/2024 J3 (ATLAS)
03:26:46.48 -22:19:02.0 16.3mag C/2024 T5 (ATLAS)
05:17:05.83 +45:10:46.1 17.7mag C/2025 J1 (Borisov)
13:36:57.48 +45:46:41.2 15.2mag C/2025 L1 (ATLAS)
03:25:59.53 -26:16:55.1 17.8mag C/2025 Q3 (ATLAS)
23:47:32.79 +18:26:58.2 8.4mag C/2025 R3 (PANSTARRS)
12:53:55.30 +03:02:23.9 17.4mag C/2025 Y1 (ATLAS)
03:31:34.17 +02:34:23.3 13.4mag C/2026 A1 (MAPS)
00:00:51.38 +37:18:06.8 14.6mag C/2026 B2 (Sun-Gao)
18:43:48.45 -09:41:43.2 11.8mag 10P/Tempel
14:59:40.91 +03:09:43.7 14.0mag 24P/Schaumasse
11:02:40.94 -01:30:42.4 15.7mag 29P/Schwassmann-Wachmann
18:01:05.07 -09:35:38.3 18.0mag 40P/Vaisala
10:37:32.77 -04:03:48.3 16.9mag 43P/Wolf-Harrington
01:49:22.35 +17:33:51.0 17.2mag 47P/Ashbrook-Jackson
07:11:35.83 +36:54:54.8 17.0mag 63P/Wild
23:29:37.91 -11:23:49.4 15.7mag 65P/Gunn
04:04:27.44 +21:24:31.2 15.9mag 76P/West-Kohoutek-Ikemura
01:06:34.40 +08:19:01.1 14.3mag 78P/Gehrels
23:04:21.96 -09:15:29.9 14.6mag 88P/Howell
02:11:40.75 +20:45:42.4 15.1mag 93P/Lovas
04:55:39.37 +32:18:40.3 16.2mag 123P/West-Hartley
08:28:53.60 +38:09:09.5 16.2mag 124P/Mrkos
02:33:54.83 +14:25:12.1 16.4mag 128P/Shoemaker-Holt
02:48:25.37 +14:32:52.0 17.5mag 131P/Mueller
01:28:32.28 +13:23:33.6 10.6mag 141P/Machholz
01:37:24.18 +05:02:32.4 10.6mag 141P-A/Machholz
00:22:29.07 +00:56:09.0 12.8mag 141P-D/Machholz
02:07:46.03 +06:48:06.4 17.8mag 141P-I/Machholz
01:03:38.27 -01:17:58.1 15.1mag 162P/SidingSpring
14:50:37.62 -00:01:19.9 17.7mag 210P/Christensen
21:40:08.70 -11:20:26.6 17.6mag 218P/LINEAR
17:16:40.15 -13:52:46.0 16.1mag 235P/LINEAR
05:35:27.44 +34:43:55.3 16.8mag 240P/NEAT
07:38:43.01 -05:07:07.3 17.7mag 242P/Spahr
22:18:02.15 -20:51:37.0 17.9mag 260P/McNaught
01:59:06.67 +20:34:24.6 18.0mag 295P/LINEAR
15:42:27.99 +07:01:12.1 17.5mag 391P/Kowalski
07:34:22.23 +21:22:01.7 17.7mag 450P/LONEOS
05:36:31.79 +45:00:21.6 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 16 05:53 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
15:25:54.99 +07:49:24.50 2026-04-12.14 16.96
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
04:55:50.66 -29:52:57.70 SN 2026dpg 2026-02-23.11 15.75
04:21:28.18 -53:22:54.40 AT2026drl 2026-02-21.03 17.31
-rw-r--r-- 1 apache apache 5.8K Apr 16 05:53 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 16 05:53 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
14:32:40.720 +02:42:54.71 AT 2026jay 2026-04-06.66 22
14:07:18.110 +04:13:29.83 AT 2026jax 2026-04-06.66 22.26
14:14:08.750 +03:35:26.74 AT 2026jaw 2026-04-06.66 22.24
14:03:53.740 +04:33:03.03 AT 2026jav 2026-04-06.66 22.18
14:07:43.620 +03:35:48.12 AT 2026jau 2026-04-06.66 21.82
14:10:23.930 -01:02:22.49 AT 2026jat 2026-04-06.65 22.15
13:51:42.460 +03:14:48.63 AT 2026jas 2026-04-06.65 21.87
13:42:53.750 +01:22:24.17 AT 2026jar 2026-04-06.65 22.6
13:44:21.040 -01:54:42.32 AT 2026jaq 2026-04-06.65 22.71
13:35:29.290 +00:58:49.10 AT 2026jap 2026-04-06.64 22.39
13:41:45.110 +04:07:23.04 AT 2026jao 2026-04-06.64 21.84
13:38:11.980 +03:37:12.11 AT 2026jan 2026-04-06.64 22.48
13:27:27.970 +05:34:49.94 AT 2026jam 2026-04-06.64 21.79
13:28:44.170 +03:09:01.26 AT 2026jal 2026-04-06.64 22.01
13:29:02.030 -02:11:15.98 AT 2026jak 2026-04-06.64 21.54
13:11:37.460 +01:53:43.84 AT 2026jaj 2026-04-06.63 21.95
13:13:23.110 +00:38:42.68 AT 2026jai 2026-04-06.63 21.88
13:19:01.640 +03:04:08.10 AT 2026jah 2026-04-06.63 22.02
13:06:29.860 +02:34:35.75 AT 2026jag 2026-04-06.63 22.28
13:04:16.080 -00:23:58.35 AT 2026jaf 2026-04-06.63 22.55
-rw-r--r-- 1 apache apache 30K Apr 16 05:53 tns_transients_list.txt
