File Naming Convention
文件管理制度英文
文件管理制度英文1. PurposeThe purpose of this File Management Policy is to establish guidelines for the proper creation, management, storage, and retention of electronic and physical files within the organization. This policy aims to ensure that all files are organized, secure, and easily accessible to authorized individuals.2. ScopeThis policy applies to all employees, contractors, and third-party vendors who create, manage, or access files on behalf of the organization. It covers electronic files stored on servers, databases, and other digital platforms, as well as physical files kept in office spaces or off-site storage facilities.3. File Creation and Naming ConventionAll employees are responsible for creating and naming files in a consistent and descriptive manner. File names should accurately reflect the content of the file, making it easy for users to search for and identify the information they need. File names should not contain special characters, lengthy abbreviations, or spaces.4. File Organization and StructureIt is important to organize files in a logical and consistent manner to facilitate efficient retrieval and sharing of information. Employees should adhere to a standardized file structure, with clearly defined folders and subfolders for various departments, projects, or categories. The use of meaningful folder names and hierarchical organization helps to minimize confusion and duplication of files.5. Access Control and PermissionsAccess to electronic files should be restricted to authorized individuals based on their role and responsibilities within the organization. File permissions should be set to limit the ability to view, modify, or delete files to only those who have a legitimate business need. Regular reviews of user access rights should be conducted to ensure that unauthorized access is prevented.6. File Storage and BackupAll electronic files should be stored on secure, centralized servers or cloud-based platforms that are regularly backed up to prevent data loss. Employees should refrain from storing files on local hard drives or personal devices to minimize the risk of unauthorized access or loss of data. Regular backups should be scheduled to ensure that all files are protected in the event of a system failure or security breach.7. File Retention and DisposalThe organization is required to maintain records of its activities in accordance with legal and regulatory requirements. Employees should adhere to the organization's record retention policy and schedule, which stipulates the minimum and maximum retention periods for various types of files. Files that have exceeded their retention period should be securely destroyed to prevent unauthorized access and comply with data protection regulations.8. File Security and EncryptionConfidential and sensitive files should be encrypted to prevent unauthorized access or disclosure of sensitive information. Employees should be trained on the proper handling and storage of sensitive files, including the use of encryption tools and secure transfer methods. Access to sensitive files should be restricted to authorized individuals and monitored for suspicious activities.9. File Sharing and CollaborationEmployees may need to share and collaborate on files with internal or external parties. When sharing files, employees should use secure methods such as encrypted email attachments or secure file-sharing platforms. Employees should refrain from using personal email accounts or unsecured platforms to share sensitive information to prevent data breaches and unauthorized access.10. Compliance and MonitoringThe organization's IT department is responsible for establishing and monitoring compliance with this File Management Policy. Regular audits and assessments should be conducted to ensure that employees are following the guidelines outlined in this policy. Non-compliance with this policy may result in disciplinary actions and revocation of access privileges.11. Training and AwarenessAll employees should receive training on the organization's File Management Policy upon their onboarding and periodically thereafter. Training should cover the proper creation, management, and storage of files, as well as the importance of data security and confidentiality. Employees should be made aware of their responsibilities in adhering to this policy to protect the organization's information assets.ConclusionEffective file management is essential for maintaining the integrity, security, and accessibility of an organization's information assets. This File Management Policy provides clear guidelines for employees on the proper creation, organization, storage, and disposal of electronic and physical files. By following these guidelines, the organization can minimizethe risk of data loss, unauthorized access, and non-compliance with legal and regulatory requirements.。
一、导出文件教程
从3DMAX中导出文件Gamebryo 3ds max导出选项（ Gamebryo 3ds max Export Options）你可以在3DMAX的导出选项中选择格式来导出你的场景文件。
一旦输入了要保存的文件名后，将出现下列对话框。
你所做的导出设置将在MAX文件保存时一同保存下来。
这些选项作为额外数据被保存在Max scene-graph的根节点下。
这个功能有助于以后的文件导出都使用同样的设置。
Max文件在导出过程中不会自动保存，因此需要在导出后再次保存Max文件以保存导出选项。
1、灯光及摄像机导出子面板（Export Options Sub-panel）：摄像机(Cameras):如需导出摄像机，勾选此项。
灯光(Lights)：如需导出灯光，勾选此项。
注意：如果你在场景中没有创建任何灯光，3DMAX将自动创建2盏方向灯(directional light)以及1盏环境灯（ambient light）。
Gamebryo 导出的Max Ambient light 的详细参数可在Rendering–>Environment–>Global Lighting options中调节（如果你不希望场景中有额外的环境灯，你可以将环境色设置为0，0，0。
此时环境灯将不被导出。
或者取消前的勾选，也可以达到同样的目的。
）2、贴图导出子面板（Textures Options Sub-panel）：贴图：贴图可以在主群NIF格式、分离NIFs格式及其他原有的格式中导出。
请参照贴图导出说明文档（documentation on Exporting Textures）以比较各种方式的优缺点。
附注：贴图导出说明文档（documentation on Exporting Textures）贴图导出（Exporting Textures）：贴图可以在主要的NIF格式、特殊的NIFs格式及原始格式中导出。
这些选项可以在Export dialog或者单独在Texture Conversion Custom Attributes中设置。
化学行业免费的谱图数据库18个
化学专业免费的谱图数据库18个1、【名称】ChemExper化学品目录CDD (包括MSDS、5000张红外谱图）【资源简介】The database contains currently more than 70 000 chemicals, 16000 MSDS, 5000 IR spectra and more than 20 suppliers. It is the only chemical database that lets you SUBMIT your own data! 【检索途径】You can find a chemical by its molecular formula, IUPAC name, common name, CAS number, catalog number, substructure or physical characteristics【地址】http://www.chemexper.be/【名称】 (NMR谱图数据库及NMR谱图预测)【资源简介】This is a web-based approach implementing a new java applet that enables to assign a chemical structure to the corresponding NMR spectrum by simply drawing lines between atoms and automatically characterized signals.This NMR predictor allows to predict the spectrum from the chemical structure based on Spinus (Structure-based Predictions In NUclear magnetic resonance Spectroscopy), which is an on-going project for the development of structure-based tools for fast prediction of NMR spectra developed by Gasteiger (http://www2.chemie.uni-erlangen.de/services/spinus/index.html). SPINUS - WEB currently accepts molecular structures via a Java molecular editor, and estimates 1H NMR chemical shifts.【地址】/2、【名称】BioMagResBank (BMRB): 多肽、蛋白质、核酸等的核磁共振数据存储库【资源简介】IntroductionBioMagResBank (BMRB) is the publicly-accessible depository for NMR results from peptides, proteins, and nucleic acids recognized by the International Society of Magnetic Resonance and by the IUPAC-IUBMB-IUPAB Inter-Union Task Group on the Standardization of Data Bases of Protein and Nucleic Acid Structures Determined by NMR Spectroscopy. In addition, BMRB provides reference information and maintains a collection of NMR pulse sequences and computer software for biomolecular NMR. Access to data in BMRB is free directly from its web site (URL ) and ftp site () and will remain so as public funding permits. The concept of a biomolecular NMR data bank developed under a five-year research grant awarded to the University of Wisconsin-Madison from the National Library of Medicine, National Institutes of Health. This grant was phased out after that period, and a Request for Applications was issued by the NIH for future support of this activity. BMRB at t he University of Wisconsin-Madison won this competition, has been supported since 1 September 1996 by the National Library of Medicine, NIH under grant 1 P41 LM05799. The current award for five years expires on 31 August 2004.AimsIn collaboration with the Protein Data Bank (PDB, Brookhaven National Laboratories) and Nucleic Acid Data Bank (NDB, Rutgers University), BMRB aims to develop into the collection site for structural NMR data in proteins and nucleic acids. Steps are being taken at BMRB to achieve this capability, which will include transmission of all relevant data to the PDB and NDB collections. In addition, BMRB has the goal of archiving NMR-specific data including assigned chemical shifts, J-couplings, relaxation rates, and chemical information derived from NMR investigations (for example, hydrogen exchange rates and pKa values). In developing these collections BMRB intends to be responsive to the needs and priorities of the scientific community. The operating policy at BMRB is monitored and shaped by its Advisory Board which meets once each year to review progress and set priorities. The Advisory Board is composed ofrepresentatives from laboratories that originate and/or use data within the BMRB p urview.【地址】/3、【名称】NIST Chemistry WebBook【资源简介】The November 1998 release of The NIST WebBook is the fifth edition of the NIST Chemistry WebBook. It contains thermochemical data for over 5000 organic and small inorganic compounds, reaction thermochemistry data for over 8000 reactions, IR spectra for over 5000 compounds, mass spectra for over 10,000 compounds, electronic / vibrational spectra for over 3000 compounds, constants ofdiatomic molecules (spectroscopic data) for over 600 compounds, Ion energetics data for over 14,000 compounds, and thermophysical property data for 16 fluids There are many avenues for searching the database. Structures are given for most species, as well as common and commercial names.【检索途径】Formula NamePartial formulaCAS registry numberStructure basedIon energeticsVibrational and electronic spectraMolecular weightAuthor【地址】/chemistry4、【名称】粉末衍射模式数据库PowBase (Powder Patterns Database)【资源简介】PowBase is a "minimum database" of constant wavelength powder patterns. The data files (zipped) contain either a CIF file or a .dat file (the latter can be viewed by WinPLOTR, option INSTRM=0).The search output produces entry numbers with hyperlink to the raw data (zipped files), the formula, wavelength, a comment, and a reference with email address. Some pertinent hyperlinks may be added, and also a VRML 3D view, sometimes.【地址】http://sdpd.univ-lemans.fr/powbase/5、【名称】上海有机化学所:化学数据库【资源简介】上海有机化学研究所的化学专业数据库由多个数据库组成，注册后可免费使用。
RINEX格式
RINEX格式RINEX是The Receiver Independent Exchange Format（与接收机无关的数据交换格式）的缩写，它是GPS测量领域中的一种广为使用的数据格式，绝大部分的数据处理软件均支持这种格式。
下面是一份有关该格式的文挡：RINEX: The Receiver Independent Exchange Format Version 2*********************************************************(Revision, April 1993)(Clarification December 1993)(Doppler Definition: January 1994)(PR Clarification: October 1994)(Wlfact Clarification: February 1995)(Event Time Frame Clarification: May 1996)(Minor errors in the examples A7/A8: May 1996)(Naming convention for compressed met files; January 1997)(Continuation line clarifications: April 1997)(GLONASS Extensions: April 1997)(Met sensor description and position records: April 1997)(Wavelength factor clarifications: April 1997)Werner GurtnerAstronomical InstituteUniversity of Berne0. INTRODUCTION0.1 First RevisionThis paper is a revised version of the one published by W. Gurtner and G.Mader in the CSTG GPS Bulletin of September/October 1990. The main reasonfor a revision is the new treatment of antispoofing data by the RINEXformat (see chapter 7). Chapter 4 gives a recommendation for data compression procedures, especially useful when large amounts of data are exchanged through computer networks. In Table A3 in the original paper the definiton of the "PGM / RUN BY / DATE" navigation header record was missing, although the example showed it. The redefinition of AODE/AODC to IODE/IODC also asks for an update of the format description. For consistency reasons we also defined a Version 2 format for the Meteorological Data files(inclusion of a END OF HEADER record and an optional MARKER NUMBER record).* The slight modification (or rather the definition of a bit in the Loss ** of Lock Indicator unused so far) to flag AS data is so small a change ** that we decided to NOT increase the version number! *0.2 Later Revisions:* URA Clarification (10-Dec-93):The user range accuracy in the Navigation Message File did not contain a definition of the units: There existed two ways of interpretation:Either the 4 bit value from the original message or the converted value in meters according to GPS ICD-200. In order to simplify the interpretation for the user of the RINEX files I propose the bits to be converted into meters prior to RINEX file creation.* GLONASS Extensions:In March 1997 a proposal for extensions to the current RINEX definitions based on experiences collected with GLONASS only and mixed GPS/GLONASS data files was circulated among several instrument manufacturers and software developers.The results of the call for comments have been worked into this document.A separate document (glonass.txt) summarizes just the necessary extensions.* A blank satellite identifier is allowed in pure GPS files only* Met sensor description and position records were added to facilitate the precise use of met values.* Description and examples for wavelength factors and their temporary changes(bit 1 of LLI) clarified.In order to have all the available information about RINEX in one place we also included parts of earlier papers and a complete set of format definiton tables and examples.1. THE PHILOSOPHY OF RINEXThe first proposal for the "Receiver Independent Exchange Format" RINEX has been developed by the Astronomical Institute of the University of Berne for the easy exchange of the GPS data to be collected during the large European GPS campaign EUREF 89, which involved more than 60 GPS receivers of 4 different manufacturers. The governing aspect during the development was the following fact:Most geodetic processing software for GPS data use a well-defined set of observables:- the carrier-phase measurement at one or both carriers (actually being a measurement on the beat frequency between the received carrier of the satellite signal and a receiver-generated reference frequency).- the pseudorange (code) measurement, equivalent to the difference of the time of reception (expressed in the time frame of the receiver) and the time of transmission (expressed in the time frame of the satellite) of a distinct satellite signal.- the observation time being the reading of the receiver clock at the instant of validity of the carrier-phase and/or the code measurements.Usually the software assumes that the observation time is valid for both the phase AND the code measurements, AND for all satellites observed.Consequently all these programs do not need most of the information that is usually stored by the receivers: They need phase, code, and time in the above mentioned definitions, and some station-related information like station name, antenna height, etc.2. GENERAL FORMAT DESCRIPTIONCurrently the format consists of four ASCII file types:1. Observation Data File2. Navigation Message File3. Meteorological Data File4. GLONASS Navigation Message FileEach file type consists of a header section and a data section. The header section contains global information for the entire file and is placed at the beginning of the file. The header section contains header labels in columns 61-80 for each line contained in the header section. These labels are mandatory and must appear exactly as given in these descriptions and examples.The format has been optimized for mimimum space requirements independent from the number of different observation types of a specific receiver by indicating in the header the types of observations to be stored. In computer systems allowing variable record lengths the observation records may then be kept as short as possible. The maximum record length is 80 bytes per record.Each Observation file and each Meteorological Data file basically contain the data from one site and one session. RINEX Version 2 also allows to include observation data from more than one site subsequently occupied by a roving receiver in rapid static or kinematic applications.If data from more than one receiver has to be exchanged it would not be economical to include the identical satellite messages collected by the different receivers several times. Therefore the Navigation Message File from one receiver may be exchanged or a composite Navigation MessageFile created containing non-redundant information from several receivers in order to make the most complete file.The format of the data records of the RINEX Version 1 Navigation Message file is identical to the former NGS exchange format.The actual format descriptions as well as examples are given in the Tables at the end of the paper.3. DEFINITION OF THE OBSERVABLESGPS observables include three fundamental quantities that need to be defined: Time, Phase, and Range.TIME:The time of the measurement is the receiver time of the received signals. It is identical for the phase and range measurements and is identical for all satellites observed at that epoch. It is expressed in GPS time (not Universal Time).PSEUDO-RANGE:The pseudo-range (PR) is the distance from the receiver antenna to the satellite antenna including receiver and satellite clock offsets (and other biases, such as atmospheric delays):PR = distance + c * (receiver clock offset - satellite clock offset + other biases)so that the pseudo-range reflects the actual behavior of the receiver and satellite clocks. The pseudo-range is stored in units of meters.See also clarifications for pseudoranges in mixed GPS/GLONASS files in chapter 8.1.PHASE:The phase is the carrier-phase measured in whole cycles at both L1 and L2. The half-cycles measured by sqaring-type receivers must be converted to whole cycles and flagged by the wavelength factor in the header section.The phase changes in the same sense as the range (negative doppler). The phase observations between epochs must be connected by including the integer number of cycles. The phase observations will not contain any systematic drifts from intentional offsets of the reference oscillators.The observables are not corrected for external effects like atmospheric refraction, satellite clock offsets, etc.If the receiver or the converter software adjusts the measurements using the real-time-derived receiver clock offsets dT(r), the consistency of the 3 quantities phase / pseudo-range / epoch must be maintained, i.e. the receiver clock correction should be applied to all 3 observables:Time(corr) = Time(r) - dT(r)PR(corr) = PR(r) - dT(r)*cphase(corr) = phase(r) - dT(r)*freqDOPPLER:The sign of the doppler shift as additional observable is defined as usual:Positive for approaching satellites.4. THE EXCHANGE OF RINEX FILES:We recommend using the following naming convention for RINEX files:ssssdddf.yyt ssss: 4-character station name designatorddd: day of the year of first recordf: file sequence number within day0: file contains all the existingdata of the current dayyy: yeart: file type:O: Observation fileN: Navigation fileM: Meteorological data fileG: GLONASS Navigation fileTo exchange RINEX files on magnetic tapes we recommend using the following tape format:- Non-label; ASCII; fixed record length: 80 characters;block size: 8000- First file on tape contains list of files using above-mentioned naming conventionsWhen data transmission times or storage volumes are critical we recommend compressing the files prior to storage or transmission using the UNIX "compress" und "uncompress" programs. Compatible routines are available on VAX/VMS and PC/DOS systems, as well.Proposed naming conventions for the compressed files:System Obs files GPS Nav Files GLONASS Nav Files Met FilesUNIX ssssdddf.yyO.Z ssssdddf.yyN.Z ssssdddf.yyG.Z ssssdddf.yyM.ZVMS ssssdddf.yyO_Z ssssdddf.yyN_Z ssssdddf.yyG_Z ssssdddf.yyN_ZDOS ssssdddf.yyY ssssdddf.yyX ssssdddf.yyV ssssdddf.yyW5. RINEX VERSION 2 FEATURESThe following section contains features that have been introduced for RINEX Version 2.5.1 Satellite Numbers:Version 2 has been prepared to contain GLONASS or other satellite systems' observations. Therefore we have to be able to distinguish the satellites of the different systems: We precede the 2-digit satellite number with a system identifier.snn s: satellite system identifierG or blank : GPSR : GLONASST : Transitnn :PRN (GPS), almanac number (GLONASS) or two-digit Transit satellite numberNote: G is mandatory in mixed GPS/GLONASS files(blank default modified in April 1997)5.2 Order of the Header Records:As the record descriptors in columns 61-80 are mandatory, the programs reading a RINEX Version 2 header are able to decode the header records with formats according to the record descriptor, provided the records have been first read into an internal buffer.We therefore propose to allow free ordering of the header records, with the following exceptions:- The "RINEX VERSION / TYPE" record must be the first record in a file- The default "WAVELENGTH FACT L1/2" record (if present) should precede all records defining wavelength factors for individual satellites- The "# OF SATELLITES" record (if present) should be immediately followed by the corresponding number of "PRN / # OF OBS" records. (These records may be handy for documentary purposes. However, since they may only be created after having read the whole raw data file we define them to be optional.5.3 Missing Items, Duration of the Validity of ValuesItems that are not known at the file creation time can be set to zero or blank or the respectiverecord may be completely omitted. Consequently items of missing header records will be set to zero or blank by the program reading RINEX files. Each value remains valid until changed by an additional header record.5.4. Event Flag RecordsThe "number of satellites" also corresponds to the number of records of the same epoch followed. Therefore it may be used to skip the appropriate number of records if certain event flags are not to be evaluated in detail.5.5 Receiver Clock OffsetA large number of users asked to optionally include a receiver-derived clock offset into the RINEX format. In order to prevent confusion and redundancy, the receiver clock offset (if present) should report the value that has been used to correct the observables according to the formulae under item 1. It would then be possible to reconstruct the original observations if necessary. As the output format for the receiver-derived clock offset is limited to nanoseconds the offset should be rounded to the nearest nanosecond before it is used to correct the observables in order to guarantee correct reconstruction.6. ADDITIONAL HINTS AND TIPSPrograms developed to read RINEX Version 1 files have to verify the version number. Version 2 files may look different (version number, END OF HEADER record, receiver and antenna serial number alphanumeric) even if they do not use any of the new featuresWe propose that routines to read RINEX Version 2 files automatically delete leading blanks in any CHARACTER input field. Routines creating RINEX Version 2 files should also left-justify all variables in the CHARACTER fields.DOS, and other, files may have variable record lengths, so we recommend to first read each observation record into a 80-character blank string and decode the data afterwards. In variable length records, empty data fields at the end of a record may be missing, especially in the case of the optional receiver clock offset.7. RINEX UNDER ANTISPOOFING (AS)Some receivers generate code delay differences between the first and second frequency using cross-correlation techniques when AS is on and may recover the phase observations on L2 in full cycles. Using the C/A code delay on L1 and the observed difference it is possible to generate a code delay observation for the second frequency.Other receivers recover P code observations by breaking down the Y code into P and W code.Most of these observations may suffer from an increased noise level. In order to enable the postprocessing programs to take special actions, such AS-infected observations are flagged using bit number 2 of the Loss of Lock Indicators (i.e. their current values are increased by 4).8. GLONASS Extensions8.1 RINEX Observation file8.1.1 Time System IdentifierRINEX Version 2 needs one major supplement, the explicit definition of the time system:GLONASS is basically running on UTC (or, more precisely, GLONASS system time linked to UTC(SU)), i.e. the time tags are given in UTC and not GPS time. In order to remove possible misunderstandings and ambiguities, the header records "TIME OF FIRST OBS" and (if present) "TIME OF LAST OBS" in GLONASS and GPS observation files _can_, in mixed GLONASS/GPS observation files _must_contain a time system identifier defining the system that all time tags in the file are referring to: "GPS" to identify GPS time, "GLO" to identify the GLONASS UTC time system. Pure GPS files default to GPS and pure GLONASS files default to GLO.Format definitions see Table A1.Hence, the two possible time tags differ by the current number of leap seconds.In order to have the current number of leap seconds available we recommend to include a LEAP SECOND line into the RINEX header.If there are known non-integer biases between the "GPS receiver clock" and "GLONASS receiver clock" in the same receiver, they should be applied.In this case the respective code and phase observations have to be corrected,too (c * bias if expressed in meters).Unknown such biases will have to be solved for during the post processingThe small differences (modulo 1 second) between GLONASS system time, UTC(SU),UTC(USNO) and GPS system time have to be dealt with during the post-processing and not before the RINEX conversion. It may also be necessary to solve for remaining differences during the post-processing.8.1.2 Pseudorange DefinitionThe pseudorange (code) measurement is defined to be equivalent to the difference of the time of reception (expressed in the time frame of the receiver) and the time of transmission (expressed in the time frame of the satellite) of a distinct satellite signal.If a mixed-mode GPS/GLONASS receiver refers all pseudorange observations to one receiver clock only,- the raw GLONASS pseudoranges will show the current number of leap seconds between GPS time and GLONASS time if the receiver clock is running in the GPS time frame- the raw GPS pseudoranges will show the negative number of leap seconds between GPS time and GLONASS time if the receiver clock is running in the GLONASS time frameIn order to avoid misunderstandings and to keep the code observations within the format fields, the pseudoranges must be corrected in this case as follows:PR(GPS) := PR(GPS) + c * leap_seconds if generated with a receiver clock running in the GLONASS time framePR(GLO) := PR(GLO) - c * leap_seconds if generated with a receiver clock running in the GPS time frameto remove the contributions of the leap seconds from the pseudoranges."leap_seconds" is the actual number of leap seconds between GPS and GLONASS(UTC) time, as broadcast in the GPS almanac and distributed in Circular T of BIPM.8.1.3 More than 12 satellites per epochThe format of the epoch / satellite line in the observation record part of the RINEX Observation files has only been defined for up to 12 satellites per epoch. We explicitly define now the format of the continuation lines, see table A2.8.2 RINEX Navigation Files for GLONASSAs the GLONASS navigation message differs in contents from the GPS message too much, a special GLONASS navigation message file format has been defined.The header section and the first data record (epoch, satellite clock information) is similar to the GPS navigation file. The following records contain the satellite position, velocity and acceleration, the clock and frequency biases as well as auxiliary information as health, satellite frequency (channel), age of the information.*** In order to use the same sign conventions for the time and frequency bias as in the GPS navigation files, the broadcast GLONASS values are multiplied by -1.The time tags in the GLONASS navigation files are given in UTC (i.e. _not_Moscow time or GPS time).Filenaming convention: See above.9. REFERENCESEvans, A. (1989): "Summary of the Workshop on GPS Exchange Formats." Proceedings of the Fifth International Geodetic Symposium on Satellite Systems, pp. 917ff, Las Cruces.Gurtner, W., G. Mader, D. Arthur (1989): "A Common Exchange Format for GPS Data." CSTG GPS Bulletin Vol.2 No.3, May/June 1989, National Geodetic Survey, Rockville.Gurtner, W., G. Mader (1990): "The RINEX Format: Current Status, Future Developments." Proceedings of the Second International Symposium of Precise Positioning with the Global Positioning system, pp. 977ff, Ottawa.Gurtner, W., G. Mader (1990): "Receiver Independent Exchange Format Version 2." CSTG GPS Bulletin Vol.3 No.3, Sept/Oct 1990, National Geodetic Survey, Rockville.10. RINEX VERSION 2 FORMAT DEFINITIONS AND EXAMPLES+----------------------------------------------------------------------------+| TABLE A1 || OBSERVATION DATA FILE - HEADER SECTION DESCRIPTION |+--------------------+------------------------------------------+------------+| HEADER LABEL | DESCRIPTION | FORMAT || (Columns 61-80) | | |+--------------------+------------------------------------------+------------+|RINEX VERSION / TYPE| - Format version (2) | I6,14X, || | - File type ('O' for Observation Data) | A1,19X, || | - Satellite System: blank or 'G': GPS | A1,19X || | 'R': GLONASS | || | 'T': NNSS Transit | || | 'M': Mixed | |+--------------------+------------------------------------------+------------+|PGM / RUN BY / DATE | - Name of program creating current file | A20, || | - Name of agency creating current file | A20, || | - Date of file creation | A20 |+--------------------+------------------------------------------+------------+*|COMMENT | Comment line(s) | A60 |*+--------------------+------------------------------------------+------------+|MARKER NAME | Name of antenna marker | A60 |+--------------------+------------------------------------------+------------+*|MARKER NUMBER | Number of antenna marker | A20 |*+--------------------+------------------------------------------+------------+|OBSERVER / AGENCY | Name of observer / agency | A20,A40 | +--------------------+------------------------------------------+------------+ |REC # / TYPE / VERS | Receiver number, type, and version | 3A20 | | | (Version: e.g. Internal Software Version)| | +--------------------+------------------------------------------+------------+ |ANT # / TYPE | Antenna number and type | 2A20 | +--------------------+------------------------------------------+------------+ |APPROX POSITION XYZ | Approximate marker position (WGS84) | 3F14.4 | +--------------------+------------------------------------------+------------+ |ANTENNA: DELTA H/E/N| - Antenna height: Height of bottom | 3F14.4 | | | surface of antenna above marker | | | | - Eccentricities of antenna center | | | | relative to marker to the east | | | | and north (all units in meters) | | +--------------------+------------------------------------------+------------+ |WAVELENGTH FACT L1/2| - Wavelength factors for L1 and L2 | 2I6, | | | 1: Full cycle ambiguities | | | | 2: Half cycle ambiguities (squaring) | | | | 0 (in L2): Single frequency instrument | | | | - Number of satellites to follow in list | I6, | | | for which these factors are valid. | | | | 0 or blank: Default wavelength factors | | | | for all satellites not contained in | | | | such a list. | | | | - List of PRNs (satellite numbers) | 7(3X,A1,I2)| | | | | | | Repeat record if necessary | | +--------------------+------------------------------------------+------------+ |# / TYPES OF OBSERV | - Number of different observation types | I6, | | | stored in the file | | | | - Observation types | 9(4X,A2) | | | | | | | If more than 9 observation types: | | | | Use continuation line(s) |6X,9(4X,A2) | | | | | | | The following observation types are | | | | defined in RINEX Version 2: | | | | | | | | L1, L2: Phase measurements on L1 and L2 | | | | C1 : Pseudorange using C/A-Code on L1 | | | | P1, P2: Pseudorange using P-Code on L1,L2| | | | D1, D2: Doppler frequency on L1 and L2 | | | | T1, T2: Transit Integrated Doppler on | | | | 150 (T1) and 400 MHz (T2) | || | | | | | Observations collected under Antispoofing| | | | are converted to "L2" or "P2" and flagged| | | | with bit 2 of loss of lock indicator | | | | (see Table A2). | | | | | | | | Units : Phase : full cycles | | | | Pseudorange : meters | | | | Doppler : Hz | | | | Transit : cycles | | | | | | | | The sequence of the types in this record | | | | has to correspond to the sequence of the | | | | observations in the observation records | | +--------------------+------------------------------------------+------------+ *|INTERVAL | Observation interval in seconds | I6 |* +--------------------+------------------------------------------+------------+ |TIME OF FIRST OBS | - Time of first observation record | 5I6,F12.6, | | | (4-digit-year, month,day,hour,min,sec) | | | | - Time system: GPS (=GPS time system) | 6X,A3 | | | GLO (=UTC time system) | | | | Compulsory in mixed GPS/GLONASS files | | | | Defaults: GPS for pure GPS files | | | | GLO for pure GLONASS files | | +--------------------+------------------------------------------+------------+ *|TIME OF LAST OBS | - Time of last observation record | 5I6,F12.6, |* | | (4-digit-year, month,day,hour,min,sec) | | | | - Time system: GPS (=GPS time system) | 6X,A3 | | | GLO (=UTC time system) | | | | Compulsory in mixed GPS/GLONASS files | | | | Defaults: GPS for pure GPS files | | | | GLO for pure GLONASS files | | +--------------------+------------------------------------------+------------+ *|LEAP SECONDS | Number of leap seconds since 6-Jan-1980 | I6 |* | | Recommended for mixed GPS/GLONASS files | | +--------------------+------------------------------------------+------------+ *|# OF SATELLITES | Number of satellites, for which | I6 |* | | observations are stored in the file | | +--------------------+------------------------------------------+------------+ *|PRN / # OF OBS | PRN (sat.number), number of observations |3X,A1,I2,9I6|* | | for each observation type indicated | | | | in the "# / TYPES OF OBSERV" - record. | | | | | | | | If more than 9 observation types: | || | Use continuation line(s) | 6X,9I6 | | | | | | | This record is (these records are) | | | | repeated for each satellite present in | | | | the data file | | +--------------------+------------------------------------------+------------+ |END OF HEADER | Last record in the header section. | 60X | +--------------------+------------------------------------------+------------+Records marked with * are optional+----------------------------------------------------------------------------+ | TABLE A2 | | OBSERVATION DATA FILE - DATA RECORD DESCRIPTION | +-------------+-------------------------------------------------+------------+ | OBS. RECORD | DESCRIPTION | FORMAT | +-------------+-------------------------------------------------+------------+ | EPOCH/SAT | - Epoch : | 5I3,F11.7, | | or | year (2 digits), month,day,hour,min,sec | | | EVENT FLAG | - Epoch flag 0: OK | I3, | | | 1: power failure between | | | | previous and current epoch | | | | 1: Event flag | | | | - Number of satellites in current epoch | I3, | | | - List of PRNs (sat.numbers) in current epoch | 12(A1,I2), | | | - receiver clock offset (seconds, optional) | F12.9 | | | | | | | If more than 12 satellites: Use continuation | 32X, | | | line(s) | 12(A1,I2) | | | | | | | If EVENT FLAG record (epoch flag 1): | | | | - Event flag: | | | | 2: start moving antenna | | | | 3: new site occupation (end of kinem. data) | | | | (at least MARKER NAME record follows) | | | | 4: header information follows | | | | 5: external event (epoch is significant, | | | | same time frame as observation time tags)| | | | 6: cycle slip records follow to optionally | | | | report detected and repaired cycle slips | | | | (same format as OBSERVATIONS records; | | | | slip instead of observation; LLI and | | | | signal strength blank) | || | - "Number of satellites" contains number of | | | | records to follow (0 for event flags 2,5) | | +-------------+-------------------------------------------------+------------+ |OBSERVATIONS | - Observation | rep. within record for | m(F14.3, | | | - LLI | each obs.type (same seq | I1, | | | - Signal strength | as given in header) | I1) | | | | | | | If more than 5 observation types (=80 char): | | | | continue observations in next record. | | | | | | | | This record is (these records are) repeated for | | | | each satellite given in EPOCH/SAT - record. | | | | | | | | Observations: | | | | Phase : Units in whole cycles of carrier | | | | Code : Units in meters | | | | Missing observations are written as 0.0 | | | | or blanks. | | | | Loss of lock indicator (LLI). Range: 0-7 | | | | 0 or blank: OK or not known | | | | Bit 0 set : Lost lock between previous and | | | | current observation: cycle slip | | | | possible | | | | Bit 1 set : Opposite wavelength factor to the | | | | one defined for the satellite by a | | | | previous WAVELENGTH FACT L1/2 line.| | | | Valid for the current epoch only. | | | | Bit 2 set : Observation under Antispoofing | | | | (may suffer from increased noise) | | | | | | | | Bits 0 and 1 for phase only. | | | | | | | | Signal strength projected into interval 1-9: | | | | 1: minimum possible signal strength | | | | 5: threshold for good S/N ratio | | | | 9: maximum possible signal strength | | | | 0 or blank: not known, don't care | | +-------------+-------------------------------------------------+------------++----------------------------------------------------------------------------+ | TABLE A3 | | NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION | +--------------------+------------------------------------------+------------+。
埃德斯科尔外语学习指南说明书
New submission arrangements for oral recordings - May/June 2022 series onwardsInternational GCSE and IAS/IAL Modern Foreign LanguagesThis guidance applies to all international qualifications with a speaking component: •International GCSE Chinese, French, German and Spanish.•International GCSE English as a Second Language and Swahili (optional speaking components).•International AS/A level French, German and Spanish.Submitting oral recordings via Learner Work TransferTo help with teacher-examiner workload, and to ensure our commitment to working more digitally, we have developed a new online way for centres to submit their candidate speaking recordings to Pearson.The system is called the digital Learner Work Transfer (LWT) portal and is already used by centres for International AS/A level languages. Audio files for all language qualifications must now be submitted via this portal, which is available to access through Edexcel Online (EOL). Submissions using USB / CDs will no longer be accepted. Please contact our customer services team if you need support with the LWT portal.Please note that you should always keep a copy of your candidates’ recordings and paperwork. Should there be any issues with the recording or paperwork uploaded onto LWT, Pearson may request a copy of the candidates' work.Key dates and deadlinesThe speaking assessment windows for the May/June 2022 series are as follows: •International GCSE Chinese, French, German and Spanish: 14 March-20 May 2022.•International GCSE English as a Second Language and Swahili (optional speaking components): 28 March-20 May 2022.•International AS/A level French, German and Spanish: 18 April-20 May 2022.Speaking dates for future series will be available once they are confirmed in the key dates finder and on the languages landing page.Learner Work Transfer for the summer 2022 series will be available for centres to access from 4 April 2022.For International GCSE orals that are scheduled within the designated speaking window before 4 April 2022, candidate recordings and associated paperwork should therefore be stored securely in the centre (accessible only by exams officers and authorised staff) to be submitted as soon as possible once LWT is available. The usual 2 working day submissions window applied to all our MFL qualifications would therefore not apply this year to International GCSE orals conducted before 4 April 2022.In subsequent series, LWT will be scheduled to be available to centres for all language qualifications at the start of the prescribed speaking window dates.The usual submission deadline is 2 working days after the final speaking exam for that language qualification has taken place in the centre. The LWT window to submit materials will therefore close at 5pm GMT on 24 May 2022.Files to submitCentres must submit the following documents for each candidate. Where signatures are required, names can simply be typed on the on-screen forms – there is no need to print, sign manually and scan the forms.For International GCSE Chinese, French, German and Spanish:•Candidate recording•Candidate cover sheet (CCS)•Picture used for task A, picture-based discussion, in digital or scanned form (ifa candidate has chosen a personal photo, a written description of the picturemay be provided instead).For International GCSE English as a Second Language (ESL):•Candidate recording•Candidate cover sheet for ESL (CCS)For International GCSE Swahili (optional centre-assessed speaking endorsement): •Candidate recording for moderation purposes•Assessment record sheet for spoken language endorsementPlease note that for International GCSE Swahili, submission is only required if a sample of recordings or all recordings are requested for external monitoring.For IAS/IAL:•Candidate recording•Oral topic form (OR1) for Unit 1 and/or•Oral chosen issue form (OR3) for Unit 3•Candidate speaking authentication sheet (CAS).File naming conventionsWhen you create a file for each sampled student then each file should use the following naming convention:[centre #]_[candidate number #]_[surname]_[first letter of first name]For example, Jane Smith with candidate number 7890 at centre 12345 would have work in a folder titled: 12345_7890_Smith_JIf you are uploading more than one document for a student, please adopt the following naming approach:International GCSE candidate:•12345_7890_Smith_J (for the speaking recording itself)•12345_7890_Smith_J_CCS (for the candidate cover sheet)•12345_7890_Smith_J_pic (for the candidate’s chosen picture for task A)IAS/IAL candidate:•12345_7890_Smith_J (for the speaking recording itself)•12345_7890_Smith_J_OR1 (for the oral topic form for IAS/IAL)•12345_7890_Smith_J_CAS (for the candidate authentication sheet) Recording formatsPearson Edexcel only accepts recordings in the following formats:mp3 / mpeg / wav / vlc / m4a / ogg / wma / oga / aif / mid / aiff / midiIf centres record the oral assessment in a different digital format, they must convert the recording to one of the above accepted formats before submitting them to Pearson Edexcel.Complete, unedited recordings of all assessments must be submitted to Pearson Edexcel via the LWT. There is no need to encrypt the files you are uploading as the LWT portal is secure. Please do not use zip files.Data protection and privacyThe LWT portal is secure, so there is no need to encrypt the files you are uploading.How to use the LWT portal to submit oral assessmentsInstructions on how to access LWT can be found here and guidance on managing uploads is available in video format here. If you need further support, step-by-step guidance and screenshots are provided below. If you have any issues with the LWT system, please contact our helpdesk on 0800 169 9202.1. Accessing the portalAccess the portal through your Edexcel Online account under ‘Learner Work Transfer’.An example of the Learner Work Transfer dashboard is shown below. Depending on the state of the request (‘To Do’, ‘In Progress’ or ‘Completed’), the default view will start on a particular tab.2. Viewing candidates in the portalThe search box can be used to narrow down the results as required. Click the three vertical dots on the right of the request then ‘View’ learners to open the request.You will be presented with a list of all learners entered for the unit. If you have additional learners who have not yet been entered, please make entries for them through the usual process. This should be updated within 24 hours. If you have uploaded evidence for some learners, when the new entries have been added, the request will show a status on ‘In Progress (C)’ to represent a change.3. Naming documents for uploadWhen you create a file for each sampled student then each file should use the following naming convention:[centre #]_[candidate number #]_[surname]_[first letter of first name]For example, Jane Smith with candidate number 7890 at centre 12345 would have work in a folder titled: 12345_7890_Smith_JMore details on naming individual documents are provided on page 1 of this guidance.If you are uploading one CAS form for multiple candidates, please use the following naming convention: [centre number]_CS4, i.e. 12345_CS4. Please see the instructions on linking a file to multiple learners below.4. Uploading filesTo upload learner evidence, click ‘Browse’ under the learner.This will open a file explorer. Click on a file to upload or hold down the ‘Ctrl’ key to select multiple files then click ‘Open’. Alternatively drag the files from your computer onto the grey area of the page, where it states: ‘Drop files here’.Files uploaded will then move to ‘Scanning’ state. Once the checks are successful it is up dated to ‘Accepted’ or ‘Rejected’. If you have uploaded the incorrect document, you can remove it by clicking the ‘X’ next to the file name.Please do not zip files. You can hold CTRL down whilst selecting multiple files in the file explorer if you wish to upload multiple files for a single student in one go. LWT is a secure platform, so there is no need to encrypt files.The portal accepts most of the popular file types including mp3, mp4 and jpeg files.A full list of accepted file types can be found here.For any learners who were absent for the assessment, the centre should change their status to ‘Absent’ using the ‘Status’ dropdown. This will take the place of completing the attendance register.If the learners work is not available, for example where special consideration is being applied, the status should be changed to ‘No Evidence’. Special consideration should be completed via an application following the usual process.Attendance registers can be uploaded in the ‘Administration Material’ section. You should only upload documents in this section that are required for the course at cohort level.Once you have at least one file uploaded per learner and indicated their status (absent/no evidence) the ‘Submit Request’ option will become available at the top of the screen and also from the ‘In Progress’ dashboard.Once a request has been submitted, you will receive a confirmation message, click ‘Ok’ to proceed. This will send the request to your assessor, and you will no longer be able to add, edit or remove evidence. The completed tab shows requests which have been submitted for assessment.If the assessor finds that the wrong material has been uploaded, they can return the request to the centre. You should receive an email from the assessor or Pearson. This will show in the ‘In Progress’ tab with a status ‘Returned’. You can then add or remove files before resubmitting the request.If the centre identifies incorrect documents uploaded and submitted, they will need to contact the assessor or Pearson for the request to be returned.5. Linking a file to multiple learnersUse the ‘Shared Files’ feature to upload a file that must be shared between multiple learners. You can drag and drop files into the grey space or browse to the required file within your system.A file cannot be uploaded directly to a learner or via the shared files functionality if another file with the same name and format has already been uploaded to that card. For example, you cannot upload multiple pdfs called ‘speaking form’ to the sa me learner, or within the shared file section. If this occurs an error message is shown.However, each learner can have a file called ‘speaking form’ uploaded to their card or associated to them via the shared files functionality.Please see this video guide (from 5 mins 55 seconds) for step-by-step instructions on how to upload a file and link it to multiple candidates. If uploading one form for multiple candidates, please name it with your centre number and the form name. There is no need to name a form with multiple candidate numbers if it is linked to them on LWT in this way.Pearson Edexcel– New submission arrangements for oral recordings, May/June 2022 series onwards – Issue 3 – 25 March 2022 – Author and Approver: Sheena Newland, Assessment and Qualifications – DCL1 © Pearson Education Limited 2022。
火鸟帧抓取器快速入门指南说明书
FireBird Frame Grabbers - Installation and UseQUICKSTART GUIDEFIREBIRD FRAME GRABBERS – QUICKSTART GUIDEContentsFIREBIRD FRAME GRABBERS – QUICKSTART GUIDE 2HARDWARE INSTALLATION 3 SOFTWARE INSTALLATION 4 UPDATING THE FIREBIRD FIRMWARE 5 WHERE TO GO NEXT 6 ACTIVECAPTURE - INTRODUCTION 7 ACTIVECAPTURE - IN USE 8 GENTL CAMERA LINK SETUP UTILITY 9 WHAT ELSE IS INSTALLED? 10 SOFTWARE UN-INSTALLATION 11 CONTACT DETAILS 12DisclaimerWhile every precaution has been taken in the preparation of this document, Active Silicon assumes no responsibility for errors or omissions. Active Silicon reserves the right to change the specification of the product described within this document and the document itself at any time without notice and without obligation of Active Silicon to notify any person of such revisions or changes.Copyright NoticeCopyright © 2022 Active Silicon. All rights reserved. This document may notin whole or in part, be reproduced, transmitted, transcribed, stored in any electronic medium or machine readable form, or translated into any language or computer language without the prior written consent of Active Silicon.Trademarks and AcknowledgementsAll trademarks and registered trademarks are the property of their respective owners.Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.GenICam is a trademark of EMVA, CoaXPress is a trademark of JIIA, Camera Link is a trademark of A3.Part InformationPart Number: FBD-MAN-QS.Power off and open up the computer taking the usual anti-static precautions.Please note: The boards are keyed so that they can only be fitted into a slot in which they will work.Do not modify the FireBird board or the motherboard in an attempt to override the keying as this could result in serious damage.For full performance, boards with a part number including ’PE8’ mustbe fitted in a slot that supportsPCI Express at x8 width; similarly those including ‘PE4’ must use aslot supporting x4. Boards with apart number including ’3PE’ mustbe fitted in a slot that supports PCIExpress at Gen 3 speeds; similarlythose including ‘2PE’ must use a slotsupporting Gen 2 speeds. Check yourcomputer documentation for detailsof the PCI Express connectors.CoaXPress Boards Only: Formultichannel CoaXPress boards,and the 1XCXP6-2PE8 board, if theboard will be used to power camerasthrough the CoaXPress cables usingPoCXP then the auxiliary powerconnector J13 must be connectedto the computer power supply. Thecorrect power supply cable is oneintended for PCI Express Graphics(PEG) cards, and may have 6 or 8ways. To distinguish it from othersimilar connectors in the computer,the connector should be black andmay be marked ‘PCI-E’ or ‘PEG’. Similarconnectors that are not PEG should bewhite. However this is often not thecase, so the cables should be carefullychecked for the pattern of squaresand chamfers on the plastic body ofthe connector at the end of the cable.See the images below.Also, the wires should be black onthe side with the connector clip, andcolored (often yellow or blue) on theother side.If the connector does not matchthose shown above, DO NOTattempt to force it into FireBird asthis could result in serious damage.If a 6 way connector is plugged intoFireBird, it should be aligned at theupper 6 ways of the 8 way FireBirdconnector as shown below.PEG cable splitters, PEG to SATAadapters and PEG to ‘Molex’ adaptersare available from Active Silicon andare included in the optional cablestarter kit.Close and power on the computer.The Active Silicon FireBird Package includes the FireBird Driver (device driver and core libraries), various applications including ActiveCapture, a GenICam-based GUI program, and the GenTL Producer. Additionally, ActiveSDK is for software developers.By default, selecting Typical installs everything, but individual options can be deselected if required (see image below). The packages are supplied as a compressed file which includes the installation package along with theseinstructions and the release notes.The file naming convention is:as-<product>-<OS>- vXX_YY_ZZwhere <product> is:z fbd-cxp for the FireBird CoaXPressPackage.z fbd-cl for the FireBird Camera LinkPackage.z fbd-sdk for the FireBird ActiveSDKPackage.Windows® 10 and 11Uninstall any previous version ofthe Active Silicon FireBird Package(see page 11). Note: The previousSDK can be left on the PC to allowdevelopers to refer to both old andnew SDKs.Un-zip the required msi package to alocal disk.Run the msi.Follow the on-screen prompts,including to reboot the PC onceinstallation has completed.After completing installation it isrecommended to update the FireBirdfirmware (see the next page).Windows ServicePart of the installation is a Windowsservice ‘Active Silicon FireBird’ whichautomatically runs as Windows starts.This loads the main firmware intoFireBird boards with part numbersincluding ‘3PE’. Until the service runsthese boards have limited functionality,and from a hardware viewpoint theydo not power or discover connectedcameras and LEDs do not function. Thisprocess is needed to meet PCI Expressrequirements with the larger FPGA used.Other Operating SystemsSee the specific Quickstart Guidesupplied with the installation package.It is recommended to always update the firmware on FireBird boards to match that in the current driver set. This is also important because new boards ship with firmware used in production testing.UPDATING THE FIREBIRD FIRMWARE Design option controls the configuration mode of the board. The options presenteddepend on the board in use. The options with a 4xCXP6 FireBird are shown here.Default updates the firmware keeping the same configuration mode as before the update.4xCXP6: 1 Camera selects the configuration mode with 1 camera with up to 4 coax cables.4xCXP6: 2 Camera selects the configuration mode with 2 cameras each with 2 coax cables.4xCXP6: 4 Camera selects the configuration mode with 4 cameras each with 1 coax cable.Feedback window shows which boards will be updated, their current configuration and firmware version, what they will beupdated to, and progress information duringupdating.Board option allows only selected boards in a system to be updated. By default all boards are updated. Note that updater will update any Phoenix boards it finds in a system as well as FireBirds. Program Board(s) button to start the update process. Wait for the process to complete, then reboot the PC.If the updater fails for any reason so that the board is no longer recognized, jumper J8 can be moved to the ‘FF’position before rebooting the PC to allow the board to configure from its ‘Factory’ design, to allow the update process to be run again. When the updater has finished, shut down the PC and move the jumper back to its default position before powering up the board. See the Jumpers section of the FireBird Hardware Manual for more information.and documentation for other for other operating systems refer to the specific Quickstart Guide.four coax cables, but it can be configured e.g. to support four cameras each with one coax cable by selecting Design 4xCXP6: 4 Camera .To update firmware select Flash Programming from the Tools menu in ActiveCapture to run the FireBird / Phoenix Firmware Updater utility.This utility also allows the configuration mode of the board to be changed – for example a four input CoaXPress board by default supports one camera with up toWHERE TO GO NEXTCheck the PC BIOSOlder BIOS versions in PCs cangive noticeably lower PCI Express bandwidth. It is recommended to check for available BIOS updates, especially if any bandwidth problems are seen.Many PCs now support power saving features in the BIOS. These can result in poor PCI Express bandwidth, maybe only occasionally. Therefore Active Silicon recommends that the following settings are used (where available):z C-States set to ‘Off’.z Speedstep set to ‘Off’.z PCI Performance Mode set to ‘On’.z PCI Express Power Management setto ‘Off’.Check the BandwidthNext run the Bandwidth Test utility.FireBird can transfer data at very highrates but if the PC cannot keep up thesystem will not work. This utility, in theTools menu in ActiveCapture, shows themaximum rate that FireBird can transferdata to the PC.For a board with part number including‘3PE8’ a value around 6800 Mbytes/secis typical of a good PC; similarly 3400Mytes/sec for a ‘3PE4’ or ‘2PE8’ and 1700Mbytes/sec for a ‘2PE4’. A low or unstablevalue means that problems are likely tobe seen.Low Bandwidth?If the bandwidth test reports a low orunstable value, check the following:Check that a suitable PCI Express slotis in use (see Hardware Installation onpage 3). Sometimes motherboardrestrictions mean that a Gen 2 x16 slotworks much better than a Gen 2 x8slot, so try using a x16 slot.Check the BIOS settings (see Check thePC BIOS opposite).How old is the motherboard?Old chipsets may show worseperformance than current ones.DocumentationThe Start Menu under Active SiliconFireBird <xx> – Documentation includesthis document, release notes, and thefollowing key documents:The FireBird Hardware Manual givesfull details of all connectors, LEDs andjumpers on FireBird, I/O support, and PCrequirements.The FireBird System Manual is thefirst place for system developers andprogrammers to go. It gives an overviewof the options to configure a system,describes all the trigger modes in detail,and discusses system issues.Documentation on the API is describedin the ActiveSDKsection (see page 10).Device List.Acme” highlighted here, andConnect button.Live button for continuousSingle Sequence buttonTools menu gives access to utilities such as the firmware updaterand the GenTL CL Setup Utility.ACTIVECAPTURE - IN USE and “-” keys on the keyboard, or the mouse wheel.2. The Feature Browser shows the selected in the Device List . Any feature that is not greyed out can be changed. Note that many features are greyed out whileacquisition is in progress – first stop acquistion to change them. The FireBird features for pixel format, width and height are automatically set to match the camera. Therefore to change the values of these features, change them on the camera.The Feature Browser refreshes visible features periodically while the system is in use. With Camera Link cameras this can be slow, and turning off Polling can be useful. Refresh button can then be used to update features on demand.Clicking the Histogram button displays a histogram and statistics for the selected image, or byentering coordinates, for just part of the image.Similarly, the 1D Profile button ActiveCapture featuresGENTL CAMERA LINK SETUP UTILITY The GenTL CL Setup Utility needs to be run to allow the use of Camera Link cameras that support GenICam. It is needed because Camera Link pre-dates GenICam so cameras cannot be discovered automatically.The utility only needs to be run once for a given camera connection. ToCamera Probing to select a channel on a FireBird board, and the camera that is connected to it.The list of cameras will show all the CLProtocolDLLs installed on the machine, including thegeneric GenICam#GenCP_01_00 DLL which should be used for all GenCP cameras.Click Add to attempt to connect to the camera. If it is found it will be added to the list ofknown cameras.found and added using the Camera Probing controls.Click Save when the cameras have been correctly added.A GenTL application will attempt to connect to these cameras, so if a camera is removedfrom a system or moved to another port, select the camera and click Delete .Status Log shows what the utility has done.do this run it from the Tools menu in ActiveCapture , after ensuring that no cameras are open in ActiveCapture , and closing any other application that may have the cameras open.After it has been run, refresh the Device List in the GenTL consumer applicationin use, such as ActiveCapure , and the camera should then be listed and operate correctly.The utility associates a CLProtocol DLL with a specific Camera Link port on FireBird. For cameras using GenCP , a generic GenCP DLL is provided as part ofthe FireBird installation.For other cameras, note that onlyCamera Link cameras that are provided with a CLProtocol DLL can be used with GenICam. Older Camera Link cameras may not provide a suitable DLL and therefore will not work with GenICam applications. Contact the camera vendor to obtain the correct DLL file.WHAT ELSE IS INSTALLED?GenICam GenTLThe GenTL Producer allows GenTL based GenICam applications to control the camera and FireBird. It should work with third party applications described as‘GenTL Consumers’, without needing any custom interface code.Note that some GenICam applications do not use GenTL, but rely on direct image transfer from GigE Vision cameras – these will not work with FireBird. Documentation on the Producer and the following GenTL utilities is in the FireBird GenTL Producer Manual which can be found in the Start Menu under Active Silicon FireBird <xx> – Documentation.ActiveSDKThe FireBird ActiveSDK IntroductoryManual gives an overview of ActiveSDK,and the various API Manuals describethe available ActiveSDK functions indetail. These are in the Start Menu underActive Silicon ActiveSDK vXX.YY.ZZ –Documentation.Example source code is in the theStart Menu under Active Silicon ActiveSDKvXX.YY.ZZ – View Example Source, andthe Visual Studio project can be openedfrom the Start Menu under Active SiliconActiveSDK vXX.YY.ZZ – Open ExampleProjects.Support InformationThe Help menu in ActiveCapture givestwo groups of information that can beuseful when contacting Active Silicon’ssupport team.Show Board Information gives details ofthe Active Silicon boards in the system.System Information gives more generalinformation about a system. Theinformation is both displayed to thescreen, and saved in file as_sysinfo.txt inPublic Documents \ Active Silicon.Miscellaneous:PCF setup files for many camerasare in the Start Menu under ActiveSilicon FireBird <xx> – PCF Files. Theseconfigure the FireBird board to matchthe specified camera. They can be usedwith ActiveCapture, and can be read intoprograms written using the PHX API.PhoenixCapture: This is Active Silicon’soriginal application to display imagesfrom cameras. It has been replaced byActiveCapture, but for users familiar withthe application it can be found in theProgram Files \ Active Silicon \ FireBird<xx>\ Bin \ Win64/32 directory. The utility isbest used in conjunction with PCF files(see above).WindowsWindows 10 and 11: Remove the package using the Windows Settings Apps & features. All packages are listed with names starting “Active Silicon”.Note that it is not necessary to remove previous copies of ActiveSDK before installing a new one. Multiple copies of ActiveSDK can be installed on the PC to allow developers to refer to both old and new versions.Other Operating SystemsSee the specific Quickstart Guide supplied with the installation package.SOFTWARE UN-INSTALLATIONFireBird Frame Grabbers – Quickstart Guide v2.511CONTACT DETAILS Contact DetailsNorth AmericaTel: +1 410-696-7642Email:***************************** Web: Europe & ROWTel: +44 (0) 1753 650600 Email:***************************** Web: 。
cep电子版纸版递交指南(中英文)cep_guidance_for_cep_applications
201306 PA/PH/CEP(09)108 2R CEP电子提交和纸质提交指南（中英文）官网原文下载：.edqm.eu/en/Guidance-for-electronic-and-paper-submissions-1585.html?mbID=107新版本生效日期：2013年8月1日Certification of Substances DivisionFK/CBPUBLIC DOCUMENT公开文件(LEVEL 1)第一层次English only/Anglais seulement仅英文版PA/PH/CEP(09)108, 2RStrasbourg, June 2013 Certification of suitability to Monographs of the European PharmacopoeiaGuidance for electronic and paper submissionsFor Certificates of Suitability (CEP) applicationsCEP电子和纸质申报指南Date of implementation: 1 August 2013Address: 7, sllee Kastner, CS 30026F-67081 Strasbourg (France)Telephone: 33(0)3 88 41 30 30 – Fax: 33 (0) 3 88 41 27 71 – :cepedqm.euInternet:.edqm.euTable of content目录1Introduction介绍2Scope and general requirements围和一般要求3Electronic submission formats电子申报格式3.1eCTD submission format eCTD申报格式3.2NeeS submission format NeeS申报格式3.3PDF format PDF格式4Submission of paper dossiers纸质文件提交5Content and structure of an application申报的容和结构6Lifecycle management of applications申报的生命周期管理6.1Granularity and updated sections章节分类和更新部分6.2When to submit a baseline Module 3?什么时候提交基准模块37Validation by the EDQM EDQM验证8Routes (or pathways) of submission递交方式（途径）9Security安全性1Introduction介绍This document is guidance for electronic and paper submissions for Certificates of Suitability (CEPs) applications. Information and requirements described in this document are intended to facilitate the handling and assessment of submissions for certificates of suitability (CEPs) and to maintain their lifecycle even if the submission is not an eCTD.本文件意在指导CEP的电子和纸质申报。
戴尔 OEM 客户端身份模块安装指南说明书
Dell OEM Client Identity Module Installation GuideThis document provides instructions to install an Identity Module on a Dell client system. June 2018RevisionsThe information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with re spect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.Use, copying, and distribution of any software described in this publication requires an applicable software license.Copyright © 2018 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA [8/21/2018]Dell believes the information in this document is accurate as of its publication date. The information is subject to change without notice.Table of contents Revisions (2)1Introduction (4)2Obtaining the Identity Module (4)2.1Obtaining the Client ID Installation Utility (5)2.2Install the Client Identity Module (5)3Verifying installation of Identity Module (6)4Troubleshooting (6)5Contact Information ..................................................................................................... Error! Bookmark not defined. 6Installing Identity Module ............................................................................................. Error! Bookmark not defined.6.1Uploading and installing Identity Module file ..................................................... Error! Bookmark not defined.6.2Resetting iDRAC................................................................................................ Error! Bookmark not defined.6.3Setting BIOS to defaults .................................................................................... Error! Bookmark not defined. 7Verifying installation of Identity Module ....................................................................... Error! Bookmark not defined. 8Contact Information (7)1 IntroductionThe Dell EMC OEM Identity Module enables OEMs to rebrand and customize their products. The Identitymodule centralizes the control points of multiple features, enabling OEM customers to save time andresources when deploying their systems.This document describes the process of installing an OEM Identity Module on a Dell Client system.Note: To install an Identity Module outside of Dell manufacturing facilities, use the Board Service Utility (BSU) version of the installation file.Note: The Dell EMC OEM Identity Module is also referred to as Personality Module in some earlierdocumentation.2 Obtaining the Identity ModuleThe Client Identity Module (IDM) is delivered by your Dell EMC account team. It may also be availablethrough the DellYourID website.The IDM file has a .pfs extension. The file name varies depending on the platform name and your rebrandedname. A common convention is as follows:SWB_Base_Rebrand_BSU_1.0.0.pfs, where∙SWB = Software Bundle∙Base = Base system∙Rebrand = Rebrand nameNotes:∙Do not use a file that does not have BSU in the file name.∙If you receive an executable file, open the file to extract the .pfs file. Use the .pfs file while performing the steps mentioned in this document.∙Sample or watermarked IDMs that are delivered exclusively for preview may not follow the common file naming convention.3 Obtaining the Client ID Installation UtilityTo install the IDM, you need the Client ID Installation Utility. This utility may also be referred to as the ClientID Injection Tool or the PMI Tool.You can obtain the Client ID Installation Utility from your Dell EMC account team.Notes:∙The Client ID Installation Utility is available in 32-bit and 64-bit versions. Use the utility corresponding to the version of Windows OS on your test platform. Both 32-bit and 64-bit version can be used in aDOS 16-bit environment.∙The Readme file of the Client ID Installation Utility is generic and suggests that the system is kept in manufacturing mode. However, to use the Client ID Installation Utility, your system does not have tobe in manufacturing mode.∙If an OS other than Windows is installed on your Dell Client system, boot the system using a DOS-based image, and then use the installation utility to install the IDM.4 Installing the IDM1. Copy the Client ID Installation Utility and the IDM .pfs file to a folder on your system.2. Open a Command Prompt with Administrator privileges.3. Navigate to the directory where you copied the installation utility and the .pfs file.Execute the command PMI_Wxx.exe /pm=<ID File> where <ID File> is the name of yourIDM .pfs file.4. Click Yes when prompted to allow the program to modify the system.The system reboots and the IDM is installed during POST.Warning: To avoid causing damage to your computer, do not turn off your computer or disconnectthe power source until the update is complete. During the update, your computer restarts and a blankscreen is displayed briefly.A message is displayed on the POST screen indicating that the installation was successful.5 Verifying installation of IDMAfter the IDM is installed, you can verify the installation by checking for the following:∙Custom splash screen image.Note: The custom splash logo may be displayed for a very short period of time. You may need to coldboot your system or take your monitor out of sleep mode to see the splash logo.∙System Setup (F2 at POST): Manufacturer and Model Name displayed in the upper left-hand corner of System Setup.∙One-Time Boot Menu (F12 at POST): Manufacturer and Model Name displayed at the bottom of the screen of One-Time Boot Menu.∙Additional validation of SMBIOS tables, specifically type 11.You can use the open-source dmidecode tool to check the SMBIOS tables.a. Download the version of this tool that is applicable to your operating system.b. Open the tool and use the following command: dmidecode -t11.- If an IDM is installed, an entry like the following is displayed:String 4 = 7[XXXX], where XXXX is the unique reseller ID for the IDM.Dell can share this reseller ID for your delivered ID Module upon request.- If an IDM is not installed or if the installation failed, the Type 11 table Tag 7 is not present in SMBIOS.If Tag 7 is present but lists a reseller ID that does not correspond to your specific ID Module, itindicates that a different ID Module is installed on the system. Contact your Dell EMC Accountteam.Note: You may need to check the Type 11 fields in conjunction with other checks to determine the rightsystem and the right model name. Contact your Dell EMC Account team for relevant documentation for thedifferent SMBIOS fields that are customized by the IDM. The customer is responsible for writing, maintaining,and executing the correct script to perform verification.6 TroubleshootingIDM installation fails without an error message.∙Ensure that you are using the latest available version of the Client ID Installation Utility. The utility may be periodically updated to support newer generations of BIOS.∙Contact your Dell EMC Account team. Include the project details to help the Accounts team in investigating the issue.Tag 7 is populated with a different reseller ID∙Confirm the correct reseller ID with your Dell EMC Account team.∙If you install different IDMs for different platforms or configurations, each IDM has a different reseller ID. Ensure to check for the appropriate reseller ID.∙If you run the reseller ID verification script before you attempt to install the IDM, and if your Dell platform is an OEM-ready platform, it might have a different generic ID Module already installed.In such cases, installing your custom IDM replaces the reseller ID already installed on the system.7 Contact InformationFor questions related to this document, contact the account manager responsible for the customerengagement.。
CAD图层命名标准
2027 CAD STANDARDS1. CAD文件命名规则1.1. 原则：为了加强在CAD绘图中协同工作,需要有一套科学的方法对所有的项目文件命名,采用西文字符缩写组合以便于同国际上优秀的设计公司交流.1.2. 目前状态：已形成涵盖建筑、结构、暖通、给排水、弱电、强电专业的CAD文件命名规则并有相应的实践经验.在命名格式上我们主要采取主组码+次组码+状态码+文1-4个西文字符如右图所示1.2.1. 文件名称格式,以下仅举例表示各专业的部分命名规则建筑专业2.2.1. 原则：为了加强在协同设计中文件交叉引用的直观性和方便性,需要一套科学的方法来组织和管理所有的CAD文件.2.2. 目前状态：在建筑、结构、暖通、给排水、弱电、强电专业都已形成一套文件结构组织规则.2.3. 以下为建筑专业的文件结构举例3. 字体类型3.1. 原则：为了方便与其它设计公司合作,避免在图纸中的出现乱码.3.2. 目前状态:我们采用西文字体Arial和中文字体宋体.这两种字体均为Windows操作系统自带的TureType字体.设计师根据样板文件建立的新文件中已涵盖了这两种字体,并通过DWS标准文件以保证随时变更的可能性.图A 代表我们常用的文字类型和标注类型.图B表示标准的四种字体类型.其中G_01,G_02采用西文的Arial和中文字体.S_01,S_02采用经过编译过西文的Arial和中文字体,供结构专业使用以方便输入三种钢筋符号.C-D_ T0G_01共用专业,字体高宽比为1.00C-D_ T0G_02共用专业,字体高宽比为0.75C-D_ T0S_01结构专业,字体高宽比为1.00C-D_ T0S_02结构专业,字体高宽比为0.75B4. 标注类型4.1. 原则：保证项目图纸标注类型统一,提高图纸标准化和表达水平,提高出图效率和质量,并要求减少设计师选择不同标注类型的工作量.4.2. 目前状态：如下图所示,我们采用统一的标注样式,以与快速的使用标注格式,并确保图形中的标注符合行业标准或项目标准.但由于专业的不同,标注上的字体的高宽比不同,所以也编制四套标注类型,设计师根据专业设计要求通过标准文件DWS进行匹配.5. 图层5.1. 原则：为便于各专业之间信息交换需要有一种科学的原则制定图层名称和设置.为了便于同国际主流设计公司交流,选用AIA规则做图层命名原则.5.2. 目前状态：图层名采用西文的缩写格式命名,编码之间用西文连接符"-"连接.一方面我们已参照相关的国家制图规范,同时更注意学习和吸收SOM、贝聿铭等国外优秀设计公司的图纸表达方式,另一方面,在水立方项目中,和PTW、ARUP等境外设计公司合作中所获得的经验证实了采用西文命名格式给每位设计师带来了方便.5.3. 建筑专业5.3.1. 平面部份的划分依据主要元素按照性质材质分为面积、露面、洁具等等.5.3.2. 立面部分的划分依据主要有两种情况⑴按照线宽的不同分为5种等级线：极粗、粗、中、细、极细.⑵按照元素的性质材质分为设备、装饰、管道等.5.3.3. 剖面部分的划分依据主要有两种情况⑴按照线宽的不同分为5种等级线：极粗、粗、中、细、极细.⑵按照元素的性质材质分为材料、图案等.5.4. 结构专业5.4.1. 结构图层按照图像元素的绘图需要分为梁体、柱子、平台、墙体等等.5.5. 暖通专业5.5.1. 暖通图层按照它的主要元素分为风口、风管、风机、采暖、水管、排烟等等.5.6. 给排水专业5.6.1. 按照水循环机理与其主要性质分为直饮水、热水、中水等等.5.7. 弱电强电专业5.7.1. 将弱电按其性质分为设备和线路两大类,将强电按其性质分为桥架、线路、设备三类.5.8. 通用资源专业5.8.1. 我们将各个专业共用的图层放在通用资源专业,方便设计师不会重复使用图层.5.8.2. 在通用资源图层中,我们把外部引用的图层放在0-XREF层中,没有放在0 层的原因考虑到很多图块都是放在0层的,如果把引用的图层关掉,会导致图块也会有影响. 5.9. 没有采用专业代码的原因在图层命名工作中,我们没有采用在主码前面加上专业码,例如A-DOOR-IDEN,因为每个在外部引用为前提的资料提交中图层名称前都有文件名为前缀,所以一般不会发生在图层名跨专业重合的情况.这样就为取消专业代码提供了现实基础.同时从实际操作中可以发现取消专业代码后,各专业设计师会更加方便选择图层.因为通过键入图层名的第一个字母来快速检索所需要的图层.5.10. 每个专业图层单独放在一个DWS标准文件中,以供设计师保证图纸与最新标准的同步更新.6. 笔宽设置文件6.1. 原则：为了保证参加外部引用的文件能按照不同专业需求方便灵活的打印,需要一种不依赖图层色彩的打印笔宽设置方法,以便提高图纸正确率和图纸表达水平,提高出图效率和质量.6.2. 目前状态：采用的笔宽文件为.STB 格式.考虑到由不同的专业共同完成一套图纸,如果采用CTB,不但在颜色选择上非常有局限性,而且对于建筑图层的笔宽表达上会很不方便. 如下图所示为建筑专业的图层设置,在Plot Style属性中每个图层都有相对应的打印类型,这种方法在图层设置时工作量会比较大,但在后期出图时会更加灵活方便.例如WALL-FULL这个图层,建筑专业在绘图时选用红色,出图时需要设置成0.25,而对于暖通专业来说,WALL-FULL图层也选用红色,但出图时只需要设置成0.1,如何使用CTB打印方式,完成以上命题会异常困难,但在STB打印方式下,暖通专业设计师只要选用标准命名的STB文件即可.7. 出图文件7.1. 原则：为了保证每张图纸都拥有唯一的电子文件,以便于日常检索和工程项目结束后归档.出图文件的命名与图纸编号同.7.2. 目前状态：出图文件主要基于计算机辅助设计师事先定义好的出图文件的样板文件而创建的,里面包含大量的图纸初始化设置.出图文件的命名与组织结构均遵守相应规则.7.3. 出图文件中包含的内容出图文件图纸空间只有外部引用进来的图框、作为图块插入的图签、版本号、视口标签与打印图章；模型空间中仅引用工作文件.7.4. 图框文件图框文件已初始化在出图文件的样板文件中.这样设计师就不需要在出图文件中重复外部引用图框的操作.图框文件的维护由指定设计师负责,这样不会导致图框文件的多个版本. 8. 批量打印8.1. 原则：在保证各种CAD设置参数都标准的情况下,可以使用此功能以减少日常重复性出图打印工作.8.2. 目前状态：我们已在2003年国家游泳中心《水立方》项目中使用此功能.并且在以后的每个项目中都把dsd文件标准化命名,以方便不同的设计师日常批量出图,如下图所示是在水立方项目中我们所制作的批打印列表文件.9. Global scale factor 全局比例因子9.1. 目前状态：线型比例因子在出图文件中,始终保持为"1"并勾选中 "Use Paper Spaceunits for scaling", 线型文件都是在图纸是空间按照1：1设置,在工作文件中则须根据最终的出图比例在Global scale factor值内填入相应图纸比例值.如下图所示：10. DWS 标准文件10.1. 原则：为维护图形文件的一致性,使图层、线型、标注类型、文字类型的出图效果达到统一,提高出图质量.10.2. 目前状态：我们已于2003年国家游泳中心《水立方》项目中使用DWS标准文件功能来控制该项目所有文件的制图标准统一工作,下图为我们当时为每个专业设立的标准文件.11. Page Set Up Change/Import11.1. 原则：提高出图的速度,保证图纸打印的一致性.11.2. 目前状态：我们已在2003年国家游泳中心《水立方》项目中使用打印控制中心来控制所有文件出图时的页面设置,因为页面设置是所有打印参数的集合,它包括打印设备,纸张设置,布局参数.所有命名过的页面设置均保存在一个.dwt 样板文件中,这样可以最高效率的帮助设计师在Publish Import 中锁定需要的页面设置.11.3. 下图为中建##分公司的打印控制中心中页面设置的名称.。
文件英文_精品文档
文件英文Title: Document Management Best Practices: Ensuring Smooth Workflow EfficiencyIntroduction:Efficient management of documents plays a critical role in the success of any organization. Document management involves the creation, distribution, and storage of documents in an organized and easily accessible manner. This document will provide an overview of best practices for managing documents effectively, focusing on the importance of clear file naming conventions, proper folder organization, version control, and security measures to ensure smooth workflow efficiency.I. Clear File Naming Conventions:1. Consistency: Establishing and following consistent file naming conventions are crucial for easy retrieval and organization of documents. Use a standardized format that reflects the content and purpose of the document.2. Descriptive and Meaningful: Choose file names that clearly reflect the content of the document. Avoid using generic terms or ambiguous abbreviations, as these can lead to confusion and difficulty in finding the desired files.3. Use Keywords: Incorporate relevant keywords in the file names to improve searchability. Including dates or project codes within the file names can also aid in categorization and sorting.II. Proper Folder Organization:1. Intuitive Structure: Create a logical and intuitive folder structure to help users navigate through the document repository effortlessly. Consider organizing folders based on projects, departments, or document types.2. Limit Subfolder Depth: Avoid excessively deep hierarchical structures, as they can lead to cumbersome navigation and reduced efficiency. Aim to keep the folder structure simple and easily understandable.3. Avoid Duplication: Discourage the replication of documents across folders. Instead, use shortcuts or symbolic links to keep documents organized in a single location while still making them available in relevant folders.III. Version Control:1. Document Versioning: Implement a systematic version control system to track changes made to documents over time. This allows users to access older versions if needed and ensures the integrity of the document management process.2. Clear Version Naming: Use a clear and consistent naming convention to differentiate between different versions of the same document. Incorporate information such as revision numbers, dates, or initials to avoid confusion.IV. Security Measures:1. Password Protection: Implement password protection measures for sensitive documents to ensure confidentiality and prevent unauthorized access.2. User Permissions: Assign appropriate access rights to different users or groups, limiting access to sensitive or confidential materials. Regularly review and update permissions to maintain data security.3. Backup and Recovery: Regularly back up documents to a secure location to prevent the loss of critical information in case of hardware failure, natural disasters, or other unforeseen events. Implement a robust recovery plan to restore files quickly.Conclusion:Effective document management is essential for maintaining workflow efficiency and ensuring easy access to critical information. By implementing clear file naming conventions, organizing folders logically, establishing version control practices, and implementing security measures, organizations can streamline their document management processes. These best practices not only save time and effort but also enhance collaboration, productivity, and overall operational efficiency. With careful consideration and implementation of these strategies, organizations can establish a document management system that empowers employees and promotes business success.。
关于加强文件格式和规范文件名称的相关要求
英文回答：In order to enhance the robustness of file formats and standardize the nomenclature of files, it is imperative to establish unequivocal guidelines and protocols. This will ensure that all files within an organization are systematically organized and readily accessible. Of particular importance is the delineation of a standardized file naming convention that accurately reflects the content of each file. This convention ought to epass elements such as the date of creation, project appellation, version identification, and any other pertinent details that facilitate file discernment. The implementation of a uniform file naming convention substantially simplifies the task of locating and retrieving essential files for team members. Furthermore, the adoption of a consistent format for file names enhances overall operational efficiency and mitigates the potential for errors during file management.为了提高文件格式的稳健性并使文件名称标准化，必须制定明确的准则和协议。
s57文件命名规则
s57文件命名规则File naming rules may seem like a small detail, but they play a crucial role in organizing and finding information efficiently. 文件命名规则可能看起来是一个小细节，但它在高效组织和查找信息方面起着至关重要的作用。
When it comes to naming S57 files, consistency is key. It is essential to establish a clear and standardized naming convention that everyone in the organization follows. 对于S57文件的命名，一致性至关重要。
建立一个清晰且标准化的命名规范，确保组织中的每个人都遵循。
A good naming convention should include elements such as project name, date, version number, and a brief description of the file contents. 这个良好的命名规范应该包括项目名称、日期、版本号和文件内容简要描述等元素。
By including these elements in the file name, users can easily identify and locate the information they need. 通过在文件名中包含这些元素，用户可以轻松识别并定位他们所需的信息。
Consistent file naming also helps to prevent confusion and errors. When files are named in a structured and systematic way, it reduces the risk of duplicates, outdated versions, or misplaced documents. 一致性的文件命名还有助于防止混乱和错误。
英语作文件异形模板
英语作文件异形模板英文回答：What is a File Upload Template?A file upload template is a predefined structure that specifies the format and content of a file that will be uploaded to a server. It defines the rules for how the file should be structured, what type of data it should contain, and how it should be named. File upload templates help ensure that files uploaded to a server are consistent and follow a standardized format, making them easier to process and store.Benefits of Using a File Upload Template。
Consistency: File upload templates ensure that all files uploaded to a server adhere to the same structure and format, making them easier to work with and analyze.Data Integrity: By defining the type and format of data that should be included in uploaded files, templates help maintain data integrity and prevent inconsistencies or errors.Automation: File upload templates enable the automation of file processing tasks, such as extracting data, validating content, and storing files in a structured way.Error Prevention: By specifying rules for file naming and content, templates help prevent errors and rejected files, leading to a smoother file upload process.How to Create a File Upload Template。
增加人员档案设置的操作步骤 -回复
增加人员档案设置的操作步骤-回复Title: Setting Up Personnel Files: A Step-by-Step GuideIntroduction:Managing employee records is a vital function in any organization. A comprehensive and organized personnel file not only helps streamline administrative processes but also ensures compliance with legal requirements. In this guide, we will walk you through the step-by-step process of setting up an effective personnel file system.I. Understanding the Importance of Personnel FilesBefore diving into the process, it is crucial to comprehend the significance of personnel files. Employee records serve various purposes, including:1. Documentation of Hiring Process: Personnel files chronicle an employee's journey from recruitment to separation, encompassing all essential hiring documents such as resumes, offer letters, employment contracts, and background checks.2. Performance Management: Personnel files provide a comprehensive overview of an employee's performance, including performance reviews, disciplinary actions, and commendations.3. Compliance and Legal Protection: Personnel files serve as a legally defensible record to ensure compliance with variousregulations, such as labor laws, anti-discrimination laws, and privacy laws.II. Defining Organizational RequirementsBefore setting up personnel files, determine the specific requirements and policies of your organization. Consider the following aspects:1. Mandatory Documents: Identify the essential documents that must be included in every personnel file. This may vary depending on local laws, industry norms, and internal policies. Common documents include resumes, employment applications, I-9 forms, tax forms (W-4), and emergency contact information.2. Categorization: Determine how to categorize personnel files to ensure easy access and retrieval. Common categories include employment history, compensation information, performance evaluations, training records, and disciplinary records.III. Establishing a Personnel File SystemNow that we understand the importance of personnel files and have defined organizational requirements, let's move on to setting up the actual file system. Follow these steps:Step 1: Gather Materials and Tools- Collect necessary supplies such as file folders, file labels, dividers, and a secure cabinet or storage area.- Ensure you have access to a computer or cloud-based system for digital recordkeeping (optional but recommended).Step 2: Determine File Naming Convention- Develop a consistent and logical file naming convention to ensure files are easily identifiable. Consider using a combination of employee identification numbers, names, or a standardized format.Step 3: Create Individual Personnel Files- Start by creating a separate file folder for each employee using the predetermined naming convention.- Label each folder with the employee's name, employee identification number, or any other relevant identifier.Step 4: Categorize Files- Divide each employee's file into appropriate categories based on your earlier categorization decision.- Use file dividers and labels to clearly mark each category within the personnel file.Step 5: Organize Mandatory Documents- Place all essential documents, as determined by organizational requirements, into the appropriate categories within each personnel file.- Ensure the documents are filed in chronological order to maintain a systematic record of the employee's history.Step 6: Capture Additional Records- Continuously update the employee's personnel file with relevant documentation throughout their employment tenure. These may include performance evaluations, training certificates, promotions or demotions, disciplinary actions, and any other significant changes.IV. Digital Recordkeeping (Optional)If you choose to maintain digital personnel records, consider the following steps:Step 1: Choose a Secure Electronic System- Evaluate different software options or cloud-based storage services.- Ensure the chosen system meets security standards, data privacy regulations, and provides user-friendly features for searching and accessing files.Step 2: Digitize Existing Paper Records- Scan and upload physical documents into the digital system.- Ensure all necessary metadata, such as employee names and relevant identifiers, are associated with each document.Step 3: Establish a Document Retention Policy- Determine how long each record will be retained in the digital system.- Create a backup and disaster recovery plan to protect against data loss.Conclusion:Establishing an efficient personnel file system is an integral part of HR management. By following this step-by-step guide, organizations can ensure the effective organization and management of employee records, improving compliance, facilitating performance management, and safeguarding legal interests. Remember, personnel files are confidential, and proper security measures must be taken at all times to protect employees' privacy.。
NZQA在线数字提交用户指南说明书
26 May 2022 V1.2Table of contentsIntroduction (1)Before you begin (2)Steps to submit a digital file to NZQA (3)Step 1: Go to the digital submission page for the standard (4)Step 2: Check filename is correct for the student (11)Step 3: Select file(s) for upload (12)Step 4: Review any file matching error messages (16)Step 5: Upload the files (18)Step 6: Upload student files over 200MB (21)Replace student files (26)Submit additional student files (28)Delete student files (32)IntroductionAudience This guide is for anyone who uploads student files to NZQA, using the Digital Submission Upload option in the Provider Login.Topics This document has the following topics:Before you begin 2Steps to submit a digital file to NZQA 3Step 1: Go to the digital submission page for the standard 4Step 2: Check filename is correct for the student 11Step 3: Select file(s) for upload12Step 4: Review any file matching error messages 16Step 5: Upload the files18Step 6: Upload student files over 200MB21Replace student files26Submit additional student files28Before you beginStudent entered You can only upload files for students with an entry submitted to NZQA for that standard.File type Some standards have limited permitted submission file types.The file types accepted for a standard are listed in the AssessmentSpecifications for that standard.The standard’s Assessment Specification can be found on the NZQA website:NCEA standard: https:///ncea/subjects/(under the standard’ssubject page)NZ Scholarship standard: https:///qualifications-standards/awards/new-zealand-scholarship/scholarship-subjects/ .File name To link an uploaded file to the correct student’s entry, the file name must include the student’s NSN and/or name in a specific format.NZQA’s preferred file naming convention is:[School No]-[NSN]-[Standard No].[extension]Example: 0045-345678912-91979.pdfNote: The school number must be padded with leading zeros to 4 digits. Forexample, 0123, 0023, 0004.Other permitted file naming conventions are covered inStep 2: Check filename is correct for the student.Google account If any submitted file is over 200MB, then you need to log in to a Google account to complete the file submission process.If you do not have a Google account, you can create one when prompted on the screen or refer to Google’s instructions on how to create an account.Link:https:///accounts/answer/27441?hl=en&ref_topic=3382296.Steps to submit a digital file to NZQAUpload options There are two NZQA web pages available for uploading student files:•The standard entries page allows multiple students’ files for that standard to be uploaded at a time.•From the standard entries page, an individual student can be selected to open their specific entry page which will only allow that student’s file(s) for the standard to be uploaded.The methods of adding the files, the file requirements and the error messages are the same for both options.Main steps These are the main steps to submit a digital file to NZQA.1 Go to the digital submission page for the standard (page 4).2 Check filename is correct for the student (page 11).3 Select file(s) for upload(page 12).4 Review any file matching error messages (page 16).5 Upload the files (page 18).6 Upload student files over 200MB(page 21).Optional actions These are additional optional actions, after you have submitted a digital file to NZQA.•Replace student files(page 26)•Submit additional student files(page 28)•Delete student files(page 32)Steps Follow the steps below to go to the digital submission page for the standard.1 Open one of these browsers:•Chrome•Firefox•Microsoft Edge.2 Log in to the NZQA Schools’ Provider Login.Full URL link: https:///login/continued3 Click Digital Submission Upload from either the:•School’s Home menu on the left side of the screen•General Security Features on the main part of the screen.continued3 cont’d Result: For the current academic year, a list of the subjects that have entries from your school and accept digital submission files displays.Note: The list also shows the number of standard entries there are for each subject.4 Determine your next step.THEN…know the standard number you want to uploadsubmission files togo to step 5.don’t know the standard number you want to uploadsubmission files togo to step 6.continued5 If you know the standard number, then enter it in the Search by Standard Numberfield and click Search.Result: Students entered in the standard display.continued6 If you do not know the standard number click the subject in the list that contains thestandard that you want to upload files to.Result: Subject’s standards where digital submissions are accepted display.Note: Standards are grouped by year level. The Candidates column shows howmany of your students are entered in the standard.continued7Click the standard you want to upload files to.Result: Students entered in the standard display.8 Review the list of students with entries for the selected standard.Determine your next step.THEN…the student is not listed the PN must submit an updated data file toNZQA to create an entryyou would like to upload files for one specific student go to step 9, then continue to Step 2: Check filename is correct for the student sectionyou would like to upload files for one or more entered students go to Step 2: Check filename is correct for the student sectioncontinued9 Click on a link directly below the student’s name to load the files against one specificstudent only.Note: The link will be:•Upload File if no files have been uploaded•n file uploaded if files have been previously successfully loaded.Result: The Upload files for External Submissions page displays.Step 2: Check filename is correct for the studentIntroduction The 2nd step you need to do is check that the filename is correct for the file that you want to upload.A correct filename will successfully link to the student entry, in preparation forupload.An incorrect filename will return an error and will not be uploaded to NZQA.File namingconventionYou must use one of these file naming conventions for the student’s file:[School No]-[NSN]-[Standard No].[extension]* recommended convention0045-456729012-91979.pdf[NSN].[extension] 456729012.mp3[Surname]-[First name].[extension] Marshall-James.mp3[NSN]-[Surname]-[First name].[extension] 456729012-Marshall-James.mp3School number The school number is your school’s Ministry of Education (MoE) number.If you use your school number in the file name it must be padded with leading zeros to make it 4 digits long. Example: 0123, 0023, 0004.Student name must match exactly If you use a file naming convention that includes the student’s name, then the student name must exactly match the name and case displayed in the student entry. It must also match any spaces shown within the name in student entry. Examples:Foster, Sasha Foster-Sasha.mp4CESARIO PIOTTO, May CESARIO PIOTTO-May.movDe Hoedt Norgrove, Sheree De Hoedt Norgrove-Sheree.avi Smith-Long, Jane Smith-Long-Jane.mtsMcCollum, Amy McCollum-Amy.pdfSmith, T’reik Smith-T’reik.pdfMacDonald, KUSHLA MacDonald-KUSHLA.mp4Step 3: Select file(s) for uploadSelecting Files Check that the file(s) being uploaded are for the correct standard. There are two ways to add files for upload:•Files can be selected by dragging files on to the webpage •Files can be selected by clicking the Add files button.Adding files by drag and drop To drag the files, open your local drive with your file browser and select the file(s) to load.Drag the files on to the webpage area anywhere below the title bar.When the icon changes to a loading symbol then you are in the right place to drop the file(s).Adding files through ‘Add files’ buttonTo add the files through a file browser, click Add files.Navigate to your local drive, select the file(s) and click Open .Note: You can also drag and drop the files across instead of clicking Open .Selecting multiple files in the file browser In the file browser you can select multiple consecutive files by holding down the Shift key and selecting the first file of interest and the last file of interest in the file list in the file browser window.You can select multiple non-consecutive files by holding down the Ctrl key and selecting individual files of interest from the file list in the file browser window.Review messages after adding files The result of adding the file(s) by dragging files on to the webpage or by clicking the Add files button will be the same.The result will be:files cannot be matched to astudent entryan error message will display in themessage panel.files can be matched to more thanone student enteredan error message will display in themessage panel.An example would be using names onlyin the filenames and two students of thesame name are entered in a standard. files are not a permitted file type forthis standardan error message displays under thestudent’s name.files are over 200MB a message displays under the student’sname with a link to load the file bygoogle form.file is successfully matched to anentry and the correct typethe file will show with a message ‘readyto upload’Error messages for file naming errors or the incorrect file type can be downloaded.You have the option to cancel the upload and correct the cause of the error then reload the student file(s), or continue with the upload of ‘ready to upload’ files.Next actionfor a messageUse the table below to see what to do next:files matching student entry errors go to the section Step 4: Review any file matching error messages.files matching more than one entry go to the section Step 4: Review any file matching error messages.files are not a permitted type check the Assessment Specification for the standard on the standard’s subject page on the NZQA website.(https:///ncea/subjects/).files that are larger than 200MB go to the section Step 6: Upload student files over 200MB.files ready to upload go to the section Step 5: Upload files.Note: You can click Cancel upload and clear the list to clear all errors and cancel the files listed as ready to upload.Step 4: Review any file matching error messagesIntroduction File matching error messages are the same whether files are loaded to the page listing all entries to the standard or the page for an individual student’s entry tothe standard.The error message includes the name of the file that triggered the error.File matching error If there are errors encountered during the file upload with the file name(s) or matching the file to a student entry, the message panel will identify the file(s) that contain the error and a brief description of the validation error.Example errors are:•File [filename] doesn’t match with any candidate(s) information on this page. •There are 2 candidates with information matching this file. Please rename the file to make it unique. E.g. include NSN.Go to the section Step 2: Check filename is correct for the student to see examples of the correct use of student names in the file names.If you are uploading a class and at this point notice the entry is missing for one file, then the school PN must add a standard entry for the missing student.Step 4: Review any file matching error messages, continuedExporting the file matching error(s)To export the list of errors, click Export to CSV. Result:Note:This function is useful when there are several errors displayed, as theerror messages will disappear when the upload page is refreshed.Step 5: Upload the filesFiles are ready to upload For files that show as ‘ready to upload’, you must complete the process by uploading the files.Steps Follow the steps below to complete the file(s) upload.1 Click Start Upload.1Result: The file(s) will progress through 3 stages:cont’d1 The Uploading file progress bar displays:2 The Analysing file message displays:3 The File uploaded successfully message displays:Note:If the file upload encountered issues during the upload, then a message displays:Follow the instructions and reattempt the upload, before contacting the NZQA Contact Centre.2 Click the browser refresh button () to view an updated list of the files uploaded.Note: If you used a filename that was not the recommended naming convention, the file will be given a system file name in the recommended format with your schoolnumber, the student’s NSN and the standard number.Step 6: Upload student files over 200MBFiles over 200MB If a file being uploaded is over 200MB, a message will direct you to submit the file via a link which opens a Google form.The Google form will prompt you for the information required by NZQA staff to process the file.Large files are processed separately to minimise security risk to NZQA.Google account To load a submission file via a Google form you must have a Google account. If you do not have a Google account, then you can create one from the link on the Google login screen or refer to the Google online instructions on how to create an account(https:///accounts/answer/27441?hl=en&ref_topic=3382296).Steps Follow the steps below to upload the file using a Google form.1 From the file size message, click on the clicking here link to open the Google form.3 Complete the form.You will need to fill in:•an email address that we can contact you on•your School’s name•your School’s MoE ID (School number)•the student’s name•the student’s NSN•the standard number.4 To upload the files, click the Add File linkResult: A popup window is displayed.5 You can drag the files into the popup window or click Select files from your deviceto use a file explorer to find the student’s file.Result: The file will show in the window.6 Click the Upload button to upload the selected fileResult: The progress bar will display the uploading progress.7 When the file has completed uploading the popup window will close and return you tothe main form.8 Click the Submit button to complete the submission process.Result: A message will display that your Digital Submission Upload response has been recorded.9 Close the tab.This completes the process.Note: The uploaded file will not show against the Standard entry page, but NZQA will receive the information that the file has been uploaded through the google form.Replace student filesDeadline for replacement submission The date of file submission is recorded by the system at the time of upload. All files, whether first submissions or replacements must be submitted by the submission deadline date.ReplacingfilesThe ability to replace a file is dependent on the settings for the standard.a standard does notpermit multiple filesubmissions per studenta new submitted file will replace the existing file.a standard permits multiple files of different types per student a new submitted file will replace an existing file if the new file is the same file type as an existing file.If you want to replace a previously submitted file that is a different type see the Delete student files section for who to contact for assistance.a standard permits multiple files of the same type per student a new submitted file will show as an additional file in the student’s entry page.If you do not want the previous submitted file to be assessed see the Delete student files section for who to contact for assistance.Steps Follow the steps below to replace a file and confirm the replacement file has been uploaded successfully.Note: For this example, a standard that does not permit multiple files is used.1To submit a replacement file for a student with an existing submitted file, follow steps 1 to 6 of submitting a file, with the new file.Result: The file submission web page must show the message File uploadedsuccessfully.Replace student files, continued1 cont’d. Note: At this stage the existing file will also show.2 Click refresh on your browser () to view the new file detailsResult: For standards not permitting multiple file uploads, only one file shows with an upload date of the most recent file upload:Submit additional student filesDeadline for completing submission The date of file submission is recorded by the system at the time of upload. All files, whether first submissions or additional files must be submitted by the submission deadline date.Multiple files permitted You can only submit multiple file(s) for an individual student if the standard permits multiple submission file types.The ability to add multiple files is dependent on the settings for the standard. does not permit multiplefile submissions perstudentthere can only be one file against a student’s entryat any one time.Therefore, a new submission file will overwrite anexisting file.permits multiple files ofdifferent types perstudentthere can only be one file per permitted file typeagainst a student’s entry at any one time.Therefore, a new submission file will replace anexisting file if it is of the same file type.If you want to replace a previously submitted filethat is a different type see the Delete student filessection for who to contact for assistance.permits multiple files ofthe same type perstudentthere can be multiple files of the same type againsta student’s entry at any time.Therefore, a new submission file will load as anadditional file to the existing submitted files in thestudent’s entry page.If you do not want a previously submitted file to beassessed see the Delete student files section forwho to contact for assistance.Steps Follow the steps below to submit additional files and confirm it has been uploaded successfully.Note: For this example, a standard that permits multiple files for different filetypes is used.1 To submit additional file(s) for a student with an existing submitted file, follow theSteps 1 to 6 of submitting a file, with the new file.Result: The file will show as ready to upload, and is a different file type.2 Click Start Upload button.Result: The file submission web page must show the message “File uploaded successfully”.3 Click refresh on your browser () to view the new file details.Result: Both the existing file and the new file will show as loaded.4 On the Candidates Entered in the standard page the file count has increased.Delete student filesDeleting student files There is no current functionality for schools to delete submitted files.To delete a submitted file, the PN must contact NZQA, requesting the file be removed.If it is after the submission deadline, then an explanation must be given. Contact the NZQA call centre or email ******************.nz.。
电子计划审查指南说明书
Customer Electronic Plan Review (ePlans) GuideVersion 2020_0821IntroductionTo help streamline the submittal process, the Building Development Division has established an electronic plan review program (ePlans). Please use the following guide to prepare and submit documents for electronic plan review.Please note:Electronic plan review will not start until fees are paid, and the submittal meets the requirements of this guide. Failure to pay fees or meet requirements of this guide will delay the plan review process.ProjectsProjects listed in Table 1 and 2 must be submitted electronically; paper plan submissions will not be accepted. For all other projects that do not meet the requirements of Table 1 or 2, a paper plan is required. The County reserves the right to require electronic or paper plan submission for any project. Paper plans currently in review shall remain paper submissions until final inspection approval.Submittal ChecklistSubmittals for electronic plan review must meet the minimum requirements below. For assistance, please contact Plan Intake at 703-792-4040 or *********************.Building Development Division (BDD) Forms available here☐ Forms are submitted as individual PDF filesDocuments(GIS Address Validation, Zoning Approval, Site Plans, Plats, Energy Calculations, Structural Calculations, Geotechnical Reports, Truss Submittals, other)☐ Documents meet Credentialing requirements for seal, signature, and date☐ Documents are submitted each as separate PDF filesPlans - General Requirements☐ File names meet the File Naming Convention requirements☐ Plans meet Credentialing requirements☐ Plans include all disciplines in a single PDF file (architectural, mechanical, electrical, plumbing, and structural)☐ PDF files are not password protected☐ PDF does not contain layers or comments☐ Plans with more than 10 sheets have bookmarks listing sheet number and title. For example: A1 First Floor Plan ☐ Plans are in landscape orientation☐ Plans are monochrome, not in color☐ P rovide a 3” x 3” box in the same location each sheet for county review stampCommercial Plans☐ Minimum sheet size is 24” x 30” maximum sheet size is 36” x 48”☐ Plans are to minimum scale 1/8” = 1’-0”. It is preferred that plans are in vector format to allow for measuring☐ Resubmissions include all sheets (complete new set) and Resubmission - Revision Checklist☐ Revisions include only revised sheets and Resubmission - Revision ChecklistResidential Plans(group R-5 single family, townhouse, additions, alterations, repairs, accessory structures, etc.)☐ Minimum sheet size is 8-1/2” x 11” maximum sheet size is 36” x 48”☐ Plans are to minimum scale 1/8” = 1’-0”☐ Plans may be scanned with sheets aligned in landscape orientation☐ Resubmissions include all sheets (complete new set)☐ Revisions include only revised sheets and have changes cloudedCredentialingPlans and documents shall be electronically signed, dated, and sealed in accordance with 18VAC10-20-760 Part C and Policy 1.11. Every sheet in the plan set is required to be sealed, signed, and dated. Any revised sheet should reflect the revision date. SubmittingTo submit Commercial Building Plans, Residential Building Plans, or Residential Stand-alone Trade permits please use the ePortal application found at /eportal. For ePortal user guides, videos, and frequently asked questions click here. To submit via ePortal, you must have an ePortal account.To submit for Commercial Stand-alone Trade permits please email plans and documents up to 30 MB to Plan Intake at*********************. For plans and documents over 30 MB please email Plan Intake at ********************* to request a file sharing link.For assistance, please contact Plan Intake at 703-792-4040 or *********************.File Naming ConventionsFiles for the first submission, resubmissions, and revisions shall be named in accordance with Table 4 below.PaymentsPayments can be made via ePortal (preferred), over the phone by calling 703-792-6930, in person at the county office, or by mailing a check. Payments by mailing a check will delay the plan review process.To pay via ePortal, you must have an ePortal account. To create an ePortal account click here.For assistance, please contact Plan Intake at 703-792-4040 or *********************.Reviewed Documents (Approvals)A copy of the reviewed submittal (BDD Forms, Plans, Documents) with digital County review stamps will be provided electronically to the applicant.Reviewed Documents Required On-site for InspectionsThe applicant shall print the submittal (BDD Forms, Plans, Documents) with digital County review stamps to remain on site for inspection field use. The permit(s) shall be printed and posted at the construction site where it is visible from the public way. For assistance with obtaining the submittal or permit, please contact the Permitting Services at 703-792-6924 or*********************.For assistance with inspections, please contact the Inspections Branch at 703-792-7006.。
ASTER数据简介
ASTER数据简介TERRA卫星于1999年12月从范登堡空军基地发射升空，与太阳同步，从北向南每天上午(AM)飞经赤道上空。
所以TERRA之前也有人称之为上午星（AM-1）。
其设计寿命为5年。
ASTER是美国NASA（宇航局）与日本METI（经贸及工业部）合作并有两国的科学界、工业界积极参与的项目。
它是Terra卫星上的一种高级光学传感器，包括了从可见光到热红外共14个光谱通道，可以为多个相关的地球环境资源研究领域提供科学、实用的卫星数据。
其主要情况介绍如下：一个完整的AST数据由18个文件组成一、Terra卫星的主要参数●轨道：太阳同步，降交点时刻：10:30 am；●卫星高度：705公里；●轨道倾角：98.2±0.15°；●重复周期：16天（绕地球233圈/16天）；●在赤道上相邻轨道之间的距离：172公里；二、ASTER传感器Ⅰ.ASTER传感器有3个谱段：可见光近红外（VNIR）：●波长：3●空间分辨率：15米●辐射分辨率：NE ≤0.5％●绝对辐射精度：±4%●立体成像后视角：27.6°●侧视角：±24°（垂直轨道方向）●瞬时视场：21.3μrad(天底方向)18.6μrad(后视方向)●立体成像基高比：0.6●探测器：5000象元（任意时刻实际使用为4100象元）●扫描周期：2.2msce●MTF：〉0.25（横轨方向）〉0.25（沿轨方向）短波红外（SWIR）●空间分辨率：30米●辐射分辨率：NE ≤0.5％-1.5%●对辐射精度：±4%●侧视角：±8.55°（垂直轨道方向）●瞬时视场：42.6μrad●探测器：2048象元/band●扫描周期：4.398msec●MTF：〉0.25（横轨方向）〉0.20（沿轨方向）热红外（TIR）●空间分辨率：90●辐射分辨率：NE T≤0.3K●侧视角：±8.55°（垂直轨道方向）●瞬时视场：127.8μrad●探测器：10象元/band●扫描周期：2.2msec●MTF：〉0.25（横轨方向）〉0.20（沿轨方向）Ⅱ.扫幅：均为60公里Ⅲ.ASTER主要特征如下：●获取从可见光到热红外谱段范围的地表影像数据；●拥有光学传感器各波段较高的几何分辨率和辐射分辨率；●在单条轨上可以获取近红外立体影像数据。
landsat TM数据命名规则
一、地理云空间下载影像命名规则1、文件夹命名规则：LT51310352009209IKR00LT5——landsat5号卫星；131——条带号；035——行编号；2009——获取日期；209——儒略日；IKR——接站代码；00——产品级别；2、数据命名规则：L5131035_0352*******_B10LLfppprrr_rrrYYYYMMDD_AAAL5——landsat5卫星；131——产品起条带号；035_035——产品起始、截止行号；20090728——日期；B10——第一波段；二、USGS影像命名规则：1、Landsat 7影像命名规则：The file naming convention for Landsat 7 GeoTIFF is as follows: L7fppprrr_rrrYYYYMMDD_AAA.TIF where:L7 = Landsat-7 missionf = ETM+ data format (1 or 2)ppp = starting path of the productrrr_rrr = starting and ending rows of the productYYYYMMDD = acquisition date of the imageAAA = file type:B10 = band 1B20 = band 2B30 = band 3B40 = band 4B50 = band 5B61 = band 6L (low gain)B62 = band 6H (high gain)B70 = band 7B80 = band 8MTL = Level-1 metadataTIF = GeoTIFF file extension2、其他Landsat影像命名规则：The file naming convention for other Landsat GeoTIFF is as follows: LTNppprrrOOYYDOY10_AA.TIF where:LT = Landsat Thematic MapperN = satellite number.This should be validated against the satellite field if used exclusively ppp = starting path of the productrrr = starting row of the productOO = WRS row offset (set to 00)YY = last two digits of the year of acquisitionDOY = Julian date of acquisition1 = instrument mode0 = instrument multiplexor (MUX)AA = file type:B1 = band 1B2 = band 2B3 = band 3B4 = band 4B5 = band 5B6 = band 6B7 = band 7TIF = GeoTIFF file extension。
日本葵花卫星资料
3. Map Projection Method For Himawari Standard Data, Normalized Geostationary Projection is adopted as defined
in LRIT/HRIT Global Specification 2 Section 4.4. The projection describes the view from the satellite to an idealized earth.
576
2,880
2,880
Figure 1 Himawari-8 and -9 scan images on a timeline -3-
Table 3 Himawari-8 and -9 observation areas and numbers of pixels
Observation area
10.4
14
11.2
15
12.3
16
13.3
-1-
2. Observation Areas Himawari-8 and -9 will each carry an Advanced Himawari Imager (AHI) scanning five
areas: Full Disk (images of the whole Earth as seen from the satellite), the Japan Area (Regions 1 and 2), the Target Area (Region 3) and two Landmark Areas (Regions 4 and 5). While the scan ranges for Full Disk and the Japan Area will be preliminarily fixed, those of the Target Area and Landmark Areas will be flexible to enable prompt reaction to meteorological conditions. At the beginning of Himawari-8’s operation, Landmark Area data will be used only for navigation, and are not intended for use as satellite products. In the future, JMA plans to use Region 5 for observation of phenomena such as rapidly developing cumulonimbus clouds and to provide the resulting data to users. In each 10-minute period, the AHI will scan the Full Disk once, the Japan Area and Target Area four times, and the two Landmark Areas twenty times. These 10-minute divisions are basic units of an observation schedule called a timeline. In Himawari-8 and -9’s baseline observation, the timeline will be repeated every 10 minutes except in their housekeeping operation.
OceanSurfaceCurrentAnalysis（OSCAR）ThirdDegree...
Ocean Surface Current Analysis (OSCAR) Third Degree Resolution User’s HandbookCopyright 2009 California Institute of Technology.All rights reserved.TABLE OF CONTENTSDATA PRODUCT ABSTRACT (1)1. INVESTIGATOR’S NAME AND CREDIT (1)2. DATA DESCRIPTION (1)2.1 FILENAMING CONVENTION (1)2.2 FILE FORMAT (1)2.3 TEMPORAL COVERAGE AND RESOLUTION (1)2.4 SPATIOAL COVEAGE AND RESOLUTION (2)2.5 DATA PARAMETERS AND FORMAT (2)2.6 SAMPLE DATA RECORD (3)2.7 SAMPLE GLOBAL ATTRIBUTES (4)3. AVAILABLE READ SOFTWARE (4)4. PROCESSING METHODS (4)5. CALIBRATION INFORMATION (5)6. SOURCES OF ERROR (5)7. KNOWN PROBLEMS (5)8. DIFFERENCES BETWEEN 1/3° AND 1° OSCAR (6)9. REFERENCES (6)10. ACRONYMS (7)11. CONTACT INFORMATION (8)12. DOCUMENT INFORMATION (8)13. ACKNOWLEDGEMENTS (8)DATA PRODUCT ABSTRACTThis product contains global near-surface current estimates, derived using quasi-linear and steady flow momentum equations. The horizontal velocity is directly estimated from sea surface height, surface vector wind and sea surface temperature, these data were collected from various satellites and in situ instruments (see processing methods). The model formulation combines geostrophic, Ekman and Stommel shear dynamics, and a complementary term from the surface buoyancy gradient [1].The ocean surface velocity files are in netCDF format which contain zonal (u) and meridional (v) velocitiesINVESTIGATOR’S NAME AND CREDITThe OSCAR product was developed by Gary Lagerloef, Fabrice Bonjean andKathleen Dohan from Earth and Space Research (ESR).If you use OSCAR data in publications, please include the following citation:The OSCAR data were obtained from JPL Physical Oceanography DAAC anddeveloped by ESR.Also, ESR would appreciate receiving a preprint and/or reprint of publicationsutilizing these data for inclusion in the OSCAR bibliography. These publications should be sent to:OSCAR Project OfficeEarth and Space Research2101 Fourth Avenue, Suite 1310Seattle, WA 98121DATA DESCRIPTIONFILENAMING CONVENTIONThe file names have a naming convention of oscar_velNNNN.ncoscar – name of productvel – velocity product calculated from altimetry, scatterometer winds, and sst.NNNN – year of the data or a single day’s worth of data with NNNN thenumber of days since October 5, 1992FILE FORMATThe data are in NetCDF files and have a maximum size of 480 MB whenzipped.TEMPORAL COVERAGE AND RESOLUTIONOne file consists of an entire year’s worth of data, except for the present year.The time resolution within each file is 1/72 year ≈ 5 days, or half a Jason-1 or TOPEX/Poseidon cycle. For the present year, data are added as it comes in. SPATIAL COVERAGE AND RESOLUTIONThe data covers -80° to 80° latitude and 0° to 360° longitude. However thedata represents longitude as 20° to 420°, i.e. the entire Earth is representedin the data as 20° to 380°, and the data repeats itself from 380.33° to 420°.Thus 390° is actually 30°. This range for longitude was chosen so that themajor ocean basins would not be broken, but continuous.The resolution is 1/3° in each direction.DATA PARAMETERS AND FORMATLatitudeDefinition: LatitudeDimension: 481Unit: degrees NorthElement type: doubleLongitudeDefinition: LongitudeDimension: 1201Unit: degrees EastElement type: doubleTimeDefinition: TimeDimension: 72Unit: days since 1992-10-05 00:00:00Element type: integerYearDefinition: Time in yearsDimension: 72Unit: time in fractional yearElement type: floatDepthDefinition: DepthDimension: 1Unit: metersElement type: floatUmDefinition: Ocean surface Zonal currents maximum maskDimension: time, depth, latitude, longitudeUnit: m/sElement type: doubleVmDefinition: Ocean surface Meridional currents maximum maskDimension: time, depth, latitude, longitudeUnit: m/sElement type: doubleUDefinition: Zonal VelocityDimension: time, depth, latitude, longitudeUnit: m/sElement type: doubleMissing value: nanVDefinition: Meridional VelocityDimension: time, depth, latitude, longitudeUnit: m/sElement type: doubleMissing value: nanSAMPLE DATA RECORDThese data are from oscar_vel2008.nclatitude = 80, 79.6666666666667, 79.3333333333333, 79,78.6666666666667longitude = 20, 20.3333333333333, 20.6666666666667, 21,21.3333333333333time = 5566, 5571, 5576, 5581, 5586year = 2008, 2008.014, 2008.027, 2008.041, 2008.055depth = 15um = nan, nan, nan, nan, nanvm = nan, nan, nan, nan, nanu = nan, nan, nan, nan, nanv = nan, nan, nan, nan, nanSAMPLE GLOBAL ATTRIBUTESThese global attributes come from oscar_vel2008.nc.:VARIABLE = "Ocean Surface Currents" ;:DATATYPE = "1/72 YEAR Interval" ;:DATASUBTYPE = "unfiltered" ;:GEORANGE = "20 to 420 -80 to 80" ;:PERIOD = "Jan.01,2008 to Dec.26,2008" ;:year = "2008" ;:description = "OSCAR Third Degree Sea Surface Velocity" ;:CREATION_DATE = "18:41 24-Mar-2009" ;:version = 2009.f ;:source="GaryLagerloef,ESR(*************)andKathleenDohan,ESR (**************)";:contact="KathleenDohan(**************)orJohnT.Gunn(************)";:company = "Earth & Space Research, Seattle, WA" ;:reference = "Bonjean F. and G.S.E. Lagerloef, 2002 ,Diagnostic model and analysis of the surface currents in the tropical Pacific ocean, J. Phys.Oceanogr., 32, 2,938-2,954" ;AVAILABLE READ SOFTWARERead software are available from PO.DAAC’s anonymous ftp site for IDL and Matlab at /pub/ocean_currents/OSCAR/software.Unidata also has software available to read NetCDF files with the ncdump command at /downloads/netcdf/index.jsp PROCESSING METHODSThe near-surface velocity is directly derived from sea surface height (ssh),wind stress (τ) and sea surface temperature (sst). It is the sum of the geostrophic, Ekman-Stommel and thermal wind currents, whereg – gravity accelerationζ - sea surface displacementh – depthθ - buoyancy forceτ - wind stressA – eddy viscosityU’ – vertical shear.The total velocity is the vertical average over a surface layer thickness of 30 m [2].The data used to calculate the velocity are:- TOPEX/POSEIDON, Jason-1, Jason-2, ERS1-2, GFO and ENVISAT ssh anomalies, merged into a gridded product (AVISO). An absolute ssh product is obtained by adding to the anomalies a mean dynamic topography which is a combined product recovering 7 years(1993-1999) based on GRACE mission, altimetry and in situ data (hydrologic and drifters data)[2], [3]- wind velocity from SSM/I [4] October 1992 to July 1999 and QScat [5] August 1999 to present.- sst from weekly Reynolds Smith O.I.v2 [6].The altimeter data are initially gridded on a “Mercator” grid (variable, from1/3°x1/3° at the equator to higher latitude resolution poleward), and horizontal gradients are calculated onto a 1/3°x1/3° grid with a temporal sampling of ≈5 days. Winds and sst are on the same temporal and 1/3°x1/3° grid as described above.For more detailed information on the processing methods refer to Bonjean and Lagerloef 2002 [1] and /methodology.html.CALIBRATION INFORMATIONValidation information on this product can be found in Johnson et al. 2007 [7]. Note: since the Johnson et al. (2007) article was published, a new OSCAR dataset corresponding to the one described on this web page has been released with significant improvements, notably the implementation of the new AVISO merged altimetry product (2006) into the OSCAR processing. Updated validation results can be found at /~bonjean/oscar/global_validation/ .SOURCES OF ERRORThis section only concerns the source datasets used to estimate surface velocity. High winds and rain can cause anomalous readings in SSM/I and QScat. Errors in the satellite altimetry product can come from residual orbit errors and long wavelength errors. All gridded products are also subject to formal mapping errors. KNOWN PROBLEMSThese near-surface currents are estimated through a simplified diagnostic model of the surface circulation. Notably, local acceleration and non-linearities are not represented. As shown in [7], the present velocity field is best used for description of large scale and low frequency variations of surface flow (T>=20 days, L>=5°longitude). ESR currently provides the scientific community with an unfiltered velocity field (no post-processing), on a 1/3° X 1/3° grid with a 5 day resolution. Smoothing may have been induced only by the processing of the source data, that is ssh [2], W [4,5] and sst [6]; also some smoothing inherent to the method itself was caused by calculation of spatial gradient (for geostrophic and thermal-wind currents only). When comparing OSCAR to the drifter data, smoothing can also just be implied by the interpolation from the 1/3° X 1/3° per 5-day grid to the drifter locations and times. This sort of indirect smoothing effect is lessened in the 1/3°OSCAR from the 1° OSCAR product. ESR encourages researchers to make comparisons between this velocity field and in-situ observations on meso to short scales. As this surface current estimation is a work in progress, we are interested in any result involving the present velocity field, and we remain available for any help and discussion.DIFFERENCES BETWEEN 1/3° AND 1° OSCARSurface currents are extended closer to the coasts in the 1/3° than 1° OSCAR. The Maximum Mask velocity (Um, Vm) is the maximum possible extent of the data per day. The data, given in U and V, are confined by the spatial extent of all satellite data on each day. The Maximum Mask velocity uses the geostrophic component for velocity at all points, along with the buoyancy-driven and wind-driven components, where they are available. This is done since sea surface height satellite data extends closer to the coast than wind and temperature at some locations, and the geostrophic component is an order of magnitude larger than the other components outside of the equator. This field is intended for testing purposes only.The model for equatorial velocities has been changed. The equatorial solution is now used within +/- 5 degrees of the equator. The turbulence parameterization is modified to blend from equatorial empirical values to global empirical values.The method for calculating gradients has also been changed to suit the higher resolution data, and produces much better comparisons with in situ data.A filtered velocity is not available in the 1/3° product since the 1° OSCAR filtered velocity is still provided.Velocities over 3m/s are removed without any further processing.REFERENCES1. Bonjean, F., and G. S. E. Lagerloef, 2002. Diagnostic model and analysis ofthe surface currents in the tropical Pacific Ocean. J. Phys. Oceanogr., vol.32, pg. 2938-2954./documents/bonjean/bl2002/bl2002.pdf2. SALP-MU-P-EA-21065-CLS, Edition 1.9, June 2008 Ssalto/Duacs UserHandbook : (M)SLA and (M)ADT Near-Real Time and Delayed TimeProducts(/fileadmin/documents/data/tools/hdbk_duacs.pdf )3. Rio, M. H. and F. Hernandez, 2004. A mean dynamic topography computedover the world ocean from altimetry, in situ measurements, and a geoidmodel. J. Geophys. Res., 109, C12032, doi:10.1029/2003JC002226.4. Atlas, R., R. Hoffman, S. Bloom, J. Jusem, and J. Ardizzone, 1996. A multi-year global surface wind velocity dataset using SSM/I wind observations.Bull. Amer. Meteor. Soc., vol. 77, pg. 869-882.5. Pegion, P. J., M. A. Bourassa, D. M. Legler, and J. J. O'Brien, 2000:Objectively-derived daily "winds" from satellite scatterometer data. Mon.Wea. Rev., 128, 3150-3168.(/scatterometry/Qscat/gcv_glob_L2B_1x1.html ) 6.Reynolds, R.W., N.A. Rayner, T.M. Smith, D.C. Stokes, and W. Wang.2002. An Improved In Situ and Satellite SST Analysis for Climate. J. Clim.vol. 15, pg. 1609-1625.(/research/cmb/sst_analysis/)7. Johnson, E. S., F. Bonjean, G. S. E. Lagerloef, and J. T. Gunn, 2007.Validation and error analysis of OSCAR sea surface currents. J. Atm.Ocean. Tech., vol. 24, pg. 688-701.ACRONYMSAVISO Archiving, Validation and Interpretation of SatelliteOceanographic dataCHAMP Challenging Mini-Satellite Payload for Geophysical Researchand ApplicationDh Dynamic heightESR Earth and Space ResearchGDR Geophysical Data RecordGRACE Gravity Recovery and Climate ExperimentJPL Jet Propulsion LaboratoryNetCDF Network Common Data FormOSCAR Ocean Surface Current AnalysisPO.DAAC Physical Oceanography Distributed Active Archive Center QScat QuikSCAT- Quick ScatterometerSSH Sea Surface HeightSSM/I Special Sensor Microwave ImagerSST Sea Surface TemperatureWOA World Ocean AtlasCONTACT INFORMATIONQuestions or comments about this data product should be directed via email to the PhysicalOceanographyDAAC:*****************.DOCUMENT INFORMATIONJessica Hausman, PO.DAACFabrice Bonjean, ESRKathleen Dohan, ESRMay 2009ACKNOWLEDMENTSThe research described in this handbook was carried out at Earth Space Research and written at the Jet Propulsion Laboratory, California Institute of Technology, under a contract with the National Aeronautics and Space Administration and the National Oceanic and Atmospheric Administration.。