Probably a minor quibble, but maybe worth noticing?
The unitinfo.txt files have different names, even when assigned to
similar hardware. For example, two identical Conroe2d's
The project list here: http://fah-web.stanford.edu/psummary.html
calls it p2665_IBX in water.
Yet on Machine #1
Current Work Unit
-----------------
Name: HGG with glycosylations
Tag: P2665R2C850G6
Download time: June 7 14:58:48
Due time: June 13 14:58:48
Progress: 100% [||||||||||]
...
Project: p2665 (Run 2 Clone 850 Gen 6)
================
And on Machine #2
Current Work Unit
-----------------
Name: HGG in water
Tag: P2665R3C639G9
Download time: June 8 15:33:44
Due time: June 14 15:33:44
Progress: 26% [||________]
...
Project: p2665 (Run 3 Clone 639 Gen 9)
Project 2665 with three differing names
Moderators: Site Moderators, FAHC Science Team
Re: Project 2665 with three differing names
hi there, thanks for your observant post. I checked the server, and the reason for this is due to our ability to have multiple starting structures within a project. at least one of them was labelled differently, probably so its easier for Peter to keep track of the runs..... hope this helps!
nick
nick
-
- Posts: 365
- Joined: Tue Feb 12, 2008 7:33 am
- Hardware configuration: Running exclusively Linux headless blades. All are dedicated crunching machines.
- Location: SE Michigan, USA
Re: Project 2665 with three differing names
I understand, I think. However, that creates problems for us users that try to monitor multiple machines, across differing operating systems. It's difficult to match differing protein names against a lookup table to show the current WU points, for example.
Many people download the project summary list, then use that as the "official" list. When there is noexact match of the name found in the unitinfo.txt file, it creates problems.
Many people download the project summary list, then use that as the "official" list. When there is noexact match of the name found in the unitinfo.txt file, it creates problems.