Posts by William


log in
1) Message boards : Number crunching : Unsupported computer (Message 1760072)
Posted 13 days ago by Profile WilliamProject donor
The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.

Since quite a while back, Lunatics sources are hosted at Berkeley too:
https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
or do an SVN checkout as described on the porting page.

I didn't see anything for v8. That's why it looked out of date to me.

Well apparentely neither Jason nor Raistmer felt it necessary to start a whole new branch for v8, but one of them put v7 into the initial commit...
Trust me all the optimisations are going into that sah_v7_opt branch (cuda is under XBranch in there) and Eric is committing in seti_boinc/client (so that's the branch you want to build for stock).
2) Message boards : Number crunching : Unsupported computer (Message 1760009)
Posted 14 days ago by Profile WilliamProject donor
The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.

Since quite a while back, Lunatics sources are hosted at Berkeley too:
https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
or do an SVN checkout as described on the porting page.
3) Message boards : Number crunching : Task Deadlines - Near Deadline Tasks Not Running First (Message 1759993)
Posted 14 days ago by Profile WilliamProject donor
@sleepy scheduling behaviour was completely redone in BOINC 7. yours still has something called 'long term debt' and yes in boinc v6, if a _project_ experienced EDF then it picks the one at the end of the list first and works it's way backwards, leading to the behaviour you are seeing. As Jord said at the time, he had yet to see a task actually no make the deadline with that system, even though it seems counterintuitive.
Anyway, workfetch, resource share and scheduling are completely different in new BOINCs. I always found it works better if you have multiple projects.
The interface got some nice features added too, you may want to try it.
4) Message boards : Number crunching : BOINC Board Down... :-( (Message 1759768)
Posted 14 days ago by Profile WilliamProject donor
I doubt somebody in the Netherlands can pull a plug in Berkeley.

Hey, they are always up when we are down, they can head here as refugees for once...
5) Message boards : Number crunching : Task Deadlines - Near Deadline Tasks Not Running First (Message 1759669)
Posted 15 days ago by Profile WilliamProject donor
I have been complaining about this a long time ago.
Seti seems to be the only project that computes the tasks in order they were received.
In theory, there should be a mechanism that runs task, that are in danger of missing the first. However, i do not know, if that works.


SETI works with looooooooong deadlines. about 6 weeks for a mid AR task. Even my stoneage 1Ghz SSE CPU finishes a midAR tasks in about 22 hours. So, SETI is almost never in risk of missing a deadline.

And don't forget the 'minimum work' you specify works as 'maximum time between two scheduler contacts' too, so if you set a 7+7 cache and gets tasks from a project that has 7 day deadlines those tasks will instantly go into EDF. (of course the project won't be asked for tasks in a hurry again after the tasks got run first)
6) Message boards : Number crunching : Task Deadlines - Near Deadline Tasks Not Running First (Message 1759664)
Posted 15 days ago by Profile WilliamProject donor
BOINC all the time recalculates if tasks are going to meet their deadline, when running in the order received (FIFO) and according to the resource share that project has. IOW it has a list of when it's going to start a certain task and when that task is going to finish (acoording to how long _BOINC thinks_ it's going to take. may be way off)
IF a task is in danger of missing its deadline (incl. safety margin) then BOINC puts it into EDF - Earliest Deadline First, also know as 'high priority' (that's what ir used to show up as in the boinc manager).
Since 'high priority' confused the hell out of people, leading them to the wrong conclusions about what it actually meant, this label was removed from BOINC clients a while back (not the best approach IMO).
Nowadays, if you want to ascertain a task is in EDF you need to activated the 'cpu_sched_debug' log flag. WARNING advanced users only. You are prone to be more confused by the log output than informed.
IF you run it and need it explained, post a sample.
7) Message boards : Number crunching : tasks downloaded and completed not showing up in my account pages (Message 1759659)
Posted 15 days ago by Profile WilliamProject donor
As per panic thread and server status page, the replica database is currently offline. Most functions where a user wants DB access (e.g. task viewing) run off the replica, to reduce load on the main DB.

No replica, no updates to website tasks lists.

A lot of other stuff probably runs off the replica too, so if you notice something isn't updating, it's probably due to that, too.
8) Message boards : Number crunching : No Such Task (Message 1759448)
Posted 16 days ago by Profile WilliamProject donor
As 26/01 15:30 GMT+2 , I can see it is online... How many hours will it take to sync approximately ?

you have to look further right:

Replica seconds behind master Offline

there it would say how long - if it was online.
9) Message boards : Number crunching : Panic Mode On (101) Server Problems? (Message 1758264)
Posted 19 days ago by Profile WilliamProject donor
I noticed after installing Lunatics I'm not getting any more work.

Before I had a full cache of 500 (400 for the GPUs and 100 for the CPU)

Now when I request work I get the following.

Not requesting task:don't need (CPU;job cache full;NVIDIA GPU:job cache full)


I'm going to let it run until I'm out of work, but if it doesn't refill I might have to pull remove everything and start again and see if it returns after a reinstall...

work_fetch_debug is your friend ;)
it needs 11 valids per host (non-overflow) for the scheduler to use APR for estimating runtimes. (one value per app, see you computers details page, e.g. cpu and gpu have separate entries (you did know that, but there's always lurkers)
shouldn;t take too long on a fast GPU ;) (wingmates permitting)

edit: and what Mark and Jason said of course.
10) Message boards : Number crunching : Lunatics Windows Installer v0.44 - new release for v8 (required upgrade) (Message 1758214)
Posted 20 days ago by Profile WilliamProject donor
that's a tad difficult, but you just gave me an idea. I'll run it past Richard, maybe we can rustle up something for the next version using app_config.xml (boinc versions 7.0.40+ only)

NB theses days if you have a v7 BOINC it's far easier to use app_config.xml instead of changing counts in app_info.xml, plus the installer doesn't touch app_config.xml (yet).
11) Message boards : Number crunching : V8 CUDA for Linux? (Message 1758165)
Posted 20 days ago by Profile WilliamProject donor
Short answer: Wait for somebody (e.g. Jason) to do a Linux version of x41zi, hand it to Eric for beta testing and after successful beta testing have Eric transfer the app to Main.
12) Message boards : Number crunching : Panic Mode On (101) Server Problems? (Message 1758113)
Posted 20 days ago by Profile WilliamProject donor
I don’t know if others have the same problem.

With v8, wu’s never end, and error out. Gpu usage is 0, with 2 tasks at the same time.

If I restart Boinc the wu’s start over and do the same thing. I use app_config.xml

Computer ID: 7578465


made link clickable
Check out this beta thread , see if anything there helps. [I've not really had the time to check tonights additions though] If not, please start a dedicated thread and we'll try to look into the problem. But not this morning, we have people breathing down our neck waiting for the installer release (most of them quite patiently, thankfully, but I know they are pretty anxious to get their GPUs back up ;))
13) Message boards : Number crunching : Seti@home v8 (Message 1758111)
Posted 20 days ago by Profile WilliamProject donor
DOn't forget that new BOINCs go on extended backup times if they can't get tasks. they max out at 24h - so it will be a while before all the unattended machines are back crunching.
14) Message boards : Number crunching : Panic Mode On (101) Server Problems? (Message 1758107)
Posted 20 days ago by Profile WilliamProject donor
It's very quiet here. Are you all holding the breath?

Calm before the storm.
At least here - will get frantic in a few hours trying to push that installer release out.
15) Message boards : Number crunching : GPUBeta v8 allready finished ? (Message 1757851)
Posted 21 days ago by Profile WilliamProject donor
iam sorry...no mac available here, many NV cards, and a HD 6950 too, an ARM Odroid for example , thats all i got.

btw, will a emulated system do the trick ? Maybe a trialversion of MAC OS for example, running on a PC in Virtual Mode ?

If you have fun experimenting you could give it a try, but for the purposes of beta testing for Eric, it would need to be a native Mac.
Thanks again.

NB most people attach to beta with a small resource share or periodically check if something is being tested and allow some tasks then. It helps if you can watch hosts doing beta and report any anomalies there.
16) Message boards : Number crunching : GPUBeta v8 allready finished ? (Message 1757840)
Posted 21 days ago by Profile WilliamProject donor
21st means 21st in Berkeley - they are on GMT-8 or 9 hours behind German time. I don;t think you'd be working at 3am ;)

If all goes to plan we expect apps to be released in the morning (Berkeley time) that's late evening for Europe. You should start to get GPU tasks some time in the night then.

Thanks for the offer of beta, but the development cycle is almost finished - unless you have a Mac on offer, preferably with an NV card?
We've covered the mainstream hardware, but some less used areas still need testing.


Und nochmal auf Deutsch:

21. bedeutet 21. in Berkeley und die sind auf UTC-8 oder 9 Stunden früher als MEZ. Du würdest um 3 in der früh sicher auch nicht arbeiten ;)

Wir erwarten, sofern alles planmäßig verläuft, daß die GPU Apps am Morgen (Berkeley Zeit) erscheinen. Das wäre dann am späten Abend in Europa. Du solltest im Laufe der Nacht GPU Tasks erhalten.

Danke für das Angebot Beta zu machen, aber wir sind fast fertig, ausser Du hättest einen Mac mit ner NV Karte?
Wir haben die Standardhardware abgedeckt, aber einige seltenere Kombinationen brauchen noch mehr Tests.
17) Message boards : News : SETI@home Version 8 for Android and GPU to be released January, 21st (Message 1757810)
Posted 21 days ago by Profile WilliamProject donor
Will there be instructions on how to run the new stock GPU apps under "Anonymous Platform"?

Won't be needed, we will be releasing an installer. (v 0.44)
Timeline for that is day (GMT) after Eric releases, since Richard and I are Europe based and need to check several files for consistency with what is released before we can finalise the installer and publish. Also it's good to give stock a head start, the APR system is flawed enough without us introducing extra chaos straight away.

Of course, now I have jinxed it.
18) Message boards : Number crunching : Panic Mode On (101) Server Problems? (Message 1757634)
Posted 22 days ago by Profile WilliamProject donor
...and the wait for more tapes for AP begins. My 10-day stockpile has been depleted.

Oh well, at least I don't have to keep telling BOINC to snooze when I do some video encoding now, so.. there's that, I guess.

why don't you set the video encoding program as exclusive app or exclusve gpu app?
19) Message boards : Number crunching : New app? (Message 1756611)
Posted 26 days ago by Profile WilliamProject donor
you should be fine if you use published app_info.xml or aistubs and only edit count or similar.

when you start editing name fields and version numbers, then you should really know what you are doing.

@ Louis as far as I can see, you are running stock CPU as anon as per sticky thread. no problem there.
20) Message boards : Number crunching : New app? (Message 1756546)
Posted 27 days ago by Profile WilliamProject donor
Songbird:
Keep a very close eye on your computer, note exactly what it is doing, report anything that is strange to the correct thread in Beta, although you may have to wait a bit to get enough credit to do so.
As you have just started over in Beta it is probably best if you do not run using the "Anonymous platform" just in case you have problems caused by how you are running rather than by the application under test. By running using the Anonymous platform you have keep a close watch that you are running the correct version of the applications, so you may have to update fairly often, whereas running "stock" the updates happen without you doing anything.

Posting to beta requires no RAC - apart from the cafe area. this is precisely to enable users who have just attached and run into problems to communicate.

@ Songbird, please PM me at beta so we can try to sort out your problem there, should it persist.

in general, for beta testing just keep an eye on things and report if something seems to go wrong, like getting lots of inconclusives/invalids or outright app failures. also keep reading the beta news thread.


Next 20

Copyright © 2016 University of California