1. Introduction
When the first CSS specification was published, all of CSS was contained in one document that defined CSS Level 1. CSS Level 2 was defined also by a single, multi-chapter document. However for CSS beyond Level 2, the CSS Working Group chose to adopt a modular approach, where each module defines a part of CSS, rather than to define a single monolithic specification. This breaks the specification into more manageable chunks and allows more immediate, incremental improvement to CSS.
Since different CSS modules are at different levels of stability, the CSS Working Group has chosen to publish this profile to define the current scope and state of Cascading Style Sheets as of mid 2017. This profile includes only specifications that we consider stable and for which we have enough implementation experience that we are sure of that stability.
Note: This is not intended to be a CSS Desktop Browser Profile: inclusion in this profile is based on feature stability only and not on expected use or Web browser adoption. This profile defines CSS in its most complete form.
Note: Although we don’t anticipate significant changes to the specifications that form this snapshot, their inclusion does not mean they are frozen. The Working Group will continue to address problems as they are found in these specs. Implementers should monitor www-style and/or the CSS Working Group Blog for any resulting changes, corrections, or clarifications.
1.1. Background: The W3C Process and CSS
This section is non-normative.
In the W3C Process, a Recommendation-track document passes through three levels of stability, summarized below:
- Working Draft (WD)
-
This is the design phase of a W3C spec. The WG iterates the spec in response to internal and external feedback.
The first official Working Draft is designated the “First Public Working Draft” (FPWD). In the CSSWG, publishing FPWD indicates that the Working Group as a whole has agreed to work on the module, roughly as scoped out and proposed in the editor’s draft.
The transition to the next stage is sometimes called “Last Call Working Draft” (LCWD) phase. The CSSWG transitions Working Drafts once we have resolved all known issues, and can make no further progress without feedback from building tests and implementations.
This “Last Call for Comments” sets a deadline for reporting any outstanding issues, and requires the WG to specially track and address incoming feedback. The comment-tracking document is the Disposition of Comments (DoC). It is submitted along with an updated draft for the Director’s approval, to demonstrate wide review and acceptance.
- Candidate Recommendation (CR)
-
This is the testing phase of a W3C spec.
Notably, this phase is about using tests and implementations to test the specification:
it is not about testing the implementations.
This process often reveals more problems with the spec,
and so a Candidate Recommendation will morph over time in response to implementation and testing feedback,
though usually less so than during the design phase (WD).
Demonstration of two correct, independent implementations of each feature is required to exit CR, so in this phase the WG builds a test suite and generates implementation reports.
The transition to the next stage is “Proposed Recommendation” (PR). During this phase the W3C Advisory Committee must approve the transition to REC.
- Recommendation (REC)
- This is the completed state of a W3C spec and represents a maintenance phase. At this point the WG only maintains an errata document and occasionally publishes an updated edition that incorporates the errata back into the spec.
An Editor’s Draft is effectively a live copy of the editors’ own working copy. It may or may not reflect Working Group consensus, and can at times be in a self-inconsistent state. (Because the publishing process at W3C is time-consuming and onerous, the Editor’s Draft is usually the best (most up-to-date) reference for a spec. Efforts are currently underway to reduce the friction of publishing, so that official drafts will be regularly up-to-date and Editor’s Drafts can return to their original function as scratch space.)
2. Cascading Style Sheets (CSS) — The Official Definition
As of 2017, Cascading Style Sheets (CSS) is defined by the following specifications.
- CSS Level 2, latest revision (including errata) [CSS2]
- This defines the core of CSS, parts of which are overridden by later specifications. We recommend in particular reading Chapter 2, which introduces some of the basic concepts of CSS and its design principles.
- CSS Syntax Level 3 [CSS-SYNTAX-3]
- Replaces CSS2§4.1, CSS2§4.2, CSS2§4.4, and CSS2§G, defining how CSS is parsed.
- CSS Style Attributes [CSS-STYLE-ATTR]
- Defines how CSS declarations can be embedded in markup attributes.
- Media Queries Level 3 [CSS3-MEDIAQUERIES]
- Replaces CSS2§7.3 and expands on the syntax for media-specific styles.
- CSS Conditional Rules Level 3 [CSS3-CONDITIONAL]
- Replaces CSS2§7.2, updating the definition of @media rules to allow nesting, and introduces @supports rules for feature-support queries.
- CSS Namespaces [CSS3-NAMESPACE]
- Introduces an @namespace rule to allow namespace-prefixed selectors.
- Selectors Level 3 [SELECT]
- Replaces CSS2§5 and CSS2§6.4.3, defining an extended range of selectors.
- CSS Cascading and Inheritance Level 3 [CSS-CASCADE-3]
- Replaces CSS2§1.4.3 and CSS2§6
- CSS Values and Units Level 3 [CSS-VALUES-3]
- Replaces CSS2§<IP_ADDRESS>, CSS2§4.3, and CSS2§A.2.1–3, defining CSS’s property definition syntax and expanding its set of units.
- CSS Color Level 3 [CSS3-COLOR]
- Replaces CSS2§4.3.6, CSS2§14.1, and CSS2§18.2, defining an extended range of color values. Also introduces the opacity property.
- CSS Backgrounds and Borders Level 3 [CSS3-BACKGROUND]
- Replaces CSS2§8.5 and CSS2§14.2, providing more control of backgrounds and borders, including layered background images, image borders, and drop shadows.
- CSS Image Values and Replaced Content Level 3 [CSS3-IMAGES]
- Provides a new foundation text for the sizing of replaced elements (such as images), adds additional controls to their sizing and orientation, and introduces syntax for gradients as images in CSS.
- CSS Fonts Level 3 [CSS-FONTS-3]
- Replaces CSS2§15 and provides more control over font choice and feature selection.
- CSS Multi-column Layout Level 1 [CSS3-MULTICOL]
- Introduces multi-column flows to CSS layout.
- CSS User Interface Module Level 3 [CSS-UI-3]
- Replaces CSS2§18.1 and CSS2§18.4, defining cursor, outline, and several new CSS features that also enhance the user interface.
- CSS Compositing and Blending Level 1 [COMPOSITING]
- Defines the compositing and blending of overlaid content and introduces features to control their modes.
- CSS Writing Modes Level 3 [CSS-WRITING-MODES-3]
- Defines CSS support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).
- CSS Transitions Level 1 [CSS3-TRANSITIONS] and CSS Animations Level 1 [CSS3-ANIMATIONS]
- Define mechanisms for transitioning the computed values of CSS properties over time.
- CSS Flexible Box Module Level 1 [CSS-FLEXBOX-1]
- Introduces a flexible linear layout model for CSS.
- CSS Transforms Level 1 [CSS3-TRANSFORMS]
- Introduces graphical transformations to CSS.
- CSS Custom Properties for Cascading Variables Module Level 1 [CSS-VARIABLES-1]
- Introduces cascading variables as a new primitive value type that is accepted by all CSS properties, and custom properties for defining them.
- CSS Text Module Level 3 [CSS-TEXT-3]
- Defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
- CSS Counter Styles Level 3 [CSS-COUNTER-STYLES-3]
- Expands the possible values of <counter-style> and provides an @counter-style syntax for customized counter styles.
- CSS Masking Level 1 [CSS-MASKING-1]
- Replaces CSS2§11.1.2 and introduces more powerful ways of clipping and masking content.
- CSS Shapes Module Level 1 [CSS-SHAPES-1]
- Extends floats to effect non-rectangular wrapping shapes.
- CSS Text Decoration Level 3 [CSS-TEXT-DECOR-3]
- Replaces CSS2§16.3, providing more control over text decoration lines and adding the ability to specify text emphasis marks and text shadows.
- CSS Will Change Level 1 [CSS-WILL-CHANGE-1]
- Introduces a performance hint property called will-change.
We hope to incorporate them into a future snapshot.
A list of all CSS modules, stable and in-progress, and their statuses can be found at the CSS Current Work page.
2.1. CSS Levels
Cascading Style Sheets does not have versions in the traditional sense; instead it has levels. Each level of CSS builds on the previous, refining definitions and adding features. The feature set of each higher level is a superset of any lower level, and the behavior allowed for a given feature in a higher level is a subset of that allowed in the lower levels. A user agent conforming to a higher level of CSS is thus also conformant to all lower levels.
- CSS Level 1
- The CSS Working Group considers the CSS1 specification to be obsolete. CSS Level 1 is defined as all the features defined in the CSS1 specification (properties, values, at-rules, etc), but using the syntax and definitions in the CSS2.1 specification. CSS Style Attributes defines its inclusion in element-specific style attributes.
- CSS Level 2
-
Although the CSS2 specification is technically a W3C Recommendation, it passed into the Recommendation stage
before the W3C had defined the Candidate Recommendation stage. Over time
implementation experience and further review has brought to light many problems
in the CSS2 specification, so instead of expanding an already unwieldy
errata list, the CSS Working Group chose to define CSS Level 2
Revision 1 (CSS2.1). In case of any conflict between the two specs
CSS2.1 contains the definitive definition.
Once CSS2.1 became Candidate Recommendation—effectively though not officially the same level of stability as CSS2—obsoleted the CSS2 Recommendation. Features in CSS2 that were dropped from CSS2.1 should be considered to be at the Candidate Recommendation stage, but note that many of these have been or will be pulled into a CSS Level 3 working draft, in which case that specification will, once it reaches CR, obsolete the definitions in CSS2.
The CSS2.1 specification defines CSS Level 2 and the CSS Style Attributes specification defines its inclusion in element-specific style attributes.
- CSS Level 3
-
CSS Level 3 builds on CSS Level 2 module by module, using the CSS2.1
specification as its core. Each module adds functionality and/or
replaces part of the CSS2.1 specification. The CSS Working Group
intends that the new CSS modules will not contradict the CSS2.1
specification: only that they will add functionality and refine
definitions. As each module is completed, it will be plugged in to
the existing system of CSS2.1 plus previously-completed modules.
From this level on modules are levelled independently: for example Selectors Level 4 may well be completed before CSS Line Module Level 3. Modules with no CSS Level 2 equivalent start at Level 1; modules that update features that existed in CSS Level 2 start at Level 3.
- CSS Level 4 and beyond
- There is no CSS Level 4. Independent modules can reach level 4 or beyond, but CSS the language no longer has levels. ("CSS Level 3" as a term is used only to differentiate it from the previous monolithic versions.)
2.2. CSS Profiles
Not all implementations will implement all functionality defined in CSS.
In the past, the Working Group published a few Profiles, which were meant to define the minimal subset of CSS that various classes of User Agents were expected to support.
This effort has been discontinued, as the Working Group was not finding it effective or useful, and the profiles previously defined are now unmaintained.
Note: Partial implementations of CSS, even if that subset is an official profile, must follow the forward-compatible parsing rules for partial implementations.
3. Requirements for Responsible Implementation of CSS
The following sections define several conformance requirements for implementing CSS responsibly, in a way that promotes interoperability in the present and future.
3.1. Partial Implementations
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 property 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.
3.2. Implementations of Unstable and Proprietary Features
To avoid clashes with future stable CSS features, the CSSWG recommends the following best practices for the implementation of unstable features and proprietary extensions to CSS:
3.2.1. Experimentation and Unstable Features
Implementations of unstable features that are described in W3C specifications but are not interoperable should not be released broadly for general use; but may be released for limited, experimental use in controlled environments.
Why?
We want to allow both authors and implementors to experiment with the feature and give feedback, but prevent authors from relying on them in production websites and thereby accidentally "locking in" (through content dependence) certain syntax or behavior that might change later.A CSS feature is considered unstable until its specification has reached the Candidate Recommendation (CR) stage in the W3C process. In exceptional cases, the CSSWG may additionally, by an officially-recorded resolution, add pre-CR features to the set that are considered safe to release for broad use.
Note: Vendors should consult the WG explicitly and not make assumptions on this point, as a pre-CR spec that hasn’t changed in awhile is usually more out-of-date than stable.
The current list of pre-CR features approved for wide release consists of:
- CSS Animations [CSS3-ANIMATIONS]
- CSS Transitions [CSS3-TRANSITIONS]
- CSS Transforms [CSS3-TRANSFORMS]
- The min-content, max-content, and fit-content keywords from [CSS-SIZING-3]
- The :dir() and :lang() selectors from [SELECTORS4]
3.2.2. Proprietary and Non-standardized Features
To avoid clashes with future CSS features, the CSS2.1 specification reserves a prefixed syntax [CSS2] for proprietary and experimental extensions to CSS. A CSS feature is a proprietary extension if it is meant for use in a closed environment accessible only to a single vendor’s user agent(s). A UA should support such proprietary extensions only through a vendor-prefixed syntax and not expose them to open (multi-UA) environments such as the World Wide Web.
Why?
The prefixing requirement allows shipping specialized features in closed environments without conflicting with future additions to standard CSS. The restriction on exposure to open systems is to prevent accidentally causing the public CSS environment to depend on an unstandardized proprietary extensions.Even if a feature is intended to eventually be used in the Web, if it hasn’t yet been standardized it should still not be exposed to the Web.
3.2.3. Market Pressure and De Facto Standards
If a feature is unstable (i.e. the spec has not stabilized yet), yet
-
at least three UAs implement the feature (or a UA has broken the other rules and shipped for broad use an unstable or otherwise non-standard feature in a production release),
-
and the implementations have rough interoperability,
-
and the CSS Working Group has recorded consensus that this feature should exist and be released,
implementers may ship that feature unprefixed in broad-release builds. Rough interoperability is satisfied by a subjective judgment that even though there may be differences, the implementations are sufficiently similar to be used in production websites for a substantial number of use cases.
Note that the CSSWG must still be consulted to ensure coordination across vendors and to ensure sanity review by the CSS experts from each vendor. Note also that rough interoperability still usually means painful lack of interop in edge (or not-so-edge) cases, particularly because details have not been ironed out through the standards review process.
Why?
If a feature is sufficiently popular that three or more browsers have implemented it before it’s finished standardization, this clause allows releasing the pressure to ship. Also, if a feature has already escaped into the wild and sites have started depending on it, pretending it’s still “experimental” doesn’t help anyone. Allowing others to ship unprefixed recognizes that the feature is now de facto standardized and encourages authors to write cross-platform code.<IP_ADDRESS>. Vendor-prefixing Unstable Features
When exposing such a standards-track unstable feature to the Web in a production release, implementations should support both vendor-prefixed and unprefixed syntaxes for the feature. Once the feature has stabilized and the implementation is updated to match interoperable behavior, support for the vendor-prefixed syntax should be removed.
Why?
This is recommended so that authors can use the unprefixed syntax to target all implementations, but when necessary, can target specific implementations to work around incompatibilities among implementations as they get ironed out through the standards/bugfixing process.The lack of a phase where only the prefixed syntax is supported greatly reduces the risk of stylesheets being written with only the vendor-prefixed syntax. This in turn allows UA vendors to retire their prefixed syntax once the feature is stable, with a lower risk of breaking existing content. It also reduces the need occasionally felt by by some vendors to support a feature with the prefix of another vendor, due to content depending on that syntax.
Anyone promoting unstable features to authors should document them using their standard unprefixed syntax, and avoid encouraging the use of the vendor-prefixed syntax for any purpose other than working around implementation differences.
<IP_ADDRESS>. Preserving the Openness of CSS
In order to preserve the open nature of CSS as a technology, vendors should make it possible for other implementors to freely implement any features that they do ship. To this end, they should provide spec-editing and testing resources to complete standardization of such features, and avoid other obstacles (e.g., platform dependency, licensing restrictions) to their competitors shipping the feature.
3.3. Implementations of CR-level Features
Once a specification reaches the Candidate Recommendation stage, implementers should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec, and should avoid exposing a prefixed variant of that feature.
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.
4. Indices
These sections are non-normative.
4.1. Terms Index
- a
- additive tuple
- alignment baseline
- alignment container
- alignment context
- alignment subject
- an+b
- animation-tainted
- are a valid escape
- ascii case-insensitive
- as conformance class
- at-rule
- aural "box" model
- authoring tool
- automatic minimum size
- avoid break values
- b
- baseline alignment
- baseline alignment preference
- baseline content-alignment
- baseline self-alignment
- baseline set
- baseline-sharing group
- border
- box alignment properties
- box-corner
- box fragment
- break
- cascade
- check if three code points would start an identifier
- check if three code points would start a number
- check if two code points are a valid escape
- circled-lower-latin
- clipping path
- clipping region
- code point
- collapsed flex item
- column break
- compatible baseline alignment preferences
- component value
- conditional group rule
- conditional group rules
- conformance::authoring tool
- conformance::processor
- conformance::style sheet
- consume a component value
- consume a declaration
- consume a function
- consume a list of declarations
- consume a list of rules
- consume a name
- consume an at-rule
- consume an escaped code point
- consume an ident-like token
- consume a number
- consume a numeric token
- consume a qualified rule
- consume a simple block
- consume a string token
- consume a token
- consume a unicode-range token
- consume a url token
- consume comments
- consume the next input token
- consume the remnants of a bad url
- content
- content-based minimum size
- content-distribution
- content-distribution properties
- content size
- content size suggestion
- convert a string to a number
- coordinated self-alignment preference
- counter style
- counter symbol
- cross axis
- cross-axis
- cross-axis baseline set
- cross dimension
- cross-end
- cross size
- cross-size
- cross size property
- cross-start
- css
- cssconditionrule
- cssgroupingrule
- cssmediarule
- css qualified name
- csssupportsrule
- current input code point
- current input token
- current tuple
- custom property
- declaration
- decode
- default namespace
- definite
- definite size
- destination
- determine the fallback encoding
- dice
- digit
- display
- distributed alignment
- document
- documents
- ending token
- end of the range
- environment encoding
- eof code point
- escaping
- expanded name
- fallback alignment
- first-baseline alignment
- first-baseline content-alignment
- first baselines
- first-baseline self-alignment
- first baseline set
- first cross-axis baseline set
- first main-axis baseline set
- first symbol value
- flex base size
- flex basis
- flex container
- flex direction
- flex factor
- flex formatting context
- flex grow factor
- flexible
- flexible length
- flex item
- flex layout
- flex-level
- flex line
- flex shrink factor
- font-family
- footnote
- forced break
- forced break values
- fragment
- fragmentainer
- fragmentation
- fragmentation break
- fragmentation container
- fragmentation context
- fragmentation direction
- fragmentation root
- fragmented flow
- frequency
- fully inflexible
- function
- general_enclosed
- generate a counter
- generate a counter representation
- generate baselines
- get an encoding
- go
- group_rule_body
- group rule body
- gutter
- hex digit
- hypothetical cross size
- hypothetical main size
- identifier
- ignored
- indefinite
- indefinite size
- initial free space
- initial representation for the counter value
- input stream
- integer
- interpreter
- invalid
- invalid at computed-value time
- last-baseline alignment
- last-baseline content-alignment
- last baselines
- last-baseline self-alignment
- last baseline set
- last cross-axis baseline set
- last main-axis baseline set
- letter
- line break
- list-style-image
- list-style-type
- lowercase letter
- main axis
- main-axis
- main-axis baseline set
- main dimension
- main-end
- main-size
- main size
- main size property
- main-start
- margin
- mask border image
- mask border image area
- mask image
- mask layer image
- mask painting area
- mask-position
- mask positioning area
- mask-size
- max cross size
- max cross size property
- maximum allowed code point
- max main size
- max main size property
- media
- '@media' rule
- min cross size
- min cross size property
- min main size
- min main size property
- monolithic
- multi-line flex container
- name code point
- namespace prefix
- name-start code point
- nested_statement
- newline
- next input code point
- next input token
- non-ascii code point
- non-negative-number
- non-printable code point
- number
- or
- order-modified document order
- overflow alignment
- padding
- page break
- pagination
- parse
- parse a comma-separated list of component values
- parse a component value
- parse a css stylesheet
- parse a declaration
- parse a list of component values
- parse a list of declarations
- parse a list of rules
- parse a rule
- parse a stylesheet
- parse error
- parse something according to a css grammar
- participates in baseline alignment
- pending-substitution value
- percentage
- positional alignment
- preserved tokens
- propagate
- propagation
- qualified rule
- reconsume the current input code point
- reconsume the current input token
- region break
- remaining fragmentainer extent
- remaining free space
- renderer
- representation
- scaled flex shrink factor
- self-alignment
- self-alignment properties
- serialize an <an+b> value
- shared alignment context
- simple block
- single-line flex container
- source
- specified size
- specified size suggestion
- spread break
- start of the range
- starts with an identifier
- starts with a number
- starts with a valid escape
- start with an identifier
- start with a number
- static-position rectangle
- stretched
- strings
- stroke bounding box
- strut size
- style attribute
- style rule
- style sheet
- style sheet!!as conformance class
- substitute a var()
- support
- supports_condition
- supports_condition_in_parens
- supports_conjunction
- supports_declaration_condition
- supports_disjunction
- supports_negation
- supports_rule
- '@supports' rule
- supports_sym
- surrogate code point
- synthesize baseline
- synthesized baseline
- target main size
- time
- top-level flag
- transferred size
- transferred size suggestion
- triangle
- trinary
- ua
- unforced break
- upper-alpha-legal
- uppercase letter
- use a negative sign
- user agent
- uses a negative sign
- var() substitution
- visual box model
- whitespace
- would start an identifier
- would start a number
4.2. Selector Index
4.3. At-Rule Index
4.4. Property Index
- --*
- align-content
- align-items
- align-self
- box-decoration-break
- break-after
- break-before
- break-inside
- clip
- clip-path
- clip-rule
- column-gap
- cue
- cue-after
- cue-before
- flex
- flex-basis
- flex-direction
- flex-flow
- flex-grow
- flex-shrink
- flex-wrap
- gap
- grid-column-gap
- grid-gap
- grid-row-gap
- justify-content
- justify-items
- justify-self
- mask
- mask-border
- mask-border-mode
- mask-border-outset
- mask-border-repeat
- mask-border-slice
- mask-border-source
- mask-border-width
- mask-clip
- mask-composite
- mask-image
- mask-mode
- mask-origin
- mask-position
- mask-repeat
- mask-size
- mask-type
- order
- orphans
- pause
- pause-after
- pause-before
- place-content
- place-items
- place-self
- rest
- rest-after
- rest-before
- row-gap
- speak
- speak-as
- voice-balance
- voice-duration
- voice-family
- voice-pitch
- voice-range
- voice-rate
- voice-stress
- voice-volume
- widows
- will-change
4.5. Values Index
- add
- additive
- alpha
- alphabetic
- arabic-indic
- armenian
-
auto
- in css-align-3, for align-self
- in css-align-3, for justify-self
- in css-break-3, for break-before, break-after
- in css-break-3, for break-inside, page-break-inside
- in css-counter-styles-3, for @counter-style/range
- in css-counter-styles-3, for @counter-style/speak-as
- in css-flexbox-1, for align-items, align-self
- in css-flexbox-1, for flex-basis
- in css-flexbox-1, for min-width, min-height
- in css-masking-1, for mask-mode
- in css-will-change-1, for will-change
- avoid
- avoid-column
- avoid-page
- avoid-region
- baseline
- bengali
- border-box
- bullets
- cambodian
- center
- circle
- cjk-decimal
- cjk-earthly-branch
- cjk-heavenly-stem
- cjk-ideographic
- clone
- column
- column-reverse
- content
- content-box
- contents
- <counter-style-name>
- <custom-ident>
- cyclic
- decimal
- decimal-leading-zero
- devanagari
- disc
- disclosure-closed
- disclosure-open
- end
- ethiopic-numeric
- evenodd
- exclude
- extends
- fill
- fill-box
- first
- first baseline
- fixed
- flex
- <'flex-basis'>
- flex-end
- <'flex-grow'>
- <'flex-shrink'>
- flex-start
- georgian
- gujarati
- gurmukhi
- hebrew
- hiragana
- hiragana-iroha
- inline-flex
- <integer>
- intersect
- japanese-formal
- japanese-informal
- kannada
- katakana
- katakana-iroha
- khmer
- korean-hangul-formal
- korean-hanja-formal
- korean-hanja-informal
- lao
- last
- last baseline
- left
- legacy
- lower-alpha
- lower-armenian
- lower-greek
- lower-latin
- lower-roman
- luminance
- malayalam
- margin-box
- match-source
- mongolian
- myanmar
- no-clip
- none
- nonzero
- normal
- nowrap
- <number>
- numbers
- numeric
- objectboundingbox
- oriya
- padding-box
- page
- persian
- recto
- region
- right
- row
- row-reverse
- safe
- scroll-position
- self-end
- self-start
- simp-chinese-formal
- simp-chinese-informal
- slice
- space-around
- space-between
- space-evenly
- spell-out
- square
- start
- stretch
- stroke-box
- subtract
- symbolic
- tamil
- telugu
- thai
- tibetan
- trad-chinese-formal
- trad-chinese-informal
- unsafe
- upper-alpha
- upper-armenian
- upper-latin
- upper-roman
- <url>
- userspaceonuse
- verso
- view-box
- words
- wrap
- wrap-reverse
5. Acknowledgements
Special thanks to Florian Rivoal for creating the initial draft of the §3.2.1 Experimentation and Unstable Features recommendations.


| chartSeries {quantmod} | R Documentation |
Charting tool to create standard financial charts given a time series like object. Serves as the base function for future technical analysis additions. Possible chart styles include candles, matches (1 pixel candles), bars, and lines. Chart may have white or black background.
reChart
allows for dynamic changes to the chart without
having to respecify the full chart parameters.
chartSeries(x, type = c("auto", "candlesticks", "matchsticks", "bars","line"), subset = NULL, show.grid = TRUE, name = NULL, time.scale = NULL, log.scale = FALSE, TA = 'addVo()', TAsep=';', line.type = "l", bar.type = "ohlc", theme = chartTheme("black"), layout = NA, major.ticks='auto', minor.ticks=TRUE, yrange=NULL, plot=TRUE, up.col,dn.col,color.vol = TRUE, multi.col = FALSE, ...) reChart(type = c("auto", "candlesticks", "matchsticks", "bars","line"), subset = NULL, show.grid = TRUE, name = NULL, time.scale = NULL, line.type = "l", bar.type = "ohlc", theme = chartTheme("black"), major.ticks='auto', minor.ticks=TRUE, yrange=NULL, up.col,dn.col,color.vol = TRUE, multi.col = FALSE, ...)
x |
an OHLC object - see details |
type |
style of chart to draw |
subset |
xts style date subsetting argument |
show.grid |
display price grid lines? |
name |
name of chart |
time.scale |
what is the timescale? automatically deduced (broken) |
log.scale |
should the y-axis be log-scaled? |
TA |
a vector of technical indicators and params, or character strings |
TAsep |
TA delimiter for TA strings |
line.type |
type of line in line chart |
bar.type |
type of barchart - ohlc or hlc |
theme |
a chart.theme object |
layout |
if |
major.ticks |
where should major ticks be drawn |
minor.ticks |
should minor ticks be draw? |
yrange |
override y-scale |
plot |
should plot be drawn |
up.col |
up bar/candle color |
dn.col |
down bar/candle color |
color.vol |
color code volume? |
multi.col |
4 color candle pattern |
... |
additional parameters |
Currently displays standard style OHLC charts familiar in financial applications, or line charts when not passes OHLC data. Works with objects having explicit time-series properties.
Line charts are created with close data, or from single column time series.
The subset
argument can be used to specify a
particular area of the series to view. The underlying
series is left intact to allow for TA functions to
use the full data set. Additionally, it is possible
to use syntax borrowed from the first
and last
functions, e.g. ‘last 4 months’.
TA
allows for the inclusion of a variety of
chart overlays and tecnical indicators. A full list is
available from addTA
. The default TA argument is
addVo()
- which adds volume, if available, to the
chart being drawn.
theme
requires an object of class chart.theme
, created
by a call to chartTheme
. This function can be used to modify the
look of the resulting chart. See chart.theme
for details.
line.type
and bar.type
allow further fine tuning of
chart styles to user tastes.
multi.col
implements a color coding scheme used in some
charting applications, and follows the following rules:
grey => Op[t] < Cl[t] and Op[t] < Cl[t-1]
white => Op[t] < Cl[t] and Op[t] > Cl[t-1]
red => Op[t] > Cl[t] and Op[t] < Cl[t-1]
black => Op[t] > Cl[t] and Op[t] > Cl[t-1]
reChart
takes any number of arguments from the original
chart call — and redraws the chart with the updated parameters.
One item of note: if multiple color bars/candles are desired,
it is necessary to respecify the theme
argument. Additionally
it is not possible to change TA parameters at present. This must be
done with addTA/dropTA/swapTA/moveTA commands.
Returns a standard chart plus volume, if available, suitably scaled.
If plot=FALSE
a chob object will be returned.
Most details can be fine-tuned within the function, though the code does a reasonable job of scaling and labelling axes for the user.
The current implementation maintains a record of actions carried
out for any particular chart. This is used to recreate the original when
adding new indicator. A list of applied TA actions is available with a call
to listTA
. This list can be assigned to a variable and used in new
chart calls to recreate a set of technical indicators. It is also possible
to force all future charts to use the same indicators by calling setTA
.
Additional motivation to add outlined candles to allow for scaling and advanced color coding is owed to Josh Ulrich, as are the base functions (from TTR) for the yet to be released technical analysis charting code.
Many improvements in the current version were the result of conversations with Gabor Grothendieck. Many thanks to him.
Jeffrey A. Ryan
Josh Ulrich - TTR package and multi.col coding
getSymbols
, addTA
, setTA
,
chartTheme
## Not run: getSymbols("YHOO") chartSeries(YHOO) chartSeries(YHOO, subset='last 4 months') chartSeries(YHOO, subset='2007::2008-01') chartSeries(YHOO,theme=chartTheme('white')) chartSeries(YHOO,TA=NULL) #no volume chartSeries(YHOO,TA=c(addVo(),addBBands())) #add volume and Bollinger Bands from TTR addMACD() # add MACD indicator to current chart setTA() chartSeries(YHOO) #draws chart again, this time will all indicators present ## End(Not run)


A set is an abstract data type that is similar to a bag. It is also unordered, but it does not allow duplicates. Examples of sets would be even integers or a collection of the movies you have previously seen. Which bag behavior would need to be modified for a set?
There are no hints for this question


Use your zipcode to search and register for local cleanup events.
See the positive impact you have on the environment by using a reusable water bottle
Using a simple zip code search, you can easily find your nearest recycling solution.
Get news and articles from The NY Times on environmental issues.
Get inspired by seeing other people making a diffeREnce in our world.


{# 500.html is used for 500 Internal Server Error #} {%- extends "base/base.html" %} {% from "base/macros.html" import flash_alert %} {% set active_page = '500'|default('index') -%} {% block title %}500 Internal Server Error{%- endblock title %} {% block content %}
Oops, something went seriously wrong!
Try reloading the page or come back later...


Graphic Devices Based on AGG
Documentation for package ‘ragg’ version 1.1.2
DESCRIPTION file
.
Help Pages
agg_capture
Draw to a buffer that can be accessed directly
agg_jpeg
Draw to a JPEG file
agg_png
Draw to a PNG file
agg_ppm
Draw to a PPM file
agg_tiff
Draw to a TIFF file


R/number-conditions.R
multiple_conditions_fun2.Rd
This function generates a derived variable (number_conditions) that counts the number of chronic conditions a respondent has. This function takes 6 CCHS-defined conditions (heart disease, cancer, stroke, bowel disorder, mood disorder and arthritis), and well one derived variable (respiratory condition) to count the number of conditions a respondent has.
multiple_conditions_fun2( CCC_121, CCC_131, CCC_151, CCC_171, CCC_280, resp_condition_der, CCC_051 )
| CCC_121 | variable indicating if respondent has heart disease (1 = respondent has heart disease, 2 = respondent does not have heart disease) |
|---|---|
| CCC_131 | variable indicating if respondent has active cancer (1 = respondent has active cancer, 2 = respondent does not have active cancer) |
| CCC_151 | variable indicating if respondent suffers from the effects of a stroke (1 = respondent suffers from stroke effects, 2 = respondent does not suffer from stroke effects) |
| CCC_171 | variable indicating if respondent has a bowel disorder (1 = respondent has bowel disorder, 2 = respondent does not have a bowel disorder) |
| CCC_280 | variable indicating if respondent has a mood disorder (1 = respondent has a mood disorder, 2 = respondent does not have a mood disorder. Note, variable was not asked to respondents in the 2001 CCHS survey cycle. |
| resp_condition_der | derived variable indicating if respondent has a
respiratory condition. (1 = respondent is over the age of 35 and has
a respiratory condition, 2 = respondent is under the age of 35 and has a
respiratory conditions, 3 = respondent does not have a respiratory
condition). See |
| CCC_051 | variable indicating if respondent has arthritis or rheumatism (1 = respondent has arthritis or rheumatism, 2 = respondent does not have arthritis or rheumatism) |
A categorical variable indicating the number of chronic conditions a respondent has. Respondents with 5 or more conditions are grouped in the "5+" category.
mood disorder (CCC_280) was not asked to respondents in the 2001
CCHS survey cycle. This mean respondents in this cycle will only be able to
have a maximum of 6 chronic conditions as opposed to 7 for respondents in
other cycles. multiple_conditions_fun1
is used for CCHS cycles
from 2003 to 2014.
# Using rec_with_table() to generate multiple_conditions in a CCHS # cycle. # multiple_conditions_fun2() is specified in variable_details.csv along with # the CCHS variables and cycles included. # To generate multiple_conditions, use rec_with_table() and specify the # multiple_conditions, along with the variables that are derived from it. # Since resp_condition_der is also a derived variable, you will have to # specify the variables that are derived from it. In this example, data # from the 2010 CCHS will be used, so DHHGAGE_cont, CCC_091, and CCC_031 # will be specified along with resp_condition_der. library(cchsflow) conditions_2009_2010 <- suppressWarnings(rec_with_table(cchs2009_2010_p, c("DHHGAGE_cont", "CCC_091", "CCC_031", "CCC_121","CCC_131","CCC_151", "CCC_171","CCC_280", "resp_condition_der","CCC_051", "number_conditions")))#>#>#>#> CCC_031 CCC_051 CCC_091 CCC_121 CCC_131 CCC_151 CCC_171 CCC_280 DHHGAGE_cont #> 1 2 NA(a) NA(a) 2 2 2 2 2 13 #> 2 2 2 NA(a) 2 2 2 2 2 27 #> 3 2 1 2 2 2 2 2 1 62 #> 4 2 2 2 2 2 2 2 2 52 #> 5 2 2 2 2 2 2 2 2 67 #> 6 2 1 2 2 2 2 2 2 62 #> resp_condition_der number_conditions #> 1 3 1 #> 2 3 1 #> 3 3 3 #> 4 3 1 #> 5 3 1 #> 6 3 2# Generating multiple_conditions with user inputted values # Let's say you are an individual that has heart disease, bowel disorder, # and arthritis. multiple_conditions_fun2() can be used to count the number # of chronic conditions you have library(cchsflow) num_conditions <- multiple_conditions_fun2(CCC_121 = 1, CCC_131 = 2, CCC_151 = 2, CCC_171 = 1, CCC_280 = 2, resp_condition_der = 3, CCC_051 = 1) print(num_conditions)#> [1] 3


Amber says Coraline eyed a jar of green olives at Costco today sign hungrily for "more." Any doubt she was our daughter is now obliterated.
7/8/2009, 4:09:43 PM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Amber says Coraline eyed a jar of green olives at Costco today sign hungrily for "more." Any doubt she was our daughter is now obliterated.
7/8/2009, 4:09:43 PM
Favs: 0
Retweets: 0
link


This MBA Student Dances Her Way to Manage Road Traffic in Indore | Watch
As part of her 15-day internship, Jain took the initiative after watching some students who were creating awareness on the same issue to make Indore roads safe and disciplined.
New Delhi: Adding a touch of drama to the streets, an MBA student in Indore, Madhya Pradesh on Monday volunteered to manage road traffic in her own unique way in order to spread awareness about traffic rules and regulations.
Shubi Jain, who is pursuing her MBA from Symbiosis Institute in Pune, emerged as an inspiration after a video with her interesting dance moves replicating efforts of Indore cop Ranjeet Singh surfaced on the internet.
In a video shared by news agency ANI, Jain can be seen dancing and instructing people of traffic norms. In the video, she tells people to wear a helmet, and put on the seat belts while driving.
As part of her 15-day internship, Jain took the initiative after watching some students who were creating awareness on the same issue to make Indore roads safe and disciplined and make the traffic manageable by 2022, aligned with the vision of Indore Additional Director General of Police (ADGP).
Two years ago, a similar awareness drive was taken up by traffic police Ranjeet Singh, whose Michael Jackson style ‘moonwalk’ traffic policing along with a Freddie Mercury moustache went viral and grabbed people’s attention across India’s chaotic streets.
“Many a time people ignore them which results in accidents. This is a creative method I have decided to apply so that the public abides by the rules,” Singh had said adding that his method simply adds an entertainment factor to his monotonous work.
For breaking news and live news updates, like us on Facebook or follow us on Twitter and Instagram. Read more on India Latest News on India.com.
Story Timeline
- 18 Nov 2019 This MBA Student Dances Her Way to Manage Road Traffic in Indore | Watch
- 28 Oct 2019 Madhya Pradesh: Huge Fire at Adjacent Godown Engulfs Apollo Hospital in Indore
- 21 Oct 2019 Indore: Massive Fire Breaks Out at a Four-storey Hotel, no Casualty so Far
- 30 Sep 2019 Madhya Pradesh Honey-trap Case: 3 Accused Women to be Produced Before Court in Indore Tomorrow
Comments - Join the Discussion


|
gtsam 4.1.1
gtsam
|
Sampling structure that keeps internal random number generators for diagonal distributions specified by NoiseModel.
Public Member Functions | |
constructors | |
| Sampler (const noiseModel::Diagonal::shared_ptr &model, uint_fast64_t seed=42u) | |
| Create a sampler for the distribution specified by a diagonal NoiseModel with a manually specified seed. More... | |
| Sampler (const Vector &sigmas, uint_fast64_t seed=42u) | |
| Create a sampler for a distribution specified by a vector of sigmas directly. More... | |
access functions | |
| size_t | dim () const |
| Vector | sigmas () const |
| const noiseModel::Diagonal::shared_ptr & | model () const |
basic functionality | |
| Vector | sample () const |
| sample from distribution | |
Public Types | |
| typedef boost::shared_ptr< Sampler > | shared_ptr |
Protected Member Functions | |
| Vector | sampleDiagonal (const Vector &sigmas) const |
| given sigmas for a diagonal model, returns a sample | |
Protected Attributes | |
| noiseModel::Diagonal::shared_ptr | model_ |
| noiseModel created at generation | |
| std::mt19937_64 | generator_ |
| generator | |
|
explicit |
Create a sampler for the distribution specified by a diagonal NoiseModel with a manually specified seed.
NOTE: do not use zero as a seed, it will break the generator
|
explicit |
Create a sampler for a distribution specified by a vector of sigmas directly.
NOTE: do not use zero as a seed, it will break the generator


Interface to the Dryad "Solr" API, their "OAI-PMH" service, and fetch datasets. Dryad (<http://datadryad.org/>) is a curated host of data underlying scientific publications.
| Version: | 0.4.0 |
| Imports: | crul (≥ 0.4.0), curl (≥ 3.0), xml2 (≥ 1.0.0), oai (≥ 0.2.2), solrium (≥ 1.0.0), data.table, tibble |
| Suggests: | testthat |
| Published: | 2018-06-18 |
| Author: | Scott Chamberlain [aut, cre], Carl Boettiger [aut], Karthik Ram [ctb] |
| Maintainer: | Scott Chamberlain <myrmecocystus at gmail.com> |
| BugReports: | https://github.com/ropensci/rdryad/issues |
| License: | MIT + file LICENSE |
| URL: | https://github.com/ropensci/rdryad |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| In views: | Phylogenetics |
| CRAN checks: | rdryad results |
| Reference manual: | rdryad.pdf |
| Package source: | rdryad_0.4.0.tar.gz |
| Windows binaries: | r-devel: rdryad_0.4.0.zip, r-release: rdryad_0.4.0.zip, r-oldrel: rdryad_0.4.0.zip |
| OS X binaries: | r-release: rdryad_0.4.0.tgz, r-oldrel: rdryad_0.4.0.tgz |
| Old sources: | rdryad archive |
Please use the canonical form https://CRAN.R-project.org/package=rdryad to link to this page.


Angular Material provides two sets of components designed to add collapsible side content (often navigation, though it can be any content) alongside some primary content. These are the sidenav and drawer components.
The sidenav components are designed to add side content to a fullscreen app. To set up a sidenav we use three components:
<mat-sidenav-container>
which acts as a structural container for our content and sidenav,
<mat-sidenav-content>
which represents the main content, and
<mat-sidenav>
which represents the added side content.
By default, Material will only measure and resize the drawer container in a few key moments (on open, on window resize, on mode change) in order to avoid layout thrashing, however there are cases where this can be problematic. If your app requires for a drawer to change its width while it is open, you can use the autosize option to tell Material to continue measuring it. Note that you should use this option at your own risk, because it could cause performance issues.
Auto-resizing sidenav
Lorem, ipsum dolor sit amet consectetur.
The drawer component is designed to add side content to a small section of your app. This is accomplished using the
<mat-drawer-container>
,
<mat-drawer-content>
, and
<mat-drawer>
components, which are analogous to their sidenav equivalents. Rather than adding side content to the app as a whole, these are designed to add side content to a small section of your app. They support almost all of the same features, but do not support fixed positioning.


Comprehensive list of options available in Assemble
Most options are defined in the assemble
task or target options in the Gruntfile, some options may only be defined inside the
YAML front matter of a file, and some may be defined in either location.
Additionally, options may be defined in "external" JSON or YAML configuration files.
For the purposes of clarity, we will refer to options that are defined in the Gruntfile as "configuration" options, and options that are defined in the YFM as "page" options.
These options are defined in the assemble
task in your project's Gruntfile. Any option may be defined at the
task or target level.
| Option | Description |
|---|---|
| assets | directory that contains commonly used "assets" for a project, such as images, fonts, javascripts and stylesheets. Assemble will generate a relative path from dest files to the given assets directory. |
| collections | Built-in collections for tags , categories and pages are available at the root of the context. |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
| helpers | path to custom helper(s) to be registered and used by the current template engine. Handlebars is the default. |
| layout * |
Layouts are optional and assemble will build
pages without one. However, when a layout is specified the file must contain a {{> body }} tag, since this tag indicates where the content from each file in a target should be inserted. |
| layoutdir * |
Layouts are optional and assemble will build
pages without one. However, when a layout is specified the file must contain a {{> body }} tag, since this tag indicates where the content from each file in a target should be inserted. |
| partials | the partials or "includes" to be used with pages. |
*Note that when a layout is used the {{> body }} tag must be included inside the layout in order for content from pages to be "pulled in".
These options are defined in the assemble
task in your Gruntfile.
Type: String|Array
(optional) Default: src/data
Retrieves data from any specified JSON
and/or YAML
files to populate the templates when rendered. Data gets passed through the data
object to the options on the assemble task, and then to the context in your
templates. Also useful for specifying [configuration][] data.
options: { data: 'src/data/**/*.{json,yml}' }
Note that assemble
merges the task and target-level data for options.data
.
Learn more about data →
Type: String
(optional) Default: undefined
Layouts are optional and may be defined at the task and/or target level. Unlike Jekyll, Assemble requires a file extension since you are not limited to using a single file type.
options: { layout: 'src/layouts/default.hbs' }
Learn more about layouts →
Type: String
|False
|None
(optional) Default: undefined
Path to the directory that is to be used as the "cwd" for layouts.
options: { layoutdir: 'src/layouts' }
When layoutdir
is defined, then a layout
may defined without the path:
options: { layout: 'default.hbs' }
or
---
layout: default.hbs
---
Type: String
(optional) Default: undefined
Path to the "assets" or "public" directory that will be used by dest files. Assemble uses path in the assets
option to generate a relative path from dest files to the given "assets" directory. The "assets"
folder commonly contains the CSS, JavaScripts, images and other similar files for a project. The assets
option may be defined at the task or target-level.
options: { assets: 'docs/assets' }
Type: String|Array
(optional) Default: undefined
Specifies the Handlebars partials files, or paths to the directories of files to be used.
options: { partials: 'src/partials/**/*.hbs' }
Note that assemble
merges the task and target-level data for options.partials
.
Learn more about partials →
Type: String
(optional) Default: .html
Specify the file extension to be used for destination files. For example:
assemble: {
// Build sitemap from JSON and templates
sitemap: {
options: { ext: '.xml' },
files: {
'.': ['path/to/sitemap.tmpl' ]
}
},
// Build README from YAML and templates
readme: {
options: { ext: '.md' },
files: {
'.': ['path/to/readme.tmpl' ]
}
}
}
Learn more about the ext option →
Type: String
(optional) Default: handlebars
The engine to use for processing client-side templates. Assemble ships Handlebars as the default template engine, to learn more about adding other template engines please read the documentation on assemble methods.
Also, we welcome pull requests for additional template engines. If you have questions please create an [Issue][assemble-issues].
Type: String|Array
(optional) Default: 100+ helpers from
handlebars-helpers
Assemble depends on handlebars-helpers, an external library which includes more than 100 Handlebars helpers. So any helpers from that project may be used in your templates.
If you wish for Assemble to use custom helpers with Handlebars or any specified template engine, just provide the path to the helper or helpers in options.helpers
:
options: { helpers: 'your/custom/helpers' }
Type: Boolean
Default: false
Remove extraneous whitespace added by Handlebars in rendered files. Use at your own risk, this is an experimental option and may be removed.
These options are defined in the YAML front matter of a page.
type: string
default: undefined
Specifies the layout file to be used. Layouts defined in YFM will override layouts defined in the Gruntfile.
type: boolean
default: true
Defining published: false
in the
YAML front matter of a page will:
pages
collection.Custom, user-defined variables may be specified in the [Options][options-overview] of the assemble task or target. Any variables defined in the options will be added to the root of the data context and thus they will also be available in any templates.
A common use case for defining custom variables in the options is for easily including or excluding content based on current "development status".
For example, assuming we have defined a custom option, production
:
assemble: {
options: {
production: false
},
files: {
'site/': ['src/pages/*.hbs' ]
}
}
And we add the production
variable to our templates:
{{#if production}}
<script src="dist/assets/script.min.js"></script>
{{else}}
<script src="dist/assets/script.js"></script>
{{/if}}
Since production: false
is defined in the Assemble
task options, the following HTML will be rendered with the non-minified version of the script:
<script src="dist/assets/script.js"></script>
The following is just a handful of options that can be used in your Gruntfile. Please visit the Grunt documentation to learn more.
expand
Set to true
to enable the following options:cwd
All src
matches are relative to (but don't include) this path.src
Pattern(s) to match, relative to the cwd
.dest
Destination path prefix.ext
Replace any existing extension with this value in generated dest
paths.flatten
Remove all path parts from generated dest
paths.rename
This function is called for each matched src
file, (after extension renaming and flattening). The dest
and matched src
path are passed in, and this function must return a new dest
value.
If the same dest
is returned more than once, each src
which used it will be added to an array of sources for it.See the template for this page →
Find an error? Let us know →


Paul Sinha's panel show appearances
Paul Sinha (born 1970-05-28[ref]) has appeared in 20 episodes between 2009-2016. Paul Sinha on IMDB. Paul Sinha on Wikipedia. Paul Sinha on Chortle.
- 2016-02-26 / Bad Language
- 2016-02-19 / Bad Language
- 2016-02-12 / Bad Language
- 2016-02-05 / Bad Language
- 2016-01-29 / Bad Language
- 2016-01-22 / Bad Language
- 2015-06-12 / Breaking The News
- 2014-06-16 / Just A Minute
- 2014-05-26 / Just A Minute
- 2014-02-28 / The News Quiz
- 2013-02-20 / Dilemma
- 2012-06-18 / Just A Minute
- 2012-06-04 / Just A Minute
- 2011-10-14 / The News Quiz
- 2011-06-03 / The News Quiz
- 2011-05-27 / The News Quiz
- 2011-02-18 / The News Quiz
- 2011-01-28 / The News Quiz
- 2009-10-30 / The News Quiz
- 2009-08-24 / Just A Minute


New Darksiders Genesis trailer showcases abilities and the Creature Core system
by John PapadopoulosAirship Syndicate and THQ Nordic have released a new gameplay trailer, presenting the game’s so-called “Creature Core”-system. This system will allow players to upgrade and customize their horseman’s battle skills.
As the press release reads, both fighters begin with a variety of different attacks but will gain access to more devastating and fascinating ways to smash demons on their journey through hell. “Creature Cores” can be picked up afters slaying enemies and bosses. They are also available for purchase at Vulgrim’s store in exchange for souls.
The “Creature Core”-system will allow players to shift the balance between the different playstyles of WAR and STRIFE.
Darksiders Genesis features the debut of the fourth and final horsemen , STRIFE. STRIFE will battle alongside his brother and fellow horsemen WAR in the first ever Darksiders two-player co-op mode. Solo players will be able to alternate between STRIFE and WAR on the fly. Thus, they’ll be able to take advantage of STRIFE’s ranged and WAR’s melee style attacks. Both characters can build up a special attack meter that, when activated, temporarily turns them into a colossal creature that leaves epic destruction in its wake.
The game currently targets a December 5th release.
Enjoy!


Major/New Features
3.4 is a smaller release to lay the groundwork for major new features described in Spree Development Roadmap. It also contains number of bug fixes and improvements besides described in this document.
Enhanced codebase quality
We’ve removed tons of unused & deprecated code and on top of that, we’ve updated RuboCop rules and tidied up the code quality of all Spree modules.
Contributed to Spark Solutions
Enhanced Segment.com integration
We’ve added Segment.com integration in Spree 3.3 but it was still limited. Since then we’ve put a lot of work to implement tracking of nearly all e-commerce events supported by Segment.com.
Contributed to Spark Solutions
Updated User Documentation
We’ve updated the entire User section of Spree Documentation also adding new content describing new features like Store Credits.
This is part of our Guides 2.0 project
Contributed by Spark Solutions
Searchable Documentation
Thanks to cooperation with Algolia DocSearch you can easily search the entire Spree Documentation.
This is part of our Guides 2.0 project
Contributed by Spark Solutions
Spree Demo
You can fire up the newest fully functional version of Spree on Heroku with a just one click :)
Contributed by Spark Solutions
Spree Frontend views exporter
You can easily copy all of the default spree views into your project with just one command line:
rails g spree:frontend:copy_views
We hope will make frontend customization easier.
Contributed by Spark Solutions
Upgrade
Update Gemfile
gem 'spree', '~> 3.4.0' gem 'spree_auth_devise', '~> 3.3' gem 'spree_gateway', '~> 3.3'
Update your extensions
We’re changing how extensions dependencies work. Previously you had to match
extension branch to Spree branch. Starting from Spree 3.2 release master
branch of all
spree-contrib
extensions should work with Spree >= 3.1
and < 4.0
. Please change
your extensions in Gemfile eg.:
from:
gem 'spree_braintree_vzero', github: 'spree-contrib/spree_braintree_vzero', branch: '3-1-stable'
to:
gem 'spree_braintree_vzero', github: 'spree-contrib/spree_braintree_vzero'
Run bundle update
Install missing migrations
rails spree:install:migrations rails spree_auth:install:migrations rails spree_gateway:install:migrations
Run migrations
rails db:migrate
Other Gotchas
Migrate Spree::Taxon icons to Spree Assets
We changed Spree::Taxon
icon to use Spree::Asset
to unify attachment usage
across all Spree models. If you were using icon images in Spree::Taxon
please run this to migrate your icons:
rails db:migrate_taxon_icons
Noteworthy Changes
Also please review each of the noteworthy changes, and ensure your customizations or extensions are not effected. If you are affected by a change, and have any of your own tips please submit a PR to help the next person!
Full Changelog
You can view the full changes using Github Compare.
Noteworthy Changes
-
Moved Admin Panel account menu into Spree core and redesigning it
-
Better multi store support for Spree frontend (use
current_store
withlast_incomplete_spree_order
) -
Added OptionTypes & OptionValues API V1 Documentation
-
Removed previously deprecated
Shipment#editable_by?
&Shipment#send_shipped_email
-
Removed previously deprecated
Variant#having_orders
&Variant#on_backorder
-
Removed previously deprecated
DelegateBelongsTo
-
Updated
Address#require_phone?
to useaddress_requires_phone
preference -
Performance optimization - replaced
pluck.sum
andmap.sum
withsum
-
Performance optimization - replaced
.count > 0
with.exists?
-
Removed previously deprecated
Calculator::PercentPerItem
-
Removed deprecated
StoreHelper
from frontend -
Removed deprecated
TestingSupport::MicroData
-
Deprecated
ContentController#show


Headline formatting. Put pre-text (comma) post-text
Section formatting. Put pre-text (comma) post-text
Subsection formatting. Put pre-text (comma) post-text
List formatting. Put pre-text (comma) post-text (comma) pre-item (comma) post-item
Formatting for categories Special fields are category name from label (%c). Also possible (%z) total estimates.
Formatting for issue. Special fields are issue nummer (%n), id (repo and number) (%d), title (%t) estimate (%e) and RN (%r). Use %x for RN under title in table, use %y to use RN if not empty, otherwise title
Show closed milestones
Milestones to show
Issue types (labels) to output to RN sections). Comma-separated list of Label|Header
Label to force skipping issue into RN
Label to indicate that a Meta issue
Label filter as comma separated list w/o spaces (AND)
Fallback category (comma) regular expression for splitting into categories
Label value causing issue to be listed into Known Issues RN (default "Q - Known Issue")
Issue types (labels) to output to Known RN sections). Comma-separated list of Label|Header


Problem Space
We interviewed around 12 individuals mostly, current students and recent Alumni from Stanford currently seeking housing or having done so in the past.
Key Insights
- Trust issues with sellers -Despite the proliferation of property listing websites, people feel compelled to tour in person to verify the validity of the property
- Users wanted to get a sense of the neighborhood that they would be living in.
- Disparate information sources and having to navigate several different platforms
- Need to move quickly- Rentals can close in under a week in NYC. This makes it critical to seize the opportunity immediately and tour the property. However, if you’re currently attending school, you can’t fly out to another coast to only tour one apartment.
“I could have saved money on Craigslist but i only looked on Airbnb because there are a lot of trust issues with the latter”
“I always have to see the apartment since there are a lot of scams. I came across 5 of them”
“I rejected an apartment because the streets were shady, there were no street lights and there were a lot of homeless people. The area isn’t shady generally but the street definitely was”
“If i Google best neighborhoods in New York, 50 articles with different neighborhoods show up and they all target different things. I can do 6 hours of research or just visit the place”
“I actually wrote a python script that calculates the commute distance from my workplace to each potential apartmen”
“I had to navigate between AirBnB and Google maps, to figure out distance to the office or the closest gym”
“The thing with New York and San Francisco and is that you have to make a decision on the spot. Like in a few hours or you'll lose it”
Among these different insights we found that several of them ended up having the same effect - the need to visit the apartment and neighborhood before leasing it.
This was alright for a student graduating from Stanford and moving to San Francisco but in some cases we had people fly across the country, crashing on friends couches or living in hotels. When they couldn’t afford to find the time and money to travel they tried to look for a friend in the area that could help them verify it.
This is something that is particularly cost ineffective right now and it would provide the biggest financial incentive for users to solve. This problem is also faced largely by fresh graduates who are tight on money and inexperienced with finding apartments
User Profile
We narrowed our user to be based not only the problem but the ones we had to access to interview and test prototypes with.
Recent college graduates from Stanford living in California, moving to the greater New York area for a full time job, who want an apartment to rent and are generally unfamiliar with the process or the city.- Inexperience with leasing apartments
- Know the city they'll be moving to but not the nieghborhood
- Know the city they'll be moving to but not the nieghborhood
- Unfamiliar with the city they are moving to
- Making atleast a year long commitement
- Have jobs starting but conscious of budgets
- Open to /prefer living with roommates
We can uniquely idenitfy these users by
Design
Constraints
- Since our users use desktop for their real estate searches, we are constraining ourselves to a desktop / web experience (as opposed to mobile first).
- 100% of the apartment rental search process needs to be completed online as the expectations from almost all other transactions (online services, marketplaces etc) in the users life are digital.
Prototypes
We were looking to develop a solution that would allow the user to lease an apartment without actually visiting it.
We tested out two prototypes each addressing a different problem
- The users want to have a sense of the neighborhood they will be living in Prototype
- A web application that takes input from the user on their routine and factors that they consider important in their apartment hunt (commute, public transport, groceries etc) and shows what their lives will look like
- This prototyped on the whole helped user to quickly decide between two potential apartments but wasn’t able to paint a sufficient picture that the users didn’t need to visit the apartment
- Lack of trust between the buyers and the sellers Prototype
- A web application that connects users who are looking for apartments to rent with locals who are willing to verify the apartment and answer any questions for the user.
- This seemed like a promising direction as we realized that most users already did some form of this interaction through friends, if they had any in the area they were moving
"The prototype tells me exactly how he different options fare against each other, making the trade off between houses easier"
"A real person can tell you what you wouldn't know to lookup : "there's construction going on all the time on the street""
"Users trusted individuals with similar demographics and long term residents of the the potential neighborhoods where they wished to move."
Final Prototype
We ended up with a platform that connects people looking for apartments (apartment-seekers) to finders (brokers). We plan to launch the product with a selected group of professional brokers but as we gather trust in our product we want to move on to signing up local residents as finders.


Before Change
logits_tp1[range(len(logits_tp1)), :, probs_ids_tp1_min].\
view(-1, self._num_heads, self.num_atoms).detach()
gammas = self._gammas**self._n_step
done_t = done_t[:, None, :] // B x 1 x 1
rewards_t = rewards_t[:, None, :] // B x 1 x 1
gammas = gammas[None, :, None] // 1 x num_heads x 1
atoms_target_t = rewards_t + (1 - done_t) * gammas * self.z
value_loss = [
After Change
return policy_loss, value_loss
def _categorical_loss(
self, states_t, actions_t, rewards_t, states_tp1, done_t
):
gammas, done_t, rewards_t = self._process_components(done_t, rewards_t)
// actor loss
actions_tp0 = self.actor(states_t)
// Again, we use the same actor for each critic


Reká Solymosi, Matt Ashby, Tom Cohen and Aiden Sidebottom
Office for National Statistics, 2011 Census: Aggregate data (England and Wales) [computer file]. UK Data Service Census Support. Downloaded from: http://infuse.mimas.ac.uk.
Ordnance Survey data are © Crown Copyright and/or database right 2015; all rights reserved.
Crime data contain public sector information licensed under the UK Open Government Licence v1.0.
Powered by TfL Open Data.
Craig Bush, Christopher Smith and Michael Caroe Andersen via Flickr.
<EMAIL_ADDRESS>| @wkndinthecity
<EMAIL_ADDRESS>| @lesscrime
These slides at:
http://lesscrime.info/presentations/stockholm2015/


{% extends "layout.html" %} {%block content%}
This tools has been developed as part of the OSR4Rights project.
This face recognition tool makes use of the Dlib library for face recognition via https://pypi.org/project/face-recognition/
Alpha version: July 2020
Released under MIT License
CNN Small Face Detection ON (slower):
CNN Small Face Detection OFF (faster):
Bulk Delete Search/Target Encodings function
Enter lowercase delete hog or delete cnn to remove the matching files from the search folder then push ok button
This tool is designed to assist in searching for a person's face in an image collection.
The software scans each image for faces then generates a corresponding face encoding file.
This can take a while - therefore there are 2 search facilities offered:
Option 1) HOG mode: +fast -accuracy
Option 2) CNN mode: +accuracy -slow
Once a face encoding has been computed it is saved to disk with the extension .fe_hog or .fe_cnn.
These encodings will be used in the future so that repeat searches of the same image collection will be much faster.
Put the files you wish to scan into a directory on your PC which is shared with the Docker container as 'data' Image files to be scanned must be placed in a folder structure as follows:
/osr4rights/search - files to be searched to find the target face(s)
/osr4rights/target - files which define the target face(s) to find
Image files must be of type .jpg or .png
Set the target face(s) to find. This can be several different pictures of the same person.
The software will then search for any matches.
The output report will rank from close matches to distant matches.
Please note this can take a long while depending on the speed of the PC and number of files to scan.
There is a toggle for scanning small faces. This enlarges the original image and divides into 4 sections before scanning for faces. This is done to keep the memory usage as low as possible, while giving better recognition for smaller faces in images. However the extra image processing will increase the processing time.
Use the image details page to check how many faces were found in each image, and check a sample to see if you need to enable the smallfaces option. It can over-report the number of faces found in the image details list if small faces scanning is included, due to the double processing of each image.
{%endblock content%}


| Package | Description |
|---|---|
| org.apache.log4j |
The main log4j package.
|
| org.apache.log4j.chainsaw |
Chainsaw is a GUI log viewer and filter for the log4j
package.
|
| org.apache.log4j.config |
Package used in getting/setting component properties.
|
| org.apache.log4j.helpers |
This package is used internally.
|
| org.apache.log4j.jdbc |
The JDBCAppender provides for sending log events to a database.
|
| org.apache.log4j.jmx |
This package lets you manage log4j settings using JMX.
|
| org.apache.log4j.lf5 | |
| org.apache.log4j.lf5.util | |
| org.apache.log4j.lf5.viewer | |
| org.apache.log4j.lf5.viewer.categoryexplorer | |
| org.apache.log4j.lf5.viewer.configure | |
| org.apache.log4j.net |
Package for remote logging.
|
| org.apache.log4j.nt |
Package for NT event logging.
|
| org.apache.log4j.or |
ObjectRenders are resposible for rendering messages depending on
their class type.
|
| org.apache.log4j.or.jms |
This package contains the MessageRenderer which renders objects of
type
javax.jms.Message . |
| org.apache.log4j.or.sax |
This package contains the AttributesRenderer which renders object of
class
org.xml.sax.Attributes . |
| org.apache.log4j.pattern |
Provides classes implementing format specifiers in conversion patterns.
|
| org.apache.log4j.rewrite | |
| org.apache.log4j.spi |
Contains part of the System Programming Interface (SPI) needed to
extend log4j.
|
| org.apache.log4j.varia |
Contains various appenders, filters and other odds and ends.
|
| org.apache.log4j.xml |
XML based components.
|
| org.apache.log4j.xml.examples |
Copyright © 1999-2016 Apache Software Foundation. All Rights Reserved.


Etiquette, or a series of social and cultural norms concerning behavior, is an important part of Japanese culture. Become familiar with proper Japanese etiquette in various circumstances, and try to observe it whenever possible.
Follow these basic guidelines when enjoying a kaiseki meal:
- Wait to be seated until you are invited to do so by the host.
- Prior to the meal, wash your hands with the wet towel provided to you. Men are permitted to wash their faces, as well.
- After eating, put each dish back in the position it was in when served. Never discard shells or tails on the table, but instead on the plates provided.


|
SAILAPIGuide
1_10_00_06
|
| bma2x2.c | |
| bma2x2.h | BMA2x2 Sensor Driver Support Header File |
| bme280.c | |
| bme280.h | BME280 Sensor Driver Support Header File |
| bmi160.c | |
| bmi160.h | BMI160 Sensor Driver Support Header File |
| button.c | |
| button.h | Button driver |
| led.c | |
| led.h | Led driver |
| opt3001.c | |
| opt3001.h | OPT3001 Ambient Light Sensor Driver |
| pga460.c | |
| pga460.h | PGA460-Q1 Automotive Ultrasonic Signal Processor and Transducer Driver |
| tmp006.c | |
| tmp006.h | TMP006 driver |
| tmp007.c | |
| tmp007.h | TMP007 driver |


Primary attainment and RAISE online statistics team
Email<EMAIL_ADDRESS>Telephone: Ayo Babatunde 020 7340 8473
National Statistics
Provisional information on the 2015 national curriculum assessments at key stage 2 in England.
PDF , 806KB , 14 pages
MS Excel Spreadsheet , 413KB
MS Excel Spreadsheet , 2.1MB
PDF , 843KB , 34 pages
ZIP , 57.2KB
Plain text , 2.37KB
This statistical first release ( SFR ) gives provisional assessment results for pupils in schools at:
It sets out provisional figures on expected progress between key stage 1 (typically age 7) and key stage 2 (typically age 11).
It includes results from the key stage 2 tests in:
Information on key stage 2 teacher assessments in the following subjects is also available:
Email<EMAIL_ADDRESS>Telephone: Ayo Babatunde 020 7340 8473
Published: 27 August 2015
Updated: 27 August 2015
From: Department for Education
Part of: Statistics: key stage 2


6.4. Information System Management¶
This chapter contains SIMP security concepts that are related to the management security controls in NIST 800-53.
6.4.1. Risk Assessment¶
This section describes the process of identifying risks within a system.
6.4.2. SIMP Self Risk Assessment¶
Risk can be found in any system. The SIMP team is constantly evaluating the system and the settings to minimize inherit risk. Most risks can be mitigated by processes and procedures at the implementation level. The following table describes the known areas in SIMP. [RA-1]
| Risk | Possible Mitigations |
|---|---|
| Disabling Puppet: This can cause the clients to be out of sync with the Puppet Master. | SIMP attempts to force a break on any locks and restart Puppet on all clients after a time of 4*runinterval (30 minutes by default). Implementations should ensure that further steps have not been taken to disable Puppet and should monitor their logs. Administrators can use the puppetlast command on the Puppet Master to detect servers that have not checked in within a reasonable time period. |
| Out of Date Patches: SIMP can be built with the RPMs from CentOS or Red Hat. Those RPMs should be assumed out of date at the time a system is initially installed (if using the SIMP DVD). | Implementations should obtain the latest RPMs and apply them in a reasonable manner. All SIMP systems will, by default, attempt to update all packages using YUM nightly. Therefore, having an updated repository will ensure that the systems are updated on a regular basis. |
| Poor Account Management: SIMP security access control is based on users being created and managed over time. Giving shell access to unnecessary users allows them the opportunity to escalate privileges. | Use the default LDIF files and local user modules to ensure that account settings remain restrictive. Ensure the system has policies and procedures in place to manage accounts. Finally, ensure that users are in appropriate groups with limited privileges. |
Table: SIMP Risk
6.4.3. Vulnerability Scanning¶
The SIMP development and security team performs regular vulnerability scanning of the product using commercial and open source tools. Results and mitigations for findings from those tools can be provided upon request. [CA-2, RA-5]
6.4.4. Security Assessment and Authorization¶
Assessment and authorization varies by implementation. Implementations are encouraged to use documentation artifacts provided by the SIMP team to assist with assessment and authorization. [CA-2]
Note
Should users find issues with internal assessments, the SIMP team highly encourages them to submit a bug report using our Bug Tracker


It is a genus of 70–75 species of flowering plants native to Asia and the Americas. By far the greatest species diversity is in eastern Asia, notably Korea, China, and Japan. Most are shrubs 1 to 3 meters tall, but some are small trees, and others lianas reaching up to 30m by climbing up trees. They can be either deciduous or evergreen, though the widely cultivated temperate species are all deciduous.
- Price: 5.99 GBP
You have already added this item.
The hydrangea has a wide range of meanings, from heartfelt emotion to gratitude to boastfulness. Each meaning stems from different cultural beliefs and stories.
Because of the Japanese legend above, hydrangeas are associated with apology.
Victorians considered hydrangeas a negative plant, and used it to represent boastfulness, bragging, or vanity.
Hydrangeas became associated with these boastfulness and vanity because they produce magnificent flowers, but very few seeds. They were also given to people who turned down love interests as signs that they were cold or frigid.
Most hydrangeas thrive in rich, porous, somewhat moist soils. Add compost to enrich poor soil.
They prefer full sun in the morning, with some afternoon shade; however, many will grow and bloom in partial shade. This is especially true for the Bigleaf hydrangeas.
Plant in spring or fall.
Dig a hole as deep as the root ball and 2 to 3 times as wide.
Set the plant in the hole and fill it half full with soil. Water. After water is drained, fill the rest of the hole with soil.
Water thoroughly.
18 - 28℃


Want a new pic? 💁♂
Hit refresh! 🦄
For a long time, I was struggling to style images quickly using CSS Filters and I had to spend a lot of time in dev tools to get the perfect styling to an image. So, I said why not build a tool for this?
You can toggle any filter and change the values with the
slider and import the code to your project.
Made by Tulsi Prasad. Deployed on
Vercel.


Dental Implants Online is an Internet resource to educate you about the placement of dental implants and to help you locate a dental implant practice in your area.
Incredible Dentistry
Top oral surgeons for patients who want to learn more about dental implants