I'm wondering how I just got the einsteinbinary_BRP4G_1.56_windows_x86_64__BRP4G-Beta-cuda55.exe application for Task 257944943 if the 64 bit version is supposedly deprecated.
While your post states "just got" that task was actually sent to you over ten hours before the time stamp of your post, at 11 Oct 2016, 8:02:48 UTC. That was well before the end of the period in which such units were sent out today.
Thanks for the comment, Zalster. I thought that's what I should do but wanted to check-in with the forum firsthand. I see that I have picked up the new 1.57 app on the other machines and some new BRP4G CUDA55 x86 32 bit tasks accordingly. Not sure at all why the server sent me the deprecated 64 bit app on this machine. I had reset the project on all machines last week I think to clear out the systems since they still had BRP5 and BRP6 applications in the directories. I wanted to start a clean slate with the BRP4G GPU app since that is all that is left now. The 1.57 app STILL is not showing on the Applications page.
Well, I don't sit on top of the machines checking in every couple of minutes. It was a case of "just got" since I saw it was issued today. Plus, I saw the message in this thread the 64 bit app was deprecated and wondered how I received it anyway. I didn't have the app prior to today.
No comment from anyone so far about my deprecated app received today. I'm concerned because when this app was issued for BRP6, EVERY task errored out within seconds of starting. Should I just delete the new task assigned this deprecated app?
Keith cancel any v1.56 work units.
Hopefully you will start to get the v1.57 soon
Zalster, (and others here),
Exeter, (Win XP Pro x64 with EVGA GTX-760), is ONLY crunching 1.52 BRP4G Beta Units right now... NO 1.57's in sight... Andromeda, (MAC OS and two GTX-750TI SC cards), is now crunching 1.56 BRP4G Beta Units now... AGAIN, NO 1.57's in sight.
The 1.52 Units have been going on for quite some time now. At least a couple of weeks. No issues to report with 1.52.
Andromeda has only begun crunching Einstein, again, today. The 1.56 Units seem to be validating. Should I continue, or abort and wait for 1.57???
Well, I don't sit on top of the machines checking in every couple of minutes.
Nobody said you had to, or even that you should.
Keith Myers wrote:
It was a case of "just got" since I saw it was issued today.
If you'd looked more closely at your tasks list in BOINC Manager you could have seen the precise time today.
Keith Myers wrote:
Plus, I saw the message in this thread the 64 bit app was deprecated and wondered how I received it anyway. I didn't have the app prior to today.
Of course you didn't - nobody did. It was just recently issued, the problem was found quickly and so the faulty app was immediately deprecated. You got your task in that small window of opportunity. Archae86 explained this quite well. So, instead of just thanking him for the explanation, you send a somewhat rude reply. Considering that it takes a bit of effort these days to research another user's task list, I'm sure a simple 'thank you' would have been more appreciated.
For now I issued the BRP4G Cuda 5.5 app versions as "Beta", as these were on BRP6, so you can decide yourself whether to run these or not.
Is there a cuda 5.5 app version for Linux or is it just Windows only? I'm only getting the cuda 3.2 version (v1.52 BRP4G-Beta-opencl-ati) at the moment. What happens if there are two beta apps, 3.2 and 5.5? How does the scheduler choose which one to use?
Hmm.. I hadn't realized he was running OSX with the arecibo beta 55. It does appear that those are finishing, which would point to a problem specifically to windows version.
Sorry about that TL. Hopefully you have not aborted those work units, which looking at your computers it appears you have not. Keep them and let them run. Maybe they can figure out why with your validated work units.
tolafoph wrote:Hi, I just
)
My 980Tis are running 2 at a time and have similiar times. Have to test with 3 and 4 to see what those times look like.
Zalster
Keith Myers wrote:I'm
)
While your post states "just got" that task was actually sent to you over ten hours before the time stamp of your post, at 11 Oct 2016, 8:02:48 UTC. That was well before the end of the period in which such units were sent out today.
Nothing special.
Thanks for the comment,
)
Thanks for the comment, Zalster. I thought that's what I should do but wanted to check-in with the forum firsthand. I see that I have picked up the new 1.57 app on the other machines and some new BRP4G CUDA55 x86 32 bit tasks accordingly. Not sure at all why the server sent me the deprecated 64 bit app on this machine. I had reset the project on all machines last week I think to clear out the systems since they still had BRP5 and BRP6 applications in the directories. I wanted to start a clean slate with the BRP4G GPU app since that is all that is left now. The 1.57 app STILL is not showing on the Applications page.
Well, I don't sit on top of
)
Well, I don't sit on top of the machines checking in every couple of minutes. It was a case of "just got" since I saw it was issued today. Plus, I saw the message in this thread the 64 bit app was deprecated and wondered how I received it anyway. I didn't have the app prior to today.
Zalster wrote:Keith Myers
)
Zalster, (and others here),
Exeter, (Win XP Pro x64 with EVGA GTX-760), is ONLY crunching 1.52 BRP4G Beta Units right now... NO 1.57's in sight... Andromeda, (MAC OS and two GTX-750TI SC cards), is now crunching 1.56 BRP4G Beta Units now... AGAIN, NO 1.57's in sight.
The 1.52 Units have been going on for quite some time now. At least a couple of weeks. No issues to report with 1.52.
Andromeda has only begun crunching Einstein, again, today. The 1.56 Units seem to be validating. Should I continue, or abort and wait for 1.57???
TL
TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join SETI Refugees
Keith Myers wrote:Well, I
)
Nobody said you had to, or even that you should.
If you'd looked more closely at your tasks list in BOINC Manager you could have seen the precise time today.
Of course you didn't - nobody did. It was just recently issued, the problem was found quickly and so the faulty app was immediately deprecated. You got your task in that small window of opportunity. Archae86 explained this quite well. So, instead of just thanking him for the explanation, you send a somewhat rude reply. Considering that it takes a bit of effort these days to research another user's task list, I'm sure a simple 'thank you' would have been more appreciated.
Cheers,
Gary.
TL, Abort any v1.56 and
)
TL,
Abort any v1.56 and await v1.57 to be sent to you.
Zalster
Bernd Machenschalk wrote:For
)
Is there a cuda 5.5 app version for Linux or is it just Windows only? I'm only getting the cuda 3.2 version (v1.52 BRP4G-Beta-opencl-ati) at the moment. What happens if there are two beta apps, 3.2 and 5.5? How does the scheduler choose which one to use?
Cheers,
Gary.
Zalster wrote:Abort any v1.56
)
Is the problem with 1.56 just specific to Windows?
Maybe there wont be a need for a 1.57 app for OS X??
Cheers,
Gary.
Hmm.. I hadn't realized he
)
Hmm.. I hadn't realized he was running OSX with the arecibo beta 55. It does appear that those are finishing, which would point to a problem specifically to windows version.
Sorry about that TL. Hopefully you have not aborted those work units, which looking at your computers it appears you have not. Keep them and let them run. Maybe they can figure out why with your validated work units.