Yes, there are a LARGE number of b_Per images that are not plate-solved and are clogging the queue. They take 3 minutes a piece before they fail three catalogs!
We have removed them from the queue so it should move along better!
Sorry, Ken
PS: Thus the desire to plate-solve before uploading. These happen to be faint and difficult to plate solve by pinpoint off line too! Ugh!
The queue seems to be stalled, I have seen no change in status for the last three days. I uploaded a single file, to test a new setup, but have not seen it in the queue or posted as available. It has been a while since I used VPhot so I could be doing something wrong.
Not sure what you observed but there are no active images in the queue at the moment. There are six inactive images that we will remove manually. It has certainly not been stuck for three days!
I assume that you can try again? Try to describe exactly what happens. You can always email me off-line at kenmenstar@gmail.com for assistance.
Thanks for the quick reply. I tried again a few minutes ago and VPhot worked fine, image was uploaded and processed quickly. I have no idea what I (or my system) was doing wrong earlier. I thought I had followed the Wizard step-by-step instructions, same as I did today. Must be my 83 year old memory :>).
I think the six active images listed may have been what made me think the queue was stuck. It looked to me (erroneously) that, with zero images being processed, the queue was not moving. My mistake, sorry for the confusion. All is well.
I do some of observing through itelescope.net and occassionally an image will get stuck in the processing queue and not get through. There's one there now with the name:-
This happens once in a while. Much of the time it is an itelescope image that doesn't make it through the queue. As far as we can tell, the images often look to be partial/corrupted for some reason.
In any case, they do not plug up the queue. The file name just sits there until we get around to deleting it. So, unless you have some other concern, it is nothing to worry about.
Still hung up. There are hundreds of images in the queue. It is stuck on b_per_bsm_nh2_i_200120.1751_hqa.fts
The queue is now moving again.
A large batch of un-plate-solved images was uploaded by the AAVSOnet, and VPhot was struggling to solve them itself.
George
Phil et al:
Yes, there are a LARGE number of b_Per images that are not plate-solved and are clogging the queue. They take 3 minutes a piece before they fail three catalogs!
We have removed them from the queue so it should move along better!
Sorry, Ken
PS: Thus the desire to plate-solve before uploading. These happen to be faint and difficult to plate solve by pinpoint off line too! Ugh!
The queue seems to be stalled, I have seen no change in status for the last three days. I uploaded a single file, to test a new setup, but have not seen it in the queue or posted as available. It has been a while since I used VPhot so I could be doing something wrong.
Bob:
Not sure what you observed but there are no active images in the queue at the moment. There are six inactive images that we will remove manually. It has certainly not been stuck for three days!
I assume that you can try again? Try to describe exactly what happens. You can always email me off-line at kenmenstar@gmail.com for assistance.
Ken
Ken,
Thanks for the quick reply. I tried again a few minutes ago and VPhot worked fine, image was uploaded and processed quickly. I have no idea what I (or my system) was doing wrong earlier. I thought I had followed the Wizard step-by-step instructions, same as I did today. Must be my 83 year old memory :>).
I think the six active images listed may have been what made me think the queue was stuck. It looked to me (erroneously) that, with zero images being processed, the queue was not moving. My mistake, sorry for the confusion. All is well.
Bob
Hello,
I do some of observing through itelescope.net and occassionally an image will get stuck in the processing queue and not get through. There's one there now with the name:-
calibrated-T30-bsr15-SU Oct-20200218-213545-R-BIN1-W-060-001.fit.zip
Any suggestions about what to do when this happens?
Thanks
Bill Rea
Hi Bill:
This happens once in a while. Much of the time it is an itelescope image that doesn't make it through the queue. As far as we can tell, the images often look to be partial/corrupted for some reason.
In any case, they do not plug up the queue. The file name just sits there until we get around to deleting it. So, unless you have some other concern, it is nothing to worry about.
Ken