Posts by adrianxw

1) Message boards : Number crunching : Strange credit observation. (Message 106337)
Posted 26 days ago by Profile adrianxw
Post:
1488751880 1324253399 3161065 30 May 2022, 18:56:58 UTC 31 May 2022, 14:05:09 UTC Completed and validated 43,640.71 42,703.34 474.11 Rosetta v4.20
windows_x86_64
1488730111 1324234927 3161065 30 May 2022, 17:49:17 UTC 31 May 2022, 12:35:34 UTC Completed and validated 43,812.85 42,888.56 141.21 Rosetta v4.20
windows_x86_64

Just saying...
2) Message boards : Number crunching : Strange credit observation. (Message 106114)
Posted 28 Apr 2022 by Profile adrianxw
Post:
I looked later, the two are credited now.

1484546130 1319847242 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 13:11:46 UTC Error while computing 20,896.15 16,495.94 148.00 Rosetta v4.20
windows_x86_64
1484546134 1319847241 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 8:19:25 UTC Error while computing 973.13 915.19 8.00 Rosetta v4.20
windows_x86_64
1484546135 1319847243 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 18:12:26 UTC Error while computing 38,960.04 32,750.23 295.00 Rosetta v4.20
windows_x86_64
3) Message boards : Number crunching : Strange credit observation. (Message 106110)
Posted 28 Apr 2022 by Profile adrianxw
Post:
With this current crop of work units, I was surprised to see I had 3 errors.

1484546130 1319847242 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 13:11:46 UTC Error while computing 20,896.15 16,495.94 --- Rosetta v4.20
windows_x86_64
1484546134 1319847241 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 8:19:25 UTC Error while computing 973.13 915.19 8.00 Rosetta v4.20
windows_x86_64
1484546135 1319847243 3161065 28 Apr 2022, 7:02:09 UTC 28 Apr 2022, 18:12:26 UTC Error while computing 38,960.04 32,750.23 --- Rosetta v4.20
windows_x86_64

The short one got a few credits, the two long ones got none. Each finished with...

Exit status 1 (0x00000001) Unknown error code
4) Message boards : Number crunching : Waste of resource. (Message 106086)
Posted 27 Apr 2022 by Profile adrianxw
Post:
As I understand things, a work unit has "a problem", it generates a random number then uses the program to run the model with that random start point. If it finishes within the time limit set by the user, it generates a new random number and repeats.
Thinking about that, setting a long run time may not be a good idea.
Rational, the project has estimated the number of runs needed to produce the result they need. They estimate the number of work units required to achieve such a result, (they can estimate this from in house runs on their own machines). They sit back and wait.
By setting a long run time, I generate more results per work unit on both of my machines. Others are quite possibly doing the same thing. The number of runs required when the initial estimate was made is reached earlier. Are further work units then not sent, or are they left in the queue to, basically, waste the resource?
5) Message boards : Number crunching : Lot of failures (Message 105793)
Posted 2 Apr 2022 by Profile adrianxw
Post:
>>> It looks like the WU are bad and you are OK.

Yes, I know.
6) Message boards : Number crunching : Lot of failures (Message 105781)
Posted 1 Apr 2022 by Profile adrianxw
Post:
>>> LARGE part of clients/volunteers runs Windows

Certainly. Let us, however, consider the purpose. We are trying to help them. It is up to them to decide if Linux users are sufficient in number to acheive the result they require. It is already mentioned in this thread, that the amount of work from the project is a lot less than it used to be. They will, however, pick up on the fact that Windows users are seeing crashed work, and stop issuing it to these people, that, obviously, includes me.
7) Message boards : Number crunching : Lot of failures (Message 105777)
Posted 1 Apr 2022 by Profile adrianxw
Post:
Hi JD, yes, Linux systems certainly do seem immune from this problem. If the project is getting enough work done, there is little impetus to fix the problem with Windows, or issue VBox work to the same crunchers.

As long as the work is getting done, fair enough. Twenty years ago, the comms was so slow, it would have been a serious annoyance.
8) Message boards : Number crunching : Lot of failures (Message 105773)
Posted 1 Apr 2022 by Profile adrianxw
Post:
The two I mentioned earlier are still crunching away, 24% and 26% respectively. VBox is here, and a couple of projects use it without issue.

I know what you mean by "work starved". I always regarded Rosetta as an endless supply of work units which caused no problems for me, (Windows 8.1 x64), but work units are few and far between nowadays. The Italian project TN-Grid, (http://gene.disi.unitn.it/test/), is taking up most of the slack though. Generally, the number of projects I consider to be worth supporting has fallen markedly.
9) Message boards : Number crunching : Lot of failures (Message 105770)
Posted 1 Apr 2022 by Profile adrianxw
Post:
A large percentage of the work units sent here today quickly, (~20 seconds), failed with...

-1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION

... two, however, have started, have been running for a couple of hours, and are showing 12% complete.
10) Message boards : Number crunching : Constant computation errors. (Message 105459)
Posted 16 Mar 2022 by Profile adrianxw
Post:
All failing on both my Windows 8.1x64 systems after about 70 seconds. The exit code is "1 (0x00000001) Unknown error code" which is not much help.
11) Message boards : News : Thank you! (Message 105402)
Posted 11 Mar 2022 by Profile adrianxw
Post:
It simply replaces the message with...

>>> This post is not shown because the sender is on your 'ignore' list. Click here to view this post

... The "box" on the left of the post still appears though.
12) Message boards : News : Thank you! (Message 105381)
Posted 10 Mar 2022 by Profile adrianxw
Post:
>>> You make me sick

I'd try to get used to that Peter. People are free to join projects, and just as free to leave them. How that makes YOU feel is not really going to be a concern.
13) Message boards : Number crunching : computation errors (Message 105163)
Posted 23 Feb 2022 by Profile adrianxw
Post:
There has been other work recently. At this moment, I have 12 work units running on my machines that have all gone past the rapid failure point I was seeing.Two of these are past 9 hours now and running for example.
14) Message boards : Number crunching : computation errors (Message 105110)
Posted 21 Feb 2022 by Profile adrianxw
Post:
>>> little longer than me

Yes, you are a relative newbie!!!!!

If you consider the machines we were running back then, to keep run times sensible, the amount of calculation per work unit must have been a fraction of what we turn over today.
15) Message boards : Number crunching : computation errors (Message 105103)
Posted 21 Feb 2022 by Profile adrianxw
Post:
>>> Someone put movingstubs on the server without beta testing it

A little worrying.

>>> no one from the project pays attention to this

Would certainly seem to be the case.
16) Message boards : Number crunching : computation errors (Message 105097)
Posted 21 Feb 2022 by Profile adrianxw
Post:
>>> Not nearly as puzzled as i am by yours.

Oh, I see, my puzzlement is bigger than yours!

I still have no idea of what you're on about. Rosetta USED to be a project with endless work units from their various work projects to download and crunch. Since late last year, that changed. Now, it is a project that produces a batch of work, lets that run, then stops for an unknown period, until the next batch starts. I saw new work from Rosetta coming in, and watched them crashing quickly. After seeing that, It wasn't wasting vast amounts of time, but felt no new tasks was appropriate. Looking at the sent times, I see that three would come, fail and return. About 30 minutes later, another three would come, fail and return. After a number of these cycles, I set no new tasks. Some time later, I opened downloads to see what the status was, and nothing came. Conclusion, they have all gone, or that someone at the project had stopped them.
17) Message boards : Number crunching : computation errors (Message 105095)
Posted 21 Feb 2022 by Profile adrianxw
Post:
I am a little puzzled by your message actually.

>>> Did you even pay the slightest bit of attention to the statement i was responding to???

Well, I didn't really need to since the statement you appeared to be responding to was written by me? I do know how BOINC works, I've been with it, and Davids earlier version, (probably not the right word, but it conveys the meaning, anyway, since 1998), since its first appearence.
18) Message boards : Number crunching : computation errors (Message 105009)
Posted 19 Feb 2022 by Profile adrianxw
Post:
>>> Nothing to do with the project, that is normal behaviour for the BOINC Manager.

When a project has submitted a batch of work units that are immediately crashing in the cruncher pool, an in touch project manager can remove future downloads of the failing work units. It is exactly relevent to the project, and absolutely nothing to do with BOINC.
19) Message boards : Number crunching : computation errors (Message 104931)
Posted 18 Feb 2022 by Profile adrianxw
Post:
Perhaps someone at the project noticed the problem. I had a large number of these quickly crashing work units, on both my machines, but neither has downloaded new work for a couple of hours.
20) Message boards : Number crunching : Lots of computer time, little credit (Message 104780)
Posted 10 Feb 2022 by Profile adrianxw
Post:
>>> It's you who claimed LHC has only Linux apps.

Having an app, is not the same thing as having work for it.


Next 20



©2022 University of Washington
https://www.bakerlab.org