Military Applications Of Data Analytics Data Analytics Applications 1st Edition Kevin Huggins Editor instant download
Military Applications Of Data Analytics Data Analytics Applications 1st Edition Kevin Huggins Editor instant download
https://ebookbell.com/product/military-applications-of-data-
analytics-data-analytics-applications-1st-edition-kevin-huggins-
editor-11300924
https://ebookbell.com/product/military-applications-of-data-analytics-
huggins-kevin-9953730
https://ebookbell.com/product/military-applications-of-modeling-
selected-case-studies-francis-p-hoeber-44693610
https://ebookbell.com/product/the-democratic-offset-contestation-
deliberation-and-participation-regarding-military-applications-of-ai-
johannes-thumfart-49936434
https://ebookbell.com/product/applications-of-mathematics-and-
informatics-in-military-science-nicholas-j-daras-4158188
Applications Of Operations Research And Management Science For
Military Decision Making 1st Ed 2019 William P Fox
https://ebookbell.com/product/applications-of-operations-research-and-
management-science-for-military-decision-making-1st-ed-2019-william-p-
fox-10797210
https://ebookbell.com/product/military-displays-technology-and-
applications-daniel-d-desjardins-society-of-photooptical-
instrumentation-engineers-4723932
https://ebookbell.com/product/the-application-of-the-european-
convention-on-human-rights-to-military-operations-stuart-
wallace-10898690
https://ebookbell.com/product/figurative-uses-of-animal-names-in-
latin-and-their-application-to-military-devices-a-study-in-
semantics-1912-eugene-stock-mccartney-55044232
https://ebookbell.com/product/monitoring-metabolic-status-predicting-
decrements-in-physiological-and-cognitive-performance-committee-on-
metabolic-monitoring-for-military-field-applications-2134626
Military Applications
of Data Analytics
Data Analytics Applications
Series Editor: Jay Liebowitz
PUBLISHED
Actionable Intelligence for Healthcare
Jay Liebowitz and Amanda Dawson
Edited by
Kevin Huggins
AN AUERBACH BOOK
CRC Press
Taylor & Francis Group
6000 Broken Sound Parkway NW, Suite 300
Boca Raton, FL 33487-2742
This book contains information obtained from authentic and highly regarded sources. Reasonable efforts
have been made to publish reliable data and information, but the author and publisher cannot assume
responsibility for the validity of all materials or the consequences of their use. The authors and publishers
have attempted to trace the copyright holders of all material reproduced in this publication and apologize
to copyright holders if permission to publish in this form has not been obtained. If any copyright material
has not been acknowledged please write and let us know so we may rectify in any future reprint.
Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced,
transmitted, or utilized in any form by any electronic, mechanical, or other means, now known or
hereafter invented, including photocopying, microfilming, and recording, or in any information storage
or retrieval system, without written permission from the publishers.
For permission to photocopy or use material electronically from this work, please access www.copyright.
com (http://www.copyright.com/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood
Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and
registration for a variety of users. For organizations that have been granted a photocopy license by the
CCC, a separate system of payment has been arranged.
Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are
used only for identification and explanation without intent to infringe.
Visit the Taylor & Francis Web site at
http://www.taylorandfrancis.com
Preface ...............................................................................................................vii
Acknowledgments ..............................................................................................ix
Editor ..................................................................................................................xi
Contributors .....................................................................................................xiii
1 Bayesian Networks for Descriptive Analytics in Military
Equipment Applications .........................................................................1
DAVID AEBISCHER
v
vi ◾ Contents
Index ...........................................................................................................187
Preface
Military organizations around the world are normally huge producers and consumers
of data. Accordingly, they stand to gain from the many benefits associated with data
analytics. However, for leaders in defense organizations—either government or
industry—accessible use cases are not always available. The reason that I embarked on
this book was to provide a diverse collection of detailed use cases that could serve as a
representation of the realm of possibilities in military data analytics. I trust you will find
it useful, and I look forward to hearing about your successful analytics projects.
vii
Acknowledgments
This, like most other works, was truly a team effort. First, I’d like to thank my
family for their patience and encouragement. Additionally, I’m grateful to Jay
Liebowitz for giving me this opportunity. It was definitely an adventure. I am also
indebted to my colleagues at Harrisburg University for their insights and recom-
mendations. Finally, I would like to thank my awesome team of reviewers. They
generously shared their expertise to raise the quality of this work significantly. The
review team consisted of the following experts:
ix
Editor
xi
Contributors
xiii
xiv ◾ Contributors
Contents
Introduction ..........................................................................................................1
DSEV ...................................................................................................................4
Frame the Problem ................................................................................................5
Ready the Experts..................................................................................................5
Pre-DSEV ...........................................................................................................12
Define .................................................................................................................13
Structure .............................................................................................................14
Elicit ...................................................................................................................17
Verify ..................................................................................................................21
Critical Decision Method (CDM) .......................................................................23
References ...........................................................................................................28
Introduction
The lives of U.S. soldiers in combat depend on complex weapon systems and
advanced technologies. Operational command, control, communications, computers,
intelligence, surveillance, and reconnaissance (C4ISR) systems provide soldiers the
1
2 ◾ Military Applications of Data Analytics
tools to conduct operations against the enemy and to maintain life-support. When
equipment fails, lives are in danger; therefore, fast and accurate diagnosis and repair of
equipment may mean the difference between life and death. But in combat conditions,
the resources available to support maintenance of these systems are minimal.
Following a critical system failure, technical support personnel may take days to
arrive via helicopter or ground convoy, leaving soldiers and civilian experts exposed
to battlefield risks. What is needed is a means to translate experiential knowledge and
scientific theory—the collective knowledge base—into a fingertip-accessible, artificial
intelligence application for soldiers. To meet this need, we suggest an operations research
(OR) approach to codifying expert knowledge about Army equipment and applying
that knowledge to troubleshooting equipment in combat situations. We infuse a
classic knowledge-management spiral with OR techniques: from socializing advanced
technical concepts and eliciting tacit knowledge, to encoding expert knowledge in
Bayesian Belief Networks, to creating an intuitive, instructive, and learning interface,
and finally, to a soldier internalizing a practical tool in daily work. We start development
from this concept with counterfactuals: What would have happened differently had a
soldier been able to repair a piece of critical equipment? Could the ability to have made
a critical diagnosis and repair prevented an injury or death? The development process,
then, takes on all the rigor of a scientific experiment and is developed assuming the
most extreme combat conditions. It is assumed that our working model is in the hands
of a soldier who is engaged with the enemy in extreme environmental conditions,
with limited knowledge of, and experience with, the equipment that has failed, with
limited tools, but with fellow soldiers depending on him (her) to take the necessary
steps to bring their life-saving equipment back into operation and get the unit out of
danger (Aebischer et al., 2017). The end product is a true expert system for soldiers.
Such systems will improve readiness and availability of equipment while generating
a sustainable cost-savings model through personnel and direct labor reductions. The
system ensures fully functional operation in a disconnected environment, making it
impervious to cyber-attack and security risks. But most importantly, these systems
are a means to mitigate combat risk. Reducing requirements for technical support
personnel reduces requirements for helicopter and ground-convoy movements, and
this translates directly to reductions in combat casualties (Bilmes, 2013).
In On War, Carl Von Clausewitz wrote, “War is the realm of uncertainty; three
quarters of the factors on which action is based are wrapped in a fog of greater or lesser
uncertainty” (Kiesling, 2001). Clausewitz’s “Fog of War” metaphor is well-made and
oft-used, becoming so popular as to become part of the modern military lexicon.
Analysis of his writing has, naturally, led to discussion about how information tech-
nology can be brought to bear to reduce battlefield entropy. From this familiar terri-
tory, let us deliberately examine data analytics in context with combat uncertainty. Let
us further refine that to the combat soldier and his equipment—in the most extreme
scenario of enemy threat, geography, and environment—and determine what data
analytics can put at a soldier’s fingertips. This task requires a fine balance of complex-
ity and usability. It must be mathematically precise, yet infused with tacit knowledge.
Bayesian Networks for Descriptive Analytics in Military ◾ 3
It must be exhaustive, as the consequences of failure can be dire. Most of all, the task
must establish the primacy of soldiers at the point of need. We submit that this is a
doable and necessary task and an opportunity to apply a unique analytics solution
to this, and other, multivariate problems. This chapter will provide an introductory
guide for tapping into an expert knowledge base and codifying that knowledge into
a practical, useful, and user-friendly working model for diagnostics. In order, we will
provide a general description of all the tools, techniques, and resources needed to con-
struct the model, and then proceed through a practical example of model building.
The category of Descriptive Analytics, and diagnostics as a sub-category, serves
well to frame our initial efforts. Korb and Nicholson (2011) describe:
By building artifacts which model our best understanding of how
humans do things (which can be called descriptive artificial intelligence)
and also building artifacts which model our best understanding of what
is optimal in these activities (normative artificial intelligence), we can
further our understanding of the nature of intelligence and also produce
some very useful tools for science, government, and industry. (p. 21)
Causal analysis is at the heart of descriptive analytics. To perform this analysis,
we will need a couple of tools: a knowledge engineering tool to capture knowledge
about the domain of interest, and Bayesian networks to codify and represent that
knowledge. The knowledge engineering tool and the Bayesian network tool work
hand-in-hand, so they will be detailed as such. We will also need to designate a spe-
cific C4ISR system as a use case and as a practical example to demonstrate how each
tool works separately and in combination with the other to model complex systems.
For this, we will use the Army’s diesel engine-driven tactical generator, the primary
source of power for Army Command Post operations. Generators meet our needs in
terms of multi-domain complexity (electrical, electronics, and electro-mechanical)
and in terms of ubiquity in combat environments. We will look at these tools indi-
vidually in some detail, but we will focus more on how they overlap and how they
integrate around our diesel generator use case. All of this goes toward learning how
to work with limited or nonexistent data. Our richest source of knowledge is experts,
and our actual data-generating process is from facilitating effective and efficient
knowledge elicitation sessions with those experts. Our first tool will help us navigate
the challenging, but rewarding, world of working with experts and expertise.
It is easy to recall instances where we have witnessed experts at work. The great
artists—composers, painters, poets, musicians—seem to possess something that
transcends talent, and they describe their art as something that occurs when their
ideas have gone somewhere that was not intended. The process by which they cre-
ate and do is not describable, existing only in their heads. It is much the same with
equipment experts—possessing a blend of experiential and theoretical knowledge
and an innate ability to apply that knowledge in ways few of us can comprehend.
Coming to understand, and make explicit, even a fraction of this knowledge is the
goal of knowledge engineering and the process of knowledge elicitation (Figure 1.1).
4 ◾ Military Applications of Data Analytics
Human expert
Dialogue
Knowledge
engineer
Explicit
Knowledge base
of expert system
DSEV
Define, Structure, Verify, Elicit (DSEV) is a field-proven method for developing
Bayesian models strictly from expert knowledge with a unique blend of soft and hard
skills. DSEV is infused with techniques that mitigate bias and ensure the elicitation
process aggregates expert judgments into a unified network. We will first outline the
methods we use to execute each phase of the model and then, later, demonstrate how
it is applicable, flexible, and scalable to a practical problem domain.
DSEV starts, stops, and cycles with experts. In both the theory and practice of
Bayesian networks, assumptions—expert knowledge about any specific problem
domain—are a necessary component. But it is inherently difficult for experts to explain
what they know, and equally difficult for non-experts to understand what experts
are saying. What is needed is a formalism for bridging the gap between experts and
non-experts and codifying complex technical concepts into graphical structure and
probability distributions. Our DSEV objective is an exhaustive probabilistic model of
how the generator can fail—with expert-based pathways through each failure mode.
But DSEV requires unique facilitation skills, so, prior to starting the DSEV process, we
want to do some preparatory tasks so that facilitators and experts—the whole team—
understand the tools, tasks, and processes associated with Figure 1.2 (Hepler et al., 2015).
Bayesian Networks for Descriptive Analytics in Military ◾ 5
Frame the Ready the Build the Validate and Use the
problem experts network update model
Define Structure
DSEV
Verify Elicit
150
100
50
0
0 2 4 6 8
Group size
Research on practical group events bears that out, with group member ratings
converging to between four and five members for optimum efficiency (Hackman and
Vidmar, 1970). It is usually best to choose “complementary experts”: some with specific
hands-on experience with the equipment, and some with more academic or theoretical
perspectives. It also helps to have an expert with significant general knowledge in the
field (domain experience) but not specific experience on the system. This combination
provides a good setting for “productive friction” between experts, stimulating the
CDM “deepening” process that reveals new insights into the domain. The expert team
is combined with a facilitation team consisting, normally, of two knowledge engineers,
with one focusing on doing the direct elicitation—extracting and interpreting the
expert knowledge—and one focusing on building a model based on the elicitation and
interpretation. Regular dialogue between knowledge engineers to clarify statements is
expected, and it is often helpful to reverse roles at some interval during the elicitation.
With a well-organized and well-balanced team in place, the next step is to ensure the
experts know how their knowledge will be used and how will it be represented.
Bayesian networks (BNs) are probabilistic models of how we believe our “world”
works (Pearl, 1988). BNs are based on Bayes theorem, an equation that calculates
the probability of an event (A) given we know an event (B) has occurred, or P (A|B)
(Figure 1.3).
Bayes Theorem
• Bayes theorem is most commonly used to estimate the
state of a hidden, causal variable H based on the
measured state of an observable variable D:
Likelihood
Prior
p(D|H)p(H)
p(H|D) =
p(D)
Posterior Evidence
Cause Effect
above, the arcs do indicate a cause and effect, or temporal, ordering. But information
flows in both directions—both with and against the arc direction. So knowing
the Engine Cranks but w/n Start and setting evidence accordingly will influence
the probability distribution of Battery and Ambient Temperature, just as setting
evidence on Ambient Temperature will influence the distribution of Battery and
Engine Cranks but w/n Start (Figure 1.6).
However, if we know B (Battery state of charge is LOW, as in Figure 1.7), and set
evidence accordingly, this closes the information path in both directions. We say, then,
that A and C are independent given (conditioned on) B, or that setting any evidence on
B makes A and C independent. This is intuitive because if we know the Battery state
of charge is low or high, then knowing Ambient Temperature is no longer useful with
respect to the “Engine Cranks but w/n Start” variable, and vice versa. This structure
type is particularly useful for modeling electrical wiring or fiber optic runs, as it will
translate an expert’s thought such as “a reading at test point B will make a test point A
reading unnecessary with respect to C” into a compact structural model.
In the common cause structure (A can cause B or C), B and C are marginally
dependent. Information can flow from B to C through A, and from C to B through A.
Consider a case where the “Cylinder Pressure” variable (A) can be the cause of both the
“Engine Cranks but w/n Start” (B) and “Compression Test” (C) variables. Knowing
the state of the “Engine Cranks but w/n Start” variable will certainly change our
reasoning (and probability distribution) on the “Compression Test” variable, and vice
versa (Figure 1.8).
However, if we already know the state of the “Cylinder Pressure” variable (we
know the cause) and enter evidence accordingly, this blocks the path between
effects through the cause in both directions. This is intuitive because knowing
the state of “Cylinder Pressure” makes knowing the state of “Engine Cranks but
w/n Start” no longer useful to our belief about “Compression Test,” and vice versa.
B and C are, then, independent given evidence for A (Figure 1.9).
The common cause structure translates expert’s statements such as “low cylin-
der pressure can cause engine starting problems and a marginal or low compression
test” directly into a compact model that reasons like the expert; that is, what tests
are most economical and most sensitive?
In the common effect structure, A or B can cause C. Comment effect structures
are also known as colliders. Information cannot flow from A to B in a collider
because C blocks the path of information in both directions. A and B are, then,
marginally independent. Consider a case where both the “Battery” and the “Fuel
System” could cause “Engine Cranks but w/n Start.” This is intuitive, as knowing
the state of “Battery” tells us nothing about “Fuel System” (Figure 1.10).
Cause 2 (B)
Cause 1 (A)
Engine Cranks
Effect (C)
but w/n Start
But, if we know the state of “Engine Cranks but w/n Start” and we enter evidence
accordingly, then this opens the path from A to B, making them dependent given
evidence for C. This is also intuitive. If we know the effect and we know the state of
one of the possible causes, then we can reason about the state of the other cause. In
network terms, if we know that “Battery” state is “low” and we have evidence that
“Engine Cranks but w/n Start” is “Yes,” then we can reason that “Fuel System” is less
likely to be the cause. This is known as “explaining away” and is a powerful tool for
articulating expert knowledge. The collider structure translates expert’s statements
such as “there are multiple causes for the engine to crank but not start” into a model
that reasons like an expert; that is, if A is true and we know C, then it is unnecessary
to test B (Figure 1.11).
LOW
With evidence entered for the effect and one
Battery Fuel System
cause, information flows between Cause A and
Cause B in either direction because C opens the
path. Cause A and B are, then, dependent
conditioned on C in the common effect/collider
structure (A ⫫ B)
YES
Engine Cranks
but w/n Start
The key takeaway from this section is that ANY piece of expert knowledge
(variables and relationships between variables) can be encoded using these three struc-
tures, or combinations thereof, by the knowledge engineering team. We now have all
the tools we need to develop the qualitative, or structural, component of BNs: the
DAG. The BN is incomplete, however, without a means to specify the relationships.
The quantitative component of the CBN is constructed using conditional prob-
ability tables (CPT) and conditional probability statements for each parent-child
relationship. These statements specify probabilities of each state of a child node
given the state of its parents (Figure 1.12).
Bayesian Networks for Descriptive Analytics in Military ◾ 11
We will discuss, in detail, some techniques for working with CPTs in the Elicit sec-
tion of DSEV. For now, it is easiest to consider this analogy when thinking about the
quantitative portion: experts use the DAG to model what they think the world of their
domain looks like; experts use the CPT to model how they move through that world.
The qualitative and quantitative components combine to make a BN. Note that all of the
structures described earlier are in use in the small network shown below (Figure 1.13).
Ambient Temperature
The experts need to understand the basics and building blocks of BNs, need
to know what their knowledge looks like in a BN, and need to see how the BN
changes in response to different evidence. This is usually accomplished by building
a small sample BN—6–8 nodes, as above—for a familiar domain and demonstrat-
ing how it changes, what structures are used to model different types of relation-
ships, and what biases are in play. The BN in Figure 1.13 draws from our use case.
While it is very basic, it demonstrates how easily relationships can be articulated
and how it can frame further development. The translation of expert knowledge is
such that the completed BN looks like, behaves like, and learns like the experts that
contributed to its construction. With our experts now knowledgeable of the process
and the tools, we move to a few other pre-DSEV tasks: framing the problem, iden-
tifying a target node, and generating the list of nodes (variables) that will provide
the input for our DSEV process.
Pre-DSEV
This initialization stage starts with creating one to two very descriptive and specific
sentences that fit under the objective and the use cases and that will guide the facili-
tation and model building. For our use case, we could use, “The generator type is
a 60 kilowatt (kW) B model. The generator’s diesel engine will crank (turn over)
but not start in high ambient temperature.” Using that as a guide, the symptom
“diesel engine cranks but will not start” serves well as a target node. A note on tar-
get nodes: the goal is to find the right magnification. Too small, or narrow, and a
target (i.e., Generator fuel pump inoperative) may miss many possible causes of the
engine start problem; too large, or too wide, and a target (i.e., the Generator won’t
run) will cause the network to be too large and more difficult to elicit. A good target
finds the middle ground with sufficient specificity to identify all problems but with
a manageable network size. The experts are then asked to develop a list of nodes
that influence, or are influenced by, the target node. A number of good, CTA-based
techniques are useful for this process. Nominal group technique (NGT) is widely
used because its silent voting process eliminates many of the biases associated with
expert elicitations—most importantly, those that involve personalities influencing
the development of the node list (e.g., more charismatic experts may influence other
experts). In our use case, we would expect to see nodes representing causes of the
engine problem and nodes representing effects of the engine problem (Figure 1.14).
We are now ready to start the DSEV process proper.
Define
The node list is voted on, prioritized, and then discussed at length, removing, by
consensus, duplicate or similar nodes. The imperative of the Define phase is to
ensure the state space in each node meets all criteria. The state space is a simple
description of what values the variable can take on in nature. The state space must
be exhaustive (all possible states enumerated) and mutually exclusive (the variable
can only be in one state). Most importantly, the state space must be intuitive to the
KE team and to the experts. Our CBN tools provide some help in that regard by
enabling us to add contextual information on values to establish thresholds, assign
upper and lower bounds, and make the states more specific. These can be as simple
as binary state space (true–false; yes–no), or multi-state where the value field pro-
vides the necessary threshold levels (Figure 1.15).
Structure
The first step in the developing the DSEV Structure phase is to work with a small
“chunk” of nodes and connect them. This requires knowledge of the three basic
BN node structures (discussed previously) and of the different types/categories of
nodes in a BN. BNs consist of five types of nodes: hypothesis nodes, context nodes,
indicator nodes, report nodes, and intermediate nodes. The state space of all types
of nodes must be, as discussed in the Define phase, mutually exclusive (the node
can only be in one state) and exhaustive (the state space must cover all that are
possible). We will briefly describe the attributes of each.
Hypothesis nodes describe possible root causes for the symptom. Hypothesis
nodes precede indicator nodes and report nodes in temporal order (they are parents
of indicator and report nodes). This means directed arcs go from the hypothesis node
to the indicator or report node. Hypothesis nodes succeed context nodes in temporal
order (they are children of context nodes). This means directed arcs come into the
hypothesis node from the context node. “Battery,” “Fuel System,” and “Mechanical”
are examples of hypotheses nodes for our problem statement (Figure 1.16).
Ambient Temperature
Ambient Temperature
Indicator nodes are children of hypothesis nodes. Directed arcs come into indi-
cator nodes from hypothesis nodes. Indicator nodes are, in general, symptoms of the
hypothesis node, but they may not always be easily observable. “Cranking Speed”
and “Cylinder Pressure” are examples of indicators of the hypothesis, as they are
symptoms but not readily observable (Figure 1.18).
Ambient Temperature
Report nodes are children of indicator nodes. Directed arcs come into report
nodes from indicator nodes. Report nodes, in general, are observables of the indicator
node. “Specific Gravity Test” and “Compression Test” are examples of report nodes
for the hypotheses as they are both observables for the indicator node (Figure 1.19).
16 ◾ Military Applications of Data Analytics
Ambient Temperature
Mechanical
Cylinder Pressure
Engine Cranks
but w/n Start
Another example from our “diesel engine cranks but will not start” problem
statement ties all these node types together: Cold ambient temperatures (pre-
disposition) slow down the flow of electrons through a battery’s electrolyte
(hypothesis) causing slow engine cranking speed (indicator, not directly observable/
quantifiable) that can be detected using a specific gravity test (report) (Conrady and
Jouffe, 2015) (Figure 1.21).
The key knowledge engineering task of the Structure phase involves deciding
what types of nodes we have in the list from the Define phase, where those nodes fit
in the model, and what structures to use to represent the knowledge. With all this
in hand, we can move to the description of the Elicit phase, where the structural
relationships described previously can be specified.
Elicit
This phase involves drawing out from the experts the probabilities for the structural
model you have built in the previous phase. This estimation process is burdened with a
number of biases that the team must be (a) aware of, and (b) have a mitigation plan for.
Before outlining the soft and hard skill requirements for the Elicit phase, Table 1.2 is
provided as a quick reference on common biases and mitigation techniques.
18 ◾ Military Applications of Data Analytics
Table 1.2
Anchoring: Initial impressions, whether quantitative or qualitative in nature,
can cause bias as the human brain tends to give more weight to the first
information received.
Mitigate by making the team aware and attempting to take emotion out of
the estimation process by reviewing pertinent statistics.
Confirmation: The human mind tends to seek out confirming evidence. Given
a preferred outcome, an individual will tend to seek out evidence to confirm
that outcome, and interpret evidence to confirm that outcome, instead of
giving equal weight to evidence that conflicts with the desired outcome.
Mitigate by making the team aware and actively seeking out disconfirming
evidence. Try to draw out scenarios that would result in a different
conclusion.
With this knowledge in hand, we move our focus to the key DSEV techniques
for eliciting probabilities for each node. One of the key challenges in this process
is in establishing the base rate, or prior probability, for each node. The base rate
should be an estimate of the state in nature with no other forces acting upon it. For
example, when eliciting the prior probability of a “cranks but will not run” fault,
consider some relevant parametric data, such as your own automobile. Does the
engine fail to start 1 out 100 starts? 1 out of 1000? 1 out of 10,000? Consider these
ratios knowing the tendency is to set the base rate too high. Consider both data and
context. For example, the base rate for smokers vs. non-smokers in a chest clinic is
significantly different that the base rate for smokers in a random selection of people
on the street. The prior probability should be entered into the nodes conditional
probability table (Hepler et al., 2015) (Figure 1.22).
Bayesian Networks for Descriptive Analytics in Military ◾ 19
For root nodes (nodes with no parents) these probabilities can be entered
directly into the CPT. For any node with parents, the node must be temporarily
disconnected (arcs coming into the node disconnected) to input prior probabilities.
This should be done for all nodes before reconnecting all the arcs. The resulting
reconnected network will show the marginal probabilities for each node, or the
probabilities with no evidence entered for any node, but the nodes will indicate that
the underlying CPT still needs to be filled in. As detailed earlier, the CPT is a series
of statements that show the probability distribution for each state of a child node
given each state of its parents (Conrady and Jouffe, 2015) (Figure 1.23).
20 ◾ Military Applications of Data Analytics
The knowledge engineering team and the experts work through each of the
statements. This is the heart of the process as these estimations are what makes
the expert knowledge show through in the BN and what makes the network
think and act like an expert. There are many direct and indirect methods for
drawing out these estimations. Experts like to work with words. Direct meth-
ods use questions designed to elicit a number response; indirect methods use
questions designed to elicit relationships that can be converted to numbers
(Table 1.3).
In some cases the team may find it easier to use a formula, such as a normal dis-
tribution, to translate expert statements and fill in the table. The key techniques here
are to avoid bias and to use tools to convert language into probabilities. The elicited
probabilities can be “played back” to the experts in real time to ensure they agree with
how the network responds to evidence. This is the essence of the final phase (Hepler
et al., 2015).
Bayesian Networks for Descriptive Analytics in Military ◾ 21
Verify
The sub-headings under this phase—consistency, coherence, what-if analysis, and
sensitivity analysis—all have to do with ensuring that the model you are working
on is operating as intended. Working with your expert team, use these techniques
to exercise the model in different ways to uncover any possible discrepancies, or
to just fine-tune the model. Consistency tests involve going into the CPT of each
child node, rearranging the order of the parents in all possible combinations, and
observing patterns after each reordering. Note below that rearranging the order
of parents makes it more obvious to the experts that the relationship between
“Cylinder Pressure” and “Engine Cranks but w/n Start” is independent of the
other parents. This will show, at a wide angle, how each parent node affects the
child node distribution, and this provides one way for the experts to review their
work and acknowledge the veracity of the parent-child relationships (Figure 1.24).
Similarly, coherence tests just provide the experts and the team with a different
perspective on the model. By examining the marginal distributions (no evidence
entered), we can analyze the relationships between variables and see if there is good
fit between the expert’s knowledge and the model. In most cases, this is a way to
22 ◾ Military Applications of Data Analytics
verify that the prior probability distributions and the conditional distributions in
the CPT are representative of the expert’s thought processes (Figure 1.25).
The “what-if” tests, as the name implies, involves “playing” with the model by
entering different sets of evidence and seeing how the model acts under different
scenarios. Always prepare experts for this test by asking what they expect to see. The
perspective on elicited results and computed results (2) provides yet another way for
experts to think about their view of the domain (Figure 1.26).
The key technical takeaway for this phase is mutual information. In building
the model, we are interested in how much entropy is reduced in a variable by
instantiating evidence in other nodes in the model. Mutual information sensitivity
nests well with the “first best question” philosophy that guides the practical tool for
soldiers and diagnostics in general. We want to eliminate as many possibilities as
(1) Incident selection (2) Constructing a timeline (3) Deepening (4) What-if ’s
generation world, these cases will usually involve calls for assistance where critical
systems are down due to a lack of power and the usual supply and maintenance
resources are not available. For example, in Iraq in 2003, water purification assets
were placed strategically along convoy and supply lines to ensure coalition troops
and civilians had a dependable source of potable water (Figure 1.29).
These assets were often located on river side farms owned and run by local
Iraqi families. The only power sources sufficient to run the water purification
systems were the diesel generators mounted on the system trailers. Failure of these
generators and the loss of purified water production put soldiers and civilians at
immediate risk. Our specific case involves a generator deployed to a farm along on
the Tigris River in Iraq (Figure 1.30).
1. The expert convoyed to the site and was delayed several times along the way
due to enemy activity.
2. Without any communication with the site during the convoy, the expert
started running possible cause and effect relationships and started developing
a set of questions.
3. Upon arrival at the site, the expert asked key questions of the crew to create a
sub-timeline of the failure itself, e.g., did it occur during full load operation,
no-load operation, starting, etc.
From a DSEV perspective, the knowledge engineering team uses this information
to confirm a target node and to compile a list of these potential “first-best”
questions that will become context and indicator variables. As the timeline gets
richer in detail, we gather that the expert had a good idea of what he or she wanted
to look at first when gaining access to the generator, and this was an “audible click”
test, not available in any technical manual or doctrine, that the expert himself
had developed from his own experience and from discussions with engineers.
The test was designed as a quick way to determine if power was available at the
fuel injection pump actuator. A positive test result (audible click) would verify all
control circuits were functioning and would place the problem in the mechanical
or fuel supply subsystems. A negative test result would mean that a failure in
the control circuit was nearly certain. The test effectively isolates the problem to
mechanical or electrical and reduces a significant amount of entropy with very
little time or effort required (Figure 1.31).
Per our DSEV process guidelines and based on our expert team make-up, the
majority of these experts will have similar experiences troubleshooting critical failures
in deployed areas. The discussion of the audible click test will stimulate discussion
on if, and how, the test should be a part of the troubleshooting network. It will also
stimulate discussion on what the other experts do in the same situation, possibly
revealing other such tests. These are exactly the types of discussions DSEV can
Other documents randomly have
different content
began his sermons in the fields and looked down from a green slope
on several thousand colliers grimy from the coalpits near Bristol to
see, as he preached, tears "making white channels down their
blackened cheeks." Later again, Hannah More drew sympathy to the
poverty and crime of the agricultural classes.
The Influence of Walnut on Cabinet-making.—If oak was the
wood which the country joiner loved best, he was not without some
sympathetic leaning towards the effects which could be produced in
the softer walnut. Such styles accordingly began slowly to have a
marked influence upon the farmhouse furniture in early-Georgian
days. It was not easy to produce curved lines in the refractory oak,
tough and brittle, but the village craftsman essayed his best to
please his patrons whose taste had been caught by the newer
fashions observed in the squire's parlour when paying rare visits.
In the two examples illustrated of farmhouse cupboard and bureau
bookcase (p. 163) it will be seen that here is the country maker
definitely trying his skill in his native wood to emulate the finer
walnut examples of town cabinet-makers. This is even more
noticeable in regard to some of the tables actually found in
farmhouses belonging to as early as the first quarter of the
eighteenth century. The two specimens illustrated (p. 165) exemplify
this tendency to imitate the designs of trained workers. The country
touch always betrays itself in the cabriole leg, whether in chair or in
table. The upper table has less naïveté than most examples found.
There is a balance in its construction rarely found in provincial work.
The legs, always the stumbling-block to the less experienced
artificer, are here of exceptionally fine proportions, terminating in
club feet. The lower table shows a less capable treatment of the
cabriole leg. The hoof foot and the carved knee have obviously been
copied from a fine Queen Anne model. In the underframing of both
tables there is an experiment in ornament and form rarely attempted
except in the highest flights of the country maker, and as such these
two fine examples must be regarded.
OAK TABLE.
Showing clumsy corners and indicating the naïveté of the country
cabinet-maker.
OAK TABLE.
Showing transition from cabriole leg to straight leg of 1760.
In the table the cabriole leg showed early signs of passing away. The
two examples illustrated (p. 173) clearly indicate this. The upper
one, of the time of Queen Anne, shows the cabriole leg in fine
proportion under due subjection, and is a delicate example of fine
cabinet-work. The lower one sees the leg losing its cabriole curve,
but still rounded and still possessing the club foot.
Even more interesting are the two tables illustrated (p. 177). The
country maker was slow to adopt the cabriole leg when it was
fashionable, but when it became unfashionable he was equally loth
to depart from his accustomed style. These clearly point to the
transition between the cabriole leg and the straight leg of
Chippendale, and are about 1760 in date.
The forms of design of tables of eighteenth-century date are
extremely varied in character, denoting the rapidly changing habits
of the people. The Queen Anne tea-table, with scalloped edges for
cups, marks the note of preciosity creeping into country life. A
revolving bookstand in table form, of about 1720 in date, is another
rare piece. The adjacent table (p. 181) is country Chippendale. The
exaggerated knee and the feeble ball-and-claw foot mark the failure
of the provincial hand at curved work, accurate though he might be
in straight joinery. The "Cupid's bow" underframing is interesting in
combination with the rest of the design.
The tripod table offered difficulties of construction and is not often
found. The example illustrated is probably unique in form. In date it
is about 1760, and is remarkable for the attempt at elaborate rococo
work. Sometimes, though not often, mahogany was used in
farmhouse examples. The table illustrated (p. 183) is an instance of
the use of this wood instead of oak. It is about 1730 in date, and
exhibits an unusual form in the round cross stretcher, a touch of
originality by the maker. It is, as will be seen, a square-topped table
with flaps.
Elaboration of a high order was happily not often attempted by the
country workman, or the results with his limited experience would
have been disastrous. Instead of a fine series of really good, solid,
and well-constructed furniture made for practical use we should
have had a wilderness of failures at attempting the impossible. A
copy of a fine Chippendale side-table illustrated (p. 187) is a case in
point. There is the usual want of balance in the poise of the leg, but
the carving is of exceptional character. The table beneath, with its
long and tapering legs, has all the characteristics of the Adam style.
The beaded decoration on the legs, the classic fluting and the carved
rosette claim distant relationship with the classic inventions of
Robert Adam. The wood is pinewood, and as an example it is of
singular interest.
The rapid survey of eighteenth-century influences bearing on the
class of furniture of which this volume treats will perhaps induce the
collector to scrutinise more carefully all pieces coming under his
notice, with a view to arriving at their salient features in connection
with the native design of more or less untutored craftsmen.
ELABORATE TABLE.
Country attempt to imitate fine Chippendale side table. Note the want of
balance in leg.
PINEWOOD COUNTRY-MADE ADAM TABLE.
Note the unusually long leg.
CHAPTER VII
THE EVOLUTION
OF THE CHAIR
CHAPTER VII
THE EVOLUTION OF THE CHAIR
The two other chairs illustrated on the same page are later
examples, in date about 1690. One of these is fashioned of chestnut.
The form of these backs is related to the contemporary high-back
cane chairs of the time of Charles II. and James II. But these
fashions influenced the proportions only of farmhouse chairs. In
arriving at the date of such specimens as these the bevelled panel is
an important factor in determining the late period.
Cushions had no place in the effects of the farmhouse in early days,
although ropes were sometimes used to support cushions, as we
have shown. But as a general rule the wooden seats show tangible
signs of rough usage of centuries, and the stretcher has its worn
surface marked by generations of owners who found it protective
against the cold flagged or rush-strewn floor and the draughts in
days prior to carpets and rugs.
The Evolution of the Stretcher.—In making a study of the
evolution of the chair the stretcher is an important factor. For
obvious reasons, as explained above, no early chairs were made
without the stretcher across the front, a good sound serviceable
piece of British oak to stand rough wear and tear. Gradually, keeping
time with the march of comfort, the front stretcher begins to leave
its old position near the floor, and in later examples it is half-way up
the front legs. It still had a use, and a very important one: it added
considerable strength and solidity to the chair, and is nearly always
found in chairs intended for use. In the series illustrated herein there
are only few examples without the front stretcher. Later it took
another form, as the illustrated specimens in this chapter show: it
united the two side stretchers, and crossed the chair underneath in
the centre at right angles to the side stretchers. Its purpose in
adding stability to this class of furniture was evidently never lost
sight of.
At first strictly utilitarian, the stretcher was a solid foot-rest; later,
when partly utilitarian in adding to the strength, it became suitable
for ornamentation, Although in the class of furniture here under
review such ornament never took an elaborate form, there are
examples slightly differing in character from chairs intended for the
use of the wealthier classes, and these are evidently a local effort to
keep in touch with prevailing taste.
Finely turned stretchers, such as are found in gate tables, are a
feature of a certain class of local chairs, such as those illustrated on
p. 197. This kind of chair without arms is rather more decorated and
conforms more to the styles of furniture made for higher spheres
than the farmhouse. The upper chair with its light open back and
ornate decoration is a Yorkshire type, and the ball turning in the
stretcher shows the transition period to Charles II. The other two
are Cromwellian chairs, but showing indications of the next period.
In date they are all three about 1660.
OAK SETTLE.
With back panel under seat made from older Oak Chest. Date 1675.
OAK ARM CHAIR. DATE 1675.
With Bevelled Panels.
ebookbell.com