I submitted a brief paper for the 2019 International Symposium on Wearable Computers (ISWC 2019).

You can find the accepted and peer-reviewed version here.

Skip to content
# Lukas Brausch

## Welcome to Lukas' world. Here you will find study and work related things. Boring for most of you but hopefully useful for some.

# Brief paper: Towards a Wearable Low-Cost Ultrasound Device for Classification of Muscle Activity and Muscle Fatigue

# Installing Brave Browser on Debian 9

# Dealing with a “ResourceExhaustedError” in Keras

# Making a subplot span several columns with pyplot

# Fixing a broken Matlab installation after an Ubuntu update

# Implementing cross correlation in Matlab without using xcorr

# Multiresolution Elastic Matching

I submitted a brief paper for the 2019 International Symposium on Wearable Computers (ISWC 2019).

You can find the accepted and peer-reviewed version here.

Advertisements

curl -s https://brave-browser-apt-release.s3.brave.com/brave-core.asc | sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-release.gpg add - source /etc/os-release echo "deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bionic main" | sudo tee /etc/apt/sources.list.d/brave-browser-release-boinic.list sudo apt update sudo apt install brave-keyring brave-browser

I’m using Keras (version 2.2.0) with TensorFlow (version 1.8.0) to train ANNs with many input neurons (204800 to be precise) and a rather small database.

I recently started to get the following error message every once in a while:

> ResourceExhaustedError (see above for traceback): OOM when allocating tensor with shape[204800,100] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc

> [[Node: dense_58/kernel/Assign = Assign[T=DT_FLOAT, use_locking=true, validate_shape=true, _device=”/job:localhost/replica:0/task:0/device:GPU:0″](dense_58/kernel, dense_58/random_uniform)]]

> Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

If you run into the same issue, there are two things to try:

1.) Add the following to your code:

from keras import backend as K

[…]

K.clear_session()

2.) Try to save each model to the hard-drive (resulting in roughly 240 MB for each model in my case) and delete it to free memory for a new model in each iteration. You can delete a model by simply telling Python to free the memory and clean up:

import gc

[…]

del model

gc.collect()

Currently, I’m using PyPlot a lot. There was one issue bugging me for a few days now and this issue was the simply question how on earth a subplot spanning several columns could look like. There doesn’t seem to be any official documentation mentioning this and even the corresponding Stackoverflow article could only give some hints in the right direction. Finally I found the solution using trial and error:

import matplotlib.pyplot as plt

```
```

`plt.ion()`

fig = plt.figure(figsize=(height_in,width_in), dpi=80)

ax1 = plt.subplot(221)

ax2 = plt.subplot(2,2,(3,4))

ax3 = plt.subplot(222)

In case you are wondering about the meaning of those strange numbers, I quote from the article cited above:

“These are subplot grid parameters encoded as a single integer. For example, “111” means “1×1 grid, first subplot” and “234” means “2×3 grid, 4th subplot”.

Alternative form for add_subplot(111) is add_subplot(1, 1, 1).”

Today, I updated Ubuntu as usual and suddenly Matlab stopped working. Instead of starting up nicely, it only complained about some “segmentation violation”. Luckily however, I came across a rather simple solution to this problem. All I had to do was to install the “matlab-support” and “matlab-support-dev” packages via:

sudo aptitude install matlab-support

sudo aptitude install matlab-support-dev

and after that, Matlab worked like a charm again. I just wanted to share that insight in case anyone stumbles across the same problem one day. 🙂

If you’ve ever wanted to implement the cross correlation function in Matlab without using the inbuilt xcorr function, this post might be of some help for you.

This is how such a function could look like:

%Implementation of the cross correlation function function [result] = crossCorrelation(signalA,signalB) signalALength = size(signalA,1); signalBLength = size(signalB,1); result = zeros(1, signalALength + signalBLength - 1 ); resultLength = size(result,2); for m = 1 : resultLength arg = (m - signalALength); if(arg < 0) negativeCondition = 1; limit = signalALength + arg; else negativeCondition = 0; limit = signalALength - arg; end for n = 1:limit if (negativeCondition) result(m) = result(m) + signalA(n) * signalB(n - arg); else result(m) = result(m) + signalA(arg + n) * signalB(n); end end end end

** **

It has been a while since I last updated this blog. But today I finally found the time to do it and share another presentation summary with you.

This time the summary is about the paper “Multiresolution Elastic Matching” from Ruzena Bajcsy and Stane Kovačič.

The summary introduction goes as follows:

The general idea behind the work presented in”Multiresolution Elastic Matching” is to develop a mechanism to match “an explicit 3-dimensional pictorial model to locally variant data”.In other words, two existing representations (one model representation and one input representation) are put into correspondence. To achieve this goal,rigid transforms are used to account for global misalignments, while elastic deformations are appliedfor local shape differences. A coarse-to-fine strategy(called multiresolution elastic matching) is the heart of the presented paper and leads to more efficient computations and improved convergence of the matching process in general.

You can find the summary here: Multiresolution Elastic Matching – a summary.