grlib说明文档中文版
rtklib中文说明(部分)

RTKLIB provide the following general purpose C‐functions callable from user AP (application program).User can use these function to develop user original positioning APs.(1) Matrix and vector functions 矩阵与向量函数(2) Time and string functions 时间和字符串函数(3) Coordinates transformation and geoid model坐标变换和大地水准面模型(4) Navigation processing 导航处理(5) Positioning models (troposphere, ionosphere, antenna PCV) 定位模型(对流层,电离层,天线PCV)(6) SBAS DGPS/DGNSS correction DGPS / SBAS DGNSS校正(7) Single point positioning 单点定位(8) Carrier‐based and code‐based relative positioning 基于载波‐和代码‐基础相对定位(9) OTF integer ambiguity resolution OTF求解整周模糊度(10) Receiver raw binary data input 接收原始二进制数据输入(11) Positioning solution/NMEA input/output输入/输出的NMEA /定位解决方案(12) RINEX observation data/navigation message input/output RINEX观测数据和导航信息的输入/输出(13) Precise ephemeris input 精密星历的输入(14) Stream data communication library流数据通信库(15) NTRIP (Networked Transport of RTCM via Internet Protocol) library NTRIP(网络传输协议通过Internet协议)库(16) RTK‐GPS/GNSS positioning server rtk‐gps / GNSS定位服务器(17) RTCM 2.3 and 3.0/3.1/3.2 message handling RTCM 2.3和3 / 3.1 / 3.2信息处理(18) Downloader functions 下载功能The following instructions shows the way to utilize the library of RTKLIB in user AP.下面的说明显示在用户rtklib AP利用库的方式(1)Add the following include directive to the source program of user AP.#include "rtklib.h"(2)Set the following compiler option to add RTKLIB source directory path to compiler include paths.-I rtklib_<ver>\src(3)Add the necessary RTKLIB library source files to source programs set for the AP build. Refer AppendixC Library APIs for the library function list and source programs provided by RTKLIB.Appendix A CUI Command ReferencesA.1 RTKRCVSYNOPSIS 简介rtkrcv [-s][-p port|-d dev][-o file][-t level]DESCRIPTIONA command line version of the real‐time positioning AP by RTKLIB. To start or stop RTK server, toconfigure options or to print solution/status, login a console and input commands. As default, stdin/stdoutare used for the console. Use ‐p option for network login with telnet protocol. To show the availablecommands, type ?or help on the console. The initial processing options are loaded from defaultconfiguration file rtkrcv.conf. To change the file, use ‐o option. To configure the processing options, editthe configuration file or use set, load or save command on the console. To shutdown the program, useshutdown command on the console or send the USR2 signal to the process. For configuration file, refer B.4.通过rtklib的实时‐时间定位命令行版本,启动或停止RTK服务器,配置选项或打印解决方案/状态,登录控制台,输入命令。
RTKLIB中文说明书

1.文件目录结构 \app-- APs构建环境 \bin --可执行二进制APs和windows链接库 \data-- APs样本数据 \doc --文档文件 \lib --库生成环境 \src --RTKLIB库的源程序 \test--测试程序和数据 \util-- 实用程序工具 2.\bin\rtklaunch.exe 应用程序启动器3.RTKNAVI实时定位结算 输入GPS / GNSS接收机原始观测数据,实时进行导航处理。
3.1执行\bin\rtknavi.exe3.2用RTKNAVI进行实时定位必须输入GPS/GNSS接收机原始观测数据和卫星星历,点击I进入输入流对话框 检查设置Rover、Basestation、Correction三个选项的设置,如果设置定位模式,只选择一个,基站和校正并不需要。
流类型可有从以下选项中选择 (a)Serial :串口输入数据 (b)TCP Client :连接到一个TCP服务器,通过TCP连接输入数据 (c)TCP Server :接受一个TCP客户端连接和通过TCP连接的输入数据 (d)NTRIP Client :连接一个NTRIP caster输入数据 (e)File :日志文件中输入数据。
[.conf](f)FTP :通过FTP下载一个文件后输入数据 (g)HTTP :通过(a) HTTP 下载一个文件后输入数据 3.3选择流类型为?Serial?(连续的)点击...按钮设置选项3.4在流类型中如果你选择了SerialTCP Client或者TCP Server作为类型,你可以通过流设置GPS / GNSS接收机启动和关闭命令,设置命令,按下“Cmd?标签下的…按钮。
在?Serial/TCP Commands?对话框中进行设置,可以加载和保存命令3.5流类型中设置类型为?File?可以设置文件输入路径,数据为原始数据,还可以设置时间 3.6设置输出流格式,点击O按钮,弹出 ?Output Streams?对话框,设置类型,3.7类型选择?File?文件路径中的一些关键词将被日期和时间代替,按下按钮可以查看,选择?Swap Intv?输出文件在特定的周期内替换3.8输出一个输入流作为路径日志,点击按钮,弹出 ?Log Streams? 对话框,和 ?Output Streams?对画框一样路径被关键词替换3.9设置完成后,点击Start按钮。
RTKLIB2.4.3中文使用说明书

1.文件目录结构\app-- APs构建环境 \bin --可执行二进制APs和windows链接库 \data-- APs样本数据 \doc --文档文件\lib --库生成环境 \src --RTKLIB库的源程序\test--测试程序和数据 \util-- 实用程序工具2.\bin\rtklaunch.exe 应用程序启动器3.RTKNAVI实时定位结算输入GPS / GNSS接收机原始观测数据,实时进行导航处理。
3.1执行\bin\rtknavi.exe3.2用RTKNAVI进行实时定位必须输入GPS/GNSS接收机原始观测数据和卫星星历,点击I进入输入流对话框检查设置Rover、Basestation、Correction三个选项的设置,如果设置定位模式,只选择一个,基站和校正并不需要。
流类型可有从以下选项中选择(a)Serial :串口输入数据(b)TCP Client :连接到一个TCP服务器,通过TCP连接输入数据(c)TCP Server :接受一个TCP客户端连接和通过TCP连接的输入数据(d)NTRIP Client :连接一个NTRIP caster输入数据(e)File :日志文件中输入数据 。
[.conf](f)FTP :通过FTP下载一个文件后输入数据(g)HTTP :通过(a) HTTP 下载一个文件后输入数据3.3选择流类型为ʺSerialʺ(连续的)点击...按钮设置选项3.4在流类型中如果你选择了SerialTCP Client或者TCP Server作为类型,你可以通过流设置GPS / GNSS接收机启动和关闭命令,设置命令,按下“Cmdʺ标签下的…按钮。
在ʺSerial/TCP Commandsʺ对话框中进行设置,可以加载和保存命令3.5流类型中设置类型为ʺFileʺ可以设置文件输入路径,数据为原始数据,还可以设置时间3.6设置输出流格式,点击O按钮,弹出 ʺOutput Streamsʺ对话框,设置类型,3.7类型选择ʺFileʺ文件路径中的一些关键词将被日期和时间代替,按下按钮可以查看,选择ʺSwap Intvʺ输出文件在特定的周期内替换3.8输出一个输入流作为路径日志,点击按钮,弹出 ʺLog Streamsʺ 对话框,和 ʺOutput Streamsʺ对画框一样路径被关键词替换3.9设置完成后,点击Start按钮。
MATLAB克里格工具箱中文翻译版

MATLAB克里格工具箱(4.0版:2001年7月)翻译:阿童木看星星伊夫格拉顿等加拉弗勒克里格工具箱是分布式的自由和技术支持。
规格克里格工具箱4.0版MATLAB 6.1兼容。
这是一个2.0版本的升级,已matlab下实现4.2编译,编译matlab下实现5.1和3.0版本。
请注意,此升级只使用2 - D矩阵,即使新的MATLAB版本支持更大的矩阵维数。
优化功能要求的Matlab优化工具箱。
然而,站在替代自我功能还提供了人,谁没有购买优化工具箱(参见“fitvario.m”)。
志工具箱正常的研究是必要的。
它是提供与克里格工具箱。
说明此工具箱的发展是基于使用2个或3个标量的客观分析的必要性在物理海洋学的尺寸。
这种类型的插值通常比标准更好的结果插值方法。
此外,它的不可忽略的优势,使插值误差的估计。
这个工具箱的功能几乎完全是从书Deutsch和Journel(1992)和Marcotte论文(1991)。
变差函数的功能是墨西哥文件编制前,而协同克里格法的功能发表后,在Matlab格式,在1991年Marcotte的论文。
所有的参数和例子可以发现,在英国,在该两本刊物。
Journel和Huijbregts(1992)的书是最好的书semivariograms。
一个完整的例子在物理海洋学的最优估计可以登曼和弗里兰(1985)发现的文件。
同时,kridemo显示2 - D目标的轮廓分析。
登曼,吉隆坡和HJ斐然,1985年。
相关秤,客观的测绘和统计检验Geostrophy超过大陆架。
研究月RES,43:517-539。
德语,C. V和AG Journel,1992年GSLIB:地统计的软件库和用户指南。
牛津牛津大学出版社,340页。
Journel,AG和Huijbregts终审法院首席法官,1992年,矿业统计学。
学术出版社,纽约,600页。
Marcotte,D. 1991。
Cokrigeage与MATLAB。
rtklib中文说明(部分)

The following instructions shows the way to utilize the library of RTKLIB in user AP.下面的说明显示在用户rtklib AP利用库的方式(1)Add the following include directive to the source program of user AP.(2)#include ""(3)Set the following compiler option to add RTKLIB source directory path to compiler include paths.(4)-I rtklib_<ver>\src(5)Add the necessary RTKLIB library source files to source programs set for the AP build. Refer Appendix(6)C Library APIs for the library function list and source programs provided by RTKLIB.Appendix A CUI Command ReferencesRTKRCVSYNOPSIS 简介rtkrcv [-s][-p port|-d dev][-o file][-t level]DESCRIPTIONA command line version of the real‐time positioning AP by RTKLIB. To start or stop RTK server, toconfigure options or to print solution/status, login a console and input commands. As default, stdin/stdoutare used for the console. Use ‐p option for network login with telnet protocol. To show the availablecommands, type or help on the console. The initial processing options are loaded from defaultconfiguration file . To change the file, use ‐o option. To configure the processing options, editthe configuration file or use set, load or save command on the console. To shutdown the program, useshutdown command on the console or send the USR2 signal to the process. For configuration file, refer .通过rtklib的实时‐时间定位命令行版本,启动或停止RTK服务器,配置选项或打印解决方案/状态,登录控制台,输入命令。
Swift GRB产品指南说明书

Swift GRB Products GuideSwift GRB Products Guideby:Alex PadgettDavide DonatoLorella AngeliniHEASARCLaboratory for High Energy Astrophysics,NASA/GSFC,Code662,Greenbelt,MD20771Nov20091IntroductionThis document describes the on-line data products for the Swift Gamma Ray Burst Catalog.2Archive Structure and Filenames2.1Directory LayoutA complete GRB products set contains at mostfive sub-directories:•html-All requiredfiles for on-line GRB web pages•images-GIF images from each available instrument•info-FITS information table(see§2.2.4)•lightcurves-FITS light curves and plots for all available instruments•spectra-BAT and XRT spectra and plotsIf there are no archive data for a given GRB(e.g.TDRSS messages only),then there will only be an html directory.2.2File Naming Conventions2.2.1Light Curves and PlotsLight curves in FITS format are generated for each Swift intrument,and various modes of each instrument.Plots of some of these light curves are also produced,as well as plots of combinations of them.The FITS and gif light curve products archived for each GRB have the following general form:GRBNAMETable1:Left two columns:Instrument character codes and their meaning.Right two columns: Instrument mode character codes and their meaningCharacter Code MeaningXRT Only XRT PC modeBAT Only XRT WT modeUVOT Only XRT WT/PC modeMixed Instruments XRT and BATBAT Pre-Pre-slew EpochBAT Pre-slew EpochBAT In-slew EpochBAT After-slew EpochBAT All Available EpochsUVOT(allfilters)Table2:Energy band character codesCharacter Code Meaning15-350keV Allfilterse10.3-2keV-15-150keV-lc.gif’.Note that not all light curves have a corresponding plot(in fact,most will not), and some gifs are combinations of different light curves.2.2.2Spectra and Spectral PlotsIn addition to light curves,there are spectra and related plots produced for the BAT and XRT. These are named in a similar manner:GRBNAMEph.gif’in place of ’.pha’.Table3:Data type character codesCharacter Code MeaningcnfarmE(if extant),TIMEDEL,and FRACEXP columns are valid for all curves in thefile.∗∗Magnitude only applies to UVOT light curves and plots and Fitted light curve only applies to XRT light curve plots.Table4:Image Plot Character CodesCharacter Code Meaningi1i2i3[I][MM][BB][OO][TT][a-z?].gifwhere GRBNAME,I,MM,BB and OO are identical to§2.2.1.TT is the type of image as shown in Table4.A trailing character from a through z indicates that a mosaic image was split into multiple images.Table5:GRB HTML pagesMain interface html pagegrb051221a BAT and XRT spectra html pagegrb051221a Light curves html pagegrb051221a Images html page2.2.4Information FITS FileIn addition to the data products above,there will also be an information table for each GRB.This table will have at most four extensions-’XRTINFO’,’XRTFLDREG’,’XRTFITINFO’and’BATINFO’. This table will be named:GRBNAMETable6:XRT Only FITS Productsxpcetsra.lcgrb051221a XRT WT0.3-10keV source light curvesxpce1sra.lcgrb051221a XRT WT0.3-2keV source light curvesxpce2sra.lcgrb051221a XRT WT2-10keV source light curvesxpcetsrrb.lcxwtetsrrb.lcxpcetsr.phaxpcetbg.phaxpcet.arfgrb051221a XRT PC total source spectrum(excludingflares) grb051221a XRT PC total background spectrumgrb051221a XRT PC total ancillary responsefilexpcetsrt1.phaxpcetbgt1.phaxpcetsrt1.arfgrb051221a XRT PC time interval2source spectrumgrb051221a XRT PC time interval2background spectrum grb051221a XRT PC time interval2ancillary responsefile xpcetsrt3.phaxpcetbgt3.phaxpcetsrt3.arfxwtetsr.phaxwtetbg.phaxwtetsr.arfgrb051221a XRT WT total source spectrum(excludingflares) grb051221a XRT WT total background spectrumgrb051221a XRT WT total ancillary responsefilexwtetsrt1.phaxwtetbgt1.phaxwtetsrt1.arfgrb051221a XRT WT time interval2source spectrumgrb051221a XRT WT time interval2background spectrum grb051221a XRT WT time interval2ancillary responsefile xwtetsrt3.phaxwtetbgt3.phaxwtetsrt3.arfTable7:XRT Only GIF Productsxpwetsrcb XRT PC/WT0.3-10keV source cal.binned light curve grb051221a lc.gifxpwetsrrb XRT PC/WT0.3-10keV source hardness ratio binned grb051221a lc.gifgrb051221a XRT PC0.3-10keV image mosaicgrb051221a XRT PC0.3-10keV double diagonal imagegrb051221a XRT WT0.3-10keV image mosaicgrb051221a XRT WT0.3-10keV double diagonal imagegrb051221a ph.gifxpwetsrt1XRT PC/WT time interval1source spectrum grb051221a ph.gifxpwetsrt3XRT PC/WT time interval3source spectrumTable8:BAT Only ProductsFilename Description grb051221a BAT15-350keV source net light curvegrb051221a BAT4-channel source net light curvegrb051221a BAT0.3-150keV Multi-bandflux BAT-block light curves bppetsr.phabppetsr.rspbpsetsr.phabpsetsr.rspbisetsr.phabisetsr.rspbasetsr.phabasetsr.rspbbaetsr.phabbaetsr.rspGIF Products bbaetsrn BAT15-350keV source net light curve gifgrb051221a lc.gifgrb051221a ph.gifbppe2src BAT15-150keV Pre-Pre-slew source spectrum(cutoffpower-law) grb051221a ph.gifbpse2src BAT15-150keV Pre-slew source spectrum(cutoffpower-law)grb051221a ph.gifbise2src BAT15-150keV In-slew source spectrum(cutoffpower-law)grb051221a ph.gifbase2src BAT15-150keV After-slew source spectrum(cutoffpower-law) grb051221a ph.gifbbae2src BAT15-150keV Total source spectrum(cutoffpower-law)bbaetsri1.gifTable9:UVOT Only ProductsFilename Descriptiongrb051221a UVOT Allfilter source binned light curvesFilename Descriptiongrb051221a UVOT optical source imagegrb051221a UVOT optical sourcefinding chart imagegrb051221a lc.gifuuvetsrmb UVOT optical source magnitude light curvesTable10:XRT and BAT Combined ProductsFilename Description grb051221a lc.gifmxbe3srfb XRT+BAT2.0-10keV sourceflux binned light curve4Example Plots4.1XRT PlotsFigure1shows the plotted XRT PC and WT mode corrected count rate,flux and hardness ratio light curves for GRB090618.Thisfigure also contains thefitted XRT light curve,which is used to extract andfit spectra from up to three epochs.Figure2shows the extracted andfitted spectra from eachfitted epoch,and the totalfitted spectra.Figure3shows the plotted XRT PC and WT images and image mosaics for GRB090618.4.2BAT PlotsFigures4through7show typical BAT only plots.Figure4shows the BAT light curve plots.Figure 5shows the BAT spectral plots with a power-law modelfit.Figure6shows the same,but with an exponential cutoffmodelfit.And Figure7shows the pre-and post-slew BAT burst images.4.3UVOT PlotsFigure8shows theflux converted light curves for GRB090618,and the magnitude light curves for the same source.Figure9shows the highest signal to noise image from the UVOT,and the UVOT finding chart image for GRB090618.Figure 1:Clockwise from top left:GRB 090618XRT PC and WT mode corrected rate light curves;Flux light curves;Modelled light curve –dashed lines show fitted time breaks;0.3-2.0keV light curves,2-10keV light curves,and hardness ratios.Figure 2:Clockwise from top left:GRB 090618XRT PC and WT mode spectrum from the first time interval (see bottom right panel of Figure 1);Second time interval spectra;Third time interval spectra;Total spectrumFigure3:Clockwise from top left:GRB090618XRT PC double image;Per-segment XRT PC image mosaic;Per-segment XRT WT image mosaic;XRT WT double imageFigure 4:Left:GRB 0906184-channel BAT constant time bin light curves.The energy band of each light curve is in shown in the upper right corner of each panel.Right:GRB 0906181-channel (15-350keV)BAT constant time bin light curve.4.4Combined BAT/XRT PlotsFigure 10shows the combined BAT and XRT flux converted light curve plots for GRB 090618.Figure5:Clockwise from top left:GRB090618BAT pre-slew spectrumfitted with a simple power-law model normalized at50keV.GRB090618BAT slew spectrumfitted with the same model.GRB 090618BAT post-slew spectrumfitted with the same model.GRB090618total BAT spectrum fitted with the same model.Figure6:Clockwise from top left:GRB090618BAT pre-slew spectrumfitted with an exponential cut-offpower-law model normalized at50keV.GRB090618BAT slew spectrumfitted with the same model.GRB090618BAT post-slew spectrumfitted with the same model.GRB090618total BAT spectrumfitted with the same model.Figure7:Left:GRB090618BAT pre-slew image of the GRBfield-of view.Right:GRB090618 BAT post-slew image.Figure8:Left:GRB090618UVOT integratedflux light curves.Right:GRB090618UVOT magnitude light curves.Figure9:Left:GRB090618UVOT highest signal to noise image.Right:GRB090618UVOT finding chart image.Figure10:Left:GRB090618BAT and XRTflux converted light curves in0.3-10keV.Right:GRB 090618BAT and XRTflux converted light curves in2-10keV.。
[LEON_Grlib_Guide1_0325]grlib安装指南_1103修订
![[LEON_Grlib_Guide1_0325]grlib安装指南_1103修订](https://img.taocdn.com/s3/m/0232be4676232f60ddccda38376baf1ffc4fe323.png)
20101012修订 0.120110324修订 0.2GRLIB IP Library User’s ManualGRLIB IP库 用户指导手册(一)安装指南Version 1.0.22CH Reversion 1.0Jiri Gaisler, Sandi Habinc翻译: ****************Copyright Aeroflex Gaisler, 2010目录内容目录1 简介 (3)1.1 综述 (3)1.2 组织结构 (3)1.3 片上总线 (3)2 安装过程 Installation (6)2.1 安装 Installation (6)2.2 文件组织 Directory organization (7)2.3 宿主机平台支持 Host platform support (8)2.3.1 Linux (9)2.3.2 安装了Cygwin的windows (9)2.3.3 (补充)与Windows下ISE配合的折衷安装方法 (9)1简介1.1综述GRLIB IP 库是一个可重用IP核的完整集合,它是为片上系统(SOC)开发打造的。
这些IP核集中于通用的片上总线周边,采用清晰明了的方法进行仿真与综合。
1.2组织结构GRLIB is organized around VHDL libraries, where each major IP (or IP vendor) is assigned a unique library name. Using separate libraries avoids name clashes between IP cores and hides unnecessary implementation details from the end user. Each VHDL library typically contains a number of packages, declaring the exported IP cores and their interface types.Simulation and syn- thesis scripts are created automatically by a global makefile. Adding and removing of libraries and packages can be made without modifying any global files, ensuring that modification of one ven- dor’s library will not affect other vendors. A few global libraries are provided to define shared data structures and utility functions.GRLIB provides automatic script generators for the Modelsim, Ncsim, Aldec, Sonata and GHDL simulators, and the Synopsys, Synplify, Cadence, Mentor, Actel, Altera, Lattice, and Xilinx imple- mentation tools. Support for other CAD tools can be easily be added.1.3片上总线The GRLIB is designed to be ‘bus-centric’, i.e. it is assumed that most of the IP cores will be con- nected through an on-chip bus. The AMBA-2.0 AHB/APB bus has been selected as the common on-chip bus, due to its market dominance (ARM processors) and because it is well documented and can be used for free without license restrictions. The figure below shows an example of a LEON3 system designed with GRLIB1.4Distributed address decodingAdding an IP core to the AHB bus is unfortunately not as straight-forward as just connecting the bus signals. The address decoding of AHB is centralized, and a shared address decoder and bus multiplexer must be modified each time an IP core is added or removed. To avoid dependencies on a global resource, distributed address decoding has been added to the GRLIB cores and AMBA AHB/APB controllers.1.5Interrupt steeringGRLIB provides a unified interrupt handling scheme by adding 32 interrupt signals to the AHB and APB buses. An AMBA module can drive any of the interrupts, and the unit that implements the interrupt controller can monitor the combined interrupt vector and generate the appropriate processor interrupt. In this way, interrupts can be generated regardless of which processor or inter- rupt controller is being used in the system, and does not need to be explicitly routed to a global resource. The scheme allows interrupts to be shared by several cores and resolved by software.1.6Plug&Play capabilityA broad interpretation of the term ‘plug&play’ is the capability to detect the system hardwarecon- figuration through software. Such capability makes it possible to use software application or oper-ating systems which automatically configure themselves to match the underlying hardware. This greatly simplifies the development of software applications, since they do not need to be custom- ized for each particular hardware configuration.In GRLIB, the plug&play information consists of three items: a unique IP core ID, AHB/APB memory mapping, and used interrupt vector. This information is sent as a constant vector to the bus arbiter/decoder, where it is mapped on a small read-only area in the top of the address space.Any AHB master can read the system configuration using standard bus cycles, and a plug&play operating system can be supported.To provide the plug&play information from the AMBA units in a harmonized way, a configuration record for AMBA devices has been defined (figure 1). The configuration record consists of 8 32- bit words, where four contain configuration words defining the core type and interrupt routing, and four contain so called ‘bank address registers’ (BAR), defining the memory mapping.The configuration word for each device includes a vendor ID, device ID, version number, and interrupt routing information. A configuration type indicator is provided to allow for future evolve-ment of the configuration word. The BARs contain the start address for an area allocated to the device, a mask defining the size of the area, information whether the area is cacheable or pre-fetch- able, and a type declaration identifying the area as an AHB memory bank, AHB I/O bank or APB I/O bank. The configuration record can contain up to four BARs and the core can thus be mapped on up to four distinct address areas.2安装过程 Installation2.1安装 Installation(本系统安装过程演示在RedHat Linux中进行,其他*nix和cygwin等环境应大体相同)GRLIB is distributed as a gzipped tar-file and can be installed in any location on the host system: GRLIB 是以gzip压缩格式发布的,可以在宿主机的任意位置发布。
Fragstats4.1帮助文档中文版(谷歌翻译)

概述什么是FRAGSTATSFRAGSTATS是空间格局的分析程序来表示景观结构的景观镶嵌模型分类地图。
请注意,FRAGSTATS不适合代表景观结构的景观梯度模型的连续表面地图。
景观受分析是用户定义的,并且可以表示任何空间的现象。
FRAGSTATS简单量化作为分类地图所代表的景观空间异质性;这是义不容辞的用户建立了良好的基础定义和缩放景观的主题内容和分辨率和空间的粮食和程度方面。
我们强烈建议您阅读使用该程序之前,FRAGSTATS背景部分。
重要的是,从FRAGSTATS输出才有意义,如果定义的景观是有意义的相对于正在审议的现象。
规模的注意事项FRAGSTATS需要的空间谷物或网格的分辨率是>0.001米,但它放置没有限制对景观本身的空间范围,虽然有对可加载的网格的尺寸存储器的限制。
然而,在计算FRAGSTATS的移动距离和面积为基础的度量报道平方米,公顷,分别。
因此,极端的程度和/或分辨率的景观可导致相当麻烦的数字和/或受舍入误差。
然而,FRAGSTATS输出,可以使用任何数据库管理程序,以重新调整指标或将其转换为其他单位(例如,转换公顷亩)被操纵以ASCII格式的数据文件。
计算机要求FRAGSTATS是一个用微软的Visual C单机+ +程序在Windows操作系统环境中使用,是一个32位进程(即使运行的是64位计算机上)。
FRAGSTATS的开发和在Windows 7操作系统上进行测试,尽管它应该在所有的Windows操作系统上运行。
请注意,FRAGSTATS是高度依赖于平台,因为它是在Microscroft环境下开发的,所以移植到其他平台上是不容易实现的。
FRAGSTATS是计算密集型的程序;其性能取决于两个处理器速度和计算机存储器(RAM)。
最后,处理的图像的能力依赖于足够的存储器可用,并且处理该图像的速度依赖于处理器速度。
特别值得注意的是该存储器的约束。
FRAGSTATS是一个32位的过程,因此,最多只能使用2GB的内存;但如果正确配置Windows可以让32位进程看高达3GB的内存。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
5GRLIB design concept5.1introductionGRLIB是一个可重用IP Core的集合,并分成了多个VHDL库。
每一个库提供了特定厂商的元件或者一系列共享的功能或接口。
在GRLIB设计中使用的数据结构和元件声明都是通过库指定的VHDL包来输出的。
GRLIB是基于AMBA AHB和APB片上总线的,并把该总线用作标准的互联接口。
AHB/APB总线的实现是与AMBA-2.0相兼容的,并附加了额外的“sideband”(边带)信号。
这些边带信号的有三个用途:automatic address decoding,interrupt steering和device identification(a.k.a plug&play support)。
根据AHB/APB 信号的功能,GRLIB的库把这些信号以VHDL records的形式组合在一起。
GRLIB AMBA包的源文件在lib/grlib/amba/下。
所有的GRLIB core都使用同样的data structures来声明AMBA接口,这样相互之间的连接就很容易了。
GRLIB库还包含了一个AHB bus controller和一个AHB/APB bridge,借助这两个模块,可以很快组装成一个全功能的AHB/APB的系统。
下面的部分将描述AMBA总线是怎么实现的以及怎样用GRLIB来建一个SOC设计。
5.2AMAB AHB on-chip bus5.2.1General(概述)AMBA Advanced High-performance Bus(AHB)是一个multi-master的总线,可以以high data rate and/or variable latency的形式来互连各单元。
图5就是一个概念图。
图中连在总线上的单元分为masters(主)和slaves(客),并都受一个全局的总线仲裁器(global bus arbiter)控制。
由于AHB总线是复用的(而不是三态的),更正确的总线与单元互连示图可以参考图6。
每一个master驱动了一系列以VHDL record形式的组合在一起的信号HMSTO。
当前总线master的输出record被总线复用器选中并被送到所有AHB slaves的input record(ahbsi)。
被激活的slave的output record(ahbso)被总线复用器(bus multiplexer)选中并输出到所有的masters。
一个组合的bus arbiter,address decoder and bus multiplexer 控制着哪个master和slave会被选中。
5.2.2AHB master interfaceAHB master的inputs、outputs都定义成VHDL record type形式,都以GRLIB AMBA库中TYPES package 的形式输出:--AHB master inputsType ahb_mst_in_type is recordhgrant:std_logic_vector(0to NAHBMST-1);--bus granthready:std_ulogic;--transfer donehresp:std_logic_vector(1downto0);--response typehrdata:std_logic_vector(31downto0);--read data bushcache:std_ulogic;--cacheablehirq:std_logic_vector(NABIRQ-1downto0);--interrupt result busend record;--AHB master outputstype ahb_mst_out_type is recordhbusreq:std_ulogic;--bus requesthlock:std_ulogic;--lock requesthtrans:std_logic_vector(1downto0);--transfer typehaddr:std_logic_vector(31downto0);--address bus(byte)hwrite:std_ulogic;--read/writehsize:std_logic_vector(2downto0);--transfer sizehburst:std_logic_vector(2downto0);--burst typehprot:std_logic_vector(3downto0);--protection controlhwdata:std_logic_vector(31downto0);--write data bushirq:std_logic_vector(NAHBIRQ-1downto0);--interrupt bushconfig:ahb_config_type;--memory access reg.hindex:integer range0to NAHBMST-1;--diagnostic use onlyend record;record type中的信号与AMBA2.0规范中AHB master的相应信号一致,但附加了四个边带信号:HCACHE,HIRQ,HCONFIG,HINDEX。
GRLIB中一个典型的AHB master定义如下:library grlib;use grlib.amba.all;library ieee;use ieee.std_logic.all;entity ahbmaster isgeneric(hindex:integer:=0);--master bus indexport(reset:in std_ulogic;clk:in std_ulogic;hmsti:in ahb_mst_in_type;--AHB master inputshmsto:out ahb_mst_out_type--AHB master outputs);end entity;输入record(HMSTI)接到各masters,当中包括对全部masters的bus grant(总线允许)信号HMSTI.HGRANT。
因此,一个AHB master必须使用一个generic(常量)来指定具体的哪一根HGRANT是要用的。
这个generic 的type是integer,通常叫作HINDEX(参见上面的例子)。
5.2.3AHB slave interface与AHB master的接口类似,AHB slaves的inputs和outputs也是定义成两个VHDL的records types: --AHB slave inputstype ahb_slv_in_type is recordhsel:std_logic_vector(0to NAHBSLV-1);--slave selecthaddr:std_logic_vector(31downto0);--address bus(byte)hwrite:std_ulogic;--read/writehtrans:std_logic_vector(1downto0);--transfer typehsize:std_logic_vector(2downto0);--transfer sizehburst:std_logic_vector(2downto0);--burst typehwdata:std_logic_vector(31downto0);--write data bushprot:std_logic_vector(3downto0);--protection controlhready:std_ulogic;--transfer donehmaster:std_logic_vector(3downto0);--current masterhmastlock:std_ulogic;--locked accesshbsel:std_logic_vector(0to NAHBCFG-1);--bank selecthcache:std_ulogic;--cacheablehirq:std_logic_vector(NAHBIRQ-1downto0);--interrupt result busend record;--AHB slave outputstype ahb_slv_out_type is recordhready:std_ulogic;--transfer donehresp:std_logic_vector(1downto0);--response typehrdata:std_logic_vector(31downto0);--read data bushsplit:std_logic_vector(15downto0);--split completionhcache:std_ulogic;--cacheablehirq:std_logic_vector(NAHBIRQ-1downto0);--interrupt bushconfig:ahb_config_type;--memory access reg.hindex:integer range0to NAHBSLV-1;--diagnostic use onlyend record;上面record中的信号与AMBA2.0规范中AHB slaves中对应的信号是一致的,额外附加了五个边带信号:HBSEL,HCACHE,HIRQ,HCONFIG,HINDEX。
GRLIB中典型的AHB slave定义如下:library grlib;use grlib.amba.all;library ieee;use ieee.std_logic.all;entity ahbslave isgeneric(hindex:integer:=0);--slave bus indexport(reset:in std_ulogic;clk:in std_ulogic;hslvi:in ahb_slv_in_type;--AHB slave inputshslvo:out ahb_slv_out_type--AHB slave outputs);end entity;input record(ahbsi)接到所有slaves,其中包括对所有slaves的选择信号ahbsi.hsel。
因此一个AHB slave必须使用一个generic(常量)来指定具体哪一个hsel是需要使用的。