Durability problems with explicit instruction in an EFL context： the learning of the English co

同义词假设中⼼假定使脱离合作反弹有活⼒的许多的，⽆数的收获，获得重要的，最终的提⾼潜能产⽣负⾯消级的具体的，特定的获得证实招聘有能⼒的使认知，通知主要的流利，⼝齿伶俐令⼈痛苦的解决努⼒提炼，提⾼新⼿合⼀的，整体的统⼀性实施标准，规范消逝谴责可获得的批准，同意接受，采纳暂时的逆境，困难赞助成熟的保证结果在…之前避难所Hypothesis supposition proposition assumption postulation Hub center core nucleus pivot Posit postulate speculate hypothesizeDisengage unfasten unlock untie extricateCollaborate cooperate pool resourcesRebound spring back recoil bounce backVigorously dynamically robustly spiritedlyMyriad countless innumerable uncountable numerous Harvest reap ingather gather obtain Ultimate eventual crucial essential imperativeEnhance heighten improve boostPotential capacity capabilityEngender produce cause bring about generateNegative unconstructive undesirable destructive adverse Specific particular definite identifiable Secure acquire capture procureConfirm verify substantiate back upRecruitment staffing employment enlistmentCompetent capable skilled adeptAcquaint familiarize notify informPrimarily chiefly mainly principally predominantly Eloquence facility glibnessTraumatic shocking distressing upsettingResolve solve settle come to a decisionStrive endeavor do one’s utmost go all outHone refine polish enhanceNovice apprentice greenhornUnification fusion integrationUniformity standardization samenessEnforce implement carry outCriterion form norm benchmark yardstickElapse lapse go by slip awayDenunciation condemnation censure criticism scolding Available obtainable accessible on hand Ratify approve endorse consentEmbrace accept supportProvisional interim makeshiftAdversity hardship misfortuneSponsor subsidizeMature developed established advanced Warrant guarantee pledgeConsequence result outcome upshot aftermath Precede lead heraldShelter refuge haven asylum sanctuary严重的模型住房阻碍包括⽬标，意图⽆与伦⽐的环绕凹的(凸的)破坏古代忍耐⼒迷信宣告分离使…容易运⽤摆动使…固定批评，评估调解，商谈偏见根本的深刻的改变把…嵌⼊语境，环境壮观的强调多样性反对的完整的导⼊，开端拘留使⼊迷引⽤，提及实⽤的标明，指出多样的⾼级的定界限，划分领域促进，怂恿⼴泛性Severely harshly sternly strictly rigorouslyPrototype archetype exemplarDwelling abode lodging residenceObstruction obstacle barrier impediment hindrance Incorporate contain encompass assimilateIntent intention target goal objective purpose Unparalled unmatched matchless incomparableEnclose encircle enfoldConcave hollow dished curved in (convex)Disrupt upsetAntiquity bygone days time immemorialDurability permanence endurance indestructibility Superstition irrational beliefProclamation declaration assertionDiscrete separate disconnected detachedFacilitate smooth simplify expediteDeploy arrange implementSway suspendAnchor fasten attach affix moorCritique review criticism evaluationMediate reconcile negotiate intercedeBias prejudice partiality preferenceRadical fundamental profound fanatical revolutionary Transformation alternation conversion revolutionaryEmbed implant insert set inContext setting circumstances milieu environment Spectacular stunning impressive magnificent dazzling breathtaking marvelousHighlight emphasize underline underscore draw attention to Diversity variety multiplicityContradictory opposing clashing conflicting incongruousRun-up introduction lead-in preamble preface prelude Imprint impression stamp Captivity imprisonment confinement detentionFascinate captivate charm enthrall entice allureCite quote allude toFunctional operational serviceableDesignate tile entitle termMultifarious diverse diversified varied miscellaneous Senior leading chief superior Demarcate delineate delimit define mark outDomain area field sphere realm territoryInstigate prompt initiate activate set offCatholicism catholicity universally下降恢复悲伤主张维护坚持⽀持破坏有毒的繁殖腐朽的窒息陡峭的释放死亡游说，请愿含糊的意思史前显⽰标明对⽴的特殊阐明摘要，典型和谐统⼀清楚地阐明混乱的更改，调整难以理解的提供卓越的，杰出的占优势的渴望，劲头使开始从事对⼿残留的明晰的丑闻商店诱拐劫持绑架折磨狂怒的撤退慎重的在价值上超过Decline drop fall decrease decay dwindle diminish Recovery restoration mending renewal recuperation Lament mourn grieve (over/for) weep wailAssert insist emphasize stress affirm aver avow Uphold support sustain endorse advocateBreach break crack open ruptureToxic poisonous contaminated noxious lethal deadly Reproduction breeding procreation propagationDegraded decayed corrupted worsenedSuffocate choke smother stifle throttlePrecipitous steep abrupt verticalRelease liberate emancipatePerish die deceaseLobby petition sway opinionObscurity oblivion murkiness ambiguousnessPrehistoric primeval primitive primordialManifestation exhibition expression indication demonstration Opposing opposite contrasting conflicting divergent contradictoryElaborate expound particularizeEmbodiment epitome incarnation quintessenceConcord harmony accord unityFormulate frame verbalize voice articulateChaotic muddled tumultuousModify adapt adjust amend refashion reviseElusive indefinable intangible obscureRendition renderingPreeminent eminent prominent distinguished prestigious exalted outstandingDominant prevailing governing predominant preponderate Avidly keenly enthusiastically passionately ardently fervently Launch initiate commence unleash inaugurateRival adversary contenderResidual lingeringExplicit obvious unequivocal perspicuous overt manifest Scandal disgrace dishonor shame humiliationOutlet retailer channelAbduct kidnap take hostage take prisonTorture torment afflict brutalize mistreatFurious livid fuming infuriatedRetreat withdrawal hideawayStrategic deliberate premeditatedOutweigh overshadow prevail over dwarf裂缝引发占主导地位渗透变形散发，散发物撤退巨⼤的有能⼒的下降缺乏节奏证实，核实分别的灾变严重的经受住贪婪的消灭，遮盖剩余物使⼊迷利⽤稳定的不现实的显⽰揭⽰传递使信服请求委员紧紧抓住差异，不⼀致推断强加接连发⽣的塞得过满标记显著的，突出的重要的挥霍的丰富的免费的诺⾔保证危险⼀团Fissure crevice cleftTrigger activate set off generate producePredominant prevail dominate outweigh preponderate Saturate soak drench marinate steep Deformation distortion twist disfigurementEmission release discharge emanationEvacuation removal withdrawal retreat exodusImmense vast enormous gigantic colossalProficient capable adept competentDecline deterioration decay degenerationScarcity lack shortage paucity insufficiencyRhythm tempo cadenceVerify authenticate confirm validate substantiate attest Respectively individually singly separately Cataclysm catastrophe calamityGrave serious severe momentous crucialWithstand endure survive tolerate weatherGreedy avaricious covetous desirous materialistic Obliterate demolish eliminate eradicate abolish Remnant residueCaptivate attract fascinate enchant charmHarness utilize exploitSteady stable constant perpetual ceaselessImpractical unfeasible unworkable unusableUnveil reveal disclose uncover unwrapTransmit convey transfer transport deliverConvince persuade sway win over prevail uponSolicit petition implore lobbyCommissioner official officer administratorGrip clasp clutch seizeDiscrepancy difference inconsistency incongruity divergence Extrapolate infer reason deduce conclude Impose inflict force foistEnsuing subsequent compact compress squeeze Overstuffed brimming overflowingInsignia emblem badgeSalient striking noticeable prominentlyCrucial vital critical pivotal essentialExtravagant overgenerous spendthrift lavishAmple plentiful abundant bounteous copious Complimentary free gratis on the housePledge vow oath assuranceHazard danger peril risk menace threatClot congeal solidify thicken叙述，描述致命的事件⿇烦瑕疵着迷的，上瘾的猎物有侵略性的敬畏，崇敬神圣的仪式窒息残害，实施暴⼒⼝头上的主导的，流⾏的压迫，征服构想，设想破坏公共物品唤起，引起……苗条的象征Recount tell relate narrate describeFatal lethal mortal disastrous ruinousEpisode incident occurrence eventPlague trouble pester agitate vex perturbDefect flaw imperfection blemishFanatical obsessive fervent passionate addicted frenzied Prey quarry victim Aggressive bellicose belligerent hostile assertive uncompromising Revere hold in the highest regard worship venerateSacred holy hallowed consecrated revered sanctifiedRite ritual sacramentSuffocate smother choke stifle throttle snuff out。

DIRECTIVESCOMMISSION DIRECTIVE 2010/26/EUof 31 March 2010amending Directive 97/68/EC of the European Parliament and of the Council on the approximation of the laws of the Member States relating to measures against the emission of gaseous and particulate pollutants from internal combustion engines to be installed in non-road mobile machinery(Text with EEA relevance)THE EUROPEAN COMMISSION, Having regard to the Treaty on the Functioning of the European Union,Having regard to Directive 97/68/EC of 16 December 1997 of the European Parliament and of the Council on the approxi ­mation of the laws of the Member States relating to measures against the emission of gaseous and particulate pollutants from internal combustion engines to be installed in non-road mobile machinery ( 1 ), and in particular Articles 14 and 14a thereof, Whereas:(1) Article 14a of Directive 97/68/EC sets out the criteria and the procedure for extending the period referred to in Article 9a(7) of that Directive. Studies carried out in accordance with Article 14a of Directive 97/68/EC show that there are substantial technical difficulties to comply with stage II requirements for professional use, multi- positional, hand-held mobile machinery in which engines of classes SH:2 and SH:3 are installed. It is therefore necessary to extend the period referred to in Article 9a(7) until 31 July 2013. (2) Since the amendment of Directive 97/68/EC in 2004, technical progress has been made in the design of diesel engines with a view to make them compliant with the exhaust emission limits for stages IIIB and IV. Electronically controlled engines, largely replacing me- chanically controlled fuel injection and control systems, have been developed. Therefore, the current general type- approval requirements in Annex I to Directive 97/68/EC should be adapted accordingly and general type-approval requirements for stages IIIB and IV should be introduced. (3) Annex II to Directive 97/68/EC specifies the technical details of the information documents that need to be submitted by the manufacturer to the type-approval authority with the application for engine type-approval. The details specified regarding the additional anti- pollution devices are generic and should be adapted to the specific after-treatment systems that need to be used to ensure that engines comply with exhaust emission limit stages IIIB and IV. More detailed information on the after-treatment devices installed on the engines should be submitted to enable type-approval authorities to assess the engine’s capability to comply with stages IIIB and IV.(4) Annex III to Directive 97/68/EC sets out the methodtesting the engines and determining their level of emissions of gaseous and particulate pollutants. The type-approval testing procedure of engines to demon ­strate compliance with the exhaust emission limits of stage IIIB and IV should ensure that the simultaneous compliance with the gaseous (carbon monoxide, hydro ­carbons, oxides of nitrogen) and the particulate emission limits is demonstrated. The non-road steady cycle (NRSC) and non-road transient cycle (NRTC) should be adapted accordingly. (5) Point 1.3.2 of Annex III to Directive 97/68/EC foreseesthe modification of the symbols (section 2.18 of Annex I), the test sequence (Annex III) and calculation equations (Appendix III to Annex III), prior to the introduction of the cold/hot composite test sequence. The type approval procedure to demonstrate compliance with the exhaust emission limits of stage IIIB and IV requires the intro ­duction of a detailed description of the cold start cycle. (6) Section 3.7.1 of Annex III to Directive 97/68/EC sets out the test cycle for the different equipment specifications. The test cycle under point 3.7.1.1 (specification A) needs to be adapted to clarify which engine speed needs to be used in the type approval calculation method. It is also necessary to adapt the reference to the updated version of the international testing standard ISO 8178-4:2007.( 1 ) OJ L 59, 27.2.1998, p. 1.(7) Section 4.5 of Annex III to Directive 97/68/EC outlines the emissions test run. This section needs to be adapted to take account of the cold start cycle. (8) Appendix 3 of Annex III to Directive 97/68/EC sets out the criteria for the data evaluation and calculation of the gaseous emissions and the particulate emissions, for both the NRSC test and the NRTC test set out in Annex III. The type approval of engines in accordance with stage IIIB and IV requires the adaptation of the calculation method for the NRTC test. (9) Annex XIII to Directive 97/68/EC sets out the provisions for engines placed on the market under a ‘flexible scheme’. To ensure a smooth implementation of stage IIIB, an increased use of this flexibility scheme may be needed. Therefore, the adaptation to technical progress to enable the introduction of stage IIIB compliant engines needs to be accompanied by measures to avoid that the use of the flexibility scheme may be hampered by notifi ­cation requirements which are no longer adapted to the introduction of such engines. The measures should aim at simplifying the notification requirements and the reporting obligations, and at making them more focused and tailored to the need for market surveillance authorities to respond to the increased use of the flexi ­bility scheme that will result from the introduction of stage IIIB. (10) Since Directive 97/68/EC provides for the type-approval of stage IIIB engines (category L) as from 1 January 2010 it is necessary to provide for the possibility to grant type approval from that date. (11) For reasons of legal certainty this Directive should enter into force as a matter of urgency. (12) The measures provided for in this Directive are in accordance with the opinion of the Committee estab ­lished in Article 15(1) of Directive 97/68/EC, HAS ADOPTED THIS DIRECTIVE: Article 1 Amendments to Directive 97/68/EC Directive 97/68/EC is amended as follows: 1. in Article 9a(7), the following subparagraph is added: ‘Notwithstanding the first subparagraph, an extension of the derogation period is granted until 31 July 2013, within the category of top handle machines, for professional use, multi- positional, hand-held hedge trimmers and top handle tree service chainsaws in which engines of classes SH:2 and SH:3 are installed.’;2. Annex I is amended in accordance with Annex I to this Directive;3. Annex II is amended in accordance with Annex II to this Directive;4. Annex III is amended in accordance with Annex III to this Directive;5. Annex V is amended in accordance to Annex IV to this Directive;6. Annex XIII is amended in accordance with Annex V to this Directive.Article 2Transitional provisionWith effect from the day following the publication of this Directive in the Official Journal, Member States may grant type-approval in respect of electronically controlled engines which comply with the requirements laid down in Annexes I, II, III, V and XIII to Directive 97/68/EC, as amended by this Directive.Article 3Transposition1. Member States shall bring into force the laws, regulations and administrative provisions necessary to comply with the Directive within 12 months after the publication of the Directive. They shall forthwith communicate to the Commission the text of those provisions.They shall apply those provisions from 31 March 2011.When Member States adopt those provisions, they shall contain a reference to this Directive or be accompanied by such a reference on the occasion of their official publication. Member States shall determine how such reference is to be made.2. Member States shall communicate to the Commission the text of the main provisions of national law which they adopt in the field covered by this Directive.Article 4Entry into forceThis Directive shall enter into force on the day following its publication in the Official Journal of the European Union .Article 5AddresseesThis Directive is addressed to the Member States. Done at Brussels, 31 March 2010. For the Commission The President José Manuel BARROSOANNEX IThe following section 8 is added to Annex I to Directive 97/68/EC:IIIBIVSTAGESANDFOR‘8. TYPEAPPROVALREQUIREMENTS8.1. This section shall apply to the type-approval of electronically controlled engines, which uses electronic control todetermine both the quantity and timing of injecting fuel (hereafter “engine”). This section shall apply irrespective of the technology applied to such engines to comply with the emission limit values set out in sections 4.1.2.5 and 4.1.2.6 of this Annex.8.2. DefinitionsFor the purpose of this section, the following definitions shall apply:8.2.1. “emission control strategy” means a combination of an emission control system with one base emission controlstrategy and with one set of auxiliary emission control strategies, incorporated into the overall design of an engine or non-road mobile machinery into which the engine is installed.8.2.2. “reagent” means any consumable or non-recoverable medium required and used for the effective operation of theexhaust after-treatment system.8.3. Generalrequirements8.3.1. Requirements for base emission control strategy8.3.1.1. The base emission control strategy, activated throughout the speed and torque operating range of the engine,shall be designed as to enable the engine to comply with the provisions of this Directive8.3.1.2. Any base emission control strategy that can distinguish engine operation between a standardised type approvaltest and other operating conditions and subsequently reduce the level of emission control when not operating under conditions substantially included in the type approval procedure is prohibited.8.3.2. Requirements for auxiliary emission control strategy8.3.2.1. An auxiliary emission control strategy may be used by an engine or a non-road mobile machine, provided thatthe auxiliary emission control strategy, when activated, modifies the base emission control strategy in response toa specific set of ambient and/or operating conditions but does not permanently reduce the effectiveness of theemission control system:(a) where the auxiliary emission control strategy is activated during the type approval test, sections 8.3.2.2 and8.3.2.3 shall not apply;(b) where the auxiliary emission control strategy is not activated during the type approval test, it must bedemonstrated that the auxiliary emission control strategy is active only for as long as required for thepurposes identified in section 8.3.2.3.8.3.2.2. The control conditions applicable to this section are all of the following:(a) an altitude not exceeding 1 000 metres (or equivalent atmospheric pressure of 90 kPa);(b) an ambient temperature within the range 275 K to 303 K (2 °C to 30 °C);(c) the engine coolant temperature above 343 K (70 °C).Where the auxiliary emission control strategy is activated when the engine is operating within the control conditions set out in points (a), (b) and (c), the strategy shall only be activated exceptionally.8.3.2.3. An auxiliary emission control strategy may be activated in particular for the following purposes:(a) by onboard signals, for protecting the engine (including air-handling device protection) and/or non-roadmobile machine into which the engine is installed from damage;(b) for operational safety and strategies;(c) for prevention of excessive emissions, during cold start or warming-up, during shut-down;(d) if used to trade-off the control of one regulated pollutant under specific ambient or operating conditions, formaintaining control of all other regulated pollutants, within the emission limit values that are appropriate forthe engine concerned. The purpose is to compensate for naturally occurring phenomena in a manner thatprovides acceptable control of all emission constituents.8.3.2.4. The manufacturer shall demonstrate to the technical service at the time of the type-approval test that theoperation of any auxiliary emission strategy complies with the provisions of section 8.3.2. The demonstration shall consist of an evaluation of the documentation referred to in section 8.3.3.8.3.2.5. Any operation of an auxiliary emission control strategy not compliant with section 8.3.2 is prohibited.8.3.3. Documentation requirements8.3.3.1. The manufacturer shall provide an information folder accompanying the application for type-approval at thetime of submission to the technical service, which ensures access to any element of design and emission control strategy and the means by which the auxiliary strategy directly or indirectly controls the output variables. The information folder shall be made available in two parts:(a) the documentation package, annexed to the application for type-approval, shall include a full overview of theemission control strategy. Evidence shall be provided that all outputs permitted by a matrix, obtained fromthe range of control of the individual unit inputs, have been identified. This evidence shall be attached to theinformation folder as referred to in Annex II;(b) the additional material, presented to the technical service but not annexed to the application for type-approval, shall include all the modified parameters by any auxiliary emission control strategy and theboundary conditions under which this strategy operates and in particular:(i) a description of the control logic and of timing strategies and switch points, during all modes ofoperation for the fuel and other essential systems, resulting in effective emissions control (such asexhaust gas recirculation system (EGR) or reagent dosing);(ii) a justification for the use of any auxiliary emission control strategy applied to the engine, accompanied by material and test data, demonstrating the effect on exhaust emissions. This justification may be basedon test data, sound engineering analysis, or a combination of both;(iii) a detailed description of algorithms or sensors (where applicable) used for identifying, analysing, or diagnosing incorrect operation of the NO x control system;(iv) the tolerance used to satisfy the requirements in section 8.4.7.2, regardless of the used means.8.3.3.2. The additional material referred to in point (b) of section 8.3.3.1 shall be treated as strictly confidential. It shallbe made available to the type-approval authority on request. The type-approval authority shall treat this material as confidential.ofoperationNO x control measures8.4. Requirementstoensurecorrect8.4.1. The manufacturer shall provide information that fully describes the functional operational characteristics of theNO x control measures using the documents set out in section 2 of Appendix 1 to Annex II and in section 2 of Appendix 3 to Annex II.8.4.2. If the emission control system requires a reagent, the characteristics of that reagent, including the type of reagent,information on concentration when the reagent is in solution, operational temperature conditions and reference to international standards for composition and quality must be specified by the manufacturer, in section 2.2.1.13 of Appendix 1 and in section 2.2.1.13 of Appendix 3 to Annex II.8.4.3. The engine emission control strategy shall be operational under all environmental conditions regularly pertainingin the territory of the Community, especially at low ambient temperatures.8.4.4. The manufacturer shall demonstrate that the emission of ammonia during the applicable emission test cycle ofthe type approval procedure, when a reagent is used, does not exceed a mean value of 25 ppm.8.4.5. If separate reagent containers are installed on or connected to a non-road mobile machine, means for taking asample of the reagent inside the containers must be included. The sampling point must be easily accessible without requiring the use of any specialised tool or device.8.4.6. Use and maintenance requirements8.4.6.1. The type approval shall be made conditional, in accordance with Article 4(3), upon providing to each operator ofnon-road mobile machinery written instructions comprising the following:(a) detailed warnings, explaining possible malfunctions generated by incorrect operation, use or maintenance ofthe installed engine, accompanied by respective rectification measures;(b) detailed warnings on the incorrect use of the machine resulting in possible malfunctions of the engine,accompanied by respective rectification measures;(c) information on the correct use of the reagent, accompanied by an instruction on refilling the reagentbetween normal maintenance intervals;(d) a clear warning, that the type-approval certificate, issued for the type of engine concerned, is valid only whenall of the following conditions are met:(i) the engine is operated, used and maintained in accordance with the instructions provided;(ii) prompt action has been taken for rectifying incorrect operation, use or maintenance in accordance with the rectification measures indicated by the warnings referred to in point (a) and (b);(iii) no deliberate misuse of the engine has taken place, in particular deactivating or not maintaining an EGR or reagent dosing system.The instructions shall be written in a clear and non-technical manner using the same language as is used in the operator’s manual on non-road mobile machinery or engine.8.4.7. Reagent control (where applicable)8.4.7.1. The type approval shall be made conditional, in accordance with the provisions of section 3 of Article 4, uponproviding indicators or other appropriate means, according to the configuration of the non-road mobile machinery, informing the operator on:(a) the amount of reagent remaining in the reagent storage container and by an additional specific signal, whenthe remaining reagent is less than 10 % of the full container’s capacity;(b) when the reagent container becomes empty, or almost empty;(c) when the reagent in the storage tank does not comply with the characteristics declared and recorded insection 2.2.1.13 of Appendix 1 and section 2.2.1.13 of Appendix 3 to Annex II, according to the installedmeans of assessment.(d) when the dosing activity of the reagent is interrupted, in cases other than those executed by the engine ECUor the dosing controller, reacting to engine operating conditions where the dosing is not required, providedthat these operating conditions are made available to the type approval authority.8.4.7.2. By the choice of the manufacturer the requirements of reagent compliance with the declared characteristics andthe associated NO x emission tolerance shall be satisfied by one of the following means:(a) direct means, such as the use of a reagent quality sensor.(b) indirect means, such as the use of a NO x sensor in the exhaust to evaluate reagent effectiveness.(c) any other means, provided that its efficacy is at least equal to the one resulting by the use of the means ofpoints (a) or (b) and the main requirements of this section are maintained.’ANNEX IIAnnex II to Directive 97/68/EC is amended as follows:1. Section 2 of Appendix 1 is replaced by the following:POLLUTIONAIRAGAINSTTAKEN‘2. MEASURESyes/no(*)............................................................................................................gases:recyclingcrankcase2.1. Deviceforcoverednotbyheading)ifanother(ifanti-pollutiondevices2.2. Additionalandany,(*)yes/noconverter:2.2.1. Catalytic.......................................................................................................................................................................................2.2.1.1. Make(s):........................................................................................................................................................................................2.2.1.2. Type(s):converterselements................................................................................................................andcatalytic2.2.1.3. Numberofconverter(s):...............................................................................................thecatalyticofandvolume2.2.1.4. Dimensions-........................................................................................................................................................action:ofcatalytic2.2.1.5. Typeprecious........................................................................................................................................metals:of2.2.1.6. Totalchargeconcentration:...........................................................................................................................................................2.2.1.7. Relative.....................................................................................................................................material):and2.2.1.8. Substrate(structure...............................................................................................................................................................................2.2.1.9. Celldensity:2.2.1.10. Type of casing for the catalytic converter(s): .................................................................................................................2.2.1.11. Location of the catalytic converter(s) (place(s) and maximum/minimum distance(s) from engine): ............2.2.1.12. Normal operating range (K): ................................................................................................................................................2.2.1.13. Consumable reagent (where appropriate): .......................................................................................................................2.2.1.13.1. Type and concentration of reagent needed for catalytic action: .............................................................................2.2.1.13.2. Normal operational temperature range of reagent: ......................................................................................................2.2.1.13.3. International standard (where appropriate): ....................................................................................................................2.2.1.14. NO x sensor: yes/no (*)(*)yes/nosensor:2.2.2. Oxygen.......................................................................................................................................................................................2.2.2.1. Make(s):............................................................................................................................................................................................2.2.2.2. Type:.....................................................................................................................................................................................2.2.2.3. Location:(*)yes/noinjection:2.2.3. Airetc.):.........................................................................................................................................pump,2.2.3.1. Type(pulseair,air(*)yes/no2.2.4. EGR:etc.):pressure,........................................................................2.2.4.1. Characteristicspressure/low(cooled/uncooled,high(*)yes/no2.2.5. Particulatetrap:particulate.........................................................................................................thetrap:capacityof2.2.5.1. Dimensionsandparticulatetrap:.........................................................................................................................theandof2.2.5.2. Typedesignengine):..................................................................fromdistance(s)2.2.5.3. Locationand(place(s)maximum/minimumdescriptionand/ordrawing:regeneration,............................................................................ofor2.2.5.4. Methodsystempressure(kPa)and..................................................................................range:2.2.5.5. Normal(K)operatingtemperature(*)yes/nosystems:2.2.6. Otheroperation:...................................................................................................................................................and2.2.6.1. Description___________(*) Strike out what does not apply.’2. Section 2 of Appendix 3 is replaced by the following:POLLUTIONAGAINSTAIRTAKEN‘2. MEASURESyes/no(*)............................................................................................................gases:crankcase2.1. Deviceforrecyclingcoverednotbyheading)ifanotherany,anti-pollutiondevices(ifand2.2. Additional(*)yes/noconverter:2.2.1. Catalytic.......................................................................................................................................................................................2.2.1.1. Make(s):........................................................................................................................................................................................2.2.1.2. Type(s):and................................................................................................................converterselementscatalyticof2.2.1.3. Numberconverter(s):...............................................................................................thecatalyticofandvolume2.2.1.4. Dimensions-........................................................................................................................................................action:ofcatalytic2.2.1.5. Typeprecious........................................................................................................................................metals:of2.2.1.6. Totalchargeconcentration:...........................................................................................................................................................2.2.1.7. Relative.....................................................................................................................................material):and2.2.1.8. Substrate(structure...............................................................................................................................................................................2.2.1.9. Celldensity:2.2.1.10. Type of casing for the catalytic converter(s): .................................................................................................................2.2.1.11. Location of the catalytic converter(s) (place(s) and maximum/minimum distance(s) from engine): ............2.2.1.12. Normal operating range (K) .................................................................................................................................................2.2.1.13. Consumable reagent (where appropriate): .......................................................................................................................2.2.1.13.1. Type and concentration of reagent needed for catalytic action: .............................................................................2.2.1.13.2. Normal operational temperature range of reagent: ......................................................................................................2.2.1.13.3. International standard (where appropriate): ....................................................................................................................2.2.1.14. NO x sensor: yes/no (*)yes/no(*)sensor:2.2.2. Oxygen.......................................................................................................................................................................................2.2.2.1. Make(s):............................................................................................................................................................................................2.2.2.2. Type:.....................................................................................................................................................................................2.2.2.3. Location:(*)yes/noinjection:2.2.3. Airetc.):.........................................................................................................................................pump,2.2.3.1. Type(pulseair,air(*)yes/no2.2.4. EGR:etc.):pressure,........................................................................2.2.4.1. Characteristicspressure/low(cooled/uncooled,high(*)yes/no2.2.5. Particulatetrap:particulate.........................................................................................................thetrap:capacityof2.2.5.1. Dimensionsandparticulatetrap:.........................................................................................................................theandof2.2.5.2. Typedesignengine):..................................................................fromdistance(s)2.2.5.3. Locationand(place(s)maximum/minimumdescriptionand/ordrawing:regeneration,............................................................................ofor2.2.5.4. Methodsystempressure(kPa)and..................................................................................range:2.2.5.5. Normal(K)operatingtemperature(*)yes/nosystems:2.2.6. Otheroperation:...................................................................................................................................................and2.2.6.1. Description___________(*) Strike out what does not apply.’。

1-877-496-3566 – 1INSTALLATIONMANUALDistributed in the U.S.A. by:Revised on 01/10/2018Supersedes all previous versions.Check website for updates.Job Site Conditions 3Subfloors 3Subfloor Preparation 3-5Storage & Handling 5Roll Installation6-7INSTALLATIONI.JOB SITE CONDITIONS1.Installation should not begin until after all other trades are finished in the area. If the job requires othertrades to work in the area after the installation of the floor, the floor should be protected with anappropriate cover. Kraft paper or plastic works well.2.Areas to receive flooring should be weather tight and maintained at a minimum uniform temperature of65°F (18°C) for 48 hours before, during, and after the installation.II.SUBFLOORSDURA WOOD may be installed over concrete, approved Portland- based patching and leveling materials, such as Ardex K-15 or equivalent, and wood.NOTE: Ardex Engineered Cements400 Ardex Park DriveAliquippa, PA 15001(724) 203-5000NOTE: Gypsum-based patching and leveling compounds are not acceptable.1.Wood Subfloors –W ood subfloors should be double construction with a minimum thickness of one inch.The floor must be rigid and free from movement with a minimum of 18 inches of well-ventilated air spacebelow.2.Underlayments – The preferred underlayment panel is American Plywood Association (APA)underlayment grade plywood, minimum thickness of 1/4-inch, with a fully s anded face.3.Plywood Subfloors and underlayments must be American Plywood Association (APA) approved.Plywood shall not have any treatments added. (For example – fire retardant) The moisture content ofthe plywood may not exceed 12%.4.Concrete Floors – Concrete shall have a minimum compressive strength of 3000 psi. New concreteslabs should cure for a minimum of 28 days before installing DURA WOOD. Concrete must be fullycured and permanently dry.NOTE: Particleboard, chipboard, Masonite and lauan are not considered to be suitable underlayments.III.SUBFLOOR REQUIREMENTS AND PREPARATION1.Subfloors shall be dry, clean, smooth, level, and structurally sound. They should be free of dust, solvent,paint, wax, oil, grease, asphalt, sealers, curing and hardening compounds, alkaline salts, old adhesiveresidue, and other extraneous materials, according to ASTM F710.2.Subfloors should be smooth to prevent irregularities, roughness, or other defects from telegraphingthrough the new flooring. The surface should be flat to the equivalent of 3/16˝ (4.8 mm) in 10´ (3.0 m).3.Mechanically remove all traces of old adhesives, paint, or other debris by scraping, sanding, or scarifyingthe substrate. Do not use solvents. All high spots shall be ground level and low spots filled with anapproved Portland-based patching compound.4.All saw cuts (control joints), cracks, indentations, and other non-moving joints in the concrete must be filled with an approved Portland-based patching compound.INSTALLATION5.Expansion joints in the concrete are designed to allow for expansion and contraction of the concrete. If a floor covering is installed over an expansion joint, it will likely fail in that area. Use expansion joint coversdesigned for resilient flooring.NOTE: Expansion joint covers can be obtained from:Balco, Inc.2626 South SheridanP .O. Box 17249Witchita, KS 67217(316) 945-93286.Always allow patching materials to dry thoroughly and install according to the manufacturer’s instructions. Excessive moisture in patching material may cause bonding problems or a bubblingreaction with the adhesive.HAZARDS:SILICA WARNING – Concrete, floor patching compounds, toppings, and leveling compounds can contain free crystalline silica. Cutting, sawing, grinding, or drilling can produce respirable crystalline silica (particles 1- 10 micrometers). Classified by OSHA as an IA carcinogen, respirable silica is known to cause silicosis andother respiratory diseases. Avoid actions that may cause dust to become airborne. Use local or generalventilation or provide protective equipment to reduce exposure to below the applicable exposure limits.ASBESTOS WARNING – Resilient flooring, backing, lining felt, paint, or asphaltic “cutback” adhesives cancontain asbestos fibers. Avoid actions that cause dust to become airborne. Do not sand, dry sweep, dryscrape, drill, saw, beadblast, or mechanically chip or pulverize. Regulations may require that the material be tested to determine the asbestos content. Consult the document “Recommended Work Practices forRemoval of Existing Resilient Floor Coverings” available from the Resilient Floor Covering Institute.LEAD WARNING – Certain paints can contain lead. Exposure to excessive amounts of lead dust presents ahealth hazard. Refer to applicable federal, state, and local laws and the publication “Lead Based Paint:Guidelines for Hazard Identification and Abatement in Public and Indian Housing” available from the UnitedStates Department of Housing and Urban Development.7.Maximum moisture vapor emission of the concrete must not exceed 5.5 lbs. per 1000 sq.ft. in a 24 hourperiod as measured by the calcium chloride moisture emission test conducted in accordance to ASTMF1869. Moisture can also be measured using the RH Relative Humidity test method per ASTM F2170standard. Moisture content should not exceed 85% RH. If levels are high using either test method, thenone of Summit International Floorings recommended vapor retardants must be used. If the emissionsexceed the limitations, the installation should not proceed until the situation has been corrected.NOTE: For moisture remediation, Summit International Flooring recommends the following two vaporretardant products.1.ARDEX MC Rapid, Plus or Ultra - 724-203-5000, 2.Bostik Durabond D-250 - 888-592-8558, INSTALLATION8.It is essential that pH tests be taken on all concrete floors. If the pH is greater than 9, it must beneutralized prior to beginning the installation.9.Adhesive bond tests should be conducted in several locations throughout the area. Glue down 3´ x 3´ test pieces of the flooring with the recommended adhesive and trowel. Allow to set for 72 hours beforeattempting to remove. A sufficient amount of force should be required to remove the flooring and, whenremoved, there should be adhesive residue on the subfloor and on the back of the test pieces.IV. M ATERIAL STORAGE AND HANDLING1.Material should be delivered to the job site in its original, unopened packaging with all labels intact.2.Roll material should always be stored on end. Storing DURA WOOD laying down may cause welting, which causes permanent memory of the material. Rolls should only be stored on a clean, dry, smooth surface.3.Inspect a ll materials f or v isual d efects b efore beginning the installation. No labor claim w ill behonored o n m aterial i nstalled with v isual d efects. Verify t he m aterial delivered is t he c orrect style,color, and amount. Any discrepancies must be reported immediately before beginning installation.4.The material and adhesive must be acclimated at room temperature for a minimum of 48 hours beforestarting installation.5.All D URA W OOD r olls m ust be u nrolled and installed i n the s ame d irection. L aying r olls inthe opposite direction can cause color variations between the rolls.y the rolls to provide as few seams as possible with economical use of materials. Match edges for color shading and pattern at seams. Be prepared to straight edge cut the side seams to ensure patternconsistency.7.For best results, the installer should unroll all rolls and allow to relax overnight.INSTALLATIONTECHNICAL MANUALV.INSTALLATION – DURA WOOD ROLL MATERIAL1.Make the assumption that the walls you are butting against are not straight or square. Using a chalkline, make a starting point for an edge of the flooring to follow. The chalk line should be set where thefirst seam will be located.2.Remove the DURA WOOD from the shrink wrap and unroll it onto the floor. Lay the vinyl on the floorin a way that will use your cuts efficiently. Cut all rolls at the required length, including enough to runup the wall a couple inches.3.If end seams are necessary, they should be staggered on the floor and overlapped approximately 2”.End seams will be trimmed after acclimation period using a square to ensure they fit tightly withoutgaps. Match and cut seams to maintain overall continuity of color and pattern.4.After allowing proper acclimation and rough cuts are made you may begin the installation.5.Align the first edge to the chalk line.Note: i t i s v ery i mportant t hat t he f irst seam i s p erfectly s traight.6.Position the second roll with appropriate overlap required to maintain board pattern consistency. Afterseams are trimmed, the edges should fit snug with no visual gaps. Care should be taken to not overcompress the seam. Over compressed seams will cause peaking.7.Repeat for each consecutive sheet necessary to complete the area or those rolls that will be installedthat day.INSTALLATION – GLUE DOWN DURA WOOD Rollsa.After performing the above procedures, begin the application of the adhesive. We recommend SIF848.SIF 848 should not be mixed. It is specially formulated for use right out of the pail. Apply SIF 848 e substrateusing a 1/16˝square- notched trowel.b.Fold over the first drop along the wall (half the width of the roll). Rolls are 6 feet wide and 30 feet long.When roll is folded over this will leave an exposed area of substrate that is 3 feet wide and 30 feetlong.c.Spread the adhesive using the proper size square-notched trowel. Take care not to spread more Ithan can be covered with flooring within 30 minutes. The open time of the adhesive is 30–40minutes at 70°F and 50% relative humidity.NOTE: Temperature and humidity affect the open time of the adhesive. Temperatures above 70°F and/orrelative humidity above 50% will cause the adhesive to set up more quickly. Temperatures below 70°Fand/or relative humidity below 50% will cause the adhesive to set up more slowly. The installer shouldmonitor the on-site conditions and adjust the open time accordingly.y the flooring into the wet adhesive. Do not allow the material to “flop” into place; this may cause air entrapment and bubbles beneath the flooring.INSTALLATIONTECHNICAL MANUALe.Immediately roll the floor with a 75–100 lb. roller to ensure proper adhesive transfer. Overlap each passof the roller by 50% of the previous pass to ensure the floor is properly rolled. Roll the width first andthen the length.f.Fold over the second half of the first roll and half the width of the second roll. Taking roll sizes intoaccount, this will provide an exposed area of substrate of 6 feet wide and 30 feet in length per roll.Spread the adhesive, roll the flooring, and repeat for each consecutive drop.g.Continue the process for each consecutive drop. Work at a pace so that you are always foldingmaterial back into wet adhesive bed.NOTE: Never leave adhesive ridges or puddles. They will telegraph through the material.h.Do not allow SIF 848 to cure on your hands or the flooring. Immediately wipe off excess adhesive with a rag dampened with mineral spirits! Cured adhesive is very difficult to remove from hands. We stronglysuggest wearing gloves while using SIF 848i.Hand roll all seams after the entire floor has been rolled.j.Keep traffic off the floor for a minimum of 24 hours. Floor should be free from rolling loads for aminimum of 48-72 hours.INSTALLATION – Welding DURA WOOD Rollsk. a. Groove seams in vinyl sheet flooring with a hand groover or a mechanical groover. (Leister welding tools are excellent) b. Apply coordinating weld rod with heat welder (Leister or equivalent) c. Using a standard skiving knife take initial pass to remove excess weld rod. d. Allow weld seam to set for 15 minutes and take a final pass with the skive knife so the weld rod is completely flush and smooth to the sheet vinyl flooring. e. All seams are RECOMMENDED to be HEAT WELDED. f. If you are installing Dura Wood Sheet Flooring in areas that may get wet periodically (Bathrooms/kitchens/bars) then the seams MUST BE HEAT WELDED.INSTALLATION。

电阻率异常提取英文英文回答：Electrical resistivity is a fundamental property of materials that measures their resistance to the flow of electric current. It is defined as the resistance of a conductor of unit length and cross-sectional area, and is typically measured in ohm-meter s (Ω-m). The resistivity of a material is influenced by several factors, including its chemical composition, temperature, and crystal structure.In some cases, resistivity may exhibit anomalous behavior, deviating from the expected values or showing unusual temperature dependence. These anomalies can provide valuable insights into the material's properties and behavior. Some common types of resistivity anomalies include:Negative temperature coefficient of resistivity (NTCR): Materials that exhibit a decrease in resistivity withincreasing temperature. This behavior is typically observed in semiconductors and metallic alloys.Positive temperature coefficient of resistivity (PTCR): Materials that exhibit an increase in resistivity with increasing temperature. This behavior is commonly found in metals and insulators.Metal-insulator transition (MIT): Some materials undergo a transition from a metallic state with low resistivity to an insulating state with high resistivity at a critical temperature.Resistivity anomalies can be caused by various physical mechanisms, such as:Structural defects: Impurities, vacancies, and dislocations can disrupt the regular arrangement of atomsin a material, increasing its resistivity.Phase transitions: Changes in the material's crystal structure or electronic properties can lead to abruptchanges in resistivity.Magnetic ordering: In magnetic materials, the alignment of magnetic moments can affect the flow of electric current, resulting in resistivity anomalies.The study of resistivity anomalies has applications in various fields of science and engineering, including:Materials characterization: Resistivity measurementscan provide information about the chemical composition, crystal structure, and defect density of materials.Semiconductor device design: The temperature dependence of resistivity is crucial for designing semiconductor devices, such as transistors and solar cells.Geophysics: Resistivity surveys are used to explore the Earth's interior and detect underground structures.Medical diagnostics: Bioimpedance spectroscopy, which measures the electrical impedance of biological tissues,can provide insights into physiological conditions and disease states.In summary, resistivity anomalies refer to deviations from the expected resistivity behavior of materials. These anomalies can provide valuable information about the material's properties and behavior, and have applications in various fields of science and engineering.中文回答：电阻率是材料的一个基本特性，用来衡量它们对电流流动的阻力。

以下是一段英文版本的“Unable to validate the factsage education package”的翻译，希望能够帮助到您："Unable to validate the FactsAge education package" - this error message usually appears when there is a problem with the installation or validation of the FactsAge education package.Some possible reasons for this issue include:1.Missing or incorrect installation: This could be due to a failed installation, uninstall, or an incomplete installation.2.Invalid package: The package may be corrupted, incomplete or invalid.3.Hardware or system requirements: The system may not meet the minimum hardware or software requirements to install or run the package.4.File permissions: The installer may not have sufficient permissions to access or modify files during installation.5.Outdated or incompatible software: The FactsAge package may be incompatible with the existing software version or configuration on the system.To resolve this issue, you can try the following troubleshooting steps:1.Check if the installation file is corrupted or incomplete. If it is, download it again from a reliable source and try installing it again.2.Make sure your system meets the minimum hardware and software requirements for the FactsAge package. If not, upgrade your system accordingly.3.Check if your antivirus or firewall software is blocking the installation process. If it is, add an exception in the antivirus or firewall settings for the installation file.4.Verify if you have sufficient permissions to install the package. If not, try running the installer as an administrator.5.Check if there is any outdated or incompatible software on your system that may be causing conflicts with the FactsAge package. If found, uninstall or upgrade the conflicting software.6.Contact the FactsAge support team for further assistance if you still experience issues after trying these troubleshooting steps. They may be able to provide additional help and support for your specific issue.。

failed to run the ida analysis allegroI'm sorry to hear that you are facing issues running the IDA analysis Allegro. It would be helpful if you could provide more details about the problem you're encountering, such as any error messages or steps you have taken so far.In general, when facing difficulties with running IDA analysis in Allegro, you can try the following troubleshooting steps:1. Update Allegro and IDA to the latest version: Make sure you have the most recent versions of both software installed, as they often include bug fixes and improvements.2. Check system requirements: Ensure that your computer meets the minimum system requirements for running IDA analysis and Allegro. This includes having a supported operating system, sufficient RAM, and compatible hardware.3. Validate license: Verify that your license for Allegro and IDA is valid and properly activated. Sometimes, licensing issues can prevent the proper functioning of the software.4. Reinstall the software: Uninstall Allegro and IDA, then reinstall them from scratch. This can help to resolve any issues that may have occurred during the initial installation.5. Contact technical support: If the problem persists, reach out to the technical support team for IDA and/or Allegro. They can provide further assistance and guidance tailored to your specific situation.Remember to provide detailed information about the problem when contacting technical support, including any error messages you have encountered and steps you have taken to troubleshoot so far.。

The Strength of a Chain Lies in Its WeakestLinkIn the realm of mechanical engineering, a common adage goes, "The strength of a chain lies in its weakest link." This proverb, while originally referring to the integrity of physical chains, can be aptly applied to various aspects of life, from the smallest personal endeavors to thelargest societal undertakings. The crux of the matter is that the weakest element, regardless of its size or significance, has the potential to determine the overall strength and durability of the entire system.In the context of personal development, one's weakest link could be a lack of self-discipline, a fear of failure, or a limiting belief about one's capabilities. These weak points, often hidden in the shadows of our subconscious minds, can hold us back from achieving our full potential. It is crucial to identify and address these weaknesses if we want to move forward in our personal growth and development.In the workplace, the weakest link could be a poor communication system, a lack of team cohesion, or a failureto adapt to changing market conditions. If these weaknesses are not addressed, they can lead to breakdowns in productivity, decreased morale, and ultimately, failure to meet organizational goals.On a societal level, the weakest link could be afailure to provide equal educational opportunities, a lack of infrastructure development, or a failure to address social injustices. These issues, if left unresolved, can lead to societal breakdowns, increased social tension, and a lack of progress towards collective goals.The importance of addressing the weakest link isfurther emphasized in the realm of technology. In computer systems, for example, a single faulty component can cause the entire system to crash. Similarly, in engineering projects, a minor flaw in the design or construction of a single component can lead to catastrophic failure of the entire structure.In conclusion, the strength of a chain lies in its weakest link. Whether we are considering personal growth, organizational success, or societal progress, it is imperative that we identify and address the weak pointsthat threaten the integrity of the system. By doing so, we can ensure that we are building stronger, more resilient chains that are capable of withstanding the tests of time and adversity.**链条的强度取决于它的薄弱环节**在机械工程领域，有一句谚语说道：“链条的强度取决于它的薄弱环节。

bad material definition in element"Bad material" in the context of an element could refer to a material that is defective, damaged, or does not meet the required specifications or standards. Here are a few possible definitions of "bad material" in an element:1. Substandard quality: Material that does not meet the desired level of quality, performance, or durability. This could include materials with flaws, impurities, or other defects that affect their functionality or longevity.2. Damage or degradation: Material that has suffered physical damage, deterioration, or degradation due to exposure to environmental factors, wear and tear, or improper handling. This can lead to reduced integrity or reliability of the element.3. Non-compliance with specifications: Material that does not adhere to the specified requirements or guidelines. This can include incorrect dimensions, mechanical properties, chemical composition, or other characteristics.4. Failure to meet performance standards: Material that does not perform as expected or fails to meet the necessary performance criteria. This can result in ineffective or低效 functioning of the element.5. Unsuitable for intended use: Material that is not appropriate or compatible for the specific application or purpose of the element. It may lack the necessary properties or characteristics required for optimal performance.It's important to note that the definition of "bad material" can vary depending on the specific context and industry. In some cases, it may be subjective and dependent on the specific standards or requirements being applied.I hope this provides a comprehensive overview of the possible definitions of "bad material" in the context of an element. If you have any further questions or need more specific information, please feel free to ask.。

the issue can’t be reproduced anymore全文共四篇示例，供读者参考第一篇示例：最近在软件开发过程中，一个非常常见的问题是"the issue can't be reproduced anymore"，即无法再重现问题。

这种情况给开发人员和测试人员带来了极大的困扰，因为他们无法解决或验证问题是否已经解决。

造成问题无法再次重现的原因有很多种，其中一种可能是由于复制的环境不一样。

在软件开发的过程中，测试人员往往会在一个特定的环境中重现问题，一旦环境发生变化，问题就可能不再出现。

这也是为什么在软件开发过程中要尽量保持环境的一致性，以便更容易重现和修复问题。

另一个可能的原因是数据的不一致性。

在某些情况下，问题可能是由于特定的数据输入或操作触发的，一旦输入的数据不再存在或者操作不再执行，问题就不会再次出现。

这也需要测试人员详细记录并分析问题触发的条件和数据，以便更好地理解和解决问题。

此外，问题不再重现还可能是由于代码变更导致的。

在软件开发过程中，代码的变更是常有的事情，如果问题已经修复或者相关代码发生了变更，问题就有可能不再出现。

这也是为什么要及时记录和跟踪问题对应的代码变更，以便更好地理解和解决问题。

针对问题无法重现的情况，我们可以采取一些方法来解决。

首先，我们可以尝试还原问题发生时的环境和数据，以尽量模拟出问题的触发条件。

其次，我们可以尝试回顾问题的历史记录，查看相关的代码变更和提交信息，以了解问题的修复和改动情况。

最后，我们可以尝试与团队其他成员或相关利益方进行讨论，以了解问题的根本原因，并共同寻找解决方案。

总的来说，问题无法再次重现是软件开发过程中的常见问题，但我们可以通过仔细记录和分析问题的触发条件、环境、数据和代码变更等信息，来尽力解决问题并确保软件的质量和稳定性。

希望我们在今后的软件开发过程中能够更好地应对和处理这种情况，以提高软件的质量和用户体验。

The Design DocumentDesign phase: deliveries•Main delivery: design documentDesign = an activity that gives structure to the solution to a given problem •the design phase starts with the requirements document and maps the requirements into architecture•the architecture defines the components, their interfaces and behaviors•the design document describes a plan to implement the requirements•details on computer programming languages and environments, machines, packages, application architecture, distributedarchitecture layering, memory size, platform, algorithms, datastructures, global type definitions, interfaces, and many otherengineering details are established•may include the usage of existing componentsDesign document template (1)•Introduction•System Overview •Design Considerations–Assumptions andDependencies–General Constraints–Goals and Guidelines–Development Methods •Architectural Strategies–strategy-1 name ordescription–strategy-2 name ordescription–...•System Architecture–component-1 name ordescription–component-2 name ordescription–... •Policies and Tactics–policy/tactic-1 name ordescription–policy/tactic-2 name ordescription–...•Detailed System Design–module-1 name ordescription–module-2 name ordescription–...•Glossary•Bibliography(Software projects survival guide)Design document template (2)•Introduction–Describe the purpose, scope and intended audience–Identify the system/product using any applicable names and/or version numbers.–Provide references for any other pertinent documents such as: •Related and/or companion documents•Prerequisite documents•Documents which provide background and/or context for thisdocument•Documents that result from this document (e.g. a test plan or adevelopment plan)–Define any important terms, acronyms, or abbreviations–Summarize (or give an abstract for) the contents of this document.Design document template (3)•System Overview–Provide a general description of the software system:•functionality and•matters related to the overall system and its design•[discussion of the basic design approach or organization] •Design Considerations–describes many of the issues which need to be addressed or resolved before attempting to devise a complete design solution •Assumptions and Dependencies–Describe any assumptions or dependencies regarding the software and its use:•Related software or hardware•Operating systems•End-user characteristics•Possible and/or probable changes in functionalityDesign document template (4)•General Constraints–global limitations or constraints that have a significant impact on the design:•Hardware or software environment•End-user environment•Availability or volatility of resources•Standards compliance•Interoperability requirements•Interface/protocol requirements•Data repository and distribution requirements•Security requirements (or other such regulations)•Memory and other capacity limitations•Performance requirements•Network communications•Verification and validation requirements (testing)•Other means of addressing quality goals•Other requirements described in the requirements specificationDesign document template (5)•Goals and Guidelines–goals, guidelines, principles, or priorities which dominate or embody the design of the system's software:•The KISS principle ("Keep it simple stupid!")•Emphasis on speed versus memory use•working, looking, or "feeling" like an existing product –for each such goal or guideline, unless it is implicitly obvious, describe the reason for its desirability•Development Methods–describe the method or approach used for this software design –include a reference to a more detailed description of formal or published methodsDesign document template (6)•Architectural Strategies–decisions and/or strategies that affect the overall organization of the system and its higher-level structures–should provide insight into the key abstractions and mechanisms used in the system architecture–the reasoning employed for each decision and/or strategy and how any design goals or priorities were balanced or traded-off•Use of a particular type of product (programming language, database, library, etc. ...)•Reuse of existing software components to implement various parts/features of the system•Future plans for extending or enhancing the software•User interface paradigms (or system input and output models)•Hardware and/or software interface paradigms•Error detection and recovery•Memory management policies•External databases and/or data storage management and persistence•Distributed data or control over a network•Generalized approaches to control•Concurrency and synchronization•Communication mechanisms•Management of other resourcesDesign document template (7)•System Architecture–high-level overview of how the functionality and responsibilities of the system were partitioned and then assigned to subsystems or components –not too much detail about the individual components themselves–main purpose: to gain a general understanding of how and why the system was decomposed, and how the individual parts work together to provide the desiredfunctionality–major responsibilities that the software must undertake and the various roles that the system (or portions of the system) must play–how the system was broken down into its components/subsystems–how the higher-level components collaborate with each other–provide some sort of rationale for choosing this particular decomposition–make use of design patterns–include any diagrams, models, flowcharts, documented scenarios or use-cases of the system behavior and/or structure•Subsystem Architecture–more detailed discussion of particular components–how the component was further divided into subcomponents, and the relationships and interactions between the subcomponents–recurse if necessary, but leave the details for the Detailed System Design sectionDesign document template (8)•Policies and Tactics–Choice of which specific product to use (compiler, interpreter, database, library, etc. ...)–Engineering trade-offs–Coding guidelines and conventions–The protocol of one or more subsystems, modules, or subroutines–The choice of a particular algorithm or programming idiom (design pattern) to implement portions of the system's functionality –Plans for ensuring requirements traceability–Plans for testing the software–Plans for maintaining the software–Interfaces for end-users, software, hardware, and communications–Hierarchical organization of the source code into its physical components (files and directories).–How to build and/or generate the system's deliverables (how to compile, link, load, etc. ...)Design document template (9)•Detailed System Design–detailed description of the components introduced in “System Architecture”chapter–Classification•kind of component, such as a subsystem, module, class, package, function, file, etc. ....–Definition•specific purpose and semantic meaning of the component.–Responsibilities•primary responsibilities and/or behavior of this component:–What does this component accomplish? What roles does it play?–What kinds of services does it provide to its clients?–Constraints•relevant assumptions, limitations, or constraints for this component: on timing, storage, or state•might include rules for interacting with this component (preconditions, postconditions, invariants, data formats and data access, synchronization, exceptions, etc.) –Composition•description of the use and meaning of the subcomponents that are a part of this component.Design document template (10)•Detailed System Design(continuation)–Uses/Interactions•collaborations with other components:–What other components is this entity used by?–What other components does this entity use?•known or anticipated subclasses, superclasses, and metaclasses.–Resources•resources that are managed, affected, or needed by this entity: memory, processors, printers, databases, or a software library•discussion of any possible race conditions and/or deadlock situations, and how they might be resolved.–Processing•how this components goes about performing the duties necessary to fulfill its responsibilities•encompass a description of any algorithms used; changes of state; relevant time or space complexity; concurrency; methods of creation, initialization, and cleanup; andhandling of exceptional conditions.–Interface/Exports•services (resources, data, types, constants, subroutines, and exceptions) provided by this componentDesign document template (11)•Detailed Subsystem Design–detailed description of this software component (or a reference to sucha description)–include diagrams showing the details of component structure, behavior, or information/control flow•Glossary–ordered list of defined terms and concepts used throughout the document.•Bibliography–list of referenced and/or related publications.DevelopmentDevelopmentDevelopment = writing a program based on a designspecification•Types of development–Traditional–waterfall model -coding starts after the system is fully specified and models have beendesigned–Incremental–produce & deliver software inincrementsTraditional developmentIncremental developmentNeed for speed…•rapidly changing business environments lead to challenges for businesses:–they have to respond to new opportunities andcompetition–getting to a stable, consistent set of requirements isoften impossible•businesses require software, hence rapid development and delivery is becoming critical •businesses may be willing to accept lower quality software if rapid delivery of essential functionality is possibleSolution: rapid app development •Principles:–specification, design and implementation areconcurrent–no detailed specification–design documentation is minimized–the system is developed in a series of increments–end users•evaluate each increment•make proposals for later increments–system user interfaces are usually developed usingan interactive development systemRAD advantages•accelerated delivery of customer services –each increment delivers the highest priorityfunctionality to the customer•user engagement with the system –users have to be involved in the development1the system is more likely to meet theirrequirements1the users are more committed to the system.RAD disadvantages•Management problems–progress can be hard to judge–issues can be hard to find…because there is no documentation to demonstrate what has beendone•Contractual problems–the normal contract may include a specification…without a specification, different forms of contract have to be used •Validation problems…without a specification, what is the system being tested against?•Maintenance problems–continual change tends to corrupt software structure•it gets more expensive to change and evolve to meet newrequirementsRAD: How?...•Agile methods–focus on the code rather than the design–based on an iterative approach to software development–intended to deliver working software quickly and evolve this quickly to meet changing requirements.–probably best suited to small/medium-sized business systems or PC products2Extreme programming2Feature-driven developmentPrinciples of agile methods(Sommerville)Extreme programmingExtreme programming (XP)•‘extreme’approach to iterative development –requirements –expressed as scenarios (user stories)–programmers work in pairs–new versions may be built several times per day–increments –delivered to customers every 2 weeks –tests are developed before writing the code–all tests must be run for every build–the build is only accepted if tests run successfullyExtreme programming release cycleExtreme programming practices •Incremental planning–requirements stored on Story Cards–stories are broken into tasks•Small releases–first developed –essential functionality–releases are frequent; they add functionality incrementally•Simple design–restrict to what is neededExtreme programming practices•Test-first development–write tests for a new piece of functionality before implementing it•Refactoring–cleaning up the code–keeping it simple, maintainable•Pair programming–developers check each other’s jobExtreme programming practices•Collective ownership–developers own all code–developers work on all areas–anyone can change anything •Continuous integration– a finished task is integrated in the system–after the integration, all unit tests must passExtreme programming practices•Sustainable pace–Overtime not acceptable•On-site customer– a representative of the customer should be available full-time to the developers team –the customer is member of the teamTesting in XP•writing tests before code clarifies the requirements to be implemented.•tests are written as programs rather than data so that they can be executed automatically.•the test includes a check that it has to be executed correctly.•all previous and new tests are automatically run when new functionality is added, checking that the newfunctionality has not introduced errors.Pair programming in XP •programmers work in pairs, sitting together to develop code•this helps to develop common ownership of code and spreads knowledge across the team•it serves as an informal review process: each line of code is looked at by more than one person•it encourages refactoring as the whole team can benefit from this•development productivity with pair programming is similar to that of two people working independently.Feature-driven developmentFeature-driven development (FDD)•model-driven short-iteration process thatconsists of five basic activities •milestones defined–for accurate state reporting–for keeping track of the softwaredevelopment project–mark the progress made on each feature are definedFDD activitiesFDD activities•Develop overall model–start with a high-level walkthrough of the scope of the system–detailed domain walkthroughs are held for each modeling area–walkthrough models are composed by small groups and presented for peer review and discussion–one of the proposed models or a merge of them is selected –it becomes the model for that particular domain area–domain area models are merged into an overall model–the overall model shape is adjusted along the way.FDD activities•Build Feature List–use the knowledge gathered during the initial modeling to identify a list of features–functionally decompose the domain into subject areas–subject areas contain business activities–the steps within each business activity form the categorized feature list–features are small pieces of client-valued functionsexpressed in the form <action> <result> <object>,´Calculate the total of a sale´´Validate the password of a user´.–features should not take more than two weeks to complete, else they should be broken down into smaller pieces.FDD activities•Plan By Feature–produce the development plan–class ownership is done by ordering and assigning features (or feature sets) as classes to programmers•Design By Feature– a design package is produced for each feature– a chief programmer selects a small group of features that are to be developed within two weeks–together with the corresponding class owners, theprogrammer•works out detailed sequence diagrams for each feature•refines the overall model–the class and method prologues are written–at the end, a design inspection is held.FDD activities•Build By Feature–produce a completed client-valued function (feature)–class owners develop the actual code for their classes–after a unit test and a successful code inspection, the completed feature is promoted to the main buildFDD: Milestones•milestones mark the progress –important for accurate state reporting and keeping track of the development •FDD defines six milestones per feature that are to be completed sequentially–the first three are completed during the Design By Feature activity–the last three are completed during the Build By Feature activity•a percentage complete is assigned to each milestone。

电阻率异常提取英文## Resistivity Anomalous Extraction.Resistivity anomaly extraction is a key step in resistivity method data processing. It is the process of identifying and extracting anomalous resistivity values from a resistivity survey dataset. These anomalies may indicate the presence of subsurface features or structures of interest, such as ore deposits, groundwater aquifers, or geological faults.Methods of Resistivity Anomaly Extraction.There are various methods that can be used to extract resistivity anomalies from a survey dataset. Some of the most common methods include:Thresholding: This is a simple method that involves setting a threshold value for resistivity. Any resistivity values that exceed the threshold are considered anomalous.Clustering: This method uses statistical techniques to group resistivity values into clusters. Clusters that are significantly different from the background resistivity values are considered anomalous.Machine learning: This method uses machine learning algorithms to classify resistivity values as anomalous or non-anomalous. The algorithms are trained on a dataset of known anomalous and non-anomalous resistivity values.Factors Affecting Resistivity Anomaly Extraction.The accuracy and effectiveness of resistivity anomaly extraction depends on a number of factors, including:The quality of the resistivity survey data: Noisy or incomplete data can lead to false anomalies.The resistivity contrast between the anomalous feature and the surrounding rock: A large resistivity contrast will make the anomaly easier to identify.The depth of the anomalous feature: Deeper anomalies are more difficult to identify due to the attenuation of the resistivity signal.The presence of other geological features: Other geological features, such as faults or fractures, can create resistivity anomalies that can interfere with the identification of the anomalous feature of interest.Applications of Resistivity Anomaly Extraction.Resistivity anomaly extraction is used in a variety of applications, including:Mineral exploration: Resistivity anomaly extraction can be used to identify ore deposits by detecting the resistivity contrast between the ore and the surrounding rock.Groundwater exploration: Resistivity anomaly extraction can be used to identify groundwater aquifers bydetecting the resistivity contrast between the water-saturated rock and the surrounding dry rock.Geological mapping: Resistivity anomaly extraction can be used to map geological features, such as faults and fractures, by detecting the resistivity contrast between the different rock types.## 中文回答：电阻率异常提取。

一、名词解释（5*3分=15分）(斜体表明仅供参考) 计量经济学：以经济理论和经济数据的事实为依据，运用数学和统计学的方法，通过建立数学模型来研究经济数量关系和规律的一门经济学科。

最小二乘法：指在满足古典假设的条件下，用使估计的剩余平方和最小的原则确定样本回归函数的方法，简称OLS 随机扰动项：总体回归函数中，各个Y值与条件期望的Y值的偏差，又称随机误差项。

是代表那些对Y有影响但又未纳入模型的诸多因素的影响。

总体回归函数：在给定解释变量X i条件下，总体被解释变量Y i的期望轨迹，函数式表示为E（Y i∣X i）=f(Xi)= β0+β1X i 样本回归函数：在总体中抽取若干个样本构成新的总体，然后在新的总体下，给定解释变量X i，被解释变量Y i的期望轨迹，函数式表示为E（Y i∣X i）=Y i^= β0^+β1^X i系数显着性检验:（t检验）对回归系数对应的解释变量是否对被解释变量有显着影响的统计学检验方法方程显着性检验:（F检验）对模型的被解释变量与所有解释变量之间的线性关系在整体上是否显着的统计学检验方法高斯-。

拟合优度多重共线性异方差（εi）=σi2σi2，根据最小自相关≠j)判断题（1234567891011 ( 乂 )12、变量不存在两两高度相关表示不存在高度多重共线性。

( 乂 )13、当异方差出现时，最小二乘估计是有偏的和不具有最小方差特性。

（乂）14、当异方差出现时，常用的t检验和F检验失效。

（√）15、在异方差情况下，通常OLS估计一定高估了估计量的标准差。

（乂）16、如果OLS回归的残差表现出系统性，则说明数据中有异方差性。

（√）17、如果回归模型遗漏一个重要的变量，则OLS残差必定表现出明显的趋势。

（√）18、在异方差情况下，通常预测失效。

（√）19、当模型存在高阶自相关时，可用D-W法进行自相关检验。

（乂）20、当模型的解释变量包括内生变量的滞后变量时，D-W检验就不适用了。

build failed with errors 报错看不懂的代码对于一个开发者来说，经常出现“build failed with errors”是再正常不过的事情了。

尤其是在开始学习新的编程语言或者框架的时候，报错成为了我们日常开发中不可避免的一部分。

然而，面对看不懂的代码报错，可能会让初学者感到十分困扰和无助。

因此，本文将结合个人经验，为大家详细介绍应对报错的一些方法和技巧。

基本概念在深入了解如何处理报错之前，我们需要了解一些基本概念。

首先，我们需要了解什么是编译。

编译是将高级语言代码转换为机器语言代码的过程。

通常，编译器会对源代码进行语法和语义分析、优化和目标代码生成。

如果在这个过程中有任何错误或者警告，编译器会产生利用报错信息告诉开发者为什么编译失败的消息。

常见的编译器错误包括语法错误、未定义变量和函数、编译时错误等。

编译器警告意味着代码可以正常编译，但是可能存在一些问题，例如不建议使用的过时功能、空的控制流语句等。

如何处理报错当我们遇到“build failed with errors”时，该怎么办呢？以下是一些通用的解决方法和技巧。

1.审查报错信息第一步，需要仔细审查报错信息。

查看报错信息的位置、错误类型和具体原因。

可能需要寻找使用了未定义的变量、重复定义变量、语法错误等问题。

排除这些错误，代码就可以进行编译。

如果出现build failed with warnings的情况，需要注意代码中可能存在一些问题。

尤其是无用的语句和变量、未使用的函数等。

这些问题需要规避，以避免出现意外的错误情况。

此外，一般来说，在编译失败时，编译器会提供帮助信息。

这些信息提供了出错的具体代码行，以及所报告的错误的类型。

因此，正确理解和理解错误信息是重要的。

2.备份代码在修改代码之前建议备份整个代码库。

所以你可以还原到修改之前的状态。

这个操作相当于在修改的过程中实现代码版本控制。

3.实现断点调试如果代码非常复杂，找到问题可能会很麻烦。

The Strength of a Chain Lies in Its WeakestLinkIn the realm of mechanical engineering, a chain's strength is often judged not by its sturdiest links, but by its weakest ones. This adage applies not just to physical chains but also to the intangible ones that shape our lives, such as habits, beliefs, and systems. In essence, the strength of any entity is contingent upon the weakest part, which, if compromised, can lead to its overall failure.The concept of the weakest link is particularlyrelevant in the context of teamwork. A team, regardless of how talented or skilled its members are, can only achieveits full potential if each member fulfills their role effectively. It is the member who lags behind, the one whois not as proficient or engaged, that can limit the team's overall performance. Similarly, in a chain, it is the weakest link that determines how much weight the chain can bear before breaking.This principle also applies to personal development. We often focus on building our strengths and talents, ignoring the areas where we are weakest. However, it is theseweaknesses that can hold us back from achieving our full potential. It is essential to identify and work on our weaknesses to ensure that they do not become the Achilles' heel that prevents us from reaching our goals.Moreover, the weakest link principle highlights the importance of continuous improvement. In a chain, regular maintenance and replacement of weak links can ensure its durability and longevity. Similarly, in our lives, we must continually strive to improve ourselves, addressing our weaknesses and turning them into strengths.In conclusion, the strength of a chain lies in its weakest link. This principle reminds us that it is our weaknesses, not our strengths, that determine our limits.It urges us to identify and address our weaknesses, to work towards continuous improvement, and to recognize that the smallest link in the chain can have the biggest impact on our overall strength and success.**链条的强度取决于它的薄弱环节**在机械工程领域，链条的强度往往不是由它最坚固的环节决定，而是由最薄弱的环节决定。

从其它论坛转贴过来的一些ANSYS精华，(希望斑主加分呀)。

Q为问，A为回复。

------------------------------------------------------------------------------------------------------Q:模态分析得到的结果是不是某个方向上的各阶频率啊？我要得到各个方向的一阶频率能做到吗？A：模态分析得到的结果是你所选择的自由度内的振型。

如果需要得到某一个方向内的振型，用RUDECED法，选择你所希望的主自由度，如UX。

将所求的频率值设置为一即可。

Q：不过大型复杂结构的振型一般都不是一个方向的，应该是一个方向为主，其它方向为次，如果把所要求的方向设为主自由度，会不会跟真是实际结果有出入？Q：对于复杂的大型实体，其主自由度无法给出，此时就无法应用reduce法。

可不可以改约束？还是就认为一次得到前3阶频率就是x,y,z方向的一阶频率啊？A：正是因为复杂结构的主自由度不好确定，所以我还是倾向于用SUBSPACE和BLOCK LANCZOS法。

约束不要随便改，它应该描述结构真实的状态。

不能说前3阶频率即为X、Y、Z方向的第一阶频率。

你可以好好想想所用方程中[K]和[M]的意义。

----------------------------------------------------------------------------------------------------Q：轴承是用来支撑要研究的对象，把轴承等价为弹簧，将其刚度加在对象的节点上。

这样就要定义刚度的大小在加。

是否还要定义单元类型，然后才能定义其刚度？A：我曾经用LINK8单元模拟过，根据K=EA/L确定刚度，我当时取E=210e9,L=0.1,然后A=KL/E。

经过检验，是可行的。

A：1、用link单元模拟其刚度，k=EA/L，通过假定E,A,L的值使之和k相等，其密度要＝0；2、用combin14模拟其刚度，阻尼＝0----------------------------------------------------------------------------------------------------Q：ANSYS处理动力问题（如土层地震响应、或基础振动反应），可否从边界施加加速度荷载？若可以，如何？瞬态动力反应分析，时间子步为>200?A：如果你所希望求的最高频率的周期为f，则ANSYS取时间步长为1/20f为默认值。

Flexible plastic pipes are used in various applications due to their durability, corrosion resistance, and ease of installation. They are often used in place of metal piping in areas where vibration, movement, or corrosive environments are present.Extra-flexible plastic pipe connections provide a secure and reliable means of joining plastic pipes. They are designed to withstand various environmental conditions and provide a leak-free seal.Some of the key functions of extra-flexible plastic pipe connections include:1.Leakage Prevention: Extra-flexible plastic pipe connections aredesigned to prevent leaks, even under extreme conditions. The sealing mechanism employed in these connections provides a tight seal, ensuring that no fluid escapes from the piping system.2.Vibration Damping: Extra-flexible plastic pipe connections caneffectively absorb vibrations, reducing the risk of stress and strain on the piping system. This feature is beneficial in applications where vibrations are common, such as in industrial settings or automotive applications.3.Easy Installation: Extra-flexible plastic pipe connections are oftendesigned for easy installation, providing a cost-effective and time-saving solution. The connections may be installed without the need for special tools or expertise, simplifying the installation process.4.Corrosion Resistance: Plastic materials used in extra-flexible pipeconnections are generally corrosion-resistant, making them suitable for use in harsh environments where corrosive fluids or gases may be present. This attribute extends the service life of the piping system and reduces the need for frequent maintenance.5.Temperature Resistance: Extra-flexible plastic pipe connections canwithstand a range of temperatures, making them suitable for use in both cold and hot applications. This versatility allows them to be used in various industrial processes and other temperature-sensitive applications.In conclusion, extra-flexible plastic pipe connections provide a range of functions that make them suitable for a variety of applications. Their durability, corrosion resistance, ease of installation, and temperature resistance make them a popular choice for fluid handling in various industries.。

Mistakes in Fortran 90 Programs That Might Surprise YouOver the years we have made lots of interesting and fun mistakes in Fortran 90 that we would like to share with you. We welcome your contributions and experiences so that we can share your pain.TopicsThese "gotchas" are nasty because they will not fail on some machines, while failing on others (given various combinations of compilers and machine platforms).* Danger with Optional Arguments* Danger with intent(out)* A suprise with non-advancing I/O* Suprise with locally initialized variables* Danger of calling Fortran 90 style routines* Danger with interfaces to Fortran 77 subroutines* A suprise with generic functions* Big Danger with Undefined Pointers* Subtle danger with overloading (=) to assign pointers* Danger with pointers to pointersDanger with Optional ArgumentsIn this example an optional argument is used to determine if a header is printed.subroutine print_char(this,header)character(len=*), intent (in) :: thislogical, optional, intent (in) :: header! THIS IS THE WRONG WAYif (present(header) .and. header) thenprint *, 'This is the header 'endifprint *, thisend subroutine print_charsubroutine print_char(this,header)character(len=*), intent (in) :: thislogical, optional, intent (in) :: header! THIS IS THE RIGHT WAYif (present(header)) thenif (header) print *, 'This is the header 'endifprint *, thisend subroutine print_charExplanationThe first method is not safe because the compiler is allowed to evaluate the header argument before the present function is evaluated. If the header argument is not in fact present an out of bounds memory reference could occur, which could cause a failure.Danger with intent(out)In this example we assign components of a derived type with intent(out).program intent_gotchatype mytypeinteger :: xreal :: yend type mytypetype (mytype) :: aa%x = 1 ; a%y = 2.call assign(a)! a%y COULD BE UNDEFINED HEREprint *, acontainssubroutine assign(this)type (mytype), intent (out) :: this! THIS IS THE WRONG WAYthis%x = 2end subroutine assignsubroutine assign(this)type (mytype), intent (out) :: this! THIS IS THE RIGHT WAYthis%x = 2 ; this%y = 2.end subroutine assignend program intent_gotchaExplanationThe problem is that when intent(out) is used with a derived type, any component not assigned in a procedure could become undefined on exit. For example, even though a%y was defined on entry to this routine, it couldbecome undefined on exit because it was never assigned within the routine. The lesson is that all components of a derived type should be assigned within a procedure, when intent(out) is used. Intent(out) behaves like the result variable in a function: all components must be assigned.As an alternative, use intent(inout).A suprise with non-advancing I/OMany people think that the new non-advancing I/O in Fortran 90 is the same as stream I/O in other languages. It is not.do i = 1, 128write (unit=6,fmt='(a)',advance='no') 'X'end doWe expect this program to print 128 X's in a row. However, unexpected behavior may occur if the record length for unit 6 is less than 128.One can inquire the record length in the follow way:open(unit=6)inquire(unit=6, recl=i)print *, 'recl =', iExplanationAll Fortran I/O is still record based. Non-advancing I/O allows partial reads and writes within a record. For many compilers the default record length is very large (e.g., 2147483647) giving the appearance of stream I/O. This is not true for all compilers however.On some compilers it is possible to set the record length as follows:open(unit=6, recl = 2147483646)On other compilers unit 6 is preconnected and the record length cannot be changed. (Thanks to Jon Richards of the USGS for this tip.)Note that unit 6 and unit * are not necessarily the same. Although they both may point to the default output device, with non-advancing I/O, each could keep track of the current location in its own record separately. Therefore we advise choosing one default unit and sticking with it. Suprise with locally initialized variablesOne must be careful when initializing a locally declared variable.real function kinetic_energy(v)real, dimension(:), intent(in) :: vinteger i! THIS IS THE WRONG WAYreal :: ke = 0.0do i = 1, size(v)ke = ke + v(i)**2enddokinetic_energy = .5*keend function kinetic_energyreal function kinetic_energy(v)real, dimension(:), intent(in) :: vinteger i! THIS IS THE RIGHT WAYreal :: keke = 0.do i = 1, size(v)ke = ke + v(i)**2enddokinetic_energy = .5*keend function kinetic_energyExplanationA local variable that is initialized when declared has an implicit save attribute. ke is initialized only the first time the function is called. On subsequent calls the old value of ke is retained. This is a real suprise to C programmers.To avoid confusion it is best to add the save attribute to such locally initialized variables explicitly, even though this is redundant. Danger of calling Fortran 90 style routinesprogram mainreal, dimension(5) :: xx = 0.! THIS IS WRONGcall incb(x)print *, xend program mainsubroutine incb(a)! this is a fortran90 style subroutinereal, dimension(:) :: aa = a + 1.end subroutine incbExplanationThe subroutine incb uses a Fortran 90 style assumed shape array (containing dimension(:)). Such routines must either be in a module, or have an explicit interface wherever they are used. In this example, neither one was true.One correct way to call such procedures is to use an explicit interface as follows:program mainreal, dimension(5) :: x! THIS IS THE RIGHT WAYinterfacesubroutine incb(a)real, dimension(:) :: aend subroutine incbend interfacex = 0.call incb(x)print *, xend program mainsubroutine incb(a)! this is a fortran90 style subroutinereal, dimension(:) :: aa = a + 1.end subroutine incbIf the routine is in a module interfaces are generated automatically and do not need to be explicitly written.! THIS IS ANOTHER RIGHT WAYmodule inccontainssubroutine incb(a)! this is a fortran90 style subroutinereal, dimension(:) :: aa = a + 1.end subroutine incbend module incprogram mainuse increal, dimension(5) :: xx = 0.call incb(x)print *, xend program mainIf interfaces are used, the interface MUST match the actual function. Danger with interfaces to Fortran 77 subroutinesprogram mainreal, dimension(5) :: x! interface to Fortran 77 style routineinterfacesubroutine inca(a,n)integer :: n! THIS IS THE WRONG WAYreal, dimension(:) :: a! THIS IS THE RIGHT WAYreal, dimension(n) :: aend subroutine incaend interfacex = 0.call inca(x,5)print *, xend program mainsubroutine inca(a,n)! this is a fortran77 style subroutinedimension a(n)do 10 j = 1, na(j) = a(j) + 1.10 continuereturnendExplanationThe interface declaration must always match the actual subroutine declaration. In this case, the interface statement refers to a Fortran 90 style assumed shape array. The actual subroutine refers to a Fortran 77 explicit shape array. The lesson here is: Interfaces to Fortran 77 style routines must only use Fortran 77 style constructs.In this example, it is permitted to leave out the interface altogether since routines without interfaces are treated as Fortran77 style routines by default. However, if the interface is left out, the compiler will no longer check whether the arguments of calling procedures agree with the arguments listed in the interface.A Suprise with Generic Functions (Function Overloading)Fortran 90 allows the same function name to be used for different actual functions, so long as the arguments to the functions differ. One would expect that the functions first_sub and second_sub below would be different, because in first_sub, the first argument is a real and the second is an integer, while in second_sub the arguments are reversed.subroutine first_sub(a,i)real :: ainteger :: i...end subroutine first_sub!subroutine second_sub(i,a)integer :: ireal :: a...end subroutine second_subSo that one could define a generic function first_or_second below:interface first_or_secondmodule procedure first, secondend interfaceThis is NOT so.ExplanationThe reason is that Fortran 90 allows procedures to be called by name (keyword) arguments. The followingreal :: binteger :: ncall first_or_second(i=n,a=b)does not work because when called by keyword, first_sub and second_sub are indistinguishable,call first_sub(i=n,a=b)call second_sub(i=n,a=b)and therefore a generic function cannot be defined. A generic function must be able to distinguish its arguments by type AND by name.The solution is to not use the same dummy argument name in both procedures. For example, the following would work:subroutine second_sub(i,aa)integer :: ireal :: aa...end subroutine second_subDangers with PointersFortran 90 has 3 ways to implement dynamic memory: Automatic arrays, allocatable arrays, and pointers.Automatic arrays are automatically created on entry and deleted on exit from a procedure, and they are safest and easiest to use. Allocatable arrays require the user to manually create and delete them, and should only be used if automatic creation and deletion is not the desired behavior.Pointers are the most error prone and should only be used when allocatable arrays are not possible, e.g., when one desires an array to be a component of a derived type.Big Danger with Undefined PointersMany people think that the status of a pointer which has never been associated is .not. associated. This is false.In this example we are allocating a local_table on first entry that is to be reused on subsequent entries.subroutine local_pointer(this)real, dimension(:) :: thisreal, dimension(:), save, pointer :: local_table! THIS IS THE WRONG WAYif (.not. associated(local_table)) thenallocate(local_table(size(this)))endiflocal_table = ......end subroutine local_pointersubroutine local_pointer(this)real, dimension(:) :: thisreal, dimension(:), save, pointer :: local_table! THIS IS THE RIGHT WAYlogical, save :: first_entry = .true.if (first_entry) thennullify(local_table) ; first_entry = .false.end ifif (.not. associated(local_table)) thenallocate(local_table(size(this)))endiflocal_table = ......end subroutine local_pointerExplanationWhen a pointer is declared its status is undefined, and cannot be safely queried with the associated intrinsic. A second variable is introduced to nullify the pointer on first entry so that its status can be safely tested. This is not a problem in Fortran 95 which allows one to nullify a pointer on declaration.Note that the save attribute for local_table is necessary to guarantee that the array and the pointer status are preserved on subsequent entries. We recommend that the save attribute should always be used when pointers and allocatable arrays are allocated in procedures.Subtle danger with overloading (=) to assign pointersOne must be careful with overloading the assignment operator.In this module we have created a private type which contains a pointer and a public procedure to assign that pointer.module assign_pointer_classtype mytypeprivatereal, pointer :: prend type mytypeinterface assignment (=)module procedure assign_pointerend interfacecontainssubroutine assign_pointer(this, a)type (mytype), intent(out) :: thisreal, target, intent(in) :: athis%pr => aend subroutine assign_pointerend module assign_pointer_classIn this main program we intend to assign the pointer component x%pr to the variable a, x%pr =>a. We cannot do so directly because the components of mytype are private. One must use a public procedure to do so. Furthermore, to simplify the syntax one might be tempted to use an overloaded assignment operator (=).program mainuse assign_pointer_classtype (mytype) :: xreal :: a = 0! THIS IS THE WRONG WAYx = aend program mainDon't give into this temptation! The only safe way to accomplish this is to call the procedure directly.program mainuse assign_pointer_classtype (mytype) :: x! THIS IS THE RIGHT WAYreal, target :: a = 0call assign_pointer(x,a)end program mainExplanationThe Fortran 90 standard says that the right hand side of an assignment operator is an expression that may potentially only persist for the duration of the call. In other words, x%pr could inadvertently point to a temporary copy of the variable a.Thanks to Henry Zongaro of IBM for pointing this out. (We never would have figured this one out on our own.)Also, James Giles found a subtle point regarding this example. We did not include "target" in the declaration of the real variable "a" (this has been corrected above). In James' words:"Notice that for this to really work, the actual argument, 'a', must be declared with the target attribute. You correctly declare the dummy argument in the assign_pointer routine with the target attribute, but the actual argument must also have that attribute (otherwise it's illegal for any pointer to be associated with it). Just a minor point..."Danger with pointers to pointersWhen creating a hierarchy of pointers to pointers, each level of pointers must be allocated before being used.program maintype mytypereal, dimension(:), pointer :: pend type mytypetype (mytype), pointer :: x! BOTH OF THESE ARE THE WRONG WAY! AND THE COMPILER WON'T CATCH IT! nullify(x%p)! allocate(x%p(5))! ONE SHOULD ALWAYS IMMEDIATELY NULLIFY THE PARENT POINTER! OR ALLOCATE ITnullify(x) ! or allocate(x)...! THEN LATER NULLIFY OR ALLOCATE THE CHILD POINTERcall child_construct(x,5)if (associated(x%p)) print *, x%pcontainssubroutine child_construct(this,len)! child constructor for pointer within mytype! if len is present, then allocate it, otherwise nullify it.! mytype is assumed to be already nullified or allocatedtype (mytype), pointer :: thisinteger, optional, intent(in) :: lenif (.not.associated(x)) allocate(x)if (present(len)) thenallocate(x%p(len))x%p = 0.elsenullify(x%p)endifend subroutine child_constructend program mainExplanationThis example creates a pointer to a pointer to an array of reals where the first pointer has not been allocated. For safety one should always either allocate or nullify the parent pointer immediately after its declaration. The child pointer cannot be allocated before the parent. Since the child pointer may be allocated elsewhere in the code, it is convenient to use constructor routines for this purpose.Each child constructor can safely allocate or nullify its pointers only when it can be sure that its parent's pointers have been allocated or nullified.。