<p><div><div><div><div data-show-faces="false" data-height="21" data-width="100" data-layout="button_count" data-send="true" data-href="https://www.r-bloggers.com/featurizing-images-the-shallow-end-of-deep-learning/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="http://blog.revolutionanalytics.com/2017/09/wood-knots.html"> Revolutions</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<div>
<div>

<p><em>by Bob Horton and Vanja Paunic, Microsoft AI and Research Data Group</em></p>
<p>Training deep learning models from scratch requires large data sets and significant computational reources. Using pre-trained deep neural network models to extract relevant features from images allows us to build classifiers using standard machine learning approaches that work well for relatively small data sets. In this context, a deep learning solution can be thought of as incorporating layers that compute features, followed by layers that map these features to outcomes; here we’ll just map the features to outcomes ourselves.</p>
<p>We explore an example of using a pre-trained deep learning image classifier to generate features for use with traditional machine learning approaches to address a problem the original model was never trained on (see the blog post <a rel="nofollow" href="https://blogs.msdn.microsoft.com/rserver/2017/04/12/image-featurization-with-a-pre-trained-deep-neural-network-model" target="_blank">“Image featurization with a pre-trained deep neural network model”</a> for other examples). This approach allows us to quickly and easily create a custom classifier for a specific specialized task, using only a relatively small training set. We use the image featurization abilities of Microsoft R Server 9.1 (MRS) to create a classifier for different <a rel="nofollow" href="http://www.ee.oulu.fi/research/imag/knots/KNOTS/" target="_blank">types of knots in lumber</a>. These images were made publicly available from the laboratory of <a rel="nofollow" href="http://www.ee.oulu.fi/~olli/" target="_blank">Prof., Dr. Olli Silven</a>, University of Oulu, Finland, in 1995. Please note that we are using this problem as an academic example of an image classification task with clear industrial implications, but we are not really trying to raise the bar in this well-established field.</p>
<p>We characterize the performance of the machine learning model and describe how it might fit into the framework of a lumber grading system. Knowing the strengths and weaknesses of the classifier, we discuss how it could be used to triage additional image data for labeling by human experts, so that the system can be iteratively improved.</p>
<p>The pre-trained deep learning models used here are optional components that can be installed alongside Microsoft R Server 9.1; directions are <a rel="nofollow" href="https://docs.microsoft.com/en-us/r-server/install/microsoftml-install-pretrained-models" target="_blank">here</a>.</p>
<div>
<h2>Lumber grading</h2>
<p>In the sawmill industry lumber grading is an important step of the manufacturing process. Improved grading accuracy and better control of quality variation in production leads directly to improved profits. Grading has traditionally been done by visual inspection, in which a (human) grader marks each piece of lumber as it leaves the mill, according to a factors like size, category, and position of knots, cracks, species of tree, etc. Visual inspection is often an error prone and laborious task. Certain defect classes may be difficult to distinguish, even for a human expert. To that end, a number of automated lumber grading systems have been developed which aim to improve the accuracy and the efficiency of lumber grading [2-7].</p>
</div>
<div>
<h2>Loading and visualizing data</h2>
<p>Let us start by downloading the data.</p>
</div>
</div>
<div>
<pre><code>DATA_DIR &lt;- file.path(getwd(), 'data')

if(!dir.exists(DATA_DIR)){
  
  dir.create(DATA_DIR)
  
  knots_url &lt;- 'http://www.ee.oulu.fi/research/imag/knots/KNOTS/knots.zip'
  names_url &lt;- 'http://www.ee.oulu.fi/research/imag/knots/KNOTS/names.txt'
  
  download.file(knots_url, destfile = file.path(DATA_DIR, 'knots.zip'))
  download.file(names_url, destfile = file.path(DATA_DIR, 'names.txt'))
  unzip(file.path(DATA_DIR, 'knots.zip'), exdir = file.path(DATA_DIR, 'knot_images'))

}</code></pre>
</div>
<p>Let’s now load the data from the downloaded files and look at some of those files.</p>
<div>
<pre><code>knot_info &lt;- read.delim(file.path(DATA_DIR, &quot;names.txt&quot;), sep=&quot; &quot;, header=FALSE, stringsAsFactors=FALSE)[1:2]

names(knot_info) &lt;- c(&quot;file&quot;, &quot;knot_class&quot;)

knot_info$path &lt;- file.path(DATA_DIR, &quot;knot_images&quot;, knot_info$file)

names(knot_info)</code></pre>
</div>
<div>
<pre><code>## [1] &quot;file&quot;       &quot;knot_class&quot; &quot;path&quot;</code></pre>
</div>
<p>We’ll be trying to predict <code>knot_class</code>, and here are the counts of the categories:</p>
<div>
<pre><code>table(knot_info$knot_class)</code></pre>
</div>
<div>
<pre><code>## 
## decayed_knot     dry_knot    edge_knot encased_knot    horn_knot 
##           14           69           65           29           35 
##    leaf_knot   sound_knot 
##           47          179</code></pre>
</div>
<p>Four of these labels relate to how the knot is integrated into the structure of the surrounding wood; these are the descriptions from the README file:</p>
<ul>
<li>
<p>sound: “A knot grown firmly into the surrounding wood material and does not contain any bark or signs of decay. The color may be very close to the color of sound wood.”</p>
</li>
<li>
<p>dry: “A firm or partially firm knot, and has not taken part to the vital processes of growing wood, and does not contain any bark or signs of decay. The color is usually darker than the color of sound wood, and a thin dark ring or a partial ring surrounds the knot.”</p>
</li>
<li>
<p>encased: “A knot surrounded totally or partially by a bark ring. Compared to dry knot, the ring around the knot is thicker.”</p>
</li>
<li>
<p>decayed: “A knot containing decay. Decay is difficult to recognize, as it usually affects only the strength of the knot.”</p>
</li>
</ul>
<p>Edge, horn and leaf knots are related to the orientation of the knot relative to the cutting plane, the position of the knot on the board relative to the edge, or both. These attributes are of different character than the ones related to structural integration. Theoretically, you could have an encased horn knot, or a decayed leaf knot, etc., though there do not happen to be any in this dataset. Unless otherwise specified, we have to assume the knot is sound, cross-cut, and not near an edge. This means that including these other labels makes the <code>knot_class</code> column ‘untidy’, in that it refers to more than one different kind of characteristic. We could try to split out distributed attributes for orientation and position, as well as for structural integration, but to keep this example simple we’ll just filter the data to keep only the sound, dry, encased, and decayed knots that are cross-cut and not near an edge. (It turns out that you can use featurization to fit image classification models that recognize position and orientation quite well, but we’ll leave that as an exercise for the reader.)</p>
<div>
<pre><code>knot_classes_to_keep &lt;- c(&quot;sound_knot&quot;, &quot;dry_knot&quot;, &quot;encased_knot&quot;, &quot;decayed_knot&quot;)

knot_info &lt;- knot_info[knot_info$knot_class %in% knot_classes_to_keep,]
knot_info$knot_class &lt;- factor(knot_info$knot_class, levels=knot_classes_to_keep)</code></pre>
</div>
<p>We kept the <code>knot_class</code> column as character data while we were deciding which classes to keep, but now we can make that a factor.</p>
<p>Here are a few examples of images from each of the four classes:</p>
<div>
<pre><code>library(&quot;pixmap&quot;)

set.seed(1)

samples_per_category &lt;- 3

op &lt;- par(mfrow=c(1, samples_per_category), oma=c(2,2,2,2), no.readonly = TRUE)


for (kc in levels(knot_info$knot_class)){
  kc_files &lt;- knot_info[knot_info$knot_class == kc, &quot;path&quot;]
  kc_examples &lt;- sample(kc_files, samples_per_category)
  for (kc_ex in kc_examples){
    pnm &lt;- read.pnm(kc_ex)
    plot(pnm, xlab=gsub(&quot;.*(knot[0-9]+).*&quot;, &quot;\\1&quot;, kc_ex))
    mtext(text=gsub(&quot;_&quot;, &quot; &quot;, kc), side=3, line=0, outer=TRUE, cex=1.7)
  }
}</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed556970c-pi" target="_blank"><img border="0" alt="Knots1" title="Knots1" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed556970c-800wi"></a></p>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01bb09c799b3970d-pi" target="_blank"><img border="0" alt="Knots2" title="Knots2" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01bb09c799b3970d-800wi"></a></p>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed55e970c-pi" target="_blank"><img border="0" alt="Knots3" title="Knots3" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed55e970c-800wi"></a></p>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed566970c-pi" target="_blank"><img border="0" alt="Knots4" title="Knots4" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aed566970c-800wi"></a></p>
<div>
<pre><code>par(op)</code></pre>
</div>
<div>
<h2>Featurizing images</h2>
<p>Here we use the <code>rxFeaturize</code> function from Microsoft R Server, which allows us to perform a number of transformations on the knot images in order to produce numerical features. We first resize the images to fit the dimensions required by the pre-trained deep neural model we will use, then extract the pixels to form a numerical data set, then run that data set through a DNN pre-trained model. The result of the image featurization is a numeric vector (“feature vector”) that represents key characteristics of that image.</p>
<p>Image featurization here is accomplished by using a deep neural network (DNN) model that has already been pre-trained by using millions of images. Currently, MRS supports four types of DNNs – three ResNet models (18, 50, 101)[1] and AlexNet [8].</p>
<div>
<pre><code>knot_data_df &lt;- rxFeaturize(data = knot_info,
                            mlTransforms = list(loadImage(vars = list(Image = &quot;path&quot;)),
                                                resizeImage(vars = list(Features = &quot;Image&quot;), 
                                                            width = 224, height = 224, 
                                                            resizingOption = &quot;IsoPad&quot;),
                                                extractPixels(vars = &quot;Features&quot;),
                                                featurizeImage(var = &quot;Features&quot;, 
                                                               dnnModel = &quot;resnet101&quot;)),
                            mlTransformVars = c(&quot;path&quot;, &quot;knot_class&quot;))</code></pre>
</div>
<div>
<pre><code>## Elapsed time: 00:02:59.8362547</code></pre>
</div>
<p>We have chosen the “resnet101” DNN model, which is 101 layers deep; the other ResNet options (18 or 50 layers) generate features more quickly (well under 2 minutes each for this dataset, as opposed to several minutes for ResNet-101), but we found that the features from 101 layers work better for this example.</p>
<p>We have placed the features in a dataframe, which lets us use any R algorithm to build a classifier. Alternatively, we could have saved them directly to an XDF file (the native file format for Microsoft R Server, suitable for large datasets that would not fit in memory, or that you want to distribute on HDFS), or generated them dynamically when training the model (see examples in the <a rel="nofollow" href="https://blogs.msdn.microsoft.com/rserver/2017/04/12/image-featurization-with-a-pre-trained-deep-neural-network-model/" target="_blank">earlier blog post</a>).</p>
<p>Since the featurization process takes a while, let’s save the results up to this point. We’ll put them in a CSV file so that, if you are so inspired, you can open it in Excel and admire the 2048 numerical features the deep neural net model has created to describe each image. Once we have the features, training models on this data will be relatively fast.</p>
<div>
<pre><code>write.csv(knot_data_df, &quot;knot_data_df.csv&quot;, row.names=FALSE)</code></pre>
</div>
</div>
<div>
<h2>Select training and test data</h2>
<p>Now that we have extracted numeric features from each image, we can use traditional machine learning algorithms to train a classifier.</p>
<div>
<pre><code>in_training_set &lt;- sample(c(TRUE, FALSE), nrow(knot_data_df), replace=TRUE, prob=c(2/3, 1/3))
in_test_set &lt;- !in_training_set</code></pre>
</div>
<p>We put about two thirds of the examples (203) into the training set and the rest (88) in the test set.</p>
</div>
<div>
<h2>Fit Random Forest model</h2>
<p>We will use the popular <code>randomForest</code> package, since it handles both “wide” data (with more features than cases) as well as multiclass outcomes.</p>
<div>
<pre><code>library(randomForest)

form &lt;- formula(paste(&quot;knot_class&quot; , paste(grep(&quot;Feature&quot;, names(knot_data_df), value=TRUE), collapse=&quot; + &quot;), sep=&quot; ~ &quot;))

training_set &lt;- knot_data_df[in_training_set,]
test_set &lt;- knot_data_df[in_test_set,]

fit_rf &lt;- randomForest(form, training_set)

pred_rf &lt;- as.data.frame(predict(fit_rf, test_set, type=&quot;prob&quot;))
pred_rf$knot_class &lt;- knot_data_df[in_test_set, &quot;knot_class&quot;]
pred_rf$pred_class &lt;- predict(fit_rf, knot_data_df[in_test_set, ], type=&quot;response&quot;)

# Accuracy
with(pred_rf, sum(pred_class == knot_class)/length(knot_class))</code></pre>
</div>
<div>
<pre><code>## [1] 0.8068182</code></pre>
</div>
<p>Let’s see how the classifier did for all four classes. Here is the confusion matrix, as well as a moisaic plot showing predicted class (<code>pred_class</code>) against the actual class (<code>knot_class</code>).</p>
<div>
<pre><code>with(pred_rf, table(knot_class, pred_class))</code></pre>
</div>
<div>
<pre><code>##               pred_class
## knot_class     sound_knot dry_knot encased_knot decayed_knot
##   sound_knot           51        0            0            0
##   dry_knot              3       19            0            0
##   encased_knot          6        5            1            0
##   decayed_knot          2        1            0            0</code></pre>
</div>
<div>
<pre><code>mycolors &lt;- c(&quot;yellow3&quot;, &quot;yellow2&quot;, &quot;thistle3&quot;, &quot;thistle2&quot;)
mosaicplot(table(pred_rf[,c(&quot;knot_class&quot;, &quot;pred_class&quot;)]), col = mycolors, las = 1, cex.axis = .55, 
           main = NULL, xlab = &quot;Actual Class&quot;, ylab = &quot;Predicted Class&quot;)</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aeb011970c-pi" target="_blank"><img border="0" alt="Knot2" title="Knot2" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aeb011970c-800wi"></a></p>
<p>It looks like the classifier performs really well on the sound knots. On the other hand, all of the decayed knots in the test set are misclassified. This is a small class, so let’s look at those misclassified samples.</p>
<div>
<pre><code>library(dplyr)

pred_rf$path &lt;- test_set$path

# misclassified knots
misclassified &lt;- pred_rf %>% filter(knot_class != pred_class)

# number of misclassified decayed knots
num_example &lt;- sum(misclassified$knot_class == &quot;decayed_knot&quot;)

op &lt;- par(mfrow = c(1, num_example), mar=c(2,1,0,1), no.readonly = TRUE)

for (i in which(misclassified$knot_class == &quot;decayed_knot&quot;)){
  example &lt;- misclassified[i, ]
  pnm &lt;- read.pnm(example$path)
  plot(pnm)
  mtext(text=sprintf(&quot;predicted as\n%s&quot;, example$pred_class), side=1, line=-2)
}
mtext(text='Misclassified Decayed Knots', side = 3, outer = TRUE, line = -3, cex=1.2)</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aeb03f970c-pi" target="_blank"><img border="0" alt="Knot3" title="Knot3" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b8d2aeb03f970c-800wi"></a></p>
<div>
<pre><code>par(op)</code></pre>
</div>
<p>We were warned about the decayed knots in the README file; they are more difficult to visually classify. Interestingly, the ones classified as sound actually do appear to be well-integrated into the surrounding wood; they also happen to look somewhat rotten. Also, the decayed knot classified as dry does have a dark border, and looks like a dry knot. These knots appear to be two decayed sound knots and a decayed dry knot; in other words, maybe decay should be represented as a separate attribute that is independent of the structural integration of the knot. We may have found an issue with the labels, rather than a problem with the classifier.</p>
<p>Let’s look at the performance of the classifier more closely. Using the scores returned by the classifier, we can plot an ROC curve for each of the individual classes.</p>
<div>
<pre><code>library(pROC)

plot_target_roc &lt;- function(target_class, outcome, test_data, multiclass_predictions){
  is_target &lt;- test_data[[outcome]] == target_class
  roc_obj &lt;- roc(is_target, multiclass_predictions[[target_class]])
  plot(roc_obj, print.auc=TRUE, main=target_class)
  text(x=0.2, y=0.2, labels=sprintf(&quot;total cases: %d&quot;, sum(is_target)), pos=3)
}

op &lt;- par(mfrow=c(2,2), oma=c(2,2,2,2), #mar=c(0.1 + c(7, 4, 4, 2)), 
          no.readonly = TRUE)

for (knot_category in levels(test_set$knot_class)){
  plot_target_roc(knot_category, &quot;knot_class&quot;, test_set, pred_rf)
}

mtext(text=&quot;ROC curves for individual classes&quot;, side=3, line=0, outer=TRUE, cex=1.5)</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b7c9245502970b-pi" target="_blank"><img border="0" alt="Knot4" title="Knot4" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b7c9245502970b-800wi"></a></p>
<div>
<pre><code>par(op)</code></pre>
</div>
<p>These ROC curves show that the classifier scores can be used to provide significant enrichment for any of the classes. With sound knots, for example, the score can unambiguously identify a large majority of the cases that are not of that class. Another way to look at this is to consider the ranges of each classification score for each actual class:</p>
<div>
<pre><code>library(tidyr)
library(ggplot2)

pred_rf %>% 
  select(-path, -pred_class) %>%
  gather(prediction, score, -knot_class) %>% 
  ggplot(aes(x=knot_class, y=score, col=prediction)) + geom_boxplot()</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01bb09c77588970d-pi" target="_blank"><img border="0" alt="Knot5" title="Knot5" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01bb09c77588970d-800wi"></a></p>
<p>Note that the range of the sound knot and dry knot scores tend to be higher for all four classes. But when you consider the scores for a given prediction class across all the actual classes, the scores tend to be higher when they match than when they don’t. For example, even though the decayed knot score never goes very high, it tends to be higher for the decayed knots than for other classes. Here’s a boxplot of just the decayed_knot scores for all four actual classes:</p>
<div>
<pre><code>boxplot(decayed_knot ~ knot_class, pred_rf, xlab=&quot;actual class&quot;, ylab=&quot;decayed_knot score&quot;, main=&quot;decayed_knot score for all classes&quot;)</code></pre>
</div>
<p><a rel="nofollow" href="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b7c9245561970b-pi" target="_blank"><img border="0" alt="Knot6" title="Knot6" src="http://revolution-computing.typepad.com/.a/6a010534b1db25970b01b7c9245561970b-800wi"></a></p>
<p>Even though the multi-class classifier did not correctly identify any of the three decayed knots in the test set, this does not mean that it is useless for finding decayed knots. In fact, the decayed knots had higher scores for the decayed predictor than most of the other knots did (as shown in the boxplots above), and this score it is able to correctly determine that almost 80% of the knots are not decayed. This means that this classifier could be used to screen for knots that are more likely to be decayed, or alternatively, you could use these scores to isolate a collection of cases that are unlikely to be any of the kinds of knots your classifier is good at recognizing. This ability to focus on things we are not good at might be helpful if we needed to search through a large collection of images to find more of the kinds of knots for which we need more training data. We could show those selected knots to expert human labelers, so they wouldn’t need to label all the examples in the entire database. This would help us get started with an active learning process, where we use a model to help develop a better model.</p>
<p>Here we’ve shown an open-source random forest model trained on features that have been explicitly written to a dataframe. The model classes in the MicrosoftML package can also generate these features dynamically, so that the trained model can accept a file name as input and automatically generate the features on demand during scoring. For examples see the <a rel="nofollow" href="https://blogs.msdn.microsoft.com/rserver/2017/04/12/image-featurization-with-a-pre-trained-deep-neural-network-model" target="_blank">earlier blog post</a>. In general, these data sets are “wide”, in that they have a large number of features; in this example, they have far more columns of features than rows of cases. This means that you need to select algorithms that can handle wide data, like elastic net regularized linear models, or, as we’ve seen here, random forests. Many of the MicrosoftML algorithms are well suited for wide datasets.</p>
</div>
<div>
<h2>Discussion</h2>
<p>Image featurization allows us to make effective use of relatively small sets of labeled images that would not be sufficient to train a deep network from scratch. This is because we can re-use the lower-level features that the pre-trained model had learned for more general image classification tasks.</p>
<p>This custom classifier was constructed quite quickly; although the featurizer required several minutes to run, after the features were generated all training was done on relatively small models and data sets (a few hundred cases with a few thousand features), where training a given model takes on the order of seconds, and tuning hyperparameters is relatively straightforward. Industrial applications commonly require specialized classification or scoring models that can be used to address specific technical or regulatory concerns, so having a rapid and adaptable approach to generate such models should have considerable practical utility.</p>
<p>Featurization is the low-hanging fruit of transfer learning. More general transfer learning allows the specialization of deeper and deeper layers in a pre-trained general model, but the deeper you want to go, the more labelled training data you will generally need. We often find ourselves awash in data, but limited by the availability of quality labels. Having a partially effective classifier can let you bootstrap an <a rel="nofollow" href="https://en.wikipedia.org/wiki/Active_learning_(machine_learning)" target="_blank">active learning</a> approach, where a crude model is used to triage images, classifying the obvious cases directly and referring only those with uncertain scores to expert labelers. The larger set of labeled images is then used to build a better model, which can do more effective triage, and so on, leading to iterative model improvement. Companies like <a rel="nofollow" href="https://www.crowdflower.com/crowdflower-and-microsoft-better-together" target="_blank">CrowdFlower</a> use these kinds of approaches to optimize data labeling and model building, but there are many use cases where general crowdsourcing may not be adequate (such as when the labeling must be done by experts), so having a straightforward way to bootstrap that process could be quite useful.</p>
<p>The labels we have may not be tidy, that is, they may not refer to distinct characteristics. In this case, the decayed knot does not seem to really be an alternative to “encased”, “dry”, or “sound” knots; rather, it seems that any of these categories of knots might possibly be decayed. In many applications, it is not always obvious what a properly distributed outcome labeling should include. This is one reason that a quick and easy approach is valuable; it can help you to clarify these questions with iterative solutions that can help frame the discussion with domain experts. In a subsequent iteration we may want to consider “decayed” as a separate attribute from “sound”, “dry” or “encased”.</p>
<p>Image featurization gives us a simple way to build domain-specific image classifiers using relatively small training sets. In the common use case where data is plentiful but good labels are not, this provides a rapid and straightforward first step toward getting the labeled cases we need to build more sophistiated models; with a few iterations, we might even learn to recognize decayed knots. Seriously, wood that knot be cool?</p>
</div>
<div>
<h2>References</h2>
<ol>
<li>
<p>Kaiming He, Xiangyu Zhang, Shaoqing Ren, Jian Sun. (2016) The IEEE Conference on Computer Vision and Pattern Recognition (CVPR), pp. 770-778</p>
</li>
<li>
<p>Kauppinen H. and Silven O.: A Color Vision Approach for Grading Lumber. In Theory &amp; Applications of Image Processing II – Selected papers from the 9th Scandinavian Conference on Image Analysis (ed. G. Borgefors), World Scientific, pp. 367-379 1995.</p>
</li>
<li>
<p>Silven O. and Kauppinen H.: Recent Developments in Wood Inspection. (1996) International Journal on Pattern Recognition and Artificial Intelligence, IJPRAI, pp. 83-95, 1996.</p>
</li>
<li>
<p>Rinnhofer, Alfred &amp; Jakob, Gerhard &amp; Deutschl, Edwin &amp; Benesova, Wanda &amp; Andreu, Jean-Philippe &amp; Parziale, Geppy &amp; Niel, Albert. (2006). A multi-sensor system for texture based high-speed hardwood lumber inspection. Proceedings of SPIE – The International Society for Optical Engineering. 5672. 34-43. 10.1117/12.588199.</p>
</li>
<li>
<p>Irene Yu-Hua Gu, Henrik Andersson, Raul Vicen. (2010) Wood defect classification based on image analysis and support vector machines. Wood Science and Technology 44:4, 693-704. Online publication date: 1-Nov-2010.</p>
</li>
<li>
<p>Kauppinen H, Silven O &amp; Piirainen T. (1999) Self-organizing map based user interface for visual surface inspection. Proc. 11th Scandinavian Conference on Image Analysis (SCIA’99), June 7-11, Kangerlussuaq, Greenland, 801-808.</p>
</li>
<li>
<p>Kauppinen H, Rautio H &amp; Silven O (1999). Nonsegmenting defect detection and SOM-based classification for surface inspection using color vision. Proc. EUROPTO Conf. on Polarization and Color Techniques in Industrial Inspection (SPIE Vol. 3826), June 17-18, Munich, Germany, 270-280.</p>
</li>
<li>
<p>Alex Krizhevsky, Ilya Sutskever, and Geoffrey E. Hinton. (2012) ImageNet Classification with Deep Convolutional Neural Networks. In NIPS, 2012.</p>
</li>
</ol>
</div>
</div>
	<p>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="http://blog.revolutionanalytics.com/2017/09/wood-knots.html"> Revolutions</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a rel="nofollow" href="https://www.r-project.org/" title="The R Project for Statistical Computing">R</a> news and <a rel="nofollow" href="https://www.r-bloggers.com/search/tutorial" title="R tutorials">tutorials</a> on topics such as: <a rel="nofollow" href="https://www.r-bloggers.com/search/data%20science" title="Data science">Data science</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data" title="Big Data">Big Data, <a rel="nofollow" href="https://www.r-users.com/" title="R jobs">R jobs</a>, visualization (<a rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2" title="ggplot and ggplot2 tutorials">ggplot2</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/boxplot" title="Boxplots using lattice and ggplot2 tutorials">Boxplots</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/map" title="Maps and gis">maps</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/animation" title="Animation in R">animation</a>), programming (<a rel="nofollow" href="https://www.r-bloggers.com/search/RStudio" title="RStudio IDE for R">RStudio</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/sweave" title="Sweave and literate programming">Sweave</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX" title="LaTeX in R">LaTeX</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/SQL" title="SQL and databases">SQL</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/eclipse" title="Eclipse IDE for R">Eclipse</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/git" title="git and github, Version Control System">git</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/hadoop" title="Large data in R using Hadoop">hadoop</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping" title="Web Scraping of google, facebook, yahoo, twitter and more using R">Web Scraping</a>) statistics (<a rel="nofollow" href="https://www.r-bloggers.com/search/regression" title="Regressions and ANOVA analysis tutorials">regression</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/PCA" title="principal component analysis tutorial">PCA</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/time+series" title="Time series">time series</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/trading" title="finance trading">trading</a>) and more...
<img width="1" alt="" src="http://feeds.feedburner.com/~r/RBloggers/~4/I1e__qdt7Ws" height="1"></a></div>