Search

670 pillar is a geological barrier that will trap the rock blocks falling and rolling from the deformation zone of the Eynez fault as well as to prevent the materials belonging to the landslides to be formed along the fault zone from reaching the coal production area. It forms the foot wall of Soma-Eynez fault and consists of Neogene aged marls. The toppling failures observed in the 670-pillar's slopes threatened the safety of excavation works for coal production in the open pit. The maximum runout distances of rock fragments that had toppled, fallen and rolled at different slope heights as a result of the mentioned mass movements were determined using computer softwares. The project excavation limit for the open pit coal mine was determined by considering the runout distances calculated for different slope heights. In this work, toppling failures observed in the 670-pillar's slopes were investigated both kinematically and numerically, using stereographic projection and different computer softwares, respectively. Safety factors obtained from different softwares for the same slope geometries were compared and the effect of friction angle (ɸ) and cohesion (c) values of the joint surfaces on safety factor that cause toppling failures were investigated. In addition, the time-dependent changes of joint aperture increase rate obtained from 20-deformation measurement points installed on the cracks causing toppling failures were investigated. The areas where the joint aperture increase rate is highest and the areas where the toppling failure is observed in the pillar's slope were associated. [ABSTRACT FROM AUTHOR]

This study presents the results of nonlinear time history analyses of a multi-story building with structural system having highly ductile moment resisting frames composed of concrete filled composite columns and steel beams, which was designed per Turkish Code for Design and Construction of Steel Structures 2016 and Turkish Seismic Code for Buildings 2018. The nonlinear analyses were carried out with ETABS and OpenSEES using 11 earthquake ground motion records. The results of the analyses are evaluated on the basis of plastic rotations occurred in the beams and columns hinges. In addition, according to the values of plastic rotations, damage levels of beams and columns were determined and the seismic performance of the structural system of the building was also investigated. Shear forces acting on each floor (diaphragm forces) considered for the design of the diaphragm elements were also examined within the Turkish Seismic Code for Buildings 2018. The consistency between the analyses results from both computer softwares were comparatively assessed. [ABSTRACT FROM AUTHOR]

The article presents information on the role of Version Control (VC) systems in developing computer softwares. One of the oldest, most vulnerable VC systems is Concurrent Versions System (CVS). CVS is a open source tool. As software is developed in small steps or versions. These versions are results of collaborations among different persons. At times one want to refer to a previous version or compare various variants. Sometimes, one need to trace changes to change requests. All these tasks are concerned with version control. VC systems only stores the differences between successive versions. The basic VC idea is to separate the files that programmers work on, called working copies, from the master copies of the same files, which are stored in a repository. The programmers never work on the repository. They check out their working copies from the repository, make changes, and then check in their changes. Every time a programmer commits a file, the VC system creates a new version in the repository. In this way, the repository contains all versions of a file. In addition, it also highlights the comparison between various version control systems. INSET: Version Control System Resources..

The article discusses ways to identify and capture early aspects in requirements and architecture activities related to computer softwares. Early aspects are concerns that crosscut an artifact's dominant decomposition or base modules derived from the dominant separation-of-concerns criterion, in the early stages of the software life cycle. Identifying and managing early aspects helps in improving modularity in the requirements and architecture design and to detect conflicting concerns early, thus resolving trade-offs. Besides, identifying aspects at one stage provides benefits downstream. Knowledge of requirements-level aspects helps architects in designing a better systems. Similarly, knowing architecture-level aspects helps produce a better implementation. Early aspects can measure development activities and many find their way into the code as traditional implementation aspects. Identifying early aspects across phases can increase the consistency of requirements and architecture designs with each other and provides a rationale and traceability for aspects across life-cycle activities. INSET: Dominant Decomposition in Early Software Development..