Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This Working Draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for printing environments.
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/.
This document is a Last Call Working Draft. The W3C Membership and other interested parties are invited to review the document and send comments to to<EMAIL_ADDRESS>(archives) until 8 February 2008. There is an accompanying SVG Print 1.2, Part 1: Primer that lists the ways SVG Print, along with other SVG documents, may be used for SVG Printing.
This document has been produced by the W3C SVG Working Group as part of the W3C Graphics Activity within the Interaction Domain. The Working Group expects to advance this Working Draft to Recommendation Status.
Publication as a Working Draft 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 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 draft of SVG Print is a snapshot of a work-in-progress.
The main purpose of this document is to encourage public feedback. The best way to give feedback is by sending an email to<EMAIL_ADDRESS>Please identify in the subject line of your message the part of the specificationto which your comment refers (e.g "Print compositing" or "Print render formats"). If you have comments on multiple areas of this document, then it is preferable to send several separate comments.
The public are welcome to comment on any aspect in this document, but there are a few areas in which the SVG Working Group are explicitly requesting feedback. These areas are noted in place within this document. There is also a specific area related to the specification that is listed here:
Interaction with other print standards. The SVG Working Group believe that some design decisions would be best made in collaboration with other print standards bodies, and would welcome liaison statements in this area.
This document lists features that may be used in the context of printing. The various usage scenarios are listed in the SVG Print Requirements document.
This document is normative.
This document contains explicit conformance criteria that overlap with some RNG definitions in requirements. If there is any conflict between the two, the explicit conformance criteria are the definitive reference.
This document contains conformance criteria for a number of different entities:
Some conformance criteria allow or require the User Agent for Printing and the User Agent for Print Preview to communicate with each other.
The conformance criteria have awkward names - any suggestions for replacing "A User Agent for Printing", "A User Agent for Print Preview", and "A User Agent for Printing or Print Preview" would be welcome.
TODO: The above terms will probably be replaced as follows:
A User Agent for Print Preview SHOULD, when requested to print, provide a mechanism for passing details for that printing to a User Agent for Printing. The mechanisms for doing so are covered by other specifications and are outside the scope of the present one.
A User Agent for Printing SHOULD provide a mechanism for accepting details for that printing (from a User Agent for Print Preview, or other sources). The mechanisms for doing so are covered by other specifications and are outside the scope of the present one.
A User Agent for Printing MUST NOT print any content if there is no pageSet element and if there is no content that would otherwise mark the SVG canvas.
A User Agent for Printing MUST comply with the Static Profile of SVG Tiny 1.2.
A User Agent for Print Preview MUST comply with the Static Profile of SVG Tiny 1.2.
The pageSet element is the container for a set of page elements.
<define name='pageSet'> <element name='pageSet'> <ref name='pageSet.AT'/> <zeroOrMore><ref name='page'/></zeroOrMore> </element> </define> <define name='pageSet.AT' combine='interleave'> <ref name='svg.Core.attr'/> </define>
A User Agent for Printing or Print Preview MUST treat all pageSet elements beyond the first as unsupported elements.
A User Agent for Printing or Print Preview MUST treat all children of a pageSet element as unsupported elements except for page elements, masterPage elements and use elements.
A User Agent for Printing or Print Preview MUST treat all elements from the SVG namespace between the closing pageSet tag and the closing svg tag as unsupported elements.
The page element appears only as a child of a pageSet element.
<define name='page'> <element name='page'> <ref name='page.AT'/> <zeroOrMore><ref name='svg.G.group'/></zeroOrMore> </element> </define> <define name='page.AT' combine='interleave'> <ref name='svg.Core.attr'/> <ref name='svg.page-orientation.attr'/> </define>
Conceptually, the page element is similar to an svg element but without transformation and positioning. All pages are in the coordinate system of their pageSet, which is in the coordinate system of the root svg element.
A User Agent for Printing or Print Preview MUST, when rendering a page, render only the children of the page, and any relevant Master Pages.
A User Agent for Printing or Print Preview MUST treat page elements that are not inside the pageSet element as unsupported elements.
Content that has references inside a page element MUST refer only to elements within the same page or in the SVG document before the pageSet element.
A User Agent for Printing or Print Preview MUST treat any references in a page that refer to content in a different page in the same document as unsupported.
Content MAY have references inside a page element that refer to external documents, but authors SHOULD use the externalResourcesRequired feature in this case.
A User Agent for Printing MAY discard a page element and all its children after that page element has been dealt with.
The masterPage element appears only as a child of a pageSet element.
<define name='masterPage'> <element name='masterPage'> <ref name='masterPage.AT'/> <zeroOrMore><ref name='svg.G.group'/></zeroOrMore> </element> </define> <define name='masterPage.AT' combine='interleave'> <ref name='svg.Core.attr'/> <ref name='svg.rendering-order.attr'/> </define>
A User Agent for Printing or Print Preview MUST NOT directly render any masterPage element or any of its children.
The rendering-order attribute may appear only on the masterPage element.
Attribute definition:
A Foreground Master Page is a Master Page with rendering-order set to "over".
A Background Master Page is a Master Page with rendering-order set to "under".
It is possible to have multiple Background Master Pages and/or Foreground Master Pages in an SVG Print document, though only one of each can be active at any given time. Whenever the renderer encounters a Background or Foreground Master Page, it replaces the current Background or Foreground Master Page with the new one, and subsequent pages use the newer one.
A User Agent for Printing or Print Preview MUST apply one Background Master Page and one Foreground Master Page to a displayed page. The Background Master Page and Foreground Master Page MUST be the ones most closely preceding the page in document order.
A User Agent for Printing or Print Preview MUST render content that is part of the Background Master Page on each displayed page, before the page content.
A User Agent for Printing or Print Preview MUST render content that is part of the Foreground Master Page on each displayed page, after the page content.
A User Agent for Printing or Print Preview MUST discard the Foreground Master Page and all its children when the next Foreground Master Page is parsed.
A User Agent for Printing or Print Preview MUST discard the Background Master Page and all its children when the next Background Master Page is parsed.
The default master pages are made available as a simple default that gives sensible printing behaviour for documents that do not have pageSet elements.
A User Agent for Printing or Print Preview MUST use all elements in the SVG document after the opening svg tag and before the opening pageSet tag as the initial Background Master Page, applying to all page elements that appear before the next Background Master Page in document order.
A User Agent for Printing or Print Preview MUST set the initial Foreground Master Page to be empty.
Note that, as a consequence of the foregoing conformance statements, the default background master page (all the elements between the svg element and the pageSet element) is no longer used as a default master page when another background master page is set. Elements in the defs element of an svg document will be available to all pages in the pageSet element.
Content that has MasterPage elements SHOULD NOT make use of the default background master page (ie. should not have content between the svg element and the pageSet element).
A User Agent for Printing MAY allow control over the job information (e.g. JDF), by means of an encapsulation of an SVG file or document fragment.
A User Agent for Printing or Print Preview MAY, when requested to print an SVG document, and in the absence of conflicting Job Control information, provide a means for selecting which pages to print.
A User Agent for Printing SHOULD, when requested to print an SVG document, and in the absence of conflicting Job Control information, print all pages, in the order in which the pages appear in the SVG document.
If an SVG document fragment with multiple pages is embedded in, or referenced by, a document from another namespace, such as XHTML, then typically it is up to that namespace to define the processing of pages.
The orientation of each page element can be controlled by the page-orientation property. This enables the content to define whether a portrait or landscape mode is used for display and printing.
| Value: | -270 | -180 | -90 | 0 | 90 | 180 | 270 |
| Initial: | 0 |
| Applies to: | page elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual print |
| Animatable: | yes |
When displaying a page on a User Agent for Print Preview, the value of the page-orientation property introduces the following transform before the top-level viewport transformation:
The values for width and height are the dimensions of the top-level viewBox in the user coordinate system or the dimensions of the top-level viewport if there is no viewBox specified.
A User Agent for Printing or Print Preview MUST display each page with the orientation as specified by page-orientation.
The use-master-page attribute may appear only on a use element referencing an external page element.
Attribute definition:
Both the current Foreground Master Page and Background Master Page of the referencing document must be used when use-master-page is set to current.
Both the current Foreground Master Page and Background Master Page of the externally referenced document must be used when use-master-page is set to external.
By default, if the use-master-page attribute is not specified on the use element referencing an external page, then both the current Foreground Master Page and Background Master Page of the referencing document must be used.
A User Agent for Printing or Print Preview MUST use the current Foreground Master Page and Background Master Page of the referencing document when use-master-page is set to a value of current.
A User Agent for Printing or Print Preview MUST use the current Foreground Master Page and Background Master Page of the externally referenced document when use-master-page is set to a value of external.
A User Agent for Printing or Print Preview MUST use the current Foreground Master Page and Background Master Page of the referencing document if use-master-page is not set on the use element.
TODO: Need feedback on this feature. Are there compelling uses cases for having this extra complexity? What benefit does it provide?
Attribute definition:
A User Agent for Printing or Print Preview MUST, for the purposes of printing or print preview, treat a value of noPrint for the print-display attribute as though the element has display=none.
TODO: Need feedback on this feature. display-print is a replacement for noPrint. The attribute was originally a boolean. This changes is still under consideration. The following alternatives are available:
Content that uses CSS SHOULD define all styles for use in the entire document at the start of the SVG document, prior to any page elements.
Content intended for print applications SHOULD be authored using presentation attributes exclusively.
A User Agent for Printing MUST NOT run any script or start any animation in the SVG document.
A User Agent for Print Preview MUST NOT run any script or start any animation in any page being displayed.
SVG Print extends the control of color, relative to SVG Tiny 1.2, in two ways. Firstly by adding an additional color space for interpolation and compositing; this means that colors are no longer constrained to the sRGB gamut. Secondly by extending the syntax for Paint, thus allowing colors to be specified as calibrated (ICC and named) and uncalibrated ('device') color.
The color-interpolation property, not in SVG Tiny 1.2 but used in SVG 1.1 [SVG11], is extended by this specification to add new values using the CIE L*a*b* color space. Both the cartesian (CIE-Lab) and polar (CIE-LCHab) forms are supported.
A User Agent for Printing or Print Preview MUST use the color space defined by color-interpolation for calculations when interpolating between gradient stops and alpha compositing of graphics elements into the current background.
| Value: | auto | sRGB | linearRGB | CIE-Lab | CIE-LCHab | inherit |
| Initial: | sRGB |
| Applies to: | container elements, graphics elements and 'animateColor' |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual |
| Animatable: | yes |
The 'color-interpolation' property specifies the color space for gradient interpolations and alpha compositing.
When a child element is blended into a background, the value of the 'color-interpolation' property on the child determines the type of blending, not the value of the 'color-interpolation' on the parent.
The definition of paint in SVG Tiny 1.2 [SVGT12] is extended by this specification to add the icc-color values from paint in SVG Full 1.1 [SVG11] and also to add new values for named colors and uncalibrated (device) colors.
| <paint> : | none | currentColor | <color> | <color> icc-color(<name> [,<icccolorvalue>]*) | <color> icc-named-color(<name>, <namedColor>) | <color> device-color(<name> [,<devicecolorvalue>]*) | <FuncXMLRI> [ none | currentColor | <color>] | <system paint> | inherit |
TODO: Need feedback on this feature. Looking into the possibility of having ICC or Name ICC fallback for Device Color as well. ICC or Named ICC should have priority over an sRGB fallback if both types of fallback are specified.
Note that by default, color interpolation occurs in the sRGB color space, even if an ICC-based color specification is provided, unless the 'color-interpolation' property is set to one of the CIE Lab color spaces. If an sRGB color interpolation space is specified, all ICC-based colors used for the interpolation must be converted into the sRGB interpolation colorspace.
As with SVG Tiny 1.2, colors may be specified in the sRGB color space (see [sRGB]). Since all SVG Print and SVG Print Preview User Agents are color management capable, the rendering requirements are more strict than for SVG User Agents [SVG11] where color management is optional.
When an sRGB color is used - because it is the sole color specification, or in a permitted fallback situation - a conformant SVG Print or SVG Print Preview User Agent shall render it in conformance with the ICC profile for sRGB to obtain the desired color appearance.
As with SVG Full 1.1, SVG Print content may specify color using an ICC profile (see [ICC42]). For resiliency and for compatibility with SVG Tiny 1.2, an sRGB fallback must still be provided.
If ICC-based colors are provided, a conformant SVG Print or SVG Print Preview user agent MUST use the the ICC-based color in preference to the sRGB fallback color, unless the ICC color profile is unavailable, malformed, or uses a profile connection space other than CIE XYZ or CIE LAB.
When an ICC color is used, a conformant SVG Print or SVG Print Preview User Agent shall render it in conformance with the specified ICC profile to obtain the desired color appearance.
SVG Print introduces the ability to specify a color using a 'Named Color Profile'.
If ICC-based named colors are provided, a conformant SVG Print or SVG Print Preview user agent MUST use the the ICC-based named color in preference to the sRGB fallback color, unless the ICC named color profile is unavailable, malformed, or uses a profile connection space other than CIE XYZ or CIE LAB.
When an ICC named color is used, a conformant SVG Print or SVG Print Preview User Agent shall render it in conformance with the specified ICC profile to obtain the desired color appearance.
SVG Print also introduces a method of specifying uncallibrated device colors. This is sometimes useful in print workflows. This feature utilises the deviceColor element and the device-color keyword.
As these are uncalibrated, any interpolation or compositing occurs using the fallback sRGB color space
TODO: Need feedback on this feature. Looking into the possibility of having ICC or Name ICC fallback for Device Color as well. ICC or Named ICC should have priority over an sRGB fallback if both types of fallback are specified.
The International Color Consortium has established a standard, the ICC Profile [ICC32], for documenting the color characteristics of input and output devices. Using these profiles, it is possible to build a transform and correct visual data for viewing on different devices.
A color profile description provides the bridge between an ICC profile and references to that ICC profile within SVG content. The color profile description is added to the user agent's list of known color profiles and then used to select the relevant profile. The color profile description contains descriptors for the location of the color profile on the Web, a name to reference the profile and information about rendering intent.
Color profile descriptions can be specified in either of the following ways:
If a color profile with the same name value has been identified by both a 'color-profile' element and @color-profile rules within a CSS style sheet, then the user agent MUST first attempt to locate the profile by using the specifications in the @color-profile rules first.
<define name='color-profile'> <element name='color-profile'> <ref name='color-profile.AT'/> <empty/> </element> </define> <define name='color-profile.AT' combine='interleave'> <ref name='svg.Core.attr'/> <ref name='svg.local.attr'/> <ref name='svg.name.attr'/> <ref name='svg.rendering-intent.attr'/> </define>
Attribute definitions:
'rendering-intent' permits the specification of a color profile rendering intent other than the default. 'rendering-intent' is applicable primarily to color profiles corresponding to CMYK color spaces. The different options cause different methods to be used for translating colors to the color gamut of the target rendering device:
When the document is styled using CSS, the @color-profile rule can be used to specify a color profile description. The general form is:
@color-profile { <color-profile-description> }
where the <color-profile-description> has the form:
descriptor: value; [...] descriptor: value;
Each @color-profile rule specifies a value for every color profile descriptor, either implicitly or explicitly. Those not given explicit values in the rule take the initial value listed with each descriptor in this specification. These descriptors apply solely within the context of the @color-profile rule in which they are defined, and do not apply to document language elements. Thus, there is no notion of which elements the descriptors apply to, or whether the values are inherited by child elements.
The following are the descriptors for a <color-profile-description>:
"local(" + <string> + ")"where <string> is the profile's unique ID as specified by International Color Consortium. (Note: Profile description fields do not represent a profile's unique ID. With current ICC proposals, the profile's unique ID is an MD5-encoded value within the profile header.)
| Values: | <name> |
| Initial: | undefined |
| Media: | visual |
| Values: | auto | perceptual | relative-colorimetric | saturation | absolute-colorimetric |
| Initial: | auto |
| Media: | visual |
| Animatable: | no |
See the description for the rendering-intent attribute on the 'color-profile' element.
TODO: Need some conformance criteria. Also, this reiterates some of the color-profile element stuff, so we should reference that more here.
| Value: | auto | sRGB | <name> | <iri> | inherit |
| Initial: | auto |
| Applies to: | 'image' elements that refer to raster images |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual |
| Animatable: | yes |
TODO: Need some conformance criteria. Also, need to reference color-profile element.
Certain print applications can improve printing quality by specifying colors by name or in an alternative color format. This is commonly referred to as using 'spot' colors, device colors or inks, and usually means that a particular ink will be used for the color when it is printed. Furthermore, there are applications in the printing press industry where presses can be set up with different inks for different jobs. This means that the content creator will need to create content tailored to the particular press setup in order to obtain the best results.
The deviceColor element can be used to indicate an alternative color for a particular paint. This element will be mostly used in closed workflows, since the names of the inks and the parameters (percentages of each ink's color components) rarely have meaning outside the domain of the target device.
<xs:element name="deviceColor"> <xs:complexType> <xs:attribute ref="href" use="required" namespace="http://www.w3.org/1999/xlink"/> <xs:attribute ref="name" use="required" type="string"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element>
TODO: This needs to be converted to RNG
A URI used to identify the device-specific information included in this element. If the User Agent does not recognize the URI (ie. is not able to recognize the particular device parameters) then the element should be ignored and should not be part of the rendering process.
| Animatable: | no |
The name of this device-specific color information. The name attribute is used within the device-color specification within <paint> to reference this deviceColor element.
| Animatable: | no |
The deviceColor element uses attributes from external namespaces to define the device specific properties that are to be used when the deviceColor is referenced from a <paint>.
The following example illustrates the use of deviceColor. There are two things to note:
<svg xmlns="http://www.w3.org/2000/svg" version="1.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ecpi="http://www.example.com/press/inks"> <defs> <!-- describe a particular output device --> <deviceColor name="device-inks" xlink:href="http://www.example.com/pressInks" ecpi:value="Cyan, Magenta, Yellow, Black, Silver, Gray, Green"/> </defs> <text x="100" y="150" font-family="Verdana" font-size="35" fill="rgb(22,33,44) device-color(device-inks, 11,55,66,77,0,0,88)" > Hello, out there </text> </svg>
In the example above, a supplemental attribute, value, from a private namespace has been added. This example value attribute provides the definitions of colors or inks to be interpreted in the context of the URI specified. It is in a private namespace so that content and context authors can use any understood format to convey the necessary information. When the particular deviceColor element is referenced later by a device-color keyword specification, it is generally expected that the number of parameters following the name reference (1st parameter) in the function-like representation for the value of device-color alternate in a fill or stroke attribute (for example) will have an understood one-to-one correspondence with the information specified for the value attribute in the the deviceColor element. The interpretation of the parameters is implied specifically by the context set by the URI.
TODO: Need some conformance criteria.


Collective communication is defined as communication that involves a group or groups of processes. The functions of this type provided by MPI are the following:
One of the key arguments in a call to a collective routine is a communicator that defines the group or groups of participating processes and provides a context for the operation. This is discussed further in Section Communicator Argument . The syntax and semantics of the collective operations are defined to be consistent with the syntax and semantics of the point-to-point operations. Thus, general datatypes are allowed and must match between sending and receiving processes as specified in Chapter Datatypes . Several collective routines such as broadcast and gather have a single originating or receiving process. Such a process is called the root. Some arguments in the collective functions are specified as ``significant only at root,'' and are ignored for all participants except the root. The reader is referred to Chapter Datatypes for information concerning communication buffers, general datatypes and type matching rules, and to Chapter Groups, Contexts, Communicators, and Caching for information on how to define groups and create communicators.
The type-matching conditions for the collective operations are more strict than the corresponding conditions between sender and receiver in point-to-point. Namely, for collective operations, the amount of data sent must exactly match the amount of data specified by the receiver. Different type maps (the layout in memory, see Section Derived Datatypes ) between sender and receiver are still allowed.
Collective operations can (but are not required to) complete as soon as the caller's participation in the collective communication is finished.  A nonblocking (immediate) call requires a separate completion call (cf. Section Nonblocking Communication ). The completion of a collective operation indicates that the caller is free to modify locations in the communication buffer. It does not indicate that other processes in the group have completed or even started the operation (unless otherwise implied by the description of the operation). Thus, a collective communication operation may, or may not, have the effect of synchronizing all calling processes. This statement excludes, of course, the barrier operation.
Collective communication calls may use the same communicators as point-to-point communication; MPI guarantees that messages generated on behalf of collective communication calls will not be confused with messages generated by point-to-point communication. The collective operations do not have a message tag argument. A more detailed discussion of correct use of collective routines is found in Section Correctness .
Rationale.
The equal-data restriction (on type matching) was made so as to avoid the complexity of providing a facility analogous to the status argument of MPI_RECV for discovering the amount of data sent. Some of the collective routines would require an array of status values.
The statements about synchronization are made so as to allow a variety of implementations of the collective functions.
( End of rationale.)
Advice to users.
It is dangerous to rely on synchronization side-effects of the collective operations for program correctness. For example, even though a particular implementation may provide a broadcast routine with a side-effect of synchronization, the standard does not require this, and a program that relies on this will not be portable.
On the other hand, a correct, portable program must allow for the fact
that a collective call may be synchronizing. Though one cannot
rely on any synchronization side-effect, one must program so as to allow
it. These issues are discussed further in Section Correctness
.
( End of advice to users.)
Advice
to implementors.
While vendors may write optimized collective routines matched to
their architectures, a complete library of the collective communication
routines can be written entirely using the MPI point-to-point communication
functions and a few auxiliary functions. If implementing on top of
point-to-point, a hidden, special communicator
might
be created for the
collective operation so as to avoid interference with any on-going
point-to-point communication at the time of the collective call. This
is discussed further in Section Correctness
.
( End of advice to implementors.)
Many of the descriptions of the collective routines provide illustrations in
terms of blocking MPI point-to-point routines. These are intended solely to
indicate what data is sent or received by what process. Many of these
examples
are not correct MPI programs; for purposes of simplicity, they often
assume infinite buffering.


{% extends "sentry_hipchat_ac/layout.html" %} {% load sentry_helpers %} {% block body %}
{{ me.event.culprit }}
Project: {{ me.event.project.name }} {{ me.last_mentioned|date:"M d, Y" }} {{ me.last_mentioned|time:"H:i" }}


You've just completed a tutorial ! Will any member of {{ learnerdetails.squadname }} get a skill boost from this ?
Select a squad member who hasn't completed this tutorial before, and they will get a {{ details.skillincrease }} boost in their {{ details.category }} skill level.


Gecode::Search::Meta::Sequential::Slave Class Reference
Runnable slave of a portfolio master.
More...
#include <pbs.hh>
List of all members.
Detailed Description
Runnable slave of a portfolio master.
Definition at line 71 of file pbs.hh.
Constructor & Destructor Documentation
| Gecode::Search::Meta::Sequential::Slave::~Slave |
( |
void |
|
) |
[inline] |
Delete slave.
Definition at line 73 of file pbs.hpp.
Member Function Documentation
| void Gecode::Search::Meta::Sequential::Slave::init |
( |
Engine * |
s, |
|
|
Stop * |
so | |
|
) |
| | [inline] |
Initialize with slave s and its stop object so.
Definition at line 53 of file pbs.hpp.
| Space * Gecode::Search::Meta::Sequential::Slave::next |
( |
void |
|
) |
[inline] |
Return next solution.
Definition at line 57 of file pbs.hpp.
| Statistics Gecode::Search::Meta::Sequential::Slave::statistics |
( |
void |
|
) |
const [inline] |
Return statistics of slave.
Definition at line 61 of file pbs.hpp.
| bool Gecode::Search::Meta::Sequential::Slave::stopped |
( |
void |
|
) |
const [inline] |
Check whether slave has been stopped.
Definition at line 65 of file pbs.hpp.
| void Gecode::Search::Meta::Sequential::Slave::constrain |
( |
const Space & |
b |
) |
[inline] |
Constrain with better solution b.
Definition at line 69 of file pbs.hpp.
| void Gecode::Search::Meta::Sequential::Slave::run |
( |
void |
|
) |
|
Member Data Documentation
The slave engine.
Definition at line 74 of file pbs.hh.
The documentation for this class was generated from the following files:


Rugby World Cup final: England failed to meet goal after defeat, says Eddie Jones
Eddie Jones says he cannot explain why England came up short after his side failed to achieve their goal of winning the World Cup in Japan.
England were beaten 32-12 by South Africa in the final in Yokohama.
It came a week after England knocked out three-time champions New Zealand in the semi-final in one of the best performances in Jones' tenure as coach.
"I'm not sure why we came up short today, sometimes you never know," said the England head coach.
"Sometimes you can investigate but you'll never know why it happened. We're going to be kicking stones now for four years, we're massively disappointed."
Captain Owen Farrell kicked four penalties for England, but Handre Pollard replied with six for South Africa before tries from Makazole Mapimpi and Cheslin Kolbe put the game beyond Jones' side.
The Australian has a contract with England until 2021 but said it was "not the time to discuss" his future after the defeat.
"We are the second best team in the world," added Jones, who lost the 2003 final to England while coaching the Wallabies but was a consultant to South Africa the last time the Springboks won the trophy in 2007.
"We didn't meet our goal to be the best team in the world, but we are the second best team in the world, so I think that's how we should be remembered.
"The players prepared tremendously well for this World Cup. I thought they played with a lot of pride and passion, and we got caught short today.
"These things happen, but we can't doubt the effort of the players. I thought they were extraordinary.
"The only thing I am worried about now is having a few beers, and that's the only thing we will worry about.
"And then after we have a few beers today, we will probably have a few more beers tomorrow and maybe Monday, and then maybe we will have to pull up stumps."
Defeat 'heartbreaking' for England
England scrum-half Ben Youngs says it will take a long time to get over the defeat.
"We're devastated," he said. "It's been an unbelievable effort, it hasn't just been this tournament, it's been a huge lead-up to this and it's heartbreaking.
"It will take a while to get over this."
Captain Farrell added: "[We're] proud to be a part of it, proud to have come as far as we've come.
"Today didn't go our way but we've enjoyed this tournament and a lot of people have put a lot of work into us.
"The squad has enjoyed its time here in Japan, the competition as a whole. It's been fantastically run and we've loved our time here."
Matt Dawson, World Cup-winning scrum-half in 2003, says it is important to "look after" England's players after the loss.
"The England players will have to be looked after here," he told BBC Radio 5 Live.
"It's a while before they play again in an England jersey. Some will think about whether they'll take it on and go through that again."
'One of the most painful experiences'
Fly-half George Ford says England were "nowhere near good enough" to win Saturday's final, but insists Jones' side "will come back".
"Congratulations to South Africa, I thought they executed their plan brilliantly," Ford told BBC Radio 5 Live.
"I couldn't be prouder of the lads, they've been brilliant all tournament up front, they just did a job on us today.
"It's obviously a huge disappointment for our side. We wanted to finish it off today but we were nowhere near good enough to do that.
"We've come a long way and it's probably the most together squad I've ever been a part of."
| England's World Cup |
|---|
| Top points scorer: Owen Farrell (58) |
| Most tries scored: Jonny May, Manu Tuilagi, Luke Cowan-Dickie (3) |
| Most clean breaks made: Anthony Watson (10) |
| Most tackles: Maro Itoje (71) |
Lock Maro Itoje says his England team-mates "are trying to draw positives out of the journey" and is already looking towards the 2023 tournament in France.
"It is not exactly a disco in there," the 25-year-old said about the England dressing room. "But we are united, we are sticking together, we are talking to each other and consoling each other.
"We want to get better and most of this squad will be at the next one. It is a long way away to think about now but our goal is to do better next time around.
"Losing this game was one of the most painful experiences that I have had in life, not just my rugby career. It is not easy.
"It is a tough time and tough period to go through but if we stay together then I am sure all will be well in the long run.
"We are disappointed to lose. Our goal was to win the World Cup and we have fallen short."
'It is special to be a part of this'
Wing Jonny May says it will be "special" to reflect on England's tournament once the dust settles on their final defeat.
"I will keep that [silver] medal and I am sure that once everything calms down and you come back into your own body - it is special to be a part of this - an England player in a World Cup in Japan," he said.
"There have been some great moments. I couldn't have done any more and the team couldn't have done any more. It's just what happened. It has been special to represent our country."
Joe Marler says he was "really gutted" to see fellow prop Kyle Sinckler taken off with concussion in the third minute but believes he will continue to improve along with the rest of the England squad.
"This team, if they keep developing as they have, they will dominate for a long period and that is a joy to see," said Marler.
"I have thoroughly enjoyed my time over the last 10 weeks and seeing the growth of the youngsters. They have got a bright future."


A Passion in the Desert A film review by Marty Mapes Copyright 1998 Marty Mapes
*** (out of 4) A PASSION IN THE DESERT has good cinematography and an inventive story. A slowly paced midsection and an off-putting subject matter keep it from being great (or widely distributed), but for the adventurous moviegoer, it's worth a look.
Augustin (played very well by Ben Daniels, in a role with little dialogue) is a soldier in Napoleon's army. Augustin's unit is transporting Venture (Michel Piccoli), one of Napoleon's artists, to some of the sights in the Egyptian Desert. After a martial skirmish, Augustin and Venture find themselves alone and lost in the desert.
Augustin leaves Venture in search of water (both men knowing that he's leaving Venture to die). Time passes, Augustin walks, and eventually, his horse dies. He keeps plodding on foot and finally comes to a tent, where he steals some water. He is chased from the tent and flees into a desert canyon, where he hides in a cave. As his pursuers approach, he discovers that he is sharing his cave with a leopard. The cat leaps out of the cave and kills one of the men, giving Augustin the opportunity to find a new hiding place.
The surrounding desert condemns Augustin and the leopard to share the same canyon. The leopard has spared Augustin's life once, but the two still don't trust each other. They come to terms with each other around the watering hole, learning to share the water without hostility. Eventually, they learn to share food, and finally, affection.
Augustin's affection for the leopard takes an unnatural turn after several nights spent sleeping near each other. A passionate lick is all we see (or all that transpires, for all we know), but it changes an interesting hypothetical situation into something more fantastic. It severs some of the the audience's empathy by being more than most of us would be willing to share.
At this point, it seems that Augustin has given up on being human. After desperate days wandering through the desert and facing his own death, he adapts to life with the leopard (whom he names Simoom). He has given up on finding a way out of the desert and has instead chosen to fulfill his needs in Simoom's canyon. Being a French soldier has not allowed him to survive; being this leopard's partner has. When a troop of French soldiers comes within earshot, he hides himself from them. He truly has shunned humanity.
Augustin's passion turns into jealousy when a male leopard shows up and mates with his newfound love. He takes this insult badly. The problem, as he sees it, is not his unnatural passion and jealousy, but his species. In another of the film's awkward moments, Augustin strips naked, makes paint from different-colored rocks, and cakes himself with orange and black mud.
Simoom seems to understand the limits of their relationship much better than Augustin, and eventually she convinces him to rejoin his own species.
Daniels had a tough job in this role, and he pulled it off very well. The range required for the part is expansive, and Daniels was convincing at each level, from competent soldier to near-dead mummy to leopard-man. The "acting" on the part of Simoom was also incredible (though some credit for the "performance" should surely go to the director and editor for filling in the gaps). The leopard had to, and did, communicate distrust, trust, and affection.
The cinematography (by Alexei Rodionov) was also very good, although it's hard to go wrong when you are filming in a desert. The film was shot in Jordan and in Moab, Utah, both of which seem naturally photogenic. The same could be said for Daniels' piercing blue eyes and the leopard's sleek form. Not to detract from Rodionov's accomplishment, but it would have been hard to shoot this film badly.
With all this going for it, A PASSION IN THE DESERT should be an outstanding film. But Augustin's unnatural passion keeps us from really empathizing with him, and thus from getting caught up in the film. His behavior is explainable, but it is not fathomable. And because this was so integral to the movie, its length could not have been easily cut. Perhaps the setup could have been shortened, but then we would not be able to see the change in the man so drastically. The movie, too long by a couple of minutes, had nothing left to trim.
Still, the movie is quite original, so if you're feeling daring, go and see it.
Check out more current movie reviews at http://www.indra.com/~mmapes/
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


@OneToMany
Edit a JPA @Entity adding Phone numbers as a @OneToMany relationship
Name
Email address
Phone Numbers
Id
Number
Action
New
1
555-5555


Password Generator
Please choose from the following criteria for your password (must choose at least one type of character):
×
Length of password (between 8 and 128 characters)
Special characters
Numeric characters
Lowercase characters
Uppercase characters
Generate a Password
Generate Password
Copy to Clipboard


A linear equation is any equation that can be written in the form
ax + b = 0
where a and b are real numbers and x is a variable. This form is sometimes called the standard form of a linear equation. Note that most linearax2 + bx + c = 0
where a, b, c are known values and x is the variable or unknown (we don't know it yet). Also, a can't be 0.A = π × r2
or, when you know the diameter (D):A = (π / 4) × D2
or, when you know the circumference (C):A = C2 / 4 × π
A ∩ B = { x : x ∈ A and x ∈ B }
That is, x is an element of the intersection A ∩ B if and only if x is both an element of A and an element of B.


A tourtip points out a new feature or section of the page. A tourtip is open by default and must be explcitly closed using its close button. Once closed, it cannot be reopened.
Toggle the tourtip--expanded modifier to expand or collapse the tourtip.
Tourtip also supports having a footer as well as an index in the case there are multiple tourtips on the page


Id: 37
Name: Beth Sanchez
Status: Alive
Species: Human
Type:
Gender: Female
OriginName: Earth (C-500A)
OriginUrl: https://rickandmortyapi.com/api/location/23
LocationName: Earth (C-500A)
LocationUrl: https://rickandmortyapi.com/api/location/23
Image: https://rickandmortyapi.com/api/character/avatar/37.jpeg
Episode: ['https://rickandmortyapi.com/api/episode/8']
Url: https://rickandmortyapi.com/api/character/37
Created: 2017-11-05T09:38:22.960Z


My main interest honestly... is video games. I'm ashamed to say it but I get a lot of enjoyment out of them and I'm a bit of an achievement hunter. Getting that 100%+ completion percentage is my way of life.
Another interest I have is music. Not so much production even though that does sound interesting but listening to music. I have found that my music taste has gotten a lot better over the years with my middle school tastes involving minecraft parodies and now I am more interested in rap and hiphop with some of my favorites being Tyler, the Creator and Kendrick.
Lastly, I got to throw something that makes it look like I have been outside. So one of my interests is mountain biking. Living in Utah there are no shortage of mountains and mountain biking is tons of fun. I think the best way to describe it to the uninitaited is that it is like riding a roller coaster without restraints.
| Monday | Tuesday | Wednesday | Thursday | Friday | |
| 1:00 | CS 305G | CS 305G | |||
| 1:30 | |||||
| 2:00 | |||||
| 2:30 | Discrete Math | Discrete Math | |||
| 3:00 | Fit for Life | ||||
| 3:30 | ART 1400 | ART 1400 | |||
| 4:00 | |||||
| 4:30 | |||||
| 5:00 | |||||
| 5:30 | Networks | Networks | |||
| 6:00 | |||||
| 6:30 | |||||
| 7:00 |


Biryani is a mixed rice dish with its origins among the Muslims of Indian subcontinent. It can be compared to mixing a curry, later combining it with semi-cooked rice separately. This dish is especially popular throughout the Indian subcontinent, as well as among its diaspora.
Noodles are a type of food made from unleavened dough which is rolled flat and cut, stretched or extruded, into long strips or strings. Noodles can be refrigerated for short-term storage or dried and stored for future use. Noodles are usually cooked in boiling water, sometimes with cooking oil or salt added.
Sambar is a lentil-based vegetable stew, cooked with pigeon pea and tamarind broth. It is popular in South Indian and Sri Lankan cuisines.


"GaussianHMM",
"MultinomialHMM"]
COVARIANCE_TYPES = ["spherical", "tied", "diag", "full"]
class GaussianHMM(_BaseHMM):
Hidden Markov Model with Gaussian emissions.
__all__ = ["GMMHMM", "GaussianHMM", "MultinomialHMM"]
COVARIANCE_TYPES = frozenset(("spherical", "diag", "full", "tied"))
class GaussianHMM(_BaseHMM):
Hidden Markov Model with Gaussian emissions.


beefy.finance
Join the cowmunity!
BSC Allowance
Find & revoke all the addresses that can spend your tokens
Revoke 10
Revoke all
Token
Authorised Spender
Allowance


Welcome To The Quiz
Test Your Knowledge
Through our exceptionally curated occasion bundles, we need to take you on an adventure where you personally enjoy with the stunning magnificence of Sri Lanka.
Address
Telephone
Copyright © Wanderlust All Rights Reserved


|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use KeyStroke | |
|---|---|
| javax.swing | Provides a set of "lightweight" (all-Java language) components that, to the maximum degree possible, work the same on all platforms. |
| javax.swing.plaf.basic | Provides user interface objects built according to the Basic look and feel. |
| javax.swing.text | Provides classes and interfaces that deal with editable and noneditable text components. |
| Uses of KeyStroke in javax.swing |
|---|
| Methods in javax.swing that return KeyStroke | |
|---|---|
KeyStroke[] |
InputMap.allKeys()
Returns an array of the KeyStroke s defined in this
InputMap and its parent. |
KeyStroke |
JMenuItem.getAccelerator()
Returns the KeyStroke which serves as an accelerator
for the menu item. |
static KeyStroke |
KeyStroke.getKeyStroke(char keyChar)
Returns a shared instance of a KeyStroke
that represents a KEY_TYPED event for the
specified character. |
static KeyStroke |
KeyStroke.getKeyStroke(Character keyChar,
int modifiers)
Returns a shared instance of a KeyStroke, given a Character object and a set of modifiers. |
static KeyStroke |
KeyStroke.getKeyStroke(char keyChar,
boolean onKeyRelease)
Deprecated. use getKeyStroke(char) |
static KeyStroke |
KeyStroke.getKeyStroke(int keyCode,
int modifiers)
Returns a shared instance of a KeyStroke, given a numeric key code and a set of modifiers. |
static KeyStroke |
KeyStroke.getKeyStroke(int keyCode,
int modifiers,
boolean onKeyRelease)
Returns a shared instance of a KeyStroke, given a numeric key code and a set of modifiers, specifying whether the key is activated when it is pressed or released. |
static KeyStroke |
KeyStroke.getKeyStroke(String s)
Parses a string and returns a KeyStroke . |
static KeyStroke |
KeyStroke.getKeyStrokeForEvent(KeyEvent anEvent)
Returns a KeyStroke which represents the stroke which generated a given KeyEvent. |
KeyStroke[] |
JComponent.getRegisteredKeyStrokes()
Returns the KeyStrokes that will initiate
registered actions. |
KeyStroke[] |
InputMap.keys()
Returns the KeyStroke s that are bound in this InputMap . |
| Methods in javax.swing with parameters of type KeyStroke | |
|---|---|
Object |
InputMap.get(KeyStroke keyStroke)
Returns the binding for keyStroke , messaging the
parent InputMap if the binding is not locally defined. |
ActionListener |
JComponent.getActionForKeyStroke(KeyStroke aKeyStroke)
Returns the object that will perform the action registered for a given keystroke. |
int |
JComponent.getConditionForKeyStroke(KeyStroke aKeyStroke)
Returns the condition that determines whether a registered action occurs in response to the specified keystroke. |
static boolean |
SwingUtilities.notifyAction(Action action,
KeyStroke ks,
KeyEvent event,
Object sender,
int modifiers)
Invokes actionPerformed on action if
action is enabled (and non null). |
protected boolean |
JTable.processKeyBinding(KeyStroke ks,
KeyEvent e,
int condition,
boolean pressed)
|
protected boolean |
JMenuBar.processKeyBinding(KeyStroke ks,
KeyEvent e,
int condition,
boolean pressed)
Subclassed to check all the child menus. |
protected boolean |
JComponent.processKeyBinding(KeyStroke ks,
KeyEvent e,
int condition,
boolean pressed)
Invoked to process the key bindings for ks as the result
of the KeyEvent e . |
void |
ComponentInputMap.put(KeyStroke keyStroke,
Object actionMapKey)
Adds a binding for keyStroke to actionMapKey . |
void |
InputMap.put(KeyStroke keyStroke,
Object actionMapKey)
Adds a binding for keyStroke to actionMapKey . |
void |
JComponent.registerKeyboardAction(ActionListener anAction,
KeyStroke aKeyStroke,
int aCondition)
This method is now obsolete, please use a combination of getActionMap() and getInputMap() for
similiar behavior. |
void |
JComponent.registerKeyboardAction(ActionListener anAction,
String aCommand,
KeyStroke aKeyStroke,
int aCondition)
This method is now obsolete, please use a combination of getActionMap() and getInputMap() for
similiar behavior. |
void |
ComponentInputMap.remove(KeyStroke key)
Removes the binding for key from this object. |
void |
InputMap.remove(KeyStroke key)
Removes the binding for key from this
InputMap . |
void |
JMenuItem.setAccelerator(KeyStroke keyStroke)
Sets the key combination which invokes the menu item's action listeners without navigating the menu hierarchy. |
void |
JMenu.setAccelerator(KeyStroke keyStroke)
setAccelerator is not defined for JMenu . |
void |
JComponent.unregisterKeyboardAction(KeyStroke aKeyStroke)
This method is now obsolete. |
| Uses of KeyStroke in javax.swing.plaf.basic |
|---|
| Fields in javax.swing.plaf.basic declared as KeyStroke | |
|---|---|
protected KeyStroke |
BasicDesktopPaneUI.closeKey
Deprecated. As of 1.3. |
protected KeyStroke |
BasicSplitPaneUI.dividerResizeToggleKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicToolBarUI.downKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicTabbedPaneUI.downKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.downKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.endKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.homeKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicToolBarUI.leftKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicTabbedPaneUI.leftKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.leftKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicDesktopPaneUI.maximizeKey
Deprecated. As of 1.3. |
protected KeyStroke |
BasicDesktopPaneUI.minimizeKey
Deprecated. As of 1.3. |
protected KeyStroke |
BasicDesktopPaneUI.navigateKey
Deprecated. As of 1.3. |
protected KeyStroke |
BasicDesktopPaneUI.navigateKey2
Deprecated. As of 1.3. |
protected KeyStroke |
BasicInternalFrameUI.openMenuKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicToolBarUI.rightKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicTabbedPaneUI.rightKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.rightKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicToolBarUI.upKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicTabbedPaneUI.upKey
Deprecated. As of Java 2 platform v1.3. |
protected KeyStroke |
BasicSplitPaneUI.upKey
Deprecated. As of Java 2 platform v1.3. |
| Uses of KeyStroke in javax.swing.text |
|---|
| Fields in javax.swing.text declared as KeyStroke | |
|---|---|
KeyStroke |
JTextComponent.KeyBinding.key
The key. |
| Methods in javax.swing.text that return KeyStroke | |
|---|---|
KeyStroke[] |
Keymap.getBoundKeyStrokes()
Fetches all of the keystrokes in this map that are bound to some action. |
KeyStroke[] |
Keymap.getKeyStrokesForAction(Action a)
Fetches the keystrokes that will result in the given action. |
| Methods in javax.swing.text with parameters of type KeyStroke | |
|---|---|
void |
Keymap.addActionForKeyStroke(KeyStroke key,
Action a)
Adds a binding to the keymap. |
Action |
Keymap.getAction(KeyStroke key)
Fetches the action appropriate for the given symbolic event sequence. |
boolean |
Keymap.isLocallyDefined(KeyStroke key)
Determines if the given key sequence is locally defined. |
void |
Keymap.removeKeyStrokeBinding(KeyStroke keys)
Removes a binding from the keymap. |
| Constructors in javax.swing.text with parameters of type KeyStroke | |
|---|---|
JTextComponent.KeyBinding(KeyStroke key,
String actionName)
Creates a new key binding. |
|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV NEXT | FRAMES NO FRAMES |
Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.


Migrating to HTTPS
In February, Google announced that beginning in July with the release of Chrome 68, their web browser will mark all HTTP sites as "not secure".
So, while making a web site secure has always been important, now is the time to actually take the step from http
to https
. That is, if you haven't already.
I am using GitHub Pages for this site, so I checked out their guide on securing GitHub Pages sites with HTTPS, but unfortunately this doesn't cover custom domains. So what's a webmaster to do?
Cloudflare to the rescue
My web hosting is working on integrating Let's Encrypt, which will eventually offer me a free certificate for this site, but for some reason the progress is slow. And I couldn't wait. Chrome 68 is about to happen soon.
So, I chose to go with Cloudflare, and created an account. They offer a free plan for personal websites and there is an extensive instruction here.
You may also be interested in this article on CSS-tricks.com.
So, after adding my site to Cloudflare, I had a cup of coffee and sat down waiting for the DNS to kick in.
Well, actually, I didn't sit around waiting, because it took some time to finish. Anyway, it seems to be working fine, and yay, it's secure!


please refresh to update settings
autoplay options
skip first
seconds
skip last
seconds
player options
player skin:
dark
light
glass
back/next buttons:
questions/comments
/r/KissAutoplay


Consent form for participation in this online experiment
Center for Adaptive Rationality (ARC)
Designed by: Charley Wu
Email: cwu[at]mpib-berlin[dot]mpg[dot]de
Aim of the study and content
This study is a research project of the Max Planck Institute (MPI) for Human Development in cooperation with Harvard University. The data collected will be used for research purposes only.
The purpose of this study is to investigate how people search in an unknown environment. For this purpose you will be asked to perform a simple computer task in which you learn about areas on a grid and uncover rewards. A bonus of up to $1.50 will be granted based on your performance, along with a basic fee of $0.50 for completing the study. There will be no payment if the study is not completed. The study will on average last about 15 minutes.
What will happen to the data collected
After completing the experiment your Mturk ID will be deleted from the study data, once we have awarded you your bonus payment. This means that it will become impossible to link the study data to you.
The study data (but not Mturk ID) may be shared with cooperation partners for collaborative analysis. The study data may also be made publicly accessible via research data bases or scientific publications (typically via the Internet). This makes it possible for other researchers to check or replicate the results and enhances the quality of scientific research. The study data may also be used for new research questions going beyond the purposes of this particular study.
Participation in this study is voluntary. You may withdraw from the study at any time. You may also withdraw your consent to data processing and usage at any time before payment with effect for the future. To do so, please contact Charley Wu, cwu[at]mpib-berlin[dot]mpg[dot]de. Please note that data collected from you can no longer be associated with you, once your Mturk ID is deleted from the study data after payment.
By clicking on the button below, you agree to the following:
I have read and understood the conditions outlined above. I consent to participate in the study and agree to the collection, storage, and use of my data as described above.
Instructions:
Please read the following instructions very carefully:
In the following study, you will be presented with a series of 8 different grids to explore. By clicking on tiles in the grid, you reveal points that are associated to the location on the grid. On each grid, you will have either 20 or 40 clicks, with the number of remaining clicks displayed above the grid. When you run out of clicks, you will start a new trial on the next unexplored grid.
Each grid starts with a single tile revealed. Use your mouse to click and reveal new tiles, which will display a number corresponding to the number of points you gain. Revealed tiles are also color coded, as a visual aid to help you in this task. Darker colors correspond to larger rewards. Previously revealed tiles can also be reselected and there may be small changes in the point value.
It is your task to gain as many points as possible across all 8 grids. You will be assigned a bonus of up to $1.50 based on your total score across all grids.
Important! Points are clustered along the grid, such that areas with high-value points tend to appear close to each other and areas of low-value points tend to appear close to each other. All payoffs are greater than zero, with the maximum payoff differing between grids.
Below, we show some examples of what the distribution of points are like, with the darker tiles indicating higher point values.
Instructions:
Please read the following instructions very carefully:
In the following study, you will be presented with a series of 8 different grids to explore. By clicking on tiles in the grid, you reveal points that are associated to the location on the grid. On each grid, you will have either 20 or 40 clicks, with the number of remaining clicks displayed above the grid. When you run out of clicks, you will start a new trial on the next unexplored grid.
Each grid starts with a single tile revealed. Use your mouse to click and reveal new tiles, which will display a number corresponding to the number of points you gain. Revealed tiles are also color coded, as a visual aid to help you in this task. Darker colors correspond to larger rewards. Previously revealed tiles can also be reselected and there may be small changes in the point value.
It is your task to learn where the largest reward is in each of the 8 grids. You will be assigned a bonus of up to $1.50 based on the largest value you reveal in each grid.
Important! Points are clustered along the grid, such that areas with high-value points tend to appear close to each other and areas of low-value points tend to appear close to each other. All payoffs are greater than zero, with the maximum payoff differing between grids.
Below, we show some examples of what the distribution of points are like, with the darker tiles indicating higher point values.
Only when you answered all the question correctly will you be able to start the study.
Very good. You have answered all questions correctly and can now start the study.
Goal: Gain as many points as possible.
Goal: Learn where the largest reward is.
Summarized Instructions:
I. Below you see a grid with 11x11 tiles. When you click on a tile, the points of that tile are revealed and its value will be displayed. Tiles are colored, corresponding to the point value.
II. Tiles can be repeatedly clicked, although there may be small variations in the points earned. The most recently uncovered point value is displayed, while the history of revealed points can be viewed by hovering over the tile.
III. The points of a tile depends upon where it is located, with neighboring tiles tending to have similar point values.
IV. On top of the grid, you can see how many clicks you have left, the number of grids left to explore, and the amount of bonus you have currently earned.
V. There are 8 different grids with either 20 or 40 clicks in each (alternating).
Reward Earned on Current Trial: $0.00
Number of grids left: 8
Number of clicks left: 20
You have finished exploring this grid. You have 7 more grids to explore.
You have run out of clicks for this grid. Please click the tile where you believe the largest reward is located.
Thank you for completing our study.
Please check that your MTurk ID is correct. If not entered correctly, you may not be able to receive your bonus.
How old are you?
What's your gender?
Female
Male
Thank you for participating in our experiment.
You have achieved a bonus of $0.00
To earn your base fee of $0.50, please copy and paste the following completion code into the Amazon MTurk window for this HIT: MAB2018


In Physical Design (PD), there are so many terminologies involved. It could be daunting for a fresher to get acquainted with these terms at the beginning of his career. So, I thought of making a page with terminologies and its description. It might be helpful for a beginner or an experienced professional to quickly refer something related to PD.
I will be regularly updating this page if I found some new terminology along with its description. Make sure you bookmark it. 😉
Floorplanning
-
Aspect Ratio
It is the ratio between height and width of the core or a block. Routing resources, congestion, placement of standard cells, timing, clock-tree, placement of IO pads and packaging depends on the aspect ratio of the core or a block.
-
Cell Orientation
Every instance in a design such as a block, a macro, an IO pad or a standard cell have orientation associated with them. Orientation is defined as the rotation and/or mirroring of that instance about x or y axis to make connections meaningful and easier. Different types of cell orientations are R0, MX, MY, R90, R180, R270, MX90, MY90.
- R0 - No rotation.
- MX - Mirror through x-axis.
- MY - Mirror through y-axis.
- R90 - Rotate 90 degrees counter-clockwise.
- R180 - Rotate 180 degrees counter-clockwise.
- R270 - Rotate 270 degrees counter-clockwise.
- MX90 - Mirror through x-axis and rotate 90 degrees counter-clockwise.
- MY90 - Mirror through y-axis and rotate 90 degrees counter-clockwise.
-
Core Boundary
It is the area or region within which standard cells and macros are placed in the design. From top-level of a design, core boundary will be rectangular or square shaped. From block-level of a design, core boundary may have rectangular or rectilinear shape.
-
Core Utilization
It defines the total area occupied by the standard cells and macros in the block or top-level design. Typically, 70-80% utilization is taken into account for blocks as timing optimization involves placement of buffers or inverters which requires area.
-
Flylines
These are virtual lines that shows logical connections from an instance (block or macro or cell or IO pad). Using flylines, one can understand different connections from a block or a macro or a cell or an IO pad with which floorplanning could be done easily.
-
Halo
It is the area around the boundary of a block or a macro or a standard cell within which no other block or standard cell or macro is placed. If the blocks or standard cells or macros are moved, halos for those instances move along with it. It is also called as the keepout region. Halos of two adjacent instances can be overlapped.
-
Instance
A single occurance or a single object of a standard cell type or a macro or a block defined with a unique instance name. Ex: a 2-input AND gate could be instantiated as CELL_AND_1 and a usb 2.0 macro could be instantiated as USB_2_0_1.
-
Macro
A Macro is an Intellectual Property (IP) in a design that is owned by a company. These are reusable logic blocks used in a design without the necessity of building them from scratch. Two types of macro are Soft Macro and Hard Macro.
- Soft Macro is not specific to any technology node. Due to this, soft macros are unpredictable in terms of timing, area and power. But soft macros are more flexible in terms of reconfigurability and can be modified at the RTL level.
- Hard Macro is what we call as a Block in PD. It is designed specific to a technology node to meet timing, area and power.
-
Manufacturing Grid
The smallest resolution of the technology node is called as the Manufacturing Grid. Any geometry (or shape) created in the design must be snapped (or aligned) with this grid to avoid DRC errors.
-
Net
A logical connection between two or more pins of different instances. Some of the different types of net in a design are single fanout net, multi-fanout net, power net, ground net, signal net, clock net etc.
-
Physical Cells
These cells do not have any logical functionality in the design. Some of the standard physical cells are tap cells, tie cells, endcap cells, decap cells, filler cells, spare cells.
-
Pin
A pin is an IO terminal that is present in blocks or hard-macros or standard-cells of a design. Ex: For a 2-input AND gate, CELL_AND_1/a, CELL_AND_1/b are the input pins and CELL_AND_1/z is the output pin.
-
Placement Blockage
It is the area defined by the designer for the PnR tool to avoid placing, legalizing or overlapping standard cells in that particular area. If a block or standard cell or macro or IO pad is moved, placement blockages does not move along with it.
- Hard placement blockage means that the tool must not place, legalize or overlap any standard cell (including buffers and inverters) in the mentioned blockage area.
- Non-buffer blockage means that the tool can place, legalize or overlap any buffer or inverter in the mentioned blockage area except other standard cells in the design.
- Partial blockage means that the designer can adjust the percentage of blockage inside the blockage area and the tool should honor it. By default, 100% placement is blocked inside the blockage area.
-
Placement Grid
Placement grid is a multiple of the manufacturing grid in which all the standard cells are placed. Based on the placement grid, rows are formed and standard cells are placed.
-
Port
A port is an IO (Input/Output) terminal that is present in blocks or hard-macros of a design. From top-level, ports are pins in hard-macros or blocks. But from block-level, pins talking to top-level are celled as ports. Direction of ports can be input, output or in-out.
-
Power Domain
It is the collection of instances or blocks that share the same supply voltage in a design. Each power domain has a separate library associated with it.
-
Routing Blockage
It is the area defined by the designer for the PnR tool to block routing resources in single or multiple metal layers at a particular area. Routing blockages can be created and removed at any point in the design based on the requirements. It is possible to create routing blockages over a block or an instance using it’s cell type or instance name without the area numbers.
-
Row
Standard cell row is the area defined for placing standard cells in the design. Every standard cell in the design sits on the standard cell row. The row height is based on the standard cell height used in the design. Different types of rows are possible in a design based on sites or heights of standard cells used.
-
Track
Track is a virtual line (guideline) for the PnR tool in which routing of metal wires happen in the design. For each metal layer in the design, tracks are defined for preferred and non-preferred direction with specific pitch and offset. The PnR tool routes the metal wires by assuming the track at the center of metal piece.
-
Voltage Island
It is a dedicated area in the design which has its own row, site, cells and power structure defined for better power consumption. Level-shifters are used to convert from one voltage level to another.
-
Wire
A physically realized connection of a net which is routed by the router by having the center of metal piece in the track (on-track) using same or different metal layers and vias.
Placement
-
Cell Legalization
It means all standard cells must be placed on the standard cell rows (in placement grid) without any off-grid violations and overlaps. Only if all cells are legalized, the PnR tool will proceed with routing.
-
Cell Padding
It is a variable assigned to all standard cells or specific standard cell instances that belong to a cell-type in the design. Using this variable, the cell instances will have a padding associated with it around which other cells or blocks wont be placed. It’s like a breathing-space for a cell which is used to avoid congestion.
-
Driver
Any pin (or output pin) that drives one or multiple pins is called as a driver pin and it’s corresponding instance is called as the driver. There can always be only one driver pin in a design.
-
Fanin
The maximum number of inputs that a standard cell (or a logic gate) can accept is termed as the fanin of that standard cell.
-
Fanout
The maximum number of inputs (loads) that the output of a single standard cell (driver) can drive is termed as the fanout of that standard cell.
-
Load
Any pin (or input pin) that acts as a load for a driver pin is called as a load pin. There can be one or more load pins for a single driver pin, hence the term multi-fanout.
-
Placement Density
It is the amount of area utilized for placing cells (except filler cells) in the design. There is a golden equation that this placement density should be lesser than or equal to 70% so that the remaining 30% can be used for routing resources.
-
Standard Cells
Any complex chip is built using basic building blocks in digital design such as and, or, not, nor, nand, flipflop, buffer etc. Based on a technology node, these building blocks (called standard cells) are predesigned (i.e will have logical, symbol, abstract, layout and schematic views plus timing information for different scenarios) and given to the IC designer. Standard cells have fixed height and variable width. Height of these cells are same as the height of a standard cell row. In some cases, there might be double-height or triple-height cells that occupies two or three rows respectively.
Routing
-
Congestion
If the number of available routing tracks for routing in a particular area is lesser than the number of required routing tracks, then that particular area is said to be congested. Congestion creates shorts and DRCs which makes functionality fail in a design.
-
Detailed Routing
Detail routing determines the exact physical routing for all the logical nets in the design with the help of track assignment, wires and vias insertion at different metal layers. Real picture of congestion, metal DRCs and crosstalk issues are known only after detail routing the design.
-
Global Routing
Global routing partitions the entire design into tiles or global routing cells or g-cells and then, the paths for various nets are computed. Global routing doesn’t necessarily assign specific tracks to each net, but assigns each net to specific g-cells. Congestion can be estimated earlier in the design using Global routing before starting detail routing.
-
Metal Layers
Based on technology node, there are different metal layers involved for routing. Each metal layer is designated with a name say M1 or M3 and each metal layer has preferred and non-preferred directions with well-defined width, pitch, offset and tracks. Ex: M1 can have preferred direction as vertical and non-preferred direction as horizontal, while M4 can have preferred direction as horizontal and non-preferred direction as vertical.
-
NDR
Non-Default Rule is a routing rule applied for a single net or a group of nets that is not default. Default routing rule have defined width and spacing for each metal layer and via. Using Non-Default Rules, one can create an NDR rule with double or triple the width with double or triple the spacing. Ex: 1W2S means single width and twice the default spacing. NDRs are used for clock nets and critical nets (high-frequency nets) in a design to avoid Signal Integrity (SI) issues such as crosstalk and noise.
-
Shorts
When two or more wires or vias of different nets in the same metal layer cross each other, then it is termed as a short. Shorts are the number one concern after detail routing a block. These overlapping wire segments must be corrected for proper functioning of the design.
-
VIA
Vertical Interconnect Access (VIA) is the small vertical path (or opening) in an insulating oxide layer (cut-layer) that allows a conductive path (or connection) between different metal layers. Some types of VIA are single VIA, stacked VIA, VIA array etc.
Power Distribution
-
PMIC
PMIC or Power Management Integrated Circuit takes care of all possible supported external supplies and defines the power sequence for the board. It supplies power to different components inside the board. Also, it protects the board from unsupported overvoltage and undervoltage. It is usually software-controllable (often as an I2C device). Different voltage values such as VDD_1, VDD_2, VDD_3 etc., inside a chip are obtained using a PMIC.
-
Gridcheck
Gridcheck is a verification process that is performed to check for opens and shorts in the power distribution grid of a design. For a design to function properly, it must be free from opens and shorts. Before analyzing a design for static and dynamic IR drop, it must be free from opens and shorts (i.e. zero opens and zero shorts).
-
Static IR Drop
As the name suggests, even when the chip is off or quiescent (static), there exists some amount of power dissipation due to transistor’s leakage characteristics giving rise to leakage power. This is due to the characteristic of CMOS transistors itself, which is a function of power supply voltage \( V_{DD} \), threshold voltage \( V_{th} \) and transistor’s dimension (width \(W \) and length \( L \)). Static IR drop analysis is a vectorless IR drop analysis with average current cycles. It is typically used for Electro-Migration (EM) analysis where current limit is checked for wires.
-
Dynamic IR Drop
As the name suggests, dynamic power dissipation occurs when the transistors are switching from one logic state to another. There are two types of dynamic power dissipation in CMOS circuits namely switching power and short-circuit power. Dynamic IR drop analysis is a vectorless or VCD based IR drop analysis with worst-case switching currents. It is typically used to check voltage drop limit for switching instances.
-
ESD Cell
ESD or Electro-Static Discharge cells are clamp circuits that are placed at appropriate locations in the chip to provide a low impedance discharge path for the Electro-Static Discharge and clamp the signal voltage at a level that avoids dielectic breakdown. As technology node decreases in feature size, ESD cells are mandatory to avoid functional failure or burn out of the chip.
Physical Verification
-
Antenna
Antenna violation, commonly referred as the plasma induced gate oxide damage, occurs during manufacturing stage of a chip. It is a result of charge accumulation on metals and discharge to a transistor’s gate through gate oxide which ultimately damages the gate.
-
DRC
Design Rule Checks are performed at the physical design stage to verify if the designed layout meets the design rules so that the design can be manufactured properly without any issues. These design rules are specific to a technology node and are provided to the designer by the foundry. Base and Metal are checked and verified completely with zero DRC error before tapeout. DRC include physical layout checks such as metal width, metal pitch, metal spacing, via spacing, via type, base (well connectivity).
-
LVS
Layout vs Schematic is another physical verification check that is performed at the physical design stage. This is to ensure that the designed layout is functionally the same as the schematic netlist so that there isn’t any deviation in functionality of the design. There must be zero opens and shorts without any DRC errors. Some other LVS errors are parameter mismatches and unbound pins.
-
ERC
Electrical Rule Check is a physical verification check that reports any electrical connection that is potentially dangerous. It checks the design for accurate power and ground connections. Transistors with gate unconnected (floating gate), wrong transistor-level connections (such as shorted drain and source, connecting high voltage to thin gates), floating nets, floating pins, floating wells, antenna errors are some of the checks reported here.
In case if you found something useful to add to this article or you found a bug in the code or would like to improve some points mentioned, feel free to write it down in the comments. Hope you found something useful here.
Happy learning!


Recipe 5.9. Looking for Items in a Sorted SequenceCredit: Noah Spurrier ProblemYou need to look for a lot of items in a sequence. SolutionIf list L is sorted, module bisect from the Python Standard Library makes it easy to check if some item x is present in L: import bisect x_insert_point = bisect.bisect_right(L, x) x_is_present = L[x_insert_point-1:x_insert_point] == [x] DiscussionLooking for an item x in a list L is very easy in Python: to check whether the item is there at all, if x in L; to find out where exactly it is, L.index(x). However, if L has length n, these operations take time proportional to nessentially, they just loop over the list's items, checking each for equality to x. If L is sorted, we can do better. The classic algorithm to look for an item in a sorted sequence is known as binary search, because at each step it roughly halves the range it's still searching onit generally takes about log2n steps. It's worth considering when you're going to look for items many times, so you can amortize the cost of sorting over many searches. Once you've decided to use binary search for x in L, after calling L.sort( ), module bisect from the Python Standard Library makes the job easy. Specifically, we need function bisect.bisect_right, which returns the index where an item should be inserted, to keep the sorted list sorted, but doesn't alter the list; moreover, if the item already appears in the list, bisect_right returns an index that's just to the right of any items with the same value. So, after getting this "insert point" by calling bisect.bisect_right(L, x), we need only to check the list immediately before the insert point, to see if an item equal to x is already there. The way we compute x_is_present in the "Solution" may not be immediately obvious. If we know that L is not empty, we can use a simpler and more obvious approach: x_is_present = L[x_insert_point-1] == x However, the indexing in this simpler approach raises an exception when L is empty. When the slice boundaries are invalid, slicing is less "strict" than indexing, since it just produces an empty slice without raising any exception. In general, somelist[i:i+1] is the same one-item list as [somelist[i]] when i is a valid index in somelist: it's an empty list [ ] when the indexing would raise IndexError. The computation of x_is_present in the recipe exploits this important property to avoid having to deal with exceptions and handle empty and nonempty cases for L in one uniform way. An alternative approach is: x_is_present = L and L[x_insert_point-1] == x This alternative approach exploits and's short-circuiting behavior to guard the indexing, instead of using slicing. An auxiliary dict, as shown in Recipe 5.12, is also a possibility as long as items are hashable (meaning that items can be used as keys into a dict). However, the approach in this recipe, based on a sorted list, may be the only useful one when the items are comparable (otherwise, the list could not be sorted) but not hashable (so a dict can't have those items as its keys). When the list is already sorted, and the number of items you need to look up in it is not extremely large, it may in any case be faster to use bisect than to build an auxiliary dictionary, since the investment of time in the latter operation might not be fully amortized. This is particularly likely in Python 2.4, since bisect has been optimized very effectively and is much faster than it was in Python 2.3. On my machine, for example, bisect.bisect_right for an item in the middle of a list of 10,000 integers is about four times faster in Python 2.4 than it was in Python 2.3. See AlsoDocumentation for the bisect module in the Library Reference and Python in a Nutshell; Recipe 5.12. |


McDonald's Brings Back Classic Happy Meal Toys
by Mike FaheyThe McDonald’s Happy Meal has produced some pretty iconic crappy, french fry-scented bits of colourful plastic over the years. From November 21, Suprise Happy Meals will be packed with one of 17 classic toys from the past four decades, including Power Rangers, Tamagotchi, Furbies and more.
The good news is there are 17 iconic food toys in the special Surprise Happy Meals, including remakes of some of the most sought-after McDonald’s toy collectibles. I need the Dinosaur Happy Meal and hamburger transforming figures, and if I don’t come out of this special event with all three of the special McNugget figures, what’s the point of life?
- Cowboy McNugget (McDonald’s): 1988
- Fireman McNugget (McDonald’s): 1988
- Mail Carrier McNugget (McDonald’s): 1988
- Hamburger Changeable (McDonald’s): 1989
- Grimace (McDonald’s): 1990
- Dino Happy Meal Box Changeable (McDonald’s): 1991
- McDonald’s Hot Wheels Thunderbird (Mattel): 1993
- Hamburglar (McDonald’s): 1995
- Power Rangers (Hasbro): 1995
- Space Jam Bugs Bunny (Warner Brothers): 1996
- Patti the Platypus (Ty Beanie Baby): 1997
- 101 Dalmatians – U.S. Exclusive (Disney): 1997
- Tamagotchi (Bandai): 1998
- My Little Pony (Hasbro): 1998
- Furby (Hasbro): 1999
- Sorcerer’s Apprentice Mickey – U.S. Exclusive (Disney): 2002
- Hello Kitty (Sanrio): 2013
Editor's Note: This list comes from the U.S. but the promotion is being launched in Australia soon after, so we expect a similar range of toys here.
Thanks to my children’s insatiable appetite for chicken nuggets and my local McDonald’s jumping the gun, my family has already acquired the Furby and Power Ranger toys. That means we need to purchase at least 15 more Happy Meals to collect the whole set. Or wait a week and eBay the damn things.


Breaking Myths
Why are we even having this discussion ?
Increasing awareness about technologies in application and how to use it better.
Agenda
- Facts about JS and JS in Saltmarsh
- SM web’s grunt lifecycle
- Backbone.js basics(Model, View, Validation, Router) – Just fyi
- Backbone pattern used in SM
- Other helper JS libs jQuery, handlebars
- JS basics and quiz
- Best practices / Formal guideline
Facts about JS
https://github.com/jashkenas/backbone/wiki/Projects-and-Companies-using-Backbone
JS in Saltmarsh
- https://github.com/AlDanial/cloc
The big picture: SM web’s grunt lifecycle
data-src="img/visio image here.png">
Backbone.js basics
- MVC Framework (Backbone library)
- Backbone is an MV framework, controller implementation is integrated with backbone on client side
- Backbone gives us the module structure for a large-scale application but still makes the design of the project flexible enough to customize it as per our needs
- Backbone.js gives structure to web applications by providing models with key- value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface
- Data comes from WebAPI in form of model.
- Handle Bar - Allows you to create template with placeholders
Backbone.js Constructs
- Model (and Collection): Application (domain) data objects that are retrieved from and persisted to the server
- View: HTML presentation of the data stored in the models and DOM 'controller'
- Router: Controller that saves the state of the application via a url hash
- Events: Module that can be mixed in to any object, giving the object the ability to bind and trigger custom named events.
- This wasn't a detailed Backbone session, theres more to it including how MVC works and backbone page lifecycle. Checkout backbonejs.org
BackboneJS usage and pattens in SM
Javascript the good parts:
Thank you
Ankit Arora


I believe a roaster is to a coffee farmer, what a publisher is to a writer. We are the last link in the chain of a journey of a coffee's story. The magic of any coffee is written on the farm; a unique tale crafted from variety, geography, history, know-how. As roasters, our jobs are to curate these stories and present them as honestly as possible (and in a nice wrapper), to our audience.
- Ben Roberts, Founder and Director


Appointed Committee Chairs
Click on a name below to contact a committee chair via email or use<EMAIL_ADDRESS>to send an email to headquarters.
Marta A. Alcumbrac
Bench Bar Committee Co-Chair
James M. Baratta, Jr.
Young Lawyers Committee Co-Chair
Alan J. Carnegie
Construction Committee Co-Chair
Lisa Collinson
General Liability Committee Co-Chair
Michael A. Colton
Lawyer Defense Committee Chair
Patricia Daehnke
Coalition for Improving Court Access Chair
Jean Daly
Brown Bag Seminars Committee Co-Chair
Insurance Committee Co-Chair
Randall J. Dean
Emeritus Committee Co-Chair
Julianne DeMarco
MedMal Committee Chair
Peter Doody
Transportation Committee Co-Chair
San Diego Seminar Co-Chair
Chris Faenza
Employment Committee Co-Chair
Thomas Feher
Employment Committee Co-Chair
Steven S. Fleischman
Amicus Committee Co-Chair
Dana A. Fox
Law Firm Management Seminar Co-Chair
Tom Gmelich
Law Firm Management Seminar Co-Chair
Bjorn C. Green
Construction Committee Co-Chair
Colin Harrison
Long Term Care Litigation Chair
Lauren Kadish
Young Lawyers Committee Co-Chair
Robert L. Kaufman
Public Entity Committee Chair
Patrick J. Kearns
Court Liason/Bench Bar Committee Co-Chair
Anthony C. Kohrs
Young Lawyers Committee Co-Chair
Edward Leonard
Membership Committee Co-Chair
Philip H. Lo
Insurance Committee Co-Chair
Diana Lytel
Diversity Committee Co-Chair
General Liability/Premises Committee Co-Chair
Bryan Martin
San Diego Seminar Co-Chair
Lisa McMains
Brown Bag Committee Co-Chair
Brian Merges
Construction Committee Co-Chair
Gary T. Montgomery
Golf Committee Co-Chair
Hannah L. Mohrman
Diversity Committee Co-Chair
Robert A. Olson
Emeritus Committee Co-Chair
Tom M. Peabody
MedMal Committee Co-Chair
Lisa Perrochet
Publications/Website Committee Co-Chair
David Pruett
Coalition for Improving Court Access Co-Chair
Alice Chen Smith
Diversity Committee Co-Chair
Lawrence R. Ramsey
Products Committee Co-Chair
Michael N. Schonbuch
General Liability/Premises Committee Co-Chair
Eric C. Schwettmann
Employment Committee Co-Chair
Patrick Stockalper
Intellectual Property Chair
William Woodland
Membership Co-Chair
Golf Co-Chair
Ted L. Xanders
Amicus Committee Co-Chair


- Arbitrary binary data can be represented with a 6-bit char set.
- No problems with 7-bit char set restrictions.
- No problems with line length restrictions or special control characters.
- Only an enlargement of about 33 % (instead of an enlargment of 100 % when encoding to hexadecimal values).
|
- No support for distribution of big files.
- Enlargement of about 33 % (in comparison to the original file).
Only UUencode:
- No EBCDIC support.
- No defined standards.
|


Welcome to Avaa!.
With you, Always.
John doe
John doe
Home
Schedule
Timetable
Hostel
Budget
Payments
Assignments
Contact Us
Your Timetable
Your Timetable for today:


You can't buy happiness, but you can buy pizza, and that's
almost the same thing.
First Name:
Last Name:
Phone Number:
Email:
House Number:
Street Name:
County:
City:
Total: Kshs


JavaScript Tone Generator
Ear:
Left
Right
Wave type:
Frequency (Hz):
-1
+1
-12
+12
Volume (dB):
Modulation index:
Modulation frequency:
Start


|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
| Quick Links: Home | Nation | World | Business | Entertainment | Sci-Health | Special Reports | Photos | Current Issue | Archive | |
|
Copyright © 2005 Time Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited. Subscribe | Customer Service | Help | Site Map | Search | Contact Us | Privacy Policy | RSS Feeds Terms of Use | Reprints & Permissions | Opinion Leaders Panel TIME Classroom | Press Releases | Media Kit | Try AOL for 1000 Hours FREE! EDITIONS: TIME Europe |TIME Asia | TIME Pacific | TIME Canada | TIME For Kids |


1. pwd
Finds out the path of the current working directory (folder) you’re in.
2. cd
Navigates through directories. cd
goes to a folder located in your current path. You can also use cd /folder1/folder1.1/destination
folder
for example.
cd ..
(with two dots) to move one directory up
cd
to go straight to the home folder
cd-
(with a hyphen) to move to your previous directory
Note that Linux folders are case sensitive.
3. ls
The ls command is used to view the contents of a directory. By default, this command will display the contents of your current working directory.
If you want to see the content of other directories, type ls and then the directory’s path. For example, enter
ls
/home/username/Documents
to view the content of Documents.
There are variations you can use with the ls command:
ls -R
will list all the files in the sub-directories as well
ls -a
will show the hidden files
ls -al
will list the files and directories with detailed information like the permissions, size,
owner, etc.
4. cat
cat (short for concatenate) is one of the most frequently used commands in Linux. It is used to list the contents
of a file on the standard output (sdout). To run this command, type cat followed by the file’s name and its
extension. For instance: cat file.txt
.
5. cp
Use the cp command to copy files from the current directory to a different directory. For instance, the
commandcp
scenery.jpg /home/username/Pictures
would create a copy of scenery.jpg (from your current directory)
into the
Pictures directory.
6. mkdir
Use mkdir
command to make a new directory — if you type mkdir Music it will create a directory
called Music.
7. rmdir
If you need to delete a directory, use the rmdir command. However, rmdir only allows you to delete empty directories.
1) A Linux system running Docker
2) Preconfigured containers loaded and running
3) Access to a terminal window/command prompt (Ctrl+Alt+T or Ctrl+Alt+F2)
4) A user account with sudo privileges
The docker attach command links a local input, output, and error stream to a container. By default, it launches in a bash shell. To connect to a running container, enter the following:
sudo docker attach Container_Name
In the example below, the system will connect to the nginx-test container:
sudo docker attach nginx-test
Once the command is executed, you will be working in the container. Any commands you run will affect the virtual Docker environment.
More Linux Commands: https://linuxconfig.org/linux-commands
More methods to login Docker Container: https://www.youtube.com/watch?v=2FOnngHmF7Y


Hi! I'm
Hemant Sahay
B.Tech ,
Electronics and Communication Engineering
(Delhi Technological University)
Visit Resume


Collin Lynch
Transaction-Based Analysis of Piazza and other learning platforms
In this talk I will briefly describe our analysis of data from online learning platforms with a special attention to our work with Piazza. I will also describe our shared library for Piazza data analysis, itself the product of a CSSPLICE grant. And I will start the discussion for our initiative to share standards for the analysis of transactional data from educational platforms.


ontology.effects.binary
Classes
AttractGaze
BounceForward
CollectResource
KillIfFromAbove
KillIfOtherHasMore
PullWithIt
TeleportToExit
WallStop


I am studying information system at Brigham Young University. BYU is well-known for its spiritual environment and outstanding academic program in the World. I receive professional business programming skills and enterprise stsem development training at the prestige Marriott School
I am from Hsinchu, Taiwan. I have been living in the U.S. in the past five years for University education. I am passionate about using technology to develop busines tools and computer applications. I love movies, cooking, basketball, rock drums, reading, camping, hiking, and BYU Football.


Grand Master Tobias:
(Tobias seems to conduct some kind of a ritual while holding the Sealed Prophecy. A bright light briefly shines forth from the Writings, then fades...)
There! It is unsealed...
If you can interpret this properly, you should be able to determine the location of the fallen angel.
Take this Prophecy - Path of the God
Receive the Prophecy.