Hemiola (Aug 12 2010)

snipped.......
AS a (mostly) mechanical engineer, it does my heart good to see my electronic colleagues adapting the time honoured and tested ways of the mech eng.

Matt.. if I might share.. from my experiences of keeping together antiques that were often poorly "refurbished"..

many problems clear permanently upon "re-seating" unplugging, and plugging back in. Other times taking things out, some surprise drops loose(seen or unseen 50/50).. and are then magically "fixed". Whether they were dirty connections, a bit of dust, someones raisinette.. does not really matter as long as they clear. a bad connection invisible to the eye might nearly need "bumped".. and could be gone forever.

We came up with things such as "pencil test".. where while monitoring the signal we tapped the outside case and see if it had effects. And some of the equipment was old enough to even contain mercury relays, where the mercury would vaporize, re-solidify in obscure pieces, and refuse to work until we "bounced" (hold edge of component 3-4" above anti-static surface, drop and catch on first bounce, re-insert) to clear.

These are also good reasons why "fault tolerance" is a good(although expensive) principle.

On the reports going back.. all of these were jotted down as "re-seat to clear."

Because if we told the truth, the whole truth, and nothing but the truth... it would have been the Salem Witch trials all over again.

One thing that used to work on CRT terminals, back in the '80s, was to give them a "slap upside the screen". Some terminals would come back to life for a time after the slap. Location (and force) was brand-dependent, and with one of the brands, there were two methods that worked, depending on symptom: the slap, directed at the upper right of the CRT, and lifting the front of the CRT about an inch, and dropping. IBM 3278's were pretty reliable, but when they went, they could (sometimes...) be brought back by slapping the back right corner, and picking up the back about .5 inch, and dropping...

AS a (mostly) mechanical engineer, it does my heart good to see my electronic colleagues adapting the time honoured and tested ways of the mech eng.

And to think that some people think that I'm daft. LOL

Maybe in the future we can just swear at the particular part/item without getting physical but I doubt things will ever get that good. :D

'server run, August 13-16 2010'

Because of the upper mentioned thread is closed, I write here.

Since ~ 24 hours the cricket graph show maxed out traffic.

So the mentioned 'WU limit in progress' isn't active.

My BOINC could DL the adjusted WU cache.

To now no server crash.

So why would be the limit needed?

The new donated server can manage the traffic better now?

____________


>Das Deutsche Cafe. The German Cafe.<

snipped.......
AS a (mostly) mechanical engineer, it does my heart good to see my electronic colleagues adapting the time honoured and tested ways of the mech eng.


We electronic engineers have always used the drop or kick test as a first line tool for faulty equipment. The distinction of being a good, no so good or lousy engineer depends on your skill and experience at delivering the require accurate shock.

The new donated server can manage the traffic better now?

LOL! There ain't much that can't be fixed without the judicious application of a "Birmingham Screwdriver" :-)

The new donated server can manage the traffic better now?

Are you talking about the server that they still need to write the purchase order for?

~ 28 1/2 hours maxed out traffic.

The cricket graph isn't longer maxed out.
So all PCs out there DLed their adjusted WU cache.

So I'm curious why we had/needed 'WU limit in progress'.
IIRC, it was for to protect server crashes.
But now, it worked without a limit.

The server are now more stable because of the last 3 day outage?
If, what the SETI@home crew did, what made the server more stable?
____________


>Das Deutsche Cafe. The German Cafe.<

Goofy WU Limits fixed???

I got two AP units a few hours ago and they 'think' they will require ~348 hrs when they have been completing in ~60 hrs for some time now. Hmmm???

603 & 608 units seem to be timed about right. Guess it's just wait-and-see...

And also in the SETI Bêta N.C. Forums, same 'problem', occurs in the ATI GPU's, running OpenCL, CAL/BROOK or a mix of them.
But latest revisions like 434, are quite fast and do drop computing time from 122 to 3 - 6 hours.
But this is a bit 'of topic'.

____________


Knight Who Says Ni N!, OUT numbered.................

Any chance we can have Seti Beta brought up, so we can upload/report our completed tasks before the Next outage?

Claggy

Edit: and in future bring it up a bit earlier?, please.

Validate errors!

'Message 1025850'

Please disable the UL server/service. For to hold small the value of validate errors.

The SETI@home crew will let run the famous script then again for to grant the Cr.?
____________


>Das Deutsche Cafe. The German Cafe.<