Mesh Class
A data buffer to be stored in the GPU
Constructor
Mesh
-
vertexBuffers
-
indexBuffers
-
options
Parameters:
-
vertexBuffers
Objectobject with all the vertex streams
-
indexBuffers
Objectobject with all the indices streams
-
options
Object
Item Index
Methods
- addBuffers
- addIndexBuffer
- addVertexBuffer
- compile
- computeNormals
- computeTangents
- computeWireframe
- freeData
- generateMetadata
- getBuffer
- getIndexBuffer
- getVertexBuffer
- getVertexNumber
- Mesh.computeBounding
- Mesh.cube
- Mesh.cylinder
- Mesh.load
- Mesh.mergeMeshes
- Mesh.plane
- Mesh.plane2D
- Mesh.sphere
- removeVertexBuffer
- setBounding
- updateBounding
Methods
addBuffers
-
vertexBuffers
-
indexBuffers
-
stream_type
Adds vertex and indices buffers to a mesh
Parameters:
-
vertexBuffers
Objectobject with all the vertex streams
-
indexBuffers
Objectobject with all the indices streams
-
stream_type
Enumdefault gl.STATIC_DRAW (other: gl.DYNAMIC_DRAW, gl.STREAM_DRAW )
addIndexBuffer
-
name
-
data
-
stream_type
Creates a new empty index buffer and attachs it to this mesh
Parameters:
-
name
String -
data
Typed array -
stream_type
Enumgl.STATIC_DRAW, gl.DYNAMIC_DRAW, gl.STREAM_DRAW
addVertexBuffer
-
name
-
attribute
-
spacing
-
buffer_data
-
stream_type
Creates a new empty buffer and attachs it to this mesh
Parameters:
-
name
String"vertices","normals"...
-
attribute
Stringname of the stream in the shader "a_vertex","a_normal",... [optional, if omitted is used the common_buffers]
-
spacing
Numbercomponents per vertex [optioanl, if ommited is used the common_buffers, otherwise 3]
-
buffer_data
ArrayBufferViewthe data in typed array format [optional, if ommited it created an empty array of getNumVertices() * spacing]
-
stream_type
Enum[optional, default = gl.STATIC_DRAW (other: gl.DYNAMIC_DRAW, gl.STREAM_DRAW ) ]
compile
-
buffer_type
Uploads data inside buffers to VRAM.
Parameters:
-
buffer_type
Numbergl.STATIC_DRAW, gl.DYNAMIC_DRAW, gl.STREAM_DRAW
computeNormals
()
Creates a stream with the normals
computeTangents
()
Creates a new stream with the tangents
computeWireframe
()
Creates a new index stream with wireframe
freeData
()
Remove all local memory from the streams (leaving it only in the VRAM) to save RAM
generateMetadata
()
Computes some data about the mesh
getBuffer
-
name
Returns a vertex buffer
Parameters:
-
name
Stringof vertex buffer
Returns:
the buffer
getIndexBuffer
-
name
Returns a index buffer
Parameters:
-
name
Stringof index buffer
Returns:
the buffer
getVertexBuffer
-
name
Returns a vertex buffer
Parameters:
-
name
Stringof vertex buffer
Returns:
the buffer
getVertexNumber
-
vertices
Computes bounding information
Parameters:
-
vertices
Typed Arrayarray containing all the vertices
Mesh.computeBounding
-
vertices
Computes bounding information
Parameters:
-
vertices
Typed Arrayarray containing all the vertices
Mesh.cube
-
options
Returns a cube mesh
Parameters:
-
options
Objectvalid options: size
Mesh.cylinder
-
options
Returns a cube mesh
Parameters:
-
options
Objectvalid options: radius, height, subdivisions
Mesh.load
-
buffers
-
options
-
output_mesh
Static method for the class Mesh to create a mesh from a list of common streams
Parameters:
-
buffers
Objectobject will all the buffers
-
options
Object -
output_mesh
Meshoptional mesh to store the mesh, otherwise is created
Mesh.mergeMeshes
-
meshes
Returns a mesh with all the meshes merged
Parameters:
-
meshes
Arrayarray containing all the meshes
Mesh.plane
-
options
Returns a planar mesh (you can choose how many subdivisions)
Parameters:
-
options
Objectvalid options: detail, detailX, detailY, size, width, heigth, xz (horizontal plane)
Mesh.plane2D
()
Returns a 2D Mesh (be careful, stream is vertices2D )
Mesh.sphere
-
options
Returns a sphere mesh
Parameters:
-
options
Objectvalid options: radius, lat, long
removeVertexBuffer
-
name
Removes a vertex buffer from the mesh
Parameters:
-
name
String"vertices","normals"...
setBounding
-
center
-
half_size
forces a bounding box to be set
Parameters:
-
center
Vec3center of the bounding box
-
half_size
Vec3vector from the center to positive corner
updateBounding
()
Update bounding information of this mesh


Class EnVector2Extensions
Inheritance
System.Object
EnVector2Extensions
Assembly: ECHTNICE.EnUnityEngineExtensions.dll
Syntax
public static class EnVector2Extensions
Methods
|
Improve this Doc
View Source
AddX(Vector2, Single)
Declaration
public static Vector2 AddX(this Vector2 vec, float x)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
| System.Single |
x |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
AddY(Vector2, Single)
Declaration
public static Vector2 AddY(this Vector2 vec, float y)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
| System.Single |
y |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
Distance(Vector2, Vector2)
Distance to a second point.
Declaration
public static float Distance(this Vector2 v, Vector2 u)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
v |
Origin point.
|
| UnityEngine.Vector2 |
u |
Destination point.
|
Returns
| Type |
Description |
| System.Single |
The distance from origin to destination.
|
|
Improve this Doc
View Source
Dot(Vector2, Vector2)
Calculate two vector's dot product. Sugar for UnityEngine.Vector2.Dot(UnityEngine.Vector2,UnityEngine.Vector2)
Declaration
public static float Dot(this Vector2 v, Vector2 u)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
v |
|
| UnityEngine.Vector2 |
u |
|
Returns
| Type |
Description |
| System.Single |
The vector's dot product.
|
|
Improve this Doc
View Source
Invert(Vector2)
Declaration
public static Vector2 Invert(this Vector2 vec)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
InvertX(Vector2)
Declaration
public static Vector2 InvertX(this Vector2 vec)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
InvertY(Vector2)
Declaration
public static Vector2 InvertY(this Vector2 vec)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
Rotate(Vector2, Quaternion)
Declaration
public static Vector2 Rotate(this Vector2 point, Quaternion angle)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
point |
Vector to rotate.
|
| UnityEngine.Quaternion |
angle |
Angle to rotate.
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
The result of rotating point.
|
|
Improve this Doc
View Source
RotateAround(Vector2, Vector2, Quaternion)
Rotate around a given point.
Declaration
public static Vector2 RotateAround(this Vector2 point, Vector2 origin, Quaternion angle)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
point |
Point to rotate.
|
| UnityEngine.Vector2 |
origin |
Reference for rotation.
|
| UnityEngine.Quaternion |
angle |
Angle to rotate.
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
The result of rotating point around origin.
|
|
Improve this Doc
View Source
SqrDistance(Vector2, Vector2)
Squared distance to a second point.
Declaration
public static float SqrDistance(this Vector2 v, Vector2 u)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
v |
Origin point.
|
| UnityEngine.Vector2 |
u |
Destination point.
|
Returns
| Type |
Description |
| System.Single |
The squared distance from origin to destination.
|
|
Improve this Doc
View Source
To(Vector2, Vector2)
Get vector between source and destination
Declaration
public static Vector2 To(this Vector2 source, Vector2 destination)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
source |
|
| UnityEngine.Vector2 |
destination |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
WithX(Vector2, Single)
Declaration
public static Vector2 WithX(this Vector2 vec, float x)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
| System.Single |
x |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|
|
Improve this Doc
View Source
WithY(Vector2, Single)
Declaration
public static Vector2 WithY(this Vector2 vec, float y)
Parameters
| Type |
Name |
Description |
| UnityEngine.Vector2 |
vec |
|
| System.Single |
y |
|
Returns
| Type |
Description |
| UnityEngine.Vector2 |
|


Eurojackpot results for Friday 18th December 2015
The winning numbers for the 51st Eurojackpot draw in 2015 that took place on Friday 18th December at 21:00 CEST (20:00 GMT) were:
Winners
Winners
Amount
Slovenian Prize Breakdown
View prize breakdowns for other countries| Numbers Matched | Prize Per Winner | Winners from Slovenia | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 1 | €2,747 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 13 | €2,405 | 775 |
|
Match 4 |
€88.20 | 26 | €2,293.20 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 45 | €2,308.50 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 524 | €10,846.80 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 636 | €10,239.60 | 29,614 |
|
Match 3 |
€13.20 | 1,156 | €15,259.20 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 2,366 | €24,843 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 8,008 | €61,661.60 | 392,264 |
|
Total |
- | 12,775 | €132,603.90 | 619,056 |
Eurojackpot prizes in Slovenia must be claimed within 90 days of the draw date, so tickets purchased for this draw were valid until Thursday 17th March 2016.
Additional Draw Information
In total there were 15,932,712 entries into this draw from all participating countries.
Draw Number: 51
European Prize Breakdown
| Numbers Matched | Prize Per Winner | Winners from Croatia | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
kn0 | 0 | kn0 | 0 |
|
Match 5 and 1 Euro Number |
kn0 | 0 | kn0 | 3 |
|
Match 5 |
kn0 | 0 | kn0 | 6 |
|
Match 4 and 2 Euro Numbers |
kn0 | 0 | kn0 | 58 |
|
Match 4 and 1 Euro Number |
kn0 | 0 | kn0 | 775 |
|
Match 4 |
kn0 | 0 | kn0 | 1,264 |
|
Match 3 and 2 Euro Numbers |
kn0 | 0 | kn0 | 1,863 |
|
Match 2 and 2 Euro Numbers |
kn0 | 0 | kn0 | 23,795 |
|
Match 3 and 1 Euro Number |
kn0 | 0 | kn0 | 29,614 |
|
Match 3 |
kn0 | 0 | kn0 | 51,741 |
|
Match 1 and 2 Euro Numbers |
kn0 | 0 | kn0 | 117,673 |
|
Match 2 and 1 Euro Number |
kn0 | 0 | kn0 | 392,264 |
|
Total |
- | 0 | kn0 | 619,056 |
Eurojackpot prizes in Croatia must be claimed within 60 days of the draw date, so tickets purchased for this draw were valid until Tuesday 16th February 2016.
The estimated jackpot advertised in Croatia prior to the draw was 0.
| Numbers Matched | Prize Per Winner | Winners from Czech Republic | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
Kč0 | 0 | Kč0 | 0 |
|
Match 5 and 1 Euro Number |
Kč12,202,066 | 0 | Kč0 | 3 |
|
Match 5 |
Kč2,153,304 | 0 | Kč0 | 6 |
|
Match 4 and 2 Euro Numbers |
Kč74,251 | 1 | Kč74,251 | 58 |
|
Match 4 and 1 Euro Number |
Kč5,000 | 20 | Kč100,000 | 775 |
|
Match 4 |
Kč2,384 | 34 | Kč81,056 | 1,264 |
|
Match 3 and 2 Euro Numbers |
Kč1,386 | 51 | Kč70,686 | 1,863 |
|
Match 2 and 2 Euro Numbers |
Kč559 | 608 | Kč339,872 | 23,795 |
|
Match 3 and 1 Euro Number |
Kč435 | 707 | Kč307,545 | 29,614 |
|
Match 3 |
Kč356 | 1,203 | Kč428,268 | 51,741 |
|
Match 1 and 2 Euro Numbers |
Kč283 | 2,959 | Kč837,397 | 117,673 |
|
Match 2 and 1 Euro Number |
Kč208 | 9,066 | Kč1,885,728 | 392,264 |
|
Total |
- | 14,649 | Kč4,124,803 | 619,056 |
Eurojackpot prizes in Czech Republic must be claimed within 35 days of the draw date, so tickets purchased for this draw were valid until Friday 22nd January 2016.
The estimated jackpot advertised in Czech Republic prior to the draw was 0.
| Numbers Matched | Prize Per Winner | Winners from Denmark | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
kr.0 | 0 | kr.0 | 0 |
|
Match 5 and 1 Euro Number |
kr.2,877,875 | 0 | kr.0 | 3 |
|
Match 5 |
kr.507,884 | 1 | kr.507,884 | 6 |
|
Match 4 and 2 Euro Numbers |
kr.17,542 | 6 | kr.105,252 | 58 |
|
Match 4 and 1 Euro Number |
kr.1,209 | 74 | kr.89,466 | 775 |
|
Match 4 |
kr.592 | 137 | kr.81,104 | 1,264 |
|
Match 3 and 2 Euro Numbers |
kr.357 | 200 | kr.71,400 | 1,863 |
|
Match 2 and 2 Euro Numbers |
kr.155 | 2,655 | kr.411,525 | 23,795 |
|
Match 3 and 1 Euro Number |
kr.120 | 2,909 | kr.349,080 | 29,614 |
|
Match 3 |
kr.99 | 5,249 | kr.519,651 | 51,741 |
|
Match 1 and 2 Euro Numbers |
kr.78 | 13,335 | kr.1,040,130 | 117,673 |
|
Match 2 and 1 Euro Number |
kr.57 | 41,909 | kr.2,388,813 | 392,264 |
|
Total |
- | 66,475 | kr.5,564,305 | 619,056 |
Eurojackpot prizes in Denmark must be claimed within a set period of time depending on how much you have won. Visit the How to Claim page to find specific claim periods, with some prizes needing to be claimed within 90 days of the draw (valid until Thursday 17th March 2016).
The estimated jackpot advertised in Denmark prior to the draw was 0.
| Numbers Matched | Prize Per Winner | Winners from Estonia | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 0 | €0 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 5 | €925 | 775 |
|
Match 4 |
€88.20 | 12 | €1,058.40 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 13 | €666.90 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 222 | €4,595.40 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 269 | €4,330.90 | 29,614 |
|
Match 3 |
€13.20 | 439 | €5,794.80 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 1,067 | €11,203.50 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 3,386 | €26,072.20 | 392,264 |
|
Total |
- | 5,413 | €54,647.10 | 619,056 |
Eurojackpot prizes in Estonia must be claimed within 90 days of the draw date, so tickets purchased for this draw were valid until Thursday 17th March 2016.
The estimated jackpot advertised in Estonia prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Finland | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 3 | €1,354,280.40 | 3 |
|
Match 5 |
€79,663.50 | 1 | €79,663.50 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | At present this information is not released by the lottery operator of Finland | 58 | |
|
Match 4 and 1 Euro Number |
€185 | 775 | ||
|
Match 4 |
€88.20 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
€51.30 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
€20.70 | 23,795 | ||
|
Match 3 and 1 Euro Number |
€16.10 | 29,614 | ||
|
Match 3 |
€13.20 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
€10.50 | 117,673 | ||
|
Match 2 and 1 Euro Number |
€7.70 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Finland must be claimed within 365 days of the draw date, so tickets purchased for this draw were valid until Saturday 17th December 2016.
The estimated jackpot advertised in Finland prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Germany | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 4 | €318,654 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | At present this information is not released by the lottery operator of Germany | 58 | |
|
Match 4 and 1 Euro Number |
€185 | 775 | ||
|
Match 4 |
€88.20 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
€51.30 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
€20.70 | 23,795 | ||
|
Match 3 and 1 Euro Number |
€16.10 | 29,614 | ||
|
Match 3 |
€13.20 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
€10.50 | 117,673 | ||
|
Match 2 and 1 Euro Number |
€7.70 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Germany must be claimed within 3 years of the draw date, so tickets purchased for this draw were valid until Tuesday 18th December 2018.
The estimated jackpot advertised in Germany prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Hungary | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
Ft22,082,720 | 0 | Ft0 | 6 |
|
Match 4 and 2 Euro Numbers |
Ft761,470 | 4 | Ft3,045,880 | 58 |
|
Match 4 and 1 Euro Number |
Ft51,280 | 49 | Ft2,512,720 | 775 |
|
Match 4 |
Ft24,450 | 50 | Ft1,222,500 | 1,264 |
|
Match 3 and 2 Euro Numbers |
Ft14,220 | 83 | Ft1,180,260 | 1,863 |
|
Match 2 and 2 Euro Numbers |
Ft5,740 | 1,000 | Ft5,740,000 | 23,795 |
|
Match 3 and 1 Euro Number |
Ft4,465 | 1,254 | Ft5,599,110 | 29,614 |
|
Match 3 |
Ft3,660 | 1,831 | Ft6,701,460 | 51,741 |
|
Match 1 and 2 Euro Numbers |
Ft2,910 | 4,037 | Ft11,747,670 | 117,673 |
|
Match 2 and 1 Euro Number |
Ft2,135 | 14,023 | Ft29,939,105 | 392,264 |
|
Total |
- | 22,331 | Ft67,688,705 | 619,056 |
Eurojackpot prizes in Hungary must be claimed within 180 days of the draw date, so tickets purchased for this draw were valid until Wednesday 15th June 2016.
The estimated jackpot advertised in Hungary prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Iceland | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
kr.4,566,334,940 | 0 | kr.0 | 0 |
|
Match 5 and 1 Euro Number |
kr.63,709,860 | 0 | kr.0 | 3 |
|
Match 5 |
kr.11,242,900 | 0 | kr.0 | 6 |
|
Match 4 and 2 Euro Numbers |
kr.387,680 | At present this information is not released by the lottery operator of Iceland | 58 | |
|
Match 4 and 1 Euro Number |
kr.26,100 | 775 | ||
|
Match 4 |
kr.12,440 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
kr.7,230 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
kr.2,270 | 23,795 | ||
|
Match 3 and 1 Euro Number |
kr.2,920 | 29,614 | ||
|
Match 3 |
kr.1,860 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
kr.1,480 | 117,673 | ||
|
Match 2 and 1 Euro Number |
kr.1,080 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Iceland must be claimed within 1 year of the draw date, so tickets purchased for this draw were valid until Sunday 18th December 2016.
The estimated jackpot advertised in Iceland prior to the draw was 0.
| Numbers Matched | Prize Per Winner | Winners from Italy | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 6 | €16,482 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 34 | €6,290 | 775 |
|
Match 4 |
€88.20 | 45 | €3,969 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 116 | €5,950.80 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 1,111 | €22,997.70 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 1,450 | €23,345 | 29,614 |
|
Match 3 |
€13.20 | 2,585 | €34,122 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 5,585 | €58,642.50 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 20,285 | €156,194.50 | 392,264 |
|
Total |
- | 31,217 | €327,993.50 | 619,056 |
Eurojackpot prizes in Italy must be claimed within a set period of time depending on how much you have won. Visit the How to Claim page to find specific claim periods, with some prizes needing to be claimed within 30 days of the draw (valid until Sunday 17th January 2016).
The estimated jackpot advertised in Italy prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Latvia | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | At present this information is not released by the lottery operator of Latvia | 58 | |
|
Match 4 and 1 Euro Number |
€185 | 775 | ||
|
Match 4 |
€88.20 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
€51.30 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
€20.70 | 23,795 | ||
|
Match 3 and 1 Euro Number |
€16.10 | 29,614 | ||
|
Match 3 |
€13.20 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
€10.50 | 117,673 | ||
|
Match 2 and 1 Euro Number |
€7.70 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Latvia must be claimed within 30 days of the draw date, so tickets purchased for this draw were valid until Sunday 17th January 2016.
The estimated jackpot advertised in Latvia prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Lithuania | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 3 | €8,241 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 3 | €555 | 775 |
|
Match 4 |
€88.20 | 2 | €176.40 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 15 | €769.50 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 121 | €2,504.70 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 145 | €2,334.50 | 29,614 |
|
Match 3 |
€13.20 | 250 | €3,300 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 612 | €6,426 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 1,805 | €13,898.50 | 392,264 |
|
Total |
- | 2,956 | €38,205.60 | 619,056 |
Eurojackpot prizes in Lithuania must be claimed within 60 days of the draw date, so tickets purchased for this draw were valid until Tuesday 16th February 2016.
The estimated jackpot advertised in Lithuania prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Netherlands | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€0 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | At present this information is not released by the lottery operator of Netherlands | 58 | |
|
Match 4 and 1 Euro Number |
€185 | 775 | ||
|
Match 4 |
€88.20 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
€51.30 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
€20.70 | 23,795 | ||
|
Match 3 and 1 Euro Number |
€16.10 | 29,614 | ||
|
Match 3 |
€13.20 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
€10.50 | 117,673 | ||
|
Match 2 and 1 Euro Number |
€7.70 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Netherlands must be claimed within 365 days of the draw date, so tickets purchased for this draw were valid until Saturday 17th December 2016.
The estimated jackpot advertised in Netherlands prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Norway | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
kr.0 | 0 | kr.0 | 0 |
|
Match 5 and 1 Euro Number |
kr.4,288,550 | 0 | kr.0 | 3 |
|
Match 5 |
kr.756,800 | 0 | kr.0 | 6 |
|
Match 4 and 2 Euro Numbers |
kr.26,095 | At present this information is not released by the lottery operator of Norway | 58 | |
|
Match 4 and 1 Euro Number |
kr.1,755 | 775 | ||
|
Match 4 |
kr.835 | 1,264 | ||
|
Match 3 and 2 Euro Numbers |
kr.485 | 1,863 | ||
|
Match 2 and 2 Euro Numbers |
kr.195 | 23,795 | ||
|
Match 3 and 1 Euro Number |
kr.150 | 29,614 | ||
|
Match 3 |
kr.125 | 51,741 | ||
|
Match 1 and 2 Euro Numbers |
kr.95 | 117,673 | ||
|
Match 2 and 1 Euro Number |
kr.70 | 392,264 | ||
|
Total |
- | 619,056 |
Eurojackpot prizes in Norway must be claimed within 3 months of the draw date, so tickets purchased for this draw were valid until Friday 18th March 2016.
The estimated jackpot advertised in Norway prior to the draw was 0.
| Numbers Matched | Prize Per Winner | Winners from Slovakia | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 0 | €0 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 11 | €2,035 | 775 |
|
Match 4 |
€88.20 | 18 | €1,587.60 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 39 | €2,000.70 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 419 | €8,673.30 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 589 | €9,482.90 | 29,614 |
|
Match 3 |
€13.20 | 952 | €12,566.40 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 2,021 | €21,220.50 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 6,879 | €52,968.30 | 392,264 |
|
Total |
- | 10,928 | €110,534.70 | 619,056 |
Eurojackpot prizes in Slovakia must be claimed within 35 days of the draw date, so tickets purchased for this draw were valid until Friday 22nd January 2016.
The estimated jackpot advertised in Slovakia prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Spain | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
€32,355,522.92 | 0 | €0 | 0 |
|
Match 5 and 1 Euro Number |
€451,426.80 | 0 | €0 | 3 |
|
Match 5 |
€79,663.50 | 0 | €0 | 6 |
|
Match 4 and 2 Euro Numbers |
€2,747 | 2 | €5,494 | 58 |
|
Match 4 and 1 Euro Number |
€185 | 19 | €3,515 | 775 |
|
Match 4 |
€88.20 | 25 | €2,205 | 1,264 |
|
Match 3 and 2 Euro Numbers |
€51.30 | 60 | €3,078 | 1,863 |
|
Match 2 and 2 Euro Numbers |
€20.70 | 690 | €14,283 | 23,795 |
|
Match 3 and 1 Euro Number |
€16.10 | 847 | €13,636.70 | 29,614 |
|
Match 3 |
€13.20 | 1,429 | €18,862.80 | 51,741 |
|
Match 1 and 2 Euro Numbers |
€10.50 | 3,680 | €38,640 | 117,673 |
|
Match 2 and 1 Euro Number |
€7.70 | 12,215 | €94,055.50 | 392,264 |
|
Total |
- | 18,967 | €193,770 | 619,056 |
Eurojackpot prizes in Spain must be claimed within 30 days of the draw date, so tickets purchased for this draw were valid until Sunday 17th January 2016.
The estimated jackpot advertised in Spain prior to the draw was €31,000,000.
| Numbers Matched | Prize Per Winner | Winners from Sweden | Prize Fund Amount | Total Winners |
|---|---|---|---|---|
|
Match 5 and 2 Euro Numbers |
kr.0 | 0 | kr.0 | 0 |
|
Match 5 and 1 Euro Number |
kr.4,190,414 | 0 | kr.0 | 3 |
|
Match 5 |
kr.739,484 | 0 | kr.0 | 6 |
|
Match 4 and 2 Euro Numbers |
kr.25,499 | 0 | kr.0 | 58 |
|
Match 4 and 1 Euro Number |
kr.16,126 | 22 | kr.354,772 | 775 |
|
Match 4 |
kr.8,743 | 36 | kr.314,748 | 1,264 |
|
Match 3 and 2 Euro Numbers |
kr.4,351 | 45 | kr.195,795 | 1,863 |
|
Match 2 and 2 Euro Numbers |
kr.192 | 730 | kr.140,160 | 23,795 |
|
Match 3 and 1 Euro Number |
kr.150 | 817 | kr.122,550 | 29,614 |
|
Match 3 |
kr.123 | 1,562 | kr.192,126 | 51,741 |
|
Match 1 and 2 Euro Numbers |
kr.97 | 3,496 | kr.339,112 | 117,673 |
|
Match 2 and 1 Euro Number |
kr.71 | 11,394 | kr.808,974 | 392,264 |
|
Total |
- | 18,102 | kr.2,468,237 | 619,056 |
Eurojackpot prizes in Sweden must be claimed within 3 months of the draw date, so tickets purchased for this draw were valid until Friday 18th March 2016.
The estimated jackpot advertised in Sweden prior to the draw was 0.
Associated Draw Results
- 0
- 8
- 3
- 2
- 9
- 3
| Numbers Matched | Prize Per Winner | Total Winners |
|---|---|---|
| Match 6 in Exact Order | €50,000 | 0 |
| Match Last 5 in Exact Order | €5,000 | 0 |
| Match Last 4 in Exact Order | €500 | 11 |
| Match Last 3 in Exact Order | €50 | 70 |
| Match Last 2 in Exact Order | €5 | 799 |
| Match Last 1 in Exact Order | €3 | 7,788 |
- 3
- 9
- 5
- 7
- 6
- 9
| Numbers Matched | Prize Per Winner | Total Winners |
|---|---|---|
| Match 6 | CZK2,000,000 | 0 |
| Match 5 | CZK200,000 | 0 |
| Match 4 | CZK20,000 | 4 |
| Match 3 | CZK2,000 | 58 |
| Match 2 | CZK200 | 648 |
| Match 1 | CZK120 | 6,505 |
- 6
- 9
- 4
- 9
- 6
- 7
- 2
| Numbers Matched | Prize Per Winner | Total Winners |
|---|---|---|
| Match 7 in Exact Order | €0 | 0 |
| Match Any 6 in the Right Spot | €20,000 | 1 |
| Match Any 5 in the Right Spot | €500 | 45 |
| Match Any 4 in the Right Spot | €50 | 562 |
| Match Any 3 in the Right Spot | €6 | 4,838 |
| Match Any 2 in the Right Spot | €3 | 26,148 |
- 8
- 1
- 4
- 1
- 8
| Numbers Matched | Prize Per Winner | Total Winners |
|---|---|---|
| Match 5 in Exact Order | kr2,000,000 | 0 |
| Match First/Last 4 in Exact Order | kr100,000 | 1 |
| Match First/Last 3 in Exact Order | kr10,000 | 6 |
| Match First/Last 2 in Exact Order | kr2,000 | 105 |
Related Eurojackpot Results Links
- Automatically check your Eurojackpot ticket
- View average prizes and winners for each prize tiers
- View the largest jackpot winners and total winners from each country
- View previous Eurojackpot results by year
Buy Eurojackpot Tickets Online
By buying your Eurojackpot tickets online you don’t have to worry about ever losing your Eurojackpot lottery tickets. When you play the Eurojackpot online all your lottery tickets purchased on the internet are stored in your personal account, meaning that you can view them anytime you wish.


{% extends 'base.html' %} {% block content %}
{{pitch.pitch_content}}
Posted by {{pitch.username}}
{{pitch.comment_content}}


--- layout : default title : awesomeScripts active : home ---
You can contribute by adding new scripts, improving current scripts or Documentation.Here are some Instructions before making a Pull Request
| Script Name | Author(GitHub username) | Short introduction to program |
|---|---|---|
| {{project.name}} | {{project.author}} | {{project.description}} |
Deepak Raj |


Primary Content (h2)
Headline the Third (h3)
Headline the Fourth (h4)
First paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence. Some words in sentences need to be bolded, italicized, strengthened or emphasized.
Another paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
- Unordered List - First item.
- Another item with a link.
- Another item that is linked
- Last item.
- Ordered List - First item.
- Another item with a link.
- Another item that is linked.
- Last item.
Another paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
Unordered List with Paragraphs - First item.
Another item with a link.
Last item.
Ordered List with Paragraphs - First item.
Another item with a link.
Last item.
Headline the Fourth (h4)
Another paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
First blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence. Some words in sentences need to be bolded, italicized, strengthened or emphasized.
Another blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
Last blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
Cite tags are great for showing references.
Headline the Fourth (h4)
Another blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
- Definition List - First term
- A definition may be a statement of the essential properties of a certain thing, or a statement of equivalence between a term and that term's meaning. The two are not mutually exclusive, nor are they equivalent.
- Another Term with a Link.
- A definition may be a statement of the essential properties of a certain thing, or a statement of equivalence between a term and that term's meaning. The two are not mutually exclusive, nor are they equivalent.
- Another Term that is Linked
- A definition may be a statement of the essential properties of a certain thing, or a statement of equivalence between a term and that term's meaning. The two are not mutually exclusive, nor are they equivalent.
- Last Term
- A definition may be a statement of the essential properties of a certain thing, or a statement of equivalence between a term and that term's meaning. The two are not mutually exclusive, nor are they equivalent.
Headline the Fourth (h4)
Another blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
| First | Second | Third | Fourth | Fifth | Last |
|---|---|---|---|---|---|
| Total | Total | Total | Total | Total | Total |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
| Alt 1 | Alt 2 | Alt 3 | Alt 4 | Alt 5 | Alt 6 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
| Alt 1 | Alt 2 | Alt 3 | Alt 4 | Alt 5 | Alt 6 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
Another blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
| Total | Total | Total | Total | Total | Total | |
| Title : | Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
|---|---|---|---|---|---|---|
| Title : | Alt 1 | Alt 2 | Alt 3 | Alt 4 | Alt 5 | Alt 6 |
| Title : | Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
| Title : | Alt 1 | Alt 2 | Alt 3 | Alt 4 | Alt 5 | Alt 6 |
| Title : | Data 1 | Data 2 | Data 3 | Data 4 | Data 5 | Data 6 |
Headline the Fourth (h4)
Another blockquote paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.
Headline the Fourth (h4)
Last paragraph. In typography, a paragraph is a block of text. Paragraphs are the medium-size unit of human-language text. A group of sentences developing a single idea from a topic sentence.


JRemoting 1.0.1 released.
RMI transport has a bug fixed use of the RMI Registry. SimpleRetryingClientMonitor now is able to have customizable retry delay.
JRemoting 1.0 released.


We continue to follow our New Year’s resolutions, where we have promised to catch the iOS version of OsmAnd up with the one on Android, and we are getting there. OSM Editing allows you to make contributions to OpenStreetMap, a global community aimed at creating a comprehensive map of the world and providing up-to-date open-source data to every user.
The feature lets you create new objects, so-called points of interest or POI on the map and OSM notes.
So how to do it? Tap on the map where the new POI has to be placed -> 'Actions' and press 'Create POI' or 'Open OSM Note' add its name and other details like working hours, website, etc. You'll also have to register at OpenStreetMap and then provide your OSM credentials to introduce changes.
There are all your "Edits" and "Notes" at general menu -> 'My Places' -> 'OSM Edits'. From this menu, you can delete or upload all your edits and notes.
Combined "Favorites", "Trips" and "OSM Edits" screens into a new 'My Places' screen.
• Added options to control the size of map elements: use “Text Size” option to control the size of the text and icons on the map and “Map Magnifier” to control the overall size of map elements.
• Opening a search result on the map will now zoom in on the selected point.
• Fixed icon sizes on map.
• Optimized multiple menus for iPhone X screen.
• Added Hungarian and Hungarian (formal) TTS, added alphabetical sorting to the TTS language list.
And remember that only together we can achieve the best results!
New features are coming SOON!


This assessment is based on our own internal research done on the subject. Attached is a PDF that includes the grading charts that we have gathered from the Colorado Department of Education.


Amazon EC2 instances are the fundamental building block for your computing needs in the AWS cloud. You can think of instances as virtual servers that can run applications. Instances are created from an Amazon Machine Image (AMI) and choosing an appropriate instance type. An AMI is a template that contains a software configuration, including an operating system, which defines your operating environment. You can select an AMI provided by AWS, our user community, or on the AWS Marketplace. You can also create and optionally share your own AMIs. A single AMI can be used to launch one or thousands of instances.
Amazon EC2 provides a wide selection of instance types optimized to fit different use cases. Instance types comprise varying combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose
the appropriate mix of resources for your applications. Each instance type includes one or more instance sizes, allowing you to scale your resources to the requirements of your target workload. For the best experience, you should launch on instance types that are appropriate for your applications. You have the flexibility to choose the combination of instance types most appropriate for your application today, and then choose a different instance size as your business and application needs change. To make it easier for you to select the best option for your applications, Amazon EC2 instance types are grouped together into families based on target application profiles. Below is a quick guide to help you think about choosing the right
instance type.
Amazon EC2 instances are available in the following families:
This family includes the M1 and M3 instance types, and provides a balance of compute, memory, and network resources, and it is a good choice for many applications. General-purpose instances are recommended for small and mid-size databases, data processing tasks that require additional memory, caching fleets, and for running backend servers for SAP, Microsoft SharePoint, and other enterprise applications. M3 instances are the newest generation of general-purpose instances, and give you the option of a larger number of virtual CPUs (vCPUs) that provide higher performance. M3 instances are recommended if you are seeking general purpose instances with demanding CPU requirements. M1 instances are the original family of general-purpose instances and provide the lowest cost options for running your applications. M1 instances are a great option if you are seeking moderate CPU performance, and a lower overall price.
This family includes the C1 and CC2 instance types and is optimized for applications that benefit from high compute power. Compute-optimized instances have a higher ratio of vCPUs to memory than other families and the lowest cost per vCPU among all Amazon EC2 instance types. We recommend compute-optimized instances for running CPU-bound scale out applications. Examples of such applications include high traffic front end fleets, on-demand batch processing, distributed analytics, web servers, batch processing, and high performance science and engineering applications. CC2 instances are the latest generation of compute-optimized instances and provide the lowest cost CPU power relative to other instance families. CC2 instances also provide a number of advanced capabilities: Intel Xeon E5-2670 processors; high core count (32 vCPUs); support for cluster networking. These capabilities allow you to cluster CC2 instances into high performance clusters capable of delivering hundreds of teraflops of floating point performance. C1 instances are the first generation of compute-optimized instances; they are available in smaller sizes and useful for massively scaled-out applications. For example, customers have launched distributed clusters of thousands of c1.xlarge instances to encode videos or screen compound libraries to design new drugs.
This family includes the M2 and CR1 instance types and is optimized for memory-intensive applications. Memory-optimized instances have the lowest cost per GiB of RAM among Amazon EC2 instance types. We recommend memory-optimized instances for many database applications, for memcached and other distributed caches, and larger deployments of enterprise applications like SAP and Microsoft SharePoint. CR1 instances are the latest generation of memory-optimized instances and provide even more memory (244 GiB), run on faster CPUs (Intel Xeon E5-2670 with NUMA support) compared to M2 instances, and support cluster networking for bandwidth intensive applications. M2 instances are available in smaller sizes, and are an excellent option for many memory-bound applications.
This family includes the HI1 and HS1 instance types, and provides you with direct-attached
storage options optimized for applications with specific disk I/O
and storage capacity requirements. Currently, there are two types of storage-optimized
instances. HI1 instances provide very fast SSD-backed instance
storage capable of supporting over 120,000 random read IOPS, and are optimized for
very high random I/O performance and low cost per IOPS. HS1 instances are optimized
for very high storage density, low storage cost, and high sequential I/O performance.
We recommend using HI1 instances for NoSQL databases like Cassandra and MongoDB which benefit
from very high random I/O performance and the low request latency of direct-attached
SSDs. HI1 instances are also an excellent choice for transactional systems that
can manage their own resiliency.
HS1 instances provide you with 48 TB of storage capacity across 24 hard disk
drives, high network performance, and offer throughput performance
of up to 2.6 GBps. We recommend HS1 instances for customers running large-scale
data warehouses or parallel file systems. For instance, if you are running an always-on Hadoop
cluster with 100s of terabytes of data, you should choose HS1 instances.
 Micro instances may opportunistically increase CPU capacity in short bursts when additional cycles are available. They are well suited for lower throughput applications and websites that require additional compute cycles periodically, but are not appropriate for applications that require sustained CPU performance.
This family includes the CG1 instances and allows you to take advantage of the parallel performance of NVidia Tesla GPUs using the CUDA and OpenCL programming models for GPGPU computing. GPU instances also provide high CPU capabilities and support cluster networking.
We recommend that you select the instance type that is most appropriate for your workload profile and scale, and then change your instance type if your application's requirements change. In all cases, we strongly recommend application profiling and load testing. The availability of multiple instance types, combined with features like EBS-optimization and cluster networking allow applications to be optimized for increased performance, improved application resilience, and lower costs. In particular, you should evaluate the most important performance metrics for your application. For applications that benefit from a low
cost per CPU, we recommend choosing compute-optimized instances (C1 or CC2 instances). For applications that require the lowest cost per GiB of memory, we recommend choosing memory-optimized instances (M2 or CR1 instances). Additionally, we recommend that if you are running a database, you should choose instances that support EBS-optimization or instances that support cluster networking. For applications with high inter-node network requirements, you should choose instances that support cluster networking. Micro instances provide short-lived CPU resources opportunistically and are not recommended for applications that require sustained CPU performance.
For a complete list of instance families, sizes, and specifications of Amazon EC2
instance types please see Amazon EC2 Instance Details
Amazon EC2 instances provide a number of additional features to help you deploy, manage, and scale your applications.
Amazon EC2 allows you to choose between multiple storage options based on your requirements. Amazon EBS is a durable, block-level storage volume that you can attach to a single, running Amazon EC2 instance. You can use Amazon EBS as a primary storage device for data that requires frequent and granular updates. For example, Amazon EBS is the recommended storage option when you run a database on Amazon EC2. Amazon EBS volumes persist independently from the running life of an Amazon EC2 instance. Once a volume is attached to an instance you can use it like any other physical hard drive. Amazon EBS provides two volume types: Standard volumes and Provisioned IOPS volumes. They differ in performance characteristics and price, allowing you to tailor your storage performance and cost to the needs of your applications.
Standard volumes offer storage for applications with moderate or bursty I/O requirements. Standard volumes deliver approximately 100 IOPS on average with a best effort ability to burst to hundreds of IOPS. Standard volumes are also well suited for use as boot volumes, where the burst capability provides fast instance start-up times.
Provisioned IOPS volumes are designed to deliver predictable, high performance for I/O intensive workloads such as databases. With Provisioned IOPS, you specify an IOPS rate when creating a volume, and then Amazon EBS provisions that rate for the lifetime of the volume. Amazon EBS currently supports up to 4000 IOPS per Provisioned IOPS volume. You can stripe multiple volumes together to deliver thousands of IOPS per Amazon EC2 instance to your application.
Many Amazon EC2 instances can also include storage from disks that are physically attached to the host computer. This disk storage is referred to as instance store. Instance store provides temporary block-level storage for Amazon EC2 instances. The data on an instance store volume persists only during the life of the associated Amazon EC2 instance.
In addition to block level storage via Amazon EBS or instance store, you can also use Amazon S3 for highly durable, highly available object storage. Learn more about Amazon EC2 storage options from the Amazon EC2 documentation.
For a low, additional, hourly fee, you can launch selected Amazon EC2 instances types as EBS-optimized instances. EBS-optimized instances deliver dedicated throughput between Amazon EC2 and Amazon EBS, with options for 500 Mbps and 1000 Mbps depending on the instance type used. We recommend using Provisioned IOPS volumes with EBS-optimized instances or instances that support cluster networking for applications with high storage I/O requirements.
CC2, CR1, CG1, HI1, and HS1 instances support cluster networking. Instances launched into a common cluster placement group are placed into a logical cluster that provides high-bandwidth, low-latency networking between all instances in the cluster. Cluster networking is ideal for high performance analytics systems and many science and engineering applications, especially those using the MPI library standard for parallel programming.
Dedicated Instances are Amazon EC2 instances that run on single-tenant hardware dedicated to a single customer. They are ideal for workloads where corporate policies or industry regulations require that your EC2 instances be physically isolated at the host hardware level from instances that belong to other customers. Dedicated Instances let you take full advantage of the benefits of the AWS cloud – on-demand elastic provisioning, pay only for what you use, all while ensuring that your Amazon EC2 compute instances are isolated at the hardware level.
Amazon EC2 allows you to provision a variety of instances types, which provide different combinations of CPU, memory, disk, and networking. Launching new instances and running tests in parallel is easy, and we recommend measuring the performance of applications to identify appropriate instance types and validate application architecture. We also recommend rigorous load/scale testing to ensure that your applications can scale as you intend.
Amazon EC2 provides you with a large number of options across ten different instance types, each with one or more size options, organized into six distinct instance families optimized for different types of applications. We recommend that you assess the requirements of your applications and select the appropriate instance family as a starting point for application performance testing. You should start evaluating the performance of your applications by (a) identifying how your application needs compare to different instance families (e.g. is the application compute-bound, memory-bound, etc.?), and (b) sizing your workload to identify the appropriate instance size. There is no substitute for measuring the performance of your full application since application performance can be impacted by the underlying infrastructure or by software and architectural limitations. We recommend application-level testing, including the use of application profiling and load testing tools and services.
The following table list the specifications for each Amazon EC2 Instance Type:
| Instance Family | Instance Type | Processor Arch | vCPU | ECU | Memory (GiB) | Instance Storage (GB) | EBS-optimized Available | Network Performance |
| General purpose | m1.small |
32-bit or 64-bit |
1 | 1 | 1.7 | 1 x 160 | - | Low |
| General purpose | m1.medium |
32-bit or 64-bit |
1 | 2 | 3.75 | 1 x 410 | - | Moderate |
| General purpose | m1.large | 64-bit | 2 | 4 | 7.5 | 2 x 420 | Yes | Moderate |
| General purpose | m1.xlarge | 64-bit | 4 | 8 | 15 | 2 x 840 | Yes | High |
| General purpose | m3.xlarge | 64-bit | 4 | 13 | 15 | EBS only | Yes | Moderate |
| General purpose | m3.2xlarge | 64-bit | 8 | 26 | 30 | EBS only | Yes | High |
| Compute optimized | c1.medium |
32-bit or 64-bit |
2 | 5 | 1.7 | 1 x 350 | - | Moderate |
| Compute optimized | c1.xlarge | 64-bit | 8 | 20 | 7 | 4 x 420 | Yes | High |
| Compute optimized | cc2.8xlarge | 64-bit | 32 *1 | 88 | 60.5 | 4 x 840 | - | 10 Gigabit *5 |
| Memory optimized | m2.xlarge | 64-bit | 2 | 6.5 | 17.1 | 1 x 420 | - | Moderate |
| Memory optimized | m2.2xlarge | 64-bit | 4 | 13 | 34.2 | 1 x 850 | Yes | Moderate |
| Memory optimized | m2.4xlarge | 64-bit | 8 | 26 | 68.4 | 2 x 840 | Yes | High |
| Memory optimized | cr1.8xlarge | 64-bit | 32 *1 | 88 | 244 |
2 x 120
SSD |
- | 10 Gigabit *5 |
| Storage optimized | hi1.4xlarge | 64-bit | 16 | 35 | 60.5 |
2 x 1,024 SSD*3 |
- | 10 Gigabit *5 |
| Storage optimized | hs1.8xlarge | 64-bit | 16 | 35 | 117 | 24 x 2,048*4 | - | 10 Gigabit *5 |
| Micro instances | t1.micro |
32-bit or 64-bit |
1 | Variable *6 | 0.615 | EBS only | - | Very Low |
| GPU instances | cg1.4xlarge | 64-bit | 16 *2 | 33.5 | 22.5 | 2 x 840 | - | 10 Gigabit *5 |
*1 CC2 and CR1 Instances are backed by 2 x Intel Xeon E5-2670 processors, eight-cores with hyperthreading
*2 CG1 Instances are backed by 2 x Intel Xeon X5570, quad-core with hyperthread plus 2 NVIDIA Tesla M2050 GPUs
*3 HI1 Instances can deliver more than 120,000 4 KB random read IOPS and between 10,000 and 85,000 4 KB random write IOPS (depending on active logical block addressing span) to applications. The maximum sequential throughput on is approximately 2 GB/s read and 1.1 GB/s write.
*4 HS1 Instances can deliver 2.4 GB/s of 2 MB sequential read performance and 2.6 GB/s of sequential write performance.
*5 Instances launched into the same cluster placement group are placed into a non-blocking 10 Gigabit ethernet network
*6 For more information on the Micro instances see the AWS documentation


Usually "GUI" is pronounced "gooey." (Many "gooey" programs run on "eunuchs" systems with "scuzzy" disks.)
All Java GUI classes are based on the fundamental classes in the Application Windowing Toolkit, or AWT. The AWT fundamental classes are also used as the base classes an older set of components (which are usually regarded as part of the AWT). Swing components come with Java release 1.1.2 and later. If you download the most recent release of Java, Swing will be part of it.
The older AWT components are similar to Swing components, but Swing components are more versatile. Also, Swing integrates smoothly with the Java Foundation Classes. The Java Foundation Classes provide many classes needed for modern software development. Sun Microsystems recommends that you use Swing for all new application code.
Warning: you may need to know both AWT and Swing for Java certification. Check for the most recent requirements.


ÁVision Build Log Project: C:\Users\Prashant\Desktop\Experiments\5_ADC_Sensor_Display_on_LCD\ADC_Sensor_Display.uvproj Project File Date: 01/17/2014 Output:


The plot below shows the number of
Susceptible
,
Exposed
,
Infectious
, and
Resistant
individuals over time (in days) as percentages of the entire population.
Equations
Parameters
R
0
:
Latent period \(\left(\frac{1}{\alpha}\right)\):
Infectious period \(\left(\frac{1}{\gamma}\right)\):
Duration of resistance \(\left(\frac{1}{\sigma}\right)\):
Mixing exponent \(\left(\eta\right)\):
Initial susceptibility \(\left(S(t=0)\right)\):
Days:
Upper bound for Y axis:
%


The Better Scientific Software (BSSw) website is an incredible resource for learning about scientific software engineering tutorials, explanations, and best practices on topics such as presented here and much more. Python specific materials are linked on the Python for HPC: Community Materials website.
The official Python documentation online is actually fantastic. The modules from the standard library are well documented and include examples that go into more detail and nuance than covered here.
Discussed libraries:
setuptools
twine
pytest
hypothesis
sphinx
numpy
line_profiler
memory_profiler
numba


Parallax Engine that reacts to the orientation of a smart device. Where no gyroscope or motion detection hardware is available, the position of the cursor is used instead.
Check out the demo to see it in action!
compiled.zip
from the latest releaseparallax.js
and parallax.min.js
filesparallax.js
if you want to snoop around in the codeparallax.min.js
for deployment, because it has a smaller file sizenpm i -s parallax-js
You will then find the source code in node_modules/parallax-js/src/parallax.js
and the browserified, babelified, uglified, production-ready version in node_modules/parallax-js/dist/parallax.min.js
If you use the compiled version, either downloaded from the releases page, or copied from the dist
folder, include the script like any other Javascript library:
Of course, when you've installed via npm, and use browserify/babel, you can also simply do:import Parallax from 'parallax-js'
orconst Parallax = require('parallax-js')
Each Parallax.js instance needs a container element, the scene. You're free to identify it by any means you want, but for now, let's use an ID:

Per default, all direct child elements of the scene will become moving objects, the layers. You can change this to a custom query selector, but again, we're going with the easiest approach for now:

My first Layer!

My second Layer!

While all other options and parameters are optional, with sane defaults, and can be set programatically, each layer needs a data-depth
attribute. The movement applied to each layer will be multiplied by its depth attribute.

My first Layer!

My second Layer!

As soon as your DOM is ready and loaded, you can create a new Parallax.js instance, providing your scene element as first parameter.
var scene = document.getElementById('scene');
var parallaxInstance = new Parallax(scene);
That's it, you're running Parallax.js now!
Most configuration settings can be declared either as data-value attribute of the scene element, or property of the configuration object. The programmatic approach will take priority over the data-value attributes set in the HTML.
Some options can also be set at run-time via instance methods.
Declarative:

My first Layer!

My second Layer!

Programmatic:
var scene = document.getElementById('scene');
var parallaxInstance = new Parallax(scene, {
relativeInput: true
});
Using Methods at Runtime:
parallaxInstance.friction(0.2, 0.2);
Property: relativeInput
Attribute: data-relative-input
Value: boolean
Default: false
Makes mouse input relative to the position of the scene element.
No effect when gyroscope is used.
Property: clipRelativeInput
Attribute: data-clip-relative-input
Value: boolean
Default: false
Clips mouse input to the bounds of the scene. This means the movement stops as soon as the edge of the scene element is reached by the cursor.
No effect when gyroscope is used, or hoverOnly
is active.
Property: hoverOnly
Attribute: data-hover-only
Value: boolean
Default: false
Parallax will only be in effect while the cursor is over the scene element, otherwise all layers move back to their initial position. Works best in combination with relativeInput
.
No effect when gyroscope is used.
Property: inputElement
Attribute: data-input-element
Method: setInputElement(HTMLElement)
Value: null or HTMLElement / String
Default: null
Allows usage of a different element for cursor input.
The configuration property expects an HTMLElement, the data value attribute a query selector string.
Will only work in combination with relativeInput
, setting hoverOnly
might make sense too.
No effect when gyroscope is used.
Property: calibrateX & calibrateY
Attribute: data-calibrate-x & data-calibrate-y
Method: calibrate(x, y)
Value: boolean
Default: false for X, true for Y
Caches the initial X/Y axis value on initialization and calculates motion relative to this.
No effect when cursor is used.
Property: invertX & invertY
Attribute: data-invert-x & data-invert-y
Method: invert(x, y)
Value: boolean
Default: true
Inverts the movement of the layers relative to the input. Setting both of these values to false will cause the layers to move with the device motion or cursor.
Property: limitX & limitY
Attribute: data-limit-x & data-limit-y
Method: limit(x, y)
Value: false or integer
Default: false
Limits the movement of layers on the respective axis. Leaving this value at false gives complete freedom to the movement.
Property: scalarX & scalarY
Attribute: data-scalar-x & data-scalar-y
Method: scalar(x, y)
Value: float
Default: 10.0
Multiplies the input motion by this value, increasing or decreasing the movement speed and range.
Property: frictionX & frictionY
Attribute: data-friction-x & data-friction-y
Method: friction(x, y)
Value: float between 0 and 1
Default: 0.1
Amount of friction applied to the layers. At 1 the layers will instantly go to their new positions, everything below 1 adds some easing.
The default value of 0.1 adds some sensible easing. Try 0.15 or 0.075 for some difference.
Property: originX & originY
Attribute: data-origin-x & data-origin-y
Method: origin(x, y)
Value: float between 0 and 1
Default: 0.5
X and Y origin of the mouse input. The default of 0.5 refers to the center of the screen or element, 0 is the left (X axis) or top (Y axis) border, 1 the right or bottom.
No effect when gyroscope is used.
Property: precision
Attribute: data-precision
Value: integer
Default: 1
Decimals the element positions will be rounded to. 1 is a sensible default which you should not need to change in the next few years, unless you have a very interesting and unique setup.
Property: selector
Attribute: data-selector
Value: null or string
Default: null
String that will be fed to querySelectorAll on the scene element to select the layer elements. When null, will simply select all direct child elements.
Use .layer
for legacy behaviour, selecting only child elements having the class name layer.
Property: pointerEvents
Attribute: data-pointer-events
Value: boolean
Default: false
Set to true to enable interactions with the scene and layer elements. When set to the default of false, the CSS attribute pointer-events: none
will be applied for performance reasons.
 You have to either set position: absolute
on all layer child elements, or keep pointerEvents at false and set pointer-events: all
for the interactable elements only.
Property: onReady
Value: null or function
Default: null
Callback function that will be called as soon as the Parallax instance has finished its setup. This might currently take up to 1000ms (calibrationDelay * 2
).
In addition to the configuration methods outlined in the section above, there are a few more publicly accessible methods:
Enables a disabled Parallax instance.
Disables a running Parallax instance.
Completely destroys a Parallax instance, allowing it to be garbage collected.
Returns the version number of the Parallax library.
git clone git@github.com:wagerfield/parallax.git
cd parallax
npm install
gulp watch
If you need help relating the direct usage of this library in a project of yours, provide us with a working, running example of your work. This can be a GitHub repository, a ZIP file containing your work, a project on CodePen or JSFiddle, you name it.
Do not complain about something not working without giving us some way to help you. Thank you!
It seems MS Edge does not support the children
or querySelectorAll
methods for SVG elements.
jQuery will not prevent you from using this library in any way. If you want to use jQuery for selecting your Parallax scene element, you can do so too.
var scene = $('#scene').get(0);
var parallaxInstance = new Parallax(scene);
Check out the section on the configuration option pointerEvents
above.
Either download compiled_with_examples.zip from the GitHub Releases section, or follow section 4.1
This project is licensed under the terms of the MIT License. Enjoy!
Matthew Wagerfield: @wagerfield
René Roth: Website


Home
Results
Submit Park
Login / Register
Search
Sign Up for Access!
Email
Password
Address
Phone Number
Province
Select
Ontario
British Columbia
Quebec
Saskatchewan
P.E.I
Nova Scotia
New Brunswick
Alberta
Newfoundland & Labrador
Manitoba
Yukon
Northwest Territories
Nunavut
Date of Birth
Sign Up


--- title: "UI Colors" type: colors scss: _assets/stylesheets/_variables.scss usage: "Colors used to give the site its base flavor." ---
$background-color
$body-color
$text-color
$caption-color
$link-color
$link-color-hover
$border-color


(Supplementary material for the ISMIR 2021 submission)
All samples are synthesized using FluidSynth with the MuseScore General soundfont.
Shortcuts to examples on paper:
Figure 1,
Figure 2,
Figure 3,
Figure 4,
Figure 5,
Figure 6
Shortcuts to random samples:
Bach chorales,
string quartets,
game music,
pop music
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: piano, guitar, bass, strings, brass.)
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: first violin, second violin, viola, cello.)
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: soprano, alto, tenor, bass.)
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: pulse wave I, pulse wave II, triangle wave.)
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: piano, guitar, bass, strings, brass.)
| Mixture (input) | ||
| Ground truth | ||
| Online LSTM prediction | ||
| Offline BiLSTM prediction |
(Colors: piano, guitar, bass, strings, brass.)
(The following five samples are randomly chosen from the test set. Abbreviations: emb.–pitch, time, beat embedding, dur.–duration input, e.h.–entry hints.)
Tracks: soprano, alto, tenor, bass
| Ich freue mich in dir (BWV 133) |
Wo Gott der Herr nicht bei uns hält (BWV 258) |
Ich hab mein Sach Gott heimgestellt (BWV 351) |
Jesu, meine Freude (BWV 358) |
Nicht so traurig, nicht so sehr (BWV 384) |
|
|---|---|---|---|---|---|
| Mixture (input) | |||||
| Ground truth | |||||
| Zone-based | |||||
| Closest-pitch | |||||
| Closest-pitch (mono) | |||||
| LSTM (+emb.) | |||||
| LSTM (+emb. +e.h.) | |||||
| BiLSTM (+emb.) | |||||
| BiLSTM (+emb. +e.h. +dur.) |
(The following five samples are randomly chosen from the test set. Abbreviations: emb.–pitch, time, beat embedding, dur.–duration input, e.h.–entry hints.)
Tracks: violin I, violin II, viola, cello
| Mozart's String Quartet No. 14 (G major, K. 387, Movement 1) |
Dvořák's String Quartet No. 10 (E-flat, Op.51, Movement 4) |
Dvořák's String Quartet No. 12 (F major, Op. 96, Movement 2) |
Ravel's String Quartet in F (Movement 2) |
Beethoven's String Quartet No. 15 (A minor, Movement 2) |
|
|---|---|---|---|---|---|
| Mixture (input) | |||||
| Ground truth | |||||
| Zone-based | |||||
| Closest-pitch | |||||
| Closest-pitch (mono) | |||||
| LSTM (+emb.) | |||||
| LSTM (+emb. +e.h.) | |||||
| BiLSTM (+emb.) | |||||
| BiLSTM (+emb. +e.h. +dur.) |
(The following five samples are randomly chosen from the test set. Abbreviations: emb.–pitch, time, beat embedding, dur.–duration input, e.h.–entry hints.)
Tracks: pulse wave I, pulse wave II, triangle wave
| Booby March (from Booby Kids) |
To Be Continued (from Golgo 13: Top Secret Episode) |
William's Theme (from Murder on the Mississippi) |
Pattern Clear (from Quarth) |
Break Time (from VS Duck Hunt) |
|
|---|---|---|---|---|---|
| Mixture (input) | |||||
| Ground truth | |||||
| Zone-based | |||||
| Closest-pitch | |||||
| Closest-pitch (mono) | |||||
| LSTM (+emb.) | |||||
| LSTM (+emb. +e.h.) | |||||
| BiLSTM (+emb.) | |||||
| BiLSTM (+emb. +e.h. +dur.) |
(The following five samples are randomly chosen from the test set. Abbreviations: emb.–pitch, time, beat embedding, dur.–duration input, e.h.–entry hints.)
(Note: This dataset is rather noisy due to instrument mapping. Oftentimes, melody track is missing.)
Tracks: piano, guitar, bass, strings, brass
| Alt wie ein Baum (by Puhdys) |
Wide Open Spaces (by The Chicks) |
Children Of Paradise (by Boney M.) |
We will rock you (by Queen) |
Encore Une Fois (by Sash!) |
|
|---|---|---|---|---|---|
| Mixture (input) | |||||
| Ground truth | |||||
| Zone-based | |||||
| Closest-pitch | |||||
| Closest-pitch (mono) | |||||
| LSTM (+emb.) | |||||
| LSTM (+emb. +e.h.) | |||||
| BiLSTM (+emb.) | |||||
| BiLSTM (+emb. +e.h. +dur.) |


|
|
| AbstractSceneObject (const AbstractSceneObject &obj) |
| |
|
AbstractSceneObject & | operator= (const AbstractSceneObject &obj) |
| |
|
virtual const ModelBounds & | bounds () const =0 |
| |
|
virtual const Matrix4x4 & | transform () const =0 |
| |
|
bool | isVisible () const |
| |
|
void | setVisible (bool v) |
| |
|
virtual float | x () const =0 |
| |
|
virtual float | y () const =0 |
| |
|
virtual float | z () const =0 |
| |
|
virtual float | sizeX () const =0 |
| |
|
virtual float | sizeY () const =0 |
| |
|
virtual float | sizeZ () const =0 |
| |
|
virtual float | radius () const =0 |
| |
The documentation for this class was generated from the following file:


I’m Dan. I live in Chicago, ride bikes, make things from fabric, put things on maps, and write code. I work for the Delta Institute in Chicago.
This space is part experiment, documentation, memory aid, and sounding board. Development is ongoing and you can follow along or submit an issue on GitHub.
Because whether it’s computers, bicycles, craft beer or home appliances, everybody loves specs.
You can get a hold of me via:
If you’re looking for info on Maptime Chicago, try contacting me through one of the above channels or via one of Maptime Chicago’s more official channels:
Thanks!


---
creation_epoch:<PHONE_NUMBER>
lastmod_epoch:<PHONE_NUMBER>
categories: ['Computer Problems']
title: Boot USB drive on older BIOS
---
Some older BIOS have early USB boot support, but it doesn't alway seem to work.
I have a EliteGroup K7S5A Pro motherboard that detects a 1GB USB flash drive as "USB-RFD" that will not boot from a normally formatted and partitioned USB drive. I found the following solutions to handle older BIOS with legacy USB boot methods.
BIOS settings to use:
- USB Function Support = Enabled
- USB Function for DOS = Disabled
- Thumb = Disabled
- Hit F8 to bring up the boot menu or configure it in your bios if you like
Making the USB drive bootable:
- Plug the USB drive into a Linux machine
- Wipe the drive with dd if=/dev/zero of=/dev/sdX bs=64k
- mkdiskimage -4 /dev/sdX 0 64 32
- This creates a single partition as the "4th" partition which allows the older BIOS to boot the usb drive like a ZIP drive which it expects since it uses an older boot method
- You can also use another partition program and mkfs just make sure to create it as the 4th partition with 64 heads, 32 sectors
- mkfs.msdos /dev/sdX4 (Important that it is made FAT16)
- syslinux /dev/sdX4 to make it bootable


Members page permits active or registered user visualization/exploration and several types of search on SPOD platform.
There are three sections to explore the users including: All, On line and Search.
1
All
This page shows all users who signed up on the SPOD platform.
2
Online
On line page shows only users online on SPOD platform.
3
Search
Search page allows search of users by name or gender.


THE HANGING GARDEN
A Film Review by James Berardinelli
RATING: *** OUT OF ****
Canada, 1997 U.S. Release Date: 6/98 (limited) Running Length: 1:31 MPAA Classification: R (Profanity, sexuality, mature themes) Theatrical Aspect Ratio: 1.85:1
Cast: Chris Leavins Troy Veinotte, Kerry Fox, Peter MacNeill, Sarah Polley, Seana McKenna, Joel S. Keller, Joan Orenstein, Christine Dunsworth Director: Thom Fitzgerald Producers: Thom Fitzgerald, Louise Garfield, Arnie Gelbart Screenplay: Thom Fitzgerald Cinematography: Daniel Jobin Music: Ashley MacIsaac, Heather Rankin U.S. Distributor: Goldwyn Films
THE HANGING GARDEN was one of the hottest films to be shown at the 1997 Toronto International Film Festival. Not only was it the centerpiece of the "Perspective Canada" series, but it packed its first critics' screening and took home two prestigious prizes: the Toronto City Award for the Best Canadian First Feature and the Air Canada People's Choice Award for the Most Popular Film. While I'm not sure that the picture deserves the full share of praise heaped upon it at the festival, there's no denying that it's a fine, fascinating debut effort from director Thom Fitzgerald.
THE HANGING GARDEN dissects one of the most dysfunctional families ever to appear on the silver screen. It is by turns engrossing, horrifying, shocking, eccentric, and pretentious. In order to tell the entire story, the film moves back and forth through three different time frames. There are overlaps in the periods, with characters from the past slipping into their future. It's up to the viewer to determine whether they're real or imaginary – ghosts or physical embodiments of guilt and responsibility. THE HANGING GARDEN opens in the present, with the wedding of Rosemary (Kerry Fox, last seen in WELCOME TO SARAJEVO) and Fletcher (Joel S. Keller). It also marks the return home of Sweet William (Chris Leavens), Rosemary's brother, after a lengthy absence. William's appearance – he's thin and handsome – surprises everyone, since, when he left home as a teenager, he was grossly overweight. Now, having started a new life away from his abusive father, he has learned to embrace his homosexuality and to like himself. Also on hand for the wedding are the abusive father, Mac (Peter MacNeill); Rosemary and William's mother, Iris (Seana McKenna); their dotty old grandmother, Grace (Joan Orenstein); and their little sister, tomboy Violet (Christine Dunsworth).
Before long, images from the past rise up to haunt William.  Fearing that he might not be "normal," Iris arranged for him to have intercourse with a local woman who was willing, for a little money, to act as an instructor. Meanwhile, Mac's attitude toward his son was shaped by the typical unpredictability of an alcoholic father – loving one moment, violent the next. Only William's closeness with Rosemary (Sarah Polley, of THE SWEET HEREAFTER) kept him sane.
THE HANGING GARDEN is brimming with symbolism. Most of the characters – Sweet William, Rosemary, Violet, Iris – are named after the plants that grow in the family's extensive, well-groomed garden. Each of the names says something significant about the person who bears it. Sweet William is vulnerable, Rosemary is biting, Violet is resilient, and Iris is proud and regal. There's also a great deal of religious imagery, most of which is used to emphasize guilt (especially William's concerning his sexual urges). On a number of occasions, the eyes of a Virgin Mary statue are seen to move.
THE HANGING GARDEN is not plot intensive, although the story offers at least one unexpected revelation (we anticipate a "surprise" concerning this plot element, but not the one that comes to light). Rather, it's about the characters -- how they interact and how the consequences of long-age actions have irrevocably altered their personalities. From her teen years into her twenties, Rosemary has remained the same person (the performances of Fox and Polley, who work to match their presentations of Rosemary's mannerisms and personality, allow us to always see the character, not the actresses). Sweet William, on the other hand, is vastly different in appearance, confidence level, and his ability to cope with the misery of his adolescent existence. The watershed moment in William's life is THE HANGING GARDEN's central mystery. Fitzgerald handles all of this difficult material like a pro (only occasionally going overboard with flashes of pretentiousness), displaying a distinctive visual style, and injecting a fair amount of humor into what is, in essence, a tragic tale about abuse, misunderstanding, and love gone awry. THE HANGING GARDEN is a memorable debut.
Copyright 1998 James Berardinelli
- James Berardinelli e-mail<EMAIL_ADDRESS>Now with more than 1400 reviews... The ReelViews web site: http://movie-reviews.colossus.net/
"My belief is that no movie, nothing in life, leaves people neutral.
-- David Puttnam
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


- 创建一个链上广告 See how it works
-
合约TX ID 部署地址
ATP will be the first application level protocol to be built on Nebulas Blockchain, allowing all participants involved to benefit from decentralized digital marketing.
Nebulas is a next generation public blockchain, capable of providing Decentralized Search Engine Framework for data on blockchain. ATP will utilize Nebulas technology of Nebulas Rank (NR) and Developer Incentive Protocol (DIP).
Token Sale
Traffic Flow
Ads Platform
Game Distribution
Tiefeng Liu
Founder & CTO
Leiyu Liu
Co-founder & VP of Operation
Jin Tong
Partner, Senior Product Managing Director
Ming Jiang
Senior R&D Director


The purpose of this protocol is to provide a wire format for implementing a binary request/response communication interface, such as that of the Jini ERInet.jini.jeri.connection.ConnectionManager
net.jini.jeri.connection.ServerConnectionManager
net.jini.jeri.tcp.TcpEndpoint
net.jini.jeri.tcp.TcpServerEndpoint
net.jini.jeri.ssl.SslEndpoint
net.jini.jeri.ssl.SslServerEndpoint
net.jini.jeri.kerberos.KerberosEndpoint
net.jini.jeri.kerberos.KerberosServerEndpoint
OutboundRequest
and InboundRequest
interfaces, on top of a bi-directional byte stream connection.
The intended application of this protocol is to communicate Jini ERI
remote method invocations over TCP and similar connection-oriented
transport protocols, as well as over layered application-level
protocols that can provide a connection-oriented byte stream
interface.
OutboundRequest
and InboundRequest
interfaces
Items in the protocol are of the following simple types:
The client may use the connection to send requests to the server and receive responses in reply. The server may use the connection to receive requests and send responses in reply. (Note that the terms "client" and "server" in this page are only used as convenient labels to distinguish the two endpoints of the asymmetric connection over which this protocol operates; they do not necessarily correspond to higher-level application concepts of "client" and "server".)
How the connection is established is outside the scope of this protocol. A typical model, however, is for the server to passively listen on a network address for incoming connections and to publish that address to clients, and for the client to actively attempt to connect to the server at the published address; if the server accepts the connection, this protocol may then commence over the established connection.
A message comprises a four-byte header optionally followed by more data, depending on the type of the message. The first byte of the message header defines the type of the message. Message types fall into two general categories: messages that pertain to the connection as a whole, which begin with a byte in the range 0-0xF, and messages that pertain to a particular session, which begin with a byte in the range 0x10-0xFF.
The following table lists the allowed ranges of values for the first byte of a message header, and what message type each range corresponds to. The value ranges are listed as both bit patterns, in which x represents a bit that may be either 0 or 1 for the given message type, and in hexadecimal, in which two hyphen-separated values indicate an inclusive range. Some of the hexadecimal ranges include more values than are legally allowed for the given message type, but the bit pattern range specifies the allowed values exactly.
It is a protocol violation to send a message with a first byte that does not match one of the above bit patterns.
bit pattern hexadecimal range message type 00000000 00 NoOperation 00000010 02 Shutdown 00000100 04 Ping 00000110 06 PingAck 00001000 08 Error 0001xxx0 10-1F IncrementRation 001000x0 20-23 Abort 00110000 30 Close 01000000 40 Acknowledgment 100xxxx0 80-9F Data
A session may be either established or terminated with respect to either endpoint. A session established with respect to an endpoint may also be finished with respect to that endpoint, meaning that the endpoint is finished sending data for that session. These and other session state changes occur as a result of messages sent for the associated session identifier.
For any transmitted message that affects the state of a session, the state change is clearly known first to the sender of the message (when the message is sent), and later to the receiver (when the message is received). All restrictions on what messages may be sent relating to the current state of a session require that there is some interleaved order of messages received and messages sent by a given endpoint for which the restrictions are satisfied.
A session is established with respect to both endpoints when the client sends a Data message with the open flag set. The newly established session is associated with the session identifier contained in the message header. A session remains established with respect to a given endpoint until it becomes terminated with respect to that endpoint.
An established session is finished with respect to a given endpoint after the endpoint has sent a Data message with the eof flag set for the associated session identifier. A session finished with respect to a given endpoint still remains established with respect to that endpoint (and data still can be received) until it becomes terminated with respect to the endpoint. Note that a session can become both established and finished from a single Data message sent from the client, if both the open and the eof flags are set.
The client may re-use a session identifier for establishing a new session after the previous session associated with that session identifier is terminated with respect to the client and the server, or after it is terminated with respect to the server and the client has sent a Data message with the eof flag set with the session identifier (after which the previous session associated with the session identifier becomes implicitly terminated with respect to the client).
Each endpoint has two state values associated with each session:
When a session is first established, the client's inbound ration is the value that the client sent in the ClientConnectionHeader for the connection, and the client's outbound ration is the value that the server sent in the ServerConnectionHeader for the connection (although it will likely be immediately decremented by the length value of the Data message used to establish the session). Also, the server's outbound ration is the value that the client sent in the ClientConnectionHeader for the connection, and the server's inbound ration is the value that the server sent in the ServerConnectionHeader for the connection (although it will likely be immediately decremented by the length value of the Data message used to establish the session).
An endpoint's outbound ration for a session is incremented when it receives an IncrementRation message for that session with a non-zero increment, and it is decremented when it sends a Data message for that session with a non-zero length. An endpoint's inbound ration for a session is incremented when it sends an IncrementRation message for that session with a non-zero increment, and it is decremented when it receives a Data message for that session with a non-zero length. It is a protocol violation for an endpoint to send a Data message with a length value greater than its current outbound ration.
The sequence of messages sent by the server ends with a Shutdown message, an Error message, or closure of the connection's stream from the server. The sequence of messages sent by the client ends with an Error message or closure of the connection's stream from the client.
initialRation: 16-bit integerA ClientConnectionHeader message must and must only be sent by the client, as the first message of this protocol over the connection.
For all newly established sessions, the client's initial inbound ration and the server's initial outbound ration will be (initialRation * 256) if initialRation is non-zero, or infinity if initialRation is zero.
(If the server receives an invalid ClientConnectionHeader message, the server should respond with an Error message following the ServerConnectionHeader message.)
The structure of a ClientConnectionHeader message is 8 bytes as follows:
offset bit pattern content 0 to 3 01001010
01101101
01110101
01111000
magic number (ASCII "Jmux") 4 00000001
version 5 to 6 xxxxxxxx
xxxxxxxx
initialRation 7 00000000
reserved
initialRation: 16-bit integerA ServerConnectionHeader message must and must only be sent by the server, as the first message of this protocol over the connection.
For all newly established sessions, the server's initial inbound ration and the client's initial outbound ration will be (initialRation * 256) if initialRation is non-zero, or infinity if initialRation is zero.
The structure of a ServerConnectionHeader message is 8 bytes as follows:
offset bit pattern content 0 to 3 01001010
01101101
01110101
01111000
magic number (ASCII "Jmux") 4 00000001
version 5 to 6 xxxxxxxx
xxxxxxxx
initialRation 7 00000000
reserved
length: 16-bit integerA NoOperation message may be sent by the client or the server. A NoOperation message should be ignored by the receiver.
data: sequence of length bytes
The structure of a NoOperation message is (4+length) bytes as follows:
offset bit pattern content 0 00000000
NoOperation message type identifier 1 00000000
reserved 2 to 3 xxxxxxxx
xxxxxxxx
length 4 to (4+length-1) n/a data
A Shutdown message contains the following variable items:
length: 16-bit integerThe Shutdown message is used to indicate that the server is shutting down the connection in a graceful fashion.
detail: sequence of length bytes
A Shutdown message must only be sent by the server.
By definition, a Shutdown message is the last message of the protocol sent by the server over the connection; after sending a Shutdown message, the server will typically close the connection.
When the client receives a Shutdown message, it should discard the connection and consider all established sessions that were not finished with respect to the server as if they have been aborted (as with an Abort message) with no partial processing-- thus the client can safely retry such sessions on another connection without violating at most once execution semantics. Therefore, the server must only send a Shutdown message if it can guarantee that no currently established sessions have been processed with any possible side effects.
The server can use the detail item to provide the client with more information explaining the reason for the Shutdown message. The content of the detail item, if any, is a UTF-8 encoded string of unspecified content.
The structure of a Shutdown message is (4+length) bytes as follows:
offset bit pattern content 0 00000010
Shutdown message type identifier 1 00000000
reserved 2 to 3 xxxxxxxx
xxxxxxxx
length 4 to (4+length-1) n/a detail
A Ping message contains the following variable items:
cookie: 16-bit integerThe Ping message is used to test the liveness of the receiver.
A Ping message may be sent by the client or the server.
The sender may choose any arbitrary value for cookie. After sending a Ping message, the sender can expect the receiver to respond with exactly one corresponding PingAck message containing the same cookie value. The sender may expect the corresponding PingAck within a reasonable timeout, and if it is not received, the sender may consider the receiver to have gone down or become unreachable (such as due to a network partition), in which case it should discard the connection and consider all open sessions aborted (with partial processing, if the sender is the client).
The structure of a Ping message is 4 bytes as follows:
offset bit pattern content 0 00000100
Ping message type identifier 1 00000000
reserved 2 to 3 xxxxxxxx
xxxxxxxx
cookie
cookie: 16-bit integerThe PingAck message is used to respond to a Ping message.
A PingAck message may be sent by the client or the server, and must only be sent in response to exactly one previous Ping message received by the sender.
After receiving a Ping message with a given cookie value, an endpoint should immediately respond with a PingAck message with the same cookie value.
The structure of a PingAck message is 4 bytes as follows:
offset bit pattern content 0 00000110
PingAck message type identifier 1 00000000
reserved 2 to 3 xxxxxxxx
xxxxxxxx
cookie
length: 16-bit integerThe Error message is used to indicate that the sender has detected a protocol violation somewhere in the messages that it has received.
detail: sequence of length bytes
An Error message may be sent by the client or the server.
By definition, an Error message is the last message of the protocol sent by the sender over the connection; after sending an Error message, the sender will typically close the connection.
When the client receives an Error message, it should discard the connection and consider all established sessions that were not finished with respect to the server as if they have been aborted (as with an Abort message) with possible partial processing-- thus the client cannot safely retry such sessions on another connection without violating at most once execution semantics.
When the server receives an Error message, it should discard the connection and consider all established sessions as if they have been aborted.
The sender can use the detail item to provide the receiver with more information explaining the reason for the Error message. The content of the detail item, if any, is a UTF-8 encoded string of unspecified content.
The structure of an Error message is (4+length) bytes as follows:
offset bit pattern content 0 00001000
Error message type identifier 1 00000000
reserved 2 to 3 xxxxxxxx
xxxxxxxx
length 4 to (4+length-1) n/a detail
shift: 3-bit integerThe IncrementRation message is used to indicate that more data can be received by the sender for a given session.
sessionID: 7-bit integer
increment: 16-bit integer
An IncrementRation message may be sent by the client or the server. The sessionID must identify a session established with respect to the sender. (In other words, the client must not send an IncrementRation message after sending an Abort message for the given session, and the server must not send an IncrementMessage after sending a Close or an Abort message for the given session.)
An IncrementRation message indicates that the sender is prepared to receive (increment<<(shift*2)) more bytes for the session beyond its current inbound ration for the session identified by sessionID. After sending an IncrementRation message, the sender's inbound ration for the session is incremented by (increment<<(shift*2)), and after receiving an IncrementRation message, the receiver's outbound ration is incremented by (increment<<(shift*2)). It is a protocol violation for an IncrementRation message to cause the sender's inbound ration to exceed 0x7FFFFFFF. (Therefore, if the receiver's outbound ration is caused to exceed 0x7FFFFFFF, the receiver should respond with an Error message.)
If the session is finished (or terminated) with respect to the receiver, this message should be ignored.
For a given session, if an endpoint is expecting more data from the other endpoint but its inbound ration is zero, then it must send an IncrementRation message (with a non-zero increment) for that session.
The structure of an IncrementRation message is 4 bytes as follows:
offset bit pattern content 0 0001----
IncrementRation message type identifier 0 ----xxx-
shift 0 -------0
reserved 1 0-------
reserved 1 -xxxxxxx
sessionID 2 to 3 xxxxxxxx
xxxxxxxx
increment
partial: flagThe Abort message is used to terminate a session abruptly, usually before its expected exchange of data has completed.
sessionID: 7-bit integer
length: 16-bit integer
detail: sequence of length bytes
An Abort message may be sent by the client or the server. The partial flag must only be set when the sender is the server. The sessionID must identify a session established with respect to the sender.
An Abort message causes the session to be terminated with respect to the sender; the sender must not send any further messages for the session.
If the session is not yet terminated with respect to the receiver, then the receiver should cease sending messages for the session, except to respond in a timely fashion with an Abort message for the session so that it will be terminated with respect to the receiver.
If the client receives an Abort message with the partial flag set, then it must assume that any data sent over the session has been at least partially processed with any possible side effects-- thus the client cannot safely retry the session again without violating at most once execution semantics. If the client receives an Abort message with the partial flag not set, then it may assume that no data sent over the session has been even partially executed with any possible side effects-- thus the client can safely retry the session again without violating at most once execution semantics. Therefore, the server must only send an Abort message with the partial flag not set if it can guarantee that no amount of the data received for the session has been processed with any possible side effects.
The sender can use the detail item to provide the receiver with more information explaining the reason for the Abort message. The content of the detail item, if any, is a UTF-8 encoded string of unspecified content.
The structure of an Abort message is (4+length) bytes as follows:
offset bit pattern content 0 001000--
Abort message type identifier 0 ------x-
partial 0 -------0
reserved 1 0-------
reserved 1 -xxxxxxx
sessionID 2 to 3 xxxxxxxx
xxxxxxxx
length 4 to (4+length-1) n/a detail
sessionID: 7-bit integerThe Close message is used to indicate that the server is done with a particular session in the normal fashion.
A Close message must only be sent by the server. The sessionID must identify a session finished (but established) with respect to the server.
A Close message causes the session to be terminated with respect to the server; the server must not send any further messages for the session.
The server should send a Close message in a timely fashion after the session is finished with respect to the server and either finished with respect to the client or the server is not interested in the remainder of the request data, so that the client may reuse the session identifier. When possible, the server should use the abbreviated form of the Close message: the close flag of the Data message.
If the session is finished (or terminated) with respect to the client, then after receipt of a Close message for the session, the client may reuse the session identifier.
If the session is not yet terminated with respect to the client, then the client should cease sending messages for the session, except to respond in a timely fashion with an Abort message for the session so that it will be terminated with respect to the client as well, and then the client may reuse the session identifier. Note that in this case, the client must not consider the session to have failed; instead, it must provide the data received as the complete response, and it should consider that the server is not interested in the remainder of the request data, so it should be silently discarded.
The structure of a Close message is 4 bytes as follows:
offset bit pattern content 0 00110000
Close message type identifier 1 0-------
reserved 1 -xxxxxxx
sessionID 2 to 3 00000000
00000000
reserved
sessionID: 7-bit integerThe Acknowledgment message is used to indicate that the client is done processing the complete response data for a particular session.
An Acknowledgment message must only be sent by the client. The sessionID must identify a session established with respect to the client. An Acknowledgment must only be sent after the server has sent a Data message with the ackRequired flag set for the session, and it must only be sent once for the session.
Upon receipt of an Acknowledgment message, the server may consider that the client has finished processing the response.
The structure of an Acknowledgment message is 4 bytes as follows:
offset bit pattern content 0 01000000
Acknowledgment message type identifier 1 0-------
reserved 1 -xxxxxxx
sessionID 2 to 3 00000000
00000000
reserved
open: flagThe Data message is used by the client to establish a session, by the client or the server to transmit fragments of data for a session and to signal the end of data for a session, and by the server to terminate the session and to request an acknowledgment for complete processing of the data sent.
eof: flag
close: flag
ackRequired: flag
sessionID: 7-bit integer
length: 16-bit integer
data: sequence of length bytes
A Data message may be sent by the client or the server. The open flag must only be set when the sender is the client, and the close and ackRequired flags must only be set when the sender is the server. The close and the ackRequired flags must only be set if the eof flag is also set.
If the open flag is not set, then sessionID must identify a session established and not finished with respect to the sender. If the open flag is set, then sessionID must not identify an established session, and a new session is established associated with the session identifier sessionID.
The data of the message represents the next fragment of data that constitutes the request data (if sent by the client) or the response data (if sent by the server) of the session. It is a protocol violation for an endpoint to send a Data message with a length value greater than its current outbound ration for the session. (Therefore, if the receiver's inbound ration is less than length, the receiver should respond with an Error message.) After sending a Data message, the sender's outbound ration is decremented by length, and after receiving a Data message, the receiver's inbound ration is decremented by length.
The eof flag marks this message as containing the last fragment of data for the session, and thus the request or response data has been completely transmitted and the session is finished with respect to the sender.
The meaning of the close flag being set is equivalent to the meaning of the same Data message sent without the close flag being set immediately followed by a Close message with the same sessionID.
The ackRequired flag indicates that the server is interested in being notified with a positive acknowledgment when the client is done processing the response data for the session. Such a positive acknowledgment takes the form of an Acknowledgment message received from the client with the same sessionID. If instead the server receives an Abort message with the same sessionID, or the server receives a Data message with the open flag set and the same sessionID, or the connection is closed, then that constitutes a negative acknowledgment (as a positive acknowledgment could never be received).
After the client has received a Data message with the ackRequired flag set, it should send an Acknowledgment message with the same sessionID in a timely fashion after it is done processing the response data.
The structure of a Data message is (4+length) bytes as follows:
offset bit pattern content 0 100-----
Data message type identifier 0 ---x----
open 0 ----x---
close 0 -----x--
eof 0 ------x-
ackRequired 0 -------0
reserved 1 0-------
reserved 1 -xxxxxxx
sessionID 2 to 3 xxxxxxxx
xxxxxxxx
length 4 to (4+length-1) n/a data


These icons are supposed to be square, but only one attribute is set in
stylesheet:
If both attributes are set in stylesheet, icon scales correctly:
These icons are square in modern browsers, but fail in Internet Explorer,
which is unfortunately still used by enough people to support it. You can use
this method, but better just avoid it:


Some of my favorite t-shirts to have stood the test of time.
Read More →Just a quick recipe for those cold winter evenings.
Read More →Diving into the skincare products I'm currently enjoying.
Read More →After spending a year living in Portland, I've updated my original city guide with my current favorite spots in the area.
Read More →It's that time of year again. Here's a list of items on my wish list along with some personal favorites to spark some gift ideas this holiday season.
Read More →