EventMessage extends Message
EventMessage class
Tags
Table of Contents
- $_propDict : array<string|int, mixed>
- The array of properties available to the model
- __construct() : mixed
- Construct a new Entity
- getAttachments() : array<string|int, mixed>|null
- Gets the attachments The fileAttachment and itemAttachment attachments for the message.
- getBccRecipients() : array<string|int, mixed>|null
- Gets the bccRecipients The Bcc: recipients for the message.
- getBody() : ItemBody|null
- Gets the body The body of the message. It can be in HTML or text format. Find out about safe HTML in a message body.
- getBodyPreview() : string|null
- Gets the bodyPreview The first 255 characters of the message body. It is in text format.
- getCategories() : string|null
- Gets the categories The categories associated with the item
- getCcRecipients() : array<string|int, mixed>|null
- Gets the ccRecipients The Cc: recipients for the message.
- getChangeKey() : string|null
- Gets the changeKey Identifies the version of the item. Every time the item is changed, changeKey changes as well. This allows Exchange to apply changes to the correct version of the object. Read-only.
- getConversationId() : string|null
- Gets the conversationId The ID of the conversation the email belongs to.
- getConversationIndex() : Stream|null
- Gets the conversationIndex Indicates the position of the message within the conversation.
- getCreatedDateTime() : DateTime|null
- Gets the createdDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
- getEndDateTime() : DateTimeTimeZone|null
- Gets the endDateTime The end time of the requested meeting.
- getEvent() : Event|null
- Gets the event The event associated with the event message. The assumption for attendees or room resources is that the Calendar Attendant is set to automatically update the calendar with an event when meeting request event messages arrive. Navigation property. Read-only.
- getExtensions() : array<string|int, mixed>|null
- Gets the extensions The collection of open extensions defined for the message. Nullable.
- getFlag() : FollowupFlag|null
- Gets the flag The flag value that indicates the status, start date, due date, or completion date for the message.
- getFrom() : Recipient|null
- Gets the from The owner of the mailbox from which the message is sent. In most cases, this value is the same as the sender property, except for sharing or delegation scenarios. The value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
- getHasAttachments() : bool|null
- Gets the hasAttachments Indicates whether the message has attachments. This property doesn't include inline attachments, so if a message contains only inline attachments, this property is false. To verify the existence of inline attachments, parse the body property to look for a src attribute, such as .
- getId() : string|null
- Gets the id Read-only.
- getImportance() : Importance|null
- Gets the importance The importance of the message. The possible values are: low, normal, and high.
- getInferenceClassification() : InferenceClassificationType|null
- Gets the inferenceClassification The classification of the message for the user, based on inferred relevance or importance, or on an explicit override. The possible values are: focused or other.
- getInternetMessageHeaders() : array<string|int, mixed>|null
- Gets the internetMessageHeaders A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message. Returned only on applying a $select query option. Read-only.
- getInternetMessageId() : string|null
- Gets the internetMessageId The message ID in the format specified by RFC2822.
- getIsAllDay() : bool|null
- Gets the isAllDay
- getIsDelegated() : bool|null
- Gets the isDelegated True if this meeting request is accessible to a delegate, false otherwise. Default is false.
- getIsDeliveryReceiptRequested() : bool|null
- Gets the isDeliveryReceiptRequested Indicates whether a read receipt is requested for the message.
- getIsDraft() : bool|null
- Gets the isDraft Indicates whether the message is a draft. A message is a draft if it hasn't been sent yet.
- getIsOutOfDate() : bool|null
- Gets the isOutOfDate
- getIsRead() : bool|null
- Gets the isRead Indicates whether the message has been read.
- getIsReadReceiptRequested() : bool|null
- Gets the isReadReceiptRequested Indicates whether a read receipt is requested for the message.
- getLastModifiedDateTime() : DateTime|null
- Gets the lastModifiedDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
- getLocation() : Location|null
- Gets the location
- getMeetingMessageType() : MeetingMessageType|null
- Gets the meetingMessageType The type of event message: none, meetingRequest, meetingCancelled, meetingAccepted, meetingTenativelyAccepted, meetingDeclined.
- getMultiValueExtendedProperties() : array<string|int, mixed>|null
- Gets the multiValueExtendedProperties The collection of multi-value extended properties defined for the message. Nullable.
- getODataType() : string|null
- Gets the ODataType
- getParentFolderId() : string|null
- Gets the parentFolderId The unique identifier for the message's parent mailFolder.
- getProperties() : array<string|int, mixed>
- Gets the property dictionary of the Entity
- getReceivedDateTime() : DateTime|null
- Gets the receivedDateTime The date and time the message was received. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
- getRecurrence() : PatternedRecurrence|null
- Gets the recurrence
- getReplyTo() : array<string|int, mixed>|null
- Gets the replyTo The email addresses to use when replying.
- getSender() : Recipient|null
- Gets the sender The account that is actually used to generate the message. In most cases, this value is the same as the from property. You can set this property to a different value when sending a message from a shared mailbox, for a shared calendar, or as a delegate. In any case, the value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
- getSentDateTime() : DateTime|null
- Gets the sentDateTime The date and time the message was sent. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
- getSingleValueExtendedProperties() : array<string|int, mixed>|null
- Gets the singleValueExtendedProperties The collection of single-value extended properties defined for the message. Nullable.
- getStartDateTime() : DateTimeTimeZone|null
- Gets the startDateTime
- getSubject() : string|null
- Gets the subject The subject of the message.
- getToRecipients() : array<string|int, mixed>|null
- Gets the toRecipients The To: recipients for the message.
- getType() : EventType|null
- Gets the type
- getUniqueBody() : ItemBody|null
- Gets the uniqueBody The part of the body of the message that is unique to the current message. uniqueBody is not returned by default but can be retrieved for a given message by use of the ?$select=uniqueBody query. It can be in HTML or text format.
- getWebLink() : string|null
- Gets the webLink The URL to open the message in Outlook on the web.You can append an ispopout argument to the end of the URL to change how the message is displayed. If ispopout is not present or if it is set to 1, then the message is shown in a popout window. If ispopout is set to 0, then the browser will show the message in the Outlook on the web review pane.The message will open in the browser if you are logged in to your mailbox via Outlook on the web. You will be prompted to login if you are not already logged in with the browser.This URL cannot be accessed from within an iFrame.
- jsonSerialize() : array<string|int, mixed>
- Serializes the object by property array Manually serialize DateTime into RFC3339 format
- setAttachments() : Message
- Sets the attachments The fileAttachment and itemAttachment attachments for the message.
- setBccRecipients() : Message
- Sets the bccRecipients The Bcc: recipients for the message.
- setBody() : Message
- Sets the body The body of the message. It can be in HTML or text format. Find out about safe HTML in a message body.
- setBodyPreview() : Message
- Sets the bodyPreview The first 255 characters of the message body. It is in text format.
- setCategories() : OutlookItem
- Sets the categories The categories associated with the item
- setCcRecipients() : Message
- Sets the ccRecipients The Cc: recipients for the message.
- setChangeKey() : OutlookItem
- Sets the changeKey Identifies the version of the item. Every time the item is changed, changeKey changes as well. This allows Exchange to apply changes to the correct version of the object. Read-only.
- setConversationId() : Message
- Sets the conversationId The ID of the conversation the email belongs to.
- setConversationIndex() : Message
- Sets the conversationIndex Indicates the position of the message within the conversation.
- setCreatedDateTime() : OutlookItem
- Sets the createdDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
- setEndDateTime() : EventMessage
- Sets the endDateTime The end time of the requested meeting.
- setEvent() : EventMessage
- Sets the event The event associated with the event message. The assumption for attendees or room resources is that the Calendar Attendant is set to automatically update the calendar with an event when meeting request event messages arrive. Navigation property. Read-only.
- setExtensions() : Message
- Sets the extensions The collection of open extensions defined for the message. Nullable.
- setFlag() : Message
- Sets the flag The flag value that indicates the status, start date, due date, or completion date for the message.
- setFrom() : Message
- Sets the from The owner of the mailbox from which the message is sent. In most cases, this value is the same as the sender property, except for sharing or delegation scenarios. The value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
- setHasAttachments() : Message
- Sets the hasAttachments Indicates whether the message has attachments. This property doesn't include inline attachments, so if a message contains only inline attachments, this property is false. To verify the existence of inline attachments, parse the body property to look for a src attribute, such as .
- setId() : Entity
- Sets the id Read-only.
- setImportance() : Message
- Sets the importance The importance of the message. The possible values are: low, normal, and high.
- setInferenceClassification() : Message
- Sets the inferenceClassification The classification of the message for the user, based on inferred relevance or importance, or on an explicit override. The possible values are: focused or other.
- setInternetMessageHeaders() : Message
- Sets the internetMessageHeaders A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message. Returned only on applying a $select query option. Read-only.
- setInternetMessageId() : Message
- Sets the internetMessageId The message ID in the format specified by RFC2822.
- setIsAllDay() : EventMessage
- Sets the isAllDay
- setIsDelegated() : EventMessage
- Sets the isDelegated True if this meeting request is accessible to a delegate, false otherwise. Default is false.
- setIsDeliveryReceiptRequested() : Message
- Sets the isDeliveryReceiptRequested Indicates whether a read receipt is requested for the message.
- setIsDraft() : Message
- Sets the isDraft Indicates whether the message is a draft. A message is a draft if it hasn't been sent yet.
- setIsOutOfDate() : EventMessage
- Sets the isOutOfDate
- setIsRead() : Message
- Sets the isRead Indicates whether the message has been read.
- setIsReadReceiptRequested() : Message
- Sets the isReadReceiptRequested Indicates whether a read receipt is requested for the message.
- setLastModifiedDateTime() : OutlookItem
- Sets the lastModifiedDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
- setLocation() : EventMessage
- Sets the location
- setMeetingMessageType() : EventMessage
- Sets the meetingMessageType The type of event message: none, meetingRequest, meetingCancelled, meetingAccepted, meetingTenativelyAccepted, meetingDeclined.
- setMultiValueExtendedProperties() : Message
- Sets the multiValueExtendedProperties The collection of multi-value extended properties defined for the message. Nullable.
- setODataType() : Entity
- Sets the ODataType
- setParentFolderId() : Message
- Sets the parentFolderId The unique identifier for the message's parent mailFolder.
- setReceivedDateTime() : Message
- Sets the receivedDateTime The date and time the message was received. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
- setRecurrence() : EventMessage
- Sets the recurrence
- setReplyTo() : Message
- Sets the replyTo The email addresses to use when replying.
- setSender() : Message
- Sets the sender The account that is actually used to generate the message. In most cases, this value is the same as the from property. You can set this property to a different value when sending a message from a shared mailbox, for a shared calendar, or as a delegate. In any case, the value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
- setSentDateTime() : Message
- Sets the sentDateTime The date and time the message was sent. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
- setSingleValueExtendedProperties() : Message
- Sets the singleValueExtendedProperties The collection of single-value extended properties defined for the message. Nullable.
- setStartDateTime() : EventMessage
- Sets the startDateTime
- setSubject() : Message
- Sets the subject The subject of the message.
- setToRecipients() : Message
- Sets the toRecipients The To: recipients for the message.
- setType() : EventMessage
- Sets the type
- setUniqueBody() : Message
- Sets the uniqueBody The part of the body of the message that is unique to the current message. uniqueBody is not returned by default but can be retrieved for a given message by use of the ?$select=uniqueBody query. It can be in HTML or text format.
- setWebLink() : Message
- Sets the webLink The URL to open the message in Outlook on the web.You can append an ispopout argument to the end of the URL to change how the message is displayed. If ispopout is not present or if it is set to 1, then the message is shown in a popout window. If ispopout is set to 0, then the browser will show the message in the Outlook on the web review pane.The message will open in the browser if you are logged in to your mailbox via Outlook on the web. You will be prompted to login if you are not already logged in with the browser.This URL cannot be accessed from within an iFrame.
Properties
$_propDict
The array of properties available to the model
protected
array<string|int, mixed>
$_propDict
Methods
__construct()
Construct a new Entity
public
__construct([array<string|int, mixed> $propDict = array() ]) : mixed
Parameters
- $propDict : array<string|int, mixed> = array()
-
A list of properties to set
Return values
mixed —getAttachments()
Gets the attachments The fileAttachment and itemAttachment attachments for the message.
public
getAttachments() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The attachments
getBccRecipients()
Gets the bccRecipients The Bcc: recipients for the message.
public
getBccRecipients() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The bccRecipients
getBody()
Gets the body The body of the message. It can be in HTML or text format. Find out about safe HTML in a message body.
public
getBody() : ItemBody|null
Return values
ItemBody|null —The body
getBodyPreview()
Gets the bodyPreview The first 255 characters of the message body. It is in text format.
public
getBodyPreview() : string|null
Return values
string|null —The bodyPreview
getCategories()
Gets the categories The categories associated with the item
public
getCategories() : string|null
Return values
string|null —The categories
getCcRecipients()
Gets the ccRecipients The Cc: recipients for the message.
public
getCcRecipients() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The ccRecipients
getChangeKey()
Gets the changeKey Identifies the version of the item. Every time the item is changed, changeKey changes as well. This allows Exchange to apply changes to the correct version of the object. Read-only.
public
getChangeKey() : string|null
Return values
string|null —The changeKey
getConversationId()
Gets the conversationId The ID of the conversation the email belongs to.
public
getConversationId() : string|null
Return values
string|null —The conversationId
getConversationIndex()
Gets the conversationIndex Indicates the position of the message within the conversation.
public
getConversationIndex() : Stream|null
Return values
Stream|null —The conversationIndex
getCreatedDateTime()
Gets the createdDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
public
getCreatedDateTime() : DateTime|null
Return values
DateTime|null —The createdDateTime
getEndDateTime()
Gets the endDateTime The end time of the requested meeting.
public
getEndDateTime() : DateTimeTimeZone|null
Return values
DateTimeTimeZone|null —The endDateTime
getEvent()
Gets the event The event associated with the event message. The assumption for attendees or room resources is that the Calendar Attendant is set to automatically update the calendar with an event when meeting request event messages arrive. Navigation property. Read-only.
public
getEvent() : Event|null
Return values
Event|null —The event
getExtensions()
Gets the extensions The collection of open extensions defined for the message. Nullable.
public
getExtensions() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The extensions
getFlag()
Gets the flag The flag value that indicates the status, start date, due date, or completion date for the message.
public
getFlag() : FollowupFlag|null
Return values
FollowupFlag|null —The flag
getFrom()
Gets the from The owner of the mailbox from which the message is sent. In most cases, this value is the same as the sender property, except for sharing or delegation scenarios. The value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
public
getFrom() : Recipient|null
Return values
Recipient|null —The from
getHasAttachments()
Gets the hasAttachments Indicates whether the message has attachments. This property doesn't include inline attachments, so if a message contains only inline attachments, this property is false. To verify the existence of inline attachments, parse the body property to look for a src attribute, such as .
public
getHasAttachments() : bool|null
Return values
bool|null —The hasAttachments
getId()
Gets the id Read-only.
public
getId() : string|null
Return values
string|null —The id
getImportance()
Gets the importance The importance of the message. The possible values are: low, normal, and high.
public
getImportance() : Importance|null
Return values
Importance|null —The importance
getInferenceClassification()
Gets the inferenceClassification The classification of the message for the user, based on inferred relevance or importance, or on an explicit override. The possible values are: focused or other.
public
getInferenceClassification() : InferenceClassificationType|null
Return values
InferenceClassificationType|null —The inferenceClassification
getInternetMessageHeaders()
Gets the internetMessageHeaders A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message. Returned only on applying a $select query option. Read-only.
public
getInternetMessageHeaders() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The internetMessageHeaders
getInternetMessageId()
Gets the internetMessageId The message ID in the format specified by RFC2822.
public
getInternetMessageId() : string|null
Return values
string|null —The internetMessageId
getIsAllDay()
Gets the isAllDay
public
getIsAllDay() : bool|null
Return values
bool|null —The isAllDay
getIsDelegated()
Gets the isDelegated True if this meeting request is accessible to a delegate, false otherwise. Default is false.
public
getIsDelegated() : bool|null
Return values
bool|null —The isDelegated
getIsDeliveryReceiptRequested()
Gets the isDeliveryReceiptRequested Indicates whether a read receipt is requested for the message.
public
getIsDeliveryReceiptRequested() : bool|null
Return values
bool|null —The isDeliveryReceiptRequested
getIsDraft()
Gets the isDraft Indicates whether the message is a draft. A message is a draft if it hasn't been sent yet.
public
getIsDraft() : bool|null
Return values
bool|null —The isDraft
getIsOutOfDate()
Gets the isOutOfDate
public
getIsOutOfDate() : bool|null
Return values
bool|null —The isOutOfDate
getIsRead()
Gets the isRead Indicates whether the message has been read.
public
getIsRead() : bool|null
Return values
bool|null —The isRead
getIsReadReceiptRequested()
Gets the isReadReceiptRequested Indicates whether a read receipt is requested for the message.
public
getIsReadReceiptRequested() : bool|null
Return values
bool|null —The isReadReceiptRequested
getLastModifiedDateTime()
Gets the lastModifiedDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
public
getLastModifiedDateTime() : DateTime|null
Return values
DateTime|null —The lastModifiedDateTime
getLocation()
Gets the location
public
getLocation() : Location|null
Return values
Location|null —The location
getMeetingMessageType()
Gets the meetingMessageType The type of event message: none, meetingRequest, meetingCancelled, meetingAccepted, meetingTenativelyAccepted, meetingDeclined.
public
getMeetingMessageType() : MeetingMessageType|null
Return values
MeetingMessageType|null —The meetingMessageType
getMultiValueExtendedProperties()
Gets the multiValueExtendedProperties The collection of multi-value extended properties defined for the message. Nullable.
public
getMultiValueExtendedProperties() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The multiValueExtendedProperties
getODataType()
Gets the ODataType
public
getODataType() : string|null
Return values
string|null —The ODataType
getParentFolderId()
Gets the parentFolderId The unique identifier for the message's parent mailFolder.
public
getParentFolderId() : string|null
Return values
string|null —The parentFolderId
getProperties()
Gets the property dictionary of the Entity
public
getProperties() : array<string|int, mixed>
Return values
array<string|int, mixed> —The list of properties
getReceivedDateTime()
Gets the receivedDateTime The date and time the message was received. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
public
getReceivedDateTime() : DateTime|null
Return values
DateTime|null —The receivedDateTime
getRecurrence()
Gets the recurrence
public
getRecurrence() : PatternedRecurrence|null
Return values
PatternedRecurrence|null —The recurrence
getReplyTo()
Gets the replyTo The email addresses to use when replying.
public
getReplyTo() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The replyTo
getSender()
Gets the sender The account that is actually used to generate the message. In most cases, this value is the same as the from property. You can set this property to a different value when sending a message from a shared mailbox, for a shared calendar, or as a delegate. In any case, the value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
public
getSender() : Recipient|null
Return values
Recipient|null —The sender
getSentDateTime()
Gets the sentDateTime The date and time the message was sent. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
public
getSentDateTime() : DateTime|null
Return values
DateTime|null —The sentDateTime
getSingleValueExtendedProperties()
Gets the singleValueExtendedProperties The collection of single-value extended properties defined for the message. Nullable.
public
getSingleValueExtendedProperties() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The singleValueExtendedProperties
getStartDateTime()
Gets the startDateTime
public
getStartDateTime() : DateTimeTimeZone|null
Return values
DateTimeTimeZone|null —The startDateTime
getSubject()
Gets the subject The subject of the message.
public
getSubject() : string|null
Return values
string|null —The subject
getToRecipients()
Gets the toRecipients The To: recipients for the message.
public
getToRecipients() : array<string|int, mixed>|null
Return values
array<string|int, mixed>|null —The toRecipients
getType()
Gets the type
public
getType() : EventType|null
Return values
EventType|null —The type
getUniqueBody()
Gets the uniqueBody The part of the body of the message that is unique to the current message. uniqueBody is not returned by default but can be retrieved for a given message by use of the ?$select=uniqueBody query. It can be in HTML or text format.
public
getUniqueBody() : ItemBody|null
Return values
ItemBody|null —The uniqueBody
getWebLink()
Gets the webLink The URL to open the message in Outlook on the web.You can append an ispopout argument to the end of the URL to change how the message is displayed. If ispopout is not present or if it is set to 1, then the message is shown in a popout window. If ispopout is set to 0, then the browser will show the message in the Outlook on the web review pane.The message will open in the browser if you are logged in to your mailbox via Outlook on the web. You will be prompted to login if you are not already logged in with the browser.This URL cannot be accessed from within an iFrame.
public
getWebLink() : string|null
Return values
string|null —The webLink
jsonSerialize()
Serializes the object by property array Manually serialize DateTime into RFC3339 format
public
jsonSerialize() : array<string|int, mixed>
Return values
array<string|int, mixed> —The list of properties
setAttachments()
Sets the attachments The fileAttachment and itemAttachment attachments for the message.
public
setAttachments(Attachment $val) : Message
Parameters
- $val : Attachment
-
The attachments
Return values
Message —setBccRecipients()
Sets the bccRecipients The Bcc: recipients for the message.
public
setBccRecipients(Recipient $val) : Message
Parameters
- $val : Recipient
-
The bccRecipients
Return values
Message —setBody()
Sets the body The body of the message. It can be in HTML or text format. Find out about safe HTML in a message body.
public
setBody(ItemBody $val) : Message
Parameters
- $val : ItemBody
-
The body
Return values
Message —setBodyPreview()
Sets the bodyPreview The first 255 characters of the message body. It is in text format.
public
setBodyPreview(string $val) : Message
Parameters
- $val : string
-
The bodyPreview
Return values
Message —setCategories()
Sets the categories The categories associated with the item
public
setCategories(string $val) : OutlookItem
Parameters
- $val : string
-
The categories
Return values
OutlookItem —setCcRecipients()
Sets the ccRecipients The Cc: recipients for the message.
public
setCcRecipients(Recipient $val) : Message
Parameters
- $val : Recipient
-
The ccRecipients
Return values
Message —setChangeKey()
Sets the changeKey Identifies the version of the item. Every time the item is changed, changeKey changes as well. This allows Exchange to apply changes to the correct version of the object. Read-only.
public
setChangeKey(string $val) : OutlookItem
Parameters
- $val : string
-
The changeKey
Return values
OutlookItem —setConversationId()
Sets the conversationId The ID of the conversation the email belongs to.
public
setConversationId(string $val) : Message
Parameters
- $val : string
-
The conversationId
Return values
Message —setConversationIndex()
Sets the conversationIndex Indicates the position of the message within the conversation.
public
setConversationIndex(Stream $val) : Message
Parameters
- $val : Stream
-
The conversationIndex
Return values
Message —setCreatedDateTime()
Sets the createdDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
public
setCreatedDateTime(DateTime $val) : OutlookItem
Parameters
- $val : DateTime
-
The createdDateTime
Return values
OutlookItem —setEndDateTime()
Sets the endDateTime The end time of the requested meeting.
public
setEndDateTime(DateTimeTimeZone $val) : EventMessage
Parameters
- $val : DateTimeTimeZone
-
The endDateTime
Return values
EventMessage —setEvent()
Sets the event The event associated with the event message. The assumption for attendees or room resources is that the Calendar Attendant is set to automatically update the calendar with an event when meeting request event messages arrive. Navigation property. Read-only.
public
setEvent(Event $val) : EventMessage
Parameters
- $val : Event
-
The event
Return values
EventMessage —setExtensions()
Sets the extensions The collection of open extensions defined for the message. Nullable.
public
setExtensions(Extension $val) : Message
Parameters
- $val : Extension
-
The extensions
Return values
Message —setFlag()
Sets the flag The flag value that indicates the status, start date, due date, or completion date for the message.
public
setFlag(FollowupFlag $val) : Message
Parameters
- $val : FollowupFlag
-
The flag
Return values
Message —setFrom()
Sets the from The owner of the mailbox from which the message is sent. In most cases, this value is the same as the sender property, except for sharing or delegation scenarios. The value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
public
setFrom(Recipient $val) : Message
Parameters
- $val : Recipient
-
The from
Return values
Message —setHasAttachments()
Sets the hasAttachments Indicates whether the message has attachments. This property doesn't include inline attachments, so if a message contains only inline attachments, this property is false. To verify the existence of inline attachments, parse the body property to look for a src attribute, such as .
public
setHasAttachments(bool $val) : Message
Parameters
- $val : bool
-
The hasAttachments
Return values
Message —setId()
Sets the id Read-only.
public
setId(string $val) : Entity
Parameters
- $val : string
-
The id
Return values
Entity —setImportance()
Sets the importance The importance of the message. The possible values are: low, normal, and high.
public
setImportance(Importance $val) : Message
Parameters
- $val : Importance
-
The importance
Return values
Message —setInferenceClassification()
Sets the inferenceClassification The classification of the message for the user, based on inferred relevance or importance, or on an explicit override. The possible values are: focused or other.
public
setInferenceClassification(InferenceClassificationType $val) : Message
Parameters
- $val : InferenceClassificationType
-
The inferenceClassification
Return values
Message —setInternetMessageHeaders()
Sets the internetMessageHeaders A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message. Returned only on applying a $select query option. Read-only.
public
setInternetMessageHeaders(InternetMessageHeader $val) : Message
Parameters
- $val : InternetMessageHeader
-
The internetMessageHeaders
Return values
Message —setInternetMessageId()
Sets the internetMessageId The message ID in the format specified by RFC2822.
public
setInternetMessageId(string $val) : Message
Parameters
- $val : string
-
The internetMessageId
Return values
Message —setIsAllDay()
Sets the isAllDay
public
setIsAllDay(bool $val) : EventMessage
Parameters
- $val : bool
-
The isAllDay
Return values
EventMessage —setIsDelegated()
Sets the isDelegated True if this meeting request is accessible to a delegate, false otherwise. Default is false.
public
setIsDelegated(bool $val) : EventMessage
Parameters
- $val : bool
-
The isDelegated
Return values
EventMessage —setIsDeliveryReceiptRequested()
Sets the isDeliveryReceiptRequested Indicates whether a read receipt is requested for the message.
public
setIsDeliveryReceiptRequested(bool $val) : Message
Parameters
- $val : bool
-
The isDeliveryReceiptRequested
Return values
Message —setIsDraft()
Sets the isDraft Indicates whether the message is a draft. A message is a draft if it hasn't been sent yet.
public
setIsDraft(bool $val) : Message
Parameters
- $val : bool
-
The isDraft
Return values
Message —setIsOutOfDate()
Sets the isOutOfDate
public
setIsOutOfDate(bool $val) : EventMessage
Parameters
- $val : bool
-
The isOutOfDate
Return values
EventMessage —setIsRead()
Sets the isRead Indicates whether the message has been read.
public
setIsRead(bool $val) : Message
Parameters
- $val : bool
-
The isRead
Return values
Message —setIsReadReceiptRequested()
Sets the isReadReceiptRequested Indicates whether a read receipt is requested for the message.
public
setIsReadReceiptRequested(bool $val) : Message
Parameters
- $val : bool
-
The isReadReceiptRequested
Return values
Message —setLastModifiedDateTime()
Sets the lastModifiedDateTime The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z
public
setLastModifiedDateTime(DateTime $val) : OutlookItem
Parameters
- $val : DateTime
-
The lastModifiedDateTime
Return values
OutlookItem —setLocation()
Sets the location
public
setLocation(Location $val) : EventMessage
Parameters
- $val : Location
-
The location
Return values
EventMessage —setMeetingMessageType()
Sets the meetingMessageType The type of event message: none, meetingRequest, meetingCancelled, meetingAccepted, meetingTenativelyAccepted, meetingDeclined.
public
setMeetingMessageType(MeetingMessageType $val) : EventMessage
Parameters
- $val : MeetingMessageType
-
The meetingMessageType
Return values
EventMessage —setMultiValueExtendedProperties()
Sets the multiValueExtendedProperties The collection of multi-value extended properties defined for the message. Nullable.
public
setMultiValueExtendedProperties(MultiValueLegacyExtendedProperty $val) : Message
Parameters
- $val : MultiValueLegacyExtendedProperty
-
The multiValueExtendedProperties
Return values
Message —setODataType()
Sets the ODataType
public
setODataType(string $val) : Entity
Parameters
- $val : string
-
The ODataType
Return values
Entity —setParentFolderId()
Sets the parentFolderId The unique identifier for the message's parent mailFolder.
public
setParentFolderId(string $val) : Message
Parameters
- $val : string
-
The parentFolderId
Return values
Message —setReceivedDateTime()
Sets the receivedDateTime The date and time the message was received. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
public
setReceivedDateTime(DateTime $val) : Message
Parameters
- $val : DateTime
-
The receivedDateTime
Return values
Message —setRecurrence()
Sets the recurrence
public
setRecurrence(PatternedRecurrence $val) : EventMessage
Parameters
- $val : PatternedRecurrence
-
The recurrence
Return values
EventMessage —setReplyTo()
Sets the replyTo The email addresses to use when replying.
public
setReplyTo(Recipient $val) : Message
Parameters
- $val : Recipient
-
The replyTo
Return values
Message —setSender()
Sets the sender The account that is actually used to generate the message. In most cases, this value is the same as the from property. You can set this property to a different value when sending a message from a shared mailbox, for a shared calendar, or as a delegate. In any case, the value must correspond to the actual mailbox used. Find out more about setting the from and sender properties of a message.
public
setSender(Recipient $val) : Message
Parameters
- $val : Recipient
-
The sender
Return values
Message —setSentDateTime()
Sets the sentDateTime The date and time the message was sent. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z.
public
setSentDateTime(DateTime $val) : Message
Parameters
- $val : DateTime
-
The sentDateTime
Return values
Message —setSingleValueExtendedProperties()
Sets the singleValueExtendedProperties The collection of single-value extended properties defined for the message. Nullable.
public
setSingleValueExtendedProperties(SingleValueLegacyExtendedProperty $val) : Message
Parameters
- $val : SingleValueLegacyExtendedProperty
-
The singleValueExtendedProperties
Return values
Message —setStartDateTime()
Sets the startDateTime
public
setStartDateTime(DateTimeTimeZone $val) : EventMessage
Parameters
- $val : DateTimeTimeZone
-
The startDateTime
Return values
EventMessage —setSubject()
Sets the subject The subject of the message.
public
setSubject(string $val) : Message
Parameters
- $val : string
-
The subject
Return values
Message —setToRecipients()
Sets the toRecipients The To: recipients for the message.
public
setToRecipients(Recipient $val) : Message
Parameters
- $val : Recipient
-
The toRecipients
Return values
Message —setType()
Sets the type
public
setType(EventType $val) : EventMessage
Parameters
- $val : EventType
-
The type
Return values
EventMessage —setUniqueBody()
Sets the uniqueBody The part of the body of the message that is unique to the current message. uniqueBody is not returned by default but can be retrieved for a given message by use of the ?$select=uniqueBody query. It can be in HTML or text format.
public
setUniqueBody(ItemBody $val) : Message
Parameters
- $val : ItemBody
-
The uniqueBody
Return values
Message —setWebLink()
Sets the webLink The URL to open the message in Outlook on the web.You can append an ispopout argument to the end of the URL to change how the message is displayed. If ispopout is not present or if it is set to 1, then the message is shown in a popout window. If ispopout is set to 0, then the browser will show the message in the Outlook on the web review pane.The message will open in the browser if you are logged in to your mailbox via Outlook on the web. You will be prompted to login if you are not already logged in with the browser.This URL cannot be accessed from within an iFrame.
public
setWebLink(string $val) : Message
Parameters
- $val : string
-
The webLink


--- layout: post title: no title date: '2016-06-04T16:29:40-07:00' tags: - design - color - movies - fromtheinternet tumblr_url: http://beekley.xyz/post/145425649451/i-forgot-top-gun-was-beautiful-from ---
I forgot Top Gun was beautiful. From digitalsynopsis.


R-tips
> getwd() # print the current working directory
> ls() # list the objects in the current workspace
> setwd("/home/rocky/workspace/Rworkspace") # set working directory
# view and set options for the session
> help(options) # learn about available options
> options() # view current option settings
> options(digits=3) # number of digits to print on output
# work with your previous commands
> history() # display last 25 commands
> history(max.show=Inf) # display all previous commands
# save your command history
> savehistory(file="myfile") # default is ".Rhistory"
# recall your command history
> loadhistory(file="myfile") # default is ".Rhistory"
# save the workspace to the file .RData in the cwd
> save.image()
# save specific objects to a file
# if you don't specify the path, the cwd is assumed
> save(object list,file="myfile.RData")
# load a workspace into the current session
# if you don't specify the path, the cwd is assumed
> load("myfile.RData")


ARTICLE 9. MISCELLANEOUS PROVISIONS
Note
Article heading reenacted by L 2015, c 77, pt of §1.
§576B-901 Uniformity of application and construction. In applying and construing this uniform act, consideration shall be given to the need to promote uniformity of the law with respect to its subject matter among states that enact it. [L 1997, c 295, pt of §1; am L 2015, c 77, pt of §1]


×
Car
Previous
Next
Add Order
Register
Register
Log In
Log In
Username
Password
model...
transmission...
body...
engine...
driveType...
search
id
sold
car
price
year
user
photo


Reload items (mp3 list)
Reread the list of cards
Terminate the main loop (you will need to restart the machine)


11 Trait Dependent Diversification
The previous chapter used a variety of methods to estimate the rate of diversification in a phylogeny. This is an interesting and contentious field of study which allows us to ask marcoevolutionary questions. In this chapter, we will extend this approach to model the effects of trait evolution on diversification.
11.1 Binary traits: BiSSE
BiSSE stands for Binary State Speciation and Extinction model. In fitting this model, we are looking to see if the rate of diversification is different when lineages are in one state or another. For example, we might hypothesise that aquatic animals diversify more rapidly than terrestrial species.
Let’s start by simulating a tree and binary character using the tree.bisse function in the package diversitree (FitzJohn 2012). We need to specify parameters for the simulation. These parameters are (in order);
- The speciation rate with the trait in state 0: \(\lambda_{0}\)
- The speciation rate with the trait in state 1: \(\lambda_{1}\)
- The extinction rate with the trait in state 0: \(\mu_{0}\)
- The extinction rate with the trait in state 1: \(\mu_{1}\)
- The probability of transitioning from state 0 to 1: \(q_{01}\)
- The probability of transitioning from state 1 to 0: \(q_{10}\)
For this example, we will imagine a scenario in which lineages are twice as likely to speciate with the trait in state 1 than in state 0 (\(\lambda_{1} = 2 \times\lambda_{0}\)). Extinction rates will not be different in either state (\(\mu_{0} = \mu_{1}\)) and the probability of transitioning between states is the same in either direction (\(q_{01} = q_{10}\)).
library(diversitree)
pars <- c(.1,.2,.03,.03,.01,.01)
set.seed(42)
phy <- tree.bisse(pars, max.t = 30, x0 = 0)
states <- phy$tip.state
We can extract the history of the trait’s evolution using history.from.sim.discrete. Note that although this looks like an ancestral state reconstruction, it isn’t. This is the actual history of the trait we have simulated.
Next we use the function make.bisse with the tree and the named vector of states. This creates a likelihood function that we will go on to use in our analysis.
To perform a maximum likelihood search, we will also need to select a starting point. The function starting.point.bisse produces a guess for a starting point based on the character-independent birth-death fit.
lambda0 lambda1 mu0 mu1 q01 q10
0.09380372 0.09380372 0.00000000 0.00000000 0.01876074 0.01876074
Now that we have our likelihood function and our starting point for each parameter, we can start the likelihood search using find.mle. Depending on the size and complexity of your tree and data, this step may take a while.
The resulting object contains the log likelihood of the model (lnLik) and the estimates for all of the parameters.
[1] -152.5654
lambda0 lambda1 mu0 mu1 q01 q10
0.089 0.150 0.000 0.052 0.018 0.022
In this case we can compare these parameters to the known values we set for the simulation. The estimates are not exactly the same and perhaps a better set of starting estimates would be helpful. However, we can see that \(\lambda_{1} > \lambda_{0}\) as we know it should be.
Let’s look at testing the hypothesis that speciation rates are different when the trait we are studying is in different states. We can do this by constraining the speciation rates to be equal in a new model using constrain.
[1] -153.0321
We can put the estimated parameters together in a table for ease of comparison.
| lambda0 | lambda1 | mu0 | mu1 | q01 | q10 | |
|---|---|---|---|---|---|---|
| full | 0.089 | 0.150 | 0 | 0.052 | 0.018 | 0.022 |
| equal.l | 0.094 | 0.094 | 0 | 0.000 | 0.016 | 0.030 |
The final thing to do is test the difference between the new and old models.
Df lnLik AIC ChiSq Pr(>|Chi|)
full 6 -152.56 317.13
model 1 5 -153.03 316.06 0.93342 0.334
The ANOVA table tells us that there is no significant difference in fit between the two models (\(\chi^{2} = 0.93, \text{p} = 0.33\)).
If you’re not a fan of maximum likelihood estimation you can run the same analysis by MCMC. First we need to set a prior as the starting point for our analysis. The function make.prior.exponential will allow us to set an exponential prior of \(\frac{1}{2r}\). Remember that \(r = \lambda - \mu\).
In our final mcmc analysis we will need to provide an argument called simply w. This is a so-called tuning parameter for the sampling that the mcmc function will perform. The function uses a process called slice sampling (Neal 2003). In slice sampling, the parameter w affects how many function evaluations are required between sample updates. According to the documentation for the function, the optimal value for w is equal to the width of the high probability region we are searching through. The easiest way to work this out is to run a short chain and use the obseved range in the results.
set.seed(42)
tmp <- mcmc(lik, fit$par, nsteps=100, prior=prior,
lower=0, w=rep(1, 6), print.every=0)
w <- diff(sapply(tmp[2:7], range))
To run our full analysis, we will need to use a much longer chain. I’ve gone for 10,000 here. Be aware that this will take a little while.
We can plot the distributions of \(\lambda_{0}\) and \(\lambda_{1}\) using the function profiles.plot. Here we can see the true values as lines. The shaded areas and bars along the x axis both represent the 95% confidence intervals of the sample.
col <- c("#004165", "#eaab00")
profiles.plot(samples[c("lambda0", "lambda1")], col.line=col, las=1,
xlab="Speciation rate", legend="topright")
abline(v=c(.1, .2), col=col)
The reason we haven’t really identified the difference that we know is there from our simulation is almost certainly because the tree is too small and so our analysis is not powerful enough.
11.2 Multi-state traits: MuSSE
BiSSE works well with binary traits but what about categrorical traits with more than two states? For this we can use an extension of the BiSSE model called MuSSE (Multiple State Speciation and Extinction).
Let’s start with a simulated example. The traits we simulate will have three states (coded numerically) and transitions are only possible between adjacent states (you can’t go from state 1 to 3 or 3 to 1). All other transition rates will be equal. In this case we need to specify the parameters in the following order:
\[\lambda_{1} \;\; \lambda_{2} \;\; \lambda_{3} \;\; \mu_{1} \;\; \mu_{2} \;\; \mu_{3} \;\; q_{12} \;\; q_{13} \;\; q_{21} \;\; q_{23} \;\; q_{31} \;\; q_{32}\]
pars <- c(.1,.15, .2, #lambda
.03, .045, .06, #mu
.05, 0, #q12 q13
.05, .05, #q21 q23
0, 0.05) #q31 q32
Now we can simulate our tree and data using tree.musse.
We can extract the history of the simulated trait with history.from.sim.discrete and plot it over the tree.
col <- c("#eaab00", "#004165", "#618e02")
h <- history.from.sim.discrete(phy, 1:3)
plot(h, phy, cex=1, col=col, no.margin=TRUE, font=1)
Next we must make the likelihood function in much the same way as we did for BiSSE but this time using the function make.musse.
For our analysis, we’ll start with a very simple model. The simplest model is one in which all three speciation rates are the same (\(\lambda_{1} = \lambda_{2} = \lambda_{3}\)), all 3 extinction rates are the same (\(\mu_{1} = \mu_{2} = \mu_{3}\)) and all the non-zero transition rates are the same (\(q_{12} = q_{21} = q_{23} = q_{32}\)). Also, remember that \(q_{13}\) and \(q_{31}\) are still both 0.
lik.base <- constrain(lik, lambda2 ~ lambda1, lambda3 ~ lambda1,
mu2 ~ mu1, mu3 ~ mu1,
q13 ~ 0, q21 ~ q12,
q23 ~ q12, q31 ~ 0, q32 ~ q12)
Just as with BiSSE, we need to set a starting point for the likelihood search, this time with the function starting.point.musse.
Now we can start the maximum likelihood search with find.mle.
[1] -153.4905
lambda1 mu1 q12
0.201 0.139 0.055
To test if the speciation rate varies when the traits is in different states, we can run another model in which the values of \(\lambda_{1}\), \(\lambda_{2}\) and \(\lambda_{3}\) are unconstrained.
lik.lambda <- constrain(lik, mu2 ~ mu1, mu3 ~ mu1,
q13 ~ 0, q21 ~ q12,
q23 ~ q12, q31 ~ 0, q32 ~ q12)
fit.lambda <- find.mle(lik.lambda, p[argnames(lik.lambda)])
In this case the new model is not significantly better than the minimal model (\(\chi^{2} = 2.67, \; \text{p} = 0.263\)). Keep in mind that when we simulated the data, we specified that \(\lambda\) was indeed different between different states. It’s probable that we haven’t been able to detect this on such a small tree (n = 42).
Df lnLik AIC ChiSq Pr(>|Chi|)
minimal 3 -153.49 312.98
free.lambda 5 -152.16 314.32 2.6651 0.2638
Small trees are not good fits for these methods. Generally, the larger the tree the more power you have. Here is the model comparison for the same analysis with the same parameters but simulated on a tree with 1000 tips. As you can see, the analysis shows very clearly that the model in which \(\lambda\) is allowed to vary is a much better fit (\(\chi^{2} = 33.35, \; \text{p} < 0.001\)).
| Df | lnLik | AIC | ChiSq | Pr(>|Chi|) | |
|---|---|---|---|---|---|
| minimal | 3 | -3694.195 | 7394.390 | NA | NA |
| free.lambda | 5 | -3677.520 | 7365.041 | 33.34883 | 1e-07 |
11.3 Quantitative traits: QuaSSE
Dealing with quantitative traits in models like these is slightly less straightforward. Categorical traits are well defined and we can model the transition rates between states. Deciding when something like body mass has undergone significant evolutionary change is a little more difficult. This is the same problem we faced with continuous characters in ancestral state reconstruction and it will come up again when we look at convergence.
For diversification, we have the QuaSSE (Quantitative State Speciation and Extinction) model.
First we need to specify some functions to use. For lambda we will use a sigmoidal function with an inflection at x = 0. This means we will have an increasing rate of speciation reaching a plateau. We can specify this with the function sigmoid.x.
Next we can specify the model of character evolution for our trait simulation. We will be going with Brownian motion and we will set the diffusion parameter to 0.025. To specify all this, we can use the function make.brownian.with.drift.
Now as with BiSSE and MuSSE, we can simulate the tree and data using tree.quasse.
Extract the trait states and specify the standard deviation. For this example, assume the standard deviation for all tips is 1/200.
Next we create the likelihood function, this time specifying the speciation and extinction functions.
Now to calculate the starting point. This is a little more involved than BiSSE and MuSSE! starting.point.quasse gives us constant rates for each parameter.
lambda mu diffusion
0.16107838 0.02569057 0.03164062
Let’s ignore drift for our first model (drift ~ 0). The function argnames will return the names of parameters we will need to supply.
[1] "l.y0" "l.y1" "l.xmid" "l.r" "m.c" "diffusion"
Next, we select the starting point values. For l.y0 and l.y1, we will take the suggested value of \(\lambda\) from starting.point.quasse (p[1]). For l.xmid we will take the mean of the state values (mean(states)). l.r is set at 1. m.c (\(\mu\)) and diffusion are taken straight from p (p[2:3])
l.y0 l.y1 l.xmid l.r m.c diffusion
0.16107838 0.16107838 0.57097062 1.00000000 0.02569057 0.03164062
One final thing before we run the search. We now need to specify the lower bounds for the search for each parameter..
Finally we are ready to run our analysis! As with BiSSE and MuSSE, we will do so with find.mle. This will take some time.
fit <- find.mle(lik.nodrift, p.start,
control=list(parscale=.1),
lower=lower, verbose=0)
round(coef(fit),3)
l.y0 l.y1 l.xmid l.r m.c diffusion
0.000 0.220 0.238 28961.248 0.000 0.029
Let’s compare this model to one in which \(\lambda\) is constant.
lik.constant <- constrain(lik.nodrift,
l.y1 ~ l.y0,
l.xmid ~ 0,
l.r ~ 1)
fit.constant <- find.mle(lik.constant,
p.start[argnames(lik.constant)],
control=list(parscale=.1),
lower=0, verbose=0)
knitr::kable(anova(fit, constant=fit.constant))
| Df | lnLik | AIC | ChiSq | Pr(>|Chi|) | |
|---|---|---|---|---|---|
| full | 6 | -51.73395 | 115.4679 | NA | NA |
| constant | 3 | -55.15222 | 116.3044 | 6.836543 | 0.0772943 |
Once again we see no significant difference (\(\chi^{2} = 6.84, \; p = 0.08\)). Again this probably due to the small tree and a larger one would give us more power.
11.3.1 QuaSSE primate example
To demonstrate how QuaSSE can be used in research, let’s investigate trait dependent diversification in primates using some existing data on primate body mass (Fitzjohn 2010).
We will need to log-transform mass and we will also assume the standard deviation is \(\frac{1}{50}\).
Starting point parameter estimates.
lambda mu diffusion
0.19072726 0.11034810 0.03251953
Now we will create a piecewise linear function using make.linear.x. The function is linear between xr[1] and xr[2] and flat outside this range.
Now let’s create a shortcut because we will be analysing several models. First we will create a function that will take our speciation and extinction functions and buld our model for us using make.quasse. The second function simply constrains drift to zero.
make.primates <- function(lambda, mu)
make.quasse(phy, mass, mass.sd, lambda, mu)
nodrift <- function(f)
constrain(f, drift ~ 0)
Now we can use these functions to build our likelihood functions. We are keeping \(\mu\) constant in each case.
f.c <- make.primates(constant.x, constant.x)
f.l <- make.primates(linear.x, constant.x)
f.s <- make.primates(sigmoid.x, constant.x)
f.h <- make.primates(noroptimal.x, constant.x)
We will start by fitting the constant model (f.c) with no drift.
control <- list(parscale=.1, reltol=0.001)
mle.c <- find.mle(nodrift(f.c), p, lower=0, control=control, verbose=0)
Next we calculate starting points for our other models.
p.c <- mle.c$par
p.l <- c(p.c[1], l.m=0, p.c[2:3])
p.s <- p.h <- c(p.c[1], p.c[1], mean(xr), 1, p.c[2:3])
names(p.s) <- argnames(nodrift(f.s))
names(p.h) <- argnames(nodrift(f.h))
Once we have our starting points, we are ready to fit each of the models. Each of these lines may take a while to run.
mle.l <- find.mle(nodrift(f.l), p.l, control=control, verbose=0)
mle.s <- find.mle(nodrift(f.s), p.s, control=control, verbose=0)
mle.h <- find.mle(nodrift(f.h), p.h, control=control, verbose=0)
anova(mle.c, linear=mle.l, sigmoidal=mle.s, hump=mle.h)
| Df | lnLik | AIC | ChiSq | Pr(>|Chi|) | |
|---|---|---|---|---|---|
| minimal | 3 | -841.4029 | 1688.806 | NA | NA |
| linear | 4 | -836.0697 | 1680.139 | 10.66629 | 0.0010911 |
| sigmoidal | 6 | -832.6038 | 1677.208 | 17.59805 | 0.0005323 |
| hump | 6 | -829.0036 | 1670.007 | 24.79861 | 0.0000170 |
The ANOVA table shows us that the best fit is the hump model where speciation rate follows a hump shaped fit.
The next lines (which will again take some time) will start with parameters from the previous constrained models and add the drift parameter.
mle.d.l <- find.mle(f.l, coef(mle.l, TRUE), control=control, verbose=0)
mle.d.s <- find.mle(f.s, coef(mle.s, TRUE), control=control, verbose=0)
mle.d.h <- find.mle(f.h, coef(mle.h, TRUE), control=control, verbose=0)
We should add these new models to the ANOVA table to compare them all. We can see that in all cases the fit of the model is improved by the addition of drift.
knitr::kable(anova(mle.c, linear=mle.l, sigmoidal=mle.s,
hump=mle.h, drift.linear=mle.d.l,
drift.sigmoidal=mle.d.s, drift.hump=mle.d.h))
| Df | lnLik | AIC | ChiSq | Pr(>|Chi|) | |
|---|---|---|---|---|---|
| minimal | 3 | -841.4029 | 1688.806 | NA | NA |
| linear | 4 | -836.0697 | 1680.139 | 10.66629 | 0.0010911 |
| sigmoidal | 6 | -832.6038 | 1677.208 | 17.59805 | 0.0005323 |
| hump | 6 | -829.0036 | 1670.007 | 24.79861 | 0.0000170 |
| drift.linear | 5 | -832.5001 | 1675.000 | 17.80563 | 0.0001360 |
| drift.sigmoidal | 7 | -830.2691 | 1674.538 | 22.26745 | 0.0001773 |
| drift.hump | 7 | -825.3671 | 1664.734 | 32.07150 | 0.0000018 |
When we extract the drift parameters, we can see that in all cases they are positive, indicating that mass is increasing over the tree on average.
c(linear=coef(mle.d.l)[["drift"]],
sigmoidal=coef(mle.d.s)[["drift"]],
hump=coef(mle.d.h)[["drift"]])
linear sigmoidal hump
0.10458477 0.06776915 0.07929087
So the hump model with drift is the best fit to the data. The parameters of this model tell us that \(\lambda\) peaks around a log body mass value of 8.43 (l.xmid) and a variance of 0.12 (l.s2).
l.y0 l.y1 l.xmid l.s2 m.c drift diffusion
0.12415911 0.33331587 8.43421271 0.11936647 0.05362881 0.07929087 0.03201213
When we plot the data alongside the tree, we can see that many of the species that fall within 2 standard deviations of the value of l.xmid are within the Cercopithecidae.
This suggests we might want to split the tree here and evaluate different models for each section of the tree much like we did with cetaceans in the previous chapter. In fact, the output of analysis with MEDUSA supports the idea that there has been a shift in diversification in the Cercopithecinae.
Appropriate aicc-threshold for a tree of 233 tips is: 6.687066.
Step 1: lnLik=-691.8978; aicc=1387.821; model=bd
Step 2: lnLik=-678.3882; aicc=1366.907; shift at node 386; model=bd; cut=node; # shifts=1
No significant increase in aicc score. Disregarding subsequent piecewise models.
Calculating profile likelihoods on parameter values.
Model.ID Shift.Node Cut.At Model Ln.Lik.part r epsilon r.low
1 1 234 node bd -491.4083 0.0756587 0.4497380 0.0627243
2 2 386 node bd -186.9799 0.2446490 0.0745145 0.1937557
r.high eps.low eps.high
1 0.0903268 0.2837926 0.5764245
2 0.3039223 0.0000000 0.3621622
Before we proceed, it might be best to label the nodes so we can call the right one by name.
Now we can make split QuaSSE objects using make.quasse.split. The node we want here is node 153. In this case the speciation and extinction functions are both constant and the functions are the same on both sides of the split. For cases where functions may differ either side of the split, we can pass lists of functions. The Inf places the split at the base of the branch protuding from Node 153 (as in the MEDUSA plot above). A value of 0 would place the split at the node itself.
[1] "l.c.1" "m.c.1" "drift.1" "diffusion.1" "l.c.2"
[6] "m.c.2" "drift.2" "diffusion.2"
The first set of parameters refer to the “background” tree and the second set refer to the “foreground” tree rooted at node 153.
Let’s constrain drift to be 0 and assume diffusion is the same in both trees.
[1] "l.c.1" "m.c.1" "diffusion.1" "l.c.2" "m.c.2"
Next we generate a starting point using the starting points from the earlier model (p.c).
Let’s run the ML search.
We need to repeat this process for linear speciation functions and calculate starting points for these as well.
f.ll <- make.quasse.split(phy, mass, mass.sd, linear.x, constant.x, "nd153", Inf)
g.ll <- constrain(f.ll, drift.1 ~ 0, drift.2 ~ 0, diffusion.2 ~ diffusion.1)
g.lc <- constrain(g.ll, l.m.2 ~ 0)
g.cl <- constrain(g.ll, l.m.1 ~ 0)
p.cc <- coef(mle.cc)
p.ll <- c(p.cc[1], 0, p.cc[2:4], 0, p.cc[5])
names(p.ll) <- argnames(g.ll)
Once again we run the ML search and save the results.
Finally, we generate starting points for models in which just one of the sections of the tree have linear speciation functions.
The ML searches for these models…
mle.lc <- find.mle(g.lc, p.lc, control=control, verbose=0)
mle.cl <- find.mle(g.cl, p.cl, control=control, verbose=0)
Once all the searches are complete, we can finally compare each model in an ANOVA table.
knitr::kable(anova(mle.c, linear=mle.l, sigmoidal=mle.s, hump=mle.h,
part.constant=mle.cc, part.linear.bg=mle.lc,
part.linear.fg=mle.cl, part.linear=mle.ll))
| Df | lnLik | AIC | ChiSq | Pr(>|Chi|) | |
|---|---|---|---|---|---|
| minimal | 3 | -841.4029 | 1688.806 | NA | NA |
| linear | 4 | -836.0697 | 1680.139 | 10.66629 | 0.0010911 |
| sigmoidal | 6 | -832.6038 | 1677.208 | 17.59805 | 0.0005323 |
| hump | 6 | -829.0036 | 1670.007 | 24.79861 | 0.0000170 |
| part.constant | 5 | -828.5921 | 1667.184 | 25.62147 | 0.0000027 |
| part.linear.bg | 6 | -828.2577 | 1668.515 | 26.29041 | 0.0000083 |
| part.linear.fg | 6 | -826.0173 | 1664.035 | 30.77116 | 0.0000009 |
| part.linear | 7 | -828.3231 | 1670.646 | 26.15951 | 0.0000294 |
We can clearly see that all models are significant improvements over the minimal model. The best fit is for part.linear.fg in which the foreground tree has a linear speciation model. We can see this as it has the lowest AIC value (AIC = 1664).
Inspecting the coeffiients shows us that the speciation rate in the foreground clade is a negative function of body size (l.m.2 = -0.193) and therefore that in this clade, an increasing body size is associated with a decreasing speciation rate.
l.c.1 m.c.1 diffusion.1 l.c.2 l.m.2 m.c.2
0.141392843 0.068877966 0.031964900 1.972507892 -0.193181732 0.005147044
Bibliography
FitzJohn, R.G. (2012) ‘Diversitree: Comparative Phylogenetic Analyses of Diversification in R’. Methods in Ecology and Evolution in press
Fitzjohn, R.G. (2010) ‘Quantitative Traits and Diversification’. Systematic Biology [online] 59 (6), 619–633. available from <https://liverpool.idm.oclc.org/login?url=https://search.ebscohost.com/login.aspx?direct=true&db=edselc&AN=edselc.2-52.0-78650666284&site=eds-live&scope=site>
Neal, R.M. (2003) ‘Slice Sampling’. Annals of Statistics [online] 31 (3), 705–741. available from <https://liverpool.idm.oclc.org/login?url=https://search.ebscohost.com/login.aspx?direct=true&db=edselc&AN=edselc.2-52.0-1642370803&site=eds-live&scope=site>


Survey Site
Add Survey
View Survey Data
{{survey.title}}
Question ID#
Question Title
Answer
{% for answer in answers %} {% for qa in answer.questionanswer_set.all %}
{{qa.answer.question.id}}
{{qa.answer.question.question_text}}
{{qa.answer.choice_text}}
{% endfor %} {% endfor %}


|
Neodroid
0.2.0
Machine Learning Environment Prototyping Tool
|
Public Member Functions | |
| override void | Display (Double value) |
| override void | Display (float[] values) |
| override void | Display (String values) |
| override void | Display (Vector3 value) |
| override void | Display (Vector3[] value) |
| override void | Display (Points.ValuePoint points) |
| override void | Display (Points.ValuePoint[] points) |
| override void | Display (Points.StringPoint point) |
| override void | Display (Points.StringPoint[] points) |
| override void | Display (float values) |
| void | ScatterPlot (Vector3[] points) |
| void | PlotSeries (float[] points) |
| override void | PlotSeries (Points.ValuePoint[] points) |
| Public Member Functions inherited from droid.Runtime.Prototyping.Displayers.Displayer | |
| abstract void | Display (Single value) |
| abstract void | Display (Single[] values) |
| Public Member Functions inherited from droid.Runtime.Utilities.GameObjects.PrototypingGameObject | |
| void | RefreshStart () |
| void | RefreshAwake () |
| Public Member Functions inherited from droid.Runtime.Interfaces.IDisplayer | |
| void | Display (double value) |
| void | Display (string value) |
Protected Member Functions | |
| override void | Setup () |
| Protected Member Functions inherited from droid.Runtime.Prototyping.Displayers.Displayer | |
| override void | RegisterComponent () |
| override void | UnRegisterComponent () |
| virtual void | Clean () |
| Protected Member Functions inherited from droid.Runtime.Utilities.GameObjects.PrototypingGameObject | |
| void | Start () |
| void | Awake () |
| virtual void | Clear () |
Additional Inherited Members | |
| Protected Attributes inherited from droid.Runtime.Prototyping.Displayers.Displayer | |
| bool | _RetainLastPlot = true |
| dynamic | _Values = null |
| Protected Attributes inherited from droid.Runtime.Utilities.GameObjects.PrototypingGameObject | |
| string | _Custom_Name = "" |
| Properties inherited from droid.Runtime.Prototyping.Displayers.Displayer | |
| AbstractPrototypingEnvironment | ParentEnvironment [get, set] |
| override string | PrototypingTypeName [get] |
| Properties inherited from droid.Runtime.Utilities.GameObjects.PrototypingGameObject | |
| virtual string | PrototypingTypeName [get] |
| string | Identifier [get] |
| Properties inherited from droid.Runtime.Interfaces.IRegisterable | |
| string | Identifier [get] |
Definition at line 12 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| value |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 56 of file GameObjectScatterPlotDisplayer.cs.
| override void droid.Runtime.Prototyping.Displayers.ScatterPlots.GameObjectScatterPlotDisplayer.Display | ( | float [] | values | ) |
| values |
Implements droid.Runtime.Interfaces.IDisplayer.
Definition at line 67 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| value |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 82 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| value |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 98 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| value |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 99 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| point |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 101 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| points |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 103 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| point |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 132 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| points |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 133 of file GameObjectScatterPlotDisplayer.cs.
| override void droid.Runtime.Prototyping.Displayers.ScatterPlots.GameObjectScatterPlotDisplayer.Display | ( | float | values | ) |
Implements droid.Runtime.Interfaces.IDisplayer.
Definition at line 137 of file GameObjectScatterPlotDisplayer.cs.
| void droid.Runtime.Prototyping.Displayers.ScatterPlots.GameObjectScatterPlotDisplayer.PlotSeries | ( | float [] | points | ) |
Definition at line 177 of file GameObjectScatterPlotDisplayer.cs.
|
virtual |
| points |
Implements droid.Runtime.Prototyping.Displayers.Displayer.
Definition at line 204 of file GameObjectScatterPlotDisplayer.cs.
| void droid.Runtime.Prototyping.Displayers.ScatterPlots.GameObjectScatterPlotDisplayer.ScatterPlot | ( | Vector3 [] | points | ) |
| points |
Definition at line 151 of file GameObjectScatterPlotDisplayer.cs.
|
protectedvirtual |
Reimplemented from droid.Runtime.Utilities.GameObjects.PrototypingGameObject.
Definition at line 27 of file GameObjectScatterPlotDisplayer.cs.


The runner is tracked by our proprietary hardware and wearable sensors. Timing information is then live streamed to our servers.
Server-side code interprets runner's I.D.s, times, and computes pace.
Times are immediately pushed from the cloud to your personal device or tablet.


|
plibsys
0.0.4
|
Shared memory. More...
Go to the source code of this file.
Typedefs | |
| typedef enum PShmAccessPerms_ | PShmAccessPerms |
| Enum with shared memory access permissions. More... | |
| typedef struct PShm_ | PShm |
| Shared memory opaque data structure. More... | |
Enumerations | |
| enum | PShmAccessPerms_ { P_SHM_ACCESS_READONLY = 0, P_SHM_ACCESS_READWRITE = 1 } |
| Enum with shared memory access permissions. More... | |
Functions | |
| P_LIB_API PShm * | p_shm_new (const pchar *name, psize size, PShmAccessPerms perms, PError **error) |
| Creates a new PShm object. More... | |
| P_LIB_API void | p_shm_take_ownership (PShm *shm) |
| Takes ownership of a shared memory segment. More... | |
| P_LIB_API void | p_shm_free (PShm *shm) |
| Frees PShm object. More... | |
| P_LIB_API pboolean | p_shm_lock (PShm *shm, PError **error) |
| Locks PShm object for usage. More... | |
| P_LIB_API pboolean | p_shm_unlock (PShm *shm, PError **error) |
| Unlocks PShm object. More... | |
| P_LIB_API ppointer | p_shm_get_address (const PShm *shm) |
| Gets a starting address of a PShm memory segment. More... | |
| P_LIB_API psize | p_shm_get_size (const PShm *shm) |
| Gets the size of a PShm memory segment. More... | |
Shared memory.
Shared memory is a memory segment which can be accessed from several threads or processes. It provides an efficient way to transfer large blocks of data between processes. It can be used as any other regular memory segment in an application.
Shared memory acts like an inter-process communication method. This memory exchange implementation is process-wide so you can transfer data not only between the threads. But it makes this IPC method (actually like any other IPC method, as well) relatively heavy. Consider using other approaches instead if you do not need to cross the process boundary.
A shared memory segment doesn't provide any synchronization primitives itself which means that several processes or threads can concurrently write and read from it. This can lead to data consistency problems. To avoid such situations a locking mechanism is provided: use p_shm_lock() before entering a critical section on the memory segment and p_shm_unlock() when leaving this section. The locking mechanism is working across the process boundary.
A process-wide shared memory segment is identified by its name across the system, thus it is also called a named memory segment. Use p_shm_new() to open the named shared memory segment and p_shm_free() to close it.
Please note the following platform specific differences:
You can take ownership of the shared memory segment with p_shm_take_ownership() to explicitly remove it from the system after closing.
Definition in file pshm.h.
| typedef struct PShm_ PShm |
| typedef enum PShmAccessPerms_ PShmAccessPerms |
Enum with shared memory access permissions.
| enum PShmAccessPerms_ |
Gets the size of a PShm memory segment.
| shm | PShm to get the size for. |
Note that the returned size would be a slightly larger than specified during the p_shm_new() call due to service information stored inside.
| P_LIB_API PShm* p_shm_new | ( | const pchar * | name, |
| psize | size, | ||
| PShmAccessPerms | perms, | ||
| PError ** | error | ||
| ) |
Creates a new PShm object.
| name | Shared memory name. | |
| size | Size of the memory segment in bytes, can't be changed later. | |
| perms | Memory segment permissions, see PShmAccessPerms. | |
| [out] | error | Error report object, NULL to ignore. |
Takes ownership of a shared memory segment.
| shm | Shared memory segment. |
If you take ownership of the shared memory object, p_shm_free() will try to completely unlink it and remove from the system. This is useful on UNIX systems where shared memory can survive an application crash. On the Windows and OS/2 platforms this call has no effect.
The common usage of this call is upon application startup to ensure that the memory segment from the previous crash will be unlinked from the system. To do that, call p_shm_new() and check if its condition is normal (the segment size, the data). If not, take ownership of the shared memory object and remove it with the p_shm_free() call. After that, create it again.


09 August 2016
This is the person tasked with drawing an image of the fauna and flora of the world they encounter, focusing primarily on the monsters. Whereas the Journal Keeper writes upon their experiences this person captures the imagery of what they encounter and hopefully get it published in the legendary Dragonica.
This is a role which doesn't require a superb artist to fill, all that would be required is just a fun individual who is willingly to draw up their concept of the monsters for the other members to see.
-
Originally posted by
Lantern Lighters Roleplayers
↩


Family is the fundamental building block of all human civilizations. Marriage is the glue that holds it
together. The health of our culture, its citizens and their children is intimately linked to the health and
well-being of marriage. In these pages, you will find a wealth of information and resources that will help
you understand just how much the family matters and keep up to date on how the family is faring in our
culture.
Chuck Colson on the New Mexico Biblical Worldview
Learn More
Sign up for our mailing list


Class Room
java.lang.Object
it.polimi.ingsw.server.roomhandler.Room
public class Room
extends java.lang.Object
This class represents the room of a game. It has all the connection with the clients, the controller and model of one match.
- Author:
- Stefano Fossati
-
Constructor Summary
-
Method Summary
Modifier and Type Method Description void
addConnectionToClient(java.lang.String name, ConnectionToClient connection, boolean reconnection)
Adds the new connection with a client to the list of all the actually connections with this room.void
eliminateRoom()
Eliminates the room from the map of all the rooms in the server.java.util.Map<java.lang.String,ConnectionToClient>
getConnections()
Getter synchronized of all the connection with the clients currently connected to this room.DisconnectionHandler
getDisconnectionHandler()
Getter of the disconnection handler of this room.int
getNumPlayer()
Getter of the number of player of this room.java.lang.String
getPlayerSendNumPlayer()
int
getRoomNumber()
Getter of the number of this room.boolean
isFullPlayer()
Getter of the boolean that indicates if all the client/player are connected with this room.boolean
isSendNumPlayer()
Getter of the boolean that indicates if the number player request is already send.boolean
isStart()
Getter of the boolean that indicates if the game has already started.void
setDisconnectionHandler(DisconnectionHandler disconnectionHandler)
Sets the disconnection handler of this room.void
setFullPlayer(boolean fullPlayer)
Sets if all the client are connected in this match.void
setNumPlayer(int numPlayer)
Sets the number of players of the match in this room.void
setPlayerSendNumPlayer(java.lang.String playerSendNumPlayer)
void
setSendNumPlayer(boolean sendNumPlayer)
Sets if the number of player request for this room is already send to the first client connected or not.void
startGame()
Starts the match when all the players/clients are connected.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
-
Constructor Details
-
Room
Constructs the room initialising default attributes and creates controllers of connection and of the game.- Parameters:
roomNumber
- The number of the room of the match.server
- The server of the game.
-
-
Method Details
-
getPlayerSendNumPlayer
public java.lang.String getPlayerSendNumPlayer() -
setPlayerSendNumPlayer
public void setPlayerSendNumPlayer(java.lang.String playerSendNumPlayer) -
setNumPlayer
public void setNumPlayer(int numPlayer)Sets the number of players of the match in this room.- Parameters:
numPlayer
- The number of player of the game.
-
setDisconnectionHandler
Sets the disconnection handler of this room.- Parameters:
disconnectionHandler
- The disconnection handler of this room.
-
setSendNumPlayer
public void setSendNumPlayer(boolean sendNumPlayer)Sets if the number of player request for this room is already send to the first client connected or not.- Parameters:
sendNumPlayer
- The boolean that indicates if the number player request is already send.
-
setFullPlayer
public void setFullPlayer(boolean fullPlayer)Sets if all the client are connected in this match.- Parameters:
fullPlayer
- Is set true if all the player are connected to this room, else is set false.
-
getRoomNumber
public int getRoomNumber()Getter of the number of this room.- Returns:
- The number of this room.
-
getConnections
Getter synchronized of all the connection with the clients currently connected to this room.- Returns:
- The map with all the current connected players.
-
getNumPlayer
public int getNumPlayer()Getter of the number of player of this room.- Returns:
- The number of player of this room.
-
getDisconnectionHandler
Getter of the disconnection handler of this room.- Returns:
- The disconnection handler of this room.
-
isSendNumPlayer
public boolean isSendNumPlayer()Getter of the boolean that indicates if the number player request is already send.- Returns:
- It is true if the number player request is already send, else is false.
-
isStart
public boolean isStart()Getter of the boolean that indicates if the game has already started.- Returns:
- It is true if the game is already started, else false.
-
isFullPlayer
public boolean isFullPlayer()Getter of the boolean that indicates if all the client/player are connected with this room.- Returns:
- True if all the player are connected, else false.
-
addConnectionToClient
public void addConnectionToClient(java.lang.String name, ConnectionToClient connection, boolean reconnection)Adds the new connection with a client to the list of all the actually connections with this room.- Parameters:
name
- The name of the player of the connection.connection
- Teh connection with the client.reconnection
- The boolean that indicates if the client has done a reconnection, or not.
-
startGame
public void startGame()Starts the match when all the players/clients are connected. -
eliminateRoom
public void eliminateRoom()Eliminates the room from the map of all the rooms in the server.
-


#include <GrKFInterpolator.h>
Public Member Functions | |
| GrKFInterpolator () | |
| pass in the keyframe data to the interpolator. | |
| GrKFInterpolator (URef< GrKFAnimData > kfData) | |
| ~GrKFInterpolator () | |
| void | Init (URef< GrKFAnimData > kfData) |
| initializes the animation... this is useful for arrays of interpolators. | |
| URef< GrKFAnimData > | GetKFData () const |
| returns a pointer to the keyframe data that we're using. | |
| bool | SetOutput (GrAnimXFormCache *output) |
| sets the player the interpolator should write to. | |
| void | ApplyPose (float time, float blendWeight, float clampDuration, bool clamp) |
| gets the pose for a given instant in time. |
Definition at line 24 of file GrKFInterpolator.h.
| GrKFInterpolator::GrKFInterpolator | ( | ) |
pass in the keyframe data to the interpolator.
class header.
File: GrKFInterpolator.h Author: Kevin Bray Created: 04-29-06 Copyright © 2004 Bootstrap Studios. All rights reserved. project includes. class GrKFInterpolator ctor & dtor
Definition at line 27 of file GrKFInterpolator.cpp.
| GrKFInterpolator::GrKFInterpolator | ( | URef< GrKFAnimData > | kfData | ) |
Definition at line 41 of file GrKFInterpolator.cpp.
| GrKFInterpolator::~GrKFInterpolator | ( | ) |
Definition at line 58 of file GrKFInterpolator.cpp.
| void GrKFInterpolator::ApplyPose | ( | float | time, | |
| float | blendWeight, | |||
| float | clampDuration, | |||
| bool | clamp | |||
| ) |
gets the pose for a given instant in time.
if we don't have an output, then don't do anything!
the clamp duration ensures that an animation channel is clamped until it's parent animation completes.
convert the incoming time from seconds to 22.10 fixed point.
find the correct keyframes to work with.
simply lerp to the desired rotation.
find the correct keyframes to work with.
perform a cubic bezier interpolation to the desired scale.
find the correct keyframes to work with.
perform a cubic bezier interpolation to the desired translation.
slerp from identity!
Definition at line 118 of file GrKFInterpolator.cpp.
| URef< GrKFAnimData > GrKFInterpolator::GetKFData | ( | ) | const |
returns a pointer to the keyframe data that we're using.
Definition at line 90 of file GrKFInterpolator.cpp.
| void GrKFInterpolator::Init | ( | URef< GrKFAnimData > | kfData | ) |
initializes the animation... this is useful for arrays of interpolators.
public methods.
Definition at line 70 of file GrKFInterpolator.cpp.
| bool GrKFInterpolator::SetOutput | ( | GrAnimXFormCache * | output | ) |
sets the player the interpolator should write to.
check the index of the transform we're driving. If it does not exist, then we failed to set the output.
success!
Definition at line 97 of file GrKFInterpolator.cpp.


--- permalink: /spec/lang/2019R3/experimental/ redirect_from: - /spec/lang/v2019R3/experimental.html - /spec/lang/2019R3/experimental.html ---
Primary contributors:
Copyright © 2018, 2019 WSO2
Licensed under the Creative Commons Attribution-NoDerivatives 4.0 International license
This document describes features implemented experimentally in Ballerina 1.0.
behavioral-type-descriptor := ... | stream-type-descriptor
stream-type-descriptor := stream
[type-parameter]
A value of type stream<T>
is a distributor for values of type
T
: when a value v of type T is put into the stream, a function will
be called for each subscriber to the stream with v as an argument. T must be a
pure type.
A value belongs to a type stream
(without the type-parameter)
if it has basic type stream.
A new stream can be constructed using a new
expression.
expression := ... | table-query-expr
table-query-expr :=from
query-source [query-join-type query-join-source] [query-select] [query-group-by] [query-order-by] [query-having] [query-limit] query-source := identifier [as
identifier] [query-where] query-where :=where
expression query-join-type := [([left
|right
|full
]outer
)|inner
]join
query-join-source := query-sourceon
expression query-select :=select
(*
| query-select-list) query-select-list := expression [as
identifier] (,
expression [as
identifier])* query-group-by :=group
by
identifier (,
identifier)* query-order-by :=order
by
identifier [(ascending
|descending
)] (,
identifier [(ascending
|descending
)])* query-having :=having
expression query-limit :=limit
int-literal
Query expressions bring language integrated SQL-like querying to Ballerina tables.
statement := ... | lock-stmt | forever-stmt | transaction-stmt | transaction-control-stmt
lock-stmt := lock
block-stmt
A lock statement is used to execute a series of assignment statements in a serialized manner. For each variable that is used as an L-value within the block statement, this statement attempts to first acquire a lock and the entire statement executes only after acquiring all the locks. If a lock acquisition fails after some have already been acquired then all acquired locks are released and the process starts again.
forever-stmt :=forever
{
streaming-query-pattern+}
streaming-query-pattern := streaming-query-expr=>
(
array-type-descriptor identifier)
block-stmt streaming-query-expr :=from
(sq-source [query-join-type sq-join-source]) | sq-pattern [query-select] [query-group-by] [query-order-by] [query-having] [query-limit] [sq-output-rate-limiting] sq-source := identifier [query-where] [sq-window [query-where]] [as
identifier]* sq-window :=window
function-call-expr sq-join-source := sq-sourceon
expression sq-output-rate-limiting := sq-time-or-event-output | sq-snapshot-output sq-time-or-event-output := (all
|last
|first
)every
int-literal (time-scale |events
) sq-snapshot-output :=snapshot
every
int-literal time-scale time-scale :=seconds
|minutes
|hours
|days
|months
|years
sq-pattern := [every
] sp-input [sp-within-clause] sp-within-clause :=within
expression sp-input := sp-edge-input ((followed
by
) |,
) sp-input |not
sp-edge-input (and
sp-edge-input) | (for
int-literal time-scale) | [sp-edge-input (and
|or
) ] sp-edge-input |(
sp-input)
sp-edge-input := identifier [query-where] [sp-int-range-expr] [as
identifier] sp-int-range-expr :=[
expression..
[expression]]
The forever statement is used to execute a set of streaming queries against some number of streams concurrently and to execute a block of code when a pattern matches. The statement will never complete and therefore the worker containing it will never complete.
transaction-stmt :=transaction
trans-conf? block-stmt trans-retry? transaction-control-stmt := retry-stmt | abort-stmt trans-conf := trans-conf-item (,
trans-conf-item)* trans-conf-item := trans-retries | trans-oncommit | trans-onabort trans-retries :=retries
=
expression trans-oncommit :=oncommit
=
identifier trans-onabort :=onabort
=
identifier trans-retry :=onretry
block-stmt retry-stmt :=retry
;
abort-stmt :=abort
;
A transaction statement is used to execute a block of code within a 2PC transaction. A transaction can be established by this statement or it may inherit one from the current worker.
If no transaction context is present in the worker then the transaction statement starts a new transaction (i.e., becomes the initiator) and executes the statements within the transaction statement.
Upon completion of the block the transaction is immediately tried to be committed. If the commit succeeds, then if there's an on-commit handler registered that function gets invoked to signal that the commit succeeded. If the commit fails, and if the transaction has not been retried more times than the value of the retries configuration, then the on-retry block is executed and the transaction block statement will execute again in its entirety. If there are no more retries available then the commit is aborted the on-abort function is called.
The transaction can also be explicitly aborted using an abort statement, which will call the on-abort function and give up the transaction (without retrying).
If a retry statement is executed if the transaction has not been retried more times than the value of the retries configuration, then the on-retry block is executed and the transaction block statement will execute again in its entirety.
If a transaction context is present in the executing worker context, then the transaction statement joins that transaction and becomes a participant of that existing transaction. In this case, retries will not occur as the transaction is under the control of the initiator. Further, if the transaction is locally aborted (by using the abort statement), the transaction gets marked for abort and the participant will fail the transaction when it is asked to prepare for commit by the coordinator of the initiator. When the initiating coordinator decides to abort the transaction it will notify all the participants globally and their on-abort functions will be invoked. If the initiating coordinator decides to retry the transaction then a new transaction is created and the process starts with the entire containing executable entity (i.e. resource or function) being re-invoked with the new transaction context.
When the transaction statement reaches the end of the block the transaction is marked as ready to commit. The actual commit will happen when the coordinator sends a commit message to the participant and after the commit occurs the on-commit function will be invoked. Thus, reaching the end of the transaction statement and going past does not have the semantic of the transaction being committed nor of it being aborted. Thus, if statements that follow the transaction statement they are unaware whether the transaction has committed or aborted.
When in a participating transaction, a retry statement is a no-op.
The transaction context in a worker is always visible to invoked functions. Thus any function invoked within a transaction, which has a transaction statement within it, will behave according to the "participated transactions" semantics above.
The transaction context is also propagated over the network via the Ballerina Microtransaction Protocol [XXX].
The stream basic type has a lang library module lang.stream
.


Snider's Woodshop
Main Navigation
HOME
PRODUCTS
ABOUT
CONTACT
wood turning
Contact
Form for Contact Info
Please consider contacting me if you have any questions, comments or inquiries.
Contact Form
Name: (required)
Email: (Required)
Topic
Comments
Comment Box
What is 1 + 3?


I'm an award-winning designer, developer, and entrepreneur who combines the big
picture with an obsession over fine details. I love creating products that delight users and add
tangible value.
June 2021 - Present • New York, NY
Building trust in blockchains at Chainalysis.
Working on Chainalysis' Know Your Transaction platform to help organizations reduce manual workflows, stay compliant with local and global regulations, and safely interact with emerging technologies such as DeFi.
August 2019 - June 2021 • Redmond, WA
Software Engineer at Microsoft.
Worked on Microsoft's Viva Insights team, bringing together communications, knowledge, learning, resources, and insights into an employee experience that integrates seamlessly into the apps you use every day.
May 2018 - August 2018 • Sunnyvale, CA
Software Engineering Intern at Amazon.
Software Engineering Intern on Amazon's Supply Chain Technology at Amazon Lab126. Created an objective and standardized way to score Amazon hardware suppliers.
May 2018 - August 2018 • Redmond, WA
Software Engineering Intern at Microsoft.
Worked on Microsoft Office 365's Workplace Analytics team, developing analytics to help offices around the world become more productive.
May 2017 - August 2017 • New York, NY
I worked at Namely as their first software engineering intern, ever.
As a software engineering intern, I worked closely with Namely's core HCM team. I was given ownership of their product timeline, which I helped reshape both aesthetically and functionally to increase user engagement and create a more elegant experience.
May 2016 - November 2016 • San Francisco, CA
Software Engineering Intern at Twitter.
Worked on Twitter's Timeline Service team. Developed a tool to analyze and debug why posts were selected for injection into user timelines, as well as implementing general overall improvements to the Twitter timeline experience.
October 2015 - May 2016 • New York, NY
Software Engineering Intern at Vine.
Wrote Espresso tests for Twitter's Vine app for Android, an app that has over 50 million downloads on the Play Store.


Guardian Services
Following types of guarding services are offered by us:
Office Guards
They provide surveillance and protection services for persons and property in an office environment. They have a three fold mission: reception, observation and control. Reception involves escorting and guidance of visitors, delivery of badges and managing telephone calls. Observation includes regulation of movement of staff and visitors and their vehicles. Control involves management of keys, badges and electronic security systems. To facilitate integration into the client’s environment, while keeping necessary distance essential for the security mission, office guards are chosen for their sociability, courtesy and presentation.
Industrial Guards
They provide surveillance of persons, equipment and goods in an industrial environment aimed at prevention of losses and maintenance of production flows. We ensure that the guards are physically robust, have a sense of responsibility and possess all round communication skills. Their typical assignments are physical access control, personnel checks, and management of visitors, reception and routing of goods, management of electronic alarms and CCTV and external & internal prevention rounds.
Executive Protection
VIP security services provide professional personal security to Captains of the Industry, diplomats and celebrities. A security assessment of the client, his/her family, home and work environment is conducted. The risks can vary from violation of privacy, unwanted media exposure to threat to life and property. Services provided include security drivers, personal bodyguard, escort teams (several bodyguards) and residential security teams for permanent/temporary residences, offices, venues, holiday resorts and high profile events. VIP personal bodyguards are trained in martial arts and use of firearms. They are young, motivated, disciplined & well groomed and can operate unobtrusively in any environment. We are proud to state that “Ms Julia Roberts” the renowned Hollywood actor has been one of our esteemed client. We earned laurels from print & electronics media on this important & challenging assignment.
Retail Security Services
Retail security aims to reduce losses incurred by shopkeepers and distributors as a result of theft in premises. The bouquet constitutes uniformed guards at the entry for deterrence and shop inspectors inside the shop in plain clothes. Electronic surveillance further strengthens the vigilance. This is a specialized activity and security personnel are selected for their social skills, strength of character and observance of strict, ethical rules and procedures.
Event Security Services
These services provide security to fairs, exhibitions, film shooting and entertainment events. The service includes security at the parking, access control at entry points, security in main premises and perimeter access checks.


Greetings !!
To Know about me, Please Visit:
Github
|
LinkedIn
Nikhil Kuyya
Thank you for visiting this website, Page is under developement.
The Cat is coding the webiste. We will be right back in a week or so.
CAT
Stck Figure of a Cat.


Spysol
This Spider-like card game requires Javascript.
Foundation =
0
/ 104 (
0
%)
Stock =
0
Draw
New Game
You win!


My Journey
Timeline
1999-01-31
Born in Zhengzhou, a small city located in central part of China.
2015-07-21
Arrived in Boston, Massachusetts. This was the first time I came to the US.
2015-09-01
Studied in Hamden, Connecticut. I spent 3 years of my high school life here.
2018-08-24
Moved to Brooklyn, New York. Declared my major as CS, I'm currently pursuing a bachelor degree at NYU.
2019-08-09
Traveled to Shanghai, China during last summer. I like to go to Shanghai a lot when I went back home.
2020-01-15
Traveled to Los Angeles, California during last winter. Visited Disneyland Park and several museums in downtown LA.


Activities on Paradise Island
When you're not relaxing, enjoy these activities
Zipline across the island
Float in the lazy river
Hike the forest trails
Visit our one-of-a-kind sports facility
Return to main page


Guides and Grid tab have one option, Grid.
Grid part is used to set various options like Style, Grid line dimension, Grid line color, Subdivisions, Show grid, Show minor lines of grid.
Style, sets line style of Grid major and minor lines. It can be: Lines, Dashed lines and Dots.
Grid line every, sets how often grid line appears and what is the part between two lines in measuring unit you set.
Subdivisions, sets number of minor lines between two major lines.
Show grid, if checked shows grid if not hides grid.
Show minor lines, if checked grid will be divided in to minor lines, if not grid will show only major lines.
Color box is used to set color of the grid lines both Major and Minor.