This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 21 02 22.28 +18 09 58.0 9.7 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4135979,2461149.9609,9.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
DocumentRef: VOTx4135979 20260419.4609 9.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASAS J211017+1834.7,2461149.9609,11.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASAS J211017+1834.7 20260419.4609 11.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4125525,2461149.9609,12.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
DocumentRef: VOTx4125525 20260419.4609 12.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!
TCP 2026 04 19.4610* 21 01 13.10 +18 56 33.0 14.4 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.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
target,2461149.9609,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J317.1815+25.2456,2461149.9609,13.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J317.1815+25.2456 20260419.4609 13.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
NSVS J2112100+184903,2461149.9609,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
NSVS J2112100+184903 20260419.4609 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!
TCP 2026 04 19.4610* 21 05 53.72 +19 23 31.0 13.5 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,13.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 13.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 1841593126539496320,2461149.9609,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
Gaia DR3 1841593126539496320 20260419.4609 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!
TCP 2026 04 19.4610* 20 59 27.19 +17 55 47.4 13.8 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,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
target 20260419.4609 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
target,2461149.9609,13.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 13.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
WISE J211014.9+203300,2461149.9609,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
WISE J211014.9+203300 20260419.4609 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 1841416410106997504,2461149.9609,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1841416410106997504 20260419.4609 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 21 05 55.58 +19 22 45.5 13.9 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 21 06 12.94 +18 35 54.0 13.9 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J320.6833+24.9193,2461149.9609,14.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
ATO J320.6833+24.9193 20260419.4609 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 20 55 28.91 +18 02 50.7 14.3 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.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 1841073366776849408,2461149.9609,14.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1841073366776849408 20260419.4609 14.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.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 20260419.4609 14.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
target,2461149.9609,14.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
target 20260419.4609 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 21 05 03.29 +19 54 14.7 14.5 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.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
target 20260419.4609 14.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,2461149.9609,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.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
target 20260419.4609 14.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,2461149.9609,14.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
target 20260419.4609 14.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,2461149.9609,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.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
target,2461149.9609,14.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.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,2461149.9609,14.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.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
target,2461149.9609,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 20 58 55.54 +19 37 57.6 14.6 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.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
target 20260419.4609 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 19.4610* 21 01 17.88 +19 13 32.4 14.7 U Del 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.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 20260419.4609 14.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,2461149.9609,14.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461149.9609,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260419.4609 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0693 Peg,2461149.9609,11.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0693 Peg 20260419.4609 11.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.54561373 27.12.2025 01:05:31.026 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461036.54561373 27.12.2025 01:05:31.026 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461149.96129420 19.04.2026 11:04:05.819 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.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.99
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: 7 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): 17998
Objects passed selection criteria: 17905
Measurements per detected object (mean, median, min, max): 3.0 3.0 2 4
Measurements per selected object (mean, median, min, max): 3.0 3.0 2 4
Average stars detected per image: 13853.5
Average stars matched: 12026.2 (86.8102 %)
Memory usage VmPeak: 120680 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 06:50:34 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461036.54561373 27.12.2025 01:05:31.026 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461036.54561373 27.12.2025 01:05:31.026 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461149.96129420 19.04.2026 11:04:05.819 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 196
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.63
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: 75 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): 124362
Objects passed selection criteria: 123995
Measurements per detected object (mean, median, min, max): 2.9 3.0 2 4
Measurements per selected object (mean, median, min, max): 2.9 3.0 2 4
Average stars detected per image: 96902.5
Average stars matched: 84994.2 (87.7111 %)
Memory usage VmPeak: 1934476 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Apr 16 15:05:05 CDT 2026
VaST build number 1.0rc89-19-g55e4b97d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Apr 19 06:54:11 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
SExtractor catalog cache: saved Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat to cache
SExtractor catalog cache: saved Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461149.96059851
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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits exists and is non-empty
Saving wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits to local_wcs_cache/
'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits' -> 'local_wcs_cache/wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits'
wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits exists and is non-empty
Saving wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits to local_wcs_cache/
'wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits' -> 'local_wcs_cache/wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits'
wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits exists and is non-empty
Saving wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits to local_wcs_cache/
'wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits' -> 'local_wcs_cache/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits'
wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits exists and is non-empty
Saving wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits to local_wcs_cache/
'wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits' -> 'local_wcs_cache/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits (1st reference image)
verification OK: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Image size: 941.6'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:13:51.296 +21:59:55.63 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits (1st new image)
verification OK: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Image size: 915.6'x627.1' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.74"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:14:00.763 +21:58:38.39 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 21:13:51.296 +21:59:55.63
Second-epoch image center 21:14:00.763 +21:58:38.39
Angular distance between the image centers 0.0424 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits (2nd new image)
verification OK: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Image size: 915.6'x627.6' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.74"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:13:58.474 +21:59:15.23 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 21:13:51.296 +21:59:55.63
Second-epoch image center 21:13:58.474 +21:59:15.23
Angular distance between the image centers 0.0299 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 21:14:00.763 +21:58:38.39
Second-epoch second image center 21:13:58.474 +21:59:15.23
Angular distance between the image centers 0.01353 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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits &> /tmp/tmp.Dx3v0coPHb
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits &> /tmp/tmp.2JCQT1X5sh
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits &> /tmp/tmp.fwjm0n6ecH
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits &> /tmp/tmp.9JS0s6jRzx
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Calibrating the magnitude scale
Found non-empty wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
Found non-empty wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
The reference image (wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits) and catalog (wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat) found
'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat' -> 'wcsmag.cat'
Read 18556 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 309.7692 to 327.3471 deg, Dec +16.4399 to +27.3032 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 309.7692 to 327.3471 deg, Dec 16.4399 to 27.3032 deg
Loaded 16162 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): 11578 out of 12381 total matches.
Matched with Tycho-2 12381 out of 18556 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.929726
a=0.000000 b=1.000000 c=22.929726
From vast_summary.log: estimated ref. image limiting mag.: -7.99
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.94
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.94
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: 8000)
Median FWHM seeing for isolated stars:
2.4 pix Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
2.4 pix Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
2.7 pix fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
2.7 pix fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Limiting magnitude estimates:
14.9 mag. Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
14.9 mag. Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
14.8 mag. fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
14.8 mag. fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 12.0 (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.Dx3v0coPHb (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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits' -> 'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS_IMAGE_NAME=wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS-calibrated image found: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Checking if the catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits alredy exist and is non-empty...
Catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS catalog name: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1581, passed=18556
Got 18556 stars (including 16957 good ones) from the SExtractor catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
util/solve_plate_with_UCAC5 got 18556 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010462 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 941 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 915 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.45"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 17889 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.44"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 941 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 17887 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.45"
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 17887 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.49"
Excluding outliers - 938 stars left (next iteration limit 1031)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits -region wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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.2JCQT1X5sh (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/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits' -> 'wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS_IMAGE_NAME=wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS-calibrated image found: wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Checking if the catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits alredy exist and is non-empty...
Catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS catalog name: wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1543, passed=18535
Got 18535 stars (including 16975 good ones) from the SExtractor catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat
util/solve_plate_with_UCAC5 got 18535 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 913.8'
Seting catalog search parameters based on the expected field of view 913.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012692 (45.7 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010153 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 514 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 466 matched stars entering correct_measured_positions(), 398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.10"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 466 matched stars entering correct_measured_positions(), 7862 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.36"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 526 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 475 matched stars entering correct_measured_positions(), 7866 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.25"
Accuracy estimation diagnostic: 474 matched stars entering correct_measured_positions(), 7706 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.52"
Excluding outliers - 474 stars left (next iteration limit 512)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits -region wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.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.fwjm0n6ecH (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS_IMAGE_NAME=wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS-calibrated image found: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Checking if the catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits alredy exist and is non-empty...
Catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS catalog name: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1461, passed=17811
Got 17811 stars (including 16338 good ones) from the SExtractor catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat
util/solve_plate_with_UCAC5 got 17811 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 915.6'
Seting catalog search parameters based on the expected field of view 915.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012717 (45.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.010173 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 538 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 513 matched stars entering correct_measured_positions(), 454 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.65"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 512 matched stars entering correct_measured_positions(), 7873 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.16"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 572 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 537 matched stars entering correct_measured_positions(), 7886 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.10"
Accuracy estimation diagnostic: 536 matched stars entering correct_measured_positions(), 8401 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.29"
Excluding outliers - 536 stars left (next iteration limit 563)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits -region wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.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.9JS0s6jRzx (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS_IMAGE_NAME=wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS-calibrated image found: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Checking if the catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits alredy exist and is non-empty...
Catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS catalog name: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1411, passed=17522
Got 17522 stars (including 16094 good ones) from the SExtractor catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat
util/solve_plate_with_UCAC5 got 17522 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 915.6'
Seting catalog search parameters based on the expected field of view 915.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012717 (45.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.010173 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 540 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 512 matched stars entering correct_measured_positions(), 451 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.72"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 510 matched stars entering correct_measured_positions(), 7922 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.22"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 565 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 536 matched stars entering correct_measured_positions(), 7942 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.14"
Accuracy estimation diagnostic: 536 matched stars entering correct_measured_positions(), 8008 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.18"
Excluding outliers - 536 stars left (next iteration limit 561)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits -region wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits'
Saving fully-calibrated image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits'
Saving fully-calibrated image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits'
Saving fully-calibrated image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits'
Preparing the HTML report for the field Vul-03-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_gaiadr2.txt__out24865.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out24987.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out25031.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out25361.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out21095.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out23877.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out25040.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 61s
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: 3s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21095_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 21095_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23074_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 23074_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:21:06.25 +24:21:35.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23177_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 23177_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:12:31.86 +21:29:59.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23597_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 23597_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:23:19.28 +23:28:44.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23857_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 23857_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23877_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 23877_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23960_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 23960_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (41.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24541_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 24541_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:12:31.71 +24:43:04.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24678_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 24678_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (23.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24779_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 24779_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:10:09.35 +25:56:22.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24865_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 24865_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:22:40.18 +18:37:09.3 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.94, MAG_FAINT_SEARCH_LIMIT=12.92)GAIADR2_OUTPUT=# 1.640 1785563869412135296 320.66707965494 +18.61892500980 10.8144 9.4284 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.640#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24987_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 24987_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:11:15.44 +23:28:32.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.07, MAG_FAINT_SEARCH_LIMIT=13.05)GAIADR2_OUTPUT=# 0.515 1840144829206768512 317.81417857100 +23.47562968615 11.6839 10.8953 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#0.515#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25031_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 25031_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:32:10.99 +22:57:46.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.97, MAG_FAINT_SEARCH_LIMIT=12.95)GAIADR2_OUTPUT=# 1.183 1797229275466538752 323.04582763180 +22.96316013899 11.2286 10.0573 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#1.183#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25040_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 25040_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25104_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 25104_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:21:13.52 +21:57:28.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25107_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 25107_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:23:13.36 +20:38:43.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 25361_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 25361_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:30:04.18 +22:21:29.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.06, MAG_FAINT_SEARCH_LIMIT=13.04)GAIADR2_OUTPUT=# 2.065 1791013049040084480 322.51684940394 +22.35834280859 10.9524 9.5786 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.065#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 17151_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 17151_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:29:22.57 +18:10:02.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 14947_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 14947_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:13:01.10 +18:56:07.3 in the exclusion list exclusion_list.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 64s
Prepared the HTML report for the field Vul-03-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 ####
21:02:22.28 +18:09:58.0
21:10:18.35 +18:34:41.4
21:09:32.65 +21:06:34.7
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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
SExtractor catalog cache: saved Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat to cache
SExtractor catalog cache: saved Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Creating symlink local_wcs_cache/wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Creating symlink local_wcs_cache/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Creating symlink local_wcs_cache/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits exists and is non-empty
wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits exists and is non-empty
wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits exists and is non-empty
wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits (1st reference image)
verification OK: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Image size: 941.6'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:13:51.296 +21:59:55.63 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits (1st new image)
verification OK: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Image size: 915.6'x627.1' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.74"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:14:00.763 +21:58:38.39 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 21:13:51.296 +21:59:55.63
Second-epoch image center 21:14:00.763 +21:58:38.39
Angular distance between the image centers 0.0424 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits (2nd new image)
verification OK: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Image size: 915.6'x627.6' 15.3(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.74"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 21:13:58.474 +21:59:15.23 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 21:13:51.296 +21:59:55.63
Second-epoch image center 21:13:58.474 +21:59:15.23
Angular distance between the image centers 0.0299 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 21:14:00.763 +21:58:38.39
Second-epoch second image center 21:13:58.474 +21:59:15.23
Angular distance between the image centers 0.01353 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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits &> /tmp/tmp.qorSlIcw99
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits &> /tmp/tmp.5eE2yGPzH2
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits &> /tmp/tmp.8sijfysGPt
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits &> /tmp/tmp.uETeEyMOTl
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Calibrating the magnitude scale
Found non-empty wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
Found non-empty wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
The reference image (wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits) and catalog (wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat) found
'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat' -> 'wcsmag.cat'
Read 136126 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 309.7552 to 327.3571 deg, Dec +16.4400 to +27.3032 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 309.7552 to 327.3571 deg, Dec 16.4400 to 27.3032 deg
Loaded 16188 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): 10471 out of 13465 total matches.
Matched with Tycho-2 13465 out of 136126 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.751440
a=0.000000 b=1.000000 c=22.751440
From vast_summary.log: estimated ref. image limiting mag.: -7.63
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.12
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.12
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 158 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.2 pix Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
2.2 pix Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
2.5 pix fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
2.5 pix fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Limiting magnitude estimates:
15.1 mag. Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
15.1 mag. Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
14.8 mag. fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
14.8 mag. fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 14.2 (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.qorSlIcw99 (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/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits' -> 'wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS_IMAGE_NAME=wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS-calibrated image found: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Checking if the catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits alredy exist and is non-empty...
Catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
WCS catalog name: wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=50, blended=14038, passed=136076
Got 136076 stars (including 121801 good ones) from the SExtractor catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat
util/solve_plate_with_UCAC5 got 136076 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010462 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 944 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 915 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.45"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 132398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.46"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 944 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 132397 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.46"
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 132399 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
Excluding outliers - 940 stars left (next iteration limit 1034)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits -region wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.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.5eE2yGPzH2 (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/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits 567.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits' -> 'wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS_IMAGE_NAME=wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS-calibrated image found: wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Checking if the catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits alredy exist and is non-empty...
Catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat corresponding to the image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
WCS catalog name: wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=30, blended=13978, passed=135637
Got 135637 stars (including 121417 good ones) from the SExtractor catalog wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat
util/solve_plate_with_UCAC5 got 135637 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 913.8'
Seting catalog search parameters based on the expected field of view 913.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012692 (45.7 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010153 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 524 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 472 matched stars entering correct_measured_positions(), 404 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.78"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 469 matched stars entering correct_measured_positions(), 59707 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.00"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 537 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 486 matched stars entering correct_measured_positions(), 59719 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.98"
Accuracy estimation diagnostic: 483 matched stars entering correct_measured_positions(), 62102 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.47"
Excluding outliers - 483 stars left (next iteration limit 515)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits -region wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.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.8sijfysGPt (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS_IMAGE_NAME=wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS-calibrated image found: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Checking if the catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits alredy exist and is non-empty...
Catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
WCS catalog name: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=12, blended=11941, passed=105723
Got 105723 stars (including 93661 good ones) from the SExtractor catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat
util/solve_plate_with_UCAC5 got 105723 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 915.6'
Seting catalog search parameters based on the expected field of view 915.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012717 (45.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.010173 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 519 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 491 matched stars entering correct_measured_positions(), 428 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.94"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 487 matched stars entering correct_measured_positions(), 43193 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.24"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 551 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 521 matched stars entering correct_measured_positions(), 43207 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.23"
Accuracy estimation diagnostic: 518 matched stars entering correct_measured_positions(), 47323 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.38"
Excluding outliers - 518 stars left (next iteration limit 535)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits -region wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.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.uETeEyMOTl (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS_IMAGE_NAME=wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS-calibrated image found: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Checking if the catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits alredy exist and is non-empty...
Catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat corresponding to the image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
WCS catalog name: wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat
SExtractor catalog parsing summary: zero_flux=8, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=19, blended=11929, passed=105572
Got 105572 stars (including 93532 good ones) from the SExtractor catalog wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat
util/solve_plate_with_UCAC5 got 105572 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 915.6'
Seting catalog search parameters based on the expected field of view 915.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012717 (45.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.010173 (36.6 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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 522 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 495 matched stars entering correct_measured_positions(), 431 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.89"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 493 matched stars entering correct_measured_positions(), 43150 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.17"
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 532 to 588 (Dec 16.4 to 27.3)
Done reading UCAC5 zone files...
Matched 552 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 526 matched stars entering correct_measured_positions(), 43169 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.16"
Accuracy estimation diagnostic: 523 matched stars entering correct_measured_positions(), 48260 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.42"
Excluding outliers - 523 stars left (next iteration limit 542)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits -region wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.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_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_Vul-03-Q2b1x1_2025-12-26_19-05-31_20.00sec_-14.90C_LIGHT_0006.fits
Saving fully-calibrated image wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_Vul-03-Q2b1x1_2025-12-26_19-06-11_20.00sec_-15.00C_LIGHT_0007.fits
Saving fully-calibrated image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-03-05_20.00sec_-5.00C_LIGHT_0767.fits
Saving fully-calibrated image wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-19_CI_Vul-03-Q2b1x1_060450_TTUQ2b1x1_2799170_MCxPy9Em/wcs_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768.fits
Preparing the HTML report for the field Vul-03-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
Adding exclusion_list_gaiadr2.txt__out155335.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out155393.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out178517.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out183075.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out184432.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out187839.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out155359.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out155390.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out155411.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out165738.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172111.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out172303.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175574.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out175654.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out176727.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177017.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out177742.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out178905.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out181659.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out183048.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out184536.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out185060.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out185212.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out186407.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out186743.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out186878.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187489.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187517.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187640.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187662.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187728.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187907.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out187956.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out188190.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out188225.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out188480.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out55751.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 56s
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: 20s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155335_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155335_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:09:42.14 +24:10:40.1 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.72, MAG_FAINT_SEARCH_LIMIT=15.70)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155341_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155341_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (30.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155358_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155358_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (24.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155359_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 155359_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155363_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155363_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (36.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155364_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155364_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (35.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155365_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155365_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (35.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155369_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155369_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155374_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155374_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155375_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155375_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (26.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155380_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155380_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155389_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155389_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (31.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155390_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 155390_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155393_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155393_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:24:44.24 +18:23:09.3 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.68, MAG_FAINT_SEARCH_LIMIT=14.66)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155411_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 155411_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155414_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155414_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155416_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155416_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155419_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155419_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (37.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155422_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155422_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (33.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155423_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155423_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155424_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155424_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155425_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155425_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:21:01.72 +25:53:39.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155427_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 155427_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 156021_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 156021_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:13:01.20 +18:56:06.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 157978_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 157978_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (29.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 158251_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 158251_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:21:06.31 +24:21:34.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 160570_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 160570_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 161707_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 161707_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (30.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 163308_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 163308_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 164722_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 164722_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165738_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 165738_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 165750_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 165750_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:15:06.04 +18:38:03.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 166392_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 166392_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:26:28.04 +21:53:17.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 168333_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 168333_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170758_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 170758_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (32.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170778_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 170778_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (29.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171039_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 171039_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172111_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 172111_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172303_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 172303_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172808_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 172808_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:11:00.54 +25:06:20.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 173490_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 173490_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174165_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 174165_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174366_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 174366_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175484_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 175484_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:31:45.18 +21:26:17.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175574_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 175574_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175654_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 175654_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175895_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 175895_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 175989_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 175989_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176003_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 176003_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:19:38.22 +24:02:14.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176690_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 176690_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:23:31.43 +25:56:41.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 176727_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 176727_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177017_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 177017_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177742_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 177742_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178343_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 178343_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178350_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 178350_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:12:21.35 +19:51:55.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178389_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 178389_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (44.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178517_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 178517_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:21:59.23 +25:29:41.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.91, MAG_FAINT_SEARCH_LIMIT=14.89)GAIADR2_OUTPUT=# 5.181 1846599546577465856 320.49525291124 +25.49515443914 13.9461 13.3846 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.181#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 178905_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 178905_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179040_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 179040_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:12:29.91 +19:16:44.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179473_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 179473_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179896_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 179896_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (59.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 180693_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 180693_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:22:35.71 +21:58:48.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181295_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 181295_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:27:03.22 +21:51:51.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181596_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 181596_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181659_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 181659_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181966_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 181966_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182059_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 182059_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (33.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182363_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 182363_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (27.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182501_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 182501_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182698_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 182698_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182922_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 182922_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 183048_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 183048_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 183075_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 183075_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:08:04.30 +23:43:30.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.39, MAG_FAINT_SEARCH_LIMIT=15.37)GAIADR2_OUTPUT=# 3.085 1840132390981147776 317.01732067584 +23.72588298828 14.8683 13.8684 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.085#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 183343_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 183343_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 183395_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 183395_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 183496_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 183496_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184044_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184044_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184273_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184273_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (62.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184319_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184319_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184432_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184432_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:11:37.90 +25:55:58.6 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.47, MAG_FAINT_SEARCH_LIMIT=15.45)GAIADR2_OUTPUT=# 5.186 1841642913800302464 317.90637689724 +25.93334175178 14.4428 13.7194 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.186#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184493_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184493_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184536_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 184536_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184678_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184678_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (41.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184895_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184895_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (31.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184903_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184903_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (33.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 184984_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 184984_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (42.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185060_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 185060_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185110_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185110_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (45.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185147_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185147_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (59.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185212_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 185212_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185278_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185278_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185396_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185396_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185459_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185459_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (62.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185508_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185508_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185559_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185559_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185715_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185715_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185842_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185842_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185847_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185847_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:11:34.79 +23:44:49.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 185966_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 185966_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (34.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186079_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186079_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186233_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186233_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (27.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186234_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186234_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186241_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186241_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:26:45.99 +20:22:16.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186277_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186277_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186358_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186358_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (32.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186407_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 186407_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186430_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186430_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:09:03.19 +23:36:04.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186513_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186513_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186563_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186563_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (64.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186572_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186572_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (25.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186680_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186680_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186743_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 186743_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186768_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186768_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186858_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186858_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186878_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 186878_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186958_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186958_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186973_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 186973_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187048_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187048_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187089_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187089_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (77.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187123_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187123_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (27.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187191_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187191_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (35.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187199_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187199_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187239_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187239_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (41.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187273_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187273_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187290_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187290_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187332_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187332_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187449_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187449_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187483_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187483_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (39.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187489_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187489_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187517_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187517_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187523_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187523_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (29.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187537_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187537_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187539_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187539_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (34.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187601_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187601_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187625_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187625_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187640_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187640_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187662_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187662_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187728_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187728_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187732_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187732_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (31.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187804_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187804_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187839_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187839_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:10:57.09 +25:17:25.1 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.54, MAG_FAINT_SEARCH_LIMIT=15.52)GAIADR2_OUTPUT=# 4.227 1841491559152637184 317.73659939029 +25.29052615371 14.2832 13.6501 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.227#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187907_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187907_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187956_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 187956_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187990_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 187990_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188025_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 188025_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188065_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 188065_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188190_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 188190_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188225_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 188225_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188238_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 188238_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (28.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188480_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 188480_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 147972_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 147972_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:23:19.32 +23:28:44.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 55751_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
Preparing report for the candidate 55751_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 121049_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 121049_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:23:13.91 +19:25:27.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 99728_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 99728_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (34.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 103651_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 103651_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:29:22.61 +18:10:02.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 107733_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 107733_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:10:18.27 +18:34:42.2 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 79516_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 79516_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
**** FOUND 21:12:32.21 +21:29:59.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 102015_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768
The candidate 102015_fd_Vul-03-Q2b1x1_2026-04-19_06-04-05_20.00sec_-5.00C_LIGHT_0768 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 2s
make_report_in_HTML.sh TOTAL: 78s
Prepared the HTML report for the field Vul-03-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
21:02:22.28 +18:09:58.0
21:10:18.35 +18:34:41.4
21:09:32.65 +21:06:34.7
21:01:13.10 +18:56:33.0
21:29:46.44 +25:14:40.0
21:08:45.01 +25:14:28.5
21:12:10.48 +18:49:03.9
21:05:53.72 +19:23:31.0
21:15:18.91 +25:51:28.1
20:59:27.19 +17:55:47.4
21:10:18.97 +20:43:43.9
21:10:14.10 +20:32:57.9
21:11:13.92 +24:52:10.9
21:05:55.58 +19:22:45.5
21:06:12.94 +18:35:54.0
21:22:45.78 +24:54:54.8
20:55:28.91 +18:02:50.7
21:07:45.21 +24:42:05.6
21:24:29.80 +25:11:31.9
21:11:13.97 +25:47:34.3
21:05:03.29 +19:54:14.7
21:15:52.70 +24:31:46.4
21:24:05.96 +22:43:51.7
21:08:52.16 +21:07:14.8
21:04:07.68 +22:47:35.5
21:10:39.74 +25:07:21.6
21:12:23.99 +25:51:59.4
21:05:38.04 +23:25:07.4
20:58:55.54 +19:37:57.6
21:14:10.12 +25:04:21.1
21:01:17.88 +19:13:32.4
21:23:29.07 +24:21:05.0
21:21:37.33 +25:02:12.5
21:27:55.92 +23:10:53.6
########### Completed Vul-03-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 ####
21:02:22.28 +18:09:58.0
21:10:18.35 +18:34:41.4
21:09:32.65 +21:06:34.7
21:01:13.10 +18:56:33.0
21:29:46.44 +25:14:40.0
21:08:45.01 +25:14:28.5
21:12:10.48 +18:49:03.9
21:05:53.72 +19:23:31.0
21:15:18.91 +25:51:28.1
20:59:27.19 +17:55:47.4
21:10:18.97 +20:43:43.9
21:10:14.10 +20:32:57.9
21:11:13.92 +24:52:10.9
21:05:55.58 +19:22:45.5
21:06:12.94 +18:35:54.0
21:22:45.78 +24:54:54.8
20:55:28.91 +18:02:50.7
21:07:45.21 +24:42:05.6
21:24:29.80 +25:11:31.9
21:11:13.97 +25:47:34.3
21:05:03.29 +19:54:14.7
21:15:52.70 +24:31:46.4
21:24:05.96 +22:43:51.7
21:08:52.16 +21:07:14.8
21:04:07.68 +22:47:35.5
21:10:39.74 +25:07:21.6
21:12:23.99 +25:51:59.4
21:05:38.04 +23:25:07.4
20:58:55.54 +19:37:57.6
21:14:10.12 +25:04:21.1
21:01:17.88 +19:13:32.4
21:23:29.07 +24:21:05.0
21:21:37.33 +25:02:12.5
21:27:55.92 +23:10:53.6
###################################################################################
21:02:22.28 +18:09:58.0 -- not an asteroid (will add it to exclusion list)
21:10:18.35 +18:34:41.4 -- not an asteroid (will add it to exclusion list)
21:09:32.65 +21:06:34.7 -- not an asteroid (will add it to exclusion list)
21:01:13.10 +18:56:33.0 -- not an asteroid (will add it to exclusion list)
21:29:46.44 +25:14:40.0 -- not an asteroid (will add it to exclusion list)
21:08:45.01 +25:14:28.5 -- not an asteroid (will add it to exclusion list)
21:12:10.48 +18:49:03.9 -- not an asteroid (will add it to exclusion list)
21:05:53.72 +19:23:31.0 -- not an asteroid (will add it to exclusion list)
21:15:18.91 +25:51:28.1 -- not an asteroid (will add it to exclusion list)
20:59:27.19 +17:55:47.4 -- not an asteroid (will add it to exclusion list)
21:10:18.97 +20:43:43.9 -- not an asteroid (will add it to exclusion list)
21:10:14.10 +20:32:57.9 -- not an asteroid (will add it to exclusion list)
21:11:13.92 +24:52:10.9 -- not an asteroid (will add it to exclusion list)
21:05:55.58 +19:22:45.5 -- not an asteroid (will add it to exclusion list)
21:06:12.94 +18:35:54.0 -- not an asteroid (will add it to exclusion list)
21:22:45.78 +24:54:54.8 -- not an asteroid (will add it to exclusion list)
20:55:28.91 +18:02:50.7 -- not an asteroid (will add it to exclusion list)
21:07:45.21 +24:42:05.6 -- not an asteroid (will add it to exclusion list)
21:24:29.80 +25:11:31.9 -- not an asteroid (will add it to exclusion list)
21:11:13.97 +25:47:34.3 -- not an asteroid (will add it to exclusion list)
21:05:03.29 +19:54:14.7 -- not an asteroid (will add it to exclusion list)
21:15:52.70 +24:31:46.4 -- not an asteroid (will add it to exclusion list)
21:24:05.96 +22:43:51.7 -- not an asteroid (will add it to exclusion list)
21:08:52.16 +21:07:14.8 -- not an asteroid (will add it to exclusion list)
21:04:07.68 +22:47:35.5 -- not an asteroid (will add it to exclusion list)
21:10:39.74 +25:07:21.6 -- not an asteroid (will add it to exclusion list)
21:12:23.99 +25:51:59.4 -- not an asteroid (will add it to exclusion list)
21:05:38.04 +23:25:07.4 -- not an asteroid (will add it to exclusion list)
20:58:55.54 +19:37:57.6 -- not an asteroid (will add it to exclusion list)
21:14:10.12 +25:04:21.1 -- not an asteroid (will add it to exclusion list)
21:01:17.88 +19:13:32.4 -- not an asteroid (will add it to exclusion list)
21:23:29.07 +24:21:05.0 -- not an asteroid (will add it to exclusion list)
21:21:37.33 +25:02:12.5 -- not an asteroid (will add it to exclusion list)
21:27:55.92 +23:10:53.6 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
20:55:28.91 +18:02:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
20:58:55.54 +19:37:57.6 -- does not seem to be a hot pixel (will add it to exclusion list)
20:59:27.19 +17:55:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:01:13.10 +18:56:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
21:01:17.88 +19:13:32.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:02:22.28 +18:09:58.0 -- does not seem to be a hot pixel (will add it to exclusion list)
21:04:07.68 +22:47:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
21:05:03.29 +19:54:14.7 -- does not seem to be a hot pixel (will add it to exclusion list)
21:05:38.04 +23:25:07.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:05:53.72 +19:23:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
21:05:55.58 +19:22:45.5 -- does not seem to be a hot pixel (will add it to exclusion list)
21:06:12.94 +18:35:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
21:07:45.21 +24:42:05.6 -- does not seem to be a hot pixel (will add it to exclusion list)
21:08:45.01 +25:14:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
21:08:52.16 +21:07:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
21:09:32.65 +21:06:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
21:10:14.10 +20:32:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
21:10:18.35 +18:34:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:10:18.97 +20:43:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
21:10:39.74 +25:07:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
21:11:13.92 +24:52:10.9 -- does not seem to be a hot pixel (will add it to exclusion list)
21:11:13.97 +25:47:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
21:12:10.48 +18:49:03.9 -- does not seem to be a hot pixel (will add it to exclusion list)
21:12:23.99 +25:51:59.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:14:10.12 +25:04:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
21:15:18.91 +25:51:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
21:15:52.70 +24:31:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
21:21:37.33 +25:02:12.5 -- does not seem to be a hot pixel (will add it to exclusion list)
21:22:45.78 +24:54:54.8 -- does not seem to be a hot pixel (will add it to exclusion list)
21:23:29.07 +24:21:05.0 -- does not seem to be a hot pixel (will add it to exclusion list)
21:24:05.96 +22:43:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
21:24:29.80 +25:11:31.9 -- does not seem to be a hot pixel (will add it to exclusion list)
21:27:55.92 +23:10:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
21:29:46.44 +25:14:40.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)
20:55:28.91 +18:02:50.7 -- not a known variable star
20:58:55.54 +19:37:57.6 -- not a known variable star
20:59:27.19 +17:55:47.4 -- not a known variable star
21:01:13.10 +18:56:33.0 -- not a known variable star
21:01:17.88 +19:13:32.4 -- not a known variable star
21:02:22.28 +18:09:58.0 -- not a known variable star
21:04:07.68 +22:47:35.5 -- not a known variable star
21:05:03.29 +19:54:14.7 -- not a known variable star
21:05:38.04 +23:25:07.4 -- not a known variable star
21:05:53.72 +19:23:31.0 -- not a known variable star
21:05:55.58 +19:22:45.5 -- not a known variable star
21:06:12.94 +18:35:54.0 -- not a known variable star
21:07:45.21 +24:42:05.6 -- a known variable star
21:08:45.01 +25:14:28.5 -- not a known variable star
21:08:52.16 +21:07:14.8 -- not a known variable star
21:09:32.65 +21:06:34.7 -- not a known variable star
21:10:14.10 +20:32:57.9 -- a known variable star
21:10:18.35 +18:34:41.4 -- a known variable star
21:10:18.97 +20:43:43.9 -- not a known variable star
21:10:39.74 +25:07:21.6 -- not a known variable star
21:11:13.92 +24:52:10.9 -- not a known variable star
21:11:13.97 +25:47:34.3 -- not a known variable star
21:12:10.48 +18:49:03.9 -- a known variable star
21:12:23.99 +25:51:59.4 -- not a known variable star
21:14:10.12 +25:04:21.1 -- not a known variable star
21:15:18.91 +25:51:28.1 -- a known variable star
21:15:52.70 +24:31:46.4 -- not a known variable star
21:21:37.33 +25:02:12.5 -- not a known variable star
21:22:45.78 +24:54:54.8 -- not a known variable star
21:23:29.07 +24:21:05.0 -- not a known variable star
21:24:05.96 +22:43:51.7 -- not a known variable star
21:24:29.80 +25:11:31.9 -- not a known variable star
21:27:55.92 +23:10:53.6 -- a known variable star
21:29:46.44 +25:14:40.0 -- not a known variable star
Found 28 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
34 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
###################################################################################
Adding identified Gaia sources from exclusion_list_gaiadr2.txt
exclusion_list_apass.txt NOT FOUND
IS_THIS_TEST_RUN= NO ALLOW_EXCLUSION_LIST_UPDATE= YES
#### Adding the following to the exclusion list ####
20:55:28.91 +18:02:50.7
20:58:55.54 +19:37:57.6
20:59:27.19 +17:55:47.4
21:01:13.10 +18:56:33.0
21:01:17.88 +19:13:32.4
21:02:22.28 +18:09:58.0
21:04:07.68 +22:47:35.5
21:05:03.29 +19:54:14.7
21:05:38.04 +23:25:07.4
21:05:53.72 +19:23:31.0
21:05:55.58 +19:22:45.5
21:06:12.94 +18:35:54.0
21:07:45.21 +24:42:05.6
21:08:45.01 +25:14:28.5
21:08:52.16 +21:07:14.8
21:09:32.65 +21:06:34.7
21:10:14.10 +20:32:57.9
21:10:18.35 +18:34:41.4
21:10:18.97 +20:43:43.9
21:10:39.74 +25:07:21.6
21:11:13.92 +24:52:10.9
21:11:13.97 +25:47:34.3
21:12:10.48 +18:49:03.9
21:12:23.99 +25:51:59.4
21:14:10.12 +25:04:21.1
21:15:18.91 +25:51:28.1
21:15:52.70 +24:31:46.4
21:21:37.33 +25:02:12.5
21:22:45.78 +24:54:54.8
21:23:29.07 +24:21:05.0
21:24:05.96 +22:43:51.7
21:24:29.80 +25:11:31.9
21:27:55.92 +23:10:53.6
21:29:46.44 +25:14:40.0
21:22:40.18 +18:37:09.3
21:11:15.44 +23:28:32.2
21:32:10.99 +22:57:46.2
21:30:04.18 +22:21:29.2
21:09:42.14 +24:10:40.1
21:24:44.24 +18:23:09.3
21:21:59.23 +25:29:41.2
21:08:04.30 +23:43:30.8
21:11:37.90 +25:55:58.6
21:10:57.09 +25:17:25.1
####################################################
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461149.96059851 -observatory V36
00:26:09.34 -00:02:11.3 Mercury (-0.1mag)
03:25:41.22 +19:06:25.4 Venus (-3.9mag)
00:27:40.02 +01:56:35.7 Mars (1.2mag)
07:14:15.99 +22:43:29.6 Jupiter (-2.1mag)
00:30:42.92 +00:58:30.5 Saturn (0.9mag)
03:48:26.18 +19:49:50.0 Uranus (5.8mag)
00:11:17.31 -00:12:33.4 Neptune (7.8mag)
20:33:53.67 -22:52:48.2 Pluto (14.5mag)
03:33:16.74 +23:25:52.8 Moon (-8.8mag)
-rw-r--r-- 1 apache apache 362 Apr 19 06:50 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461149.96059851:
07:14:12.21 +22:43:39.7 Io (5.8mag)
07:14:17.05 +22:43:30.2 Europa (5.9mag)
07:13:57.89 +22:44:10.3 Ganymede (5.4mag)
07:14:28.10 +22:42:55.4 Callisto (6.6mag)
07:17:26.76 +22:29:33.7 Himalia (15.4mag)
07:14:15.41 +22:43:28.7 Thebe (16.2mag)
07:17:42.38 +22:59:53.6 Elara (17.3mag)
07:13:23.02 +23:21:41.3 Pasiphae (17.4mag)
07:22:30.95 +22:41:50.4 Carme (18.5mag)
00:30:33.66 +00:58:50.5 Titan (8.8mag)
00:30:40.55 +00:58:46.2 Rhea (10.1mag)
00:30:17.79 +00:58:06.6 Iapetus (11.5mag)
00:30:37.89 +00:58:58.3 Hyperion (14.8mag)
00:32:16.99 +01:06:55.9 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 19 06:50 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461149.96059851:
15:51:35.44 -18:36:45.0 JWST
16:47:00.81 +46:11:32.5 Chandra
20:36:14.91 +33:50:53.1 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 19 06:50 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461149.96059851 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:53:16.76 -28:59:14.6 13.9mag P/2010 H2 (Vales)
05:09:16.56 -69:30:05.8 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:33:13.73 +31:27:41.9 17.2mag C/2017 K2 (PANSTARRS)
17:30:01.70 +10:57:13.6 17.6mag C/2021 G2 (ATLAS)
23:11:06.02 +29:22:11.6 17.1mag C/2022 E2 (ATLAS)
04:33:17.81 +26:07:49.8 16.0mag C/2022 N2 (PANSTARRS)
09:04:14.75 +32:01:48.2 16.2mag C/2022 QE78 (ATLAS)
08:31:40.11 +00:12:21.9 17.4mag C/2022 R6 (PANSTARRS)
18:52:50.24 +18:49:10.1 17.6mag C/2023 A3 (Tsuchinshan-ATLAS)
15:39:30.28 -11:28:14.3 17.5mag P/2023 B1 (PANSTARRS)
09:06:08.08 -11:20:17.1 17.7mag C/2023 F3 (ATLAS)
21:57:32.84 +63:06:54.2 17.5mag C/2023 H5 (Lemmon)
19:15:59.83 -03:47:47.9 14.1mag C/2023 R1 (PANSTARRS)
21:23:24.53 +86:23:49.1 17.8mag C/2023 X2 (Lemmon)
06:19:41.09 +63:30:06.8 17.2mag C/2024 A1 (ATLAS)
05:20:33.35 +19:23:50.1 11.3mag C/2024 E1 (Wierzchos)
16:16:58.78 +06:57:18.3 17.4mag C/2024 G6 (ATLAS)
20:21:41.58 +16:13:31.7 14.6mag C/2024 J3 (ATLAS)
03:29:30.47 -21:51:58.8 16.3mag C/2024 T5 (ATLAS)
05:19:41.58 +44:26:52.3 17.7mag C/2025 J1 (Borisov)
13:24:35.60 +47:30:43.3 15.3mag C/2025 L1 (ATLAS)
03:30:50.76 -26:45:50.4 17.9mag C/2025 Q3 (ATLAS)
00:22:11.24 +16:48:10.3 8.1mag C/2025 R3 (PANSTARRS)
12:52:37.95 +03:13:03.9 17.4mag C/2025 Y1 (ATLAS)
03:53:24.66 +02:18:35.6 14.2mag C/2026 A1 (MAPS)
00:09:14.85 +37:49:56.6 14.7mag C/2026 B2 (Sun-Gao)
18:49:39.42 -09:31:53.9 11.6mag 10P/Tempel
14:55:34.13 +02:49:47.6 14.3mag 24P/Schaumasse
11:01:56.20 -01:25:08.1 15.7mag 29P/Schwassmann-Wachmann
10:37:34.01 -03:50:13.5 17.0mag 43P/Wolf-Harrington
01:54:02.60 +18:04:25.0 17.3mag 47P/Ashbrook-Jackson
07:17:15.00 +36:15:39.2 17.0mag 63P/Wild
23:33:25.84 -11:02:25.1 15.7mag 65P/Gunn
04:12:36.45 +22:25:05.5 15.9mag 76P/West-Kohoutek-Ikemura
01:13:15.81 +08:54:17.5 14.3mag 78P/Gehrels
23:13:21.83 -08:22:02.2 14.7mag 88P/Howell
02:20:17.29 +21:32:56.6 15.1mag 93P/Lovas
05:01:25.73 +32:27:52.9 16.2mag 123P/West-Hartley
08:32:35.58 +36:45:56.0 16.2mag 124P/Mrkos
02:38:35.61 +14:45:07.5 16.4mag 128P/Shoemaker-Holt
02:54:20.87 +14:54:26.1 17.5mag 131P/Mueller
01:44:31.52 +14:23:02.1 10.5mag 141P/Machholz
01:52:55.26 +06:09:50.2 10.5mag 141P-A/Machholz
00:36:40.47 +01:58:12.7 12.4mag 141P-D/Machholz
02:23:27.86 +07:55:06.2 17.9mag 141P-I/Machholz
01:12:03.94 +00:13:11.8 15.0mag 162P/SidingSpring
14:45:18.46 +00:15:57.4 17.8mag 210P/Christensen
21:48:36.93 -10:37:11.7 17.7mag 218P/LINEAR
17:17:11.19 -13:30:47.1 16.1mag 235P/LINEAR
05:42:00.92 +34:56:37.8 16.8mag 240P/NEAT
07:40:16.69 -04:48:10.1 17.8mag 242P/Spahr
22:25:34.16 -20:02:17.5 17.8mag 260P/McNaught
02:05:19.36 +21:19:35.5 18.0mag 295P/LINEAR
15:41:13.10 +07:12:39.8 17.5mag 391P/Kowalski
07:35:36.17 +21:22:21.0 17.7mag 450P/LONEOS
05:40:58.61 +44:49:48.7 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Apr 19 06:50 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
14:49:14.13 -27:29:20.60 2026-04-16.06 14.03
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:36.30 ASASSN-26co 2026-04-7.15 15.11
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.87 -53:16:33.70 ASASSN-26cc 2026-03-20.08 3.93
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.90 -45:55:38.40 ASASSN-26bt 2026-03-19.05 16.24
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.45 +15:42:15.00 SN2026ehe 2026-03-12.11 -0.29
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.67 -47:26:43.70 ASASSN-26bn 2026-03-10.12 15.2
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.48 -37:49:32.80 ASASSN-26bk 2026-03-2.3 13.11
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.37 +19:58:46.70 ASASSN-26be 2026-02-25.58 14.8
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
-rw-r--r-- 1 apache apache 5.8K Apr 19 06:50 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
-rw-r--r-- 1 apache apache 188K Apr 19 06:50 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
17:37:45.700 +39:48:28.26 AT 2026jjh 2026-04-07.87 20.39
16:35:21.390 +30:27:47.12 AT 2026jjg 2026-04-07.79 20.91
17:02:03.120 +41:30:38.89 AT 2026jjf 2026-04-03.89 21.38
17:08:30.580 +41:56:13.61 AT 2026jje 2026-04-03.89 21.47
16:48:25.780 +33:00:44.35 AT 2026jjd 2026-04-03.85 21.29
16:46:02.450 +30:55:42.15 AT 2026jjc 2026-04-03.80 19.57
16:51:04.120 +44:26:50.06 AT 2026jjb 2026-03-30.84 21.02
12:10:02.030 +43:26:37.06 AT 2026jja 2026-03-28.87 21.46
17:56:59.910 +48:20:04.31 AT 2026jiz 2026-03-27.87 20.99
15:23:12.550 +15:30:01.81 AT 2026jiy 2026-03-27.82 21.09
12:45:41.400 +53:52:15.13 AT 2026jix 2026-03-24.70 20.56
12:05:28.040 +47:18:05.03 AT 2026jiw 2026-03-24.69 20.17
12:49:49.680 +44:27:28.62 AT 2026jiv 2026-03-24.69 21.87
12:17:57.600 +45:03:04.77 AT 2026jiu 2026-03-24.69 20.4
11:39:16.940 +45:15:03.67 AT 2026jit 2026-03-24.66 21.06
14:17:33.100 +43:22:03.41 AT 2026jis 2026-03-22.80 20.74
14:45:33.130 +38:26:13.04 AT 2026jir 2026-03-22.80 21.14
14:42:55.800 +38:18:34.13 AT 2026jiq 2026-03-22.80 21.14
12:43:36.900 +28:13:26.06 AT 2026jip 2026-03-20.69 21.81
13:50:42.590 +38:45:33.09 AT 2026jio 2026-03-29.93 20.87
-rw-r--r-- 1 apache apache 30K Apr 19 06:50 tns_transients_list.txt
