Forums | MacLife

macFanDave · 2003-02-13 8:04 am

1) No home page. At least from the perspective of those attempting to reach via the Folding@Home site. If there is a home page, you need to get Pande's lab to update the link.

2) Safari unzips 3.24 incorrectly as text. While Safari is generally magnificent, when you let it open "safe" files, it screws up .tgz ones. I went back to IE (boo!), told it to just save tgz files and used Stuffit expander to correctly get the app. (I believe if you turn off the "Open safe files" in Safari Preferences, it'll probably do the same thing).

Keep in mind that we users are donating our time so screwing with the Folding app is not something many of us are likely to do.

3) Lots of failures with the Console mode. For whatever reason, I got nothing but Attempt to connect failed messages starting in late November.

4) Verbosity 9 is not very verbose. I'd expect progress messages (even if they are 10%, 20% etc.) when I asked the program to be as verbose as possible.

5) Although we are all caught up now, the fact that Windows and Linux were up to version 3.24 and OS X was stuck at 3.12 made me feel like the Mac crowd was being taken for granted. At one time the ratio of active OSX processors to total OSX processors was much higher than Windows and Linux, but with sleights like this, we have become the lowest. This makes for a self-fulfilling prophecy givng Mac teams the lowest priority.

I don't think any of these problems are hard to fix, but they need to be done if we ever hope to make the top 20 again.

JediKnightChewie · 2003-02-19 7:53 pm

3) Lots of failures with the Console mode. For whatever reason, I got nothing but Attempt to connect failed messages starting in late November.

yep, not only is this quite discouraging, but it also makes it much harder to actually finish a unit

im considering going back to the graphical verison. although its "slower" i was actually able to finish units then tongue

macFanDave · 2003-02-20 7:19 am

had I not used the Graphical version and seen how slowly the 632 project was going, I'd have assumed it was broken again and may have quit for good. I don't understand why maximum verbosity in the console version can't tell you it's progress from time to time ("Completed frame 10/400 at 4:00 pm")

belloq · 2003-02-20 1:45 pm

I don't understand why maximum verbosity in the console version can't tell you it's progress from time to time ("Completed frame 10/400 at 4:00 pm")

Adam should be able to answer that. It likely has something to do with the Core process not being able to output what it wants to in the same manner as the Win32 client.

NoahJ · 2003-02-21 12:08 pm

Adam should be able to answer that. It likely has something to do with the Core process not being able to output what it wants to in the same manner as the Win32 client.

From what i have been able to gather, Tinker has a bug in it on the Mac that it just does not output to a file as it should. Unfortunately. being the minority platform you get less of the programming cycles to fix these bugs. If this were occuring on the Windows side it would have been fixed immediately due to the fact that they would get no feedback as to what is going on with the folding process and why it is failing otherwise. WE have had this issue for a long time and even moving up to a new client version had no effect. neutral

NoahJ

belloq · 2003-02-21 1:58 pm

that it just does not output to a file as it should. Unfortunately. being the minority platform you get less of the programming cycles to fix these bugs.

Well, not entirely. The core does output to a logfile in the work folder. It's just that 1) the filename changes with the workunit number it is working on (0-9) and 2) it doesn't have a timestamp along with the output.

It does say "Finished a frame (10)" but nothing else.

NoahJ · 2003-02-21 2:20 pm

Well, not entirely. The core does output to a logfile in the work folder. It's just that 1) the filename changes with the workunit number it is working on (0-9) and 2) it doesn't have a timestamp along with the output.

It does say "Finished a frame (10)" but nothing else.

Yes, however that is not even close to parity with the windows side where you can look at the FAHLOG.txt with default verbosity and get a full view of the unit you are working on, any errors that occurred and how far along in said work unit you are with time stamps without having to visit any other log files along the way. This should be a simple fix and unfortunately is not getting any attention from Stanford's programmers. I realize they are busy working on many different things, but they have released new clients and cores and have not spent a few extra cycles to fix this thus showing it is not a high priority to them. So long as the client and cores work I am not complaining about it. However unless you know more than I do (which is really possible) they are hardly taking time out to fix this issue.

NoahJ

Not trying to start and argument, just being sure that my facts are straight and yours too. Perhaps togehter we might get the real picture. Or not.. tongue

Forums | MacLife

#1 2003-02-13 8:04 am

Why we are losing people...

#2 2003-02-19 7:53 pm

Re: Why we are losing people...

#3 2003-02-20 7:19 am

Re: Why we are losing people...

#4 2003-02-20 1:45 pm

Re: Why we are losing people...

#5 2003-02-21 12:08 pm

Re: Why we are losing people...

#6 2003-02-21 1:58 pm

Re: Why we are losing people...

#7 2003-02-21 2:20 pm

Re: Why we are losing people...

Board footer