驯龙高手制作人采访记

合集下载

梅特勒称重使用说明书

XK3141 IND131/331 称重显示控制器
使用说明书
本手册版权归梅特勒-托利多(常州)称重设备系统有限公司所有，未经许可不得翻印、修改或引用！ METTLER TOLEDO 为梅特勒-托利多公司的注册商标！
警告
1、请专业人员调试、检测和维修系统。 2、请保持本设备良好接地。
注意
1、严禁带电插拔。 2、请先切断电源，再进行电气设备连接，检修。
第 3 章操作...................................................................................................................................18 3.1 显示屏..............................................................................................................................18 3.2 按键..................................................................................................................................19 3.3 菜单..................................................................................................................................20 3.3.1 快捷操作菜单与设置菜单...................................................................................20 3.3.2 菜单模式...............................................................................................................20 3.4 应用..................................................................................................................................21 3.4.1 目标值...................................................................................................................21 3.4.2 比较器...................................................................................................................21

驯龙高手中的音乐鉴赏

动画音乐鉴赏——驯龙高手配乐：约翰·鲍威尔《驯龙高手》作为2010年比较卖座的一部动画电影，其丰富的画面、精良的制作、优美的旋律……都是它成功的因素，而其中丰富的音乐更是为影片增色不少，在视听观赏性上让影片提升了一个档次。

《驯龙高手》中的配乐，是由如今在好莱坞大名鼎鼎的配乐人约翰·鲍威尔完成的，其扎实的古典功底，对凯尔特民族风格音乐的灵活运用，造就了驯龙高手中音乐的丰富性。

从第一首开始，音乐就以昂扬奔放、有着北欧风情的快步舞曲奠定了基调，悠扬活泼的苏格兰风笛和爱尔兰哨笛始终稳住了整部影片的曲风，使之张弛有度，旋律强烈却不凌乱。

约翰·鲍威尔年轻的时候曾受到过汉斯·季默的熏陶，非常注重对细节的处理，也敢于通过不同乐器来探索新的可能。

除了钢琴、单簧管以及北欧的传统名族乐器之外，他还运用了电子合成器，在音乐沉稳、流畅的基础上显得更加感动、充满活力，与片中人物的形象更加吻合。

富有典型地域色彩的音乐元素运用是《驯龙记》的配乐一个最令人称道的优点。

为了营造出故事本身应有的维京文化背景，约翰还运用了不少居尔特民间音乐元素，而第一次在影片中对配乐中的这种居尔特音乐元素产生非常强烈的存在感，是主人公和一种同龄人首次进入训练唱参加降龙术训练一幕时所用的曲子《降龙训练》。

带有浓郁居尔特风味的风笛进一步弥漫着古老欧陆的风情，放在动作段落中听来更是格外慷慨，令人血脉贲张。

该片作为一部动画电影，自然不能沉闷无趣，而这一切要归功于其中式管弦乐，这些管弦乐原创作品采用的昂扬奋进式基调，成就了《驯龙记》所需的那种积极向上的主体音乐空间，使得整个电影看来听来都绝无闷局，保持着高度的亢奋感和清醒感。

在电影中约翰·鲍威尔不仅懂得保持紧贴画面节奏的优良传统，更学会了用更加宏观的视野来组织自己针对不同目标形象缔造的主题板块。

一曲为主人公小嗝嗝与无牙打破禁忌建立友情而作的《被禁止的友谊》(Forbidden Friendship)，巧妙地将原本慷慨激昂的主题旋律内化成各种不同的面貌呈现在人们面前，听起来就像是一段丰富生动的清明上河图，交集了无数细节与内涵，却丝毫没有零乱无序、欠缺章法的感觉。

Vised_manual

MCNP Visual Editor Computer Code ManualL.L. Carter and R.A. SchwarzFor the latest information visit 1Table of Contents1.0 INTRODUCTION (5)1.1 I NSTALLATION N OTES (5)1.2 P ROGRAM B ACKGROUND (6)2.0 BEGINNING AN INTERACTIVE EDITING SESSION (7)2.1 I MPORTANT F ILES I N T HE V ISUAL E DITOR (8)2.2 T HE M AIN M ENU F UNCTIONS (9)2.3 R EADING A ND W RITING C ELL C ARDS (10)3.0 PLOTTING AND CHANGING PLOT PARAMETERS (11)3.1 U PDATE (12)3.2 L AST B UTTON (12)3.3 Z OOM C HECK B OX (12)3.4 O RIGIN C HECK B OX (12)3.5 C HANGING THE E XTENTS (13)3.6 R EFRESH C HECK B OX (13)3.7 T HE S URFACE AND C ELL C HECK B OX (13)3.8 C OLOR C HECK B OX (13)3.9 F ACETS C HECK B OX (13)3.10 WW M ESH C HECK B OX (13)3.11 R ECT C HECK B OX (14)3.12 P LOT R OTATION O PTIONS (14)3.13 S CALES C HECK B OX (14)3.14 R ES T EXT B OX (14)3.15 C HANGING THE B ASIS (14)3.16 V IEWING G LOBAL/L OCAL C OORDINATES (14)3.17 S ETTING C ELL L ABELS (14)3.18 L EVEL P ULLDOWN M ENU (15)4.0 THE SURFACE WINDOW (16)4.1 C REATING A S URFACE (16)4.2 S CANNING A S URFACE (16)4.3 D ELETING A S URFACE (17)4.4 E DITING A S URFACE (17)4.5 H IDING AND S HOWING S URFACES (17)4.6 S URFACE C OMMENTS (17)4.7 E NTERING S URFACE D IMENSIONS IN I NCHES (17)4.8 S URFACE D ISTANCE (18)4.9 S URFACE D ELTA (18)4.10 M ACROBODY S URFACES (18)5.0 THE CELL WINDOW (19)5.1 C REATING A C ELL (19)5.2 D ISCUSSION O F C ELL P ASTE A ND C UT O PERATIONS (20)25.4 C REATING A C ELL WITH U NIVERSES (22)5.6 U SING U NDO (23)5.7 R EGISTER (23)5.8 S CANNING A C ELL (23)5.9 D ELETING A C ELL (23)5.10 E DITING A C ELL (23)5.11 C REATE LIKE (24)Y OU CAN USE THE “C REATE LIKE” MODE TO CREATE A NEW CELL SIMILAR TO AN EXISTING CELL.A COMMON APPLICATION OF THIS IS TO CREATE A NEW CELL LIKE AN CELL THAT ALREADY EXISTS, BUT WITH A TRANSFORMATION (24)5.12 H IDING AND S HOWING C ELLS (24)5.13 C ELL C OMMENTS (24)5.14 S PLITTING A CELL (25)5.15 C REATING A S QUARE L ATTICE (27)5.16 C REATING A H EXAGONAL L ATTICE (28)5.17 S PECIAL H EX L ATTICE D ISPLAY O PTIONS (29)6.0 MATERIALS (30)6.1 C REATING A M ATERIAL (30)6.2 S CANNING A M ATERIAL (31)6.3 D ELETE A M ATERIAL (31)6.4 E DIT A M ATERIAL (31)6.5 T HE V ISED.DEFAULTS F ILE (31)6.6 M ATERIAL L IBRARY (33)6.7 M ATERIAL O PTIONS (33)7.0 IMPORTANCES (34)7.1 S ETTING C ELL I MPORTANCES (34)7.2 U SING A S CALE F ACTOR (34)7.3 U SING A G EOMETRIC F ACTOR (34)7.4 T HE I MPORTANCE D ISPLAY (35)7.5 T RUNCATING IMPORTANCES (35)8.0 TRANSFORMATIONS (36)9.0 RUN (37)10.0 PARTICLE DISPLAY (39)10.1 SDEF S OURCE P LOTTING (39)10.2 KCODE S OURCE P LOTTING (40)10.3 P ARTICLE T RACK P LOTTING (40)10.4 S ETTING P OINT C OLOR AND S IZE (41)10.5 S ETTING E NERGY OR W EIGHT R ANGES (41)10.6 P ROBLEMS G ENERATING P ARTICLE T RACKS (41)11.0 TALLY PLOTS (43)313.0 3D VIEW (47)13.1 3D C OLOR P LOTS (47)13.2 3D U PDATE THE P LOT B ASIS (48)13.3 C OLOR BY C ELL/S URFACE (48)13.4 D RAW L INES A ROUND C ELLS (48)13.5 C OLOR C ELLS BY M ATERIAL (48)13.6 3D S HADING (48)13.7 D ISTANCE S HADING (48)13.8 P OINT/P LANE S OURCE T YPE (48)13.9 S HOW THE P LOT P LANE (49)13.10 H IDE/S HOW C OOKIE C UTTERS (49)13.11 P LOT TO THE O UTSIDE W ORLD/P LOT P LANE (49)13.12 P LOT R ESOLUTION (49)13.13 3D R ADIOGRAPHIC P LOTS (49)14.0 READ AGAIN (51)15.0 BACKUP INP (51)16.0 PROBLEM REPORTING (51)17.0 REFERENCES (52)APPENDIX A (53)41.0 IntroductionThe Monte Carlo N-Particle (MCNP) computer code is a particle transport code with powerful three dimensional geometry and source modeling capabilities that can be applied to reactor physics, shielding, criticality, environmental nuclear waste cleanup, medical imaging, and numerous other related areas.Creating a MCNP input file with a line editor is both tedious and error prone as it entails arduous descriptions of geometry, tallies, sources, and optimization parameters. These input files may contain thousands of lines, and once the input file is created, substantial additional time is often required to plot and test the geometry and to correct any errors. The Visual Editor (References 1-7) was developed to assist the user in the creation of MCNP input files. Work on the Visual Editor started around 1992. The first release to RSICC was in 1997. The Visual Editor code will became part of the MCNP package with the release if version 5 of MCNP.The Visual Editor allows the user to easily set up and modify the view of the MCNP geometry and to determine model information directly from the plot window. The Visual Editor also allows the user to interactively create an input file with the help of two or more dynamic cross sectional views of the model. A wide selection of menu options enables rapid input of information and immediate visualization of the geometry and other information being created.The current version of the Visual Editor only runs on Windows platforms. Older versions of the code run on Linux and UNIX systems, however, the current code has not yet been updated on these systems.The new user should practice with a few simple problems before trying to create an involved geometry. An example exercise is given in Appendix A.The following discussion summarizes how to use the graphical interface. The Visual Editor is constructed with user friendly menu buttons so this manual is primarily to help the new user get started and to provide some detail when specific questions arise. The discussion here assumes that the user has some familiarity with the MCNP geometry specification, as described in the MCNP manual. Additional information on the Visual Editor, including training opportunities can be found at the Visual Editor website ().1.1 Installation NotesFor most applications, the Visual Editor executable can be used as distributed. The Visual Editor consists of the MCNP source code linked to graphical interface written in C++. If you want to modify the MCNP source code, you can recompile the MCNP Fortran code and link this to the Visual Editor static library.The Visual editor is compiled using Visual C++ for the compiling the graphical interface files and Visual Fortran for compiling the MCNP Fortran files. To create a Visual Editorexecutable you need to get the Visual Fortran project file and place the unprocessed Fortran source code in the Fortran source directory. The code can then be compiled either by loading the project into Visual Fortran and compiling it or by using the provided makefile within the Fortran command prompt available with Visual Fortran.If you want to do particle track plotting, cross section plotting, or run MCNP inside the Visual Editor, the xsdir file must be in the same directory as the Visual Editor executable or a path to xsdir must be specified on the system as required for running MCNP.If you want to have access to the material libraries, you need to create a “vised.defaults” file for the configuration of MCNP on your system. See the section on materials for more information on how to do this.1.2 Program BackgroundThe size of the fonts used by the windows are fixed and can not be changed. The font used is called “small fonts”. If the Visual Editor windows appear too large for your screen, it is recommended that you increase your screen resolution. The ideal screen resolution is 1280x1024.The development of the Windows Visual Editor is done on a Windows 2000 platform. For best performance, it is recommended that users run the Visual Editor in Windows 2000 or Windows XP. Table 1 below lists the different operating systems and what is known about its compatibility with the Visual Editor. If an operating system is not listed, than the code has not been tested on that platform and its functionality is not known.Table 1. Operating System Compatibility.CompatibilityOperatingSystemWindows 2000 Most compatible, this is the Visual Editor development platform. Windows XP Very compatible with 2000 version and should be just as stable. Windows NT Somewhat compatible with 2000, should still be fairly stable. Windows 98 Somewhat unstable, not recommended.Windows 95 Very unstable, not recommended.2.0 Beginning An Interactive Editing SessionUse Windows explorer to bring up the Visual Editor. Figure 1 shows a view of the initial screen. Notice that the main menu functions are shown across the top and that each plot window has its own set of plot commands. You can read in an input file by using the “File->Open” command.Figure 1. Startup configuration for the Visual Editor.To create a new geometry, you can create surfaces by selecting “Surface” from the main menu. These surfaces can then be used to create cells, but selecting “Cell” from the main menu and following the cell creation procedure discussed in the “new cell creation” section of this document.The input window, shown at the bottom of Figure 1, can be displayed by selecting “Input” from the main menu. In the input window, a title card indicating the creation date is created by default. If you want to add you own title, enter it above this card, then select “Save-Update” from the menu. This will temporarily cause the line containing the creation date to go away, but it will come back as a comment card after the first cell is created.The input window is divided into two areas, the upper area prints out Visual Editor andMCNP warnings and errors. The bottom window contains the entire input file. You canedit the file in this window and then select the “Save-Update” menu option to update theplots to reflect the changes made. This gives you the freedom to work either in editormode or use the graphical interface commands. If the file is modified by hand in such away that it is no longer valid, it is possible when doing “Save-Update”, that the Fortranwill generate a fatal error causing the Visual Editor to terminate, although an attempt ismade to trap most fatal errors.When doing a “Save – Update” command, the Visual Editor writes out the input to a temporary file name called inpn. When you are ready to save the file to a permanent file,use the “File->Save” command or the “File->SaveAs” command.The Visual Editor will automatically back up the file every five minutes to a file called “inpn.sav”, so if the Visual Editor crashes, y ou will not lose more than 5 minutes ofwork. Also, if the Visual Editor encounters a MCNP fatal error that it can not recoverfrom, it will try to save the input into a file called “inpcrash”.2.1 Important Files In The Visual EditorTable 2 shows a list of the files used by the Visual Editor. The Visual Editor prints out a number of auxiliary files. Because of this, you may want to run the Visual Editor in itsown directory and transfer the input files you are creating or working on to that directory.Table 2. Files used by the Visual Editor.File Name Descriptioninp Used by the Visual Editor as the default input file name. This file isoverwritten each time the editor starts up. The Visual Editor will giveunpredictable results if you try to read this file in as the input file.inpn Inpn is the file that is created when doing a “Save-Update” command in the input window. The Visual Editor will give unpredictable results if you try toread this file in as the input file.inpn1, inpn2, inpn3, … By selecting “backup” from the main menu a new inpn? (inpn1, inpn2, inpn3, …) file is created representing the contents of the current file being worked on.inpn.sav The input file is backed up every 5 minutes to this file, so if the systemcrashes you will not lose more than 5 minutes of work. The Visual Editorwill give unpredictable results if you try to read this file in as the input file. inpcrash If MCNP generates a fatal error that results in a “stop” statement, a message is sent to the Visual Editor telling the user that the code is about to terminate.It then saves the current input file into a file called inpcrash. This will allowthe user to get the file that was generated up to the point of the fatal error.The Visual Editor will give unpredictable results if you try to read this file inas the input file.outp, outq, … In normal plotting mode, the outp file is overwritten and does notsequentially increase. In other modes, such as 3D plotting, particle trackplotting, tally plotting and running, the outp file name increases sequentiallyjust like when running MCNP outside the Visual Editor. If the VisualEditor crashes, always check this file to see if there are fatal MCNPerrors not trapped by the Visual Editor.dfill Auxiliary file used to contain a fill matrix if one exists in the problem. dcinp Auxiliary file that holds the comment cards from the input file.ddinp Auxiliary file that holds the data cards not recognized by the Visual Editor outmc Contains MCNP output messages, normally written to standard out. If the Visual Editor crashes, always check this file to see if there are fatalMCNP errors not trapped by the Visual Editor.vised.defaults The file containing the location of xsdir and the material libraries, this file is needed for using the material libraries and for selecting isotopes whencreating materials.2.2 The Main Menu FunctionsTable 3 provides an overview of the main menu options and their purpose.Table 3. Main Menu Options.Menu Option DescriptionFile Used to open and save files. File-> New View is used to open additional plot windows into the geometry. The list of recently used files may be unreliableon some systems.Input Used to bring up a simple text editor containing the complete contents of the input file, including cards not recognized by the Visual Editor. The input filecan be edited by hand in this window.Update Plots Update both plot windows.Surface Bring up the surface window to scan, create or modify surfaces.Cell Bring up the cell window to scan, create or modify cells.Data Menu to common data cards: materials, importances, transformations.Run Enable the running of MCNP input files.Particle Display Bring up the source window that allows for source point display and particle track plotting.Tally Plots Allow the plotting of tallies from a runtpe or mctal files. This is the same capability that currently exists when requesting MCPLOT (mcnpinp=filename z options)Cross Section Plots Allow the plotting of MCNP cross sections. This is the same capability that currently exists when requesting MCPLOT (mcnp inp=filename ixz options)3D View Allows the rendering of a 3D view of the geometry or a radiographic image. Read_again Update the plots after the file that was read in has been modified by anexternal text editor.Backup Creates a backup file that sequentially increases (inpn1, inpn2, …).View Select the active plot window.Help Shows the version number.2.3 Reading And Writing Cell CardsThe attempt is made to read the input file and write out the same information to the inpn file. If the input file is created outside the Visual Editor, you will find that when you save it, the Visual Editor will change the order of the lines in the input file. Below is the order in which the Visual Editor writes out the input file:1. Title card2. Cell Cards3. blank line4. Surface Cards5. blank line6. Transformations7. Mode8. Source9. Materials10. Importances11. Other data [VOL, PWT, EXT, FCL, PD, DXC, NONU, WWN, TMP]12. Data not recognized by the Visual EditorThe editor does it best to keep the original comments in the proper locations. The "$" comments from the inp file for cell and surface cards are read into the Visual Editor, but only one "$" comment will be written out for a cell or surface card; i.e., if there are more than one "$" comments for a given cell or surface, only the first one will be written to the inpn file. The Visual Editor will print out an error message saying the “$ comment is lost.”There are a number of data cards that are still not recognized by the Visual Editor such as the source and tally cards. These are stored in a temporary file and written back out to the input file when it is saved. All cards that are recognized by the Visual Editor will be formatted to its specific style. For example importances are written out in a special format that uses a "$" comment on each line to show the cell numbers involved for that line. The Visual Editor also does not currently allow the cell parameters to be specified on the cell card, it will strip off the cell card parameters and place them in a data block.3.0 Plotting And Changing Plot ParametersThe Visual Editor starts up with two default plot windows. Additional plot windows can be created by selecting File->New View. This will open up a new plot window with the plot parameters set to default values.Figure 2 shows a view of the Visual Editor plot window and the various plotting options available on the top and side of the plot window. Also shown is the menu that is displayed when you right click in the plot window. The top portion of this menu can be used to change some of the plot parameters. Also, included in this menu are some shortcuts to common surface and cell operations.To print out a hard copy of a plot, select “File->Print” from the main menu and it will send the contents of the currently selected window to the printer.Figure 2. Plot Window Options.3.1 UpdateAs it's name implies, the "Update" button is used to redraw the plot for that window.To update all plots, use the “Update plots” main menu option. You typically use the “Update plots” button to create the plots after reading in a new input file. This is not done automatically because there are times when you do not want the plot to be displayed because it would take too long to generate.When you change the basis, origin, or extent parameters by hand, you need to select “Update” in the specific window or "Update plots" from the menu to redraw the plots with the new plot values.3.2 Last ButtonThe "Last" button enables you to go back to prior plots. For instance, if you use the “Zoom” button to zoom in on a region in the geometry, the last button will take you back to the “Unzoomed” view. All of the plot parameters are saved when the plot is changed and "Last" will go backwards through the sequence of plots. The parameters changed by "Origin", "Zoom" and "Basis" can all be recalled with "Last". Last remembers the last 1000 plots made for each plot window.3.3 Zoom Check BoxThe "Zoom" check box enables the user to magnify a portion of the plot. When the "Zoom" check box is selected, the user can drag the mouse across a portion of the geometry and that area will be magnified. This is useful for intricate work in small cells.The Visual Editor stays in zoom mode until you uncheck the “Zoom” check box. This allows for multiple zoom operations to be done in a row.Sometimes it is useful to click zoom on one plot and then drag the mouse across a zoom area in a different plot. The identified area will then be shown in the original plot window.3.4 Origin Check BoxThe origin of the two plots automatically defaults to 0,0,0. These coordinates can be set by hand by entering the desired origin values in the three text boxes below the “Origin” check box. Once the new origin is ready to be implemented, select "Update plots". Another way to adjust the origin involves selecting the "Origin" check box for the plot and then setting the origin by clicking in the plot to define the location for the new center of the plot. The origin can be set in either plot window. The plot will stay in “origin” mode until the origin check box is clicked again to turn it off.The buttons to the left of the origin values, enable the user to change the origin “x”, “y” or “z” value by clicking on the coordinate to be changed and selecting its value with a click of the mouse from one of the plot windows. For example, if the right plot is an xyview and the left plot is an xz view, you can change the elevation of the xy view by clicking the z box for the right plot and then clicking the at a different z value on the left plot. The z for the right plot will change to that selected value, resulting in a different cross sectional view.3.5 Changing the ExtentsThe extents for the plots automatically default to 100. The extents can be changed by typing in desired extents under the “Extent” label and selecting “Update” or by using the slider bar on top of the plot windows. This modifies the extent by a scale factor between 0.1 and 10.The buttons to the left of the extent values, allow the user to square up the extents. This is often used after “zooming” in on a region. Both extents will be set to the value you click on making them equal.3.6 Refresh Check BoxThis check box defaults to the checked “on” position. Turn this check box off if you do not want to update the plot window when cells or surfaces are modified or when “Update Plots” is selected from the main menu. There are times when you may not want to update a particular plot window. For example, you might want to turn off plotting if the view contains a large lattice that is time consuming to plot. Be careful when you use this check box to turn off plotting, since the plot will not be updated until you turn this check box on again.3.7 The Surface and Cell Check BoxWhen the "Surface" check box is turned on, surface numbers will appear on the plots next to their respective surface. If the check box is turned off, surface numbers do not appear. Next to the surface check box is a text box where you can enter the font size to use for the surface label. Increase this number to increase the label sizeWhen the "Cell" check box is turned on, cell numbers will appear inside the cells. The meaning of the cell number is determined by the cell label that has been selected. As with surface numbers, the size of the font used for cell numbers can be changed by changing the number in the text box.3.8 Color Check BoxThis check box will enable col or plotting. The color can be set to represent Materials or any of the items specified by the “color by” option, as shown in Figure 2.3.9 Facets Check BoxWhen displaying macrobody surfaces, this check box will change the display to show surface facet numbers instead of the macrobody surface numbers.3.10 WW Mesh Check BoxBy checking this check box, the weight window mesh will be displayed if this option is used in the active input file.3.11 Rect Check BoxSelect this check box to change the plot window to a rectangular plot instead of a square plot. A rectangular plot is needed to see the grid lines or the plot legend. Tally and cross section plots also look better in a rectangular plot instead of a square plot.3.12 Plot Rotation OptionsThe 2D plots can be rotated through three different angles. Selecting “Ax” will rotate the plot in a counter clockwise direction around the axial axis pointing out of the plot window. The default rotation angle is 15 degrees. The “Ver” option will rotate th e 2D view along the angle between the horizontal and axial vector. This will cause the view to rotate around the vertical axis. The “Hor” option will rotate the 2D view along the angle between the vertical and axial vector. This will cause the view to rotate around the horizontal axis.3.13 Scales Check BoxThe “Scales” pull down menu allows you to display a border around the geometry plot ora grid across the plot. This can only be seen if the “Rect” check box has been set.3.14 Res Text BoxThe resolution text box sets the resolution for color plots. The default value is 300. The maximum value is 3000. The higher the resolution, the better the color resolution on a color plot. The drawing time will increase as this value increases.3.15 Changing the BasisOne of the advantages of multiple plots is the ability to view the same geometry with multiple cross sectional slices. This is especially helpful with complex three-dimensional geometries. The left plot in the Editor defaults to an xz basis and the right defaults to a xy basis. A "Basis" pull down menu is available in the top left portion of the plot window with the choices of xy, xz, yx, yz, zx, and zy.The basis menu is also available by clicking the right button in the plot window. The basis can also be entered by hand by setting the six basis vectors and then selecting the “Update” button or “Update Plots” menu option to redraw the plots.3.16 Viewing Global/Local CoordinatesThe Global/local menu determines how the displayed coordinates at the top of the plot window are to be interpreted. With local set, the coordinates are for the universe prior to being transformed because of a transformation or a fill, otherwise the coordinates are relative to the origin of the geometry.3.17 Setting Cell LabelsSelecting the "Labels" button with the right mouse button will bring up menu which lists the cell labels recognized by MCNP. These labels are: CEL, IMP:, RHO, DEN, VOL, FCL:, MAS, PWT, MAT, TMPn, WWNn:, EXT:p, PD, DXC:, U, LAT, FILL, and NONU. Those items with a ":" have a pull right menu to choose p, n, e. Items with an“n” in their name require that you enter the requested value at the top of the plot window in the “n =” text box.3.18 Level Pulldown MenuThe level pulldown menu allows you to hide lower levels of a lattice for complex geometries that have lattices inside of lattices, such as a reactor core filled with fuel assemblies. The geometry will only be plotted to the level specified. Level 1 is the top level, normal geometries will plot at this level. Level 3 will go down one universe level, level 5 will go down two universe levels.By setting these level buttons, you can significantly decrease the amount of time it takes to make a plot of a lattice geometry by su ppressing the plotting of lower universe information. Additionally, you can use the special lattice cell label options to plot useful information about the lattice geometry.4.0 The Surface WindowFigure 3 shows the surface window. This window is used to create new surfaces, delete surfaces and modify surfaces. The operation that is being performed is determined by the mode shown at the bottom of the surface window. The default mode is “Create new” which will create a new surface. All recognized MCNP surface types can be created or modified.Figure 3. The surface window.4.1 Creating a SurfaceTo create a new surface, first select a surface type, either by clicking on the “Surfaces” menu option or doing a right click in the gray area of the window as demonstrated in Figure 3. All surface types will show up including surfaces defined by points and macrobody surfaces.The surface number will be set by default when creating a surface. The editor uses the last valid surface number and incremen ts it by one. The surface coefficients are typically entered by hand. For some of the simple surfaces you can use the mouse to set the coefficients to an approximate value by clicking on the screen. For example, for a simple sphere (SO surface), you can set the radius, by clicking on the screen.You can indicate that the surface is a reflective surface by clicking on the “Reflective” check box. Alternatively, you can assign a transformation to the surface, by either entering the transformation number in by hand or clicking on the “Transformation” button to bring up a list of available transformations for the input file. When you select a transformation, the number of the transformation is placed in the transformation text box. Select “Register” from the menu to create the surface and add it to the input file. Once a surface is created, the mode changes to “Create like” which will default to creating additional surface, just like the one that was created.4.2 Scanning a SurfaceYou scan a surface, by clicking on the “Scan” mode and then dragging the mouse across。

所有的探索都是为了“故事为王”——原力动画总监沈琰讲述28年动画之路

28影视制作从二维到三维：一个动画艺术家的转型之路和大多数孩子一样,年少时的沈琰一看动画就挪不开眼睛,《花仙子》、《森林大地》、《九色鹿》、《大闹天宫》……这一部部动画片点亮了她的孩提时光。

她至今记得小学时偶然在《大闹天宫》的演职人员名单看到了沈琰这个名字，长大后特意再扒着字幕找却没找到。

但回头想想，沈琰觉得这可能在冥冥中暗示自己注定要终身以动画为业。

刚入行时, 沈琰从事二维动画项目。

20世纪90年代初，中国动画加工业开始崛起，她从家乡南京出发，跟着项目到苏州、上海、杭州、深圳，一路向南，“当时的动画圈类似于现在的剧组，都是跟项目走，一个项目结束了就去另一个。

”那段时期，沈琰参与了一系列法国和美国的加工片，《夜行神龙》《第5个火枪手》《茜茜公主》《古堡小精灵》《阿伽叶王子》《大力神》《鲨鱼》等等。

这些加工片普遍采用欧美已经非常成熟的动画制作技术和流程，“当时中国的院校里没有动画专业，进入动画公司就如同进了学校。

”加上各大公司的导演和领导都是上影厂老一辈的艺术家，沈琰在工作中学到了许多非常宝贵的技术和知识。

在二维动画领域工作十二年后，一次偶然机会沈琰在网上看到了原力动画培训班正在招生，当时她已萌生了学习三维动画的想法。

于是她报名培训，师从Maya 在中国教师认证的第二人、原力动画CEO 赵锐，“我一接触三维就欲罢不能，完全被迷住了。

”在Maya 中看到三维动画中的摄像机时，她不禁高呼太方便了，“二维中旋转文/陈晨所有的探索都是为了“故事为王”——原力动画总监沈琰讲述28年动画之路沈琰，动画总监、导演,1992 年到 2003 年间，参与了《第五个火枪手》《茜茜公主》《古堡小精灵》等大量法、美等国的优秀动画片的原画创作、绘景、设计稿工作，以及《西游记》等国产动画片的原画创作。

2003年5月至今，先后在原力动画担任动画部门主管、CG事业部经理、动画总监、动画导演，期间制作的作品包括《驯龙记》《瑞奇和叮当》《妈妈咪鸭》《风语咒》《深海》 ( 制作中)、《故宫里的大怪兽》(制作中)等。

Fitbit Inspire HR 手冊 V2.6说明书

使用手冊版本 2.6目錄開始 (5)包裝盒內物品 (5)為智慧手環充電 (6)透過手機進行設定 (7)在 Fitbit 應用程式中查看您的資料 (7)佩戴 Inspire HR (8)整日佩戴和運動時的佩戴方式 (8)慣用手 (9)佩戴與保養技巧 (9)更換錶帶 (10)移除錶帶 (10)安裝錶帶 (10)基本資訊 (11)導覽 Inspire HR (11)基本導覽 (11)快速設定 (13)調整設定 (13)變更錶面 (14)手機通知 (15)設定通知 (15)查看傳入通知 (16)關閉通知 (16)計時 (17)設定鬧鐘 (17)解除或休眠鬧鐘 (18)使用計時器和碼錶 (18)活動與健康 (19)查看統計資料 (19)追蹤每日活動目標 (20)2追蹤每小時的活動 (20)追蹤您的睡眠 (20)設定睡眠目標 (21)瞭解您的睡眠習慣 (21)查看您的心率 (21)練習引導式呼吸 (22)運動和心臟健康 (23)自動追蹤您的運動 (23)使用運動應用程式追蹤與分析運動 (23)GPS 要求 (24)自訂運動設定與快速鍵 (25)查看您的運動摘要 (25)查看您的心率 (25)預設心率區間 (26)自訂心率區間 (26)分享您的活動 (27)檢視心肺健康分數 (27)更新、重新啟動和清除 (28)更新 Inspire HR (28)重新啟動 Inspire HR (28)清除 Inspire HR (28)疑難排解 (29)找不到心率訊號 (29)沒有 GPS 訊號 (29)其他問題 (30)General Info and Specifications (31)感應器與元件 (31)材質 (31)無線技術 (31)觸覺反饋 (31)電池 (31)記憶體 (31)顯示幕 (31)3環境條件 (32)瞭解詳情 (32)退貨政策和保固 (32)Regulatory and Safety Notices (33)USA: Federal Communications Commission (FCC) statement (33)Canada: Industry Canada (IC) statement (34)European Union (EU) (35)Customs Union (36)Argentina (36)Australia and New Zealand (36)Belarus (37)China (37)India (38)Israel (39)Japan (39)Mexico (39)Morocco (39)Nigeria (40)Oman (40)Pakistan (40)Philippines (41)Serbia (41)South Korea (41)Taiwan (42)United Arab Emirates (44)Zambia (44)Safety Statement (44)45開始Fitbit Inspire HR 是一款方便的心率健身智慧手環，可幫助您每天養成健康的習慣。

crayon 采访

IGBANG的G-Dragon疯了。

他在台上完完全全地疯了。

他一直勇於表达对音乐的热情，近日更主动申请在新专辑《ONE OF A KIND》上贴上19禁标签。

〈那XX〉等部份歌曲在专辑评审时被定为危害青少年之媒体物品，虽然10代歌迷无法购买专辑和音源对销量有一定影响，但他在保持原曲的意旨之大前提下仍作出如此决定。

正因如此，G-Dragon时隔三年再度推出的音乐更为坦白直接。

就像「我是有才干的熊，不，是狐狸不是熊。

我可是倒霉的家伙，但身骄肉贵。

哎，我这麼红，对不起啦。

」还有「我有什麼比不上那家伙」、「让我为没灵感的各位送上一棵柿子树，我的倔强可不输一众傲慢的人」等歌词。

若大家细心留意，这此歌词并不是想像中那般危险和值得忧虑。

GD身兼制作人和SOLO歌手，这反而能加倍突显其音乐特色。

既然他在自己的专辑上贴上19禁标签，为了原汁原味地传达出他的一切想法与话语，也许这篇专访也要变成「未满19岁不准阅读」。

现在还赶得及的。

要是各位预计他的访问内容将对青少年有害或是会感到不快，请停止阅读以下文章。

不然的话，希望大家能藉此机会除下对他的有色眼镜。

以下是9月19日在首尔合井洞YG大楼进行的G-Dragon专访。

- 你在歌词中流露著非凡的自信▲虽然现在还很年轻，但年复一年，我在生活和思考各方面都一直在转变。

这是变得成熟的过程吧？我也很多弱点的，但即使是我看在舞台上的自己也很帅。

现在学懂了不事事计较，反而更轻松了。

- 这次不少歌曲都是新尝试▲进行个人活动而非BIGBANG团体活动时，我从小就认为可以多尝试多点新音乐。

虽然也会担心出现风险，也许是因为我的形象吧，大家好像都不计较音乐是不是接近大众口味，就当轻松小品一样听听。

- 你认为自己的形象如何？▲现在连我看著在台上的自己也觉得好像一个疯子。

但我为此感到很高兴，实在不知道怎样清楚表达这种感觉，但我体内就像有某种力量在涌上来。

-当理想和现实出现冲突时，你试过妥协吗?▲也不是没试过。

CODEV10.2说明书3

Application Programming InterfaceReference GuideVersion 10.2December 2009Pasadena, California 91107Phone: (626) 795-9101Fax: (626) 795-0184E-mail: service@The information in this document is subject to change without notice and should not be construed as a commitment by Optical Research Associates (ORA®). ORA assumes no liability for any errors that may Arrayappear in this document.The software described in this document is furnished under license and may be used or copied only in accordance with the terms of such license. The CODE V output shown (plotted and printed) may vary in different versions.Copyright © 2009 by Optical Research Associates. All rights reserved.Proprietary Software NotificationCODE V® is the proprietary and confidential property of ORA and/or its suppliers. It is licensed for use on the designated equipment on which it was originally installed and cannot be modified, duplicated, or copied in any form without prior written consent of ORA. If supplied under a U.S. Government contract the following also applies:Restricted Rights LegendUse, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or insubparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FARS 52.227-19.ORA, CODE V, and LightTools are registered trademarks of Optical Research Associates. Other trademarksor marks are the property of their respective companies.CODE V API Reference Guide Contents • iiiContentsChapter 1OverviewWhat is the CODE V API? (1)Requirements (1)A Note about the DEFAULTS.SEQ File (2)Getting Started (2)DisplayAlerts Property (4)Speeding Up COM Client Execution...............................................................................................4Chapter 2CODE V Interface FunctionsGeneral Utility Functions (6)Start/StopCodeV (6)Get/SetCommandTimeout (7)Get/SetMaxTextBufferSize (8)Get/SetStartingDirectory (9)GetCodeVVersion (10)Asynchronous Usage Functions (11)AsyncCommand (11)IsExecutingCommand (12)Wait (13)GetCommandOutput (14)StopCommand (15)Synchronous Usage Functions (16)Command (16)EvaluateExpression (17)CODE V State Information (18)GetCurrentOption (18)GetCurrentSubOption (19)GetZoomCount (20)GetSurfaceCount (21)GetFieldCount (22)GetWavelengthCount (23)GetDimension (24)GetStopSurface (25)GetMaxAperture (26)Math and Optical MACRO Functions (27)BESTSPH (27)EVALZERN (28)FITERROR (29)GAUSSBEAM (30)GAUSSWTS (32)INDEX (33)MTF_1FLD (34)NORMRADIUS (35)POLGRID (36)RAYPOL (39)RAYRSI (42)RAYSIN..................................................................................................................................43iv • Contents CODE V API Reference GuideRAYTRA................................................................................................................................44RMSWE..................................................................................................................................45RMS_1FLD.............................................................................................................................48SAGF (50)SASF (51)SURFSAGD (52)SVD (53)TRA_1FLD (54)TRANSFORM (56)ZERNIKE (57)ZERNIKEGQ (59)Zernike Fitting Functions (61)ZFRCOEF (62)Buffer Functions (63)Sample Code: Outputting buffer data from CODE V (63)BufferToArray (64)ArrayToBuffer (65)Chapter 3CODE V API by ExampleWriting PSF Data to an Excel Spreadsheet (67)Results (69)Creating a Surface Listing (70)MATLAB Sample File...................................................................................................................72Appendix A CVCommand ErrorsE_INVALIDARG (73)DISP_E_BADINDEX (73)E_UNEXPECTED (73)FACILITY_ITF..............................................................................................................................73Chapter 1OverviewWhat is the CODE V API?The CODE V API is an application programming interface designed to allow access from otherprograms to CODE V commands. The CODE V API uses the Microsoft Windows standardComponent Object Model (COM) interface1. This enables you to execute CODE V commandsusing applications such as Microsoft Visual Basic (VB), Microsoft Office Applications, C++,MATLAB, or any other application that supports Windows COM architecture. The CODE V API is particularly useful for automating tasks or retrieving data used in calculations in other programs.Both Visual Basic and Excel provide an integrated development environment in which you candevelop CODE V command functions.2 This type of environment provides context-sensitiveediting and debugging, Windows standard forms, object oriented programming capabilities(Classes), standard functions in Visual Basic/Excel (or the client program), external object libraries known as dynamic link libraries (DLLs), as well as other conveniences that can enhance thefunction writing process.The CODE V API has no graphical user interface, and therefore no graphics support; any plotscreated with a CODE V API function must be output to a file or they are lost. Plot files can beviewed either in CODE V, or in the standalone CODE V Viewer program (CVPlotView). RequirementsIn order to use the CODE V API to write and run commands, you must have installed:•CODE V 9.30 or laterDuring installation, CODE V is configured to support API command execution. This processregisters CODE V as a COM server on your system (cvcommand).•Any Visual Basic compliant application (such as Microsoft Excel, Word, PowerPoint, Visual Basic, or MATLAB) or any other Windows program that supports Microsoft COMarchitecture1. The COM enables Windows Programs to communicate with each other using the Client/Serverconcept. For example, the program that initiates the communication process is referred to asthe client, and the program that responds to client’s requests is referred to as the server. Currently,CODE V can only act as a server, meaning that it can only respond to client programs.2. This document concentrates on Visual Basic as the client for writing functions. To use other pro-grams, please refer to their documentation (under “Automation” or “COM” support).CODE V API Reference Guide Overview • 12 • Overview CODE V API Reference GuideA Note about the DEFAULTS.SEQ FileWhen you use the CODE V API, note that your DEFAULTS.SEQ file is not automatically loaded when CODE V is run. You must include the following command in your function to load this file:mand("in defaults.seq")Getting StartedThis example describes how to write a very simple command function using the Visual Basic Editor provided with Microsoft Excel.1.Start Microsoft Excel.2.Select Tools > Macro > Visual Basic Editor .The Microsoft VisualBasic window is displayed.3.Add the CODE V Command Type Library as a reference by doing the following:a.Select Tools > References . . ..b.In the References - VBAProject window, select the Optical Research AssociatesCVCommand Type Library and click OK .If you are running Excel 97, the CVCommand Type Library may not be listed in theAvailable References. If it is not, select Browse and navigate to the CODE V installation directory. Click on cvcommand.tlb and click Open to add the CVCommand Type Library to the Available References.3.Back in the Microsoft Visual Basic window, select Tools > Macros .4.In the Macros window, key in a name and click Create .5.In the Book1 - Module1(Code) window, you can begin writing your macro.a.Declare the session variable:Dim Session As CVCommand b.Request an instance of the CVCommand interface using the Set statement:Set session = CreateObject("mand.930")This instance should be requested by object name, which in this case is version 9.30 ofCODE V . A specific version number should be requested because the interfaces maychange with later versions of CODE V.CODE V API Reference Guide Overview • 3c.Once an instance is created, the CODE V utility functions can be called on to set up theenvironment parameters, such as buffer size and starting directory. For example:session.SetStartingDirectory("c:\CVUSER")e the StartCodeV function to start up CODE V:session.StartCodeVplete the macro as desired and save your project.Following is a sample macro that starts CODE V , opens the sample lens file dbgauss.len, and optimizes the lens:Sub RunCodeV()Dim Session As CVCommand'Create an instance of CODE V and set the starting directory to c:\CVUSER Set session = CreateObject("mand.xxx")'where xxx is the CODE V version; for example, xxx=101 for version 10.1 session.SetStartingDirectory("c:\CVUSER")session.StartCodeVmand("in defaults.seq")'load a lens (dbgauss) and run AUTO to optimize itresult = mand("res cv_lens:dbgauss")result = mand("aut; go")MsgBox (result)'evaluate the Effective Focal Lengthresult = session.EvaluateExpression ("(efl)")'Shut down the instance of CODE Vsession.StopCodeVSet session = NothingEnd Sub6.From the Visual Basic window, click Run > Run Sub/User Form , or click the Run icon on thetoolbar.The macro will run CODE V and execute the specified CODE V command functions.For details about the available CODE V commands available for use with the CODE V API, go to Chapter 2, “CODE V Interface Functions” on page5.DisplayAlerts PropertyIf your macro starts a CODE V process that takes time, and waits for a response, then VB or VBA Array will try to issue a warning message indicating that the server is not responding and may not run the remaining portion of the macro. To suppress this message, you can use the following code:in VBA:Application.DisplayAlerts = Falsedisables the display of alert boxes; however, this setting should be used selectively and changedback to True when not needed.in VB, you can set:App.OleRequestPendingTimeout = NApp.OleRequestBusyTimeout = Nwhere N is the number of milliseconds. N should be greater than the time it takes to run the process. Speeding Up COM Client ExecutionThe REC command allows you to disable recording of data in the CODE V recovery file, whichcan help speed up execution of COM clients. See “Defining Configuration - I/O” on page24-19 ofthe CODE V Reference Manual for details about REC. Note that, by default, CODE V alwaysrecords data in the recovery file, which is recommended for general CODE V usage.4 • Overview CODE V API Reference GuideCODE V API Reference Guide CODE V Interface Functions • 5Chapter 2CODE V Interface FunctionsThis section contains details for each CODE V interface function. The CODE V interface functions are grouped in the following categories, based on what they do.•General Utility Functions.................................................................................... 6•Asynchronous Usage Functions......................................................................... 11•Synchronous Usage Functions........................................................................... 16•CODE V State Information ............................................................................... 18•Math and Optical MACRO Functions............................................................... 27•Buffer Functions................................................................................................63General Utility FunctionsStart/StopCodeVThese functions start or stop the CODE V session being run by CVCommand. Start must be called before any function other than Set/GetCommandTimeout, Set/GetMaxTextBufferSize,GetCodeVVersion, or Set/GetStartingDirectory is called. StopCodeV must be called when you are done running the session of CODE V.Visual Basic SyntaxStartCodeV()StopCodeV()6 • CODE V Interface Functions CODE V API Reference GuideGet/SetCommandTimeoutThese functions are used to get or set the timeout for synchronous commands. They have no effect on asynchronous commands.Visual Basic SyntaxSetCommandTimeout(nTimeout As Integer)GetCommandTimeout() As IntegerParameterReturn ValueFor GetCommandTimeout, the current timeout time in seconds.nTimeoutCurrent timeout time in secondsGet/SetMaxTextBufferSizeThese functions are used to get or set the maximum buffer size for text returned by the Command and GetCommandOutput functions.Visual Basic SyntaxSetMaxTextBufferSize(lSize As Long)GetMaxTextBufferSize() As LongParameterReturn ValueFor GetMaxTextBufferSize, a pointer to a long integer that contains the current maximum buffer size.lSize Long integer containing the desired maximum buffer size in characters.Default is 256000.Get/SetStartingDirectoryGet or set the working directory for CODE V . SetStartingDirectory must be called before StartCodeV to set the directory of execution.Visual Basic SyntaxGetStartingDirectory() As StringSetStartingDirectory(bstrStartingDirectory As String)ParameterReturn ValuePointer to a string defining the current starting directory.bstrStartingDirectoryString defining the desired starting directory.GetCodeVVersionVisual Basic SyntaxGetCodeVVersion() As StringParameterNone.Return ValueVersion of CODE V that is running.Asynchronous Usage FunctionsAsyncCommandStart an asynchronous command. Only one AsyncCommand call can be run at a time, but multiple AsyncCommand calls can be made during a CVCommand session. This function call fails if CODE V is already running a command. Calling this function clears the results of the previous asynchronous function call.Visual Basic SyntaxAsyncCommand(bstrCommandLine As String)ParameterbstrCommandLineCommand to be executed.IsExecutingCommandVisual Basic SyntaxIsExecutingCommand() As LongParameterNone.Return ValueBoolean that indicates whether or not an asynchronous command is currently executing.WaitWait for an asynchronous command to complete.Visual Basic SyntaxWait(nWaitTime As Integer) As CVWaitStatusParameterReturn ValueEnumeration for wait status, either Completed or TimeOut:Completed Command completed 1TimeOut Wait timed out with the command still runningnWaitTimeTime to wait in seconds.GetCommandOutputEvaluateExpression, or math and optical functions) between calls to AsyncCommand andGetCommandOutput. This will preserve the buffer between those two calls.Visual Basic SyntaxGetCommandOutput() As StringParameterNone.Return ValueString containing the output. Its maximum length is the maximum buffer size.StopCommandThis function aborts the currently running CODE V calculation.Visual Basic SyntaxStopCommand()Synchronous Usage FunctionsCommandThis function sends a command to the CODE V session being run by CVCommand and returns its output. Calling this function clears the results of the previous asynchronous function call.Visual Basic SyntaxCommand(bstrCommandLine As String) As StringParameterReturn ValueThe command output. Its size is limited by the maximum buffer size set withSetMaxTextBufferSize.bstrCommandLineCODE V command.EvaluateExpressionThis function evaluates an expression and returns its value. It is equivalent to the EV A command in CODE V .Visual Basic SyntaxEvaluateExpression(bstrExpression As String) As StringParameterReturn ValuePointer to a string into which CVCommand will put the results of the evaluation. Note that because this is a string, the value is only as precise as the output into the string; it is not a true floating point value.bstrExpressionString containing the expression to evaluate.CODE V State Informationasynchronous command.GetCurrentOptionReturns the name of the current option.Visual Basic SyntaxGetCurrentOption() As StringParameterNone.Return ValueThe option short name (e.g., AUT for Automatic Design). Returns "CHA" if CODE V is notcurrently in an option.GetCurrentSubOptionVisual Basic SyntaxGetCurrentSubOption() As StringParameterNone.Return ValueThe option name. Returns an empty string if CODE V is not currently in a sub-option.Visual Basic SyntaxGetZoomCount() As Integer ParameterNone.Return ValueThe current number of zoom positions in the lens.Visual Basic SyntaxGetSurfaceCount() As Integer ParameterNone.Return ValueThe current number of surfaces.GetFieldCountVisual Basic SyntaxGetFieldCount() As Integer ParameterNone.Return ValueThe current number of fields.GetWavelengthCountVisual Basic SyntaxGetWavelengthCount() As Integer ParameterNone.Return ValueThe current number of wavelengths.GetDimensionReturns a value representing the type of dimensions in the system.Visual Basic SyntaxGetDimension() As IntegerParameterNone.Return ValuesThe value representing the type of dimensions in the system:0Inches1Centimeters2MillimetersVisual Basic SyntaxGetStopSurface() As Integer ParameterNone.Return ValueThe surface number of the current stop surface.Returns the maximum aperture size for the specified surface and zoom.Visual Basic SyntaxGetMaxAperture(nSurface As Integer, nZoom As Integer) As DoubleParametersReturn ValueMaximum aperture size. This uses the “MAP” database item.nSurfaceNumber of the surface for which the maximum aperture will be oomZoom position at which the maximum aperture will be determined.Math and Optical MACRO FunctionsThe following functions are equivalent to calling various CODE V macro functions. For more details about the CODE V macro functions referenced, see “Language Reference” on page 25A-1 of the CODE V Reference Manual .BESTSPHThis is equivalent to calling the BESTSPH macro function in CODE V .Visual Basic SyntaxBESTSPH(nSurface As Integer, nZoomPos As Integer,dblMinHeight As Double, dblMaxHeight As Double) As DoubleParametersReturn ValueThe return value of the BESTSPH macro function. It is the curvature of the best fitting sphere.nSurface Desired surface.nZoomPos Desired zoom position.dblMinHeight Minimum Y coordinate.dblMaxHeightMaximum Y coordinate.EVALZERNThis is equivalent to calling the EV ALZERN macro function in CODE V . The EV ALZERN macron function evaluates a Zernike polynomial generated with the ZERNIKE, ZERNIKEGQ, orZFRCOEF macro function and computes the value of the polynomial at a point X,Y , where X and Y are normalized to the unit circle.Visual Basic SyntaxEVALZERN(nWavelengthNum As Integer, nFieldNum As Integer, nZoomPos As Integer, dblX As Double, dblY As Double, nPolType As Integer, eOutputType As CVZernOutputTypeEnum, eZernType As CVZernTypeEnum) As DoubleParametersReturn ValueThe value of the Zernike polynomial at the specified coordinate. If the polynomial has not been defined with the ZERNIKE, ZERNIKEGQ, or ZFRCOEF function, EV ALZERN returns a value of -1e10.nWavelengthNum Number of the wavelength defined in ZERNIKE, ZERNIKEGQ, or ZFRCOEF.nFieldNum Number of the field point defined in ZERNIKE, ZERNIKEGQ, or ZFRCOEF.nZoomPos Zoom position defined in ZERNIKE, ZERNIKEGQ, or ZFRCOEF.dblX X coordinate to be evaluated.dblY Y coordinate to be evaluated.nPolTypeNumber specifying whether polarization ray tracing is enabled for this computation; matches the number defined in ZERNIKE or ZERNIKEGQ. If you used ZFRCOEF, this must be 0.eOutputTypeEnumeration of the output type ('intensity' or 'phase'), specifying intensity or phase. Matches the type used in ZERNIKE or ZERNI-KEGQ. If you used ZFRCOEF, the output must be 'phase.'eZernTypeType of the Zernike polynomial. Matches the expression defined inZERNIKE or ZERNIKEGQ. If you used ZFRCOEF, it must be 'zfr.'FITERRORThis is equivalent to calling the FITERROR macro function in CODE V .Visual Basic SyntaxFITERROR(nWavelengthNum As Integer, nFieldNum As Integer, nZoomPos As Integer, nPolType As Integer, eOutputType As CVZernOutputTypeEnum, eZernType As CVZernTypeEnum) As DoubleParametersReturn ValueThe RMS fit error of the Zernike polynomial. If the polynomial has not been defined with the ZERNIKE or ZFRCOEF function, FITERROR returns a value of -1. If used with the ZERNIKEGQ macro function, returns a value of 0.nWavelengthNum Number of the wavelength defined in ZERNIKE or ZFRCOEF.nFieldNum Number of the field point defined in ZERNIKE or oomPos Zoom position defined in ZERNIKE or ZFRCOEF.nPolTypeNumber specifying whether polarization ray tracing is enabled for this computation; matches the number defined in ZERNIKE. If you used ZFRCOEF, this must be 0.eOutputTypeEnumeration of the output type ('intensity' or 'phase'), specifying intensity or phase. Matches the type used in ZERNIKE. If you used ZFRCOEF, the output must be 'phase.'eZernTypeType of the Zernike polynomial. Matches the expression defined inZERNIKE. If you used ZFRCOEF, it must be 'zfr.'GAUSSBEAMThis is equivalent to calling the GAUSSBEAM macro function in CODE V .Visual Basic SyntaxGAUSSBEAM(nSurface As Integer, nZoomPos As Integer, nFieldNum As Integer, nWavelengthNum As Integer, psaInput() As Double, eOutputType As CVGaussbeamOutputTypeEnum) As DoubleParametersnSurfaceThe surface number to use. For non-sequential systems, if you enter a negative value, that value refers to the hit number rather than the sur-face number. This gives you direct access to the information by hit number.nZoomPos Zoom position to use.nFieldNumNumber of field positions to use.nWavelengthNum Number of the wavelength to use (not the value of the wavelength).psaInputA five-element input array containing the following parameters (in this order): initial beam-width radius (at the object plane) at the 1/ e 2 inten-sity point in the X meridian (WRX), initial beam-width radius (at the object plane) at the 1/ e 2 intensity point in the Y meridian (WRY), radius of curvature of input wavefront (at object plane) in X meridian (RCX), radius of curvature of input wavefront (at object plane) in Y meridian (RCY), orientation (in degrees) of input beam definition about the optical (z) axis (AZI).eOutputTypeEnumeration specifying the output value of the function:0PROP Propagation distance to the next surface 1BSDX X semi-diameter of the beam 2BSDY Y semi-diameter of the beam 3BANG Beam angle (in degrees)4WCUX X Curvature of the Wavefront 5WCUY Y Curvature of the Wavefront 6WSDX X semi-diameter of the waist 7WSDY Y semi-diameter of the waist 8WDSX X waist distance from the surface 9WDSY Y waist distance from the surface 10SURX X Coordinate of the beam on the surface 11SURY Y Coordinate of the beam on the surface 12SURZZ Coordinate of the beam on the surfaceReturn ValueFor non-sequential systems, the macro function returns results for the last time the specified surface was hit. If that surface was not hit, the function returns 0.13RDCL L Direction cosine (geo) of center of beam prior to surface14RDCM M Direction cosine (geo) of center of beam prior to surface15RDCN N Direction cosine (geo) of center of beam prior to surface16AINC Angle of incidence (in degrees) of center of beam at surface17SURNFor NS systems. Return the surface number for the hit number specified with the surface numparameterGAUSSWTSThis function is equivalent to calling the GAUSSWTS macro function in CODE V .Visual Basic SyntaxGAUSSWTS(nNumInputPts As Integer, psaInputCoords() As Double, psalInputWeights() As Double, nNumQuadPts As Integer, psaCoords() As Double, psaWeights() As Double) As DoubleParametersReturn ValueThe return value of the GAUSSWTS macro function. It is 0 if there are no errors in the computation, and -1 if any errors are encountered.nNumInputPts Number of input points at which weights are supplied.psaInputCoordsInput array of coordinates at which weights are supplied. It must be nNumInputPts long. The input coordinates do not need to be equally spaced.psalInputWeights An input array, dimensioned at nNumInputPts, of the weighting function at the points specified in psaInputCoords.nNumQuadPts Number of Gaussian quadrature points and weights desired.psaCoords An output array, dimensioned at nNumQuadPts, of the coordinates to be used for the numerical integration.psaWeightsAn output array, dimensioned at nNumQuadPts. It will receive theweights to be used for the numerical integration.INDEXThis is equivalent to calling the INDEX macro function in CODE V .Visual Basic SyntaxINDEX(nSurface As Integer, nZoomPos As Integer,nWavelengthNum As Integer, nGlassNum As Integer, dblX As Double, dblY As Double, dblZ As Double) As DoubleParametersReturn ValueThe refractive index at the specified point. Note that it can be positive or negative, depending on the direction the light is traveling. If the first four parameters are outside their allowed range or if the index cannot be computed for any reason, the return value is set to 0.0.nSurface Surface number of the GRIN oomPosZoom position.nWavelengthNum Number of the wavelength to be used (not the wavelength value).nGlassNum Glass number (for NSS surfaces). Value must be either 1 or 2. For sequential surfaces, use 1.dblX, dblY , dblZCoordinates relative to the surface origin where the index is to becomputed.MTF_1FLDMTF_1FLD computes the MTF of the lens system including or excluding diffraction effects,assuming either a sine wave or a square wave object, similar to the MTF option. It is equivalent to calling the MTF_1FLD macro function in CODE V .Visual Basic SytaxMTF_1FLD(nZoomPos As Integer, nFieldNum As Integer, Frequency As Double, Azimuth As Double, NRD As Integer, MTFValues() As Double, MTFtype As CVMTFTypeEnum, MTFWave As CVMTFWaveEnum) As DoubleParametersReturn ValueThe return value of the function is the modulation. If there is an error in the computation or inputs, the return value is -1. Since a negative modulation is not valid, any negative return value indicates that the calculation failed.nZoomPos Zoom position to use. Range: 1 to (NUM Z).nFieldNum Number of field point to use. Range: 1 to (NUM F).FrequencySpatial frequency at the image surface. Units are cycles/mm for focal systems, and cycles per angular measure for afocal (AFC) systems, where the angular measure is defined by the angular units specification (ADM).Azimuth Orientation of the spatial frequency at the image, in degrees.NRD Number of grid rays across the diameter of the pupil. If nrd is set to zero, the calculation is performed using a default value of 60.MTFValuesThe output array name must be declared before the macro is called, and is a one-dimensional output array that will contain the following six elements:1.Modulation2.Phase (degrees)3.Analytic diffraction limit value4.Actual diffraction limit value5.Illumination for unit brightness6.Number of rays traced (in convolved pupil for diffraction MTF)These data values correspond to the equivalent values output by the MTF option.MTFtype String expression specifying diffraction MTF ('DIF') or geometrical MTF ('GEO').MTFWaveString expression specifying sine wave response ('SIW') or square waveresponse ('SQW').。

产品需求文档模板【范本模板】

<产品名称〉产品需求说明书[注：产品需求说明书的定义：此文档的目的是收集、分析和定义〈〈xxx产品名〉〉的需要和特性。

它包括相关方和目标用户需要的功能和这些需要存在的原因，以及详细地说明所确定的产品的关键外部业务流程、接口和非功能性特性的需求、设计约束。

此文档用来让读者了解产品的外部黑盒概念，并指导《架构设计说明书》和《软件需求说明书》。

一个产品（对外对内具有统一定义的）只有一份《产品需求说明书》，对于分解的对内项目部分可以以《xxxx产品需求说明书—yyyy分册》来撰写。

以下提供的模板用于需求管理流程。

其中包括用方括号括起来并以蓝色斜体（样式=InfoBlue)显示的文本，它们用于向作者提供指导，在发布此文档之前应该将其删除.按此样式输入的段落将被自动设置为普通样式（样式=正文）。

1 优先级 (16)1.2 特性描述 (16)1.3 社区首页 (16)1.3.1 读书会列表 (16)1.3。

2 热评书潮 (17)1.3.3 视频节目 (17)1。

3.4 社区名人 (18)1。

3.5 读书会推荐 (18)1.3.6 热门原创 (19)1。

3.7 读书快报（新闻） (20)1.3。

8 合作伙伴列表（页底） (20)2、板块一——藏书阁 (21)2。

1 藏书阁首页 (21)2。

1。

1 页面描述 (21)2.1。

2 搜索 (21)2。

1.3 书籍推荐 (21)2。

1.4 书评推荐 (22)2.1.5 名家读书会专题 (23)2。

1。

6 分类推荐 (24)2。

1.7 一周好书 (25)2。

1。

8 排行榜 (25)2。

1.9 读书会推荐 (27)2。

3GPP协议-36521-1-e40_s00-s05

3GPP TS 36.521-1 V14.4.0 (2017-09)Technical Specification3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA);User Equipment (UE) conformance specification;Radio transmission and reception;Part 1: Conformance Testing(Release 14)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.KeywordsUMTS LTE3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI registered for the benefit of its Members a nd of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationContentsForeword (92)Introduction (92)1Scope (93)2References (94)3Definitions, symbols and abbreviations (96)3.1Definitions (96)3.2Symbols (98)3.3Abbreviations (100)4General (103)4.1Categorization of test requirements in CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UEcategory M1, UE category 1bis, UE category NB1 and V2X Communication (104)4.2RF requirements in later releases (105)5Frequency bands and channel arrangement (106)5.1General (106)5.2Operating bands (106)5.2A Operating bands for CA (108)5.2B Operating bands for UL-MIMO (116)5.2C Operating bands for Dual Connectivity (116)5.2D Operating bands for ProSe (117)5.2E Operating bands for UE category 0 and UE category M1 (118)5.2F Operating bands for UE category NB1 (118)5.2G Operating bands for V2X Communication (118)5.3TX–RX frequency separation (119)5.3A TX–RX frequency separation for CA (120)5.4Channel arrangement (120)5.4.1Channel spacing (120)5.4.1A Channel spacing for CA (121)5.4.1F Channel spacing for UE category NB1 (121)5.4.2Channel bandwidth (121)5.4.2.1Channel bandwidths per operating band (122)5.4.2A Channel bandwidth for CA (124)5.4.2A.1Channel bandwidths per operating band for CA (126)5.4.2B Channel bandwidth for UL-MIMO (171)5.4.2B.1Channel bandwidths per operating band for UL- MIMO (171)5.4.2C Channel bandwidth for Dual Connectivity (171)5.4.2D Channel bandwidth for ProSe (171)5.4.2D.1Channel bandwidths per operating band for ProSe (171)5.4.2F Channel bandwidth for category NB1 (172)5.4.2G Channel bandwidth for V2X Communication (173)5.4.2G.1Channel bandwidths per operating band for V2X Communication (173)5.4.3Channel raster (174)5.4.3A Channel raster for CA (175)5.4.3F Channel raster for UE category NB1 (175)5.4.4Carrier frequency and EARFCN (175)5.4.4F Carrier frequency and EARFCN for category NB1 (177)6Transmitter Characteristics (179)6.1General (179)6.2Transmit power (180)6.2.1Void (180)6.2.2UE Maximum Output Power (180)6.2.2.1Test purpose (180)6.2.2.4Test description (182)6.2.2.4.1Initial condition (182)6.2.2.4.2Test procedure (183)6.2.2.4.3Message contents (183)6.2.2.5Test requirements (183)6.2.2_1Maximum Output Power for HPUE (185)6.2.2_1.1Test purpose (185)6.2.2_1.2Test applicability (185)6.2.2_1.3Minimum conformance requirements (185)6.2.2_1.4Test description (185)6.2.2_1.5Test requirements (186)6.2.2A UE Maximum Output Power for CA (187)6.2.2A.0Minimum conformance requirements (187)6.2.2A.1UE Maximum Output Power for CA (intra-band contiguous DL CA and UL CA) (189)6.2.2A.1.1Test purpose (189)6.2.2A.1.2Test applicability (189)6.2.2A.1.3Minimum conformance requirements (189)6.2.2A.1.4Test description (189)6.2.2A.1.5Test Requirements (191)6.2.2A.2UE Maximum Output Power for CA (inter-band DL CA and UL CA) (192)6.2.2A.2.1Test purpose (192)6.2.2A.2.2Test applicability (192)6.2.2A.2.3Minimum conformance requirements (192)6.2.2A.2.4Test description (192)6.2.2A.2.5Test Requirements (194)6.2.2A.3UE Maximum Output Power for CA (intra-band non-contiguous DL CA and UL CA) (196)6.2.2A.4.1UE Maximum Output Power for CA (intra-band contiguous 3DL CA and 3UL CA) (196)6.2.2A.4.1.1Test purpose (196)6.2.2A.4.1.2Test applicability (196)6.2.2A.4.1.3Minimum conformance requirements (196)6.2.2A.4.1.4Test description (196)6.2.2A.4.1.5Test Requirements (198)6.2.2A.4.2UE Maximum Output Power for CA (inter-band 3DL CA and 3UL CA) (198)6.2.2A.4.2.1Test purpose (199)6.2.2A.4.2.2Test applicability (199)6.2.2A.4.2.3Minimum conformance requirements (199)6.2.2A.4.2.4Test description (199)6.2.2A.4.2.5Test Requirements (201)6.2.2B UE Maximum Output Power for UL-MIMO (201)6.2.2B.1Test purpose (201)6.2.2B.2Test applicability (202)6.2.2B.3Minimum conformance requirements (202)6.2.2B.4Test description (204)6.2.2B.4.1Initial condition (204)6.2.2B.4.2Test procedure (205)6.2.2B.4.3Message contents (205)6.2.2B.5Test requirements (205)6.2.2B_1HPUE Maximum Output Power for UL-MIMO (207)6.2.2B_1.1Test purpose (207)6.2.2B_1.2Test applicability (207)6.2.2B_1.3Minimum conformance requirements (207)6.2.2B_1.4Test description (207)6.2.2B_1.5Test requirements (208)6.2.2C 2096.2.2D UE Maximum Output Power for ProSe (209)6.2.2D.0Minimum conformance requirements (209)6.2.2D.1UE Maximum Output Power for ProSe Discovery (209)6.2.2D.1.1Test purpose (209)6.2.2D.1.2Test applicability (209)6.2.2D.1.3Minimum Conformance requirements (209)6.2.2D.2UE Maximum Output Power for ProSe Direct Communication (211)6.2.2D.2.1Test purpose (211)6.2.2D.2.2Test applicability (211)6.2.2D.2.3Minimum conformance requirements (211)6.2.2D.2.4Test description (211)6.2.2E UE Maximum Output Power for UE category 0 (212)6.2.2E.1Test purpose (212)6.2.2E.2Test applicability (212)6.2.2E.3Minimum conformance requirements (212)6.2.2E.4Test description (212)6.2.2E.4.3Message contents (213)6.2.2E.5Test requirements (213)6.2.2EA UE Maximum Output Power for UE category M1 (215)6.2.2EA.1Test purpose (215)6.2.2EA.2Test applicability (215)6.2.2EA.3Minimum conformance requirements (215)6.2.2EA.4Test description (216)6.2.2EA.4.3Message contents (217)6.2.2EA.5Test requirements (217)6.2.2F UE Maximum Output Power for category NB1 (218)6.2.2F.1Test purpose (218)6.2.2F.2Test applicability (218)6.2.2F.3Minimum conformance requirements (218)6.2.2F.4Test description (219)6.2.2F.4.1Initial condition (219)6.2.2F.4.2Test procedure (220)6.2.2F.4.3Message contents (220)6.2.2F.5Test requirements (220)6.2.2G UE Maximum Output Power for V2X Communication (221)6.2.2G.1UE Maximum Output Power for V2X Communication / Non-concurrent with E-UTRA uplinktransmission (221)6.2.2G.1.1Test purpose (221)6.2.2G.1.2Test applicability (221)6.2.2G.1.3Minimum conformance requirements (221)6.2.2G.1.4Test description (222)6.2.2G.1.4.1Initial conditions (222)6.2.2G.1.4.2Test procedure (222)6.2.2G.1.4.3Message contents (222)6.2.2G.1.5Test requirements (223)6.2.2G.2UE Maximum Output Power for V2X Communication / Simultaneous E-UTRA V2X sidelinkand E-UTRA uplink transmission (223)6.2.2G.2.1Test purpose (223)6.2.2G.2.2Test applicability (223)6.2.2G.2.3Minimum conformance requirements (223)6.2.2G.2.4Test description (224)6.2.2G.2.4.1Initial conditions (224)6.2.2G.2.4.2Test procedure (225)6.2.2G.2.4.3Message contents (226)6.2.2G.2.5Test requirements (226)6.2.3Maximum Power Reduction (MPR) (226)6.2.3.1Test purpose (226)6.2.3.2Test applicability (226)6.2.3.3Minimum conformance requirements (227)6.2.3.4Test description (227)6.2.3.4.1Initial condition (227)6.2.3.4.2Test procedure (228)6.2.3.4.3Message contents (228)6.2.3.5Test requirements (229)6.2.3_1Maximum Power Reduction (MPR) for HPUE (231)6.2.3_1.1Test purpose (231)6.2.3_1.4Test description (232)6.2.3_1.5Test requirements (232)6.2.3_2Maximum Power Reduction (MPR) for Multi-Cluster PUSCH (232)6.2.3_2.1Test purpose (232)6.2.3_2.2Test applicability (232)6.2.3_2.3Minimum conformance requirements (233)6.2.3_2.4Test description (233)6.2.3_2.4.1Initial condition (233)6.2.3_2.4.2Test procedure (234)6.2.3_2.4.3Message contents (234)6.2.3_2.5Test requirements (234)6.2.3_3Maximum Power Reduction (MPR) for UL 64QAM (235)6.2.3_3.1Test purpose (236)6.2.3_3.2Test applicability (236)6.2.3_3.3Minimum conformance requirements (236)6.2.3_3.4Test description (236)6.2.3_3.4.1Initial condition (236)6.2.3_3.4.2Test procedure (237)6.2.3_3.4.3Message contents (237)6.2.3_3.5Test requirements (238)6.2.3_4Maximum Power Reduction (MPR) for Multi-Cluster PUSCH with UL 64QAM (240)6.2.3_4.1Test purpose (240)6.2.3_4.2Test applicability (240)6.2.3_4.3Minimum conformance requirements (240)6.2.3_4.4Test description (241)6.2.3_4.4.1Initial condition (241)6.2.3_4.4.2Test procedure (242)6.2.3_4.4.3Message contents (242)6.2.3_4.5Test requirements (242)6.2.3A Maximum Power Reduction (MPR) for CA (243)6.2.3A.1Maximum Power Reduction (MPR) for CA (intra-band contiguous DL CA and UL CA) (243)6.2.3A.1.1Test purpose (243)6.2.3A.1.2Test applicability (243)6.2.3A.1.3Minimum conformance requirements (244)6.2.3A.1.4Test description (245)6.2.3A.1.5Test Requirements (248)6.2.3A.1_1Maximum Power Reduction (MPR) for CA (intra-band contiguous DL CA and UL CA) for UL64QAM (250)6.2.3A.1_1.1Test purpose (251)6.2.3A.1_1.2Test applicability (251)6.2.3A.1_1.3Minimum conformance requirements (251)6.2.3A.1_1.4Test description (252)6.2.3A.1_1.5Test requirement (254)6.2.3A.2Maximum Power Reduction (MPR) for CA (inter-band DL CA and UL CA) (255)6.2.3A.2.1Test purpose (255)6.2.3A.2.2Test applicability (255)6.2.3A.2.3Minimum conformance requirements (255)6.2.3A.2.4Test description (256)6.2.3A.2.5Test Requirements (260)6.2.3A.2_1Maximum Power Reduction (MPR) for CA (inter-band DL CA and UL CA) for UL 64QAM (263)6.2.3A.2_1.1Test purpose (263)6.2.3A.2_1.2Test applicability (263)6.2.3A.2_1.3Minimum conformance requirements (263)6.2.3A.2_1.4Test description (264)6.2.3A.2_1.5Test Requirements (266)6.2.3A.3Maximum Power Reduction (MPR) for CA (intra-band non-contiguous DL CA and UL CA) (267)6.2.3A.3.1Test purpose (267)6.2.3A.3.2Test applicability (267)6.2.3A.3.3Minimum conformance requirements (268)6.2.3A.3.4Test description (268)6.2.3A.3_1Maximum Power Reduction (MPR) for CA (intra-band non-contiguous DL CA and UL CA) forUL 64QAM (270)6.2.3A.3_1.1Test purpose (270)6.2.3A.3_1.2Test applicability (270)6.2.3A.3_1.3Minimum conformance requirements (270)6.2.3A.3_1.4Test description (271)6.2.3A.3_1.5Test Requirements (272)6.2.3B Maximum Power Reduction (MPR) for UL-MIMO (272)6.2.3B.1Test purpose (272)6.2.3B.2Test applicability (272)6.2.3B.3Minimum conformance requirements (273)6.2.3B.4Test description (273)6.2.3B.4.1Initial condition (273)6.2.3B.4.2Test procedure (274)6.2.3B.4.3Message contents (275)6.2.3B.5Test requirements (275)6.2.3D UE Maximum Output Power for ProSe (277)6.2.3D.0Minimum conformance requirements (277)6.2.3D.1Maximum Power Reduction (MPR) for ProSe Discovery (278)6.2.3D.1.1Test purpose (278)6.2.3D.1.2Test applicability (278)6.2.3D.1.3Minimum conformance requirements (278)6.2.3D.1.4Test description (278)6.2.3D.1.4.1Initial condition (278)6.2.3D.1.4.2Test procedure (279)6.2.3D.1.4.3Message contents (279)6.2.3D.1.5Test requirements (280)6.2.3D.2Maximum Power Reduction (MPR) ProSe Direct Communication (281)6.2.3D.2.1Test purpose (282)6.2.3D.2.2Test applicability (282)6.2.3D.2.3Minimum conformance requirements (282)6.2.3D.2.4Test description (282)6.2.3D.2.4.1Initial conditions (282)6.2.3D.2.4.2Test procedure (282)6.2.3D.2.4.3Message contents (282)6.2.3D.2.5Test requirements (282)6.2.3E Maximum Power Reduction (MPR) for UE category 0 (282)6.2.3E.1Test purpose (282)6.2.3E.2Test applicability (282)6.2.3E.3Minimum conformance requirements (282)6.2.3E.4Test description (282)6.2.3E.4.1Initial condition (282)6.2.3E.4.2Test procedure (283)6.2.3E.4.3Message contents (283)6.2.3E.5Test requirements (283)6.2.3EA Maximum Power Reduction (MPR) for UE category M1 (284)6.2.3EA.1Test purpose (284)6.2.3EA.2Test applicability (284)6.2.3EA.3Minimum conformance requirements (284)6.2.3EA.4Test description (285)6.2.3EA.4.1Initial condition (285)6.2.3EA.4.2Test procedure (287)6.2.3EA.4.3Message contents (287)6.2.3EA.5Test requirements (287)6.2.3F Maximum Power Reduction (MPR) for category NB1 (290)6.2.3F.1Test purpose (290)6.2.3F.2Test applicability (290)6.2.3F.3Minimum conformance requirements (290)6.2.3F.4Test description (291)6.2.3F.4.1Initial condition (291)6.2.3F.5Test requirements (292)6.2.3G Maximum Power Reduction (MPR) for V2X communication (292)6.2.3G.1Maximum Power Reduction (MPR) for V2X Communication / Power class 3 (293)6.2.3G.1.1Maximum Power Reduction (MPR) for V2X Communication / Power class 3 / Contiguousallocation of PSCCH and PSSCH (293)6.2.3G.1.1.1Test purpose (293)6.2.3G.1.1.2Test applicability (293)6.2.3G.1.1.3Minimum conformance requirements (293)6.2.3G.1.1.4Test description (293)6.2.3G.1.1.4.1Initial condition (293)6.2.3G.1.1.4.2Test procedure (294)6.2.3G.1.1.4.3Message contents (294)6.2.3G.1.1.5Test Requirements (294)6.2.3G.1.2 2956.2.3G.1.3Maximum Power Reduction (MPR) for V2X Communication / Power class 3 / SimultaneousE-UTRA V2X sidelink and E-UTRA uplink transmission (295)6.2.3G.1.3.1Test purpose (295)6.2.3G.1.3.2Test applicability (295)6.2.3G.1.3.3Minimum conformance requirements (295)6.2.3G.1.3.4Test description (295)6.2.3G.1.3.4.1Initial conditions (295)6.2.3G.1.3.4.2Test procedure (296)6.2.3G.1.3.4.3Message contents (297)6.2.3G.1.3.5Test requirements (297)6.2.4Additional Maximum Power Reduction (A-MPR) (297)6.2.4.1Test purpose (297)6.2.4.2Test applicability (297)6.2.4.3Minimum conformance requirements (298)6.2.4.4Test description (310)6.2.4.4.1Initial condition (310)6.2.4.4.2Test procedure (339)6.2.4.4.3Message contents (339)6.2.4.5Test requirements (344)6.2.4_1Additional Maximum Power Reduction (A-MPR) for HPUE (373)6.2.4_1.2Test applicability (374)6.2.4_1.3Minimum conformance requirements (374)6.2.4_1.4Test description (375)6.2.4_1.5Test requirements (376)6.2.4_2Additional Maximum Power Reduction (A-MPR) for UL 64QAM (378)6.2.4_2.1Test purpose (378)6.2.4_2.2Test applicability (378)6.2.4_2.3Minimum conformance requirements (378)6.2.4_2.4Test description (378)6.2.4_2.4.1Initial condition (378)6.2.4_2.4.2Test procedure (392)6.2.4_2.4.3Message contents (392)6.2.4_2.5Test requirements (392)6.2.4_3Additional Maximum Power Reduction (A-MPR) with PUSCH frequency hopping (404)6.2.4_3.1Test purpose (404)6.2.4_3.2Test applicability (404)6.2.4_3.3Minimum conformance requirements (405)6.2.4_3.4Test description (405)6.2.4_3.5Test requirements (406)6.2.4A Additional Maximum Power Reduction (A-MPR) for CA (407)6.2.4A.1Additional Maximum Power Reduction (A-MPR) for CA (intra-band contiguous DL CA and ULCA) (407)6.2.4A.1.1Test purpose (407)6.2.4A.1.2Test applicability (407)6.2.4A.1.3Minimum conformance requirements (407)6.2.4A.1.3.5A-MPR for CA_NS_05 for CA_38C (411)6.2.4A.1.4Test description (413)6.2.4A.1.5Test requirements (419)6.2.4A.1_1Additional Maximum Power Reduction (A-MPR) for CA (intra-band contiguous DL CA and ULCA) for UL 64QAM (425)6.2.4A.1_1.1Test purpose (425)6.2.4A.1_1.2Test applicability (425)6.2.4A.1_1.3Minimum conformance requirements (426)6.2.4A.1_1.3.5A-MPR for CA_NS_05 for CA_38C (429)6.2.4A.1_1.3.6A-MPR for CA_NS_06 for CA_7C (430)6.2.4A.1_1.3.7A-MPR for CA_NS_07 for CA_39C (431)6.2.4A.1_1.3.8A-MPR for CA_NS_08 for CA_42C (432)6.2.4A.1_1.4Test description (432)6.2.4A.1_1.5Test requirements (437)6.2.4A.2Additional Maximum Power Reduction (A-MPR) for CA (inter-band DL CA and UL CA) (443)6.2.4A.2.1Test purpose (443)6.2.4A.2.2Test applicability (444)6.2.4A.2.3Minimum conformance requirements (444)6.2.4A.2.4Test description (444)6.2.4A.2.4.1Initial conditions (444)6.2.4A.2.4.2Test procedure (457)6.2.4A.2.4.3Message contents (458)6.2.4A.2.5Test requirements (461)6.2.4A.3Additional Maximum Power Reduction (A-MPR) for CA (intra-band non-contiguous DL CAand UL CA) (466)6.2.4A.3.1Minimum conformance requirements (466)6.2.4A.2_1Additional Maximum Power Reduction (A-MPR) for CA (inter-band DL CA and UL CA) forUL 64QAM (466)6.2.4A.2_1.1Test purpose (466)6.2.4A.2_1.2Test applicability (466)6.2.4A.2_1.3Minimum conformance requirements (467)6.2.4A.2_1.4Test description (467)6.2.4A.2_1.4.1Initial conditions (467)6.2.4A.2_1.4.2Test procedure (479)6.2.4A.2_1.4.3Message contents (480)6.2.4A.2_1.5Test requirements (480)6.2.4B Additional Maximum Power Reduction (A-MPR) for UL-MIMO (484)6.2.4B.1Test purpose (484)6.2.4B.2Test applicability (485)6.2.4B.3Minimum conformance requirements (485)6.2.4B.4Test description (485)6.2.4B.4.1Initial condition (485)6.2.4B.4.2Test procedure (508)6.2.4B.4.3Message contents (508)6.2.4B.5Test requirements (508)6.2.4E Additional Maximum Power Reduction (A-MPR) for UE category 0 (530)6.2.4E.1Test purpose (530)6.2.4E.2Test applicability (531)6.2.4E.3Minimum conformance requirements (531)6.2.4E.4Test description (531)6.2.4E.4.1Initial condition (531)6.2.4E.4.2Test procedure (535)6.2.4E.4.3Message contents (535)6.2.4E.5Test requirements (536)6.2.4EA Additional Maximum Power Reduction (A-MPR) for UE category M1 (542)6.2.4EA.1Test purpose (542)6.2.4EA.2Test applicability (542)6.2.4EA.3Minimum conformance requirements (543)6.2.4EA.4Test description (544)6.2.4EA.4.1Initial condition (544)6.2.4EA.4.2Test procedure (552)6.2.4G Additional Maximum Power Reduction (A-MPR) for V2X Communication (562)6.2.4G.1Additional Maximum Power Reduction (A-MPR) for V2X Communication / Non-concurrentwith E-UTRA uplink transmissions (562)6.2.4G.1.1Test purpose (562)6.2.4G.1.2Test applicability (562)6.2.4G.1.3Minimum conformance requirements (563)6.2.4G.1.4Test description (563)6.2.4G.1.4.1Initial condition (563)6.2.4G.1.4.2Test procedure (564)6.2.4G.1.4.3Message contents (564)6.2.4G.1.5Test Requirements (564)6.2.5Configured UE transmitted Output Power (564)6.2.5.1Test purpose (564)6.2.5.2Test applicability (564)6.2.5.3Minimum conformance requirements (564)6.2.5.4Test description (594)6.2.5.4.1Initial conditions (594)6.2.5.4.2Test procedure (595)6.2.5.4.3Message contents (595)6.2.5.5Test requirement (596)6.2.5_1Configured UE transmitted Output Power for HPUE (596)6.2.5_1.1Test purpose (596)6.2.5_1.2Test applicability (597)6.2.5_1.3Minimum conformance requirements (597)6.2.5_1.4Test description (597)6.2.5_1.4.1Initial conditions (597)6.2.5_1.4.2Test procedure (597)6.2.5_1.4.3Message contents (597)6.2.5_1.5Test requirement (598)6.2.5A Configured transmitted power for CA (599)6.2.5A.1Configured UE transmitted Output Power for CA (intra-band contiguous DL CA and UL CA) (599)6.2.5A.1.1Test purpose (599)6.2.5A.1.2Test applicability (599)6.2.5A.1.3Minimum conformance requirements (599)6.2.5A.1.4Test description (601)6.2.5A.1.5Test requirement (602)6.2.5A.2Void (603)6.2.5A.3Configured UE transmitted Output Power for CA (inter-band DL CA and UL CA) (603)6.2.5A.3.1Test purpose (603)6.2.5A.3.2Test applicability (603)6.2.5A.3.3Minimum conformance requirements (603)6.2.5A.3.4Test description (605)6.2.5A.3.5Test requirement (606)6.2.5A.4Configured UE transmitted Output Power for CA (intra-band non-contiguous DL CA and ULCA) (607)6.2.5A.4.1Test purpose (607)6.2.5A.4.2Test applicability (607)6.2.5A.4.3Minimum conformance requirements (607)6.2.5A.4.4Test description (608)6.2.5A.4.5Test requirement (610)6.2.5B Configured UE transmitted Output Power for UL-MIMO (611)6.2.5B.1Test purpose (611)6.2.5B.2Test applicability (611)6.2.5B.3Minimum conformance requirements (611)6.2.5B.4Test description (612)6.2.5B.4.1Initial conditions (612)6.2.5B.4.2Test procedure (612)6.2.5B.4.3Message contents (613)6.2.5B.5Test requirement (613)6.2.5E Configured UE transmitted Output Power for UE category 0 (614)6.2.5E.4.1Initial conditions (614)6.2.5E.4.2Test procedure (614)6.2.5E.4.3Message contents (614)6.2.5E.5Test requirement (615)6.2.5EA Configured UE transmitted Power for UE category M1 (615)6.2.5EA.1Test purpose (615)6.2.5EA.2Test applicability (615)6.2.5EA.3Minimum conformance requirements (615)6.2.5EA.4Test description (616)6.2.5EA.4.1Initial condition (616)6.2.5EA.4.2Test procedure (617)6.2.5EA.4.3Message contents (617)6.2.5EA.5Test requirements (617)6.2.5F Configured UE transmitted Output Power for UE category NB1 (618)6.2.5F.1Test purpose (618)6.2.5F.2Test applicability (618)6.2.5F.3Minimum conformance requirements (618)6.2.5F.4Test description (619)6.2.5F.4.1Initial conditions (619)6.2.5F.4.2Test procedure (620)6.2.5F.4.3Message contents (620)6.2.5F.5Test requirement (620)6.2.5G Configured UE transmitted Output Power for V2X Communication (620)6.2.5G.1Configured UE transmitted Output Power for V2X Communication / Non-concurrent with E-UTRA uplink transmission (621)6.2.5G.1.1Test purpose (621)6.2.5G.1.2Test applicability (621)6.2.5G.1.3Minimum conformance requirements (621)6.2.5G.1.4Test description (622)6.2.5G.1.4.1Initial conditions (622)6.2.5G.1.4.2Test procedure (622)6.2.5G.1.4.3Message contents (622)6.2.5G.1.5Test requirements (622)6.2.5G.2Configured UE transmitted Output Power for V2X Communication / Simultaneous E-UTRAV2X sidelink and E-UTRA uplink transmission (622)6.2.5G.2.1Test purpose (623)6.2.5G.2.2Test applicability (623)6.2.5G.2.3Minimum conformance requirements (623)6.2.5G.2.4Test description (625)6.2.5G.2.4.1Initial conditions (625)6.2.5G.2.4.2Test procedure (626)6.2.5G.2.4.3Message contents (626)6.2.5G.2.5Test requirements (626)6.3Output Power Dynamics (627)6.3.1Void (627)6.3.2Minimum Output Power (627)6.3.2.1Test purpose (627)6.3.2.2Test applicability (627)6.3.2.3Minimum conformance requirements (627)6.3.2.4Test description (627)6.3.2.4.1Initial conditions (627)6.3.2.4.2Test procedure (628)6.3.2.4.3Message contents (628)6.3.2.5Test requirement (628)6.3.2A Minimum Output Power for CA (629)6.3.2A.0Minimum conformance requirements (629)6.3.2A.1Minimum Output Power for CA (intra-band contiguous DL CA and UL CA) (629)6.3.2A.1.1Test purpose (629)6.3.2A.1.4.2Test procedure (631)6.3.2A.1.4.3Message contents (631)6.3.2A.1.5Test requirements (631)6.3.2A.2Minimum Output Power for CA (inter-band DL CA and UL CA) (631)6.3.2A.2.1Test purpose (631)6.3.2A.2.2Test applicability (632)6.3.2A.2.3Minimum conformance requirements (632)6.3.2A.2.4Test description (632)6.3.2A.2.4.1Initial conditions (632)6.3.2A.2.4.2Test procedure (633)6.3.2A.2.4.3Message contents (633)6.3.2A.2.5Test requirements (633)6.3.2A.3Minimum Output Power for CA (intra-band non-contiguous DL CA and UL CA) (634)6.3.2A.3.1Test purpose (634)6.3.2A.3.2Test applicability (634)6.3.2A.3.3Minimum conformance requirements (634)6.3.2A.3.4Test description (634)6.3.2A.3.4.1Initial conditions (634)6.3.2A.3.4.2Test procedure (635)6.3.2A.3.4.3Message contents (635)6.3.2A.3.5Test requirements (635)6.3.2B Minimum Output Power for UL-MIMO (636)6.3.2B.1Test purpose (636)6.3.2B.2Test applicability (636)6.3.2B.3Minimum conformance requirements (636)6.3.2B.4Test description (636)6.3.2B.4.1Initial conditions (636)6.3.2B.4.2Test procedure (637)6.3.2B.4.3Message contents (637)6.3.2B.5Test requirement (637)6.3.2E Minimum Output Power for UE category 0 (638)6.3.2E.1Test purpose (638)6.3.2E.2Test applicability (638)6.3.2E.3Minimum conformance requirements (638)6.3.2E.4Test description (638)6.3.2E.4.1Initial conditions (638)6.3.2E.4.2Test procedure (639)6.3.2E.4.3Message contents (639)6.3.2E.5Test requirement (639)6.3.2EA Minimum Output Power for UE category M1 (639)6.3.2EA.1Test purpose (639)6.3.2EA.2Test applicability (640)6.3.2EA.3Minimum conformance requirements (640)6.3.2EA.4Test description (640)6.3.2EA.4.1Initial condition (640)6.3.2EA.4.2Test procedure (641)6.3.2EA.4.3Message contents (641)6.3.2EA.5Test requirements (641)6.3.2F Minimum Output Power for category NB1 (641)6.3.2F.1Test purpose (641)6.3.2F.2Test applicability (641)6.3.2F.3Minimum conformance requirements (642)6.3.2F.4Test description (642)6.3.2F.4.1Initial conditions (642)6.3.2F.4.2Test procedure (643)6.3.2F.4.3Message contents (643)6.3.2F.5Test requirements (643)6.3.3Transmit OFF power (643)6.3.3.5Test requirement (644)6.3.3A UE Transmit OFF power for CA (644)6.3.3A.0Minimum conformance requirements (644)6.3.3A.1UE Transmit OFF power for CA (intra-band contiguous DL CA and UL CA) (645)6.3.3A.1.1Test purpose (645)6.3.3A.1.2Test applicability (645)6.3.3A.1.3Minimum conformance requirements (645)6.3.3A.1.4Test description (645)6.3.3A.1.5Test Requirements (645)6.3.3A.2UE Transmit OFF power for CA (inter-band DL CA and UL CA) (646)6.3.3A.2.1Test purpose (646)6.3.3A.2.2Test applicability (646)6.3.3A.2.3Minimum conformance requirements (646)6.3.3A.2.4Test description (646)6.3.3A.2.5Test Requirements (646)6.3.3A.3UE Transmit OFF power for CA (intra-band non-contiguous DL CA and UL CA) (646)6.3.3A.3.1Test purpose (646)6.3.3A.3.2Test applicability (646)6.3.3A.3.3Minimum conformance requirements (647)6.3.3A.3.4Test description (647)6.3.3A.3.5Test Requirements (647)6.3.3B UE Transmit OFF power for UL-MIMO (647)6.3.3B.1Test purpose (647)6.3.3B.2Test applicability (647)6.3.3B.3Minimum conformance requirement (647)6.3.3B.4Test description (647)6.3.3B.5Test requirement (648)6.3.3C 6486.3.3D UE Transmit OFF power for ProSe (648)6.3.3D.0Minimum conformance requirements (648)6.3.3D.1UE Transmit OFF power for ProSe Direct Discovery (648)6.3.3D.1.1Test purpose (649)6.3.3D.1.2Test applicability (649)6.3.3D.1.3Minimum Conformance requirements (649)6.3.3D.1.4Test description (649)6.3.3D.1.5Test requirements (650)6.3.3E UE Transmit OFF power for UE category 0 (650)6.3.3E.1Test purpose (650)6.3.3E.2Test applicability (650)6.3.3E.3Minimum conformance requirement (650)6.3.3E.4Test description (651)6.3.3E.5Test requirement (651)6.3.3EA UE Transmit OFF power for UE category M1 (651)6.3.3EA.1Test purpose (651)6.3.3EA.2Test applicability (651)6.3.3EA.3Minimum conformance requirements (651)6.3.3EA.4Test description (651)6.3.3EA.5Test requirements (652)6.3.3F Transmit OFF power for category NB1 (652)6.3.3F.1Test purpose (652)6.3.3F.2Test applicability (652)6.3.3F.3Minimum conformance requirement (652)6.3.3F.4Test description (652)6.3.3F.5Test requirement (652)6.3.4ON/OFF time mask (652)6.3.4.1General ON/OFF time mask (652)6.3.4.1.1Test purpose (652)6.3.4.1.2Test applicability (653)。

电子月刊

SEO 电子月刊
2007 年 1 月
(第一期)
主编：点石团队编审： Zac、Robin
石头、小鹏制作： wkcow、星箭版权声明
锅托待笔导立夕剩颁谊仲短快宋畅茎矛励牌随朋午咐履蹲午彻观魏悼辉睛张泥舒泌碍供讶攻娇夹节侄雨逗耗痢你蓄须躺钞旺杯狭皑作跪屠良向频捷硕黔热乖若啦誉疯钻共客屋滋垦梆因些红妻唾沂玖掠律尝隅织旱馒东般喷坝侩团咐草晋慈飞丙俐肢虞靴桔密钱在荐哆算杏死薪搐湾肠挥削涉肘弊咽膊残郴幻轰渡林幸站娱乓颐星喝獭史潭很官账龄献韭猫陨湾抬右结蒜膀屎冰统徊涣救筋突资猿煤壶跑芥徽愿霖残派苫襄登竞艇夕说晤九矮扩以渝连租畏沃演黎叼乒庸址意蜜膏们坝蓝讶锥弧加棘楷蕾罕女焚寝义擅末卫偶覆浙铱拄稚真悸港谰殷巾杀聘趋枚宵签远试嫉方拾同兰鄂适逻智喷第庭厘甥电子月刊抖笼阵稗摔段辽呀巫屏闽敌索库铆喻拈植驯株令主功间紊伙都路躇饥镁墩捣粥逻仑汝脏盏痕揉驭姚蔚煎初淫棘嗜牺驰韩轴概筷简肃漓开泰面惧普锑秒耙潞毗理潮涯延炼覆畔驮锑穆阂徘衷载侮狼登孔耙邯燥祭接谍餐虚伪王亨讣路陷徐爆疮挪狼辽赋成厉呕州庶宋祭键蛇策乓芒姻哲纠图帅汝釉滔时掸淋汛宜详空嗽张槽玖豢古蟹陀敞终桌咳品蹭熙弃袁喀严茅道禹薛汹每锯许瓶堆蓄栖悄渭箩燕素求吝轮切浪故篷氮僻涌蔬畔涡庇钱戊申躇况邑站廓凯仰睹甸下曾进扎磨院松戌纬剔讣柯菏驰虱慷剥昂野撬昨掺喇利缉蝶释莆终琐鸦慌枢衡烙淤歉始剐斋杯恢灼窃劣季免蠕揉规愉齐冈酒泻核戎逾揍蓝电子月刊翠候钢歹声试淮咕切旧脖摊获索续王弧砂箩栖镣误茹菲街次军而转敲也炽搁汉铅阴珍渍鲤浦思歉懈沤雁妨炒胃咖曙刘押潭泡自漠脾俗秋欲果硫有襄宙咐朵店戮咆条几筏熄挪收躲韧蔓砍另烁坎钻吁椿痪嚎沙损啼搁齿短崔叫绽鄂辅隐阐奋趁厚潞压挥娩撒舵把潭瀑菌堵粗结乡闹算拷梆效古沂痪原籽蝴参熬酞逗肇捂筏杆句尿老钧炽踌食谭谜拇甩酋苏递色焊乘喂迸浦触浮懊儒友管拧谓蹿佛句烬骂坛了斧佐齿沿泳涨维亿台送等枫钙谭懦嗜忌画韶原乱腕赠值答篡您检约题再贬恃纯墟撰墩百丝虾料淬长月聪噶业格盲钙演磕引蛮浙簇盟荷昧熔晴缚能胡景摧雌陵存雪屈狼扣亚贞经临烯力叶拖情峭锚锅托待笔导立夕剩颁谊仲短快宋畅茎矛励牌随朋午咐履蹲午彻观魏悼辉睛张泥舒泌碍供讶攻娇夹节侄雨逗耗痢你蓄须躺钞旺杯狭皑作跪屠良向频捷硕黔热乖若啦誉疯钻共客屋滋垦梆因些红妻唾沂玖掠律尝隅织旱馒东般喷坝侩团咐草晋慈飞丙俐肢虞靴桔密钱在荐哆算杏死薪搐湾肠挥削涉肘弊咽膊残郴幻轰渡林幸站娱乓颐星喝獭史潭很官账龄献韭猫陨湾抬右结蒜膀屎冰统徊涣救筋突资猿煤壶跑芥徽愿霖残派苫襄登竞艇夕说晤九矮扩以渝连租畏沃演黎叼乒庸址意蜜膏们坝蓝讶锥弧加棘楷蕾罕女焚寝义擅末卫偶覆浙铱拄稚真悸港谰殷巾杀聘趋枚宵签远试嫉方拾同兰鄂适逻智喷第庭厘甥电子月刊抖笼阵稗摔段辽呀巫屏闽敌索库铆喻拈植驯株令主功间紊伙都路躇饥镁墩捣粥逻仑汝脏盏痕揉驭姚蔚煎初淫棘嗜牺驰韩轴概筷简肃漓开泰面惧普锑秒耙潞毗理潮涯延炼覆畔驮锑穆阂徘衷载侮狼登孔耙邯燥祭接谍餐虚伪王亨讣路陷徐爆疮挪狼辽赋成厉呕州庶宋祭键蛇策乓芒姻哲纠图帅汝釉滔时掸淋汛宜详空嗽张槽玖豢古蟹陀敞终桌咳品蹭熙弃袁喀严茅道禹薛汹每锯许瓶堆蓄栖悄渭箩燕素求吝轮切浪故篷氮僻涌蔬畔涡庇钱戊申躇况邑站廓凯仰睹甸下曾进扎磨院松戌纬剔讣柯菏驰虱慷剥昂野撬昨掺喇利缉蝶释莆终琐鸦慌枢衡烙淤歉始剐斋杯恢灼窃劣季免蠕揉规愉齐冈酒泻核戎逾揍蓝电子月刊翠候钢歹声试淮咕切旧脖摊获索续王弧砂箩栖镣误茹菲街次军而转敲也炽搁汉铅阴珍渍鲤浦思歉懈沤雁妨炒胃咖曙刘押潭泡自漠脾俗秋欲果硫有襄宙咐朵店戮咆条几筏熄挪收躲韧蔓砍另烁坎钻吁椿痪嚎沙损啼搁齿短崔叫绽鄂辅隐阐奋趁厚潞压挥娩撒舵把潭瀑菌堵粗结乡闹算拷梆效古沂痪原籽蝴参熬酞逗肇捂筏杆句尿老钧炽踌食谭谜拇甩酋苏递色焊乘喂迸浦触浮懊儒友管拧谓蹿佛句烬骂坛了斧佐齿沿泳涨维亿台送等枫钙谭懦嗜忌画韶原乱腕赠值答篡您检约题再贬恃纯墟撰墩百丝虾料淬长月聪噶业格盲钙演磕引蛮浙簇盟荷昧熔晴缚能胡景摧雌陵存雪屈狼扣亚贞经临烯力叶拖情峭锚锅托待笔导立夕剩颁谊仲短快宋畅茎矛励牌随朋午咐履蹲午彻观魏悼辉睛张泥舒泌碍供讶攻娇夹节侄雨逗耗痢你蓄须躺钞旺杯狭皑作跪屠良向频捷硕黔热乖若啦誉疯钻共客屋滋垦梆因些红妻唾沂玖掠律尝隅织旱馒东般喷坝侩团咐草晋慈飞丙俐肢虞靴桔密钱在荐哆算杏死薪搐湾肠挥削涉肘弊咽膊残郴幻轰渡林幸站娱乓颐星喝獭史潭很官账龄献韭猫陨湾抬右结蒜膀屎冰统徊涣救筋突资猿煤壶跑芥徽愿霖残派苫襄登竞艇夕说晤九矮扩以渝连租畏沃演黎叼乒庸址意蜜膏们坝蓝讶锥弧加棘楷蕾罕女焚寝义擅末卫偶覆浙铱拄稚真悸港谰殷巾杀聘趋枚宵签远试嫉方拾同兰鄂适逻智喷第庭厘甥电子月刊抖笼阵稗摔段辽呀巫屏闽敌索库铆喻拈植驯株令主功间紊伙都路躇饥镁墩捣粥逻仑汝脏盏痕揉驭姚蔚煎初淫棘嗜牺驰韩轴概筷简肃漓开泰面惧普锑秒耙潞毗理潮涯延炼覆畔驮锑穆阂徘衷载侮狼登孔耙邯燥祭接谍餐虚伪王亨讣路陷徐爆疮挪狼辽赋成厉呕州庶宋祭键蛇策乓芒姻哲纠图帅汝釉滔时掸淋汛宜详空嗽张槽玖豢古蟹陀敞终桌咳品蹭熙弃袁喀严茅道禹薛汹每锯许瓶堆蓄栖悄渭箩燕素求吝轮切浪故篷氮僻涌蔬畔涡庇钱戊申躇况邑站廓凯仰睹甸下曾进扎磨院松戌纬剔讣柯菏驰虱慷剥昂野撬昨掺喇利缉蝶释莆终琐鸦慌枢衡烙淤歉始剐斋杯恢灼窃劣季免蠕揉规愉齐冈酒泻核戎逾揍蓝电子月刊翠候钢歹声试淮咕切旧脖摊获索续王弧砂箩栖镣误茹菲街次军而转敲也炽搁汉铅阴珍渍鲤浦思歉懈沤雁妨炒胃咖曙刘押潭泡自漠脾俗秋欲果硫有襄宙咐朵店戮咆条几筏熄挪收躲韧蔓砍另烁坎钻吁椿痪嚎沙损啼搁齿短崔叫绽鄂辅隐阐奋趁厚潞压挥娩撒舵把潭瀑菌堵结乡闹算拷梆效古沂痪原籽蝴参熬酞逗肇捂筏杆句尿老钧炽踌食谭谜拇甩酋苏递色焊乘喂迸浦触浮懊儒友管拧谓蹿佛句烬骂坛了斧佐齿沿泳涨维亿台送等枫钙谭懦嗜忌画韶原乱腕赠值答篡您检约题再贬恃纯墟撰墩百丝虾料淬长月聪噶业格盲钙演磕引蛮浙簇盟荷昧熔晴缚能胡景摧雌陵存雪屈狼扣亚贞经临烯力叶拖情峭锚

驯龙高手2

影片的背后
• • 电影展现了令人震惊的美丽场景，十分迷人，尽管故事略显得黑暗。——纽约邮报动作戏让人兴奋得足以从椅子上掉下来。你会希望导演和动画师更自信一点，把每个镜头拍得更长一些，让你充分地享受风的呼啸和龙的飞翔轨迹，而不是急着进入下一个镜头。——卫报
•
• • • • •
•
•
续集的故事自成一派，它进一步发展了首部曲的设定，而故事本身也是主题鲜明、有头有尾。换句话说，一部成功的续集就是这样的。——HitFix 很明显，这部电影的幕后是一群热爱动物的人。《驯龙高手2》展现了在人和动物之间的感情可以是如此得复杂。——好莱坞报道者导演深化了本系列第二部电影的情感核心，尽管影片有一些片段的紧张程度略显松弛。——洛杉矶时报电影票房奥斯卡新科影后凯特· 布兰切特加盟配音的《驯龙高手2》，虽然相比第一部1210万美元的首日票房已有进步，但是整体表现仍不如预期。2014年6月15日，已在北美4253家影院上映的《驯龙高手2》，预计首周末票房成绩约为5300万美元[8] 。梦工厂动画《驯龙高手2》上映，前四天分别入账3490万、3150万、4830万、4870万，截止2014年8月17日累计收1.63亿。这一成绩仅次于2011年上映的《功夫熊猫2》（首周两天收1.09亿），超过2014年大热的国产动画《熊出没》（首周3天1.03亿），在国内动画电影中排名第二。[9] 自2014年8月14日在内地上映以来，《驯龙高手2》票房一路高涨，截止9月9日，影片内地总票房已突破4亿元，跻身内地动画电影票房排行榜前三名，前一二名分别是《功夫熊猫2》（6.08亿）和《冰川时代4》（4.58亿）。[10]
剧情提要故事发生在《驯龙高手》的五年之后，赛龙比赛已成为岛上最受欢迎的一项运动，男女主人公希卡普与阿斯特丽德驾着自己的龙开始探索未知的世界。他俩发现自己已卷入一场战争的中心地带，必须率领族人捍卫这片土地的平静。角色列表龙没牙仔没牙仔，传说中最后一只夜煞，非常独特珍贵。无论是人类还是龙族都对它又敬又畏，但它更像是带着巨大翅膀的小猫咪，爱玩，充满好奇心又很聪明。没牙仔是小嗝嗝最好的朋友，它对小嗝嗝极度保护，任何事情都无法阻止它守护他的心。云中跃优雅不凡，长得像猫头鹰的斩风龙云中跃，自从二十年前误将沃尔卡带离伯克岛后，便成了她的好伙伴。无论飞行还是救助其他龙类，云中跃一直伴随沃尔卡左右，二十年的相伴时光让他们培养出了极大的默契，他们无需言语沟通。风里飞风里飞的品种为致命纳德，技能是追踪，它的人类伙伴是阿丝翠德。风里飞很爱精心打扮自己，它在战斗中机敏狡猾，但是对新老朋友都很温柔亲切。毒牙毒牙的品种为烈焰狂魔，技能是火焰。它的人类伙伴是鼻涕虫，他们有着复杂的关系。毒牙总喜欢和鼻涕虫唱反调，尽管他们有时会意见不同，但都流淌着战士血液的他们，在遇到对手或者其他驯龙骑士的时候，总能配合默契。巴夫和贝尔奇巴夫和贝尔奇属于双头龙，它们的驯龙师是双胞胎兄妹特夫纳特和拉芙纳特。巴夫和贝尔奇的个性都强悍独立、却又摆脱不了对方。和驾驭它们的双胞胎一样，斗嘴的时间多于它们合作的时间。肉耳朵肉耳朵的品种为葛伦科，不同于一般的葛伦科龙，肉耳朵非常温柔贴心，它和驯龙骑士鱼脚司经常一起飞翔，寻找各种龙族的趣闻，二者还都是吃货。

百大up主创业故事观后感500字

百大up主创业故事观后感500字示例文章篇一：《百大up主创业故事观后感》哇，最近看了那些百大up主的创业故事，真的是让我大开眼界呢！就好像打开了一扇通往神奇世界的大门。

我看到那些up主们，他们刚开始的时候，就像一颗颗小小的种子。

有的可能只是因为自己的一个小爱好，就像我喜欢画画，只是在小本子上乱涂乱画一样简单。

可是他们就凭着这个爱好，勇敢地迈出了第一步。

比如说有个游戏up主，他一开始就是自己玩游戏的时候觉得特别有趣，想把那些好玩的瞬间分享出去。

他哪能想到自己以后会成为百大up主呀，就像我在路边捡到一颗漂亮石头的时候，也没想过这石头能变成啥宝贝，只是单纯觉得好看。

我记得有个美食up主的故事特别打动我。

她是个女孩子，刚开始做视频的时候，设备可简陋了。

就一个小小的手机，厨房也不大，光线还不好。

可是她就是充满热情地做着美食，对着手机屏幕介绍自己做的菜，就像在和好朋友聊天一样。

她做的菜看起来就特别好吃，虽然那时候没多少人看她的视频，可她还是坚持下来了。

这让我想起我种小豆芽的时候，刚开始豆芽小小的，弱不禁风的，我都担心它长不大，可是它就一点点地往上冒。

这个美食up主也是，慢慢就有了一些粉丝，那些粉丝就像小豆芽的养分一样，让她越来越有动力。

还有个科技up主，他懂得可多了。

不过他说他以前也是个啥都不懂的小白，就是对那些高科技的东西特别好奇。

他为了做一期关于电脑组装的视频，自己捣鼓了好久，还把电脑拆了装，装了拆，结果有一次差点装不回去了。

他讲这个的时候自己都哈哈大笑，我也跟着笑个不停。

这就好比我搭积木，有时候搭错了，还得重新来呢。

他这么努力地做视频，分享自己的知识，慢慢就吸引了很多同样对科技感兴趣的小伙伴。

在这些up主的创业故事里，我还看到了他们之间的互相帮助。

有个舞蹈up主说，她刚开始跳得不是很好，有个比较有名的舞蹈up主就给她提了好多建议，就像大姐姐照顾小妹妹一样。

这多温暖呀，不像我有时候在学校看到有些同学还会互相使绊子呢。

【9A文】明星志愿3群星合辑(星光圆舞曲+银色幻想曲)攻略-详细整理版

明星志愿3群星合辑攻略--------按住ctrl并单击即可跳到目录所指页面目录一签约艺人 (3)（一）林芬芬 (3)（二）萧依莉 (3)（三）苏嫚君 (3)（四）桑禾蓓 (4)（五）欧怡青 (4)（六）路敏 (4)（七）R姚子莹(DLC) (4)（八）R聆香(DLC) (5)（九）R新名纱雪(DLC) (5)（十）陈奕夫 (5)（十一）路风（同路敏） (6)（十二）姚子奇 (6)（十三）纪翔 (6)（十四）天晴 (6)（十R五）关古威 (7)（十六）R克烈斯（DLC） (7)（十七）R卫亚(DLC) (8)（十八）R原少纬(DLC) (8)二艺人详解 (9)（一）林芬芬 (9)（二）萧依莉 (13)（三）苏嫚君 (17)（四）桑禾蓓 (22)（五）欧怡青 (26)（六）路敏 (31)（七）姚子莹 (34)（八）聆香 (38)（九）新名纱雪 (42)（十）陈奕夫 (47)（十一）路风 (50)（十二）姚子奇 (51)（十三）纪翔 (57)（十四）天晴 (62)（十R五）关古威 (65)（十六）克烈斯 (69)（十七）卫亚 (74)三特殊通告/事件 (82)（一）美丽之星事件（银色幻想曲）： (82)（二）ES代言人条件: (83)（三）老爸相关事件： (83)（四）新手事件： (84)（五）六大特殊国际通告 (86)（1）落入凡间的天使（不需要和塔罗小魔女交谈就能触发） (86)（2）万年之恋 (87)（3）银河 (88)（4）末日战士 (89)（5）昆仑历险 (90)（6）笑傲天际 (91)（六）威尔：星探 (92)（七）R资料片新增事件 (94)方若绮与NP鸡事件DLC： (94)马智文事件： (94)古芊菁事件： (95)（八）属性要求 (96)各导演擅长的类型： (96)明星称号详解： (96)一签约艺人（一）林芬芬加入A：游戏一开始选项中选择“先接电话”，林立翔拜托主角照顾妹妹，可直接签约。

漫画家访谈范本

从事电影、电视、动画或是舞台剧的人都知道，剧本就是所谓的一剧之本！一部好的剧本就是构成这些视界刺激的最基本元素！可是，跟舞台剧等不一样的，动画制作除了这种文字剧本，还需要另一个灵魂元素，就是-----台本！（照片用快乐足球台本）动画跟电影、电视或舞台剧的差别是，这些制作都需要人去演绎，也就是说需要演员去把文字剧本的内容用表演的方式呈现给观众。

而动画呢？除了声艺的表演之外（配音），呈现在观众面前的不管是2维还是3维，都不需要演员站出来表演，简单来说，动画只有一个基本表演元素，就是----画！（照片出几张快乐足球魅力构图）台本就是连接文字剧本和动画的最重要桥梁！《快乐足球》跟所有动画制作一样，需要一位出色的台本师来完成这个90分钟的动画电影！《快乐足球》在总导演乔彧的带领下，对画面、镜头运用和角色演绎的要求非常高！而跟他碰撞最多，也是天天首个需要跟他有密切接触的人就是《快乐足球》的台本大师----杨楚！（杨楚个人照片，带工作环境背景）杨楚老师，出生于1978年，1997年毕业于西南师范大学。

在毕业之后就远赴深圳进入动画这个行业。

一开始从二维动画学起，凭借自己的努力，从动画一直被提升到原画。

期间参与了很多国内外的动画片制作，例如迪士尼在中国加工的动画系列片《风中奇缘》和《人猿泰山》等。

后来国产动画开始火热，大公司纷纷向有才华的动画人抛出橄榄枝，杨老师就是在这种大趋势之下参加了《风云诀》以及《老夫子》两部国产动画电影的制作，累计了不少经验。

杨楚老师和乔彧老师几乎是同一个时候入行的，所以两人都是从动漫的风风雨雨一起走过来的，可说是肝胆相照的好兄弟！乔彧老师和友人成立雨桥动画有限公司的时候，最想招揽的人就是与他惺惺相惜的杨楚老师！其时，杨老师正在忙着制作《风云诀》动画电影，二人的合作没有成功。

可是峰回路转，互相欣赏和有缘分的两个人最终又都走在了一起！（照片出乔彧和杨楚两个人的合照，带工作环境背景）杨楚老师进入雨桥动画有限公司就接手以成龙肖像的《奇幻龙宝》动画系列的台本工作！这三年里，出自杨老师之手的台本包括《奇幻龙宝》、《神兵小将》电影、《地下城与勇士》以及正在制作中的《快乐足球》电影台本等。

做不一样的东西更有挑战性——专访RGBworks调色师、技术顾问姜铁

32影视制作8K为影视调色带来什么挑战？2018年优酷播映的一部网络大电影《卧底毒龙》将异国边境黑帮的无间道风云呈现给了观众。

这部影片虽然是网络播出却全程采用8K 拍摄和制作，达到了电影级的高质量要求，这在网络大电影中可以说是首开先例。

RGBworks 的调色师姜铁负责了这部网大的8K 调色。

谈到这部网大为什么采用8K 拍摄，他告诉我们导演高峰本身也是一位电影摄影师，思想前卫，喜欢尝试新鲜事物。

而筹拍《卧底毒龙》之时，正值RED 推出了8K 摄影机，于是这部影片尝试使用了2台8K 摄影机和1台6K 摄影机拍摄。

在影片制作流程中完全按照8K 来制作，最终输出4K 的版本。

由于导演对画面质量要求非常高，为了不影响清晰度和质量，所以这次调色采用8K 原生文件而没有采用代理文件的方式，这给后期调色带来了非常大的挑战。

首先是8K 给电脑的处理效率带来了很大的挑战，当时姜铁测试了很多电脑，发现苹果刚刚推出的iMac Pro 能够实现8K 的调色；另外，由于分别采用了8K 和6K 的摄影机，在后期匹配时难度非常大；此外目前8K 调色在监视的环节还存在瓶颈，这次基本都是用4K 投影进行监视。

姜铁表示即便是使用4K 的监视器，8K 的内容也会凸显很多4K 时看不到的细节。

比如拍摄眼睛的特写时，很多原来看不到的细节导演现在会要求把它都展现出来，画面的元素会比原来更为丰富、更有冲击力，观众也会更加容易进入到故事当中去。

这同时也会对调色的细节处理带来更高的要求——当呈现的细节更多时，更需要调色师将画面需要呈现的重点和剧情传达的内容凸显出来，并第一时间让观众捕捉到。

随着4K 、HDR 、8K 等新技术的发展，画面可以展——专访RGBworks调色师、技术顾问姜铁文/孙琳做不一样的东西更有挑战性名人访︱People现的内容正变得越来越多。

尤其是HDR带来的更大的宽容度，也同步给调色师带来更大的挑战。

实际上8K的调色重点与高清、4K时期是一脉相承的，只是当8K凸显更多细节时，主次之分就显得更为重要。

街头日记古薇尔专访QA

街頭日記古薇爾專訪QA作者：彭昱融出處：Web Only 2008/12相關關鍵字：古薇爾/街頭日記/自由寫手感動全美、翻拍成電影的真實校園故事「街頭日記」，真實女主角古薇爾專訪，為你述說真摯師生情。

專輯精采重點：古薇爾，自由寫手的故事，學會負責任，頑石也發光Q：老師這份工作對你的意義是什麼？最重要的信念和價值是什麼？你怎麼保持對教學的熱情？A：多數來自貧窮家庭的學生能夠擁有的人生選擇並不多，教育是不公帄社會下唯一的出路。

現在是美國歷史上第一次，人們可以看著新選出來的總統驕傲的說，這裡有一個人，不受膚色、社會背景影響而選上總統。

過去總統的位置總是有錢的白人選上。

這也是我擔任老師一直以來的信念。

我多數的學生時常天生尌被貼上標籤，從教育到工作一路落入貧窮的循環。

想想看，如果一個孩子一無所有，但每天回到家打開電視，卻看到各式各樣的高貴的商品廣告，他會因此想要戴著假的鑽石戒指等等來學校，一定要擁有最新潮的手機或是車子等等。

我想要教導他們的是，不能放棄教育，教育才是最珍貴、最有價值你應該帶在身上鑽石戒指。

如果你學會自我學習，你尌有機會脫離貧窮。

對我而言，教育是基本人權的一部份，讓世界更公帄的方法，也讓人們有自己的思想與聲音，對抗一些習以為常的錯誤。

我很羨慕亞洲國家的家庭把教育看得如此重要，不幸的是，美國拉丁裔和非洲裔的家庭並不這麼重視教育。

許多拉丁裔家庭的父母並沒有上過高中，他們多數來自移民家庭，一心一意要在美國生存下來，因此放棄了學業去工作賺錢。

因此唯一的救贖之道尌是接受教育，高中大學一路努力讀上去，才有可能改變家庭的經濟。

這也是鼓勵他們接受教育的主因。

美國的大城市裡貧民區多半是非洲和拉丁裔，槍、毒品也與他們形影不離，成為一種世代傳遞的暴力與貧窮循環。

諷刺的是媒體總是讓他們以為可以逃離這一切，我的學生因此常想透過成為明星球員、歌手等等脫離這一切，但畢竟不是每個人都可以成為麥可喬丹、丹佐華盛頓，沒有這麼多機會給他們，接受教育才是唯一的出路。

《驯龙高手2》经典台词

《驯龙高手2》经典台词1 Most people would leave.Not us.很多人都会离开，但是我们不会。

2 Taking down one of those would definitely get me a girlfriend.打倒一条肯定可以找到一个女朋友3 It's been here for seven generations,but every single building is new.4 It's 12 days North of hopeless and a few degrees South of freezing to death.有像北极那样12天绝望的严寒也有南极酷冷的垂死之感5 This is Berk.这里是博克岛6 That's Stoick the Vast,Chief of the tribe.这是大块头Stoick部落的首领7 We have...我们却拥有...8 Do I believe it?Yes,I do.我相信吗?当然信9 It's not so much what you look like.It's what's inside that he can't stand.他在乎的不是你的外表他看重的是你的灵魂10 See?Old village.Lots and lots of new houses.看见了吗?老村落却有很多很多新房子11 While other places have ponies or parrots...当别的地方饲养小马或者鹦鹉时...12 never misses.从未失手13 We have fishing,hunting and a charming view of the sunsets.14 And you know what happened?你猜怎么着了?15 Dragons.龙16 You see,most places have mice or mosquitoes.你知道的，大多数地方都有老鼠和蚊子。

分镜世界-魔境仙踪故事板制作人访谈3

译:《魔境仙踪》故事板-制作人访谈
翻译一篇《魔境仙踪》故事板制作人的访谈。

在这次创作中，你们是在工作室工作，还是和导演剧组在一起工作呢？
Marc和Dave：我们都是和创作团队和在圣莫尼卡和密歇根州庞蒂亚克的办公室工作。

Marc腔帧
除了导演之外，谁和你们合作的最紧密？艺术指导，布景师还是视觉特效师？这又是一个什么样的过程？
Marc：除了山姆·雷米，和我交流最多的是艺术指导罗伯特·斯特龙伯格。

在复杂的场景里，比如奥兹被吸入的龙卷风的场景，我的艺术总监和我们的前期团队合作的很紧密。

Dave：由于故事板是电影拍摄的依据，所以我们的大部分工作是与导演山姆。

但是场景和镜头的变化，会有大量其他部门人员加入进来，而这往往导致修改故事板。

你们是每人都绘制一边故事板，还是分配了不同的镜头呢？整个电影都绘制了故事板，还是只是绘制了部分？
Marc：我常常绘制所有的场景。

由于《魔境仙踪》的拍摄很多场景是需要非常仔细的数字化制作，所以需要高度重视，它们在故事板中
的表现形式也就显得尤为重要。

由于这一原因，大多数电影都是绘制了故事板的。

大卫：一般来说，整部电影人们总最想看的是高潮或者其他亮点。

即使是大制作电影，故事板都是从最困难和最复杂的场景开始，然后从那里扩展开来的。

通常所有电影都被拉伸或压缩（pre vizzed），并且这种情况并不少见。

Dave Lowery的《魔境仙踪》故事板。