毕业设计译文格式

合集下载

(完整版)_毕业设计参考文献译文

毕业设计参考文献译文题目：PID控制器PID controller院（系）计算机科学与信息工程学院专业年级 09自动化 2 班学生姓名周文龙学号日期2013年3月7日PID控制器摘要：比例积分微分控制器（PID调节器）是一个控制环，广泛地应用于工业控制系统里的反馈机制。

PID控制器通过调节给定值与测量值之间的偏差，给出正确的调整，从而有规律地纠正控制过程。

PID控制器算法涉及到三个部分：比例，积分，微分。

比例控制是对当前偏差的反应，积分控制是基于新近错误总数的反应，而微分控制则是基于错误变化率的反应。

这三种控制的结合可用来调节过程系统，例如调节阀的位置，或者加热系统的电源调节。

根据具体的工艺要求，通过PID 控制器的参数整定，从而提供调节作用。

控制器的响应可以被认为是对系统偏差的响应。

注意一点的是，PID算法不一定就是系统或系统稳定性的最佳控制。

一些应用可能只需要运用一到两种方法来提供适当的系统控制。

这是通过把不想要的控制输出置零取得。

在控制系统中存在P,PI,PD,PID调节器。

PI调节器很普遍，因为微分控制对测量噪音非常敏感。

积分作用的缺乏可以防止系统根据控制目标而达到它的目标值。

关键字：PID 最佳控制反馈1.控制环基础一个关于控制环类似的例子就是保持水在理想温度，涉及到两个过程，冷、热水的混合。

人可以凭触觉估测水的温度。

基于此他们设计一个控制行为：用冷水龙头调整过程。

重复这个过程，调节热水流直到温度处于期望的稳定值。

感觉水温就是对过程值或变量的测量。

期望得到的温度称为给定值。

控制器的输出对象和过程的输入对象称为控制参数。

测量值与给定值之间的差就是偏差值，太高、太低或正常。

作为一个控制器，在确定温度给定值后，就可以粗略决定改变阀门位置多少，以及怎样改变偏差值。

首次估计即是PID 控制器的比例度的确定。

当它几乎正确时，PID控制器的积分作用就是起着逐渐调整温度的作用。

微分作用就是根据水温变得更热、更冷，以及变化速率来决定什么时候、怎样调整那些阀门。

毕业设计外文翻译译文

1 工程概论1.1 工程专业1.2 工业和技术1.3 现代制造业工程专业1 工程行业是历史上最古老的行业之一。

如果没有在广阔工程领域中应用的那些技术，我们现在的文明绝不会前进。

第一位把岩石凿削成箭和矛的工具匠是现代机械工程师的鼻祖。

那些发现地球上的金属并找到冶炼和使用金属的方法的工匠们是采矿和冶金工程师的先祖。

那些发明了灌溉系统并建造了远古世纪非凡的建筑物的技师是他们那个时代的土木工程师。

2 工程一般被定义为理论科学的实际应用，例如物理和数学。

许多早期的工程设计分支不是基于科学而是经验信息，这些经验信息取决于观察和经历，而不是理论知识。

这是一个倾斜面实际应用的例子，虽然这个概念没有被确切的理解，但是它可以被量化或者数字化的表达出来。

3 从16、17世纪当代初期，量化就已经成为科学知识大爆炸的首要原因之一。

另外一个重要因素是实验法验证理论的发展。

量化包含了把来源于实验的数据和信息转变成确切的数学术语。

这更加强调了数学是现代工程学的语言。

4 从19世纪开始，它的结果的实际而科学的应用已经逐步上升。

机械工程师现在有精确的能力去计算来源于许多不同机构之间错综复杂的相互作用的机械优势。

他拥有能一起工作的既新型又强硬的材料和巨大的新能源。

工业革命开始于使用水和蒸汽一起工作。

从此使用电、汽油和其他能源作动力的机器变得如此广泛以至于它们承担了世界上很大比例的工作。

5 科学知识迅速膨胀的结果之一就是科学和工程专业的数量的增加。

到19世纪末不仅机械、土木、矿业、冶金工程被建立而且更新的化学和电气工程专业出现了。

这种膨胀现象一直持续到现在。

我们现在拥有了核能、石油、航天航空空间以及电气工程等。

每种工程领域之内都有细分。

6 例如，土木工程自身领域之内有如下细分：涉及永久性结构的建筑工程、涉及水或其他液体流动与控制系统的水利工程、涉及供水、净化、排水系统的研究的环境工程。

机械工程主要的细分是工业工程，它涉及的是错综复杂的机械系统，这些系统是工业上的，而非单独的机器。

外文参考文献译文及原文【范本模板】

广东工业大学华立学院本科毕业设计（论文）外文参考文献译文及原文系部城建学部专业土木工程年级 2011级班级名称 11土木工程9班学号 23031109000学生姓名刘林指导教师卢集富2015 年5 月目录一、项目成本管理与控制 0二、Project Budget Monitor and Control (1)三、施工阶段承包商在控制施工成本方面所扮演的作用 (2)四、The Contractor’s Role in Building Cost Reduction After Design (4)一、外文文献译文（1）项目成本管理与控制随着市场竞争的激烈性越来越大,在每一个项目中，进行成本控制越发重要。

本文论述了在施工阶段,项目经理如何成功地控制项目预算成本。

本文讨论了很多方法。

它表明，要取得成功，项目经理必须关注这些成功的方法.1。

简介调查显示,大多数项目会碰到超出预算的问……功控制预算成本.2.项目控制和监测的概念和目的Erel and Raz (2000）指出项目控制周期包括测量成……原因以及决定纠偏措施并采取行动。

监控的目的就是纠偏措施的。

.。

标范围内。

3.建立一个有效的控制体系为了实现预算成本的目标，项目管理者需要建立一……被监测和控制是非常有帮助的。

项目成功与良好的沟通密。

决（ Diallo and Thuillier， 2005）.4.成本费用的检测和控制4.1对检测的优先顺序进行排序在施工阶段，很多施工活动是基于原来的计……用完了。

第四,项目管理者应该检测高风险活动，高风险活动最有。

..重要（Cotterell and Hughes, 1995)。

4.2成本控制的方法一个项目的主要费用包括员工成本、材料成本以及工期延误的成本。

为了控制这些成本费用，项目管理者首先应该建立一个成本控制系统：a)为财务数据的管理和分析工作落实责任人员b)确保按照项目的结构来合理分配所有的……它的变化-—在成本控制线上准确地记录所有恰..。

毕业设计(论文)外文资料及译文(模板)

大连东软信息学院
毕业设计（论文）外文资料及译文
系所：
专业：
班级：
姓名：
学号：
大连东软信息学院
Dalian Neusoft University of Information
外文资料和译文格式要求
一、装订要求
1、外文资料原文（复印或打印）在前、译文在后、最后为指导教师评定成绩。

2、译文必须采用计算机输入、打印。

3、A4幅面打印，于左侧装订。

二、撰写要求
1、外文文献内容与所选课题相关。

2、本科学生译文汉字字数不少于4000字，高职学生译文汉字字数不少于2000字。

三、格式要求
1、译文字号：中文小四号宋体，英文小四号“Times New Roman”字型，全文统一，首行缩进2个中文字符，1.5倍行距。

2、译文页码：页码用阿拉伯数字连续编页，字体采用“Times New Roman”字体，字号小五，页底居中。

3、译文页眉：眉体使用单线，页眉说明五号宋体，居中“大连东软信息学院本科毕业设计（论文）译文”。

毕业设计(论文)外文资料和译文格式要求(模板)

成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。

外文资料原文（复印或打印）在前，译文在后，于左侧装订。

二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。

2、译文汉字字数不少于4000字。

3、正文格式要求：宋体五号字。

译文格式参见《译文格式要求》，宋体五号字，单倍行距。

纸张纸张为A4纸，页边距上2.54cm、下2.54cm、左3.17cm、右3.17cm。

装订外文资料原文（复印或打印）在前，译文在后封面封面的专业、班级、姓名、学号等信息要全部填写正确。

封面指导教师必须为讲师以上职称，若助教则需要配备一名讲师协助指导。

讲师在前，助教在后。

指导教师姓名后面空一个中文空格，加职称。

页眉页眉说明宋体小五，左端“XX学院毕业设计（论文）”，右端“译文”。

页眉中的学院名称要与封面学院名称一致。

字数本科4000字。

附：外文资料和译文封面、空白页成都东软学院外文资料和译文专业：软件工程移动互联网应用开发班级：2班姓名：罗荣昆学号：12310420216指导教师：2015年 12月 8日Android page layoutUsing XML-Based LayoutsW hile it is technically possible to create and attach widgets to our activity purely through Java code, the way we did in Chapter 4, the more common approach is to use an XML-based layout file. Dynamic instantiation of widgets is reserved for more complicated scenarios, where the widgets are not known at compile-time (e g., populating a column of radio buttons based on data retrieved off the Internet).With that in mind, it’s time to break out the XML and learn how to lay out Android activities that way.What Is an XML-Based Layout?As the name suggests, an XML-based layout is a specification of widgets’ relationships to each other—and to their containers (more on this in Chapter 7)—encoded in XML format. Specifi cally, Android considers XML-based layouts to be resources, and as such layout files are stored in the res/layout directory inside your Android project.Each XML file contains a tree of elements specifying a layout of widgets and their containers that make up one view hierarchy. The attributes of the XML elements are properties, describing how a widget should look or how a container should behave. For example, if a Button element has an attribute value of android:textStyle = "bold", that means that the text appearing on the face of the button should be rendered in a boldface font style.Android’s SDK ships with a tool (aapt) which uses the layouts. This tool should be automatically invoked by your Android tool chain (e.g., Eclipse, Ant’s build.xml). Of particular importance to you as a developer is that aapt generates the R.java source file within your project, allowing you to access layouts and widgets within those layouts directly from your Java code. Why Use XML-Based Layouts?Most everything you do using XML layout files can be achieved through Java code. For example, you could use setTypeface() to have a button render its textin bold, instead of using a property in an XML layout. Since XML layouts are yet another file for you to keep track of, we need good reasons for using such files.Perhaps the biggest reason is to assist in the creation of tools for view definition, such as a GUI builder in an IDE like Eclipse or a dedicated Android GUI designer like DroidDraw1. Such GUI builders could, in principle, generate Java code instead of XML. The challenge is re-reading the UI definition to support edits—that is far simpler if the data is in a structured format like XML than in a programming language. Moreover, keeping generated XML definitions separated from hand-written Java code makes it less likely that somebody’s custom-crafted source will get clobbered by accident when the generated bits get re-generated. XML forms a nice middle ground between something that is easy for tool-writers to use and easy for programmers to work with by hand as needed.Also, XML as a GUI definition format is becoming more commonplace. Microsoft’s XAML2, Adobe’s Flex3, and Mozilla’s XUL4 all take a similar approach to that of Android: put layout details in an XML file and put programming smarts in source files (e.g., JavaScript for XUL). Many less-well-known GUI frameworks, such as ZK5, also use XML for view definition. While “following the herd” is not necessarily the best policy, it does have the advantage of helping to ease the transition into Android from any other XML-centered view description language. OK, So What Does It Look Like?Here is the Button from the previous chapter’s sample application, converted into an XMLlayout file, found in the Layouts/NowRedux sample project. This code sample along with all others in this chapter can be found in the Source Code area of .<?xml version="1.0" encoding="utf-8"?><Button xmlns:android="/apk/res/android"android:id="@+id/button"android:text=""android:layout_width="fill_parent"android:layout_height="fill_parent"/>The class name of the widget—Button—forms the name of the XML element. Since Button is an Android-supplied widget, we can just use the bare class name. If you create your own widgets as subclasses of android.view.View, you would need to provide a full package declara tion as well.The root element needs to declare the Android XML namespace:xmlns:android="/apk/res/android"All other elements will be children of the root and will inherit that namespace declaration.Because we want to reference this button from our Java code, we need to give it an identifier via the android:id attribute. We will cover this concept in greater detail later in this chapter.The remaining attributes are properties of this Button instance:• android:text indicates the initial text to be displayed on the button face (in this case, an empty string)• android:layout_width and android:layout_height tell Android to have the button’swidth and height fill the “parent”, in this case the entire screen—these attributes will be covered in greater detail in Chapter 7.Since this single widget is the only content in our activity, we only need this single element. Complex UIs will require a whole tree of elements, representing the widgets and containers that control their positioning. All the remaining chapters of this book will use the XML layout form whenever practical, so there are dozens of other examples of more complex layouts for you to peruse from Chapter 7 onward.What’s with the @ Signs?Many widgets and containers only need to appear in the XML layout file and do not need to be referenced in your Java code. For example, a static label (TextView) frequently only needs to be in the layout file to indicate where it should appear. These sorts of elements in the XML file do not need to have the android:id attribute to give them a name.Anything you do want to use in your Java source, though, needs an android:id.The convention is to use @+id/... as the id value, where the ... represents your locally unique name for the widget in question. In the XML layout example in the preceding section, @+id/button is the identifier for the Button widget.Android provides a few special android:id values, of the form @android:id/.... We will see some of these in various chapters of this book, such as Chapters 8 and 10.We Attach These to the Java How?Given that you have painstakingly set up the widgets and containers in an XML layout filenamed main.xml stored in res/layout, all you need is one statement in your activity’s onCreate() callback to use that layout:setContentView(yout.main);This is the same setContentView() we used earlier, passing it an instance of a View subclass (in that case, a Button). The Android-built view, constructed from our layout, is accessed from that code-generated R class. All of the layouts are accessible under yout, keyed by the base name of the layout file—main.xml results in yout.main.To access our identified widgets, use findViewById(), passing in the numeric identifier of the widget in question. That numeric identifier was generated by Android in the R class asR.id.something (where something is the specific widget you are seeking). Those widgets are simply subclasses of View, just like the Button instance we created in Chapter 4.The Rest of the StoryIn the original Now demo, the button’s face would show the current time, which would reflect when the button was last pushed (or when the activity was first shown, if the button had not yet been pushed).Most of that logic still works, even in this revised demo (NowRedux). However,rather than instantiating the Button in our activity’s onCreate() callback, we can reference the one from the XML layout:package youts;import android.app.Activity;import android.os.Bundle;import android.view.View;import android.widget.Button; import java.util.Date;public class NowRedux extends Activity implements View.OnClickListener { Button btn;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);btn=(Button)findViewById(R.id.button);btn.setOnClickListener(this);upd ateTime();}public void onClick(View view) { updateTime();}private void updateTime() {btn.setText(new Date().toString()); }}The first difference is that rather than setting the content view to be a view we created in Java code, we set it to reference the XML layout (setContentView(yout.main)). The R.java source file will be updated when we rebuild this project to include a reference to our layout file (stored as main.xml in our project’s res/l ayout directory).The other difference is that we need to get our hands on our Button instance, for which we use the findViewById() call. Since we identified our button as @+id/button, we can reference the button’s identifier as R.id.button. Now, with the Button instance in hand, we can set the callback and set the label as needed.As you can see in Figure 5-1, the results look the same as with the originalNow demo.Figure 5-1. The NowRedux sample activity Employing Basic WidgetsE very GUI toolkit has some basic widgets: fields, labels, buttons, etc. Android’s toolkit is no different in scope, and the basic widgets will provide a good introduction as to how widgets work in Android activities.Assigning LabelsThe simplest widget is the label, referred to in Android as a TextView. Like in most GUI toolkits, labels are bits of text not editable directly by users. Typically, they are used to identify adjacent widgets (e.g., a “Name:” label before a field where one fills in a name).In Java, you can create a label by creating a TextView instance. More commonly, though, you will create labels in XML layout files by adding a TextView element to the layout, with an android:text property to set the value of the label itself. If you need to swap labels based on certain criteria, such as internationalization, you may wish to use a resource reference in the XML instead, as will be described in Chapter 9. TextView has numerous other properties of relevance for labels, such as:• android:typeface to set the typeface to use for the label (e.g., monospace) • android:textStyle to indicate that the typeface should be made bold (bold), italic (italic),or bold and italic (bold_italic)• android:textColor to set the color of the label’s text, in RGB hex format (e.g., #FF0000 for red)For example, in the Basic/Label project, you will find the following layout file:<?xml version="1.0" encoding="utf-8"?><TextView xmlns:android=/apk/res/androidandroid:layout_width="fill_parent"android:layout_height="wrap_content"android:text="You were expecting something profound?" />As you can see in Figure 6-1, just that layout alone, with the stub Java source provided by Android’s p roject builder (e.g., activityCreator), gives you the application.Figure 6-1. The LabelDemo sample applicationButton, Button, Who’s Got the Button?We’ve already seen the use of the Button widget in Chapters 4 and 5. As it turns out, Button is a subclass of TextView, so everything discussed in the preceding section in terms of formatting the face of the button still holds. Fleeting ImagesAndroid has two widgets to help you embed images in your activities: ImageView and ImageButton. As the names suggest, they are image-based analogues to TextView and Button, respectively.Each widget takes an android:src attribute (in an XML layout) to specify what picture to use. These usually reference a drawable resource, described in greater detail in the chapter on resources. You can also set the image content based on a Uri from a content provider via setImageURI().ImageButton, a subclass of ImageView, mixes in the standard Button behaviors, for responding to clicks and whatnot.For example, take a peek at the main.xml layout from the Basic/ImageView sample project which is found along with all other code samples at : <?xml version="1.0" encoding="utf-8"?><ImageView xmlns:android=/apk/res/androidandroid:id="@+id/icon"android:layout_width="fill_parent"android:layout_height="fill_parent"android:adjustViewBounds="true"android:src="@drawable/molecule" />The result, just using the code-generated activity, is shown in Figure 6-2.Figure 6-2. The ImageViewDemo sample applicationFields of Green. Or Other Colors.Along with buttons and labels, fields are the third “anchor” of most GUI toolkits. In Android, they are implemented via the EditText widget, which is a subclass of the TextView used for labels.Along with the standard TextView properties (e.g., android:textStyle), EditText has many others that will be useful for you in constructing fields, including:• android:autoText, to control if the fie ld should provide automatic spelling assistance• android:capitalize, to control if the field should automatically capitalize the first letter of entered text (e.g., first name, city) • android:digits, to configure the field to accept only certain digi ts • android:singleLine, to control if the field is for single-line input or multiple-line input (e.g., does <Enter> move you to the next widget or add a newline?)Beyond those, you can configure fields to use specialized input methods, such asandroid:numeric for numeric-only input, android:password for shrouded password input,and android:phoneNumber for entering in phone numbers. If you want to create your own input method scheme (e.g., postal codes, Social Security numbers), you need to create your own implementation of the InputMethod interface, then configure the field to use it via android: inputMethod.For example, from the Basic/Field project, here is an XML layout file showing an EditText:<?xml version="1.0" encoding="utf-8"?><EditTextxmlns:android=/apk/res/androidandroid:id="@+id/field"android:layout_width="fill_parent"android:layout_height="fill_parent"android:singleLine="false" />Note that android:singleLine is false, so users will be able to enter in several lines of text. For this project, the FieldDemo.java file populates the input field with some prose:package monsware.android.basic;import android.app.Activity;import android.os.Bundle;import android.widget.EditText;public class FieldDemo extends Activity { @Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);EditText fld=(EditText)findViewById(R.id.field);fld.setText("Licensed under the Apache License, Version 2.0 " + "(the \"License\"); you may not use this file " + "except in compliance with the License. You may " + "obtain a copy of the License at " +"/licenses/LICENSE-2.0");}}The result, once built and installed into the emulator, is shown in Figure 6-3.Figure 6-3. The FieldDemo sample applicationNote Android’s emulator only allows one application in the launcher per unique Java package. Since all the demos in this chapter share the monsware.android.basic package, you will only see one of these demos in your emulator’s launcher at any one time.Another flavor of field is one that offers auto-completion, to help users supply a value without typing in the whole text. That is provided in Android as the AutoCompleteTextView widget and is discussed in Chapter 8.Just Another Box to CheckThe classic checkbox has two states: checked and unchecked. Clicking the checkbox toggles between those states to indicate a choice (e.g., “Ad d rush delivery to my order”). In Android, there is a CheckBox widget to meet this need. It has TextView as an ancestor, so you can use TextView properties likeandroid:textColor to format the widget. Within Java, you can invoke: • isChecked() to determi ne if the checkbox has been checked• setChecked() to force the checkbox into a checked or unchecked state • toggle() to toggle the checkbox as if the user checked itAlso, you can register a listener object (in this case, an instance of OnCheckedChangeListener) to be notified when the state of the checkbox changes.For example, from the Basic/CheckBox project, here is a simple checkbox layout:<?xml version="1.0" encoding="utf-8"?><CheckBox xmlns:android="/apk/res/android"android:id="@+id/check"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="This checkbox is: unchecked" />The corresponding CheckBoxDemo.java retrieves and configures the behavior of the checkbox:public class CheckBoxDemo extends Activityimplements CompoundButton.OnCheckedChangeListener { CheckBox cb;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);cb=(CheckBox)findViewById(R.id.check);cb.setOnCheckedChangeListener(this);}public void onCheckedChanged(CompoundButton buttonView,boolean isChecked) {if (isChecked) {cb.setText("This checkbox is: checked");}else {cb.setText("This checkbox is: unchecked");}}}Note that the activity serves as its own listener for checkbox state changes since it imple ments the OnCheckedChangeListener interface (via cb.setOnCheckedChangeListener(this)). The callback for the listener is onCheckedChanged(), which receives the checkbox whose state has changed and what the new state is. In this case, we update the text of the checkbox to reflect what the actual box contains.The result? Clicking the checkbox immediately updates its text, as you can see in Figures 6-4 and 6-5.Figure 6-4. The CheckBoxDemo sample application, with the checkbox uncheckedFigure 6-5. The same application, now with the checkbox checkedTurn the Radio UpAs with other implementations of radio buttons in other toolkits, Android’s radio buttons are two-state, like checkboxes, but can be grouped such that only one radio button in the group can be checked at any time.Like CheckBox, RadioButton inherits from CompoundButton, which in turn inherits fromTextView. Hence, all the standard TextView properties for font face, style, color, etc., are available for controlling the look of radio buttons. Similarly, you can call isChecked() on a RadioButton to see if it is selected, toggle() to select it, and so on, like you can with a CheckBox.Most times, you will want to put your RadioButton widgets inside of aRadioGroup. The RadioGroup indicates a set of radio buttons whose state is tied, meaning only one button out of the group can be selected at any time. If you assign an android:id to your RadioGroup in your XML layout, you can access the group from your Java code and invoke:• check() to check a specific radio button via its ID (e.g., group.check(R.id.radio1))• clearCheck() to clear all radio buttons, so none in the group are checked• getCheckedRadioButtonId() to get the ID of the currently-checked radio button (or -1 if none are checked)For example, from the Basic/RadioButton sample application, here is an XML layout showing a RadioGroup wrapping a set of RadioButton widgets: <?xml version="1.0" encoding="utf-8"?> <RadioGroupxmlns:android=/apk/res/androidandroid:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent" ><RadioButton android:id="@+id/radio1"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Rock" /><RadioButton android:id="@+id/radio2"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Scissors" /><RadioButton android:id="@+id/radio3"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Paper" /></RadioGroup>Figure 6-6 shows the result using the stock Android-generated Java forthe project and this layout.Figure 6-6. The RadioButtonDemo sample application Note that the radio button group is initially set to be completely unchecked at the outset. To pre-set one of the radio buttons to be checked, use either setChecked() on the RadioButton or check() on the RadioGroup from within your onCreate() callback in your activity.It’s Quite a ViewAll widgets, including the ones previously shown, extend View, and as such give all widgets an array of useful properties and methods beyond those already described.Useful PropertiesSome of the properties on View most likely to be used include:• Controls the focus sequence:• android:nextFocusDown• android:nextFocusLeft• android:nextFocusRight• android:nextFocusUp• android:visibility, which controls wheth er the widget is initially visible• android:background, which typically provides an RGB color value (e.g., #00FF00 for green) to serve as the background for the widgetUseful MethodsYou can toggle whether or not a widget is enabled via setEnabled() and see if it is enabled via isEnabled(). One common use pattern for this is to disable some widgets based on a CheckBox or RadioButton selection.You can give a widget focus via requestFocus() and see if it is focused via isFocused(). You might use this in concert with disabling widgets as previously mentioned, to ensure the proper widget has the focus once your disabling operation is complete.To help navigate the tree of widgets and containers that make up an activity’s overall view, you can use:• get Parent() to find the parent widget or container• findViewById() to find a child widget with a certain ID• getRootView() to get the root of the tree (e.g., what you provided to the activity via setContentView())Android 页面布局使用XML进行布局虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。

毕业设计译文格式要求

毕业设计译文格式要求在进行毕业设计过程中，撰写译文是一个重要的环节。

为了保证毕业设计的质量和规范，毕业设计译文的格式要求是必须要注意的。

本文将介绍毕业设计译文格式要求的具体细节，以便同学们在撰写译文过程中参考和遵循。

1. 字体要求：毕业设计译文应使用宋体、楷体或仿宋等常用字体，字体大小为小四（即12号），且要统一整篇译文中的字体和字号。

2. 行间距和段间距要求：译文的行间距应设为1.5倍行距，段间距应保持一个空行，以便最大限度地提高译文的可读性。

3. 页面设置要求：毕业设计译文应采用A4纸张大小，纸张方向为纵向，页边距上下左右均为2.5厘米。

4. 标题和页眉要求：译文的每一页上方应设有页眉，页眉中居中显示“译文”二字，并注明页码。

页码应从引言部分开始，采用阿拉伯数字连续标注。

5. 对齐和缩进要求：毕业设计译文中的文本应采用左对齐方式排版，段落的首行应进行缩进，缩进的大小约为2个字符。

6. 标点符号要求：在译文中使用标点符号时，应遵循中文标点符号的使用规范，如逗号、句号、问号等。

7. 引用和注释要求：毕业设计译文中如需引用其他文献或进行注释，应采用脚注的形式进行标注，脚注编号应以阿拉伯数字进行标注，且应置于所引用句子或需要注释的内容之后。

8. 表格和图表要求：若译文中需要使用表格和图表来支持或说明内容，应进行适当的编号，并附上简短的标题和注释。

同时，表格和图表应与译文内容相互呼应，并尽可能地与正文排在相近的位置。

9. 参考文献要求：如果在译文中使用了参考文献或其他引用资料，则应在译文末尾列出参考文献列表，按照引用顺序和特定的参考文献格式进行排列。

总结起来，毕业设计译文的格式要求主要包括字体和字号、行间距和段间距、页面设置、标题和页眉、对齐和缩进、标点符号、引用和注释、表格和图表以及参考文献等方面。

同学们需要遵循这些要求，以确保自己的毕业设计译文达到学术规范的要求，提高毕业设计的质量和可读性。

最后，同学们在撰写毕业设计译文时还需注意文笔的流畅性和准确性。

毕业设计(论文)外文原文及译文

毕业设计（论文）外文原文及译文一、外文原文MCUA microcontroller (or MCU) is a computer-on-a-chip. It is a type of microcontroller emphasizing self-sufficiency and cost-effectiveness, in contrast to a general-purpose microprocessor (the kind used in a PC).With the development of technology and control systems in a wide range of applications, as well as equipment to small and intelligent development, as one of the single-chip high-tech for its small size, powerful, low cost, and other advantages of the use of flexible, show a strong vitality. It is generally better compared to the integrated circuit of anti-interference ability, the environmental temperature and humidity have better adaptability, can be stable under the conditions in the industrial. And single-chip widely used in a variety of instruments and meters, so that intelligent instrumentation and improves their measurement speed and measurement accuracy, to strengthen control functions. In short，with the advent of the information age, traditional single- chip inherent structural weaknesses, so that it show a lot of drawbacks. The speed, scale, performance indicators, such as users increasingly difficult to meet the needs of the development of single-chip chipset, upgrades are faced with new challenges.The Description of AT89S52The AT89S52 is a low-power, high-performance CMOS 8-bit microcontroller with 8K bytes of In-System Programmable Flash memory. The device is manufactured using Atmel's high-density nonvolatile memory technology and is compatible with the industry-standard 80C51 instruction set and pinout. The on-chip Flash allows the program memory to be reprogrammed in-system or by a conventional nonvolatile memory programmer. By combining a versatile 8-bit CPU with In-System Programmable Flash on a monolithic chip, the Atmel AT89S52 is a powerful microcontroller which provides a highly-flexible and cost-effective solution to many embedded control applications.The AT89S52 provides the following standard features: 8K bytes ofFlash, 256 bytes of RAM, 32 I/O lines, Watchdog timer, two data pointers, three 16-bit timer/counters, a six-vector two-level interrupt architecture, a full duplex serial port, on-chip oscillator, and clock circuitry. In addition, the AT89S52 is designed with static logic for operation down to zero frequency and supports two software selectable power saving modes. The Idle Mode stops the CPU while allowing the RAM, timer/counters, serial port, and interrupt system to continue functioning. The Power-down mode saves the RAM contents but freezes the oscillator, disabling all other chip functions until the next interrupt or hardware reset.Features• Compatible with MCS-51® Products• 8K Bytes of In-System Programmable (ISP) Flash Memory– Endurance: 1000 Write/Erase Cycles• 4.0V to 5.5V Operating Range• Fully Static Operation: 0 Hz to 33 MHz• Three-level Program Memory Lock• 256 x 8-bit Internal RAM• 32 Programmable I/O Lines• Three 16-bit Timer/Counters• Eight Interrupt Sources• Full Duplex UART Serial Channel• Low-power Idle and Power-down Modes• Interrupt Recovery from Power-down Mode• Watchdog Timer• Dual Data Pointer• Power-off FlagPin DescriptionVCCSupply voltage.GNDGround.Port 0Port 0 is an 8-bit open drain bidirectional I/O port. As an output port, each pin can sink eight TTL inputs. When 1s are written to port 0 pins, the pins can be used as high-impedance inputs.Port 0 can also be configured to be the multiplexed low-order address/data bus during accesses to external program and data memory. In this mode, P0 has internal pullups.Port 0 also receives the code bytes during Flash programming and outputs the code bytes during program verification. External pullups are required during program verification.Port 1Port 1 is an 8-bit bidirectional I/O port with internal pullups. The Port 1 output buffers can sink/source four TTL inputs. When 1s are written to Port 1 pins, they are pulled high by the internal pullups and can be used as inputs. As inputs, Port 1 pins that are externally being pulled low will source current (IIL) because of the internal pullups.In addition, P1.0 and P1.1 can be configured to be the timer/counter 2 external count input (P1.0/T2) and the timer/counter 2 trigger input (P1.1/T2EX), respectively.Port 1 also receives the low-order address bytes during Flash programming and verification.Port 2Port 2 is an 8-bit bidirectional I/O port with internal pullups. The Port 2 output buffers can sink/source four TTL inputs. When 1s are written to Port 2 pins, they are pulled high by the internal pullups and can be used as inputs. As inputs, Port 2 pins that are externally being pulled low will source current (IIL) because of the internal pullups.Port 2 emits the high-order address byte during fetches from external program memory and during accesses to external data memory that use 16-bit addresses (MOVX @ DPTR). In this application, Port 2 uses strong internal pull-ups when emitting 1s. During accesses to external data memory that use 8-bit addresses (MOVX @ RI), Port 2 emits the contents of the P2 Special Function Register.Port 2 also receives the high-order address bits and some control signals during Flash programming and verification.Port 3Port 3 is an 8-bit bidirectional I/O port with internal pullups. The Port 3 output buffers can sink/source four TTL inputs. When 1s are written to Port 3 pins, they are pulled high by the internal pullups and can be used as inputs. As inputs, Port 3 pins that are externally being pulled low will source current (IIL) because of the pullups.Port 3 also serves the functions of various special features of the AT89S52, as shown in the following table.Port 3 also receives some control signals for Flash programming and verification.RSTReset input. A high on this pin for two machine cycles while the oscillator is running resets the device. This pin drives High for 96 oscillator periods after the Watchdog times out. The DISRTO bit in SFR AUXR (address 8EH) can be used to disable this feature. In the default state of bit DISRTO, the RESET HIGH out feature is enabled.ALE/PROGAddress Latch Enable (ALE) is an output pulse for latching the low byte of the address during accesses to external memory. This pin is also the program pulse input (PROG) during Flash programming.In normal operation, ALE is emitted at a constant rate of 1/6 the oscillator frequency and may be used for external timing or clocking purposes. Note, however, that one ALE pulse is skipped during each access to external data memory.If desired, ALE operation can be disabled by setting bit 0 of SFR location 8EH. With the bit set, ALE is active only during a MOVX or MOVC instruction. Otherwise, the pin is weakly pulled high. Setting the ALE-disable bit has no effect if the microcontroller is in external execution mode.PSENProgram Store Enable (PSEN) is the read strobe to external program memory. When the AT89S52 is executing code from external program memory, PSENis activated twice each machine cycle, except that two PSEN activations are skipped during each access to external data memory.EA/VPPExternal Access Enable. EA must be strapped to GND in order to enable the device to fetch code from external program memory locations starting at 0000H up to FFFFH. Note, however, that if lock bit 1 is programmed, EA will be internally latched on reset. EA should be strapped to VCC for internal program executions.This pin also receives the 12-volt programming enable voltage (VPP) during Flash programming.XTAL1Input to the inverting oscillator amplifier and input to the internal clock operating circuit.XTAL2Output from the inverting oscillator amplifier.Special Function RegistersNote that not all of the addresses are occupied, and unoccupied addresses may not be implemented on the chip. Read accesses to these addresses will in general return random data, and write accesses will have an indeterminate effect.User software should not write 1s to these unlisted locations, since they may be used in future products to invoke new features. In that case, the reset or inactive values of the new bits will always be 0.Timer 2 Registers:Control and status bits are contained in registers T2CON and T2MOD for Timer 2. The register pair (RCAP2H, RCAP2L) are the Capture/Reload registers for Timer 2 in 16-bit capture mode or 16-bit auto-reload mode.Interrupt Registers:The individual interrupt enable bits are in the IE register. Two priorities can be set for each of the six interrupt sources in the IP register.Dual Data Pointer Registers: To facilitate accessing both internal and external data memory, two banks of 16-bit Data Pointer Registers areprovided: DP0 at SFR address locations 82H-83H and DP1 at 84H-85H. Bit DPS = 0 in SFR AUXR1 selects DP0 and DPS = 1 selects DP1. The user should always initialize the DPS bit to the appropriate value before accessing the respective Data Pointer Register.Power Off Flag:The Power Off Flag (POF) is located at bit 4 (PCON.4) in the PCON SFR. POF is set to “1” during power up. It can be set and rest under software control and is not affected by reset.Memory OrganizationMCS-51 devices have a separate address space for Program and Data Memory. Up to 64K bytes each of external Program and Data Memory can be addressed.Program MemoryIf the EA pin is connected to GND, all program fetches are directed to external memory. On the AT89S52, if EA is connected to VCC, program fetches to addresses 0000H through 1FFFH are directed to internal memory and fetches to addresses 2000H through FFFFH are to external memory.Data MemoryThe AT89S52 implements 256 bytes of on-chip RAM. The upper 128 bytes occupy a parallel address space to the Special Function Registers. This means that the upper 128 bytes have the same addresses as the SFR space but are physically separate from SFR space.When an instruction accesses an internal location above address 7FH, the address mode used in the instruction specifies whether the CPU accesses the upper 128 bytes of RAM or the SFR space. Instructions which use direct addressing access of the SFR space. For example, the following direct addressing instruction accesses the SFR at location 0A0H (which is P2).MOV 0A0H, #dataInstructions that use indirect addressing access the upper 128 bytes of RAM. For example, the following indirect addressing instruction, where R0 contains 0A0H, accesses the data byte at address 0A0H, rather than P2 (whose address is 0A0H).MOV @R0, #dataNote that stack operations are examples of indirect addressing, so the upper 128 bytes of data RAM are available as stack space.Timer 0 and 1Timer 0 and Timer 1 in the AT89S52 operate the same way as Timer 0 and Timer 1 in the AT89C51 and AT89C52.Timer 2Timer 2 is a 16-bit Timer/Counter that can operate as either a timer or an event counter. The type of operation is selected by bit C/T2 in the SFR T2CON (shown in Table 2). Timer 2 has three operating modes: capture, auto-reload (up or down counting), and baud rate generator. The modes are selected by bits in T2CON.Timer 2 consists of two 8-bit registers, TH2 and TL2. In the Timer function, the TL2 register is incremented every machine cycle. Since a machine cycle consists of 12 oscillator periods, the count rate is 1/12 of the oscillator frequency.In the Counter function, the register is incremented in response to a1-to-0 transition at its corresponding external input pin, T2. In this function, the external input is sampled during S5P2 of every machine cycle. When the samples show a high in one cycle and a low in the next cycle, the count is incremented. The new count value appears in the register during S3P1 of the cycle following the one in which the transition was detected. Since two machine cycles (24 oscillator periods) are required to recognize a 1-to-0 transition, the maximum count rate is 1/24 of the oscillator frequency. To ensure that a given level is sampled at least once before it changes, the level should be held for at least one full machine cycle.InterruptsThe AT89S52 has a total of six interrupt vectors: two external interrupts (INT0 and INT1), three timer interrupts (Timers 0, 1, and 2), and the serial port interrupt. These interrupts are all shown in Figure 10.Each of these interrupt sources can be individually enabled or disabledby setting or clearing a bit in Special Function Register IE. IE also contains a global disable bit, EA, which disables all interrupts at once.Note that Table 5 shows that bit position IE.6 is unimplemented. In the AT89S52, bit position IE.5 is also unimplemented. User software should not write 1s to these bit positions, since they may be used in future AT89 products. Timer 2 interrupt is generated by the logical OR of bits TF2 and EXF2 in register T2CON. Neither of these flags is cleared by hardware when the service routine is vectored to. In fact, the service routine may have to determine whether it was TF2 or EXF2 that generated the interrupt, and that bit will have to be cleared in software.The Timer 0 and Timer 1 flags, TF0 and TF1, are set at S5P2 of the cycle in which the timers overflow. The values are then polled by the circuitry in the next cycle. However, the Timer 2 flag, TF2, is set at S2P2 and is polled in the same cycle in which the timer overflows.二、译文单片机单片机即微型计算机，是把中央处理器、存储器、定时/计数器、输入输出接口都集成在一块集成电路芯片上的微型计算机。

毕业设计论文中英文翻译要求(最新)

附件1（毕业设计一）材料科学与工程学院毕业实习环节外文翻译要求一、翻译论文的选择：1、与自己毕业设计相关的外文参考文献2、该译文可以作为设计论文中文献综述中的部分内容；3、原则上选取的英语原文不超过5页。

二、译文结构内容1、作者，英文原文题目，期刊名称，卷期号，年份，起止页码，2、文章题目，作者（保持英文，不需翻译），作者单位（英文不变）3、摘要，关键词4、正文部分：引言，试验过程，结果与讨论，结论，参考文献（保持原文状态）5、译文中的图标需要翻译，图可以复印后粘贴或扫描插入三、译文和原文统一装订在一起，独立与毕业论文一起上交四、几点附属说明1 文章所在期刊的期刊名及相关信息不要翻译。

2 文章的作者，作者的单位，地址，下注的通讯作者的情况，参考文献不要翻译。

3文章的题目，摘要，关键词，及正文都要按照原文的顺序来翻译。

4文章中图表翻译示例如下：此为翻译前的表格：此为翻译后的表格：表1 微波和常规方法加工的粉体金属样品的性能Table 1 Properties of microwave and conventionally processedpowdered metal samplesMW 代表微波烧结；conv代表常规方法。

大部分微波烧结的样品的断裂模量比常规方法烧结的要高。

许多微波烧结的样品的密度也是高于常规方法烧成的样品。

MW, microwave processed; conv., conventionally processed. Themodulus of rupture(MOR) of most microwave-processed samples ishigher than that of the conventional samples. The densities of manymicrowave-processed samples are also higher than those ofconventional samples.即表头和注释中英文都要。

毕业设计(论文)外文资料翻译(学生用)

毕业设计外文资料翻译学院：信息科学与工程学院专业：软件工程姓名： XXXXX学号： XXXXXXXXX外文出处： Think In Java (用外文写)附件： 1.外文资料翻译译文；2.外文原文。

附件1：外文资料翻译译文网络编程历史上的网络编程都倾向于困难、复杂，而且极易出错。

程序员必须掌握与网络有关的大量细节，有时甚至要对硬件有深刻的认识。

一般地，我们需要理解连网协议中不同的“层”（Layer）。

而且对于每个连网库，一般都包含了数量众多的函数，分别涉及信息块的连接、打包和拆包；这些块的来回运输；以及握手等等。

这是一项令人痛苦的工作。

但是，连网本身的概念并不是很难。

我们想获得位于其他地方某台机器上的信息，并把它们移到这儿；或者相反。

这与读写文件非常相似，只是文件存在于远程机器上，而且远程机器有权决定如何处理我们请求或者发送的数据。

Java最出色的一个地方就是它的“无痛苦连网”概念。

有关连网的基层细节已被尽可能地提取出去，并隐藏在JVM以及Java的本机安装系统里进行控制。

我们使用的编程模型是一个文件的模型；事实上，网络连接（一个“套接字”）已被封装到系统对象里，所以可象对其他数据流那样采用同样的方法调用。

除此以外，在我们处理另一个连网问题——同时控制多个网络连接——的时候，Java内建的多线程机制也是十分方便的。

本章将用一系列易懂的例子解释Java的连网支持。

15.1 机器的标识当然，为了分辨来自别处的一台机器，以及为了保证自己连接的是希望的那台机器，必须有一种机制能独一无二地标识出网络内的每台机器。

早期网络只解决了如何在本地网络环境中为机器提供唯一的名字。

但Java面向的是整个因特网，这要求用一种机制对来自世界各地的机器进行标识。

为达到这个目的，我们采用了IP（互联网地址）的概念。

IP以两种形式存在着：(1) 大家最熟悉的DNS（域名服务）形式。

我自己的域名是。

所以假定我在自己的域内有一台名为Opus的计算机，它的域名就可以是。

毕业设计(论文)外文资料翻译【范本模板】

南京理工大学紫金学院毕业设计（论文）外文资料翻译系：机械系专业：车辆工程专业姓名:宋磊春学号:070102234外文出处：EDU_E_CAT_VBA_FF_V5R9(用外文写)附件：1。

外文资料翻译译文；2.外文原文.附件1：外文资料翻译译文CATIA V5 的自动化CATIA V5的自动化和脚本：在NT 和Unix上：脚本允许你用宏指令以非常简单的方式计划CATIA。

CATIA 使用在MS –VBScript中(V5.x中在NT和UNIX3。

0 )的共用部分来使得在两个平台上运行相同的宏。

在NT 平台上：自动化允许CATIA像Word/Excel或者Visual Basic程序那样与其他外用分享目标。

ATIA 能使用Word/Excel对象就像Word/Excel能使用CATIA 对象。

在Unix 平台上:CATIA将来的版本将允许从Java分享它的对象。

这将提供在Unix 和NT 之间的一个完美兼容。

CATIA V5 自动化：介绍（仅限NT）自动化允许在几个进程之间的联系:CATIA V5 在NT 上：接口COM：Visual Basic 脚本(对宏来说)，Visual Basic 为应用（适合前:Word/Excel )，Visual Basic。

COM（零部件目标模型)是“微软“标准于几个应用程序之间的共享对象。

Automation 是一种“微软“技术,它使用一种解释环境中的COM对象。

ActiveX 组成部分是“微软“标准于几个应用程序之间的共享对象,即使在解释环境里。

OLE（对象的链接与嵌入）意思是资料可以在一个其他应用OLE的资料里连结并且可以被编辑的方法(在适当的位置编辑）.在VBScript,VBA和Visual Basic之间的差别：Visual Basic(VB）是全部的版本。

它能产生独立的计划,它也能建立ActiveX 和服务器。

它可以被编辑。

VB中提供了一个补充文件名为“在线丛书“(VB的5。

毕业设计文档成果规范化要求

毕业设计（论文）文本格式及要求1.A4纸页边距调整要求：上 4.1 下2.7左 2.6 右2.32. A4纸行距要求：固定值20磅或多倍行距1.1-1.2倍（一）外文翻译通过文献查阅与翻译，进一步提高掌握使用外文的能力，熟悉本专业的几种主要外文书刊，了解毕业设计（论文）课题的国内外信息与动向。

（体育类、艺术类专业的毕业生，外文翻译不作要求，但是在论文正文中按要求需要翻译成外文的仍然不变）1、格式：（1）外文（译文前面附被翻译的外文原件复印件）；（2）翻译成中文格式：①标题(宋体小二号加粗居中)②署名(宋体五号居中)③翻译正文(宋体小四号)④外文著录(times new roman小四号)2、内容要求：（1）阅读每位学生在文献查阅环节中，必须阅读5～10万个印刷符号的外语文献资料（最好阅读与课题或本专业有联系的内容），择其重要的翻译1～2万个印刷符号（约3000汉字）。

（2）翻译①标题应真实地反映出翻译外文的主体内容或原外文标题内容，一般控制在20个汉字以内。

可以用副标题对标题予以补充说明；②标题下方正中为外文作者署名；③外文翻译成中文的内容；④外文著录。

为了反映文稿的科学依据和译者尊重他人研究成果的严肃态度以及向读者提出有关信息的出处，要求译者按著录/题名/出版事项顺序排列注明：期刊——著者，题名，期刊名称，出版年，卷号（期号），起始页码。

书籍——著者，书名、版次（第一版不标注），出版地，出版者，出版年，起始页码。

（二）开题报告（含文献综述）1、格式：（1）课题名称；(宋体小二号加粗居中)（2）学生、指导教师和教学单位署名；(宋体五号居中)（3）开题报告的正文撰写。

(宋体小四号)2、内容要求：（1）课题名称要求与毕业设计（论文）正文标题名称一致（一般控制在20个汉字以内，可以用副标题对标题予以补充说明）。

（2）学生、指导教师和教学单位署名：课题下方正中即是学生署名，学生署名下方即是指导教师署名，指导教师署名下方即是教学单位署名（教学单位指学院）。

外文翻译格式及规范

嘉兴学院毕业论文（设计）外文翻译撰写格式规范一、外文翻译形式要求1、要求本科生毕业论文（设计）外文翻译部分的外文字符不少于1.5万字, 每篇外文文献翻译的中文字数要求达到2000字以上，一般以2000~3000字左右为宜。

2、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。

3、外文翻译应包括外文文献原文和译文，译文要符合外文格式规范和翻译习惯。

二、打印格式嘉兴学院毕业论文（设计）外文翻译打印纸张统一用A4复印纸，页面设置：上：2.8；下：2.6；左：3.0；右：2.6；页眉：1.5；页脚：1.75。

段落格式为：1.5倍行距，段前、段后均为0磅。

页脚设置为：插入页码，居中。

具体格式见下页温馨提示：正式提交“嘉兴学院毕业论文（设计）外文翻译”时请删除本文本中说明性的文字部分（红字部分）。

嘉兴学院本科毕业论文（设计）外文翻译题目：（指毕业论文题目）学院名称：服装与艺术设计学院专业班级：楷体小四学生姓名：楷体小四一、外文原文见附件（文件名：12位学号+学生姓名+3外文原文．文件扩展名）。

二、翻译文章翻译文章题目（黑体小三号，1.5倍行距，居中）作者（用原文，不需翻译，Times New Roman五号，加粗，1.5倍行距，居中）工作单位（用原文，不需翻译，Times New Roman五号，1.5倍行距，居中）摘要：由于消费者的需求和汽车市场竞争力的提高，汽车检测标准越来越高。

现在车辆生产必须长于之前的时间并允许更高的价格进行连续转售……。

(内容采用宋体五号，1.5倍行距)关键词：汽车产业纺织品，测试，控制，标准，材料的耐用性1 导言（一级标题，黑体五号，1.5倍行距，顶格）缩进两个字符，文本主体内容采用宋体（五号），1.5倍行距参考文献（一级标题，黑体五号， 1.5倍行距，顶格）略（参考文献不需翻译，可省略）资料来源：AUTEX Research Journal, V ol. 5, No3, September 2008*****译****校（另起一页）三、指导教师评语***同学是否能按时完成外文翻译工作。

毕业设计外文文献翻译【范本模板】

毕业设计（论文)外文资料翻译系别：专业：班级:姓名：学号:外文出处:附件： 1. 原文; 2。

译文2013年03月附件一：A Rapidly Deployable Manipulator SystemChristiaan J。

J。

Paredis, H. Benjamin Brown，Pradeep K. KhoslaAbstract:A rapidly deployable manipulator system combines the flexibility of reconfigurable modular hardware with modular programming tools，allowing the user to rapidly create a manipulator which is custom-tailored for a given task. This article describes two main aspects of such a system，namely，the Reconfigurable Modular Manipulator System （RMMS)hardware and the corresponding control software。

1 IntroductionRobot manipulators can be easily reprogrammed to perform different tasks, yet the range of tasks that can be performed by a manipulator is limited by mechanicalstructure。

Forexample，a manipulator well-suited for precise movement across the top of a table would probably no be capable of lifting heavy objects in the vertical direction. Therefore，to perform a given task,one needs to choose a manipulator with an appropriate mechanical structure.We propose the concept of a rapidly deployable manipulator system to address the above mentioned shortcomings of fixed configuration manipulators。

毕业设计(论文)外文资料及译文(模板)

2、译文必须采用计算机输入、打印。

3、A4幅面打印，于左侧装订。

二、撰写要求
1、外文文献内容与所选课题相关。

2、本科学生译文汉字字数不少于4000字，高职学生译文汉字字数不少于2000字。

三、格式要求
1、译文字号：中文小四号宋体，英文小四号“Times New Roman”字型，全文统一，首行缩进2个中文字符，1.5倍行距。

2、译文页码：页码用阿拉伯数字连续编页，字体采用“Times New Roman”字体，字号小五，页底居中。

3、译文页眉：眉体使用单线，页眉说明五号宋体，居中“大连东软信息学院本科毕业设计（论文）译文”。

大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文。

本科毕业设计(论文)外文翻译译文

本科毕业设计（论文）外文翻译译文学生姓名：院（系）：油气资源学院专业班级：物探0502指导教师：完成日期：年月日地震驱动评价与发展：以玻利维亚冲积盆地的研究为例起止页码：1099——1108出版日期：NOVEMBER 2005THE LEADING EDGE出版单位：PanYAmericanYEnergyvBuenosYAiresvYArgentinaJPYBLANGYvYBPYExplorationvYHoustonvYUSAJ.C.YCORDOVAandYE.YMARTINEZvYChacoYS.A.vYSantaYCruzvYBolivia 通过整合多种地球物理地质技术，在玻利维亚冲积盆地，我们可以减少许多与白垩纪储集层勘探有关的地质技术风险。

通过对这些远景区进行成功钻探我们可以验证我们的解释。

这些方法包括盆地模拟，联井及地震叠前同时反演，岩石性质及地震属性解释，A VO/A V A,水平地震同相轴，光谱分解。

联合解释能够得到构造和沉积模式的微笑校正。

迄今为止，在新区有七口井已经进行了成功钻探。

基质和区域地质。

Tarija/Chaco盆地的subandean 褶皱和冲断带山麓的中部和南部，部分扩展到玻利维亚的Boomerange地区经历了集中的成功的开采。

许多深大的泥盆纪气田已经被发现，目前正在生产。

另外在山麓发现的规模较小较浅的天然气和凝析气田和大的油田进行价格竞争，如果他们能产出较快的油流而且成本低。

最近发现气田就是这种情况。

接下来，我们赋予Aguja的虚假名字就是为了讲述这些油田的成功例子。

图1 Aguja油田位于玻利维亚中部Chaco盆地的西北角。

基底构造图显示了Isarzama背斜的相对位置。

地层柱状图显示了主要的储集层和源岩。

该油田在Trija和冲积盆地附近的益背斜基底上，该背斜将油田和Ben i盆地分开（图1），圈闭类型是上盘背斜，它存在于连续冲断层上，Aguja有两个主要结构：Aguja中部和Aguja Norte,通过重要的转换压缩断层将较早开发的“Sur”油田分开Yantata Centro结构是一个三路闭合对低角度逆冲断层并伴随有小的摆幅。

译文标准格式模板

切记：1、原文在前、译文在后合订后放入资料袋。

2、译文的排版规范同毕业论文一致译文要求：1、不少于3000汉字的译文；2、选取的外文文献内容必须与课题内容相关，原则上应来源于最新专业期刊，并说明出处（参照”参考文献的著录”要求）；3、译文应于毕业设计中期完成，交指导教师（或评阅人）批阅、签字。

最后存档译文不应有老师批改的痕迹。

4、译文要求文字通顺，语言流畅，无错别字，统一用A4纸打印，且按教务处印制的统一格式封皮左侧装订。

同时上交电子文档（word）由各学院存档。

版面要求：页码：居中、底部；行距：固定值20；页边距：上2.5cm，下2.5cm，左3cm、右2.5cm；在LSGM体系中掺杂SiO2对其晶界电导率的影响(译文题目，小三黑体，段前段后各空一行)（全文字体要求：中文选择宋体，西文选择Times New Roman)SiO2-Tolerant Grain-Boundary Conduction (原文题目，五号，Times New Roman)Electrochemical and Solid-State Letters, 2014，13 (3)：B28-B31(原文出处，五号斜体，Times New Roman)王娜译长春工业大学化学与生命科学学院(译者信息，五号，宋体)摘要：研究了在La0.8Sr0.2Ga0.8Mg0.2O3-δ体系中掺杂SiO2杂质对其晶界电导率的影响。

结果表明：即使增加了500-2000 ppm SiO2，LSGM的晶界传导率仅受到轻微的影响。

然而在氧化铈基体中掺杂500-2000 ppm SiO2其晶界电阻率明显的增加至大约780倍，通过SrO基质附近聚集的酸性硅质相来解释在LSGM样品中晶界传导对硅质杂质具有较高容忍性。

(小四；“摘要：”加粗；段前段后各空一行,行距：固定值20；)关键词：氧化铈晶界电阻率(小四；关键词之间空2格；“关键词：”加粗；段前段后各空一行)1. 简介/前言(小四；加粗；段前段后各空一行)稳定氧化锆的晶界电阻通常是晶粒电阻的102–104倍[1,2]，在高纯度样品中，在晶界附近氧空位的消耗是主要的[1,3]，在某种程度上SiO2 杂质甚至在几百ppm较低的浓度下对晶界传导有非常不利的作用[4-6]，SiO2杂质是普遍存在的，在陶瓷的加工、烧结和燃料电池操作方面很容易将其引入[7]。

毕业设计译文格式

(完整版)_毕业设计参考文献译文

最新外文文献翻译格式范例

毕业设计外文翻译译文

外文参考文献译文及原文【范本模板】

毕业设计(论文)外文资料及译文(模板)

毕业设计(论文)外文资料和译文格式要求(模板)

毕业设计译文格式要求

毕业设计(论文)外文原文及译文

毕业设计论文中英文翻译要求(最新)

毕业设计(论文)外文资料翻译(学生用)

毕业设计(论文)外文资料翻译【范本模板】

毕业设计文档成果规范化要求

外文翻译格式及规范

毕业设计外文文献翻译【范本模板】

毕业设计(论文)外文资料及译文(模板)

本科毕业设计(论文)外文翻译译文

译文标准格式模板