This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG
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 19.3967* 00 18 46.05 +65 38 05.4 11.6 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,2461149.8967,11.62,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 20260419.3967 11.62CV 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 19.3967* 23 49 03.92 +61 01 34.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
target,2461149.8967,10.92,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 20260419.3967 10.92CV 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 19.3967* 23 43 24.64 +61 39 38.6 11.1 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
DocumentRef: VOTx3611798,2461149.8967,11.06,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
DocumentRef: VOTx3611798 20260419.3967 11.06CV 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 19.3967* 23 37 12.62 +62 01 06.5 11.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
DocumentRef: VOTx3616507,2461149.8967,11.29,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
DocumentRef: VOTx3616507 20260419.3967 11.29CV 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 19.3967* 00 07 29.36 +61 46 55.9 11.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 429853589846286848,2461149.8967,11.31,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 429853589846286848 20260419.3967 11.31CV 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 19.3967* 23 41 12.38 +63 17 23.0 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
Gaia DR3 2016281025705701504,2461149.8967,11.66,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 2016281025705701504 20260419.3967 11.66CV 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 19.3967* 00 21 26.92 +59 13 53.3 11.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
FQ Cas,2461149.8967,11.39,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
FQ Cas 20260419.3967 11.39CV 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 19.3967* 00 28 08.49 +60 29 22.8 11.5 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
NSV 168,2461149.8967,11.48,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
NSV 168 20260419.3967 11.48CV 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 19.3967* 23 43 59.54 +60 03 07.4 11.8 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,2461149.8967,11.82,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 20260419.3967 11.82CV 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 19.3967* 00 20 55.72 +64 54 31.6 13.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,2461149.8967,13.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 20260419.3967 13.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 19.3967* 00 26 00.71 +60 59 09.2 13.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
ZTF J002602.33+605901.5,2461149.8967,13.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
ZTF J002602.33+605901.5 20260419.3967 13.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 19.3967* 00 18 09.09 +61 05 55.9 13.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,2461149.8967,13.89,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 20260419.3967 13.89CV 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 19.3967* 00 19 22.35 +63 01 34.1 13.5 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,2461149.8967,13.47,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 20260419.3967 13.47CV 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 19.3967* 23 38 05.24 +61 30 09.1 13.5 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 2012530793400489856,2461149.8967,13.54,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 2012530793400489856 20260419.3967 13.54CV 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 19.3967* 00 30 24.63 +60 12 33.1 13.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 428618086677459456,2461149.8967,12.98,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 428618086677459456 20260419.3967 12.98CV 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 19.3967* 00 16 16.75 +60 17 34.1 13.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 429150005483473024,2461149.8967,12.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
Gaia DR3 429150005483473024 20260419.3967 12.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 19.3967* 00 01 34.12 +62 18 04.3 12.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,2461149.8967,12.66,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 20260419.3967 12.66CV 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 19.3967* 00 16 19.48 +60 59 18.9 11.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 429571603776296320,2461149.8967,11.41,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 429571603776296320 20260419.3967 11.41CV 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 19.3967* 23 49 33.54 +62 11 42.7 10.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 2012896144805163136,2461149.8967,10.32,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 2012896144805163136 20260419.3967 10.32CV 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 19.3967* 23 26 42.58 +61 21 51.0 11.6 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,2461149.8967,11.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
target 20260419.3967 11.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 19.3967* 23 26 35.13 +61 35 40.1 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,2461149.8967,11.68,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 20260419.3967 11.68CV 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 19.3967* 23 47 32.76 +58 42 02.3 11.5 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,2461149.8967,11.46,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 20260419.3967 11.46CV 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 19.3967* 23 49 33.37 +62 09 18.4 11.6 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,2461149.8967,11.62,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 20260419.3967 11.62CV 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 19.3967* 00 21 27.45 +59 13 58.2 11.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
FQ Cas,2461149.8967,11.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
FQ Cas 20260419.3967 11.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 19.3967* 00 01 55.54 +60 18 54.9 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
ATO J000.4673+60.3247,2461149.8967,11.69,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 J000.4673+60.3247 20260419.3967 11.69CV 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 19.3967* 00 36 57.02 +63 06 27.7 11.8 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,2461149.8967,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 20260419.3967 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 19.3967* 00 19 30.52 +65 03 57.7 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
target,2461149.8967,11.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
target 20260419.3967 11.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 19.3967* 23 26 52.76 +62 16 23.5 12.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
target,2461149.8967,12.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
target 20260419.3967 12.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!
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,2461149.8967,12.68,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 20260419.3967 12.68CV 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 19.3967* 23 58 05.91 +61 02 00.8 12.5 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 2011698879716758400,2461149.8967,12.46,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 2011698879716758400 20260419.3967 12.46CV 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 19.3967* 00 09 22.87 +59 39 18.3 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
ATO J002.3361+59.6510,2461149.8967,12.32,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 J002.3361+59.6510 20260419.3967 12.32CV 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 19.3967* 00 06 54.07 +58 55 02.1 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
DocumentRef: VOTx4156490,2461149.8967,12.32,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
DocumentRef: VOTx4156490 20260419.3967 12.32CV 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 19.3967* 00 01 28.67 +62 07 54.6 12.6 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
DocumentRef: VOTx4160891,2461149.8967,12.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
DocumentRef: VOTx4160891 20260419.3967 12.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 19.3967* 23 39 49.14 +61 18 18.8 12.8 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
DocumentRef: VOTx4171249,2461149.8967,12.78,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
DocumentRef: VOTx4171249 20260419.3967 12.78CV 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 19.3967* 00 01 51.70 +60 18 53.8 12.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
Gaia DR3 429337717038798848,2461149.8967,12.68,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 429337717038798848 20260419.3967 12.68CV 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 19.3967* 23 58 29.83 +59 43 31.6 12.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,2461149.8967,12.88,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 20260419.3967 12.88CV 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 19.3967* 00 27 06.59 +60 41 03.4 12.8 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
DocumentRef: VOTx2151,2461149.8967,12.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
DocumentRef: VOTx2151 20260419.3967 12.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 19.3967* 00 13 11.74 +65 11 29.5 13.1 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
DocumentRef: VOTx17383,2461149.8967,13.05,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
DocumentRef: VOTx17383 20260419.3967 13.05CV 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 19.3967* 00 04 36.81 +64 36 18.3 13.1 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,2461149.8967,13.12,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 20260419.3967 13.12CV 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 19.3967* 00 20 12.06 +63 44 49.8 13.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
target,2461149.8967,13.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
target 20260419.3967 13.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 19.3967* 00 29 28.30 +60 49 44.6 12.8 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
NSVS J0029273+604956,2461149.8967,12.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
NSVS J0029273+604956 20260419.3967 12.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 19.3967* 00 32 55.17 +59 02 40.5 12.8 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
ASASSN-V J003253.91+590244.1,2461149.8967,12.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
ASASSN-V J003253.91+590244.1 20260419.3967 12.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 19.3967* 00 09 32.13 +58 40 24.5 12.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
ATO J002.3916+58.6834,2461149.8967,12.92,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 J002.3916+58.6834 20260419.3967 12.92CV 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 19.3967* 00 30 08.95 +60 08 01.3 12.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,2461149.8967,12.88,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 20260419.3967 12.88CV 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 19.3967* 23 59 08.84 +60 39 35.7 13.1 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,2461149.8967,13.11,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 20260419.3967 13.11CV 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 19.3967* 00 01 07.39 +62 07 27.5 13.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,2461149.8967,13.18,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 20260419.3967 13.18CV 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 19.3967* 00 00 02.51 +60 17 21.3 13.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,2461149.8967,13.15,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 20260419.3967 13.15CV 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 19.3967* 00 15 25.89 +59 45 44.5 13.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,2461149.8967,13.15,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 20260419.3967 13.15CV 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 19.3967* 23 54 21.36 +62 28 24.7 13.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 2012997093716394496,2461149.8967,13.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
Gaia DR3 2012997093716394496 20260419.3967 13.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 19.3967* 23 43 52.23 +61 33 10.9 13.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
target,2461149.8967,13.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
target 20260419.3967 13.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 19.3967* 00 00 07.43 +60 16 31.0 13.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
target,2461149.8967,13.26,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 20260419.3967 13.26CV 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 19.3967* 00 05 38.87 +61 16 24.3 13.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,2461149.8967,13.23,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 20260419.3967 13.23CV 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 19.3967* 23 58 40.62 +62 34 34.7 13.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 2012825260667144576,2461149.8967,13.28,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 2012825260667144576 20260419.3967 13.28CV 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 19.3967* 00 01 04.39 +62 07 33.8 13.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
target,2461149.8967,13.32,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 20260419.3967 13.32CV 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 19.3967* 00 02 03.93 +60 27 31.6 13.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
ZTF J000204.34+602726.2,2461149.8967,13.30,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
ZTF J000204.34+602726.2 20260419.3967 13.30CV 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 19.3967* 00 24 30.43 +60 35 50.0 13.1 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,2461149.8967,13.07,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 20260419.3967 13.07CV 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 19.3967* 00 02 16.38 +61 11 15.8 13.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
target,2461149.8967,13.29,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 20260419.3967 13.29CV 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 19.3967* 23 36 07.74 +63 34 50.5 13.6 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,2461149.8967,13.60,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 20260419.3967 13.60CV 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 19.3967* 00 19 10.29 +63 50 52.4 13.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
target,2461149.8967,13.39,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 20260419.3967 13.39CV 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 19.3967* 23 37 38.28 +61 41 60.0 13.6 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,2461149.8967,13.55,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 20260419.3967 13.55CV 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 19.3967* 23 52 49.22 +63 13 33.5 13.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
target,2461149.8967,13.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
target 20260419.3967 13.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 19.3967* 23 51 42.23 +59 40 36.7 13.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
target,2461149.8967,13.41,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 20260419.3967 13.41CV 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 19.3967* 23 41 45.24 +61 51 17.8 13.5 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,2461149.8967,13.53,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 20260419.3967 13.53CV 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 19.3967* 00 05 36.25 +64 28 01.1 13.5 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,2461149.8967,13.49,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 20260419.3967 13.49CV 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 19.3967* 00 00 08.47 +64 22 40.8 13.5 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,2461149.8967,13.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 20260419.3967 13.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 19.3967* 00 23 39.22 +65 16 53.3 13.6 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,2461149.8967,13.60,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 20260419.3967 13.60CV 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 19.3967* 00 27 12.78 +60 23 19.4 13.1 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,2461149.8967,13.13,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 20260419.3967 13.13CV 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 19.3967* 23 52 02.46 +59 08 44.7 13.6 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,2461149.8967,13.60,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 20260419.3967 13.60CV 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 19.3967* 23 43 21.09 +61 27 14.8 13.6 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,2461149.8967,13.61,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 20260419.3967 13.61CV 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 19.3967* 00 16 14.91 +61 01 11.8 13.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 429571913013933568,2461149.8967,13.34,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 429571913013933568 20260419.3967 13.34CV 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 19.3967* 23 25 14.10 +60 51 03.0 13.8 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,2461149.8967,13.78,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 20260419.3967 13.78CV 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 19.3967* 00 22 32.66 +64 21 43.3 13.6 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,2461149.8967,13.62,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 20260419.3967 13.62CV 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 19.3967* 00 16 03.27 +63 07 24.4 13.6 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,2461149.8967,13.56,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 20260419.3967 13.56CV 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 19.3967* 23 51 36.93 +63 13 10.9 13.8 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 2016137470723690240,2461149.8967,13.78,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 2016137470723690240 20260419.3967 13.78CV 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 19.3967* 23 52 38.14 +63 10 12.8 13.8 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
ZTF J235235.48+631028.3,2461149.8967,13.78,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
ZTF J235235.48+631028.3 20260419.3967 13.78CV 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 19.3967* 00 13 52.50 +61 10 26.1 13.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,2461149.8967,13.70,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 20260419.3967 13.70CV 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 19.3967* 23 55 09.73 +62 43 50.1 14.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
target,2461149.8967,14.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 20260419.3967 14.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!
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,2461149.8967,14.26,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 20260419.3967 14.26CV 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 19.3967* 23 47 32.24 +59 21 02.6 14.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
target,2461149.8967,14.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
target 20260419.3967 14.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 19.3967* 00 13 38.00 +62 59 16.5 14.1 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,2461149.8967,14.12,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 20260419.3967 14.12CV 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 19.3967* 23 53 00.87 +64 22 07.6 14.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
target,2461149.8967,14.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
target 20260419.3967 14.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 19.3967* 23 48 04.93 +62 21 25.4 14.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 2012959779036588800,2461149.8967,14.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
Gaia DR3 2012959779036588800 20260419.3967 14.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!
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,2461149.8967,14.55,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 20260419.3967 14.55CV 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 19.3967* 00 18 53.26 +59 05 32.2 11.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
ATO J004.7214+59.0811,2461149.8967,11.30,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.7214+59.0811 20260419.3967 11.30CV 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 19.3967* 00 35 54.44 +60 37 03.8 12.1 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
ASASSN-V J003553.23+603714.5,2461149.8967,12.11,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 J003553.23+603714.5 20260419.3967 12.11CV 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 19.3967* 00 04 31.75 +60 48 01.8 12.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,2461149.8967,12.86,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 20260419.3967 12.86CV 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 19.3967* 00 08 37.48 +60 36 17.0 13.1 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,2461149.8967,13.05,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 20260419.3967 13.05CV 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 19.3967* 00 28 35.41 +59 15 17.1 13.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
MNIC V9,2461149.8967,12.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
MNIC V9 20260419.3967 12.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 19.3967* 23 37 12.82 +62 01 16.6 11.5 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 2015607811047868928,2461149.8967,11.46,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 2015607811047868928 20260419.3967 11.46CV 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 19.3967* 00 35 26.57 +61 14 35.8 11.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
V1302 Cas,2461149.8967,11.29,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
V1302 Cas 20260419.3967 11.29CV 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 19.3967* 00 28 09.57 +60 29 25.8 11.5 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
NSV 168,2461149.8967,11.50,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
NSV 168 20260419.3967 11.50CV 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 19.3967* 00 34 26.23 +64 30 06.8 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,2461149.8967,12.22,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 20260419.3967 12.22CV 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 19.3967* 00 31 44.16 +57 54 07.1 11.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
NSVS J0031432+575409,2461149.8967,11.42,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 J0031432+575409 20260419.3967 11.42CV 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 19.3967* 23 41 13.48 +63 17 22.0 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
Gaia DR3 2016281025705701504,2461149.8967,11.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
Gaia DR3 2016281025705701504 20260419.3967 11.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 19.3967* 23 58 28.35 +59 25 31.8 12.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
target,2461149.8967,12.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
target 20260419.3967 12.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 19.3967* 00 12 46.95 +62 44 20.4 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
Gaia DR3 431305018222881920,2461149.8967,11.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
Gaia DR3 431305018222881920 20260419.3967 11.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 19.3967* 00 34 32.59 +61 56 08.7 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
NSVS J0034316+615643,2461149.8967,12.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
NSVS J0034316+615643 20260419.3967 12.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 19.3967* 23 56 27.76 +63 01 16.4 12.5 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 2013093949509487488,2461149.8967,12.48,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 2013093949509487488 20260419.3967 12.48CV 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 19.3967* 00 04 56.84 +60 17 56.6 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,2461149.8967,11.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
target 20260419.3967 11.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 19.3967* 23 51 15.11 +59 27 54.5 13.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
target,2461149.8967,13.30,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 20260419.3967 13.30CV 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 19.3967* 00 35 03.21 +61 18 49.7 10.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
V0826 Cas,2461149.8967,10.66,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
V0826 Cas 20260419.3967 10.66CV 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 19.3967* 00 39 17.31 +64 26 42.3 12.6 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,2461149.8967,12.61,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 20260419.3967 12.61CV 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 19.3967* 00 32 27.33 +60 34 04.5 13.5 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
NSVS J0032257+603420,2461149.8967,13.48,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 J0032257+603420 20260419.3967 13.48CV 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.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
First image: 2461036.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Last image: 2461149.89711444 19.04.2026 09:31:40.688 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 13
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.98
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): 22330
Objects passed selection criteria: 22217
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: 16229.8
Average stars matched: 14856.8 (91.5402 %)
Memory usage VmPeak: 124720 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 04:36:26 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.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
First image: 2461036.58829464 27.12.2025 02:06:58.657 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Last image: 2461149.89711444 19.04.2026 09:31:40.688 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 337
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.61
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: 67 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): 149679
Objects passed selection criteria: 149286
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: 111248
Average stars matched: 101025 (90.81 %)
Memory usage VmPeak: 1965376 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 04:52:31 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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: 2461149.89635792
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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits'
wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits (1st reference image)
verification OK: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Image size: 941.5'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:01.853 +61:59:36.76 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Image size: 923.8'x606.8' 15.4(deg)x10.1(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.70"/pix along the Y axis
Image center: 00:00:05.702 +61:58:53.21 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:01.853 +61:59:36.76
Second-epoch image center 00:00:05.702 +61:58:53.21
Angular distance between the image centers 0.0143 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Image size: 923.8'x606.8' 15.4(deg)x10.1(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.70"/pix along the Y axis
Image center: 00:00:03.672 +61:59:22.26 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:01.853 +61:59:36.76
Second-epoch image center 00:00:03.672 +61:59:22.26
Angular distance between the image centers 0.0054 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:05.702 +61:58:53.21
Second-epoch second image center 00:00:03.672 +61:59:22.26
Angular distance between the image centers 0.00899 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits &> /tmp/tmp.mJ7i6mccEP
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits &> /tmp/tmp.qB2rZbU3fk
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits &> /tmp/tmp.CQR6ipCW79
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits &> /tmp/tmp.SsiSyvryE2
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
The reference image (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits) and catalog (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat) found
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat' -> 'wcsmag.cat'
Read 25547 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0005 to 359.9978 deg, Dec +55.3501 to +67.4045 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.0005 to 359.9978 deg, Dec 55.3501 to 67.4045 deg
Loaded 133072 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): 14110 out of 15859 total matches.
Matched with Tycho-2 15859 out of 25547 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.955169
a=0.000000 b=1.000000 c=22.955169
From vast_summary.log: estimated ref. image limiting mag.: -7.98
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.98
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.98
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 12 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.5 pix Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
2.5 pix Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
2.6 pix fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
2.6 pix fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Limiting magnitude estimates:
15.0 mag. Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
15.0 mag. Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
All-image limiting magnitude estimate: 14.3 (SNR ) 11.6 (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.mJ7i6mccEP (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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3206, passed=25547
Got 25547 stars (including 22312 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
util/solve_plate_with_UCAC5 got 25547 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 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 341.2187 through 0 to 19.8663, gap 19.8663 to 341.2187
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 950 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
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 341.2185 through 0 to 19.8666, gap 19.8666 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 977 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
Accuracy estimation diagnostic: 976 matched stars entering correct_measured_positions(), 24870 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.48"
Excluding outliers - 976 stars left (next iteration limit 1073)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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.qB2rZbU3fk (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/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3160, passed=25477
Got 25477 stars (including 22297 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
util/solve_plate_with_UCAC5 got 25477 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 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 341.2186 through 0 to 19.8660, gap 19.8660 to 341.2186
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.4 to 67.4)
Done reading UCAC5 zone files...
Matched 978 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 944 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.58"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24335 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.52"
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 341.2185 through 0 to 19.8672, gap 19.8672 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 978 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24333 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.52"
Accuracy estimation diagnostic: 977 matched stars entering correct_measured_positions(), 24332 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Excluding outliers - 977 stars left (next iteration limit 1074)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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.CQR6ipCW79 (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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1105, passed=15536
Got 15536 stars (including 14415 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat
util/solve_plate_with_UCAC5 got 15536 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (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.010264 (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 341.4584 through 0 to 19.0502, gap 19.0502 to 341.4584
Reading UCAC5 zone files...
Searching UCAC5 zones 730 to 787 (Dec 56.0 to 67.1)
Done reading UCAC5 zone files...
Matched 319 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 250 matched stars entering correct_measured_positions(), 169 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.96"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 243 matched stars entering correct_measured_positions(), 3661 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.45"
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 238.1020 through 0 to 19.0544, gap 19.0544 to 238.1020
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 330 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 283 matched stars entering correct_measured_positions(), 3689 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.46"
Accuracy estimation diagnostic: 277 matched stars entering correct_measured_positions(), 4369 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 14.10"
Excluding outliers - 277 stars left (next iteration limit 267)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.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.SsiSyvryE2 (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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1064, passed=15521
Got 15521 stars (including 14442 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat
util/solve_plate_with_UCAC5 got 15521 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (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.010264 (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 341.4591 through 0 to 19.0495, gap 19.0495 to 341.4591
Reading UCAC5 zone files...
Searching UCAC5 zones 730 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 312 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 245 matched stars entering correct_measured_positions(), 169 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.79"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 238 matched stars entering correct_measured_positions(), 3647 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.73"
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 341.4573 through 0 to 19.0540, gap 19.0540 to 341.4573
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 333 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 275 matched stars entering correct_measured_positions(), 3669 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.73"
Accuracy estimation diagnostic: 270 matched stars entering correct_measured_positions(), 4205 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.20"
Excluding outliers - 270 stars left (next iteration limit 261)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
Saving fully-calibrated image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits'
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out31177.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out32754.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out32896.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33283.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33586.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34039.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34155.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34332.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34668.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 120s
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: 8s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31177_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 31177_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32754_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 32754_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32896_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 32896_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33283_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 33283_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33586_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 33586_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34039_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 34039_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34155_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 34155_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34332_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 34332_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34664_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 34664_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34668_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 34668_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10459_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 10459_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10636_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 10636_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 128s
Prepared the HTML report for the field Cas-02-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:18:46.05 +65:38:05.4
23:49:03.92 +61:01:34.5
23:43:24.64 +61:39:38.6
23:37:12.62 +62:01:06.5
00:07:29.36 +61:46:55.9
23:41:12.38 +63:17:23.0
00:21:26.92 +59:13:53.3
00:28:08.49 +60:29:22.8
23:43:59.54 +60:03:07.4
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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Creating symlink local_wcs_cache/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Creating symlink local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Creating symlink local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits exists and is non-empty
wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits exists and is non-empty
wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits exists and is non-empty
wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits (1st reference image)
verification OK: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Image size: 941.5'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:01.853 +61:59:36.76 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Image size: 923.8'x606.8' 15.4(deg)x10.1(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.70"/pix along the Y axis
Image center: 00:00:05.702 +61:58:53.21 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:01.853 +61:59:36.76
Second-epoch image center 00:00:05.702 +61:58:53.21
Angular distance between the image centers 0.0143 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Image size: 923.8'x606.8' 15.4(deg)x10.1(deg) 9576x6388 pix
Image scale: 5.79"/pix along the X axis and 5.70"/pix along the Y axis
Image center: 00:00:03.672 +61:59:22.26 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:01.853 +61:59:36.76
Second-epoch image center 00:00:03.672 +61:59:22.26
Angular distance between the image centers 0.0054 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:05.702 +61:58:53.21
Second-epoch second image center 00:00:03.672 +61:59:22.26
Angular distance between the image centers 0.00899 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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits &> /tmp/tmp.KALsLrmlGp
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits &> /tmp/tmp.vgbqXmnTUp
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits &> /tmp/tmp.QmuwNgBFQW
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits &> /tmp/tmp.4H3yAlfW4e
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
Found non-empty wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits and wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
The reference image (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits) and catalog (wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat) found
'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat' -> 'wcsmag.cat'
Read 170710 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 360.0000 deg, Dec +55.3116 to +67.4209 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 360.0000 deg, Dec 55.3116 to 67.4209 deg
Loaded 133731 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): 10993 out of 16914 total matches.
Matched with Tycho-2 16914 out of 170710 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.762297
a=0.000000 b=1.000000 c=22.762297
From vast_summary.log: estimated ref. image limiting mag.: -7.61
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.15
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.15
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 297 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.3 pix Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
2.3 pix Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
2.5 pix fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
2.5 pix fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Limiting magnitude estimates:
15.1 mag. Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
15.1 mag. Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
14.4 mag. fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
14.4 mag. fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
All-image limiting magnitude estimate: 14.4 (SNR ) 13.8 (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.KALsLrmlGp (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/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=35, blended=28495, passed=170675
Got 170675 stars (including 141953 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat
util/solve_plate_with_UCAC5 got 170675 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 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 341.2187 through 0 to 20.1102, gap 20.1102 to 341.2187
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 959 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167939 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
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 341.2185 through 0 to 20.1102, gap 20.1102 to 341.2185
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167939 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
Accuracy estimation diagnostic: 974 matched stars entering correct_measured_positions(), 167944 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Excluding outliers - 974 stars left (next iteration limit 1071)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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.vgbqXmnTUp (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/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits' -> 'wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=60, blended=28344, passed=170985
Got 170985 stars (including 142400 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat
util/solve_plate_with_UCAC5 got 170985 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 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 341.2186 through 0 to 20.0818, gap 20.0818 to 341.2186
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 973 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 953 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166835 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
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 341.2184 through 0 to 20.0827, gap 20.0827 to 341.2184
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 973 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166834 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 166834 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.56"
Excluding outliers - 972 stars left (next iteration limit 1069)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits -region wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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.QmuwNgBFQW (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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=7, blended=10255, passed=97244
Got 97244 stars (including 86897 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat
util/solve_plate_with_UCAC5 got 97244 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (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.010264 (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 341.2928 through 0 to 19.2136, gap 19.2136 to 341.2928
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 299 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 225 matched stars entering correct_measured_positions(), 146 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.15"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 220 matched stars entering correct_measured_positions(), 19957 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.23"
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 238.0791 through 0 to 19.2260, gap 19.2260 to 238.0791
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 310 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 253 matched stars entering correct_measured_positions(), 19975 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.24"
Accuracy estimation diagnostic: 251 matched stars entering correct_measured_positions(), 22953 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.38"
Excluding outliers - 251 stars left (next iteration limit 242)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.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.4H3yAlfW4e (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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=12, blended=10193, passed=97034
Got 97034 stars (including 86750 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat
util/solve_plate_with_UCAC5 got 97034 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (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.010264 (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 341.2428 through 0 to 19.2212, gap 19.2212 to 341.2428
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 299 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 228 matched stars entering correct_measured_positions(), 147 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 221 matched stars entering correct_measured_positions(), 20353 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.13"
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 238.0746 through 0 to 19.2296, gap 19.2296 to 238.0746
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 787 (Dec 56.0 to 67.2)
Done reading UCAC5 zone files...
Matched 310 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 251 matched stars entering correct_measured_positions(), 20372 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.15"
Accuracy estimation diagnostic: 248 matched stars entering correct_measured_positions(), 21853 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 13.69"
Excluding outliers - 248 stars left (next iteration limit 243)
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits -region wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_Cas-02-Q2b1x1_2025-12-26_20-06-58_20.00sec_-15.00C_LIGHT_0063.fits
Saving fully-calibrated image wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_Cas-02-Q2b1x1_2025-12-26_20-07-54_20.00sec_-14.90C_LIGHT_0064.fits
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-30-35_20.00sec_-4.90C_LIGHT_0688.fits
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.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-19_CI_Cas-02-Q2b1x1_043220_TTUQ2b1x1_3465555_YFnRoSmG/wcs_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689.fits
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_gaiadr2.txt__out193999.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out102223.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out111971.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out119947.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out120115.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out120340.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out135878.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out181704.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187935.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18826.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193929.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193930.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193932.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193980.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193998.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194009.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194011.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194024.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194029.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194893.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196741.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196899.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out196996.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out197111.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out197252.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out197731.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198399.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out198443.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out199566.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201022.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201117.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201272.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201387.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out201892.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out202811.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out203006.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out204867.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205277.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205325.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205350.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205647.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out205726.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206202.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206300.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206367.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out206504.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207389.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207626.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out207942.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208020.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208169.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208307.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208309.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208520.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208562.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out208660.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209028.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209138.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209615.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209630.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209775.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out209999.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210030.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210157.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210205.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210282.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out210787.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211045.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211059.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211177.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211264.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211967.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out211977.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212551.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212676.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out212754.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out215505.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out215937.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out216238.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out217242.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out217421.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out217830.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out218157.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out218467.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out48326.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out51255.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52924.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out58687.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out69913.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out71228.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out71810.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out82205.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out90694.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out91927.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out94769.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 197s
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: 63s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193926_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193926_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193929_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 193929_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193930_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 193930_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193932_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 193932_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193951_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193951_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (29.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193957_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193957_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193961_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193961_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193963_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193963_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193964_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193964_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (27.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193966_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193966_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193969_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193969_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (30.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193972_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193972_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193973_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193973_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193977_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193977_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193978_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193978_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193979_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193979_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193980_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 193980_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193981_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193981_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193982_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193982_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193983_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193983_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193987_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193987_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193990_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193990_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193991_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193991_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193995_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193995_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193997_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193997_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193998_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 193998_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193999_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 193999_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
**** FOUND 00:29:01.04 +60:28:52.2 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.08, MAG_FAINT_SEARCH_LIMIT=14.06)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194000_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194000_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194001_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194001_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194002_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194002_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194004_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194004_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194005_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194005_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194008_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194008_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194009_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 194009_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194010_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194010_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194011_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 194011_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194012_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194012_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194013_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194013_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194014_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194014_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194016_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194016_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194018_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194018_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194019_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 194019_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194024_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 194024_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 194029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194893_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 194893_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 195835_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 195835_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196741_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 196741_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196899_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 196899_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 196996_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 196996_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197111_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 197111_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197252_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 197252_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197600_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 197600_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197731_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 197731_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 197847_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 197847_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (30.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198096_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 198096_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198382_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 198382_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (37.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198399_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 198399_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198443_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 198443_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198598_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 198598_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 198707_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 198707_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199039_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199039_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199229_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199229_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199483_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199483_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199489_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199489_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199555_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199555_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199566_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 199566_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199948_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 199948_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 200233_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 200233_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201022_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 201022_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201043_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201043_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201075_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201075_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (162020.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201094_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201094_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201117_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 201117_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201272_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 201272_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201387_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 201387_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201444_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201444_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201681_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201681_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201699_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201699_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201712_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 201712_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 201892_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 201892_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202034_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 202034_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202048_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 202048_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
**** FOUND 00:05:17.64 +61:19:27.0 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202811_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 202811_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 202837_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 202837_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203006_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 203006_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203262_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 203262_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (37.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203306_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 203306_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203365_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 203365_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203489_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 203489_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 203652_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 203652_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204093_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 204093_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 204867_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 204867_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205112_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205112_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205277_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 205277_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205288_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205288_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205293_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205293_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205325_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 205325_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205350_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 205350_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205358_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205358_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205438_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205438_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (38.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205595_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205595_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (22.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205647_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 205647_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205726_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 205726_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205797_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205797_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205933_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 205933_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206063_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206063_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (29.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206068_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206068_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206202_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 206202_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206220_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206220_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206300_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 206300_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206367_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 206367_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206480_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206480_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206504_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 206504_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206541_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206541_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206542_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206542_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206549_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206549_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206639_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206639_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 206875_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 206875_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207037_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207037_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207142_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207142_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207351_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207351_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207389_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 207389_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207399_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207399_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207494_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207494_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207508_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207508_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207626_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 207626_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207735_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207735_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207808_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207808_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207871_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207871_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207942_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 207942_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207973_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207973_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 207987_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 207987_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208020_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208020_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208082_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208082_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208135_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208135_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208169_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208169_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208293_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208293_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (32.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208307_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208307_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208309_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208309_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208424_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208424_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208520_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208520_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208562_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208562_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208569_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208569_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208660_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 208660_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208726_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208726_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208798_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208798_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208822_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208822_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 208851_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 208851_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209028_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209028_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209098_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209098_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209138_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209138_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209199_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209199_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209253_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209253_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209434_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209434_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209463_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209463_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209544_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209544_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209569_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209569_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209583_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209583_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209609_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209609_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209615_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209615_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209630_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209630_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209680_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209680_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209690_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209690_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209732_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209732_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209748_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209748_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209775_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209775_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209785_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209785_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (29.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209856_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209856_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209869_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209869_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209932_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 209932_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 209999_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 209999_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210030_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 210030_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210132_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210132_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210157_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 210157_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210205_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 210205_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210282_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 210282_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210289_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210289_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210290_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210290_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210490_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210490_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (162074.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210514_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210514_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (37.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210576_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210576_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210669_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210669_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210787_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 210787_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210920_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210920_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 210967_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 210967_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211026_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211026_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211045_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211045_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211054_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211054_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211059_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211059_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211126_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211126_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211138_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211138_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211150_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211150_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211177_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211177_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211264_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211264_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211349_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211349_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211418_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211418_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211522_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211522_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211549_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211549_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211595_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211595_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211642_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211642_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211709_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211709_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211783_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211783_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211786_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211786_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (33.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211818_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 211818_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211967_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211967_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 211977_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 211977_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212070_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212070_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212095_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212095_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212119_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212119_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212139_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212139_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212183_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212183_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (162200.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212208_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212208_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212225_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212225_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (47.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212409_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212409_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212417_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212417_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212551_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 212551_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212658_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212658_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212676_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 212676_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212685_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212685_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212754_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 212754_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212916_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212916_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 212918_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 212918_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213036_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213036_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213215_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213215_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213233_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213233_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213378_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213378_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213520_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213520_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213555_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213555_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 213980_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 213980_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214075_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214075_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214082_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214082_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214173_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214173_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214214_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214214_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214307_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214307_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214382_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214382_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214619_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214619_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (91603.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 214642_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 214642_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 215505_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 215505_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 215937_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 215937_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216000_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216000_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216130_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216130_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (91662.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216210_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216210_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216216_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216216_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216218_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216218_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216238_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 216238_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216390_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216390_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (37.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216431_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216431_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216844_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216844_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216886_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216886_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 216970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 216970_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217242_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 217242_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217329_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 217329_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217347_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 217347_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217421_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 217421_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217689_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 217689_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217732_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 217732_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 217830_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 217830_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 218113_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 218113_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 218157_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 218157_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 218467_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 218467_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 218583_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 218583_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 218909_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 218909_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187763_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 187763_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (38.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34035_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 34035_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (34.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 119947_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 119947_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168413_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 168413_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23283_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 23283_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (28.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 82205_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 82205_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91927_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 91927_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92225_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 92225_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 94769_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 94769_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 111971_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 111971_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71810_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 71810_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 101029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 101029_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71228_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 71228_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 90694_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 90694_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18826_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 18826_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 135878_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 135878_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 133657_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 133657_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 48326_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 48326_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 120115_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 120115_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52924_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 52924_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58687_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 58687_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 51255_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 51255_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 64855_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 64855_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 102223_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 102223_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 120340_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 120340_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 96971_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 96971_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69913_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 69913_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181704_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 181704_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92948_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 92948_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187935_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
Preparing report for the candidate 187935_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71937_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 71937_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71095_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689
The candidate 71095_fd_Cas-02-Q2b1x1_2026-04-19_04-31-40_20.00sec_-5.00C_LIGHT_0689 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 8s
make_report_in_HTML.sh TOTAL: 268s
Prepared the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:18:46.05 +65:38:05.4
23:49:03.92 +61:01:34.5
23:43:24.64 +61:39:38.6
23:37:12.62 +62:01:06.5
00:07:29.36 +61:46:55.9
23:41:12.38 +63:17:23.0
00:21:26.92 +59:13:53.3
00:28:08.49 +60:29:22.8
23:43:59.54 +60:03:07.4
00:04:56.84 +60:17:56.6
00:28:35.41 +59:15:17.1
00:18:53.26 +59:05:32.2
23:58:28.35 +59:25:31.8
23:51:15.11 +59:27:54.5
00:31:44.16 +57:54:07.1
00:39:17.31 +64:26:42.3
00:32:27.33 +60:34:04.5
00:34:26.23 +64:30:06.8
00:20:55.72 +64:54:31.6
00:26:00.71 +60:59:09.2
00:18:09.09 +61:05:55.9
00:19:22.35 +63:01:34.1
23:38:05.24 +61:30:09.1
00:30:24.63 +60:12:33.1
00:16:16.75 +60:17:34.1
00:01:34.12 +62:18:04.3
00:16:19.48 +60:59:18.9
23:49:33.54 +62:11:42.7
23:26:42.58 +61:21:51.0
23:26:35.13 +61:35:40.1
23:47:32.76 +58:42:02.3
23:49:33.37 +62:09:18.4
00:21:27.45 +59:13:58.2
00:01:55.54 +60:18:54.9
00:36:57.02 +63:06:27.7
00:19:30.52 +65:03:57.7
23:26:52.76 +62:16:23.5
23:29:50.30 +65:16:18.9
23:58:05.91 +61:02:00.8
00:09:22.87 +59:39:18.3
00:06:54.07 +58:55:02.1
00:01:28.67 +62:07:54.6
23:39:49.14 +61:18:18.8
00:01:51.70 +60:18:53.8
23:58:29.83 +59:43:31.6
00:27:06.59 +60:41:03.4
00:13:11.74 +65:11:29.5
00:04:36.81 +64:36:18.3
00:20:12.06 +63:44:49.8
00:29:28.30 +60:49:44.6
00:32:55.17 +59:02:40.5
00:09:32.13 +58:40:24.5
00:30:08.95 +60:08:01.3
23:59:08.84 +60:39:35.7
00:01:07.39 +62:07:27.5
00:00:02.51 +60:17:21.3
00:15:25.89 +59:45:44.5
23:54:21.36 +62:28:24.7
23:43:52.23 +61:33:10.9
00:00:07.43 +60:16:31.0
00:05:38.87 +61:16:24.3
23:58:40.62 +62:34:34.7
00:01:04.39 +62:07:33.8
00:02:03.93 +60:27:31.6
00:24:30.43 +60:35:50.0
00:02:16.38 +61:11:15.8
23:36:07.74 +63:34:50.5
00:19:10.29 +63:50:52.4
23:37:38.28 +61:41:60.0
23:52:49.22 +63:13:33.5
23:51:42.23 +59:40:36.7
23:41:45.24 +61:51:17.8
00:05:36.25 +64:28:01.1
00:00:08.47 +64:22:40.8
00:23:39.22 +65:16:53.3
00:27:12.78 +60:23:19.4
23:52:02.46 +59:08:44.7
23:43:21.09 +61:27:14.8
00:16:14.91 +61:01:11.8
23:25:14.10 +60:51:03.0
00:22:32.66 +64:21:43.3
00:16:03.27 +63:07:24.4
23:51:36.93 +63:13:10.9
23:52:38.14 +63:10:12.8
00:13:52.50 +61:10:26.1
23:55:09.73 +62:43:50.1
23:31:13.60 +64:53:44.7
23:47:32.24 +59:21:02.6
00:13:38.00 +62:59:16.5
23:53:00.87 +64:22:07.6
23:48:04.93 +62:21:25.4
23:36:50.81 +65:57:54.1
23:41:13.48 +63:17:22.0
23:56:27.76 +63:01:16.4
00:12:46.95 +62:44:20.4
00:34:32.59 +61:56:08.7
00:35:03.21 +61:18:49.7
00:35:26.57 +61:14:35.8
23:37:12.82 +62:01:16.6
00:35:54.44 +60:37:03.8
00:28:09.57 +60:29:25.8
00:04:31.75 +60:48:01.8
00:08:37.48 +60:36:17.0
########### Completed Cas-02-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:18:46.05 +65:38:05.4
23:49:03.92 +61:01:34.5
23:43:24.64 +61:39:38.6
23:37:12.62 +62:01:06.5
00:07:29.36 +61:46:55.9
23:41:12.38 +63:17:23.0
00:21:26.92 +59:13:53.3
00:28:08.49 +60:29:22.8
23:43:59.54 +60:03:07.4
00:20:55.72 +64:54:31.6
00:26:00.71 +60:59:09.2
00:18:09.09 +61:05:55.9
00:19:22.35 +63:01:34.1
23:38:05.24 +61:30:09.1
00:30:24.63 +60:12:33.1
00:16:16.75 +60:17:34.1
00:01:34.12 +62:18:04.3
00:16:19.48 +60:59:18.9
23:49:33.54 +62:11:42.7
23:26:42.58 +61:21:51.0
23:26:35.13 +61:35:40.1
23:47:32.76 +58:42:02.3
23:49:33.37 +62:09:18.4
00:21:27.45 +59:13:58.2
00:01:55.54 +60:18:54.9
00:36:57.02 +63:06:27.7
00:19:30.52 +65:03:57.7
23:26:52.76 +62:16:23.5
23:29:50.30 +65:16:18.9
23:58:05.91 +61:02:00.8
00:09:22.87 +59:39:18.3
00:06:54.07 +58:55:02.1
00:01:28.67 +62:07:54.6
23:39:49.14 +61:18:18.8
00:01:51.70 +60:18:53.8
23:58:29.83 +59:43:31.6
00:27:06.59 +60:41:03.4
00:13:11.74 +65:11:29.5
00:04:36.81 +64:36:18.3
00:20:12.06 +63:44:49.8
00:29:28.30 +60:49:44.6
00:32:55.17 +59:02:40.5
00:09:32.13 +58:40:24.5
00:30:08.95 +60:08:01.3
23:59:08.84 +60:39:35.7
00:01:07.39 +62:07:27.5
00:00:02.51 +60:17:21.3
00:15:25.89 +59:45:44.5
23:54:21.36 +62:28:24.7
23:43:52.23 +61:33:10.9
00:00:07.43 +60:16:31.0
00:05:38.87 +61:16:24.3
23:58:40.62 +62:34:34.7
00:01:04.39 +62:07:33.8
00:02:03.93 +60:27:31.6
00:24:30.43 +60:35:50.0
00:02:16.38 +61:11:15.8
23:36:07.74 +63:34:50.5
00:19:10.29 +63:50:52.4
23:37:38.28 +61:41:60.0
23:52:49.22 +63:13:33.5
23:51:42.23 +59:40:36.7
23:41:45.24 +61:51:17.8
00:05:36.25 +64:28:01.1
00:00:08.47 +64:22:40.8
00:23:39.22 +65:16:53.3
00:27:12.78 +60:23:19.4
23:52:02.46 +59:08:44.7
23:43:21.09 +61:27:14.8
00:16:14.91 +61:01:11.8
23:25:14.10 +60:51:03.0
00:22:32.66 +64:21:43.3
00:16:03.27 +63:07:24.4
23:51:36.93 +63:13:10.9
23:52:38.14 +63:10:12.8
00:13:52.50 +61:10:26.1
23:55:09.73 +62:43:50.1
23:31:13.60 +64:53:44.7
23:47:32.24 +59:21:02.6
00:13:38.00 +62:59:16.5
23:53:00.87 +64:22:07.6
23:48:04.93 +62:21:25.4
23:36:50.81 +65:57:54.1
00:18:53.26 +59:05:32.2
00:35:54.44 +60:37:03.8
00:04:31.75 +60:48:01.8
00:08:37.48 +60:36:17.0
00:28:35.41 +59:15:17.1
23:37:12.82 +62:01:16.6
00:35:26.57 +61:14:35.8
00:28:09.57 +60:29:25.8
00:34:26.23 +64:30:06.8
00:31:44.16 +57:54:07.1
23:41:13.48 +63:17:22.0
23:58:28.35 +59:25:31.8
00:12:46.95 +62:44:20.4
00:34:32.59 +61:56:08.7
23:56:27.76 +63:01:16.4
00:04:56.84 +60:17:56.6
23:51:15.11 +59:27:54.5
00:35:03.21 +61:18:49.7
00:39:17.31 +64:26:42.3
00:32:27.33 +60:34:04.5
###################################################################################
00:18:46.05 +65:38:05.4 -- not an asteroid (will add it to exclusion list)
23:49:03.92 +61:01:34.5 -- not an asteroid (will add it to exclusion list)
23:43:24.64 +61:39:38.6 -- not an asteroid (will add it to exclusion list)
23:37:12.62 +62:01:06.5 -- not an asteroid (will add it to exclusion list)
00:07:29.36 +61:46:55.9 -- not an asteroid (will add it to exclusion list)
23:41:12.38 +63:17:23.0 -- not an asteroid (will add it to exclusion list)
00:21:26.92 +59:13:53.3 -- not an asteroid (will add it to exclusion list)
00:28:08.49 +60:29:22.8 -- not an asteroid (will add it to exclusion list)
23:43:59.54 +60:03:07.4 -- not an asteroid (will add it to exclusion list)
00:20:55.72 +64:54:31.6 -- not an asteroid (will add it to exclusion list)
00:26:00.71 +60:59:09.2 -- not an asteroid (will add it to exclusion list)
00:18:09.09 +61:05:55.9 -- not an asteroid (will add it to exclusion list)
00:19:22.35 +63:01:34.1 -- not an asteroid (will add it to exclusion list)
23:38:05.24 +61:30:09.1 -- not an asteroid (will add it to exclusion list)
00:30:24.63 +60:12:33.1 -- not an asteroid (will add it to exclusion list)
00:16:16.75 +60:17:34.1 -- not an asteroid (will add it to exclusion list)
00:01:34.12 +62:18:04.3 -- not an asteroid (will add it to exclusion list)
00:16:19.48 +60:59:18.9 -- not an asteroid (will add it to exclusion list)
23:49:33.54 +62:11:42.7 -- not an asteroid (will add it to exclusion list)
23:26:42.58 +61:21:51.0 -- not an asteroid (will add it to exclusion list)
23:26:35.13 +61:35:40.1 -- not an asteroid (will add it to exclusion list)
23:47:32.76 +58:42:02.3 -- not an asteroid (will add it to exclusion list)
23:49:33.37 +62:09:18.4 -- not an asteroid (will add it to exclusion list)
00:21:27.45 +59:13:58.2 -- not an asteroid (will add it to exclusion list)
00:01:55.54 +60:18:54.9 -- not an asteroid (will add it to exclusion list)
00:36:57.02 +63:06:27.7 -- not an asteroid (will add it to exclusion list)
00:19:30.52 +65:03:57.7 -- not an asteroid (will add it to exclusion list)
23:26:52.76 +62:16:23.5 -- not an asteroid (will add it to exclusion list)
23:29:50.30 +65:16:18.9 -- not an asteroid (will add it to exclusion list)
23:58:05.91 +61:02:00.8 -- not an asteroid (will add it to exclusion list)
00:09:22.87 +59:39:18.3 -- not an asteroid (will add it to exclusion list)
00:06:54.07 +58:55:02.1 -- not an asteroid (will add it to exclusion list)
00:01:28.67 +62:07:54.6 -- not an asteroid (will add it to exclusion list)
23:39:49.14 +61:18:18.8 -- not an asteroid (will add it to exclusion list)
00:01:51.70 +60:18:53.8 -- not an asteroid (will add it to exclusion list)
23:58:29.83 +59:43:31.6 -- not an asteroid (will add it to exclusion list)
00:27:06.59 +60:41:03.4 -- not an asteroid (will add it to exclusion list)
00:13:11.74 +65:11:29.5 -- not an asteroid (will add it to exclusion list)
00:04:36.81 +64:36:18.3 -- not an asteroid (will add it to exclusion list)
00:20:12.06 +63:44:49.8 -- not an asteroid (will add it to exclusion list)
00:29:28.30 +60:49:44.6 -- not an asteroid (will add it to exclusion list)
00:32:55.17 +59:02:40.5 -- not an asteroid (will add it to exclusion list)
00:09:32.13 +58:40:24.5 -- not an asteroid (will add it to exclusion list)
00:30:08.95 +60:08:01.3 -- not an asteroid (will add it to exclusion list)
23:59:08.84 +60:39:35.7 -- not an asteroid (will add it to exclusion list)
00:01:07.39 +62:07:27.5 -- not an asteroid (will add it to exclusion list)
00:00:02.51 +60:17:21.3 -- not an asteroid (will add it to exclusion list)
00:15:25.89 +59:45:44.5 -- not an asteroid (will add it to exclusion list)
23:54:21.36 +62:28:24.7 -- not an asteroid (will add it to exclusion list)
23:43:52.23 +61:33:10.9 -- not an asteroid (will add it to exclusion list)
00:00:07.43 +60:16:31.0 -- not an asteroid (will add it to exclusion list)
00:05:38.87 +61:16:24.3 -- not an asteroid (will add it to exclusion list)
23:58:40.62 +62:34:34.7 -- not an asteroid (will add it to exclusion list)
00:01:04.39 +62:07:33.8 -- not an asteroid (will add it to exclusion list)
00:02:03.93 +60:27:31.6 -- not an asteroid (will add it to exclusion list)
00:24:30.43 +60:35:50.0 -- not an asteroid (will add it to exclusion list)
00:02:16.38 +61:11:15.8 -- not an asteroid (will add it to exclusion list)
23:36:07.74 +63:34:50.5 -- not an asteroid (will add it to exclusion list)
00:19:10.29 +63:50:52.4 -- not an asteroid (will add it to exclusion list)
23:37:38.28 +61:41:60.0 -- not an asteroid (will add it to exclusion list)
23:52:49.22 +63:13:33.5 -- not an asteroid (will add it to exclusion list)
23:51:42.23 +59:40:36.7 -- not an asteroid (will add it to exclusion list)
23:41:45.24 +61:51:17.8 -- not an asteroid (will add it to exclusion list)
00:05:36.25 +64:28:01.1 -- not an asteroid (will add it to exclusion list)
00:00:08.47 +64:22:40.8 -- not an asteroid (will add it to exclusion list)
00:23:39.22 +65:16:53.3 -- not an asteroid (will add it to exclusion list)
00:27:12.78 +60:23:19.4 -- not an asteroid (will add it to exclusion list)
23:52:02.46 +59:08:44.7 -- not an asteroid (will add it to exclusion list)
23:43:21.09 +61:27:14.8 -- not an asteroid (will add it to exclusion list)
00:16:14.91 +61:01:11.8 -- not an asteroid (will add it to exclusion list)
23:25:14.10 +60:51:03.0 -- not an asteroid (will add it to exclusion list)
00:22:32.66 +64:21:43.3 -- not an asteroid (will add it to exclusion list)
00:16:03.27 +63:07:24.4 -- not an asteroid (will add it to exclusion list)
23:51:36.93 +63:13:10.9 -- not an asteroid (will add it to exclusion list)
23:52:38.14 +63:10:12.8 -- not an asteroid (will add it to exclusion list)
00:13:52.50 +61:10:26.1 -- not an asteroid (will add it to exclusion list)
23:55:09.73 +62:43:50.1 -- not an asteroid (will add it to exclusion list)
23:31:13.60 +64:53:44.7 -- not an asteroid (will add it to exclusion list)
23:47:32.24 +59:21:02.6 -- not an asteroid (will add it to exclusion list)
00:13:38.00 +62:59:16.5 -- not an asteroid (will add it to exclusion list)
23:53:00.87 +64:22:07.6 -- not an asteroid (will add it to exclusion list)
23:48:04.93 +62:21:25.4 -- not an asteroid (will add it to exclusion list)
23:36:50.81 +65:57:54.1 -- not an asteroid (will add it to exclusion list)
00:18:53.26 +59:05:32.2 -- not an asteroid (will add it to exclusion list)
00:35:54.44 +60:37:03.8 -- not an asteroid (will add it to exclusion list)
00:04:31.75 +60:48:01.8 -- not an asteroid (will add it to exclusion list)
00:08:37.48 +60:36:17.0 -- not an asteroid (will add it to exclusion list)
00:28:35.41 +59:15:17.1 -- not an asteroid (will add it to exclusion list)
23:37:12.82 +62:01:16.6 -- not an asteroid (will add it to exclusion list)
00:35:26.57 +61:14:35.8 -- not an asteroid (will add it to exclusion list)
00:28:09.57 +60:29:25.8 -- not an asteroid (will add it to exclusion list)
00:34:26.23 +64:30:06.8 -- not an asteroid (will add it to exclusion list)
00:31:44.16 +57:54:07.1 -- not an asteroid (will add it to exclusion list)
23:41:13.48 +63:17:22.0 -- not an asteroid (will add it to exclusion list)
23:58:28.35 +59:25:31.8 -- not an asteroid (will add it to exclusion list)
00:12:46.95 +62:44:20.4 -- not an asteroid (will add it to exclusion list)
00:34:32.59 +61:56:08.7 -- not an asteroid (will add it to exclusion list)
23:56:27.76 +63:01:16.4 -- not an asteroid (will add it to exclusion list)
00:04:56.84 +60:17:56.6 -- not an asteroid (will add it to exclusion list)
23:51:15.11 +59:27:54.5 -- not an asteroid (will add it to exclusion list)
00:35:03.21 +61:18:49.7 -- not an asteroid (will add it to exclusion list)
00:39:17.31 +64:26:42.3 -- not an asteroid (will add it to exclusion list)
00:32:27.33 +60:34:04.5 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:02.51 +60:17:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:07.43 +60:16:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:08.47 +64:22:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:04.39 +62:07:33.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:07.39 +62:07:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:28.67 +62:07:54.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:34.12 +62:18:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:51.70 +60:18:53.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:55.54 +60:18:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:03.93 +60:27:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:16.38 +61:11:15.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:31.75 +60:48:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:36.81 +64:36:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:56.84 +60:17:56.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:36.25 +64:28:01.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:38.87 +61:16:24.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:54.07 +58:55:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:29.36 +61:46:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:37.48 +60:36:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:22.87 +59:39:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:32.13 +58:40:24.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:46.95 +62:44:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:11.74 +65:11:29.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:38.00 +62:59:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:52.50 +61:10:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:25.89 +59:45:44.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:03.27 +63:07:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:14.91 +61:01:11.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:16.75 +60:17:34.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:19.48 +60:59:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:09.09 +61:05:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:46.05 +65:38:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:53.26 +59:05:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:10.29 +63:50:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:22.35 +63:01:34.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:30.52 +65:03:57.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:12.06 +63:44:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:55.72 +64:54:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:26.92 +59:13:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:27.45 +59:13:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:32.66 +64:21:43.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:39.22 +65:16:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:30.43 +60:35:50.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:00.71 +60:59:09.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:06.59 +60:41:03.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:12.78 +60:23:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:08.49 +60:29:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:09.57 +60:29:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:35.41 +59:15:17.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:28.30 +60:49:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:08.95 +60:08:01.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:24.63 +60:12:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:44.16 +57:54:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:27.33 +60:34:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:55.17 +59:02:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:26.23 +64:30:06.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:32.59 +61:56:08.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:03.21 +61:18:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:26.57 +61:14:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:54.44 +60:37:03.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:57.02 +63:06:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:17.31 +64:26:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:14.10 +60:51:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:35.13 +61:35:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:42.58 +61:21:51.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:52.76 +62:16:23.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:50.30 +65:16:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:13.60 +64:53:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:07.74 +63:34:50.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:50.81 +65:57:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:12.62 +62:01:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:12.82 +62:01:16.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:38.28 +61:41:60.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:05.24 +61:30:09.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:49.14 +61:18:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:12.38 +63:17:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:13.48 +63:17:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:45.24 +61:51:17.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:21.09 +61:27:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:24.64 +61:39:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:52.23 +61:33:10.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:59.54 +60:03:07.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:32.24 +59:21:02.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:32.76 +58:42:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:04.93 +62:21:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:03.92 +61:01:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:33.37 +62:09:18.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:33.54 +62:11:42.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:15.11 +59:27:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:36.93 +63:13:10.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:42.23 +59:40:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:02.46 +59:08:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:38.14 +63:10:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:49.22 +63:13:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:00.87 +64:22:07.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:21.36 +62:28:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:09.73 +62:43:50.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:27.76 +63:01:16.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:05.91 +61:02:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:28.35 +59:25:31.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:29.83 +59:43:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:40.62 +62:34:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:08.84 +60:39:35.7 -- 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:00:02.51 +60:17:21.3 -- not a known variable star
00:00:07.43 +60:16:31.0 -- not a known variable star
00:00:08.47 +64:22:40.8 -- not a known variable star
00:01:04.39 +62:07:33.8 -- not a known variable star
00:01:07.39 +62:07:27.5 -- not a known variable star
00:01:28.67 +62:07:54.6 -- not a known variable star
00:01:34.12 +62:18:04.3 -- not a known variable star
00:01:51.70 +60:18:53.8 -- a known variable star
00:01:55.54 +60:18:54.9 -- not a known variable star
00:02:03.93 +60:27:31.6 -- a known variable star
00:02:16.38 +61:11:15.8 -- not a known variable star
00:04:31.75 +60:48:01.8 -- not a known variable star
00:04:36.81 +64:36:18.3 -- not a known variable star
00:04:56.84 +60:17:56.6 -- not a known variable star
00:05:36.25 +64:28:01.1 -- not a known variable star
00:05:38.87 +61:16:24.3 -- not a known variable star
00:06:54.07 +58:55:02.1 -- not a known variable star
00:07:29.36 +61:46:55.9 -- a known variable star
00:08:37.48 +60:36:17.0 -- not a known variable star
00:09:22.87 +59:39:18.3 -- not a known variable star
00:09:32.13 +58:40:24.5 -- not a known variable star
00:12:46.95 +62:44:20.4 -- not a known variable star
00:13:11.74 +65:11:29.5 -- not a known variable star
00:13:38.00 +62:59:16.5 -- not a known variable star
00:13:52.50 +61:10:26.1 -- not a known variable star
00:15:25.89 +59:45:44.5 -- not a known variable star
00:16:03.27 +63:07:24.4 -- not a known variable star
00:16:14.91 +61:01:11.8 -- a known variable star
00:16:16.75 +60:17:34.1 -- not a known variable star
00:16:19.48 +60:59:18.9 -- a known variable star
00:18:09.09 +61:05:55.9 -- not a known variable star
00:18:46.05 +65:38:05.4 -- not a known variable star
00:18:53.26 +59:05:32.2 -- not a known variable star
00:19:10.29 +63:50:52.4 -- not a known variable star
00:19:22.35 +63:01:34.1 -- not a known variable star
00:19:30.52 +65:03:57.7 -- not a known variable star
00:20:12.06 +63:44:49.8 -- not a known variable star
00:20:55.72 +64:54:31.6 -- not a known variable star
00:21:26.92 +59:13:53.3 -- a known variable star
00:21:27.45 +59:13:58.2 -- a known variable star
00:22:32.66 +64:21:43.3 -- not a known variable star
00:23:39.22 +65:16:53.3 -- not a known variable star
00:24:30.43 +60:35:50.0 -- not a known variable star
00:26:00.71 +60:59:09.2 -- a known variable star
00:27:06.59 +60:41:03.4 -- not a known variable star
00:27:12.78 +60:23:19.4 -- not a known variable star
00:28:08.49 +60:29:22.8 -- a known variable star
00:28:09.57 +60:29:25.8 -- a known variable star
00:28:35.41 +59:15:17.1 -- a known variable star
00:29:28.30 +60:49:44.6 -- a known variable star
00:30:08.95 +60:08:01.3 -- not a known variable star
00:30:24.63 +60:12:33.1 -- not a known variable star
00:31:44.16 +57:54:07.1 -- a known variable star
00:32:27.33 +60:34:04.5 -- a known variable star
00:32:55.17 +59:02:40.5 -- a known variable star
00:34:26.23 +64:30:06.8 -- not a known variable star
00:34:32.59 +61:56:08.7 -- not a known variable star
00:35:03.21 +61:18:49.7 -- a known variable star
00:35:26.57 +61:14:35.8 -- a known variable star
00:35:54.44 +60:37:03.8 -- a known variable star
00:36:57.02 +63:06:27.7 -- not a known variable star
00:39:17.31 +64:26:42.3 -- not a known variable star
23:25:14.10 +60:51:03.0 -- not a known variable star
23:26:35.13 +61:35:40.1 -- not a known variable star
23:26:42.58 +61:21:51.0 -- not a known variable star
23:26:52.76 +62:16:23.5 -- not a known variable star
23:29:50.30 +65:16:18.9 -- not a known variable star
23:31:13.60 +64:53:44.7 -- not a known variable star
23:36:07.74 +63:34:50.5 -- not a known variable star
23:36:50.81 +65:57:54.1 -- not a known variable star
23:37:12.62 +62:01:06.5 -- not a known variable star
23:37:12.82 +62:01:16.6 -- not a known variable star
23:37:38.28 +61:41:60.0 -- not a known variable star
23:38:05.24 +61:30:09.1 -- not a known variable star
23:39:49.14 +61:18:18.8 -- not a known variable star
23:41:12.38 +63:17:23.0 -- a known variable star
23:41:13.48 +63:17:22.0 -- a known variable star
23:41:45.24 +61:51:17.8 -- not a known variable star
23:43:21.09 +61:27:14.8 -- not a known variable star
23:43:24.64 +61:39:38.6 -- not a known variable star
23:43:52.23 +61:33:10.9 -- not a known variable star
23:43:59.54 +60:03:07.4 -- not a known variable star
23:47:32.24 +59:21:02.6 -- not a known variable star
23:47:32.76 +58:42:02.3 -- not a known variable star
23:48:04.93 +62:21:25.4 -- a known variable star
23:49:03.92 +61:01:34.5 -- not a known variable star
23:49:33.37 +62:09:18.4 -- not a known variable star
23:49:33.54 +62:11:42.7 -- a known variable star
23:51:15.11 +59:27:54.5 -- not a known variable star
23:51:36.93 +63:13:10.9 -- not a known variable star
23:51:42.23 +59:40:36.7 -- not a known variable star
23:52:02.46 +59:08:44.7 -- not a known variable star
23:52:38.14 +63:10:12.8 -- a known variable star
23:52:49.22 +63:13:33.5 -- not a known variable star
23:53:00.87 +64:22:07.6 -- not a known variable star
23:54:21.36 +62:28:24.7 -- a known variable star
23:55:09.73 +62:43:50.1 -- not a known variable star
23:56:27.76 +63:01:16.4 -- not a known variable star
23:58:05.91 +61:02:00.8 -- a known variable star
23:58:28.35 +59:25:31.8 -- not a known variable star
23:58:29.83 +59:43:31.6 -- not a known variable star
23:58:40.62 +62:34:34.7 -- a known variable star
23:59:08.84 +60:39:35.7 -- not a known variable star
Found 77 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
103 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 103 (excluding asteroids and hot pixels, 77 new), not updating the exclusion list!
###################################################################################
Not allowed to update the exclusion list IS_THIS_TEST_RUN=NO ALLOW_EXCLUSION_LIST_UPDATE= NO
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461149.89635792 -observatory V36
00:25:47.65 -00:04:33.8 Mercury (-0.1mag)
03:25:22.00 +19:05:04.8 Venus (-3.9mag)
00:27:29.06 +01:55:23.8 Mars (1.2mag)
07:14:14.07 +22:43:32.9 Jupiter (-2.1mag)
00:30:41.21 +00:58:20.0 Saturn (0.9mag)
03:48:25.33 +19:49:47.3 Uranus (5.8mag)
00:11:16.81 -00:12:36.5 Neptune (7.8mag)
20:33:53.53 -22:52:47.9 Pluto (14.5mag)
03:27:56.51 +23:07:46.4 Moon (-8.7mag)
-rw-r--r-- 1 apache apache 362 Apr 19 04:36 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461149.89635792:
07:14:08.90 +22:43:45.6 Io (5.8mag)
07:14:13.74 +22:43:36.5 Europa (5.9mag)
07:13:55.60 +22:44:14.0 Ganymede (5.4mag)
07:14:26.96 +22:42:57.2 Callisto (6.6mag)
07:17:25.02 +22:29:38.7 Himalia (15.4mag)
07:14:15.87 +22:43:26.8 Thebe (16.2mag)
07:17:40.56 +22:59:58.5 Elara (17.3mag)
07:13:20.83 +23:21:46.6 Pasiphae (17.4mag)
07:22:29.12 +22:41:53.3 Carme (18.5mag)
00:30:32.01 +00:58:40.4 Titan (8.8mag)
00:30:39.13 +00:58:35.9 Rhea (10.1mag)
00:30:16.16 +00:57:56.7 Iapetus (11.5mag)
00:30:36.41 +00:58:47.8 Hyperion (14.8mag)
00:32:15.34 +01:06:45.8 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 19 04:36 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461149.89635792:
15:51:40.02 -18:34:48.6 JWST
16:42:47.59 +47:24:48.2 Chandra
19:29:58.09 +03:17:02.4 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 19 04:36 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461149.89635792 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:53:15.54 -28:59:00.2 13.9mag P/2010 H2 (Vales)
05:09:13.64 -69:30:16.3 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:33:12.81 +31:27:40.2 17.2mag C/2017 K2 (PANSTARRS)
17:30:02.25 +10:56:46.7 17.6mag C/2021 G2 (ATLAS)
23:11:05.09 +29:22:01.8 17.1mag C/2022 E2 (ATLAS)
04:33:13.22 +26:07:43.7 16.0mag C/2022 N2 (PANSTARRS)
09:04:13.73 +32:01:48.1 16.2mag C/2022 QE78 (ATLAS)
08:31:39.36 +00:11:58.3 17.4mag C/2022 R6 (PANSTARRS)
18:52:51.33 +18:48:51.1 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:31.65 -11:28:17.8 17.5mag P/2023 B1 (PANSTARRS)
09:06:09.63 -11:20:53.1 17.7mag C/2023 F3 (ATLAS)
21:57:29.29 +63:06:39.5 17.5mag C/2023 H5 (Lemmon)
19:16:03.65 -03:47:43.1 14.1mag C/2023 R1 (PANSTARRS)
21:23:37.47 +86:23:16.0 17.8mag C/2023 X2 (Lemmon)
06:19:38.86 +63:30:07.4 17.2mag C/2024 A1 (ATLAS)
05:20:25.29 +19:22:40.8 11.3mag C/2024 E1 (Wierzchos)
16:17:01.43 +06:56:40.7 17.4mag C/2024 G6 (ATLAS)
20:21:40.72 +16:12:27.4 14.6mag C/2024 J3 (ATLAS)
03:29:26.92 -21:52:32.9 16.3mag C/2024 T5 (ATLAS)
05:19:38.16 +44:27:47.7 17.7mag C/2025 J1 (Borisov)
13:24:51.37 +47:28:42.9 15.3mag C/2025 L1 (ATLAS)
03:30:44.39 -26:45:12.6 17.9mag C/2025 Q3 (ATLAS)
00:21:18.71 +16:50:57.0 8.1mag C/2025 R3 (PANSTARRS)
12:52:39.60 +03:12:50.5 17.4mag C/2025 Y1 (ATLAS)
03:52:58.83 +02:18:53.1 14.2mag C/2026 A1 (MAPS)
00:09:04.20 +37:49:16.3 14.7mag C/2026 B2 (Sun-Gao)
18:49:32.09 -09:32:06.4 11.6mag 10P/Tempel
14:55:39.62 +02:50:14.1 14.3mag 24P/Schaumasse
11:01:57.11 -01:25:15.0 15.7mag 29P/Schwassmann-Wachmann
10:37:33.86 -03:50:30.3 17.0mag 43P/Wolf-Harrington
01:53:56.58 +18:03:45.9 17.3mag 47P/Ashbrook-Jackson
07:17:07.59 +36:16:30.3 17.0mag 63P/Wild
23:33:21.00 -11:02:52.1 15.7mag 65P/Gunn
04:12:25.84 +22:23:49.1 15.9mag 76P/West-Kohoutek-Ikemura
01:13:07.18 +08:53:32.4 14.3mag 78P/Gehrels
23:13:10.41 -08:23:10.4 14.7mag 88P/Howell
02:20:06.14 +21:31:56.7 15.1mag 93P/Lovas
05:01:18.19 +32:27:41.5 16.2mag 123P/West-Hartley
08:32:30.63 +36:47:43.3 16.2mag 124P/Mrkos
02:38:29.56 +14:44:42.1 16.4mag 128P/Shoemaker-Holt
02:54:13.23 +14:53:58.7 17.5mag 131P/Mueller
01:44:10.87 +14:21:48.2 10.5mag 141P/Machholz
01:52:35.24 +06:08:24.4 10.5mag 141P-A/Machholz
00:36:22.08 +01:56:52.6 12.4mag 141P-D/Machholz
02:23:07.66 +07:53:41.5 17.9mag 141P-I/Machholz
01:11:53.08 +00:11:15.0 15.0mag 162P/SidingSpring
14:45:25.34 +00:15:36.4 17.8mag 210P/Christensen
21:48:26.33 -10:38:06.4 17.7mag 218P/LINEAR
17:17:10.87 -13:31:15.4 16.1mag 235P/LINEAR
05:41:52.40 +34:56:22.4 16.8mag 240P/NEAT
07:40:14.60 -04:48:33.9 17.8mag 242P/Spahr
22:25:24.53 -20:03:21.2 17.8mag 260P/McNaught
02:05:11.30 +21:18:37.6 18.0mag 295P/LINEAR
15:41:14.80 +07:12:25.5 17.5mag 391P/Kowalski
07:35:34.50 +21:22:20.8 17.7mag 450P/LONEOS
05:40:52.81 +44:50:02.2 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Apr 19 04:36 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
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
-rw-r--r-- 1 apache apache 5.8K Apr 19 04:36 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 19 04:36 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
16:35:21.390 +30:27:47.12 AT 2026jjg 2026-04-07.79 20.91
17:02:03.120 +41:30:38.89 AT 2026jjf 2026-04-03.89 21.38
17:08:30.580 +41:56:13.61 AT 2026jje 2026-04-03.89 21.47
16:48:25.780 +33:00:44.35 AT 2026jjd 2026-04-03.85 21.29
16:46:02.450 +30:55:42.15 AT 2026jjc 2026-04-03.80 19.57
16:51:04.120 +44:26:50.06 AT 2026jjb 2026-03-30.84 21.02
12:10:02.030 +43:26:37.06 AT 2026jja 2026-03-28.87 21.46
17:56:59.910 +48:20:04.31 AT 2026jiz 2026-03-27.87 20.99
15:23:12.550 +15:30:01.81 AT 2026jiy 2026-03-27.82 21.09
12:45:41.400 +53:52:15.13 AT 2026jix 2026-03-24.70 20.56
12:05:28.040 +47:18:05.03 AT 2026jiw 2026-03-24.69 20.17
12:49:49.680 +44:27:28.62 AT 2026jiv 2026-03-24.69 21.87
12:17:57.600 +45:03:04.77 AT 2026jiu 2026-03-24.69 20.4
11:39:16.940 +45:15:03.67 AT 2026jit 2026-03-24.66 21.06
14:17:33.100 +43:22:03.41 AT 2026jis 2026-03-22.80 20.74
14:45:33.130 +38:26:13.04 AT 2026jir 2026-03-22.80 21.14
14:42:55.800 +38:18:34.13 AT 2026jiq 2026-03-22.80 21.14
12:43:36.900 +28:13:26.06 AT 2026jip 2026-03-20.69 21.81
13:50:42.590 +38:45:33.09 AT 2026jio 2026-03-29.93 20.87
19:45:48.257 -49:40:35.86 AT 2026jin 2026-04-12.35 18.142
-rw-r--r-- 1 apache apache 30K Apr 19 04:36 tns_transients_list.txt
