<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Data driven case base construction for prediction of success of marine operations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bjørn Magnus Mathisen</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Agnar Aamodt</string-name>
          <email>agnar@ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Helge Langseth</string-name>
          <email>helge.langseth@ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Norwegian University of Science and Technology</institution>
        </aff>
      </contrib-group>
      <fpage>104</fpage>
      <lpage>113</lpage>
      <abstract>
        <p>It is a common situation to have lots of recorded data that you want to use for improving a process in your organization or make use of this data to provide new services or products. Starting with one primary data set we describe a system that enhances this data set to a level such that it can be used by a deep learning system. This deep learning system then creates a model based on this data set, trying to predict operational windows for marine operations. Using this model the system extracts cases for use in a CBR-system aimed at providing operational support. This paper describes the partial implementation and results of this system.</p>
      </abstract>
      <kwd-group>
        <kwd>Data Science</kwd>
        <kwd>Deep Neural Networks</kwd>
        <kwd>Data Analytics</kwd>
        <kwd>Case-based Reasoning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Critical operations are often meticulously planned and subject to many
parameters that decide if and how these operations are performed. Some of these
parameters are called operational time windows, which in marine environments
often are connected to external factors such as weather.</p>
      <p>This paper uses machine learning to predict favorable operational time
windows or warn of unfavorable operational windows, so that critical operations
can be planned with better accuracy, e.g. when the operation should ideally
take place. One way of doing this is to look at historical data of previously
executed operations. By combining data on successful and unsuccessful operations
with the relevant context of that operation, we create a data set that can be
used to find indicators for success or failure in advance. Which context that is
relevant is dependent on the nature of operational window; wind and fog are
important contexts for aviation, while waves and current are important for marine
operations but not aviation.</p>
      <p>This paper focuses on marine operations, and we analyze event data captured
from boats moving in and out of zones connected to aquaculture installations.
Next, we calculate the duration of these events and connect them to the relevant
context and the associated success or failure classification.</p>
      <p>The data used in this analysis is gathered as part of the EXPOSED project1.
This project aims to develop enabling- and applied technologies for exposed
1 http://exposedaquaculture.no/en/
Copyright © 2017 for this paper by its authors. Copying permitted for private and
academic purpose. In Proceedings of the ICCBR 2017 Workshops. Trondheim, Norway
aquaculture operations. The work we describe aims to improve planning of
operations on aquaculture installations on exposed locations.</p>
      <p>The data is a subset of boats moving across geofences attached to
aquaculture installations. This system consists of two zones around every aquaculture
installation in Norway: One outer zone 400 meters from the outer points of the
structures holding the fish themselves (not including the control building/fishfeed
silos). The inner zone is 20 meters from the structure. These limits are in
adherence to government regulations that no boat should fish within the outer
zone and no boat should move within the inner zone unless the boat is there to
operate on the installation.</p>
      <p>An example of geofencing zones are shown in Fig. 1 below.</p>
      <p>An event is created each time a boat crosses any of the geofence zones,
marking the time. Table 1 below shows an example of a typical event.</p>
      <p>Event ID Location-ID Vessel Name Time LocationZone EventType
81766 12966 Vessel A 2014-09-02 21:39:32 1 1
81767 12966 Vessel A 2014-09-02 21:40:11 1 2
Table 1: This table shows an example of two events of a vessel entering
(EventType=1) and leaving (EventType=2) the outer zone (LocationZone=1) of
location 12966.</p>
      <p>In data gathered in the EXPOSED project, the aquaculture industry reports on
several possible problems with fish feed carriers interacting with aquaculture
installations: Approaching the feed barges, often placed in shallow waters; Knowing which
barge container to fill with what feed; Planning according to weather and route to
enable the installation crew to attend the operation; And the fact that impact and
currents from the boat can damage the installation.</p>
      <p>As our data only gives us the time spent in two different proximities to the
aquaculture installation there will be limits to which types of operational problems we can
detect, and it will be very hard to discern between different causes (other than bad
weather which is very general) of any detected problem.</p>
      <p>The architecture of the full decision support system for EXPOSED is illustrated in
Fig. 2. In this paper we only present results from parts of the system. Future work will
integrate these results with the other modules (e.g. knowledge models) to complete the
system to a state where it can be verified in the field.</p>
      <p>Current
State</p>
      <p>Sensor
Sensor
ReaSdeinsor
Readin
Rgeadin
gg</p>
      <p>Preprocessing</p>
      <p>Preprocessing
Knowledge</p>
      <p>and
Experience</p>
      <p>Simulators/
Simulators/
NuSmimeruiclaatlors/
Numerical
MNoudmelserical
Models</p>
      <p>Models
Simulators/
Simulators/
Numerical
NKunmoewrliecdagle
Models</p>
      <p>MModoedlesls
Simulators/
Simulators/
NumMearicchailne
Numerical
MoLdeealrsning
Models
Models</p>
      <p>Future</p>
      <p>State
Case Base</p>
      <p>Decision
Support
System</p>
      <p>Our main hypothesis is that given enough contextual weather data a deep neural
network should be able to predict the length of a maritime operation at a aquaculture
installation, enabling us to predict favorable operational windows. The main
contribution of this paper is to show the reader the process of gathering, collating, filtering of
data and subjecting this data to an analysis.</p>
      <p>This paper is structured as follows; Section 2 introduces related work and our work
in the light of this previous work. Section 3 describes the methods used in our work
as well as the data sources used. Section 4 shows the result of our experiments, while
section 5 presents the conclusion along with a discussion of the results.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related work</title>
      <p>In this work we aim to extract cases from a time series of events, CBR research has
been done on several aspects of automatic case-authoring.</p>
      <p>
        In CBR there has been a lot of focus on how to measure competence and utility of
a case-base [
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], they do this via reversing deletion policies constructed in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
that try to improve case base utility without degrading competence.
4
      </p>
      <p>
        Several works [
        <xref ref-type="bibr" rid="ref5 ref6 ref7">5,6,7</xref>
        ] use NLP to extract cases from structured and unstructured
([
        <xref ref-type="bibr" rid="ref10 ref8 ref9">8,9,10</xref>
        ]) text.
      </p>
      <p>
        More specifically connected to the task of extracting cases from time series is the
work done by Bach et.al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] where they employ clustering of time-series events in
time and space, in combination with other detection methods. Funk et. al [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] uses
different models of how predictive (or discriminatory) different time-series patterns are
to different medical diagnosis of stress. For more insight into work done in time-series
analysis connected to CBR research we suggest chapter 3.3 in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]
      </p>
      <p>
        The work presented in this paper shares the approach of Bach et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] in that we
try to extract the useful data points from the time series via clustering and filtering.
Our work differs from the previous work in that we have very few verified cases apriori
or during learning. In other words, the time-series is in all practical sense unlabeled for
our use. We will try to apply common knowledge about how long an operation usually
takes to perform. Then we can extract failed operations from the even time series to
create cases that exemplify failed operations.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Method</title>
      <p>To enable the deep learning system to correctly model and predict the time spent
at an installation, we need to provide it with as much context data as possible for each
of the event data points. In addition, we need the data to be as noise free as possible,
thus we want to filter away operations that naturally have a high degree of variation
in time spent at the location. We address these two requirements by combining the
primary data set with other data sets, to enable us to provide filtering and context. An
illustration of this process can be seen in Fig. 3 . Below we describe each of the data
sets.</p>
      <p>Boat data set As mentioned in the introduction we do not want to analyze all
the traffic data of all of the boats. To verify that our method is usable in at least
one instance, we want to look at a specific type of boat that has stable characteristics
when it comes to the parameters (e.g. time and stability of time) of the operations it
executes on the installation. We chose fishfeed boats in this case, as they only do one
type of operation. That way we do not need to deduce the type of operation from the
event data (one less hidden variable). In addition, this operation should be stable in
the time it takes to execute it. To filter the data accordingly we need to combine the
event data set with a data source that describes the boats. We can then easily extract
the fishfeed boats.</p>
      <p>
        NORA10 data set NORA10 [
        <xref ref-type="bibr" rid="ref14 ref15">14,15</xref>
        ] is a data set that describes output of a
precise weather model (hind-cast), that is validated by measurements. It has a higher
resolution (10km) than most other models (e.g. the much used ERA2 model with 80km
resolution) as it is re-sampled for this specific region around Norway. We sample this
model for each of the installations and at each time of each event (in the case of long
events we use the median time of the event). We sample every datatype that we think
will have an impact on the time spent on an operation: wind speed, wave direction,
wind direction, significant swell wave height and significant wave height.
      </p>
      <p>
        Exposure data set SINTEF EXPOSED has produced a data set [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] that
describes the degree of exposure for a large number of the installations that are used in
the event data set. This data set provides a level of exposure for 360 degrees around the
installation (from 0 to max, where max is no land in sight). We combine our weather
data with this (described above), thus we combine the wind direction of the wind with
how exposed the location is in the direction of the wind using a filter that combines
exposure level from +/- 10 degrees around the direction of the wind.
3.1
      </p>
      <sec id="sec-3-1">
        <title>Extracting time spent in zones.</title>
        <p>The data set needs to contain the time spent in the zones around the aquaculture
installations. The raw data only contains events of entering and exiting the zones. To
extract this we sequentially find each exit from a zone then search backwards for the
entry to that zone by the same boat, then compute the time spent in that zone.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Grouping events close in time</title>
        <p>After converting all discrete events into events with a duration, we still ended up
with a lot of extremely short events. This is most probably caused by boats trying
to stay close to the installation but the dynamic positioning system moves them in
and out of the inner or outer zones. To counter this fact we grouped all events with
the same boat at the same location within 1 hour into one event. However, after this
grouping there is still 63% (or 244) of the events within the first 10 minute window.
These are events within a zone that is less than ten minutes in duration and without
another event in the same location within one hour of the original event. There are
three possible explanations for these strange events: 1. The boat is passing through
the location, and not returning for at least one hour. Or otherwise briefly enters and
exists the zone, without this fact having any effect on the operation. 2. The boat
tries to perform an operation at the location but has to abort and leaves within ten
minutes. 3. The event was not registered correctly when the data was gathered. The
most probable cause for most of these events are boats that travel through the zone
heading for another location. This hypothesis can be tested by removing outer zone
events from the distribution. As the inner zone is small, very few of these big fishfeed
carrier boats would drive through the inner zone of an aquaculture installation when
2 http://www.ecmwf.int/en/research/climate-reanalysis/era-interim
6
heading somewhere else. We can still see 244 events that are of duration 10 minutes
or less within the inner zone of an aquaculture installation. Figure 4 looks at the 1
minute distribution within the first 10 minutes to try to find the causes for the high
number of short stay events. And once again we can see that many of the events are
very short, with very few events lasting more than 3 minutes. This further supports
our first hypothesis.</p>
        <p>200
150
100
50
00 7351.%0 1 5294.%0 2 4290.%0 3 17.0 4 17.0 5 8.0 6 3.0 7 7.0 8 7.0 9 2.0 10</p>
        <p>7% 7% 3% 1% 3% 3% 1%</p>
        <p>One problem with our approach so far is that some events are very far apart in
time as well as having different zone types. One example being one boat having a 0
second stay in the inner zone of location 31437 at 18:23 the 28th of November, however
the boat entered the outer zone of the same site at 17:04 the same day, and exited zone
1 of that location at 18:24. We can then conclude that the boat spent approximately
1 hour and 20 minutes at the location in the outer zone, then very briefly entered the
inner zone before leaving the location. Again supporting the first hypothesis. From this
we can see that including inner zone in analyzing fishfeed carrier operations adds very
little information to our analysis as the fishfeed carriers do not enter the inner zone
when transferring fishfeed. As a consequence we discard the inner zone data. We are
still left with 2401 events with a duration shorter than 10 minutes. Fig 5 shows the
distribution of these events length in stay. We can see that most of these are shorter
than 5 minutes, and most probably does not represent actual maritime operations (or
failed tries), but rather traveling through the zone. Thus we discard events shorter than
10 minutes, giving us the final distribution shown in Fig. 6.</p>
        <p>To extract cases that exemplify instances where the weather conditions stops a
fishfeed operation from being successfull, we are currently building a deep learning
model aimed at predicting the time spent at the installation, with the given weather
and level of exposure at the time and location. The input to the model is: draft and
length of the boat, wind speed3, distance between the model grid point and actual site
coordinate, wave direction3, wind direction3, maximum level of exposure at location,
significant swell wave height3, month, hour, wind effect (wind speed combined with
3 Measured at the closest grid point in NORA10
00 52129%.0 1 62260%.0 2 42914%.0 3 31765%.0 4 200.0 5 110.0 6 43.0 7 24.0 8 9.0 9 7.0 10</p>
        <p>8% 5% 2% 1% 0% 0%
exposure levels in the wind direction +/- 10 degrees) and significant wave height. The
output of the model is the amount of time spent on the installation.</p>
        <p>The regression was implemented using python. We used sklearn for
preprocessing and scaling (MinMax scaling) of input data (including regression target). The
Keras library for deep learning was used for the regression itself, with a input layer
of inputcolumns + 1 = 14 nodes. We used 3 hidden layers with 13 nodes each and a
output layer of 1 node. All nodes used the ReLU activation function.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>The current results show that there is little information in the gathered data
(through the NORA10 model and exposure levels) that account for the variance shown
in the time spent at the locations. The neural network models presented in the previous
Section 3.3 gets very low accuracy (0.11%, which means the predictor is very slightly
better than just outputting the average) in terms of predicting how long a fish feed
boat stays at a aquaculture installation. Figure 7 shows the length of all of the events in
the chronologically in blue and the predicted length in orange. The "Time Spent" axis
is normalized values of the time spent in near a installation where y = 1:0 represents
the longest stay recorded in the training data. There are obvious differences between
8
predicted and true values; predicted values consistently returns too high values, and
fails to predict short stays. A cross validated (cv = 5) hyper parameter grid search
was performed and showed no better performance at 10 hidden layers with 56 nodes
in each hidden layer.</p>
      <p>After we received the disappointing results we created scatter plots of two weather
variables in relation to the length of stay at the installations. Typically most would
assume there would be a pattern of some correlation between the weather and the
length of stay. However Figure 8 shows that neither wind (8a) or waves (8b) reveals
any obvious correlation patterns against time spent at installations.</p>
      <p>In addition we did a principal component analysis of the data, to discover if there
where any clear principal components that could contain the variance in the data. The
components returned: C = (0:127; 0:117; 0:109; 0:099; 0:091; 0:039; 0:034; 0:028; 0:020; 0:011
; 0:008; 0:004; 0:002; 0:000) Where the sum of components sum(C) = 0:6967 indicating
that the total of the components could account for little of the variance. Finally we
tried a standard method for non-linear regression as a base-line result to measure the
DNN against. We tried Epsilon-Support Vector Regression (SVR) which scored with a
coefficient of determination R2 = 0:83 which is worse than constantly predicting the</p>
      <p>Histogram cutoff at time &lt; 30 and time &gt; 300</p>
      <p>Histogram cutoff at time &lt; 30 and time &gt; 300
225
200
175
mean of the target (which would give R2 = 0:0). This final result shows in the context
of the other results listed above us that the data set may not contain the features
needed to predict the length of the stay at a installation.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions and future work</title>
      <p>We started the work with a hypothesis that whether or not a fishfeed boat operation
(loading of fishfeed from boat to barge) succeeded depended on the weather, and that
such a failure could be detected from the length of time the fishfeed boat stayed at
the aquaculture installation. Our analysis did not find any deterministic correlation
between the weather and location data and the length of the stay at the installation.
There can be many reasons for this, we will try to list some of the reasons we think
are probable;</p>
      <p>The first possibility is that despite our efforts to remove noise from the data, the
data still contains noise. This includes the three factors listed in the introduction section
and other possibilities we have not considered.</p>
      <p>Second, given the size of the boats and their stability, they can operate during
harsh conditions. In addition these boats are expensive in operation, and even more
expensive if they fail to deliver feed at the appointed time, possibly starving the fish at
the installation. Thus these boats are already subject to careful operational planning.
It may therefore be that there is none to very few failed fishfeed operations in the data
captured. An additional consequence is that the time spent during operations has very
low variance.</p>
      <p>Extending this work would start with confirming these possible explanations for
the lack of correlation found in our data. We would also like to gather further data,
extending the number of events beyond the current 2700. This would enable us to train
and test our models with more rigor and less uncertainty.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledements</title>
      <p>None of the work done in this paper would have been possible without the support of
the EXPOSED project. Special thanks to ANTEO (http://anteo.no/) for providing
data to this experiment and working with us to make use of this data.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Barry</given-names>
            <surname>Smyth</surname>
          </string-name>
          and
          <article-title>Elizabeth McKenna. Modelling the competence of case-bases</article-title>
          , pages
          <fpage>208</fpage>
          -
          <lpage>220</lpage>
          . Lecture Notes in Computer Science. Springer Nature,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Barry</given-names>
            <surname>Smyth</surname>
          </string-name>
          and
          <string-name>
            <surname>Elizabeth McKenna</surname>
          </string-name>
          .
          <source>Building Compact Competent Case-Bases</source>
          , pages
          <fpage>329</fpage>
          -
          <lpage>342</lpage>
          .
          <source>Case-Based Reasoning Research and Development</source>
          . Springer Nature,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Jun</given-names>
            <surname>Zhu</surname>
          </string-name>
          and
          <string-name>
            <given-names>Qiang</given-names>
            <surname>Yang</surname>
          </string-name>
          .
          <article-title>Remembering to add: competence-preserving caseaddition policies for case-base maintenance</article-title>
          .
          <source>In IJCAI</source>
          , volume
          <volume>99</volume>
          , pages
          <fpage>234</fpage>
          -
          <lpage>241</lpage>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>B</given-names>
            <surname>Smyth and M Keane</surname>
          </string-name>
          .
          <article-title>Remembering to forget: A competence-preserving deletion policy for cbr</article-title>
          .
          <source>In Proceedings IJCAI-95</source>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Chunsheng</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Benoit</given-names>
            <surname>Farley</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Bob</given-names>
            <surname>Orchard</surname>
          </string-name>
          .
          <source>Automated case creation and management for diagnostic cbr systems. Applied Intelligence</source>
          ,
          <volume>28</volume>
          (
          <issue>1</issue>
          ):
          <fpage>17</fpage>
          -
          <lpage>28</lpage>
          ,
          <year>Feb 2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Qiang</given-names>
            <surname>Yang</surname>
          </string-name>
          and Hong Cheng.
          <source>Case mining from large databases. Lecture Notes in Computer Science</source>
          , page
          <volume>691</volume>
          -
          <fpage>702</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>Marvin</given-names>
            <surname>Zaluski</surname>
          </string-name>
          , Nathalie Japkowicz, and
          <string-name>
            <given-names>Stan</given-names>
            <surname>Matwin</surname>
          </string-name>
          .
          <article-title>Case authoring from text and historical experiences</article-title>
          .
          <source>Lecture Notes in Computer Science, page 222-236</source>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>Kerstin</given-names>
            <surname>Bach</surname>
          </string-name>
          ,
          <string-name>
            <surname>Klaus-Dieter</surname>
            <given-names>Althoff</given-names>
          </string-name>
          , Régis Newo, and
          <string-name>
            <given-names>Armin</given-names>
            <surname>Stahl</surname>
          </string-name>
          .
          <source>A Case-Based Reasoning Approach for Providing Machine Diagnosis from Service Reports</source>
          , pages
          <fpage>363</fpage>
          -
          <lpage>377</lpage>
          .
          <source>Case-Based Reasoning Research and Development</source>
          . Springer Nature,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Valmi</given-names>
            <surname>Dufour-Lussier</surname>
          </string-name>
          , Florence Le Ber, Jean Lieber, and
          <string-name>
            <given-names>Emmanuel</given-names>
            <surname>Nauer</surname>
          </string-name>
          .
          <article-title>Automatic case acquisition from texts for process-oriented case-based reasoning</article-title>
          .
          <source>Information Systems</source>
          ,
          <volume>40</volume>
          (nil):
          <fpage>153</fpage>
          -
          <lpage>167</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>Benoit</given-names>
            <surname>Farley</surname>
          </string-name>
          .
          <article-title>From free-text repair action messages to automated case generation</article-title>
          .
          <source>In Proceedings of AAAI 1999 Spring Symposium: AI in Equipment Maintenance Service &amp; Support, Technical Reprot SS-99-02</source>
          , Menlo Park, CA, AAAI Press, pages
          <fpage>109</fpage>
          -
          <lpage>118</lpage>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kerstin</surname>
            <given-names>Bach</given-names>
          </string-name>
          , Odd Erik Gundersen,
          <string-name>
            <given-names>Christian</given-names>
            <surname>Knappskog</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Pinar</given-names>
            <surname>Öztürk</surname>
          </string-name>
          .
          <article-title>Automatic case capturing for problematic drilling situations</article-title>
          .
          <source>In International Conference on Case-Based Reasoning</source>
          , pages
          <fpage>48</fpage>
          -
          <lpage>62</lpage>
          . Springer,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>Peter</given-names>
            <surname>Funk</surname>
          </string-name>
          and
          <string-name>
            <given-names>Ning</given-names>
            <surname>Xiong</surname>
          </string-name>
          .
          <article-title>Case-based reasoning and knowledge discovery in medical applications with time series</article-title>
          .
          <source>Computational Intelligence</source>
          ,
          <volume>22</volume>
          (
          <issue>3-4</issue>
          ):
          <fpage>238</fpage>
          -
          <lpage>253</lpage>
          ,
          <year>Aug 2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. Odd Erik Gundersen.
          <article-title>Enhancing the Situation Awareness of Decision Makers by Applying Case-Based Reasoning on Streaming Data</article-title>
          .
          <source>PhD thesis</source>
          , NTNU,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Øyvind</surname>
            <given-names>Breivik</given-names>
          </string-name>
          , Magnar Reistad, and
          <string-name>
            <given-names>Hilde</given-names>
            <surname>Haakenstad</surname>
          </string-name>
          .
          <article-title>A high-resolution hindcast study for the north sea, the norwegian sea and the barents sea</article-title>
          .
          <source>In 10th International Workshop on Wave Hindcasting and Forecasting</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Magnar</surname>
            <given-names>Reistad</given-names>
          </string-name>
          , Øyvind Breivik, Hilde Haakenstad, Ole Johan Aarnes,
          <string-name>
            <surname>Birgitte R Furevik</surname>
          </string-name>
          , and
          <string-name>
            <surname>Jean-Raymond Bidlot</surname>
          </string-name>
          .
          <article-title>A high-resolution hindcast of wind and waves for the north sea, the norwegian sea, and the barents sea</article-title>
          .
          <source>Journal of Geophysical Research: Oceans</source>
          ,
          <volume>116</volume>
          (
          <issue>C5</issue>
          ),
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Pål</surname>
            <given-names>Lader</given-names>
          </string-name>
          , David Kristiansen,
          <string-name>
            <given-names>Morten</given-names>
            <surname>Alver</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Hans. V</given-names>
            <surname>Bjelland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>and Dag</given-names>
            <surname>Myrhaug</surname>
          </string-name>
          .
          <article-title>Classification of aquaculture locations in norway with respect to wind wave exposure</article-title>
          .
          <source>In Proceedings of the ASME 2017 36th International Conference on Ocean, Offshore and Arctic Engineering OMAE2017</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>