I recently crossed the 100 kk credits barrier, still I did not achieve a single publication badge while others collected tons of these (often with only a fraction of work done).
Throughout 2016 & 2017, I almost exclusively processed ADRIAs, PABLOs and Giannis tasks.
Obviously, you guys need to become more productive - publication wise, right?^^
Although... shouldn't at least Gianni be on each of the papers?

Michael.

P.S.: I am not sure what your status is regarding support of AMD cards. In case you need some testing, please let me know. I have 290X and 280X cards.

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.

I recently crossed the 100 kk credits barrier, still I did not achieve a single publication badge while others collected tons of these (often with only a fraction of work done).
Throughout 2016 & 2017, I almost exclusively processed ADRIAs, PABLOs and Giannis tasks.

It can take quite a while until a badge is obtained. The results of a given project we are crunching for need to get published first, only then badges are distributed for it.

See just in my case: I joined in January 2015, and got my first (and so far only one) badge about half a year ago.

So, please be patient :-)

The results of a given project we are crunching for need to get published first, only then badges are distributed for it.

Well, that's of course obvious.

See just in my case: I joined in January 2015, and got my first (and so far only one) badge about half a year ago.

So, please be patient :-)

Don't worry, I will... :-)

I was rather interested in getting to know the criteria for receiving such a publication badge. From what I said above, I conclude that not a single one of all the tasks I was working on throughout 2016 & 2017 was part of a project that got published to date. Is that correct?

Or is it rather so that to get one of these publication badges, the user has to contribute one of the critical tasks that ly at the core of new scientific findings that make up the related paper? I mean, the latter case would be rather an unfair situation as the distribution of such tasks is purely governed by chance while all of the tasks in one MD simulation project batch are equally important to check on, right?

Michael.

P.S.: By the way, I am quite enthusiastic about the presence of these publication badges. I do not think there is any distributed computing project out there that gives such a nicely detailed feedback on what the users actually contributed to. Very good idea that others should adopt, too!

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.

Any information on this?

Michael.

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.

Any information on this?

I hope that anyone else can give us more details -

Look in the news area for threads / posts like this one.

Badges on this project are awarded when the scientific research is complete, analysed, written up and published - which in the peer-reviewed scientific publishing world takes a significant time, say a couple of years minimum.

From what I said above, I conclude that not a single one of all the tasks I was working on throughout 2016 & 2017 was part of a project that got published to date. Is that correct?

Yes, and it applies to all crunchers, not just you. Take a look at my badges, I have 2 from 2016, but the computation for these publications finished long ago. Publishing the results can take more than a year or two.

Or is it rather so that to get one of these publication badges, the user has to contribute one of the critical tasks that lay at the core of new scientific findings that make up the related paper?

That is false. There's no distinction between tasks of a given batch regarding publication badges. There are no "critical tasks" in this project. A given batch contribute to a specific research, e.g. publication; there could be multiple ongoing research simultaneously, but sometimes a given batch is prioritized due to publication deadlines, etc.

I mean, the latter case would be rather an unfair situation as the distribution of such tasks is purely governed by chance...

Yes, it would be "unfair" but there are no "such tasks". Awarding publication badges is not lottery.

... while all of the tasks in one MD simulation project batch are equally important to check on, right?

Right. These simulations take 8~80 hours on the fastest GPUs (GTX 1080Ti) per trajectory, and there could be hundreds or even thousands of trajectories to compute for reliable statistics.

Thank you. Things got much clearer now.

Michael.

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.