Fixing broken links

pull/1/head
Oliver Kennedy 2015-12-03 20:12:34 -05:00
parent 2c3b1f5bc2
commit 9866a8f679
42 changed files with 25 additions and 23 deletions

BIN
.DS_Store vendored

Binary file not shown.

3
.gitignore vendored
View File

@ -1 +1,2 @@
site
site
.DS_Store

BIN
assets/.DS_Store vendored

Binary file not shown.

BIN
assets/logos/.DS_Store vendored

Binary file not shown.

View File

@ -26,10 +26,8 @@ var metalsmith = Metalsmith(__dirname)
pattern: 'css/*.css'
}))
// .use(inplace({ "engine" : "handlebars" }))
.use(markdown())
.use(assets({
source: './assets',
destination: './assets'
.use(markdown({
pattern: "**/*.md"
}))
.use(paths({
property: "paths"

View File

@ -27,7 +27,7 @@
<li><a href="{{{rootPath}}}projects/index.html">Projects</a></li>
<li><a href="{{{rootPath}}}teaching/index.html">Teaching</a></li>
<li><a href="{{{rootPath}}}pubs.html">Publications</a></li>
<li><a href="{{{rootPath}}}grants.html">Funding</a></li>
<li><a href="{{{rootPath}}}grants/index.html">Funding</a></li>
<li><a href="http://gitlab.odin.cse.buffalo.edu/odin-lab/documentation/wikis/home">Wiki</a></li>
</div>

BIN
src/.DS_Store vendored

Binary file not shown.

View File

Before

Width:  |  Height:  |  Size: 3.9 KiB

After

Width:  |  Height:  |  Size: 3.9 KiB

View File

Before

Width:  |  Height:  |  Size: 4.2 KiB

After

Width:  |  Height:  |  Size: 4.2 KiB

View File

Before

Width:  |  Height:  |  Size: 4.7 KiB

After

Width:  |  Height:  |  Size: 4.7 KiB

View File

Before

Width:  |  Height:  |  Size: 6.2 KiB

After

Width:  |  Height:  |  Size: 6.2 KiB

View File

Before

Width:  |  Height:  |  Size: 7.9 KiB

After

Width:  |  Height:  |  Size: 7.9 KiB

View File

Before

Width:  |  Height:  |  Size: 3.7 KiB

After

Width:  |  Height:  |  Size: 3.7 KiB

View File

Before

Width:  |  Height:  |  Size: 16 KiB

After

Width:  |  Height:  |  Size: 16 KiB

View File

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 18 KiB

View File

Before

Width:  |  Height:  |  Size: 553 B

After

Width:  |  Height:  |  Size: 553 B

View File

Before

Width:  |  Height:  |  Size: 2.8 KiB

After

Width:  |  Height:  |  Size: 2.8 KiB

View File

Before

Width:  |  Height:  |  Size: 3.6 KiB

After

Width:  |  Height:  |  Size: 3.6 KiB

View File

Before

Width:  |  Height:  |  Size: 353 KiB

After

Width:  |  Height:  |  Size: 353 KiB

View File

Before

Width:  |  Height:  |  Size: 8.3 KiB

After

Width:  |  Height:  |  Size: 8.3 KiB

View File

Before

Width:  |  Height:  |  Size: 145 KiB

After

Width:  |  Height:  |  Size: 145 KiB

View File

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 22 KiB

View File

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 31 KiB

View File

Before

Width:  |  Height:  |  Size: 36 KiB

After

Width:  |  Height:  |  Size: 36 KiB

View File

Before

Width:  |  Height:  |  Size: 24 KiB

After

Width:  |  Height:  |  Size: 24 KiB

View File

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 26 KiB

View File

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

View File

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 67 KiB

View File

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 12 KiB

View File

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 26 KiB

BIN
src/grants/.DS_Store vendored

Binary file not shown.

BIN
src/ideas/.DS_Store vendored

Binary file not shown.

BIN
src/papers/.DS_Store vendored

Binary file not shown.

BIN
src/projects/.DS_Store vendored

Binary file not shown.

Binary file not shown.

View File

@ -1,41 +1,44 @@
##<img class="alignnone wp-image-5" src="assets/astral.png" alt="ASTral" width="43" height="43" /><a title="ASTral" href="astral.html">ASTral / Just In Time Data Structures</a>
## <a href="mimir/index.html"><img src="../assets/logos/mimir_logo_final.png" alt="" width="266" height="106" /></a>
Many analytics tasks are based on information that is initially incomplete, inconsistent, or simply used incorrectly. Existing strategies to help people cope with these sources of uncertainty often require heavyweight upfront organizational tasks (i.e., tagging, data-cleaning, or modeling). The Mimir project aims to streamline this process, making it more on-demand and intuitive.
<hr />
## <img src="../assets/logos/BlackHat.png" alt="BlackHat" width="43" height="43" /><a href="insider-threats/index.html">Insider Threat Detection</a>
One of the greatest threats to a the security of a database system comes from within: Users who have been granted access to data using it in a malicious or illegitimate way. Our goal is to develop new types of statistical signatures for a user or role's behavior as they access a database. Using these signatures, we can identify non-standard behvaior that could be evidence of malicious activity.
<hr />
## <img src="../assets/logos/astral.png" alt="ASTral" width="43" height="43" /><a title="ASTral" href="astral/index.html">ASTral / Just In Time Data Structures</a>
ASTral is a database that uses a combination of programming language, program optimization, and data structure techniques to create and maintain self-adapting physical layouts that rapidly react to changing workloads.
<hr />
<h2><img class="alignnone wp-image-5" src="http://odin.cse.buffalo.edu/wp-content/uploads/2015/10/PocketData.png" alt="PocketData" width="43" height="43" /> <span style="text-decoration: underline;"><a title="PocketData" href="http://odin.cse.buffalo.edu/research/pocketdata/">PocketData</a></span></h2>
<p style="text-align: justify;">The PocketData project explores how smartphones make use of embedded databases in the interest of designing new energy-efficient, low-latency, developer-friendly data management tools for pocket-scale data.</p>
## <img src="../assets/logos/PocketData.png" alt="PocketData" width="43" height="43" /><a title="PocketData" href="pocketdata/index.html">PocketData</a>
The PocketData project explores how smartphones make use of embedded databases in the interest of designing new energy-efficient, low-latency, developer-friendly data management tools for pocket-scale data.
<hr />
<a href="http://odin.cse.buffalo.edu/research/mimir/"><img class="aligncenter wp-image-720" src="http://odin.cse.buffalo.edu/wp-content/uploads/2015/10/mimir_logo_final.png" alt="" width="133" height="53" /></a>
<p style="text-align: justify;">Many analytics tasks are based on information that is initially incomplete, inconsistent, or simply used incorrectly. Existing strategies to help people cope with these sources of uncertainty often require heavyweight upfront organizational tasks (i.e., tagging, data-cleaning, or modeling). The Mimir project aims to streamline this process, making it more on-demand and intuitive.</p>
## <a href="http://blue.cse.buffalo.edu/projects/maybe/"><tt>maybe</tt> Statements</a>
<hr />
One of the reasons programming mobile systems is so hard is the uncertainty created by the wide variety of environments a typical app encounters at runtime. Programmers should not be forced to make choices about runtime environments at development time. The Maybe project aims to create an infrastructure that developers can use to analyze and optimize program behavior __after__ it enters the wild.
<h2><img class="alignnone wp-image-7" src="http://odin.cse.buffalo.edu/wp-content/uploads/2014/10/BlackHat.png" alt="BlackHat" width="43" height="43" /><a href="http://odin.cse.buffalo.edu/research/insider-threats/"><span style="text-decoration: underline;">Insider Threat Detection</span></a></h2>
<p style="text-align: justify;">One of the greatest threats to a the security of a database system comes from within: Users who have been granted access to data using it in a malicious or illegitimate way. Our goal is to develop new types of statistical signatures for a user or role's behavior as they access a database. Using these signatures, we can identify non-standard behvaior that could be evidence of malicious activity.</p>
<hr/>
# Older Projects
<hr />
<h2>   ?   <a href="http://blue.cse.buffalo.edu/projects/maybe/"><span style="text-decoration: underline;"><tt>maybe</tt> Statements</span></a></h2>
<p style="text-align: justify;">One of the reasons programming mobile systems is so hard is the uncertainty created by the wide variety of environments a typical app encounters at runtime. Programmers should not be forced to make choices about runtime environments at development time. The Maybe project aims to create an infrastructure that developers can use to analyze and optimize program behavior <strong>after</strong> it enters the wild.</p>
<h1><a href="http://www.dbtoaster.org"><img class="alignnone wp-image-75" src="http://mjolnir.cse.buffalo.edu/wp-content/uploads/2014/10/dbtoaster-logo.gif" alt="dbtoaster-logo" width="174" height="80" /></a></h1>
## <a href="http://www.dbtoaster.org"><img src="../assets/logos/dbtoaster-logo.gif" alt="dbtoaster-logo" width="174" height="80" /></a>
<a href="http://www.dbtoaster.org">DBToaster</a> is an SQL-to-native-code compiler. It generates lightweight, specialized, embeddable query engines for applications that require real-time, low-latency data processing and monitoring capabilities. The DBToaster compiler generates code that can be easily incorporated into any C++ or JVM-based (Java, Scala, ...) project.
Since 2009, DBToaster has spearheaded the currently ongoing database compilers revolution. If you are looking for the fastest possible execution of continuous analytical queries, DBToaster is the answer. DBToaster code is 3-6 orders of magnitude faster than all other systems known to us.
<em>DBToaster was started at Cornell by the research group of Christoph Koch (now at EPFL).  Development on DBToaster continues at the DATA lab at <a href="http://data.epfl.ch">EPFL</a>.</em>
<hr />
<a href="http://maybms.sourceforge.net"><img class="alignnone wp-image-76" src="http://mjolnir.cse.buffalo.edu/wp-content/uploads/2014/10/maybms_logo.jpg" alt="maybms_logo" width="180" height="76" /></a>
## <a href="http://maybms.sourceforge.net"><img src="../assets/logos/maybms_logo.jpg" alt="maybms_logo" width="180" height="76" /></a>
The <span class="cmti-12"><a href="http://maybms.sourceforge.net">MayBMS</a> </span>system (note: MayBMS is read as “maybe-MS”, like DBMS) is a complete probabilistic database management system that leverages robust relational database technology: MayBMS is an extension of the Postgres server backend. MayBMS is open source and the source code is available under the BSD license.
The <a href="http://maybms.sourceforge.net">MayBMS</a> system (note: MayBMS is read as “maybe-MS”, like DBMS) is a complete probabilistic database management system that leverages robust relational database technology: MayBMS is an extension of the Postgres server backend. MayBMS is open source and the source code is available under the BSD license.
MayBMS stands alone as a complete probabilistic database management system that supports a powerful, compositional query language for which nevertheless worst-case efficiency and result quality guarantees can be made. The MayBMS backend is accessible through several APIs, with efficient internal operators for computing and managing probabilistic data.

Binary file not shown.

Binary file not shown.