forked from liuliu/ccv
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
53 lines (53 loc) · 2.98 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
---
layout: default
is_index: true
---
{% for news in site.posts limit:1 %}
<h2><a class="news" href="{{ news.url }}">{{ news.title }} ›</a></h2>
{% endfor %}
<h2>Backstory</h2>
<p>I set to build ccv with a minimalism inspiration. That was back in 2010, out
of the frustration with the computer vision library then I was using, ccv
was meant to be a much easier to deploy, simpler organized code with a bit
caution with dependency hygiene. The simplicity and minimalistic nature at
then, made it much easier to integrate into any server-side deployment
environments.</p>
<h2>Portable and Embeddable</h2>
<p>Fast forward to now, the world is quite different from then, but ccv adapts
pretty well in this new, mobile-first environment. It now runs on Mac OSX,
Linux, FreeBSD, Windows*, iPhone, iPad, Android, Raspberry Pi. In fact,
anything that has a proper C compiler probably can run ccv. The majority
(with notable exception of convolutional networks, which requires a BLAS
library) of ccv will just work with no compilation flags or dependencies.</p>
<h2>Modern Computer Vision Algorithms</h2>
<p>One core concept of ccv development is <b>application driven</b>. Thus, ccv ends
up implementing a handful state-of-art algorithms. It includes a close to
state-of-the-art image classifier, a state-of-the-art frontal face detector,
reasonable collection of object detectors for pedestrians and cars, a useful
text detection algorithm, a long-term general object tracking algorithm,
and the long-standing feature point extraction algorithm.</p>
<h2>Clean Interface with Cached Image Preprocessing</h2>
<p>Many computer vision tasks nowadays consist of quite a few preprocessing
layers: image pyramid generation, color space conversion etc. These potentially
redundant operations cannot be easily eliminated within a mature API. ccv
provides a built-in cache mechanism that, while maintains a clean function
interface, effectively does transparent cache for you.
<a href="/doc/doc-cache"> - How?</a></p>
<p>For computer vision community, there is no shortage of good algorithms, good
implementation is what it lacks of. After years, we stuck in between either the
high-performance, battle-tested but old algorithm implementations, or the new,
shining but Matlab algorithms. ccv is my take on this problem, hope you enjoy
it.</p>
<h2>License</h2>
<p>ccv source code is distributed under <a href="https://raw.github.com/liuliu/ccv/unstable/COPYING">BSD 3-clause License</a>.<p>
<p>ccv's data models and documentations are distributed under <a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.<p>
<h2><a href="/tutorial">Getting Started</a></h2>
<h2><a href="/doc">Documentation</a></h2>
<h2><a href="/lib">Library Reference</a></h2>
<h2>Dated Posts</h2><ul class="sub-list">
{% for post in site.posts offset:1 %}
{% unless post.lib or post.doc %}
<li><a href="{{ post.url }}">{{ post.title }}. - {{ post.date | date_to_human_string }}</a></li>
{% endunless %}
{% endfor %}
</ul>