2005.08.19 UD狀況回報 (分數歸0與任務天數限制解說)

我將這兩天官方討論區的資料轉述一下

先附一張現在官網的圖



真的好嚇人
但是不用擔心
請看以下解說：

2005.08.17

Dear Users,

You may notice that all the stats are currently showing zero. This is due to the maintenance we are doing to try to get the team stats working again. We believe that the problem with the stats is because the stats table has grown too large (years of stats all held in one single table). We have cleared the table and are reimporting the last two years to try to reduce the size of the table. This is why everything is currently at zero.

Nothing is lost and if you have been contributing for more than two years again nothing is lost. Please be patient while we try to get this working again.
_________________
-----------------
Robby Brewer
Senior Support Engineer
United Devices

========================================================
翻譯如下(yahoo提供)^^"：
========================================================

親愛的用戶,

您可以注意, 所有stats 當前顯示零。這歸結於我們做□設法得到隊stats 再運作的維護。我們相信, 有stats 的問題是因為stats 桌增長太大(幾年stats 所有舉行在一張唯一桌裡) 。我們收拾了桌子和reimporting 最近二年設法減少桌的大小。這就是為什麼一切當前是在零。

□什麼丟失並且如果您貢獻為超過二年□什麼再丟失。請是耐心當我們設法再得到這工作。
_________________
-----------------
Robby 釀酒者
高級支持工程師
團結的設備

*********************************************************
2005.08.18

Dear members,

There has been some confusion regarding the processing of workunits and point credit for returned workunits. I will try to clarify how the current system works and mention briefly how the upgraded system will work in regards to this.

Currently, workunits are credited as long as the job is still in an "active" state. Once the job is changed from an "active" state, any outstanding workunits will not be accepted and no point credit can be given. This is not new behavior, but some of the work management (e.g. new Rosetta jobs) we have been doing lately may make you think so.

For the past many many months, the Cancer jobs have been in an "active" state and any workunits could always be uploaded and credit recieved anytime. Since the data is not new and final results have been calculated, all but one Cancer job have been disabled. Anyone still crunching any of those other workunits would not have received credit once the job was marked inactive. Please understand that we cannot let jobs run forever.

The Rosetta jobs we have been running have been finishing much more quickly than we had expected (very good). In order to not crunch redundant workunits and to move on to new data, we have been disabling the Rosetta jobs as soon as they finish and we have been starting a new one with new data immediately. This would mean that any dispatched workunits that were still outstanding would not be credited after the job was marked "inactive".

We now realize that this may be causing some frustration and will tweak the Rosetta jobs to minimize this as follows.

1) We will limit the number of concurrent dispatches per workunit. This should limit the number of outstanding dispatched workunits at any given time.

2) We have set the wallclock timeout to three days. Any workunit that takes more than three real days to complete will be discarded.

3) Once we have all of the required number of results per workunit and the job is complete, we will wait the three day wall clock limit before marking the job "inactive". This should greatly limit the number of invalid workunits since we are limiting how many active dispatches there can be.

Note that there will still be some cases where there are dispatched workunits that will not be returned before the job is marked "inactive" and no credit will be given. Also note that once we move to the latest version of the grid software, this will no longer be an issue. When we have all of the results, the job will be marked "suspended" which means no more workunits will be dispatched, but we will still credit any returned workunits. Unfortunately, that same behavior just does not exist in the version we are currently running.

I know there is frustration in the user community due to perceived "work for nothing", but we are burning through Rosetta jobs in just a few days which is amazing and something everyone should be proud of. We still have a couple of snags getting the new Cancer data uploaded, but I know we will see similarly amazing results.

Please hang in there and thank you for contributing.
_________________
-----------------
Robby Brewer
Senior Support Engineer
United Devices
========================================================
翻譯如下(yahoo提供)^^"：
========================================================
親愛的成員,

有是一些混亂關於處理workunits 和點credit 為返回的workunits 。我將設法澄清怎麼當前的系統運作和簡要地提及怎麼被升級的系統將運作關於這。

當前, workunits 相信只要工作仍然是在"活躍" 狀態。一旦工作被更換從"活躍" 狀態, 任何卓著的workunits 不會被接受並且點無法被相信。這不是新行為, 但是一些工作管理(即新Rosetta 工作) 我們最近做□可以使您認為如此。

在過去許多許多月, 巨蟹星座工作是在"活躍" 狀態並且所有workunits 能總被上裝並且credit recieved 任何時候。因為資料不是新的並且最後的結果被計算了, 所有除了一個巨蟹星座工作失去了能力。任何人仍然咬嚼任何那些其它workunits 不會接受credit 一旦工作是被標記的不活潑的。請瞭解, 我們無法讓工作永遠運行。

我們運行的Rosetta 工作比我們期望了迅速完成(非常好) 。為了不咬嚼重複workunits 和不行動向新資料, 我們使Rosetta 工作失去能力當他們完成並且我們立刻開始新的以新資料。這會意味, 任何派遣了依然傑出不會相信的workunits 在工作是被標記的"不活潑的" 之後。

我們現在意識到, 這也許導致某一失望, 將扭捏Rosetta 工作使這減到最小如下。

1) 我們將限制一致急件的數量每workunit 。這應該在指定時候限制卓著的被派遣的workunits 的數量。

2) 我們設置了wallclock 暫停對三天。需要超過三真正的天完成的任一workunit 將被擯除。

3) 一旦我們有所有結果的必需的數量每workunit 並且工作是完全的, 我們將等待3 天的壁鐘極限在標記工作之前"不活潑" 。這應該很大地限制無效workunits 的數量因為我們限制多少份活躍急件那裡可能是。

注意有更將是有被派遣的workunits 不會返回的一些案件在工作是被標記的"不活潑的" 之前並且不會被相信。並且注意一旦我們搬走向柵格軟體的最新的版本, 這不再將是問題。當我們有所有結果, 意味的工作將被標記"暫停" 沒有其他workunits 不會被派遣, 但是我們更將相信所有返回的workunits 。不幸地, 那同樣行為不存在在我們當前跑的版本。

我知道有失望在廣大用戶由於被察覺的"工作為□什麼", 但我們燒通過Rosetta 工作在幾天是令人驚訝的並且某事大家應該是驕傲的。我們仍然有兩三根斷枝得到新巨蟹星座資料被上裝, 但我知道我們將看相似地令人驚訝的結果。

請垂懸那裡和謝謝貢獻。
_________________
-----------------
Robby 釀酒者
高級支持工程師
團結的設備

********************************************************

現在請耐心等待分數的歸來
也希望連同團隊分數一併能夠恢復

另外，Rosetta任務限制天數的問題
應該是新舊資料在轉換，擔心有重覆或無效的資料，所以才採取這樣的方式
(因為大家的努力，所以Rosetta的進度超過預期進度)

請大家先切換成LigandFit任務，避免您的付出沒有分數

p.s：LigandFit任務超過3天還是有成績唷



大家一起加油!!

x0

呃... 沒事就好... 在公司初見分數歸零的訊息還嚇了一跳.....

x0

看來這次更新是個大大大工程了！連原來每日一次的個人資料更新與本來可以適時反應機器回傳資料時間次數(Device Manager--Statistic)也都暫停了～

x0

今天
又有一些更變
看一下最新官方資料

2005.08.19

Dear members,

After some very constructive feedback, it has become obvious that the three day timeout is not acceptable due to slower machines. We absolutely do want to keep these machines crunching work units. Therefore, we will change the timeout. Here is the new configuration of the Rosetta jobs:

1) The maximum number of dispatches per workunit will be limited to 20.

2) The wall clock timeout will be set to 7 days. This means that after 7 days, your workunit will be discarded if it has not completed processing and uploaded to the grid server. Please do not grab more work than you can complete in a week (UD Mon or whatever) so we do not have to redispatch due to lost work.

3) After we have the minimum results (currently 3) for each and every workunit, the job will be considered completed. At that time we will wait 7 days for any outstanding workunits to be returned for credit. After 7 days, the job will be marked completed and no credit will be given for outstanding workunits.

4) We will enable a new job as soon as we have the minimum results for the first job. That way there will always be new work that needs to be processed.

Again we are in a trial and error mode while we attempt to find the optimal configuration that benefits both the work that needs to be done and the user community that is performing that work. If we need to make a change we will make it. Please offer suggestions if you have them and please keep the flames to a minimum. It is not our intent to invalidate work or keep users from getting the points they deserve.

Thank you for your patience and your contribution.
_________________
-----------------
Robby Brewer
Senior Support Engineer
United Devices

======================================================
yahoo翻譯
======================================================

親愛的成員,

在一些非常建設性的反饋以後, 它變得明顯, 3 天的暫停不可接受歸結於更慢的機器。我們absolutely 想要繼續這些機器咬嚼工作單位。所以, 我們將改變暫停。這Rosetta 工作的新配置:

1) 急件的最大數字每workunit 將被限制到20 。

2) 壁鐘暫停將被設置對7 天。這意味著, 在7 天以後, 您的workunit 將被擯除如果它未完成處理和上裝對柵格伺服器。比您能完成在一個星期請不要劫掠更多工作(UD 星期一或什麼) 我們不如此必須redispatch 由於失去的工作。

3) 在我們有之後極小值收效(當前3) 為各workunit, 工作將被認為被完成。那時我們將等7 天所有卓著的workunits 返回為credit 。在7 天以後, 工作將被標記完成了並且不會被相信為卓著的workunits 。

4) 我們將使能一個新工作當我們有極小的結果為第一工作。那個方式那裡總將是需要被處理的新工作。

我們再是在嘗試方式下當我們試圖發現有益於工作需要完成並且廣大用戶進行那工作的優選的配置。如果我們需要做變動我們將做它。請提供建議如果您有他們並且請保留火焰對極小值。這不是我們的意向退役工作或保留用戶從得到他們該當的點。

謝謝您的耐心和您的貢獻。
_________________
-----------------
Robby 釀酒者
高級支持工程師
團結的設備

*******************************************************

嗯...
又有了些應對的更新

雖然有點不便

不過，大家一樣要繼續加油喔  

x0

反正這是做功德
0也沒差

x0

但是沒有分數，就好象做了工作沒人家認同一樣，心裏都不舒服。

x0

下面是引用dgleung於2005-08-23 16:36發表的 :
但是沒有分數，就好象做了工作沒人家認同一樣，心裏都不舒服。

至少：您的UD AGENT會反應分數啦～～官版的SERVER一時之間不會反應沒關係～

x0