|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use Result | |
|---|---|
| org.apache.pig.backend.hadoop.executionengine.physicalLayer | Implementation of physical operators that use hadoop as the execution engine and data storage. |
| org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators | |
| org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators |
| Uses of Result in org.apache.pig.backend.hadoop.executionengine.physicalLayer |
|---|
| Fields in org.apache.pig.backend.hadoop.executionengine.physicalLayer declared as Result | |
|---|---|
protected Result |
PhysicalOperator.res
|
| Methods in org.apache.pig.backend.hadoop.executionengine.physicalLayer that return Result | |
|---|---|
Result |
PhysicalOperator.getNext(byte dataType)
Implementations that call into the different versions of getNext are often identical, differing only in the signature of the getNext() call they make. |
Result |
PhysicalOperator.getNextBigDecimal()
|
Result |
PhysicalOperator.getNextBigInteger()
|
Result |
PhysicalOperator.getNextBoolean()
|
Result |
PhysicalOperator.getNextDataBag()
|
Result |
PhysicalOperator.getNextDataByteArray()
|
Result |
PhysicalOperator.getNextDateTime()
|
Result |
PhysicalOperator.getNextDouble()
|
Result |
PhysicalOperator.getNextFloat()
|
Result |
PhysicalOperator.getNextInteger()
|
Result |
PhysicalOperator.getNextLong()
|
Result |
PhysicalOperator.getNextMap()
|
Result |
PhysicalOperator.getNextString()
|
Result |
PhysicalOperator.getNextTuple()
|
Result |
PhysicalOperator.processInput()
A generic method for parsing input that either returns the attached input if it exists or fetches it from its predecessor. |
| Uses of Result in org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators |
|---|
| Methods in org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators with parameters of type Result | |
|---|---|
protected Result |
POProject.consumeInputBag(Result input)
|
| Uses of Result in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators |
|---|
| Fields in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators with type parameters of type Result | |
|---|---|
protected BlockingQueue<Result> |
POStream.binaryInputQueue
|
protected BlockingQueue<Result> |
POStream.binaryOutputQueue
|
| Methods in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators that return Result | |
|---|---|
protected Result |
POCounter.addCounterValue(Result input)
Add current task id and local counter value. |
Result |
PORank.addRank(Result input)
Reads the output tuple from POCounter and the cumulative sum previously calculated. |
Result |
POStream.getNextHelper(Tuple t)
|
Result |
POUnion.getNextTuple()
The code below, tries to follow our single threaded shared execution model with execution being passed around each non-drained input |
Result |
POStream.getNextTuple()
|
Result |
POStore.getNextTuple()
|
Result |
POSplit.getNextTuple()
|
Result |
POSortedDistinct.getNextTuple()
|
Result |
POSort.getNextTuple()
|
Result |
PORank.getNextTuple()
|
Result |
POPreCombinerLocalRearrange.getNextTuple()
Calls getNext on the generate operator inside the nested physical plan. |
Result |
POPartitionRearrange.getNextTuple()
Calls getNext on the generate operator inside the nested physical plan. |
Result |
POPartialAgg.getNextTuple()
|
Result |
POPackageLite.getNextTuple()
Similar to POPackage.getNext except that only one input is expected with index 0 and ReadOnceBag is used instead of DefaultDataBag. |
Result |
POPackage.getNextTuple()
From the inputs, constructs the output tuple for this co-group in the required format which is (key, {bag of tuples from input 1}, {bag of tuples from input 2}, ...) |
Result |
POOptimizedForEach.getNextTuple()
Calls getNext on the generate operator inside the nested physical plan and returns it maintaining an additional state to denote the begin and end of the nested plan processing. |
Result |
POMultiQueryPackage.getNextTuple()
Constructs the output tuple from the inputs. |
Result |
POMergeJoin.getNextTuple()
|
Result |
POMergeCogroup.getNextTuple()
|
Result |
POLocalRearrange.getNextTuple()
Calls getNext on the generate operator inside the nested physical plan. |
Result |
POLoad.getNextTuple()
The main method used by this operator's successor to read tuples from the specified file using the specified load function. |
Result |
POLimit.getNextTuple()
Counts the number of tuples processed into static variable soFar, if the number of tuples processed reach the limit, return EOP; Otherwise, return the tuple |
Result |
POJoinPackage.getNextTuple()
Calls getNext to get next ForEach result. |
Result |
POForEach.getNextTuple()
Calls getNext on the generate operator inside the nested physical plan and returns it maintaining an additional state to denote the begin and end of the nested plan processing. |
Result |
POFilter.getNextTuple()
Attaches the proccesed input tuple to the expression plan and checks if comparison operator returns a true. |
Result |
POFRJoin.getNextTuple()
|
Result |
PODistinct.getNextTuple()
|
Result |
PODemux.getNextTuple()
|
Result |
POCross.getNextTuple()
|
Result |
POCounter.getNextTuple()
|
Result |
POCombinerPackage.getNextTuple()
|
Result |
POCollectedGroup.getNextTuple()
|
protected Result |
POForEach.processPlan()
|
| Methods in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators that return types with arguments of type Result | |
|---|---|
BlockingQueue<Result> |
POStream.getBinaryInputQueue()
|
BlockingQueue<Result> |
POStream.getBinaryOutputQueue()
|
| Methods in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators with parameters of type Result | |
|---|---|
protected Result |
POCounter.addCounterValue(Result input)
Add current task id and local counter value. |
Result |
PORank.addRank(Result input)
Reads the output tuple from POCounter and the cumulative sum previously calculated. |
| Method parameters in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators with type arguments of type Result | |
|---|---|
protected Tuple |
POLocalRearrange.constructLROutput(List<Result> resLst,
List<Result> secondaryResLst,
Tuple value)
|
protected Tuple |
POLocalRearrange.constructLROutput(List<Result> resLst,
List<Result> secondaryResLst,
Tuple value)
|
protected Tuple |
POPreCombinerLocalRearrange.constructLROutput(List<Result> resLst,
Tuple value)
|
protected Tuple |
POCollectedGroup.constructOutput(List<Result> resLst,
Tuple value)
|
protected DataBag |
POPartitionRearrange.constructPROutput(List<Result> resLst,
Tuple value)
|
protected Object |
POLocalRearrange.getKeyFromResult(List<Result> resLst,
byte type)
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |


Maximize
the potential of your clinical and genomic data by combining it with best-in-class
analysis, reference data
sets and domain-specific visualizations. To request training or a custom solution contact
us at
<EMAIL_ADDRESS>Analysis
ReliableAll data manipulation and augmentation is done using
established open source libraries and public stores with citations.
ReproducibleAll analysis in Oncoscape is fully reproducible. Pause,
rewind and interrogate every variable and result.
Data
Public Data SetsExplore The Cancer Genome Atlas (TCGA) and other curated
data from our growing list of reference libraries.
Private Data Upload
Securely manage and analyze your clinical and genomics data, then share results with
colleagues.
Gene SetsSelect from thousands of curated gene sets from MSigDB or
create your own.
PathwaysSelect from thousands of top level pathways from Reactome,
PathwayCommons, and more.
Visualization
Clinical DashboardCompare cohorts at a glance
SpreadsheetSort and export your data, cohorts and genes of interest in
tabular format.
Matrix DecompositionVisualize the inherent spatial structure of high dimensional
datasets in 3D. With 13 fully customizable linear dimension
reduction algorithm, select from 5 variants of PCA, Factor Analysis, LDA, SVD and more.
Manifold LearningLike Matrix Decomposition, Manifold Learning seeks to unveil
the spatial structure of high dimensional datasets. Unlike
Matrix Decomposition the dimension reduction process is non-linear. Available methods
include T-SNE, MDS, IsoMap,
Local Linear and Spectral Embedding.
Heat mapSort, group and visualize your data using 7 agglomerative
clustering algorithms in conjunction with 20 distance metrics.
Leverage dendrogram to sub select populations of samples or markers for further
investigation.
GenomeIdentify chromosomal regions of interest by projecting your
data onto a visual representation of the genome. Overlay
CNV, Gistic or expression data along with Topically Aligned Domains and Cytobands. Explore
thousands of curated gene
sets or create your own.
ChromosomeCompare datasets at the chromosomal level with circos and
linear visualizations. Overlay pathways or topically aligned
domains.
PathwaysOverlay your data on over 5,900 pathways curated from Kegg,
Panther, Reactome, SMPDB, WikiPathways and Pathway Commons.
SurvivalEstimate and compare survival rates for patient populations
using Kaplin Kaplan-Meier, Nelson-Aalen, Aalen, Weibull
and Cox models.
HazardEstimate and compare hazard rates for patient populations
using Kaplin Kaplan-Meier, Nelson-Aalen, Aalen, Weibull and
Cox models.
TimelinesVisualize patterns in time series data with an interactive
swimmer plot. Sort, group and highlight patients using clinical
attributes.
Box + WhiskerGain insights into the distribution of your data by
visualizing the minimum, first quartile, median, 3rd quartile and
maximum values.
Force Directed GraphVisualize graph data in three-dimensions using a class of
algorithms called " force directed graphs. " These algorithms
use the number and strength of connections to position nodes.
EdgesConnect multiple graphs with edges. Link tumor/normal
samples or visualize mutations.


In the previous article we’ve set up the necessary soft for our rails application. In this article we’ll meet wit Capistrano, configure Nginx and Puma server and logrotate.
Capistrano
Add this lines or neccessary gems to the Gemfile of your application, mentioned below:
gem 'puma'
and
group :development do
gem 'capistrano'
gem 'capistrano-rails'
gem 'capistrano-bundler'
gem 'capistrano-rvm'
gem 'capistrano3-puma'
end
I like puma in development because it’s better than Webrick. But if you like something different (like pow) in development add ‘puma’ gem to :production section.
After that:
bundle install
cap install
To the new Capfile add
require 'capistrano/rvm'
require 'capistrano/bundler'
require 'capistrano/rails/assets'
require 'capistrano/rails/migrations'
require 'capistrano/puma'
To config/deploy.rb modify this strings:
set :application, 'your_application_name'
set :repo_url, 'your repository_url'
set :deploy_user, 'deploy'
set :deploy_to, "/home/#{fetch :deploy_user}/apps/#{fetch :application}"
set :rvm_ruby_version, '2.x.x@your_gemset --create'
And set linked files and dirs after that. Linked dirs or files - its files and directories that necessary for the project but not designated to store in your repository. For example config files like database.yml, and folders like vendor/bundle, log, public/uploads (if you use something like CarrierWave to crop photos). This files have to be in a ‘shared’ folder and each release should contain only symlinks for that otherwise it won’t appear in the next release (because that is not presented in the repository)
set :linked_files, fetch(:linked_files, []).push('.env', 'config/you_first_config.yml', 'your_second_config')
set :linked_dirs, fetch(:linked_dirs, []).push('log', 'tmp/pids', 'tmp/cache', 'tmp/sockets', 'vendor/bundle', 'another_folder')
For the security reasons you should store your configuration values such ‘secret_key_base’, postgres username and password, different oauth client_id and client_secrets in environment variables. So, add to your Gemfile
gem 'dotenv-rails'
bundle install
add ~~~ .env ~~~
to your .gitignore file and create .env.example with example parameters in the root of the repository (you should store this file in the remote repository)
And another one - you should have file config/environments/production.rb. The rails default installation contains this file and I suppose that you know or can uderstand this options. If not you should met with configuring rails applications.
After that we should deploy the project the first time we will get the error. Don’t worry, for now it’s okey.
cap production deploy
Add to config/deploy/production.rb
role :app, %w{deploy@your-host-machine-ip}
role :web, %w{deploy@your-host-machine-ip}
role :db, %w{deploy@your-host-machine-ip}
Then ssh to your server as deploy user, go to ~/apps/your_app_folder/shared and create .env file with your very secret values(for syntax and more see .env). Don’t forget to create in shared folder files linked before (yes, that files and folders mentioned in ~~~set :linked_files~~~). So, your config files for example like secrets.yml, sidekiq.yml and others should be in ~/apps/your_app_folder/shared/config
After you do it, run again
cap production deploy
If your need to stop/start puma, use
cap production puma:start
cap production puma:stop
Okey, it’s time to configure Nginx
Login as root and create file /etc/nginx/sites-available/your_app_name.conf and open it via your favorite editor. For example
vim /etc/nginx/sites-available/your_app_name.conf
add there this config options
upstream application {
server unix:/home/deploy/apps/APPNAME/shared/tmp/sockets/puma.sock fail_timeout=0;
}
server {
listen 80;
server_name DOMAIN;
root /home/deploy/apps/APPNAME/current/public;
try_files $uri/index.html $uri @application;
location @application {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass http://application;
access_log /var/log/nginx/APPNAME.access.log;
error_log /var/log/nginx/APPNAME.error.log;
}
location ~ ^/(assets|images|javascripts|stylesheets|swfs|system|uploads)/ {
gzip_static on;
expires max;
add_header Cache-Control public;
add_header Last-Modified "";
add_header ETag "";
open_file_cache max=1000 inactive=500s;
open_file_cache_valid 600s;
open_file_cache_errors on;
break;
}
client_max_body_size 10M;
keepalive_timeout 10;
error_page 500 502 504 /500.html;
error_page 503 @503;
location = /50x.html {
root html;
}
location = /404.html {
root html;
}
location @503 {
error_page 405 = /system/maintenance.html;
if (-f $document_root/system/maintenance.html) {
rewrite ^(.*)$ /system/maintenance.html break;
}
rewrite ^(.*)$ /503.html break;
}
if ($request_method !~ ^(GET|HEAD|PUT|POST|DELETE|OPTIONS)$ ){
return 405;
}
if (-f $document_root/system/maintenance.html) {
return 503;
}
location ~ \.(php|html)$ {
return 405;
}
}
where replace ‘your_app_name’ to your real app name. Tell about each line is out of this article because this articles is like a tutorial for people like me. When I stood in front of the problem deployment problem it was the last thing that I wanted to know what means each line of this config.
After that go to /etc/nginx/sites-enabled and create symlink to the file described below.
cd /etc/nginx/sites-enabled
ln -s ../sites-available/your_app_name.conf
And restart nginx
service nginx restart
Set up logrotate
# save as /etc/logrotate.d/APPNAME
/home/deploy/apps/APPNAME/shared/log/*.log {
su deploy deploy
daily
missingok
rotate 30
compress
delaycompress
notifempty
copytruncate
}
sudo logrotate /etc/logrotate.d/APPNAME -f
That is all. If all was correct you should see your site in the browser at http://your-machine-ip


{{race?.line.name}} {{race?.date.toDateString()}} {{race?.direction}}
Reserved children
| Child | Taken | Absent |
|---|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
|
Non Reserved
| Child | Taken |
|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
Non Reserved
| Child | Taken |
|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
Absent children
| Child | Taken |
|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
Absent children
| Child | Taken |
|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
Taken children
| {{child.childDetails.name}} {{child.childDetails.surname}} |
Reserved children
| Child | Taken | Absent |
|---|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
|
Reserved children
| Child | Delivered | Absent |
|---|---|---|
| {{child.childDetails.name}} {{child.childDetails.surname}} |
|
|


Don’t break things yourself. Share the joy of destruction with others!
9/1/2022, 2:05:59 PM
Favs: 17
Retweets: 2
link--- layout: tweet ---
Don’t break things yourself. Share the joy of destruction with others!
9/1/2022, 2:05:59 PM
Favs: 17
Retweets: 2
linkConstruction steps to first grievous, entirely blocking mistake: 7 💪🏻
9/1/2022, 2:55:31 PM
Favs: 1
Retweets: 0
linkSecond MASSIVE error at step 7, but not noticed until step 17. 🤬
9/1/2022, 7:05:51 PM
Favs: 0
Retweets: 0
link


Exp. Calc
PoE Tools
Path of Exile Tools
A collection of tools, that help to quickly calculate stats relevant to the game
Path of Exile
Angular seed app: v


{% extends "layout.html" %} {% block content %}
{{ error }}
Already registered? Return to the home page to login.
Look at all the benefits!


Upcoming Events
We offer both competitive and noncompetitve tournaments for a variety of games free to join! (Each participant must pay $5 entrance fee)
Our Weekly Super Smash Bros tournaments are our most popular but we host a variety of games depending on popularity
Lifelight
Combosed By: Hideki Sakamoto
Performed By: Abby Trott
Weekend Smash Tournaments
- Friday 5:00pm
- Friday 7:00pm
- Saturday 12:30pm
- Saturday 3:00pm
- Saturday 5:00pm
- Saturday 7:00pm
- Sunday 3:00pm
- Sunday 5:00pm
Call of Duty 4v4 (Non Competitive)
- Tuesday, October 19, 4:00pm
- Thursday, October 21, 4:00pm
- Saturday, October 23, 6:00pm
Call of Duty 4v4 (Competitive)
- Tuesday, October 19, 4:30pm
- Thursday, October 21, 4:30pm
- Saturday, October 23, 6:30pm
Competitive tournaments have a $60 prize pool for the winners.


{% include "_detail_field.html" with field="scope_and_content" name="Scope and Content" %}
{% include "_detail_field.html" with field="creator" name="Creator" %}
{% include "_detail_field.html" with field="revision_history" name="Revision History" %}
{% include "_detail_field.html" with field="rules" name="Rules" %}
{% include "_detail_field.html" with field="arrangement" name="Arrangement" %}
{% include "_detail_field.html" with field="finding_aids" name="Finding Aids" %}
{% include "_detail_field.html" with field="reproduction_conditions" name="Reproduction Conditions" %}
{% include "_detail_field.html" with field="access_conditions" name="Access Conditions" %}
{% include "_detail_field.html" with field="location_of_originals" name="Location of Originals" %}
{% include "_detail_field.html" with field="location_of_copies" name="Location of Copies" %}
{% include "_detail_field.html" with field="acquisition" name="Acquisition" %}
{% include "_detail_field.html" with field="dates_of_existence" name="Dates of existence" %}
{% include "_detail_field.html" with field="notes" name="Notes" %}


Wendy:
This flower...
The smell. I remember it. I remember... my friend.
It's still so confusing. I can only recall one thing, and I don't know what it means: This flower was registered in experiment plan file N-45.
Administrator Pavel, and...
... um...
Ask her if she is OK.


Hello
To add a skill, fill in the form below.
Year taken:
Charge per hour(optional):
Teacher:
Grade in class:
A
B
C
D
F
Select class:
English
History
Pre-Algebra
Algebra
Algebra 2
Geometry
Trigonometry
Precalculus
AP Calculus AB
AP Calculus BC
Statistics
Rhetoric
AP English Literature
AP English Language
AP European History
AP United States History
Biology
AP Biology
Chemistry
Chemistry Honors
AP Chemistry
AP Environmental Science
Physics
AP Physics
SAT
ACT
AP score:
N/A
5
4
3
2
1
SAT score:
ACT score:
Comments (optional):
Submit
Cancel


Sign out
Delete account
Sign in to post.
Friendly Microblog
Powered by Firebase
Loading...
What's on your mind?
in 140 characters or less
Save this for posterity
Firehose of recent posts


{% load bootstrap3 %} {% load i18n %} {% include 'editor/fragment_modal_close.html' %}
{% trans 'Do you really want to accept and apply these changes?' %}


| PVC (Poly VinylChloride) /vinyl/pleather/artificial leather |
Emits pure chlorine gas when cut! |
Don’t ever cut this material as it will ruin the optics, cause the metal of the machine to corrode, and ruin the motion control system. |
| ABS |
Emits cyanide gas and tends to melt |
ABS does not cut well in a laser cutter. It tends to melt rather than vaporize, and has a higher chance of
catching on fire and leaving behind melted gooey deposits on the vector cutting grid. It also does not
engrave well (again, tends to melt). |
| Thick ( >1mm ) Polycarbonate/Lexan |
Cut very poorly, discolor,catch fire |
Polycarbonate is often found as flat, sheet material. The window of the laser cutter is made of Polycarbonate because polycarbonate strongly absorbs infrared radiation! This is the frequency of light the laser cutter uses to cut materials, so it is very ineffective at cutting polycarbonate. Polycarbonate is a poor choice for laser cutting. |
| HDPE/milk bottle plastic |
Catches fire and melts |
It melts. It gets gooey. Don’t use it. |
| PolyStyrene Foam |
Catches fire |
It catches fire, it melts, and only thin pieces cut. This is the #1 material that causes laser fires!!! |
| PolyPropylene Foam |
Catches fire |
Like PolyStyrene, it melts, catches fire, and the melted drops continue to burn and turn into rock-hard drips and pebbles. |
| Fiberglass |
Emits fumes |
It’s a mix of two materials that cant’ be cut. Glass (etch, no cut) and epoxy resin (fumes) |
| Coated Carbon Fiber |
Emits noxious fumes |
|


Before Change
VERSION = tfds.core.Version("1.0.0",
experiments={tfds.core.Experiment.S3: False})
SUPPORTED_VERSIONS = [
tfds.core.Version(
"2.0.0", "New split API (https://tensorflow.org/datasets/splits)"),
]
def _info(self):
return tfds.core.DatasetInfo(
builder=self,
After Change
class Nsynth(tfds.core.BeamBasedBuilder):
A large-scale and high-quality dataset of annotated musical notes.
BUILDER_CONFIGS = [
NsynthConfig(description=_FULL_DESCRIPTION),
NsynthConfig(
gansynth_subset=True,
description=_GANSYNTH_DESCRIPTION),
NsynthConfig(
gansynth_subset=True,
estimate_f0_and_loudness=True,
description=_GANSYNTH_DESCRIPTION + _F0_AND_LOUDNESS_ADDENDUM),
]
def _info(self):
features = {
"id":


Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform
and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.
The
Spring Tool Suite is an Eclipse-based development environment that is customized for developing Spring applications. It provides a ready-to-use environment to implement, debug,
run, and deploy your Spring applications, including integrations for Pivotal tc Server, Pivotal Cloud Foundry, Git, Maven, AspectJ, and more.
Spring Security Spring Security is a powerful and highly customizable authentication and access-control framework. It is the de-facto standard for securing Spring-based
applications. Spring Security is a framework that focuses on providing both authentication and authorization to Java applications. Like all Spring projects, the real power of Spring Security is found in how easily it
can be extended to meet custom requirements
JSON Web Token (JWT) is an open standard
(RFC 7519) that defines a compact and self-contained way for securely transmitting
information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using
RSA or ECDSA.
Angular 12 Angular is a platform and framework for building single-page client applications using HTML and TypeScript. Angular is written in TypeScript. It implements core and optional
functionality as a set of TypeScript libraries that you import into your applications.
Hibernate ORM enables developers to more easily write applications whose data outlives the application process. As an Object/Relational Mapping (ORM) framework, Hibernate is concerned
with data persistence as it applies to relational databases (via JDBC).
In addition to its own "native" API, Hibernate is also an implementation of the Java Persistence API (JPA) specification. As such, it can
be easily used in any environment supporting JPA including Java SE applications, Java EE application servers, Enterprise OSGi containers, etc.
Bootstrap is an open source toolkit for developing with HTML, CSS, and JS. Quickly prototype your ideas or build your entire app with our Sass variables and mixins, responsive
grid system, extensive prebuilt components, and powerful plugins built on jQuery.


Drag and Drop the Columns in order to arrange them in an order you like. You can hide them as well by dragging them to the right.


A classical problem in probability is about "collisions" of birthdays. This birthday problem was posed by Richard von Mises and other mathematicians (its origin has not been well established) and asks, "If there are $n$ people in a room, what is the chance that some pair among them have the same birthday?"
The problem is commonly solved under the assumptions that each year consists of 365 days and that each person is equally likely to be born on any of the 365 days regardless of the birthdays of others.
You can see that assumptions ignore leap years as well as multiple births (twins, for example) and any lack of uniformity in the distribution of births during the year. These assumptions make calculations simpler but need not reflect the reality of birthdays in every population. Data scientists have to be careful about their assumptions – if the assumptions don't reflect the truth, then the conclusions won't either.
So let's note that we are working under simplifying assumptions that we should check before making conclusions about specific groups. Ignoring leap years and multiple births should not make a big difference to the conclusions in any case. If births are more likely to happen at some times of year than others, then it has been proved that the chance of matching birthdays is larger than the answer under our assumptions.
There are many variations of the birthday problem, but we will stick with the classic.
We will state our assumptions succinctly as "all $365^n$ sequences of birthdays are equally likely". You can see that this makes the birthday problem the same as the collision problem of the previous section, with $N = 365$. As before, the only interesting cases are when $n \le N$, for which
$$ P(\text{all $n$ birthdays are different}) ~=~ \prod_{i=0}^{n-1} \frac{N-i}{N} $$For a known $N$, the function p_all_different
takes $n$ as its argument and returns this probability. The rest of the code displays all the results in a table. The table includes a column containing the chance that there is a collision:
N = 365
def p_all_different(n):
individuals_array = np.arange(n)
return np.prod((N - individuals_array)/N)
results = Table().with_column('Trials', np.arange(1, N+1, 1))
different = results.apply(p_all_different, 'Trials')
results = results.with_columns(
'P(all different)', different,
'P(at least one match)', 1 - different
)
results
The first thing to notice in the table is the use of the label Trials
to denote people. In probability it is common to think of random experiments as sequences of trials in which the outcome of each trial depends on chance. In the birthday problem, each person is being thought of as a trial, and we are looking to see whether there is at least one matching pair of birthdays among all the trials.
Next, notice that in the boring case where there is just one person, there can't be a matching pair of birthdays, and $P(\text{all different})$ has been defined as 1 because there is no match. In many problems there are such "edge cases" that have to be handled individually.
Finally, notice that when the number of people is small, the chance they all have different birthdays is large. This is consistent with our intuition that if the number of individuals is small relative to the number of available hash values, and you assign values to individuals at random, then the chance of a collision is small.
But the chance of a collision increases as the number of people increases. In fact, it increases rather sharply.
results.scatter('Trials', 'P(at least one match)')
plt.xlim(0, N/3)
plt.ylim(0, 1);
You can see that if there are more than about 50 people, then the chance of a matching pair of birthdays is pretty close to 1.
How many people must there be for the chance of a collision to be more than 50%? Let's see if we can find the smallest number of people for which this happens.
results.where('P(at least one match)', are.between(0.5, 0.51))
With just 23 people, a match is more likely than not. This surprises those who haven't done the calculation, and hence is known as the birthday paradox. But in fact there is nothing paradoxical or contradictory about it at all. It just has to do with the way the chance of a matching pair of birthdays grows as a function of the number of people.
We have done the calculation for $N = 365$, but how fast would the function have grown had $N$ been some other number? We need to know this if we are going to apply our results in contexts other than birthdays.
To figure this out, we could redo our code for various different values of $N$ and see if the output tells us anything for those values. But it is altogether more efficient and insightful to use math, which is what we will do in the next section.


Day 1
Challenges & Myths in Data Sciences
Nutrition Data Sharing: Perspectives from Govt, Academia, & NGOs
Efficacy & Applications of Standardized Nutrition Indicators
Big Data Challenges in Biochemical & Molecular Nutrition
Day 2
Challenges & Solutions in Applied Data Sciences
Harnessing the Power of Geospatial Data in Nutrition
Nutrition in Humanitarian Emergencies Simulation Exercise
Data Sandbox
Day 3
The Future of Nutrition Technology


12.5
Maintenance, Damage and RepairsGenerally the information available from on board is restricted to the observations of passengers as basically reported in Chapter 12.4, because the crew members had been forbidden by their employer ESCO to talk about ESTONIA at all. Only very few have talked, although very carefully, as will be explained on the following pages.
It has also been very difficult to obtain information from N&T/Hornet AB/ Estline or ESCO. Apart from the discussion with Ulf Hobro during the first meeting with the JAIC in Stockholm in February 1995, there are only some details available from the files of the public prosecutor and from those of the JAIC, which will also be discussed subsequently.
1. Maintenance
The vessel was drydocked at Turku between 4-8 January 1993 and the necessary inspections were carried out. At this time also some maintenance work was performed which had been partly ordered by the old owners, Wasa Line, and partly by the technical managers of the new owners, N&T, as outlined in detail in Subchapter 6.5.
Consequently in January 1993 during the time at the yard:
a) the locking devices of visor and bow ramp were neither serviced nor strengthened, and
b) the outer hinges of the bow ramp were not serviced nor were the bushings and bolts renewed, and
c) 15 m of the rubber packings of the visor and 10 m of the rubber packings of the bow ramp were not renewed.
As to (a):
Since the crew was unable to service and strengthen the locking devices of visor and bow ramp, they were never serviced and strengthened until the casualty. Since the crew was also unable to service the hinges of the bow ramp and to renew the bushings and bolts, in particular the port outer hinge, it is a fact that nothing was done to rectify the poor condition of - at least - the port outer bow ramp hinge. It is, however, known from Börje Stenström, head of the technical group of JAIC, that the crew had put the damaged port outer bow ramp hinge on the repair list a number of times, but that repairs were postponed by the technical managers until the next scheduled yard stay, probably in January 1995. The respective memo is attached as Enclosure 12.5.166.As to (b):
Also the visor hinges required professional maintenance which the crew was apparently also unable to provide, because according to the testimony of the 2nd engineer Peeter Tüür in June 1996, who is responsible for the technical functioning of visor and bow ramp - the crew had problems to have the hinges properly greased and even had to add oil to the grease to ensure that the grease reached all parts to be lubricated - see Enclosure 12.5.167. Needless to say that the effect of grease is destroyed by adding oil. Due to the severely misaligned visor the hinges could no more be properly lubricated. This resulted in excessive wear of the bronze bushings which consequently had to be renewed.
Such renewal is normally effected by drilling out the steel and bronze bushing by means of a particular milling installation in order to avoid damage to the hinge plates, which would be created if the bushings would be burned out. Whereas drilling, including proper welding of new bushings, takes about 2 days in port - whilst the visor is detached from the vessel and the vessel thus has to be taken out of service - burning is much faster, however, is combined with a loss of material of the hinge plates, the creating of deep burning marks, each of which is a crack starter. It is obvious that such damage to the hinge plates reduced their weight carrying capacity and furthermore increased the propagation of fatigue cracks in the hinge plates. For further details see Subchapter 34.3. Although denied by the technical managers and crew, the steel bushings of both visor hinges were evidently burned out and replaced by new steel and bronze bushings which, however, were fitted in a very unprofessional way. This will be further explained in Subchapter 34.3.As to (c):
On one hand the responsible inspector in the organisation of the technical managers, N&T, Ulf Hobro, stated before the JAIC on 17 February 1995:»... we did not care for the rubber packings, we have never renewed any of them nor was it ever our intention to do so. The visor was full of water at sea and this was known to everybody.«
On the other hand, Lennart Klevberg, in charge of spare parts with N&T, did testify to the criminal police Stockholm, that
»rubber packings for the visor had been ordered but were not installed because Capt. Andresson and Tomas Rasmusson had decided to wait until MARE BALTICUM would be taken over in order to do the replacement on both ferries simultaneously.«
This does not make much sense, however, based on the underwater videos it is indeed a fact that the rubber packings of the visor were missing from forward of the Atlantic lock along the whole port side and about 1 m up the front bulkhead, whilst at the starboard side there were some rubber packings from forward of the Atlantic lock to the "corner of the mouth", which was empty up to ca. 2 m of the front bulkhead.
It is obvious that the visor was no more weathertight and thus full of water at sea up to the outboard level as evident from the watermarks inside of the visor.
2. Damage and Repairs
The crew also denied ever having carried out repairs to the visor, the bow ramp and/or to their locking devices. This is true as far as the major repairs are concerned which would have been necessary to bring the visor back into proper shape and alignment, but which were never carried out. The crew, however, is wrong as far as numerous smaller repairs and rectifications to the visor, the bow ramp and their locking devices are concerned which were frequently performed to avoid the worst and keep visor and bow ramp best terms possible in workable condition. This had been observed by many passengers as outlined in Chapter 12.4. and was even admitted by crew members, for example by the safety officer Ervin Roden who told Spiegel TV on 02.05.97, among other things: "Something was always being repaired on board. There was always welding work being carried out. I am uncertain whether also to the visor. But everywhere repairs were carried out, also in the area of visor and bow ramp and also by the Finns." The complete interview is attached as Enclosure 12.5.168.
Apart from the damages existing already when the ferry was taken over from the previous owners and which were not repaired by the new owners/ managers, it is quite obvious that the ferry sustained more damage to the visor and consequently also to its fixing points, the hinges and locking devices, when for example forcing ice at excessive speed as observed by various passengers. The observation repeated below is just one example:»Observation by Henning Frederiksson on 24.03.94: It was stormy weather and "Estonia" was proceeding in open water at full speed with a following sea when she met pack ice, into which she crashed without any speed reduction. "Estonia" came fast into the pack ice with an enormous crash and had to go backwards and try again. There was 16 m/sec. storm, nevertheless, "Estonia" kept her high speed.«
The results of such reckless navigation are clearly visible on the large photo on the previous page which was taken on the following day, 25 March 1994, in Tallinn by the professional photographer Li Samuelson.
The ice damage sustained by the visor during the months of February and March 1994, when the Gulf of Finland and the Northern and Middle Baltic where more or less continuously covered by ice (see Subchapter 12.4.2), were roughly repaired by replacing parts of shell plating and bottom of the visor in Tallinn whilst the vessel remained in service. The renewed parts are still visible on the visor.This is also confirmed by the observation of the passenger Christer Eriksson, who reported the following:
»I travelled to Tallinn on the "Estonia" on 3/4 May 1994 and left the vessel only at about 10.30 hours when all the other passengers had already gone ashore. The gangway was pulled in and I had to go ashore via the car deck and bow ramp. When I came down on the car deck I noticed a curtain of sparks falling down from the open visor on to the bow ramp and I managed to jump through it and saw on the bow ramp a giant red transformer turned 90° towards the ramp which in my opinion was Red Army surplus. Cables were running up to the port side of the forecastle deck/visor, where obviously heavy burning/ cutting work was in progress. When I returned from ashore at about 06.00 hours the workers were just collecting their tools, but the huge transformer was still on the bow ramp.«
The fax exchange reflecting the above is attached as Enclosure 12.6.169.
Although the work explained above doubtlessly falls into the category "maintenance & repair" and also could not be considered very minor, the repairs are not mentioned in the "List of Maintenance and Repair Works on M.V. 'Estonia', April 1993 - August 1994" which is Supplement No. 230 to the Report of the JAIC. Since also other visible repairs do not appear on this list, it has to be assumed that the list is incomplete for obvious reasons.Also Lars Gunnar Nyström informed the Swedish Commission that he had made many trips on the ESTONIA. In February and March 1994 he was on board when ESTONIA was forcing ice twice and arrived in Tallinn once with a delay of 1.5 hours.
The damage sustained by the visor while proceeding at full speed through ice barriers several meters high and using the vessel as an ice breaker is demonstrated by the preceding photo and can also be seen on the video image below made from a film of 30.03.94.
As a result of the sustained severe structural damages and in combination with the different lifting speeds of the actuators and severely worn out hinge bushings, the visor became increasingly misaligned and out of geometry.
All of this led to problems - observed and reported by passengers as described in Subchapter 12.4 - during the opening and closing which also affected the locking devices and reportedly the problems became worse and took more time to be overcome the nearer the day of ESTONIA's last departure came. This is demonstrated by the following examples:
Note: Rapid closing of the visor is only possible by opening the hydraulic valves at the actuators (hydraulic lifting cylinders) manually. Thereafter the simultaneous movements of the cylinders has to be readjusted by service engineers.
It had also been frequently observed that the lugs of the hydraulic side locks were cut off by burning and subsequently rewelded, which is confirmed by the following observations:
3. The Bow Ramp was the upper extension of the collision bulkhead above bulkhead deck and as such had to be mandatorily weathertight. Therefore the ramp required regular maintenance of the rubber packings, the hinge arrange-ment and the locking devices.
As stated before 10 m of the rubber packings should have been renewed already during the yard time in January 1993, however, this was never done up to the casualty.
The same refers to the locking devices of the bow ramp which should have been serviced and strengthened already in January 1993, which was also never done.
Whilst damaged and missing rubber packings cause a bow ramp which is otherwise in proper condition to leak, this becomes much worse if the bow ramp is visibly misaligned and twisted.
This had been the case on ESTONIA for several months before the casualty and the condition deteriorated as time went by. It is a fact that water was penetrating the bow ramp already in 1993 according to the evidence of passengers and pilots. In particular the statement of the Stockholm pilot Bo Söderman - see Enclosure <IP_ADDRESS> - is striking.The following drawing clearly demonstrates that already in calm sea the water rose above the 3rd stringer inside the also severely leaking visor due to the height of the bow wave at full speed.
Since the lower part of the deck opening with the missing and/or damaged rubber packings (see arrow on drawing) was below the 3rd stringer level of the closed visor, it is obvious that water penetrated the car deck already in calm sea when the vessel was on full speed (height of bow wave ca. 2.5 m). It is also obvious that the water inside the visor rose when the vessel was pitching in head seas. The height of the water inside the visor depended on the height of the outside water level, i.e. when the ferry was taking green water on the forecastle for a certain time the visor would fill up more or less completely with respective water pressure on the leakage of the bow ramp.
Since absolutely nothing had been done to improve the condition of the rubber packings and also no maintenance to the bow ramp had taken place since the vessel was put under Estonian flag, also the condition of the ramp hinges, in particular the port outer one, deteriorated continuously. This process was being sped up by the wrong loading of the car deck through the also apparently in this respect rather inexperienced Estonian officers, because the vessel frequently had a list during loading/unloading when the heavy trucks were rolling on/off board via the bow ramp and the effect on the already pre-damaged and weakened hinges of the bow ramp was disastrous. This finally led to the complete destruction of the port outer hinge and the breaking of the inner lug connecting the ramp to the vessel, whilst the outer lug slid off the hinge bolt apparently after the securing plate was broken off. The result is explained by a truck driver who witnessed this incident as follows:
»I drove on board as one of the last trucks and after leaving my truck I saw that the crew tried to close the bow ramp, which was not possible because only the starboard side came up while the port side remained down. Only after several ups and downs of the ramp and some other things done by the crew did they finally manage to close the ramp. Ever since then the ramp was visibly twisted and when the visor opened and the bow ramp was still "closed", light fell in through the upper left corner.«
The above is based on a telephone conversation in December 1997. It has not yet been possible to take the statement of the truck driver.
This severe damage to the port outer hinge and to the ramp itself was reported by the crew to the technical managers and also put on the repair list several times according to Börje Stenström (see Enclosure 12.5.166). However, nothing was done to rectify this damage despite the fact that it constituted a severe violation of the SOLAS - and Class - requirements because evidently the open car deck was, via the leaking bow ramp, connected to the visor which at sea was filled with water.
As no maintenance took place the crew tried to seal the leaks as best they could by putting mattresses, blankets and rags into the openings between the ramp and car deck/bulkhead at the port lower corner. As a further consequence of the detached port lower side of the bow ramp the port lower securing bolt no longer fitted into the ramp pocket, whilst the upper port bolt fitted only to a limited extent and it is doubtful whether the port ramp hook was able to engage the lug at the ramp side at all.
These very severe deficiencies led to continuous problems for the crew when opening and closing the bow ramp and/or the locking devices which had been observed by many passengers, in particular by the truck drivers using the ferry twice a week or more as summarised in Chapter 12.4. These observations prove that the bow ramp as well as its locking devices had been in a very poor state of maintenance and that they no more fulfilled the SOLAS and the Class requirements.
Only since the files of the Swedish part of the JAIC and the files of the Stockholm prosecutor, Tomas Lindstrand, have to a large extent, though not completely, been opened to the public, has more background information become available, which shall be introduced as follows:
(1) Memo in one of the files of the prosecutor concerning director S.-C. Forsberg's phone call to the office of the prosecutor on the day of the catastrophe, 28 September 1994, at 14.00 hours.
(2) Explanatory letter written by S.-C. Forsberg to the Stockholm police on 01.11.1994.
(3) Statement of Inspector Ulf Hobro taken by the Stockholm police.
(4) Telephone interview of Tomas Ramusson, Hornet AB by the Stockholm police according to a transcript in the prosecutor's file.
(5) Statement of Lennart Klevberg, N&T, taken by the public prosecutor on 24.06.1996.
(6) Statements of some of the surviving crew members and of the member of a previous working team on board the ESTONIA.
The statements of
- Sten-Christer Forsberg /N&T
- Ulf Hobro /N&T
- Tomas Rasmusson /Hornet AB
- Karl Karell /Hornet ABtaken by the Swedish part of the JAIC had been classified until publication of the Final Report of the JAIC, but are now only available on tape in Swedish, thus cannot be evaluated in this report.
as to (1): (Phone call Forsberg)
According to a memo in the files of the prosecutor, S.-C. Forsberg had reported the following by telephone at 14.00 hours on the day of the casualty, the 28 September 1994:"There are rumours going around town that burning and welding work has been carried out to the visor of the "Estonia". The owners do not know anything about this. It is, however, possible that the observations refer to de-icing of the visor in winter by means of burners."
Note:
In this connection reference is made to the evidence of passenger Anders who had observed in Stockholm welding being done underneath the partly open bow ramp at the Atlantic lock and of passenger Christer Eriksson who had observed burning and welding of the visor in Tallinn in May 1994 which took a full working day (see Enclosure 12.5.169).
as to (2): (Letter Forsberg)
The letter dated 01.11.94 written by S.-C. Forsberg to the criminal police Stockholm shall be quoted and discussed. The complete letter in Swedish together with the office translation is attached as Enclosure 5.2.110.
Sten-Christer Forsberg
- Manager of the Shipping Department of N&T
- Technical Director of N&T
- Board member of Estline AB
(CV see Enclosure 5.2.108)a graduated naval architect of Chalmers University, Gothenburg, ex colleague of Börje Stenström, member of the JAIC, and Kaj Janérus - then managing director of Sjöfartsverket - from a mutual employment with Salén Shipping Company, Stockholm was directly responsible for the technical condition and performance of the ESTONIA and explains as follows:
»Technical Supervision of the Vessel
N&T's shipping department was responsible for the technical supervision of the vessel. Under the manager of the shipping department, Sten-Christer Forsberg, Ulf Hobro was the inspector/ superintendent of the vessel for the whole time and spent a large part of his working time on MV "Estonia". Hobro checked the condition of the vessel regularly regardless of what the master, chief officer and chief engineer did.
Tomas Rasmusson, who is one of N&T's own chief engineers, assisted the N&T operations organisation with the preparation work for ca. 2 months before take-over of the vessel and also during the following months he helped the Estonian chief engineer to update the vessel's computer based maintenance program including establishing the part of N&T's organisation concerning supervision of handling and maintenance of the engine plant.
Lennart Klevberg, employed by N&T's organisation as the purchaser, was located at the Estline Terminal in Stockholm the whole time and was responsible for negotiating and purchasing spare parts, lashing material, and other technical equipment and consumables for MV "Estonia".«Note: According to von Tell GmbH, Hamburg the only spare part ordered by N&T in 20 months for ESTONIA was one new ice cylinder for the visor.
»To assist the chief engineer in steering, controlling, and documenting the technical maintenance of the engineer on board there was the administrative data system/program (AMOS-D) available. The system delivered information concerning particular maintenance items to be dealt with and the system registered remarkable details. The system included the recommendations of the manufacturers as well as the requirements of the Classification Society and modified continuously the gained operation experience.«
Note: Forsberg does not mention the 'Öberg-Data-System' which was installed on board and ashore and by which, among other things, repair lists respectively working lists were printed and monitored. Also the distribution of working lists is not explained,
i.e. - original to repair firm
- yellow copy to N&T
- Technical Dept.
- green and blue copies for ship's file.Note: Contrary to his earlier statements that he had received a copy of the repair list concerning the damaged bow ramp hinge from N&T, Börje Stenström later said that according to N&T all copies had remained on board. Even if it should be true, which is very doubtful because it is neither common practice nor does it make practical sense, the original went ashore to N&T and must be available.
The letter continues:
»MV "Estonia" was taken over from her previous owners at the ship-yard in Turku, there the Estonian crew took possession of the vessel, the on-board organisation was established and the necessary work to adjust the vessel to Estline's traffic was carried out. Finnish speaking personnel from the previous owners Wasa Line (chief officer, 1st engineer, electrician and two repairmen) were hired from the start of the new traffic for between 21/2 and 5 months to assist their Estonian successors with practical advice in dealing with vessel's specific systems. This principle was always followed by the operations organisation of N&T when taking over vessels, independently of flag or nationality of crew. ...
Earlier supervision of the vessel by maritime authorities and Classification Society had been carried out by B.V. in Finland, however, since the technical supervision of the vessel was to be dealt with by N&T Stockholm, N&T demanded that the vessel in this respect should be moved to B.V. in Sweden. Thereafter mainly the inspector Anders Wirstam of B.V.'s Stockholm office carried out the on-board inspection. ...
In connection with an education program for Estonian ship inspector aspirants chief inspector Åke Sjöblom and 1st ship inspector Gunnar Zahlée from the Sjöfartsverket Inspection Office Malmö carried out an inspection on board the "Estonia" in the afternoon and evening of the 27 September 1994. Thereby no noteworthy deficiencies in relation to vessel's seaworthiness and safety at sea were discovered.«Note: In this connection see also Chapter 15, but - in particular - it has to be borne in mind that - according to sources from inside Sjöfartsverket - Åke Sjöblom and Gunnar Zahlée very well noted the obvious deficiencies of the bow ramp and demanded rectification before the ferry should be allowed to sail on 27.09.94. This was rejected by the Estonian authorities - their trainees - whereupon the managing director of Sjöfartsverket, Kaj Janérus, was phoned and asked what should be done. The managing director reportedly referred them to the Estonian authorities who did nothing and the ferry sailed into the catastrophe.
as to (3): (Statement Hobro)
Ulf Hobro - CV see Enclosure 5.2.109:
»Marine engineer with 20 years experience at sea, whereof 12 years as chief engineer; has also worked as safety inspector for Sjöfartsverket for several years; employed as a technical inspector with Nordström & Thulin AB, had been responsible for "Estonia's" running maintenance, budget and finances. His office is at Skepsbronn in the old city of Stockholm. Has been engaged in "Estonia" since the plan to purchase the vessel arose, inspected the vessel before she was bought. His duty was to investigate the vessel and the vessel's general condition and to control the certificates required for the vessel. When visiting the vessel he discussed possible defects, damages, etc. with master and chief engineer on board. Defects were generally repaired by the crew, but often spare parts had to be ordered and this was dealt with by Lennart Klevberg in charge of the purchase of spare parts. In case of considerable damage special firms were engaged for the repair.
Hobro was assisted by Tomas Rasmusson who had his office at the Estline Terminal and was working as assistant inspector. He was on board the vessel to and from Tallinn on several occasions and he was the contact person between the Master and Hobro. Rasmusson was in daily contact with the vessel.
Hobro stated that since the vessel started her service in January 1993, there have been no remarks on the bow visor. There may possibly have been some hydraulic leakages on some piston. No defect, however, has been brought to Hobro's knowledge. In case of any extensive defect to the bow visor, this would have been reported to Bureau Veritas.«The statement was taken by the Stockholm police on 22.11.94 and is attached as Enclosure 12.5.171.
In addition, this 'Group of Experts' had the opportunity to ask Ulf Hobro questions in the presence of JAIC on 17.02.95 in Stockholm, which revealed the following:
- With the exception of the unscheduled drydockings due to the leaking stern tube seals in March and April 1993, the vessel under the management of N&T was only once at the Yard and in drydock, i.e. in January 1994 in Turku, when the stabilisers were installed and the ice paint was touched up the last time.
- At that time the B.V. surveyor Anders Wirstam carried out a Load Line Survey, which normally should have included the rubber packings of the visor.Note: At that time Ulf Hobro knew very well from the specification of the previous crew that they had asked for a renewal of 15 m of rubber packing in way of the visor, which was never carried out.
- This was said to be the last time that Ulf Hobro had been inside the closed visor near the Atlantic lock. There were smaller leakages of the hydraulic cylinders of the Atlantic lock and the side locks as well as the bow ramp, which were said to be normal according to him. Larger hydraulic oil leakages inside the visor were said to be unknown to the Inspection Department of N&T.
Note: The picture on the next page was taken in October 1993 and shows the lower part of the closed bow ramp severely stained by oil, most probably hydraulic oil, which cannot just be explained by normal leakages.
- During the time between the take-over in January 1993 and the sinking on 28.09.94 no rubber packings had been renewed in way of the visor.  asked Ulf Hobro. "It was known to everybody that the visor was anyway full of water at sea and this was also the explanation for the white paint washed off in the area below the 3rd stringer."
- Upon being confronted with the photos showing the severely oil-stained 3rd stringer with rather fresh footprints Ulf Hobro stated that to be normal due to the crew carrying out maintenance work, but he did not state what was maintained.
- According to his knowledge there had never been problems, neither with the Atlantic lock nor with the side locks.
- Upon being confronted with the empty sensor plate of the Atlantic lock he reacted with surprise and then drew attention to the changed system on board of MARE BALTICUM (where the sensors had been mounted higher up above the normal water level). He promised to clarify this with the electrician having survived, who was now serving on board of MARE BALTICUM.Note: The sensor plate of the Atlantic lock - see explanations in Chapter 2.6.2 - page 117 ff. - was noted to be empty, i.e. without sensors, on all the underwater videos, moreover the cables leading to the sensors were evidently cut. These facts were presented to Ulf Hobro, who apparently subsequently spoke to ESCO and the result was the 'Explanatory Note' with sketch dated 23.02.95 which was submitted shortly afterwards to JAIC. The note states "that contrary to the von Tell drawing 49111-373 showing mechanical sensors, there were installed 'magnetic sensitive elements' when the vessel was taken over, which were not replaced, but just the distance was regulated and the indication checked. It is assumed that these 'sensitive elements' had already been installed during newbuilding as the same type can also be found on various other installations, such as lifeboats, lifts, car deck platforms, etc."
The note does not state that the 'sensitive elements' were still in position on the last voyage nor does it give any explanation for the empty sensor plate.
Underneath the text the following names are listed without any signature:
| the chief engineer of the other crew | H. Moosaar |
| the electric engineer of the other crew | M. Doronjuk |
| the electrician of the other crew | D. Salomon |
| the electrician, who survived | A. Rohumaa |
| the boatswain of the other crew | H. Leik |
The 'Explanatory Note' is attached as Enclosure 12.5.172.
- The proof for the empty sensor plate was also submitted to B.V. and a retrospective class withdrawal was suggested by this 'Group of Experts'. This resulted in respective questions by B.V. to N&T which forced N&T to examine the matter quite closely. The result is summarised in the letter of N&T to Börje Stenström dated 15.11.95 with enclosures - all of which are attached - with office translations - as Enclosure 12.5.173.
- Part of the enclosures to the above-mentioned letter is a "Memorandum concerning a meeting on board MARE BALTICUM on 6 November 1995 in Tallinn". At this meeting the three electricians and the boatswain of the Piht crew - Heino Leik - were questioned in respect of the following subjects.
It is revealed in this memorandum that the crew experienced problems with the magnetic switches between the spring of 1994 and September 1994 to the effect that the green light did not go on if the bolt was closed. The problem was said to be solved by a simple adjustment of the magnetic switch. These problems were mentioned already by Henrik Sillaste and Tanel Moosaar during the interview on 10.03.95 in Stockholm see Enclosure 12.5.174.
According to information received by one of the Finnish engineers from one of the Estonian engineers shortly after the casualty the magnetic switches had actually been destroyed by ice hacking already in February/March 1994 and were not replaced, because crew members had to go down anyway to hammer close and open the bolt of the Atlantic lock - see statement Arvi Myyryläinen Enclosure 12.5.175 - and therefore it was decided not to renew the switches for the time being.
- Stabilisers were installed into pockets already arranged at newbuilding with respective electrical connections. The installation - according to Hobro - became necessary after less than one year in service to be able to compete also in this respect with the Helsinki ferries from Silja and Viking.Note:
-As a matter of fact, Hobro had asked the Turku Repair Yard already in April 1993 to quote for the installation of stabilisers, i.e. after less than 3 months in service the management had to realise that the vessel was now trading in a completely different sea area with a much rougher sea state. The quotation is attached as Enclosure 12.3.143.
- Hobro did not say a word about the fire in way of the starboard stabiliser pocket at the time of installation of the stabilisers in the drydock of Naantali which - according to Henrik Sillaste - had caused damage and had cut the short time planned for installation of the stabilisers at the shipyard even shorter. Reportedly the required careful welding work to install the starboard stabiliser therefore could not be carried out as it otherwise would and should have been the case.
- The damaged parts of the "Inerta" ice paint in way of the bootop strake including the lower part of the visor with stempost were touched up.
as to (4):
Tomas Rasmusson: (Telephone Interview)- He had been on board WASA KING already to become acquainted with the vessel.
- His boss was Ulf Hobro
- he was between Hobro and the crew.
- He took part in the work in connection with changing flag to Estonia, lots of translations and the like.
- Everything functioned well between N&T/crew.
- His job was more social. He had no direct responsibilities.
- He carried out his own inspections and controls.
- He was also the contact between the crew and the spare parts handler Lennart Klevberg.
- At the beginning he was on board in 14-day periods, he and Anders Andersson relieved each other.
- Later he was more shore based and made one trip per week.
- He worked mainly with engine matters, Hobro and Kleberg.
- Everything was perfect. The crew never drank alcohol. The crew was ambitious and good. No incidents or problems whatsoever.
- ESTONIA was in very good condition. Deficiencies were rectified at once. Everything was listed by the data system AMOS-D. Each month a list was printed which showed what had been done and what had to be done. In case the chief engineer had done nothing, he was instructed by Hobro or himself what to do.
- He did not know if and how the visor was controlled. He never heard anything.The above are notes made when sighting the files in the office of the prosecutor in Stockholm. A photocopy of the transcript is attached as Enclosure 12.5.176.
as to (5):
Lennart Klevberg: (Statement)- He was frequently on board the ESTONIA.
- He ordered the hydraulic parts and valves for the visor and bow ramp.
- He had ordered rubber packings for the visor which were to be delivered together with the packings for MARE BALTICUM.
- Capt. Andresson and Tomas Rasmusson had told him to wait with the delivery of the new rubber packings until MARE BALTICUM would be taken over and then have it done for both ships at the same time.Note:
Hobro stated that no rubber packings were ordered, nor was it their intention ever to order them.
Rasmusson stated not to have direct responsibility, however, he was the contact between the spare-parts man Lennart Klevberg and the crew, on the other hand he testified that he did not know if and how the visor was controlled and that he never heard anything in this respect.
Kleberg, however, testified that he had been told by Capt. Andresson and T. Rasmusson that he should wait with the delivery of the rubber packings for the visor of ESTONIA until MARE BALTICUM had been over.
as to (6): (Statements of some of the surviving crew members and the member of a working team)
a.) The member of the working team and then student at the Nautical Academy Tallinn, Rain Oolmets, has testified respectively had been interviewed three times about his observation on board and the respective statements/transcripts are attached as follows:
- Statement Rain Oolmets to the security police Tallinn on 03.10.94, Enclosure 12.5.177.
- Statement Rain Oolmets taken by JAIC at Hangö on 24.03.1995, Enclosure 12.5.178.
- Transcript of the interview of Rain Oolmets in April 1996, Enclosure 12.5.179. The interview is also available on video tape.
Rain Oolmets worked on board ESTONIA from 11 July to 11 September 1994.
The relevant parts of the testimonies shall be quoted as follows:
»I'm not quite certain of the exact date, but one afternoon after half past four I was busy with painting the bow visor on the deck. As the bow is in raised position only in Tallinn, I was painting the part that was otherwise not visible. Before painting I had also polished and primed the visor. While painting, I once again could not help noticing the cracks in the bow visor fastenings, which were the result of the fatigue of metal. When repainting the bow visor, I noticed them too. The cracks were visible only with the bow in raised position. The starboard side fastening mechanism/box of the visor had a crack of nearly 10 cm in length. The port side one had a 6 cm long crack. There was also a crack in the welding between the bow visor and the fastening beam, which was about 2 cm long. I am prepared to show the location of the cracks on drawings.«
Q: When were observations made of cracks in the visor of "Estonia"?
A: I observed them while painting on the bow deck of the "Estonia" in early August 1994. Painting was done in the port of Tallinn.
Q: In what position was the visor when you were working?
A: The visor was open, otherwise we could not have seen the cracks.
Q: What colours did you paint?
A: Both green and white (i.e. both the deck surface and areas rising from the deck).
Q: Can you show on the visor where the cracks were?
A: Those parts have been removed, this is why I cannot show the crack locations. (Upon instructions of Börje Stenström the hinge remains had been removed for metallographic investigations and mechanical testing already in January, that is why the crack locations could not be demonstrated.)
Q: Could you indicate on these sketches where the cracks were?
A: You have to look from forward to aft at the hinges to be able to see the cracks in the welding seams between the bushings and the hinge plates of the visor hinges (hinges at the visor). The cracks were opposite to the deck when the visor was closed. At the starboard hinge there were cracks in both welds. At port side there was only one crack in the weld. The drawing below shows the location and approximate length of the cracks.
The cracks were less then 10 cm long. (Reference is made to the statement taken by the Estonian police on 03.10.1994).
Q: Could you tell us a bit more in detail about the paint work and the damage to the visor?
A: Actually the damage could only be seen when the visor was open. There were very many. On a drawing one could see that more in detail. Actually at one side there were these cracks. Possibly as a result of mechanical action.
Q: You said on one side the crack was 10 cm long and on the other side about 6 cm long? This is written in your statement.
A: This might have been so.
Q: Quite sometime has passed but I assume that you are not going to withdraw your written statement?
A: No.
A: I did not inform the boatswain about my observations. It was the time when the cars were rolling on board. And the boatswain ... you had to work with him. He did observe exactly. He disliked it if somebody did not work during his working time. Then I did not get a chance to tell him. I was actually of the opinion that it was known anyway. Therefore I forgot to report it.
Q: What was the condition of the visor when you started to work?
A: I did not have specific instructions to do something at a particular location. During my work I was climbing everywhere, cleaned and painted. This location was difficult to reach. Presumably the last time this area had been painted was when the vessel was painted white for the first time. I thought that certainly somebody from the administration knew about the cracks because the vessel was checked quite often. Also the boatswain checked our work. Therefore I believe that certainly somebody knew of the cracks.
Q: Thus you were convinced that due to the frequent checks that somebody knew about the condition of the visor and also of the cracks?
A: Yes, I was sure that they knew it.
Q: Did the crack appear only after you had removed the paint?
A: No, the crack was visible already before.
Q: It was consequently enough to climb there to see the crack?
A: Yes.The complete interview is attached as Enclosure 12.5.179.
In summary of these three statements it has to be concluded that the welding seams between the bushings and hinge plates of the visor hinges were visibly cracked up to 10 cm at the beginning of August 1994, less than 8 weeks before the casualty.
The photo below shows a part cut out of the bushing recovered by divers from the wreck. It is most probably the starboard inner bushing as will be explained in Chapter 30.
photo of stb. inner bushing recovered by divers
For a better understanding, the relevant parts have been numbered as follows:
1 = steel bushing
2 = hinge plate
3 = area between hinge plate/bushing
4 = welding material
5 = arrow pointing to the large gap between bushing and hinge plate
6 = welding seams between bushing/hinge plateWithout going too much into detail, already now attention has to be drawn to some very obvious irregularities, viz.
- The bushing had been too small for the bore of the hinge plate (2), therefore a gap (5) remained between bushing and inner surface of the hinge plate.
- The welding seams (6) are rather weak compared to the dimension of hinge plate and bushing.
- There had obviously been a crack at the left side in the welding seam (4) which had been tried to be closed by welding. This led to the accumulation of welding material inside the gap between bushing / hinge plate.
- The surface area between hinge plate/bushing (3) is severely corroded which would not have been possible if the inside had been airtight by intact welding seams. In other words, the apparent fact that the space between bushing/hinge plate could be attacked by corrosion as found is proof that the welding seams had been cracked over the full thickness for a longer time already.b.) That there was something seriously wrong at least with the starboard hinge arrangement of the visor well before the casualty becomes very obvious when having a close look at the video film made by a passenger upon departure from Tallinn on 17 September 1994, i.e. 10 days before ESTONIA's last sailing. He stood on the open forepart of the 8th deck and with his video camera filmed the closing of the visor. Thereby he zoomed in on the starboard hinge arrangement. The subsequent evaluation of the video proved that the starboard visor hinges were totally misaligned with the lower part of the outer bushing as well as the securing plate missing. The video was analysed and evaluated in detail by the Reconnaissance Expert Bryan Roberts of Churchgate/UK and his report is attached as Enclosure 12.5.180.
The print is shown below and the enlargement is attached as Enclosure 12.5.181.
Although the distortion and misalignment of the starboard hinge is clearly visible to everybody, the Swedish part of JAIC gave a copy of the film to the Military Intelligence Service, who produced the picture attached as Enclosure <IP_ADDRESS>, which evidently shows the same. Nevertheless, the Intelligence people declared the whole film to be unreliable since 5 out of about 800 sequences had been slightly "jumping", which was accepted by the JAIC as well as N&T and the film from then on was ignored by the JAIC and consequently is also not mentioned in their Report. What the film really shows becomes clear on the enlargement below, viz. some major deficiencies:
- the gap between the starboard vessel hinge plate and the outer bushing is much too large (Arrow 1).
- the outer bushing is sticking much too far out of the outer visor hinge plate (Arrow 2) (which explains the large gap mentioned above).
- the lower part of outer bushing is missing.
- the securing plate is missing and the outer end of the bolt is not visible.
- the outer bushing appears to be twisted anti-clockwise.
- the inner bushing appears to be twisted anti-clockwise.Bearing in mind that the nautical student Rain Oolmets reported the cracks observed at the beginning of August 1994 immediately after he had learned of the casualty to his uncle, who was then sailing as chief officer for ESCO, and the uncle went to the police who subsequently interrogated the student on 03.10.94, it is difficult to believe that Rain Oolmets had remained silent on the real damage to the starboard hinge, had it been there already.
On the other hand, he had told Klaus Rahka during the questioning at Hangö on 24.03.95 that he had painted the visor hinges green and white and - as clearly visible on the video image on the following page showing the starboard hinge bolt - there is quite a lot of green paint on the bolt which could not possibly have got there as long as the hinges were in their original, intact condition because then it was practically a closed system, i.e. paint could not reach the bolt. The intact system has no gap as can be seen from the drawing below showing the intact starboard hinge arrangement.
As it is, however, obvious from the video print below, showing the starboard bolt - without bushing - resting on the rail bar, there is a stripe of green paint at the bolt. Measurements reveal that the paint is in way of the gap between the outer bushing and the vessel hinge plate which is visible on the enlarged video print on the previous page (Arrow 1).
Therefore it has to be concluded that the gap must have been there already when the green paint was applied, however, this will be evaluated more in detail in Chapter 29/30.
Oolmets commenced his job mid July 1994 and left the vessel on the 11 September 1994. He had discovered up to 10 cm long cracks in the weldings between bushings and visor hinge plates both at port side and starboard side of the visor hinges when the visor was open. This was in early August, at a time after 16.30 hours when the loading of the trucks had already commenced. The boatswain then on board was Vello Ruben, thus it was the Andresson crew. Considering the fact that the Andresson and Piht crews relieved each other every 14 days, further that the Andresson crew would have been relieved on the 29.09.94, thus came on board on 15 September 1994, going back from that date in 14-day intervals, it becomes obvious that the early August time for the Andresson crew with Vello Ruben as boatswain ended on 4 August 1994 in Tallinn. As on that day the crews would change in the morning, the loading of the trucks after 16.30 hrs was already attended by the boatswain of the relief crew, Heino Leik. As on the day before, 3 August 1994, the vessel had been in Stockholm, it has to be concluded that Rain Oolmets found the cracks on 2 August 1994 as this is the only day in early August when Vello Ruben was on the car deck after 16.30 hours. The Andresson crew returned on 18 August 1994, but this date or later would hardly be considered early August by Rain Oolmets. On 11 September 1994 he left the vessel (see time schedule of crew change - Enclosure 12.5.182).
If he had finished painting the starboard hinges, which has to be assumed as he stayed on board for another 6 weeks after discovery of the cracks in early August, there must have been quite a gap between the inside of the outer visor hinge plate and the outside of the outer hinge plate at the vessel's side, as otherwise it would not have been possible for such green deck paint to reach the bolt.
This could indicate that the repairs to the starboard hinges of the visor had already been carried out when Rain Oolmets discovered the reported cracks on 2 August 1994. It would, of course, mean that he told the criminal police as well as JAIC only part of the truth, which would not be surprising.
c.) According to the statement of 2nd engineer Peeter Tüür he was also responsible for all watertight (weathertight) openings of the vessel, their maintenance and proper functioning. In his statement taken on 3 October 1994 by the Estonian security police in Tallinn - see Enclosure 12.5.183 - Peeter Tüür, who is the highest ranking officer to have survived, has testified:
»I am the 2nd Engineer. Each engineer has his tasks. Part of my tasks were the watertight openings and to keep the technical functioning in order. It was also my responsibility to see that the visor was in order, but I was specifically responsible for the hydraulic of the visor. The closing of the visor was carried out by the boatswain, however, I am unaware who was directly responsible for the closing, possibly the mate. Behind the visor is the ramp. This should also be hermetically tight, there are just a few places where the ramp does not close hermetically. The visor is closed hydraulically and securing wedges fix the visor in closed condition. There are 5 fixing points.«
This statement of Peeter Tüür is in many respects of great importance, because he has stated that
Further it shall be mentioned that N&T supplied the JAIC with the 47-paged "List of Maintenance and Repairs Works on M.V. 'Estonia', April 1993 - August 1994", which is drawn up in a rather peculiar way and is signed by the chief engineers Moosaar and Leiger. The list contains for example many repairs to dish washing and slicing machines in the galley as well as the cleaning of search lights, ventilation pipes, etc., however neither bow ramp nor visor are mentioned at all, although the crew and external repairmen did a lot of burning and welding and other maintenance work.
The only 10 items of interest on the 47 pages of the above-mentioned list have been summarised and are attached as Enclosure 12.5.184.
Finally, the transcript of the interview of Sten-Christer Forsberg (SCF) by Erik Ridderstolpe (ER) from Swedish Radio in December 1997 after publication of the Joint Accident Investigation Commission's Report shall be quoted. The transcript was also found in the files of the prosecutor and is attached as Enclosure 12.5.185.
After Forsberg had admitted that N&T was responsible for the condition of the ferry upon departure from Tallinn, he was confronted with the last repair list of the Finnish crew by Ridderstolpe and the following Q/A developed:SCF: I have seen this repair list for the first time in the Final Report of the Commission.
ER: And you did not receive any information in this respect beforehand?
SCF: No, it was not available to us.Note: This is wrong. The repair list - Enclosure 3.4.96 - and the yard quotation - Enclosure 3.4.97 - were handed over during the yard time in January 1993 from Wasa Line to N&T. N&T did subsequently order some of the items which were carried out by the yard. The subsequent yard invoice - Enclosure 3.4.103 - issued to N&T contains only the reference nos. of the repair list without any text. Thus N&T could interpret and understand these items only by means of the repair list.
ER: Silja had a maintenance contract with MacGregor concerning rubber packings, locking devices, etc. which you cancelled immediately.
SCF: We did have the time and capacities to do everything in port ourselves. The acting of the previous owners was more directed by short stays in port and lack of capacities.
ER: The vessel had a wrong PSSC.
SCF: The wrong construction of the vessel since newbuilding is mainly to be blamed for the casualty, not so much the wrongly issued certificate.
ER: The vessel was loaded totally wrong in Tallinn.
SCF: The wrong loading is regrettable. It would, however, also have been done by any other crew.
ER: The safety equipment did not comply with the regulations.
SCF: The bad and overaged safety equipment was accepted by Sjöfartsverket, otherwise we would have renewed everything.
ER: In my opinion N&T acted with gross negligence.
SCF: I cannot accept this, but insist to the contrary that we had a very well maintained and very well managed ship, which had been seaworthy in every respect. If anybody is of a different opinion and is able to prove it on basis of the now available report, then he is welcome do so.«In the following chapters the condition of the "very well maintained" and "very well managed" vessel which was "in every respect seaworthy" upon her last departure from Tallinn shall be presented.


| DOSE: T+ 0:00 |
150 seeds |
oral |
Datura |
(seeds) |
| T+ 18:00 |
450 seeds |
oral |
Datura |
(seeds) |
Its October 10th, 2 days before my 15th birthday.  I say no as he proceeds to tell me about his experience with them. He said he injested one pod, about 100-200 seeds. He tells me he was on his way to his best friends house and he walked into the neibours house instead without even noticing. He walked to the fridge and poured a glass of milk then drank it, suddenly an old lady walks in and screams 'What are you doing in my house?' He frantically runs out of her house an to the right house. Then he tells me he did them the next day and did the exact same thing to the same house. Being the kind of person who will try almost anything once to find out what it does to me, I instantly was interested in trying this drug and asked what they looked like and how many I should do. He said to eat no more than one whole pod.
I told 2 of my friends about these things and what they did to Dave. My friend Steve said he heard of them and know where one is growing. Me, Shawn and Steve start walking toward where they were. I was a little nervous since Iíve never heard of this before but was still eager to try them. We picked a single pod off and decided to get our other friend Stuters (Shayne) to come along. We sat there and told him about them and he wanted to be the first to try them. So we cut open the pod and he injested every last beat red seed, chewed, and swallowed. We went back to Stuters house and about half hour later he slured the words 'I feel a bit drunk' and told us to go eat some.
Knowing they were for real and did get you high we went back to the plant and raided it. We took 3 more pods and each ate one. We decided to walk down town. About an hour later I felt very hot and uncomfortable. I remeber Steve saying he was going home to see his girl. Me, Shawn, and Stuters were on Stuters front porch. Stuters said he was going to be right back, then I remember waking up on his front porch by myself and it was dark out by now. Confused, I got up and walked home. On the way I kept looking over and seeing all my friends I did them with. I was talking to them and smokin a spliff with them. I turned again and they were gone. I got real confused as too why they kept running off on me, it made me pretty mad too. I donít remember getting home or much after that at all. My mom told me the rest.
 She said I sat down at the computer table without a single word and started moving my hands as I were rolling a joint, then lit it up and passed it around. I was talking to Shawn and Stuters about selling these things she said.  'No your not,' she said, 'Your on somthing harder.í And I argued with her 'No Iíve just been chillin with Shawn and Shayne smokiin weed, ask them!' She looks at me and yells 'Thereís noone fuckin there!' I turned and looked beside me with a confused look on my face and said 'Oh. theyíll be right back.'
She still didnít know what I was on because I simply didnít remember, all I knew was I was chillin wit my friends. She said over the next 7 hours I kept smoking cigarettes that werenít there and thinking I was burning myself. My step dad stayed up all night on the computer watching me since I wouldnít stay still or sleep. He told my at about 4 in the morning I got up off the couch and walked towards the table. It was pitch black so he couldnít see what I was doing. He said I was moving things around on the table so he told me to sit back down on the couch, so I did. He noticed I had somthing in my hands, looking at it, fliping it around and about 5 minutes later he heard me say, 'Is this the fuckin lid to the butter?í So he stands up and turns on the light. There I was sitting on the couch with the lid to our glass butter holder.
My parents said they got a huge kick out of me, they said I was like a 10 year old kid with a 10 second memory span. Another incident my moma told me about was that I went to the bathroom an I was in there for like 10 minutes before I came out struting my stuff buck naked in the hallway. She turned to her boyfriend and asked 'What do I do?' and he said I donít know Iím not touchin him, so they told me to get dressed and it took quite a while for me to come out and when I did I had my momas pants around my head so they had to get me dressed themselves which I later apologised to them.
It was a school night so my moma said I should stay home while they went to work. In the morning I was still pretty high but I remembered what I did by then. I went to my friend Joe's house and told him all about it and we decided he wasnít gunna go to school either and he was gunna do some seeds with me. We were gunna sell them to kids and make some money too so we went to the plant and grabed like 20 pods.
We got there and cut open all the pods and put them in bagies. We figured not many people would buy them so we ate another 3 pods each.  I instantly got paranoid since I just ate 4 more pods.
I only remember about 10% of the whole time but Shawn wanted to stay sober to see what we do because he didnít remember the night before which was good because we probly wouldnít be here if he did them too. He first noticed Joe was trippin out because he asked Shawn who the lady suntaning in his back yard was. Shawn seen there was no one there and said it was his momís friend. His mom was coming home soon so he walked up to Joeís house. On the way he said he knew I was high now too because I was chewing on my shirt like it was food, he said I looked at him and with the funniest expression on my face I said to him with my shirt in my hands, 'Sosage???' he just laughed and said ĎNo, its ok Jamie.í
When we got to Joeís he was having a hard time watching us since Joe was in his house and I was all over the place, in his back yard, his basement and walkin down his street. He came out back once and seen me smoking somthing and passing it to people who werenít there. He started playing with me a bit asking if he can have some and I was like ĎNo! Your cut you fucker!í He just laughed and went back inside. When he got in there Joe was in his bathroom slicking his hair back with hair gel. Shawn didnít say anything to him, just watched to see what he was doing. Joe got out of the bathroom and sat on his couch.  Shawn told me he actually fell to the ground laughing.
The whole time this was going on I had 1 hit of ecstacy that I was saving for my birthday in a dime bag, Shawn said he kept asking to see it and make sure I still had it, I pulled it out a few times and showed him then he said that one time I pulled out the baggie and it was empty, he started getting paranoid and kept saying 'Whereís the pill? Where is it?' I had no idea what he was talking about and we still donít know to this day if I ate it or not.
About 5 hours of him babysitting us he was getting frustrated and decided to bring me home. He told my mom Shayne was in the hospital and she and him brought me there, Joeís dad came home and found him talking to a telephone pole. My moma told Joeís dad to bring him there too. When we got into the car she said I thought we were going to get my contacts so she didnít tell me we were going to the hospital. When we got there it was around the time when the sars were going around so we had to get asked all these questions.  I grabed at all the bottles that were on the desk and I was trying to drink one of em.  There were people staring at me by this time and the nurse fetches a doctor.
I got brought to this room and on the bed beside me was my friend Joe. Stuters was in intensive care. I vaguely remember this but I remember some. I remember the doctors and the 3 cops standing in front of me. The doctors gave me 2 cups of charcole in a paper cup and said I had to drink them or they would have to stick a tube down my throat. Me, having still no idea why I was in the hospital, was kinda thirsty anyway and forgot it was charcole. I looked down at the 2 cups and I figured it was pepsi or somthing so I chuged the first one then the second one.
Instantly I felt a sandy feeling in my throat and was disgusted, then came 8 cups of see through liquid and the cop says I have to drink them too. Still mad they fed me pop with sand in it I refused. I lied back in my chair and tried to look over at my friend Joe but the curtain was in the way. I whispered to my mom to push my bed back so I could see him and she said if I drink the cups first. So I did, slowly but surely. I remember how gross it was but still I did it.  My moma would hold it back and say no and I was like 'I just want to see it, just for a second.' So she let me.
I was moving my finger slowly towards my hand then in a fast motion I grabed it and riped it off. They put the clip back on and I kept trying. Finally when I gave up I whispered to my moma again. 'Move back my bed so I can see Joeí. So without the doctors noticing she did so (gotta love my moma). I looked over at Joe and I remember seeing the biggest smile on his face as he said 'Your nose is broken, thatís why your here.' and I replied 'Really? Why are you here man?' and he laughed and said 'I broke both of my legs man, Iíll never be able to walk again.' and all the cops started laughing at us.
I forgot to mention when the cops were trying to get me to drink the stuff my mom said I was hitting on the lady cop and she was blushing and everything, I laughed when she told me that. But anyway we got put into our own rooms. When I got out of the hospital like 6 of my friends told me I called them from the hospital and I donít remember still. One of the nurses found me naked in the elevator trying to excape the hospital. When I got out I was still having major side effects such as blurred vision (lasted over a week) dialated pupils (lasted a few days) for about a month after that every once in a while I would forget to take a breath, then find myself grasping for air.  Heh.
Jimson seeds is the only drug Iíve done that Iíve said and actually meant that Iíll never do them again, they were quite the experiance from what I remeber but are no doubt very harmful to my body and very unpredictable seeings how the levels of poison in the plant varys from year to year and even from leaf to leaf. I know how I think when people say donít do this or even suggest not too, Iím a curious kid and thatís why I did them and I know many more kids will too so Iíll just try to let you know what your in for, I suggest you donít do them, they are evil but I know how I am and I know some will. I spent my 15th birthday in the hospital and Iíll never forget that. Iím personally glad I did them because I learned alot, I learned that even when things seem fun they could be fatal.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


 Don't Tell Me! recording two shows when they travel to some cities; in which, the Thursday taping getting aired that weekend and the Friday taping used for future Best Of shows. The Friday shows have different Not My Job guest lined up and thus have only appeared in later Best Of shows.
This report lists out all of the Not My Job guests that have only appeared on Best Of shows and not regular shows.
{% endblock synopsis%} {% block content %}| Guest | Show Date | Repeat Show | Score | Scoring Exception |
|---|---|---|---|---|
| {{ guest.name }} | {{ guest.appearances[0].date }} | {{ guest.appearances[0].repeat_show }} | {{ guest.appearances[0].score }} | {{ guest.appearances[0].exception }} |
| {{ guest.name }} | {% endif %}{{ guest.appearances[count].date }} | {{ guest.appearances[count].repeat_show }} | {{ guest.appearances[count].score }} | {{ guest.appearances[count].exception }} |


| 120 | (A) | and so vn-knawen he was comen vs katyfes to helpe |
| 115 | (C) | So vnknowen he come caytyfes to helpe |
| 116 | (D) | So vnknowyn he come caytifs to helyn |
| 114 | (E) | & so vnknowyn he cam . caytifes to hele |
| (Ex) | ---- no text ---- | |
| 119 | (L) | & so vnknowen he came caytifes to helpe |
| 113 | (P) | So vnknawen he come . caytifs to helpe |
| 115 | (U) | So vnknowen he kom / keitifs to helpen |
| (V) | ---- no text ---- |


The data on this tracker will stop updating from 2022-09-27.
As the government of Japan announced their reduction of case reporting, the data this site relies on will not be regularly updated. As an alternative, please use the NHK News COVID-19 dashboard for up to date information.


This tutorial provides you with a quick introduction to libunittest. Note that this tutorial reflects the state of the latest version of libunittest. Please also check out the examples and unit tests that are shipped with libunittest.
There are different ways
of writing tests with libunittest depending on your needs
and requirements. The easiest way to do it would be to define
a source file like this:
// easy.cpp
By including
#include <libunittest/all.hpp>
TEST(test_value_is_true)
{
}
struct fixture {
};
TEST_FIXTURE(fixture, test_with_fixture)
{
}
Note that the above example uses the easy style by
using the macros
In order to compile the above example it is assumed
that libunittest is installed in a default system location.
In order to compile on Unix-like systems
using
g++ -std=c++0x -pthread -lunittest easy.cpp -o unittest.exe
Doing
test_value_is_true::test ... [0.000127s] ok
To get a quick help to your test application just do
test_with_fixture::test ... [0.000154s] ok
--------------------------------------------------
Ran 2 tests in 0.000281s
OK
This is your test application using libunittest 9.3.1
Usage: ./unittest.exe [Arguments]
Arguments:
-h Displays this help message and exits
-v Sets verbose output for running tests
-d A dry run without actually executing any tests
-s Stops running tests after the first test fails
-x Enables the generation of the XML output
-e Turns off handling of unexpected exceptions
-k Runs tests regardless of whether they are skipped
-i Disables the measurement of any test timeouts
-p number Runs tests in parallel with a given number of threads
-n name A certain test to be run superseding any other run filter
-f string A run filter applied to the beginning of the test names
-g regex A run filter based on regex applied to the test names
-z shuffseed A seed of >= 0 enables shuffling (0 means time based)
-t timeout A timeout in seconds for tests without static timeouts
-r precision The maximum displayed value precision
-l length The maximum displayed string length (default: 500)
-o xmlfile The XML output file name (default: libunittest.xml)
-u suite The name of the test suite (default: libunittest)
Using random functionality can be a convenient way
of generating test data. libunittest provides
easy-to-use classes to generate random values and
containers. All random stuff can be found in
Let's check out an example:
auto random = unittest::make_random_value<int>(10);
random->seed(42); // let's you set the random seed (default is 1)
int rand_value1 = random->get(); // a random int in [0, 10]
int rand_value2 = random->get(); // another random int in [0, 10]
Here's an overview of the random classes (in pseudo code) with brief descriptions:
random_value() // value between 0 and 1
random_value(maximum) // value between 0 and max
random_value(minimum, maximum) // value between min and max
The corresponding factory functions are:
make_random_value<T>(...)
random_choice(container)
The corresponding factory function is:
make_random_choice(container)
random_container(random_object, size)
random_container(random_object, min_size, max_size)
The corresponding factory functions are:
make_random_container(...)
make_random_vector(...) // for convenience
random_shuffle(container)
random_shuffle(container, size)
The corresponding factory functions are:
make_random_shuffle(...)
random_tuple(random_objects...)
The corresponding factory function is:
make_random_tuple(random_objects...)
random_pair(random_object1, random_object2)
The corresponding factory function is:
make_random_pair(random_object1, random_object2)
random_combination(container1, container2, size)
The corresponding factory function is:
make_random_combination(container1, container2, size)
./test_application -p number
where number denotes the number of concurrent threads to use.
TEST(test_number_greater_zero)
{
int number = 42;
TESTINFO("Check for number greater than zero: ", number);
ASSERT_GREATER(number, 0);
}
This will output the given test info to the
output XML and to standard out in case of fails and errors.
Note: Only use one If you'd like to contribute to libunittest then this section will be interesting for you. First you'd want to check out the code. For the following, it is assumed that you develop on a Unix-like OS such as Linux or MacOSX. However, developing on Windows and Visual Studio is just as easy.
libunittest uses the GNU build system (autotools) which means you will need to have
./autogen.sh
Now you can run things like
./configure --enable-debug
Whether you're developing a new feature or
fixing a bug, please always and in any case make
sure you test the stuff you're writing. You can
easily add your tests to the existing test
suite. Also consider providing an example on how
to use your new feature. And finally, your
code is only complete if it is properly documented.
In order to check if your code documentation is complete you can do:
make -C docs/doxygen
Happy coding!


--- layout: search title: Jekyll Search permalink: /search-jekyll/ description: Jekyll Search power_supply_url: "https://github.com/daviddarnes/jekyll-search-js" power_supply_label: "jekyll-search-js" ---