1) Message boards : GPUGRID CAFE : Schizophrenia information (Message 36959)
Posted 63 days ago by Profile robertmiles
Uncovering clues to the genetic cause of schizophrenia
http://www.eurekalert.org/pub_releases/2014-05/cumc-uct052814.php
2) Message boards : News : WU: BI_3 (Message 36869)
Posted 74 days ago by Profile robertmiles
Finally, some workunits I can recommend on the diabetes newsgroups.

Thank you!
3) Message boards : News : WU: A2AR (Message 35998)
Posted 125 days ago by Profile robertmiles
A big hi to all the users! I'm currently undergoing my master thesis in the lab and I'll very proud to participate in this fantastic community for the first time by sending some simulations to gpugrid.

You will identify them with the ID A2AR, which stands for A2A adenosine receptor. It is a membrane protein from to a huge family called GPCRs that is key on neurodegenerative diseases such as Parkinson and therefore an important target of drug development. With these simulations we will try to prove the affinity of a couple of known ligands in silico.


I've seen some articles elsewhere indicating that it may be significant whether certain brain proteins have an affinity for aluminum, copper or iron that is not already bound to some other protein, so are those among the known ligands you are testing? If not, do the GPUGRID software even allow testing them for affinity?

The human brain's natural defense against Alzheimer's is a small protein that also regulates the level of free copper ions inside the brain. Iron is known to bind to damaged tissues in the brain, and appears likely to be the cause of the brain damage in Parkinson's. Aluminum in known to bind to certain areas of the brain during a later stage of Alzheimer's - the same areas that are damaged in that stage.

FSU Scientist Links Iron Imbalance To Parkinson's Disease
http://www.sciencedaily.com/releases/2004/10/041013084413.htm
4) Message boards : Graphics cards (GPUs) : GTX Titan Black announced (Message 35131)
Posted 164 days ago by Profile robertmiles
Nvidia lets loose GeForce GTX Titan Black
http://hexus.net/tech/news/graphics/66181-nvidia-lets-loose-geforce-gtx-titan-black/

When will you know if your workunits works on this model? When someone buys one and tries your workunits on it?

It appears to have a few more usable cores and a faster memory clock than the GTX Titan, but not much difference otherwise.
5) Message boards : Number crunching : Process exited with code 159 (0x9f, -97) (Message 34192)
Posted 234 days ago by Profile robertmiles
Errors with 8.14:

Error 255:

http://www.gpugrid.net/result.php?resultid=7530621
The extended attributes are inconsistent.

http://www.gpugrid.net/result.php?resultid=7530360
The extended attributes are inconsistent.


Error -97:

http://www.gpugrid.net/result.php?resultid=7528287
(unknown error) - exit code -97 (0xffffff9f)
The simulation has become unstable. Terminating to avoid lock-up (1)
The simulation has become unstable. Terminating to avoid lock-up (1)


GPUGRID now set to no new tasks on this computer, probably until
something relevant is updated. Tasks still running on my other
computer, with a slower GPU.

GTX 560, at stock speeds.
6) Message boards : Number crunching : NOELIA tasks - when suspended or exited, often crash drivers (Message 33993)
Posted 251 days ago by Profile robertmiles
some update that looks likely to fix this problem.


??? explain please ::grabs popcorn::


I'm waiting for an Nvidia driver release, a BOINC release, or a GPUGRID application release before I enable GPUGRID workunits on that computer again.


I've now installed BOINC 7.2.28 on the computer with the problem. I tried installing the 331.82 Nvidia driver a few times; it never installed correctly. I'm back to the 331.65 driver.

GPUGRID workunits have run properly on that computer for the last few days, with no more driver crashes.


This wasn't enough to fully fix the problem; however, the driver crashes no longer crash Windows also. I'll watch to see if the new crashes cause enough problems that I need to put GPUGRID back in No new tasks on that computer.
7) Message boards : Number crunching : NOELIA tasks - when suspended or exited, often crash drivers (Message 33977)
Posted 253 days ago by Profile robertmiles
some update that looks likely to fix this problem.


??? explain please ::grabs popcorn::


I'm waiting for an Nvidia driver release, a BOINC release, or a GPUGRID application release before I enable GPUGRID workunits on that computer again.


I've now installed BOINC 7.2.28 on the computer with the problem. I tried installing the 331.82 Nvidia driver a few times; it never installed correctly. I'm back to the 331.65 driver.

GPUGRID workunits have run properly on that computer for the last few days, with no more driver crashes.
8) Message boards : News : WU: NOELIA_INS1P (Message 33975)
Posted 253 days ago by Profile robertmiles
The claim is that errors can be caused by "not having enough voltage" or by "having too high of a temperature".

Do we have conclusive proof of this claim? Or is it more of a generalization based on experience? I'm struggling to understand how voltage or temperature can have any effect on error % rates, and would appreciate some guidance.

All semiconductor manufacturers create yield curves for their production lots. They show how much voltage/current it takes to achieve a given speed. In general, the more power you supply to the chip, the faster it can be clocked. Of course, it also gets hotter, which can eventually destroy the chip. That is why a power limit is also specified (e.g., 95 watts for some Intel CPUs, etc.). But the chips vary, with some being able to run fast at lower power, and some requiring higher power to achieve the same speeds. You can get errors due to a variety of reasons, with temperature being just one. But I have seen errors even below 70 C, so some other limitation may get you first.


[snip]

MrS


Something I've read that seems relevant to this explanation:

Today's CPU chips are approaching the lower limit of the voltages at which the transistors work properly. Therefore, the power used by each CPU core can't get much lower. Instead, the companies are increasing the total speed by putting more CPU cores in each CPU package. Intel in also using a different method - hyperthreading. This method gives each CPU core two sets of registers, so that while the CPU is waiting for memory operations for the program running with one of these sets, the CPU can use the other set to run the other program using that set. This makes the CPU act as if it had twice as many CPU cores as it actually does.

If a programmer want to use more than one of these CPU cores at the same time for the same program, that programmer must study parallel programming first, in order to handle the communications between the different CPU cores properly.

I used to be an electronic engineer, specializing in logic simulation, often including timing analysis.
9) Message boards : Number crunching : NOELIA tasks - when suspended or exited, often crash drivers (Message 33785)
Posted 269 days ago by Profile robertmiles
some update that looks likely to fix this problem.


??? explain please ::grabs popcorn::


I'm waiting for an Nvidia driver release, a BOINC release, or a GPUGRID application release before I enable GPUGRID workunits on that computer again.
10) Message boards : Number crunching : NOELIA tasks - when suspended or exited, often crash drivers (Message 33686)
Posted 275 days ago by Profile robertmiles
Crashes less frequent with the 331.65 driver, but not gone. GPU workunits for other BOINC projects still running properly.

Another -97 error:
http://www.gpugrid.net/result.php?resultid=7410463

Another repeated Windows crashes until I aborted the workunit:
http://www.gpugrid.net/result.php?resultid=7410730

That computer now has GPUGRID on No new tasks. I plan to leave it there until I install some update that looks likely to fix this problem.

My other computer (with a slower GPU, Windows 7, and probably an older driver) still has GPUGRID enabled since it isn't showing showing this problem.


Next 10