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
365deb2d
Commit
365deb2d
authored
13 years ago
by
Richard Torenvliet
Browse files
Options
Downloads
Patches
Plain Diff
added some changes to report
parent
e5beb422
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
+2
-2
2 additions, 2 deletions
docs/report.tex
with
2 additions
and
2 deletions
docs/report.tex
+
2
−
2
View file @
365deb2d
...
...
@@ -387,7 +387,7 @@ Performs a grid-search to find the optimal value for \texttt{c} and
\texttt
{
gamma
}
, for the given combination of NEIGHBOURS and BLUR
\_
SCALE. The
optimal classifier is saved in
\emph
{
data/classifier
\_\{
BLUR
\_
SCALE
\}\_\{
NEIGBOURS
\}
.dat
}
, and the accuracy
scores are saved in
in
scores are saved in
\emph
{
results/results
\_\{
BLUR
\_
SCALE
\}\_\{
NEIGBOURS
\}
.txt
}
.
Like
\texttt
{
create
\_
classifier.py
}
, the script ensures that the required
...
...
@@ -675,7 +675,7 @@ function for each comparison, which is expensive in terms of efficiency. The
functions also call
\texttt
{
inImage
}
, which (obviously) checks if a pixel is
inside the image. This can be avoided by adding a border around the image with
the width of half the neighbourhood size minus one (for example,
$
\frac
{
5
-
1
}{
2
}
=
2
$
pixels in a
$
5
x
5
$
neighbourhood). When creating the feature vector,
1
}{
2
}
=
2
$
pixels in a 5x5 neighbourhood). When creating the feature vector,
this border should not be iterated over.
\section
{
Conclusion
}
...
...
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