Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
CSS is a language for describing the rendering of structured documents
(such as HTML and XML) on screen, on paper, in speech, etc. This module
contains the features of CSS level 3 relating to the <image> type
and replaced elements. It includes and extends the functionality of CSS
level 2 [CSS21], which builds on CSS
level 1 [CSS1].
The main extensions compared to level 2 are the generalization of the
<url> type to the <image> type, several additions to the ‘<image>
’ type, a
generic sizing algorithm for images and other replaced content in CSS, and
several properties controlling the interaction of replaced elements and
CSS's layout models.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
A Candidate Recommendation is a document that has been widely reviewed and is ready for implementation. W3C encourages everybody to implement this specification and return comments. The (archived) public mailing list<EMAIL_ADDRESS>(see instructions) is preferred for discussion of this specification. When sending e-mail, please put the text “css3-images” in the subject, preferably like this: “[css3-images] …summary of comment…”
Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by the CSS Working Group (part of the Style Activity).
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is based on the Last Call Working Draft (12 January 2012) and includes changes that reflect the outcome of the disposition of comments.
Before the specification can progress to Proposed Recommendation, the CR exit criteria must be met. The specification will not become Proposed Recommendation before 15 October 2012. A test suite and an implementation report will be made during the Candidate Recommendation period.
The following features are at risk: …
object-fit
’, ‘object-position
’, ‘image-orientation
’, and ‘image-resolution
’ properties
This section is not normative.
In CSS Levels 1 and 2, image values, such as those used in the
‘background-image
’ property, could
only be given by a single URL value. This module introduces additional
ways of representing 2D images, for example as a
list of URIs denoting fallbacks,
or
as a gradient.
This module also defines several properties for manipulating raster images and for sizing or positioning replaced elements such as images within the box determined by the CSS layout algorithms. It also defines in a generic way CSS's sizing algorithm for images and other replaced elements.
This module defines and extends the ‘<image>
’ value type defined in [CSS3VAL].
Furthermore it replaces the ‘<url>
’
type in the ‘background-image
’ and
‘list-style-image
’ definitions in
CSS1 and CSS2 and adds ‘<image>
’ as an alternative to ‘<url>
’ in the ‘content
’ property's value. It is presumed that
CSS specifications beyond CSS2.1 will use the ‘<image>
’ notation
in place of ‘<url>
’ where 2D images
are expected. (See e.g. [CSS3BG].)
Of the properties defined in this module, only ‘image-resolution
’ applies to
::first-line
and ::first-letter
.
This specification follows the CSS property definition conventions from [CSS21]. Value types not defined in this specification are defined in CSS Level 2 Revision 1 [CSS21]. Other CSS modules may expand the definitions of these value types: for example [CSS3COLOR], when combined with this module, expands the definition of the <color> value type as used in this specification.
In addition to the property-specific values listed in their definitions, all properties defined in this specification also accept the inherit keyword as their property value. For readability it has not been repeated explicitly.
This specification defines the following units as part of the <resolution> value type:
dpi
’
dpcm
’
dppx
’
px
’ unit
The ‘<resolution>
’ unit represents the size of a
single "dot" in a graphical representation by indicating how many of these
dots fit in a CSS ‘in
’,
‘cm
’, or ‘px
’. For uses, see e.g. the ‘resolution
’ media query in [MEDIAQ] or the ‘image-resolution
’ property defined below.
Note that due to the 1:96 fixed ratio of CSS ‘in
’ to CSS ‘px
’,
‘1dppx
’ is equivalent to ‘96dpi
’. This corresponds to the default resolution
of images displayed in CSS: see ‘image-resolution
’.
The following @media rule uses Media Queries [MEDIAQ] to assign some special
style rules to devices that use two or more device pixels per CSS
‘px
’ unit:
@media (min-resolution: 2dppx) { ... }
The ‘<image>
’ value type denotes a 2D image. It
can be a url reference, image notation,
or gradient notation. Its syntax is:
<image> = <url> | <image-list> | <element-reference> | <gradient>
An ‘<image>
’ can be used in many CSS properties,
including the ‘background-image
’,
‘list-style-image
’, ‘cursor
’ properties [CSS21] (where it replaces the
‘<url>
’ component in the property's
value).
In some cases, an image is invalid, such as a ‘<url>
’ pointing to a resource that is not a
valid image format. An invalid image is
rendered as a solid-color ‘transparent
’
image with no intrinsic dimensions. However, invalid images have special behavior in
some contexts, such as the ‘image()
’
notation.
<url>
’ type and
‘url()
’ notationThe simplest way to indicate an image is to reference an image file by
URL. This can be done with the ‘url()
’ notation, defined in [CSS21].
In the example below, a background image is specified with ‘url()
’ syntax:
background-image: url(wavy.png);
If the UA cannot download, parse, or otherwise successfully display the contents at the URL as an image, it must be treated as an invalid image.
image()
’ notationThe ‘image()
’ function allows an
author to:
The ‘image()
’ notation is defined as:
<image-list> = image( [ <image-decl> , ]* [ <image-decl> | <color> ] ) <image-decl> = [ <url> | <string> | <element-reference> ]
Each ‘<string>
’ or ‘<url>
’ inside ‘image()
’ represents an image, just as if the ‘url()
’
notation had been used. As usual for URLs in CSS, relative URLs are
resolved to an absolute URL (as described in Values & Units [CSS3VAL]) when a
specified ‘image()
’ value is computed.
When a URL specified in ‘image()
’
represents a portion of a resource (e.g. by the use of media fragment
identifiers) that portion is clipped out of its context and used as a
standalone image.
For example, given the following image* and CSS:
background-image: image('sprites.svg#xywh=40,0,20,20')
...the background of the element will be the portion of the image that starts at (40px,0px) and is 20px wide and tall, which is just the circle with a quarter filled in.
* SVG-in-<img> support required. Click the picture to view the SVG directly.
So that authors can take advantage of CSS's forwards-compatible parsing
rules to provide a fallback for image slices, implementations that support
the ‘image()
’ notation must
support the xywh=#,#,#,#
form of media fragment identifiers
for images specified via ‘image()
’. [MEDIA-FRAGS]
Note that image fragments can also be used with the ‘url()
’ notation. However, a legacy UA that doesn't
understand the media fragments notation will ignore the fragment and
simply display the entirety of the image.
Since the ‘image()
’ notation
requires UAs to support media fragments, authors can take advantage of
CSS's forward-compatible parsing rules to provide a fallback when using
an image fragment URL:
background-image: url('swirl.png'); /* old UAs */ background-image: image('sprites.png#xywh=10,30,60,20'); /* new UAs */
Multiple ‘<image-decl>s
’ can be given separated by
commas, in which case the function represents the first image that's not
an invalid image. The final argument
can specify a ‘<color>
’ to serve as
an ultimate fallback; this can be used, e.g. for ‘background-image
’, to ensure adequate contrast
if none of the preceding ‘<image-decl>s
’ can be used. If the final
argument is a ‘<color>
’, it
represents a solid-color image of the given color with no intrinsic dimensions. If all of
the provided ‘<image-decl>s
’ are invalid images and a fallback color was
not provided as the last argument, the entire ‘image()
’ function must be treated as an invalid image.
The rule below would tell the UA to load ‘wavy.svg
’ if it can; failing that to load
‘wavy.png
’; failing that to display
‘wavy.gif
’. For example, the browser
might not understand how to render SVG images, and the PNG may be
temporarily 404 (returning an HTML 404 page, which the browser can't
decode as an image) due to a server move, so the GIF is used until one of
the previous problems corrects itself.
background-image: image("wavy.svg", 'wavy.png' , "wavy.gif");
The fallback color can be used to ensure that text is still readable even when the image fails to load. For example, the following code works fine if the image is rectangular and has no transparency:
body { color: black; background: white; } p.special { color: white; background: url("dark.png") black; }
When the image doesn't load, the background color is still there to
ensure that the white text is readable. However, if the image has some
transparency, the black will be visible behind it, which is probably not
desired. The ‘image()
’ function
addresses this:
body { color: black; background: white; } p.special { color: white; background: image("dark.png", black); }
Now, the black won't show at all if the image loads, but if for whatever reason the image fails, it'll pop in and prevent the white text from being set against a white background.
If a URL uses a fragment identifier syntax that the implementation does not understand, or does not consider valid for that type of image, the URL must be treated as representing an invalid image. This error-handling is limited to image(), and not in the definition of URL, for legacy compat reasons.
For example, if a future specification defined a way to refer to a specific frame of an animated GIF with a fragment identifier, an author could write the following to get newer browsers to use the GIF's frame, and older browsers to instead download the fallback image:
background-image: image('cat_meme.gif#frame=5', 'lolcat.png');
At times, one may need a solid-color image for a property or function
that does not accept the ‘<color>
’
type directly. The ‘image()
’ function
can be used for this: by specifying only a color without any
URLs, the function immediately falls back to representing a solid-color
image of the chosen color.
background-image: image(rgba(0,0,255,.5)), url("bg-image.png");
In the above, the background is the image "bg-image.png", overlaid with partially-transparent blue.
A gradient is an image that smoothly fades from one color to another. These are commonly used for subtle shading in background images, buttons, and many other things. The gradient notations described in this section allow an author to specify such an image in a terse syntax, so that the UA can generate the image automatically when rendering the page. The syntax of a <gradient> is:
<gradient> = [ <linear-gradient> | <radial-gradient> | <repeating-linear-gradient> | <repeating-radial-gradient> ]
As with the other <image> types defined in this specification, gradients can be used in any property that accepts images. For example:
background: linear-gradient(white, gray);
list-style-image: radial-gradient(circle, #006, #00a 90%,
#0000af 100%, white 100%)
A gradient is drawn into a box with the dimensions of the concrete object size, referred to as the gradient box. However, the gradient itself has no intrinsic dimensions.
For example, if you use a gradient as a background, by default the
gradient will draw into a gradient box
the size of the element's padding box. If ‘background-size
’ is explicitly set to a value
such as ‘100px 200px
’, then the gradient box will be 100px wide and 200px
tall. Similarly, for a gradient used as a ‘list-style-image
’, the box would be a 1em
square, which is the default object
size for that property.
linear-gradient()
’ notationA linear gradient is created by specifying a gradient line and then several colors placed along that line. The image is constructed by creating an infinite canvas and painting it with lines perpendicular to the gradient line, with the color of the painted line being the color of the gradient line where the two intersect. This produces a smooth fade from each color to the next, progressing in the specified direction.
The linear gradient syntax is:
<linear-gradient> = linear-gradient(
[ [ <angle> | to <side-or-corner> ] ,]?
<color-stop>[, <color-stop>]+
)
<side-or-corner> = [left | right] || [top | bottom]
The first argument to the function specifies the gradient line, which gives the gradient a direction
and determines how color-stops are positioned. It may be omitted; if so,
it defaults to ‘to bottom
’.
The gradient line's direction may be specified in two ways:
0deg
’ points upward, and positive angles represent
clockwise rotation, so ‘90deg
’ point
toward the right.
If the argument is ‘to top
’,
‘to right
’, ‘to
bottom
’, or ‘to left
’,
the angle of the gradient line is
‘0deg
’, ‘90deg
’, ‘180deg
’, or ‘270deg
’, respectively.
If the argument instead specifies a corner of the box such as
‘to top left
’, the gradient line must
be angled such that it points into the same quadrant as the specified
corner, and a line drawn perpendicular to the gradient line through the center of the
gradient box intersects the two
neighboring corners.
Starting from the center of the gradient box, extend a line at the specified angle in both directions. The ending point is the point on the gradient line where a line drawn perpendicular to the gradient line would intersect the corner of the gradient box in the specified direction. The starting point is determined identically, but in the opposite direction.
It is expected that the next level of this module will provide the ability to define the gradient's direction relative to the current text direction and writing-mode.
The gradient's color stops are typically placed between the starting point and ending point on the gradient line, but this isn't required - the gradient line extends infinitely in both directions. The starting point and ending point are merely arbitrary location markers - the starting point defines where 0%, 0px, etc are located when specifying color-stops, and the ending point defines where 100% is located. Color-stops are allowed to have positions before 0% or after 100%.
The color of the gradient at any point is determined by finding the unique line passing through that point that is perpendicular to the gradient line. The point's color is the color of the gradient line at the point where this line intersects it.
All of the following ‘linear-gradient()
’ examples are presumed to be
backgrounds applied to a box that is 200px wide and 100px tall.
Below are various ways of specifying a basic vertical gradient:
linear-gradient(yellow, blue);
linear-gradient(to bottom, yellow, blue);
linear-gradient(180deg, yellow, blue);
linear-gradient(to top, blue, yellow);
linear-gradient(to bottom, yellow 0%, blue 100%);
This demonstrates the use of an angle in the gradient. Note that, though the angle is not exactly the same as the angle between the corners, the gradient line is still sized so as to make the gradient yellow exactly at the upper-left corner, and blue exactly at the lower-right corner.
linear-gradient(135deg, yellow, blue);
linear-gradient(-45deg, blue, yellow);
This demonstrates a 3-color gradient, and how to specify the location of a stop explicitly:
linear-gradient(yellow, blue 20%, #0f0);
This demonstrates* a corner-to-corner gradient specified with keywords. Note how the gradient is red and blue exactly in the bottom-left and top-right corners, respectively, exactly like the second example. Additionally, the angle of the gradient is automatically computed so that the color at 50% (in this case, white) stretches across the top-left and bottom-right corners.
linear-gradient(to top right, red, white, blue)
* SVG-in-HTML support required to view the image.
radial-gradient()
’ notationIn a radial gradient, rather than colors smoothly fading from one side of the gradient box to the other as with linear gradients, they instead emerge from a single point and smoothly spread outward in a circular or elliptical shape.
A radial gradient is specified by indicating the center of the gradient
(where the 0% ellipse will be) and the size and shape of the ending shape (the 100% ellipse). Color stops are
given as a list, just as for ‘linear-gradient()
’. Starting from the center
and progressing towards (and potentially beyond) the ending shape uniformly-scaled concentric
ellipses are drawn and colored according to the specified color stops.
The radial gradient syntax is:
<radial-gradient> = radial-gradient( [ [ <shape> || <size> ] [ at <position> ]? , | at <position>, ]? <color-stop> [ , <color-stop> ]+ )
Here is an example of a circular radial gradient 5em wide and positioned with its center in the top left corner:
radial-gradient(5em circle at top left, yellow, blue)
The arguments are defined as follows:
background-position
’) is defined in [CSS3VAL], and is
resolved using the center-point as the object area and the gradient box as the positioning area. If
this argument is omitted, it defaults to ‘center
’.
circle
’ or
‘ellipse
’; determines whether the
gradient's ending shape is a circle or
an ellipse, respectively. If <shape> is
omitted, the ending shape defaults to
a circle if the <size> is a single
<length>, and to an ellipse otherwise.
Determines the size of the gradient's ending shape. If omitted it defaults to
‘farthest-corner
’. It can be given
explicitly or by keyword. For the purpose of the keyword definitions,
consider the gradient box edges as
extending infinitely in both directions, rather than being finite line
segments.
If the ending-shape is an ellipse, its axises are aligned with the horizontal and vertical axises.
Both ‘circle
’ and ‘ellipse
’ gradients accept the following keywords
as their <size>:
closest-side
’
farthest-side
’
closest-side
’, except
the ending shape is sized based on
the farthest side(s).
closest-corner
’
closest-side
’ were specified.
farthest-corner
’
closest-corner
’, except
the ending shape is sized based on
the farthest corner. If the shape is an ellipse, the ending shape is given the same aspect
ratio it would have if ‘farthest-side
’ were specified.
If <shape> is specified as ‘circle
’ or is omitted, the <size> may be given explicitly as:
Gives the radius of the circle explicitly. Negative values are invalid.
Note that percentages are not allowed here; they can only be used to specify the size of an elliptical gradient, not a circular one. This restriction exists because there is are multiple reasonable answers as to which dimension the percentage should be relative to. A future level of this module may provide the ability to size circles with percentages, perhaps with more explicit controls over which dimension is used.
If <shape> is specified as ‘ellipse
’ or is omitted, <size> may instead be given explicitly as:
Expanded with the above definitions, the grammar becomes:
<radial-gradient> = radial-gradient( [ [ circle || <length> ] [ at <position> ]? , | [ ellipse || [ <length> | <percentage> ]{2} ] [ at <position> ]? , | [ [ circle | ellipse ] || <extent-keyword> ] [ at <position> ]? , | at <position> , ]? <color-stop> [ , <color-stop> ]+ ) <extent-keyword> = closest-corner | closest-side | farthest-corner | farthest-side
Color-stops are placed on a gradient ray,
similar to the gradient line of linear
gradients. The gradient ray is anchored
at the center of the gradient and extends toward the right. The 0%
location is at the start of the gradient
ray, and the 100% location is on the point where the gradient ray intersects the ending shape. A color-stop can be placed
at a negative location; though the negative region of the gradient ray is never directly consulted
for rendering, color stops placed there can affect the color of
non-negative locations on the gradient
ray through interpolation or repetition (see repeating gradients). For example,
‘radial-gradient(red -50px, yellow
100px)
’ produces an elliptical gradient that starts with a
reddish-orange color in the center (specifically, #f50) and transitions to
yellow. Locations greater than 100% simply specify a location a
correspondingly greater distance from the center of the gradient.
The color of the gradient at any point is determined by first finding the unique ellipse passing through that point with the same center, orientation, and ratio between major and minor axises as the ending-shape. The point's color is then the color of the gradient ray at the location where this ellipse intersects it.
Some combinations of position, size, and shape will produce a circle or
ellipse with a radius of 0. This will occur, for example, if the center is
on a gradient box edge and ‘closest-side
’ or ‘closest-corner
’ is specified or if the size and
shape are given explicitly and either of the radiuses is zero. In these
degenerate cases, the gradient must be be rendered as follows:
0px
’.
All of the following examples are applied to a box that is 200px wide and 100px tall.
These examples demonstrate different ways to write the basic syntax for radial gradients:
radial-gradient(yellow, green);
radial-gradient(ellipse at center, yellow 0%, green 100%);
radial-gradient(farthest-corner at 50% 50%, yellow, green);
radial-gradient(circle, yellow, green);
radial-gradient(red, yellow, green);
This image shows a gradient originating from somewhere other than the center of the box:
radial-gradient(farthest-side at left bottom, red, yellow 50px, green);
Here we illustrate a ‘closest-side
’ gradient.
radial-gradient(closest-side at 20px 30px, red, yellow, green);
radial-gradient(20px 30px at 20px 30px, red, yellow, green);
radial-gradient(closest-side circle at 20px 30px, red, yellow, green);
radial-gradient(20px 20px at 20px 30px, red, yellow, green);
repeating-linear-gradient()
’ and ‘repeating-radial-gradient()
’ notationsIn addition to <linear-gradient> and <radial-gradient>, this specification defines <repeating-linear-gradient> and <repeating-radial-gradient> values. These two notations take the same values and are interpreted the same as their respective non-repeating siblings defined previously.
When rendered, however, the color-stops are repeated infinitely in both
directions, with their positions shifted by multiples of the difference
between the last specified color-stop's position and the first specified
color-stop's position. For example, ‘repeating-linear-gradient(red 10px, blue 50px)
’ is
equivalent to ‘linear-gradient(..., red -30px, blue
10px, red 10px, blue 50px, red 50px, blue 90px, ...)
’. Note
that the last color-stop and first color-stop will always coincide at the
boundaries of each group, which will produce sharp transitions if the
gradient does not start and end with the same color.
Repeating gradient syntax is basically identical to that of non-repeating gradients:
repeating-linear-gradient(red, blue 20px, red 40px)
repeating-radial-gradient(red, blue 20px, red 40px)
repeating-radial-gradient(circle closest-side at 20px 30px, red, yellow, green 100%, yellow 150%, red 200%)
If the distance between the first and last color-stops is non-zero, but is small enough that the implementation knows that the physical resolution of the output device is insufficient to faithfully render the gradient, the implementation must find the average color of the gradient and render the gradient as a solid-color image equal to the average color.
If the distance between the first and last color-stops is zero (or rounds to zero due to implementation limitations), the implementation must find the average color of a gradient with the same number and color of color-stops, but with the first and last color-stop an arbitrary non-zero distance apart, and the remaining color-stops equally spaced between them. Then it must render the gradient as a solid-color image equal to that average color.
If the height of a repeating radial gradient is zero, or is close enough to zero that the implementation knows that the physical resolution of the output device is insufficient to faithfully render the gradient, the implementation must find the average color of the gradient and render the gradient as a solid-color image equal to the average color.
To find the average color of a gradient, run these steps:
As usual, implementations may use whatever algorithm they wish, so long as it produces the same result as the above.
For example, the following gradient is rendered as a solid light-purple
image (equal to rgb(75%,50%,75%)
):
repeating-linear-gradient(red 0px, white 0px, blue 0px);
The following gradient would render the same as the previous under normal circumstances (because desktop monitors can't faithfully render color-stops 1/10th of a pixel apart), but would render as a normal repeating gradient if, for example, the author applied "zoom:100;" to the element on which the gradient appears:
repeating-linear-gradient(red 0px, white .1px, blue .2px);
<color-stop> = <color> [ <percentage> | <length> ]?
Color-stops are points placed along the line defined by the gradient line at the beginning of the rule. Color-stops must be specified in order. Percentages refer to the length of the gradient line, with 0% being at the starting point and 100% being at the ending point. Lengths are measured from the starting point in the direction of the ending point. Color-stops are usually placed between the starting point and ending point, but that's not required; the gradient line extends infinitely in both directions, and a color-stop can be placed at any position on the line.
At each color-stop, the line is the color of the color-stop. Between two color-stops, the line's color is linearly interpolated between the colors of the two color-stops, with the interpolation taking place in premultiplied RGBA space. Before the first color-stop, the line is the color of the first color-stop. After the last color-stop, the line is the color of the last color-stop.
The following steps must be applied in order to process the list of color-stops. After applying these rules, all color-stops will have a definite position and they will be in ascending order:
If multiple color-stops have the same position, they produce an infinitesimal transition from the one specified first in the rule to the one specified last. In effect, the color suddenly changes at that position rather than smoothly transitioning.
Below are several pairs of gradients. The latter of each pair is a manually "fixed-up" version of the former, obtained by applying the above rules. For each pair, both gradients will render identically. The numbers in each arrow specify which fixup steps are invoked in the transformation.
1.  In both of these example, the gradient is drawn over a white background. Both gradients could be written with the following value:
linear-gradient(90deg, red, transparent, blue)
In premultiplied space, transitions to or from "transparent" always look nice:
On the other hand, if a gradient were to incorrectly transition in
non-premultiplied space, the colors near "transparent" would noticeably
darken to a grayish color, because "transparent" is actually a shorthand
for ‘rgba(0,0,0,0)
’, or transparent
black:
* SVG-in-HTML support required to view the images.
Note: It is recommended that authors not mix different types
of units, such as px, em, or %, in a single rule, as this can cause a
color-stop to unintentionally try to move before an earlier one. For
example, the rule ‘background-image:
linear-gradient(yellow 100px, blue 50%)
’ wouldn't require any
fix-up as long as the background area is at least 200px tall. If it was
150px tall, however, the blue color-stop's position would be equivalent to
"75px", which precedes the yellow color-stop, and would be corrected to a
position of 100px.
Note: The definition and implications of "premultiplied" color spaces are given elsewhere in the technical literature, but a quick primer is given here to illuminate the process. Given a color expressed as an rgba() 4-tuple, one can convert this to a premultiplied representation by multiplying the red, green, and blue components by the alpha component. For example, a partially-transparent blue may be given as rgba(0,0,255,.5), which would then be expressed as [0, 0, 127.5, .5] in its premultiplied representation. Interpolating colors using the premultiplied representations rather than the plain rgba representations tends to produce more attractive transitions, particularly when transitioning from a fully opaque color to fully transparent. Note that transitions where either the transparency or the color are held constant (for example, transitioning between rgba(255,0,0,100%) and rgba(0,0,255,100%) or rgba(255,0,0,100%) and rgba(255,0,0,0%)) have identical results whether the color interpolation is done in premultiplied or non-premultiplied color-space. Differences only arise when both the color and transparency differ between the two endpoints.
Images used in CSS may come from a number of sources: from binary image formats (such as gif, jpeg, etc), dedicated markup formats (such as SVG), and CSS-specific formats (such as the linear-gradient() value type defined in this specification). As well, a document may contain many other types of objects, such as video, plugins, or nested documents. These images and objects (just objects hereafter) may offer many types of sizing information to CSS, or none at all. This section defines generically the size negotiation model between the object and the CSS layout algorithms.
In order to define this handling, we define a few terms, to make it easier to refer to various concepts:
The term intrinsic dimensions refers to the set of the intrinsic height, intrinsic width, and intrinsic aspect ratio (the ratio between the width and height), each of which may or may not exist for a given object. These intrinsic dimensions represent a preferred or natural size of the object itself; that is, they are not a function of the context in which the object is used. CSS does not define how the intrinsic dimensions are found in general.
 SVG images designed to scale might have only an intrinsic
aspect ratio; SVG images can also be created with only an intrinsic
width or height. CSS gradients, defined in this specification, are an
example of an object with no intrinsic dimensions at all. Another
example of this is embedded documents, such as the
<iframe>
element in HTML. An object cannot have only two
intrinsic dimensions, as any two automatically define the third.
If an object (such as an icon) has multiple sizes, then the largest size (by area) is taken as its intrinsic size. If it has multiple aspect ratios at that size, or has multiple aspect ratios and no size, then the aspect ratio closest to the aspect ratio of the default object size is used. Determine this by seeing which aspect ratio produces the largest area when fitting it within the default object size using a contain fit; if multiple sizes tie for the largest area, the wider size is chosen as its intrinsic size.
width
’ and ‘height
’ or ‘background-size
’ properties. The specified
size can be a definite width and height, a set of constraints, or a
combination thereof.
The default object size is a rectangle with a definite height and width used to determine the concrete object size when both the intrinsic dimensions and specified size are missing dimensions.
Objects in CSS are sized and rendered as follows:
url()
’ value in a ‘background-image
’ property or an
src
attribute on an <img>
element, CSS
queries the object for its intrinsic
dimensions.
Currently the rules for sizing objects are described in each context that such objects are used. This section defines some common sizing constraints and how to resolve them so that future specs can refer to them instead of redefining size resolution in each instance.
The default sizing algorithm is a set of rules commonly used to find an object's concrete object size. It resolves the simultaneous constraints presented by the object's intrinsic dimensions and either an unconstrained specified size or one consisting of only a definite width and/or height.
Some object sizing rules (such as those for ‘list-style-image
’) correspond exactly to the
default sizing algorithm.
Others (such as those for ‘border-image
’) invoke the default sizing
algorithm but also apply additional sizing rules before arriving at a
final concrete object size.
The default sizing algorithm is defined as follows:
Two other common specified sizes are the contain constraint and the cover constraint, both of which are resolved against a specified constraint rectangle using the object's intrinsic aspect ratio:
In both cases, if the object doesn't have an intrinsic aspect ratio, the concrete object size is the specified constraint rectangle.
The following examples show how the CSS 2.1 and CSS3 Backgrounds & Borders sizing algorithms correspond to concepts defined in this specification.
background-image
’
background-size
’ property can
give a sizing constraint, invoking either the default sizing algorithm or
one of the contain or cover
constraints. The concrete object size is further adjusted in later steps
if ‘background-repeat
’ has a
‘round
’ value. [CSS3BG]
list-style-image
’
border-image
’
border-image-repeat
’ property can drop the
specified size in one or more directions and may also apply an
additional rounding step. [CSS3BG]
cursor
’
content
’
content
’ property are anonymous replaced
elements, and are sized the same way. [CSS21] Note that such anonymous
elements have all their non-inherited properties (including ‘width
’, ‘height
’, etc.) set to their initial values.
content
’) in
sections 10.3.2,
10.4,
10.6.2,
and 10.7.
[CSS21] The
‘object-fit
’ property defined below
defines how the concrete object
size corresponds to the element's used width and height; by
default they coincide.
object-fit
’ property| Name: | object-fit |
|---|---|
| Value: | fill | contain | cover | none | scale-down |
| Initial: | fill |
| Applies to: | replaced elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | specified value |
The ‘object-fit
’ property specifies how the
contents of a replaced element should be fitted to the box established by
its used height and width.
fill
’
contain
’
cover
’
none
’
scale-down
’
Size the content as if ‘none
’ or
‘contain
’ were specified, whichever
would result in a smaller concrete
object size.
Note that both ‘none
’
and ‘contain
’ respect the content's
intrinsic aspect ratio, so the concept of "smaller" is well-defined.
If the content does not completely fill the replaced element's content
box, the unfilled space shows the replaced element's background. Since
replaced elements always clip their contents to the content box, the
content will never overflow. See the ‘object-position
’ property for positioning
the object with respect to the content box.
Note: the ‘object-fit
’ property has similar semantics
to the fit
attribute in [SMIL10] and the <meetOrSlice>
parameter on the preserveAspectRatio
attribute in [SVG11].
Note: Per the CSS⇋Object Negotiation algorithm, the concrete object size (or, in this case, the size of the content) does not directly scale the object itself - it is merely passed to the object as information about the size of the visible canvas. How to then draw into that size is up to the image format. In particular, raster images always scale to the given size, while SVG uses the given size as the size of the "SVG Viewport" (a term defined by SVG) and then uses the values of several attributes on the root <svg> element to determine how to draw itself.
object-position
’ property| Name: | object-position |
|---|---|
| Value: | <position> |
| Initial: | 50% 50% |
| Applies to: | replaced elements |
| Inherited: | no |
| Percentages: | refer to width and height of box itself |
| Media: | visual |
| Computed value: | specified value |
The ‘object-position
’ property determines the
alignment of the replaced element inside its box. The <position> value
type (which is also used for ‘background-position
’) is defined in [CSS3VAL], and is
resolved using the concrete object
size as the object area and the content box as the positioning
area.
Note that areas of the box not covered by the replaced element will show the element's background.
image-resolution
’ propertyThe image resolution is defined as the number of image pixels per
unit length, e.g., pixels per inch. Some image formats can record
information about the resolution of images. This information can be
helpful when determining the actual size of the image in the formatting
process. However, the information can also be wrong, in which case it
should be ignored. By default, CSS assumes a resolution of one image pixel
per CSS ‘px
’ unit; however, the
‘image-resolution
’ property allows using
some other resolution.
| Name: | image-resolution |
|---|---|
| Value: | [from-image || <resolution>] && snap? |
| Initial: | 1dppx |
| Applies to: | all elements |
| Inherited: | yes |
| Media: | visual |
| Computed value: | as specified, except with ‘<resolution> ’ possibly altered by
computing for ‘snap ’ (see below)
|
The ‘image-resolution
’ property specifies the
intrinsic resolution of all
raster images used in or on the element. It affects both content images
(e.g. replaced elements and generated content) and decorative images (such
as ‘background-image
’). The intrinsic resolution of an image is used to
determine the image's intrinsic
dimensions. Values have the following meanings:
<resolution>
’
from-image
’
1ddpx
’.
snap
’
<resolution>
’
(if any) is the specified resolution rounded to the nearest value that
would map one image pixel to an integer number of device pixels. If the
resolution is taken from the image, then the used intrinsic resolution is
the image's native resolution similarly adjusted.
As vector formats such as SVG do not have an intrinsic resolution, this property has no effect on vector images.
Printers tend to have substantially higher resolution than computer
monitors; due to this, an image that looks fine on the screen may look
pixellated when printed out. The ‘image-resolution
’ property can be used to
embed a high-resolution image into the document and maintain an
appropriate size, ensuring attractive display both on screen and on
paper:
img.high-res { image-resolution: 300dpi; }
With this set, an image meant to be 5 inches wide at 300dpi will actually display as 5in wide; without this set, the image would display as approximately 15.6in wide since the image is 15000 image pixels across, and by default CSS displays 96 image pixels per inch.
Some image formats can encode the image resolution into the image data.
This rule specifies that the UA should use the image resolution found in
the image itself, falling back to 1 image pixel per CSS ‘px
’ unit.
img { image-resolution: from-image }
These rules both specify that the UA should use the image resolution
found in the image itself, but if the image has no resolution, the
resolution is set to ‘300dpi
’ instead
of the default ‘1dppx
’.
img { image-resolution: from-image 300dpi } img { image-resolution: 300dpi from-image }
Using this rule, the image resolution is set to 300dpi. (The resolution in the image, if any, is ignored.)
img { image-resolution: 300dpi }
This rule, on the other hand, if used when the screen's resolution is 96dpi, would instead render the image at 288dpi (so that 3 image pixels map to 1 device pixel):
img { image-resolution: 300dpi snap; }
The ‘snap
’ keyword can also be used
when the resolution is taken from the image. In this rule:
img { image-resolution: snap from-image; }
An image declaring itself as 300dpi will, in the situation above, display at 288dpi (3 image pixels per device pixel) whereas an image declaring 72dpi will render at 96dpi (1 image pixel per device pixel).
image-orientation
’ propertyIf a picture is taken with a camera turned on its side, or a document
isn't positioned correctly within a scanner, the resultant image may be
"sideways" or even upside-down. The ‘image-orientation
’ property provides a way
to apply an "out-of-band" rotation to image source data to correctly
orient an image.
Note that some devices will "tag" an image with some metadata indicating its correct orientation, so image viewing software can do the necessary transformation themselves. Due to legacy compatibility restraints, Web browsers are required to ignore this data by default. A future level of this specification is expected to have a value that applies the metadata-specified transformation automatically.
Note that this property is not intended to specify layout transformations such as arbitrary rotation or flipping the image in the horizontal or vertical direction. (See [CSS3-2D-TRANSFORMS] for a feature designed to do that.) It is also not needed to correctly orient an image when printing in landscape versus portrait orientation, as that rotation is done as part of layout. (See [CSS3PAGE].) It should only be used to correct incorrectly-oriented images.
| Name: | image-orientation |
|---|---|
| Value: | <angle> |
| Initial: | 0deg |
| Applies to: | all elements |
| Inherited: | yes |
| Media: | visual |
| Computed value: | specified value, rounded and normalized (see text) |
This property specifies an orthogonal rotation to be applied to an image
before it is laid out. It applies only to content images (e.g. replaced
elements and generated content), not decorative images (such as
‘background-image
’). CSS layout
processing applies to the image after rotation. This implies, for
example:
Positive values cause the image to be rotated to the right (in a clockwise direction), while negative values cause a rotation to the left. The computed value of the property is calculated by rounding the specified angle to the nearest quarter-turn (90deg, 100grad, .25turn, etc.), rounding away from 0 (that is, 45deg is rounded to 90deg, while -45deg is rounded to -90deg), then moduloing the value by 1 turn (360deg, 400grad, etc.).
The ‘image-orientation
’ property must be
applied before any other transformations, such as being specified in the
‘image()
’ function with an opposite
directionality to its context, or using CSS Transforms.
The following example rotates the image 90 degrees clockwise:
img.ninety { image-orientation: 90deg } ... <img class="ninety" src=... />
The same effect could be achieved with, for example, an angle of -270deg or 450deg.
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for
example” or are set apart from the normative text with
class="example"
, like this:
This is an example of an informative example.
Informative notes begin with the word “Note” and are set apart from
the normative text with class="note"
, like this:
Note, this is an informative note.
Conformance to CSS Image Values and Replaced Content Module Level 3 is defined for three conformance classes:
A style sheet is conformant to CSS Image Values and Replaced Content Module Level 3 if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.
A renderer is conformant to CSS Image Values and Replaced Content Module Level 3 if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by CSS Image Values and Replaced Content Module Level 3 by parsing them correctly and rendering the document accordingly. However, the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)
An authoring tool is conformant to CSS Image Values and Replaced Content Module Level 3 if it writes style sheets that are syntactically correct according to the generic CSS grammar and the individual grammars of each feature in this module, and meet all other conformance requirements of style sheets as described in this module.
So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported component values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored.
To avoid clashes with future CSS features, the CSS2.1 specification reserves a prefixed syntax for proprietary and experimental extensions to CSS.
Prior to a specification reaching the Candidate Recommendation stage in the W3C process, all implementations of a CSS feature are considered experimental. The CSS Working Group recommends that implementations use a vendor-prefixed syntax for such features, including those in W3C Working Drafts. This avoids incompatibilities with future changes in the draft.
Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.
To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before releasing an unprefixed implementation of any CSS features. Testcases submitted to W3C are subject to review and correction by the CSS Working Group.
Further information on submitting testcases and implementation reports can be found from on the CSS Working Group's website at http://www.w3.org/Style/CSS/Test/. Questions should be directed to the<EMAIL_ADDRESS>mailing list.
For this specification to be advanced to Proposed Recommendation, there must be at least two independent, interoperable implementations of each feature. Each feature may be implemented by a different set of products, there is no requirement that all features be implemented by a single product. For the purposes of this criterion, we define the following terms:
The specification will remain Candidate Recommendation for at least six months.
Thanks to the Webkit team, Brad Kemper, Brian Manthos, and Alan Gresley
for their contributions to the definition of gradients; to Melinda Grant
for her work on ‘object-fit
’, ‘object-position
’, and ‘image-orientation
’;
to
Michael Day, Håkon Lie, and Shinyu Murakami for ‘image-resolution
’; and to L. David Baron,
Kang-Hao Lu, Leif Arne Storset, Erik Dahlstrom, and Øyvind Stenhaug for
their careful review, comments, and corrections.
Major changes include:
element()
’ feature has been
deferred to Level 4.
ltr
’/‘rtl
’
annotations in ‘image()
’) has been
deferred to Level 4 to address some design-level feedback.
image()
’.
object-fit
’ property no longer resizes
the element's content box in any cases.
image-orientation
’ property is now
inherited.
Significant details updated:
image()
’ notation.
image()
’ in order to satisfy
the prerequisite for supporting ‘image()
’.
image-orientation
’ was applied after CSS
transforms.
object-fit
’ and ‘object-position
’ properties may no longer
be aliased to ‘image-fit
’ and
‘image-position
’. A future
edition of the CSS Print
Profile may allow this for printer implementations, however.
There were also many clarifications and several sections were rearranged to make them easier to read.
The Disposition of Last Call Comments is available.
closest-corner
’, 4.2.1.
closest-side
’, 4.2.1.
dpcm
’, 2.
dpi
’, 2.
dppx
’, 2.
farthest-corner
’, 4.2.1.
farthest-side
’, 4.2.1.
| Property | Values | Initial | Applies to | Inh. | Percentages | Media |
|---|---|---|---|---|---|---|
| image-orientation | <angle> | 0deg | all elements | yes | visual | specified value, rounded and normalized (see text) |
| image-resolution | [from-image || <resolution>] && snap? | 1dppx | all elements | yes | visual | as specified, except with ‘<resolution>’ possibly altered by computing for ‘snap’ (see below) |
| object-fit | fill | contain | cover | none | scale-down | fill | replaced elements | no | N/A | visual |
| object-position | <position> | 50% 50% | replaced elements | no | refer to width and height of box itself | visual |


Gold:
Territory:
Mana:
100f
Your Wall Health:
801f
Enemy Wall Health:
800f
Gain
10f
base gold per killGain
10
territory upon victoryStage
Pause
Battle
Map
Unit Spawning
Unit Upgrades
Buildings
Spells
Options
(1)
Fireball
(2)
Chain Lightning
Spell Level:
1f
2f
3f
Unit Spawning
Click a unit type to add it to the spawn list
Construction Total:
0f
Construction Rate:
0f
Territory Used:
0f
/ 0ff
Fill up your territory with unit producing buildings!
This will decide which order your units spawn over the level!
Click the spawn list to remove a building!
This will decide which order your units spawn over the level!
Click the spawn list to remove a building!
Barracks
1f
Lumber Yard
1f
Sell Land for Construction Workers
-
Can only be purchased with unused Territory
-
100
, +.5 Construction RateCan only be purchased with unused Territory
Unit Upgrades
Click a unit type for possible upgrades
Soldier
Spearman
Buildings
Click a building type for possible upgrades
Upgrade Wall
Upgrade Fence
Created by: Stop_Sign AKA Phurple
How to Play:
Click Unit Spawning, then Barracks, then War to start the game
Watch the fight in Battle
Use hotkeys or tap spells and use them on enemies
Upgrade units, kill the enemy wall health, go further on the map
You'll need more wood to complete map 2
Even if you die on harder levels, you'll still get more gold
You have saving, but no offline. The game works full speed in a different tab


{{$index + 1}}. {{question.question_body}}
{{answer_choice}}
Your Answer: {{handleQuestion(userAnswers[$index], question.question_type, question.correct_answer.length)}}
Correct Answer: {{handleQuestion(question.correct_answer, question.question_type, question.correct_answer.length)}}
Florida State Standard: {{question.standard}}


All of Us Research Program
Data User Code of Conduct
This Data User
Code of Conduct describes how All of Us
Research Program data may and may not be used by Authorized Data Users.
An Authorized Data User is a person who is
authorized to access and/or work with Registered or Controlled Tier data from the
All of Us Research Program.
To
become an Authorized Data User, individuals must:
1.
ensure they are
covered by an institutional Data Use and Registration Agreement (DURA), as applicable;
2.
verify their identities;
3.
complete the All of Us Responsible Conduct of
Research Training;
4.
read and
acknowledge this Data User Code of Conduct; and
5.
complete all
other required steps in the Authorized Data User onboarding process.
As an “Authorized Data User” of the All of Us Research Program data, I will:
●
read and adhere
to the All of Us Research Program Core Values.
●
follow all laws
and regulations regarding research involving human data and data privacy that
are applicable in the area where I am conducting research.
○
In the US, this
includes all applicable federal, state, and local laws.
○
Outside of the
US, other laws will apply.
●
conduct research that follows all policy requirements, including those
not expressly mentioned in this document, and
conforms to the ethical principles
upheld by the All of Us Research
Program.
●
respect
the privacy of research participants at all times.
○
I will NOT use or disclose any
information that directly identifies one or more participants.
■
If I become aware
of any information that directly identifies one or more participants, I will
notify the All of Us Research Program immediately using the appropriate
process.
○
I will NOT attempt to re-identify
research participants or their relatives.
■
If I
unintentionally re-identify participants through the process of my work, I will
contact the All of Us Research
Program immediately using the appropriate process.
■ If I become aware of any uses or disclosures of All of Us Research Program data that could
endanger the security or privacy of research participants, I will contact the All of Us Research Program immediately
using the appropriate process.
● read and comply with All of Us policies pertaining to the respectful use of data from
individuals or groups who self-identify, or are identified, as American Indian
and/or Alaska Native.
● use the All
of Us Research Program data ONLY
for the purpose of biomedical or health research.
● provide a meaningful and accurate description of
my research purpose every time I create an All
of Us Research Program Workspace.
○
Within each
Workspace, I will use the All of Us Research
Program data only for the research purpose I have provided.
○ If I have a new research purpose, I will create
a new Workspace and provide a new research purpose description.
● take full responsibility for any external data,
files, or software that I import into the All
of Us Researcher Workbench and the consequences thereof.
○
I will follow all
applicable laws, regulations, and policies regarding access and use for any
external data, files, or software that I upload into my Workspace.
○
I will NOT upload data or files
containing personally identifiable information (PII), protected health
information (PHI), or identifiable private information (IPI).
○
I will NOT use external data, files, or
software that I upload into my Workspace for any malicious purpose.
○ If any import of data, files, or software into
my Workspace results in unforeseen consequences and/or unintentional violation
of these terms, I will notify the All of
Us Research Program as soon as I become aware using the appropriate
process.
● use a version of the All of Us Research Program database that is current at or after the
time my analysis begins.
●
inform the All
of Us Research Program:
○
if I have been penalized in the past for one or
more data use violations, data management incidents, research misconduct, or
legal or regulatory violations pertaining to the conduct of research; or
○
if, subsequent to
becoming an All of Us Authorized Data
User, I am penalized by another entity for a data use violation, data
management incident, research misconduct, or legal or regulatory violations
pertaining to the conduct of research.
As an
“Authorized Data User” of the All of Us Research
Program data, I will:
● NOT share my login information with anyone,
including another Authorized Data User of the All of Us Research Program data.
○ I will NOT
create any group or shared accounts.
● NOT use All
of Us Research Program data, or
any external data, files, or software that I upload into the Researcher
Workbench, for research that is discriminatory or stigmatizing of individuals,
groups, families, or communities in accordance with the All
of Us Policy on Stigmatizing Research.
○ I will contact the All of Us Research Program Resource Access Board (RAB) for further
guidance on this point as needed.
● NOT attempt to contact All of Us Research Program participants.
● NOT take screenshots or attempt in any way to copy,
download, or otherwise remove any participant-level data from the All of Us Researcher Workbench.
○
I will NOT publish or otherwise
distribute any participant-level data from the All of Us Research Program database.
○ I will NOT
publish or otherwise distribute any data or aggregate statistics corresponding
to fewer than 20 participants unless expressly permitted under the terms of the
All
of Us Data and Statistics Dissemination
Policy.
● NOT redistribute or publish any data or statistics
with the intent of reproducing the All of
Us Research Program database or part of the database outside of the All of Us Researcher Workbench.
● NOT attempt to link Registered or Controlled Tier All of Us Research Program data at the
participant-level with data from other sources.
● NOT use All
of Us Research Program data or any part of the Research Hub for marketing
purposes.
●
NOT
represent that the All of Us Research
Program endorses or approves of my research unless such endorsement is
expressly provided, in writing, by the All
of Us Research Program.
Data Disclaimer:
The All of Us Research Program does not
guarantee the accuracy or availability of the data in the All of Us Research Program database. The All of Us Research Program does not guarantee the performance of
the software in the All of Us Research
Program database. The All of Us Research
Program does not warrant or endorse the research results obtained by using the All of Us database.
Terms and Definitions:
● The All of Us Research
Program is
a national longitudinal research initiative that aims to engage one million or
more participants living in the United States. Participants contribute health
data and specimens (blood, urine, saliva) to a repository that includes health,
behavioral, genomic, and other data. The All
of Us Research Program is a key component of the Precision Medicine
Initiative, which aspires to leverage advances in genomics and health
information technology to accelerate biomedical discoveries.
● There are three
data access tiers within the All of
Us Research Program.
○
Public Tier: The resource tier containing only summary statistics and aggregate
information that poses negligible risks to the privacy of research
participants; the Public Tier can be accessed by anyone without logging into
the All of Us Researcher Workbench.
○
Registered Tier: The resource tier that contains data elements
that have a lower risk of unapproved re-identification, and thus carries
minimal risk to the privacy of research participants; Registered Tier data can
only be accessed after logging into the All
of Us Researcher Workbench; all access will be logged and may be audited
for compliance.
○ Controlled
Tier: The resource tier that contains data elements
that may not, in their own right, readily identify individual participants, but
may increase the risk of unapproved re-identification when combined with other
data elements; such data may include participant-level genomic data, clinical
notes, and narrative data; users must be appropriately accredited and granted
approval to access the Controlled Tier, and all access will be logged and may
be audited for compliance.
● An Authorized
Data User is a person who is authorized to access and/or work with Registered or Controlled Tier data from the All
of Us Research Program. Authorized Data Users must verify their identity,
complete the All of Us Responsible
Conduct of Research Training, attest to this agreement, and complete all other
aspects of the Authorized Data User onboarding process. Authorized Data Users
may also need to be covered by an institutional Data Use and Registration
Agreement (DURA).
● The Resource
Access Board (RAB) is the board that operationalizes decisions regarding
data access; responsibilities include: overseeing
registration procedures for new Authorized Data Users, conducting Workspace
audits, responding to Authorized Data User inquiries around potentially
stigmatizing research, and reviewing potential violations of the Data User Code
of Conduct; the RAB reports to the All of
Us Steering Committee.
● All of Us Researcher Workbench is the cloud-based research platform that the All of Us Research Program has created,
where individuals can apply for access to the data, and once approved as
Authorized Data Users, create project-specific Workspaces in which to access
and analyze the data.
● Workspace is a user-created analytical sandbox within the
All of Us Researcher Workbench
platform where users can virtually pull in subsets of data from the All of Us Research Program database and
perform analyses; Authorized Data Users must create a new Workspace for each
research project using All of Us data
and provide a plain language description of the research project, as well as
other project information, that will be published publicly on the All
of Us Research Projects Directory.
●
Personal Identifying Information (PII) means information that can be used to
distinguish or trace the identity of an individual (e.g., name, social security
number, biometric records etc.) either alone, or when combined with other
personal or identifying information that is linked or linkable to a specific
individual (2 CFR § 200.1).
●
Protected Health Information (PHI) means individually identifiable health
information that is transmitted by electronic media, maintained in electronic
media, or transmitted or maintained in any other form or medium (45 CFR § 160.103).
●
Identifiable Private Information (IPI) means private information for which the
identity of the subject is or may readily be ascertained by the investigator or
associated with the information (45 CFR § 46.102).
●
Marketing
means a communication about a product or service that encourages recipients of
the communication to purchase or use the product or service (45 CFR §164.501).


Before Change
num_layers = len(pytorch_tlm.transformer.encoders)
mapped_keys = convert_transformers_keys(num_layers, d, replace_layers, replace_embeds)
unknown_keys = pytorch_tlm.load_state_dict(mapped_keys, strict=False)
print("Ignored ", unknown_keys)
After Change
// the usual LP embeddings with an added bias term set to weight 0
// Option 2: the user does care about token types and has provided a token type feature (presumed to be in the
// second key of the embeddings stack
if isinstance(pytorch_tlm.embeddings[k_0], LearnedPositionalLookupTableEmbeddingsWithBias):
old_embeddings_stack = pytorch_tlm.embeddings
// we need to temporarily monkey patch the embeddings to load them, and then we can reset them to what they were
d = {k_0: pytorch_tlm.embeddings[k_0], "tt": LookupTableEmbeddings(vsz=2, dsz=pytorch_tlm.transformer.output_dim)}
pytorch_tlm.embeddings = EmbeddingsStack(d)
unknown_keys = pytorch_tlm.load_state_dict(mapped_keys, strict=False)
if old_embeddings_stack:
old_embeddings_stack[k_0].bias = nn.Parameter(pytorch_tlm.embeddings["tt"].embeddings.weight[0])
pytorch_tlm.embeddings = old_embeddings_stack


TIFF2PDF(1) TIFF2PDF(1) NAME tiff2pdf - convert a TIFF image to a PDF document SYNOPSIS tiff2pdf [ options ] input.tiff DESCRIPTION tiff2pdf opens a TIFF image and writes a PDF document to standard output. The program converts one TIFF file to one PDF file, including multiple page TIFF files, tiled TIFF files, black and white. grayscale, and color TIFF files that contain data of TIFF photometric interpretations of bilevel, grayscale, RGB, YCbCr, CMYK separation, and ICC L*a*b* as sup‐ ported by libtiff and PDF. If you have multiple TIFF files to convert into one PDF file then use tiffcp or other program to concatenate the files into a multiple page TIFF file. If the input TIFF file is of huge dimensions (greater than 10000 pixels height or width) convert the input image to a tiled TIFF if it is not already. The standard output is standard output. Set the output file name with the -o output.pdf option. All black and white files are compressed into a single strip CCITT G4 Fax compressed PDF, unless tiled, where tiled black and white images are com‐ pressed into tiled CCITT G4 Fax compressed PDF, libtiff CCITT support is assumed. Color and grayscale data can be compressed using either JPEG compression, ITU-T T.81, or Zip/Deflate LZ77 compression. Set the compression type using the -j or -z options. JPEG compression support requires that libtiff be configured with JPEG support, and Zip/Deflate compression sup‐ port requires that libtiff be configured with Zip support, in tiffconf.h. Use only one or the other of -j and -z. If the input TIFF contains single strip CCITT G4 Fax compressed informa‐ tion, then that is written to the PDF file without transcoding, unless the options of no compression and no passthrough are set, -d and -n. If the input TIFF contains JPEG or single strip Zip/Deflate compressed information, and they are configured, then that is written to the PDF file without transcoding, unless the options of no compression and no passthrough are set. The default page size upon which the TIFF image is placed is determined by the resolution and extent of the image data. Default values for the TIFF image resolution can be set using the -x and -y options. The page size can be set using the -p option for paper size, or -w and -l for paper width and length, then each page of the TIFF image is centered on its page. The distance unit for default resolution and page width and length can be set by the -u option, the default unit is inch. Various items of the output document information can be set with the -e, -c, -a, -t, -s, and -k options. Setting the argument of the option to "" for these tags causes the relevant document information field to be not written. Some of the document information values otherwise get their information from the input TIFF image, the software, author, document name, and image description. The Portable Document Format (PDF) specification is copyrighted by Adobe Systems, Incorporated. OPTIONS -o output-file Set the output to go to file. output-file -j Compress with JPEG (requires libjpeg configured with libtiff). -z Compress with Zip/Deflate (requires zlib configured with libtiff). -q quality Set the compression quality, 1-100 for JPEG. -n Do not allow data to be converted without uncompressing, no com‐ pressed data passthrough. -b Set PDF ``Interpolate'' user preference. -d Do not compress (decompress). -i Invert colors. -p paper-size Set paper size, e.g., letter, legal, A4. -F Cause the tiff to fill the PDF page. -u [i|m] Set distance unit, i for inch, m for centimeter. -w width Set width in units. -l length Set length in units. -x xres Set x/width resolution default. -y yres Set y/length resolution default. -r [d|o] Set d for resolution default for images without resolution, o for resolution override for all images. -f Set PDF ``Fit Window'' user preference. -e YYYYMMDDHHMMSS Set document information date, overrides image or current date/time default, YYYYMMDDHHMMSS. -c creator Set document information creator, overrides image software default. -a author Set document information author, overrides image artist default. -t title Set document information title, overrides image document name default. -s subject Set document information subject, overrides image image descrip‐ tion default. -k keywords Set document information keywords. -h List usage reminder to stderr and exit. EXAMPLES The following example would generate the file output.pdf from input.tiff. tiff2pdf -o output.pdf input.tiff The following example would generate PDF output from input.tiff and write it to standard output. tiff2pdf input.tiff The following example would generate the file output.pdf from input.tiff, putting the image pages on a letter sized page, compressing the output with JPEG, with JPEG quality 75, setting the title to ``Document'', and setting the ``Fit Window'' option. tiff2pdf -p letter -j -q 75 -t "Document" -f -o output.pdf input.tiff BUGS Please report bugs via the web interface at http://bugzilla.remotesensing.org/enter_bug.cgi?product=libtiff SEE ALSO libtiff(3), tiffcp(1), tiff2ps(1) Libtiff library home page: http://www.remotesensing.org/libtiff/ libtiff April 20, 2006 TIFF2PDF(1)


Cyber Ethics
Cyber Ethics basically touches on our online behaviour, how we conduct ourselves online and whether we follow certain unwritten rules of the online space.
We do have a choice to make when we come in face with our evil self. We can either be a good netizen or be the bully.
Take consent to share pictures, video or written article of someone else
Refrain from posting hurtful content
Do not write vulgar or hurtful comments on someone's post
Refrain from spreading rumours about people online as well as offline
Do not invade another person's privacy
Always give credit to the original creator if you are using their work. Also ask permission when needed
Do not spread malware in systems and devices intentionally
Gaining illegal authorization to operate a computer or systems is a crime
Do not threaten, stalk or bully a user
Do not obtain services online through deception
Refrain from downloading software from unverified websites
Few unwritten rules to follow are to be a good netizen are:
Understand that liking and sharing or reposting of embarrassing and humiliating pics and content is also considered cyber bullying. Thus refrain from any activity that harms another person.


Much of the data included in the ModelSEED is dervied from numerous published manuscripts and databases. We've done our best to cite contributing data sources here. If you beleive your data has been utilized and not properly cited, please notify us. We sincerely thank all of our data sources, without whom this resource would not exist.
| Data | Source | |
|---|---|---|
| Biochemical data and metabolic maps |
Kyoto Encyclopedia for Genes and Genomes MetaCyc PlantCyc |
|
| Genome annotations and subsystem data | SEED/RAST/MGRAST |


| Name | Total Lines | Lines of Code | Total Coverage | Code Coverage |
|---|---|---|---|---|
| app/models/person.rb | 41 | 34 | 80.49%
|
82.35%
|
Code reported as executed by Ruby looks like this...and this: this line is also marked as covered.Lines considered as run by rcov, but not reported by Ruby, look like this,and this: these lines were inferred by rcov (using simple heuristics).Finally, here's a line marked as not executed.
1 class Person < ActiveRecord::Base |
2 # Set default preferences |
3 before_validation do |
4 self.music ||= 'no_preference' |
5 self.smoking ||= 'no_preference' |
6 end |
7 |
8 validates_presence_of :name, :unless => Proc.new {|name| self.name.nil?} |
9 validates :phone, :presence => true, |
10 :format => {:with => /^\(?\b([0-9]{3})\)?[-. ]?([0-9]{3})[-. ]?([0-9]{4})$/, |
11 :message => "must be a complete and numeric US phone number"}, |
12 :unless => Proc.new {|phone| self.phone.nil?} |
13 validates_presence_of :password, :unless => Proc.new {|password| self.password.nil?} |
14 validates :address, :presence => true, :allow_nil => true #, :mailing_address => true |
15 validates :music, :inclusion => {:in => ['no_preference', 'no_music', 'quiet_music', 'loud_music'], |
16 :message => "must be one of No Preference, No Music, Quiet Music, or Loud Music"}#, :allow_nil => true |
17 validates :smoking, :inclusion => {:in => ['no_preference', 'no_smoking', 'smoking'], |
18 :message => "must be one of No Preference, No Smoking, or Smoking"}#, :allow_nil => true |
19 |
20 # Process phone numbers |
21 after_validation do |
22 self.phone.gsub!(/^\(?\b([0-9]{3})\)?[-. ]?([0-9]{3})[-. ]?([0-9]{4})$/, '(\1) \2-\3') unless self.phone.nil? |
23 end |
24 |
25 has_and_belongs_to_many :arrangements, :join_table => "arrangements_passengers", |
26 :foreign_key => "passenger_id" |
27 has_many :organized_trips, :class_name => "Trip", :foreign_key => "organizer_id" |
28 has_and_belongs_to_many :trips, :class_name => "Trip", :join_table => "participants_trips", |
29 :foreign_key => "participant_id" |
30 has_many :invitations, :foreign_key => :invitee_id |
31 has_many :pending_trips, :through => :invitations |
32 has_many :vehicles, :foreign_key => "owner_id" |
33 |
34 devise :database_authenticatable, :registerable, :validatable |
35 attr_accessible :email, :password, :password_confirmation, :name, :phone, |
36 :address, :city, :state, :music, :smoking |
37 |
38 def upcoming_trips |
39 self.trips.select {|trip| trip.upcoming?} |
40 end |
41 end |
Generated on 2010-11-22 21:31:46 -0800 with rcov 0.9.8


Psalms 10:2
The wicked in his pride doth persecute the poor: let them be taken in the devices that they have imagined.


Teaching
In Spring 2023, I'm teaching MATH 131: Numerical Methods for Scientists and Engineers .
Previous Semesters
For TA positions held, look at the CV
In Spring 2023, I'm teaching MATH 131: Numerical Methods for Scientists and Engineers .
For TA positions held, look at the CV


This is a quick guide which will help you to start using CalenStyle.
- jQuery(required; Javascript file)
- jQuery UI (required; You can use a Regular Build of jQuery UI or a Custom Build with Draggable, Droppable & Resizable Interactions and Tooltip Widget; Javascript and CSS files)
- Hammer.js (optional; Can be used to support swipe-based navigation on mobile or you can use any touch gestures library of your choice to fire navigation events; Javascript file)
- jQuery UI Touch Punch (required if you are using CalenStyle View which uses Drag-n-Drop and Resize functionality of jQuery UI for example "DetailedMonthView", "MonthView", "WeekView", "DayView", "CustomView" or "DayEventDetailView"; To enable Touch Event support for jQuery UI; Javascript file)
- calenstyle.min.js (required)
OR
- calenstyle-custom.min.js (required; a custom build of CalenStyle to include code of the required views)
- calenstyle.min.css (required; combines calenstyle.css and calenstyle-jquery-ui-override.css)
- calenstyle-iconfont.css (required, contains font icons used in CalenStyle UI like Next & Previous Buttons, Expand & Contract Buttons, Calendar Button, Default Event Icon and icons for some common events. You can use your own font icon file or customize existing file on Font Generators like IcoMoon; but include fonts for Previous Button(".cs-icon-Prev"), Next Button(".cs-icon-Next"), Expand Button(".cs-icon-Expand"), Contract Button(".cs-icon-Contract"), Calendar Button(".cs-icon-Calendar") and Default Event Icon(".cs-icon-Event"))
You have to include fonts folder in distribution file. It includes -
- calenstyle-iconfont (Font Icon - contains font icons used in CalenStyle UI like Next & Previous Buttons, Expand & Contract Buttons, Calendar Button, Default Event Icon and icons for some common events)
You have to include images folder in distribution file. It includes -
- resize-handle.png (resize handle for resizable events in Detail Views like "Week View", "Day View", "Custom View" or "DayEventDetailView")
To serve data to CalenStyle from URL, you can use sample DataServer provided in the CalenStyle folder. This Data Server is written in node.js. So you will have to follow steps mentioned below in order to make it work.
- Install node.js
- Change directory to path of DataServer
- Run command "npm install"
- Run command "npm start"
- Use following URL in CalenStyle Plugin Initialization code - http://localhost:3000 OR http://[IPv4 address of your machine]:3000
More Details about DataServer is written in DataServer/README.md file.
To start using CalenStyle, go through code of QuickUse-Default.htm for Web and Mobile/QuickUse-Default.htm for Mobile.
<div class="calendar-1">
.calendar-1 { width: 1000px; height: 500px; margin: 0px auto; font-size: 14px; }
$(document).ready(function() { $(".calendar-1").CalenStyle( { // write settings parameters }); });
This is a list of the plugin settings parameters. This list includes parameters, their default values, all possible values that you can set and describes how to use parameters.
This is a list of callback functions that are triggered on reaching the specified condition.
- Install node from http://nodejs.org.
- Run
npm install
in the CalenStyle's root directory to install grunt's dependencies. - Run
grunt
, which will run the default task, which runsconcat
,copy
,uglify
andcssmin
.
-
grunt
- This is a Default Task.It is configured as an array of tasks.
-
concat
- Default concat task, which concatenates all .js files to create calenstyle.js -
copy
- copies all .js and .css files from /src folder to /dist folder. -
uglify
- minifies javascript code -
cssmin
- concatenates /src/calenstyle.css and /src/calenstyle-jquery-ui-override.css to /dist/calenstyle.min.css and minifies css.
-
-
grunt CalenStyleConcat
- This command helps to build a /src/calenstyle-custom.js by combining .js files for specified views. After concatenation,copy
,uglify
andcssmin
tasks will be performed.For example -This command will build a custom script by combining code for DetailedMonthView, WeekView and DayView.grunt CalenStyleConcat:DetailedMonthView:WeekView:DayView
A list of valid arguments for this commandDetailedMonthView
MonthView
WeekView
DayView
CustomView
DayEventListView
DayEventDetailView
QuickAgendaView
AgendaView
WeekPlannerView
AppointmentDayView
FilterBar
DatePicker
Pickers
If you want to display DatePicker, MonthPicker and YearPicker, then you will have to use argumentsDatePicker
andPickers
respectively.


The hideEmptyCols plugin allows you to target columns three different ways. You can use the column index, the column name, or you can specify a negative integer, which would start targeting columns from the right side of the table. This means if you were to use -2 on a table, then you would be targeting the column thats second from the right.
In the example below, were targeting three columns, using two of the methods described. We target the column indexes 0 and 3, as well as the column on the end of the table via -1. The result is an array targeting the Name, Age and Notes columns. Notice that even though those 3 columns were targeted, only the Age and Notes were hidden, because the Name column is populated with values.
| Name | Position | Office | Age | Start date | Salary | Notes |
|---|---|---|---|---|---|---|
| Name | Position | Office | Age | Start date | Salary | Notes |
| Tiger Nixon | System Architect | Edinburgh | 2011/04/25 | $320,800 | ||
| Garrett Winters | Accountant | Tokyo | 2011/07/25 | $170,750 | ||
| Ashton Cox | Junior Technical Author | San Francisco | 2009/01/12 | $86,000 | ||
| Cedric Kelly | Senior Javascript Developer | Edinburgh | 2012/03/29 | $433,060 | ||
| Airi Satou | Accountant | Tokyo | 2008/11/28 | $162,700 | ||
| Brielle Williamson | Integration Specialist | New York | 2012/12/02 | $372,000 | ||
| Herrod Chandler | Sales Assistant | San Francisco | 2012/08/06 | $137,500 | ||
| Rhona Davidson | Integration Specialist | Tokyo | 2010/10/14 | $327,900 |


diff coming down with blocks being mined at regular interval
Time Block Diff
16:54:59 3400
16:57:13 3401
16:59:14 3402
17:01:25 3403
17:03:29 3404
17:05:51 3405 11895
17:08:05 3406
17:10:15 3407
17:12:40 3408 11427
17:14:47 3409 11141
17:17:16 3410
17:19:17 3411
17:21:19 3412 10127


Resume
The real-life Iron Man. Got the full 6-month Commodore manual in 3 days, made a game, sold it for 500$. At age 12. Lived on 1$/day during college, eating mostly hot dogs to learn money doesn't really matter. Gave 3 engagement rings to my wife Tallulah, one of which I designed.
Experience
Recent
-
January 2019
Traveled to China for the groundbreaking of Tesla's Shanghai Gigafactory
-
October 2018
Filed an 'intent to use' trademark application for Teslaquila
Back then
-
2017
Purchased x.com domain from PayPal
-
September 2016
Revealed Mars colonization exploration architecture details
-
2016
In 2016, I co-founded Neuralink, a neurotechnology startup company to integrate the human brain with artificial intelligence. -
December 2015
In December 2015, I announced the creation of OpenAI, a not-for-profit artificial intelligence (AI) research company. OpenAI aims to develop artificial general intelligence in a way that is safe and beneficial to humanity. -
November 2015
Made a cameo in The Big Bang Theory episode
-
June 2015
In June 2015, I announced a design competition for students and others to build Hyperloop pods to operate on a SpaceX-sponsored mile-long track in a 2015–2017 Hyperloop pod competition. The track was used in January 2017, and Musk also started building a tunnel. -
February 2015
Donated US$10 million to the Future of Life Institute
-
January 2015
Made a cameo in The Simpsons episode
-
2014
In 2014, I announced that Tesla would allow its technology patents to be used by anyone in good faith in a bid to entice automobile manufacturers to speed up development of electric cars. -
2013
SolarCity became the second largest solar power provider
-
2012
Announced SolarCity and Tesla Collaboration
-
2007
Following the financial crisis in 2008 and after a series of escalating conflicts in 2007, Eberhard was ousted from the firm. I assumed leadership of the company as CEO and product architect. -
May 2002
I founded Space Exploration Technologies, or SpaceX, in May 2002 with US$100 million of his early fortune. I became the chief executive officer (CEO) and chief technology officer (CTO). SpaceX develops and manufactures space launch vehicles with a focus on advancing the state of rocket technology. -
March 1999
In March 1999, I co-founded X.com, an online financial services and e-mail payment company, with US$10 million from the sale of Zip2. -
1995
In 1995, I and my brother, Kimbal, started Zip2, a web software company which developed and marketed an Internet city guide for the newspaper publishing industry. The company raised money from a small group of angel investors. -
1992
Went to University of Pennsylvania to Study Business and Physics
-
June 1989
Moved to Canada to attend Queen's University
-
1983
Sold his first video game, Blastar
Languages
Favourite hobby: Twitter posts
Life projects
- SpaceX
Space Exploration Technologies Corp., doing business as SpaceX, is a private American aerospace manufacturer and space transportation services company headquartered in Hawthorne, CA.
- Tesla
Tesla, Inc. is an American company that specializes in electric vehicles, energy storage and solar panel manufacturing based in Palo Alto, California.
- Neuralink
Neuralink is an American neurotechnology company founded by Elon Musk and eight others, reported to be developing implantable interfaces.
Likes
- Making life multi-planetary 🌍
- Creating electric cars consumers dream of ⚡
- Merging human and artificial intelligence 🌐
- Spending time with my 5 sons 👨👦👦
- Going out with beautiful women 👱♀
- Reading countless books 📚


Activates any OBS hotkey without having to manually press it.
You can find the unique name of a hotkey in one of these two locations:
basic.ini
file in C:/Users/USERNAME/AppData/Roaming/obs-studio/basic/profiles/YOUR_CURRENT_PROFILE
YOURSCENENAME.JSON
file in C:/Users/USERNAME/AppData/Roaming/obs-studio/basic/scenes
[HOTKEYS]
section which should have all your unique hotkey names listed.| Box Name | Type | Description |
|---|---|---|
| hotkeyName | String | Unique name of the hotkey |


Who's Your Favorite DJ?
Put your party mode ON with animated GIF's from your favorite DJ
If your favorite DJ is not on the list add it here


My Browser is: FireFox
My Browser Version is: 9.0.1
My BBLog Addon Version is: 1.1
There's a minor mistake in the Awards section.
Team Deathmatch Medal links to Team Deathmatch ribbon but it should link to Team Deathmatch Winner ribbon.
Also one of the ribbon space is empty.
Screen shots
1920x1080 - SS croped down for convenience.
With BB Addon:
http://localhostr.com/files/EcPWQyx/capture2.png
Without BB Addon:
http://localhostr.com/files/pTLbnGn/capture.png
Also would like to thank you for this awesome addon. Keep up the great work.
Cheers,
IPX


{% load floppyforms %} {% load crispy_forms_tags %} {% block content %}
This is an overview of how disease spreads from each production type to every other production type. There are three types of spread:
Every row is a source, and every column is a destination. Click on a color block to go back and edit the spread parameters and assignments.


| Field | ||||
Field(mapFrom?: undefined)
|
||||
|
Use this field decorator to parse the corresponding field from a json response by your API.
Parameters :
|
| Model | ||||
Model(options?: undefined)
|
||||
|
Add this class decorator to your model to turn it into a See ModelOptions on how to configure the name used in URLs. This decorator is responsible for setting metadata, which is used internally, on the constructor of your class.
Parameters :
|
| toDash | ||||
toDash(name: undefined)
|
||||
|
Parameters :
|
| toPlural | ||||
toPlural(name: undefined)
|
||||
|
Parameters :
|
| toPluralDash | ||||
toPluralDash(name: undefined)
|
||||
|
Parameters :
|


Rates / service
It is an example of the fee list and services you can use. Please do not hesitate to contact us with any content not mentioned.
*Please also check the notes on the bottom of the page
Interpreter
| Half a day (Up to 4 hours) |
1 day (Up to 8 hours) |
|
|---|---|---|
| Weekday | 25,000 yen | 40,000 yen |
| Weekends · Holidays | 30,000 yen | 48,000 yen |
※ It is an interpreter from English to Japanese
※ Additional charge 5,000 yen per hour
Document Translation
| 1 Japanese character / 1 English word | |
|---|---|
| Japanese to English English to Japanese |
10 yen |
* In the case of translations of 500 characters or less, we will charge a minimum fee of ¥ 5,000
* Express rate: 20% added to the above price
Transcribed translation from video / audio
| Price | |
|---|---|
| 1 minute (video / audio actual scale) | 2,000 yen |
| 1 hour (work hours minute) | 4,000 yen |
English proofreading / native check
| Price | |
|---|---|
| 1 English words | 7 yen |
caution
· The above prices can also be consulted depending on conditions such as restraint period and quantity
· It is the price as of June 1, 2012
· It is subject to change without notice


Alerts | Logged in as Judy Wawira Gichoya | Logout
User Activity
Date
JobID
JobTitle
Status
12/12/12
1234
Test App
Complete
01/07/2013
353246
Karurumo High School
Ongoing
01/07/2013
353246
Karurumo High School
Ongoing
01/07/2013
353246
Karurumo High School
Ongoing
01/07/2013
353246
Karurumo High School
Ongoing
Your Jobs
{% for job in object_list %}
{{ job }}
{% endfor %}


I craft solutions to problems.
I build beautiful websites, sculpt unique brand identities, design silly games, code lean mobile apps, and curate a variety of systems.
About Leigh My WorkIn code, I find joy and purpose.
I am a natural problem-solver, attentive listener, and I always trust my intuition. I believe solutions are a collaborative harmony, beginning and ending with the needs of my users.
While away from the desk, I enjoy: reading, sketching, tabletop gaming, and climbing mountains.
Hatha Yoga & Raspberry Pi are my latest fascinations.
The whole of life, from the moment you are born to the moment you die, is a process of learning.
Responsive
Cross-Platform
Web Admin
UX Sorceress
Fresh Dev
Next Goals


The data shown here is simply loaded from the provided dummynumbers.csv file. The cache has been populated just right now, you will see the actual data after reloading.
Cache status


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 1
Preheat the oven to 180C/350F/Gas 4.
For the chicken, lightly oil the chicken thighs with one tablespoon of the oil, then roll in the chopped herbs to coat. Season well with salt and freshly ground black pepper.
Heat the remaining oil in an ovenproof frying pan and place the chicken in skin-side down. Press down on the chicken with a spatula and fry for 4-5 minutes, or until the skin is crisp. Turn over and fry for another 3-4 minutes, then transfer to the oven to roast for 8-10 minutes, or until the chicken is cooked through. The juices should run clear when the chicken is pierced at its thickest point.
For the ratatouille, in a another pan gently fry the onion and garlic in the oil over a medium heat until softened, about 3-4 minutes. Add the courgette and aubergine and fry until they start to take on some colour, about five minutes. Stir in the chopped tomato, tomato purée, water and olives. Reduce the heat and simmer for 2-3 minutes before stirring through the fresh basil.
For the olive and red wine sauce, bring the wine in a pan to the boil and crumble in the stock cube, stirring until the cube has dissolved. Add the hot water, then reduce the heat and simmer for 4-5 minutes before stirring in the olives.
To serve, place the chicken thighs on a serving plate and spoon the ratatouille on the side. Drizzle the olive red wine sauce around the edge of the plate and serve.


Generic Function Index
ADD-RUCKSACK-ROOT
Adds an object to the root set of a rucksack.
ALLOCATE-BLOCK
Allocates a block of the requested size and returns the heap position of that block.
BLOCK-SIZE
Returns the size of the block starting at the specified position.
CACHE-COMMIT
Makes sure that all changes to the cache are written to disk.
CACHE-COUNT
Returns the number of objects (both dirty and non-dirty) in the cache.
CACHE-CREATE-OBJECT
Adds a new object to the cache and returns an object id that can be used to retrieve the object from the cache.
CACHE-DELETE-OBJECT
Removes an object-id from the cache and from the object table, so the object-id can be reused for another object later.
CACHE-GET-OBJECT
Retrieves the object with the given id from the cache and returns that object.
CACHE-RECOVER
Undoes partially committed transactions to ensure that the cache is in a consistent state.
CACHE-ROLLBACK
Undoes all cache changes that were made since the last cache-commit.
CACHE-SIZE
Returns the number of non-dirty objects that the cache may keep in memory.
CLOSE-CACHE
Closes the cache.
CLOSE-TRANSACTION
Removes a transaction from the set of open transactions.
DELETE-RUCKSACK-ROOT
Delete an object from the root set of a rucksack.
FIND-CONFLICTING-TRANSACTION
Tries to find an open transaction that has modified the object with the given object-id and is older than the given transaction.
HEAP-END
Returns the end of the heap.
SETF HEAP-END
Modifies the end of the heap.
HEAP-START
Returns the position of the first block in the heap.
HEAP-STREAM
Returns the heap's stream.
INITIALIZE-BLOCK
MAP-RUCKSACK-ROOTS
Applies a function to all objects in the root set of a rucksack.
MAP-TRANSACTIONS
Applies a function to each open transaction in a cache.
OBJECT-ID
Returns the object id of a persistent-object or persistent-data.
OPEN-TRANSACTION
Adds a transaction to the set of open transactions.
P-EQL
The persistent equivalent of EQL.
RUCKSACK-ADD-CLASS-INDEX
RUCKSACK-ADD-SLOT-INDEX
Creates a new slot index for the slot designated by CLASS-DESIGNATOR and SLOT.
RUCKSACK-CACHE
Returns the cache for a rucksack.
RUCKSACK-CLASS-INDEX
Returns the class index for a class designator.
RUCKSACK-COMMIT
Ensures that all in-memory data is saved to disk.
RUCKSACK-DELETE-OBJECT
Removes OBJECT from RUCKSACK, i.
RUCKSACK-DIRECTORY
Returns a pathname for the directory that contains all files of a rucksack.
RUCKSACK-MAKE-CLASS-INDEX
Creates a new class index and returns that index.
RUCKSACK-MAP-CLASS
FUNCTION is a unary function that gets called for all instances of the specified class.
RUCKSACK-MAP-CLASS-INDEXES
FUNCTION must take two arguments: a class name and a class index.
RUCKSACK-MAP-SLOT
FUNCTION is a unary function that gets called for all instances of the specified class that have a slot value matching the EQUAL, MIN, MAX INCLUDE-MIN and INCLUDE-MAX arguments (s
RUCKSACK-MAP-SLOT-INDEXES
FUNCTION must take three arguments: a class name, a slot name and a slot index.
RUCKSACK-MAYBE-INDEX-CHANGED-SLOT
This function is called after a slot has changed.
RUCKSACK-MAYBE-INDEX-NEW-OBJECT
Adds the object id of OBJECT to the class index for the class designated by CLASS-DESIGNATOR.
RUCKSACK-REMOVE-CLASS-INDEX
RUCKSACK-REMOVE-SLOT-INDEX
RUCKSACK-ROLLBACK
.
RUCKSACK-ROOT-P
Returns true iff OBJECT is a member of the root set of a rucksack.
RUCKSACK-ROOTS
Returns a list with all objects in the root set of a rucksack.
RUCKSACK-SLOT-INDEX
Returns the slot index for the slot specified by CLASS-DESIGNATOR and SLOT.
RUCKSACK-UPDATE-CLASS-INDEX
Compares the current class index for CLASS to the class index that's specified in the :INDEX class option of CLASS.
RUCKSACK-UPDATE-SLOT-INDEXES
Compares the current slot indexes for CLASS to the slot indexes that are specified in the slot options for the direct slots of CLASS.

TRANSACTION-CHANGED-OBJECT
If the given transaction has modified the object with the given object id, this function returns the modified object.
TRANSACTION-COMMIT-1
Save all modified objects to disk.
TRANSACTION-OLDER-P
Returns true iff transaction A is older than transaction B.
TRANSACTION-ROLLBACK-1
TRANSACTION-START-1
Creates and returns a new transaction.
UNDO-OBJECT-COMMIT
If the object version list contains a version with the given transaction-id, unhook that version from the list.
UPDATE-PERSISTENT-INSTANCE-FOR-REDEFINED-CLASS


Skills
Technical
Python
Libraries needed in Machine Learning (NumPy - Pandas - Sklearn - MAtplotlib – Seaborn)
Databases
SQL, PL/SQL, Data Modelling, Data Preprocessing, ETL, Data Pipelines, Data
Warehouse, Business Intelligence Tools (SSIS), Oracle, Microsoft SQL Server, MySQL,
Relational Database (RDBMS), Data Visualization, Tableau.
Machine Learning
Supervised Models: K-Nearest Neighbor (KNN) - Support Vector
Machine (SVM) - Naive Bayes - Decision Tree - Random Forest
Unsupervised Models: K-Means Clustering - Hierarchical Clustering
Deep Learning
ANN, CNN, RNN, LSTM, Tensorflow, Keras, Hyperparameter Tuning
Model Selection
Precision & Recall for Classification - R2 Square & Mean Square Error for Regression
Computer Vision
Image Manipulation, Data Augmentation, Image Classification & Recognition, Face Detection.
Others
Parameter Tuning (GridSearchCV), Feature Engineering , Exploratory Data Analysis , Data Mining , GitHub ,Microsoft office , good statistics knowledge , Management
Practical
Quality work check , Analytical and data interpretation skills , problem solving
skills , Drive projects with minimal guidance , challenge thinking and offering
opinions , clear communication of results
Soft Skills
Excellent communication skills ( verbal , written ) , flexibility in work , Good
listening skills , Work Under Pressure , fluent in English


OpenPreferences()
语法
Result = OpenPreferences(Filename$ [, Flags])概要
Opens a previously existing preference file.
参数
Filename$ The filename of the preference file. Flags (可选) 可以是下列值的组合︰ #PB_Preference_NoSpace: no spaces will be put around the equal sign joining key and values. It can be useful when dealing with external preferences files which doesn't accept spaces around equal sign. #PB_Preference_GroupSeparator: add an empty line between the groups to ease readability of the file.
返回值
Nonzero if the file has been successfully opened, zero otherwise.
备注
If the file wasn't found or can't be opened, it is still possible to use the read functions and it will return the specified default value. It is very useful to initialize in one step the program variables. The functions like ReadPreferenceString() can be used to read the preference values stored in the file.
To remove a key or a group, use RemovePreferenceKey() and RemovePreferenceGroup(). To create or change the current group, use PreferenceGroup().
It is possible to change existing values with WritePreferenceString() and similar functions.
Once all write operations are done, ClosePreferences() needs to be called to really write the preferences back to disk (if it has been modified inbetween).
示例
; Open a preference file OpenPreferences(#PB_Compiler_Home +"Examples\Sources\Data\test.pref") ; Examine Groups ExaminePreferenceGroups() ; For each group While NextPreferenceGroup() texte$ = texte$ + PreferenceGroupName() + #LF$ ; its name ; Examine keys for the current group ExaminePreferenceKeys() ; For each key While NextPreferenceKey() texte$ = texte$ + PreferenceKeyName() + " = " + PreferenceKeyValue() + #LF$ ; its name and its data Wend texte$ = texte$ + #LF$ Wend ; Display all groups and all keys with datas MessageRequester("test.pref",texte$) ; Close the preference file ClosePreferences()
参阅
ClosePreferences()
已支持操作系统
所有


--- layout: post title: lederhosen with ipod controls date: '2008-04-14T23:44:38+01:00' tags: [] tumblr_url: http://backlog.robbevan.com/post/31769919/lederhosen-with-ipod-controls ---
Lederhosen with iPod controls