Olympus camera class.
This class provides the operation and display of live view, including content acquisition in the camera and capturing of still images and recording movies by connecting to the camera. This class has several categories.
Please refer to each category for details of the interface.
Several functions are provided for the vendor. These are not available in third party applications.
Instance Methods | |
| (id) | - initWithDispatchQueue: |
| Initialize new camera instance. More... | |
| (BOOL) | - connectingRequiresBluetoothPassword: |
| Indicate if camera requires a password for Bluetooth Smart connection. More... | |
| (BOOL) | - wakeup: |
| Wake up the camera via Bluetooth Smart. More... | |
| (BOOL) | - canConnect:timeout:error: |
| Indicate if the application can connect to the camera. More... | |
| (BOOL) | - connect:error: |
| Connect to the camera. More... | |
| (BOOL) | - disconnectWithPowerOff:error: |
| Disconnect from the camera. More... | |
| (NSDictionary *) | - inquireHardwareInformation: |
| Get hardware information of the camera. More... | |
| (NSString *) | - cameraPropertyTitle: |
| Get title of the camera property. More... | |
| (NSArray *) | - cameraPropertyValueList:error: |
| Get list of the camera property values that can be set. More... | |
| (NSString *) | - cameraPropertyValue:error: |
| Get value that is set in the camera properties. More... | |
| (NSDictionary *) | - cameraPropertyValues:error: |
| Get values that are set in the camera properties. More... | |
| (NSString *) | - cameraPropertyValueTitle: |
| Get title of the camera property value. More... | |
| (BOOL) | - canSetCameraProperty: |
| Check to see if value to the camera properties can be set. More... | |
| (BOOL) | - setCameraPropertyValue:value:error: |
| Set value to the camera properties. More... | |
| (BOOL) | - setCameraPropertyValues:error: |
| Set values to camera properties. More... | |
| (BOOL) | - changeRunMode:error: |
| Change run mode of the camera. More... | |
| (BOOL) | - changeTime:error: |
| Change date and time of camera. More... | |
| (BOOL) | - setGeolocation:error: |
| Register geolocation information to the camera. More... | |
| (BOOL) | - clearGeolocation: |
| Discard registered geolocation information. More... | |
| (void) | - downloadContentList: |
| Download list of all supported media (still image and video) in the camera. More... | |
| (void) | - downloadContentThumbnail:progressHandler:completionHandler:errorHandler: |
| Download thumbnail of media (still image and movie) stored in memory card. More... | |
| (void) | - downloadContentScreennail:progressHandler:completionHandler:errorHandler: |
| Download reduced image of media (still image and movie) stored in memory card. More... | |
| (void) | - downloadImage:withResize:progressHandler:completionHandler:errorHandler: |
| Download a resized still image. More... | |
| (void) | - downloadContent:progressHandler:completionHandler:errorHandler: |
| Download media (still image and movie) stored in memory card. More... | |
| (void) | - downloadLargeContent:progressHandler:completionHandler:errorHandler: |
| Split large media (still image or movie) into smaller parts and download each part. More... | |
| (NSInteger) | - countNumberOfContents: |
| Count the number of media (still image and movie) in the camera. More... | |
| (NSDictionary *) | - inquireContentInformation:error: |
| Get information of media (still image and movie) stored in memory card. More... | |
| (void) | - resizeVideoFrame:size:quality:progressHandler:completionHandler:errorHandler: |
| Resize each frame of the video, and save it as a new file in the camera's memory card. More... | |
| (BOOL) | - protectContent:error: |
| Protect media (still image and movie) stored in memory card. More... | |
| (BOOL) | - unprotectContent:error: |
| Cancel protection of the media (still image and movie) stored in memory card. More... | |
| (void) | - unprotectAllContents:completionHandler:errorHandler: |
| Cancel protection of all the media (still image and movie) stored in memory card. More... | |
| (BOOL) | - eraseContent:error: |
| Delete media (still image and movie) stored in memory card. More... | |
| (BOOL) | - startLiveView: |
| Start live view. More... | |
| (BOOL) | - stopLiveView: |
| Stop live view. More... | |
| (BOOL) | - changeLiveViewSize:error: |
| Change the size of live view. More... | |
| (OLYCameraActionType) | - actionType |
| Get the shooting mode and drive mode. More... | |
| (void) | - startTakingPicture:progressHandler:completionHandler:errorHandler: |
| Start shooting photo. More... | |
| (void) | - stopTakingPicture:completionHandler:errorHandler: |
| Finish shooting photo. More... | |
| (void) | - takePicture:progressHandler:completionHandler:errorHandler: |
| Execute batch operation from start of shooting photos to end of shooting. More... | |
| (void) | - startRecordingVideo:completionHandler:errorHandler: |
| Start recording movie. More... | |
| (void) | - stopRecordingVideo:errorHandler: |
| Finish recording movie. More... | |
| (void) | - lockAutoFocus:errorHandler: |
| Lock autofocus operation. More... | |
| (BOOL) | - unlockAutoFocus: |
| Unlock autofocus operation. More... | |
| (BOOL) | - setAutoFocusPoint:error: |
| Set coordinates to use for auto focus. More... | |
| (BOOL) | - clearAutoFocusPoint: |
| Clear coordinates used for auto focus. More... | |
| (BOOL) | - lockAutoExposure: |
| Lock operation of automatic exposure control. More... | |
| (BOOL) | - unlockAutoExposure: |
| Release lock of automatic exposure control. More... | |
| (BOOL) | - setAutoExposurePoint:error: |
| Specify coordinates of reference exposure for automatic exposure control. More... | |
| (BOOL) | - clearAutoExposurePoint: |
| Release specified coordinates of reference exposure for automatic exposure control. More... | |
| (CGRect) | - autoFocusEffectiveArea: |
| Get valid range of coordinates to use for auto focus. More... | |
| (CGRect) | - autoExposureEffectiveArea: |
| Get valid range of coordinates to use for automatic exposure control. More... | |
| (BOOL) | - startDrivingZoomLensForDirection:speed:error: |
| Start driving optical zoom with specific speed and direction. More... | |
| (BOOL) | - startDrivingZoomLensToFocalLength:error: |
| Start driving optical zoom to the specified focal length. More... | |
| (BOOL) | - stopDrivingZoomLens: |
| Stop driving optical zoom. More... | |
| (NSDictionary *) | - digitalZoomScaleRange: |
| Get configurable magnification range of digital zoom. More... | |
| (BOOL) | - changeDigitalZoomScale:error: |
| Change magnification of digital zoom. More... | |
| (BOOL) | - startMagnifyingLiveView:error: |
| Start magnifying live view. More... | |
| (BOOL) | - startMagnifyingLiveViewAtPoint:scale:error: |
| Start magnifying live view with center coordinate of magnification. More... | |
| (BOOL) | - stopMagnifyingLiveView: |
| Stop magnifying live view. More... | |
| (BOOL) | - changeMagnifyingLiveViewScale:error: |
| Change magnification of live view. More... | |
| (BOOL) | - changeMagnifyingLiveViewArea:error: |
| Move display area in magnified live view. More... | |
| (NSDictionary *) | - magnifyingLiveViewArea: |
| Get display area information of magnified live view. More... | |
| (void) | - downloadLastCapturedImage:completionHandler:errorHandler: |
| Download the last captured image. More... | |
Class Methods | |
| (NSArray *) | + bluetoothServices |
| List of Bluetooth service ID. More... | |
Properties | |
| NSString * | host |
| IP address of the camera. More... | |
| NSInteger | commandPort |
| Port number where the camera receives commands. More... | |
| NSInteger | liveViewStreamingPort |
| Port number where Camera Kit receives live view images. More... | |
| NSInteger | eventPort |
| Port number where Camera Kit receives events issued by the camera. More... | |
| CBPeripheral * | bluetoothPeripheral |
| Bluetooth peripheral. More... | |
| NSString * | bluetoothPassword |
| Password to connect via Bluetooth Smart to the camera. More... | |
| BOOL | bluetoothPrepareForRecordingWhenPowerOn |
| If true, the camera starts recording setup after power on via Bluetooth Smart. More... | |
| OLYCameraConnectionType | connectionType |
| Type of connection to the camera. | |
| id< OLYCameraConnectionDelegate > | connectionDelegate |
| The object that acts as the delegate to receive change to communication state of the camera. | |
| BOOL | connected |
| Indicate whether the camera is currently connected. | |
| NSArray * | cameraPropertyNames |
| List of camera property names currently available. More... | |
| id< OLYCameraPropertyDelegate > | cameraPropertyDelegate |
| The object that acts as the delegate to receive changes to camera property. | |
| OLYCameraRunMode | runMode |
| Current run mode of the camera system. More... | |
| BOOL | highTemperatureWarning |
| Indicate if inside of the camera is in high-temperature condition. More... | |
| NSString * | lensMountStatus |
| Indicate status of lens mount. More... | |
| NSString * | mediaMountStatus |
| Indicate status of media (memory card) mount. More... | |
| BOOL | mediaBusy |
| Indicate whether the camera is writing to the media (memory card). More... | |
| BOOL | mediaError |
| Indicate whether the media (memory card) I/O error has occurred. More... | |
| NSUInteger | remainingMediaCapacity |
| Free space of the media (memory card) attached to the camera. More... | |
| NSUInteger | remainingImageCapacity |
| The maximum number of images that can be stored in the media (memory card). More... | |
| NSTimeInterval | remainingVideoCapacity |
| The maximum number of seconds a movie that can be stored in the media (memory card). More... | |
| id< OLYCameraPlaybackDelegate > | playbackDelegate |
| Delegate object to receive changes to playback operations. | |
| BOOL | autoStartLiveView |
| Indicate that live view starts automatically when run mode is changed to Recording mode. More... | |
| BOOL | liveViewEnabled |
| Indicate that live view started. More... | |
| OLYCameraLiveViewSize | liveViewSize |
| Frame size of live view in pixels. More... | |
| id< OLYCameraLiveViewDelegate > | liveViewDelegate |
| Delegate object that notifies state of live view image when it changes. | |
| id< OLYCameraRecordingDelegate > | recordingDelegate |
| Delegate object that notifies camera state when it changes. More... | |
| BOOL | takingPicture |
| Indicate that photo shooting is in progress on the camera. More... | |
| BOOL | recordingVideo |
| Indicate that video recording is in progress on the camera. More... | |
| float | actualFocalLength |
| Current focal length of the lens. More... | |
| float | minimumFocalLength |
| Focal length at the wide end of the lens. More... | |
| float | maximumFocalLength |
| Focal length at the telephoto end of the lens. More... | |
| CGPoint | actualAutoFocusPoint |
| Coordinates focused with autofocus. More... | |
| NSString * | actualApertureValue |
| F value used by lens and camera. More... | |
| NSString * | actualShutterSpeed |
| Shutter speed used by the camera. More... | |
| NSString * | actualExposureCompensation |
| Exposure compensation value used by the camera. More... | |
| NSString * | actualIsoSensitivity |
| ISO sensitivity used by camera. More... | |
| BOOL | actualIsoSensitivityWarning |
| Indicate that out of range warning of ISO sensitivity is occurring in the camera. More... | |
| BOOL | exposureWarning |
| Indicate that out of range warning of the exposure is occurring in the camera. More... | |
| BOOL | exposureMeteringWarning |
| Indicate that warning of the exposure metering is occurring in the camera. More... | |
| id < OLYCameraRecordingSupportsDelegate > | recordingSupportsDelegate |
| Delegate object to notify camera state when it changes. More... | |
| BOOL | drivingZoomLens |
| Indicate optical zoom is changing in the camera. More... | |
| BOOL | magnifyingLiveView |
| Indicate that live view is magnified. More... | |
| NSDictionary * | levelGauge |
| Information of level gauge. More... | |
| NSDictionary * | detectedHumanFaces |
| Face recognition results. More... | |
| - (OLYCameraActionType) actionType |
Get the shooting mode and drive mode.
The application can determine whether to perform any shooting as a response to a user tap by referring to this value. Please refer to the description of OLYCameraActionType.
Provided by category OLYCamera(Recording).
| - (CGRect) autoExposureEffectiveArea: | (NSError **) | error |
Get valid range of coordinates to use for automatic exposure control.
| error | Error details are set when operation is abnormally terminated. |
The application can convert to rectangular coordinates for live view image on the rectangular coordinates indicating the range using the coordinate conversion utility OLYCameraConvertRectOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
| - (CGRect) autoFocusEffectiveArea: | (NSError **) | error |
Get valid range of coordinates to use for auto focus.
| error | Error details are set when operation is abnormally terminated. |
The application can convert to rectangular coordinates from live view image in the rectangular coordinates indicating the range using the coordinate conversion utility OLYCameraConvertRectOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
| + (NSArray *) bluetoothServices |
List of Bluetooth service ID.
Provided by category OLYCamera(CameraConnection).
| - (NSString *) cameraPropertyTitle: | (NSString *) | name |
Get title of the camera property.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will have an error. Please refer to the documentation of the camera list of properties for more information.
| name | The camera property name. (e.g. "APERTURE", "SHUTTER", "ISO", "WB") |
Provided by category OLYCamera(CameraSystem).
| - (NSString *) cameraPropertyValue: | (NSString *) | name | |
| error: | (NSError **) | error | |
Get value that is set in the camera properties.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will get an error. Depending on shooting mode, connection type, etc., several properties are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
The return value is a string in the form of "<Property Name/Property Value>."
| name | The camera property name. (e.g. "APERTURE", "SHUTTER", "ISO") |
| error | Error details will be set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (NSArray *) cameraPropertyValueList: | (NSString *) | name | |
| error: | (NSError **) | error | |
Get list of the camera property values that can be set.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will have an error. If the application changes settings such as shooting mode, there are times when the contents of the list changes. Please refer to the documentation of the camera list of properties for more information.
Each value in the list is a string in the form of "<Property Name/Property Value>."
| name | The camera property name. (e.g. "APERTURE", "SHUTTER", "ISO") |
| error | Error details will be set when the operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (NSDictionary *) cameraPropertyValues: | (NSSet *) | names | |
| error: | (NSError **) | error | |
Get values that are set in the camera properties.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will get an error. Depending on shooting mode, connection type, etc., several properties are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
| names | The camera property names. Each element is a string. |
| error | Error details will be set when operation is abnormally terminated. |
The retrieved values are in dictionary format. The dictionary key is the camera property name. Setting of the camera property is stored in value corresponding to the key.
Provided by category OLYCamera(CameraSystem).
| - (NSString *) cameraPropertyValueTitle: | (NSString *) | value |
Get title of the camera property value.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will get an error. Depending on the setting value of the shooting mode, connection type, etc., several properties are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
The argument for parameter "value" is a string in the form of "<Property Name/Property Value>."
| value | Pair of property name and property value set in the property. (e.g. "<APERTURE/3.5>", "<SHUTTER/250>", "<ISO/Auto>", "<WB/WB_AUTO>") |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) canConnect: | (OLYCameraConnectionType) | connectionType | |
| timeout: | (NSTimeInterval) | timeout | |
| error: | (NSError **) | error | |
Indicate if the application can connect to the camera.
If the application is connected to the camera, the application will get an error.
| connectionType | Type of connection. You specify 'Wi-Fi'. |
| timeout | Number of seconds for timeout. If 0 is specified, default value is set. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraConnection).
| - (BOOL) canSetCameraProperty: | (NSString *) | name |
Check to see if value to the camera properties can be set.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will get an error. Depending on the setting value of the shooting mode, connection type, etc., several properties are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
| name | The camera property name. (e.g. "APERTURE", "SHUTTER", "ISO", "WB") |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) changeDigitalZoomScale: | (float) | scale | |
| error: | (NSError **) | error | |
Change magnification of digital zoom.
If application specifies magnification that is not included in the configurable range, there will be an error. When changing run mode to any mode except recording mode, magnification is changed back to 1x automatically.
| scale | Magnification of digital zoom. |
| error | Error details are set when the operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) changeLiveViewSize: | (OLYCameraLiveViewSize) | size | |
| error: | (NSError **) | error | |
Change the size of live view.
| size | Size of live view. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) changeMagnifyingLiveViewArea: | (OLYCameraMagnifyingLiveViewScrollDirection) | direction | |
| error: | (NSError **) | error | |
Move display area in magnified live view.
If live view is not magnified, an error occurs.
| direction | Scrolling direction of the display area. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) changeMagnifyingLiveViewScale: | (OLYCameraMagnifyingLiveViewScale) | scale | |
| error: | (NSError **) | error | |
Change magnification of live view.
If live view is not magnified, an error occurs.
| scale | Magnification of live view. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) changeRunMode: | (OLYCameraRunMode) | mode | |
| error: | (NSError **) | error | |
Change run mode of the camera.
Available camera features change for different run modes. For example, application should change the mode to OLYCameraRunModePlayback when shooting photographs, and should change the mode to OLYCameraRunModeRecording when getting a list of the camera contents. Please refer to the related documentation for more information on relationship between run mode and available camera features.
Response of this API may become slow when shooting or writing to memory card.
| mode | Run mode of the camera. |
| error | Error details will be set when the operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) changeTime: | (NSDate *) | date | |
| error: | (NSError **) | error | |
Change date and time of camera.
When capturing without specifying date and time in the camera, a wrong value is set to metadata of media (still image and movie) and time stamp of media file.
Date and time must be specified in Greenwich Mean Time (GMT), with time zone set in the mobile device. OS standard API returns date and time in GMT format, and this method can use the returned value without changing the format.
| date | Date and time. |
| error | Error details will be set when the operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) clearAutoExposurePoint: | (NSError **) | error |
Release specified coordinates of reference exposure for automatic exposure control.
Set camera property "AE" to "AE_PINPOINT" before calling this method.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) clearAutoFocusPoint: | (NSError **) | error |
Clear coordinates used for auto focus.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) clearGeolocation: | (NSError **) | error |
Discard registered geolocation information.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) connect: | (OLYCameraConnectionType) | connectionType | |
| error: | (NSError **) | error | |
Connect to the camera.
Connection to the camera is complete, the application will be able to use features of the SDK. If the application wants to change the connection type when it is already connected to the camera, the application must disconnect and connect again.
| connectionType | Type of connection. You cannot specify 'not connected'. |
| error | Error details will be set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraConnection).
| - (BOOL) connectingRequiresBluetoothPassword: | (NSError **) | error |
Indicate if camera requires a password for Bluetooth Smart connection.
| error | Error details will be set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraConnection).
| - (NSInteger) countNumberOfContents: | (NSError **) | error |
Count the number of media (still image and movie) in the camera.
| error | Error details are set when the operation is abnormally terminated. |
If the number of the acquired media is zero, an error may occur. If the application wants to know the exact number of media, the application should check that error details are not set.
Provided by category OLYCamera(Playback).
| - (NSDictionary *) digitalZoomScaleRange: | (NSError **) | error |
Get configurable magnification range of digital zoom.
| error | Error details are set when operation is abnormally terminated. |
The following information is included.
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) disconnectWithPowerOff: | (BOOL) | powerOff | |
| error: | (NSError **) | error | |
Disconnect from the camera.
You can also power off the camera when you disconnect from the camera. If disconnect is successful, the value of the property and state of the camera will be cleared. (Communication settings of the camera connection are not cleared.)
| powerOff | If true, the camera will be powered off with disconnection from the camera. |
| error | Error details will be set when the operation is abnormally terminated. |
Provided by category OLYCamera(CameraConnection).
| - (void) downloadContent: | (NSString *) | path | |
| progressHandler: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)(NSData *data)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Download media (still image and movie) stored in memory card.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image or movie. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Provided by category OLYCamera(Playback).
| - (void) downloadContentList: | (void(^)(NSMutableArray *list, NSError *error)) | handler |
Download list of all supported media (still image and video) in the camera.
Download list of files in /DCIM directory of memory card that is inserted in the camera. List contains all still image and movie files in supported format. Application should distinguish unsupported files using file extension and eliminate them from the list before use.
| handler | Callback used when download is complete. |
Argument of download completion callback.
Each element of the list is in dictionary format. Dictionary key is defined to access the element.
Please refer to the related documentation for more information on extended information.
Provided by category OLYCamera(Playback).
| - (void) downloadContentScreennail: | (NSString *) | path | |
| progressHandler: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)(NSData *data)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Download reduced image of media (still image and movie) stored in memory card.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image or movie. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Provided by category OLYCamera(Playback).
| - (void) downloadContentThumbnail: | (NSString *) | path | |
| progressHandler: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)(NSData *data, NSMutableDictionary *metadata)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Download thumbnail of media (still image and movie) stored in memory card.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image or movie. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Provided by category OLYCamera(Playback).
| - (void) downloadImage: | (NSString *) | path | |
| withResize: | (OLYCameraImageResize) | resize | |
| progressHandler: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)(NSData *data)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Download a resized still image.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image. |
| resize | Size in number of pixels after resizing. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Provided by category OLYCamera(Playback).
| - (void) downloadLargeContent: | (NSString *) | path | |
| progressHandler: | (void(^)(NSData *data, float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)()) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Split large media (still image or movie) into smaller parts and download each part.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image or movie. |
| progressHandler | Callback used when the part is downloaded. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of errorHandler
Provided by category OLYCamera(Playback).
| - (void) downloadLastCapturedImage: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)(NSData *data)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Download the last captured image.
Download the still image in the original size captured that was saved through the last shooting process. This API may not return an expected image if the camera does not finish writing the image to the memory card. Call this API after the camera finishes writing the image to the memory card.
Only the last one image is returned even if continuous shooting is enabled.
| progressHandler | Callback used when download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progress callback
Argument of download completion callback
Argument of abnormal termination callback
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) eraseContent: | (NSString *) | path | |
| error: | (NSError **) | error | |
Delete media (still image and movie) stored in memory card.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs. When the application tries to delete the protected media, an error occurs.
| path | File path of the media. |
| error | Error details are set when the operation is abnormally terminated. |
Provided by category OLYCamera(PlaybackMaintenance).
| - (id) initWithDispatchQueue: | (dispatch_queue_t) | dispatchQueue |
Initialize new camera instance.
| dispatchQueue | Dispatch queue for callback. |
| - (NSDictionary *) inquireContentInformation: | (NSString *) | path | |
| error: | (NSError **) | error | |
Get information of media (still image and movie) stored in memory card.
File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path to the still image or movie. |
| error | Error details are set when the operation is abnormally terminated. |
Information on still image
Information on movie (string format)
Provided by category OLYCamera(Playback).
| - (NSDictionary *) inquireHardwareInformation: | (NSError **) | error |
Get hardware information of the camera.
| error | Error details will be set when the operation is abnormally terminated. |
Hardware information is in dictionary format. The following keys are defined in order to access each element.
Please refer to the related documentation for more information.
Provided by category OLYCamera(CameraSystem).
| - (BOOL) lockAutoExposure: | (NSError **) | error |
Lock operation of automatic exposure control.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (void) lockAutoFocus: | (void(^)(NSDictionary *info)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Lock autofocus operation.
Focus the camera to the specified coordinates, and then lock so that focus does not later change. The application must have previously set the coordinates for auto focus. The application must call unlock to resume auto focus.
| completionHandler | Callback used when lock is complete. |
| errorHandler | Callback used when lock was aborted. |
Argument of completionHandler
Argument of errorHandler
The application can convert rectangular coordinates in live view image using the coordinate conversion utility OLYCameraConvertRectOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
| - (NSDictionary *) magnifyingLiveViewArea: | (NSError **) | error |
Get display area information of magnified live view.
If live view is not magnified, an error occurs.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) protectContent: | (NSString *) | path | |
| error: | (NSError **) | error | |
Protect media (still image and movie) stored in memory card.
When the application tries to delete the protected media, an error occurs. File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path of the media. |
| error | Error details are set when the operation is abnormally terminated. |
Provided by category OLYCamera(PlaybackMaintenance).
| - (void) resizeVideoFrame: | (NSString *) | path | |
| size: | (CGFloat) | resize | |
| quality: | (OLYCameraResizeVideoQuality) | quality | |
| progressHandler: | (void(^)(float progress, BOOL *stop)) | progressHandler | |
| completionHandler: | (void(^)()) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Resize each frame of the video, and save it as a new file in the camera's memory card.
String that the application specifies in the file path of the content. String must combine the directory path and file name obtained from the downloaded contents list. If the application specifies a non-video file, the application will get an error.
| path | File path to the video content. |
| resize | Frame size in number of pixels after resizing. (only 1280 is valid in current version) |
| quality | Quality of video after resizing. |
| progressHandler | Callback used when the resizing progress changes. |
| completionHandler | Callback used when resizing is complete. |
| errorHandler | Callback used when resizing is abnormally terminated. |
Argument of progress callback
Argument of abnormal termination callback
Provided by category OLYCamera(Playback).
| - (BOOL) setAutoExposurePoint: | (CGPoint) | point | |
| error: | (NSError **) | error | |
Specify coordinates of reference exposure for automatic exposure control.
Application must set coordinates with this method prior to locking automatic exposure control. Application will get an error if value exceeds the valid range of target coordinates.
Set camera property "AE" to "AE_PINPOINT" before calling this method.
| point | Target coordinates. Coordinates are in viewfinder coordinate system. |
| error | Error details are set when operation is abnormally terminated. |
Application can convert the focusing coordinates from the coordinates in live view image using the coordinate conversion utility OLYCameraConvertPointOnLiveImageIntoViewfinder.
Provided by category OLYCamera(Recording).
| - (BOOL) setAutoFocusPoint: | (CGPoint) | point | |
| error: | (NSError **) | error | |
Set coordinates to use for auto focus.
Prior to locking focus, the application sets the coordinates to focus with this method. The application will get an error if value exceeds the valid range of focus coordinates.
| point | Coordinates where to focus. Coordinates are in viewfinder coordinate system. |
| error | Error details are set when operation is abnormally terminated. |
The application can convert the focusing coordinates from coordinates in live view image using the coordinate conversion utility OLYCameraConvertPointOnLiveImageIntoViewfinder.
Provided by category OLYCamera(Recording).
| - (BOOL) setCameraPropertyValue: | (NSString *) | name | |
| value: | (NSString *) | value | |
| error: | (NSError **) | error | |
Set value to the camera properties.
If the application specifies a value that does not exist in the list of camera properties currently available, the application will get an error. Depending on the setting value of the shooting mode and connection type etc., there are several properties that are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
The argument for parameter "value" is a string in the form of "<Property Name/Property Value>."
| name | The camera property name (e.g. "APERTURE", "SHUTTER", "ISO", "WB"). |
| value | Pair of property name and property value set in the property. (e.g. "<APERTURE/3.5>", "<SHUTTER/250>", "<ISO/Auto>", "<WB/WB_AUTO>") |
| error | Error details will be set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) setCameraPropertyValues: | (NSDictionary *) | values | |
| error: | (NSError **) | error | |
Set values to camera properties.
Specifying a value that does not exist in the list of camera properties currently available, will give an error. Depending on the setting value of the shooting mode, connection type, etc., several properties are read-only access or prohibited. Please refer to the documentation of the camera list of properties for more information.
| values | The pairs of the camera property value and name. |
| error | Error details will be set when operation is abnormally terminated. |
Name-value pairs of the camera properties that can be specified in dictionary format. The application must specify the camera property name in the dictionary key and store the value associated with that key in the camera properties.
Provided by category OLYCamera(CameraSystem).
| - (BOOL) setGeolocation: | (NSString *) | location | |
| error: | (NSError **) | error | |
Register geolocation information to the camera.
After the application registers the current geolocation in the camera, the GPS geolocation information will be set in the meta-data of the picture during capture.
The geolocation information must be specified by GGA and RMC defined in NMEA-0183.
| location | The new geolocation information. |
| error | Error details will be set when the operation is abnormally terminated. |
Provided by category OLYCamera(CameraSystem).
| - (BOOL) startDrivingZoomLensForDirection: | (OLYCameraDrivingZoomLensDirection) | direction | |
| speed: | (OLYCameraDrivingZoomLensSpeed) | speed | |
| error: | (NSError **) | error | |
Start driving optical zoom with specific speed and direction.
Lens attached to the camera must support electric zoom. If the optical zoom is already being driven, application will get an error.
| direction | Driving direction. |
| speed | Driving speed. |
| error | Error details are set when the operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) startDrivingZoomLensToFocalLength: | (float) | focalLength | |
| error: | (NSError **) | error | |
Start driving optical zoom to the specified focal length.
Lens attached to the camera must support electric zoom. If the optical zoom is already being driven, application will get an error.
| focalLength | Focal length. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) startLiveView: | (NSError **) | error |
Start live view.
If live view is not started, some properties cannot update their values, and some methods for taking pictures and recording movies return an error.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) startMagnifyingLiveView: | (OLYCameraMagnifyingLiveViewScale) | scale | |
| error: | (NSError **) | error | |
Start magnifying live view.
If live view is already magnified, an error occurs.
| scale | Magnification of live view. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) startMagnifyingLiveViewAtPoint: | (CGPoint) | point | |
| scale: | (OLYCameraMagnifyingLiveViewScale) | scale | |
| error: | (NSError **) | error | |
Start magnifying live view with center coordinate of magnification.
If live view is already magnified, an error occurs.
| point | Center coordinate of the magnified display in viewfinder coordinate system. The viewfinder coordinate system is explained in coordinate conversion utilities section of functions menu. |
| scale | Magnification of live view. |
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (void) startRecordingVideo: | (NSDictionary *) | options | |
| completionHandler: | (void(^)()) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Start recording movie.
Call this method only when recording process is not in progress. Do not call this method under still image shooting mode.
| options | Not used in current version. |
| completionHandler | Callback used when start of recording is complete. |
| errorHandler | Callback used when the start of recording is aborted. |
Argument of errorHandler
Provided by category OLYCamera(Recording).
| - (void) startTakingPicture: | (NSDictionary *) | options | |
| progressHandler: | (void(^)(OLYCameraTakingProgress progress, NSDictionary *info)) | progressHandler | |
| completionHandler: | (void(^)()) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Start shooting photo.
Call this method only when shooting process is not in progress. Do not call this method under movie recoding mode.
| options | Optional parameters of the shooting. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Optional shooting parameters.
Argument of progressHandler
Argument of errorHandler
The application can convert the rectangular coordinates in live view image using the coordinate conversion utility OLYCameraConvertRectOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
| - (BOOL) stopDrivingZoomLens: | (NSError **) | error |
Stop driving optical zoom.
Lens attached to the camera must support electric zoom. If the optical zoom is already being driven, application will get an error.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (BOOL) stopLiveView: | (NSError **) | error |
Stop live view.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) stopMagnifyingLiveView: | (NSError **) | error |
Stop magnifying live view.
If live view is not magnified, an error occurs.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(RecordingSupports).
| - (void) stopRecordingVideo: | (void(^)(NSDictionary *info)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Finish recording movie.
Call this method only when recording process is in progress. Do not call this method under still image shooting mode.
| completionHandler | Callback used when end of recording is complete. |
| errorHandler | Callback used when end of recording is aborted. |
Provided by category OLYCamera(Recording).
| - (void) stopTakingPicture: | (void(^)(OLYCameraTakingProgress progress, NSDictionary *info)) | progressHandler | |
| completionHandler: | (void(^)(NSDictionary *info)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Finish shooting photo.
Call this method only when shooting process is in progress. Do not call this method under movie recoding mode.
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Provided by category OLYCamera(Recording).
| - (void) takePicture: | (NSDictionary *) | options | |
| progressHandler: | (void(^)(OLYCameraTakingProgress progress, NSDictionary *info)) | progressHandler | |
| completionHandler: | (void(^)(NSDictionary *info)) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Execute batch operation from start of shooting photos to end of shooting.
Call this method only when shooting process is not in progress. Do not call this method under movie recoding mode.
| options | Optional parameters of the shooting. |
| progressHandler | Callback used when the download progress changes. |
| completionHandler | Callback used when download is complete. |
| errorHandler | Callback used when download is aborted. |
Optional shooting parameters
Argument of progressHandler
Argument of completionHandler
Argument of errorHandler
Application can convert rectangular coordinates in live view image using coordinate conversion utility OLYCameraConvertRectOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
| - (BOOL) unlockAutoExposure: | (NSError **) | error |
Release lock of automatic exposure control.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (BOOL) unlockAutoFocus: | (NSError **) | error |
Unlock autofocus operation.
| error | Error details are set when operation is abnormally terminated. |
Provided by category OLYCamera(Recording).
| - (void) unprotectAllContents: | (void(^)(float progress)) | progressHandler | |
| completionHandler: | (void(^)()) | completionHandler | |
| errorHandler: | (void(^)(NSError *error)) | errorHandler | |
Cancel protection of all the media (still image and movie) stored in memory card.
| progressHandler | Callback used when cancellation progress changes. |
| completionHandler | Callback used when cancellation is complete. |
| errorHandler | Callback used when cancellation is aborted. |
Argument of progressHandler
Argument of errorHandler
Provided by category OLYCamera(PlaybackMaintenance).
| - (BOOL) unprotectContent: | (NSString *) | path | |
| error: | (NSError **) | error | |
Cancel protection of the media (still image and movie) stored in memory card.
When the protection is canceled, the application is allowed to delete the media. File path must be string which combines the directory path and file name obtained from list of all supported media. Otherwise an error occurs.
| path | File path of the media. |
| error | Error details are set when the operation is abnormally terminated. |
Provided by category OLYCamera(PlaybackMaintenance).
| - (BOOL) wakeup: | (NSError **) | error |
Wake up the camera via Bluetooth Smart.
After the camera turns on, the application can connect to the camera. If the application is connected to the camera, the application will get an error.
| error | Error details will be set when operation is abnormally terminated. |
Provided by category OLYCamera(CameraConnection).
|
readnonatomicstrong |
F value used by lens and camera.
This value can change depending on the state of the object and the shooting mode. This value can be changed when zooming where the focal length is set to the minimum aperture. Aperture value is set to the minimum value if the value to be set is smaller than the minimum value. Please refer to the documentation of the list of camera properties for more information.
This property is set only if the following conditions are met.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Coordinates focused with autofocus.
These coordinates are expressed in viewfinder coordinate system. The application can convert the coordinates in the live view image using the coordinate conversion utility OLYCameraConvertPointOnViewfinderIntoLiveImage.
Provided by category OLYCamera(Recording).
|
readnonatomicstrong |
Exposure compensation value used by the camera.
This value can change depending on the state of the object and the shooting mode. Please refer to the documentation of the list of camera properties for more information.
This property is set only if the following conditions are met.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Current focal length of the lens.
Provided by category OLYCamera(Recording).
|
readnonatomicstrong |
ISO sensitivity used by camera.
When ISO sensitivity of the camera property is set to automatic, the value that the camera has chosen will be set. This value can change depending on the state of the object and the shooting mode. Please refer to the documentation of the list of camera properties for more information.
This property is set only if the following conditions are met.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Indicate that out of range warning of ISO sensitivity is occurring in the camera.
When shooting during the warning, the image may be underexposed or overexposed.
Provided by category OLYCamera(Recording).
|
readnonatomicstrong |
Shutter speed used by the camera.
This value can change depending on the state of the object and the shooting mode. Please refer to the documentation of the list of camera properties for more information.
This property is set only if the following conditions are met.
Provided by category OLYCamera(Recording).
|
readwritenonatomicassign |
Indicate that live view starts automatically when run mode is changed to Recording mode.
If false, call API to start live view after changing run mode to Recording mode.
Provided by category OLYCamera(Recording).
|
readwritenonatomicstrong |
Password to connect via Bluetooth Smart to the camera.
The value may be used when you connect via Bluetooth Smart to the camera. Configure this value before starting connection via Bluetooth Smart.
Provided by category OLYCamera(CameraConnection).
|
readwritenonatomicstrong |
Bluetooth peripheral.
The value is used when you connect via Bluetooth Smart to the camera. Configure this value before starting connection via Bluetooth Smart.
Provided by category OLYCamera(CameraConnection).
|
readwritenonatomicassign |
If true, the camera starts recording setup after power on via Bluetooth Smart.
The value may be used when you connect via Bluetooth Smart to the camera. Configure this value before starting connection via Bluetooth Smart.
Provided by category OLYCamera(CameraConnection).
|
readnonatomicstrong |
List of camera property names currently available.
The application must check whether the target camera property is contained in the list or not. If not, the target property can not be configured.
Provided by category OLYCamera(CameraSystem).
|
readwritenonatomicassign |
Port number where the camera receives commands.
Value is used when you connect to the camera via Wi-Fi. Set value only if specific port number is needed. Default is TCP/80.
Provided by category OLYCamera(CameraConnection).
|
readnonatomicstrong |
Face recognition results.
Coordinate information of face detected by the camera is stored in dictionary format. The dictionary key is a string that represents the identification number. It is not possible to track the coordinates of a recognized face by relying on a specific identification number.
This property is set only if the following conditions are met.
Provided by category OLYCamera(RecordingSupports).
|
readnonatomicassign |
Indicate optical zoom is changing in the camera.
Provided by category OLYCamera(RecordingSupports).
|
readwritenonatomicassign |
Port number where Camera Kit receives events issued by the camera.
Value is used when you connect to the camera via Wi-Fi. Set value only if specific port number is needed. Default is TCP/65000.
Provided by category OLYCamera(CameraConnection).
|
readnonatomicassign |
Indicate that warning of the exposure metering is occurring in the camera.
Subject is too dark or too bright to be measured by the camera's exposure meter. When shooting during the warning, the image may be underexposed or overexposed.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Indicate that out of range warning of the exposure is occurring in the camera.
The camera can not determine ISO sensitivity, shutter speed or aperture value corresponding to current exposure value. When shooting during the warning, the image may be underexposed or overexposed.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Indicate if inside of the camera is in high-temperature condition.
You can also check using the lighting state of the LED on the camera body. If the inside of the camera has reached a high temperature, please stop using the camera immediately, and wait for the camera to return to normal temperature.
Provided by category OLYCamera(CameraSystem).
|
readwritenonatomicstrong |
IP address of the camera.
Value is used when you connect to the camera via Wi-Fi. Set value only if specific IP address is needed. Default is <IP_ADDRESS>.
Provided by category OLYCamera(CameraConnection).
|
readnonatomicstrong |
Indicate status of lens mount.
Status of lens mount:
Provided by category OLYCamera(CameraSystem).
|
readnonatomicstrong |
Information of level gauge.
The following information is included.
This property is set only if the following conditions are met.
Provided by category OLYCamera(RecordingSupports).
|
readnonatomicassign |
Indicate that live view started.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Frame size of live view in pixels.
Provided by category OLYCamera(Recording).
|
readwritenonatomicassign |
Port number where Camera Kit receives live view images.
Value is used when you connect to the camera via Wi-Fi. Set value only if specific port number is needed. Default is UDP/5555.
Provided by category OLYCamera(CameraConnection).
|
readnonatomicassign |
Indicate that live view is magnified.
Provided by category OLYCamera(RecordingSupports).
|
readnonatomicassign |
Focal length at the telephoto end of the lens.
This is the longest focal length of the lens.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
Indicate whether the camera is writing to the media (memory card).
You can also check in the lighting state of the LED on the camera body. While the camera is writing to the media, you will see API response is slow.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
Indicate whether the media (memory card) I/O error has occurred.
There is a possibility that the media is broken. Please replace with a new media if it occurs frequently.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicstrong |
Indicate status of media (memory card) mount.
Status of media mount:
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
Focal length at the wide end of the lens.
This is the shortest focal length of the lens.
Provided by category OLYCamera(Recording).
|
readwritenonatomicweak |
Delegate object that notifies camera state when it changes.
The camera state relates to capturing operation which affects still image or movie.
Provided by category OLYCamera(Recording).
|
readwritenonatomicweak |
Delegate object to notify camera state when it changes.
The camera state relates to capturing operation which affects still image or movie.
Provided by category OLYCamera(RecordingSupports).
|
readnonatomicassign |
Indicate that video recording is in progress on the camera.
When recording is in progress, the application cannot change the value of the camera properties.
Provided by category OLYCamera(Recording).
|
readnonatomicassign |
The maximum number of images that can be stored in the media (memory card).
The exact value depends on the data for the compression ratio of the captured image. Sometimes the value does not change after capturing.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
Free space of the media (memory card) attached to the camera.
Unit is byte.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
The maximum number of seconds a movie that can be stored in the media (memory card).
The exact value depends on the data for the compression ratio of the captured video.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
Current run mode of the camera system.
Provided by category OLYCamera(CameraSystem).
|
readnonatomicassign |
Indicate that photo shooting is in progress on the camera.
When shooting is in progress, the application cannot change the value of the camera properties.
Provided by category OLYCamera(Recording).


There isn't just one TV technology that is right for everyone. Some people might want cutting-edge 4K Ultra HD technology. Some may like the elegant, thin profile of LED TVs, while others will like the versatility of Smart TVs. That's why Mentor TV proudly features Samsung TV's. With Samsung, there is a flat-panel TV for virtually every taste, preference and budget.
Samsung's curved screen is supported with proprietary technology that creates an accurate picture with exceptional color, without any picture distortion. It has a dramatically improved field of view that creates a panoramic effect and helps the picture feel bigger. Become immersed in entertainment with a cutting-edge screen that surrounds you with 8.3 million pixels, creating a panoramic effect that's simply breathtaking.
Experience real world resolution with Ultra High Definition Smart TV's. Exclusive Samsung technologies deliver incredibly lifelike UHD 4K picture quality. Watch any movie, sport, disc or streaming app at 4 times the resolution of traditional 1080p HD with UHD Upscaling.
Samsung has become a world leader in HDTVs based on the amazing performance and popularity of their LED-LCD technology. Samsung LED TVs deliver a visually stunning picture that will leave you speechless. Select models feature Smart TV Technology - allowing you to quickly and simply browse a new world of TV entertainment.
Discover a new world of web-connected TV entertainment with Samsung Smart TV's at Mentor TV. Samsung Smart TVs allow you to easily search for movies, TV shows, browse the web, explore Samsung apps, chat with friends and find many other types of new interactive TV content.
Learn more about Samsung SMART TV's →


Teaching attention, part 3 / N: Thinking more creatively
To this point, our memory mechanisms all have had the same flavor. We had a running summary , which we update with every new input, though gating might mean we prevent some coordinates from changing too much. However, it’s possible to think more creatively about how we should record and attend to new memories. For example,
- We don’t need to throw away all but the last when making some prediction. We’ve been saying that a model “forgets” if there are values for early on which are erased by new inputs. But what if we just kept all the ’s, and avoided overload by having a smart lookup strategy?
- Why are we forcing the memory to architecturally mirror the inputs – that is, why does need to be a sequence? Considering that, due to gating, we only update some cells at a time, it makes sense to design architectures specifically adapted to recording and looking up useful summaries.
- We’ve assumed a pretty diligent sequential processor, which knows to check every input datapoint as it arrives. What if we had a lazy one, which played it fast and loose and tried to process only those inputs that seemed really crucial to the process.
These sorts of preposterous questions will help illuminate the more fundamental principles of memory and attention in deep learning1.
First though, a warning, reiterating points from part 1. Attention is not a well-defined, clearly demarcated mathematical term. It is a principle that is useful for reasoning about many problems, but which is always in flux, as people find variants that are suited to their particular settings.
To keep our discussion grounded, and to leave you with something mathematical examples (and not just cool paper titles) that you can take home, we’re going to explore a few attention mechanisms in detail, before briefly touring across other highlights of the memory and attention literature.
Our three methods mirror the three questions from before.
Attention in Translation Models
We don’t need to force to condense everything from . This observation lies at the heart of attention-based encoder-decoder sequence translation models. Before explaining the mechanism in more detail, a refresher on how translation works with neural networks.
Abstractly, the problem of translation is to map a sequence of words in one language to the corresponding sequence in another. For example,
I don’t speak French –> Je ne parle pas le Francais.
We make this an ML problem by treating each word as a datapoint in a sequence, and hoping to map the first trajectory into the second. That is, we want to map
where is a one-hot encoding of the word in the sentence (with respect to the words in English that we bother taking into account), and does the same for French.
The encoder-decoder approach to the problem is to take the and summarize (“encode”) them using an RNN2. The final state $h_{T}$ is then used as the used as the initial state to a separate RNN, whose states are used to predict the words of the translation. Here’s a basic picture. The shading means that teh same values are copied over.
At the time step during decoding, we use a processor , and then predict using logistic regression. A good processor should be able to capture the salient features of , and these are used for translation.
This seems like a large burden for the encoder to carry. Intuitively, at time of decoding, you really only care about the words in the corresponding neigorhood of time in the source sentence. If the sentences were already aligned, you’d expect the neighborhood around to be most relevant for being able to translate .
So, consider the mechanism, , which adds columns weighted by ’s, which we call attention weights. Of course, we need the ’s to be learned directly from data – this is the same problem as in gatings. The solution shouldn’t be a surprise: we use a differentiable, parameterized function. For example, we could use
to measure the angle between particular coordinates of the encodings.
It’s worth highlighting what doesn’t directly appear in this definition – the times and themselves. This version of attention is a purely “content-based” form of attention, which cares only about the encodings and . There are variants that take the times themselves into account, so that the decoding at time explicitly upweights encodings at around that time in the original sequence2.
There are a lot of moving parts here – an encoder, a decoder, and an attention module to link them together. But everything is end-to-end differentiable, and you can take the gradients of mistranslations with respect to all parameters.
Stepping back, this is a way of reweighting – or attending to – specific encodings as a function of our current position in the decoding task at hand. We have provided some much needed relief for our lone encoder by more richly relating elements of our differentiable system. We no longer need a processor that compresses everything into one statistic because we have a more sophisticated way of navigating a large collection of summaries and pulling out what is useful.
This kind of search for locally relevant information is a hallmark of attention mechanisms. More specifically, this pattern of breaking a task into pieces and finding a way to learn different distributions over relevant summaries is one that appears througout the literature on soft-attention mechanisms.
Neural Turing Machines
This discussion suggests that more carefully structured (if potentially intricate) mechanisms for looking thigns up can alleviate problems of remembering information that was introduced long ago. This is actually a general principle, not just some quirk about encoder-decoder architectures. To illustrate this, we consider the Neural Turing Machine.
Again, there is a bit going on. The diagram below introduces the cast of characters.
Given new input, we produce a weight distribution for what seem like the most relevant memory locations. Notice that if the rows correspond to times , then the matrix is a lot like a stacked version of the from the RNN models before. And, the ’s do seem eerily like the attention weights from before. That said, we’re trying to free ourselves from the idea that memories must be indexed by time.
In this spirit of generalization, we can define soft-attention variant,
Something in this architecture which is new, and not just a variant of what we saw before in translation, is a notion of writing to memory. We use weights, along with the add and erase vectors, to define a memory update,
If the weight is small, we don’t change that location in memory at all. If it is large, we add in and erase everything that had been at that row, with an aggressiveness controlled by (coordinates where that vector is near are almost entirely reset).
The only remaining issue is how to figure out a good combination of parameters , and , upon seeing a new input .
Kris at 09:12


Linearization in Physics/Mechanics¶
mechanics
includes methods for linearizing the generated equations of
motion (EOM) about an operating point (also known as the trim condition).
Note that this operating point doesn’t have to be an equilibrium position, it
just needs to satisfy the equations of motion.
Linearization is accomplished by taking the first order Taylor expansion of the EOM about the operating point. When there are no dependent coordinates or speeds this is simply the jacobian of the right hand side about \(q\) and \(u\). However, in the presence of constraints more care needs to be taken. The linearization methods provided here handle these constraints correctly.
Background¶
In mechanics
we assume all systems can be represented in the following
general form:
where
In this form,
- \(f_{c}\) represents the configuration constraint equations
- \(f_{v}\) represents the velocity constraint equations
- \(f_{a}\) represents the acceleration constraint equations
- \(f_{0}\) and \(f_{1}\) form the kinematic differential equations
- \(f_{2}\), \(f_{3}\), and \(f_{4}\) form the dynamic differential equations
- \(q\) and \(\dot{q}\) are the generalized coordinates and their derivatives
- \(u\) and \(\dot{u}\) are the generalized speeds and their derivatives
- \(r\) is the system inputs
- \(\lambda\) is the Lagrange multipliers
This generalized form is held inside the Linearizer
class, which
performs the actual linearization. Both KanesMethod
and
LagrangesMethod
objects have methods for forming the linearizer using
the to_linearizer
class method.
A Note on Dependent Coordinates and Speeds
If the system being linearized contains constraint equations, this results in not all generalized coordinates being independent (i.e. \(q_1\) may depend on \(q_2\)). With \(l\) configuration constraints, and \(m\) velocity constraints, there are \(l\) dependent coordinates and \(m\) dependent speeds.
In general, you may pick any of the coordinates and speeds to be dependent, but in practice some choices may result in undesirable singularites. Methods for deciding which coordinates/speeds to make dependent is behind the scope of this guide. For more information, please see [Blajer1994].
Once the system is coerced into the generalized form, the linearized EOM can be
solved for. The methods provided in mechanics
allow for two different
forms of the linearized EOM:
- \(M\), \(A\), and \(B\)
In this form, the forcing matrix is linearized into two separate matrices \(A\) and \(B\). This is the default form of the linearized EOM. The resulting equations are:
\[\begin{split}M \begin{bmatrix} \delta \dot{q} \\ \delta \dot{u} \\ \delta \lambda \end{bmatrix} = A \begin{bmatrix} \delta q_i \\ \delta u_i \end{bmatrix} + B \begin{bmatrix} \delta r \end{bmatrix}\end{split}\]where
\[\begin{split}M &\in \mathbb{R}^{(n+o+k) \times (n+o+k)}\\ A &\in \mathbb{R}^{(n+o+k) \times (n-l+o-m)}\\ B &\in \mathbb{R}^{(n+o+k) \times s}\end{split}\]Note that \(q_i\) and \(u_i\) are just the independent coordinates and speeds, while \(q\) and \(u\) contains both the independent and dependent coordinates and speeds.
- \(A\) and \(B\)
In this form, the linearized EOM are brought into explicit first order form, in terms of just the independent coordinates and speeds. This form is often used in stability analysis or control theory. The resulting equations are:
\[\begin{split}\begin{bmatrix} \delta \dot{q_i} \\ \delta \dot{u_i} \end{bmatrix} = A \begin{bmatrix} \delta q_i \\ \delta u_i \end{bmatrix} + B \begin{bmatrix} \delta r \end{bmatrix}\end{split}\]where
\[\begin{split}A &\in \mathbb{R}^{(n-l+o-m) \times (n-l+o-m)}\\ B &\in \mathbb{R}^{(n-l+o-m) \times s}\end{split}\]To use this form set
A_and_B=True
in thelinearize
class method.
Linearizing Kane’s Equations¶
After initializing the KanesMethod
object and forming \(F_r\) and \(F_r^*\)
using the kanes_equations
class method, linearization can be accomplished
in a couple ways. The different methods will be demonstrated with a simple
pendulum system:
>>> from sympy import symbols, Matrix
>>> from sympy.physics.mechanics import *
>>> q1 = dynamicsymbols('q1') # Angle of pendulum
>>> u1 = dynamicsymbols('u1') # Angular velocity
>>> q1d = dynamicsymbols('q1', 1)
>>> L, m, t, g = symbols('L, m, t, g')
>>> # Compose world frame
>>> N = ReferenceFrame('N')
>>> pN = Point('N*')
>>> pN.set_vel(N, 0)
>>> # A.x is along the pendulum
>>> A = N.orientnew('A', 'axis', [q1, N.z])
>>> A.set_ang_vel(N, u1*N.z)
>>> # Locate point P relative to the origin N*
>>> P = pN.locatenew('P', L*A.x)
>>> vel_P = P.v2pt_theory(pN, N, A)
>>> pP = Particle('pP', P, m)
>>> # Create Kinematic Differential Equations
>>> kde = Matrix([q1d - u1])
>>> # Input the force resultant at P
>>> R = m*g*N.x
>>> # Solve for eom with kanes method
>>> KM = KanesMethod(N, q_ind=[q1], u_ind=[u1], kd_eqs=kde)
>>> fr, frstar = KM.kanes_equations([pP], [(P, R)])
1. Using the Linearizer
class directly:¶
A linearizer object can be created using the to_linearizer
class method.
This coerces the representation found in the KanesMethod
object into the
generalized form described above. As the independent and dependent
coordinates and speeds are specified upon creation of the KanesMethod object,
there is no need to specifiy them here.
>>> linearizer = KM.to_linearizer()
The linearized EOM can then be formed with the linearize
method of the
Linearizer
object:
>>> M, A, B = linearizer.linearize()
>>> M
Matrix([
[1, 0],
[0, -L**2*m]])
>>> A
Matrix([
[ 0, 1],
[L*g*m*cos(q1(t)), 0]])
>>> B
Matrix(0, 0, [])
Alternatively, the \(A\) and \(B\) form can be generated instead by specifying
A_and_B=True
:
>>> A, B = linearizer.linearize(A_and_B=True)
>>> A
Matrix([
[ 0, 1],
[-g*cos(q1(t))/L, 0]])
>>> B
Matrix(0, 0, [])
An operating point can also be specified as a dictionary or an iterable of dictionaries. This will evaluate the linearized form at the specified point before returning the matrices:
>>> op_point = {q1: 0, u1: 0}
>>> A_op, B_op = linearizer.linearize(A_and_B=True, op_point=op_point)
>>> A_op
Matrix([
[ 0, 1],
[-g/L, 0]])
Note that the same effect can be had by applying msubs
to the matrices
generated without the op_point
kwarg:
>>> assert msubs(A, op_point) == A_op
Sometimes the returned matrices may not be in the most simplified form.
Simplification can be performed after the fact, or the Linearizer
object
can be made to perform simplification internally by setting the simplify
kwarg to True
.
2. Using the linearize
class method:¶
The linearize
method of the KanesMethod
class is provided as a nice
wrapper that calls to_linearizer
internally, performs the linearization,
and returns the result. Note that all the kwargs available in the
linearize
method described above are also available here:
>>> A, B, inp_vec = KM.linearize(A_and_B=True, op_point=op_point, new_method=True)
>>> A
Matrix([
[ 0, 1],
[-g/L, 0]])
The additional output inp_vec
is a vector containing all found
dynamicsymbols
not included in the generalized coordinate or speed
vectors. These are assumed to be inputs to the system, forming the \(r\) vector
described in the background above. In this example there are no inputs, so
the vector is empty:
>>> inp_vec
Matrix(0, 0, [])
What’s with the new_method
kwarg?
Previous releases of SymPy
contained a linearization method for
\(KanesMethod`\) objects. This method is deprecated, and will be removed
from future releases. Until then, you must set new_method=True
in all
calls to KanesMethod.linearize
. After the old method is removed, this
kwarg will no longer be needed.
Linearizing Lagrange’s Equations¶
Linearization of Lagrange’s equations proceeds much the same as that of Kane’s equations. As before, the process will be demonstrated with a simple pendulum system:
>>> # Redefine A and P in terms of q1d, not u1
>>> A = N.orientnew('A', 'axis', [q1, N.z])
>>> A.set_ang_vel(N, q1d*N.z)
>>> P = pN.locatenew('P', L*A.x)
>>> vel_P = P.v2pt_theory(pN, N, A)
>>> pP = Particle('pP', P, m)
>>> # Solve for eom with Lagranges method
>>> Lag = Lagrangian(N, pP)
>>> LM = LagrangesMethod(Lag, [q1], forcelist=[(P, R)], frame=N)
>>> lag_eqs = LM.form_lagranges_equations()
1. Using the Linearizer
class directly:¶
A Linearizer
object can be formed from a LagrangesMethod
object using
the to_linearizer
class method. The only difference between this process
and that of the KanesMethod
class is that the LagrangesMethod
object
doesn’t already have its independent and dependent coordinates and speeds
specified internally. These must be specified in the call to
to_linearizer
. In this example there are no dependent coordinates and
speeds, but if there were they would be included in the q_dep
and
qd_dep
kwargs:
>>> linearizer = LM.to_linearizer(q_ind=[q1], qd_ind=[q1d])
Once in this form, everything is the same as it was before with the
KanesMethod
example:
>>> A, B = linearizer.linearize(A_and_B=True, op_point=op_point)
>>> A
Matrix([
[ 0, 1],
[-g/L, 0]])
2. Using the linearize
class method:¶
Similar to KanesMethod
, the LagrangesMethod
class also provides a
linearize
method as a nice wrapper that calls to_linearizer
internally, performs the linearization, and returns the result. As before, the
only difference is that the independent and dependent coordinates and speeds
must be specified in the call as well:
>>> A, B, inp_vec = LM.linearize(q_ind=[q1], qd_ind=[q1d], A_and_B=True, op_point=op_point)
>>> A
Matrix([
[ 0, 1],
[-g/L, 0]])
Potential Issues¶
While the Linearizer
class should be able to linearize all systems,
there are some potential issues that could occur. These are discussed below,
along with some troubleshooting tips for solving them.
1. Symbolic linearization with A_and_B=True
is slow¶
This could be due to a number of things, but the most likely one is that
solving a large linear system symbolically is an expensive operation.
Specifying an operating point will reduce the expression size and speed
this up. If a purely symbolic solution is desired though (for application
of many operating points at a later period, for example) a way to get
around this is to evaluate with A_and_B=False
, and then solve
manually after applying the operating point:
>>> M, A, B = linearizer.linearize()
>>> M_op = msubs(M, op_point)
>>> A_op = msubs(A, op_point)
>>> perm_mat = linearizer.perm_mat
>>> A_lin = perm_mat.T * M_op.LUsolve(A_op)
>>> A_lin
Matrix([
[ 0, 1],
[-g/L, 0]])
The fewer symbols in A
and M
before solving, the faster this
solution will be. Thus, for large expressions, it may be to your benefit
to delay conversion to the \(A\) and \(B\) form until most symbols are subbed
in for their numeric values.
2. The linearized form has nan
, zoo
, or oo
as matrix elements¶
There are two potential causes for this. The first (and the one you should check first) is that some choices of dependent coordinates will result in singularities at certain operating points. Coordinate partitioning in a systemic manner to avoid this is beyond the scope of this guide; see [Blajer1994] for more information.
The other potential cause for this is that the matrices may not have been in the most reduced form before the operating point was substituted in. A simple example of this behavior is:
>>> from sympy import sin, tan
>>> expr = sin(q1)/tan(q1)
>>> op_point = {q1: 0}
>>> expr.subs(op_point)
nan
Note that if this expression was simplified before substitution, the correct value results:
>>> expr.simplify().subs(op_point)
1
A good way of avoiding this hasn’t been found yet. For expressions of
reasonable size, using msubs
with smart=True
will apply an
algorithm that tries to avoid these conditions. For large expressions
though this is extremely time consuming.
>>> msubs(expr, op_point, smart=True)
1
Further Examples¶
The pendulum example used above was simple, but didn’t include any dependent coordinates or speeds. For a more thorough example, the same pendulum was linearized with dependent coordinates using both Kane’s and Lagrange’s methods:


| with_env {rlang} | R Documentation |
These functions evaluate expr
within a given environment (env
for with_env()
, or the child of the current environment for
locally
). They rely on eval_bare()
which features a lighter
evaluation mechanism than base R base::eval()
, and which also has
some subtle implications when evaluting stack sensitive functions
(see help for eval_bare()
).
with_env(env, expr) locally(expr)
env |
An environment within which to evaluate |
expr |
An expression to evaluate. |
locally()
is equivalent to the base function
base::local()
but it produces a much cleaner
evaluation stack, and has stack-consistent semantics. It is thus
more suited for experimenting with the R language.
These functions are experimental. Expect API changes.
# with_env() is handy to create formulas with a given environment: env <- child_env("rlang") f <- with_env(env, ~new_formula()) identical(f_env(f), env) # Or functions with a given enclosure: fn <- with_env(env, function() NULL) identical(get_env(fn), env) # Unlike eval() it doesn't create duplicates on the evaluation # stack. You can thus use it e.g. to create non-local returns: fn <- function() { g(current_env()) "normal return" } g <- function(env) { with_env(env, return("early return")) } fn() # Since env is passed to as_environment(), it can be any object with an # as_environment() method. For strings, the pkg_env() is returned: with_env("base", ~mtcars) # This can be handy to put dictionaries in scope: with_env(mtcars, cyl)


Pizza Order
It's okay to order a pizza.
Pick a size:
Small
Medium
Large
Add a topping:
Pepporoni
Anchovies
Veggie
Olives
Pineapple
Delivery Options:
Please Deliver
No Thanks
Order Pizza
Price: $


Newcastle United have said this ahead of Aston Villa clash - and Steve Bruce will love it
Latest Aston Villa news | Steve Bruce returns to Villa Park as manager of Newcastle on Monday
by Shane Ireland, https://www.facebook.com/ShaneIrelandJournalistNewcastle United have hinted that they could be boosted by the return of two players against Aston Villa.
The Magpies visit Villa Park on Monday evening for what will be Steve Bruce’s first return to his former club since his sacking last October.
Bruce, 58, was relieved of his duties as Villa boss 13 months ago after a poor run of form saw them plummet down the Championship table.
A 3-3 draw with Preston North End, who were then bottom of the league, proved to be the breaking point for Villa after an evening which also saw a fan hurl a cabbage in Bruce’s direction.
Aston Villa latest
This is your round up of all things Villa; the one-stop shop that will keep you updated on the latest goings on at the club and beyond.
Transfers, injuries, match-days and managers, we’ve got you covered.
We’ll be bringing the very latest on the Villains throughout the week and around the clock.
Make sure you keep yourself updated with our handy daily catch up...
Must reads...
- Director reveals John McGinn's reaction to failed transfer
- Martin Keown fires puzzling criticism at Tyrone Mings
- What Jarrad Branthwaite has said about Villa interest
- Dean Smith urged to have a 'quiet word' with Frederic Guilbert
For all your latest AVFC news, opinion, analysis and transfer gossip, click here
You can follow our Villa reporter Ashley Preece on Twitter, and his email address is<EMAIL_ADDRESS>Bruce will be hoping for a happier night on his upcoming visit and he is set to have two defenders back at his disposal.
Posting on social media on Wednesday, Newcastle indicated that Florian Lejeune and Fabian Schar are set to return to action.
Lejeuene is a long-term absentee having been sidelined for most of the year with a knee injury, while Schar missed the last Premier League match as well as Switzerland’s most recent Euro 2020 qualifiers also with a knee problem.
But the north-east club shared images of the duo in the gym with emojis which said “back soon”.
Their potential return is a timely boost for Newcastle who saw captain Jamaal Lascelles suffer a serious injury against Bournemouth prior to the international break.
The centre-back is likely to be out for the rest of 2019 having been hurt during a tussle with Callum Wilson during the 2-1 win.


In the "File" menu, you can find two functions meant for manipulating the database as a single object, rather than a collection of credentials.
The "Export" function will save the database as a .crdb file at a place of your choosing. You can then move the database to a different computer, back it up to the cloud like
an ordinary file, and so forth.
The "Import" function will allow you to import either a previously exported database file (usually with a .crdb extension), or a backup (usually with a .crdb.bak extension).
However, you can also use it to import a database from older versions of the software (< 2.1.0, usually with either a .db or .db.bak extension), at which point the software
will automatically convert it to the new binary file format.
The "Merge" function will append a previously exported database's entries to your current database, using pattern matching to get rid of possible duplicate entries.


{% extends 'base/base.html' %} {% block main_content %}
There are a lot of ways our app could be used and so there is a lot of associated data, some of which we or our third party service retain.
We try to keep the data secure and the same can be said of the third party services like Firebase, google play services and any other third party service we use. But somethimes there may be situations in which there is leakage of data, for which we hold no responsibility. We cannot be held responsible for any kind of problem, whatever the cause, that our Pet app creates.
In our app, you can store images and files too. Some parts of this storage is managed or implemented by third party services, so it is wise to not store anything that may require high level of privacy or even somewhat privacy in our app.
When you upload a file of any kind, even images or photos, or even take pictures or select images through our app, it is stored in the cache of your device before it is uploaded to the cloud storage. The cached files are periodically deleted to free up storage.
Some bug or even any other kind of mistake can cause any of the files to be deleted prematurely, or in time that may be unfavorable to you. So, please do not store any important material in our app.
We cannot be held responsible in any way for any problem that is caused by or is related to our Pet app in any way. Please note that our Pet app is a very social app that has limited privacy protection that may fail due to some errors that we may or may not be aware of.
We use Ad Sense to display ads that may be relevant to you. We or our third party service store some of your data to display more personalized ads to you. Please read our privacy policy. We cannot be held responsible for problems caused or related to leakage of your personal data.


My Thoughts About the United States Banning TikTok
These are my personal thoughts about the United States banning TikTok.
As you may have already heard, some congressional leaders have proposed the ban of a Chinese based social media application called TikTok.
There is fear, with some truth mixed in, that TikTok is a danger to United States national defense. There are many reasons congressional, military, and other policy leaders fear TikTok, but the common theme seems to be related to data collection on American citizens and the potential of manipulating viewpoints in favor of the Chinese government.
There are legitimate points of concern, but I will argue that there needs to be consensus on why we want to take the extreme measure of blocking a service, which can be easily circumvented by the average user. The current reasoning seems to be:
- Protection of US citizen data (e.g., location, likes, views, etc.)
- Protection of US citizens against foreign interference of societal normalcy (e.g., skewing what is watched, pro-China propaganda, etc.)
- Protection of military and strategic interests including service members usage
- Some other reason?
As far as I am aware, we have never blocked an entire service, especially one used by millions of US citizens. Doing so would set a dangerous precedent, in my opinion, which would alter how we view and potentially control the content on the internet.
Protection of US Citizens’ Data
A natural response when asked about why the US should block TikTok typically contains points surrounding protecting the American peoples’ data. This, in my opinion, is a fallacy. You can see this by the countless data breaches every year, and we have yet to implement data protection for our own citizens data. Thank you Dave Kennedy for first mentioning that our government should instead implement a GDPR data protection policy instead trying to block content directly.
If our political leaders claim that they want to block content in the name of protecting citizens, then why not protect citizens in a more universal manner like GDPR at a national level?
Citizens must understand that Amazon, Apple, Facebook, Google, Microsoft, etc. are all US based companies and have more data about their users than most governments. As an example, as of January of 2023 Microsoft processes an estimated 65 trillion signals a day—that data is more than just which Windows updates are being downloaded. Additionally, if Google or Facebook or etc. wanted to, they could easily alter how we view news, videos, data and more. It could be difficult to near impossible to detect.
If the real reason is protection of American citizen data, then we must focus on data protection policies and legislation here at home. We should focus on software improvements, new operating systems built with security in mind, education & training programs, etc.
Protection of US Citizens Against Foreign Interference
The other big argument I am seeing from politicians and government officials is regarding the protection of American citizens by stopping potential foreign interference. FBI Director Wray said on March 8th, 2023 in a Senate Intelligence Committee hearing on worldwide threats to U.S. security, that the Chinese government could also use TikTok to control software on millions of devices and drive narratives to divide Americans over Taiwan or other issues.
This is a valid concern, but I do not believe that the government should intervene with what content I should and should not be allowed to view. This, to me, is an extreme overreach and our government should not have the authority to restrict or promote certain content, no matter the impact. This is the foundation of the internet. The internet is (and should be) free and open to anyone. I do not believe that governments should impose their political beliefs upon others. This is exactly what we are accusing China of doing.
Protecting Military & Strategic Interests
Removing or forcing government entities, employees and contractors to remove / ban TikTok from their devices is appropriate and warranted. I do not believe that the government should take this same action against all Americans.
Additional Points
I want to make a point that may not align with most people’s viewpoints on this topic. Please understand this is my opinion only.
If we are trying to convince the public that banning TikTok is in our best national interest in order to protect citizens for government interference, then we must self-reflect. Whether you agree or not, the US government has performed warrantless surveillance on Americans, forced organizations to hand over user data, unlock phones/hardware, tapped (tapping?) backbone networks and way more.
I love this country, but I cannot stand by and watch politicians and government leaders pushing for blocking TikTok in the name of national defense and freedom when we have done the same thing that we accuse China of.
Many people, who are for the TikTok ban, reference laws in place in China which gives them unprecedented access to all public and private business data on request. This is a major concern. This does not happen in the US, but we have seen the US government accessing private data on American citizens many times over the last decade or longer. That difference matters but does it matter that much?
Alternatives
I’m not going to say I know the answer, but I do have some ideas on possible options that are far more productive:
- As I mentioned above, implement a form of GPDR as a new governmental body with legal and financial authority.
- Require physical hardware and data storage in North America (or just the US) (e.g., AWS/Azure/GCP/Alibaba/etc. data centers in the US).
- Foreign services must reside in Federal Government data centers or approved data centers.
- Shoot, this would suck but force network capture of all foreign company’s services to ensure exfiltration does not occur.
So?
As I have said before, I believe that banning TikTok would set a dangerous precedent. There are many other options that have a far better chance of protecting our citizens than a superficial ban does. I do not know the answer, but I do know that I do not want my government to interfere with what I can view, access or do on the internet. Period.


anode.
connecting
...
anode
.
all
power
.
now
energy
.
now
energy
.
today
energy
.
tomorrow
energy
.
overmorrow
internet
.
perth
comfort
.
temperature
comfort
.
carbon-dioxide
comfort
.
humidity
comfort
.
noise
weather
.
today
weather
.
tomorrow
weather
.
overmorrow
weather
.
rain
weather
.
wind
weather
.
humidity
weather
.
pressure
almanac
.
sun
version
.
UNKNOWN
plot
.
hour
.
today
.
3days
.
week
.
fortnight
.
all


Payment form example
Some fields are missing
Card #
CVC #
Amount
First Name
Last Name
City
State
Pick a state
no me
se los
estados
de
U
S
A
Postal Code
We accept:
Message
Add any note here.


#include <BillingListener.h>
Inheritance diagram for WFAPI::BillingListener:
Public Member Functions | |
| BillingListener () | |
| virtual | ~BillingListener () |
| virtual void | thirdPartyTransactionVerified (RequestID requestID)=0 |
Implement a sub class of BillingListener and add as a listener to the BillingInterface to start getting billing callbacks.
The error function, declared in the super class Listener, will be called for all requests that returns with an error.
| WFAPI::BillingListener::BillingListener | ( | ) |
Constructor with no arguments.
| virtual WFAPI::BillingListener::~BillingListener | ( | ) | [virtual] |
Destructor.
| virtual void WFAPI::BillingListener::thirdPartyTransactionVerified | ( | RequestID | requestID | ) | [pure virtual] |
Called upon succesful verification of a third party transaction by the server due to a previous call to BillingInterface::verifyThirdPartyTransaction. This means that the server has added the associated rights from the purchase to the current account. Failure to verify the transaction will lead to a call to Listener::error() instead.
| requestID | The request id for the callback matches the request id received in the AsynchronousStatus call to BillingInterface::verifyThirdPartyTransaction. |


React Embed
Run
npm run optimize
External, legacy code:
Embed React components:
Hello World loading...
Messenger loading...
SimpleDataTable loading...


parcoords
gives R
users the very well designed and interactive parallel-coordinates
chart for d3
with the infrastructure, flexibility, and robustness of htmlwidgets
. parcoords
began in the Building Widgets blog series Week 04 | Interactive Parallel Coordinates and has been refined and improved through production usage in various disciplines.
# from CRAN
# install.packages("parcoords")
# for the latest release
# devtools::install_github("timelyportfolio/parcoords")
library(parcoords)
data(mtcars)
parcoords(
mtcars
,reorderable = TRUE
,brushMode = "2d-strums"
)
Please note that the ‘parcoords’ project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms. I would love for anyone to participate, but please let’s be friendly and welcoming.


Gagandeep Bhatia
Reg. No 1960466
Email<EMAIL_ADDRESS>9466935025
Who am I?
Answering a question like this has often been difficult even for those with high intelligence quotient. I may not know who I fully am, but I know who I am not.


public class GameSpecification
extends java.lang.Object
| Modifier and Type | Field and Description |
|---|---|
java.lang.String |
boardBackgroundFileName
path to a file that contains an image for the game window background
|
java.util.ArrayList<CameraObjectType> |
cameraObjectTypes
lists specifications of objects to be detected by the camera when playing on real-world game board
|
java.util.Map<java.lang.String,Element> |
elements
list of elements indexed through their name
|
java.util.Map<java.lang.String,ElementType> |
elementTypes
list of element types indexed through their name
|
java.util.Map<java.lang.String,Expression> |
expressions
list of all expressions.
|
java.lang.String |
gameName
name of the game
|
int |
initialPlayerScore
initial scores for all players
|
java.util.Map<java.lang.String,Location> |
locations
list of locations indexed through their name
|
java.util.Map<java.lang.String,LocationType> |
locationTypes
list of location types indexed through their name
|
java.lang.String[] |
playerNames
names of players - just for visualization
|
java.util.Map<java.lang.String,GameRule> |
rules
lists all the game rules, indexed by their name
|
java.util.ArrayList<GameScoring> |
scorings
specifies how the players scores change if particular game states are reached
|
java.util.Map<Expr,Expr> |
terminationConditions
list of conditions expressions that determine the game is over, if
they evaluate to true.
|
| Constructor and Description |
|---|
GameSpecification(Config config,
GameLogger logger)
construct a new empty game specification
|
| Modifier and Type | Method and Description |
|---|---|
Location |
findClosestCameraLocation(int x,
int y)
find a camera location which is closest to a specified pixel
|
boolean |
load(java.lang.String gameName)
load game specification from a file
|
public java.lang.String gameName
public java.lang.String boardBackgroundFileName
public java.util.Map<java.lang.String,LocationType> locationTypes
public java.util.Map<java.lang.String,ElementType> elementTypes
public java.util.Map<java.lang.String,Element> elements
public java.util.Map<java.lang.String,Location> locations
public java.util.Map<java.lang.String,Expression> expressions
public java.util.Map<Expr,Expr> terminationConditions
public java.util.ArrayList<GameScoring> scorings
public java.util.Map<java.lang.String,GameRule> rules
public java.util.ArrayList<CameraObjectType> cameraObjectTypes
public java.lang.String[] playerNames
public int initialPlayerScore
public GameSpecification(Config config, GameLogger logger)
public boolean load(java.lang.String gameName) throws java.lang.Exception
gameName
- the name of game, and the file where the specification is loaded from (in games/ folder)java.lang.Exception
public Location findClosestCameraLocation(int x, int y)
x
- x-coordinate of the pixely
- y-coordinate of the pixel


Dengue case confirmed on Easter Island
by News DeskBy NewsDesk @infectiousdiseasenews
The Public Health Institute of Chile reported a confirmed case of dengue serotype DEN-2 on Easter Island, the first of its kind in the island territory.
The patient, a 55-year-old man, resident in Rapa Nui, acquired the virus while traveling in Tahiti.
The patient was treated at the Hanga Roa Hospital. Once the diagnosis was known, the control activities that included epidemiological interview in the field and application of vector control measures in all the homes located in the risk area were initiated.
In May of this year, Health Alert was declared on Easter Island for confirmed cases of the disease. To date, 34 cases of dengue serotype 1 have been reported on the island.
- Plague: 4th case reported in China, according to Taiwan CDC
- Philippines: Health officials team with McDonald’s in polio vaccination campaign
- Samoa measles outbreak: 17 deaths reported, Gov’t issues compulsory vaccination orders
- Fiji reports 10th measles case, Vaccine shortages reported
- Penn State: Mumps reported on the University Park campus
- Rat Hepatitis E virus case investigated in Hong Kong
amzn_assoc_placement = "adunit0"; amzn_assoc_tracking_id = "outbre-20"; amzn_assoc_ad_mode = "manual"; amzn_assoc_ad_type = "smart"; amzn_assoc_marketplace = "amazon"; amzn_assoc_region = "US"; amzn_assoc_linkid = "f0ff92d1b0776bebaee269ddf42d8764"; amzn_assoc_design = "in_content"; amzn_assoc_title = "Paid links"; amzn_assoc_asins = "9563326415,1619020203";


This system is designed to convert the 2D images to 3D images in realtime.
By applying normal distribution selecting the fusion of prior and cue, this allows converting in constant-time, parallel per-pixel work. They compare
their approach to previous 2D-to-3D conversion systems in terms of
different metrics, as well as a user study.
It consists of two main steps: a pre-process to extract disparity priors and a runtime component. While
the pre-process uses many example images and requires
considerable time, the runtime components execute in real
time.
Thomas Leimkühler (MPI Informatik), Petr Kellnhofer（MPI Informatik, Tobias Ritschel(University College London), Karol Myszkowski (MPI Informatik), Hans-Peter Seidel (MPI Informatik)
Their approach seems to be less sensitive to the variety of scenes and works on priors
created by painting. Depending on the problem at hand,
working with sensor data can be more or less efficient than
their pragmatic approach.
References:
http://resources.mpi-inf.mpg.de/StereoCueFusion/StereoCueFusionPaper.pdf
http://resources.mpi-inf.mpg.de/StereoCueFusion/StereoCueFusionPaper_TVCG.pdf