`Gladiator' – Hail Caesar! by Homer Yen (c) 2000
`Gladiator' is a story that roars one simple message. And that message is `Charge!' This film steadily rushes towards you like centurions on a chariot. Fun summer movies are about being visceral delights. And this one delivers. Heroic in tone, epic in scope, and far from bloodless, the summer's first blockbuster-to-be is a grand tale of Rome, retribution, and requital.
The film opens with an ambitious battle sequence. `At my command, unleash Hell,' says the film's hero, General Maximus (stately Russell Crowe). Maximus leads his legion of troops into battle, masterminding an important victory for the glory of Rome. His continued leadership has brought him the admiration and love of the current but aging Emperor, Marcus Aurelius (regal Richard Harris). A benevolent leader with noble visions of Rome's future, his final hope is for Maximus to succeed him when he dies.
This decision infuriates Aurelius's tempestuous son, Commodus (darkly portrayed by Joaquin Phoenix). Consumed with jealousy, he attempts to destroy Maximus and his family before ascending the throne himself. The crafty General manages to escape, but his family is not as lucky.
Stripped of everything he loves, he is captured by slave traders and then subsequently sold to Proximo (Oliver Reed), a businessman who specializes in training Gladiators. In the training arena, Maximus filets his opponents as easily as Japanese chefs filet fish. But he is also taught that he must win over the crowd if he is to truly win the match.
As a victorious and popular gladiator, he will travel to Rome to perform in the Colosseum. As a man with a noble heart, his personal crusade is followed with much interest. As such, he garners support from fellow gladiators (including Djimon Honsou), a former love/Commodus's sister (Connie Nielsen), and a civic-minded Senator (Derek Jacobi). He looks for a chance to avenge the death of his family, restore his honor and posthumously bring forth the vision of Emperor Aurelius.
To enjoy `Gladiator' fully, find a big screen with a good sound system. There is an array of impressive combat sequences with equally imposing sound effects. When you hear a battle axe being thrown, you might want to look over your right shoulder just in case. Cinematography is also beautiful. From its renderings of ancient Rome to the way hues are incorporated into scenes (for example, gray hues magnify the bleakness of battle while rich amber hues reflect the lushness enjoyed by the nobility), careful attention is taken to immerse the audience in the movie-going experience. And the 165-minute saga of Maximus is stately and absorbing. Crowe is a gladiator's gladiator and he brings depth and feeling to a new breed of action heroes.
Yet, I have two reservations (no spoilers given). The first was that Commodus was seemingly baleful, but his actions took a backseat to his psychotic personality. He was all talk but a man of little action. When the final showdown occurs, the audience doesn't view him as much of a threat. A greater reservation, however, was the pace of the final act. So much momentum was building towards the finale that its ultimate resolution seemed like an apology from the director because they couldn't secure enough financing to finish it with the same kind of epic battle that catapulted its beginning.
But these are just minor points in an otherwise grand story. `Gladiator' is spectacular summer fare. Its tale is engaging, its presentation is bold, and it certainly sets the bar for summer movies at a high level.
Grade: A-
S: 1 out of 3 L: 1 out of 3 V: 3 out of 3
Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
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


I am an italian girl, born and grown up in Germany, enjoying the beauty & delights of Zurich since I arrived in 2010. I like food in all it's facets and this also includes spending time with my friends and family!
Due to a chronical autoimmune disease I needed to change my whole nurishment habits some years ago. It was hard to learn what was safe food, to find gluten free products in the supermarket and of course say no to the food I was used to. Explaining the whole story to family, friends and strangers was always difficult.
Eating out is all about explaining your needs, hoping to be understood and trust in whatever happens in the kitchen. I struggeled a lot with eating out. But now with years of experience, I have gathered a lot of knowledge on where to eat safe. So I wanted to share this know how with you, to give you a little peace of mind.
Every location contains detailed information. When clicking on one of the pins on the map the information appears on your screen. Most of them I personally experienced, so I added information whether they had a special menu wit allergen declaration. In any case do not forget to inform the waiter about your food restrictions.
For coeliacs: Please look at the flag "IG Zöliakie approved" and go to those restaurants as they are members of IG Zöliakie (celiac association of the german speaking part of switzerland). In any case do not forget to always communicate your nutrition restrictions, allergies to the waiter.
For other restaurants it is always helpful to have a multi language info card with you (made by IG Zöliakie).
Download Infocard
Do you like the map? Share your experiences with me. Please send me your feedback via mail.
To check how many people visit this website I use common tracking tools. Is it ok with you? Further information can be looked up here.
That's ok with me.


My name is Matthew and I want to tell you a bit about my journey.
I’ve always known that I wanted to do something special with my life, and I’ve always wanted to connect with people and help them feel strong and empowered. But the truth is, I struggled a lot growing up.
Like a lot of children my age, I was bullied physically and emotionally for my looks, my personality, and my values. I never seemed to fit in or connect to people in a way that made sense or felt authentic.
Having gone through that as kid, I still faced similar issues as an adult. I was always looking for ways to fit in. I looked for heroes in my life who would save me. I looked to friends, romantic relationships, therapists, mentors and gurus. I tried everything I could to find the secret to being happy, but I often felt like I was spinning my wheels. I spent so much of my life depressed and anxious, never truly living a satisfying life that I wanted.
After many painful years I eventually realized that I couldn’t rely on others to find that happiness or confidence. I had to take a deep look inside myself and start holding myself accountable. I wanted to commit to making a real change.
I would always feel overwhelmed by my larger goals, so I started developing small habits that seemed ineffective at the time. But those small changes created a foundation. I started slowly rebuilding myself, brick by brick, one day at a time. Physically, emotionally, and spiritually I began to change.
The truth is, change didn’t happen overnight. Becoming a hero to myself wasn’t always a grand and epic adventure. There were plenty of sacrifices I had to make along the way. I dedicated myself to change and eliminated distractions and relationships that were holding me down. I made a commitment to finding that hero.
Since then, I’ve felt a desire to help people who have felt their own sense of inadequacy. Whether through bullying, emotional or physical trauma, I have always felt a strong desire to lift up those who feel the same internal struggle that I did.
For the majority of my life I have also loved superheroes. Through my own journey, I quickly realized that if I could do this, others could too. But to do so, it would require time, dedication and action.
My Heroic Life isn’t just a saying or a catchy phrase; it’s a call to action. It is an opportunity for each of us to live better, fulfilling and empowering lives. It is a choice that we make every single day to do the right thing. It’s an opportunity to lift ourselves and each other up and to stand strong in the face of adversity.
My hope is that you will come here to find inspiration and take control of your life.  I hope that through my podcast, you will find that inspiration and discover that YOU alone have the responsibility to change your life, and that nobody else can give you that power.
I have complete faith in you. And I am glad you are here. Let’s begin our heroic journey together. One step at a time.
Matthew


--- layout: page title: Atom Format (OData Version 2.0) date: 2014-02-28 03:35:17.000000000 +08:00 permalink: /documentation/odata-version-2-0/atom-format/ ---
OData supports two formats for representing the resources (Collections, Entries, Links, etc) it exposes: the XML-based Atom format and the JSON format. This document describes how OData resources are represented in Atom (plus additional elements defined in AtomPub) and [OData-JSON] describes the JSON representation. The content type negotiation section of the [OData-Operations] document describes how clients can use standard HTTP content type negotiation to tell an OData service which format it wants to use.
As described in Atom [RFC4287], Atom is an XML-based document format that describes Collections of related information known as "feeds". Feeds are composed of a number of items, known as Entries. AtomPub [RFC5023] defines additional format constructs for Entries and Feeds to enable the resources they represent to be easily categorized, grouped, edited and discovered. For the remainder of this document, the term Atom is used to represent the combination of the format/representation rules defined in Atom[RFC4287] and AtomPub [RF5023].
As noted in the OData Basics section of [OData:Core], OData services expose Collections of structured Entries, making Atom a natural fit for representing OData resources. Since Atom does not define how structured data is encoded with feeds, to enable transfers of structured content by OData services, this document defines a set of conventions for representing structured data in an Atom feed.
It should be noted that feeds following the conventions defined in this document are valid AtomPub feeds and can be consumed by feed readers, tools, etc. which are only aware of the Atom standards ([RFC4287] & [RFC5023]), but not the additional conventions defined in this document.
The following sections define how resources (Collection, Entries, etc) exposed by an OData service can be represented in requests and responses payloads using the Atom format. For details regarding how to create various request types (Retrieve, Create, etc) see [OData-Operations] .
Through out this section the notation
Values of OData primitive types are represented as values of XML elements/attributes as per the table below. Note: The type system used by OData services is described in full in the primitive types section of the [OData-Core] document. In addition to the rules stated in the table, if the value of a primitive type is null, then it is represented as an empty XML element with an m:null="true" attribute ("m" identifies the OData metadata namespace).
| Primitive Type | Serialization Format in XML Documents |
|---|---|
| Edm.Binary | Base64 encoded value of an EDM.Binary value. See [RFC3548] . |
| Edm.Boolean | true | false |
| Edm.Byte | Same as the literal form in [OData:Core], except without the surrounding |
| Edm.DateTime | Same as the literal form in [OData:Core], except without the surrounding datetime'' syntax |
| Edm.Decimal | Same as the literal form in [OData:Core], except without the trailing "m" |
| Edm.Double | Same as the literal form in [OData:Core] |
| Edm.Guid | Same as the literal form in [OData:Core], except without the surrounding guid'' syntax |
| Edm.Int16 | Same as the literal form in [OData:Core] |
| Edm.Int32 | Same as the literal form in [OData:Core] |
| Edm.Int64 | Same as the literal form in [OData:Core] |
| Edm.SByte | Same as the literal form in [OData:Core] |
| Edm.Single | Same as the literal form in [OData:Core], except without the trailing "f" |
| Edm.String | Same as the literal form in [OData:Core], except without surrounding double quotes |
| Edm.Time | Same as the literal form in [OData:Core], except without the surrounding time'' syntax |
| Edm.DateTimeOffset | Same as the literal form in [OData:Core], except without the surrounding datetimeoffset'' syntax |
As described in [OData-Core], if a service exposes several Collections, then to aid discovery of those Collections by clients it is useful for the service to expose a Service Document which lists the available Collections. Service Documents are described in AtomPub [RFC5023], section 15.
For example, the URI https://services.odata.org/OData/OData.svc identifies the Service Document of a sample OData service which exposes a Categories, Products and Suppliers Collection. For convenience, a sample Service Document is shown in the listing below.
{% highlight xml %}Collections represent a set of Entries. In OData, Collections are represented as Atom feeds ([RFC5023] ), with one Atom entry for each Entry within the Collection. For example, a Collection of product category Entries (that could be part of a product catalog) exposed by an OData service, as identified by the URI https://services.odata.org/OData/OData.svc/Categories, is represented as shown below. The format of
Note: The "m" and "d" prefixes represent the OData metadata and data namespaces. It is likely the next version of OData will generalize the namespace URI to use an odata.org based URI.
OData V1: {% highlight xml %}In response payloads only, OData v2 supports two pieces of collection-level metadata: an Entry count (the total count of the number of entities in the Collection) and "next links" in the case when a partial listing of the Collection of Entries is being represented.
The Entry count, is only included in the feed returned by an OData service when the request URI includes the $inlinecount System Query Option. In this case, the count information is represented as a
In response payloads only, if the server does not include an
In OData, Entries are represented as Atom
If the Entry being represented links to other Entries via Navigation Properties (e.g. a Product is related to a Category), then the Links are represented as
Metadata describing the Entry being represented can be specified using additional Atom-defined and OData-defined elements/attributes as defined by the following list.
m:etag attribute
For example, as shown in the following listing, the Category Entry identified by the URI https://services.odata.org/OData/OData.svc/Categories(0), has two primitive properties (ID & Name) and one Navigation Property named â€œProductsâ€, which identifies a feed of Product Entries related to the Category.
{% highlight xml %}To conserve resources (bandwidth, CPU, and so on), it is generally not a good idea for an OData service to return the full graph of Entries related to the Entry (or Collection of entries) identified in a request URI. For example, an OData service should defer sending related Entries unless the client explicitly asked for them using the $expand System Query Option which provides a way for a client to state related entities should be represented inline.
As shown in the example in the prior section, by default properties which represent Links (the "Products" property in the example) are represented as a element to indicate the service deferred representing the related Entries. If needed, a client can then use the URI in the href attribute in a subsequent retrieve request to obtain the related Entries.
As described in the $expand System Query Option section of the [OData-URI] document, a request URI may include the $expand query option to explicitly request that a linked to Entry or collection of Entries be serialized inline, rather than deferred.
In this case the related Entry or collection of Entries is represented as the child element of an
Media Link Entries (MLE) are represented in the same way as regular Entries as described in Representing Entries; however, they also contain additional metadata per Entry that describes the Media Resource (MR) associated with the Entry and the
This additional MR-specific metadata is represented by the following constructs in the
Services may wish to have more flexibility over how Entries are represented within an
In general a service may choose to deviate from the conventions defined in Representing Entries section above and represent the value of a Property of an Entry as the value of a standard Atom element (Title, Summary, etc) or as the value of an element in a custom namespace. When a service does this form of customization it breaks the shared assumption between client and server regarding how Entries are encoded within an
The following table lists all the Feed Customization annotations defined in OData.
For example, the sample Service Metadata Document at https://services.odata.org/OData/OData.svc/$metadata states the Name Property of the Category Entry is represented as the value of the
If the Category Entry in the example above was part of a type hierarchy and the Name property was defined on the type Category derives from, then the mapping from Name to
Instead of mapping the Name property to an Atom-defined element, a Property may be mapped to a custom element in any namespace. For example, the following listing maps the Street Property of the Address Complex Type on a Supplier entry to a custom
When represented in a request/response payload as part of an Entry, Complex Type or a standalone construct in a request payload, primitive properties are represented in Atom as child elements of an
See section 3.1 for the format of Properties when they are represented independently from their defining Entry (i.e. outside the context of the defining Entry).
When represented as a property of an Entry or Complex Type (also within an Entry) in a request/response payload, a property whose type is a complex type is represented as an XML element with each property of the complex type represented as a direct child element (as described in the prior section for primitive properties). For example, the Address Complex Type of a Supplier Entry is shown in the example below.
See section 3.1.2 for the format of Complex Type Properties when they are represented independently from their defining Entry (i.e. outside the context of the defining Entry).
The smallest unit of information that can be represented in Atom is an Entry. In several application scenarios it is practical to be able to identify a specific piece of information within the Entry, particularly when the entry is mapped to an application-level construct on the server. For example, a Presentation Entry may have a Property that is the abstract describing the presentation.
To enable this scenario, as described in the Resource Path section in the [OData-URI] document, OData supports directly addressing a Property of an Entry. Since there is not a natural mapping of a single Property (outside of the context of the defining Entry) to an Atom representation, OData represents the constituent parts of an Entry using a simple XML representation, which is described by the following subsections.
As described in the Resource Path section in the [OData-URI] document, OData supports directly addressing a Property of an Entry. The following subsections describe how each type of Property is represented in XML.
When a primitive Property is represented as a standalone construct in a response from an OData service (such as when a retrieve request is made to a URI that identifies a single Property) it is represented as a single XML element where the element name equals the name of the Property and the value of the element is the value Property value. For example, the response payload to a retrieve request that identifies the Name property of a Category Entry is represented as shown below.
{% highlight xml %}When a Property whose type is a complex type is represented as a standalone construct, such as when a retrieve request is made to a URI that identifies a single Property, it uses a single XML element with the name of the Property and child elements for each Property defined on the complex type (formatted as per this section of the prior â€œRepresenting Primitive Propertiesâ€ section). For example, the response payload to a retrieve request that identifies the Name property of a Category Entry is represented as shown below.
{% highlight xml %}OData services may support addressing the entry value of a primitive Property (see the description of the $value URI segment). In this case, the value is returned using the format (aka mime type) the OData service deems to be the entry format for the Property. For example, the HTTP response from the sample OData service when retrieving the Name string Property of a Category Entry is shown in the example below.
{% highlight xml %}HTTP/1.1 200 OK DataServiceVersion: 1.0; Content-Type: text/plain;charset=utf-8 Food{% endhighlight %}A Link (or collection of Links) represents an associated Entry (or collection of associated Entries). As described in [OData-Operations] Links can be retrieved and modified to change the associations between Entries. A single link is represented as a
Note: in the paragraph above, "d" represents the OData Data Namespace.
For example, a link with multiplicity 1 (ex. Product is related to a single Supplier) would be represented in XML in a response as:
{% highlight xml %}For example, a link with multiplicity greater than 1 (e.g. Supplier is related to many products) would be represented in a response as:
{% highlight xml %}As described in [OData-Operations] OData services may expose custom behaviors via Service Operations, which may accept input parameters identified by the request URI (as described in [OData-URI]). This section specifies how the results of a Service Operation are formatted using Atom or XML. Service operations support returning:
If a Service Operation returns a collection of Entries or a single Entry, then the Entries (or Entry) are formatted in Atom as described in the Representing Collections of Entries or Representing an Entry section.
If a Service Operation returns a single primitive value, then it is formatted in XML as per the Representing Primitive Properties section. Likewise, if a Service Operation returns a single Complex Type value, then it is represented in XML as per the Representing Complex Type Properties section.
If a Service Operation returns a collection of primitive values, then the primitives are returned as the value of
If a Service Operation returns a collection of complex types, then the collection is represented in XML by a root element whose name is equal to the name of the Service Operation and includes one child


| Interface | Description |
|---|---|
| ChangeSwitch<R> |
Visitor pattern interface for the
Change class hierarchy. |
| Class | Description |
|---|---|
| Change<T> |
Object change notification.
|
| ChangeAdapter<R> |
Adpater class for the
ChangeSwitch interface. |
| ChangeCopier | |
| FieldChange<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a field changes. |
| ListFieldAdd<T,E> |
Notification object that gets passed to
@OnChange -annotated methods
when an element is added to a list field. |
| ListFieldChange<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a list field changes. |
| ListFieldClear<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a list field is cleared. |
| ListFieldRemove<T,E> |
Notification object that gets passed to
@OnChange -annotated methods
when an element is removed from a list field. |
| ListFieldReplace<T,E> |
Notification object that gets passed to
@OnChange -annotated methods
when an element is replaced in a list field. |
| MapFieldAdd<T,K,V> |
Notification object that gets passed to
@OnChange -annotated methods
when a new key/value pair is added to a map field. |
| MapFieldChange<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a map field changes. |
| MapFieldClear<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a map field is cleared. |
| MapFieldRemove<T,K,V> |
Notification object that gets passed to
@OnChange -annotated methods
when a key/value pair is removed from a map field. |
| MapFieldReplace<T,K,V> |
Notification object that gets passed to
@OnChange -annotated methods
when the value in a key/value pair is replaced with a new value. |
| ObjectCreate<T> |
Change notification that indicates a new object has been created.
|
| ObjectDelete<T> |
Change notification that indicates an object has been deleted.
|
| SetFieldAdd<T,E> |
Notification object that gets passed to
@OnChange -annotated methods
when an element is added to a set field. |
| SetFieldChange<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a set field changes. |
| SetFieldClear<T> |
Notification object that gets passed to
@OnChange -annotated methods
when a set field is cleared. |
| SetFieldRemove<T,E> |
Notification object that gets passed to
@OnChange -annotated methods
when an element is removed from a set field. |
| SimpleFieldChange<T,V> |
Notification object that gets passed to
@OnChange -annotated methods
when a simple field changes. |
@OnChange
-annotated methods.Copyright © 2020. All rights reserved.


Performance reports present delivered units and spend by campaign, placement, creative, delivery period, site, and inventory. The primary goal of these reports is to indicate whether the campaign's creatives are being successfully delivered during the campaigns complete flight. Multiple measures are provided as lenses into this how delivery unfolds for a given campaign, on a raw and percentage basis. Some of the measures are as follows:
Please note, all the reports have data available from 1/1/2015 to the prior day except for Moat whose data is available only from 5/1/2016.
CCR uses the following data sources:
Campaign Management Tool: Prisma
Primary Ad Servers: DFA & Sizmek
Campaign Verification: DoubleVerify & Moat
Due to the varying level of granularity of the reports, CCR provides these reports in four categories:
We provide summary reports for a high-level view of how each client's trafficking is performing by campaign, site and creative. Because CCR's data can be very dense at its most granular level, these reports provide superior performance when seeking to access it.
These reports include:
This category of reports provides campaign performance details on varying levels of delivery periods, namely, Monthly, Weekly and Daily.
This category of reports provides campaign performance details on varying levels granularity, namely, Creative and Placement.
This category of reports provides campaign pacing details on the most granular daily level.
This section covers some important information you must know about the downloaded reports.
File Format
All report files downloaded from the CCR website are Excel Files. When the user opens the files for the first time, they will need to click on the “Enable Content” button that appears on top of the file.
Note: Make sure you have Excel 2013 to use these reports. Some functionality may not work if you have a lower version of Excel.
Note: On clicking the “Enable Content” button, the file will automatically refresh to display the client data the user has access to. For this automatic refresh to take place, make sure you’re on GroupM network or VPN. Please allow a moment for the report to fetch all of your data.
Note: Make sure you have approved access to the data.
“Refresh Data” Button
The “Refresh Data” button helps you to refresh the reports to the latest available data. Clicking on this button will not reset your filters. The data is processed on a daily basis, and the latest data available at any time is 48 hours prior to the current date at launch. Overtime, we will aim to reduce this to a 24 hour window.
“Clear Filters” Button
The “Clear Filters” button resets all selected filters.
Both Pacing and Performance Summary reports have the same filter parameters. Details of these parameters are given below:
Both Pacing and Performance Detailed reports have the same filter parameters. Details of these parameters are given below:
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Creative | The creative name |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Delivery Month | Month of the delivery within the campaign flight date. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear. |
| Delivery Month | Month of the delivery within the campaign flight date. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Delivery Week | Week of the delivery within the campaign flight date. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear |
| Delivery Week | Week of the delivery within the campaign flight date. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Date | Date of the delivery within the campaign flight date. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear |
| Date | Date of the delivery within the campaign flight date. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Creative | The creative name |
| Cost Method | Cost method that determines how ads in the placement are priced. For example, CPC. |
| Unit Dimension | The size of the placement. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Targeting Type 1 | Behavioral, re-targeting, contextual, demographics, etc. |
| Targeting Type 2 | Behavioral, re-targeting, contextual, demographics, etc. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear |
| Placement | The placement name |
| Cost Method | Cost method that determines how ads in the placement are priced. For example, CPC. |
| Unit Dimension | The size of the placement. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Targeting Type 1 | Behavioral, re-targeting, contextual, demographics, etc. |
| Targeting Type 2 | Behavioral, re-targeting, contextual, demographics, etc. |
| Source Actual Impressions | The actual source of the delivered units. This could be the third party ad server or delivery data coming in from Prisma. The selection of the source is dependent on the cost method. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |
| Dimension Name | Description |
| Client | Client name |
| Product | Product name |
| Campaign Name | The Campaign Name |
| Campaign Start Date | The campaign start date |
| Campaign End Date | The campaign end date |
| Supplier Name | Name of the supplier as setup in Prisma. |
| Site Name | Name of the website where the placement will appear |
| Placement | The placement name |
| Cost Method | Cost method that determines how ads in the placement are priced. For example, CPC. |
| Unit Dimension | The size of the placement. |
| Inventory Type | Type of digital Inventory (platform, Format, FEP) e.g. Console FEP, Mobile App |
| Targeting Type 1 | Behavioral, re-targeting, contextual, demographics, etc. |
| Targeting Type 2 | Behavioral, re-targeting, contextual, demographics, etc. |
| Source Actual Impressions | The actual source of the delivered units. This could be the third party ad server or delivery data coming in from Prisma. The selection of the source is dependent on the cost method. |
| Date | Date of the delivery within the campaign flight date. |
| Metric Name | Description |
| Planned Cost | Total planned spend for the campaign. |
Actual Capped Cost |
Capping methods: Date Capped: Cost is "date capped", meaning that no spend is reported outside of planned flight dates. Cost Capped: This occurs at the package and flight level. Which means:
Because capping occurs at a package level, which may add complexity at lower or higher levels of aggregation, the most reliable way to monitor pacing is via the running sum reports. |
| Actual Uncapped Cost | Total actual spend reported for the campaign. |
| Planned Impressions |
Number of impressions the campaign is scheduled to achieve. Note: Planned Impressions may not always be established in Prisma by the media planning team, so it's possible to see delivered impressions where no impressions are planned. |
| Actual Impressions | Number of impressions delivered for the campaign. This value is always uncapped. |
| Payable Impressions | The number of impressions that are considered payable as per the GroupM viewability guidelines. They are the human viewable impression counts, include the scaling factor for non-measured, and accommodates the GroupM rules for Large Ad Units and Multi-Ad Units. |
| Measurable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point. These are Fraud free impressions where measurement can be attempted. |
| Viewable Impressions | The number of impressions where it was possible to determine whether the ad surface was 100% on-screen and were determined to be delivered to a human end point |
| % Measurable | [Measurable Impressions]/ ([Measurable Impressions] + [NonMeasuredImpressions]) |
| % Viewable | [Viewable Impressions] / [Measurable Impressions] |
| CPM | Cost-per-thousand impressions, so you pay for each set of a thousand views of your ad. [(actual capped cost * 1000) / impressions delivered] |
| Clicks | The total number of clicks made on an ad. |
| CTR | The percentage of impressions that result in users clicking an ad. [clicks / impressions delivered] |
| Clicks Per 1000 Imp | Clicks per thousand impressions. [clicks / (impressions delivered / 1000)] |
| CPC | The media cost for each unit of click recorded. [actual capped cost / clicks] |
| CPA | For each action, the media cost per user activity (conversion). [actual capped cost/ conversions or actions] |
| Video Completions |
The number of impressions for which an ad clip played to completion. An event is logged once per view. If the user restarts the clip, it's
not counted again.
For example, if the user plays a 30-second clip for a full 30 seconds, the event is logged. If the user replays the clip for 30 seconds, the event isn't logged again. If, however, the user plays 20 seconds of the clip, then stops and exits the clip, no completion event is logged. Additionally, a completion will be logged even if the user skips some of the video, as long as the endpoint is played. |
| VCR | The rate of video completions to video starts. [video completions / video starts] |
| Video Expansions | Number of video expansions. |
| Expansion Rate | The total number of video expansions out of served video starts. [video expansions / video starts] |
| Interactions | The total number of custom and standard events that are triggered when a user interacts with a video. |
| Interaction Rate | The total number of interactions out of the total number of served video starts. [interactions / video starts] |
| Interaction Time | The total amount of time, in seconds, that users interacted with a video. |
| Value Added | [actual uncapped cost - actual capped cost] |


Keep A TODO LIST: (There is always lots of stuff TODO, so just do it ;)
Translations: [ES]
Lazy? copy this file ($ wget -O TODO.txt keepatodo.com/TODO.txt )
Now in org mode!
Aim 1 hypothesis: Older adults will be classified into well-defined cognitive
status categories after review and categorization using a combination of
neuropsychological tests scores and CDR rating.
TODO: [A](senrabc@gmail.com)20170509 @task Convert the truth table into a CSV
that can be parsed and conveted into an ASCII table. Do this in VIM
TODO: [A](senrabc@gmail.com)20170510 @task Document that the max for a CDR sum
of boxes score can go as high as 18. This needs to be reflected in Truth Table
ref: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3409562/
TODO: [A](senrabc@gmail.com)20170501 @story In the grant we said we would turn
DxSter into the enhanced Algorithmic Diagnosis (eAlgDx). The new required
inputs woudl be CDR sum of boxes for the NPDX a map is needed to map nacc
UDS values to the ALgDx. A truth table was created in the grant for this.
TODO: [A](senrabc@gmail.com)20170501 finsh turning truth table into ascii table
working truthc table here:
*******************************************************************************
Why?
*******************************************************************************
The longer a code base exists the more likely it is that all external artifacts
associated with it will disappear. I can't tell you how many wiki articles I've
authored or edited over the years only to see them somehow get relegated and
lost since the were not with the code. It gets to be disheartening. So a
radical idea occurred to me. Why not just go back to keeping artifacts with the
code.  I'm talking about folks who may be in the
terminal/vim/emacs all day long anyway going back to a tried and true method of
tracking things that need to get done. Your mileage may very.
*******************************************************************************
Advantage for Humans
*******************************************************************************
Advantages, here are a few for using a text based TODO:
1. Your TODO items will get versioned right along with your code.
2. Your TODO list will always be human readable, ala Unix Philosophy.
3. Your text file will pretty much always be cross platform and future
proof ;)
4. I edited this with VIM over an ssh session. No GUI needed. Fast and
quick.
*******************************************************************************
Comments:
*******************************************************************************
Comments or suggestions welcome. Email me at<EMAIL_ADDRESS>fork me and make a pull request. https://github.com/senrabc/keepatodo.com


Roboticute is a small creature from Robot Planet. Usually he descovers space on his own spaceship. Now he just landed on Mushroom Planet. He received an SOS message from Princesses on that planet months ago. His trip was very long and energy tank is empty. Roboticute knows how to convert mushrooms into the energy. Help him to restore energy level and pass his mission.
←
↑
→
↓
P
Roboticute: Use keyboard's arrows UP, DOWN, LEFT, RIGHT to move Roboticute.
Use key P or button Pause Game to pause or resume game.
Mushrooms: There are two types of mushrooms at the Planet: Boroviks and Amanitas. They are growing and (if nobody picks it up) dying. Roboticute can pick up mushrooms to raise an energy level. Borovik will increase green energy, Amanita – red energy. Roboticute uses 1 red and 1 green energy unit periodically.
Frogs: Collision with any frog will convert it to Princess (if red energy level more than 0). Be careful – Princesses are very beautiful and slowly increase level of green energy , but they consume a lot of red energy. If number of Princesses more than 4 – Roboticute begin to use one more green energy unit (or even two units). You can consider red energy as money, green energy as food. No money – no Princesses. They will leave you when red energy level becomes zero.


http://www.speakers-podium.com/susangranger.
Susan Granger's review of "DOUBLE JEOPARDY" (Paramount Pictures)
In this action/revenge movie, a clever woman goes after her conniving husband after he frames her for his supposed murder.  While serving her sentence at a Washington State Prison, she discovers that her spouse is, in fact, living with another woman and raising their son. In addition, she's told by another inmate that she can't be tried twice for the same crime so, when she gets released, she figures: Why not really murder the two-timing rat? The vigilance of her parole officer, played by Tommy Lee Jones, is her only obstacle. Directed by Bruce Beresford, strong and slender Ashley Judd seems perfectly cast, yet she was not the first choice for this plum part. Jodie Foster was supposed to do it until pregnancy forced her to drop out. Tommy Lee Jones is stalwart, as always, doing the relentless law enforcement officer gig which he perfected during "The Fugitive," but Bruce Greenwood's husband part is just too slippery and sleazy. But superficiality is the keynote of the slick, plot-heavy screenplay by David Weisberg and Douglas S. Cook. As for the legal question about whether Judd's character truly has a legal license to kill, the answer is "no." Under the principle of double jeopardy, a person cannot be tried twice for the same crime. But, if the crime was really never committed, then the concept is invalid. On the Granger Movie Gauge of 1 to 10, "Double Jeopardy" is an angry, violent 4. It's an implausible, illogical but mildly intriguing thriller.
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


| Package | Description |
|---|---|
| edu.cmu.sphinx.linguist |
Provides a set of interfaces and classes that are used to define the
search graph used by the decoder.
|
| edu.cmu.sphinx.linguist.allphone | |
| edu.cmu.sphinx.linguist.flat |
Provides an implementation of the
Linguist that
statically represents the search space as a flat graph, where each
word in the vocabulary has its own branch. |
| edu.cmu.sphinx.linguist.language.classes | |
| edu.cmu.sphinx.linguist.language.ngram |
Provides classes and interfaces that represent a stochastic language model
|
| edu.cmu.sphinx.linguist.language.ngram.large |
Provides an implementation of the LanguageModel interface.
|
| Modifier and Type | Field and Description |
|---|---|
static WordSequence |
WordSequence.EMPTY
an empty word sequence, that is, it has no words.
|
| Modifier and Type | Field and Description |
|---|---|
static Comparator<WordSequence> |
WordSequence.OLDEST_COMPARATOR
Comparator that compares two sequences by their oldest part.
|
| Modifier and Type | Method and Description |
|---|---|
WordSequence |
WordSequence.addWord(Word word,
int maxSize)
Returns a new word sequence with the given word added to the sequence
|
static WordSequence |
WordSequence.asWordSequence(Dictionary dictionary,
String... words) |
WordSequence |
WordSequence.getNewest()
Returns the newest words in the sequence (the old word is omitted)
|
WordSequence |
WordSequence.getOldest()
Returns the oldest words in the sequence (the newest word is omitted)
|
WordSequence |
WordSequence.getSubSequence(int startIndex,
int stopIndex) |
WordSequence |
SearchState.getWordHistory()
Gets the word history for this state
|
WordSequence |
WordSequence.trim(int maxSize)
Returns a word sequence that is no longer than the given size, that is
filled in with the newest words from this sequence
|
| Modifier and Type | Method and Description |
|---|---|
int |
WordSequence.compareTo(WordSequence other) |
| Modifier and Type | Method and Description |
|---|---|
WordSequence |
PhoneNonEmittingSearchState.getWordHistory() |
WordSequence |
PhoneHmmSearchState.getWordHistory() |
| Modifier and Type | Method and Description |
|---|---|
WordSequence |
SentenceHMMState.getWordHistory()
Gets the word history for this state.
|
| Modifier and Type | Method and Description |
|---|---|
float |
ClassBasedLanguageModel.getProbability(WordSequence wordSequence)
Actual implementation of the class-based LM: P=P(W|C1)*P(C1|C2,C3..)
|
float |
ClassBasedLanguageModel.getSmear(WordSequence wordSequence)
Gets the smear term for the given wordSequence
|
| Modifier and Type | Method and Description |
|---|---|
LinkedList<WordSequence> |
SimpleNGramModel.getNGrams()
Returns a list of all the word sequences in the language model This
method is used to create Finite State Transducers of the language model.
|
| Modifier and Type | Method and Description |
|---|---|
float |
SimpleNGramModel.getBackoff(WordSequence wordSequence)
Returns the backoff probability for the give sequence of words
|
float |
SimpleNGramModel.getProbability(WordSequence wordSequence)
Gets the ngram probability of the word sequence represented by the word
list
|
float |
NetworkLanguageModel.getProbability(WordSequence wordSequence) |
float |
LanguageModel.getProbability(WordSequence wordSequence)
Gets the n-gram probability of the word sequence represented by the word
list
|
float |
KeywordOptimizerModel.getProbability(WordSequence wordSequence)
Gets the ngram probability of the word sequence represented by the word
list
|
float |
InterpolatedLanguageModel.getProbability(WordSequence wordSequence)
Calculates probability p = w[1]*p[1] + w[2]*p[2] + ...
|
float |
DynamicTrigramModel.getProbability(WordSequence wordSequence) |
float |
SimpleNGramModel.getSmear(WordSequence wordSequence)
Gets the smear term for the given wordSequence
|
float |
NetworkLanguageModel.getSmear(WordSequence wordSequence) |
float |
LanguageModel.getSmear(WordSequence wordSequence)
Gets the smear term for the given wordSequence.
|
float |
KeywordOptimizerModel.getSmear(WordSequence wordSequence)
Gets the smear term for the given wordSequence
|
float |
InterpolatedLanguageModel.getSmear(WordSequence wordSequence) |
float |
DynamicTrigramModel.getSmear(WordSequence wordSequence) |
| Modifier and Type | Method and Description |
|---|---|
float |
LargeNGramModel.getProbability(WordSequence wordSequence)
Gets the ngram probability of the word sequence represented by the word
list
|
float |
KeywordOptimizerLargeNGramModel.getProbability(WordSequence wordSequence)
Gets the ngram probability of the word sequence represented by the word list
|
float |
LargeNGramModel.getSmear(WordSequence wordSequence) |
float |
LargeNGramModel.getSmearOld(WordSequence wordSequence)
Gets the smear term for the given wordSequence
|
Copyright © 2017. All rights reserved.


Add Task
Task
Description
Tag
Due Date:
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Submit


PostEvent()
Syntax
PostEvent(Event [, Window, Object [, Type [, Data]]])Description
Posts an event at the end of the internal event queue.
Parameters
Event The event to post. For a list of PureBasic event, see WindowEvent(). When using custom event, the first value must be at least #PB_Event_FirstCustomValue, to not clash with internal events. Window (optional) The window number associated with the event. When using a custom event, it can be any integer number. This value can be retrieved with EventWindow(). Object (optional) The object number associated with the event. It can be for example a gadget or menu number. When using a custom event, it can be any positive integer number (zero included). This value can be retrieved with EventGadget(). Type (optional) The type associated with the event. When using custom event, the first value must be at least #PB_EventType_FirstCustomValue, to not clash with internal values. This value can be retrieved with EventType(). Data (optional) A data associated with the event. It is only valid when using a custom event and can be any integer number. This value can be retrieved with EventData().
Return value
None.
Remarks
This command can be very useful to communicate between threads and the main event loop. For example, a thread can send a custom event when it has finished its processing (with an associated data), so the main loop will get it and further processing can be done.; All our custom events Enumeration #PB_Event_FirstCustomValue #EventBeginProcessing #EventProcessingFinished EndEnumeration Procedure Thread(Value) PostEvent(#EventBeginProcessing) Delay(3000) PostEvent(#EventProcessingFinished) EndProcedure OpenWindow(0, 200, 200, 100, 100, "PostEvent") CreateThread(@Thread(), 0) Repeat Event = WaitWindowEvent() Select Event Case #EventBeginProcessing Debug "Thread begin processing " Case #EventProcessingFinished Debug "Thread processing finished" EndSelect Until Event = #PB_Event_CloseWindow
See Also
WindowEvent(), EventWindow(), EventGadget(), EventType(), EventData()
Supported OS
All


A vertical list scroller for AngularJS. luisfarzati.github.io/angulartics
Include the script and the stylesheet.
<link rel="stylesheet" href="ngTotemTicker.css">
<script src="ngTotemTicker.js"></script>
Insert the directive in your page.
<ngTotemTicker items="{{myTickerItems}}"></ngTotemTicker>
ngTotemTicker is freely distributable under the terms of the MIT license.
Copyright (c) 2014 Ole Børn Michelsen
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.