This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 31.07 +40 20 00.4 7.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.3699+40.3371,2461146.9507,7.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.3699+40.3371 20260416.4507 7.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 16.4507* 00 33 33.95 +40 06 46.8 7.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,7.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 7.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 54.93 +40 52 25.0 8.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 8.73 00:38:30.47 +40:59:13.9
120.30402 -21.81857 galactic And Second-epoch detections are separated by 1.9" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381201304122983936 | 00:38:26.50 +40:59:09.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 30.47 +40 59 13.9 8.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381201304122983936,2461146.9507,8.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381201304122983936 20260416.4507 8.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 43.85 +40 26 13.8 9.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.6869+40.4313,2461146.9507,9.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.6869+40.4313 20260416.4507 9.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 29.65 +40 22 54.0 9.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 38.53 +40 27 16.9 9.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.27 00:39:20.23 +41:55:22.1
120.52304 -20.89234 galactic And Second-epoch detections are separated by 4.4" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381540125502188416 | 00:39:19.52 +41:55:31.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F0 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 20.23 +41 55 22.1 9.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381540125502188416,2461146.9507,9.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381540125502188416 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.39 00:37:34.09 +41:05:42.6
120.12005 -21.70085 galactic And Second-epoch detections are separated by 5.6" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381212264879500800 | 00:37:30.31 +41:05:32.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: M1 1947AnDea...5....1L DO 8429
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 34.09 +41 05 42.6 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381212264879500800,2461146.9507,9.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381212264879500800 20260416.4507 9.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 16.4507* 00 35 55.08 +40 24 03.1 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.9669+40.4062,2461146.9507,9.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.9669+40.4062 20260416.4507 9.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 46.30 +40 32 34.3 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 27.23 +40 43 47.6 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 28 26.85 +40 17 47.8 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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 16.4507* 00 36 44.67 +41 24 43.6 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381413196331782528,2461146.9507,9.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381413196331782528 20260416.4507 9.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.96 00:38:08.54 +41:23:31.1
120.25400 -21.41063 galactic And Second-epoch detections are separated by 6.7" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381245834344063744 | 00:38:06.77 +41:23:27.3 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F6 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 08.54 +41 23 31.1 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381245834344063744,2461146.9507,9.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381245834344063744 20260416.4507 9.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 23 16 50.72 +50 36 39.4 10.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.2256+50.6018,2461146.9507,10.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J349.2256+50.6018 20260416.4507 10.17CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.23 00:38:35.01 +41:49:10.8
120.36729 -20.98806 galactic And Second-epoch detections are separated by 4.7" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381447766524941824 | 00:38:33.25 +41:49:10.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 35.01 +41 49 10.8 11.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381447766524941824,2461146.9507,11.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381447766524941824 20260416.4507 11.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 16.4507* 00 39 43.63 +46 33 18.7 8.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
EF And,2461146.9507,8.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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
EF And 20260416.4507 8.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 23 48 49.51 +48 06 36.5 13.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 13.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 04.90 +49 25 26.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
target,2461146.9507,12.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 12.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 16.4507* 00 29 41.54 +49 37 53.1 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
target,2461146.9507,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 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 16.4507* 00 26 11.09 +49 43 03.1 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,2461146.9507,11.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 32 10.03 +41 48 33.6 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381876537403670400,2461146.9507,10.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381876537403670400 20260416.4507 10.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 16.4507* 00 34 54.42 +43 04 37.2 10.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381670241534963712,2461146.9507,10.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381670241534963712 20260416.4507 10.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 29.93 +40 20 00.8 6.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.3699+40.3371,2461146.9507,5.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.3699+40.3371 20260416.4507 5.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 33 32.90 +40 06 45.2 6.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSV 15119,2461146.9507,6.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 15119 20260416.4507 6.57CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 7.10 00:37:54.13 +40:52:23.1
120.17413 -21.92617 galactic And Second-epoch detections are separated by 3.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381194432175326080 | 00:37:50.75 +40:52:18.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 54.13 +40 52 23.1 7.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381194432175326080,2461146.9507,7.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381194432175326080 20260416.4507 7.10CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 7.43 00:38:29.77 +40:59:11.4
120.30161 -21.81914 galactic And Second-epoch detections are separated by 3.8" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381201304122983936 | 00:38:26.50 +40:59:09.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 29.77 +40 59 11.4 7.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381201304122983936,2461146.9507,7.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381201304122983936 20260416.4507 7.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 43.10 +40 26 10.2 7.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.6869+40.4313,2461146.9507,7.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.6869+40.4313 20260416.4507 7.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 16.4507* 00 30 28.89 +40 22 49.5 7.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,7.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 7.65CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 7.80 00:35:37.81 +40:27:12.6
119.68208 -22.31848 galactic And Second-epoch detections are separated by 4.3" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380795549971142656 | 00:35:34.37 +40:27:01.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: A7V (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 37.81 +40 27 12.6 7.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380795549971142656,2461146.9507,7.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380795549971142656 20260416.4507 7.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 27 17.27 +40 22 49.7 7.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,7.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 7.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 54.41 +40 23 58.2 8.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.9669+40.4062,2461146.9507,8.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.9669+40.4062 20260416.4507 8.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 8.03 00:37:33.52 +41:05:38.3
120.11805 -21.70193 galactic And Second-epoch detections are separated by 3.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381212264879500800 | 00:37:30.31 +41:05:32.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: M1 1947AnDea...5....1L DO 8429
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 33.52 +41 05 38.3 8.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381212264879500800,2461146.9507,8.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381212264879500800 20260416.4507 8.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 45.69 +40 32 28.6 8.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.20CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 8.20 00:37:26.65 +40:43:42.6
120.07182 -22.06552 galactic And Second-epoch detections are separated by 5.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380816779993227008 | 00:37:22.88 +40:43:39.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F6 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 26.65 +40 43 42.6 8.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380816779993227008,2461146.9507,8.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380816779993227008 20260416.4507 8.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 28 26.20 +40 17 41.5 8.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 04.93 +40 40 09.7 8.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 8.53 00:33:36.61 +40:11:00.8
119.24591 -22.56057 galactic And Second-epoch detections are separated by 6.0" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380881999072860544 | 00:33:33.10 +40:10:40.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K5 1947AnDea...5....1L DO 8414
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 33 36.61 +40 11 00.8 8.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380881999072860544,2461146.9507,8.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380881999072860544 20260416.4507 8.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 16.4507* 00 30 24.38 +40 15 09.8 8.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 29 15.36 +40 43 20.6 8.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 03.86 +40 30 26.8 8.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 44.02 +40 12 32.8 8.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,8.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 8.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 16.4507* 00 35 57.94 +40 51 49.5 8.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381020571897718784,2461146.9507,8.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381020571897718784 20260416.4507 8.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 53.29 +41 33 57.4 8.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.9610+41.5555,2461146.9507,8.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.9610+41.5555 20260416.4507 8.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 24.34 +41 00 21.7 8.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381023217597561856,2461146.9507,8.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381023217597561856 20260416.4507 8.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 34 21.87 +40 27 53.0 8.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380979649449253632,2461146.9507,8.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380979649449253632 20260416.4507 8.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 27 36.10 +40 26 32.2 9.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.04 00:36:56.44 +41:38:25.9
120.02844 -21.14948 galactic And Second-epoch detections are separated by 3.7" and 4.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381428933091943040 | 00:36:54.79 +41:38:20.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G7 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 56.44 +41 38 25.9 9.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381428933091943040,2461146.9507,9.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381428933091943040 20260416.4507 9.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 28 29.02 +40 30 50.7 9.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.10CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.07 00:36:25.24 +40:19:01.1
119.83499 -22.46446 galactic And Second-epoch detections are separated by 6.9" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380801769083929984 | 00:36:25.24 +40:19:01.1 (user input) | | 2022yCat.1358....0G | (position from user input) Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F7 (LAMOST DR5) J-Ks=0.350+/-0.041 (G)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 25.24 +40 19 01.1 9.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380801769083929984,2461146.9507,9.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380801769083929984 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.12 00:35:39.62 +41:27:36.6
119.75977 -21.31438 galactic And Second-epoch detections are separated by 4.8" and 4.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381422404741662208 | 00:35:38.56 +41:27:27.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F6 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 39.62 +41 27 36.6 9.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381422404741662208,2461146.9507,9.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381422404741662208 20260416.4507 9.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 16.4507* 00 30 22.21 +41 11 13.4 9.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0491 And,2461146.9507,9.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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
V0491 And 20260416.4507 9.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 02.99 +40 49 20.9 9.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.32 00:39:39.14 +41:39:57.4
120.57223 -21.15180 galactic And Second-epoch detections are separated by 3.9" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381253251753839488 | 00:39:36.07 +41:39:59.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 39.14 +41 39 57.4 9.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381253251753839488,2461146.9507,9.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381253251753839488 20260416.4507 9.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 16.4507* 00 38 21.51 +41 28 33.1 9.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381246723402973696,2461146.9507,9.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381246723402973696 20260416.4507 9.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 16.4507* 00 32 59.19 +40 29 18.5 9.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380994355417112960,2461146.9507,9.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380994355417112960 20260416.4507 9.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 16.4507* 00 34 52.99 +40 29 18.5 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.6980+40.4947,2461146.9507,9.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.6980+40.4947 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.39 00:38:46.25 +41:34:25.5
120.39073 -21.23549 galactic And Second-epoch detections are separated by 3.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381248750627535232 | 00:38:43.72 +41:34:27.7 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F7 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 46.25 +41 34 25.5 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381248750627535232,2461146.9507,9.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381248750627535232 20260416.4507 9.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 16.4507* 00 31 28.64 +41 09 57.6 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381823558983606144,2461146.9507,9.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381823558983606144 20260416.4507 9.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 01.85 +41 13 44.6 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381404507614243968,2461146.9507,9.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381404507614243968 20260416.4507 9.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 04.98 +40 18 30.5 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.47 00:32:33.95 +41:05:05.1
119.10742 -21.64681 galactic And Second-epoch detections are separated by 5.0" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381073726412807936 | 00:32:32.65 +41:05:07.7 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 33.95 +41 05 05.1 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381073726412807936,2461146.9507,9.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381073726412807936 20260416.4507 9.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 16.4507* 00 34 33.17 +40 47 54.9 9.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381017342082660992,2461146.9507,9.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381017342082660992 20260416.4507 9.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 25.76 +40 20 32.0 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.47 00:35:23.18 +40:35:24.9
119.64199 -22.17894 galactic And Second-epoch detections are separated by 8.3" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380823553157903872 | 00:35:19.47 +40:35:14.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 23.18 +40 35 24.9 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380823553157903872,2461146.9507,9.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380823553157903872 20260416.4507 9.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 16.4507* 00 30 45.10 +40 55 22.8 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380975595000062720,2461146.9507,9.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380975595000062720 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.48 00:38:35.34 +41:34:08.9
120.35403 -21.23829 galactic And Second-epoch detections are separated by 3.2" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381248853706750464 | 00:38:32.83 +41:34:10.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K1 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 35.34 +41 34 08.9 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381248853706750464,2461146.9507,9.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381248853706750464 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.49 00:35:10.64 +40:34:31.4
119.59815 -22.19108 galactic And Second-epoch detections are separated by 8.1" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380800222896352896 | 00:35:06.94 +40:34:20.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: M0 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 10.64 +40 34 31.4 9.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380800222896352896,2461146.9507,9.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380800222896352896 20260416.4507 9.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 16.4507* 00 29 21.77 +40 27 26.5 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 40.90 +41 02 44.6 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381398632098991744,2461146.9507,9.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381398632098991744 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.65 00:39:58.57 +42:06:47.9
120.65982 -20.70787 galactic And Second-epoch detections are separated by 5.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381362863618211840 | 00:39:57.08 +42:06:57.7 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 58.57 +42 06 47.9 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381362863618211840,2461146.9507,9.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381362863618211840 20260416.4507 9.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 23.87 +40 19 52.2 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 42.88 +40 37 53.6 9.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380815165086872832,2461146.9507,9.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380815165086872832 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.67 00:38:45.67 +41:53:46.7
120.40702 -20.91329 galactic And Second-epoch detections are separated by 6.0" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381446941891759488 | 00:38:44.63 +41:53:57.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 45.67 +41 53 46.7 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381446941891759488,2461146.9507,9.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381446941891759488 20260416.4507 9.67CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.69 00:38:53.08 +41:56:59.9
120.43459 -20.86090 galactic And Second-epoch detections are separated by 5.7" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381541259374069504 | 00:38:52.12 +41:57:10.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 53.08 +41 56 59.9 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381541259374069504,2461146.9507,9.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381541259374069504 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.68 00:37:56.08 +41:34:06.7
120.22289 -21.23218 galactic And Second-epoch detections are separated by 3.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381435809336024448 | 00:37:53.73 +41:34:06.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 56.08 +41 34 06.7 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381435809336024448,2461146.9507,9.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381435809336024448 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.73 00:37:45.05 +41:03:08.6
120.15440 -21.74553 galactic And Second-epoch detections are separated by 6.5" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381209065129717120 | 00:37:41.05 +41:03:07.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: M4 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 45.05 +41 03 08.6 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381209065129717120,2461146.9507,9.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381209065129717120 20260416.4507 9.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 19.84 +41 38 25.3 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381431170771829760,2461146.9507,9.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381431170771829760 20260416.4507 9.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 59.37 +40 35 00.3 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.71 00:39:41.08 +41:25:56.3
120.56642 -21.38545 galactic And Second-epoch detections are separated by 4.6" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381237210049738752 | 00:39:38.31 +41:26:03.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 41.08 +41 25 56.3 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381237210049738752,2461146.9507,9.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381237210049738752 20260416.4507 9.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 09.91 +41 06 08.1 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381212883354787584,2461146.9507,9.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381212883354787584 20260416.4507 9.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 16.4507* 00 31 21.60 +41 08 32.7 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381823043587532032,2461146.9507,9.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381823043587532032 20260416.4507 9.74CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.71 00:36:02.01 +41:23:30.2
119.82995 -21.38723 galactic And Second-epoch detections are separated by 6.7" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381419557179638784 | 00:36:00.54 +41:23:23.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F9 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 02.01 +41 23 30.2 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381419557179638784,2461146.9507,9.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381419557179638784 20260416.4507 9.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 38.24 +40 22 07.9 9.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 45.13 +40 25 12.1 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.6939+40.4239,2461146.9507,9.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.6939+40.4239 20260416.4507 9.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 05.50 +40 27 53.9 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 47.82 +40 07 07.1 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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 16.4507* 00 37 27.34 +40 54 19.5 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.3552+40.9125,2461146.9507,9.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.3552+40.9125 20260416.4507 9.80CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.86 00:38:11.97 +41:51:02.5
120.29261 -20.95320 galactic And Second-epoch detections are separated by 4.6" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381448900395280256 | 00:38:09.43 +41:51:00.7 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 11.97 +41 51 02.5 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381448900395280256,2461146.9507,9.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381448900395280256 20260416.4507 9.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.85 00:38:35.93 +41:49:11.0
120.37035 -20.98816 galactic And Second-epoch detections are separated by 4.3" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381447766524941824 | 00:38:33.25 +41:49:10.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 35.93 +41 49 11.0 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381447766524941824,2461146.9507,9.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381447766524941824 20260416.4507 9.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 06.52 +41 37 22.2 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381430689734851840,2461146.9507,9.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381430689734851840 20260416.4507 9.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 57.21 +40 14 31.6 9.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.85CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 9.87 00:32:56.52 +40:52:13.7
119.16563 -21.86598 galactic And Second-epoch detections are separated by 6.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381055889412846976 | 00:32:54.37 +40:52:16.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 56.52 +40 52 13.7 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381055889412846976,2461146.9507,9.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381055889412846976 20260416.4507 9.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 24.48 +40 58 01.2 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.5840+40.9642,2461146.9507,9.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J007.5840+40.9642 20260416.4507 9.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 16.4507* 00 38 39.18 +40 31 22.4 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 51.78 +41 04 56.8 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.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 16.4507* 00 38 23.23 +40 11 46.2 9.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,9.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 9.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 37.75 +41 42 12.7 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
WISE J003635.9+414206,2461146.9507,9.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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
WISE J003635.9+414206 20260416.4507 9.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 14.10 +40 14 16.9 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380754279629915136,2461146.9507,9.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380754279629915136 20260416.4507 9.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.03 00:39:08.06 +41:50:06.3
120.47791 -20.97803 galactic And Second-epoch detections are separated by 4.7" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381445803724626304 | 00:39:05.06 +41:50:08.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G4 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 08.06 +41 50 06.3 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381445803724626304,2461146.9507,10.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381445803724626304 20260416.4507 10.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 26.39 +41 27 20.9 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J003724.49+412719.2,2461146.9507,10.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J003724.49+412719.2 20260416.4507 10.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 16.4507* 00 37 52.72 +41 48 01.2 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 381454324939743360,2461146.9507,10.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 381454324939743360 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.04 00:40:07.47 +42:00:15.2
120.68372 -20.81814 galactic And Second-epoch detections are separated by 5.3" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381359668162559104 | 00:40:04.26 +42:00:18.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 40 07.47 +42 00 15.2 10.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381359668162559104,2461146.9507,10.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381359668162559104 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.05 00:38:38.27 +41:14:26.7
120.34500 -21.56670 galactic And Second-epoch detections are separated by 5.6" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381240538650056448 | 00:38:35.62 +41:14:30.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K7 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 38.27 +41 14 26.7 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381240538650056448,2461146.9507,10.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381240538650056448 20260416.4507 10.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 16.4507* 00 29 43.79 +40 45 56.2 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,10.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.08 00:37:48.16 +41:51:57.8
120.21453 -20.93374 galactic And Second-epoch detections are separated by 5.4" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381460479628124416 | 00:37:45.77 +41:51:55.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: A7V (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 48.16 +41 51 57.8 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381460479628124416,2461146.9507,10.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381460479628124416 20260416.4507 10.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 29 46.73 +40 50 25.8 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,10.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 10.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 16.4507* 00 38 18.18 +40 26 01.9 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.5681+40.4345,2461146.9507,10.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.5681+40.4345 20260416.4507 10.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 16.4507* 00 36 13.41 +40 38 51.3 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,10.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 10.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 16.4507* 00 34 43.22 +41 16 42.3 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381044383196366592,2461146.9507,10.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381044383196366592 20260416.4507 10.08CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.11 00:38:21.02 +41:24:20.3
120.29664 -21.39913 galactic And Second-epoch detections are separated by 5.1" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381245177214749184 | 00:38:18.61 +41:24:23.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F0 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 21.02 +41 24 20.3 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381245177214749184,2461146.9507,10.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381245177214749184 20260416.4507 10.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 16.4507* 00 38 41.24 +40 18 11.1 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,10.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.10 00:36:58.93 +41:48:38.8
120.04771 -20.98000 galactic And Second-epoch detections are separated by 6.2" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381456661400796544 | 00:36:56.76 +41:48:33.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 58.93 +41 48 38.8 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381456661400796544,2461146.9507,10.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381456661400796544 20260416.4507 10.10CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.13 00:37:33.31 +39:59:24.2
120.04791 -22.80394 galactic And Second-epoch detections are separated by 8.1" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380734797657525632 | 00:37:34.03 +39:59:36.7 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K1 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 33.31 +39 59 24.2 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380734797657525632,2461146.9507,10.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380734797657525632 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.14 00:39:25.21 +41:39:00.2
120.52494 -21.16552 galactic And Second-epoch detections are separated by 6.1" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381255764308430080 | 00:39:21.93 +41:39:03.8 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 25.21 +41 39 00.2 10.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381255764308430080,2461146.9507,10.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381255764308430080 20260416.4507 10.14CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.19 00:39:35.33 +42:17:44.9
120.59270 -20.52212 galactic And Second-epoch detections are separated by 6.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381575339937644544 | 00:39:34.02 +42:17:52.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 35.33 +42 17 44.9 10.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381575339937644544,2461146.9507,10.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381575339937644544 20260416.4507 10.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 34 10.35 +41 06 42.6 10.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J003408.81+410645.3,2461146.9507,10.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J003408.81+410645.3 20260416.4507 10.20CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.25 00:38:06.81 +41:58:31.2
120.28287 -20.82787 galactic And Second-epoch detections are separated by 7.7" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381451202498750848 | 00:38:05.96 +41:58:40.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 06.81 +41 58 31.2 10.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381451202498750848,2461146.9507,10.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381451202498750848 20260416.4507 10.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 27.86 +41 10 22.4 10.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381216319328622976,2461146.9507,10.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381216319328622976 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.28 00:39:09.71 +41:35:23.2
120.46996 -21.22328 galactic And Second-epoch detections are separated by 5.5" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381254286839685760 | 00:39:06.67 +41:35:26.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F6 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 09.71 +41 35 23.2 10.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381254286839685760,2461146.9507,10.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381254286839685760 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.29 00:39:29.33 +41:17:53.5
120.51987 -21.51759 galactic And Second-epoch detections are separated by 6.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381230093289608704 | 00:39:26.20 +41:18:01.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 29.33 +41 17 53.5 10.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381230093289608704,2461146.9507,10.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381230093289608704 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.34 00:39:59.03 +41:43:27.9
120.64152 -21.09639 galactic And Second-epoch detections are separated by 6.2" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381347333016528512 | 00:39:55.74 +41:43:33.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 59.03 +41 43 27.9 10.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381347333016528512,2461146.9507,10.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381347333016528512 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.42 00:35:47.39 +41:15:19.2
119.77141 -21.52037 galactic And Second-epoch detections are separated by 7.3" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381416460506932736 | 00:35:45.60 +41:15:13.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K7 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 47.39 +41 15 19.2 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381416460506932736,2461146.9507,10.42,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381416460506932736 20260416.4507 10.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 16.4507* 00 38 24.06 +42 04 27.5 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381545618763964032,2461146.9507,10.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381545618763964032 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.50 00:39:38.51 +42:11:43.6
120.59791 -20.62284 galactic And Second-epoch detections are separated by 7.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381551017539222912 | 00:39:37.01 +42:11:53.8 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 38.51 +42 11 43.6 10.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381551017539222912,2461146.9507,10.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381551017539222912 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.43 00:36:13.25 +41:16:53.3
119.86009 -21.49950 galactic And Second-epoch detections are separated by 7.5" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381405053073794048 | 00:36:11.28 +41:16:49.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F7 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 13.25 +41 16 53.3 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381405053073794048,2461146.9507,10.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381405053073794048 20260416.4507 10.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 23 52 36.23 +48 55 11.3 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
Gaia DR3 1940537593812963072,2461146.9507,10.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 1940537593812963072 20260416.4507 10.65CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.56 00:38:26.33 +41:24:02.5
120.31415 -21.40497 galactic And Second-epoch detections are separated by 6.0" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381245486452394624 | 00:38:23.71 +41:24:06.3 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 26.33 +41 24 02.5 10.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381245486452394624,2461146.9507,10.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381245486452394624 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.58 00:37:15.27 +41:50:08.1
120.10353 -20.95826 galactic And Second-epoch detections are separated by 7.1" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381458001430592000 | 00:37:12.94 +41:50:04.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 15.27 +41 50 08.1 10.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381458001430592000,2461146.9507,10.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381458001430592000 20260416.4507 10.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 13.69 +41 35 27.4 10.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381427867940056064,2461146.9507,10.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381427867940056064 20260416.4507 10.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.61 00:38:37.61 +42:02:23.1
120.38846 -20.76872 galactic And Second-epoch detections are separated by 8.2" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381544725410767488 | 00:38:36.56 +42:02:34.4 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 37.61 +42 02 23.1 10.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381544725410767488,2461146.9507,10.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381544725410767488 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.70 00:31:03.20 +41:06:59.0
118.80474 -21.59195 galactic And Second-epoch detections are separated by 7.8" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381821733620943616 | 00:31:01.62 +41:06:57.3 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 03.20 +41 06 59.0 10.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381821733620943616,2461146.9507,10.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381821733620943616 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.69 00:31:28.00 +40:51:06.0
118.86440 -21.86230 galactic And Second-epoch detections are separated by 8.4" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 380970818996539008 | 00:31:25.62 +40:51:03.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 28.00 +40 51 06.0 10.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 380970818996539008,2461146.9507,10.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 380970818996539008 20260416.4507 10.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 16.4507* 00 37 21.32 +41 24 04.2 10.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.3343+41.3995,2461146.9507,10.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.3343+41.3995 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.79 00:31:49.73 +40:55:14.4
118.94404 -21.79920 galactic And Second-epoch detections are separated by 6.6" and 4.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381065200901561344 | 00:31:47.41 +40:55:13.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 49.73 +40 55 14.4 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381065200901561344,2461146.9507,10.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381065200901561344 20260416.4507 10.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 21.36 +40 51 32.5 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.0790+40.8592,2461146.9507,10.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.0790+40.8592 20260416.4507 10.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 09.56 +41 07 44.4 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.7821+41.1304,2461146.9507,10.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J008.7821+41.1304 20260416.4507 10.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.79 00:32:53.19 +41:07:42.3
119.17587 -21.60800 galactic And Second-epoch detections are separated by 8.6" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381063654713703040 | 00:32:51.46 +41:07:49.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 53.19 +41 07 42.3 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381063654713703040,2461146.9507,10.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381063654713703040 20260416.4507 10.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 27.42 +41 48 40.1 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381454977773616384,2461146.9507,10.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381454977773616384 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.77 00:32:09.50 +40:51:47.6
119.00587 -21.86151 galactic And Second-epoch detections are separated by 8.3" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381052973130753664 | 00:32:07.04 +40:51:47.9 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G0 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 09.50 +40 51 47.6 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381052973130753664,2461146.9507,10.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381052973130753664 20260416.4507 10.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 11.90 +40 55 28.9 10.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381725393211068288,2461146.9507,10.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381725393211068288 20260416.4507 10.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 16.4507* 00 28 30.92 +47 40 39.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
ATO J007.1241+47.6719,2461146.9507,10.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J007.1241+47.6719 20260416.4507 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.86 00:38:11.26 +41:34:17.7
120.27376 -21.23177 galactic And Second-epoch detections are separated by 7.8" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381437076349939328 | 00:38:08.44 +41:34:20.8 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 11.26 +41 34 17.7 10.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381437076349939328,2461146.9507,10.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381437076349939328 20260416.4507 10.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 16.4507* 00 37 41.72 +41 32 04.8 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 381438210221640320,2461146.9507,10.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 381438210221640320 20260416.4507 10.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 16.4507* 23 51 19.09 +47 26 34.3 11.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.08CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 10.95 00:38:58.96 +41:45:22.2
120.44332 -21.05539 galactic And Second-epoch detections are separated by 6.2" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381445052105686272 | 00:38:55.71 +41:45:26.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 58.96 +41 45 22.2 10.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381445052105686272,2461146.9507,10.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381445052105686272 20260416.4507 10.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 28.01 +41 37 26.2 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381472505537049088,2461146.9507,11.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381472505537049088 20260416.4507 11.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.04 00:34:50.92 +41:30:57.5
119.60105 -21.24846 galactic And Second-epoch detections are separated by 8.2" and 4.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381473360233659136 | 00:34:49.25 +41:31:01.5 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: K5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 34 50.92 +41 30 57.5 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381473360233659136,2461146.9507,11.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381473360233659136 20260416.4507 11.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.00 00:36:40.43 +41:38:49.9
119.97553 -21.13979 galactic And Second-epoch detections are separated by 8.5" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381431716230750336 | 00:36:38.27 +41:38:47.6 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F0 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 40.43 +41 38 49.9 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381431716230750336,2461146.9507,11.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381431716230750336 20260416.4507 11.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.03 00:39:09.51 +41:19:48.8
120.45503 -21.48246 galactic And Second-epoch detections are separated by 7.6" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381230750418720256 | 00:39:06.40 +41:19:57.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 09.51 +41 19 48.8 11.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381230750418720256,2461146.9507,11.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381230750418720256 20260416.4507 11.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 29 51.46 +40 52 33.7 11.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381719479040312448,2461146.9507,11.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381719479040312448 20260416.4507 11.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.15 00:35:06.20 +41:34:07.1
119.65592 -21.19918 galactic And Second-epoch detections are separated by 8.3" and 4.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381470993707957632 | 00:35:04.53 +41:34:11.8 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G2 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 35 06.20 +41 34 07.1 11.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381470993707957632,2461146.9507,11.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381470993707957632 20260416.4507 11.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.18 00:39:51.74 +41:33:16.7
120.60848 -21.26488 galactic And Second-epoch detections are separated by 8.1" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381251396327969152 | 00:39:48.31 +41:33:19.2 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 51.74 +41 33 16.7 11.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381251396327969152,2461146.9507,11.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381251396327969152 20260416.4507 11.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 16.4507* 00 38 49.36 +41 40 17.7 11.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J009.7012+41.6794,2461146.9507,11.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J009.7012+41.6794 20260416.4507 11.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.23 00:38:19.87 +41:45:43.9
120.31366 -21.04291 galactic And Second-epoch detections are separated by 8.5" and 4.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381447281193378816 | 00:38:16.79 +41:45:46.1 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: F5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 19.87 +41 45 43.9 11.2 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381447281193378816,2461146.9507,11.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381447281193378816 20260416.4507 11.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 16.4507* 00 36 14.68 +41 44 21.0 11.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 47.58 +41 33 09.8 11.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.33CV 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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.35 00:37:41.17 +41:41:48.4
120.18098 -21.10151 galactic And Second-epoch detections are separated by 8.7" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381440340525077632 | 00:37:38.35 +41:41:49.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G3 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 41.17 +41 41 48.4 11.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381440340525077632,2461146.9507,11.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381440340525077632 20260416.4507 11.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 37 51.33 +41 18 32.6 11.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 36 36.65 +41 16 53.0 11.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 17 36.49 +49 39 31.4 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,2461146.9507,11.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 37 43.33 +47 31 11.8 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,2461146.9507,11.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 32 17.22 +40 54 47.7 11.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 30 12.13 +40 54 59.2 11.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381725393211068288,2461146.9507,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381725393211068288 20260416.4507 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 16.4507* 00 38 48.33 +41 31 12.4 11.5 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 31 26.60 +41 14 46.2 11.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 16 51.12 +49 25 24.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,2461146.9507,11.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 23.78 +42 08 03.5 11.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J003924.89+420749.4,2461146.9507,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 J003924.89+420749.4 20260416.4507 11.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 23 44 20.66 +47 15 24.6 11.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1939275835497143296,2461146.9507,11.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 1939275835497143296 20260416.4507 11.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 39 38.06 +41 39 01.8 11.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 37 41.62 +47 31 10.2 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 32 31.12 +40 54 18.1 11.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 17 36.28 +45 43 37.6 11.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 01 53.12 +47 52 08.7 12.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 387291460374190848,2461146.9507,11.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 387291460374190848 20260416.4507 11.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 16.4507* 00 39 13.03 +41 46 44.4 12.0 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,11.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 11.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 16.4507* 00 37 10.96 +41 25 33.1 12.1 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 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 16.4507* 00 21 49.90 +44 52 11.5 10.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0021489+445219,2461146.9507,10.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0021489+445219 20260416.4507 10.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 23 51 17.02 +47 27 28.9 10.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461146.9507,10.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260416.4507 10.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
Mean magnitude and position on the discovery images:
2026 04 16.4507 2461146.9507 11.38 00:38:17.66 +41:33:56.2
120.29478 -21.23883 galactic And Second-epoch detections are separated by 8.6" and 4.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 varaible 381436359091840768 | 00:38:14.65 +41:34:01.0 (Gaia DR3) | | 2022yCat.1358....0G | Gaia3var=NOT_AVAILABLE Gaia DR3 varaible (the VSX policy as of July 2022 is to regard variables from Gaia DR3 as 'known') SpType: G5 (LAMOST DR5)
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 16.4507* 00 38 17.66 +41 33 56.2 11.4 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 varaible 381436359091840768,2461146.9507,11.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 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 varaible 381436359091840768 20260416.4507 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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461146.95106845 16.04.2026 10:49:22.314 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 183
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.88
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 6 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 21105
Objects passed selection criteria: 21080
Measurements per detected object (mean, median, min, max): 3.5 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.5 4.0 2 4
Average stars detected per image: 19289
Average stars matched: 18834.8 (97.645 %)
Memory usage VmPeak: 124956 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 16 05:53:15 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
First image: 2461036.57699117 27.12.2025 01:50:42.037 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Last image: 2461146.95106845 16.04.2026 10:49:22.314 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 1085
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.55
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: 124 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): 134470
Objects passed selection criteria: 134219
Measurements per detected object (mean, median, min, max): 3.5 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.5 4.0 2 4
Average stars detected per image: 123242
Average stars matched: 118958 (96.5245 %)
Memory usage VmPeak: 1958580 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 15 18:49:36 CDT 2026
VaST build number 1.0rc89-18-ga9a0ae89
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-15)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 16 06:08:33 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/TTUQ1b1x1/TTUQ1_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 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
SExtractor catalog cache: saved And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_onlybrightstars_v1
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461146.95039501
Re-using ../asassn_transients_list.txt
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
Re-using ../tocp_transients_list.txt
'../tocp_transients_list.txt' -> 'tocp_transients_list.txt'
Re-using ../tns_transients_list.txt
'../tns_transients_list.txt' -> 'tns_transients_list.txt'
Plate-solving the images
wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
Saving wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits to local_wcs_cache/
'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'local_wcs_cache/wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
Saving wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits to local_wcs_cache/
'wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'local_wcs_cache/wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits exists and is non-empty
Saving wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits to local_wcs_cache/
'wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits'
wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits exists and is non-empty
Saving wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits to local_wcs_cache/
'wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits' -> 'local_wcs_cache/wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits (1st new image)
verification OK: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Image size: 923.0'x609.8' 15.4(deg)x10.2(deg) 9576x6388 pix
Image scale: 5.78"/pix along the X axis and 5.73"/pix along the Y axis
Image center: 00:00:16.552 +45:56:15.98 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:16.552 +45:56:15.98
Angular distance between the image centers 0.0320 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits (2nd new image)
verification OK: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Image size: 922.9'x609.8' 15.4(deg)x10.2(deg) 9576x6388 pix
Image scale: 5.78"/pix along the X axis and 5.73"/pix along the Y axis
Image center: 00:00:16.634 +45:55:50.69 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:16.634 +45:55:50.69
Angular distance between the image centers 0.0388 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:16.552 +45:56:15.98
Second-epoch second image center 00:00:16.634 +45:55:50.69
Angular distance between the image centers 0.00703 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.I2nLJVi5jR
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.Mz8M55Ny1f
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits &> /tmp/tmp.JcWjUWs4MW
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits &> /tmp/tmp.sIqqu4jaFi
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 21978 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0038 to 359.9998 deg, Dec +39.9518 to +51.2135 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0038 to 359.9998 deg, Dec 39.9518 to 51.2135 deg
Loaded 169717 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 58 out of 66 total matches.
Matched with Tycho-2 66 out of 21978 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.835338
a=0.000000 b=1.000000 c=22.835338
From vast_summary.log: estimated ref. image limiting mag.: -7.88
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.96
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.96
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 156 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.5 pix And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.5 pix And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
2.4 pix fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
2.4 pix fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Limiting magnitude estimates:
15.0 mag. And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
15.0 mag. And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
14.6 mag. fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
14.6 mag. fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
All-image limiting magnitude estimate: 14.6 (SNR ) 11.8 (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.I2nLJVi5jR (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2256, passed=21978
Got 21978 stars (including 19693 good ones) from the SExtractor catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 21978 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4507 through 0 to 12.6948, gap 12.6948 to 348.4507
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 203 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 146 matched stars entering correct_measured_positions(), 68 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.79"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 2320 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.33"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4573 through 0 to 12.6998, gap 12.6998 to 348.4573
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 230 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2338 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.32"
Accuracy estimation diagnostic: 173 matched stars entering correct_measured_positions(), 3009 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.42"
Excluding outliers - 173 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.Mz8M55Ny1f (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2250, passed=22050
Got 22050 stars (including 19777 good ones) from the SExtractor catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 22050 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4512 through 0 to 12.6947, gap 12.6947 to 348.4512
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 202 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 142 matched stars entering correct_measured_positions(), 69 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.99"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 135 matched stars entering correct_measured_positions(), 2248 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.05"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4583 through 0 to 12.7006, gap 12.7006 to 348.4583
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.2)
Done reading UCAC5 zone files...
Matched 223 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 2273 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.04"
Accuracy estimation diagnostic: 172 matched stars entering correct_measured_positions(), 3100 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.65"
Excluding outliers - 172 stars left (next iteration limit 148)
The image catalog is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.JcWjUWs4MW (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS-calibrated image found: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Checking if the catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS catalog name: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat
SExtractor catalog parsing summary: zero_flux=6, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1187, passed=16832
Got 16832 stars (including 15622 good ones) from the SExtractor catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat
util/solve_plate_with_UCAC5 got 16832 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.0'
Seting catalog search parameters based on the expected field of view 923.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012819 (46.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.010256 (36.9 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5684 through 0 to 12.7377, gap 12.7377 to 348.5684
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 217 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 168 matched stars entering correct_measured_positions(), 83 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.46"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 166 matched stars entering correct_measured_positions(), 2352 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.95"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5741 through 0 to 121.1590, gap 121.1590 to 348.5741
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 236 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 180 matched stars entering correct_measured_positions(), 2362 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.78"
Accuracy estimation diagnostic: 178 matched stars entering correct_measured_positions(), 2577 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.47"
Excluding outliers - 178 stars left (next iteration limit 182)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits -region wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.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.sIqqu4jaFi (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS-calibrated image found: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Checking if the catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS catalog name: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat
SExtractor catalog parsing summary: zero_flux=2, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1172, passed=16828
Got 16828 stars (including 15636 good ones) from the SExtractor catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat
util/solve_plate_with_UCAC5 got 16828 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 922.9'
Seting catalog search parameters based on the expected field of view 922.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012818 (46.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.010254 (36.9 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5684 through 0 to 12.6194, gap 12.6194 to 348.5684
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 223 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 170 matched stars entering correct_measured_positions(), 88 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.30"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 167 matched stars entering correct_measured_positions(), 2289 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.16"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5703 through 0 to 121.1558, gap 121.1558 to 348.5703
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 242 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 186 matched stars entering correct_measured_positions(), 2305 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.15"
Accuracy estimation diagnostic: 184 matched stars entering correct_measured_positions(), 2641 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.81"
Excluding outliers - 184 stars left (next iteration limit 183)
The image catalog is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits -region wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
Saving fully-calibrated image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
Saving fully-calibrated image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits'
Saving fully-calibrated image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits'
Preparing the HTML report for the field And-01-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out09952.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31328.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31329.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31332.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31335.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31339.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31341.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31344.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31345.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31348.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31349.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31353.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31357.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31359.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31360.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31374.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31375.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31495.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 47s
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: 13s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31327_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31327_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31329_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31329_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31332_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31332_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31334_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31334_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:37:35.30 +41:25:11.7 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31335_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31335_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31339_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31339_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31341_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31341_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31344_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31344_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31345_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31345_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31348_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31348_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31353_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31353_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31357_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31357_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31360_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31360_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31362_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31362_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31370_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31370_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31371_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31371_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31372_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31372_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31374_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31374_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31375_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31375_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31376_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31376_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31378_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31378_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31382_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31382_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31383_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31383_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31392_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31392_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31394_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31394_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31397_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31397_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31398_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31398_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31412_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31412_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31413_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31413_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31414_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31414_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31416_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31416_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31418_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31418_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31423_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31423_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31424_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31424_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31427_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31427_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31428_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31428_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31429_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31429_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31432_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31432_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31435_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31435_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31436_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31436_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31440_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31440_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31445_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31445_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31451_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31451_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31452_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31452_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31455_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31455_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31457_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31457_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31458_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31458_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31463_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31463_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31465_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31465_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31466_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31466_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31468_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31468_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31471_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31471_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31472_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31472_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31473_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31473_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31475_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31475_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31477_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31477_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31478_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31478_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31481_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31481_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31482_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31482_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31484_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31484_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31489_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31489_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31495_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 31495_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31496_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31496_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (35.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31501_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31501_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31505_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31505_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31506_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31506_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31507_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31507_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31508_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31508_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31511_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31511_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31514_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31514_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31515_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31515_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31518_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31518_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31524_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31524_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31525_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31525_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31527_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31527_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31528_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31528_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31534_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31534_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31535_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31535_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31536_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31536_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31537_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31537_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31540_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31540_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31541_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31541_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31544_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31544_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31545_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31545_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31549_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31549_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31552_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31552_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31553_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31553_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31556_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31556_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31558_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31558_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31560_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31560_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31561_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31561_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31563_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31563_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31565_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31565_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31567_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31567_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31572_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31572_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31576_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31576_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31577_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31577_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31579_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31579_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31581_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31581_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31583_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31583_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31584_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31584_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31589_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31589_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31590_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31590_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31595_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31595_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31597_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31597_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31599_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31599_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31600_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31600_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31603_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31603_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31608_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31608_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31609_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31609_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31610_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31610_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31612_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31612_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31616_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31616_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31617_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31617_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31620_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31620_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31626_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31626_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31647_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31647_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (280036.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31652_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31652_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31655_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31655_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31659_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31659_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31662_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31662_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31663_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31663_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31666_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31666_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31667_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31667_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31670_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31670_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31674_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31674_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31675_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31675_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31680_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31680_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31681_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31681_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31690_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31690_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 31692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 09952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 15590_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 15590_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 10889_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 10889_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 3s
make_report_in_HTML.sh TOTAL: 63s
Prepared the HTML report for the field And-01-Q1b1x1 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:39:43.63 +46:33:18.7
00:37:31.07 +40:20:00.4
00:33:33.95 +40:06:46.8
00:37:54.93 +40:52:25.0
00:38:30.47 +40:59:13.9
00:38:43.85 +40:26:13.8
00:30:29.65 +40:22:54.0
00:35:38.53 +40:27:16.9
00:39:20.23 +41:55:22.1
00:37:34.09 +41:05:42.6
00:35:55.08 +40:24:03.1
00:30:46.30 +40:32:34.3
00:37:27.23 +40:43:47.6
00:28:26.85 +40:17:47.8
00:36:44.67 +41:24:43.6
00:38:08.54 +41:23:31.1
23:16:50.72 +50:36:39.4
00:38:35.01 +41:49:10.8
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 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
SExtractor catalog cache: saved And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat to cache
SExtractor catalog cache: saved And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Creating symlink local_wcs_cache/wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Creating symlink local_wcs_cache/wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Creating symlink local_wcs_cache/exclusion_list.txt
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
Plate-solving the images
wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits exists and is non-empty
wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits exists and is non-empty
wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits exists and is non-empty
wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits (1st reference image)
verification OK: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Image size: 924.9'x628.2' 15.4(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.80"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 00:00:19.361 +45:58:07.34 J2000 4789.000 3195.000
###################################
The image scale is 5.80"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits (1st new image)
verification OK: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Image size: 923.0'x609.8' 15.4(deg)x10.2(deg) 9576x6388 pix
Image scale: 5.78"/pix along the X axis and 5.73"/pix along the Y axis
Image center: 00:00:16.552 +45:56:15.98 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:16.552 +45:56:15.98
Angular distance between the image centers 0.0320 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits (2nd new image)
verification OK: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Image size: 922.9'x609.8' 15.4(deg)x10.2(deg) 9576x6388 pix
Image scale: 5.78"/pix along the X axis and 5.73"/pix along the Y axis
Image center: 00:00:16.634 +45:55:50.69 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:19.361 +45:58:07.34
Second-epoch image center 00:00:16.634 +45:55:50.69
Angular distance between the image centers 0.0388 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:16.552 +45:56:15.98
Second-epoch second image center 00:00:16.634 +45:55:50.69
Angular distance between the image centers 0.00703 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits &> /tmp/tmp.WsVepxREwJ
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits &> /tmp/tmp.HlDP4Ww0Ic
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits &> /tmp/tmp.qCqgH0Uvg2
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits &> /tmp/tmp.qu51iDHnfN
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Calibrating the magnitude scale
Found non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
Found non-empty wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits and wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
The reference image (wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits) and catalog (wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat) found
'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat' -> 'wcsmag.cat'
Read 142009 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 359.9998 deg, Dec +39.9057 to +51.2155 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0001 to 359.9998 deg, Dec 39.9057 to 51.2155 deg
Loaded 170564 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 91 out of 117 total matches.
Matched with Tycho-2 117 out of 142009 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 21.239432
a=0.000000 b=1.000000 c=21.239432
From vast_summary.log: estimated ref. image limiting mag.: -7.55
Updating vast_summary.log: Estimated ref. image limiting mag.: 13.69
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 13.69
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 980 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.2 pix And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
2.2 pix And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
2.4 pix fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
2.4 pix fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Limiting magnitude estimates:
13.7 mag. And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
13.7 mag. And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
13.3 mag. fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
13.3 mag. fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
All-image limiting magnitude estimate: 13.3 (SNR ) 12.6 (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.WsVepxREwJ (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits' -> 'wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS_IMAGE_NAME=wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS-calibrated image found: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Checking if the catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
WCS catalog name: wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=63, blended=18012, passed=141946
Got 141946 stars (including 123706 good ones) from the SExtractor catalog wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat
util/solve_plate_with_UCAC5 got 141946 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4418 through 0 to 12.7147, gap 12.7147 to 348.4418
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 204 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 151 matched stars entering correct_measured_positions(), 79 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 145 matched stars entering correct_measured_positions(), 15622 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.16"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4528 through 0 to 12.7273, gap 12.7273 to 348.4528
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 220 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 179 matched stars entering correct_measured_positions(), 15631 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.15"
Accuracy estimation diagnostic: 179 matched stars entering correct_measured_positions(), 19869 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.27"
Excluding outliers - 179 stars left (next iteration limit 159)
The image catalog is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits -region wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.HlDP4Ww0Ic (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits' -> 'wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS_IMAGE_NAME=wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS-calibrated image found: wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Checking if the catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits alredy exist and is non-empty...
Catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat corresponding to the image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
WCS catalog name: wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=62, blended=18105, passed=141741
Got 141741 stars (including 123418 good ones) from the SExtractor catalog wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat
util/solve_plate_with_UCAC5 got 141741 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 924.9'
Seting catalog search parameters based on the expected field of view 924.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012846 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010277 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4216 through 0 to 12.6947, gap 12.6947 to 348.4216
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 199 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 147 matched stars entering correct_measured_positions(), 78 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.77"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 141 matched stars entering correct_measured_positions(), 15340 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.76"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.4332 through 0 to 12.6945, gap 12.6945 to 348.4332
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.9 to 51.2)
Done reading UCAC5 zone files...
Matched 222 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 176 matched stars entering correct_measured_positions(), 15352 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.73"
Accuracy estimation diagnostic: 175 matched stars entering correct_measured_positions(), 19075 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.80"
Excluding outliers - 175 stars left (next iteration limit 155)
The image catalog is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits -region wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.qCqgH0Uvg2 (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS-calibrated image found: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Checking if the catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
WCS catalog name: wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat
SExtractor catalog parsing summary: zero_flux=6, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=21, blended=9171, passed=107220
Got 107220 stars (including 97880 good ones) from the SExtractor catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat
util/solve_plate_with_UCAC5 got 107220 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.0'
Seting catalog search parameters based on the expected field of view 923.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012819 (46.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.010256 (36.9 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5396 through 0 to 12.7522, gap 12.7522 to 348.5396
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.8 to 51.2)
Done reading UCAC5 zone files...
Matched 219 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 163 matched stars entering correct_measured_positions(), 82 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.91"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 153 matched stars entering correct_measured_positions(), 12039 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 14.67"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5463 through 0 to 121.1579, gap 121.1579 to 348.5463
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.8 to 51.2)
Done reading UCAC5 zone files...
Matched 240 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 187 matched stars entering correct_measured_positions(), 12069 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 14.63"
Accuracy estimation diagnostic: 184 matched stars entering correct_measured_positions(), 14182 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.06"
Excluding outliers - 184 stars left (next iteration limit 168)
The image catalog is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits -region wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.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.qu51iDHnfN (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS_IMAGE_NAME=wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS-calibrated image found: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Checking if the catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits alredy exist and is non-empty...
Catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat corresponding to the image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
WCS catalog name: wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat
SExtractor catalog parsing summary: zero_flux=5, no_flux_err=0, no_mag=1, no_mag_err=0, low_SNR=17, blended=9115, passed=105809
Got 105809 stars (including 96540 good ones) from the SExtractor catalog wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat
util/solve_plate_with_UCAC5 got 105809 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 922.9'
Seting catalog search parameters based on the expected field of view 922.9 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012818 (46.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.010254 (36.9 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5399 through 0 to 12.7528, gap 12.7528 to 348.5399
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.8 to 51.2)
Done reading UCAC5 zone files...
Matched 222 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 171 matched stars entering correct_measured_positions(), 91 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.86"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 162 matched stars entering correct_measured_positions(), 12593 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 14.15"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 348.5464 through 0 to 12.7535, gap 12.7535 to 348.5464
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 39.8 to 51.2)
Done reading UCAC5 zone files...
Matched 249 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 195 matched stars entering correct_measured_positions(), 12617 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 14.13"
Accuracy estimation diagnostic: 193 matched stars entering correct_measured_positions(), 15598 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.78"
Excluding outliers - 193 stars left (next iteration limit 178)
The image catalog is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits -region wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_And-01-Q1b1x1_2025-12-26_19-50-42_20.00sec_-14.90C_LIGHT_0050.fits
Saving fully-calibrated image wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_And-01-Q1b1x1_2025-12-26_19-51-17_20.00sec_-15.00C_LIGHT_0051.fits
Saving fully-calibrated image wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_fd_And-01-Q1b1x1_2026-04-16_05-48-24_20.00sec_-5.00C_LIGHTs_0372.fits
Saving fully-calibrated image wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-16_CI_And-01-Q1b1x1_055016_TTUQ1b1x1_27839_x5AvBqCs/wcs_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373.fits
Preparing the HTML report for the field And-01-Q1b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_local.txt__out155082.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164533.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164604.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164629.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164640.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164667.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164668.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164672.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164673.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164676.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164679.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164685.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164686.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164688.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164689.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164694.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164695.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164700.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164704.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164705.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164711.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164715.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164718.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164722.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164723.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164724.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164726.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164728.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164729.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164731.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164741.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164743.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164744.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164745.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164751.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164760.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164770.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164771.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164773.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164775.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164776.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164779.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164780.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164782.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164784.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164786.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164787.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164789.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164790.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164791.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164794.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164798.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164809.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164813.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164817.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164819.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164820.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164821.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164825.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164826.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164828.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164829.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164831.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164832.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164839.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164841.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164842.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164843.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164846.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164851.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164853.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164854.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164858.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164859.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164866.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164872.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164874.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164878.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164883.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164885.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164892.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164894.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164899.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164907.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164911.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164913.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164916.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164918.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164922.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164924.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164926.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164928.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164929.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164930.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164931.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164934.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164935.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164943.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164948.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164949.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164956.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164972.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164976.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164980.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out164993.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165005.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165011.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165029.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165033.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165045.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165054.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165062.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165079.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165082.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165103.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165109.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165113.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165142.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165146.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165150.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165154.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165155.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165159.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165170.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165175.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165190.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165210.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165224.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165226.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165244.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165245.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165249.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165263.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165303.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165328.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165340.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165397.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165408.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165411.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165439.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165454.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165471.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165494.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165500.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165513.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165559.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165588.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165593.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165596.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165635.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165645.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165675.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165737.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165781.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165809.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165856.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165867.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165926.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out166146.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out59955.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out91789.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 373s
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: 100s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164529_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164529_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (35.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164567_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164567_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (31.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164570_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164570_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164572_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164572_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164586_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164586_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164588_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164588_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164593_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164593_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164597_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164597_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164603_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164603_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164604_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164604_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164616_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164616_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164621_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164621_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (27.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164623_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164623_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164625_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164625_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164627_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164627_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164628_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164628_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164629_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164629_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164630_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164630_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164634_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164634_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164636_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164636_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (30.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164640_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164640_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164641_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164641_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164647_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164647_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164651_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164651_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164653_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164653_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164654_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164654_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164655_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164655_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164661_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164661_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164662_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164662_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164663_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164663_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164665_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164665_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (33.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164667_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164667_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164669_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164669_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164673_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164673_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164678_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164678_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:37:35.08 +41:25:12.2 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164685_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164685_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164686_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164686_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164689_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164689_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164691_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164691_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:39:20.28 +41:55:21.9 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164694_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164694_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164695_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164695_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164700_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164700_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164704_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164704_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164705_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164705_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164707_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164707_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:36:44.70 +41:24:41.1 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164711_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164711_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164715_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164715_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164718_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164718_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164721_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164721_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:38:08.62 +41:23:28.2 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164722_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164722_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164723_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164723_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164724_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164724_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164726_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164726_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164728_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164728_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164729_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164729_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164731_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164731_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164741_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164741_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164743_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164743_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164744_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164744_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164745_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164745_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164753_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164753_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (30.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164766_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164766_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164770_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164770_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164771_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164771_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164773_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164773_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164775_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164775_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164779_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164779_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164780_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164780_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164784_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164784_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164786_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164786_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164787_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164787_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164789_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164789_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164790_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164790_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164791_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164791_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164798_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164798_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164806_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164806_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164809_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164809_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164813_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164813_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164817_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164817_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164818_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164818_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164819_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164819_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164820_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164820_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164825_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164825_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164826_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164826_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164828_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164828_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164829_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164829_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164831_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164831_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164832_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164832_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164839_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164839_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164841_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164841_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164843_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164843_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164846_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164846_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164848_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164848_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164849_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164849_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164851_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164851_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164853_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164853_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164854_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164854_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164858_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164858_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164859_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164859_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164866_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164866_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164868_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164868_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164872_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164872_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164873_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164873_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164874_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164874_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164878_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164878_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164880_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164880_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164881_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164881_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164883_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164883_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164884_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164884_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164885_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164885_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164892_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164892_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164894_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164894_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164896_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164896_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164902_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164902_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164910_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164910_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164911_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164911_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164913_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164913_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164916_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164916_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164918_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164918_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164919_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164919_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164921_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164921_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164922_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164922_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164924_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164924_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164928_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164928_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164929_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164929_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164930_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164930_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164931_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164931_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164934_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164934_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164935_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164935_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164936_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164936_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164939_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164939_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164940_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164940_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164943_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164943_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164945_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164945_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164946_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164946_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164948_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164948_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164949_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164949_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164955_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164955_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164956_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164956_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164960_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164960_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164966_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164966_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164967_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164967_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164972_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164972_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164973_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164973_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164974_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164974_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164976_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164976_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164977_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164977_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164978_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164978_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164980_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164980_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164981_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164981_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164985_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164985_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164987_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164987_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164989_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164989_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164993_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 164993_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164994_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164994_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164997_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164997_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164999_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 164999_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165003_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165003_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165004_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165004_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165005_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165005_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165008_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165008_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165011_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165011_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165013_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165013_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165017_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165017_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165018_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165018_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165019_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165019_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165026_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165026_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165028_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165028_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165029_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165029_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165030_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165030_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165033_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165033_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165035_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165035_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165044_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165044_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165045_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165045_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165049_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165049_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165054_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165054_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165055_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165055_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165061_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165061_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165062_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165062_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165064_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165064_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165065_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165065_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165066_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165066_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165070_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165070_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165079_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165079_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165080_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165080_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165081_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165081_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165083_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165083_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165084_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165084_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165095_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165095_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165097_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165097_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165100_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165100_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165101_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165101_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165103_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165103_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165104_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165104_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165109_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165109_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165113_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165113_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165121_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165121_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165122_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165122_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165123_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165123_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165124_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165124_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165126_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165126_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165127_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165127_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165128_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165128_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165130_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165130_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165135_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165135_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165142_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165142_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165145_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165145_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165146_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165146_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165147_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165147_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165149_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165149_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165150_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165150_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165151_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165151_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165152_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165152_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165153_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165153_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165154_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165154_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165155_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165155_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165156_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165156_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165159_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165159_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165160_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165160_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165163_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165163_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165167_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165167_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165170_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165170_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165171_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165171_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165175_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165175_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165176_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165176_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165177_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165177_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165179_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165179_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165182_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165182_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165187_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165187_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165188_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165188_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165190_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165190_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165192_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165192_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165194_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165194_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165195_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165195_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165199_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165199_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165210_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165210_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165213_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165213_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165214_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165214_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165215_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165215_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165216_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165216_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165217_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165217_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165219_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165219_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165220_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165220_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165223_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165223_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165224_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165224_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165226_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165226_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165229_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165229_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165230_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165230_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165234_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165234_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165237_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165237_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165240_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165240_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165242_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165242_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165245_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165245_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165249_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165249_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165252_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165252_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165255_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165255_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165256_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165256_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165262_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165262_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165263_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165263_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165264_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165264_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165266_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165266_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165269_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165269_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165272_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165272_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165275_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165275_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165278_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165278_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165279_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165279_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165280_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165280_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165282_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165282_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165283_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165283_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165285_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165285_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165287_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165287_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165289_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165289_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165291_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165291_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165292_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165292_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165294_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165294_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165295_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165295_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165296_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165296_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165303_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165303_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165305_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165305_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165307_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165307_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165309_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165309_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165310_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165310_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165313_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165313_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165315_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165315_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165318_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165318_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165319_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165319_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165321_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165321_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165327_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165327_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165329_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165329_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165331_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165331_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165333_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165333_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165337_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165337_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165338_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165338_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165340_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165340_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165342_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165342_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165344_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165344_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165347_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165347_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165350_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165350_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165356_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165356_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165358_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165358_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165363_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165363_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165364_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165364_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165365_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165365_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165368_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165368_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (33.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165372_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165372_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165373_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165373_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165378_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165378_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165379_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165379_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165381_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165381_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165382_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165382_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165383_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165383_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165384_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165384_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165386_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165386_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165389_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165389_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165392_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165392_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165393_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165393_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165395_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165395_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165396_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165396_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165397_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165397_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165398_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165398_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165399_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165399_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165403_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165403_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165406_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165406_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165407_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165407_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165408_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165408_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165411_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165411_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165414_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165414_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165416_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165416_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165420_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165420_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165429_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165429_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165431_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165431_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165432_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165432_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165437_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165437_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165439_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165439_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165441_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165441_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165442_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165442_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165447_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165447_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165448_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165448_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165451_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165451_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165452_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165452_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165454_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165454_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165455_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165455_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165457_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165457_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165458_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165458_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165459_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165459_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165460_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165460_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165466_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165466_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165467_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165467_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165471_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165471_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165475_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165475_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165476_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165476_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165479_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165479_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165480_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165480_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165481_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165481_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165485_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165485_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165487_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165487_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165493_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165493_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165494_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165494_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165497_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165497_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165499_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165499_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165500_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165500_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165504_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165504_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165508_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165508_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165511_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165511_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165512_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165512_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165513_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165513_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165515_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165515_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165516_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165516_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165521_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165521_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165526_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165526_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165527_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165527_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165538_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165538_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165542_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165542_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165543_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165543_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165544_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165544_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165548_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165550_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165550_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165555_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165555_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165559_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165559_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165568_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165568_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165573_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165573_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165576_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165576_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165578_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165578_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165584_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165584_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165588_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165588_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165593_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165593_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165596_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165596_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165598_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165598_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165602_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165602_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165607_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165607_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165608_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165608_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165611_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165611_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165613_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165613_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165614_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165614_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165615_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165615_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165617_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165617_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165621_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165621_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165623_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165623_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165625_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165625_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165631_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165631_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165632_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165634_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165634_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165635_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165635_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165636_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165636_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165637_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165640_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165640_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165641_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165641_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165643_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165643_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165648_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165648_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165651_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165651_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165653_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165653_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165654_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165654_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165657_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165657_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165664_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165664_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165665_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165665_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165666_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165666_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165670_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165670_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165673_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165673_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165675_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165675_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165677_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165677_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165682_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165682_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165683_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165683_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165684_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165684_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165686_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165686_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165689_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165689_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165691_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165691_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165693_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165693_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165697_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165697_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165699_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165699_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165704_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165704_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165705_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165705_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165706_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165706_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165707_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165707_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165708_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165708_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165711_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165711_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165714_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165714_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165715_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165715_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165716_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165716_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165722_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165722_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165731_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165731_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165732_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165732_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165733_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165733_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165734_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165734_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165737_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165737_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165738_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165738_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165742_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165742_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165743_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165743_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165745_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165745_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165748_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165748_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165750_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165750_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165752_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165752_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165753_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165753_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165758_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165758_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165759_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165759_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165762_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165762_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165764_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165764_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165765_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165765_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165766_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165766_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165769_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165769_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165770_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165770_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165771_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165771_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165772_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165772_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165773_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165773_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165775_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165775_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165780_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165780_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165781_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165781_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165783_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165783_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165784_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165784_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165785_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165785_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165790_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165790_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (31.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165791_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165791_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165797_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165797_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165798_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165798_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165803_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165803_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165805_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165805_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165809_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165809_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165812_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165812_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165813_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165813_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165815_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165815_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165816_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165816_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165817_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165817_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165820_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165820_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165826_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165826_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165829_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165829_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165830_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165830_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165832_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165832_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165840_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165840_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165844_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165844_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165845_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165845_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165847_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165847_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165854_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165854_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165855_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165855_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165856_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165856_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165858_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165858_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165859_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165859_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165862_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165862_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165867_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165867_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165868_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165868_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165869_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165869_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165872_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165872_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165874_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165874_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165875_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165875_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165876_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165876_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165880_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165880_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165881_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165881_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165882_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165882_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165883_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165883_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165891_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165891_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (36.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165900_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165900_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165904_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165904_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165905_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165905_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165913_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165913_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165916_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165916_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (29.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165917_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165917_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165919_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165919_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165920_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165920_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165925_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165925_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 165926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165928_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165928_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165930_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165930_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165937_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165937_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165938_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165938_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165942_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165942_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165947_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165947_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165948_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165948_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165952_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165954_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165954_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165959_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165959_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165960_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165960_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165961_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165961_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165962_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165962_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165964_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165964_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165967_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165967_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165968_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165968_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165971_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165971_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165974_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165974_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165977_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165977_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165978_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165978_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165984_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165984_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165986_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165986_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165989_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165989_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165991_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165991_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165998_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 165998_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166000_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166000_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166007_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166007_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166013_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166013_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166014_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166014_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166017_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166017_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166020_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166020_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166024_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166024_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166025_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166025_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166027_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166027_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166028_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166028_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166029_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166029_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166031_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166031_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166032_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166032_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166033_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166033_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166035_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166035_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166038_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166038_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166039_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166039_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166041_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166041_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166043_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166043_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166045_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166045_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166047_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166047_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166048_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166048_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166050_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166050_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166051_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166051_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166054_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166054_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166061_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166061_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166063_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166063_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166065_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166065_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166068_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166068_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166070_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166070_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166073_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166073_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166074_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166074_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166075_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166075_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166077_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166077_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166084_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166084_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166086_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166086_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166087_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166087_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166089_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166089_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166091_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166091_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166094_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166094_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166095_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166095_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166097_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166097_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166105_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166105_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166107_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166107_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166109_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166109_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166111_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166111_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166113_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166113_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166116_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166116_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166118_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166118_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166119_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166119_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166121_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166121_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166122_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166122_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166123_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166123_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166124_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166124_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166127_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166127_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166130_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166130_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166131_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166131_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166137_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166137_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166139_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166139_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166146_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 166146_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166147_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166147_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166151_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166151_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (31.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166156_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166156_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166157_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166157_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166161_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166161_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166162_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166162_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166166_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166166_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166168_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166168_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166169_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166169_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166172_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166172_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166173_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166173_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166175_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166175_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166176_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166176_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166181_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166181_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166183_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166183_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166184_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166184_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166185_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166185_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166187_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166187_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166191_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166191_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166199_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166199_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166201_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166201_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166204_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166204_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166206_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166206_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166218_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166218_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166219_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166219_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166221_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166221_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166226_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166226_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166228_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166228_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166232_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166232_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166233_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166233_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166234_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166234_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166236_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166236_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166238_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166238_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166239_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166239_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166240_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166240_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (37.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166242_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166242_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166243_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166243_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166245_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166245_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166246_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166246_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166248_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166248_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166256_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166256_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166258_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166258_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166263_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166263_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166268_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166268_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166270_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166270_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166275_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166275_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166276_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166276_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166279_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166279_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (33.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166280_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166280_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166281_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166281_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166282_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166282_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166294_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166294_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166295_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166295_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166296_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166296_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166297_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166297_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166304_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166304_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166305_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166305_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166312_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166312_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166315_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166315_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166316_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166316_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166328_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166331_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166331_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166332_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166332_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166334_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166334_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166336_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166336_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166345_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166345_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166351_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166351_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166353_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166353_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166354_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166354_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166355_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166355_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166357_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166357_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (34.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166359_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166363_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166363_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166364_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166364_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166365_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166365_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166366_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166366_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166368_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166368_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166374_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166374_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166381_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166381_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166384_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166384_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166385_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166385_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166389_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166389_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166390_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166390_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166395_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166395_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166400_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166400_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166407_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166407_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166418_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166418_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166421_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166421_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166425_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166425_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166430_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166430_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166437_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166437_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166438_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166438_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166442_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166442_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166443_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166443_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166446_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166446_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166447_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166447_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (39.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166448_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166448_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166453_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166465_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166465_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166467_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166467_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166469_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166469_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166472_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166472_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166484_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166484_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166487_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166487_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166488_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166490_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166495_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166495_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166498_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166498_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (33.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166502_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166502_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (36.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166504_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166504_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166505_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166505_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166512_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166512_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166520_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166520_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166522_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166530_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166530_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166533_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166546_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166546_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166552_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166552_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166554_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166554_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166555_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166555_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166556_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166556_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166557_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166557_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166560_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166560_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166561_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166561_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166564_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166571_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166571_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166574_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166581_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166581_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166587_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166589_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166589_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166592_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166596_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166596_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (38.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166598_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166598_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166599_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166599_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166601_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166601_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (27.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166606_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166610_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166610_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166614_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166614_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166615_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166615_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166624_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166629_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166629_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166633_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166638_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166645_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166646_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166646_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166649_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166650_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166650_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166658_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166660_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (27.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166661_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166661_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166668_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166671_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166672_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166676_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166677_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166677_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166679_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166682_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166682_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166685_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166685_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166692_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166697_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166697_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166699_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166699_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166703_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166703_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166708_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166708_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166726_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166726_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166727_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166727_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166732_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166732_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166733_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166733_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166740_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166740_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166747_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166748_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166748_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166751_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166760_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166763_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166763_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166765_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166765_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (29.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166776_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166782_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166786_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166786_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166796_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166796_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166799_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166799_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166811_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166811_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166812_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166812_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166814_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166814_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166816_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166816_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166821_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166838_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166838_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166840_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166840_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166842_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166844_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166844_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166851_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166851_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166862_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166862_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166863_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166863_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166879_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166879_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166884_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166884_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166899_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166902_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166902_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166907_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166909_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166909_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166911_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166911_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166926_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166935_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166935_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166938_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166938_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166939_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166939_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166941_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166961_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166961_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166975_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166975_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166987_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166987_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166993_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 166993_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167004_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167004_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167006_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167006_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167019_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167019_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167024_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167024_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167026_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167026_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167049_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167049_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (36.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167050_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167050_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167059_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167066_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167066_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167071_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167072_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167072_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167100_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167100_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167107_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167107_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (27.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167118_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167118_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167128_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167128_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167137_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167137_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167145_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167145_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167149_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167149_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167150_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167150_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167158_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167182_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167182_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167190_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167190_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167191_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167191_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167193_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167193_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167194_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167194_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167202_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167202_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (29.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167215_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167215_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167218_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167218_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167221_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167221_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167223_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167223_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167227_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167227_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167229_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167229_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167232_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167232_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167241_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167244_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (39.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167252_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167252_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167254_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167254_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167267_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167273_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167291_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167291_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167299_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167299_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167304_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167304_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167307_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167307_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167321_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167321_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167323_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167324_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167324_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167325_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167335_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167335_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167349_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 167386_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 167386_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 161085_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91789_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 91789_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 91141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 91141_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 127674_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 127674_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 05293_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 05293_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69154_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 69154_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 101380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 101380_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 137188_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 137188_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 59955_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 59955_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 104338_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 104338_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 101276_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 101276_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 16153_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 16153_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 77205_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 77205_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57324_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 57324_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 118010_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 118010_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
Preparing report for the candidate 155082_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 60983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 60983_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
**** FOUND 00:39:43.65 +46:33:19.7 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 67474_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 67474_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 117340_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 117340_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 153477_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 153477_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140014_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 140014_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 39628_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 39628_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (34.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 104794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 104794_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 152688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 152688_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36021_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 36021_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (29.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373
The candidate 52886_fd_And-01-Q1b1x1_2026-04-16_05-49-22_20.00sec_-5.00C_LIGHTs_0373 did not pass the final checks
Rejecting candidate due to large distance (34.4") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 12s
make_report_in_HTML.sh TOTAL: 485s
Prepared the HTML report for the field And-01-Q1b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:39:43.63 +46:33:18.7
00:37:31.07 +40:20:00.4
00:33:33.95 +40:06:46.8
00:37:54.93 +40:52:25.0
00:38:30.47 +40:59:13.9
00:38:43.85 +40:26:13.8
00:30:29.65 +40:22:54.0
00:35:38.53 +40:27:16.9
00:39:20.23 +41:55:22.1
00:37:34.09 +41:05:42.6
00:35:55.08 +40:24:03.1
00:30:46.30 +40:32:34.3
00:37:27.23 +40:43:47.6
00:28:26.85 +40:17:47.8
00:36:44.67 +41:24:43.6
00:38:08.54 +41:23:31.1
23:16:50.72 +50:36:39.4
00:38:35.01 +41:49:10.8
00:38:17.66 +41:33:56.2
23:48:49.51 +48:06:36.5
00:31:04.90 +49:25:26.3
00:29:41.54 +49:37:53.1
00:26:11.09 +49:43:03.1
00:32:10.03 +41:48:33.6
00:34:54.42 +43:04:37.2
00:37:29.93 +40:20:00.8
00:33:32.90 +40:06:45.2
00:37:54.13 +40:52:23.1
00:38:29.77 +40:59:11.4
00:38:43.10 +40:26:10.2
00:30:28.89 +40:22:49.5
00:35:37.81 +40:27:12.6
00:27:17.27 +40:22:49.7
00:35:54.41 +40:23:58.2
00:37:33.52 +41:05:38.3
00:30:45.69 +40:32:28.6
00:37:26.65 +40:43:42.6
00:28:26.20 +40:17:41.5
00:39:04.93 +40:40:09.7
00:33:36.61 +40:11:00.8
00:30:24.38 +40:15:09.8
00:29:15.36 +40:43:20.6
00:31:03.86 +40:30:26.8
00:36:44.02 +40:12:32.8
00:35:57.94 +40:51:49.5
00:35:53.29 +41:33:57.4
00:36:24.34 +41:00:21.7
00:34:21.87 +40:27:53.0
00:27:36.10 +40:26:32.2
00:36:56.44 +41:38:25.9
00:28:29.02 +40:30:50.7
00:36:25.24 +40:19:01.1
00:35:39.62 +41:27:36.6
00:30:22.21 +41:11:13.4
00:39:02.99 +40:49:20.9
00:39:39.14 +41:39:57.4
00:38:21.51 +41:28:33.1
00:32:59.19 +40:29:18.5
00:34:52.99 +40:29:18.5
00:38:46.25 +41:34:25.5
00:31:28.64 +41:09:57.6
00:36:01.85 +41:13:44.6
00:37:04.98 +40:18:30.5
00:32:33.95 +41:05:05.1
00:34:33.17 +40:47:54.9
00:38:25.76 +40:20:32.0
00:35:23.18 +40:35:24.9
00:30:45.10 +40:55:22.8
00:38:35.34 +41:34:08.9
00:35:10.64 +40:34:31.4
00:29:21.77 +40:27:26.5
00:36:40.90 +41:02:44.6
00:39:58.57 +42:06:47.9
00:32:23.87 +40:19:52.2
00:36:42.88 +40:37:53.6
00:38:45.67 +41:53:46.7
00:38:53.08 +41:56:59.9
00:37:56.08 +41:34:06.7
00:37:45.05 +41:03:08.6
00:36:19.84 +41:38:25.3
00:38:59.37 +40:35:00.3
00:39:41.08 +41:25:56.3
00:37:09.91 +41:06:08.1
00:31:21.60 +41:08:32.7
00:36:02.01 +41:23:30.2
00:38:38.24 +40:22:07.9
00:38:45.13 +40:25:12.1
00:30:05.50 +40:27:53.9
00:37:47.82 +40:07:07.1
00:37:27.34 +40:54:19.5
00:38:11.97 +41:51:02.5
00:38:35.93 +41:49:11.0
00:36:06.52 +41:37:22.2
00:37:57.21 +40:14:31.6
00:32:56.52 +40:52:13.7
00:30:24.48 +40:58:01.2
00:38:39.18 +40:31:22.4
00:38:51.78 +41:04:56.8
00:38:23.23 +40:11:46.2
00:36:37.75 +41:42:12.7
00:37:14.10 +40:14:16.9
00:39:08.06 +41:50:06.3
00:37:26.39 +41:27:20.9
00:37:52.72 +41:48:01.2
00:40:07.47 +42:00:15.2
00:38:38.27 +41:14:26.7
00:29:43.79 +40:45:56.2
00:37:48.16 +41:51:57.8
00:29:46.73 +40:50:25.8
00:38:18.18 +40:26:01.9
00:36:13.41 +40:38:51.3
00:34:43.22 +41:16:42.3
00:38:21.02 +41:24:20.3
00:38:41.24 +40:18:11.1
00:36:58.93 +41:48:38.8
00:37:33.31 +39:59:24.2
00:39:25.21 +41:39:00.2
00:39:35.33 +42:17:44.9
00:34:10.35 +41:06:42.6
00:38:06.81 +41:58:31.2
00:38:27.86 +41:10:22.4
00:39:09.71 +41:35:23.2
00:39:29.33 +41:17:53.5
00:39:59.03 +41:43:27.9
00:35:47.39 +41:15:19.2
00:38:24.06 +42:04:27.5
00:39:38.51 +42:11:43.6
00:36:13.25 +41:16:53.3
23:52:36.23 +48:55:11.3
00:38:26.33 +41:24:02.5
00:37:15.27 +41:50:08.1
00:37:13.69 +41:35:27.4
00:38:37.61 +42:02:23.1
00:31:03.20 +41:06:59.0
00:31:28.00 +40:51:06.0
00:37:21.32 +41:24:04.2
00:31:49.73 +40:55:14.4
00:32:21.36 +40:51:32.5
00:35:09.56 +41:07:44.4
00:32:53.19 +41:07:42.3
00:37:27.42 +41:48:40.1
00:32:09.50 +40:51:47.6
00:30:11.90 +40:55:28.9
00:28:30.92 +47:40:39.5
00:38:11.26 +41:34:17.7
00:37:41.72 +41:32:04.8
23:51:19.09 +47:26:34.3
00:38:58.96 +41:45:22.2
00:35:28.01 +41:37:26.2
00:34:50.92 +41:30:57.5
00:36:40.43 +41:38:49.9
00:39:09.51 +41:19:48.8
00:29:51.46 +40:52:33.7
00:35:06.20 +41:34:07.1
00:39:51.74 +41:33:16.7
00:38:49.36 +41:40:17.7
00:38:19.87 +41:45:43.9
00:36:14.68 +41:44:21.0
00:32:47.58 +41:33:09.8
00:37:41.17 +41:41:48.4
00:37:51.33 +41:18:32.6
00:36:36.65 +41:16:53.0
00:17:36.49 +49:39:31.4
00:37:43.33 +47:31:11.8
00:32:17.22 +40:54:47.7
00:30:12.13 +40:54:59.2
00:38:48.33 +41:31:12.4
00:31:26.60 +41:14:46.2
00:16:51.12 +49:25:24.7
00:39:23.78 +42:08:03.5
23:44:20.66 +47:15:24.6
00:39:38.06 +41:39:01.8
00:37:41.62 +47:31:10.2
00:32:31.12 +40:54:18.1
00:17:36.28 +45:43:37.6
00:01:53.12 +47:52:08.7
00:39:13.03 +41:46:44.4
00:37:10.96 +41:25:33.1
23:51:17.02 +47:27:28.9
00:21:49.90 +44:52:11.5
########### Completed And-01-Q1b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ1.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
00:37:31.07 +40:20:00.4
00:33:33.95 +40:06:46.8
00:37:54.93 +40:52:25.0
00:38:30.47 +40:59:13.9
00:38:43.85 +40:26:13.8
00:30:29.65 +40:22:54.0
00:35:38.53 +40:27:16.9
00:39:20.23 +41:55:22.1
00:37:34.09 +41:05:42.6
00:35:55.08 +40:24:03.1
00:30:46.30 +40:32:34.3
00:37:27.23 +40:43:47.6
00:28:26.85 +40:17:47.8
00:36:44.67 +41:24:43.6
00:38:08.54 +41:23:31.1
23:16:50.72 +50:36:39.4
00:38:35.01 +41:49:10.8
00:39:43.63 +46:33:18.7
23:48:49.51 +48:06:36.5
00:31:04.90 +49:25:26.3
00:29:41.54 +49:37:53.1
00:26:11.09 +49:43:03.1
00:32:10.03 +41:48:33.6
00:34:54.42 +43:04:37.2
00:37:29.93 +40:20:00.8
00:33:32.90 +40:06:45.2
00:37:54.13 +40:52:23.1
00:38:29.77 +40:59:11.4
00:38:43.10 +40:26:10.2
00:30:28.89 +40:22:49.5
00:35:37.81 +40:27:12.6
00:27:17.27 +40:22:49.7
00:35:54.41 +40:23:58.2
00:37:33.52 +41:05:38.3
00:30:45.69 +40:32:28.6
00:37:26.65 +40:43:42.6
00:28:26.20 +40:17:41.5
00:39:04.93 +40:40:09.7
00:33:36.61 +40:11:00.8
00:30:24.38 +40:15:09.8
00:29:15.36 +40:43:20.6
00:31:03.86 +40:30:26.8
00:36:44.02 +40:12:32.8
00:35:57.94 +40:51:49.5
00:35:53.29 +41:33:57.4
00:36:24.34 +41:00:21.7
00:34:21.87 +40:27:53.0
00:27:36.10 +40:26:32.2
00:36:56.44 +41:38:25.9
00:28:29.02 +40:30:50.7
00:36:25.24 +40:19:01.1
00:35:39.62 +41:27:36.6
00:30:22.21 +41:11:13.4
00:39:02.99 +40:49:20.9
00:39:39.14 +41:39:57.4
00:38:21.51 +41:28:33.1
00:32:59.19 +40:29:18.5
00:34:52.99 +40:29:18.5
00:38:46.25 +41:34:25.5
00:31:28.64 +41:09:57.6
00:36:01.85 +41:13:44.6
00:37:04.98 +40:18:30.5
00:32:33.95 +41:05:05.1
00:34:33.17 +40:47:54.9
00:38:25.76 +40:20:32.0
00:35:23.18 +40:35:24.9
00:30:45.10 +40:55:22.8
00:38:35.34 +41:34:08.9
00:35:10.64 +40:34:31.4
00:29:21.77 +40:27:26.5
00:36:40.90 +41:02:44.6
00:39:58.57 +42:06:47.9
00:32:23.87 +40:19:52.2
00:36:42.88 +40:37:53.6
00:38:45.67 +41:53:46.7
00:38:53.08 +41:56:59.9
00:37:56.08 +41:34:06.7
00:37:45.05 +41:03:08.6
00:36:19.84 +41:38:25.3
00:38:59.37 +40:35:00.3
00:39:41.08 +41:25:56.3
00:37:09.91 +41:06:08.1
00:31:21.60 +41:08:32.7
00:36:02.01 +41:23:30.2
00:38:38.24 +40:22:07.9
00:38:45.13 +40:25:12.1
00:30:05.50 +40:27:53.9
00:37:47.82 +40:07:07.1
00:37:27.34 +40:54:19.5
00:38:11.97 +41:51:02.5
00:38:35.93 +41:49:11.0
00:36:06.52 +41:37:22.2
00:37:57.21 +40:14:31.6
00:32:56.52 +40:52:13.7
00:30:24.48 +40:58:01.2
00:38:39.18 +40:31:22.4
00:38:51.78 +41:04:56.8
00:38:23.23 +40:11:46.2
00:36:37.75 +41:42:12.7
00:37:14.10 +40:14:16.9
00:39:08.06 +41:50:06.3
00:37:26.39 +41:27:20.9
00:37:52.72 +41:48:01.2
00:40:07.47 +42:00:15.2
00:38:38.27 +41:14:26.7
00:29:43.79 +40:45:56.2
00:37:48.16 +41:51:57.8
00:29:46.73 +40:50:25.8
00:38:18.18 +40:26:01.9
00:36:13.41 +40:38:51.3
00:34:43.22 +41:16:42.3
00:38:21.02 +41:24:20.3
00:38:41.24 +40:18:11.1
00:36:58.93 +41:48:38.8
00:37:33.31 +39:59:24.2
00:39:25.21 +41:39:00.2
00:39:35.33 +42:17:44.9
00:34:10.35 +41:06:42.6
00:38:06.81 +41:58:31.2
00:38:27.86 +41:10:22.4
00:39:09.71 +41:35:23.2
00:39:29.33 +41:17:53.5
00:39:59.03 +41:43:27.9
00:35:47.39 +41:15:19.2
00:38:24.06 +42:04:27.5
00:39:38.51 +42:11:43.6
00:36:13.25 +41:16:53.3
23:52:36.23 +48:55:11.3
00:38:26.33 +41:24:02.5
00:37:15.27 +41:50:08.1
00:37:13.69 +41:35:27.4
00:38:37.61 +42:02:23.1
00:31:03.20 +41:06:59.0
00:31:28.00 +40:51:06.0
00:37:21.32 +41:24:04.2
00:31:49.73 +40:55:14.4
00:32:21.36 +40:51:32.5
00:35:09.56 +41:07:44.4
00:32:53.19 +41:07:42.3
00:37:27.42 +41:48:40.1
00:32:09.50 +40:51:47.6
00:30:11.90 +40:55:28.9
00:28:30.92 +47:40:39.5
00:38:11.26 +41:34:17.7
00:37:41.72 +41:32:04.8
23:51:19.09 +47:26:34.3
00:38:58.96 +41:45:22.2
00:35:28.01 +41:37:26.2
00:34:50.92 +41:30:57.5
00:36:40.43 +41:38:49.9
00:39:09.51 +41:19:48.8
00:29:51.46 +40:52:33.7
00:35:06.20 +41:34:07.1
00:39:51.74 +41:33:16.7
00:38:49.36 +41:40:17.7
00:38:19.87 +41:45:43.9
00:36:14.68 +41:44:21.0
00:32:47.58 +41:33:09.8
00:37:41.17 +41:41:48.4
00:37:51.33 +41:18:32.6
00:36:36.65 +41:16:53.0
00:17:36.49 +49:39:31.4
00:37:43.33 +47:31:11.8
00:32:17.22 +40:54:47.7
00:30:12.13 +40:54:59.2
00:38:48.33 +41:31:12.4
00:31:26.60 +41:14:46.2
00:16:51.12 +49:25:24.7
00:39:23.78 +42:08:03.5
23:44:20.66 +47:15:24.6
00:39:38.06 +41:39:01.8
00:37:41.62 +47:31:10.2
00:32:31.12 +40:54:18.1
00:17:36.28 +45:43:37.6
00:01:53.12 +47:52:08.7
00:39:13.03 +41:46:44.4
00:37:10.96 +41:25:33.1
00:21:49.90 +44:52:11.5
23:51:17.02 +47:27:28.9
00:38:17.66 +41:33:56.2
###################################################################################
00:37:31.07 +40:20:00.4 -- not an asteroid (will add it to exclusion list)
00:33:33.95 +40:06:46.8 -- not an asteroid (will add it to exclusion list)
00:37:54.93 +40:52:25.0 -- not an asteroid (will add it to exclusion list)
00:38:30.47 +40:59:13.9 -- not an asteroid (will add it to exclusion list)
00:38:43.85 +40:26:13.8 -- not an asteroid (will add it to exclusion list)
00:30:29.65 +40:22:54.0 -- not an asteroid (will add it to exclusion list)
00:35:38.53 +40:27:16.9 -- not an asteroid (will add it to exclusion list)
00:39:20.23 +41:55:22.1 -- not an asteroid (will add it to exclusion list)
00:37:34.09 +41:05:42.6 -- not an asteroid (will add it to exclusion list)
00:35:55.08 +40:24:03.1 -- not an asteroid (will add it to exclusion list)
00:30:46.30 +40:32:34.3 -- not an asteroid (will add it to exclusion list)
00:37:27.23 +40:43:47.6 -- not an asteroid (will add it to exclusion list)
00:28:26.85 +40:17:47.8 -- not an asteroid (will add it to exclusion list)
00:36:44.67 +41:24:43.6 -- not an asteroid (will add it to exclusion list)
00:38:08.54 +41:23:31.1 -- not an asteroid (will add it to exclusion list)
23:16:50.72 +50:36:39.4 -- not an asteroid (will add it to exclusion list)
00:38:35.01 +41:49:10.8 -- not an asteroid (will add it to exclusion list)
00:39:43.63 +46:33:18.7 -- not an asteroid (will add it to exclusion list)
23:48:49.51 +48:06:36.5 -- not an asteroid (will add it to exclusion list)
00:31:04.90 +49:25:26.3 -- not an asteroid (will add it to exclusion list)
00:29:41.54 +49:37:53.1 -- not an asteroid (will add it to exclusion list)
00:26:11.09 +49:43:03.1 -- not an asteroid (will add it to exclusion list)
00:32:10.03 +41:48:33.6 -- not an asteroid (will add it to exclusion list)
00:34:54.42 +43:04:37.2 -- not an asteroid (will add it to exclusion list)
00:37:29.93 +40:20:00.8 -- not an asteroid (will add it to exclusion list)
00:33:32.90 +40:06:45.2 -- not an asteroid (will add it to exclusion list)
00:37:54.13 +40:52:23.1 -- not an asteroid (will add it to exclusion list)
00:38:29.77 +40:59:11.4 -- not an asteroid (will add it to exclusion list)
00:38:43.10 +40:26:10.2 -- not an asteroid (will add it to exclusion list)
00:30:28.89 +40:22:49.5 -- not an asteroid (will add it to exclusion list)
00:35:37.81 +40:27:12.6 -- not an asteroid (will add it to exclusion list)
00:27:17.27 +40:22:49.7 -- not an asteroid (will add it to exclusion list)
00:35:54.41 +40:23:58.2 -- not an asteroid (will add it to exclusion list)
00:37:33.52 +41:05:38.3 -- not an asteroid (will add it to exclusion list)
00:30:45.69 +40:32:28.6 -- not an asteroid (will add it to exclusion list)
00:37:26.65 +40:43:42.6 -- not an asteroid (will add it to exclusion list)
00:28:26.20 +40:17:41.5 -- not an asteroid (will add it to exclusion list)
00:39:04.93 +40:40:09.7 -- not an asteroid (will add it to exclusion list)
00:33:36.61 +40:11:00.8 -- not an asteroid (will add it to exclusion list)
00:30:24.38 +40:15:09.8 -- not an asteroid (will add it to exclusion list)
00:29:15.36 +40:43:20.6 -- not an asteroid (will add it to exclusion list)
00:31:03.86 +40:30:26.8 -- not an asteroid (will add it to exclusion list)
00:36:44.02 +40:12:32.8 -- not an asteroid (will add it to exclusion list)
00:35:57.94 +40:51:49.5 -- not an asteroid (will add it to exclusion list)
00:35:53.29 +41:33:57.4 -- not an asteroid (will add it to exclusion list)
00:36:24.34 +41:00:21.7 -- not an asteroid (will add it to exclusion list)
00:34:21.87 +40:27:53.0 -- not an asteroid (will add it to exclusion list)
00:27:36.10 +40:26:32.2 -- not an asteroid (will add it to exclusion list)
00:36:56.44 +41:38:25.9 -- not an asteroid (will add it to exclusion list)
00:28:29.02 +40:30:50.7 -- not an asteroid (will add it to exclusion list)
00:36:25.24 +40:19:01.1 -- not an asteroid (will add it to exclusion list)
00:35:39.62 +41:27:36.6 -- not an asteroid (will add it to exclusion list)
00:30:22.21 +41:11:13.4 -- not an asteroid (will add it to exclusion list)
00:39:02.99 +40:49:20.9 -- not an asteroid (will add it to exclusion list)
00:39:39.14 +41:39:57.4 -- not an asteroid (will add it to exclusion list)
00:38:21.51 +41:28:33.1 -- not an asteroid (will add it to exclusion list)
00:32:59.19 +40:29:18.5 -- not an asteroid (will add it to exclusion list)
00:34:52.99 +40:29:18.5 -- not an asteroid (will add it to exclusion list)
00:38:46.25 +41:34:25.5 -- not an asteroid (will add it to exclusion list)
00:31:28.64 +41:09:57.6 -- not an asteroid (will add it to exclusion list)
00:36:01.85 +41:13:44.6 -- not an asteroid (will add it to exclusion list)
00:37:04.98 +40:18:30.5 -- not an asteroid (will add it to exclusion list)
00:32:33.95 +41:05:05.1 -- not an asteroid (will add it to exclusion list)
00:34:33.17 +40:47:54.9 -- not an asteroid (will add it to exclusion list)
00:38:25.76 +40:20:32.0 -- not an asteroid (will add it to exclusion list)
00:35:23.18 +40:35:24.9 -- not an asteroid (will add it to exclusion list)
00:30:45.10 +40:55:22.8 -- not an asteroid (will add it to exclusion list)
00:38:35.34 +41:34:08.9 -- not an asteroid (will add it to exclusion list)
00:35:10.64 +40:34:31.4 -- not an asteroid (will add it to exclusion list)
00:29:21.77 +40:27:26.5 -- not an asteroid (will add it to exclusion list)
00:36:40.90 +41:02:44.6 -- not an asteroid (will add it to exclusion list)
00:39:58.57 +42:06:47.9 -- not an asteroid (will add it to exclusion list)
00:32:23.87 +40:19:52.2 -- not an asteroid (will add it to exclusion list)
00:36:42.88 +40:37:53.6 -- not an asteroid (will add it to exclusion list)
00:38:45.67 +41:53:46.7 -- not an asteroid (will add it to exclusion list)
00:38:53.08 +41:56:59.9 -- not an asteroid (will add it to exclusion list)
00:37:56.08 +41:34:06.7 -- not an asteroid (will add it to exclusion list)
00:37:45.05 +41:03:08.6 -- not an asteroid (will add it to exclusion list)
00:36:19.84 +41:38:25.3 -- not an asteroid (will add it to exclusion list)
00:38:59.37 +40:35:00.3 -- not an asteroid (will add it to exclusion list)
00:39:41.08 +41:25:56.3 -- not an asteroid (will add it to exclusion list)
00:37:09.91 +41:06:08.1 -- not an asteroid (will add it to exclusion list)
00:31:21.60 +41:08:32.7 -- not an asteroid (will add it to exclusion list)
00:36:02.01 +41:23:30.2 -- not an asteroid (will add it to exclusion list)
00:38:38.24 +40:22:07.9 -- not an asteroid (will add it to exclusion list)
00:38:45.13 +40:25:12.1 -- not an asteroid (will add it to exclusion list)
00:30:05.50 +40:27:53.9 -- not an asteroid (will add it to exclusion list)
00:37:47.82 +40:07:07.1 -- not an asteroid (will add it to exclusion list)
00:37:27.34 +40:54:19.5 -- not an asteroid (will add it to exclusion list)
00:38:11.97 +41:51:02.5 -- not an asteroid (will add it to exclusion list)
00:38:35.93 +41:49:11.0 -- not an asteroid (will add it to exclusion list)
00:36:06.52 +41:37:22.2 -- not an asteroid (will add it to exclusion list)
00:37:57.21 +40:14:31.6 -- not an asteroid (will add it to exclusion list)
00:32:56.52 +40:52:13.7 -- not an asteroid (will add it to exclusion list)
00:30:24.48 +40:58:01.2 -- not an asteroid (will add it to exclusion list)
00:38:39.18 +40:31:22.4 -- not an asteroid (will add it to exclusion list)
00:38:51.78 +41:04:56.8 -- not an asteroid (will add it to exclusion list)
00:38:23.23 +40:11:46.2 -- not an asteroid (will add it to exclusion list)
00:36:37.75 +41:42:12.7 -- not an asteroid (will add it to exclusion list)
00:37:14.10 +40:14:16.9 -- not an asteroid (will add it to exclusion list)
00:39:08.06 +41:50:06.3 -- not an asteroid (will add it to exclusion list)
00:37:26.39 +41:27:20.9 -- not an asteroid (will add it to exclusion list)
00:37:52.72 +41:48:01.2 -- not an asteroid (will add it to exclusion list)
00:40:07.47 +42:00:15.2 -- not an asteroid (will add it to exclusion list)
00:38:38.27 +41:14:26.7 -- not an asteroid (will add it to exclusion list)
00:29:43.79 +40:45:56.2 -- not an asteroid (will add it to exclusion list)
00:37:48.16 +41:51:57.8 -- not an asteroid (will add it to exclusion list)
00:29:46.73 +40:50:25.8 -- not an asteroid (will add it to exclusion list)
00:38:18.18 +40:26:01.9 -- not an asteroid (will add it to exclusion list)
00:36:13.41 +40:38:51.3 -- not an asteroid (will add it to exclusion list)
00:34:43.22 +41:16:42.3 -- not an asteroid (will add it to exclusion list)
00:38:21.02 +41:24:20.3 -- not an asteroid (will add it to exclusion list)
00:38:41.24 +40:18:11.1 -- not an asteroid (will add it to exclusion list)
00:36:58.93 +41:48:38.8 -- not an asteroid (will add it to exclusion list)
00:37:33.31 +39:59:24.2 -- not an asteroid (will add it to exclusion list)
00:39:25.21 +41:39:00.2 -- not an asteroid (will add it to exclusion list)
00:39:35.33 +42:17:44.9 -- not an asteroid (will add it to exclusion list)
00:34:10.35 +41:06:42.6 -- not an asteroid (will add it to exclusion list)
00:38:06.81 +41:58:31.2 -- not an asteroid (will add it to exclusion list)
00:38:27.86 +41:10:22.4 -- not an asteroid (will add it to exclusion list)
00:39:09.71 +41:35:23.2 -- not an asteroid (will add it to exclusion list)
00:39:29.33 +41:17:53.5 -- not an asteroid (will add it to exclusion list)
00:39:59.03 +41:43:27.9 -- not an asteroid (will add it to exclusion list)
00:35:47.39 +41:15:19.2 -- not an asteroid (will add it to exclusion list)
00:38:24.06 +42:04:27.5 -- not an asteroid (will add it to exclusion list)
00:39:38.51 +42:11:43.6 -- not an asteroid (will add it to exclusion list)
00:36:13.25 +41:16:53.3 -- not an asteroid (will add it to exclusion list)
23:52:36.23 +48:55:11.3 -- not an asteroid (will add it to exclusion list)
00:38:26.33 +41:24:02.5 -- not an asteroid (will add it to exclusion list)
00:37:15.27 +41:50:08.1 -- not an asteroid (will add it to exclusion list)
00:37:13.69 +41:35:27.4 -- not an asteroid (will add it to exclusion list)
00:38:37.61 +42:02:23.1 -- not an asteroid (will add it to exclusion list)
00:31:03.20 +41:06:59.0 -- not an asteroid (will add it to exclusion list)
00:31:28.00 +40:51:06.0 -- not an asteroid (will add it to exclusion list)
00:37:21.32 +41:24:04.2 -- not an asteroid (will add it to exclusion list)
00:31:49.73 +40:55:14.4 -- not an asteroid (will add it to exclusion list)
00:32:21.36 +40:51:32.5 -- not an asteroid (will add it to exclusion list)
00:35:09.56 +41:07:44.4 -- not an asteroid (will add it to exclusion list)
00:32:53.19 +41:07:42.3 -- not an asteroid (will add it to exclusion list)
00:37:27.42 +41:48:40.1 -- not an asteroid (will add it to exclusion list)
00:32:09.50 +40:51:47.6 -- not an asteroid (will add it to exclusion list)
00:30:11.90 +40:55:28.9 -- not an asteroid (will add it to exclusion list)
00:28:30.92 +47:40:39.5 -- not an asteroid (will add it to exclusion list)
00:38:11.26 +41:34:17.7 -- not an asteroid (will add it to exclusion list)
00:37:41.72 +41:32:04.8 -- not an asteroid (will add it to exclusion list)
23:51:19.09 +47:26:34.3 -- not an asteroid (will add it to exclusion list)
00:38:58.96 +41:45:22.2 -- not an asteroid (will add it to exclusion list)
00:35:28.01 +41:37:26.2 -- not an asteroid (will add it to exclusion list)
00:34:50.92 +41:30:57.5 -- not an asteroid (will add it to exclusion list)
00:36:40.43 +41:38:49.9 -- not an asteroid (will add it to exclusion list)
00:39:09.51 +41:19:48.8 -- not an asteroid (will add it to exclusion list)
00:29:51.46 +40:52:33.7 -- not an asteroid (will add it to exclusion list)
00:35:06.20 +41:34:07.1 -- not an asteroid (will add it to exclusion list)
00:39:51.74 +41:33:16.7 -- not an asteroid (will add it to exclusion list)
00:38:49.36 +41:40:17.7 -- not an asteroid (will add it to exclusion list)
00:38:19.87 +41:45:43.9 -- not an asteroid (will add it to exclusion list)
00:36:14.68 +41:44:21.0 -- not an asteroid (will add it to exclusion list)
00:32:47.58 +41:33:09.8 -- not an asteroid (will add it to exclusion list)
00:37:41.17 +41:41:48.4 -- not an asteroid (will add it to exclusion list)
00:37:51.33 +41:18:32.6 -- not an asteroid (will add it to exclusion list)
00:36:36.65 +41:16:53.0 -- not an asteroid (will add it to exclusion list)
00:17:36.49 +49:39:31.4 -- not an asteroid (will add it to exclusion list)
00:37:43.33 +47:31:11.8 -- not an asteroid (will add it to exclusion list)
00:32:17.22 +40:54:47.7 -- not an asteroid (will add it to exclusion list)
00:30:12.13 +40:54:59.2 -- not an asteroid (will add it to exclusion list)
00:38:48.33 +41:31:12.4 -- not an asteroid (will add it to exclusion list)
00:31:26.60 +41:14:46.2 -- not an asteroid (will add it to exclusion list)
00:16:51.12 +49:25:24.7 -- not an asteroid (will add it to exclusion list)
00:39:23.78 +42:08:03.5 -- not an asteroid (will add it to exclusion list)
23:44:20.66 +47:15:24.6 -- not an asteroid (will add it to exclusion list)
00:39:38.06 +41:39:01.8 -- not an asteroid (will add it to exclusion list)
00:37:41.62 +47:31:10.2 -- not an asteroid (will add it to exclusion list)
00:32:31.12 +40:54:18.1 -- not an asteroid (will add it to exclusion list)
00:17:36.28 +45:43:37.6 -- not an asteroid (will add it to exclusion list)
00:01:53.12 +47:52:08.7 -- not an asteroid (will add it to exclusion list)
00:39:13.03 +41:46:44.4 -- not an asteroid (will add it to exclusion list)
00:37:10.96 +41:25:33.1 -- not an asteroid (will add it to exclusion list)
00:21:49.90 +44:52:11.5 -- not an asteroid (will add it to exclusion list)
23:51:17.02 +47:27:28.9 -- not an asteroid (will add it to exclusion list)
00:38:17.66 +41:33:56.2 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:01:53.12 +47:52:08.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:51.12 +49:25:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:36.28 +45:43:37.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:36.49 +49:39:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:49.90 +44:52:11.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:11.09 +49:43:03.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:17.27 +40:22:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:36.10 +40:26:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:26.20 +40:17:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:26.85 +40:17:47.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:29.02 +40:30:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:30.92 +47:40:39.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:15.36 +40:43:20.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:21.77 +40:27:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:41.54 +49:37:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:43.79 +40:45:56.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:46.73 +40:50:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:51.46 +40:52:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:05.50 +40:27:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:11.90 +40:55:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:12.13 +40:54:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:22.21 +41:11:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:24.38 +40:15:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:24.48 +40:58:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:28.89 +40:22:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:29.65 +40:22:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:45.10 +40:55:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:45.69 +40:32:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:46.30 +40:32:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:03.20 +41:06:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:03.86 +40:30:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:04.90 +49:25:26.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:21.60 +41:08:32.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:26.60 +41:14:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:28.00 +40:51:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:28.64 +41:09:57.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:49.73 +40:55:14.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:09.50 +40:51:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:10.03 +41:48:33.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:17.22 +40:54:47.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:21.36 +40:51:32.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:23.87 +40:19:52.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:31.12 +40:54:18.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:33.95 +41:05:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:47.58 +41:33:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:53.19 +41:07:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:56.52 +40:52:13.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:59.19 +40:29:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:32.90 +40:06:45.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:33.95 +40:06:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:36.61 +40:11:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:10.35 +41:06:42.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:21.87 +40:27:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:33.17 +40:47:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:43.22 +41:16:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:50.92 +41:30:57.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:52.99 +40:29:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:54.42 +43:04:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:06.20 +41:34:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:09.56 +41:07:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:10.64 +40:34:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:23.18 +40:35:24.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:28.01 +41:37:26.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:37.81 +40:27:12.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:38.53 +40:27:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:39.62 +41:27:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:47.39 +41:15:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:53.29 +41:33:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:54.41 +40:23:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:55.08 +40:24:03.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:57.94 +40:51:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:01.85 +41:13:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:02.01 +41:23:30.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:06.52 +41:37:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:13.25 +41:16:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:13.41 +40:38:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:14.68 +41:44:21.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:19.84 +41:38:25.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:24.34 +41:00:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:25.24 +40:19:01.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:36.65 +41:16:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:37.75 +41:42:12.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:40.43 +41:38:49.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:40.90 +41:02:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:42.88 +40:37:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:44.02 +40:12:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:44.67 +41:24:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:56.44 +41:38:25.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:58.93 +41:48:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:04.98 +40:18:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:09.91 +41:06:08.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:10.96 +41:25:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:13.69 +41:35:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:14.10 +40:14:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:15.27 +41:50:08.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:21.32 +41:24:04.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:26.39 +41:27:20.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:26.65 +40:43:42.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:27.23 +40:43:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:27.34 +40:54:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:27.42 +41:48:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:29.93 +40:20:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:31.07 +40:20:00.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:33.31 +39:59:24.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:33.52 +41:05:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:34.09 +41:05:42.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:41.17 +41:41:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:41.62 +47:31:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:41.72 +41:32:04.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:43.33 +47:31:11.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:45.05 +41:03:08.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:47.82 +40:07:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:48.16 +41:51:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:51.33 +41:18:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:52.72 +41:48:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:54.13 +40:52:23.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:54.93 +40:52:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:56.08 +41:34:06.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:37:57.21 +40:14:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:06.81 +41:58:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:08.54 +41:23:31.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:11.26 +41:34:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:11.97 +41:51:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:17.66 +41:33:56.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:18.18 +40:26:01.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:19.87 +41:45:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:21.02 +41:24:20.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:21.51 +41:28:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:23.23 +40:11:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:24.06 +42:04:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:25.76 +40:20:32.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:26.33 +41:24:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:27.86 +41:10:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:29.77 +40:59:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:30.47 +40:59:13.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:35.01 +41:49:10.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:35.34 +41:34:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:35.93 +41:49:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:37.61 +42:02:23.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:38.24 +40:22:07.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:38.27 +41:14:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:39.18 +40:31:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:41.24 +40:18:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:43.10 +40:26:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:43.85 +40:26:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:45.13 +40:25:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:45.67 +41:53:46.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:46.25 +41:34:25.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:48.33 +41:31:12.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:49.36 +41:40:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:51.78 +41:04:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:53.08 +41:56:59.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:58.96 +41:45:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:38:59.37 +40:35:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:02.99 +40:49:20.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:04.93 +40:40:09.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:08.06 +41:50:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:09.51 +41:19:48.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:09.71 +41:35:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:13.03 +41:46:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:20.23 +41:55:22.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:23.78 +42:08:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:25.21 +41:39:00.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:29.33 +41:17:53.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:35.33 +42:17:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:38.06 +41:39:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:38.51 +42:11:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:39.14 +41:39:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:41.08 +41:25:56.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:43.63 +46:33:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:51.74 +41:33:16.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:58.57 +42:06:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:39:59.03 +41:43:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:40:07.47 +42:00:15.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:50.72 +50:36:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:20.66 +47:15:24.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:49.51 +48:06:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:17.02 +47:27:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:19.09 +47:26:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:36.23 +48:55:11.3 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:01:53.12 +47:52:08.7 -- not a known variable star
00:16:51.12 +49:25:24.7 -- not a known variable star
00:17:36.28 +45:43:37.6 -- not a known variable star
00:17:36.49 +49:39:31.4 -- not a known variable star
00:21:49.90 +44:52:11.5 -- a known variable star
00:26:11.09 +49:43:03.1 -- not a known variable star
00:27:17.27 +40:22:49.7 -- not a known variable star
00:27:36.10 +40:26:32.2 -- not a known variable star
00:28:26.20 +40:17:41.5 -- not a known variable star
00:28:26.85 +40:17:47.8 -- not a known variable star
00:28:29.02 +40:30:50.7 -- not a known variable star
00:28:30.92 +47:40:39.5 -- not a known variable star
00:29:15.36 +40:43:20.6 -- not a known variable star
00:29:21.77 +40:27:26.5 -- not a known variable star
00:29:41.54 +49:37:53.1 -- not a known variable star
00:29:43.79 +40:45:56.2 -- not a known variable star
00:29:46.73 +40:50:25.8 -- not a known variable star
00:29:51.46 +40:52:33.7 -- not a known variable star
00:30:05.50 +40:27:53.9 -- not a known variable star
00:30:11.90 +40:55:28.9 -- not a known variable star
00:30:12.13 +40:54:59.2 -- not a known variable star
00:30:22.21 +41:11:13.4 -- not a known variable star
00:30:24.38 +40:15:09.8 -- not a known variable star
00:30:24.48 +40:58:01.2 -- not a known variable star
00:30:28.89 +40:22:49.5 -- not a known variable star
00:30:29.65 +40:22:54.0 -- not a known variable star
00:30:45.10 +40:55:22.8 -- not a known variable star
00:30:45.69 +40:32:28.6 -- not a known variable star
00:30:46.30 +40:32:34.3 -- not a known variable star
00:31:03.20 +41:06:59.0 -- not a known variable star
00:31:03.86 +40:30:26.8 -- not a known variable star
00:31:04.90 +49:25:26.3 -- not a known variable star
00:31:21.60 +41:08:32.7 -- not a known variable star
00:31:26.60 +41:14:46.2 -- not a known variable star
00:31:28.00 +40:51:06.0 -- not a known variable star
00:31:28.64 +41:09:57.6 -- not a known variable star
00:31:49.73 +40:55:14.4 -- not a known variable star
00:32:09.50 +40:51:47.6 -- not a known variable star
00:32:10.03 +41:48:33.6 -- not a known variable star
00:32:17.22 +40:54:47.7 -- not a known variable star
00:32:21.36 +40:51:32.5 -- not a known variable star
00:32:23.87 +40:19:52.2 -- not a known variable star
00:32:31.12 +40:54:18.1 -- not a known variable star
00:32:33.95 +41:05:05.1 -- not a known variable star
00:32:47.58 +41:33:09.8 -- not a known variable star
00:32:53.19 +41:07:42.3 -- not a known variable star
00:32:56.52 +40:52:13.7 -- not a known variable star
00:32:59.19 +40:29:18.5 -- not a known variable star
00:33:32.90 +40:06:45.2 -- not a known variable star
00:33:33.95 +40:06:46.8 -- not a known variable star
00:33:36.61 +40:11:00.8 -- not a known variable star
00:34:10.35 +41:06:42.6 -- a known variable star
00:34:21.87 +40:27:53.0 -- not a known variable star
00:34:33.17 +40:47:54.9 -- not a known variable star
00:34:43.22 +41:16:42.3 -- not a known variable star
00:34:50.92 +41:30:57.5 -- not a known variable star
00:34:52.99 +40:29:18.5 -- not a known variable star
00:34:54.42 +43:04:37.2 -- not a known variable star
00:35:06.20 +41:34:07.1 -- not a known variable star
00:35:09.56 +41:07:44.4 -- not a known variable star
00:35:10.64 +40:34:31.4 -- not a known variable star
00:35:23.18 +40:35:24.9 -- not a known variable star
00:35:28.01 +41:37:26.2 -- not a known variable star
00:35:37.81 +40:27:12.6 -- not a known variable star
00:35:38.53 +40:27:16.9 -- not a known variable star
00:35:39.62 +41:27:36.6 -- not a known variable star
00:35:47.39 +41:15:19.2 -- not a known variable star
00:35:53.29 +41:33:57.4 -- not a known variable star
00:35:54.41 +40:23:58.2 -- not a known variable star
00:35:55.08 +40:24:03.1 -- not a known variable star
00:35:57.94 +40:51:49.5 -- not a known variable star
00:36:01.85 +41:13:44.6 -- not a known variable star
00:36:02.01 +41:23:30.2 -- not a known variable star
00:36:06.52 +41:37:22.2 -- not a known variable star
00:36:13.25 +41:16:53.3 -- not a known variable star
00:36:13.41 +40:38:51.3 -- not a known variable star
00:36:14.68 +41:44:21.0 -- not a known variable star
00:36:19.84 +41:38:25.3 -- not a known variable star
00:36:24.34 +41:00:21.7 -- not a known variable star
00:36:25.24 +40:19:01.1 -- not a known variable star
00:36:36.65 +41:16:53.0 -- not a known variable star
00:36:37.75 +41:42:12.7 -- a known variable star
00:36:40.43 +41:38:49.9 -- not a known variable star
00:36:40.90 +41:02:44.6 -- not a known variable star
00:36:42.88 +40:37:53.6 -- not a known variable star
00:36:44.02 +40:12:32.8 -- not a known variable star
00:36:44.67 +41:24:43.6 -- not a known variable star
00:36:56.44 +41:38:25.9 -- not a known variable star
00:36:58.93 +41:48:38.8 -- not a known variable star
00:37:04.98 +40:18:30.5 -- not a known variable star
00:37:09.91 +41:06:08.1 -- not a known variable star
00:37:10.96 +41:25:33.1 -- not a known variable star
00:37:13.69 +41:35:27.4 -- not a known variable star
00:37:14.10 +40:14:16.9 -- not a known variable star
00:37:15.27 +41:50:08.1 -- not a known variable star
00:37:21.32 +41:24:04.2 -- not a known variable star
00:37:26.39 +41:27:20.9 -- a known variable star
00:37:26.65 +40:43:42.6 -- not a known variable star
00:37:27.23 +40:43:47.6 -- not a known variable star
00:37:27.34 +40:54:19.5 -- not a known variable star
00:37:27.42 +41:48:40.1 -- not a known variable star
00:37:29.93 +40:20:00.8 -- not a known variable star
00:37:31.07 +40:20:00.4 -- not a known variable star
00:37:33.31 +39:59:24.2 -- not a known variable star
00:37:33.52 +41:05:38.3 -- not a known variable star
00:37:34.09 +41:05:42.6 -- not a known variable star
00:37:41.17 +41:41:48.4 -- not a known variable star
00:37:41.62 +47:31:10.2 -- not a known variable star
00:37:41.72 +41:32:04.8 -- a known variable star
00:37:43.33 +47:31:11.8 -- not a known variable star
00:37:45.05 +41:03:08.6 -- not a known variable star
00:37:47.82 +40:07:07.1 -- not a known variable star
00:37:48.16 +41:51:57.8 -- not a known variable star
00:37:51.33 +41:18:32.6 -- not a known variable star
00:37:52.72 +41:48:01.2 -- not a known variable star
00:37:54.13 +40:52:23.1 -- not a known variable star
00:37:54.93 +40:52:25.0 -- not a known variable star
00:37:56.08 +41:34:06.7 -- not a known variable star
00:37:57.21 +40:14:31.6 -- not a known variable star
00:38:06.81 +41:58:31.2 -- not a known variable star
00:38:08.54 +41:23:31.1 -- not a known variable star
00:38:11.26 +41:34:17.7 -- not a known variable star
00:38:11.97 +41:51:02.5 -- not a known variable star
00:38:17.66 +41:33:56.2 -- not a known variable star
00:38:18.18 +40:26:01.9 -- not a known variable star
00:38:19.87 +41:45:43.9 -- not a known variable star
00:38:21.02 +41:24:20.3 -- not a known variable star
00:38:21.51 +41:28:33.1 -- not a known variable star
00:38:23.23 +40:11:46.2 -- not a known variable star
00:38:24.06 +42:04:27.5 -- not a known variable star
00:38:25.76 +40:20:32.0 -- not a known variable star
00:38:26.33 +41:24:02.5 -- not a known variable star
00:38:27.86 +41:10:22.4 -- not a known variable star
00:38:29.77 +40:59:11.4 -- not a known variable star
00:38:30.47 +40:59:13.9 -- not a known variable star
00:38:35.01 +41:49:10.8 -- not a known variable star
00:38:35.34 +41:34:08.9 -- not a known variable star
00:38:35.93 +41:49:11.0 -- not a known variable star
00:38:37.61 +42:02:23.1 -- not a known variable star
00:38:38.24 +40:22:07.9 -- not a known variable star
00:38:38.27 +41:14:26.7 -- not a known variable star
00:38:39.18 +40:31:22.4 -- not a known variable star
00:38:41.24 +40:18:11.1 -- not a known variable star
00:38:43.10 +40:26:10.2 -- not a known variable star
00:38:43.85 +40:26:13.8 -- not a known variable star
00:38:45.13 +40:25:12.1 -- not a known variable star
00:38:45.67 +41:53:46.7 -- not a known variable star
00:38:46.25 +41:34:25.5 -- not a known variable star
00:38:48.33 +41:31:12.4 -- not a known variable star
00:38:49.36 +41:40:17.7 -- not a known variable star
00:38:51.78 +41:04:56.8 -- not a known variable star
00:38:53.08 +41:56:59.9 -- not a known variable star
00:38:58.96 +41:45:22.2 -- not a known variable star
00:38:59.37 +40:35:00.3 -- not a known variable star
00:39:02.99 +40:49:20.9 -- not a known variable star
00:39:04.93 +40:40:09.7 -- not a known variable star
00:39:08.06 +41:50:06.3 -- not a known variable star
00:39:09.51 +41:19:48.8 -- not a known variable star
00:39:09.71 +41:35:23.2 -- not a known variable star
00:39:13.03 +41:46:44.4 -- not a known variable star
00:39:20.23 +41:55:22.1 -- not a known variable star
00:39:23.78 +42:08:03.5 -- a known variable star
00:39:25.21 +41:39:00.2 -- not a known variable star
00:39:29.33 +41:17:53.5 -- not a known variable star
00:39:35.33 +42:17:44.9 -- not a known variable star
00:39:38.06 +41:39:01.8 -- not a known variable star
00:39:38.51 +42:11:43.6 -- not a known variable star
00:39:39.14 +41:39:57.4 -- not a known variable star
00:39:41.08 +41:25:56.3 -- not a known variable star
00:39:43.63 +46:33:18.7 -- a known variable star
00:39:51.74 +41:33:16.7 -- not a known variable star
00:39:58.57 +42:06:47.9 -- not a known variable star
00:39:59.03 +41:43:27.9 -- not a known variable star
00:40:07.47 +42:00:15.2 -- not a known variable star
23:16:50.72 +50:36:39.4 -- not a known variable star
23:44:20.66 +47:15:24.6 -- not a known variable star
23:48:49.51 +48:06:36.5 -- not a known variable star
23:51:17.02 +47:27:28.9 -- not a known variable star
23:51:19.09 +47:26:34.3 -- not a known variable star
23:52:36.23 +48:55:11.3 -- not a known variable star
Found 173 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
180 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 180 (excluding asteroids and hot pixels, 173 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)2461146.95039501 -observatory V36
00:09:41.03 -01:48:33.2 Mercury (0.0mag)
03:10:51.41 +18:01:32.0 Venus (-3.9mag)
00:19:07.53 +01:00:19.9 Mars (1.2mag)
07:12:50.16 +22:45:52.8 Jupiter (-2.1mag)
00:29:22.98 +00:50:13.8 Saturn (0.9mag)
03:47:47.53 +19:47:46.6 Uranus (5.8mag)
00:10:53.98 -00:15:00.1 Neptune (7.8mag)
20:33:46.47 -22:52:37.2 Pluto (14.5mag)
00:42:29.20 +06:48:27.4 Moon (-8.4mag)
-rw-r--r-- 1 apache apache 361 Apr 16 05:53 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461146.95039501:
07:12:57.97 +22:45:37.2 Io (5.8mag)
07:13:01.00 +22:45:31.2 Europa (5.9mag)
07:13:03.43 +22:45:19.6 Ganymede (5.4mag)
07:13:25.35 +22:44:39.7 Callisto (6.6mag)
07:16:09.24 +22:33:17.9 Himalia (15.3mag)
07:12:52.48 +22:45:49.7 Thebe (16.2mag)
07:16:21.20 +23:03:31.3 Elara (17.3mag)
07:11:44.92 +23:25:39.0 Pasiphae (17.4mag)
07:21:09.29 +22:43:56.8 Carme (18.5mag)
00:29:22.15 +00:50:41.0 Titan (8.8mag)
00:29:23.41 +00:50:14.8 Rhea (10.1mag)
00:29:02.23 +00:50:18.9 Iapetus (11.5mag)
00:29:29.68 +00:50:35.6 Hyperion (14.8mag)
00:30:59.51 +00:58:59.1 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 16 05:53 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461146.95039501:
15:39:11.57 -16:36:29.4 JWST
15:31:50.43 +52:45:39.7 Chandra
09:08:42.85 -52:09:53.4 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 16 05:53 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461146.95039501 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:52:11.00 -28:48:21.3 13.9mag P/2010 H2 (Vales)
05:07:03.65 -69:38:25.7 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:32:32.69 +31:26:25.3 17.2mag C/2017 K2 (PANSTARRS)
17:30:23.35 +10:36:03.6 17.6mag C/2021 G2 (ATLAS)
23:10:20.66 +29:14:49.0 17.1mag C/2022 E2 (ATLAS)
04:29:45.81 +26:03:01.6 16.0mag C/2022 N2 (PANSTARRS)
09:03:31.07 +32:01:11.6 16.2mag C/2022 QE78 (ATLAS)
08:31:08.61 -00:06:20.2 17.3mag C/2022 R6 (PANSTARRS)
18:53:37.37 +18:34:12.9 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:40:31.56 -11:30:54.1 17.5mag P/2023 B1 (PANSTARRS)
09:07:25.73 -11:48:40.2 17.6mag C/2023 F3 (ATLAS)
21:54:40.00 +62:55:59.7 17.5mag C/2023 H5 (Lemmon)
19:18:48.31 -03:44:24.5 14.1mag C/2023 R1 (PANSTARRS)
21:31:36.53 +85:58:28.1 17.8mag C/2023 X2 (Lemmon)
06:18:06.80 +63:30:38.2 17.2mag C/2024 A1 (ATLAS)
05:14:14.52 +18:27:22.7 11.1mag C/2024 E1 (Wierzchos)
16:18:59.02 +06:27:51.3 17.4mag C/2024 G6 (ATLAS)
20:20:56.18 +15:23:49.6 14.6mag C/2024 J3 (ATLAS)
03:26:46.52 -22:19:01.5 16.3mag C/2024 T5 (ATLAS)
05:17:05.88 +45:10:45.4 17.7mag C/2025 J1 (Borisov)
13:36:57.26 +45:46:43.1 15.2mag C/2025 L1 (ATLAS)
03:25:59.61 -26:16:55.6 17.8mag C/2025 Q3 (ATLAS)
23:47:33.28 +18:26:57.0 8.4mag C/2025 R3 (PANSTARRS)
12:53:55.28 +03:02:24.1 17.4mag C/2025 Y1 (ATLAS)
03:31:34.58 +02:34:22.9 13.4mag C/2026 A1 (MAPS)
00:00:51.53 +37:18:07.4 14.6mag C/2026 B2 (Sun-Gao)
18:43:48.54 -09:41:43.0 11.8mag 10P/Tempel
14:59:40.84 +03:09:43.4 14.0mag 24P/Schaumasse
11:02:40.92 -01:30:42.3 15.7mag 29P/Schwassmann-Wachmann
18:01:05.08 -09:35:38.2 18.0mag 40P/Vaisala
10:37:32.77 -04:03:48.1 16.9mag 43P/Wolf-Harrington
01:49:22.43 +17:33:51.5 17.2mag 47P/Ashbrook-Jackson
07:11:35.93 +36:54:54.2 17.0mag 63P/Wild
23:29:37.98 -11:23:49.1 15.7mag 65P/Gunn
04:04:27.57 +21:24:32.2 15.9mag 76P/West-Kohoutek-Ikemura
01:06:34.51 +08:19:01.7 14.3mag 78P/Gehrels
23:04:22.11 -09:15:29.0 14.6mag 88P/Howell
02:11:40.89 +20:45:43.2 15.1mag 93P/Lovas
04:55:39.46 +32:18:40.5 16.2mag 123P/West-Hartley
08:28:53.66 +38:09:08.0 16.2mag 124P/Mrkos
02:33:54.91 +14:25:12.4 16.4mag 128P/Shoemaker-Holt
02:48:25.47 +14:32:52.4 17.5mag 131P/Mueller
01:28:32.55 +13:23:34.7 10.6mag 141P/Machholz
01:37:24.45 +05:02:33.5 10.6mag 141P-A/Machholz
00:22:29.31 +00:56:10.1 12.8mag 141P-D/Machholz
02:07:46.30 +06:48:07.6 17.8mag 141P-I/Machholz
01:03:38.41 -01:17:56.6 15.1mag 162P/SidingSpring
14:50:37.53 -00:01:19.6 17.7mag 210P/Christensen
21:40:08.84 -11:20:25.9 17.6mag 218P/LINEAR
17:16:40.16 -13:52:45.7 16.1mag 235P/LINEAR
05:35:27.56 +34:43:55.5 16.8mag 240P/NEAT
07:38:43.04 -05:07:06.9 17.7mag 242P/Spahr
22:18:02.27 -20:51:36.1 17.9mag 260P/McNaught
01:59:06.77 +20:34:25.4 18.0mag 295P/LINEAR
15:42:27.97 +07:01:12.3 17.5mag 391P/Kowalski
07:34:22.25 +21:22:01.7 17.7mag 450P/LONEOS
05:36:31.87 +45:00:21.4 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 16 05:53 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
15:25:54.99 +07:49:24.50 2026-04-12.14 16.96
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
04:55:50.66 -29:52:57.70 SN 2026dpg 2026-02-23.11 15.75
04:21:28.18 -53:22:54.40 AT2026drl 2026-02-21.03 17.31
-rw-r--r-- 1 apache apache 5.8K Apr 16 05:53 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 16 05:53 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
14:32:40.720 +02:42:54.71 AT 2026jay 2026-04-06.66 22
14:07:18.110 +04:13:29.83 AT 2026jax 2026-04-06.66 22.26
14:14:08.750 +03:35:26.74 AT 2026jaw 2026-04-06.66 22.24
14:03:53.740 +04:33:03.03 AT 2026jav 2026-04-06.66 22.18
14:07:43.620 +03:35:48.12 AT 2026jau 2026-04-06.66 21.82
14:10:23.930 -01:02:22.49 AT 2026jat 2026-04-06.65 22.15
13:51:42.460 +03:14:48.63 AT 2026jas 2026-04-06.65 21.87
13:42:53.750 +01:22:24.17 AT 2026jar 2026-04-06.65 22.6
13:44:21.040 -01:54:42.32 AT 2026jaq 2026-04-06.65 22.71
13:35:29.290 +00:58:49.10 AT 2026jap 2026-04-06.64 22.39
13:41:45.110 +04:07:23.04 AT 2026jao 2026-04-06.64 21.84
13:38:11.980 +03:37:12.11 AT 2026jan 2026-04-06.64 22.48
13:27:27.970 +05:34:49.94 AT 2026jam 2026-04-06.64 21.79
13:28:44.170 +03:09:01.26 AT 2026jal 2026-04-06.64 22.01
13:29:02.030 -02:11:15.98 AT 2026jak 2026-04-06.64 21.54
13:11:37.460 +01:53:43.84 AT 2026jaj 2026-04-06.63 21.95
13:13:23.110 +00:38:42.68 AT 2026jai 2026-04-06.63 21.88
13:19:01.640 +03:04:08.10 AT 2026jah 2026-04-06.63 22.02
13:06:29.860 +02:34:35.75 AT 2026jag 2026-04-06.63 22.28
13:04:16.080 -00:23:58.35 AT 2026jaf 2026-04-06.63 22.55
-rw-r--r-- 1 apache apache 30K Apr 16 05:53 tns_transients_list.txt
