Folding Forum

Yeah I whish the wiki however would be able to allot both http://fahwiki.net/index.php/Cores#Double_Gromacs_core and #DBGromacs ( from memory ).

I can not call the page directly because the formating is built around the table you also use in fahmon, I think it wouldn't be impossible to attach more then one anchor to a section though so anyone can link directly to the revelant core's using the core name's from the psummary page?

I think it probably is possible, I haven't checked closely though

uncle_fungus wrote:I think it probably is possible, I haven't checked closely though

It's not a primary issue, the page isn't that long that people can't scroll down to find anything it's just anoying me abit

Nm, off topic as well Off to bed, need some sleep.

Hi,

In addition to the suggestions I posted HERE, if it's not too much trouble to include in a future update, it would be nice if the user had the ability to change the FAHLog (F8) viewers' Font. Having this choice would allow FAHMon to match that of the actual console client formatting (ie: non-proportional).

Also, it would be nice that the FAHMon 'System' preferences to manually change the UTC offset would also apply to the FAHLog viewer (not the file itself). Seems I'm getting to old to keep wrapping my noodle around the twice a year time change.

Thanks.

My FahMon's status is always yellow now. What could be wrong? It used to be green before.



It's basically like that. Is there a way to fix it?

Make sure your timezone is set correctly in FahMon preferences

Tynat wrote:Also, it would be nice that the FAHMon 'System' preferences to manually change the UTC offset would also apply to the FAHLog viewer (not the file itself). Seems I'm getting to old to keep wrapping my noodle around the twice a year time change.

Wouldn't that be even more confusing for people who open the actual file and see something different?

That may make it simpler for you but it certainly will make support more complicated. People who post screen-shots never bother to tell me what timezone they're in. At least with UTC I know what I'm looking at when I see FAHlog. It's already complicated enough with Stanford servers being maintained in their own local time, the FAHlog being in UTC, and now you're suggesting to change some things to a third timezone with an unreported offset.

Having the FahMon GUI in local time makes sense, but please . . . not FAHlog.

Bruce, you're right. I suppose some people using FAHMon wouldn't even know that there is an actual log from which to gather information. In that case, the problem really is with the client itself, since the offset could already be included in the log by default. For example: FAHMon would then be able to display the adjusted information without having the problems you described.

I think the ability to change the Font remains a viable option.

Any possiblity of adding a column that showed the last time that a frame was completed? This would be very useful for VMware clients, espcecially if you turn them off and on. That way you could ensure that it wasn't actually "Hung", as it would have the last (System) time a frame was completed.
Also, haven't had a chance to read through this thread yet, but why are VMware clients so iffy? Sometimes, they will show as hung, but, if you go to the "Show/hide Messages window", and find the VMware client in question, it shows an ETA for it. Why can it show that there, but not in the main window?

Tynat wrote:I think the ability to change the Font remains a viable option.

ColonelCain wrote:Any possiblity of adding a column that showed the last time that a frame was completed? This would be very useful for VMware clients, espcecially if you turn them off and on. That way you could ensure that it wasn't actually "Hung", as it would have the last (System) time a frame was completed.

Perhaps, but not for 2.4.0.

ColonelCain wrote:Also, haven't had a chance to read through this thread yet, but why are VMware clients so iffy? Sometimes, they will show as hung, but, if you go to the "Show/hide Messages window", and find the VMware client in question, it shows an ETA for it. Why can it show that there, but not in the main window?

VMware clients cause problems because they are mostly unable to keep synchronised time with the host: 1 guest second does not always equal 1 host second by the wall clock. This means that either the guest clock runs fast or slow relative to the host and generally breaks any sort of monitoring based on time (and it also means the PPD and ETA calculations are a load of rubbish too).

I used to see that problem when I was running vmware clients on my computers as well with the time however its not hard to fix all you need to do is setup a ntp server on one computer that is not a vmware client on your lan to sync to ntp server over the internet then setup ntp clients to sync to your ntp server every hour to keep the clocks in sync. If the clocks are really bad you could set them up to sync even more often. I do not recommend syncing to the outside ntp server that often since it could put too large a load on the system you should run your own ntp server. This is not hard to do on linux I am not sure how hard it would be to set up a ntp server on Windows.

Could someone be so kind and publish a compiled FahMon for Win of the latest SC? 2.3.4 is still veeeeeery slow with the bigger log files from e.g. fast gpu client having run for 60 days straight

Thaaaanks!

Shadowtester wrote:I used to see that problem when I was running vmware clients on my computers as well with the time however its not hard to fix all you need to do is setup a ntp server on one computer that is not a vmware client on your lan to sync to ntp server over the internet then setup ntp clients to since to your ntp server every hour to keep the clocks in sync. If the clocks are really bad you could set them up to sync even more often. I do not recommend syncing to the outside ntp server that often since it could put too large a load on the system you should run your own ntp server. This is not hard to do on linux I am not sure how hard it would be to set up a ntp server on Windows.

Are you using Notfred's folding distro?

Cause I'm a complete n00b when it comes to linux...

I recently kept FAHOpen running for about 3 days and noticed that it used close to 5 hours of CPU time. Is this normal behavior? I've never kept FAHMon active for more than a couple of hours, so I'm afraid I do not know. Anyway, have closed it for now as its 5 hours that FAH could have used

If it matters, FAHMon was in the background (in the systray) 99% of the time. I do not have any clients on a remote share.

One of my boxes had a crash, nothing spectacular but a psu blown out. On reboot, the client seems to be running normally but when starting fahmon it gave a messagebox about 'unable to convert fahlog.txt to unicode'? Deleting fahlog and restarting client fixed it, think the crash caused the log to be abit corrupted. It's not really a bug, but I did have to think about what could be the cause of it and lost some precious minutes on that so maybe add some text to the messagebox to suggest deleting the logfile?

Anandhanju it shouldn't normally, but it's been reported more then once. I had this happen as well, but mostly ( almost exclusively ) with networked clients. I think the cause is a method for getting current status is not able to complete and the thread isn't discarded but I'm not sure.