failed to get light_curve data

Also have this problem
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1050398.json
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1077853.json
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1055062.json

Not seen many lately, but here you have a few others:
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1061444.json
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1066858.json
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1122462.json
failed to get light_curve datahttp://s3.amazonaws.com/ph-stars-production/APHF1055062.json

> [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> Hi,
> Anyone else seeing any? If there is a large amount I'll send in a bug report to the development team.
> Cheers,
> ~Meg
>
After a hiatus from classifying. I've begun again, but after only a few days these are halting my efforts, causing much frustration. Can you fix them so I can continue?
failed to get light_curve data
http://s3.amazonaws.com/ph-stars-production/APHF1115129.json
http://s3.amazonaws.com/ph-stars-production/APHF1137452.json
http://s3.amazonaws.com/ph-stars-production/APHF1132136.json
I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

> [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > Hi,
> > Anyone else seeing any? If there is a large amount I'll send in a bug report to the development team.
> > Cheers,
> > ~Meg
> >
> After a hiatus from classifying. I've begun again, but after only a few days these are halting my efforts, causing much frustration. Can you fix them so I can continue?
> failed to get light_curve data
> http://s3.amazonaws.com/ph-stars-production/APHF1115129.json
> http://s3.amazonaws.com/ph-stars-production/APHF1137452.json
> http://s3.amazonaws.com/ph-stars-production/APHF1132136.json
> I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.
>
I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.
Cheers,
~Meg

I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.

> [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > Hi,
> > > Anyone else seeing any? If there is a large amount I'll send in a bug report to the development team.
> > > Cheers,
> > > ~Meg
> > >
> > After a hiatus from classifying. I've begun again, but after only a few days these are halting my efforts, causing much frustration. Can you fix them so I can continue?
> > failed to get light_curve data
> > http://s3.amazonaws.com/ph-stars-production/APHF1115129.json
> > http://s3.amazonaws.com/ph-stars-production/APHF1137452.json
> > http://s3.amazonaws.com/ph-stars-production/APHF1132136.json
> > I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.
> >
> I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.
> Cheers,
> ~Meg
>
Hi Meg,
Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.
It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:
http://s3.amazonaws.com/ph-stars-production/APHF1107468.json - good.
http://s3.amazonaws.com/ph-stars-production/APHF1125318.json - Access Denied.
If you want to forward this to the development team to come up with a solution, it would be much appreciated.

I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.

Cheers,

~Meg

Hi Meg,

Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.

It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:

> [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > > [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > > Hi,
> > > > Anyone else seeing any? If there is a large amount I'll send in a bug report to the development team.
> > > > Cheers,
> > > > ~Meg
> > > >
> > > After a hiatus from classifying. I've begun again, but after only a few days these are halting my efforts, causing much frustration. Can you fix them so I can continue?
> > > failed to get light_curve data
> > > http://s3.amazonaws.com/ph-stars-production/APHF1115129.json
> > > http://s3.amazonaws.com/ph-stars-production/APHF1137452.json
> > > http://s3.amazonaws.com/ph-stars-production/APHF1132136.json
> > > I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.
> > >
> > I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.
> > Cheers,
> > ~Meg
> >
> Hi Meg,
> Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.
> It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:
> http://s3.amazonaws.com/ph-stars-production/APHF1107468.json - good.
> http://s3.amazonaws.com/ph-stars-production/APHF1125318.json - Access Denied.
> If you want to forward this to the development team to come up with a solution, it would be much appreciated.
>
Thanks. I've forwarded the entire thread to the development team in the support ticket.
One thing i'm sure you're aware is that the Zooniverse doesn't have the man power of a large tech company. They do amazing things with a small number of dedicated web developers. it take time for the development team to get to the problem. It's a handful of people managing 25+ projects and building new ones, so especially close to the launches of new projects and busier times it can take some time to fix and issue like this. I've reported it, and emailed the development team who are mostly based in Chicago. We'll have to wait and see if they can solve the issue today, but they will get to it.It may take some days, but I'll follow-up later this week. Please keep posting if the issue continues to happen, and again apologies for the frustration and thank you for your patience.
~Meg

I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.

Cheers,

~Meg

Hi Meg,

Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.

It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:

If you want to forward this to the development team to come up with a solution, it would be much appreciated.

Thanks. I've forwarded the entire thread to the development team in the support ticket.

One thing i'm sure you're aware is that the Zooniverse doesn't have the man power of a large tech company. They do amazing things with a small number of dedicated web developers. it take time for the development team to get to the problem. It's a handful of people managing 25+ projects and building new ones, so especially close to the launches of new projects and busier times it can take some time to fix and issue like this. I've reported it, and emailed the development team who are mostly based in Chicago. We'll have to wait and see if they can solve the issue today, but they will get to it.It may take some days, but I'll follow-up later this week. Please keep posting if the issue continues to happen, and again apologies for the frustration and thank you for your patience.

> [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > > > [crazyllama2](/users/4f19c963de07d859f105017c "crazyllama2"):
> > > > > > [mschwamb](/users/4d0985784478970f86000001 "mschwamb"):
> > > > > Hi,
> > > > > Anyone else seeing any? If there is a large amount I'll send in a bug report to the development team.
> > > > > Cheers,
> > > > > ~Meg
> > > > >
> > > > After a hiatus from classifying. I've begun again, but after only a few days these are halting my efforts, causing much frustration. Can you fix them so I can continue?
> > > > failed to get light_curve data
> > > > http://s3.amazonaws.com/ph-stars-production/APHF1115129.json
> > > > http://s3.amazonaws.com/ph-stars-production/APHF1137452.json
> > > > http://s3.amazonaws.com/ph-stars-production/APHF1132136.json
> > > > I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.
> > > >
> > > I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.
> > > Cheers,
> > > ~Meg
> > >
> > Hi Meg,
> > Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.
> > It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:
> > http://s3.amazonaws.com/ph-stars-production/APHF1107468.json - good.
> > http://s3.amazonaws.com/ph-stars-production/APHF1125318.json - Access Denied.
> > If you want to forward this to the development team to come up with a solution, it would be much appreciated.
> >
> Thanks. I've forwarded the entire thread to the development team in the support ticket.
> One thing i'm sure you're aware is that the Zooniverse doesn't have the man power of a large tech company. They do amazing things with a small number of dedicated web developers. it take time for the development team to get to the problem. It's a handful of people managing 25+ projects and building new ones, so especially close to the launches of new projects and busier times it can take some time to fix and issue like this. I've reported it, and emailed the development team who are mostly based in Chicago. We'll have to wait and see if they can solve the issue today, but they will get to it.It may take some days, but I'll follow-up later this week. Please keep posting if the issue continues to happen, and again apologies for the frustration and thank you for your patience.
> ~Meg
>
Looking forward to it!

I almost abandoned planethunters out of frustration. Aren't you concerned planethunters is going to loose volunteers because of this? I'm sure it will continue to cross my mind if these keep popping up. The Kepler team is getting such amazing results, it'd be sad if this held things up.

I'm sorry this is happening, and I apologize for the frustration. I'm not on the development team, so I don't have access or even know how to fix the issue. The best I can do is contact the Zooniverse development team and let them know about the issue is still happening. I've sent them an email.

Cheers,

~Meg

Hi Meg,

Thanks for replying. I've worked both in development and on helpdesks and, as you may know from experience, only a very, very small number of users report problems. The rest will wait for it be fixed, and if that doesn't happen, they abandon the site. That's the basis for my concern that planethunters volunteers could be abandoning it. In just the last few days I've been classifying I've come up with eight 'failed' light_curves. Either I'm extremely unlucky, or this is an indication that it is a common problem that may be driving volunteers away.

It should be easy enough for the developers to test/check that the link is valid. Manually opening a good link and a failed link from my PC shows this to be the case:

If you want to forward this to the development team to come up with a solution, it would be much appreciated.

Thanks. I've forwarded the entire thread to the development team in the support ticket.

One thing i'm sure you're aware is that the Zooniverse doesn't have the man power of a large tech company. They do amazing things with a small number of dedicated web developers. it take time for the development team to get to the problem. It's a handful of people managing 25+ projects and building new ones, so especially close to the launches of new projects and busier times it can take some time to fix and issue like this. I've reported it, and emailed the development team who are mostly based in Chicago. We'll have to wait and see if they can solve the issue today, but they will get to it.It may take some days, but I'll follow-up later this week. Please keep posting if the issue continues to happen, and again apologies for the frustration and thank you for your patience.