• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

FAD Questions..

Mellman

Diamond Member
as the topic says, what exactly is a "hit" in a FAD work unit? Some things get like 30 hits...and i have two machines right now that have 350+ hits.

Also are there different sized work units like there are in F@H. Some of my machines processed 5 over the weekend, while others only did 1-2, all identical machines. Just thought this was sortof odd. In any case thanks for the help!
 
Ok thats what i was thinking too. Now a followup question to that would be...are points awarded per hit? Just curious how this whole scoring thing works 🙂
 
You may want to check out:

http://www.find-a-drug.org/faq.html

They say Points are:
With the release of 1.21, we are currently experimenting with a means of weighting the CPU time contributed to the project based on the speed of the CPU and (for Windows 9X) the fraction of time spent running THINK. For an average CPU (1.2MHz) this will result in approximately 100 points per CPU hour.

They say Hits are:
This is a molecule which is predicted to interact or bind with the protein receptor.
 
"Hits" or NO "Hits" have no correlation to points awarded. Points are awarded based on CPU Rating times CPU Duration (time spent processing -- not wall clock time).

Jobs with low hits may be the most important because these jobs narrow down the number of candidates. Equally important is the fact that once a likely candidate has been found (i.e., "Hits" indicate it will likely bind to the protein receptor), subsequent queries may be be further narrowing down the candidates trying to exclude those that bind with "friendly" protein receptors (i.e., eliminating those candidates with likely major side effects). For those queries, low hits are desirable.

Now Hits and Points have do direct correlation but it is true that there is somewhat more processing to perform when a Hit is found so that will result in more CPU Time spent processing the Job and hence, the total points tend to be slightly higher for Jobs with higher Hit rates.

It is also true that some protein queries just take longer to process than others due to the complexity or flexibility of the receptor site or the compound being processed. Some queries have averaged 10-15 minutes a job or less while others have averaged days to a week or more per Job.

Hope this is helpful.

BTW ... I've had several (as in a dozen or two) that are in the 700-1000 range as far as Hits go! 350 is not an extraordinary number of hits.
 
thanks for all the help guys! I guess it looks like a projected 70,000/week points for me, hopefully i'll get it higher!
 
i think that people should be rewarded for having work with higher amounts of hits....i mean the ultimate goal is to find a cure for these issues but i think those that are processing the work with higher hits should be rewarded accordingly in the stats. it should be a combination of gflops and hits. but thats just my opinion.
 
Please read my post ...

Jobs with low hits may be as important or more important than jobs with high hits. The reason, some are testing "good" proteins and the goal is not to get any hits ... i.e., no harmful side effects. Actually, when one is looking for a cure, 1 very good hit may be worth 1,000 so-so hits. This is a screening process. The more drugs that are ruled out, the less work to be done in the labs.

Hits are luck of the draw ... a lottery of sorts. Some get high hit jobs, some don't. I run them all.
 
Back
Top