Flurry Class Reference
| Inherits from | NSObject |
| Declared in | Flurry.h |
Tasks
Pre-Session Calls
-
+ setAppVersion:
@brief Explicitly specifies the App Version that Flurry will use to group Analytics data.
-
+ getFlurryAgentVersion
@brief Retrieves the Flurry Agent Build Version.
-
+ setShowErrorInLogEnabled:
@brief Displays an exception in the debug log if thrown during a Session.
-
+ setDebugLogEnabled:
@brief Generates debug logs to console.
-
+ setLogLevel:
@brief Generates debug logs to console.
-
+ setSessionContinueSeconds:
@brief Set the timeout for expiring a Flurry session.
-
+ setSecureTransportEnabled:
@brief Send data over a secure transport.
-
+ setCrashReportingEnabled:
@brief Enable automatic collection of crash reports.
-
+ startSession:
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 2.6 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching. The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- Crash reporting will not be enabled. See #setCrashReportingEnabled: for
- more information. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (void)applicationDidFinishLaunching:(UIApplication *)application { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY”]; // …. }
- @endcode *
- @param apiKey The API key for this project.
-
+ startSession:withOptions:
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 4.0.8 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching passing in the launchOptions param.
- The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (BOOL) application:(UIApplication )application didFinishLaunchingWithOptions:(NSDictionary )launchOptions { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY” withOptions:launchOptions]; // …. }
- @endcode *
- @param apiKey The API key for this project.
- @param options passed launchOptions from the applicatin’s didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
-
+ pauseBackgroundSession
- @brief Pauses a Flurry session.
- @since 4.2.2 *
- This method is useful in case of #setBackgroundSessionEnabled: set to YES. It can be
- called when application finished all background tasks (such as playing music) to pause session.
- If the app is resumed before time specified in #setSessionContinueSeconds:,
- the session will continue, otherwise a new session will begin. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout.
- @see #setBackgroundSessionEnabled: for details on setting a custom behaviour on resigning activity. *
- @code
- (void)allBackgroundTasksFinished { // …. [Flurry pauseBackgroundSession]; // …. }
- @endcode *
Event and Error Logging
-
+ logEvent:
- @brief Records a custom event specified by @c eventName.
- @since 2.8.4 *
- This method allows you to specify custom events within your app. As a general rule
- you should capture events related to user navigation within your app, any action
- around monetization, and other events as they are applicable to tracking progress
- towards your business goals. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:) or events with parameters
- (#logEvent:withParameters:). This provides valuable information around the time the user
- spends within an action (e.g. – time spent on a level or viewing a page) or characteristics
- of an action (e.g. – Buy Event that has a Parameter of Widget with Value Golden Sword). *
- @see #logEvent:withParameters: for details on storing events with parameters. \n
logEvent:timed: for details on storing timed events. \n
logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)interestingAppAction { [Flurry logEvent:@“Interesting_Action”]; // Perform interesting action }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
-
+ logEvent:withParameters:
- @brief Records a custom parameterized event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to associate parameters with an event. Parameters
- are extremely valuable as they allow you to store characteristics of an action. For example,
- if a user purchased an item it may be helpful to know what level that user was on.
- By setting this parameter you will be able to view a distribution of levels for the purcahsed
- event on the Flurrly Dev Portal. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- A maximum of 10 parameter names may be associated with any event. Sending
- over 10 parameter names with a single event will result in no parameters being logged
- for that event. You may specify an infinite number of Parameter values. For example,
- a Search Box would have 1 parameter name (e.g. – Search Box) and many values, which would
- allow you to see what values users look for the most in your app. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:). This provides valuable information
- around the time the user spends within an action (e.g. – time spent on a level or
- viewing a page). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)userPurchasedSomethingCool { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“Cool Item”, // Parameter Value @“Item Purchased”, // Parameter Name nil]; [Flurry logEvent:@“Something Cool Purchased” withParameters:params]; // Give user cool item }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param parameters A map containing Name-Value pairs of parameters.
-
+ logError:message:exception:
- @brief Records an app exception. Commonly used to catch unhandled exceptions.
- @since 2.7 *
- This method captures an exception for reporting to Flurry. We recommend adding an uncaught
- exception listener to capture any exceptions that occur during usage that is not
- anticipated by your app. *
- @see #logError:message:error: for details on capturing errors. *
- @code
- (void) uncaughtExceptionHandler(NSException *exception) { [Flurry logError:@“Uncaught” message:@“Crash!” exception:exception]; }
-
+ logError:message:error:
- @brief Records an app error.
- @since 2.7 *
- This method captures an error for reporting to Flurry. *
- @see #logError:message:exception: for details on capturing exceptions. *
- @code
- (void) webView:(UIWebView )webView didFailLoadWithError:(NSError )error { [Flurry logError:@“WebView No Load” message:[error localizedDescription] error:error]; }
- @endcode *
- @param errorID Name of the error.
- @param message The message to associate with the error.
- @param error The error object to report.
-
+ logEvent:timed:
- @brief Records a timed event specified by @c eventName.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event. This can
- be extremely valuable to understand the level of engagement with a particular action. For
- example, you can capture how long a user spends on a level or reading an article. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use parameters with your timed
- events (#logEvent:withParameters:timed:). This provides valuable information
- around the characteristics of an action (e.g. – Buy Event that has a Parameter of Widget with
- Value Golden Sword). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { [Flurry logEvent:@“Level Played” timed:YES]; // Start user on level }
-
+ logEvent:withParameters:timed:
- @brief Records a custom parameterized timed event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event with parameters.
- This can be extremely valuable to understand the level of engagement with a particular action
- and the characteristics associated with that action. For example, you can capture how long a user
- spends on a level or reading an article. Parameters can be used to capture, for example, the
- author of an article or if something was purchased while on the level. *
- @note You should not pass private or confidential information about your users in a
- custom event. *
- @see #endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
-
+ endTimedEvent:withParameters:
- @brief Ends a timed event specified by @c eventName and optionally updates parameters with @c parameters.
- @since 2.8.4 *
- This method ends an existing timed event. If parameters are provided, this will overwrite existing
- parameters with the same name or create new parameters if the name does not exist in the parameter
- map set by #logEvent:withParameters:timed:. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- If the app is backgrounded prior to ending a timed event, the Flurry SDK will automatically
- end the timer on the event. \n
endTimedEvent:withParameters: is ignored if called on a previously
- terminated event. *
- @see #logEvent:withParameters:timed: for details on starting a timed event with parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
Page View Methods
-
+ logAllPageViews:
- @brief Automatically track page views on a @c UINavigationController or @c UITabBarController.
- @since 2.7 *
- This method increments the page view count for a session based on traversing a UINavigationController
- or UITabBarController. The page view count is only a counter for the number of transitions in your
- app. It does not associate a name with the page count. To associate a name with a count of occurences
- see #logEvent:. *
- @note Please make sure you assign the Tab and Navigation controllers to the view controllers before
- passing them to this method. *
- @see #logPageView for details on explictly incrementing page view count. *
- @code
- –(void) trackViewsFromTabBar:(UITabBarController*) tabBar { [Flurry logAllPageViews:tabBar]; }
- @endcode *
- @param target The navigation or tab bar controller.
-
+ logPageView
- @brief Explicitly track a page view during a session.
- @since 2.7 *
- This method increments the page view count for a session when invoked. It does not associate a name
- with the page count. To associate a name with a count of occurences see #logEvent:. *
- @see #logAllPageViews for details on automatically incrementing page view count based on user
- traversing navigation or tab bar controller. *
- @code
- –(void) trackView { [Flurry logPageView]; }
- @endcode *
User Info
-
+ setUserID:
@brief Assign a unique id for a user in your app.
-
+ setAge:
@brief Set your user’s age in years.
-
+ setGender:
@brief Set your user’s gender.
Location Reporting
-
+ setLatitude:longitude:horizontalAccuracy:verticalAccuracy:
- @brief Set the location of the session.
- @since 2.7 *
- Use information from the CLLocationManager to specify the location of the session. Flurry does not
- automatically track this information or include the CLLocation framework. *
- @note Only the last location entered is captured per session. \n
- Regardless of accuracy specified, the Flurry SDK will only report location at city level or higher. \n
- Location is aggregated across all users of your app and not available on a per user basis. \n
- This information should only be captured if it is germaine to the use of your app. *
- @code CLLocationManager *locationManager = [[CLLocationManager alloc] init]; [locationManager startUpdatingLocation];
- @endcode *
- After starting the location manager, you can set the location with Flurry. You can implement
- CLLocationManagerDelegate to be aware of when the location is updated. Below is an example
- of how to use this method, after you have recieved a location update from the locationManager. *
- @code CLLocation *location = locationManager.location; [Flurry setLatitude:location.coordinate.latitude longitude:location.coordinate.longitude horizontalAccuracy:location.horizontalAccuracy verticalAccuracy:location.verticalAccuracy];
- @endcode
- @param latitude The latitude.
- @param longitude The longitude.
- @param horizontalAccuracy The radius of uncertainty for the location in meters.
- @param verticalAccuracy The accuracy of the altitude value in meters. *
Session Reporting Calls
-
+ setSessionReportsOnCloseEnabled:
@brief Set session to report when app closes.
-
+ setSessionReportsOnPauseEnabled:
@brief Set session to report when app is sent to the background.
-
+ setBackgroundSessionEnabled:
@brief Set session to support background execution.
-
+ setEventLoggingEnabled:
@brief Enable custom event logging.
-
+ setPushToken:
@brief Set device push token.
Class Methods
endTimedEvent:withParameters:
- @brief Ends a timed event specified by @c eventName and optionally updates parameters with @c parameters.
- @since 2.8.4 *
- This method ends an existing timed event. If parameters are provided, this will overwrite existing
- parameters with the same name or create new parameters if the name does not exist in the parameter
- map set by #logEvent:withParameters:timed:. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- If the app is backgrounded prior to ending a timed event, the Flurry SDK will automatically
- end the timer on the event. \n
endTimedEvent:withParameters: is ignored if called on a previously
- terminated event. *
- @see #logEvent:withParameters:timed: for details on starting a timed event with parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
+ (void)endTimedEvent:(NSString *)eventName withParameters:(NSDictionary *)parameters
Discussion
- @brief Ends a timed event specified by @c eventName and optionally updates parameters with @c parameters.
- @since 2.8.4 *
- This method ends an existing timed event. If parameters are provided, this will overwrite existing
- parameters with the same name or create new parameters if the name does not exist in the parameter
- map set by #logEvent:withParameters:timed:. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- If the app is backgrounded prior to ending a timed event, the Flurry SDK will automatically
- end the timer on the event. \n
endTimedEvent:withParameters: is ignored if called on a previously
- terminated event. *
- @see #logEvent:withParameters:timed: for details on starting a timed event with parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
[Flurry logEvent:@“Level Played” withParameters:params timed:YES]; // Start user on level }
- (void)endLevel { // User gained additional 100 points in Level NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“200”, // Parameter Value @“Current Points”, // Parameter Name nil]; [Flurry endTimedEvent:@“Level Played” withParameters:params]; // User done with level }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param parameters A map containing Name-Value pairs of parameters.
Declared In
Flurry.h
getFlurryAgentVersion
@brief Retrieves the Flurry Agent Build Version.
+ (NSString *)getFlurryAgentVersion
Return Value
The agent version of the Flurry SDK.
Availability
2.7
This is an optional method that retrieves the Flurry Agent Version the app is running under. It is most often used if reporting an unexpected behavior of the SDK to Flurry Support
Discussion
@brief Retrieves the Flurry Agent Build Version.
Note: This method must be called prior to invoking #startSession:. \n FAQ for the iPhone SDK is located at Support Center – iPhone FAQ.
See Also
+ setLogLevel: for information on how to view debugging information on your console.
Declared In
Flurry.h
logAllPageViews:
- @brief Automatically track page views on a @c UINavigationController or @c UITabBarController.
- @since 2.7 *
- This method increments the page view count for a session based on traversing a UINavigationController
- or UITabBarController. The page view count is only a counter for the number of transitions in your
- app. It does not associate a name with the page count. To associate a name with a count of occurences
- see #logEvent:. *
- @note Please make sure you assign the Tab and Navigation controllers to the view controllers before
- passing them to this method. *
- @see #logPageView for details on explictly incrementing page view count. *
- @code
- –(void) trackViewsFromTabBar:(UITabBarController*) tabBar { [Flurry logAllPageViews:tabBar]; }
- @endcode *
- @param target The navigation or tab bar controller.
+ (void)logAllPageViews:(id)target
Discussion
- @brief Automatically track page views on a @c UINavigationController or @c UITabBarController.
- @since 2.7 *
- This method increments the page view count for a session based on traversing a UINavigationController
- or UITabBarController. The page view count is only a counter for the number of transitions in your
- app. It does not associate a name with the page count. To associate a name with a count of occurences
- see #logEvent:. *
- @note Please make sure you assign the Tab and Navigation controllers to the view controllers before
- passing them to this method. *
- @see #logPageView for details on explictly incrementing page view count. *
- @code
- –(void) trackViewsFromTabBar:(UITabBarController*) tabBar { [Flurry logAllPageViews:tabBar]; }
- @endcode *
- @param target The navigation or tab bar controller.
Declared In
Flurry.h
logError:message:error:
- @brief Records an app error.
- @since 2.7 *
- This method captures an error for reporting to Flurry. *
- @see #logError:message:exception: for details on capturing exceptions. *
- @code
- (void) webView:(UIWebView )webView didFailLoadWithError:(NSError )error { [Flurry logError:@“WebView No Load” message:[error localizedDescription] error:error]; }
- @endcode *
- @param errorID Name of the error.
- @param message The message to associate with the error.
- @param error The error object to report.
+ (void)logError:(NSString *)errorID message:(NSString *)message error:(NSError *)error
Discussion
- @brief Records an app error.
- @since 2.7 *
- This method captures an error for reporting to Flurry. *
- @see #logError:message:exception: for details on capturing exceptions. *
- @code
- (void) webView:(UIWebView )webView didFailLoadWithError:(NSError )error { [Flurry logError:@“WebView No Load” message:[error localizedDescription] error:error]; }
- @endcode *
- @param errorID Name of the error.
- @param message The message to associate with the error.
- @param error The error object to report.
Declared In
Flurry.h
logError:message:exception:
- @brief Records an app exception. Commonly used to catch unhandled exceptions.
- @since 2.7 *
- This method captures an exception for reporting to Flurry. We recommend adding an uncaught
- exception listener to capture any exceptions that occur during usage that is not
- anticipated by your app. *
- @see #logError:message:error: for details on capturing errors. *
- @code
- (void) uncaughtExceptionHandler(NSException *exception) { [Flurry logError:@“Uncaught” message:@“Crash!” exception:exception]; }
+ (void)logError:(NSString *)errorID message:(NSString *)message exception:(NSException *)exception
Discussion
- @brief Records an app exception. Commonly used to catch unhandled exceptions.
- @since 2.7 *
- This method captures an exception for reporting to Flurry. We recommend adding an uncaught
- exception listener to capture any exceptions that occur during usage that is not
- anticipated by your app. *
- @see #logError:message:error: for details on capturing errors. *
- @code
- (void) uncaughtExceptionHandler(NSException *exception) { [Flurry logError:@“Uncaught” message:@“Crash!” exception:exception]; }
(void)applicationDidFinishLaunching:(UIApplication *)application { NSSetUncaughtExceptionHandler(&uncaughtExceptionHandler); [Flurry startSession:@“YOUR_API_KEY”]; // …. }
- @endcode *
- @param errorID Name of the error.
- @param message The message to associate with the error.
- @param exception The exception object to report.
Declared In
Flurry.h
logEvent:
- @brief Records a custom event specified by @c eventName.
- @since 2.8.4 *
- This method allows you to specify custom events within your app. As a general rule
- you should capture events related to user navigation within your app, any action
- around monetization, and other events as they are applicable to tracking progress
- towards your business goals. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:) or events with parameters
- (#logEvent:withParameters:). This provides valuable information around the time the user
- spends within an action (e.g. – time spent on a level or viewing a page) or characteristics
- of an action (e.g. – Buy Event that has a Parameter of Widget with Value Golden Sword). *
- @see #logEvent:withParameters: for details on storing events with parameters. \n
logEvent:timed: for details on storing timed events. \n
logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)interestingAppAction { [Flurry logEvent:@“Interesting_Action”]; // Perform interesting action }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
+ (void)logEvent:(NSString *)eventName
Discussion
- @brief Records a custom event specified by @c eventName.
- @since 2.8.4 *
- This method allows you to specify custom events within your app. As a general rule
- you should capture events related to user navigation within your app, any action
- around monetization, and other events as they are applicable to tracking progress
- towards your business goals. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:) or events with parameters
- (#logEvent:withParameters:). This provides valuable information around the time the user
- spends within an action (e.g. – time spent on a level or viewing a page) or characteristics
- of an action (e.g. – Buy Event that has a Parameter of Widget with Value Golden Sword). *
- @see #logEvent:withParameters: for details on storing events with parameters. \n
logEvent:timed: for details on storing timed events. \n
logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)interestingAppAction { [Flurry logEvent:@“Interesting_Action”]; // Perform interesting action }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
Declared In
Flurry.h
logEvent:timed:
- @brief Records a timed event specified by @c eventName.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event. This can
- be extremely valuable to understand the level of engagement with a particular action. For
- example, you can capture how long a user spends on a level or reading an article. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use parameters with your timed
- events (#logEvent:withParameters:timed:). This provides valuable information
- around the characteristics of an action (e.g. – Buy Event that has a Parameter of Widget with
- Value Golden Sword). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { [Flurry logEvent:@“Level Played” timed:YES]; // Start user on level }
+ (void)logEvent:(NSString *)eventName timed:(BOOL)timed
Discussion
- @brief Records a timed event specified by @c eventName.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event. This can
- be extremely valuable to understand the level of engagement with a particular action. For
- example, you can capture how long a user spends on a level or reading an article. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- Where applicable, you should make a concerted effort to use parameters with your timed
- events (#logEvent:withParameters:timed:). This provides valuable information
- around the characteristics of an action (e.g. – Buy Event that has a Parameter of Widget with
- Value Golden Sword). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { [Flurry logEvent:@“Level Played” timed:YES]; // Start user on level }
(void)endLevel { [Flurry endTimedEvent:@“Level Played” withParameters:nil]; // User done with level }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param timed Specifies the event will be timed.
Declared In
Flurry.h
logEvent:withParameters:
- @brief Records a custom parameterized event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to associate parameters with an event. Parameters
- are extremely valuable as they allow you to store characteristics of an action. For example,
- if a user purchased an item it may be helpful to know what level that user was on.
- By setting this parameter you will be able to view a distribution of levels for the purcahsed
- event on the Flurrly Dev Portal. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- A maximum of 10 parameter names may be associated with any event. Sending
- over 10 parameter names with a single event will result in no parameters being logged
- for that event. You may specify an infinite number of Parameter values. For example,
- a Search Box would have 1 parameter name (e.g. – Search Box) and many values, which would
- allow you to see what values users look for the most in your app. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:). This provides valuable information
- around the time the user spends within an action (e.g. – time spent on a level or
- viewing a page). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)userPurchasedSomethingCool { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“Cool Item”, // Parameter Value @“Item Purchased”, // Parameter Name nil]; [Flurry logEvent:@“Something Cool Purchased” withParameters:params]; // Give user cool item }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param parameters A map containing Name-Value pairs of parameters.
+ (void)logEvent:(NSString *)eventName withParameters:(NSDictionary *)parameters
Discussion
- @brief Records a custom parameterized event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to associate parameters with an event. Parameters
- are extremely valuable as they allow you to store characteristics of an action. For example,
- if a user purchased an item it may be helpful to know what level that user was on.
- By setting this parameter you will be able to view a distribution of levels for the purcahsed
- event on the Flurrly Dev Portal. *
- @note You should not pass private or confidential information about your users in a
- custom event. \n
- A maximum of 10 parameter names may be associated with any event. Sending
- over 10 parameter names with a single event will result in no parameters being logged
- for that event. You may specify an infinite number of Parameter values. For example,
- a Search Box would have 1 parameter name (e.g. – Search Box) and many values, which would
- allow you to see what values users look for the most in your app. \n
- Where applicable, you should make a concerted effort to use timed events with
- parameters (#logEvent:withParameters:timed:). This provides valuable information
- around the time the user spends within an action (e.g. – time spent on a level or
- viewing a page). *
- @see #logEvent:withParameters:timed: for details on storing timed events with parameters. \n
endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)userPurchasedSomethingCool { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“Cool Item”, // Parameter Value @“Item Purchased”, // Parameter Name nil]; [Flurry logEvent:@“Something Cool Purchased” withParameters:params]; // Give user cool item }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param parameters A map containing Name-Value pairs of parameters.
Declared In
Flurry.h
logEvent:withParameters:timed:
- @brief Records a custom parameterized timed event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event with parameters.
- This can be extremely valuable to understand the level of engagement with a particular action
- and the characteristics associated with that action. For example, you can capture how long a user
- spends on a level or reading an article. Parameters can be used to capture, for example, the
- author of an article or if something was purchased while on the level. *
- @note You should not pass private or confidential information about your users in a
- custom event. *
- @see #endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
+ (void)logEvent:(NSString *)eventName withParameters:(NSDictionary *)parameters timed:(BOOL)timed
Discussion
- @brief Records a custom parameterized timed event specified by @c eventName with @c parameters.
- @since 2.8.4 *
- This method overrides #logEvent to allow you to capture the length of an event with parameters.
- This can be extremely valuable to understand the level of engagement with a particular action
- and the characteristics associated with that action. For example, you can capture how long a user
- spends on a level or reading an article. Parameters can be used to capture, for example, the
- author of an article or if something was purchased while on the level. *
- @note You should not pass private or confidential information about your users in a
- custom event. *
- @see #endTimedEvent:withParameters: for details on stopping a timed event and (optionally) updating
- parameters. *
- @code
- (void)startLevel { NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“100”, // Parameter Value @“Current Points”, // Parameter Name nil];
[Flurry logEvent:@“Level Played” withParameters:params timed:YES]; // Start user on level }
- (void)endLevel { // User gained additional 100 points in Level NSDictionary *params = [NSDictionary dictionaryWithObjectsAndKeys:@“200”, // Parameter Value @“Current Points”, // Parameter Name nil]; [Flurry endTimedEvent:@“Level Played” withParameters:params]; // User done with level }
- @endcode *
- @param eventName Name of the event. For maximum effectiveness, we recommend using a naming scheme
- that can be easily understood by non-technical people in your business domain.
- @param parameters A map containing Name-Value pairs of parameters.
- @param timed Specifies the event will be timed.
Declared In
Flurry.h
logPageView
- @brief Explicitly track a page view during a session.
- @since 2.7 *
- This method increments the page view count for a session when invoked. It does not associate a name
- with the page count. To associate a name with a count of occurences see #logEvent:. *
- @see #logAllPageViews for details on automatically incrementing page view count based on user
- traversing navigation or tab bar controller. *
- @code
- –(void) trackView { [Flurry logPageView]; }
- @endcode *
+ (void)logPageView
Discussion
- @brief Explicitly track a page view during a session.
- @since 2.7 *
- This method increments the page view count for a session when invoked. It does not associate a name
- with the page count. To associate a name with a count of occurences see #logEvent:. *
- @see #logAllPageViews for details on automatically incrementing page view count based on user
- traversing navigation or tab bar controller. *
- @code
- –(void) trackView { [Flurry logPageView]; }
- @endcode *
Declared In
Flurry.h
pauseBackgroundSession
- @brief Pauses a Flurry session.
- @since 4.2.2 *
- This method is useful in case of #setBackgroundSessionEnabled: set to YES. It can be
- called when application finished all background tasks (such as playing music) to pause session.
- If the app is resumed before time specified in #setSessionContinueSeconds:,
- the session will continue, otherwise a new session will begin. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout.
- @see #setBackgroundSessionEnabled: for details on setting a custom behaviour on resigning activity. *
- @code
- (void)allBackgroundTasksFinished { // …. [Flurry pauseBackgroundSession]; // …. }
- @endcode *
+ (void)pauseBackgroundSession
Discussion
- @brief Pauses a Flurry session.
- @since 4.2.2 *
- This method is useful in case of #setBackgroundSessionEnabled: set to YES. It can be
- called when application finished all background tasks (such as playing music) to pause session.
- If the app is resumed before time specified in #setSessionContinueSeconds:,
- the session will continue, otherwise a new session will begin. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout.
- @see #setBackgroundSessionEnabled: for details on setting a custom behaviour on resigning activity. *
- @code
- (void)allBackgroundTasksFinished { // …. [Flurry pauseBackgroundSession]; // …. }
- @endcode *
Declared In
Flurry.h
setAge:
@brief Set your user’s age in years.
+ (void)setAge:(int)age
Parameters
- age
Reported age of user.
Availability
2.7
Use this method to capture the age of your user. Only use this method if you collect this information explictly from your user (i.e. – there is no need to set a default value).
Discussion
@brief Set your user’s age in years.
Note: The age is aggregated across all users of your app and not available on a per user basis.
Declared In
Flurry.h
setAppVersion:
@brief Explicitly specifies the App Version that Flurry will use to group Analytics data.
+ (void)setAppVersion:(NSString *)version
Parameters
- version
The custom version name.
Availability
2.7
This is an optional method that overrides the App Version Flurry uses for reporting. Flurry will use the CFBundleVersion in your info.plist file when this method is not invoked.
Discussion
@brief Explicitly specifies the App Version that Flurry will use to group Analytics data.
Note: There is a maximum of 605 versions allowed for a single app. \n This method must be called prior to invoking #startSession:.
Declared In
Flurry.h
setBackgroundSessionEnabled:
@brief Set session to support background execution.
+ (void)setBackgroundSessionEnabled:(BOOL)setBackgroundSessionEnabled
Parameters
- setBackgroundSessionEnabled
NO to finish on resigning active, YES to omit finishing.
Availability
4.2.2
Use this method finish session data when the app is paused. The default value is taken looking at the UIBackgroundModes of application’s Info.plist. If UIBackgroundModes array is empty, equals @c NO, otherwise @c YES.
Discussion
@brief Set session to support background execution.
Declared In
Flurry.h
setCrashReportingEnabled:
@brief Enable automatic collection of crash reports.
+ (void)setCrashReportingEnabled:(BOOL)value
Parameters
- value
@c YES to enable collection of crash reports.
Availability
4.1
This is an optional method that collects crash reports when enabled. The default value is @c NO.
Discussion
@brief Enable automatic collection of crash reports.
Note: This method must be called prior to invoking #startSession:.
Declared In
Flurry.h
setDebugLogEnabled:
@brief Generates debug logs to console.
+ (void)setDebugLogEnabled:(BOOL)value
Parameters
- value
@c YES to show debug logs, @c NO to omit debug logs.
Availability
2.7
This is an optional method that displays debug information related to the Flurry SDK. display information to the console. The default setting for this method is @c NO which sets the log level to @c FlurryLogLevelCriticalOnly. When set to @c YES the debug log level is set to @c FlurryLogLevelDebug
Discussion
@brief Generates debug logs to console.
Note: This method must be called prior to invoking #startSession:. If the method, setLogLevel is called later in the code, debug logging will be automatically enabled.
Declared In
Flurry.h
setEventLoggingEnabled:
@brief Enable custom event logging.
+ (void)setEventLoggingEnabled:(BOOL)value
Parameters
- value
YES to enable event logging, NO to stop custom logging.
Availability
2.7
Use this method to allow the capture of custom events. The default value is @c YES.
Discussion
@brief Enable custom event logging.
Declared In
Flurry.h
setGender:
@brief Set your user’s gender.
+ (void)setGender:(NSString *)gender
Parameters
- gender
Reported gender of user.
Availability
2.7
Use this method to capture the gender of your user. Only use this method if you collect this information explictly from your user (i.e. – there is no need to set a default value). Allowable values are @c @“m” or @c @“f”
Discussion
@brief Set your user’s gender.
Note: The gender is aggregated across all users of your app and not available on a per user basis.
Declared In
Flurry.h
setLatitude:longitude:horizontalAccuracy:verticalAccuracy:
- @brief Set the location of the session.
- @since 2.7 *
- Use information from the CLLocationManager to specify the location of the session. Flurry does not
- automatically track this information or include the CLLocation framework. *
- @note Only the last location entered is captured per session. \n
- Regardless of accuracy specified, the Flurry SDK will only report location at city level or higher. \n
- Location is aggregated across all users of your app and not available on a per user basis. \n
- This information should only be captured if it is germaine to the use of your app. *
- @code CLLocationManager *locationManager = [[CLLocationManager alloc] init]; [locationManager startUpdatingLocation];
- @endcode *
- After starting the location manager, you can set the location with Flurry. You can implement
- CLLocationManagerDelegate to be aware of when the location is updated. Below is an example
- of how to use this method, after you have recieved a location update from the locationManager. *
- @code CLLocation *location = locationManager.location; [Flurry setLatitude:location.coordinate.latitude longitude:location.coordinate.longitude horizontalAccuracy:location.horizontalAccuracy verticalAccuracy:location.verticalAccuracy];
- @endcode
- @param latitude The latitude.
- @param longitude The longitude.
- @param horizontalAccuracy The radius of uncertainty for the location in meters.
- @param verticalAccuracy The accuracy of the altitude value in meters. *
+ (void)setLatitude:(double)latitude longitude:(double)longitude horizontalAccuracy:(float)horizontalAccuracy verticalAccuracy:(float)verticalAccuracy
Discussion
- @brief Set the location of the session.
- @since 2.7 *
- Use information from the CLLocationManager to specify the location of the session. Flurry does not
- automatically track this information or include the CLLocation framework. *
- @note Only the last location entered is captured per session. \n
- Regardless of accuracy specified, the Flurry SDK will only report location at city level or higher. \n
- Location is aggregated across all users of your app and not available on a per user basis. \n
- This information should only be captured if it is germaine to the use of your app. *
- @code CLLocationManager *locationManager = [[CLLocationManager alloc] init]; [locationManager startUpdatingLocation];
- @endcode *
- After starting the location manager, you can set the location with Flurry. You can implement
- CLLocationManagerDelegate to be aware of when the location is updated. Below is an example
- of how to use this method, after you have recieved a location update from the locationManager. *
- @code CLLocation *location = locationManager.location; [Flurry setLatitude:location.coordinate.latitude longitude:location.coordinate.longitude horizontalAccuracy:location.horizontalAccuracy verticalAccuracy:location.verticalAccuracy];
- @endcode
- @param latitude The latitude.
- @param longitude The longitude.
- @param horizontalAccuracy The radius of uncertainty for the location in meters.
- @param verticalAccuracy The accuracy of the altitude value in meters. *
Declared In
Flurry.h
setLogLevel:
@brief Generates debug logs to console.
+ (void)setLogLevel:(FlurryLogLevel)value
Parameters
- value
Log level
Availability
4.2.2
This is an optional method that displays debug information related to the Flurry SDK. display information to the console. The default setting for this method is @c FlurryLogLevelCritycalOnly.
Discussion
@brief Generates debug logs to console.
Note: Its good practice to call this method prior to invoking #startSession:. If debug logging is disabled earlier, this method will enable it.
Declared In
Flurry.h
setPushToken:
@brief Set device push token.
+ (void)setPushToken:(NSString *)pushToken
Availability
2.7
After the device has successfully registered with APNS, call this method to set the push token received from APNS.
Discussion
@brief Set device push token.
Declared In
Flurry.h
setSecureTransportEnabled:
@brief Send data over a secure transport.
+ (void)setSecureTransportEnabled:(BOOL)value
Parameters
- value
@c YES to send data over secure connection.
Availability
3.0
This is an optional method that sends data over an SSL connection when enabled. The default value is @c NO.
Discussion
@brief Send data over a secure transport.
Note: This method must be called prior to invoking #startSession:.
Declared In
Flurry.h
setSessionContinueSeconds:
@brief Set the timeout for expiring a Flurry session.
+ (void)setSessionContinueSeconds:(int)seconds
Parameters
- seconds
The time in seconds to set the session timeout to.
Availability
2.7
This is an optional method that sets the time the app may be in the background before starting a new session upon resume. The default value for the session timeout is 10 seconds in the background.
Discussion
@brief Set the timeout for expiring a Flurry session.
Note: This method must be called prior to invoking #startSession:.
Declared In
Flurry.h
setSessionReportsOnCloseEnabled:
@brief Set session to report when app closes.
+ (void)setSessionReportsOnCloseEnabled:(BOOL)sendSessionReportsOnClose
Parameters
- sendSessionReportsOnClose
YES to send on close, NO to omit reporting on close.
Availability
2.7
Use this method report session data when the app is closed. The default value is @c YES.
Discussion
@brief Set session to report when app closes.
Note: This method is rarely invoked in iOS >= 3.2 due to the updated iOS lifecycle.
See Also
Declared In
Flurry.h
setSessionReportsOnPauseEnabled:
@brief Set session to report when app is sent to the background.
+ (void)setSessionReportsOnPauseEnabled:(BOOL)setSessionReportsOnPauseEnabled
Parameters
- setSessionReportsOnPauseEnabled
YES to send on pause, NO to omit reporting on pause.
Availability
2.7
Use this method report session data when the app is paused. The default value is @c YES.
Discussion
@brief Set session to report when app is sent to the background.
Declared In
Flurry.h
setShowErrorInLogEnabled:
@brief Displays an exception in the debug log if thrown during a Session.
+ (void)setShowErrorInLogEnabled:(BOOL)value
Parameters
- value
@c YES to show errors in debug logs, @c NO to omit errors in debug logs.
Availability
2.7
This is an optional method that augments the debug logs with exceptions that occur during the session. You must both capture exceptions to Flurry and set debug logging to enabled for this method to display information to the console. The default setting for this method is @c NO.
Discussion
@brief Displays an exception in the debug log if thrown during a Session.
Note: This method must be called prior to invoking #startSession:.
See Also
+ setLogLevel: for information on how to view debugging information on your console. \n
+ logError:message:exception: for details on logging exceptions. \n
+ logError:message:error: for details on logging errors.
Declared In
Flurry.h
setUserID:
@brief Assign a unique id for a user in your app.
+ (void)setUserID:(NSString *)userID
Parameters
- userID
The app id for a user.
Availability
2.7
Discussion
@brief Assign a unique id for a user in your app.
Note: Please be sure not to use this method to pass any private or confidential information about the user.
Declared In
Flurry.h
startSession:
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 2.6 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching. The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- Crash reporting will not be enabled. See #setCrashReportingEnabled: for
- more information. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (void)applicationDidFinishLaunching:(UIApplication *)application { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY”]; // …. }
- @endcode *
- @param apiKey The API key for this project.
+ (void)startSession:(NSString *)apiKey
Discussion
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 2.6 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching. The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- Crash reporting will not be enabled. See #setCrashReportingEnabled: for
- more information. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (void)applicationDidFinishLaunching:(UIApplication *)application { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY”]; // …. }
- @endcode *
- @param apiKey The API key for this project.
Declared In
Flurry.h
startSession:withOptions:
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 4.0.8 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching passing in the launchOptions param.
- The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (BOOL) application:(UIApplication )application didFinishLaunchingWithOptions:(NSDictionary )launchOptions { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY” withOptions:launchOptions]; // …. }
- @endcode *
- @param apiKey The API key for this project.
- @param options passed launchOptions from the applicatin’s didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
+ (void)startSession:(NSString *)apiKey withOptions:(id)options
Discussion
- @brief Start a Flurry session for the project denoted by @c apiKey.
- @since 4.0.8 *
- This method serves as the entry point to Flurry Analytics collection. It must be
- called in the scope of @c applicationDidFinishLaunching passing in the launchOptions param.
- The session will continue
- for the period the app is in the foreground until your app is backgrounded for the
- time specified in #setSessionContinueSeconds:. If the app is resumed in that period
- the session will continue, otherwise a new session will begin. *
- @note If testing on a simulator, please be sure to send App to background via home
- button. Flurry depends on the iOS lifecycle to be complete for full reporting. *
- @see #setSessionContinueSeconds: for details on setting a custom session timeout. *
- @code
- (BOOL) application:(UIApplication )application didFinishLaunchingWithOptions:(NSDictionary )launchOptions { // Optional Flurry startup methods [Flurry startSession:@“YOUR_API_KEY” withOptions:launchOptions]; // …. }
- @endcode *
- @param apiKey The API key for this project.
- @param options passed launchOptions from the applicatin’s didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
Declared In
Flurry.h


Bootstrap 3 Form Builder
1 Column
2 Columns
Copy HTML
Elements
Text Input
Example block-level help text here.
Password
Example block-level help text here.
Select
Option 1
Option 2
Option 3
Example block-level help text here.
File input
Example block-level help text here.
Button Group
Left
Middle
Right
Email
Remember me
Button
Drag & Drop elements to build form.


Howard Kurtz rips pundits, saying 'media creation' Beto O'Rourke 'never came close to living up to' hype
by Joshua NelsonFormer 2020 Democratic presidential candidate Beto O'Rourke’s magic dust was not so magic, Media Buzz host Howie Kurtz told “The Daily Briefing with Dana Perino.”
“The pundits essentially drafted this failed Senate candidate into the race. His campaign was always kind of a media creation, and Beto O’Rourke never came close to living up to all the hype,” Kurtz said.
O’Rourke announced last week that he is withdrawing from the 2020 presidential race, telling supporters: “it is clear to me now that this campaign does not have the means to move forward successfully.”
FORMER TEXAS CONGRESSMAN BETO O'ROURKE DROPS OUT OF 2020 PRESIDENTIAL RACE
O'Rourke entered the race in March to great fanfare after nearly defeating Texas incumbent Sen. Ted Cruz in the 2018 midterms, but he struggled to gain traction in the massive Democratic primary field.
“My service to the country will not be as a candidate or as the nominee,” O’Rourke wrote in a post on Medium. “Acknowledging this now is in the best interests of those in the campaign; it is in the best interests of this party as we seek to unify around a nominee, and it is in the best interests of the country.”
Kurtz said that O’Rourke’s campaign was disorganized and never stood for anything other than his personal charisma and gun control.
CLICK HERE TO GET THE FOX NEWS APP
O'Rourke sought to make gun control a top issue in his campaign, most notably after the Aug. 3 mass shooting in his hometown of El Paso. He went so far as to embrace the confiscation of certain firearms, memorably saying in a September debate, "Hell yes, we are going to take your AR-15."
Fox News' Vandana Rambaran and Alex Pappas contributed to this report.


This step will run TestComplete with a batch script. See TestComplete Command Line guide
here.
In general syntax is the following:
TestComplete.exe | TestExecute.exe [file_name [/run
[(/project:project_name) | (/project:project_name /projectitem:item_name) |
(/project:project_name /test:test_name) |
(/project:project_name /unit:unit_name /routine:routine_name)]
[/ExportLog:File_name] [/exit]]
[/SilentMode [/ErrorLog:File_name] [/ForceConversion]] ]
[Timeout:Time_in_seconds] [/ns] [/agpatcheroff]
You should provide
-
Path to TestComplete.exe or TestExecute.exe
-
Project or project suit to load
-
Space separated list of any other parameters
After finished click Generate Script button and verify result batch script. Visit
this page for script example.


Hello
Sign out
Search a Contact
Search contacts:
Filter By
First Name
Last Name
Email
Phone number
Created at
Add a Contact
First name
Last name
Email
Phone Number
Add Contact
Edit a Contact
First name
Last name
Email
Phone Number
Update Contact
List of Contacts


# Copyright Atos 2021
from qat.core import Term
[docs]def permute_fermionic_operator(fermionic_term, ind):
"""
Perform the permutation of the two operators in index ind and ind + 1 in a fermionic Term pauli string
Args:
fermionic_term (Term): the fermionic term which operators we seek to permute
ind (int): the lower index of the two consecutive creation or annihilation operators we seek to permute
Returns:
list_terms (list<Term>): the list of fermionic terms resulting of the permutation
"""
coeff = fermionic_term.coeff
pauli_op = fermionic_term.op
qbits = fermionic_term.qbits
if ind >= len(pauli_op) - 1:
raise IndexError
permuted_pauli_op = pauli_op[:ind] + pauli_op[ind + 1] + pauli_op[ind] + pauli_op[ind + 2:]
permuted_qbits = qbits[:]
permuted_qbits[ind], permuted_qbits[ind + 1] = permuted_qbits[ind + 1], permuted_qbits[ind]
if 'c' in pauli_op[ind : ind + 2] and 'C' in pauli_op[ind : ind + 2] and qbits[ind] == qbits[ind + 1]:
return [Term(coefficient=coeff, pauli_op=pauli_op[: ind] + pauli_op[ind + 2:], qbits=qbits[:ind] + qbits[ind + 2:]),
Term(coefficient=-coeff, pauli_op=permuted_pauli_op, qbits=permuted_qbits)]
else:
return [Term(coefficient=-coeff ,pauli_op=permuted_pauli_op , qbits=permuted_qbits)]
[docs]def order_qubits(fermionic_term):
"""
Takes a fermionic term which pauli_op is supposed to be ordered properly, and reorder it increasing qbit numbers
Args:
fermionic_term (Term): the term to reorder
Returns:
ordered_term (Term): the reordered term
"""
coeff = fermionic_term.coeff
pauli_op = fermionic_term.op
qbits = fermionic_term.qbits
ind_c = pauli_op.index("c")
qbits_C = qbits[:ind_c]
qbits_c = qbits[ind_c:]
new_qbits = []
for qbits_op in [qbits_C, qbits_c]:
qbits_temp = qbits_op[:]
ordered = False
while not ordered:
ind = 0
while ind < len(qbits_temp) - 1 and qbits_temp[ind] <= qbits_temp[ind + 1]:
if qbits_temp[ind] == qbits_temp[ind + 1]:
return
ind += 1
if ind < len(qbits_temp) - 1:
ind += 1
new_ind = 0
while qbits_temp[new_ind] < qbits_temp[ind]:
new_ind += 1
elt_not_in_order = qbits_temp.pop(ind)
qbits_temp.insert(new_ind, elt_not_in_order)
coeff *= (-1)**(ind - new_ind)
else:
ordered = True
new_qbits += qbits_temp
return Term(coefficient=coeff, pauli_op=pauli_op, qbits=new_qbits)
[docs]def order_fermionic_ops(fermionic_term):
"""
Order the operators list of a fermionic_term by putting the creations operators on the left and the annihilation operators on the right, with respect to the fermionic anticommutation relations.
Args:
fermionic_term (Term): the term to order
Returns:
ordered_fermionic_terms (list<Term>): the list of ordered fermionic terms
"""
coeff = fermionic_term.coeff
pauli_op = fermionic_term.op
qbits = fermionic_term.qbits
ind_c = pauli_op.index('c')
try:
ind_C = pauli_op[ind_c:].index('C') + ind_c
except ValueError:
new_terms = [fermionic_term]
ordered_pauli_op = True
else:
new_terms = []
for new_fermionic_term in permute_fermionic_operator(fermionic_term, ind_C - 1):
new_terms += order_fermionic_term(new_fermionic_term)
return new_terms
[docs]def order_fermionic_term(fermionic_term):
"""
Order any fermionic term by putting the creation operators on the left, ordered by increasing qubit numbers, and the annihilation operators on the right, ordered y increasing qubit numbers, with respect to the fermionic anticommutation relations.
Args:
fermionic_term (Term): the term to order
Returns:
ordered_fermionic_terms (list<Term>): the list of ordered fermionic terms
"""
new_terms = order_fermionic_ops(fermionic_term)
ordered_terms = []
for new_term in new_terms:
ordered_term = order_qubits(new_term)
if ordered_term:
ordered_terms.append(ordered_term)
return ordered_terms


{% extends 'base.html' %} {% load staticfiles %} {% block title%} Home {% endblock%} {% block content %}
Visit us for better services to the community at large.
This will speed up your building process, but you should always test your app on native emulators and devices. Type the following code to serve your app on the web browser
This will speed up your building process, but you should always test your app on native emulators and devices. Type the following code to serve your app on the web browser
This will speed up your building process, but you should always test your app on native emulators and devices. Type the following code to serve your app on the web browser
This will speed up your building process, but you should always test your app on native emulators and devices. Type the following code to serve your app on the web browser


I am a man of many hats:
Machine Intelligence
Embedded Computing
Performance Computing
Computer Graphics
Reverse Engineering
Design... not so much
My name is Peter Muller, and welcome to my site! Here you can find some of the projects that I've worked on and want to show off to you. I enjoy taking on challenging projects in order to learn new skills and technologies. Feel free to explore and make yourself at home. For my professional resume, please visit my LinkedIn page.
Some of my favorite projects have involved autonomous vehicles, image classification, GPU programming, and assembly debugging (but not necessarily all at once). Whether it is videogame hacking in MIPS assembly or image processing in MATLAB, I take pride in all the work I do. Take a look at my blog here.
I can be contacted in a number of ways, but my top two preferred methods are:
If we have not chatted before, just mention that you found me by my website.


"x" "1" "KLIER,B AND SCHIMMER,O, MICROSOMAL METABOLISM OF DICTAMNINE:IDENTIFICATION OF METABOLITES AND EVALUATION OF THEIR MUTAGENICITY IN SALMONELLATYPHIMURIUM: MUTAGENESIS 14(2):181-185, 1999"


{border-style px;} #ffffff;} symptoms neurological celiac motor described patients px; {font-family disease disease. font-size gastrointestinal manifestations Neurological double; presenting regression reported Hadjivassiliou antibodies border-color border-width children examination revealed solid; {font-style {font-weight CD. Case Celiac associated bold children. courier; elevated em; gluten pt;} showed symptoms. vomiting


Refresh
Whoops! This user does not have any challenge history
won
{{history.acornPlural(item.amount)}}
against
{{item.comment}}
{{history.split(item.timestamp, " ")[0]}}
lost
{{history.acornPlural(item.amount / 2)}}
against
{{item.comment}}
{{history.split(item.timestamp, " ")[0]}}
lost
{{history.acornPlural(item.amount / 2)}}
against
{{item.comment}}
{{history.split(item.timestamp, " ")[0]}}
won
{{history.acornPlural(item.amount)}}
against
{{item.comment}}
{{history.split(item.timestamp, " ")[0]}}


Former New York City Mayor Michael Bloomberg is running for president
by Nick FitzgeraldHis participation is specifically a stand against Donald Trump
After much deliberation, former New York City Mayor Michael Bloomberg has announced he is officially running for president.
The 77-year-old billionaire has been mulling the idea back and forth for quite some time. It was only back in March he said he would not make a 2020 run for the White House.
However, the tides have changed, with Bloomberg hitting out at the Donald, saying he is specifically running for president to defeat Trump and "rebuild America".
In a statement he said:
"I'm running for president to defeat Donald Trump and rebuild America. We cannot afford four more years of President Trump's reckless and unethical actions.
"He represents an existential threat to our country and our values. If he wins another term in office, we may never recover from the damage."
Bloomberg, who is joining the presidential race late, joins 18 other Democrats competing for their party’s presidential nomination.
Contenders include former vice-president Joe Biden, Massachusetts senator Elizabeth Warren and Vermont senator Bernie Sanders who failed to gain enough votes back in 2016.
Mr Bloomberg, ranked as the eight-richest American by Forbes, has a distinct advantage of being able to pour millions into his presidential campaign.
It is unclear just how much money he will put into his campaign, but, senior adviser, Howard Wolfson said: “Whatever it takes to defeat Donald Trump.”
Bloomberg's decision to enter the presidential race is causing a stir amongst contenders.
On Friday, Bernie Sanders tweeted:
“I’m disgusted by the idea that Michael Bloomberg or any billionaire thinks they can circumvent the political process and spend tens of millions of dollars to buy elections."
Meanwhile, Elizabeth Warren also slammed the 77-year-old's announcement.
“I understand that rich people are going to have more shoes than the rest of us, they’re going to have more cars than the rest of us, they’re going to have more houses,” she said.
 We need to be doing the face-to-face work that lifts every voice.”
According to the Financial Times, Mr Bloomberg's aides insist he sees a clear path to victory based on his record in the private and public sectors.


AIR BUD
RATING: * (out of ****)
Walt Disney / 1:30 / 1997 / PG (gooey sentiment, overacting) Cast: Kevin Zegers; Wendy Makkena; Michael Jeter; Bill Cobbs; Eric Christmas Director: Charles Martin Smith Screenplay: Aaron Mendelson; Paul Tamasy
Disney's "Air Bud" tells a boy-and-his-dog story with a twist -- the pooch is quite an accomplished basketball player. Granted, for a family comedy, it's not a very funny or successful idea to begin with, but it doesn't seem to matter -- "Air Bud" is surprisingly solemn. Save for occasional moments of forced slapstick, the movie wags its tale with a straight face -- not a very enjoyable approach. If "Air Bud" had realized its own absurdity, then it possibly could have been better. Here, we're actually asked to cheer a moment when the dog marches out to save the big game, clad in two pairs of sneakers and even a jersey. Its number? K9. Yeah, whatever.
The movie opens as golden retriever Buddy (as himself) escapes from his current owner, abusive clown-for-hire Norm Snively (Michael Jeter). He ends up in Fernwell, Washington, where mopey new-kid-on-the-block Josh (Kevin Zegers) is trying to cope with the move and the recent death of his father. Buddy, Kevin. Kevin, Buddy. Once the dog proves his on-court prowess, Kevin's self-esteem rockets. They both win places in the school's basketball team, with the animal as their mascot. But before they can make it to the finals, Snively surfaces to reclaim Buddy.
Everything plays out just as one would think: Heavy on predictability, light on an actual story. The movie follows a calculated chain of events -- Kevin's gloom fades, Snively gets his comeuppance and Buddy contracts rabies and must be executed Old Yeller-style. Okay, that last one's a lie, but at least it would have been a quicker send-off than "Air Bud"'s courtroom climax -- no joke! There's even a faux-cute musical montage where a reluctant Buddy gets cleaned-up to "Splish Splash." Paint cans are spilled and newspapers are buried, all in the name of formula.
The end credits note that "No special visual effects were used in the basketball sequences of this motion picture." That very well may be true, and although to see a dog sink shots is quite a sight, a movie cannot exist on feat alone. But "Air Bud" doesn't seem to be interested in anything else. A friend of mine insists he saw Buddy a while back on a segment of David Letterman's "Stupid Pet Tricks."
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


After I read the Search Inside Yourself chapter 1. I realize the emotional intelligence is very important factor to becoming a successful IT professional. In the workplace, emotional intelligence enables three important skills: stellar work performance, outstanding leadership, and the ability to create the conditions for happiness. These skills are play a very important role in a team.
I feel energized, deep relax and mind peaceful after two minutes of mindfulness. It is very good way to heal your mind when you under pressure of work. I will do it every week.


Search/analytics endpoint; highly configurable. Not for bulk doc retrieval. (search)
The q.* parameters qre query/constraints that limit the matching documents. The d.* params control returning the documents. The a.* params are faceting/aggregations on a field of the documents. The *.limit params limit how many top values/docs to return. Some of the formatting and response structure has strong similarities with Apache Solr, unsurprisingly.
q.text (optional)
Query Parameter — Constrains docs by keyword search query.
q.time (optional)
Query Parameter — Constrains docs by time range. Either side can be '*' to signify open-ended. Otherwise it should either be in this format: 2013-03-01 or 2013-03-01T00:00:00 (both are equivalent). UTC time zone is implied.
q.geo (optional)
Query Parameter — A rectangular geospatial filter in decimal degrees going from the lower-left to the upper-right. The coordinates are in lat,lon format.
d.docs.limit (optional)
Query Parameter — How many documents to return in the search results. default: 0
d.docs.sort (optional)
Query Parameter — How to order the documents before returning the top X. 'score' is keyword search relevancy. 'time' is time descending. 'distance' is the distance between the doc and the middle of q.geo. default: score
a.time.limit (optional)
Query Parameter — Non-0 triggers time/date range faceting. This value is the maximum number of time ranges to return when a.time.gap is unspecified. This is a soft maximum; less will usually be returned. Note that a.time.gap effectively ignores this value. TODO WARNING: not implemented yet but must use non-0. See Solr docs for more details on the query/response format. default: 0
a.time.gap (optional)
Query Parameter — The consecutive time interval/gap for each time range. Ignores a.time.limit
a.time.filter (optional)
Query Parameter — From what time range to divide by a.time.gap into intervals. Defaults to q.time and otherwise 90 days.
a.hm.limit (optional)
Query Parameter — Non-0 triggers heatmap/grid faceting. This number is a soft maximum on thenumber of cells it should have. There may be as few as 1/4th this number in return. Note that a.hm.gridLevel can effectively ignore this value. The response heatmap contains a counts grid that can be null or contain null rows when all its values would be 0. See Solr docs for more details on the response format. default: 0
a.hm.gridLevel (optional)
Query Parameter — To explicitly specify the grid level, e.g. to let a user ask for greater or courser resolution than the most recent request. Ignores a.hm.limit.
a.hm.filter (optional)
Query Parameter — From what region to plot the heatmap. Defaults to q.geo or otherwise the world.
This API call produces the following media types according to the request header;
the media type will be conveyed by the


OpenDVD project provides a collection of high quality Open Source Software for Windows. Free and Open Source Software (FOSS) is provided with a license that gives the end user the right to use it freely for private or commercial use. You also have the right to inspect
and even modify the underlying source code. You can give away or sell the original version you received or one with your modification, though you may be required to in turn pass on the modified source code so that others can benefit from the changes you have made.


Blog
Nav Bar
>
Home
Projects
Resume
Blog
Contact
My Journey
Alicia Briceland - Web Developer
Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Week 7


SIGN UP FORM
Registration Form
Name:
Username:
Email Address:
Mobile Number:
Gender:
Male
Female
Date Of Birth:
Password:


POSC 6003: Advanced Political Analysis (Fall 2020)
Arkansas State University
Department of Political Science
Cameron Wimpy<EMAIL_ADDRESS>Tuesdays 1–3:50 p.m. HSS 3035
All content licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Course Materials 2020 Cameron Wimpy
{{- if .Site.Params.credits }}{{ .Site.Params.credits | markdownify }}
{{- end }}This site created with the Academic theme in blogdown and Hugo.


{% block body %}{% endblock %}
{% block autorefresh %}{% endblock %}
ETLs - information about the status of all ETL processes (DAGs) available in airflow database. If tables are defined this view shows number of processed tables. If tables information is missing, it shows number of tasks completed.
Tables - information available only it tables mapping is defined in a yaml file. It shows current status of processing related to a particular table.
Plugins - any information provided through plugins system available in discreETLy with appropriate tab name.
For more information contact the team responsible for maintaining the dashboard or search the documentation.


Responses
Search
Let's Go To The Park
Nathan Myers
Dec. 16, 2013
-
Share
-
Delete
08:52:05 AM
"Yes, I'd like to go to the park."
08:53:42 AM
"Let's go to Macleay Park."
08:54:47 AM
"Ok, I'll drive."
Dec. 15, 2013
-
Share
-
Delete
Dec. 14, 2013
-
Share
-
Delete
Jason Nelson
Dec. 16, 2013
-
Share
-
Delete
Some Student
Let's Go To The Park v2
Let's Go To The Park v3
Buying Coffee
Sim Conv
Responses shared with you
Let's Go To The Park v2
Let's Go To The Park v3
Buying Coffee
Sim Conv


Enable feed detection
Open feed in new tab
Display raw xml instead of preview page
Display full articles even when summaries are present
Display entry author
Use color icon in address bar
Display media:thumbnail images
Set max-width for images at
Enable custom CSS:
Bypass CSP header when needed


Class: Aws::GameLift::Types::Event
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb |
Overview
::Aws::Log
entry describing an event that involves Amazon GameLift resources
(such as a fleet). In addition to tracking activity, event codes and
messages can provide additional information for troubleshooting and
debugging problems.
Constant Summary
Instance Attribute Summary
-
#event_code ⇒ String
rw
The type of event being logged.
-
#event_id ⇒ String
rw
A unique identifier for a fleet event.
-
#event_time ⇒ Time
rw
Time stamp indicating when this event occurred.
-
#message ⇒ String
rw
Additional information related to the event.
-
#pre_signed_log_url ⇒ String
rw
Location of stored logs with additional detail that is related to the event.
-
#resource_id ⇒ String
rw
A unique identifier for an event resource, such as a fleet ID.
Instance Method Summary
Instance Attribute Details
#event_code ⇒ String
(rw)
The type of event being logged.
Fleet state transition events:
FLEET_CREATED -- A fleet resource was successfully created with a status of
NEW
. Event messaging includes the fleet ID.FLEET_STATE_DOWNLOADING -- Fleet status changed from
NEW
toDOWNLOADING
. The compressed build has started downloading to a fleet instance for installation.FLEET_STATE_VALIDATING -- Fleet status changed from
DOWNLOADING
toVALIDATING
. Amazon GameLift has successfully downloaded the build and is now validating the build files.FLEET_STATE_BUILDING -- Fleet status changed from
VALIDATING
toBUILDING
. Amazon GameLift has successfully verified the build files and is now running the installation scripts.FLEET_STATE_ACTIVATING -- Fleet status changed from
BUILDING
toACTIVATING
. Amazon GameLift is trying to launch an instance and test the connectivity between the build and the Amazon GameLift Service via the Server SDK.FLEET_STATE_ACTIVE -- The fleet's status changed from
ACTIVATING
toACTIVE
. The fleet is now ready to host game sessions.FLEET_STATE_ERROR -- The Fleet's status changed to
ERROR
. Describe the fleet event message for more details.
Fleet creation events (ordered by fleet creation activity):
FLEET_BINARY_DOWNLOAD_FAILED -- The build failed to download to the fleet instance.
FLEET_CREATION_EXTRACTING_BUILD -- The game server build was successfully downloaded to an instance, and the build files are now being extracted from the uploaded build and saved to an instance. Failure at this stage prevents a fleet from moving to ACTIVE status. Logs for this stage display a list of the files that are extracted and saved on the instance. Access the logs by using the URL in PreSignedLogUrl.
FLEET_CREATION_RUNNING_INSTALLER -- The game server build files were successfully extracted, and the GameLift is now running the build's install script (if one is included). Failure in this stage prevents a fleet from moving to ACTIVE status. Logs for this stage list the installation steps and whether or not the install completed successfully. Access the logs by using the URL in PreSignedLogUrl.
FLEET_CREATION_VALIDATING_RUNTIME_CONFIG -- The build process was successful, and the GameLift is now verifying that the game server launch paths, which are specified in the fleet's runtime configuration, exist. If any listed launch path exists, Amazon GameLift tries to launch a game server process and waits for the process to report ready. Failures in this stage prevent a fleet from moving to
ACTIVE
status. Logs for this stage list the launch paths in the runtime configuration and indicate whether each is found. Access the logs by using the URL in PreSignedLogUrl.FLEET_VALIDATION_LAUNCH_PATH_NOT_FOUND -- Validation of the runtime configuration failed because the executable specified in a launch path does not exist on the instance.
FLEET_VALIDATION_EXECUTABLE_RUNTIME_FAILURE -- Validation of the runtime configuration failed because the executable specified in a launch path failed to run on the fleet instance.
FLEET_VALIDATION_TIMED_OUT -- Validation of the fleet at the end of creation timed out. Try fleet creation again.
FLEET_ACTIVATION_FAILED -- The fleet failed to successfully complete one of the steps in the fleet activation process. This event code indicates that the game build was successfully downloaded to a fleet instance, built, and validated, but was not able to start a server process. For more information, see Debug Fleet Creation Issues.
FLEET_ACTIVATION_FAILED_NO_INSTANCES -- Fleet creation was not able to obtain any instances based on the input fleet attributes. Try again at a different time or choose a different combination of fleet attributes such as fleet type, instance type, etc.
FLEET_INITIALIZATION_FAILED -- A generic exception occurred during fleet creation. Describe the fleet event message for more details.
VPC peering events:
FLEET_VPC_PEERING_SUCCEEDED -- A VPC peering connection has been established between the VPC for an Amazon GameLift fleet and a VPC in your Amazon Web Services account.
FLEET_VPC_PEERING_FAILED -- A requested VPC peering connection has failed. Event details and status information provide additional detail. A common reason for peering failure is that the two VPCs have overlapping CIDR blocks of IPv4 addresses. To resolve this, change the CIDR block for the VPC in your Amazon Web Services account. For more information on VPC peering failures, see https://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/invalid-peering-configurations.html
FLEET_VPC_PEERING_DELETED -- A VPC peering connection has been successfully deleted.
Spot instance events:
INSTANCE_INTERRUPTED -- A spot instance was interrupted by
::Aws::EC2
with a two-minute notification.INSTANCE_RECYCLED -- A spot instance was determined to have a high risk of interruption and is scheduled to be recycled once it has no active game sessions.
Server process events:
SERVER_PROCESS_INVALID_PATH -- The game server executable or script could not be found based on the Fleet runtime configuration. Check that the launch path is correct based on the operating system of the Fleet.
SERVER_PROCESS_SDK_INITIALIZATION_TIMEOUT -- The server process did not call InitSDK() within the time expected. Check your game session log to see why InitSDK() was not called in time.
SERVER_PROCESS_PROCESS_READY_TIMEOUT -- The server process did not call ProcessReady() within the time expected after calling InitSDK(). Check your game session log to see why ProcessReady() was not called in time.
SERVER_PROCESS_CRASHED -- The server process exited without calling ProcessEnding(). Check your game session log to see why ProcessEnding() was not called.
SERVER_PROCESS_TERMINATED_UNHEALTHY -- The server process did not report a valid health check for too long and was therefore terminated by GameLift. Check your game session log to see if the thread became stuck processing a synchronous task for too long.
SERVER_PROCESS_FORCE_TERMINATED -- The server process did not exit cleanly after OnProcessTerminate() was sent within the time expected. Check your game session log to see why termination took longer than expected.
SERVER_PROCESS_PROCESS_EXIT_TIMEOUT -- The server process did not exit cleanly within the time expected after calling ProcessEnding(). Check your game session log to see why termination took longer than expected.
Game session events:
- GAME_SESSION_ACTIVATION_TIMEOUT --
GameSession
failed to activate within the expected time. Check your game session log to see why ActivateGameSession() took longer to complete than expected.
^
Other fleet events:
FLEET_SCALING_EVENT -- A change was made to the fleet's capacity settings (desired instances, minimum/maximum scaling limits). Event messaging includes the new capacity settings.
FLEET_NEW_GAME_SESSION_PROTECTION_POLICY_UPDATED -- A change was made to the fleet's game session protection policy setting. Event messaging includes both the old and new policy setting.
FLEET_DELETED -- A request to delete a fleet was initiated.
GENERIC_EVENT -- An unspecified event has occurred.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end
#event_id ⇒ String
(rw)
A unique identifier for a fleet event.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end
#event_time ⇒ Time
(rw)
Time stamp indicating when this event occurred. Format is a number
expressed in Unix time as milliseconds (for example
"1469498468.057"
).
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end
#message ⇒ String
(rw)
Additional information related to the event.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end
#pre_signed_log_url ⇒ String
(rw)
Location of stored logs with additional detail that is related to the event. This is useful for debugging issues. The URL is valid for 15 minutes. You can also access fleet creation logs through the Amazon GameLift console.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end
#resource_id ⇒ String
(rw)
A unique identifier for an event resource, such as a fleet ID.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 3887
class Event < Struct.new( :event_id, :resource_id, :event_code, :, :event_time, :pre_signed_log_url) SENSITIVE = [] include Aws::Structure end


You should install the JDK (the one from Oracle, not OpenJDK) first, and then the jMonkey SDK. If jMonkeyEngine SDK cannot find a valid JDK although you have it installed, then you have to specify the location manually.
etc
directory. Contents/Resources/jmonkeyplatform/etc/
.jmonkeyplatform.conf
in a text editor.jdkhome="/path/to/jdk"
To completely remove and/or reinstall the SDK it is vital that the settings folder is deleted too. The location can be seen through the "about" menu and is as following for the different OS's:
C:\Users\<username>\AppData\Roaming\.jmonkeyplatform
C:\Users\<username>\.jmonkeyplatform\
/Users/<username>/Library/Application Support/jmonkeyplatform
/home/<username>/.jmonkeyplatform
On some Linux and Windows systems, the SDK might perform unstable and quit with native VM crashes or "x errors". There are a few things one can try to remedy those issues.
On Windows and Linux make sure you have the latest driver installed. Make sure its the one supplied by the card manufacturer and not just the OS-default one.
First of all theres the new “OpenGL” settings page in the SDK global settings where you can enable the "heavyweight" canvas, which solved some issues for some people. The settings panel can be found under Tools→Options on Windows and Linux and in the main menu (or by pressing Apple-Comma) for MacOSX.
If you cannot start the SDK, edit the file config/Preferences/com/jme3/gde/core.properties
in the SDK settings folder (see above). If it doesn't exist, create the file including all folders. Add the line use_lwjgl_canvas=true
. To try OpenGL1 compatibility mode (works for both canvas settings) add use_opengl_1=true
.
The OS-built-in look and feel might cause issues, you can change the LAF by using the appropriate command line switch (or add it to the [app folder]/etc/jmonkeyplatform.conf file, without the "- -" prefix).
--laf javax.swing.plaf.metal.MetalLookAndFeel
Compiz on Linux might cause issues, if you set its rendering quality to "medium" these should go away. * Appearance→Set Special effects to → “Medium”
If you have problems updating the SDK, try deleting all files from jmonkeyplatform/update/download
and/or [settings folder]/update/download
depending on your system (look above for the settings folder location).
When an exception happens in the SDK, a small warning sign appears in the lower right corner of the main window. Double-click it to open a window that allows you to see the exception stack trace. When posting about issues in the forum, always post the stack trace along with a description of what happens and how it can be reproduced.
For a list of known issues and possible workarounds see the following link:


Lladro 1811 Moses & The Ten Commandments
Limited Edition With Base & Original Box
Description
Lladro 1811 Moses & The Ten Commandments Limited Edition W/Base & Original Box..
Product Overview
The model "Moses & the ten Commandments" reference number 01811, is one of a limited edition of 1200 pieces. This certificate accompanies piece N° 204
Artists contributing to the creation of this edition include:
- D.Salvador Furió
- D.Angelita Cabo
To this effect, we hereby issue this certificate of authenticity dated: Valencia, a 24 de mayo de 1996
Key Benefits
- Limited edition of 1200 pieces
- Piece N° 204 and Certificate Authenticity included
- Perfect Condition in the Original Box.
- Comes with Wooden Base.
- No chips, no marks, no scratches, no cracks, no repairs, no crazing.
- 1st quality piece with Full Lladro Markings on the bottom including the Blue Lladro Tulip Flower, signatures of the Sculptor and Decorator.
- This piece will be shipped fully insured.
- This piece will come to you in the Original Box packed and shipped with exceptional care.
Payment
We accept PayPal Only. All major credit cards are accepted through secure payment processor PayPal.
Shipping
PLEASE READ!!!
Feel Safe to Buy with Us read our Feedback is our business!!!
WEEKEND CLOSED!
Shipping out in next business day if you choose on weekend
ALASKA / HAWAII / PUERTO RICO / P.O BOX IS NOT AVAILABLE!!!!!
SHIPPING BY DHL
It usually takes 3 days of handling time. For orders within the US it takes 7 business days maximum after handling and for orders outside the US it takes 13 business days maximum.
When can you expect your order? Allow at least 2 to 3 days for tracking number to post.
When I know, you will know.
If you want cancel order we can do only before shipping...
Purchase Terms and Conditions
- Your order will be processed within 3 to 5 business day after receipt of cleared payment.
- We Only Provide Shipping to the 48 Contiguous United States.
- We are unable to ship PO Box.
- We do not combine shipping.
- 14 days in order to get your money back or item exchange*, buyer pays return shipping.
- Buyers Pay for Return Shipping Cost.
- All emails will be answered within 1 business day. If you do not receive our reply, please kindly re-sent your e-mail, and we will reply to you as soon as possible.
- All items sold by us are being described to the best of our abilities, as accurate as possible, and with utmost conscientiousness on our part. However, to avoid any potential oversights, I respectfully request your assistance in helping us to make this a mutually satisfactory transaction by Thoroughly reviewing item description and photos, and asking all questions Prior To Bidding.
- Please Note that size and color representation are subject to manufacturing variance and may not be exact. Also note that monitor settings may vary from computer to computer and may distort actual colors.
- Before you report any problem to Ebay wait for our answer.
- If there is something let you unsatisfy, please do not leave negative or neutral feedback we will try best to solve your problem and ensure your requirement.
- Please leave POSITIVE FEEDBACK after receiving the product


| Package | Description |
|---|---|
| com.opengamma.strata.basics.value |
Basic financial tools for working with values.
|
| com.opengamma.strata.product.bond |
Entity objects describing bonds.
|
| com.opengamma.strata.product.index |
Entity objects describing contracts based on rate indices.
|
| Modifier and Type | Class and Description |
|---|---|
class |
HalfUpRounding
Standard implementation of
Rounding that uses the half-up convention. |
| Modifier and Type | Method and Description |
|---|---|
static Rounding |
Rounding.none()
Obtains an instance that performs no rounding.
|
static Rounding |
Rounding.ofDecimalPlaces(int decimalPlaces)
Obtains an instance that rounds to the specified number of decimal places.
|
static Rounding |
Rounding.ofFractionalDecimalPlaces(int decimalPlaces,
int fraction)
Obtains an instance from the number of decimal places and fraction.
|
| Modifier and Type | Method and Description |
|---|---|
Rounding |
ResolvedBondFutureOption.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
ResolvedBondFuture.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
Rounding |
BondFutureSecurity.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
Rounding |
BondFutureOptionSecurity.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
BondFutureOption.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
BondFuture.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
| Modifier and Type | Method and Description |
|---|---|
MetaProperty<Rounding> |
ResolvedBondFutureOption.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
ResolvedBondFuture.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
BondFutureSecurity.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
BondFutureOptionSecurity.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
BondFutureOption.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
BondFuture.Meta.rounding()
The meta-property for the
rounding property. |
| Modifier and Type | Method and Description |
|---|---|
ResolvedBondFutureOption.Builder |
ResolvedBondFutureOption.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
ResolvedBondFuture.Builder |
ResolvedBondFuture.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
BondFutureSecurity.Builder |
BondFutureSecurity.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
BondFutureOptionSecurity.Builder |
BondFutureOptionSecurity.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
BondFutureOption.Builder |
BondFutureOption.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
BondFuture.Builder |
BondFuture.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
| Modifier and Type | Method and Description |
|---|---|
Rounding |
ResolvedIborFutureOption.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
ResolvedIborFuture.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
Rounding |
IborFutureSecurity.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
Rounding |
IborFutureOptionSecurity.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
IborFutureOption.getRounding()
Gets the definition of how to round the option price, defaulted to no rounding.
|
Rounding |
IborFuture.getRounding()
Gets the definition of how to round the futures price, defaulted to no rounding.
|
| Modifier and Type | Method and Description |
|---|---|
MetaProperty<Rounding> |
ResolvedIborFutureOption.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
ResolvedIborFuture.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
IborFutureSecurity.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
IborFutureOptionSecurity.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
IborFutureOption.Meta.rounding()
The meta-property for the
rounding property. |
MetaProperty<Rounding> |
IborFuture.Meta.rounding()
The meta-property for the
rounding property. |
| Modifier and Type | Method and Description |
|---|---|
ResolvedIborFutureOption.Builder |
ResolvedIborFutureOption.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
ResolvedIborFuture.Builder |
ResolvedIborFuture.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
IborFutureSecurity.Builder |
IborFutureSecurity.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
IborFutureOptionSecurity.Builder |
IborFutureOptionSecurity.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
IborFutureOption.Builder |
IborFutureOption.Builder.rounding(Rounding rounding)
Sets the definition of how to round the option price, defaulted to no rounding.
|
IborFuture.Builder |
IborFuture.Builder.rounding(Rounding rounding)
Sets the definition of how to round the futures price, defaulted to no rounding.
|
Copyright 2009-Present by OpenGamma Inc. and individual contributors
Apache v2 licensed
Additional documentation can be found at opengamma.github.io/StrataDocs.