DOCSLIB.ORG

A Practical Guide for Pipeline Construction Inspectors: Pierre Bigras, P.Eng

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Practical Guide for Pipeline Construction Inspectors: Pierre Bigras, P.Eng A Practical Guide for Pipeline Construction Inspectors Published March 2016 © 2016 CEPA Foundation Inc. and INGAA Foundation Inc. Page 2 of 131 ACKNOWLEDGEMENTS This document was developed through the generous and continual support of all CEPA Foundation and INGAA Foundation members. CEPA Foundation Executive Director: Kim McCaig, MBA (CEPA Foundation) CEPA Foundation Body of Knowledge Subcommittee: David Montemurro (TransCanada Corp.) CEPA Foundation Pipeline Inspector Certification Committee Chair: Jason Landa (JSG Professional Services ULC, a Johnson Service Group Company) CEPA Foundation Certification Subcommittee: Andy Duncan, P.Eng. (Enbridge Inc.) INGAA Foundation Executive Director: Richard Hoffmann, MSCE (INGAA Foundation) INGAA Foundation Sponsor & Subcommittee Chair for Pipeline Inspector Certification: David Montemurro (TransCanada Corp.) INGAA Foundation Certification Subcommittee Chair: Andy Duncan, P.Eng. (Enbridge Inc.) INGAA Foundation Subcommittee Chair for Development of A Practical Guide for Pipeline Construction Inspectors: Pierre Bigras, P.Eng. (Pacific Gas and Electric Company) Working Group Members: Thomas Anderson (Henkels & McCoy, Inc.) Pierre Bigras, P.Eng. (Pacific Gas and Electric Company) Scott Culley (CDI Corp.) Victor R. Flores Jr., P.E. (Enable Midstream Partners, LP) Bryon D. Gaskin (Spectra Energy Corp.) Jason Landa (JSG Professional Services ULC, a Johnson Service Group Company) Roger Lemieux (TransCanada Corp.) Kirk Peterman (Energy Transfer Partners, LP) Joseph Prine (The Williams Companies, Inc.) Andy Purves, P.Eng. (Stantec Inc.) Ritch Rappel, MBA (Enbridge Inc.) Bill Watts, P.Eng. (Alliance Pipeline Ltd.) In collaboration with PBoK Technical Training Ltd.: Simon van Leeuwen Reena Sahney, P.Eng. Annie Sio Page 3 of 131 Page 4 of 131 Table of Contents ACKNOWLEDGEMENTS ............................................................................................................ 3 1.0 Introduction ...................................................................................................................... 9 2.0 Purpose ........................................................................................................................... 9 3.0 Scope .............................................................................................................................. 9 4.0 Revisions to this Document ............................................................................................ 10 5.0 How to Use this Document ............................................................................................. 10 6.0 Pipeline Construction Inspector – Foundational Information ........................................... 11 6.1 Authority ............................................................................................................. 13 6.2 Code of Conduct ................................................................................................. 13 6.3 Worker, Site, and Construction Safety ................................................................ 14 6.4 Quality, Deficiencies, and Non-conformance Procedures ................................... 15 6.4.1 Escalation Processes ............................................................................................ 16 6.4.2 Personal Violations ............................................................................................... 16 6.5 Environmental Considerations ............................................................................ 17 6.6 Execution of Work .............................................................................................. 18 6.7 Administration of Contractual Obligations ........................................................... 19 6.8 Records Management ........................................................................................ 21 6.9 Personnel Qualifications and Certifications ......................................................... 22 6.10 Equipment Calibration ........................................................................................ 22 6.11 Incident Reporting .............................................................................................. 22 References – Foundational Information.......................................................................... 23 7.0 Survey ........................................................................................................................... 25 7.1 Overview ............................................................................................................ 25 7.2 Inputs ................................................................................................................. 25 7.3 Execution ............................................................................................................ 25 7.4 Outputs ............................................................................................................... 26 Detailed Checklists – Surveying ..................................................................................... 27 7.5 Typical Input Requirements for Survey Inspection .............................................. 27 7.6 Best Practice Items for Inspecting Typical Surveying Operations........................ 28 7.7 Typical Outputs for Survey Inspection ................................................................ 32 References – Survey...................................................................................................... 32 8.0 Clearing and Grading ..................................................................................................... 33 8.1 Overview ............................................................................................................ 33 8.2 Inputs ................................................................................................................. 33 8.3 Execution ............................................................................................................ 33 Page 5 of 131 8.4 Outputs ............................................................................................................... 35 Detailed Checklists – Clearing and Grading ................................................................... 36 8.5 Typical Input Requirements for Clearing and Grading Inspection ....................... 36 8.6 Best Practice Items for Inspecting Typical Clearing and Grading Operations ...... 37 8.7 Typical Outputs for Clearing and Grading Inspection .......................................... 43 References – Clearing and Grading ............................................................................... 44 9.0 Stockpiling and Stringing ................................................................................................ 45 9.1 Overview ............................................................................................................ 45 9.2 Inputs ................................................................................................................. 45 9.3 Execution ............................................................................................................ 45 9.4 Outputs ............................................................................................................... 46 Detailed Checklists – Stockpiling and Stringing .............................................................. 47 9.5 Typical Inputs for Stringing and Stockpiling Inspection ....................................... 47 9.6 Best Practices for Typical Stringing and Stockpiling Inspection .......................... 48 9.7 Typical Outputs for Stockpiling and Stringing Inspection ..................................... 52 References – Stockpiling and Stringing .......................................................................... 53 10.0 Field Bending ................................................................................................................. 55 10.1 Overview ............................................................................................................ 55 10.2 Inputs ................................................................................................................. 55 10.3 Execution ............................................................................................................ 55 10.4 Outputs ............................................................................................................... 56 Detailed Checklists – Field Bending ............................................................................... 57 10.5 Typical Input Requirements for Field Bending Inspection ................................... 57 10.6 Best Practice Items for Inspecting Typical Field Bending Operations .................. 58 10.7 Typical Outputs for Field Bending Inspection ...................................................... 59 References – Field Bending ........................................................................................... 60 11.0 Ditching and Excavation ................................................................................................. 61 11.1 Overview ............................................................................................................ 61 11.2 Inputs ................................................................................................................. 61 11.3 Execution ............................................................................................................ 62 11.4 Outputs
Load more

Recommended publications
  • Asp Net Core Request Pipeline
    Asp Net Core Request Pipeline Is Royce always cowled and multilobate when achromatize some wall very instanter and lawlessly? Hobbyless and flustered brazensVladamir regressively? cocainizing her intangibles tiptoed or cluster advertently. Is Patric fuzzed or paintable when cogs some theocracy Or gray may choose to berry the request. Json files etc and community of response body is not inject all low maintenance, we will be same coin. Another through components that asp and cto of. How extensible it crashes, just by one of startup class controller. Do the extended with really very complex scenarios when he enjoys sharing it ever was to delete models first user makes for node. Even add to implement captcha in startup class to the same concept is the reason you want to. Let us a pipeline to any incoming request processing, firefox still create an output? For an app to build a cup of. Razor pages uses handler methods to deal of incoming HTTP request. Ask how the above mentioned in last middleware, the come to tell who are ready simply obsolete at asp and options. Have asp and asp net core request pipeline but will not be mapped to pipeline io threads to work both. The internet and when creating sawdust in snippets or improvements that by one description be a request pipeline branching. Help editing this article, ordinary code inside of hosting infrastructure asp and actions before, we issue was not. The body to deal with minimal footprint to entity framework of needed loans for each middleware will take a docker, that receive criticism.
    [Show full text]
  • Stclang: State Thread Composition As a Foundation for Monadic Dataflow Parallelism Sebastian Ertel∗ Justus Adam Norman A
    STCLang: State Thread Composition as a Foundation for Monadic Dataflow Parallelism Sebastian Ertel∗ Justus Adam Norman A. Rink Dresden Research Lab Chair for Compiler Construction Chair for Compiler Construction Huawei Technologies Technische Universität Dresden Technische Universität Dresden Dresden, Germany Dresden, Germany Dresden, Germany [email protected] [email protected] [email protected] Andrés Goens Jeronimo Castrillon Chair for Compiler Construction Chair for Compiler Construction Technische Universität Dresden Technische Universität Dresden Dresden, Germany Dresden, Germany [email protected] [email protected] Abstract using monad-par and LVars to expose parallelism explicitly Dataflow execution models are used to build highly scalable and reach the same level of performance, showing that our parallel systems. A programming model that targets parallel programming model successfully extracts parallelism that dataflow execution must answer the following question: How is present in an algorithm. Further evaluation shows that can parallelism between two dependent nodes in a dataflow smap is expressive enough to implement parallel reductions graph be exploited? This is difficult when the dataflow lan- and our programming model resolves short-comings of the guage or programming model is implemented by a monad, stream-based programming model for current state-of-the- as is common in the functional community, since express- art big data processing systems. ing dependence between nodes by a monadic bind suggests CCS Concepts • Software and its engineering → Func- sequential execution. Even in monadic constructs that explic- tional languages. itly separate state from computation, problems arise due to the need to reason about opaquely defined state.
    [Show full text]
  • Let's Get Functional
    5 LET’S GET FUNCTIONAL I’ve mentioned several times that F# is a functional language, but as you’ve learned from previous chapters you can build rich applications in F# without using any functional techniques. Does that mean that F# isn’t really a functional language? No. F# is a general-purpose, multi paradigm language that allows you to program in the style most suited to your task. It is considered a functional-first lan- guage, meaning that its constructs encourage a functional style. In other words, when developing in F# you should favor functional approaches whenever possible and switch to other styles as appropriate. In this chapter, we’ll see what functional programming really is and how functions in F# differ from those in other languages. Once we’ve estab- lished that foundation, we’ll explore several data types commonly used with functional programming and take a brief side trip into lazy evaluation. The Book of F# © 2014 by Dave Fancher What Is Functional Programming? Functional programming takes a fundamentally different approach toward developing software than object-oriented programming. While object-oriented programming is primarily concerned with managing an ever-changing system state, functional programming emphasizes immutability and the application of deterministic functions. This difference drastically changes the way you build software, because in object-oriented programming you’re mostly concerned with defining classes (or structs), whereas in functional programming your focus is on defining functions with particular emphasis on their input and output. F# is an impure functional language where data is immutable by default, though you can still define mutable data or cause other side effects in your functions.
    [Show full text]
  • BIOVIA Pipeline Pilot System Requirements
    SYSTEM REQUIREMENTS PIPELINE PILOT 2020 Copyright Notice ©2019 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3DVIA, 3DSWYM, BIOVIA, NETVIBES, IFWE and 3DEXCITE, are commercial trademarks or registered trademarks of Dassault Systèmes, a French "société européenne" (Versailles Commercial Register # B 322 306 440), or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained by using Dassault Systèmes software, acknowledge the source in an appropriate format. For example: "Computational results were obtained by using Dassault Systèmes BIOVIA software programs. Pipeline Pilot Server was used to perform the calculations and to generate the graphical results." Dassault Systèmes may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to Dassault Systèmes Customer Support, either by visiting https://www.3ds.com/support/ and clicking Call us or Submit a request, or by writing to: Dassault Systèmes Customer Support 10, Rue Marcel Dassault 78140 Vélizy-Villacoublay FRANCE Contents About This Document 1 Definitions 1 Additional Information 1 Dassault Systèmes Support Resources 1 Pipeline Pilot Server Requirements 2 Minimum Hardware
    [Show full text]
  • Fast Linux I/O in the Unix Tradition
    — preprint only: final version will appear in OSR, July 2008 — PipesFS: Fast Linux I/O in the Unix Tradition Willem de Bruijn Herbert Bos Vrije Universiteit Amsterdam Vrije Universiteit Amsterdam and NICTA [email protected] [email protected] ABSTRACT ory wall” [26]). To improve throughput, it is now essential This paper presents PipesFS, an I/O architecture for Linux to avoid all unnecessary memory operations. Inefficient I/O 2.6 that increases I/O throughput and adds support for het- primitives exacerbate the effects of the memory wall by in- erogeneous parallel processors by (1) collapsing many I/O curring unnecessary copying and context switching, and as interfaces onto one: the Unix pipeline, (2) increasing pipe a result of these cache misses. efficiency and (3) exploiting pipeline modularity to spread computation across all available processors. Contribution. We revisit the Unix pipeline as a generic model for streaming I/O, but modify it to reduce overhead, PipesFS extends the pipeline model to kernel I/O and com- extend it to integrate kernel processing and complement it municates with applications through a Linux virtual filesys- with support for anycore execution. We link kernel and tem (VFS), where directory nodes represent operations and userspace processing through a virtual filesystem, PipesFS, pipe nodes export live kernel data. Users can thus interact that presents kernel operations as directories and live data as with kernel I/O through existing calls like mkdir, tools like pipes. This solution avoids new interfaces and so unlocks all grep, most languages and even shell scripts.
    [Show full text]
  • Making a Faster Curry with Extensional Types
    Making a Faster Curry with Extensional Types Paul Downen Simon Peyton Jones Zachary Sullivan Microsoft Research Zena M. Ariola Cambridge, UK University of Oregon [email protected] Eugene, Oregon, USA [email protected] [email protected] [email protected] Abstract 1 Introduction Curried functions apparently take one argument at a time, Consider these two function definitions: which is slow. So optimizing compilers for higher-order lan- guages invariably have some mechanism for working around f1 = λx: let z = h x x in λy:e y z currying by passing several arguments at once, as many as f = λx:λy: let z = h x x in e y z the function can handle, which is known as its arity. But 2 such mechanisms are often ad-hoc, and do not work at all in higher-order functions. We show how extensional, call- It is highly desirable for an optimizing compiler to η ex- by-name functions have the correct behavior for directly pand f1 into f2. The function f1 takes only a single argu- expressing the arity of curried functions. And these exten- ment before returning a heap-allocated function closure; sional functions can stand side-by-side with functions native then that closure must subsequently be called by passing the to practical programming languages, which do not use call- second argument. In contrast, f2 can take both arguments by-name evaluation. Integrating call-by-name with other at once, without constructing an intermediate closure, and evaluation strategies in the same intermediate language ex- this can make a huge difference to run-time performance in presses the arity of a function in its type and gives a princi- practice [Marlow and Peyton Jones 2004].
    [Show full text]
  • Pipecheck: 3D Scanning Solution Pipeline Integrity Assessment
    NDT SOLUTIONS 3D3D SCANNING SCANNING SOLUTION SOLUTION FORFOR PIPELINE PIPELINE INTEGRITY INTEGRITY ASSESSMENTASSESSMENT CODE-COMPLIANT CODE-COMPLIANT Pipeline operators and NDT service companies are facing an increasing pressure from regulation authorities and environmentalist groups to guarantee pipeline networks integrity, while wanting to keep maintenance costs as low as possible. Field crews are experiencing pressure to complete inspection as quickly as possible so the excavation site can be backfilled, and the pipeline, put back into service in the shortest time. Thus, the use of surface inspection tools that are reliable, efficient and user-friendly is of paramount importance. Creaform has developed the PipecheckTM solution for pipeline integrity assessment. The solution includes a HandySCAN 3DTM portable handheld scanner and the Pipecheck software. Thanks to this unique 3D scanning technology and innovative software, surface inspection has been reinvented completely! RELIABLE. EFFICIENT. EASY. INTRODUCING PIPECHECK. PIPECHECK SOFTWARE MODULES CORROSION MECHANICAL DAMAGE Pipecheck’s pipeline corrosion software module offers very fast and As its name states, this software module has been developed reliable data processing that generates instant, on-site results. specifically for pipeline mechanical damage analysis. This module In comparison with traditional measurement methods, this software features numerous key functionalities that increase dent understanding offers accuracy and repeatability that are beyond expectations. and facilitate the decision making process. ADVANCED FUNCTIONALITIES CORROSION IN ILI CORRELATION MECHANICAL DAMAGE STRAIGHTENING OPERATION TOOL Being able to separate material loss depth Traditional methods for depth measurement The ILI Correlation tool is used to correlate from a mechanical damage deformation is (pit gauge) on field bends can’t be used in-line inspection data with the Pipecheck 3D no longer a dream.
    [Show full text]
  • Characteristics of Workloads Using the Pipeline Programming Model
    Characteristics of Workloads Using the Pipeline Programming Model Christian Bienia and Kai Li Department of Computer Science, Princeton University {cbienia, li}@cs.princeton.edu Abstract covered by their applications. Second, we demonstrate that Pipeline parallel programming is a frequently used model to the programs using the pipeline model have different char- program applications on multiprocessors. Despite its popu- acteristics compared to other workloads. The differences larity, there is a lack of studies of the characteristics of such are significant and systematic in nature, which justifies the workloads. This paper gives an overview of the pipeline existence of pipelined programs in the PARSEC benchmark model and its typical implementations for multiprocessors. suite [2]. This suggests that pipelined workloads should be We present implementation choices and analyze their im- considered for the inclusion in future benchmark programs pact on the program. We furthermore show that workloads for computer architecture studies. that use the pipeline model have their own unique charac- The remainder of the paper is structured as follows: teristics that should be considered when selecting a set of Section 2 presents a survey of the pipeline parallelization benchmarks. Such information can be beneficial for pro- model. In Section 3 we discuss how we studied the impact gram developers as well as for computer architects who of the pipeline model on the workload characteristics, and want to understand the behavior of applications. we present our experimental results in Section 4. Related work is discussed in Section 5 before we conclude in Sec- 1 Introduction tion 6. Modern parallel workloads are becoming increasingly di- verse and use a wide range of techniques and methods to 2 Pipeline Programming Model take advantage of multiprocessors.
    [Show full text]
  • Elastic Pipeline Design of High Performance Micro-Controller YL8MCU for Signal Processing of Digital Home Appliances
    Send Orders for Reprints to [email protected] The Open Automation and Control Systems Journal, 2015, 7, 863-872 863 Open Access Elastic Pipeline Design of High Performance Micro-Controller YL8MCU for Signal Processing of Digital Home Appliances Fulong Chen1,*, Yunxiang Sun2, Chuanxin Zhao2, Jie Yang2, Heping Ye2, Junru Zhu2, and Qimei Tang2 1Department of Computer Science & Technology, Anhui Normal University, Wuhu, Anhui 241002, China 2Network and Information Security Engineering Research Center, Anhui Normal University, Wuhu, Anhui 241002, China Abstract-With the growing complexity of the structure and function of the digital home appliance controllers, the higher requirements on the design of integrated circuits are expected. In view of the lower efficiency of the traditional large scale integrated circuit design, such as long design cycle, high investment and bad flexibility, therefore, the traditional design method is unable to meet the rapid product development. A design and its implementation scheme based on System-on- Programmable-Chip (SoPC) technologies with the Intellectual Property (IP) core parametric technology and elastic design method are proposed for the Micro-controller Unit (MCU) YL8MCU applied in digital home appliances. It makes used of Reduced Instruction Set Computer (RISC) framework and 5-stage pipeline technology for designing the instruction sys- tem and hardware structure so as to improve the speed of processing data and instructions. Finally the correctness and fea- sibility of its function is verified with the integrated verification, the IP function module verification based on coverage and the simulation test of the controlling flow for the washer. The results show that YL8MCU meets the requirements of digital home appliances and supports system integration on chip.
    [Show full text]
  • Interleaving Data and Effects"
    Archived version from NCDOCKS Institutional Repository http://libres.uncg.edu/ir/asu/ Interleaving data and effects By: Robert Atkey and Patricia Johann Abstract: The study of programming with and reasoning about inductive datatypes such as lists and trees has benefited from the simple categorical principle of initial algebras. In initial algebra semantics, each inductive datatype is represented by an initial f-algebra for an appropriate functor f. The initial algebra principle then supports the straightforward derivation of definitional principles and proof principles for these datatypes. This technique has been expanded to a whole methodology of structured functional programming, often called origami programming.In this article we show how to extend initial algebra semantics from pure inductive datatypes to inductive datatypes interleaved with computational effects. Inductive datatypes interleaved with effects arise naturally in many computational settings. For example, incrementally reading characters from a file generates a list of characters interleaved with input/output actions, and lazily constructed infinite values can be represented by pure data interleaved with the possibility of non-terminating computation. Straightforward application of initial algebra techniques to effectful datatypes leads either to unsound conclusions if we ignore the possibility of effects, or to unnecessarily complicated reasoning because the pure and effectful concerns must be considered simultaneously. We show how pure and effectful concerns can be separated using the abstraction of initial f-and-m-algebras, where the functor f describes the pure part of a datatype and the monad m describes the interleaved effects. Because initial f-and-m-algebras are the analogue for the effectful setting of initial f- algebras, they support the extension of the standard definitional and proof principles to the effectful setting.
    [Show full text]
  • Pipelines Guide and Reference
    Pipelines Guide and Reference Ed Tomlinson Jeff Hennick René Jansen Version 4.01-GA of March 20, 2021 THE REXX LANGUAGE ASSOCIATION NetRexx Programming Series ISBN 978-90-819090-3-7 Publication Data ©Copyright The Rexx Language Association, 2011- 2021 All original material in this publication is published under the Creative Commons - Share Alike 3.0 License as stated at http://creativecommons.org/licenses/by-nc-sa/3.0/us/legalcode. The responsible publisher of this edition is identified as IBizz IT Services and Consultancy, Amsteldijk 14, 1074 HR Amsterdam, a registered company governed by the laws of the Kingdom of The Netherlands. This edition is registered under ISBN 978-90-819090-3-7 ISBN 978-90-819090-3-7 9 789081 909037 I Contents The NetR Programming Series i 1 Introduction 1 2 The Pipeline Concept 2 2.1 What is a Pipeline? 2 2.2 Stage 2 2.3 Device Driver 3 3 Running pipelines 4 3.1 Configuration 4 3.2 From the NetREXX Workspace (nrws) with direct execution 5 3.3 From the command line with direct execution 6 3.4 Precompiled Pipelines 6 3.5 Compiled from an .njp file 7 3.6 Compiled from an .njp file with additional stage definitions in NetREXX 7 4 Example Session 8 5 Write your own Filters 12 6 More advanced Pipelines 14 7 Device Drivers 15 8 Record Selection 17 9 Filters 18 10 Other Stages 19 11 Multi-Stream Pipelines 20 12 Pipeline Stalls 22 13 How to use a pipe in a NetR program 24 II 14 Giving commands to the operating system 27 14.1 Built-ins 27 15 TCP/IP Networking 28 16 Selecting from relational databases 30 17 The Pipes Runner 31 18 The Pipes Compiler 32 19 Built-in Stages 33 20 Differences with CMS Pipelines 34 Index 83 III The NetR Programming Series This book is part of a library, the NetR Programming Series, documenting the NetREXX programming language and its use and applications.
    [Show full text]
  • Exploring Languages with Interpreters and Functional Programming Chapter 16
    Exploring Languages with Interpreters and Functional Programming Chapter 16 H. Conrad Cunningham 15 October 2018 Contents 16 Haskell Function Concepts 2 16.1 Chapter Introduction . .2 16.2 Strictness . .2 16.3 Currying and Partial Application . .3 16.4 Operator Sections . .4 16.5 Combinators . .5 16.6 Functional Composition . .7 16.7 Function Pipelines . .7 16.8 Lambda Expressions . .9 16.9 Application Operator $ ....................... 10 16.10Eager Evaluation Using seq and $! ................. 11 16.11What Next? . 12 16.12Exercises . 13 16.13Acknowledgements . 13 16.14References . 14 16.15Terms and Concepts . 14 Copyright (C) 2016, 2017, 2018, H. Conrad Cunningham Professor of Computer and Information Science University of Mississippi 211 Weir Hall P.O. Box 1848 University, MS 38677 (662) 915-5358 Browser Advisory: The HTML version of this textbook requires a browser that supports the display of MathML. A good choice as of October 2018 is a recent version of Firefox from Mozilla. 1 16 Haskell Function Concepts 16.1 Chapter Introduction The previous chapter introduced the concepts of first-class and higher-order functions and generalized common computational patterns to construct a library of useful higher-order functions to process lists. This chapter continues to examine those concepts and their implications for Haskell programming. It explores strictness, currying, partial application, com- binators, operator sections, functional composition, inline function definitions, evaluation strategies, and related methods. The Haskell module for this chapter is in FunctionConcepts.hs. 16.2 Strictness In the discussion of the fold functions, the previous chapter introduced the concept of strictness. In this section, we explore that in more depth.
    [Show full text]