找回密码
 新注册用户
搜索
查看: 11600|回复: 15

[注意] S5R6 也快结束啦 [补充:S5GCE已经开始~~]

[复制链接]
发表于 2010-2-24 10:46:05 | 显示全部楼层 |阅读模式
Total needed        Already done        Work still remaining
7,449,712 units        6,481,969 units        967,743 units
100 %        87.010 %        12.990 %
152.4 days        132.6 days        19.8 days (estimated)

估计要靠ABP2项目来撑一阵子了
回复

使用道具 举报

 楼主| 发表于 2010-2-24 10:51:06 | 显示全部楼层
Posted 31 Jan 2010 13:07:52 UTC - in response to Message 102302.
Last modified: 31 Jan 2010 13:11:41 UTC                                    
Can you tell us anything about it yet:  S5R7 or S6R1?  Similar to the current run, or significant differences?

The data taken in S6 so far is actually noisier than what we have of S5, so we'll stick to S5 data for now.

S6采集到的数据还不太好,所以还是继续处理S5的数据。

We're working on a new program that will combine a new, fasterimplementation of the FStat calculation with a new method called'Global Correlation Transform' that will supersede the 'HoughTransform' used in the current HierarchicalSearch, resulting in themost sensitive search for continuous signals that we know, and stillrequiring much less computing power for the same parameter space.

新算法,灵敏度更高,需要的计算也少。

We work on turning the program into a reliable BOINC application and onsetting up a search design (i.e. how to split up the parameter spaceinto workunits), which will result in a new workunit generator andpossibly new data files.

With luck, we'll have that ready by the time we run out of S5R6 work.If we aren't, we'll insert a short run with the same application anddata as we used on S5R5 and S5R6, but looking into higher frequencies.S5R5 went up to 1kHz, S5R6 covered 1kHz to 1.2kHz, the current datafiles allow to search up to 1.5kHz.

快的话S5R6结束的时候新程序就会出来了,慢的话,继续按S5R5(-> 1khz)、S5R6(-> 1.2khz)的思路往上延伸搜索频率(最多允许到1.5khz)。

BM
回复

使用道具 举报

 楼主| 发表于 2010-2-24 10:53:35 | 显示全部楼层
Posted 10 Feb 2010 9:41:38 UTC
Last modified: 10 Feb 2010 11:26:12 UTC                                    Wefound that setting up a search (data, workunits) for the new code ispretty difficult given the little experience we do have with it. Somost liekely we'll have a short (~2 month) "engineering run" with acode that combines the new GCT with the "traditional" FStat code,analyzing the whole S5 data (first half was used in S5R1-3, second halfin S5R4-6), and looking at a parameter space that has already beencovered (partly) by S5R3 and S5R5, so we can compare the results andget a better feeling for the workunit setup.

BM

刚开始两个月测试运行,综合使用新旧算法,分析整个s5的数据,并和s5r3/s5r5的结果进行比较,以最终确定新算法的实现方式。
回复

使用道具 举报

 楼主| 发表于 2010-3-16 09:42:14 | 显示全部楼层
Posted 7 Mar 2010 21:09:54 UTC

Not much news. The run will probably be named S5GCE (S5 data Global Correlation Engineering run) and preparation and testing is underway internally. Looks like we're well in the plan. At current processing rate S5R6 will run out of (new) work on March 18th, we should be able to run the first larger tests on the main project around the next weekend.

BM

新的测试阶段名称是S5GCE,准备工作已经在内部开展,看上去应该不会有啥大问题,然后S5R6的任务应该会在18号结束,我们大概在下周就会开始运行新的测试阶段。
回复

使用道具 举报

 楼主| 发表于 2010-3-16 09:42:25 | 显示全部楼层
Posted 12 Mar 2010 16:52:21 UTC
Last modified: 12 Mar 2010 17:01:39 UTC

Testing is underway.

内部测试仍在继续。

Applications are currently x86 only. I think we will continue to suppoert Mac OS X PPC, but the Apps for this platform might be delayed by a few days.

目前只有x86的计算程序,我想我们应该会继续支持Mac OSX PPC,但是可能要晚个几天。

For this run we'll use the database for 'locality scheduling' communication between workunit generator and scheduler, instead of the communication files being used up to S5R6. AFAIK E@H is the only project using locality scheduling, so though being a medium change this doesn't affect other projects. In the mid term this should improve the overall speed of locality scheduling and the handling of data files both on the server and client side. This changes is currently giving us most of the headache.

这个阶段我们针对 locality scheduling (我们是唯一一个使用该特性的项目)将使用数据库来代替原来的文件通讯方式,新方式应该可以提高调度服务器的整体运行效率。

BM
回复

使用道具 举报

 楼主| 发表于 2010-3-17 11:44:12 | 显示全部楼层
Posted 16 Mar 2010 8:26:17 UTC

We stumbled over a major problem with our new Windows S5GCE App. Looks like that we'll run out of S5R6 work before we can start S5GCE, i.e. for some days we will send out only ABP work.

BM

S5GCE的windows程序开发上碰到点问题,因此在S5R6的任务跑完之后的几天里大家将会只能拿到ABP的任务。
回复

使用道具 举报

 楼主| 发表于 2010-3-19 09:09:55 | 显示全部楼层
Posted 18 Mar 2010 16:02:19 UTC

Originally we planned to generate just a few S5GCE tasks and then wait until they were reported back.

本来是准备只生成少量用于测试目的的S5GCE任务。

However the project behaved quite sluggish after we ran out of S5R6 work, so we decided to issue S5GCE work right away to keep the client busy and stop them from hammering on the server.

然而在S5R6的任务跑完后项目服务器的负载太重,因为大家的机器都在请求新任务,所以我们决定现在就正式发布S5GCE的任务。

The Application had been tested as far as we could on the test project, but not yet 'in the wild' where it could behave quite differently.

虽然这个计算程序我们已经进行足够多的内部测试,但正式放出来可能还是会碰到些新问题的。

BM
回复

使用道具 举报

 楼主| 发表于 2010-3-19 09:11:51 | 显示全部楼层
现在服务器的反应还是慢,虽然已经拿到两个新的任务,但任务文件下载很成问题,从下载列表看有新的数据文件,名称中包含S5R7字样,而且都有对应的S5R4数据文件。
回复

使用道具 举报

 楼主| 发表于 2010-3-19 22:14:01 | 显示全部楼层
S5GCE的任务大概占150M的内存,似乎比原来稍多点,然后在T5600上预计是16小时左右完成。
回复

使用道具 举报

发表于 2010-3-20 15:21:25 | 显示全部楼层
新的'locality scheduling'特性

什么东西啊?
回复

使用道具 举报

 楼主| 发表于 2010-3-20 16:18:09 | 显示全部楼层
我也不太清楚现在是啥意思,感觉上这个是原来就有的:大概就是说客户端从服务端请求任务时,要参照本地的项目数据文件情况,因为e@h的数据文件可以在多个wu之间共享,这样的话可以减少数据文件下载量。
回复

使用道具 举报

 楼主| 发表于 2010-3-20 16:20:02 | 显示全部楼层
哦,刚才再仔细看了下原文,是我翻译错了,8好意思啦~~

不是新的特性,只是说这个特性在服务端的实现方式有变化,原来是通过文件,现在是通过数据库。。。
回复

使用道具 举报

发表于 2010-3-21 08:45:06 | 显示全部楼层
现在的一个任务比原来时间变长了
回复

使用道具 举报

 楼主| 发表于 2010-3-21 09:16:03 | 显示全部楼层
嗯,据说项目方刚提高了每个任务包的得分,因为原来没预料到计算时间的增加
回复

使用道具 举报

发表于 2010-3-21 20:42:52 | 显示全部楼层
我算了两个,都刚好用了 10 小时。原来的包大概在 7 ~ 10 小时之间波动。
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 新注册用户

本版积分规则

论坛官方淘宝店开业啦~
欢迎大家多多支持基金会~

Archiver|手机版|小黑屋|中国分布式计算总站 ( 沪ICP备05042587号 )

GMT+8, 2024-4-29 14:27

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

快速回复 返回顶部 返回列表