Yes, you are correct. Unfortunately, BSM_S' scope computer has failed. If you check the thumbnail files you will see that we have not had images from BSM_S recently. A replacement component is being sent to BSM_Berry. The BSM_S computer replacement is in work. We'll keep you updated.
I just got a batch of "U Mon" images in my vPhot account, but they're clearly mislabeled. It appears that the target was instead S Dor (it's a much more interesting field, at least!). Not sure where the hiccup occurred, but the affected images were from 2019-01-24 and 2019-01-31 (2019-01-24 17:38:59, for example).
Speaking of U Mon, it's was saturated in some V images despite the short 15s exposure (the focus was very sharp, with most of the light in just two pixels). Scintillation will start to be a problem, but perhaps 12s or 10s would still be reasonable. That would at least yield usable data at maximum light.
I just got another two nights of data of "U Mon" in VPhot but they're also of the S Dor field. I've not gotten any U Mon images in several weeks - maybe they're labeled S Dor and going to someone else :).
Yes, you are correct. Unfortunately, BSM_S' scope computer has failed. If you check the thumbnail files you will see that we have not had images from BSM_S recently. A replacement component is being sent to BSM_Berry. The BSM_S computer replacement is in work. We'll keep you updated.
Mike
I just got a batch of "U Mon" images in my vPhot account, but they're clearly mislabeled. It appears that the target was instead S Dor (it's a much more interesting field, at least!). Not sure where the hiccup occurred, but the affected images were from 2019-01-24 and 2019-01-31 (2019-01-24 17:38:59, for example).
Speaking of U Mon, it's was saturated in some V images despite the short 15s exposure (the focus was very sharp, with most of the light in just two pixels). Scintillation will start to be a problem, but perhaps 12s or 10s would still be reasonable. That would at least yield usable data at maximum light.
Shawn (DKS)
Shawn,
Thanks for the heads up. We'll take a look at what went wrong with S Dor. I'll change the V mag exposures to 12 seconds to see if that works better.
Thanks again,
Mike
Mike
I corrected a screwup on my part, I had the plan call out the S Dor coordinates in the U Mon plan :-(
I modified the V mag exposure to 12 seconds. If that works now fine, if we need to reduce it to 10 seconds just let me know.
Sorry, thanks for your patience,
Mike
Hi Mike,
I just got another two nights of data of "U Mon" in VPhot but they're also of the S Dor field. I've not gotten any U Mon images in several weeks - maybe they're labeled S Dor and going to someone else :).
Shawn (DKS)
Hi Shawn,
I confirmed that the U Mon image ( u_mon_bsm_s_b_190301_0322 (3).fts) is of the S Dor field.
The VPhot image says the center of the image is 05:18:09.36 -69:15:48.75 which VSX confirms is the
coordinates close to S Dor:
05 18 14.35 -69 15 01.1
However, the plan in BSM_S requests these coordinates for U Mon:
#target
hh
mm
ss.ss
dd
mm
ss.s
U_Mon
7
30
47.47
-9
46
36.8
So whats going on? I'll need to review the scope computer ACP scheduler to bore down further. I'll need to gain access so please bear with us.
Thanks for your patience.
Mike