Posts by Yavanius

1) (Message 8294)
Posted 18 days ago by Yavanius
Post:
Are older Macs no longer supported? I have a couple of Core2 Duo minis that have been been successfully running for quite some time and within the last few days they are reporting that "Project has no tasks available". Update and reset do not fix the problem. Nor does a reboot help at all. Does anyone have any suggestions or is it time to retire the machines or find a different project that still uses the old hardware? One of the minis is running Snow Leopard and the other is running Lion. BOINC version is 7.6.22.



My Tab S6 Lite is currently doing the same thing (Android though). My phone still seems to be getting work though. There's plenty of work and I don't see any error messages in the log.
2) (Message 5491)
Posted 14 Sep 2017 by Yavanius
Post:
You an also check your Transfers tab. If there isn't anything listed there, then your work was uploaded. :)

It's a good idea to check it on occasion just in case you have any pending transfers due to some issue (your internet hiccuped, somebody hit the nice red button in front of the server that says 'Don't Push', BOINC didn't establish a proper connection, etc).
3) (Message 5124)
Posted 5 Feb 2017 by Yavanius
Post:

At least: we have no visualisation of the operations so its a bit boring!


Well, learn to program and you can create a visualization component for it. ;)

I don't that anybody in the community ever created a screensaver for BOINC, but it's been done for the core clients... so you, PFLIEGER, could be the first!


(And a # of projects DON'T have visualizations. Be nice if they did, but that takes a lot of time. Remember, these folks aren't JUST doing these projects. Many have professional commitments outside of the project too.)
4) (Message 5123)
Posted 5 Feb 2017 by Yavanius
Post:
The example of this can be shown in "Cosmology@Home" individual and team points status updated on a daily basis.


Cosmology@home had a LONG period where there was no contact by the head architect of the project and no updates to the apps.

At least Kyong is still visible and not gone incognito.

And, hey, at least there are some cool asteroid badges. ;)
5) (Message 4569)
Posted 15 Jul 2015 by Yavanius
Post:
Thanks for answering. Yes it is running Android. The only project that sends it WU's at the moment is Collatz. So, if they can manage it why can't other projects?


If you really want it that bad, learn to code. ;) I don't say to be spiteful, but that's really the best way to get it (unless you know someone who you can get to do it).

Even SETI@home with multiple applications still has to balance the working on the clients. In fact, some of the clients you use now evolved from 3rd party optimized clients. It still doesn't support every possible configuration out there.

There's two things that need to happen:

1. You have to have at least one of the device in the configuration you want to make a client for.

2. There has to be someone who knows how to compile and test the client on that configuration.


Even if you donate a device to the project, someone still has to create it and often times that is done by volunteers, such as students. That person can't focus just on a small segment. Also, if that person leaves, there is nobody to maintain the software.

SETI is under Berkeley's banner, but it doesn't mean that it gets the full force of Berkeley's funds. Most of these projects are under the banner of an educational institution. Some consider themselves lucky just getting hosting services from their institution...
6) (Message 4565)
Posted 12 Jul 2015 by Yavanius
Post:
BOINC transitioning to a Community Based Governance...
http://boinc.berkeley.edu/dev/forum_thread.php?id=10370


David Anderson wrote:

BOINC's funding from the U.S. National Science Foundation has ended, at least for the time being.
This funding supported me, Rom Walton, and Charlie Fenton.
We're now working on other things, although we'll stay involved in BOINC at some level.

The BOINC project will continue, and will be run according to a community-based model rather than centrally.
In essence, the people who contribute to BOINC now make the decisions about it.

This model is summarized here: http://boinc.berkeley.edu/trac/wiki/ProjectGovernance
and described in detail here: https://docs.google.com/document/d/1C6pU5RqidYBxk9oyAevm1yH1tn4Hw27oM8YpvsnR-gg

There will probably be little visible change.
The BOINC software will continue to work.
The translation system, Alpha testing project, BOINC web site,message boards, and email lists will continue to operate.
However, any new development and major bug fixes to BOINC will need to be done by volunteer programmers.
I'm confident that the BOINC community will meet the challenge.

I welcome your feedback.
Please post it to boinc_admin@googlegroups.com, a new email list for discussions about the BOINC project as a whole.

-- David
7) (Message 4560)
Posted 9 Jul 2015 by Yavanius
Post:
If it's running Android, you're probably gonna be out of luck for almost all the projects that support Android. Android on Intels are a very small portion of the market despite what MS might have you believe.

If it's Windows, it should generally be able to get work unless a project is requiring a certain minimum computation level (based on the benchmarks).
8) (Message 4558)
Posted 7 Jul 2015 by Yavanius
Post:
I am sorry, I will look at it as soon as possible and either extend the deadline or create new shorter tasks for android app but this is more difficult way.


Either the client or the work changed because as I previously noted, it wasn't this long before. SETI@home for comparison is shorter although they can take over a day's time too.

You might try double-checking you compiled with all the ARM optimizations. It's my understanding that those can make a significant difference.
9) (Message 4547)
Posted 30 Jun 2015 by Yavanius
Post:
To the admins:

I've written about this several times and gotten ZERO response.

In early May the WU run times on Android dramatically increased. A 1.4 ghz tablet takes at least 50 hours to run and that is within a 60 hour deadline.

60 hours is 5 days. That means if the tablet only runs 8 hours a day, it's impossible to meet the deadlines. BOINC is not designed as a 24/7 project. It's designed to run on UNUSED time. In this example, the device would have to be at least 90% charged and plugged in at least 10 hours a day.

If this were a phone that would a bit of a hard sell. Someone leaves at work at 6am, starts work at 7 and gets at 4, runs some errands, gets home about 6pm and plugs it in right away. That means the phone has to charge up to 90% before it can even start crunching. After being used all day, that's probably at least a couple of hours. That's 10 hours at best a day. Last time I checked, the WUs actually to be running a little longer so we're looking closer to 55 hours.

So what's the point of having an Android client if the work is just getting tossed? It's just a waste of everybody's time...
10) (Message 4546)
Posted 30 Jun 2015 by Yavanius
Post:
This isn't the BOINCstats forum. This is the Asteroids@home forum.

Asteroids has nothing to do with BOINCstats. BOINC has nothing to do with BOINCstats.
11) (Message 4537)
Posted 22 Jun 2015 by Yavanius
Post:
I have gotten no work for about 5 days ? are we out of work ?


I'm still able to get work. If you have multiple projects, Asteroids may be too low of a priority to run. Check your event log and all else fails try resetting the project.
12) (Message 4536)
Posted 21 Jun 2015 by Yavanius
Post:

Each project uses its own programmers, most do not share them, so yes it's quite possible it is not fully optimized. Multiple programmers can mean paying multiple people and most programmers tend to be really good at one platform and okay at the others, if they even do them.


The WUs are still running the same time...about 50 hours. I already dumped 12+ hours running the couple WUs on the one tablet so I might as well just let them finish.

There's not a whole lot of point of having an Android client when you are going to have WUs probably running over the deadline. Seems the developers would either optimize or just drop the Android client than wasting resources sending out WUs that aren't going to be completed in time...
13) (Message 4531)
Posted 21 Jun 2015 by Yavanius
Post:
I noticed on my Intel Core i5-2520M that the WUs are running about 3 hours. I'm wondering if the long WUs on Android are due to (lack of) optimizations? I'm running a test to see if they are still running that long...
14) (Message 4530)
Posted 21 Jun 2015 by Yavanius
Post:
Hi, could you pls manage that only 80-90% of the GPU is used like GPUGRID does? I can´t watch YT when 100% is used :(
Right @ the moment I have to block your projects when I want to watch Netflix or YouTube... that´s a waste of GPU-Power for you :(


It's noted on the BOINC client that running on the GPU while the computer is in use may cause graphics issues. The GPU is not a CPU. It's not intended to be used like that. It's like playing a 3D game and trying to watch a video at the same time. You COULD but it doesn't mean you SHOULD. ;)
15) (Message 4509)
Posted 14 Jun 2015 by Yavanius
Post:

I can't actually find this military I,II,III,IIII classification system they speak of. I would love to actually see a standard for the so called Military Class 4 as put forward by MSI in one of their flag ship motherboard listed at the link below.


http://quicksearch.dla.mil/

The I, II, ... is a classification defined in some spec. For non-combat, a lot of old specs have been obsoleted as requirements are obsoleted do to old specifications or it is easier to define requirements using commercial requirements.

You could try looking for procurements for Defense (DOD) for technology equipment and they should the exact Mil-Specs called out although sometimes you will go check a spec and see it's been superseded by a newer spec or sometimes even obsoleted. Further making things more murky is there are procurement divisions for each branch and even local bases that may have their own requirements. But DOD is a good start.

Alternatively, you can try contacting the government sales divisions of the big OEMs like HP and Dell and see if you get some more info.
16) (Message 4476)
Posted 31 May 2015 by Yavanius
Post:
I noticed some rather long times too in the last few weeks...

I have a couple of iRulu X1s that run at 1.4 Ghz. It takes 50+ hours for a WU.
My Fire HDX 8.9 runs at 2.2 GHz. I'm looking at around 30 hours for a WU (roughly 6 hours to reach 20%).

IIRC, Asteroids WAS running about 30 hours on my iRulus at the beginning of the month, so something changed, either the work or the algorithm that determines what work to send out...



Let's break it down like this for someone who is NOT running continuously plugged in... (I am mostly myself though)

Let's say that we get a good 6 hours per day of computing in allowing for the charge to hit 90%...

60 hours / 6 hours/day = 10 days to complete

We're looking at about a 10 day deadline right now.


I did get two very fast WUs Thursday night. These were of "*input_18324..."

For slower devices, these would be quite nice. 50 - 60 hours is overkill.
17) (Message 4475)
Posted 29 May 2015 by Yavanius
Post:
I am running a samsung phone galaxy 6 . but work is halted generally because the battery is under 90 % . is there a more potent power source I can use ?? this phone can run 8 cores at once


Your best bet is getting a couple of the most powerful external battery packs you can find, for example: https://www.amazon.com/dp/B00FDK2G2C

Note that they weren't intended for running your device with all cores going full-blown continuously. You'll need two because you're going to deplete one eventually and need to recharge it.

However, you're going to have a bigger issue: heat. A tablet has more surface area to spread out the heat, but your phone is quite compact. You're not going to be tossing it into a bag and unless you are someplace cold, you'll probably not enjoy the heat of it in your pocket. So, you'll need to put the phone down someplace and chances are that place will have a socket to plug in anyways...


Incidentally. That is not an octa-core. There is no such thing on the market. It's a dual quad-core, bringing it up to 8 cores total but not an octave-core. You have four cores @ 2.1 Ghz and four cores @ 1.5 Ghz. Samsung conveniently buries this info so although misleading, it's not a full-out misrepresentation.

Still, I'm waiting for the sh*t to hit the proverbial fan when the masses realize this and I'm sure a few will be making some lawyers rub their hands... but I don't expect much, except maybe a small settlement and an asterick* clarification on the marketing info. Storage Manufacturers are still saying 1mb = 1000 bytes instead of 1024 bytes although they now clarify it after a big lawsuit. So, we'll still see octa-cores but manufacturers will say that just means 8 cores, not 8 cores all clocked at the same speed...
18) (Message 4474)
Posted 29 May 2015 by Yavanius
Post:
I just completed my first task for Asteroids @ home, but it took a whopping 59 hours. For Android, is that too long?


I noticed these rather long times too in the last few weeks. There hasn't been any notes from Kyong though...

Let's break it down like this:

Let's say that we get a good 6 hours per day of computing in allowing for the charge to hit 90%...

60 hours / 6 hours/day = 10 days to complete

We're looking at about a 10 day deadline right now.

I have a couple of iRulu X1s that run at 1.4 Ghz. It takes 50+ hours for a WU.
My Fire HDX 8.9 runs at 2.2 GHz. I'm looking at around 30 hours for a WU (roughly 6 hours to reach 20%).

IIRC, Asteroids WAS running about 30 hours on my iRulus at the beginning of the month, so something changed, either the work or the algorithm that determines what work to send out...


I did get two very fast WUs last night. These were of "*input_18324..."

For slower devices, these would be quite nice. 50 - 60 hours is overkill.