Posts by Jeff Buck

1) Message boards : Number crunching : Nvidia GPUs missing (Message 1836861)
Posted 28 days ago by Profile Jeff Buck
Post:
This could happen if BOINC was installed as a "service". In that mode, it cannot detect GPUs. What I would suggest is to uninstall and then re-install BOINC, ensuring that the box for "Service Install" is not checked. You'll see that option in the window that also shows your Program and Data directories. If you see that the option is checked, use the"Advanced" button to deselect it.
2) Message boards : Number crunching : BOINC 7.6.33 improved AMD GPU detection (Message 1836808)
Posted 29 days ago by Profile Jeff Buck
Post:
Richard Haselgrove wrote:
Jeff wrote:
Not exactly promoting it as an important reason to upgrade, are they?
Who 'they'? Jord (Ageless) wrote those notes, and I've just added the line about the error code fix. BOINC will only improve if volunteers contribute to the process.
Sorry 'bout that. I would never intentionally disparage Jord's contributions. I certainly miss his well-reasoned contributions here in NC since his S@h RAC now only permits him to post in Q&A.

And thanks for making the addition to the 7.6.33 Release Notes. As I mentioned, that fix is, to me, the primary motivation for upgrading. Hopefully, it'll get the attention of others who have seen many tasks trashed by that error.
3) Message boards : Number crunching : BOINC 7.6.33 improved AMD GPU detection (Message 1836658)
Posted 29 days ago by Profile Jeff Buck
Post:
Grant (SSSF) wrote:
Unfortunately, the Release Notes don't say a word about what, to me, is the most important incentive for upgrading to 7.6.33, which is putting a stop to 1073741205 Error Code (Unknown Error), which has been bedeviling many users since at least this past spring. That's the one where BOINC keeps trying to restart tasks that Windows just terminated during system shutdown.

Does the actually released version still sort that issue out? If so, i'm surprised it's not mentioned in the Release Notes. Or did it get dropped from the Release Version?
Yeah, it's in there, but you have to follow the link to the BOINC 7.6 Change Log, then go just about all the way to the bottom of the second page, where you'll finally find "client: Check for a new process initialization error code when the user session is being logged off. Microsoft decided to add a new status code for Win10. See: #1553".

Not exactly promoting it as an important reason to upgrade, are they?
4) Message boards : Number crunching : BOINC 7.6.33 improved AMD GPU detection (Message 1836636)
Posted 29 days ago by Profile Jeff Buck
Post:
Grant (SSSF) wrote:
Everyone running the BOINC Manager will get a message in the Managers Notices tab, I can't think of anyway to let more people know about it than that.
Unfortunately, the Release Notes don't say a word about what, to me, is the most important incentive for upgrading to 7.6.33, which is putting a stop to 1073741205 Error Code (Unknown Error), which has been bedeviling many users since at least this past spring. That's the one where BOINC keeps trying to restart tasks that Windows just terminated during system shutdown. While 7.6.33 doesn't actually address the underlying BOINC vs. Windows contention, it does manage to trap the error messages so that tasks don't end up with computation errors.

Most of us who read the forums regularly know how to get around the problem, by always shutting down BOINC before shutting down the system, but it's easy to forget for those who don't have that process automated in some way. And for those who don't read the forums, well, they've probably been quietly fuming for months.
5) Message boards : Number crunching : Monitoring inconclusive GBT validations and harvesting data for testing (Message 1836440)
Posted 17 Dec 2016 by Profile Jeff Buck
Post:
Grant (SSSF) wrote:
Anybody got a preference as to how it runs?

I'd suggest CPU as that's the reference by which all others are judged.
True, but I'm not running stock. My CPU app on that machine is SSE3xj Win32 Build 3330. I don't know whether that dilutes the "gold standard" or not.
6) Message boards : Number crunching : Monitoring inconclusive GBT validations and harvesting data for testing (Message 1836436)
Posted 17 Dec 2016 by Profile Jeff Buck
Post:
jason_gee wrote:
Could be worth adding to the pile of potential hurdles, as I wade through the alpha code (please email if you have it).
If you mean the WU file, it's still on the server so just click on the WU name link in my earlier post to d/l it.
7) Message boards : Number crunching : Monitoring inconclusive GBT validations and harvesting data for testing (Message 1836429)
Posted 17 Dec 2016 by Profile Jeff Buck
Post:
Here's an Inconclusive WU with the new v8.20 (opencl_intel_gpu_sah) app. Both hosts appear to be reliable, but there's a pretty significant difference of opinion on this one.

Workunit 2362230258 (blc4_2bit_guppi_57424_80446_HIP9480_OFF_0004.32591.831.17.26.143.vlar)
Task 5362735823 (S=0, A=1, P=7, T=1, G=0) v8.00 (cuda42) windows_intelx86
Task 5362735824 (S=0, A=0, P=2, T=0, G=0) v8.20 (opencl_intel_gpu_sah) windows_intelx86

I've got the potential tiebreaker on one of my hosts. It's initially scheduled to run as Cuda50. However, since it's a VLAR, it might get rescheduled to run on the CPU if there's headroom in the CPU queue when that host boots back up in about half an hour. Anybody got a preference as to how it runs?

EDIT: Okay, looks like there wasn't room in the CPU queue so it's still scheduled to run as Cuda50, but probably not until late tomorrow afternoon. That means there's still plenty of time to change it if desired.
8) Message boards : News : Web site upgrade (Message 1836411)
Posted 17 Dec 2016 by Profile Jeff Buck
Post:
kittyman wrote:
I suppose it would require a total rewrite, but......dreaming......
And, I am not a coder, so I am 'assuming' this could be done.

It would be cool if the site code was kind of a 'template' and the user was given a number of options for the color scheme they desired.
Then the chosen color scheme would 'fill in the blanks' in the code, allowing the user to try or change the look as they desired.

New color schemes should be easy to create at that point, because you would just be compiling a table of what colors to use where.
Perhaps the user could even have access to create their own table of colors to use.
If you follow that link in the thread's very first post, to Darkly, then click on the Themes dropdown, you'll see that there are already quite a few other possibilities already built into the toolkit. How difficult it would be to make them user-selectable is the $64 question . I think the demo pages are all just separately pre-configured stand-alone pages. The demo just makes it look like the theme is changing on the fly.
9) Message boards : News : Web site upgrade (Message 1836332)
Posted 16 Dec 2016 by Profile Jeff Buck
Post:
"qbit" wrote:
...better quoting (those bars look awful and you still can't see who is quoted). It's all pretty much standard those days.
Actually, as shown, it is possible to have the quoted poster's ID appear above the quote but, as with URLs, you have to manually add the user's ID to the BBC quote tag as 'quote="xxxxxxx"'. Might as well just type it into your new post. It certainly could be done automatically by the forum code, but that might actually qualify as an "upgrade", What a concept!
10) Message boards : News : Web site upgrade (Message 1836190)
Posted 16 Dec 2016 by Profile Jeff Buck
Post:
Ergo, all of my arguments stand except to those that don't want to hear opposing views.
Ditto.
11) Message boards : News : Web site upgrade (Message 1836179)
Posted 16 Dec 2016 by Profile Jeff Buck
Post:
I would argue this point. Other than the colors, the site looks almost the same on mobile phones in landscape mode.
So you're saying that on phones, the scrolling required to view a given amount of text hasn't changed? On my PCs, it now takes close to 50% more scrolling to view the same amount of text, thanks to the font and line spacing changes needed to make it even marginally more legible.

A refreshing and much needed change.
An annoying and totally unnecessary change. If it ain't broke, don't fix it. Change for the sake of change is just plain dumb.

A more modern look.
As I said in a very early post on this topic, this reminds me of the blackboards and white chalk that we used to have in grade school 50+ years ago. I'm pretty sure "modern" usage, and not just in schools, consists of whiteboards with more easily readable black and colored markers.

EDIT: I also remember many years of plugging away with the old 3270/3278 "dumb" terminals with their green text on a black background. I think most of us were quite happy when PCs came along and we could actually have dark text on a light background. That was a very welcome change. It seems a shame to revert to the dark ages.

The truth is most people just don't like to have their cheese moved. Of course people are going to complain because people don't like change.
Most of the issues raised have been very specific, not just generic complaints about change. If there was a need for specific changes, and the changes met that need, then I doubt you'd have much argument. As far as I can tell, nothing about this "upgrade" meets that criteria, especially if there are "small display" users who are irked right along with those of us trying to cope on more standard-size monitors.
12) Message boards : News : Web site upgrade (Message 1835927)
Posted 14 Dec 2016 by Profile Jeff Buck
Post:
This next bit is so trivial, so please feel free to ignore it. It's just I was wondering if there were any plans to address the font color choices available in the drop down box. By not being set against the new background colour, it is not reflecting what the finished effect will be once the message is posted, which then require hasty editing. Also, some of the colours themselves, may no longer be suitable choices to include in the list. I tried a few in quick combination and got the legibility of a nasty bruise in places. I was going to demonstrate the effect for you here, but forgot.
As anniet has pointed out, another one of the side-effects of this ill-conceived and poorly implemented "upgrade" is the text coloring chaos that has been created. That's not only a problem for new posts but for old posts, as well. (Some of us actually do go back and read through old posts on a topic before crying for help in new ones, ya know! ;^))

Having thrown in the towel waiting for the dust to settle on this fiasco, I've finally started using "Color That Site!". Just the simplest of tweaks helps enormously. So, I decided to go back and look at a few of my old posts that made liberal use of text colors, comparing the effects as seen through the glass "Darkly" and with my altered "Color That Site" reality (which, or course, isn't exactly the old S@h color scheme, but close enough). Here's just one example.:

Darkly:
CTS:
So, the text color choices that have been used in every post going back to the beginning of time (or close enough), now look horrendous in this new scheme. On the other hand, as I noticed this morning, the more limited choices that are useful in new posts with this awful dark background don't work particularly well for anyone choosing to change it. Here's an example of a post from Richard:

Darkly:
CTS:

And one from awhile back by AMDave:
Darkly:
CTS:

I doubt if, under the old site color scheme, there were very many, if any, users here who ever disliked the presentation sufficiently to make use of a tool like "Color That Site!". Whatever minor quibbles there were, they were just that, "minor". And what one user posted was exactly what every other user saw. Now, as time goes by, I suspect there are going to be more and more users sufficiently disgusted with what they're expected to put up with that site viewing is going to diverge in unpredictable directions. How do you make text color choices, likely from a much more limited palette, that are both sufficiently distinctive to make whatever point you were aiming for, yet still legible for most viewers?

I still strongly believe that the default view for this site needs to return to the old color scheme. Bootstrap "Darkly" can then be offered as an optional skin for those who like it, and clearly there are many who do. I don't dispute that. But the current situation is just utter chaos!
13) Message boards : News : Web site upgrade (Message 1834656)
Posted 7 Dec 2016 by Profile Jeff Buck
Post:
Any ideas if there is a way to get my kitty banner and Boincstats block to display side by side again instead of one over the other?
Before the forum update, I was able to do this by putting the img lines one after the other, with no space between them.
[img]http://bluenorthernsoftware.com/k.php[/img][img]http://boincstats.com/signature/-1/user/461/sig.png[/img]

I have not changed anything, but now the forum will not do that.


Meow?

One of the attributes that's being assigned to your images when the page is actually created is "display: block". It probably needs to be "display: inline" (which is normally the default) to get it to display the way it used to. Nothing you can change. It's up to the guy doing his Alpha testing in production.
14) Message boards : News : Web site upgrade (Message 1833795)
Posted 3 Dec 2016 by Profile Jeff Buck
Post:
Edit2 - (from Number Crunching) Code blocks are wrapping. That's not good for syntax.

Yep, they sure are. On the other hand, "Pre" blocks in the forums don't wrap and may stretch the page, while "Pre" blocks for Stderr output on Task detail pages have horizontal scroll bars (where it probably doesn't much matter whether the pages stretch or not). I think it's because those are standalone <pre> elements, while on the forum pages they're subordinate to <table> and <div> elements which must be overriding the "overflow" attribute.

Anyway, they all now have white text on dark gray backgrounds. The dance of the deck chairs continues.
15) Message boards : News : Web site upgrade (Message 1833719)
Posted 2 Dec 2016 by Profile Jeff Buck
Post:
ARRRRRGHHHHHHHhhhhhhhh

We've just had a violent outbreak of orange - not at all easy on the eye :-(
I agree.
Who wanted this change from text displayed in a light yellow color to a darker orange text on a grey background?
I'm still seeing 'lemonchiffron' here - 'sandybrown' must have happened while I was out at the pub.

Still "sandybrown" here. Perhaps you've got a cached copy of the custom_dark.css file? Or maybe just beer goggles? ;^)
16) Message boards : News : Web site upgrade (Message 1833703)
Posted 2 Dec 2016 by Profile Jeff Buck
Post:
Well, as far as the latest deck chair rearrangement goes, "sandybrown" makes the link anchors infinitely more identifiable (to me, anyway) than "lemonchiffon" ever did, given that this dark background is apparently not going to be rescinded (except, of course, when composing posts, or embedding code or preformatted text, or ???).

I still don't understand why all of this trial-and-error development didn't take place for an extended period on a test site, like S@h Beta, before a finalized, broadly acceptable version could then be rolled out to the captive audience here on Main.
17) Message boards : News : New Nebula blog (Message 1833667)
Posted 2 Dec 2016 by Profile Jeff Buck
Post:
A new blog documents the progress and status of Nebula, the SETI@home back end.

How do you know that there is an actual link posted there? as it's not particularly visible without mousing over the text.

Claggy


I can see the difference in text color for links vs regular text. Links are in gold lettering. Text is in white lettering.

It's not "gold", it's "lemonchiffon", and even in natural ambient lighting, I can only just barely detect a slight hint of difference in coloring. In artificial lighting conditions, I can't see any difference at all. I just have to assume that there's a link hidden in there somewhere and, as Claggy said, wave my mouse around to find it.
18) Message boards : News : Web site upgrade (Message 1833527)
Posted 1 Dec 2016 by Profile Jeff Buck
Post:
Thanks. That's a known problem - I thought it had been fixed once, but possibly it reverted again.

Yeah, it reverted when the Bootstrap hit the fan.
19) Message boards : News : Web site upgrade (Message 1833523)
Posted 1 Dec 2016 by Profile Jeff Buck
Post:
Still waiting for the line wrapping problem to be properly addressed.
I haven't seen it myself. Could you link a specific post where you see it wrapping badly, and give an estimate of how wide your browser window is, please? (mine is "about 80% of a 1920 pixel monitor", for example)

I've seen it myself on pages where there's a [pre} or [code] block with one or more very long lines. Those blocks used to have internal horizontal scroll bars in situations where lines exceeded page width. Now, the boxes just stretch the page and the text-wrapping margin goes out to the right with them.

Take a look at Message 1832434 and see what happens to other text on the page.

EDIT: BTW, my browser window is normally about 1200 px wide.
20) Message boards : News : Web site upgrade (Message 1833516)
Posted 1 Dec 2016 by Profile Jeff Buck
Post:
Using the 'inspect element' technique...

Thanks for mentioning that. I hadn't thought of that in a long time. Now I can see that the "anchor" color, which I can't identify at all in the evening under artificial lighting conditions, and can barely distinguish during the day with natural lighting, is "lemonchiffon". That's supposedly one of the "fixes to dark-backround [sic] themes to increase legibility". Yeah, right!

I don't think there's any amount of lipstick that's going to make this pig sufficiently attractive for my sensibilities, so I guess I'll just wait until the dust settles and try out that Color-that-Site add-on that others have mentioned. How I'll actually know when the dust has truly settled, though, is another mystery altogether.


Next 20


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.