WU availability status for Gridcoin whitelisted projectssteemCreated with Sketch.

in gridcoin •  last year

I regularly read messages on BOINC forums about projects having limited or no work availability, affecting equal earnings across users and projects for work being delivered in Team Gridcoin. There are ongoing developments to resolve this issue and @guk has just launched another proposal on Steemit to address this.

To provide better visibility to the community, I thought of building a dashboard with all whitelisted projects and their WU availability.

My initial thought was to look at the amount of work-units available in the server queue but this didn’t really provide a good measure because some projects can generate very quickly new WUs and as such the WUs in queue can be low.

As second option, I checked the credits awarded in the last 7 days versus the average over the last 40 days. The idea is when projects are awarding a constant amount of credit, it also means they are sending WU’s to BOINC clients. This means when the amount of credits awarded in the last 7 days are in-line with the 40-days average than everything is fine but when the credits awarded in the last 7 days are substantially lower than the 40-days average, I would consider this a problem.

The table below is my first attempt with all whitelisted projects. There are 4 projects with problems but only 2 are significant enough to monitor closely: [email protected] and Sourcefinder. I hope this overview can contribute in the discussions and help structure the decision process of keeping projects whitelisted.

Looking forward to your comments.

Sources: BOINCStats


Thanks for reading. Follow me for more BOINC & Gridcoin related articles.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Boinc project provide xml feeds with such info iirc

This post has received gratitude of 0.91 % from @jout thanks to: @parejan.

·

You got a 0.08% upvote from @postpromoter courtesy of @jout!

I think it is a very good idea, simple but efficient... so we can be informed regularly about the situation of the projects... I would do it weekly and not daily...

·

Fuly agree, I would consider a weekly update to be sufficient as well and if there is an interest I'll post them.

·
·

I think the conditions should be automatically evaluated daily, or better twice a day. If you are doing it by hand, then yeah, however often you feel comfortable.
But post it only once a week.

This type of data would work perfectly with the whitelist process proposal, It could replace the following from my proposal:

Whitelisting & Re-Whitelisting:

  • Has had no periods greater than 48 hours without any work within the last 7 days

    replaced by something like

  • Projects "Parejan" score is Green.

Greylisting:

  • The project is offline for a period greater than 5 consecutive days

  • The project has an empty work-queue for a period greater than 5 consecutive days

  • The project has an empty work-queue for 7 days in any consecutive 14 day period

    replaced by something like

  • Projects "Parejan" score is Red.

In order to decentralise and help automate project whitelisting I wonder if such a calculation could be built into the Superblock?

·

This is really good @guk, we need to integrate it in the Superblock based on a set formula.
Red and green still need to be defined because empty doesn't mean 0 to me.

For example:
Red = below 10% of the last 40-days average
Green = above 10% of the last 40-days average
Amber = will not be used

·
·

Are you talking Fuzzy logic here?

·
·
·

No, I think we can stick to Boolean logic based on set number of variables. I don’t know how much intelligence, including external feeds, we can add to blockchains so the proposal could be too complex to implement. Do you have any views on this?

·
·
·
·

I would rather not integrate this logic into the wallet. Maybe feed the data into the "neural" network, once it is in state that can actually be edited.
Or better yet, Have the script calculating grey-list status somewhere and just notify Quez to send appropriate transaction.

·
·
·
·
·

That makes sense to build a script to calculate grey-list status seperately. I'll keep it on the list of things to take forward.

·

After you refine this idea, pleas post it to Gridcoin Tasks.

This should be automated and put on a web. Maybe Startail (@sc-steemit) can help you.

·

I agree, if @sc-steemit could integrate it in Gridcoinstats that would be the best place.

Great idea. Thanks for that. Maybe you can do this once a week?

·

No problem, I can do this until we have it in the superblock as mentioned in @guk comment.

Also a problem is, that if the credit output that day dropped below, it it is already too late to greylist.