Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
licenseplates
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Taddeüs Kroes
licenseplates
Commits
413bc35b
Commit
413bc35b
authored
13 years ago
by
Jayke Meijer
Browse files
Options
Downloads
Patches
Plain Diff
Added details to work distribution.
parent
b851b4a2
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/report.tex
+16
-20
16 additions, 20 deletions
docs/report.tex
with
16 additions
and
20 deletions
docs/report.tex
+
16
−
20
View file @
413bc35b
...
...
@@ -532,7 +532,7 @@ neighbourhoods.
\subsubsection*
{
Faulty classified characters
}
As we do not have a
$
100
\%
$
score, it is interesting to see what characters are
classified wrong. These characters are shown in appendix
\ref
{
f
aucla
}
. Most of
classified wrong. These characters are shown in appendix
\ref
{
f
cc
}
. Most of
these errors are easily explained. For example, some 0's are classified as
'D', some 1's are classified as 'T' and some 'F's are classified as 'E'.
...
...
@@ -661,7 +661,7 @@ The first problem was that the dataset contains a lot of license plates which
are problematic to read, due to excessive amounts of dirt on them. Of course,
this is something you would encounter in the real situation, but it made it
hard for us to see whether there was a coding error or just a bad example.
aucla
Another problem was that there were license plates of several countries in
the dataset. Each of these countries has it own font, which also makes it
hard to identify these plates, unless there are a lot of these plates in the
...
...
@@ -694,31 +694,27 @@ Some additional 'basics' where created in similar fashion. This ensured that
every team member was up-to-date and could start figuring out which part of the
implementation was most suited to be done by one individually or in a pair.
\subsubsection*
{
W
ho did what
}
\subsubsection*
{
W
ork distribution
}
Gijs created the basic classes we could use and helped everyone by keeping
track of what was required to be finished and whom was working on what.
Tadde
\"
us and Jayke were mostly working on the SVM and all kinds of tests
whether the histograms were matching, and what parameters had to be used.
Fabi
\"
en created the functions to read and parse the given xml files with
information about the license plates. Upon completion all kinds of learning
and data sets could be created. Richard helped out wherever anyone needed a
helping hand, and was always available when someone had doubts about what they
where doing or needed to ask something. He also wrote an image cropper that
automatically exactly cuts out a character, which eventually turned out to be
obsolete.
\subsubsection*
{
How it went
}
Sometimes one cannot hear the alarm bell and wake up properly. This however was
not a big problem as no one was afraid of staying at Science Park a bit longer
to help out. Further communication usually went through e-mails and replies
were instantaneous! A crew to remember.
Gijs also worked with Tadde
\"
us on the Local Binary Patterns code.
Tadde
\"
us and Jayke worked on the SVM and Tadde
\"
us wrote all kinds of tests
for testing what part went good and what went wrong, and what parameters had
to be used. Fabi
\"
en created the functions to read and parse the given XML
files with information about the license plates. Upon completion all kinds
of learning and data sets could be created. Richard helped out wherever
anyone needed a helping hand, and was always available when someone had
doubts about what they where doing or needed to ask something. He also wrote
an image cropper that exactly cuts out a character, which eventually turned
out to be obsolete. The work on the report was mainly done by Jayke, assisted
by Fabi
\"
en and Richard and the technical details were filled in by Gijs and
Tadde
\"
us.
\appendix
\section
{
Faulty classified characters
}
\label
{
f
aucla
}
\label
{
f
cc
}
\begin{figure}
[H]
\hspace
{
-2cm
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment