《计算机专业英语》期末考查试题

ǀ. Translation from English to Chinese (Article 1: 40’, Article 2: 30’)

Article 1:

IBM’s 5nm nanosheet chips could revolutionize the IoT market Not too long ago, Samsung and Qualcomm boasted their Exynos 8895 and Snapdragon 835 processors, respectively. Both of these chips were manufactured using a 10 nm FinFET process, currently the smallest chip size in the consumer market. IBM’s Research Alliance, however, is proving that it has done one better. By halving the size but increasing performance and energy efficiency, IBM’s 5 nm chips has the potential to push the consumer electronics market forward, especially the IoT and even the smartphone markets, at an accelerated pace.

IBM makes it clear that 5 nm chips are also possible using the now standard FinFET transistor architecture, which takes its name from the fin-like silicon structure that wraps around the transistor’s conductive channel. Those fin s, however, also limit how much space the transistors can safely take up. So while the FinFET process can indeed scale down to 5 nm, there are no other benefits other than the smaller size.

In contrast, IBM’s nanosheet architecture promises not only a smaller size but also a bigger performance improvement.

This is made possible by using nanosheets instead of fins as the main structure of the transistors. This not only allows IBM to cram even more in a tiny space but also offers some flexibility to change the width of the nanosheets even in a single manufacturing process.

In theory, IBM Research claims that the chips offer a 40% performance boost at a fixed power. Alternatively, it offers 75% power savings when running to match the performance of a 10 nm FinF ET chip. All at half the size of the chips you’ll find in something like the Samsung Galaxy S8.

More power at less space and battery drain is something that modern electronics are in great need of, from smartphones to machine learning platforms to IoT devices. Especially for the latter, which are severely limited by how much silicon can be crammed in such a small space, IBM’s 5 nm chips could give the industry the break it needs to become smarter and more capable in powering the smart homes of tomorrow.

Article 2:

Running R

How to start R and what command-line options are available is discussed in Section “Invoking R” in “R-intro.pdf”.

You should ensure that the shell has set adequate resource

limits: R expects a stack size of at least 8MB and to be able to open at least 256 file descriptors. (Any modern OS should have default limits at least as large as these, but apparently NetBSD may not. Use the shell command ulimit (sh/bash) or limit (csh/tcsh) to check.)

R makes use of a number of environment variables, the default values of many of which are set in fle

R_HOME/etc/Renviron (there are none set by default on Windows and hence no such file). These are set at configure time, and you would not normally want to change them – a possible exception is R_PAPERSIZE (see Section B.3.1 [Setting paper size], page 50). The paper size will be deduced from the ‘LC_PAPER’ locale category if it exists and R_PAPERSIZE is unset, and this will normally produce the right choice from ‘a4’ and ‘letter’ on modern Unix-alikes (but can always be overridden by setting R_PAPERSIZE).

Various environment variables can be set to determine where

R creates its per-session temporary directory. The environment variables TMPDIR, TMP and TEMP are searched in turn and the first one which is set and points to a writable area is used.

If none do, the fnal default is /tmp on Unix-alikes and the value of R_USER on Windows. The path should be an absolute path not