We are excited to announce the launch of our new forums! You can access it forums.aavso.org. For questions, please see our blog post. The forums at aavso.org/forum have become read-only.
I'm seriously starting to think that my series of images is responsible for the problem. I tried again to upload the same series and it just went on a loop, re-uploading the same files again and again. And now the service is down again :(
Here is what I mean by looping: when I mouse over the file being uploaded, I can see the file name. Well, I would see the same file name coming back again and again. So, for example, there would be the list of files being uploaded and I mouse over the first one, it quickly switches from say "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T06-40-37_023.fits" to "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T07-04-56_051.fits" (the upload of each individual file is super fast) but after a few seconds, I would see "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T06-40-37_023.fits" being the file being currently uploaded on the top of the list.
Does that make sense? I'm sorry I can't find a better way to describe this "looping" behavior.
I forgot to answer the last question: the second round of upload probably started around 4:20 CT (9:20PM UTC, Saturday October 21st 2023) give or take 10 minutes.
I'm relatively new to VPhot but I've uploaded images taken with the same setup in the past 10 days and everything worked fine. The only difference that I can think off is that these images were taken with the scheduler in Kstars/Ekos while the previous ones were from a sequence ran without using the scheduler. I cannot think of how that could be an issue.
PS: thinking more, one difference is that I started asking Kstar to compute the HFR, so there might be a slight difference in the FITS header with this series.
Should I try to upload my series in small batches? Or give up on these cursed images? They were not super important, I was just checking on RR Cet for fun because it is an easy/rewarding target.
You know that some of the images (67) got to your image list. Of course, I still sit here with some uncertainty even though it is not well founded. I did successfully upload the image you emailed to me.
So, perhaps upload a few at a time (10?) and see what happens. Increase in increments just so the process is not too tedious/annoying! This scheme gives you a chance to see what is happening quickly.
You might do this during the daytime (ET, USA), so that if things go badly, someone who can fix it is awake! ;-)
Service went down while I was loading ~400 images (4.5Mb each) this morning. Did I overload and break the system?
jf
Phil et al:
Yep, George and I know. Working on it.
Ken
Should be good-to-go
Thank you!
Phil
I'm seriously starting to think that my series of images is responsible for the problem. I tried again to upload the same series and it just went on a loop, re-uploading the same files again and again. And now the service is down again :(
Jean-Francois:
What were your images: Target, Date, Time, File Size?
Is this the first time you have ever uploaded images, or these types of images?
When did you start upload? Best estimate?
This will help find out what happened to them.
Ken
PS: Share one to me at kenmenstar@gmail.com
My images are named…
Ken,
My images are named "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T06-19-42_[XXX].fits"
Each image is 4,427 Kb. There were 371 images in the series (is that too much?)
I'll send one to you by email.
jf
JF:
They should work.
Answer my other questions above please.
What do you mean by 'looping'??
Ken
Here is what I mean by looping: when I mouse over the file being uploaded, I can see the file name. Well, I would see the same file name coming back again and again. So, for example, there would be the list of files being uploaded and I mouse over the first one, it quickly switches from say "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T06-40-37_023.fits" to "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T07-04-56_051.fits" (the upload of each individual file is super fast) but after a few seconds, I would see "RR_Cet_Light_JohnsonV_50_secs_2023-10-21T06-40-37_023.fits" being the file being currently uploaded on the top of the list.
Does that make sense? I'm sorry I can't find a better way to describe this "looping" behavior.
jf
I forgot to answer the last question: the second round of upload probably started around 4:20 CT (9:20PM UTC, Saturday October 21st 2023) give or take 10 minutes.
jf
JF:
Have you uploaded similar images to vphot before or uploaded any images before?
Ken
I'm relatively new…
Ken,
I'm relatively new to VPhot but I've uploaded images taken with the same setup in the past 10 days and everything worked fine. The only difference that I can think off is that these images were taken with the scheduler in Kstars/Ekos while the previous ones were from a sequence ran without using the scheduler. I cannot think of how that could be an issue.
PS: thinking more, one difference is that I started asking Kstar to compute the HFR, so there might be a slight difference in the FITS header with this series.
Looks like it's down again 2:10 PM pacific time.
...same error message.
Phil
Tried again ~3:40 PM pacific time. It's working again.
Phil
Fingers crossed.
BTW, if it were not for George Silvis, we would truly be out of luck!
Ken
Should I try to upload my series in small batches? Or give up on these cursed images? They were not super important, I was just checking on RR Cet for fun because it is an easy/rewarding target.
JF:
You know that some of the images (67) got to your image list. Of course, I still sit here with some uncertainty even though it is not well founded. I did successfully upload the image you emailed to me.
So, perhaps upload a few at a time (10?) and see what happens. Increase in increments just so the process is not too tedious/annoying! This scheme gives you a chance to see what is happening quickly.
You might do this during the daytime (ET, USA), so that if things go badly, someone who can fix it is awake! ;-)
Ken
Thanks! I'll try to do this tomorrow, unless Sunday is a bad day for people fixing problems when the server goes down.
And thank you to George Silvis for getting the server back up and running!