乐于分享
好东西不私藏

考研英语外刊:用AI搞科研可以吗

考研英语外刊:用AI搞科研可以吗
Hello,大家好!我是积木。
来了一些新朋友,所以我先自我介绍一下:我是上外英语本科,22年考研京区英一85分,去年刚刚硕士毕业。去年又去考了次研,京区英一83分。所以,我是科班出身,既懂英语,又懂应试,很高兴能陪伴大家一起备考。
新学期开始,27年考研备考随之启动,我们的外刊陪伴旅程也不期而至
按照往年的惯例,今年考研时间应该在12月19日、20日,从今天算还有203天
我承诺,在未来的203天,每天都有一篇文章在等着你。
今年的公众号由我亲自操刀,没有花哨的排版,把省下来的时间,都拿来提供额外的备考服务。我会在每天上午10点发布文章,每篇文章都会选择一个单词或者一个长难句进行拆解,并参照考研英语命题规律出一道仿真模拟题,答案会公布在评论区中。欢迎大家在评论区留言打卡。
我会拉一个群,欢迎大家加入,有关考研英语备考的问题,可以随时交流提问。我的微信号是jim_jimu
好啦,我们还有很多时间可以相互认识,旅途正式开始:

今天的文章,选自2026年5月24日的《自然杂志》。Why AI cannot do good science without humans

Does humanity need science? The Nobel prizewinner Max Perutz posed this question in a landmark essay1 in 1989. His conclusion, unsurprisingly, was yes. Had he lived to see the era of artificial intelligence, he might have inverted his framing of the question: does science need humanity?

Two studies in Nature provide a glimpse of what some are interpreting as humanitys shrinking role in scientific discovery in Perutzs own field, molecular biology. Both describe a pivotal step towards truly AI-driven drug discovery, in which a system of connected AI agents is trained to autonomously navigate multi-step workflows. The system trawled scholarly literature, formed hypotheses, interpreted data and engaged in internal debate to arrive at candidate drugs to treat a particular disease.

The results are impressive, but also highlight something else: AI scientists can and should empower human researchers. They cannot and should not replace them.

In one study, a team based at FutureHouse, a non-profit AI research laboratory in San Francisco, California, asked its AI system, called Robin, to find a treatment for the eye disorder dry age-related macular degeneration2. Robins agents searched the scientific literature to derive a therapeutic strategy, identified candidate molecules and selected assays to test them. The experiments Robin suggested were then handed over to humans, who conducted the studies and fed the results back to Robin for analysis, interpretation and the design of follow-up studies. The team estimates that Robin reduced the time needed for the project 200-fold compared with a typical human workflow.

A second group led by researchers at Google, based in Mountain View, California, used its AI-agent system, called Co-Scientist, to look for approved drugs that could be repurposed to treat a form of leukaemia, and to discover drug targets to treat liver fibrosis3. Humans provided input throughout the process, helping to prioritize hypotheses and approaches. The team also asked the agents to develop a hypothesis to explain why many species of bacterium share a particular suite of antibiotic-resistance genes. Scientists, including some of the projects authors, had been investigating this microbial puzzle for around a decade, but had not yet published the results. Co-Scientist arrived at the same hypothesis as the researchers — within days.

These projects represent a significant step forwards. But for all the wow’ factor, it is crucial to bear in mind that the AI systems were not working alone. In both cases, humans framed the initial project, performed experiments, offered guidance and checked the agents’ output along the way. That is a feature, not a bug — and shutting humans out of the loop would not be easy.

For one thing, the creation of a fully autonomous AI researcher would require many more AI agents to be cross-linked, and scientists would need to ensure that those agents could maintain focus and coordinate efficiently with one another during long, complex tasks4,5. It is also not yet clear whether AI agents would be able to master every step of the process of drug development. Even if they could, human oversight would still be needed to catch hallucinations (AI data fabrication) and misinterpretations, and to ensure that certain tasks are done correctly — for example, that the data AI harvests from databases for its analyses are used appropriately.

More broadly, the expertise of researchers, and the accumulated wisdom of teams that have worked on a problem, perhaps for decades, might prove impossible for machines to replicate. Humans are also needed to train future generations, and their knowledge is built, in part, on lessons learnt from failures and inefficient meanderings. Human messiness, curiosity and playfulness have fuelled countless discoveries, and helped to inform societys ethical frameworks. AI systems might offer greater efficiency in some instances, but we dont yet know whether greater efficiency equates to greater insight.

These caveats should be borne in mind as society argues over competing visions of how AI should fit into the future. Some researchers see in AI tools a path to accelerated discovery, relief from the tedium that comes with much day-to-day lab work and a faster, cheaper way to create medicines and make other discoveries. Others see a future in which scientific literature is polluted with slop, human scientists cannot find suitable training or work, and research is untempered by human empathy, ethics and wisdom.

Scientists should not allow a negative view of AI to drive them away from exploring the possibilities that AI co- scientists might hold for research. Equally, however, they must rise above the din of AI hype and advocate for their own importance — to remind the wider public, funders and fellow researchers that science still needs humanity, and that not every grant proposal need include an AI project.

Perutz began his essay with a false dialectic that also plagues many modern discussions of AI: Is scientific research the noblest pursuit of the human mind, from which springs a never-ceasing stream of beneficial discoveries, or is it a sorcerers broom that threatens us all with destruction?. These opposing extremes, both true in their own way, should not be allowed to distort AIs true potential — or obscure its limitations.

读到这里,请大家做一道考研英语阅读仿真模拟题:

It can be inferred from the passage that AI systems in scientific research _______.

[A] are capable of conducting independent and flawless drug development

[B] fail to match human researchers in experiential and cognitive depth

[C] will eventually replace human labor in tedious laboratory work

[D] have fully unlocked their potential in cross-disciplinary scientific research


第二遍,我带上翻译,形成英中对照译文,大家可以再读一遍,充分查漏补缺:

Does humanity need science? The Nobel prizewinner Max Perutz posed this question in a landmark essay1 in 1989. His conclusion, unsurprisingly, was yes. Had he lived to see the era of artificial intelligence, he might have inverted his framing of the question: does science need humanity?

人类离不开科学吗?诺贝尔奖得主马克斯·佩鲁茨在1989年一篇里程碑式的论文中提出了这个问题。不出所料,他给出的答案是肯定的。倘若他能活到人工智能时代,或许会调转问题的发问角度:科学离不开人类吗?

Two studies in Nature provide a glimpse of what some are interpreting as humanitys shrinking role in scientific discovery in Perutzs own field, molecular biology. Both describe a pivotal step towards truly AI-driven drug discovery, in which a system of connected AI agents is trained to autonomously navigate multi-step workflows. The system trawled scholarly literature, formed hypotheses, interpreted data and engaged in internal debate to arrive at candidate drugs to treat a particular disease.

《自然》刊发的两项研究,让人们窥见在佩鲁茨深耕的分子生物学领域,人类在科研发现中的作用正日渐弱化。两项研究均展现了全人工智能驱动药物研发的关键进展:一套互联互通的智能AI程序经过训练后,可自主完成多环节研发流程。该系统检索学术文献、提出研究假说、解析实验数据,并通过内部推演论证,筛选出用于特定疾病治疗的候选药物。

The results are impressive, but also highlight something else: AI scientists can and should empower human researchers. They cannot and should not replace them.

相关成果亮眼,但也点明了关键事实:人工智能科研工具能够、也应当赋能科研人员,却无法、也不该取代人类研究者。

In one study, a team based at FutureHouse, a non-profit AI research laboratory in San Francisco, California, asked its AI system, called Robin, to find a treatment for the eye disorder dry age-related macular degeneration2. Robins agents searched the scientific literature to derive a therapeutic strategy, identified candidate molecules and selected assays to test them. The experiments Robin suggested were then handed over to humans, who conducted the studies and fed the results back to Robin for analysis, interpretation and the design of follow-up studies. The team estimates that Robin reduced the time needed for the project 200-fold compared with a typical human workflow.

其中一项研究由美国加州旧金山非营利人工智能实验室未来之家团队完成,研究人员依托名为罗宾的人工智能系统,寻找干性老年性黄斑病变的治疗方案。罗宾智能程序查阅海量科研文献,敲定治疗思路、筛选候选分子、选定配套体外检测方案。罗宾给出的实验方案交由科研人员落地实操,实验结果再回传给人工智能,由其完成数据分析、结论研判以及后续实验规划。研究团队测算,相较传统全人工研发模式,罗宾将项目研发周期缩短至原先的二百分之一。

A second group led by researchers at Google, based in Mountain View, California, used its AI-agent system, called Co-Scientist, to look for approved drugs that could be repurposed to treat a form of leukaemia, and to discover drug targets to treat liver fibrosis3. Humans provided input throughout the process, helping to prioritize hypotheses and approaches. The team also asked the agents to develop a hypothesis to explain why many species of bacterium share a particular suite of antibiotic-resistance genes. Scientists, including some of the projects authors, had been investigating this microbial puzzle for around a decade, but had not yet published the results. Co-Scientist arrived at the same hypothesis as the researchers — within days.

另一项研究由加州山景城的谷歌科研团队牵头,团队使用协同科学家人工智能系统,筛选已上市老药的新用途以治疗某类白血病,同时挖掘抗肝纤维化的新药靶点。全研发流程中人类持续参与,协助筛选优先级更高的研究假说与实验路径。科研人员还委托该人工智能破解一道微生物难题:为何多种细菌携带同一组耐药基因。包括部分论文作者在内的科学家耗时近十年钻研该问题,始终未能发表定论,而协同科学家仅用数日,就得出了和人类研究者完全一致的假说。

These projects represent a significant step forwards. But for all the wow’ factor, it is crucial to bear in mind that the AI systems were not working alone. In both cases, humans framed the initial project, performed experiments, offered guidance and checked the agents’ output along the way. That is a feature, not a bug — and shutting humans out of the loop would not be easy.

上述两项研究堪称重大突破。尽管成果令人惊叹,但我们必须认清:人工智能从未独立完成全部科研工作。两项实验中,从项目立项、落地实验,到全程指导、核验人工智能输出结果,均离不开人类参与。人类介入是这套研发体系的固有优势,而非设计缺陷,想要彻底把人类排除在科研链路之外并不现实。

For one thing, the creation of a fully autonomous AI researcher would require many more AI agents to be cross-linked, and scientists would need to ensure that those agents could maintain focus and coordinate efficiently with one another during long, complex tasks4,5. It is also not yet clear whether AI agents would be able to master every step of the process of drug development. Even if they could, human oversight would still be needed to catch hallucinations (AI data fabrication) and misinterpretations, and to ensure that certain tasks are done correctly — for example, that the data AI harvests from databases for its analyses are used appropriately.

一方面,打造完全自主运行的人工智能科研主体,需要海量智能程序互联互通,科研人员还要保障各类程序在漫长繁复的科研任务中保持研究方向、高效协同。现阶段尚无法证实人工智能可以吃透药物研发全流程的所有环节。即便未来实现,也仍需人类全程监管,排查人工智能产生的信息臆造与数据误读问题,保障各项操作合规,比如规范人工智能调取数据库数据开展分析的使用边界。

More broadly, the expertise of researchers, and the accumulated wisdom of teams that have worked on a problem, perhaps for decades, might prove impossible for machines to replicate. Humans are also needed to train future generations, and their knowledge is built, in part, on lessons learnt from failures and inefficient meanderings. Human messiness, curiosity and playfulness have fuelled countless discoveries, and helped to inform societys ethical frameworks. AI systems might offer greater efficiency in some instances, but we dont yet know whether greater efficiency equates to greater insight.

从更广的层面来看,科研人员的专业积淀、科研团队耗费数十年攻关积攒的经验智慧,是机器难以复刻的。科研传承同样依托人类实现,人类的知识体系,一部分源自一次次失败与曲折摸索总结的教训。人类不拘一格的思维、与生俱来的好奇心与探索欲,催生了不计其数的科研突破,也助力搭建起社会伦理准则。人工智能固然能在部分场景提升效率,但高效率未必等同于更深邃的科研洞见。

These caveats should be borne in mind as society argues over competing visions of how AI should fit into the future. Some researchers see in AI tools a path to accelerated discovery, relief from the tedium that comes with much day-to-day lab work and a faster, cheaper way to create medicines and make other discoveries. Others see a future in which scientific literature is polluted with slop, human scientists cannot find suitable training or work, and research is untempered by human empathy, ethics and wisdom.

当下社会围绕人工智能的未来定位争论不休,上述短板值得各方谨记。一部分科研工作者认为人工智能可以提速科研进程,把科研人员从枯燥重复的日常实验里解放出来,以更低成本、更快速度研发新药与新成果;另一部分人则担忧未来科研乱象丛生:劣质AI文稿泛滥污染学术期刊、科研人员失业断档,科研项目失去人性温度、伦理约束与人文智慧的把控。

Scientists should not allow a negative view of AI to drive them away from exploring the possibilities that AI co- scientists might hold for research. Equally, however, they must rise above the din of AI hype and advocate for their own importance — to remind the wider public, funders and fellow researchers that science still needs humanity, and that not every grant proposal need include an AI project.

科研人员不必因片面否定人工智能,就放弃探索人工智能协同科研的潜力;但与此同时,科研从业者也要跳出人工智能炒作热潮,立足自身不可替代的价值发声,向公众、科研资助方和同行阐明:科学发展依旧离不开人类,科研基金项目不必强行捆绑人工智能课题。

Perutz began his essay with a false dialectic that also plagues many modern discussions of AI: Is scientific research the noblest pursuit of the human mind, from which springs a never-ceasing stream of beneficial discoveries, or is it a sorcerers broom that threatens us all with destruction?. These opposing extremes, both true in their own way, should not be allowed to distort AIs true potential — or obscure its limitations.

佩鲁茨在论文开篇抛出一组非黑即白的二元论调,如今这类偏激观点也裹挟着人工智能相关讨论:“科学研究究竟是人类心智最高贵的追求,源源不断催生造福人类的发明,还是巫师的扫帚,终将给全人类带来灭顶之灾?”两种极端看法各有依据,但不能用它们歪曲人工智能的真实潜力,或是无视其与生俱来的局限


最后,让我们一起学习一个语言点:shut sb out of the loop

loop = 圆环、闭环,科研里引申为「工作闭环、流程链路」

shut out = 隔绝、排除在外

直译:把某人关在闭环外面

考研释义:将某人排除在核心工作环节之外,不让参与关键流程

原句:That is a feature, not a bug — and shutting humans out of the loop would not be easy.

翻译:人类参与是体系优势而非缺陷,想要把人类彻底剔除出科研全流程很难。

文章通篇观点:AI只能辅助科研,没法把人类踢出科研闭环。


    好啦,今天的文章就到这里啦。

    明天,我们不见不散!

    基本 文件 流程 错误 SQL 调试
    1. 请求信息 : 2026-06-06 10:37:40 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/719361.html
    2. 运行时间 : 0.203387s [ 吞吐率:4.92req/s ] 内存消耗:4,602.63kb 文件加载:145
    3. 缓存信息 : 0 reads,0 writes
    4. 会话信息 : SESSION_ID=540b38f31b3fa9a28ec244b82e802d9f
    1. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/public/index.php ( 0.79 KB )
    2. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/autoload.php ( 0.17 KB )
    3. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_real.php ( 2.49 KB )
    4. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/platform_check.php ( 0.90 KB )
    5. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/ClassLoader.php ( 14.03 KB )
    6. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_static.php ( 6.05 KB )
    7. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper.php ( 8.34 KB )
    8. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/helper.php ( 2.19 KB )
    9. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/ralouphie/getallheaders/src/getallheaders.php ( 1.60 KB )
    10. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/helper.php ( 1.47 KB )
    11. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/stubs/load_stubs.php ( 0.16 KB )
    12. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Exception.php ( 1.69 KB )
    13. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Facade.php ( 2.71 KB )
    14. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/deprecation-contracts/function.php ( 0.99 KB )
    15. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap.php ( 8.26 KB )
    16. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap80.php ( 9.78 KB )
    17. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/Resources/functions/dump.php ( 1.49 KB )
    18. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-dumper/src/helper.php ( 0.18 KB )
    19. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/VarDumper.php ( 4.30 KB )
    20. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions_include.php ( 0.16 KB )
    21. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions.php ( 5.54 KB )
    22. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/App.php ( 15.30 KB )
    23. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Container.php ( 15.76 KB )
    24. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/container/src/ContainerInterface.php ( 1.02 KB )
    25. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/provider.php ( 0.19 KB )
    26. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Http.php ( 6.04 KB )
    27. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Str.php ( 7.29 KB )
    28. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Env.php ( 4.68 KB )
    29. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/common.php ( 0.03 KB )
    30. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/helper.php ( 18.78 KB )
    31. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Config.php ( 5.54 KB )
    32. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/alipay.php ( 3.59 KB )
    33. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Env.php ( 1.67 KB )
    34. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/app.php ( 0.95 KB )
    35. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cache.php ( 0.78 KB )
    36. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/console.php ( 0.23 KB )
    37. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cookie.php ( 0.56 KB )
    38. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/database.php ( 2.48 KB )
    39. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/filesystem.php ( 0.61 KB )
    40. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/lang.php ( 0.91 KB )
    41. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/log.php ( 1.35 KB )
    42. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/middleware.php ( 0.19 KB )
    43. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/route.php ( 1.89 KB )
    44. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/session.php ( 0.57 KB )
    45. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/trace.php ( 0.34 KB )
    46. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/view.php ( 0.82 KB )
    47. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/event.php ( 0.25 KB )
    48. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Event.php ( 7.67 KB )
    49. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/service.php ( 0.13 KB )
    50. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/AppService.php ( 0.26 KB )
    51. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Service.php ( 1.64 KB )
    52. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Lang.php ( 7.35 KB )
    53. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/lang/zh-cn.php ( 13.70 KB )
    54. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/Error.php ( 3.31 KB )
    55. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/RegisterService.php ( 1.33 KB )
    56. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/services.php ( 0.14 KB )
    57. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/PaginatorService.php ( 1.52 KB )
    58. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ValidateService.php ( 0.99 KB )
    59. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ModelService.php ( 2.04 KB )
    60. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Service.php ( 0.77 KB )
    61. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Middleware.php ( 6.72 KB )
    62. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/BootService.php ( 0.77 KB )
    63. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Paginator.php ( 11.86 KB )
    64. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/Validate.php ( 63.20 KB )
    65. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Model.php ( 23.55 KB )
    66. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Attribute.php ( 21.05 KB )
    67. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/AutoWriteData.php ( 4.21 KB )
    68. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Conversion.php ( 6.44 KB )
    69. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/DbConnect.php ( 5.16 KB )
    70. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/ModelEvent.php ( 2.33 KB )
    71. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/RelationShip.php ( 28.29 KB )
    72. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Arrayable.php ( 0.09 KB )
    73. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Jsonable.php ( 0.13 KB )
    74. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/contract/Modelable.php ( 0.09 KB )
    75. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Db.php ( 2.88 KB )
    76. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/DbManager.php ( 8.52 KB )
    77. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Log.php ( 6.28 KB )
    78. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Manager.php ( 3.92 KB )
    79. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerTrait.php ( 2.69 KB )
    80. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerInterface.php ( 2.71 KB )
    81. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cache.php ( 4.92 KB )
    82. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/simple-cache/src/CacheInterface.php ( 4.71 KB )
    83. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Arr.php ( 16.63 KB )
    84. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/driver/File.php ( 7.84 KB )
    85. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/Driver.php ( 9.03 KB )
    86. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/CacheHandlerInterface.php ( 1.99 KB )
    87. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/Request.php ( 0.09 KB )
    88. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Request.php ( 55.78 KB )
    89. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/middleware.php ( 0.25 KB )
    90. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Pipeline.php ( 2.61 KB )
    91. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/TraceDebug.php ( 3.40 KB )
    92. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/middleware/SessionInit.php ( 1.94 KB )
    93. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Session.php ( 1.80 KB )
    94. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/driver/File.php ( 6.27 KB )
    95. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/SessionHandlerInterface.php ( 0.87 KB )
    96. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/Store.php ( 7.12 KB )
    97. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Route.php ( 23.73 KB )
    98. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleName.php ( 5.75 KB )
    99. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Domain.php ( 2.53 KB )
    100. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleGroup.php ( 22.43 KB )
    101. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Rule.php ( 26.95 KB )
    102. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleItem.php ( 9.78 KB )
    103. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/route/app.php ( 3.94 KB )
    104. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Route.php ( 4.70 KB )
    105. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/dispatch/Controller.php ( 4.74 KB )
    106. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Dispatch.php ( 10.44 KB )
    107. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Index.php ( 9.87 KB )
    108. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/BaseController.php ( 2.05 KB )
    109. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/facade/Db.php ( 0.93 KB )
    110. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/connector/Mysql.php ( 5.44 KB )
    111. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/PDOConnection.php ( 52.47 KB )
    112. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Connection.php ( 8.39 KB )
    113. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/ConnectionInterface.php ( 4.57 KB )
    114. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/builder/Mysql.php ( 16.58 KB )
    115. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Builder.php ( 24.06 KB )
    116. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseBuilder.php ( 27.50 KB )
    117. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Query.php ( 15.71 KB )
    118. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseQuery.php ( 45.13 KB )
    119. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TimeFieldQuery.php ( 7.43 KB )
    120. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/AggregateQuery.php ( 3.26 KB )
    121. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ModelRelationQuery.php ( 20.07 KB )
    122. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ParamsBind.php ( 3.66 KB )
    123. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ResultOperation.php ( 7.01 KB )
    124. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/WhereQuery.php ( 19.37 KB )
    125. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/JoinAndViewQuery.php ( 7.11 KB )
    126. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TableFieldInfo.php ( 2.63 KB )
    127. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/Transaction.php ( 2.77 KB )
    128. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/driver/File.php ( 5.96 KB )
    129. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/LogHandlerInterface.php ( 0.86 KB )
    130. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/Channel.php ( 3.89 KB )
    131. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/event/LogRecord.php ( 1.02 KB )
    132. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/Collection.php ( 16.47 KB )
    133. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/View.php ( 1.70 KB )
    134. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/View.php ( 4.39 KB )
    135. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Es.php ( 3.30 KB )
    136. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Response.php ( 8.81 KB )
    137. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/response/View.php ( 3.29 KB )
    138. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cookie.php ( 6.06 KB )
    139. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-view/src/Think.php ( 8.38 KB )
    140. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/TemplateHandlerInterface.php ( 1.60 KB )
    141. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/Template.php ( 46.61 KB )
    142. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/driver/File.php ( 2.41 KB )
    143. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/contract/DriverInterface.php ( 0.86 KB )
    144. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/runtime/temp/c935550e3e8a3a4c27dd94e439343fdf.php ( 31.50 KB )
    145. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Html.php ( 4.42 KB )
    1. CONNECT:[ UseTime:0.001108s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
    2. SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.001658s ]
    3. SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000792s ]
    4. SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000813s ]
    5. SHOW FULL COLUMNS FROM `set` [ RunTime:0.001385s ]
    6. SELECT * FROM `set` [ RunTime:0.000660s ]
    7. SHOW FULL COLUMNS FROM `article` [ RunTime:0.001441s ]
    8. SELECT * FROM `article` WHERE `id` = 719361 LIMIT 1 [ RunTime:0.001201s ]
    9. UPDATE `article` SET `lasttime` = 1780713460 WHERE `id` = 719361 [ RunTime:0.009388s ]
    10. SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000326s ]
    11. SELECT * FROM `article` WHERE `id` < 719361 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.000556s ]
    12. SELECT * FROM `article` WHERE `id` > 719361 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.000349s ]
    13. SELECT * FROM `article` WHERE `id` < 719361 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.000653s ]
    14. SELECT * FROM `article` WHERE `id` < 719361 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.002102s ]
    15. SELECT * FROM `article` WHERE `id` < 719361 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.000670s ]
    0.207433s