This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ
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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3119559271076531968,2461139.6134,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3119559271076531968 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.8851+00.9980,2461139.6134,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.8851+00.9980 20260409.1134 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105909517117480064,2461139.6134,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105909517117480064 20260409.1134 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 3125863247975612032,2461139.6134,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3125863247975612032 20260409.1134 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J103.4280-01.9828,2461139.6134,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.4280-01.9828 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113562912617704832,2461139.6134,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113562912617704832 20260409.1134 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J099.9221+01.1622,2461139.6134,13.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J099.9221+01.1622 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.7789+00.7486,2461139.6134,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.7789+00.7486 20260409.1134 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3126792202162858240,2461139.6134,13.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3126792202162858240 20260409.1134 13.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113435060030679936,2461139.6134,13.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113435060030679936 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106052732803548160,2461139.6134,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106052732803548160 20260409.1134 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105924742777831040,2461139.6134,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105924742777831040 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105548121386329600,2461139.6134,12.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105548121386329600 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J103.0397+00.5734,2461139.6134,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.0397+00.5734 20260409.1134 11.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 12569794,2461139.6134,11.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 12569794 20260409.1134 11.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J100.9580+01.5948,2461139.6134,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.9580+01.5948 20260409.1134 12.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3103981287255761536,2461139.6134,12.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3103981287255761536 20260409.1134 12.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3125504223071142784,2461139.6134,12.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3125504223071142784 20260409.1134 12.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113610294697190784,2461139.6134,12.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113610294697190784 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J103.2327-02.3822,2461139.6134,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.2327-02.3822 20260409.1134 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.5628-02.3059,2461139.6134,12.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.5628-02.3059 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.6619-02.2718,2461139.6134,12.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.6619-02.2718 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.3363-00.8503,2461139.6134,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.3363-00.8503 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.6477-03.4721,2461139.6134,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.6477-03.4721 20260409.1134 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105946350754769536,2461139.6134,12.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105946350754769536 20260409.1134 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105921684761121152,2461139.6134,12.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105921684761121152 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3126153111029053568,2461139.6134,12.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3126153111029053568 20260409.1134 12.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.6933-02.7384,2461139.6134,12.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.6933-02.7384 20260409.1134 12.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113967635975814912,2461139.6134,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113967635975814912 20260409.1134 12.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J102.5787+00.4180,2461139.6134,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J102.5787+00.4180 20260409.1134 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
CoRoT 102806577,2461139.6134,13.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
CoRoT 102806577 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J102.9043-01.6544,2461139.6134,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J102.9043-01.6544 20260409.1134 13.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3107281540128223104,2461139.6134,13.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3107281540128223104 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461139.6134,13.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.1126-01.8057,2461139.6134,13.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.1126-01.8057 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
MGAB-V1900,2461139.6134,13.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
MGAB-V1900 20260409.1134 13.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
CoRoT 102785122,2461139.6134,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
CoRoT 102785122 20260409.1134 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3104844811903742208,2461139.6134,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3104844811903742208 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105302831513609216,2461139.6134,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105302831513609216 20260409.1134 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J101.8426+01.4345,2461139.6134,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.8426+01.4345 20260409.1134 13.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106831938650976384,2461139.6134,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106831938650976384 20260409.1134 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113470691079092224,2461139.6134,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113470691079092224 20260409.1134 13.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J099.6630+01.9547,2461139.6134,13.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J099.6630+01.9547 20260409.1134 13.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J099.7145+01.2057,2461139.6134,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J099.7145+01.2057 20260409.1134 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.2592-02.8330,2461139.6134,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.2592-02.8330 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3119353181365762048,2461139.6134,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3119353181365762048 20260409.1134 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106128697885405184,2461139.6134,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106128697885405184 20260409.1134 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3126750798678879360,2461139.6134,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3126750798678879360 20260409.1134 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113580985840495488,2461139.6134,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113580985840495488 20260409.1134 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3119431006172714368,2461139.6134,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3119431006172714368 20260409.1134 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3105901103278785152,2461139.6134,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3105901103278785152 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.9913-01.3476,2461139.6134,13.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.9913-01.3476 20260409.1134 13.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106181925419346432,2461139.6134,13.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106181925419346432 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.6375-01.8671,2461139.6134,13.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.6375-01.8671 20260409.1134 13.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.3519-02.0494,2461139.6134,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.3519-02.0494 20260409.1134 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461139.6134,13.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J099.7529-00.5089,2461139.6134,13.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J099.7529-00.5089 20260409.1134 13.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106199856901798528,2461139.6134,13.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106199856901798528 20260409.1134 13.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J100.9216-04.2458,2461139.6134,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J100.9216-04.2458 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3112396051604609408,2461139.6134,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3112396051604609408 20260409.1134 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113449284962372352,2461139.6134,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113449284962372352 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113342490594252544,2461139.6134,13.42,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113342490594252544 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3107281540128223104,2461139.6134,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3107281540128223104 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J063328.77+015840.4,2461139.6134,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J063328.77+015840.4 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3113463024558758528,2461139.6134,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3113463024558758528 20260409.1134 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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,2461139.6134,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J101.6413-02.6726,2461139.6134,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.6413-02.6726 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3126414691716758272,2461139.6134,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3126414691716758272 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J103.7148-02.6168,2461139.6134,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.7148-02.6168 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3106151345251783936,2461139.6134,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3106151345251783936 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J103.6215-00.7882,2461139.6134,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.6215-00.7882 20260409.1134 13.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J102.5168-01.1896,2461139.6134,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J102.5168-01.1896 20260409.1134 13.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J101.2775-01.0440,2461139.6134,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J101.2775-01.0440 20260409.1134 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 3112353243668770304,2461139.6134,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 3112353243668770304 20260409.1134 13.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
Date (UTC)
JD(UTC)
mag.
R.A. & Dec.(J2000)
X & Y (pix)
Image
WARNING from util/transients/report_transient.sh -- UCAC5 catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat.ucac5 not found - falling back to uncorrected catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J103.0276-01.3052,2461139.6134,13.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J103.0276-01.3052 20260409.1134 13.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS 12514304,2461139.6134,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 12514304 20260409.1134 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461032.81363703 23.12.2025 07:31:28.239 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
First image: 2461032.81363703 23.12.2025 07:31:28.239 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Last image: 2461139.61369706 09.04.2026 02:43:33.426 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 21
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.85
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: 10 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): 31567
Objects passed selection criteria: 31437
Measurements per detected object (mean, median, min, max): 3.1 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.1 4.0 2 4
Average stars detected per image: 25294.2
Average stars matched: 22876.2 (90.4405 %)
Memory usage VmPeak: 131784 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 8 18:56:33 CDT 2026
VaST build number 1.0rc89-5-g00c52b5f
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 9 00:25:29 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: 2461032.81363703 23.12.2025 07:31:28.239 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
First image: 2461032.81363703 23.12.2025 07:31:28.239 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Last image: 2461139.61369706 09.04.2026 02:43:33.426 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 472
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.50
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: 190 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): 231061
Objects passed selection criteria: 230312
Measurements per detected object (mean, median, min, max): 3.1 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.1 4.0 2 4
Average stars detected per image: 188530
Average stars matched: 170838 (90.6159 %)
Memory usage VmPeak: 1982152 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 8 18:56:33 CDT 2026
VaST build number 1.0rc89-5-g00c52b5f
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Apr 9 00:30:07 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
SExtractor catalog cache: saved Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat to cache
SExtractor catalog cache: saved Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.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/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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: 2461139.61302661
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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits exists and is non-empty
Saving wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits to local_wcs_cache/
'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits' -> 'local_wcs_cache/wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits'
wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits exists and is non-empty
Saving wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits to local_wcs_cache/
'wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits' -> 'local_wcs_cache/wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits'
wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits exists and is non-empty
Saving wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits to local_wcs_cache/
'wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits' -> 'local_wcs_cache/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits'
wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits exists and is non-empty
Saving wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits to local_wcs_cache/
'wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits' -> 'local_wcs_cache/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits'
The image scale is 5.84"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.8"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 06:51:43.082 -02:00:16.78
Second-epoch image center 06:51:25.737 -02:00:18.98
Angular distance between the image centers 0.0722 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 06:51:43.082 -02:00:16.78
Second-epoch image center 06:51:28.100 -01:59:37.41
Angular distance between the image centers 0.0633 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 06:51:25.737 -02:00:18.98
Second-epoch second image center 06:51:28.100 -01:59:37.41
Angular distance between the image centers 0.01517 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/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits &> /tmp/tmp.15BFSwmi0Y
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits &> /tmp/tmp.UR6rnTGw77
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits &> /tmp/tmp.9YyKsvnI76
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits &> /tmp/tmp.kDF86LKzd6
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Calibrating the magnitude scale
Found non-empty wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
Found non-empty wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
The reference image (wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits) and catalog (wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat) found
'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat' -> 'wcsmag.cat'
Read 36622 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 95.0306 to 110.7538 deg, Dec -7.3378 to +3.4896 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 95.0306 to 110.7538 deg, Dec -7.3378 to 3.4896 deg
Loaded 24069 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): 377 out of 430 total matches.
Matched with Tycho-2 430 out of 36622 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.893893
a=0.000000 b=1.000000 c=22.893893
From vast_summary.log: estimated ref. image limiting mag.: -7.85
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.04
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.04
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 19 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.1 pix Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
2.1 pix Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
2.5 pix fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
2.5 pix fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Limiting magnitude estimates:
15.0 mag. Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
15.0 mag. Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
14.7 mag. fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
14.7 mag. fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
All-image limiting magnitude estimate: 14.7 (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.15BFSwmi0Y (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits 568.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits' -> 'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS_IMAGE_NAME=wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS-calibrated image found: wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Checking if the catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits alredy exist and is non-empty...
Catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS catalog name: wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=4596, passed=36622
Got 36622 stars (including 31982 good ones) from the SExtractor catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
util/solve_plate_with_UCAC5 got 36622 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 931.8'
Seting catalog search parameters based on the expected field of view 931.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012942 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010353 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.5)
Done reading UCAC5 zone files...
Matched 457 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 347 matched stars entering correct_measured_positions(), 270 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 338 matched stars entering correct_measured_positions(), 14588 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 16.11"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.5)
Done reading UCAC5 zone files...
Matched 489 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 392 matched stars entering correct_measured_positions(), 14615 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 16.01"
Accuracy estimation diagnostic: 390 matched stars entering correct_measured_positions(), 15067 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 12.91"
Excluding outliers - 390 stars left (next iteration limit 371)
The image catalog is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits -region wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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.UR6rnTGw77 (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits 568.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits' -> 'wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS_IMAGE_NAME=wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS-calibrated image found: wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Checking if the catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits alredy exist and is non-empty...
Catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS catalog name: wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=4657, passed=36412
Got 36412 stars (including 31701 good ones) from the SExtractor catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat
util/solve_plate_with_UCAC5 got 36412 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 625.6'
Seting catalog search parameters based on the expected field of view 625.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.008689 (31.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.006951 (25.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 435 to 488 (Dec -3.0 to 7.4)
Done reading UCAC5 zone files...
Matched 20 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Retrying with a larger catalog search radius.
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 435 to 488 (Dec -3.0 to 7.4)
Done reading UCAC5 zone files...
Matched 73 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 51 matched stars entering correct_measured_positions(), 0 with non-zero local correction accuracy
ERROR: the estimated accuracy of the plate solution seems unrealistically small! No stars (out of 51 matched) have non-zero estimated_local_correction_accuracy.
ERROR running correct_measured_positions()
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.9YyKsvnI76 (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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS_IMAGE_NAME=wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS-calibrated image found: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Checking if the catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits alredy exist and is non-empty...
Catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS catalog name: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2953, passed=29071
Got 29071 stars (including 26100 good ones) from the SExtractor catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat
util/solve_plate_with_UCAC5 got 29071 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 936.0'
Seting catalog search parameters based on the expected field of view 936.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013000 (46.8 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010400 (37.4 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 468 (Dec -7.3 to 3.3)
Done reading UCAC5 zone files...
Matched 678 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 628 matched stars entering correct_measured_positions(), 582 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.80"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 625 matched stars entering correct_measured_positions(), 17379 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.15"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 468 (Dec -7.3 to 3.3)
Done reading UCAC5 zone files...
Matched 714 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 673 matched stars entering correct_measured_positions(), 17398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.12"
Accuracy estimation diagnostic: 671 matched stars entering correct_measured_positions(), 18395 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.09"
Excluding outliers - 671 stars left (next iteration limit 687)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits -region wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.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.kDF86LKzd6 (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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS_IMAGE_NAME=wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS-calibrated image found: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Checking if the catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits alredy exist and is non-empty...
Catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS catalog name: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2863, passed=29246
Got 29246 stars (including 26354 good ones) from the SExtractor catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat
util/solve_plate_with_UCAC5 got 29246 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010264 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 470 (Dec -7.3 to 3.6)
Done reading UCAC5 zone files...
Matched 652 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 588 matched stars entering correct_measured_positions(), 535 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.65"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 582 matched stars entering correct_measured_positions(), 14509 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.95"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.6)
Done reading UCAC5 zone files...
Matched 675 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 635 matched stars entering correct_measured_positions(), 14525 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.91"
Accuracy estimation diagnostic: 630 matched stars entering correct_measured_positions(), 16109 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.10"
Excluding outliers - 630 stars left (next iteration limit 640)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits -region wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits'
Saving fully-calibrated image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits'
Saving fully-calibrated image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits'
Saving fully-calibrated image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits'
Preparing the HTML report for the field Mon-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_gaiadr2.txt__out51888.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out51889.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out54820.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out57508.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out57577.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out57588.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out57979.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out58083.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out58137.dat to exclusion_list_gaiadr2.txt
make_report_in_HTML.sh Phase 1 (network queries): 1s
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: 0s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 51888_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 51888_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:38:07.67 -01:28:05.5 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.03, MAG_FAINT_SEARCH_LIMIT=12.01)GAIADR2_OUTPUT=# 1.376 3106909213700454528 099.53163508451 -01.46839862892 11.0128 10.8637 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.376#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 51889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 51889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:48:51.40 +00:22:23.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=10.91, MAG_FAINT_SEARCH_LIMIT=11.89)GAIADR2_OUTPUT=# 2.663 3113516389531142912 102.21376924338 +00.37265378636 11.0074 10.5246 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.663#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 53700_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 53700_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (262.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 54820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 54820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:42:37.62 -03:49:20.4 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.36, MAG_FAINT_SEARCH_LIMIT=12.34)GAIADR2_OUTPUT=# 5.366 3105530185602865536 100.65529148710 -03.82201114961 11.3310 10.6239 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.366#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:51:09.93 -02:35:44.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.96, MAG_FAINT_SEARCH_LIMIT=12.94)GAIADR2_OUTPUT=# 4.998 3105917355433930880 102.79000853321 -02.59546837364 11.5920 10.8606 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.998#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57577_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57577_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:48:47.25 -00:07:19.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.98, MAG_FAINT_SEARCH_LIMIT=12.96)GAIADR2_OUTPUT=# 4.135 3113436228261807616 102.19572627860 -00.12219794173 11.7066 10.8417 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.135#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57588_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57588_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:42:36.41 -02:12:26.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.00, MAG_FAINT_SEARCH_LIMIT=12.98)GAIADR2_OUTPUT=# 3.330 3106608119313089792 100.65078624539 -02.20722417901 11.9774 11.6699 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.330#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57600_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57600_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (368.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57714_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57714_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57902_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57902_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (222.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57906_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57906_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (42.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57943_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57943_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (79.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57979_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 57979_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:42:24.18 -02:34:18.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.07, MAG_FAINT_SEARCH_LIMIT=13.05)GAIADR2_OUTPUT=# 4.737 3106527515668736384 100.59945278767 -02.57160533407 11.8007 11.1211 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.737#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58058_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58058_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (195.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58083_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58083_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:53.52 +01:21:54.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.08, MAG_FAINT_SEARCH_LIMIT=13.06)GAIADR2_OUTPUT=# 5.435 3126065214517150080 102.72155493317 +01.36552187352 12.3588 11.9139 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.435#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58087_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58087_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58106_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58106_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:40:30.77 -01:04:43.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58137_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58137_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:49:28.57 +01:09:18.7 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.11, MAG_FAINT_SEARCH_LIMIT=13.09)GAIADR2_OUTPUT=# 3.037 3125687600994081280 102.36823595003 +01.15494357196 12.1619 11.8897 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.037#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58301_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 58301_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (113.7") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 1s
Prepared the HTML report for the field Mon-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
SExtractor catalog cache: saved Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat to cache
SExtractor catalog cache: saved Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Creating symlink local_wcs_cache/wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Creating symlink local_wcs_cache/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Creating symlink local_wcs_cache/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits exists and is non-empty
wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits exists and is non-empty
wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits exists and is non-empty
wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits exists and is non-empty
The image scale is 5.84"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.8"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 06:51:43.082 -02:00:16.78
Second-epoch image center 06:51:25.737 -02:00:18.98
Angular distance between the image centers 0.0722 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 06:51:43.082 -02:00:16.78
Second-epoch image center 06:51:28.100 -01:59:37.41
Angular distance between the image centers 0.0633 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 06:51:25.737 -02:00:18.98
Second-epoch second image center 06:51:28.100 -01:59:37.41
Angular distance between the image centers 0.01517 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/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits &> /tmp/tmp.WRqNBY3Kwf
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits &> /tmp/tmp.fMqYIP79Fb
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits &> /tmp/tmp.Gw8VFHmcoZ
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits &> /tmp/tmp.b4VA0UfzOi
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Calibrating the magnitude scale
Found non-empty wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
Found non-empty wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits and wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
The reference image (wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits) and catalog (wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat) found
'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat' -> 'wcsmag.cat'
Read 254624 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 95.0305 to 110.7571 deg, Dec -7.3394 to +3.4970 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 95.0305 to 110.7571 deg, Dec -7.3394 to 3.4970 deg
Loaded 24089 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): 401 out of 624 total matches.
Matched with Tycho-2 624 out of 254624 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 21.875059
a=0.000000 b=1.000000 c=21.875059
From vast_summary.log: estimated ref. image limiting mag.: -7.50
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.38
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.38
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 378 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.0 pix Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
2.0 pix Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
2.2 pix fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
2.3 pix fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Limiting magnitude estimates:
14.4 mag. Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
14.4 mag. Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
14.0 mag. fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
14.0 mag. fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
All-image limiting magnitude estimate: 14.0 (SNR ) 13.4 (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.WRqNBY3Kwf (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits 568.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits' -> 'wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS_IMAGE_NAME=wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS-calibrated image found: wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Checking if the catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits alredy exist and is non-empty...
Catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
WCS catalog name: wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=59, blended=45640, passed=254565
Got 254565 stars (including 208571 good ones) from the SExtractor catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat
util/solve_plate_with_UCAC5 got 254565 stars from the SExtractor catalog
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Updated FoV from the plate-solved image: 931.8'
Seting catalog search parameters based on the expected field of view 931.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012942 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010353 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.5)
Done reading UCAC5 zone files...
Matched 468 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 369 matched stars entering correct_measured_positions(), 265 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.77"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 366 matched stars entering correct_measured_positions(), 92781 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.43"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.5)
Done reading UCAC5 zone files...
Matched 498 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 431 matched stars entering correct_measured_positions(), 92827 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.42"
Accuracy estimation diagnostic: 428 matched stars entering correct_measured_positions(), 121659 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.79"
Excluding outliers - 428 stars left (next iteration limit 402)
The image catalog is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits -region wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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.fMqYIP79Fb (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits 568.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits' -> 'wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS_IMAGE_NAME=wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS-calibrated image found: wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Checking if the catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits alredy exist and is non-empty...
Catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat corresponding to the image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
WCS catalog name: wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=58, blended=46013, passed=257598
Got 257598 stars (including 211206 good ones) from the SExtractor catalog wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits.cat
util/solve_plate_with_UCAC5 got 257598 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 625.6'
Seting catalog search parameters based on the expected field of view 625.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.008689 (31.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.006951 (25.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 435 to 488 (Dec -3.0 to 7.4)
Done reading UCAC5 zone files...
Matched 17 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Retrying with a larger catalog search radius.
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 435 to 488 (Dec -3.0 to 7.4)
Done reading UCAC5 zone files...
Matched 68 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 44 matched stars entering correct_measured_positions(), 0 with non-zero local correction accuracy
ERROR: the estimated accuracy of the plate solution seems unrealistically small! No stars (out of 44 matched) have non-zero estimated_local_correction_accuracy.
ERROR running correct_measured_positions()
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.Gw8VFHmcoZ (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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS_IMAGE_NAME=wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS-calibrated image found: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Checking if the catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits alredy exist and is non-empty...
Catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
WCS catalog name: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=42, blended=31841, passed=202062
Got 202062 stars (including 169993 good ones) from the SExtractor catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat
util/solve_plate_with_UCAC5 got 202062 stars from the SExtractor catalog
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Updated FoV from the plate-solved image: 936.0'
Seting catalog search parameters based on the expected field of view 936.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013000 (46.8 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010400 (37.4 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 468 (Dec -7.3 to 3.3)
Done reading UCAC5 zone files...
Matched 667 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 614 matched stars entering correct_measured_positions(), 553 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.45"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 609 matched stars entering correct_measured_positions(), 112978 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.88"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 468 (Dec -7.3 to 3.3)
Done reading UCAC5 zone files...
Matched 694 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 658 matched stars entering correct_measured_positions(), 113002 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.88"
Accuracy estimation diagnostic: 655 matched stars entering correct_measured_positions(), 125293 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.90"
Excluding outliers - 655 stars left (next iteration limit 669)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits -region wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.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.b4VA0UfzOi (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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS_IMAGE_NAME=wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS-calibrated image found: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Checking if the catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits alredy exist and is non-empty...
Catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat corresponding to the image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
WCS catalog name: wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=57, blended=30709, passed=196432
Got 196432 stars (including 165510 good ones) from the SExtractor catalog wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat
util/solve_plate_with_UCAC5 got 196432 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.8'
Seting catalog search parameters based on the expected field of view 923.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012831 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010264 (37.0 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 470 (Dec -7.3 to 3.6)
Done reading UCAC5 zone files...
Matched 653 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 589 matched stars entering correct_measured_positions(), 535 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.39"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 580 matched stars entering correct_measured_positions(), 96337 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.01"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 413 to 469 (Dec -7.3 to 3.6)
Done reading UCAC5 zone files...
Matched 672 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 630 matched stars entering correct_measured_positions(), 96352 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.00"
Accuracy estimation diagnostic: 630 matched stars entering correct_measured_positions(), 113347 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.41"
Excluding outliers - 630 stars left (next iteration limit 638)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits -region wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_Mon-02-Q2b1x1_2025-12-23_01-31-28_20.00sec_-15.00C_LIGHT_0382.fits
Saving fully-calibrated image wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_Mon-02-Q2b1x1_2025-12-23_01-32-16_20.00sec_-15.00C_LIGHT_0383.fits
Saving fully-calibrated image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-42-35_20.00sec_-4.90C_LIGHT_0046.fits
Saving fully-calibrated image wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.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-08_CI_Mon-02-Q2b1x1_233737_TTUQ2b1x1_5753_kByyo7WZ/wcs_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047.fits
Preparing the HTML report for the field Mon-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_gaiadr2.txt__out283813.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out283934.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out283959.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out284139.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out284172.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out284235.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out302490.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out308470.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out313521.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out315055.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out318665.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out325434.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_apass.txt__out320943.dat to exclusion_list_apass.txt
Adding exclusion_list_local.txt__out237671.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out273991.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283657.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283665.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283725.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283749.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283802.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283822.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283842.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283869.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283876.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283907.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283914.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283918.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283925.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283931.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283960.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out283974.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284015.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284038.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284112.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284127.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284183.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284188.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out284213.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out301910.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out302955.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out302986.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out305805.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out306121.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out306732.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out308080.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out308085.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out308154.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out308907.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out308966.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out309086.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out309900.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out310217.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out310986.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out311168.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out312245.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out312427.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out313258.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314059.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314154.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314331.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314450.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314485.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314752.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out314804.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out315108.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out315213.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out315283.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out315987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out316131.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out316311.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out316383.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out317046.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out317511.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out317561.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out317712.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out317927.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out318144.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out318799.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out318820.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out318977.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out319109.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out319795.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out320030.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out320152.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out320346.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out320366.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out320615.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out321119.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out321572.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out321624.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out321831.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out322012.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out323183.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out323273.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out324722.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out324932.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out325148.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out326061.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out326349.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out326861.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out327172.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out327482.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out327855.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out327865.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out327970.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out328039.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out328175.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out328317.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out328521.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out328720.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 131s
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: 61s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283637_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283637_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (138.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283657_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283657_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283663_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283663_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (124.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283665_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283665_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283672_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283672_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (149.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283681_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283681_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (236.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283692_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283692_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (134.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283695_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283695_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (128.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283716_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283716_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (43.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283722_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283722_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283725_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283725_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283728_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283728_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (163.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283729_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283729_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (52.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283730_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283730_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (184.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283736_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283736_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (180.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283741_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283741_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (142.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283749_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283749_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283757_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283757_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (127.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283773_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283773_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (177.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283775_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283775_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283776_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283776_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283778_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283778_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (127.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283802_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283802_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283813_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283813_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:47:23.92 +01:30:18.5 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.37, MAG_FAINT_SEARCH_LIMIT=14.35)GAIADR2_OUTPUT=# 5.578 3125765567538996864 101.84829729096 +01.50441327626 14.1440 13.7368 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.578#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (269.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283822_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283822_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283823_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283823_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (196.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283824_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283824_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (274.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283839_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283839_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (47.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283842_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283842_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283844_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283844_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (98.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283858_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283858_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (215.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283860_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283860_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (349.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283862_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283862_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (119.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283869_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283869_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283874_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283874_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (172.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283876_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283876_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283880_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283880_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (59.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (93.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283892_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283892_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283895_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283895_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (215.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283898_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283898_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (341.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283899_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283899_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (133.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283906_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283906_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283907_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283907_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (342.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283914_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283914_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283916_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283916_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (116.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283918_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283918_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283921_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283921_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (213.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283923_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283923_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (76.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283925_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283925_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (137.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283928_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283928_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (242.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283931_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283931_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283934_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283934_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:39:49.27 +01:08:54.4 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.26, MAG_FAINT_SEARCH_LIMIT=14.24)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283935_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283935_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (356.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283940_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283940_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (241.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283945_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283945_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (93.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283947_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283947_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (152.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283952_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283952_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (58.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283959_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283959_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:24.32 -01:20:42.7 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.31, MAG_FAINT_SEARCH_LIMIT=14.29)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283960_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283960_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283962_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283962_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (378.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283967_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283967_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (232.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283972_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283972_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283974_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 283974_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283975_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283975_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283976_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283976_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (179.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283983_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283983_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (31.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (324.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283995_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283995_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (115.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283996_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283996_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (323.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283999_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 283999_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284009_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284009_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (232.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284011_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284011_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (202.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284015_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284015_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284017_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284017_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284027_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284027_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (101.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284029_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284029_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (245.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284031_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284031_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (184.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284038_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284038_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284040_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284040_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (119.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284041_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284041_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (221.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284050_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284050_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (179.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284056_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284056_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (76.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284058_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284058_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284059_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284059_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (146.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284062_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284062_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (223.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284079_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284079_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284080_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284080_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (222.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284092_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284092_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (93.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284094_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284094_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (146.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284096_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284096_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (96.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284102_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284102_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (374.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284109_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284109_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (191.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284112_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284112_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284115_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284115_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (159.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284118_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284118_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (42.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284121_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284121_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284123_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284123_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (114.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284126_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284126_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (388.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284127_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284127_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284129_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284129_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (349.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284133_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284133_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (331.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284137_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284137_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:46:12.90 +00:51:09.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284139_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284139_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:47:58.54 -00:59:17.3 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.59, MAG_FAINT_SEARCH_LIMIT=13.57)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284145_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284145_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (85.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284150_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284150_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (73.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284155_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284155_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (196.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284160_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284160_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (279.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284162_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284162_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (284.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284169_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284169_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (41.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284171_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284171_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (229.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:40:13.87 +01:34:06.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.23, MAG_FAINT_SEARCH_LIMIT=13.21)GAIADR2_OUTPUT=# 4.744 3126640293461251840 100.05661954788 +01.56798053311 12.8907 11.9582 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.744#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284174_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284174_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (263.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284183_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284183_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284186_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284186_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (160.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284188_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284188_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284192_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284192_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284194_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284194_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (260.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284196_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284196_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (321.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284200_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284200_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (333.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284205_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284205_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (282.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284206_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284206_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (193.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284209_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284209_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (140.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284213_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 284213_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284222_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284222_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284223_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284223_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (375.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284227_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284227_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (98.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284235_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 284235_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:47:04.55 +00:26:35.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=10.57, MAG_FAINT_SEARCH_LIMIT=11.55)GAIADR2_OUTPUT=# 4.250 3125536246345210496 101.76826728192 +00.44226502943 11.4080 10.6410 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.250#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 287327_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 287327_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:40.39 -00:32:22.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 287741_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 287741_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (100.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 288804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 288804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:51:37.40 +00:27:00.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 289601_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 289601_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:51:39.97 +00:25:33.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 290057_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 290057_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:40:37.97 +00:43:04.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 291126_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 291126_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:40:30.73 -01:04:41.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 291737_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 291737_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (104.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 291852_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 291852_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (339.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 292116_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 292116_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:41.87 -00:33:42.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 292353_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 292353_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (205.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 298377_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 298377_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (116.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 299098_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 299098_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (150.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 300087_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 300087_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:45:00.44 -00:03:30.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 300615_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 300615_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (171.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 301102_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 301102_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (90.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 301199_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 301199_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (28.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 301910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 301910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302142_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 302142_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (230.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302490_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 302490_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:45:04.99 -01:02:21.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.37, MAG_FAINT_SEARCH_LIMIT=13.35)GAIADR2_OUTPUT=# 5.156 3107346681891637888 101.26967865935 -01.04031808691 13.2059 12.6723 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.156#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302728_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 302728_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (277.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302836_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 302836_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (315.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302955_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 302955_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 302986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 302986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304072_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304072_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (106.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (202.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304353_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304353_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (143.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304532_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304532_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (154.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304738_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304738_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:47:03.94 -03:46:15.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304879_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304879_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (167.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 304942_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 304942_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (42.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 305150_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 305150_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (172.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 305320_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 305320_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (81.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 305805_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 305805_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 305990_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 305990_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (177.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 306121_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 306121_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 306547_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 306547_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (31.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 306732_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 306732_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 306964_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 306964_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:53:07.45 -01:52:39.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 307038_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 307038_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (162.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 307534_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 307534_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (101.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 307807_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 307807_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (101.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308080_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 308080_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308085_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 308085_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308154_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 308154_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308470_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 308470_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:52:14.26 -00:06:01.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.71, MAG_FAINT_SEARCH_LIMIT=13.69)GAIADR2_OUTPUT=# 5.361 3113331499779778176 103.05834787681 -00.10148142245 13.5344 12.6718 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.361#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308537_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 308537_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:49:36.23 +01:59:11.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308717_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 308717_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (162.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308756_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 308756_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (218.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308907_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 308907_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 308926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (126.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 308966_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 308966_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 309086_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 309086_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 309447_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 309447_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (349.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 309539_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 309539_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (372.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 309900_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 309900_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 309926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 309926_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (169.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 310170_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 310170_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 310217_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 310217_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 310768_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 310768_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:48:20.84 -00:31:48.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 310986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 310986_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 311168_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 311168_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 311659_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 311659_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (31.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312060_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 312060_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:48:33.62 +01:51:09.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312245_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 312245_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312390_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 312390_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (108.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312427_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 312427_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312957_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 312957_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (136.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 312997_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 312997_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (278.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 313258_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 313258_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 313516_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 313516_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (215.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 313521_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 313521_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:42:29.93 -04:08:20.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.96, MAG_FAINT_SEARCH_LIMIT=13.94)GAIADR2_OUTPUT=# 5.000 3105326264854304256 100.62362023901 -04.13992208149 13.6824 12.7988 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.000#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 313864_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 313864_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (118.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314006_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314006_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (34.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314059_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314059_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314068_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314068_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (142.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314154_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314154_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314331_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314331_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314450_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314450_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314485_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314485_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314535_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314535_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (219.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314555_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314555_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (105.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314562_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314562_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (214.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314752_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314752_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314795_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314795_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (244.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 314804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314903_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314903_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (91.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 314910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 314910_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (355.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315055_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315055_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:51:26.46 -02:20:35.4 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.04, MAG_FAINT_SEARCH_LIMIT=14.02)GAIADR2_OUTPUT=# 5.336 3106030429041323008 102.85927994532 -02.34428815611 13.6111 12.7372 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.336#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315060_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315060_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (257.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315108_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 315108_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315125_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315125_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (144.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315213_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 315213_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315283_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 315283_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315600_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315600_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (64.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315705_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315705_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (370.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315790_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315790_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (359.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315834_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315834_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (380.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315981_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 315981_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 315987_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 315987_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316131_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 316131_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316207_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316207_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (108.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316299_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316299_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (399.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316311_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 316311_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316362_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316362_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (286.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316383_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 316383_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316633_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316633_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (163.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316653_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316653_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (201.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316667_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316667_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (164.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 316823_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 316823_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (249.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317039_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 317039_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (113.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317046_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 317046_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317376_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 317376_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (196.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317484_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 317484_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317511_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 317511_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317561_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 317561_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317712_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 317712_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317920_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 317920_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (104.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 317927_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 317927_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318144_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 318144_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318147_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 318147_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (136.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318624_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 318624_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (337.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318665_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 318665_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:44:57.88 -02:51:42.0 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.18, MAG_FAINT_SEARCH_LIMIT=14.16)GAIADR2_OUTPUT=# 4.995 3105761838958624896 101.23984910248 -02.86210694641 14.0439 13.5422 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.995#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318791_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 318791_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (70.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318799_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 318799_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 318820_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 318977_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 318977_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319109_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 319109_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319132_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 319132_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (92.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319355_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 319355_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:41.78 -00:31:44.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319547_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 319547_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (102.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319595_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 319595_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (130.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319685_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 319685_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (154.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 319795_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 319795_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320004_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 320004_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (27.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320030_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 320030_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320152_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 320152_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320301_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 320301_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (36.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320346_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 320346_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320366_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 320366_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320415_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 320415_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (174.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320615_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 320615_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320863_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 320863_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (337.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 320943_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 320943_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:37.17 -01:46:51.3 in APASS (TIMEOUTCOMMAND_GAIA_VIZIER=#timeout 40 #, MAG_MEAN=13.30, MAG_FAINT_SEARCH_LIMIT=14.28)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321119_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 321119_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321200_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 321200_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (290.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321488_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 321488_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (100.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321572_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 321572_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321622_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 321622_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (50.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321624_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 321624_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321647_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 321647_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (105.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321831_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 321831_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 321987_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 321987_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:49:09.51 +01:00:02.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322012_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 322012_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322029_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322029_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (127.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322312_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322312_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (28.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322399_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322399_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (123.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322440_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322440_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (52.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322542_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322542_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322751_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322751_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322916_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322916_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (198.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 322932_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 322932_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (269.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323183_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 323183_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323270_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323270_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323273_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 323273_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323400_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323400_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (82.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (132.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323573_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323573_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323708_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323708_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 323911_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 323911_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (92.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324340_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 324340_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (71.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324707_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 324707_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (57.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324722_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 324722_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324792_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 324792_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (316.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324915_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 324915_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (139.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 324932_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 324932_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325127_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325127_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (153.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325148_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 325148_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325266_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325266_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (139.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325434_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325434_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:40:22.63 +01:18:21.5 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.47, MAG_FAINT_SEARCH_LIMIT=14.45)GAIADR2_OUTPUT=# 5.274 3125881084978463744 100.09324944831 +01.30494231969 14.2492 13.7501 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.274#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325508_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (295.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325535_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325535_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325621_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325621_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (290.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 325960_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 325960_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (372.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326000_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326000_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (185.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326061_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 326061_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326156_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326156_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (51.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326349_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 326349_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326651_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326651_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (82.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326676_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326676_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326752_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326752_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (326.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326805_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326805_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (241.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326861_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 326861_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326875_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326875_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (172.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326985_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326985_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (118.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 326992_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 326992_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (312.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327095_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327095_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (177.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 327172_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327180_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327180_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (117.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327218_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327218_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (178.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327421_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327421_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (358.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327464_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327464_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (269.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327482_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 327482_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327561_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327561_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (227.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327598_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327598_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (141.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327652_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327652_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327702_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327702_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327737_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327737_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (136.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327769_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327769_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (345.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327855_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 327855_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327865_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 327865_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327970_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 327970_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 327999_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 327999_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (50.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328026_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328026_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (106.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328039_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 328039_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328156_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328156_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (118.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328175_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 328175_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328185_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328185_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (126.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328232_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328232_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (179.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328317_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 328317_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328336_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328336_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (244.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328345_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328345_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (225.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328359_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328359_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (201.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328389_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328389_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (80.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328404_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328404_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (66.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328521_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 328521_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328587_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328587_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (200.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328637_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328637_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (216.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328654_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328654_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (93.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328655_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328655_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (141.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328720_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 328720_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328759_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328759_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328783_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328783_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (148.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328815_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328815_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (372.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328877_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328877_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (107.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328889_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (72.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328937_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328937_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (246.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328948_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328948_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (58.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328979_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328979_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (188.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 328992_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 328992_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (387.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 329111_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 329111_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (208.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 121122_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 121122_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (263.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 199360_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 199360_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (371.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273991_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 273991_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 154583_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 154583_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:41:59.48 -01:11:06.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 31804_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
Rejecting candidate due to large distance (91.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237671_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
Preparing report for the candidate 237671_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 228912_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047
The candidate 228912_fd_Mon-02-Q2b1x1_2026-04-08_21-43-33_20.00sec_-4.90C_LIGHT_0047 did not pass the final checks
**** FOUND 06:50:01.03 +01:46:35.1 in the exclusion list exclusion_list.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 7s
make_report_in_HTML.sh TOTAL: 199s
Prepared the HTML report for the field Mon-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
06:40:09.20 +01:22:21.3
06:52:06.77 -01:18:21.4
06:42:58.99 +00:21:15.5
06:42:27.39 +00:12:32.9
06:47:33.20 +00:59:50.6
06:45:13.40 -00:39:25.9
06:51:10.60 -02:47:59.5
06:41:02.69 +01:08:44.0
06:53:43.56 -01:58:38.9
06:51:28.86 +01:59:27.5
06:50:49.30 +00:23:54.0
06:39:42.13 +01:09:51.8
06:46:10.66 +01:00:17.6
06:43:14.66 +01:58:18.9
06:47:09.61 +00:44:32.7
06:49:31.34 +01:58:04.7
06:43:46.02 +00:35:16.1
06:42:18.10 +02:11:08.4
06:49:05.47 -00:09:16.3
06:54:41.08 -02:06:58.2
06:49:52.59 -02:39:52.4
06:46:14.27 +00:50:43.9
06:42:10.03 -03:38:07.6
06:52:10.49 +00:34:37.6
06:43:28.32 -03:56:29.7
06:38:54.52 +00:00:14.2
06:43:50.78 +01:35:52.4
06:40:18.01 -04:25:57.1
06:44:39.89 +00:10:09.8
06:45:06.44 -00:02:44.8
06:48:48.88 +00:23:28.1
06:48:30.86 +00:57:47.6
06:52:55.10 -02:23:01.4
06:46:15.05 -02:18:24.3
06:42:39.40 -02:16:07.8
06:41:18.81 -00:51:03.2
06:42:33.47 -03:28:04.6
06:54:00.11 -02:44:17.1
06:49:56.27 -02:40:53.3
06:54:59.65 -01:03:02.0
06:48:53.37 +01:49:31.0
06:42:46.80 -02:44:15.3
06:53:54.89 +00:47:33.6
06:47:04.35 +01:58:37.9
06:50:18.44 +00:24:41.9
06:46:10.69 -03:13:58.7
06:37:27.26 -02:40:37.9
06:51:34.50 -01:39:22.0
06:41:27.34 -01:18:59.1
06:54:40.32 -00:26:51.0
06:35:10.69 -00:43:16.1
06:39:08.92 -03:48:08.8
06:40:26.20 -01:49:06.3
06:46:50.93 +01:18:07.5
06:45:34.00 -00:26:16.1
06:36:32.65 -03:35:55.5
06:43:37.26 -04:25:01.0
06:48:57.12 -03:30:57.2
06:47:24.10 +01:25:43.7
06:41:21.30 -01:43:19.4
06:45:54.42 -00:09:35.7
06:38:39.71 +01:56:39.5
06:38:52.68 +01:12:25.3
06:44:59.86 -02:49:31.3
06:49:38.99 +00:36:43.1
06:41:40.59 -00:36:38.2
06:49:56.25 -02:17:03.0
06:38:50.11 +02:05:40.4
06:52:35.01 +00:32:32.8
06:38:38.42 -00:17:48.2
06:50:49.03 -02:55:07.3
06:49:27.97 +01:39:55.4
06:47:59.75 -01:20:52.4
06:47:46.66 -02:22:16.5
06:46:32.81 -01:51:11.7
06:45:24.79 -02:02:53.0
06:49:24.98 -00:56:16.2
06:38:58.86 -00:30:11.7
06:46:57.74 -02:12:23.0
06:43:39.98 -04:14:45.9
06:53:08.62 -00:50:31.5
06:48:33.43 -00:03:10.1
06:51:28.70 -00:06:26.9
06:51:46.27 +02:04:09.8
06:41:27.61 -01:19:21.4
06:33:29.32 +01:58:42.4
06:49:19.67 +00:10:30.5
06:51:19.86 -01:48:28.8
06:39:22.63 -04:11:17.6
06:46:31.32 -02:40:23.0
06:46:21.22 +02:10:54.9
06:54:52.41 -02:37:25.8
06:46:04.62 -02:35:18.5
06:54:28.30 -00:47:58.3
06:50:03.15 -01:10:57.5
06:45:06.86 -01:02:34.2
06:52:32.22 -01:11:28.6
########### Completed Mon-02-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
06:42:58.99 +00:21:15.5
06:42:27.39 +00:12:32.9
06:47:33.20 +00:59:50.6
06:45:13.40 -00:39:25.9
06:51:10.60 -02:47:59.5
06:41:02.69 +01:08:44.0
06:53:43.56 -01:58:38.9
06:51:28.86 +01:59:27.5
06:50:49.30 +00:23:54.0
06:39:42.13 +01:09:51.8
06:46:10.66 +01:00:17.6
06:43:14.66 +01:58:18.9
06:47:09.61 +00:44:32.7
06:49:31.34 +01:58:04.7
06:43:46.02 +00:35:16.1
06:42:18.10 +02:11:08.4
06:49:05.47 -00:09:16.3
06:54:41.08 -02:06:58.2
06:49:52.59 -02:39:52.4
06:46:14.27 +00:50:43.9
06:42:10.03 -03:38:07.6
06:52:10.49 +00:34:37.6
06:43:28.32 -03:56:29.7
06:38:54.52 +00:00:14.2
06:43:50.78 +01:35:52.4
06:40:18.01 -04:25:57.1
06:44:39.89 +00:10:09.8
06:45:06.44 -00:02:44.8
06:48:48.88 +00:23:28.1
06:48:30.86 +00:57:47.6
06:52:55.10 -02:23:01.4
06:46:15.05 -02:18:24.3
06:42:39.40 -02:16:07.8
06:41:18.81 -00:51:03.2
06:42:33.47 -03:28:04.6
06:54:00.11 -02:44:17.1
06:49:56.27 -02:40:53.3
06:54:59.65 -01:03:02.0
06:48:53.37 +01:49:31.0
06:42:46.80 -02:44:15.3
06:53:54.89 +00:47:33.6
06:47:04.35 +01:58:37.9
06:50:18.44 +00:24:41.9
06:46:10.69 -03:13:58.7
06:37:27.26 -02:40:37.9
06:51:34.50 -01:39:22.0
06:41:27.34 -01:18:59.1
06:54:40.32 -00:26:51.0
06:35:10.69 -00:43:16.1
06:39:08.92 -03:48:08.8
06:40:26.20 -01:49:06.3
06:46:50.93 +01:18:07.5
06:45:34.00 -00:26:16.1
06:36:32.65 -03:35:55.5
06:43:37.26 -04:25:01.0
06:48:57.12 -03:30:57.2
06:47:24.10 +01:25:43.7
06:41:21.30 -01:43:19.4
06:45:54.42 -00:09:35.7
06:38:39.71 +01:56:39.5
06:38:52.68 +01:12:25.3
06:44:59.86 -02:49:31.3
06:49:38.99 +00:36:43.1
06:41:40.59 -00:36:38.2
06:49:56.25 -02:17:03.0
06:38:50.11 +02:05:40.4
06:52:35.01 +00:32:32.8
06:38:38.42 -00:17:48.2
06:50:49.03 -02:55:07.3
06:49:27.97 +01:39:55.4
06:47:59.75 -01:20:52.4
06:47:46.66 -02:22:16.5
06:46:32.81 -01:51:11.7
06:45:24.79 -02:02:53.0
06:49:24.98 -00:56:16.2
06:38:58.86 -00:30:11.7
06:46:57.74 -02:12:23.0
06:43:39.98 -04:14:45.9
06:53:08.62 -00:50:31.5
06:48:33.43 -00:03:10.1
06:51:28.70 -00:06:26.9
06:51:46.27 +02:04:09.8
06:41:27.61 -01:19:21.4
06:33:29.32 +01:58:42.4
06:49:19.67 +00:10:30.5
06:51:19.86 -01:48:28.8
06:39:22.63 -04:11:17.6
06:46:31.32 -02:40:23.0
06:46:21.22 +02:10:54.9
06:54:52.41 -02:37:25.8
06:46:04.62 -02:35:18.5
06:54:28.30 -00:47:58.3
06:50:03.15 -01:10:57.5
06:45:06.86 -01:02:34.2
06:52:32.22 -01:11:28.6
06:52:06.77 -01:18:21.4
06:40:09.20 +01:22:21.3
###################################################################################
06:42:58.99 +00:21:15.5 -- not an asteroid (will add it to exclusion list)
06:42:27.39 +00:12:32.9 -- not an asteroid (will add it to exclusion list)
06:47:33.20 +00:59:50.6 -- not an asteroid (will add it to exclusion list)
06:45:13.40 -00:39:25.9 -- not an asteroid (will add it to exclusion list)
06:51:10.60 -02:47:59.5 -- not an asteroid (will add it to exclusion list)
06:41:02.69 +01:08:44.0 -- not an asteroid (will add it to exclusion list)
06:53:43.56 -01:58:38.9 -- not an asteroid (will add it to exclusion list)
06:51:28.86 +01:59:27.5 -- not an asteroid (will add it to exclusion list)
06:50:49.30 +00:23:54.0 -- not an asteroid (will add it to exclusion list)
06:39:42.13 +01:09:51.8 -- not an asteroid (will add it to exclusion list)
06:46:10.66 +01:00:17.6 -- not an asteroid (will add it to exclusion list)
06:43:14.66 +01:58:18.9 -- not an asteroid (will add it to exclusion list)
06:47:09.61 +00:44:32.7 -- not an asteroid (will add it to exclusion list)
06:49:31.34 +01:58:04.7 -- not an asteroid (will add it to exclusion list)
06:43:46.02 +00:35:16.1 -- not an asteroid (will add it to exclusion list)
06:42:18.10 +02:11:08.4 -- not an asteroid (will add it to exclusion list)
06:49:05.47 -00:09:16.3 -- not an asteroid (will add it to exclusion list)
06:54:41.08 -02:06:58.2 -- not an asteroid (will add it to exclusion list)
06:49:52.59 -02:39:52.4 -- not an asteroid (will add it to exclusion list)
06:46:14.27 +00:50:43.9 -- not an asteroid (will add it to exclusion list)
06:42:10.03 -03:38:07.6 -- not an asteroid (will add it to exclusion list)
06:52:10.49 +00:34:37.6 -- not an asteroid (will add it to exclusion list)
06:43:28.32 -03:56:29.7 -- not an asteroid (will add it to exclusion list)
06:38:54.52 +00:00:14.2 -- not an asteroid (will add it to exclusion list)
06:43:50.78 +01:35:52.4 -- not an asteroid (will add it to exclusion list)
06:40:18.01 -04:25:57.1 -- not an asteroid (will add it to exclusion list)
06:44:39.89 +00:10:09.8 -- not an asteroid (will add it to exclusion list)
06:45:06.44 -00:02:44.8 -- not an asteroid (will add it to exclusion list)
06:48:48.88 +00:23:28.1 -- not an asteroid (will add it to exclusion list)
06:48:30.86 +00:57:47.6 -- not an asteroid (will add it to exclusion list)
06:52:55.10 -02:23:01.4 -- not an asteroid (will add it to exclusion list)
06:46:15.05 -02:18:24.3 -- not an asteroid (will add it to exclusion list)
06:42:39.40 -02:16:07.8 -- not an asteroid (will add it to exclusion list)
06:41:18.81 -00:51:03.2 -- not an asteroid (will add it to exclusion list)
06:42:33.47 -03:28:04.6 -- not an asteroid (will add it to exclusion list)
06:54:00.11 -02:44:17.1 -- not an asteroid (will add it to exclusion list)
06:49:56.27 -02:40:53.3 -- not an asteroid (will add it to exclusion list)
06:54:59.65 -01:03:02.0 -- not an asteroid (will add it to exclusion list)
06:48:53.37 +01:49:31.0 -- not an asteroid (will add it to exclusion list)
06:42:46.80 -02:44:15.3 -- not an asteroid (will add it to exclusion list)
06:53:54.89 +00:47:33.6 -- not an asteroid (will add it to exclusion list)
06:47:04.35 +01:58:37.9 -- not an asteroid (will add it to exclusion list)
06:50:18.44 +00:24:41.9 -- not an asteroid (will add it to exclusion list)
06:46:10.69 -03:13:58.7 -- not an asteroid (will add it to exclusion list)
06:37:27.26 -02:40:37.9 -- not an asteroid (will add it to exclusion list)
06:51:34.50 -01:39:22.0 -- not an asteroid (will add it to exclusion list)
06:41:27.34 -01:18:59.1 -- not an asteroid (will add it to exclusion list)
06:54:40.32 -00:26:51.0 -- not an asteroid (will add it to exclusion list)
06:35:10.69 -00:43:16.1 -- not an asteroid (will add it to exclusion list)
06:39:08.92 -03:48:08.8 -- not an asteroid (will add it to exclusion list)
06:40:26.20 -01:49:06.3 -- not an asteroid (will add it to exclusion list)
06:46:50.93 +01:18:07.5 -- not an asteroid (will add it to exclusion list)
06:45:34.00 -00:26:16.1 -- not an asteroid (will add it to exclusion list)
06:36:32.65 -03:35:55.5 -- not an asteroid (will add it to exclusion list)
06:43:37.26 -04:25:01.0 -- not an asteroid (will add it to exclusion list)
06:48:57.12 -03:30:57.2 -- not an asteroid (will add it to exclusion list)
06:47:24.10 +01:25:43.7 -- not an asteroid (will add it to exclusion list)
06:41:21.30 -01:43:19.4 -- not an asteroid (will add it to exclusion list)
06:45:54.42 -00:09:35.7 -- not an asteroid (will add it to exclusion list)
06:38:39.71 +01:56:39.5 -- not an asteroid (will add it to exclusion list)
06:38:52.68 +01:12:25.3 -- not an asteroid (will add it to exclusion list)
06:44:59.86 -02:49:31.3 -- not an asteroid (will add it to exclusion list)
06:49:38.99 +00:36:43.1 -- not an asteroid (will add it to exclusion list)
06:41:40.59 -00:36:38.2 -- not an asteroid (will add it to exclusion list)
06:49:56.25 -02:17:03.0 -- not an asteroid (will add it to exclusion list)
06:38:50.11 +02:05:40.4 -- not an asteroid (will add it to exclusion list)
06:52:35.01 +00:32:32.8 -- not an asteroid (will add it to exclusion list)
06:38:38.42 -00:17:48.2 -- not an asteroid (will add it to exclusion list)
06:50:49.03 -02:55:07.3 -- not an asteroid (will add it to exclusion list)
06:49:27.97 +01:39:55.4 -- not an asteroid (will add it to exclusion list)
06:47:59.75 -01:20:52.4 -- not an asteroid (will add it to exclusion list)
06:47:46.66 -02:22:16.5 -- not an asteroid (will add it to exclusion list)
06:46:32.81 -01:51:11.7 -- not an asteroid (will add it to exclusion list)
06:45:24.79 -02:02:53.0 -- not an asteroid (will add it to exclusion list)
06:49:24.98 -00:56:16.2 -- not an asteroid (will add it to exclusion list)
06:38:58.86 -00:30:11.7 -- not an asteroid (will add it to exclusion list)
06:46:57.74 -02:12:23.0 -- not an asteroid (will add it to exclusion list)
06:43:39.98 -04:14:45.9 -- not an asteroid (will add it to exclusion list)
06:53:08.62 -00:50:31.5 -- not an asteroid (will add it to exclusion list)
06:48:33.43 -00:03:10.1 -- not an asteroid (will add it to exclusion list)
06:51:28.70 -00:06:26.9 -- not an asteroid (will add it to exclusion list)
06:51:46.27 +02:04:09.8 -- not an asteroid (will add it to exclusion list)
06:41:27.61 -01:19:21.4 -- not an asteroid (will add it to exclusion list)
06:33:29.32 +01:58:42.4 -- not an asteroid (will add it to exclusion list)
06:49:19.67 +00:10:30.5 -- not an asteroid (will add it to exclusion list)
06:51:19.86 -01:48:28.8 -- not an asteroid (will add it to exclusion list)
06:39:22.63 -04:11:17.6 -- not an asteroid (will add it to exclusion list)
06:46:31.32 -02:40:23.0 -- not an asteroid (will add it to exclusion list)
06:46:21.22 +02:10:54.9 -- not an asteroid (will add it to exclusion list)
06:54:52.41 -02:37:25.8 -- not an asteroid (will add it to exclusion list)
06:46:04.62 -02:35:18.5 -- not an asteroid (will add it to exclusion list)
06:54:28.30 -00:47:58.3 -- not an asteroid (will add it to exclusion list)
06:50:03.15 -01:10:57.5 -- not an asteroid (will add it to exclusion list)
06:45:06.86 -01:02:34.2 -- not an asteroid (will add it to exclusion list)
06:52:32.22 -01:11:28.6 -- not an asteroid (will add it to exclusion list)
06:52:06.77 -01:18:21.4 -- not an asteroid (will add it to exclusion list)
06:40:09.20 +01:22:21.3 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
06:33:29.32 +01:58:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:35:10.69 -00:43:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:36:32.65 -03:35:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:37:27.26 -02:40:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:38.42 -00:17:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:39.71 +01:56:39.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:50.11 +02:05:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:52.68 +01:12:25.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:54.52 +00:00:14.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:38:58.86 -00:30:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:39:08.92 -03:48:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:39:22.63 -04:11:17.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:39:42.13 +01:09:51.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:40:09.20 +01:22:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:40:18.01 -04:25:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:40:26.20 -01:49:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:02.69 +01:08:44.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:18.81 -00:51:03.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:21.30 -01:43:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:27.34 -01:18:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:27.61 -01:19:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:41:40.59 -00:36:38.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:10.03 -03:38:07.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:18.10 +02:11:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:27.39 +00:12:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:33.47 -03:28:04.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:39.40 -02:16:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:46.80 -02:44:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:42:58.99 +00:21:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:14.66 +01:58:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:28.32 -03:56:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:37.26 -04:25:01.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:39.98 -04:14:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:46.02 +00:35:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:43:50.78 +01:35:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:44:39.89 +00:10:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:44:59.86 -02:49:31.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:06.44 -00:02:44.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:06.86 -01:02:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:13.40 -00:39:25.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:24.79 -02:02:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:34.00 -00:26:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:45:54.42 -00:09:35.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:04.62 -02:35:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:10.66 +01:00:17.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:10.69 -03:13:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:14.27 +00:50:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:15.05 -02:18:24.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:21.22 +02:10:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:31.32 -02:40:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:32.81 -01:51:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:50.93 +01:18:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:46:57.74 -02:12:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:04.35 +01:58:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:09.61 +00:44:32.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:24.10 +01:25:43.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:33.20 +00:59:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:46.66 -02:22:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:47:59.75 -01:20:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:48:30.86 +00:57:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:48:33.43 -00:03:10.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:48:48.88 +00:23:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:48:53.37 +01:49:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:48:57.12 -03:30:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:05.47 -00:09:16.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:19.67 +00:10:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:24.98 -00:56:16.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:27.97 +01:39:55.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:31.34 +01:58:04.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:38.99 +00:36:43.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:52.59 -02:39:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:56.25 -02:17:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:49:56.27 -02:40:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:50:03.15 -01:10:57.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:50:18.44 +00:24:41.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:50:49.03 -02:55:07.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:50:49.30 +00:23:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:10.60 -02:47:59.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:19.86 -01:48:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:28.70 -00:06:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:28.86 +01:59:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:34.50 -01:39:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:51:46.27 +02:04:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:52:06.77 -01:18:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:52:10.49 +00:34:37.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:52:32.22 -01:11:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:52:35.01 +00:32:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:52:55.10 -02:23:01.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:53:08.62 -00:50:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:53:43.56 -01:58:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:53:54.89 +00:47:33.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:00.11 -02:44:17.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:28.30 -00:47:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:40.32 -00:26:51.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:41.08 -02:06:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:52.41 -02:37:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:54:59.65 -01:03:02.0 -- 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)
06:33:29.32 +01:58:42.4 -- a known variable star
06:35:10.69 -00:43:16.1 -- not a known variable star
06:36:32.65 -03:35:55.5 -- not a known variable star
06:37:27.26 -02:40:37.9 -- not a known variable star
06:38:38.42 -00:17:48.2 -- not a known variable star
06:38:39.71 +01:56:39.5 -- not a known variable star
06:38:50.11 +02:05:40.4 -- a known variable star
06:38:52.68 +01:12:25.3 -- not a known variable star
06:38:54.52 +00:00:14.2 -- not a known variable star
06:38:58.86 -00:30:11.7 -- not a known variable star
06:39:08.92 -03:48:08.8 -- not a known variable star
06:39:22.63 -04:11:17.6 -- not a known variable star
06:39:42.13 +01:09:51.8 -- not a known variable star
06:40:09.20 +01:22:21.3 -- a known variable star
06:40:18.01 -04:25:57.1 -- a known variable star
06:40:26.20 -01:49:06.3 -- not a known variable star
06:41:02.69 +01:08:44.0 -- not a known variable star
06:41:18.81 -00:51:03.2 -- not a known variable star
06:41:21.30 -01:43:19.4 -- not a known variable star
06:41:27.34 -01:18:59.1 -- a known variable star
06:41:27.61 -01:19:21.4 -- a known variable star
06:41:40.59 -00:36:38.2 -- not a known variable star
06:42:10.03 -03:38:07.6 -- not a known variable star
06:42:18.10 +02:11:08.4 -- a known variable star
06:42:27.39 +00:12:32.9 -- a known variable star
06:42:33.47 -03:28:04.6 -- not a known variable star
06:42:39.40 -02:16:07.8 -- not a known variable star
06:42:46.80 -02:44:15.3 -- not a known variable star
06:42:58.99 +00:21:15.5 -- not a known variable star
06:43:14.66 +01:58:18.9 -- not a known variable star
06:43:28.32 -03:56:29.7 -- a known variable star
06:43:37.26 -04:25:01.0 -- a known variable star
06:43:39.98 -04:14:45.9 -- not a known variable star
06:43:46.02 +00:35:16.1 -- not a known variable star
06:43:50.78 +01:35:52.4 -- not a known variable star
06:44:39.89 +00:10:09.8 -- a known variable star
06:44:59.86 -02:49:31.3 -- not a known variable star
06:45:06.44 -00:02:44.8 -- not a known variable star
06:45:06.86 -01:02:34.2 -- not a known variable star
06:45:13.40 -00:39:25.9 -- not a known variable star
06:45:24.79 -02:02:53.0 -- not a known variable star
06:45:34.00 -00:26:16.1 -- a known variable star
06:45:54.42 -00:09:35.7 -- not a known variable star
06:46:04.62 -02:35:18.5 -- not a known variable star
06:46:10.66 +01:00:17.6 -- not a known variable star
06:46:10.69 -03:13:58.7 -- a known variable star
06:46:14.27 +00:50:43.9 -- not a known variable star
06:46:15.05 -02:18:24.3 -- not a known variable star
06:46:21.22 +02:10:54.9 -- not a known variable star
06:46:31.32 -02:40:23.0 -- not a known variable star
06:46:32.81 -01:51:11.7 -- not a known variable star
06:46:50.93 +01:18:07.5 -- a known variable star
06:46:57.74 -02:12:23.0 -- not a known variable star
06:47:04.35 +01:58:37.9 -- not a known variable star
06:47:09.61 +00:44:32.7 -- not a known variable star
06:47:24.10 +01:25:43.7 -- not a known variable star
06:47:33.20 +00:59:50.6 -- not a known variable star
06:47:46.66 -02:22:16.5 -- not a known variable star
06:47:59.75 -01:20:52.4 -- not a known variable star
06:48:30.86 +00:57:47.6 -- not a known variable star
06:48:33.43 -00:03:10.1 -- not a known variable star
06:48:48.88 +00:23:28.1 -- a known variable star
06:48:53.37 +01:49:31.0 -- a known variable star
06:48:57.12 -03:30:57.2 -- not a known variable star
06:49:05.47 -00:09:16.3 -- not a known variable star
06:49:19.67 +00:10:30.5 -- not a known variable star
06:49:24.98 -00:56:16.2 -- not a known variable star
06:49:27.97 +01:39:55.4 -- not a known variable star
06:49:31.34 +01:58:04.7 -- not a known variable star
06:49:38.99 +00:36:43.1 -- not a known variable star
06:49:52.59 -02:39:52.4 -- not a known variable star
06:49:56.25 -02:17:03.0 -- not a known variable star
06:49:56.27 -02:40:53.3 -- not a known variable star
06:50:03.15 -01:10:57.5 -- not a known variable star
06:50:18.44 +00:24:41.9 -- not a known variable star
06:50:49.03 -02:55:07.3 -- a known variable star
06:50:49.30 +00:23:54.0 -- a known variable star
06:51:10.60 -02:47:59.5 -- not a known variable star
06:51:19.86 -01:48:28.8 -- not a known variable star
06:51:28.70 -00:06:26.9 -- not a known variable star
06:51:28.86 +01:59:27.5 -- not a known variable star
06:51:34.50 -01:39:22.0 -- not a known variable star
06:51:46.27 +02:04:09.8 -- not a known variable star
06:52:06.77 -01:18:21.4 -- not a known variable star
06:52:10.49 +00:34:37.6 -- not a known variable star
06:52:32.22 -01:11:28.6 -- a known variable star
06:52:35.01 +00:32:32.8 -- not a known variable star
06:52:55.10 -02:23:01.4 -- not a known variable star
06:53:08.62 -00:50:31.5 -- a known variable star
06:53:43.56 -01:58:38.9 -- not a known variable star
06:53:54.89 +00:47:33.6 -- not a known variable star
06:54:00.11 -02:44:17.1 -- not a known variable star
06:54:28.30 -00:47:58.3 -- not a known variable star
06:54:40.32 -00:26:51.0 -- not a known variable star
06:54:41.08 -02:06:58.2 -- a known variable star
06:54:52.41 -02:37:25.8 -- not a known variable star
06:54:59.65 -01:03:02.0 -- not a known variable star
Found 76 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
97 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 97 (excluding asteroids and hot pixels, 76 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)2461139.61302661 -observatory V36
23:33:14.70 -05:21:30.4 Mercury (0.2mag)
02:35:22.02 +15:06:31.4 Venus (-3.9mag)
23:58:14.54 -01:17:36.8 Mars (1.2mag)
07:09:45.57 +22:50:49.7 Jupiter (-2.1mag)
00:26:05.18 +00:29:35.3 Saturn (0.9mag)
03:46:17.42 +19:42:56.5 Uranus (5.8mag)
00:09:55.51 -00:21:09.5 Neptune (7.8mag)
20:33:24.54 -22:52:27.0 Pluto (14.5mag)
18:33:03.75 -27:54:07.8 Moon (-10.7mag)
-rw-r--r-- 1 apache apache 362 Apr 9 00:25 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461139.61302661:
07:09:48.85 +22:50:45.4 Io (5.7mag)
07:09:53.02 +22:50:36.7 Europa (5.9mag)
07:10:01.06 +22:50:13.5 Ganymede (5.3mag)
07:09:14.62 +22:51:54.9 Callisto (6.5mag)
07:13:22.49 +22:41:48.8 Himalia (15.3mag)
07:09:49.72 +22:50:41.6 Thebe (16.2mag)
07:13:24.44 +23:11:09.9 Elara (17.3mag)
07:08:10.31 +23:34:26.3 Pasiphae (17.4mag)
07:18:13.99 +22:48:06.9 Carme (18.5mag)
00:26:11.65 +00:29:24.5 Titan (8.8mag)
00:26:10.14 +00:29:43.5 Rhea (10.1mag)
00:25:59.09 +00:30:47.1 Iapetus (11.5mag)
00:26:16.40 +00:29:21.5 Hyperion (14.8mag)
00:27:47.32 +00:39:06.9 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 9 00:25 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461139.61302661:
15:04:17.07 -10:53:58.3 JWST
17:28:45.48 +39:44:20.1 Chandra
16:40:23.17 -53:36:35.6 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 9 00:25 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461139.61302661 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:48:45.98 -28:23:25.5 13.9mag P/2010 H2 (Vales)
05:01:58.54 -69:59:54.7 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:31:04.38 +31:23:35.5 17.2mag C/2017 K2 (PANSTARRS)
17:30:53.70 +09:43:25.6 17.6mag C/2021 G2 (ATLAS)
23:08:15.82 +28:58:07.9 17.0mag C/2022 E2 (ATLAS)
04:21:17.85 +25:50:51.6 15.9mag C/2022 N2 (PANSTARRS)
09:02:12.34 +31:57:06.9 16.2mag C/2022 QE78 (ATLAS)
08:30:12.96 -00:54:07.7 17.3mag C/2022 R6 (PANSTARRS)
18:55:08.41 +17:56:49.2 17.5mag C/2023 A3 (Tsuchinshan-ATLAS)
15:42:44.75 -11:37:13.7 17.6mag P/2023 B1 (PANSTARRS)
09:11:08.34 -13:00:37.1 17.6mag C/2023 F3 (ATLAS)
21:46:52.24 +62:31:17.1 17.5mag C/2023 H5 (Lemmon)
19:24:32.16 -03:38:16.1 14.2mag C/2023 R1 (PANSTARRS)
21:41:20.05 +84:58:58.6 17.8mag C/2023 X2 (Lemmon)
06:15:15.34 +63:33:25.4 17.1mag C/2024 A1 (ATLAS)
04:57:57.77 +15:47:25.0 10.6mag C/2024 E1 (Wierzchos)
16:23:28.70 +05:15:30.4 17.4mag C/2024 G6 (ATLAS)
20:18:37.94 +13:26:18.5 14.7mag C/2024 J3 (ATLAS)
03:20:16.78 -23:27:18.7 16.4mag C/2024 T5 (ATLAS)
05:11:00.79 +47:03:07.2 17.7mag C/2025 J1 (Borisov)
14:07:21.28 +40:10:54.5 14.9mag C/2025 L1 (ATLAS)
03:14:40.41 -25:10:13.0 17.8mag C/2025 Q3 (ATLAS)
23:02:34.56 +19:46:30.8 9.6mag C/2025 R3 (PANSTARRS)
12:57:07.16 +02:34:55.1 17.5mag C/2025 Y1 (ATLAS)
02:16:29.03 +03:44:54.6 10.3mag C/2026 A1 (MAPS)
23:39:35.40 +35:52:20.1 14.4mag C/2026 B2 (Sun-Gao)
18:29:30.10 -10:04:36.0 12.2mag 10P/Tempel
15:09:21.34 +03:52:09.3 13.4mag 24P/Schaumasse
11:04:48.74 -01:45:31.7 15.7mag 29P/Schwassmann-Wachmann
17:58:19.10 -09:52:29.3 17.8mag 40P/Vaisala
10:38:17.18 -04:40:48.8 16.8mag 43P/Wolf-Harrington
01:38:02.38 +16:18:15.9 17.2mag 47P/Ashbrook-Jackson
06:58:21.79 +38:28:25.8 17.0mag 63P/Wild
23:20:09.51 -12:17:26.5 15.7mag 65P/Gunn
03:45:08.82 +18:49:05.2 15.9mag 76P/West-Kohoutek-Ikemura
00:50:26.14 +06:52:02.0 14.4mag 78P/Gehrels
22:41:47.32 -11:25:13.4 14.6mag 88P/Howell
01:51:09.44 +18:46:02.7 15.1mag 93P/Lovas
04:42:06.41 +31:54:10.7 16.3mag 123P/West-Hartley
08:20:46.24 +41:32:31.0 16.2mag 124P/Mrkos
02:22:38.71 +13:35:33.7 16.4mag 128P/Shoemaker-Holt
02:34:04.34 +13:37:57.3 17.5mag 131P/Mueller
00:50:32.92 +10:44:17.7 11.0mag 141P/Machholz
01:00:17.41 +02:17:14.9 11.0mag 141P-A/Machholz
23:49:10.41 -01:29:51.6 13.7mag 141P-D/Machholz
01:29:51.42 +03:59:43.8 17.9mag 141P-I/Machholz
00:43:13.51 -04:58:20.7 15.2mag 162P/SidingSpring
10:30:07.12 +31:19:26.3 17.9mag 164P/Christensen
06:23:47.18 +24:27:03.5 17.9mag 198P/ODAS
15:03:38.11 -00:50:08.9 17.4mag 210P/Christensen
21:18:10.84 -13:06:54.9 17.5mag 218P/LINEAR
17:14:07.33 -14:44:36.9 16.2mag 235P/LINEAR
05:19:46.39 +34:07:48.4 16.6mag 240P/NEAT
07:35:21.38 -05:56:25.9 17.7mag 242P/Spahr
15:45:04.96 +06:31:08.7 17.5mag 391P/Kowalski
07:31:46.86 +21:20:00.3 17.6mag 450P/LONEOS
05:25:59.21 +45:26:15.9 17.4mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 9 00:25 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
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.70 -27:51:49.80 SN2026gvk 2026-03-30 15.48
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.80 -63:44:05.50 ASASSN-26ch 2026-03-27.86 13.02
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.88 -53:16:33.80 ASASSN-26cc 2026-03-20.04 15.48
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.96 -45:55:38.40 ASASSN-26bt 2026-03-18.8 16.32
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.46 +15:42:15.50 SN2026ehe 2026-03-12.34 -0.18
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.70 -47:26:45.00 ASASSN-26bn 2026-03-10.3 15.14
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.33 -37:49:33.00 ASASSN-26bk 2026-03-2.06 13.58
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.29 +19:58:46.30 ASASSN-26be 2026-02-25.56 14.95
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
11:50:37.32 +55:21:13.70 SN 2026dix 2026-02-21.43 16.39
16:21:19.69 -63:47:29.40 ASASSN-26az 2026-02-21.03 17.02
02:45:30.93 -54:17:43.10 SN 2026cju 2026-02-21.04 17.54
01:58:40.68 +47:34:50.10 ASASSN-26av 2026-02-21.09 15.97
18:35:53.01 -42:31:38.90 ASASSN-26aw 2026-02-21.12 15.89
11:40:18.88 -39:45:09.20 ASASSN-26ax 2026-02-21.08 15.73
02:26:23.52 -51:42:29.80 ASASSN-26ay 2026-02-21.04 13.93
08:46:07.66 +01:17:43.90 ASASSN-26ba 2026-02-20.23 15.43
14:15:47.49 -48:05:16.60 SN2026dez 2026-02-19.31 15.91
17:25:53.90 -23:28:31.50 ASASSN-26au 2026-02-18.33 15.82
16:07:59.09 -24:00:10.00 SN2026cmv 2026-02-17.28 16.19
18:15:01.25 -37:43:36.70 ASASSN-26at 2026-02-16.36 15.94
13:01:07.22 -11:25:16.10 AT2026bzh 2026-02-12.16 17.22
10:56:29.81 -07:07:25.30 SN 2026bre 2026-02-12.16 17.15
08:55:43.51 -53:26:11.50 ASASSN-26as 2026-02-12.2 16.54
06:33:50.98 -41:46:25.10 ASASSN-26ar 2026-02-12.04 16.42
12:15:22.43 +23:59:39.60 SN2026bzg 2026-02-11.27 16.32
08:01:10.95 -03:43:14.30 AT2026coj 2026-02-9.25 13.73
12:44:00.18 -57:03:46.80 ASASSN-26aq 2026-02-9.18 16
-rw-r--r-- 1 apache apache 5.8K Apr 9 00:25 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
06:57:11.19 -17:24:43.9 TCP J06571119-1724439 2026-01-18.5375 14.2mag
00:42:52.23 +41:01:44.7 PNV J00425223+4101447 2026-01-19.5505 18.74Cmag
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
-rw-r--r-- 1 apache apache 187K Apr 9 00:25 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
16:52:21.140 +31:25:32.03 AT 2026ifo 2026-03-27.86 19.73
16:06:48.970 +28:22:45.47 AT 2026ifn 2026-03-27.85 21.37
16:26:20.250 +28:06:35.30 AT 2026ifm 2026-03-27.85 20.13
17:01:36.800 +29:43:13.81 AT 2026ifl 2026-03-27.85 20.62
17:06:26.770 +28:47:25.16 AT 2026ifk 2026-03-27.85 21.39
16:47:18.680 +27:13:25.92 AT 2026ifj 2026-03-27.85 20.26
15:55:49.720 +37:36:32.33 AT 2026ifi 2026-03-24.80 21.32
16:05:53.820 +48:45:26.80 AT 2026ifh 2026-03-23.81 21.26
16:27:03.110 +44:45:26.84 AT 2026ifg 2026-03-23.81 21.9
16:41:17.580 +44:27:03.47 AT 2026iff 2026-03-23.81 22.17
16:30:53.670 +55:47:08.39 AT 2026ife 2026-03-30.85 20.99
16:07:35.060 +52:45:21.40 AT 2026ifd 2026-03-30.82 20.79
12:49:57.980 +19:52:49.93 AT 2026ifc 2026-03-20.70 19.71
15:58:08.890 +36:23:36.27 AT 2026ifb 2026-03-18.81 20.34
15:47:02.670 +48:09:28.72 AT 2026ifa 2026-03-30.81 20.31
15:30:58.600 +53:17:16.37 AT 2026iez 2026-03-23.80 21.21
10:25:53.600 +03:15:54.45 AT 2026iey 2026-03-24.63 22.18
19:10:17.892 -22:37:27.97 AT 2026iex 2026-03-30.80 18.87
12:44:39.935 -44:03:37.93 AT 2026iew 2026-03-31.50 19.02
14:52:16.530 -15:21:39.90 AT 2026iev 2026-04-02.23 19.3
-rw-r--r-- 1 apache apache 30K Apr 9 00:25 tns_transients_list.txt
