pencat

从明天起,关心粮食和蔬菜。我有一所房子,面朝大海,春暖花开

Logging in to RuneScape makes crops take longer to grow

引用: http://seanv.info/2007/farming_timers.html

In RuneScape, the act of logging in affects how long your crops take to grow. Specifically, it makes them take longer to grow.

Hypothesis: When you log in the timers on your patches are reset.

(The experiment supporting this article was done on Thu 11 May 2007 GMT; earlier or later experiments may yield different data if RuneScape’s code and/or constants were different from those running at the time of this experiment.)

Motivation

What got me thinking about this was the way herbs sometimes took a lot longer to grow than I’d anticipated. In a preliminary experiment, similar to the one documented below but with watermelons and ranarr weed, the watermelon took a full ten minutes to grow after logging in and the ranarr twenty minutes.

A bit of background: the patch timers

As you are probably aware if you’ve tried the Farming skill in RuneScape, crops grow in discrete stages. Each type of patch has a timer associated with it which, when it runs out, triggers a ‘grow event’.

I measured the time between grow events for the allotment/herb/flower set of patches:

Length of timers
Patch type Approx length 
(minutes)
Flower patch 5
Allotment 10
Herb patch 20

(The timers seem to run a few seconds longer than these times. E.g. I measured times of 5:05 and 5:09 for flower patches.)

For at least some (and in my opinion probably all) of the different types of patches the timers are synchronised. I observed (as many farmers probably will have) that herb patch grow events occur simultaneously with every second allotment grow event.

The experiment: observation of effect of logging in on timing of grow events

The plan:

  • Plant a limpwurt seed and water it
  • Watch for grow events and record the time of each
  • Log out and then quickly log back in while the limpwurt’s growing
  • See what affect this has on the timing of the grow events

The flower patch south of Falador was used.

Log of experiment
Time 
(hh:mm:ss)
What happened
02:12:21 Limpwurt planted
02:12:37 Limpwurt grew
02:17:42 Limpwurt grew
02:22:00 Logged out
02:24:00 Logged in (pressing the Login button)
02:24:02 Welcome to RuneScape screen displays
02:29:11 Limpwurt grew. (It is now fully grown)

Logging out extended the period between the second and third grow events. The third grow event occurred about five minutes after logging back in. This is the evidence presented in support of this article’s hypothesis.

Length of time to fully grow crops

(How long crops take to fully grow wasn’t the principal data the experiment was designed gather. I’m including here some of the reliable data I got in order to be able to illustrate the effect of logging in on crops’ maturation times.)

Time required for full growth of crops
Crop Patch Nr of grow events reqd
for maturity
Maturation time
Type Time between 
grow events
Min Max*
Ranarr herb 20 4 60 80
Limpwurt flower 5 3 10 15

(All times in minutes.)

(*If the outcome of any of a crop’s grow events is disease or don’t grow this time then the maximum maturation time may be longer than the figures in this column.)

Consequences for farmers

If you want your crops to grow as quickly as possible:

  • stay logged in continuously, or
  • if you log out, do not log back in until you know your crops will be fully grown.

Admittedly, I neither strive to make my crops grow as quickly as possible nor do either of these things. These suggestions might apply, say, to someone trying to get the maximum rate of farming experience.

The situation is interesting for crops which take a long time to grow, e.g. trees. I expect for normal or fruit trees the time between grow events is considerably longer, for otherwise fruit trees would have a large number of different stages of growth, which is not what I have observed. In fact I notice Maxromulan has said that fruit tree patch grow events occur every four hours. Now

4 hr = 240 min = 12 x 20 min

so perhaps fruit tree patch grow events are synchronised with every twelfth herb patch grow event. If logging in actually does reset a four hour timer, each login could lengthen the time to maturity of fruit trees by up to four hours, two hours on average if the time you spend logged on is completely random (whatever that means).

Further investigations

What about the other types of crop (trees, calquats, etc., etc.)? Their patch timers are quite a bit longer than 20 minutes. Does logging in completely reset the timer? I don’t know, but I may attempt to experiment to find out and if I do I’ll post the results here.

Acknowledgements and references

Thanks to Maxromulan for sharing some snippets of her farming knowledge in a thread on theRuneScape Rants forum. After I noticed that something interesting was happening with the farming timers, her thread confirmed it for me and encouraged me to investigate further. One of Maxromulan’s posts alerted me to the fact that there is a random chance that the outcome of a grow event is ‘don’t grow this time’. Thanks also to Luciferzero0 for his/her posts on that thread, in one of which he or she states the hypothesis of this article.

This document was originally written on 13 May 2007 GMT and was most recently updated on 22 May 2008.

 

 

 

狗样花猫

IMAP与MAILDROP造成的邮件服务器IO占用过高

 最近几周,用户经常抱怨邮件服务器慢,连不上,邮件发不出去。

 

写了几个监控脚本,对CPU,交换分区,硬盘使用率,进程等情况做了监视。 得到以下结论:

imap和maildrop引起的系统IO阻塞,是造成故障的主要原因。

imap 在大量用户的情况下本身就是瓶颈。 目前常规在线人数在100左右,邮件使用高峰期 IO的使用率是100%。 所以考虑换回POP3。

maildrop 主要是设置问题,之前没有限制最大进程数,群发的时候会启动1xxx个进程,而且都是读写硬盘的,所以要限制maxproc。

在master.cf里

 

maildrop  unix  -       n       n       -       -       pipe

  flags=DRhu user=vuser argv=maildrop -w 90 -d ${user}@${nexthop} ${recipient} ${user} ${extension} {nexthop}

改为

 

maildrop  unix  -       n       n       -       21       pipe

  flags=DRhu user=vuser argv=maildrop -w 90 -d ${user}@${nexthop} ${recipient} ${user} ${extension} {nexthop}

maxproc改成21,基本上不会太卡
 
 
 
尽管做了以上设置,但磁盘IO效率还是存在问题。 下一步准备把ext3换成reiserfs。 如果还是不成的话,那就只能上NAS了 。
 
 
EOF
 

 

 

Android Dev Phone 1

CIMG0397

CIMG0398

 

这键位基本能够满足所有linux操作需求. 很强大

CIMG0399

 

这个滚轮和黑莓很象

CIMG0403

 

USB充电口. 那个小孔应该是MIC, 我差点当成RESET......

CIMG0404

 

相机钮, 感觉用处不大

CIMG0409

 

音量钮

CIMG0410

 

我的最爱..后面的图案很迷人

CIMG0405

 

尤其是这个机器人 ;-)

CIMG0406

 

G1键盘滑出的方式很特别 下面一组图可以看出滑动路线

CIMG0411

CIMG0412

CIMG0413

CIMG0414

 

特别的代价就是磨损严重....我才用了几天啊

CIMG0415

 

G1 VS P4550

CIMG0407 

CIMG0408

comiclrf的改良

买505的目的非常明确, 看漫画.  在505未到之前就开始研究漫画的转换. 很多工具都可以转, 十分完美的几乎没有. 
comiclrf算是比较不错的. 但也有几个缺陷.
1. 不支持中文, 要用其他软件再改名.
2. AB页顺序错位, 需要用comic2psp先转换一次. 美版漫画是从左向右看. 作者没考虑到扫描版用户啊.
3. 转换后体积偏大
4. 转换速度慢
5. rar, zip 文件需要改名后才能转换.  图象文件要先压缩.
问题不大, 但是漫画多了实在有点吃不消. 所以我在2.4版的基础上进行改良.
1,2,5 已经修正.
3,4 是因为comiclrf把图象都转成了gif格式. 大概是想锐化吧. 所以体积要比转换前大好多.  速度慢也可以理解了.  这个问题还未调整, 正在考虑一个新的锐化算法。 做好之后再放上来.

 

Download

505扫盲结束

不务正业一整天, 总算对505有了初步的了解. lrf的文件格式. 中文化方法. 漫画的转化.  该准备的都准备好了. 就等机器到手开始折腾..

lrf cover tools

1. lrf2lrs     http://blog.bigcomic.com/upload/lrf2lrs_03.zip

    lrf to lrs .  python写的小工具

2. pylrs      http://blog.bigcomic.com/upload/pylrs-1.0.0.zip

    python模块, 可以生成lrf

History of LRF format

The LRF format is a proprietary format by Sony used in their e-readers.The format is still undocumented. Many efforts were done by enthusiasts to understand the format and to make utilities for LRF conversion since appearing Sony Librie (Japaneese version) reader on the market. This review is my personal vision of the history and is limited to the resources I used in my work. LRF conversion is rapidly growing area of the content generation development (inspired by new Sony Reader PRS-500). There are several other resources and wiki pages devoted to the LRF format and tools for conversion; the goal of this page is a review of major achievements for the beginners. This section reflects works done before February 2007, some links may not work. I'm not going to update this page for new resources, please visit forums listed in the Link section for up-to-date information.

 

The goal of this page is to provide a reference to the programs that can be used for understanding the LRF format, the program listed here are not the only (and not necessarily the best) way to make lrf content.

 

Formats

 

LRF format. This BINARY format used in Sony Librie and Sony PRS-500 Readers. The format is barely documented. Some very limited information can be found at http://www.sven.de/librie/Librie/BBeB . The LRF format can be understood with the python code of lrf2lrs converter and utilities for extracting the objects from LRF files (see below). The LRF can contain text or images, the ability to show images sometimes used by homemade programs with the reference to "picture" LRF (actually this is just simple implementation of one of the features of LRF format).

 

LRS (Librie Reader Source) format. LRS is a "source" XML format with the description for the objects used in LRF. This format was introduced in the Book Creator program (commercial program with Japanese interface) by Canon (see below). The format is documented: http://www.y-adagio.com/public/committees/iec_pt62448/1_np(0509)/100_1017e_DC.pdf . LRS files can be generated by either 3 ways: 1) with commercial Book Creator program by Canon; 2) with freeware Book Designer program (see below for more details) 3) with Python lrf2lrs converter by roxfan, Igor Skochinsky and several newly developed utilities available at www.mobileread.com.

 

BBeB "Broadband ebook" format by Sony. Another name of LRF and, sometimes, LRS formats.

 

Programs useful for understanding the LRF format

 

Major programs for understanding the LRF format, listed by date:

 

1. Book Creator Commercial program by Canon. First mentioned in yahoo Librie group in June 2004, see post #18). The program has Japanese interface. Since that time the development of homemade LRF content was started. First, many affords were done to make English version of Book Creator (see Librie yahoo group); Second, some homebrew programs use XYLogParser.dll (with Lrs2lrf wrapper by roxfan) to create LRF files from LRS source; Third, reverse engineering of LRF format was started to develop programs independent from XYLogParser.dll.

 

2. Makelrf program by scythic (first introduced in yahoo librie group in October, 2004). The program comes with C-code and available in the File section of Librie group. The program allows to create Lrf files from the text files with support of the images. The program cannot create rich lrf files (only basic objects are supported), but it is hard to underestimated the progress archived with the program. Till now makelrf is widely used in many other programs as an engine for creation either simple text LRF or image-based LRF. Until recently makelrf was used in BookDesigner program (in "simple" conversion mode); and JAP programs to generate image-based LRFs.

 

3. LRFParser by roxfan (yahoo Librie group, November 2004, comes with C-source). The program decompiles LRF files to the objects, including TOC, header and compressed streams. To my knowledge, LRFparser is the first program where complex LRF objects and majority of tags were understood.

 

4. lrf2lrs (first version signed by roxan, February 2006; yahoo Librie group); the latest versions (signed by roxfan, Igor Skochinsky) are available at www.mobileread.com (Sony Portable Reader - Reader Developer's Corner - Lrf2Lrs thread, posts by igorsk). (I believe that roxfan=Igor Skorchinsky=igorsk). With the program the LRF files can be converted to the LRS files. Up to date the source of this Python program is the major source of information on LRF objects and tags. Almost all possible LRF objects and tags are supported by the program.

 

5. LRFunpack (by me, available at download section of this site, November 2006). NET2.0 C# application for extracting objects from LRF files with some translation of the tags and description of the streams. Creates both dump hex files for each of the object together with the text files with some decryption. I was using this program to understand the LRF format. The advantage of this program - it never stops decompiling even if tag is unknown. Some example of decompiled lrf can be found at download section. Sorry, no source available.

 

-----------

 

I did not mention Java tools, because I never tried them myself. Please have a look at the forums of the sites listed in the Link section. I believe the most significant contributions are flatLrf (http://monalipse.sourceforge.jp/tmp/lrf/, January 2005) and LRFParser.java (by Scotty1024, May 2005, Librie yahoo group). FlatLrf is Java application to create lrf from html files; LRFParser.java is Java version of LRFParser by roxfan.

 

BookDesigner (Wiki page) (by Valerii Woizechovsky (aka vvv))). This program is an universal program for conversion between many formats, reading and ebook creation. The program creates LRS file, than the LRS file is converted to LRF with external third-party converters (makelrf, lrs2lrf , LRSparser by AlexXF, the latest version uses my MSH_Lrsparser). The strong side of the BookDesigner for understanding the LRF format is ability to generate custom LRS together with corresponding LRF file for further analysis.

 

LRF conversion utilities

 

Please refer to the Wiki page and the link section for recent progress on content generation. Recently Sony launched site for the developers at www. prslabs.com. Unfortunately there is almost no new information. The LRS format specification is given (the one mentioned above), the XYLogParser.dll (almost the same to the discussed above, it is also very slow), and the description of the interface around the XYLogparser.dll.

 

 

Lrf file format

A LRF file consists of a header, a number of objects and an object index. All values are in Intel (LSB first) order.

 

Header

Offset (hex) Size(bytes) Name/meaning Example value
0 8 LRF Signature 4C 00 52 00 46 00 00 00 = "LRF" in Unicode
8 2 version? 999 in most files
A 2 "Psuedo-Encryption" key byte 48
0C 4 RootObjectID 0x0044
10 8 NumberOfObjects 342
18 8 ObjectIndexOffset 0x00093440
20 4 unknown 0
24 1 Flags (16 - back to front, 1 = front to back) 16
25 1 unknown (padding?) 0
26 2 unknown 1600
28 2 unknown (padding?) 0
2A 2 Height? 600
2C 2 Width? 800
2E 1 unknown 24
2F 1 unknown (padding?) 0
30 0x14 unknown zeroes
44 4 Object ID of only PlaneStream (0x1E) object 0x0042
48 4 unknown 0x1536
4C 2 XMLCompSize 0x035C

Next two fields are only present if version>=800.

4E 2 unknown 0x0014
50 4 GifSize 0x03F2

Immediately follows the compressed XML metainfo, of size XMLCompSize. First dword of it is the size of uncompressed data, the rest is zlib compressed unicode XML.

If version>=800, the gif thumbnail follows, of size GifSize.

 

Object index

Offset to the index is specified by the ObjectIndexOffset in the header, and number of entries is NumberOfObjects.

Each index entry has the following layout:

Offset (hex) Size(bytes) Name/meaning Example value
00 4 id 0x32
04 4 offset 0x07B0
08 4 size 0x44
0C 4 reserved? 0

 

Objects

See LrfObject [http://buycialis.cc(approve sites) buy cialis online] [http://buycialis.cc(approve sites) buy cialis] http://buycialis.cc buy cialis online(approve sites)

file format

http://en.wikipedia.org/wiki/Alphabetical_list_of_file_extensions#L

分页:[«]2[3][4][5][6][7][8][9][10][11][12][13][14][15][16][»]

Powered By Z-Blog 1.8 Devo Build 80201

Copyright © 1998-2007 bigcomic.com All rights reserved.