expand html analysis
This commit is contained in:
78
results/templates/pages.html
Normal file
78
results/templates/pages.html
Normal file
@@ -0,0 +1,78 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8"/>
|
||||
<meta name="viewport" content="initial-scale=1.0,maximum-scale=1.0" />
|
||||
<title>__FNAME__ – Page Analyis</title>
|
||||
<link rel="stylesheet" type="text/css" href="../style.css">
|
||||
<script type="text/javascript">
|
||||
var idx = -1;
|
||||
document.addEventListener("keydown", keyDownHandler, false);
|
||||
function keyDownHandler(e) {
|
||||
if (e.key == "Right" || e.key == "ArrowRight") {
|
||||
idx = Math.min(idx + 1, 28);
|
||||
} else if (e.key == "Left" || e.key == "ArrowLeft") {
|
||||
idx = Math.max(idx - 1, 0);
|
||||
} else {
|
||||
return;
|
||||
}
|
||||
location.replace('#tb-i' + idx);
|
||||
}
|
||||
</script>
|
||||
</head>
|
||||
<body>
|
||||
<nav class="small">
|
||||
<a href="../index.html" class="home"></a>
|
||||
<a href="#top">Top</a>
|
||||
<a href="#count">Count</a>
|
||||
<a href="#double-rune">Double-Rune</a>
|
||||
<a href="#ioc">IoC</a>
|
||||
<a href="#running-ioc">Running-IoC</a>
|
||||
<a href="#concealment">Concealment</a>
|
||||
</nav>
|
||||
<h1 id="top">Page Analysis: __FNAME__</h1>
|
||||
<h2 id="count">Count</h2>
|
||||
__SEC_COUNTS__
|
||||
|
||||
<h2 id="double-rune">Double-Rune Occurrence</h2>
|
||||
<p>
|
||||
The following analysis looks at two neighboring runes.
|
||||
Whenever two identical runes appear one after the other, the number sequence will print a “1” on dark background.
|
||||
</p>
|
||||
<p>
|
||||
<b>Note:</b> Hover on a cell to see the offset in the file.
|
||||
</p>
|
||||
__SEC_DOUBLE__
|
||||
|
||||
<h2 id="ioc">Index of Coincidence (IoC)</h2>
|
||||
<p>
|
||||
Quick IoC recap: Normal english IoC is about 1.77.
|
||||
Values below 1.4 are highly unlikely to be anywhat meaningful.
|
||||
Predicting english text with IoC gets worse if the text is very short.
|
||||
</p>
|
||||
<p>Here we are considering to either ᚠ being an interrupt; or it's inverse ᛠ.</p>
|
||||
<p>
|
||||
<b>Note:</b> the darker the cell, the better the prediction.
|
||||
The runes per length columns influences the results of the other columns; so if this is low, the other columns are not reliable.
|
||||
</p>
|
||||
__SEC_IOC__
|
||||
|
||||
<h2 id="running-ioc">Running IoC</h2>
|
||||
<p>
|
||||
This section perfoms a running IoC with a window size on the whole text.
|
||||
For example, a window size of 50 will look at the first 50 runes and calculate the IoC (high).
|
||||
This will be the first value in the list.
|
||||
The text is offsetted by one and the next 50 runes are evaluated.
|
||||
This contiunes to the last set of 50 runes.
|
||||
</p>
|
||||
<p>
|
||||
Same rules apply as to normal IoC; an IoC on 20 runes is just too small to get a meaningful result.
|
||||
But it helps to get the bigger picture ;).
|
||||
</p>
|
||||
__SEC_IOC_FLOW__
|
||||
|
||||
<h2 id="concealment">Concealment Analysis</h2>
|
||||
__SEC_CONCEAL__
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user