No abstract

No abstract

Several technologies can be used in ultrasonic gas flow-meters, such as transit-time, Doppler, cross-correlation and etc. In applications, the approach based on measuring transit-time has demonstrated its advantages and become more popular. Among those techniques which can be applied to determine time-of-flight (TOF) of ultrasonic waves, including threshold detection, cross correlation algorithm and other digital signal processing algorithms, cross correlation algorithm has more advantages when the received ultrasonic signal is severely disturbed by the noise. However, the reference wave for cross correlation computation has great influence on the precise measurement of TOF. In the applications of the multipath flow-meters, selection of the reference wave becomes even more complicated. Based on the analysis of the impact factors that will introduce noise and waveform distortion of ultrasonic waves, an averaging method is proposed to determine the reference wave in this paper. In the multipath ultrasonic gas flow-meter, the analysis of each path of ultrasound needs its own reference wave. In case study, a six-path ultrasonic gas flow-meter has been designed and tested with air flow through the pipeline. The results demonstrate that the flow rate accuracy and the repeatability of the TOF are significantly improved by using averaging reference wave, compared with that using random reference wave.

Abstract. The effective provision of security in an agile development requires a new approach: traditional security practices are bound to equally traditional development methods. However, there are concerns that security is difficult to build incrementally, and can prove prohibitively expensive to refactor. This paper describes how to grow security, organically, within an agile project, by using an incremental security architecture which evolves with the code. The architecture provides an essential bridge between system-wide security properties and implementation mechanisms, a focus for understanding security in the project, and a trigger for security refactoring. The paper also describes criteria that allow implementers to recognize when refactoring is needed, and a concrete example that contrasts incremental and 'top-down' architectures.

No abstract