It is important to consider replication in the context of the overall database environment's transactional guarantees. To briefly review, transactional guarantees in a non-replicated application are based on the writing of log file records to "stable storage", usually a disk drive. If the application or system then fails, the Berkeley DB logging information is reviewed during recovery, and the databases are updated so that all changes made as part of committed transactions appear, and all changes made as part of uncommitted transactions do not appear. In this case, no information will have been lost.
If a database environment does not require the log be flushed to stable storage on transaction commit (using the DB_TXN_NOSYNC flag to increase performance at the cost of sacrificing transactional durability), Berkeley DB recovery will only be able to restore the system to the state of the last commit found on stable storage. In this case, information may have been lost (for example, the changes made by some committed transactions may not appear in the databases after recovery).
Further, if there is database or log file loss or corruption (for example, if a disk drive fails), then catastrophic recovery is necessary, and Berkeley DB recovery will only be able to restore the system to the state of the last archived log file. In this case, information may also have been lost.
Replicating the database environment extends this model, by adding a new component to "stable storage": the client's replicated information. If a database environment is replicated, there is no lost information in the case of database or log file loss, because the replicated system can be configured to contain a complete set of databases and log records up to the point of failure. A database environment that loses a disk drive can have the drive replaced, and it can then rejoin the replication group.
Because of this new component of stable storage, specifying DB_TXN_NOSYNC in a replicated environment no longer sacrifices durability, as long as one or more clients have acknowledged receipt of the messages sent by the master. Since network connections are often faster than local synchronous disk writes, replication becomes a way for applications to significantly improve their performance as well as their reliability.
Applications using Replication Manager are free to use DB_TXN_NOSYNC at the master and/or clients as they see fit. The behavior of the send function that Replication Manager provides on the application's behalf is determined by an "acknowledgement policy", which is configured by the DB_ENV->repmgr_set_ack_policy() method. Clients always send acknowledgements for DB_REP_PERMANENT messages (unless the acknowledgement policy in effect indicates that the master doesn't care about them). For a DB_REP_PERMANENT message, the master blocks the sending thread until either it receives the proper number of acknowledgements, or the DB_REP_ACK_TIMEOUT expires. In the case of timeout, Replication Manager returns an error code from the send function, causing Berkeley DB to flush the transaction log before returning to the application, as previously described. The default acknowledgement policy is DB_REPMGR_ACKS_QUORUM, which ensures that the effect of a permanent record remains durable following an election.
The rest of this section discusses transactional guarantee considerations in Base API applications.
The return status from the application's send function must be set by the application to ensure the transactional guarantees the application wants to provide. Whenever the send function returns failure, the local database environment's log is flushed as necessary to ensure that any information critical to database integrity is not lost. Because this flush is an expensive operation in terms of database performance, applications should avoid returning an error from the send function, if at all possible.
The only interesting message type for replication transactional guarantees is when the application's send function was called with the DB_REP_PERMANENT flag specified. There is no reason for the send function to ever return failure unless the DB_REP_PERMANENT flag was specified -- messages without the DB_REP_PERMANENT flag do not make visible changes to databases, and the send function can return success to Berkeley DB as soon as the message has been sent to the client(s) or even just copied to local application memory in preparation for being sent.
When a client receives a DB_REP_PERMANENT message, the client will flush its log to stable storage before returning (unless the client environment has been configured with the DB_TXN_NOSYNC option). If the client is unable to flush a complete transactional record to disk for any reason (for example, there is a missing log record before the flagged message), the call to the DB_ENV->rep_process_message() method on the client will return DB_REP_NOTPERM and return the LSN of this record to the application in the ret_lsnp parameter. The application's client or master message handling loops should take proper action to ensure the correct transactional guarantees in this case. When missing records arrive and allow subsequent processing of previously stored permanent records, the call to the DB_ENV->rep_process_message() method on the client will return DB_REP_ISPERM and return the largest LSN of the permanent records that were flushed to disk. Client applications can use these LSNs to know definitively if any particular LSN is permanently stored or not.
An application relying on a client's ability to become a master and guarantee that no data has been lost will need to write the send function to return an error whenever it cannot guarantee the site that will win the next election has the record. Applications not requiring this level of transactional guarantees need not have the send function return failure (unless the master's database environment has been configured with DB_TXN_NOSYNC), as any information critical to database integrity has already been flushed to the local log before send was called.
To sum up, the only reason for the send function to return failure is when the master database environment has been configured to not synchronously flush the log on transaction commit (that is, DB_TXN_NOSYNC was configured on the master), the DB_REP_PERMANENT flag is specified for the message, and the send function was unable to determine that some number of clients have received the current message (and all messages preceding the current message). How many clients need to receive the message before the send function can return success is an application choice (and may not depend as much on a specific number of clients reporting success as one or more geographically distributed clients).
If, however, the application does require on-disk durability on the master, the master should be configured to synchronously flush the log on commit. If clients are not configured to synchronously flush the log, that is, if a client is running with DB_TXN_NOSYNC configured, then it is up to the application to reconfigure that client appropriately when it becomes a master. That is, the application must explicitly call DB_ENV->set_flags() to disable asynchronous log flushing as part of re-configuring the client as the new master.
Of course, it is important to ensure that the replicated master and client environments are truly independent of each other. For example, it does not help matters that a client has acknowledged receipt of a message if both master and clients are on the same power supply, as the failure of the power supply will still potentially lose information.
Configuring a Base API application to achieve the proper mix of performance and transactional guarantees can be complex. In brief, there are a few controls an application can set to configure the guarantees it makes: specification of DB_TXN_NOSYNC for the master environment, specification of DB_TXN_NOSYNC for the client environment, the priorities of different sites participating in an election, and the behavior of the application's send function.
First, it is rarely useful to write and synchronously flush the log when a transaction commits on a replication client. It may be useful where systems share resources and multiple systems commonly fail at the same time. By default, all Berkeley DB database environments, whether master or client, synchronously flush the log on transaction commit or prepare. Generally, replication masters and clients turn log flush off for transaction commit using the DB_TXN_NOSYNC flag.
Consider two systems connected by a network interface. One acts as the master, the other as a read-only client. The client takes over as master if the master crashes and the master rejoins the replication group after such a failure. Both master and client are configured to not synchronously flush the log on transaction commit (that is, DB_TXN_NOSYNC was configured on both systems). The application's send function never returns failure to the Berkeley DB library, simply forwarding messages to the client (perhaps over a broadcast mechanism), and always returning success. On the client, any DB_REP_NOTPERM returns from the client's DB_ENV->rep_process_message() method are ignored, as well. This system configuration has excellent performance, but may lose data in some failure modes.
If both the master and the client crash at once, it is possible to lose committed transactions, that is, transactional durability is not being maintained. Reliability can be increased by providing separate power supplies for the systems and placing them in separate physical locations.
If the connection between the two machines fails (or just some number of messages are lost), and subsequently the master crashes, it is possible to lose committed transactions. Again, transactional durability is not being maintained. Reliability can be improved in a couple of ways:
Use a reliable network protocol (for example, TCP/IP instead of UDP).
Increase the number of clients and network paths to make it less likely that a message will be lost. In this case, it is important to also make sure a client that did receive the message wins any subsequent election. If a client that did not receive the message wins a subsequent election, data can still be lost.
Further, systems may want to guarantee message delivery to the client(s) (for example, to prevent a network connection from simply discarding messages). Some systems may want to ensure clients never return out-of-date information, that is, once a transaction commit returns success on the master, no client will return old information to a read-only query. Some of the following changes to a Base API application may be used to address these issues:
Write the application's send function to not return to Berkeley DB until one or more clients have acknowledged receipt of the message. The number of clients chosen will be dependent on the application: you will want to consider likely network partitions (ensure that a client at each physical site receives the message) and geographical diversity (ensure that a client on each coast receives the message).
Write the client's message processing loop to not acknowledge receipt of the message until a call to the DB_ENV->rep_process_message() method has returned success. Messages resulting in a return of DB_REP_NOTPERM from the DB_ENV->rep_process_message() method mean the message could not be flushed to the client's disk. If the client does not acknowledge receipt of such messages to the master until a subsequent call to the DB_ENV->rep_process_message() method returns DB_REP_ISPERM and the LSN returned is at least as large as this message's LSN, then the master's send function will not return success to the Berkeley DB library. This means the thread committing the transaction on the master will not be allowed to proceed based on the transaction having committed until the selected set of clients have received the message and consider it complete.
Alternatively, the client's message processing loop could acknowledge the message to the master, but with an error code indicating that the application's send function should not return to the Berkeley DB library until a subsequent acknowledgement from the same client indicates success.
The application send callback function invoked by Berkeley DB contains an LSN of the record being sent (if appropriate for that record). When DB_ENV->rep_process_message() method returns indicators that a permanent record has been written then it also returns the maximum LSN of the permanent record written.
There is one final pair of failure scenarios to consider. First, it is not possible to abort transactions after the application's send function has been called, as the master may have already written the commit log records to disk, and so abort is no longer an option. Second, a related problem is that even though the master will attempt to flush the local log if the send function returns failure, that flush may fail (for example, when the local disk is full). Again, the transaction cannot be aborted as one or more clients may have committed the transaction even if send returns failure. Rare applications may not be able to tolerate these unlikely failure modes. In that case the application may want to:
Configure the master to do always local synchronous commits (turning off the DB_TXN_NOSYNC configuration). This will decrease performance significantly, of course (one of the reasons to use replication is to avoid local disk writes.) In this configuration, failure to write the local log will cause the transaction to abort in all cases.
Do not return from the application's send function under any conditions, until the selected set of clients has acknowledged the message. Until the send function returns to the Berkeley DB library, the thread committing the transaction on the master will wait, and so no application will be able to act on the knowledge that the transaction has committed.


Treebank Statistics: UD_French-Sequoia: POS Tags: SCONJ
There are 7 SCONJ
lemmas (0%), 11 SCONJ
types (0%) and 769 SCONJ
tokens (1%).
Out of 16 observed tags, the rank of SCONJ
is: 13 in number of lemmas, 14 in number of types and 13 in number of tokens.
The 10 most frequent SCONJ
lemmas: que, si, comme, parce, lorsque, quand, puisque
The 10 most frequent SCONJ
types: que, qu’, si, comme, parce, quand, lorsqu’, s’, lorsque, puisqu’
The 10 most frequent ambiguous lemmas: que (SCONJ 545, PRON 110, ADV 28), si (SCONJ 135, ADV 2), comme (ADP 75, SCONJ 33), quand (SCONJ 11, ADV 2)
The 10 most frequent ambiguous types: que (SCONJ 404, PRON 62, ADV 18), qu’ (SCONJ 136, PRON 35, ADV 10), si (SCONJ 76, ADV 2), comme (ADP 68, SCONJ 28), quand (SCONJ 8, ADV 2), s’ (PRON 132, SCONJ 7)
- que
- qu’
- si
- comme
- quand
- s’
Morphology
The form / lemma ratio of SCONJ
is 1.571429 (the average of all parts of speech is 1.406661).
The 1st highest number of forms (2) was observed with the lemma “lorsque”: lorsqu’, lorsque.
The 2nd highest number of forms (2) was observed with the lemma “puisque”: puisqu’, puisque.
The 3rd highest number of forms (2) was observed with the lemma “que”: qu’, que.
SCONJ
does not occur with any features.
Relations
SCONJ
nodes are attached to their parents using 5 different relations: mark (630; 82% instances), fixed (91; 12% instances), case (46; 6% instances), advmod (1; 0% instances), dep (1; 0% instances)
Parents of SCONJ
nodes belong to 9 different parts of speech: VERB (517; 67% instances), NOUN (82; 11% instances), ADJ (60; 8% instances), ADV (50; 7% instances), SCONJ (21; 3% instances), ADP (20; 3% instances), PROPN (11; 1% instances), PRON (7; 1% instances), AUX (1; 0% instances)
746 (97%) SCONJ
nodes are leaves.
23 (3%) SCONJ
nodes have one child.
The highest child degree of a SCONJ
node is 1.
Children of SCONJ
nodes are attached using 2 different relations: fixed (22; 96% instances), punct (1; 4% instances)
Children of SCONJ
nodes belong to 3 different parts of speech: SCONJ (21; 91% instances), ADJ (1; 4% instances), PUNCT (1; 4% instances)


No of firms in
0
Toggle Heatmap
Toggle Data Layer
Change gradient
Change radius
Change opacity
States are colored Red to Green on the basis of no of firms registered within the state.


DBC Week 5 Technical Blog Post
Ruby Classes
March 7, 2015
What is a Ruby Class?
A class is the blueprints from which individual objects are created. When a new class is created, an object of type class is initialized and assigned to a global constant. The best way to show how this works would be modeling a real world object using a ruby class. Below is the Die class that we had to create for this week's challenges:
Modeling Dice Rolls
The first method in every class will be an initialize method, which is unique in Ruby. When you create a new Die object, Ruby creates an uninitialized object and then calls that object's initialize method, passing in any parameters that were passed to new. For our Die class, the only parameter is the number of sides that the dice has.
You might also have noticed the usage of the @ sign inside each method. Using @ will create an instance variable, which will record the data of a specific instance of your class. You can have form several instances of class Die, such as a 6 sided, 10 sided or even 20 sided die.
In this class, we created two class methods sides and roll. The first method will tell you how many sides the dice has and the second method will "roll the dice" and give you a random output. You can call a method by creating a new object as shown below:
a = Die.new(6)
a.roll
Doing so, will create a new 6 sided die and tell it to roll the dice and output a random number from 1-6!


| Product | Price | Quantity | Total | ||
|---|---|---|---|---|---|
| woo Single #2 | $45.00 | 1 | $45.00 | ||
| woo Single #2 | $45.00 | 2 | $90.00 | ||
|
|
May You like
$45.00
$45.00
Cart Totals
| Cart Subtotal | $135.00 |
|---|---|
| Shipping and Handling | Free Shipping |
| Order Total | $135.00 |


Transit Appliance Display Configuration
Welcome to the Transit Appliance configuration site
Create/Edit your configurations


[all packages]
[package ]
[class hierarchy]
[index]
public abstract class Graph1
(source file: Graph1.java)
java.lang.Object
|
+----Drawable
|
+----Graph1
The pure class interface.
public abstract class Graph1
extends Drawable
-
A graph with a control line.
- Author:
- Alan Jeffrey
- Version: v1.0 1998/06/11
- Graph1(Constraints, Interface, Interface, int, int)
-
Create a new graph.
- C
-
The constraints of the graph.
- bot
-
The variable for the bottom of the graph.
- controlIn
-
The variable for the position of the incoming control line.
- controlOut
-
The variable for the position of the outgoing control line.
- left
-
The variable for the lhs of the graph.
- right
-
The variable for the rhs of the graph.
- source
-
The interface at the lhs of the graph.
- target
-
The interface at the rhs of the graph.
- top
-
The variable for the top of the graph.
- pad()
-
Pad the graph a bit.
Graph1
public Graph1(Constraints C,
Interface source,
Interface target,
int controlIn,
int controlOut);
-
Create a new graph.
- Parameters:
- C - the constraint set.
- source - the incoming interface.
- target - the outgoing interface.
- controlIn - the incoming control line.
- controlOut - the outgoing control line.
left
public int left;
-
The variable for the lhs of the graph.
right
public int right;
-
The variable for the rhs of the graph.
bot
public int bot;
-
The variable for the bottom of the graph.
top
public int top;
-
The variable for the top of the graph.
C
public Constraints C;
-
The constraints of the graph.
source
public Interface source;
-
The interface at the lhs of the graph.
target
public Interface target;
-
The interface at the rhs of the graph.
controlIn
public int controlIn;
-
The variable for the position of the incoming control line.
controlOut
public int controlOut;
-
The variable for the position of the outgoing control line.
pad
public Graph1 pad();
-
Pad the graph a bit.
- Returns:
- this graph, with extra space at the left and right.
[all packages]
[package ]
[class hierarchy]
[index]
Graph1.html


public static final String |
ALERT_TEXT |
"An alert with text " |
public static final String |
B_PRESENT |
" is present on the page" |
public static final String |
CELL_OUT_OF_BOUNDS |
"Cell out of bounds" |
public static final String |
CLASS |
"class" |
public static final String |
CLASS_VALUE |
" has a class value of " |
public static final String |
CONFIRMATION_TEXT |
"A confirmation with text " |
public static final String |
CONTAINING |
" containing: " |
public static final String |
CONTAINS |
"\' contains \'" |
public static final String |
CONTAINS_TEXT |
" contains the text of " |
public static final String |
CONTAINS_VALUE |
" contains the value of " |
public static final String |
COOKIE |
"A cookie with the name " |
public static final String |
DIV_I |
"
" |
public static final String |
DOES_NOT_CONTAIN |
"\' doesn\'t contain \'" |
public static final String |
DOES_NOT_MATCH_PATTERN |
"\' doesn\'t match pattern \'" |
public static final String |
ELEMENT_NOT_PRESENT |
"Element not present" |
public static final String |
ELEMENT_NOT_SELECT |
"Element not select" |
public static final String |
ELEMENT_NOT_TABLE |
"Element not table" |
public static final String |
END_IDIV |
"
" |
public static final String |
ENDB |
"" |
public static final String |
ENDI |
"\'" |
public static final String |
EXCLUDES_TEXT |
" does not contain the text of " |
public static final String |
EXCLUDES_VALUE |
" does not contain the value of " |
public static final String |
EXCLUDING |
" excluding: " |
public static final String |
EXPECTED_ELEMENT_NOT_PRESENT |
"Expected Element Not Present" |
public static final String |
EXPECTED_NOT_TO_FIND |
"Expected not to find " |
public static final String |
EXPECTED_TO_FIND |
"Expected to find " |
public static final String |
EXPECTED_TO_FIND_A_RESPONSE_CONTAINING |
"Expected to find a response containing: " |
public static final String |
EXPECTED_TO_FIND_A_RESPONSE_EXCLUDING |
"Expected to find a response excluding: " |
public static final String |
EXPECTED_TO_FIND_A_RESPONSE_OF |
"Expected to find a response of: " |
public static final String |
FOUND |
"Found a response of: " |
public static final String |
HAS_OPTION |
" has the option of " |
public static final String |
HAS_TEXT |
" has the text of " |
public static final String |
HAS_VALUE |
" has the value of " |
public static final String |
IS_CHECKED |
" is checked on the page" |
public static final String |
IS_DISPLAYED |
" is displayed on the page" |
public static final String |
IS_EDITABLE |
" is editable on the page" |
public static final String |
IS_ENABLED |
" is enabled on the page" |
public static final String |
IS_NOT_CHECKED |
" is not checked on the page" |
public static final String |
IS_NOT_DISPLAYED |
" is not displayed on the page" |
public static final String |
IS_NOT_EDITABLE |
" is not editable on the page" |
public static final String |
IS_NOT_ENABLED |
" is not enabled on the page" |
public static final String |
IS_NOT_INPUT |
" is not an input on the page" |
public static final String |
IS_NOT_PRESENT |
" is not present on the page" |
public static final String |
IS_NOT_SELECT |
" is not a select on the page" |
public static final String |
IS_NOT_TABLE |
" is not a table on the page" |
public static final String |
IS_PRESENT |
" is present on the page" |
public static final String |
MATCH_PATTERN |
" text to match a pattern of " |
public static final String |
NO_ALERT |
"An alert is not present on the page" |
public static final String |
NO_CONFIRMATION |
"A confirmation is not present on the page" |
public static final String |
NO_ELEMENT_FOUND |
"No element found" |
public static final String |
NO_PROMPT |
"A prompt is not present on the page" |
public static final String |
NOT_STORED |
" is not stored for the page" |
public static final String |
OF |
"of " |
public static final String |
ON_PAGE |
" on the page" |
public static final String |
ONLY_VALUE |
", only the values " |
public static final String |
OPTIONS |
" has options of " |
public static final String |
PROMPT_TEXT |
"A prompt with text " |
public static final String |
STARTB |
"" |
public static final String |
STARTI |
"\'" |
public static final String |
STORED |
" is stored for the page" |
public static final String |
TEXT_B |
"The text " |
public static final String |
VALUE_OF |
" and a value of " |
public static final String |
VALUES |
" has values of " |
public static final String |
WITH |
" with the value of " |


ESTBeacon Class Reference
| Inherits from | NSObject |
| Conforms to | NSCoding NSCopying |
| Declared in | ESTBeacon.h ESTBeacon.m |
Overview
The ESTBeacon
class defines the interface for interacting with a single Estimote beacon. It enables you to retrieve properties of the beacon as well as alter its configuration settings. You do not create instances of this class directly. The ESTBeaconManager
object reports encountered beacons to its associated delegate object.
The identity of a beacon is defined by its proximityUUID
, major
, and minor
properties. The combination of the three is required to be globally unique among all the Estimote beacons - a constraint that is being validated by the Estimote Cloud at the time of modifying any of these properties.
The ESTBeacon instance is being populated with a different set of properties depending on which ESTBeaconManager
’s method was used to scan for and discover the beacon. There are two such methods currently:
startRangingBeaconsInRegion:
- which is a CoreLocation based scan.startEstimoteBeaconsDiscoveryForRegion:
- which is a CoreBluetooth based scan.
Additional properties become available once connected to the beacon. See connect for more details about connecting to the beacon. You will also need to assign a delegate to be notified about connection and disconnection events. The delegate needs to conform to the ESTBeaconDelegate
protocol.
Tasks
Accessing the Delegate
-
delegate
property
Properties Always Available
-
major
property -
minor
property -
color
property -
rssi
property -
connectionStatus
property
Properties Available After CoreLocation Based Scan
-
proximityUUID
property -
distance
property -
proximity
property
Properties Available After CoreBluetooth Based Scan
-
macAddress
property -
measuredPower
property -
firmwareState
property -
peripheral
property
Properties Available After Connecting
-
name
property -
motionProximityUUID
property -
power
property -
advInterval
property -
batteryLevel
property -
remainingLifetime
property -
batteryType
property -
hardwareVersion
property -
firmwareVersion
property -
firmwareUpdateInfo
property -
isMoving
property -
isSecured
property -
isAccelerometerAvailable
property -
isAccelerometerEditAvailable
property -
accelerometerEnabled
property -
motionUUIDEnabled
property -
basicPowerMode
property -
smartPowerMode
property -
estimoteSecureUUID
property
Connecting and Disconnecting
Interacting with Sensors (must be connected)
-
– readTemperatureWithCompletion:
-
– calibrateTemperatureWithReferenceTemperature:completion:
-
– readAccelerometerCountWithCompletion:
-
– resetAccelerometerCountWithCompletion:
Modifying Configuration Settings (must be connected)
-
– writeName:completion:
-
– writeProximityUUID:completion:
-
– writeMajor:completion:
-
– writeMinor:completion:
-
– writeAdvInterval:completion:
-
– writePower:completion:
-
– resetToFactorySettingsWithCompletion:
-
– enableAccelerometer:completion:
-
– enableMotionUUID:completion:
-
– enableBasicPowerMode:completion:
-
– enableSmartPowerMode:completion:
-
– enableEstimoteSecureUUID:completion:
Updating Firmware (must be connected)
Comparing Beacons for Equality
Properties
accelerometerEnabled
A flag indicating if accelerometer is enabled.
@property (readonly, nonatomic) BOOL accelerometerEnabled
Availability
Estimote OS A2.1
See Also
Declared In
ESTBeacon.h
advInterval
The advertising interval of the beacon in ms.
@property (readonly, nonatomic) NSNumber *advInterval
See Also
Declared In
ESTBeacon.h
basicPowerMode
A flag indicating availability and status of the Basic Power Mode.
@property (readonly, nonatomic) ESTBeaconPowerSavingMode basicPowerMode
Availability
Estimote OS A2.1
See Also
Declared In
ESTBeacon.h
batteryLevel
The battery charge level for the beacon.
@property (readonly, nonatomic) NSNumber *batteryLevel
Discussion
Battery level ranges from 0 (fully discharged) to 100 (fully charged).
Declared In
ESTBeacon.h
batteryType
The battery model.
@property (readonly, nonatomic) ESTBeaconBatteryType batteryType
See Also
Declared In
ESTBeacon.h
color
The color of the beacon.
@property (readonly, nonatomic) ESTBeaconColor color
Discussion
This value is stored and retrieved from the Estimote Cloud, which means it might be unavailable under certain circumestances - e.g. no Internet connectivity.
See Also
Declared In
ESTBeacon.h
connectionStatus
The connection status between the user device and the beacon.
@property (readonly, nonatomic) ESTConnectionStatus connectionStatus
Declared In
ESTBeacon.h
delegate
The delegate object to receive beacon related events.
@property (nonatomic, weak) id<ESTBeaconDelegate> delegate
See Also
Declared In
ESTBeacon.h
distance
An estimated distance from the beacon in meters.
@property (readonly, nonatomic) NSNumber *distance
Discussion
This value is only as accurate as the rssi
readings, i.e. it is subject to the same external factors such as multipath propagation, diffraction, absorption and interference. In general, the greater the distance, the lesser the accuracy.
Declared In
ESTBeacon.h
estimoteSecureUUID
A flag indicating status of Estimote Secure UUID.
@property (readonly, nonatomic) ESTBeaconEstimoteSecureUUID estimoteSecureUUID
Availability
Estimote OS 2.2
See Also
Declared In
ESTBeacon.h
firmwareState
Flag indicating the state the beacon’s firmware is in.
@property (readonly, nonatomic) ESTBeaconFirmwareState firmwareState
Discussion
This can be either:
ESTBeaconFirmwareStateApp
- A fully functional state. This is the usual state the firmware is in.ESTBeaconFirmwareStateBoot
- A limited function state. This is a temporary state the firmware can find itself in during a firmware update. If the update didn’t finish successfully, the firmware might remain in that state. Retry updating the firmware in order to regain full functionality. When in this state, the beacon can only be discovered using CoreBluetooth based scanning and cannot be discovered using CoreLocation based scanning.
See Also
Declared In
ESTBeacon.h
firmwareUpdateInfo
A flag indicating if a firmware update is available.
@property (readonly, nonatomic) ESTFirmwareUpdate firmwareUpdateInfo
Discussion
Bug: This property has a ESTBeaconFirmwareUpdateNone
value at all times. Use the checkFirmwareUpdateWithCompletion:
method instead.
Declared In
ESTBeacon.h
firmwareVersion
The firmware version of the beacon.
@property (readonly, nonatomic) NSString *firmwareVersion
Declared In
ESTBeacon.h
hardwareVersion
The hardware version of the beacon.
@property (readonly, nonatomic) NSString *hardwareVersion
Declared In
ESTBeacon.h
isAccelerometerAvailable
A flag indicating if the accelerometer is available.
@property (readonly, nonatomic) BOOL isAccelerometerAvailable
Availability
Estimote OS A2.0
Declared In
ESTBeacon.h
isAccelerometerEditAvailable
A flag indicating if accelerometer can be enabled and disabled.
@property (readonly, nonatomic) BOOL isAccelerometerEditAvailable
Availability
Estimote OS A2.1
See Also
Declared In
ESTBeacon.h
isMoving
A flag indicating if the beacon is in motion or not.
@property (readonly, nonatomic) BOOL isMoving
Discussion
This value changes:
from NO to YES immediately after a still beacon starts moving,
from YES to NO after a beacon stops moving and remains still for 2 seconds.
Declared In
ESTBeacon.h
isSecured
A flag indicating if the beacon has UUID rotation turned on.
@property (readonly, nonatomic) BOOL isSecured
Availability
Estimote OS A2.2
Declared In
ESTBeacon.h
macAddress
The MAC address of the beacon.
@property (readonly, nonatomic) NSString *macAddress
Declared In
ESTBeacon.h
major
The most significant value in the beacon.
@property (readonly, nonatomic) NSNumber *major
See Also
Declared In
ESTBeacon.h
measuredPower
Factory calibrated constant indicating the expected RSSI value at the distance of 1 meter from the beacon.
@property (readonly, nonatomic) NSNumber *measuredPower
Discussion
The value of this constant depends on the broadcasting power and is used to calculate the estimated distance from the beacon.
Declared In
ESTBeacon.h
minor
The least significant value in the beacon.
@property (readonly, nonatomic) NSNumber *minor
See Also
Declared In
ESTBeacon.h
motionProximityUUID
The proximity ID of the beacon when it’s in motion.
@property (readonly, nonatomic) NSUUID *motionProximityUUID
Availability
Estimote OS 2.0
Discussion
This default to the same value as the proximityUUID
. Setting it to a different value enables you to detect whether a beacon is in motion or not without a need to connect to the beacon. This can be achieved in two ways:
When ranging beacons - if the beacon is in motion, the
proximityUUID
property will be equal to themotionProximityUUID
. Note that themotionProximityUUID
property is not available unless connected to the beacon, so you need to know its value in advance.When monitoring regions - you can have two separate regions, one with the regular
proximityUUID
and one with themotionProximityUUID
. Enter and exit notifications will then correspond to the beacon starting and stopping to move.
Warning: This feature is disabled by default. The option to enable it will be made available in an upcoming update to the SDK.
Declared In
ESTBeacon.h
motionUUIDEnabled
A flag indicating if motion UUID is enabled.
@property (readonly, nonatomic) BOOL motionUUIDEnabled
Availability
Estimote OS A2.1
See Also
Declared In
ESTBeacon.h
name
The name of the beacon.
@property (readonly, nonatomic) NSString *name
Discussion
This value is stored and retrieved from the Estimote Cloud.
Declared In
ESTBeacon.h
peripheral
The underlying Bluetooth peripheral device.
@property (readonly, nonatomic) CBPeripheral *peripheral
Declared In
ESTBeacon.h
power
The power of the beacon’s radio signal in dBm.
@property (readonly, nonatomic) NSNumber *power
Discussion
This is a char
value, so the proper way to retrieve it is [beacon.power charValue]
.
See Also
Declared In
ESTBeacon.h
proximity
The relative proximity to the beacon.
@property (readonly, nonatomic) CLProximity proximity
Discussion
The value in this property gives a general sense of the relative proximity to the beacon. Use it to quickly identify beacons that are nearer to the user rather than farther away.
Declared In
ESTBeacon.h
proximityUUID
The proximity ID of the beacon.
@property (readonly, nonatomic) NSUUID *proximityUUID
See Also
Declared In
ESTBeacon.h
remainingLifetime
Remaining lifetime in days, based on current battery level, advertising interval and broadcasting power values
@property (readonly, nonatomic) NSNumber *remainingLifetime
Declared In
ESTBeacon.h
rssi
The received signal strength of the beacon, measured in decibels.
@property (readonly, nonatomic) NSInteger rssi
Discussion
This value is the average RSSI value of the samples received since the range of the beacon was last reported to your app.
Declared In
ESTBeacon.h
Instance Methods
calibrateTemperatureWithReferenceTemperature:completion:
Calibrates the beacon’s thermometer sensor.
- (void)calibrateTemperatureWithReferenceTemperature:(NSNumber *)temperature completion:(ESTNumberCompletionBlock)completion
Parameters
- temperature
The reference temperature in Celsius degrees.
- completion
A block that is called when the calibration has been completed.
The completion block receives the following parameters:
NSNumber *value
- The current temperature in Celsius degrees, after the calibration.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Discussion
Beacons are basically calibrated out of the box, but additional manual calibration is recommended in order to minimize measurement error. When the sensor is not calibrated, measurement error is ±4 ℃. After calibration it’s ±2 ℃.
To perform calibration you need to keep the beacon at room temperature for a couple of minutes. Use a separate thermometer to read the actual value (in Celsius degrees) and pass it to this method.
Declared In
ESTBeacon.h
checkFirmwareUpdateWithCompletion:
Checks if an updated firmware is available.
- (void)checkFirmwareUpdateWithCompletion:(ESTFirmwareInfoCompletionBlock)completion
Parameters
- completion
A block that is called when the check has been completed.
The completion block receives the following parameters:
ESTBeaconFirmwareInfoVO value
- Indicates whether an update is available. If so, it also holds additional information about the update.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Discussion
The result of the check is available as a ESTBeaconFirmwareInfoVO
structure in the completion block and has the following properties:
BOOL isUpdateAvailable
- YES if an update is available, NO if there’s no update available. In the latter case, all the other properties of this structure will benil
.NSString *hardwareVersion
- The version of hardware this firmware update is dedicated for.NSString *firmwareVersion
- The version of the firmware available for update.NSString *changelog
- Changes introduced in the new version.
Declared In
ESTBeacon.h
connect
Connects to the beacon using default connection timeout (15 seconds) and number of attempts (4 times).
- (void)connect
Discussion
Being connected to the beacon allows you to (re)configure the beacon. Because of that, connecting to the beacon is only possible if you’re its verified owner. This implies that before you’re able to connect to the beacon, you need to:
have the beacon assigned to your Estimote Cloud account,
set up your Estimote Cloud credentials using the
[ESTConfig setupAppID:andAppToken:]
class method.
Upon successful connection, delegate’s [ESTBeaconDelegate beaconConnectionDidSucceeded:]
method is called. If connection fails, delegate’s [ESTBeaconDelegate beaconConnectionDidFail:withError:]
method will be called instead.
Warning: Once connected, the beacon stops broadcasting and thus will no longer be picked up by ranging, monitoring and discovery until disconnected.
Declared In
ESTBeacon.h
connectWithAttempts:connectionTimeout:
Connects to the beacon.
- (void)connectWithAttempts:(NSInteger)attempts connectionTimeout:(NSInteger)timeout
Parameters
- attempts
Number of connection attempts before giving up.
- timeout
Connection timeout in seconds.
Discussion
This method allows you to overwrite the connection timeout and the number of attempts. Otherwise, it behaves exactly like connect
.
Declared In
ESTBeacon.h
disconnect
Disconnects from the beacon.
- (void)disconnect
Discussion
Always remember to disconnect from the beacon when the connection is no longer required, as the beacon in the connected state stops broadcasting and thus is not being picked up by ranging, monitoring and discovery.
Declared In
ESTBeacon.h
enableAccelerometer:completion:
Enables or disables the accelerometer.
- (void)enableAccelerometer:(BOOL)enable completion:(ESTBoolCompletionBlock)completion
Parameters
- enable
YES to enable, NO to disable the accelerometer.
- completion
A block that is called when the accelerometer has been enabled or disabled.
The completion block receives the following parameters:
BOOL value
- YES if the accelerometer has been enabled, NO if the accelerometer has been disabled.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Availability
Estimote OS A2.1
Declared In
ESTBeacon.h
enableBasicPowerMode:completion:
Enables or disables the basicPowerMode
.
- (void)enableBasicPowerMode:(BOOL)enable completion:(ESTBoolCompletionBlock)completion
Parameters
- enable
YES to enable, NO to disable the Basic Power Mode.
- completion
A block that is called when the Basic Power Mode has been enabled or disabled.
The completion block receives the following parameters:
BOOL value
- YES if the Basic Power Mode has been enabled, NO if the Basic Power Mode has been disabled.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
enableEstimoteSecureUUID:completion:
Enables Estimote Secure UUID.
- (void)enableEstimoteSecureUUID:(BOOL)enable completion:(ESTBoolCompletionBlock)completion
Parameters
- enable
Yes to enable, No to disable Estimote Secure UUID.
- completion
Block with operation result.
Declared In
ESTBeacon.h
enableMotionUUID:completion:
Enables or disables the motion UUID.
- (void)enableMotionUUID:(BOOL)enable completion:(ESTBoolCompletionBlock)completion
Parameters
- enable
YES to enable, NO to disable the motion UUID.
- completion
A block that is called when the motion UUID has been enabled or disabled.
The completion block receives the following parameters:
BOOL value
- YES if the motion UUID has been enabled, NO if the motion UUID has been disabled.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Availability
Estimote OS A2.1
Declared In
ESTBeacon.h
enableSmartPowerMode:completion:
Enables or disables the smartPowerMode
.
- (void)enableSmartPowerMode:(BOOL)enable completion:(ESTBoolCompletionBlock)completion
Parameters
- enable
YES to enable, NO to disable the Smart Power Mode.
- completion
A block that is called when the Smart Power Mode has been enabled or disabled.
The completion block receives the following parameters:
BOOL value
- YES if the Smart Power Mode has been enabled, NO if the Smart Power Mode has been disabled.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
isEqualToBeacon:
Returns a Boolean value that indicates whether a given beacon is equal to the receiver.
- (BOOL)isEqualToBeacon:(ESTBeacon *)beacon
Discussion
The comparison is based on macAddress
if available. If not, the comparison is based on proximityUUID
, major
and minor
.
Warning: You can only compare two ESTBeacon
instances if both were discovered using a CoreLocation or a CoreBluetooth based scan. Trying to compare two ESTBeacon
instances when one was discovered by a CoreLocation scan and the other one by a CoreBluetooth based scan will yield an undefined result.
This is because an ESTBeacon discovered using a CoreLocation based scan has its proximityUUID
, major
and minor
populated, but not the macAddress
. A beacon discovered by a CoreBluetooth based scan will in turn have its macAddress
populated, but not the proximityUUID
.
Declared In
ESTBeacon.h
readAccelerometerCountWithCompletion:
Retrieves the number of times the beacon has been in motion since the last resetAccelerometerCountWithCompletion:
.
- (void)readAccelerometerCountWithCompletion:(ESTNumberCompletionBlock)completion
Parameters
- completion
A block that is called when the counter has been retrieved.
The completion block receives the following parameters:
NSNumber *value
- The value of the counter.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
readTemperatureWithCompletion:
Retrieves the temperature of surrounding environment reported by the beacon.
- (void)readTemperatureWithCompletion:(ESTNumberCompletionBlock)completion
Parameters
- completion
A block that is called when the temperature has been retrieved from the beacon.
The completion block receives the following parameters:
NSNumber *value
- The temperature in Celsius degrees.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
resetAccelerometerCountWithCompletion:
Resets the counter - number of times the beacon has been in motion since the last reset.
- (void)resetAccelerometerCountWithCompletion:(ESTUnsignedShortCompletionBlock)completion
Parameters
- completion
A block that is called when the counter has been reset.
The completion block receives the following parameters:
NSNumber *value
- The new value of the counter.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
resetToFactorySettingsWithCompletion:
Resets the beacon’s major
, minor
, proximityUUID
, broadcasting power
and advInterval
to factory settings.
- (void)resetToFactorySettingsWithCompletion:(ESTCompletionBlock)completion
Parameters
- completion
A block that is called when the settings have been reset.
The completion block receives the following parameters:
NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Discussion
Warning: This method does not reset the motionProximityUUID
. You can reset it yourself to the default value of ESTIMOTE_PROXIMITY_UUID
using the <writeMotionProximityUUID:completion:>
method.
Declared In
ESTBeacon.h
updateFirmwareWithProgress:completion:
Updates the beacon’s firmware.
- (void)updateFirmwareWithProgress:(ESTProgressBlock)progress completion:(ESTCompletionBlock)completion
Parameters
- progress
A block that is called throughout the update process to report on the progress.
The progress block receives the following parameters:
NSInteger value
- A percentage value (0-100) indicating the update progress.NSString *description
- A description of the current stage of the update.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
- completion
A block that is called when the update has been completed.
The completion block receives the following parameters:
NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
valueObject
Returns ESTBeaconVO
object from ESTBeacon
, so it would be easier to compare beacons with already fetched from the cloud.
- (ESTBeaconVO *)valueObject
Declared In
ESTBeacon.h
writeAdvInterval:completion:
Sets the advertising interval, i.e. advInterval
.
- (void)writeAdvInterval:(unsigned short)interval completion:(ESTUnsignedShortCompletionBlock)completion
Parameters
- interval
The new
advInterval
in miliseconds. The value must be in range from 100 to 2000.
- completion
A block that is called when the new
advInterval
has been set.The completion block receives the following parameters:
unsigned short value
- The newadvInterval
.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
writeMajor:completion:
Sets the major
value.
- (void)writeMajor:(unsigned short)major completion:(ESTUnsignedShortCompletionBlock)completion
Parameters
- major
The new
major
value.
- completion
A block that is called when the new
major
value has been set.The completion block receives the following parameters:
unsigned short value
- The newmajor
value.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
writeMinor:completion:
Sets the minor
value.
- (void)writeMinor:(unsigned short)minor completion:(ESTUnsignedShortCompletionBlock)completion
Parameters
- minor
The new
minor
value.
- completion
A block that is called when the new
minor
value has been set.The completion block receives the following parameters:
unsigned short value
- The newminor
value.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
writeName:completion:
Sets the name
of the beacon.
- (void)writeName:(NSString *)name completion:(ESTStringCompletionBlock)completion
Parameters
- name
The new name of the beacon.
- completion
A block that is called when the new name has been set.
The completion block receives the following parameters:
NSString *value
- The new name of the beacon.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
writePower:completion:
Sets the broadcasting power
.
- (void)writePower:(ESTBeaconPower)power completion:(ESTPowerCompletionBlock)completion
Parameters
- power
The new broadcasting
power
. Must be one of the ESTBeaconPower values.
- completion
A block that is called when the new broadcasting power has been set.
The completion block receives the following parameters:
ESTBeaconPower value
- The new broadcastingpower
.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Declared In
ESTBeacon.h
writeProximityUUID:completion:
Sets the proximityUUID
.
- (void)writeProximityUUID:(NSString *)pUUID completion:(ESTStringCompletionBlock)completion
Parameters
- pUUID
The new
proximityUUID
.
- completion
A block that is called when the new
proximityUUID
has been set.The completion block receives the following parameters:
NSString *value
- The newproximityUUID
.NSError *error
- If an error occurred, this error object describes the error. If the operation completed successfully, the value isnil
.
Discussion
Warning: If you change the proximityUUID
, you might want to consider changing the motionProximityUUID
as well. If you don’t, the beacon will broadcast two different proximityUUIDs
depending on whether its in motion or not!@
Declared In
ESTBeacon.h


Best gifts: Top iPhone 11 accessories from $5 to $60
by Charlie OsborneThese are the best iPhone accessories you can pick up for an affordable price.
The holiday season has once again appeared, and on the heels of the Black Friday sales event, it is almost time to start filling up stockings and wrapping gifts.
Also: More mobile phone coverage
Most of us own a mobile device these days, and if the person you are buying a gift, for now, owns an iPhone 11 -- Apple's latest flagship smartphone -- you can purchase a range of accessories including covers, keyboards, and holders that will make great gifts while keeping Christmas affordable.
Below, we have rounded up some of the best gifts for iPhone 11 users over this holiday season.
Top iPhone 11 accessories
Disclosure: ZDNet may earn a commission from some of the products featured on this page.
ERS metal kickstand case for $16
- See it now: Amazon
A useful stocking filler for iPhone 11 users is the ERS kickstand, a combined transparent case with a 2-way kickstand for portrait and landscape positioning.
iPhone keyboards (price varies)
- See it now: Zagg
Over at Zagg, there is a wide variety of sleek and portable keyboards that are compatible with the iPhone 11. The Bluetooth-compatible range includes universal keyboards and stands, as well as wired models.
Black Eye phone lenses for $60+
- See it now: Amazon
The Black Eye universal phone lens kit is an affordable setup for improving mobile photography. You can pick up a wide-angle, fisheye, or portrait lens separately, or the full kit for $249. Each lens is made from glass and aluminum and comes with a case to protect them when used on the move.
Ubio Labs wireless charging stand for $70
- See it now: Costco
While slightly over budget, now that wireless charging has entered the mainstream, a charging stand suitable for both iPhones and Apple Watches could become a valued gift over the holiday season. Ubio Labs' offering is a 7.5W stand with two USB outputs that, while also affordable, is a small and sleek product that can be housed on a desk or coffee table.
Spigen Tough Armor phone case for $18
- See it now: Amazon
Our mobile devices go through a lot daily, with drops, spills, and accidents only a breath away from causing a screen to crack or scratches embedding themselves. If you are looking for a smartphone case as a gift, the Spigen Tough Armor product is a polycarbonate option to cushion buttons or screens, and also includes a handy kickstand.
UAG military phone case for $60
- See it now: Amazon
For a more rugged alternative, the UAG military phone case can be snapped up on Amazon. Compatible with wireless charging and meeting military drop-test standards, this case could be a great gift for an iPhone user this Christmas.
KiiPix instant photo printer for $52
- See it now: Firebox
Another interesting gift this holiday season is the KiiPix. Available at Firebox, the portable printer can be used with your smartphone to print images with a retro filter. To use, you place the smartphone on the top with the photo you want to print on display, press the shutter button, and spin the dial.
GripTight GorillaPod for $40
- See it now: Amazon
Mobile photography enthusiasts, especially those taking advantage of the new-and-improved cameras offered by devices including the iPhone 11, can give their images a boost by owning a tripod. This year, consider gifting the GropTight GorillaPod, a flexible plastic-and-steel tripod equipped with a mount to make sure devices remain secure.
Whitestone Dome glass screen protector for $46
- See it now: Mobile Fun
If cases are not your thing, it is always wise to invest in some form of screen protector -- and the same can be said for the iPhone 11. A gift worth considering is the Whitestone Dome glass screen protector, which uses a combination of adhesive and UV light to 'bond' to a screen. This layer of protection can also be applied to screens that have been damaged.
Olixar dashboard mat for $11
- See it now: Mobile Fun
Another budget-friendly option is Olixar's handy dashboard mat. The sticky mat fits snugly on your dashboard and is separated into different compartments for items, alongside a phone holder -- especially useful for those on the road who frequently use a GPS navigation system.
PopSockets PopGrip for $10
- See it now: Amazon
Available in a variety of colors, the PopSockets PopGrip could be a fun stocking filler. The stickable grip gives users a more comfortable way to handle their phones and can also act as a stand.


Uses of Interface
org.apache.qpid.protonj2.engine.sasl.SaslServerContext
-
Packages that use SaslServerContext Package Description org.apache.qpid.protonj2.engine org.apache.qpid.protonj2.engine.impl org.apache.qpid.protonj2.engine.sasl -
-
Uses of SaslServerContext in org.apache.qpid.protonj2.engine
Methods in org.apache.qpid.protonj2.engine that return SaslServerContext Modifier and Type Method Description SaslServerContext
EngineSaslDriver. server()
Configure thisEngineSaslDriver
to operate in server mode and return the associatedSaslServerContext
instance that should be used to complete the SASL negotiation with the client end. -
Uses of SaslServerContext in org.apache.qpid.protonj2.engine.impl
Methods in org.apache.qpid.protonj2.engine.impl that return SaslServerContext Modifier and Type Method Description SaslServerContext
ProtonEngineNoOpSaslDriver. server()
-
Uses of SaslServerContext in org.apache.qpid.protonj2.engine.sasl
Methods in org.apache.qpid.protonj2.engine.sasl that return SaslServerContext Modifier and Type Method Description SaslServerContext
SaslServerContext. saslFailure(javax.security.sasl.SaslException failure)
Allows the server implementation to fail the SASL negotiation process due to some unrecoverable error.SaslServerContext
SaslServerContext. sendChallenge(ProtonBuffer challenge)
Sends the SASL challenge defined by the SASL mechanism that is in use during this SASL negotiation.SaslServerContext
SaslServerContext. sendMechanisms(Symbol[] mechanisms)
Sends the set of supported mechanisms to the SASL client from which it must choose and return one mechanism which will then be the basis for the SASL authentication negotiation.SaslServerContext
SaslServerContext. sendOutcome(SaslOutcome outcome, ProtonBuffer additional)
Sends a response to a server side challenge that comprises the challenge / response exchange for the chosen SASL mechanism.SaslServerContext
SaslServerContext. setListener(SaslServerListener listener)
Sets theSaslServerListener
that will be used to driver the server side SASL negotiations with a connected "client".Methods in org.apache.qpid.protonj2.engine.sasl with parameters of type SaslServerContext Modifier and Type Method Description void
SaslServerListener. handleSaslHeader(SaslServerContext context, AMQPHeader header)
Called when the SASL header has been received and the server is now ready to send the configured SASL mechanisms.void
SaslServerListener. handleSaslInit(SaslServerContext context, Symbol mechanism, ProtonBuffer initResponse)
Called when a SASL init frame has arrived from the client indicating the chosen SASL mechanism and the initial response data if any.void
SaslServerListener. handleSaslResponse(SaslServerContext context, ProtonBuffer response)
Called when a SASL response frame has arrived from the client.default void
SaslServerListener. initialize(SaslServerContext context)
Called to give the application code a clear point to initialize all the Server side expectations.
-


backend.translator
¶
Classes¶
Translator
: Undocumented.
-
class
backend.translator.
Translator
(target_languages: List[str])¶ Inheritance
-
translate
(words: List[str]) → Set[str]¶ Translates a list of words into the target languages with which the Translator was initialized.
- Parameters
words – List of words to translate in the target languages
- Returns
Translation results without context to which language they belong
-


SweetFreeStuff.com
///////////////////////////////////////////
FREE Box of Lipton 100% Natural Tea Bags
Posted: 28 Nov 2014 01:25 AM PST
http://feedproxy.google.com/&edburner&utm_medium=email
Save 100% when you buy ONE (1) 16 CT box of Lipton® 100% Natural Tea Bags.
Expires 11/30. FREE 16 CT Box of Lipton 100% Natural Tea Bags
The post FREE Box of Lipton 100% Natural Tea Bags appeared first on
SweetFreeStuff.com.
///////////////////////////////////////////
Free Tum-E Yummies Drink at Kroger & Affiliate Stores
Posted: 27 Nov 2014 11:30 PM PST
http://feedproxy.google.com/&edburner&utm_medium=email
Load the coupon to your shoppers card today only (11/28) and use by
12/13. Free Tum-E Yummies Drink at Kroger Affiliate Stores
The post Free Tum-E Yummies Drink at Kroger Affiliate Stores appeared
first on SweetFreeStuff.com.


First of all I would like to say that I am an advocate of GHB and it's relatives (GBL 1'4 BD); I have used GHB for over 3 yrs with great benefit to my health, social life, and overall well being. However there does seems to be an issue of addiction and withdrawl from GHB which is causing some confusion which I hope to help clarify.
First, GHB is not addictive in the classic sense. The body doesn't react to a lack of GHB in the brain. GHB addiction is at first psychological. Everyone likes to feel good. The fact that GHB has such a lack of toxic effects on the body allows for the user to abuse it in a way you couldn't do with almost any other drug without ill effects. This often leads multiple dose use throughout the day. I myself found I could consume nearly 15-20 grams throughout the day, and I have found many with similar habits.
GHB's 'buzz' is caused by the action of neurotransmitters Seratonin and GABA, the levels of these two transmitters is increased due to the fact that GHB blocks the release of dopamine. Although dopamine release is blocked the product of dopamine is not. This means when the GHB wears off a dopamine rebound occurs. This is the energized feeling most expirence as the GHB wears off, also responsible for waking in the night when a larger dose is used. When GHB is used in multiple doses over weeks, monthes, and even years an excessive amount of dopamine is stored in the brain. If the user then attempts to stop GHB use this dopamine floods the brain causing numerous effects which could be catergorized as withdrawl. The most common (and the ones I myself experienced) are Insomnia, shaking (of hands or limbs), Anxiety, Rapid heart-beat, sensations of hot and cold, general sensory over stimulation, and depression.
The duration of these symptoms varys depending on the frequency, as well as duration of use. Tapering off GHB helps quite a bit. First lower your dosage, if you were taking a cap (2-2.5) grams every 2-3 hours cut to half a cap but in the same intervals. Then decrease the time between use. This will help but expect to experience a few sleepless nights if you're a heavy user. Benzos (valium, xanax) are extremely helpful if you have access. Most doctors will not have a problem perscribing them if you are displaying such withdrawl symptoms. I found .25mg of xanax 3 times daily to be sufficent. The best thing to do is never get in the situation of massive use to begin with. I now believe that GHB should not be used more then 5 days in a row without at least 24-48hrs off to allow from the dopamine to clear. Even this may be too excessive. I hope this is helpful to someone out there. Best of luck. Don't be afraid of medical attention, doctors are there to help.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


| Beer image | Name | Description | Price |
|---|---|---|---|
| Corona Extra 330ml | Corona Extra is a pale lager produced by Cervecería Modelo in Mexico for domestic distribution and export to all other countries besides the United States, and by Constellation Brands in Mexico for export to the United States. | 1.90$ | |
| Stella Artois 500ml | Stella Artois is a Belgian pilsner[1] of between 4.8 and 5.2% ABV which was first brewed by Brouwerij Artois (the Artois Brewery) in Leuven, Belgium, in 1926. Since 2008, a 4% ABV version has also been sold in Britain, Ireland, Canada and New Zealand. | 2.30$ | |
| Carlsberg 330ml | Carlsberg is the flagship beer brand in Carlsberg Group's portfolio of more than 500 brands. It is a 5% abv pilsner beer with a global distribution to 140 markets.[35] It is also known as Carlsberg Lager, Carlsberg Beer and Carlsberg Pilsner. | 1.70$ | |
| Heineken 330ml | Heineken Lager Beer (Dutch: Heineken Pilsener), or simply Heineken (Dutch pronunciation: [ˈɦɛinəkən]) is a pale lager beer with 5% alcohol by volume produced by the Dutch brewing company Heineken International. Heineken is well known for its signature green bottle and red star. | 1.80$ |


Emmerdale SPOILERS: Lydia finds out she could have Huntington’s disease
Will she take the test to find out?
by Claire CrickNext week's Emmerdale sees Lydia Hart's world shattered when she discovers her father died from Huntington's disease... and that she could have the same illness.
Lydia had her life turned upside down recently when she was mysteriously given £10,000 from a secret benefactor.
After Mandy Dingle tried to steal the money but was caught red-handed, she tried to make it up to Lydia by breaking into the solicitors' office so they could find out who it was that left such a substantial amount of cash.
It turned out the generous donation was from Lydia's estranged mum, Agatha Finn, who had been trying to track her daughter down.
Read more: Emmerdale fans beg Louisa Clein and Sandra Marvin to return to the soap as they reunite
However when Lydia arrived at the address she had for her mother, she was told by her long-lost sister, Beth, that their mum had died just three weeks earlier.
However in a cruel twist it turns out that Agatha was actually live and well... and that Beth was determined to keep the pair apart.
But next week's Emmerdale sees Mandy with fresh determination to get Beth to explain herself and she goes back to the house to confront her.
As Mandy barges into Beth's house, she is shocked to find Lydia's presumed-dead mum there and Beth's actions are soon revealed.
Agatha begs Mandy to take her to Emmerdale so that she can see her daughter that she's not seen for years, and Mandy starts to wonder if she has done the right thing.
However, once in the village it seems that Agatha has got a lot to tell Lydia after so many years apart and Lydia braces herself for what her mum has to say.
At the Dingles Lydia prepares to face her past, but when her mum tells her that she has never stopped thinking about her, Lydia starts to soften... even if her mum does constantly refer to her as Jenny.

Agatha reveals that Lydia's father died of Huntington's Disease and that there is a very high chance that Lydia could be living with the same thing but doesn't even know it.
Read More: Emmerdale fans fear Graham Foster will be murdered as Kim Tate threatens him
Lydia is shellshocked by the revelation and shares the upsetting news with the Dingles, leaving everyone reeling.
But the big question is, will Lydia get the tests done to find out if she has Huntington's? Or would she rather remain blissfully ignorant to the possibly devastating diagnosis?
Emmerdale airs weeknights at 7pm on ITV, with an extra episode at 8pm on Thursdays.
Do you think Lydia should have the test? Leave us a comment on our Facebook page @EntertainmentDailyFix and let us know what you think!


Documentation
Reference
Reference Manual
The official and comprehensive man pages that are included in the Git package itself.
Quick reference guides: GitHub Cheat Sheet | Visual Git Cheat Sheet
Book
Pro Git
The entire Pro Git book written by Scott Chacon and Ben Straub is available to read online for free. Dead tree versions are available on Amazon.com.
Videos
-
What is Version Control?
Length: 05:59
-
Get Going with Git
Length: 04:26
-
What is Git?
Length: 08:15
-
Quick Wins with Git
Length: 05:06
External Links
The External Links section is a curated, ever-evolving collection of tutorials, books, videos, and other Git resources.


Thought For The Day:
Submit
Announcement:
Submit
Remove Announcement:
Delete
Add Event:
SPIRITUAL WING
SERVICE WING
EDUCATIONAL WING
Submit
Delete Event:
Submit
Add Additional Details
Add Divine Footprints
Add Samithi
Blog Approve
Add Q&A
Thought For The Day:
Announcement:
Upcoming Events:
Past Events:
Sign out


Behave is a system, the purpose of which is to streamline the iterative process of designing, integrating and debugging behavioural AI via behaviour trees.
Most behaviour tree implementation, though generally working under the same principles, differ slightly in their definition of the practical method of behaviour trees. Behave uses a definition very close to the one described on AIgameDev.com. So if you are completely new to behaviour trees then that site is a great source of learning.
The structure of a tree is defined by a number of interconnected control nodes, ending in leaf nodes – actions. Actions are the interfaces to your agent code, talking to both sensors (enquiring about agent or world state) and motors (affecting a change in agent or world state).
A tick of a tree flows top to bottom, evaluating branching based on tree state and then bottom to top, propagating result values and updating the tree state.
Each control node has its own rule-set setting it apart – defining which child node it ticks and how it responds to the result of it – Success/Failure or Running. In general, though, a result of Running (indicating more processing needed) will always make sure that the child in question gets evaluated again next tick.
All nodes hold a tiny bit of state to indicate the current execution flow – state such as the index of the last ticked child for sequences and selectors. This state is updated in accordance with the rule-set of the node in question – in response to the result of the current tick.
With a few exceptions, once a node has updated its state, it also completes – returning a result of Sucess/Failure or Running to its parent node. Generally this means that any tree tick will result in at least one action node ticked.
The result of the root node is the result of the entire tree execution – Running indicating that the tree has not completed and Success/Failure indicating a complete run and its result.
Before starting tree execution from its initial state, it must first be reset. This resets all node state set in earlier ticks of the tree.
Each node has a number of design-time configuration options – some types more than others. Two options shared by all are Instant and Inverse.
Inverse simply changes result values of Success to Failure and vice-versa.
The instant flag (off by default) actually alters the execution of certain parent nodes. When enabled, this can be used to have simple sensor actions not “consume” an entire tick, as its Sequence or Selector parent node will continue to its next child immediately after its evaluation.
For more details on nodes and their configuration options, see the “Nodes” chapter.
The Behave system is roughly divisible in four parts:
Visually represented by a common behaviour tree design notation, the Behave designer aims to shorten the distance between idea and implementation as much as possible.
At design-time, all Behave data goes into behave Libraries, which for runtime get compiled into an executable format. It is quite possible to use multiple libraries in each project both at edit and runtime, but commonly just one library per project is used.
Unity
After creating a Behave library asset via the Asset/Create menu or the Create dropdown in the project window, the Behave main window will pop up. You can also access it from the inspector when a Behave library is selected or from the Window menu.
Unity
Aside from their asset form, Behave libraries can also live as exported .behave files. Not editable before imported back into asset form again, .behave files can be handy for transferring (full or partial) libraries or backup. Import/export can be found under the Assets/Behave menu.
Standalone
Libraries live as .behave files on disk, which can be created and loaded from the sidebar menu.
In the library settings – accessible via the library name at the top of the sidebar, you can export the current library fully or partially as well as import a .behave file into the current library – merging the two.
With a library being edited, trees can be added to it via the little “+” button next to the “Trees” headline in the sidebar. Double-clicking items in the sidebar lets you rename them – Unix path seperators serving as a means to group trees together.
By drag-drop operation from the component bar to the canvas or via the keyboard interface, nodes can be easily added to your current tree. Within the canvas, easy drag-drop or keyboard operations allow you to quickly connect, configure and organise them.
Please find an overview of the keyboard mapping below:
| Shift + mouse drag | Drag node only (default being drag subtree) |
| Arrow keys | Move selection around the tree |
| Alt + Arrow keys | Move selected node and subtree |
| Shift + Alt + Arrow keys | Move selected node only |
| Shift + Left/Right arrow | Move selected output connection left/right |
| Return/Enter | Show insertion cursor/insert |
| Esc | Hide insertion cursor/deselect |
| Tab | Cycle insertion cursor type |
| Cmd/Ctrl + Backspace | Delete node |
| Shift + Cmd/Ctrl + Backspace | Delete input connection |
| T | Toggle component instant flag |
| V | Toggle component invert flag |
| C | Switch Parallel component completion mode |
| I | Switch Parallel component child completion mode |
Once your idea has made it from your thoughts to the canvas, the next goal of Behave becomes to wire that idea to your application code as quickly as possible.
This is achieved through a compiler. It builds your trees to runtime accessible classes which an be instantiated, wired to an agent and ticked via a direct function call.
Since your behaviour trees end up as classes and functions, they are not just fast, but also familiar and easy to use when programming your application.
To compile your currently edited library, select the library name in the sidebar, configure for debug or release, choose the compiler to use and press the “Apply changes” button.
Alternatively, click the apply changes button to the right of the “Library” sidebar header to compile with the last chosen options.
At runtime, for each compiled Behave library class, you can request new instances of your designed behaviour trees. When doing so, you need to specify an agent handling the newly instantiated tree.
Trees and agents live in a symbiotic relationship. The agent ticks the tree via a function call and the tree calls back to the agent for action handling.
Agent handler functions are either resolved by the tree, on instantiation, dynamically locating and linking agent functions via introspection or by the agent deriving from a compiled agent “blueprint” – an abstract class with virtual functions for the necessary handlers.
Tree to agent invokes with no registered handlers go to default handlers on the agent.
Any good rapid iteration tool needs good tools for testing and validating designs. The Behave debugger fits the bill nicely.
When built in debugging mode, Behave libraries include debugging data and functionality for all contained trees. Instantiated trees will, to each attached debugger, continuously send information about the currently active node of the tree. The debugger uses this information to visually show you the current state of the active tree instances.
Additionally, any attached debugger may at any point unplug tree instances and manually tick or reset them. Unplugged trees will on local tick immediately return a “running” state without evaluating or changing any tree state. This allows the developer to pause a tree and step through its execution while in a relevant environment.
Debugged trees may also unplug themselves if in their execution they happen upon a node marked with a breakpoint.
Last, but definitely not the least, overrides let debuggers augment the simulation as perceived by the executing trees. This facilitates easy testing of complex or rare scenarios or perhaps the impact of new actions with no handlers implemented.
Note that since the debugger executes over the network, you can debug any Behave build on your machine, another computer, on a phone or where-ever it is running. WebPlayer builds are the exception as their sandbox environment do not allow for incoming socket connections.
For debugging to function in your runtime, you need to either update it directly at your convenience / start it with a specified frequency or in your library build settings specify that the debugger should auto-launch. See the reference for more information.
Assuming that you are running a Behave tree which has been built for debug and that you are updating the debugger runtime as described in the Flow section, your runtime should show up in the debugger list of the Behave window.
If you are confident in your configuration and you are still not seeing your runtime, you might want to try hitting the refresh button a couple of times. Once you see the runtime, clicking it will connect the editor to it, list all contained trees and let you debug them.


You can add up to 3 client apps. Which means that you can install 3 chat boxes on 3 different websites.


Toggle navigation
TheSaferZone
Home
(current)
Contact
About
Sign Up
Email
Password
Login
Remember me
Sign Up
Forgot
password?
×
SignUp
Name:
Email:
Phone
Password
Find ministry Related to your problem
The site
Home
About Us
Contact Us
Location
Bengaluru :
10th Milestone, Hosur Rd, Bengaluru, Karnataka 560068
Contact
<EMAIL_ADDRESS>+91<PHONE_NUMBER>
×
Login/SignUp
Email:
Password
Login


A report published on Right-wing news website WND on Friday, quoting a defected Iranian intelligence officer, claimed that a massive blast had ripped through the nuclear facility, buried deep within the guts of a large mountain.
The alleged blast was said to have erupted at 11.30am last Monday – on the eve of the Israeli election – partially destroyed the nuclear site and trapped 240 people underground. Tehran held Israel responsible, the report said.
More than a week later, the report is yet to be verified by a single independent source. If true, it would be the most significant attack on Iranian nuclear capabilities to date and could spark a fierce reaction from the Islamic State.
And yet on Sunday evening, Shamseddin Barbroudi, deputy head of the Iranian Atomic Energy Organisation, assured Iranian reporters there had been no explosion at the nuclear facility whatsoever.
Earlier the same day, Avi Dichter, Israel's home defence minister, had been unable to confirm the unsubstantiated reports but nonetheless, welcomed them. "Any explosion in Iran that doesn't hurt people but hurts its assets is welcome," he said.
Speaking privately, officials in Israel's foreign ministry – known to have an extensive surveillance network monitoring Iran's key nuclear sites – claimed they had no reliable intelligence of an explosion at Fordow.
One theory put forward by Shlomo Aronson, an expert in Israeli foreign security policy at Jerusalem's Hebrew University, is that Tehran had deliberately leaked false reports about a blast to prevent international inspectors from entering the site.
"They [Tehran] are more than capable of inventing such a story – although if it's true, a damaged Fordow would definitely benefit Israel," Mr Aronson conceded.
"Israel would do anything within its power to stop the Iranian nuclear programme. This includes tactics that fall just short of, or substitute, a direct attack, such as the cyber war that has been raging for the past few years or acts of sabotage on Iran's nuclear facilities."
Buried 300 feet underground, the nuclear fortress at Fordow is immune to air strikes or bunker bombs. It is thought to contain more than 2,700 centrifuges enriching uranium to more than 20 per cent. But unlike Natanz, which has more than 10,000 centrifuges, it is not a nuclear reactor and therefore not as valuable to the Iranian nuclear programme.
Tehran has repeatedly blamed Israel for a string of explosive disasters that have hit Iranian nuclear targets, including the death of Mostafa Ahmadi Roshan, one of Natanz's top nuclear scientists, killed when his car exploded in January last year.
Whilst pleading ignorance of last Monday's alleged blast, a senior Israeli official conceded that penetrating a fortified facility such as Fordow would be neither impossible nor without precedent for Israeli's intelligence services.
"Anything man-made, we can penetrate," one Israeli official told The Daily Telegraph.


Demonstration of sound-match — an xcorrSound tool
Sound-match detects occurrences of a smaller audio file (e.g. a jingle) within a larger audio file or an index of audio files.
Choose a demo wave file, or upload your own
First wave file
No selection...
Short audio file
Larger audio file
Second wave file
No selection...
Short audio file
Larger audio file
This tests xcorrsound functionality, but not performance which is affected by network bandwidth and server load.
The samples are derived from "Revolve by hisboyelroy [Noncommercial Sampling Plus]" from ccMixter.org. ccMixter is a community music site featuring remixes licensed under Creative Commons.
ccmixter.org/files/hisboyelroy/430
Related Links
xcorrSound at Github
xcorrSound blog posts:
openplanetsfoundation.org/blogs/2012-07-09-xcorrsound-waveform-compare-new-audio-quality-assurance-tool
,
openplanetsfoundation.org/blogs/2013-05-21-sound-challenge-and-easter-egg-goes
,
openplanetsfoundation.org/blogs/2014-01-21-developing-audio-qa-workflow-using-hadoop-part-i
,
openplanetsfoundation.org/blogs/2014-02-03-developing-audio-qa-workflow-using-hadoop-part-ii
, and more to come
For any question or further information, please contact Bolette A. Jurik (baj at statsbiblioteket.dk)


MAJOR LEAGUE 2 A film review by James Berardinelli Copyright 1994 James Berardinelli
Rating (0 to 10): 2.9
Date Released: 3/30/94 Running Length: 1:48 Rated: PG (Language)
Starring: Charlie Sheen, Tom Berenger, Omar Epps, David Keith, Corbin Bernsen, Dennis Haysbert, Bob Uecker Director: David Ward Producer: James G. Robinson Screenplay: R. J. Stewart Music: Michael Colombier Released by Warner Brothers
I expect a certain number of contrivances in a baseball movie, especially one that's not meant to be taken seriously, but nothing prepared me for the sheer avalanche of formulas and cliches that fill the screen in MAJOR LEAGUE 2. It's enough to make any movie-goer, baseball fan or not, gnash their teeth in frustration. The situation would have been tolerable if the film was funny, but the writers apparently forgot to include the jokes.
It's a year after the events of the original MAJOR LEAGUE. Following a Cinderella-style division win, the Cleveland Indians were bounced in four from the American League Championship Series to face a winter of "waiting for next year." When Spring Training finally arrives, all the old faces are back, although most of them have new attitudes. Hard-throwing Ricky Vaughn (Charlie Sheen), the "Wild Thing", has cleaned up his image and lost ten mph off his fastball. Jake Taylor (Tom Berenger), the veteran catcher, walks with a limp and his gimpy leg threatens to keep him off the roster. Willie Mays Hayes (Omar Epps replacing Wesley Snipes) has decided to give up speed for power. Pedro Cerrano (Dennis Haysbert), the team's top home run hitter, has become a kinder, gentler soul. And Roger Dorn (Corbin Bernsen) has turned in his uniform for a suit - and the Indians' ownership.
The first MAJOR LEAGUE was an often-amusing motion picture that remained reasonably faithful to the sport from which it took its name. I was expecting something similar for the sequel, and was therefore appalled by the result. MAJOR LEAGUE 2 is one of the worst-scripted movies of the year. Not only is the screenplay littered with one-dimensional types and stock situations (many of which repeat things from the original), but the comedy is flat and the portrayal of baseball is idiotic.
Much of the humor of MAJOR LEAGUE came from subtle send-ups of the various baseball mannerisms of a group of oddball players. The sequel exchanges the amusing for the absurd. Little care has been paid to the intelligence of the audience, and at no time is this more obvious than during the final scene. The "strategy" used to get the big out, so obviously the product of unimaginative minds, is both counter to the basic logic of the game and ridiculous for the context in which it is presented.
There are two clever scenes in this film, both of which are parodies. The first is a sendup of low-grade action flicks, with Willie Mays Hayes and Jesse Ventura teaming up in BLACK THUNDER, WHITE LIGHTNING. The second presents "Wild Thing" Vaughn's attempts to do one of those "sophisticated" Right Guard commercials. Combined, this pair of sequences totals about four minutes, less than 5% of the movie's running time.
The editing is also a serious problem. Whoever pieced together the final print of MAJOR LEAGUE 2, did so without regard for tone or pacing. The choppiness of this movie is distracting, and impossible not to notice. Large chunks of the story appear to have been excised, and the film jumps from scene to scene with little concern for what went before or what comes after.
Does Bob Uecker have to be so annoying? Do Charlie Sheen and Tom Berenger have to be so lifeless? Does Margaret Whitton's Rachel Phelps have to go so unbelievably over-the-top? And why doesn't Corbin Bernsen take some acting lessons?
MAJOR LEAGUE 2 strikes out on three pitches and, as such, isn't worthy of any more play-by-play. See a real baseball game instead. Even if your favorite team loses, the experience will be more entertaining than sitting through this turkey.
- James Berardinelli<EMAIL_ADDRESS>.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| company | email* | password* | re-enter password* | first name* | last name* | date time* |
|---|---|---|---|---|---|---|
| Insert your email | ||||||
| This field is required.Insert your email | This field is required. | This field is required. | This field is required. | This field is required. | This field is required. |


Deep-PoC is an AI drivin project used to detect deepfakes in video or images. It uses known default of GAN generated AI such as the eyes and the mouth to determine whether the image or video contains a deepfake.
{% if status %}
{% if status == "fake" %}


|
Bosch XDK110 Solace MQTT App
2.0.1
MQTT Reference Application for the Bosch XDK110
|
Module to take periodic sensor samples based on the configuration. More...
Files | |
| file | AppTelemetrySampling.c |
| file | AppTelemetrySampling.h |
Macros | |
| #define | BCDS_MODULE_ID SOLACE_APP_MODULE_ID_APP_TELEMETRY_SAMPLING |
| #define | APP_TELEMETRY_SAMPLING_TASK_INTERNAL_WAIT_TICKS UINT32_C(10) |
| #define | APP_TELEMETRY_SAMPLING_TASK_DELETE_INTERNAL_WAIT_TICKS UINT32_C(5000) |
| #define | APP_TEMPERATURE_OFFSET_CORRECTION (-3459) |
Functions | |
| static void | appTelemetrySampling_TelemetrySamplingTask (void *pvParameters) |
| The sampling task. Runs a loop with a delay of the configured sampling interval. Reads the sensor data, creates a new AppTelemetryPayload and adds it to the AppTelemetryQueue. Updates the stats if sampling is slower than expected interval using AppStatus_Stats_IncrementTelemetrySamplingTooSlowCounter(). More... | |
| Retcode_T | AppTelemetrySampling_Init (const char *deviceId, uint32_t samplingTaskPriority, uint32_t samplingTaskStackSize, const CmdProcessor_T *sensorProcessorHandle) |
| Initialize the sampling module. Call in AppController_Init(). More... | |
| Retcode_T | AppTelemetrySampling_Setup (const AppRuntimeConfig_T *configPtr) |
| Setup of the sampling module. Call in AppController_Setup(). More... | |
| Retcode_T | AppTelemetrySampling_Enable (void) |
| Enable the module. Call in AppController_Enable(). More... | |
| Retcode_T | AppTelemetrySampling_ApplyNewRuntimeConfig (AppRuntimeConfig_ConfigElement_T configElement, const void *newConfigPtr) |
| Apply a new configuration. Call only when the sampling task is not running. More... | |
| Retcode_T | AppTelemetrySampling_CreateSamplingTask (void) |
| Create the sampling task. Call only if it isn't running. More... | |
| Retcode_T | AppTelemetrySampling_DeleteSamplingTask (void) |
| Delete sampling task. Does nothing if it doesn't exist. More... | |
| bool | AppTelemetrySampling_isTaskRunning (void) |
| Check if sampling task is running. More... | |
Variables | |
| static xTaskHandle | appTelemetrySampling_TaskHandle = NULL |
| static uint32_t | appTelemetrySampling_SamplingTaskPriority = 1 |
| static uint32_t | appTelemetrySampling_SamplingTaskStackSize = 1024 |
| static SemaphoreHandle_t | appTelemetrySampling_TaskSemaphoreHandle = NULL |
| static TickType_t | appTelemetrySampling_SamplingPeriodicityMillis = 1000 |
| static char * | appTelemetrySampling_DeviceId = NULL |
| static Sensor_Setup_T | appTelemetrySampling_SensorSetup |
| Sensor set-up structure. More... | |
Module to take periodic sensor samples based on the configuration.
| #define APP_TELEMETRY_SAMPLING_TASK_DELETE_INTERNAL_WAIT_TICKS UINT32_C(5000) |
wait ticks to delete sampling task
| #define APP_TELEMETRY_SAMPLING_TASK_INTERNAL_WAIT_TICKS UINT32_C(10) |
wait ticks to start sampling loop
| #define APP_TEMPERATURE_OFFSET_CORRECTION (-3459) |
Macro for static temperature offset correction. Self heating, temperature correction factor
| #define BCDS_MODULE_ID SOLACE_APP_MODULE_ID_APP_TELEMETRY_SAMPLING |
< undefine any previous module id
| Retcode_T AppTelemetrySampling_ApplyNewRuntimeConfig | ( | AppRuntimeConfig_ConfigElement_T | configElement, |
| const void * | newConfigPtr | ||
| ) |
Apply a new configuration. Call only when the sampling task is not running.
| [in] | configElement | the configuration element to apply. only AppRuntimeConfig_Element_activeTelemetryRTParams is supported. |
| [in] | newConfigPtr | the new configuration of type configElement |
| Retcode_T AppTelemetrySampling_CreateSamplingTask | ( | void | ) |
Create the sampling task. Call only if it isn't running.
| Retcode_T AppTelemetrySampling_DeleteSamplingTask | ( | void | ) |
Delete sampling task. Does nothing if it doesn't exist.
| Retcode_T AppTelemetrySampling_Enable | ( | void | ) |
Enable the module. Call in AppController_Enable().
| Retcode_T AppTelemetrySampling_Init | ( | const char * | deviceId, |
| uint32_t | samplingTaskPriority, | ||
| uint32_t | samplingTaskStackSize, | ||
| const CmdProcessor_T * | sensorProcessorHandle | ||
| ) |
Initialize the sampling module. Call in AppController_Init().
| [in] | deviceId | the device id |
| [in] | samplingTaskPriority | the priority of the sampling task |
| [in] | samplingTaskStackSize | the stack size of the sampling task |
| [in] | sensorProcessorHandle | the command processor handle for the sensor module |
| bool AppTelemetrySampling_isTaskRunning | ( | void | ) |
Check if sampling task is running.
| Retcode_T AppTelemetrySampling_Setup | ( | const AppRuntimeConfig_T * | configPtr | ) |
Setup of the sampling module. Call in AppController_Setup().
| [in] | configPtr | the runtime configuration. Only reads activeTelemetryRTParamsPtr. |
|
static |
The sampling task. Runs a loop with a delay of the configured sampling interval. Reads the sensor data, creates a new AppTelemetryPayload and adds it to the AppTelemetryQueue. Updates the stats if sampling is slower than expected interval using AppStatus_Stats_IncrementTelemetrySamplingTooSlowCounter().
| [in] | pvParameters | unused. |
| Retcode_RaiseError | RETCODE(RETCODE_SEVERITY_ERROR, RETCODE_SOLAPP_APP_TELEMETRY_SAMPLING_ERROR_READING_SENSOR_DATA) |
| Retcode_RaiseError | retcode from AppTelemetryQueue_AddSample() |
| Retcode_RaiseError | RETCODE(RETCODE_SEVERITY_FATAL, RETCODE_SOLAPP_APP_TELEMETRY_SAMPLING_ADD_SAMPLE_TO_QUEUE)) |
|
static |
local copy of device id
|
static |
local copy of configuration for sampling interval in millis
|
static |
sampling task priority with default
|
static |
sampling task stack size with default
|
static |
Sensor set-up structure.
|
static |
the samling task task handle
|
static |
sampling task semaphore


package rdd
Provides several RDD implementations. See org.apache.spark.rdd.RDD.
- Source
- package.scala
- Alphabetic
- By Inheritance
- rdd
- AnyRef
- Any
- Hide All
- Show All
- Public
- All
Type Members
-
class
AsyncRDDActions[T] extends Serializable with Logging
A set of asynchronous RDD actions available through an implicit conversion.
-
class
CoGroupedRDD[K] extends RDD[(K, Array[Iterable[_]])]
:: DeveloperApi :: An RDD that cogroups its parents.
:: DeveloperApi :: An RDD that cogroups its parents. For each key k in parent RDDs, the resulting RDD contains a tuple with the list of values for that key.
- Annotations
- @DeveloperApi()
- Note
This is an internal API. We recommend users use RDD.cogroup(...) instead of instantiating this directly.
-
class
DoubleRDDFunctions extends Logging with Serializable
Extra functions available on RDDs of Doubles through an implicit conversion.
-
class
HadoopRDD[K, V] extends RDD[(K, V)] with Logging
:: DeveloperApi :: An RDD that provides core functionality for reading data stored in Hadoop (e.g., files in HDFS, sources in HBase, or S3), using the older MapReduce API (
org.apache.hadoop.mapred
).:: DeveloperApi :: An RDD that provides core functionality for reading data stored in Hadoop (e.g., files in HDFS, sources in HBase, or S3), using the older MapReduce API (
org.apache.hadoop.mapred
).- Annotations
- @DeveloperApi()
- Note
Instantiating this class directly is not recommended, please use
org.apache.spark.SparkContext.hadoopRDD()
- type IsWritable[A] = (A) ⇒ Writable
-
class
JdbcRDD[T] extends RDD[T] with Logging
An RDD that executes a SQL query on a JDBC connection and reads results.
An RDD that executes a SQL query on a JDBC connection and reads results. For usage example, see test case JdbcRDDSuite.
-
class
NewHadoopRDD[K, V] extends RDD[(K, V)] with Logging
:: DeveloperApi :: An RDD that provides core functionality for reading data stored in Hadoop (e.g., files in HDFS, sources in HBase, or S3), using the new MapReduce API (
org.apache.hadoop.mapreduce
).:: DeveloperApi :: An RDD that provides core functionality for reading data stored in Hadoop (e.g., files in HDFS, sources in HBase, or S3), using the new MapReduce API (
org.apache.hadoop.mapreduce
).- Annotations
- @DeveloperApi()
- Note
Instantiating this class directly is not recommended, please use
org.apache.spark.SparkContext.newAPIHadoopRDD()
-
class
OrderedRDDFunctions[K, V, P <: Product2[K, V]] extends Logging with Serializable
Extra functions available on RDDs of (key, value) pairs where the key is sortable through an implicit conversion.
Extra functions available on RDDs of (key, value) pairs where the key is sortable through an implicit conversion. They will work with any key type
K
that has an implicitOrdering[K]
in scope. Ordering objects already exist for all of the standard primitive types. Users can also define their own orderings for custom types, or to override the default ordering. The implicit ordering that is in the closest scope will be used.import org.apache.spark.SparkContext._ val rdd: RDD[(String, Int)] = ... implicit val caseInsensitiveOrdering = new Ordering[String] { override def compare(a: String, b: String) = a.toLowerCase(Locale.ROOT).compare(b.toLowerCase(Locale.ROOT)) } // Sort by key, using the above case insensitive ordering. rdd.sortByKey()
-
class
PairRDDFunctions[K, V] extends Logging with Serializable
Extra functions available on RDDs of (key, value) pairs through an implicit conversion.
-
trait
PartitionCoalescer extends AnyRef
::DeveloperApi:: A PartitionCoalescer defines how to coalesce the partitions of a given RDD.
::DeveloperApi:: A PartitionCoalescer defines how to coalesce the partitions of a given RDD.
- Annotations
- @DeveloperApi()
-
class
PartitionGroup extends AnyRef
::DeveloperApi:: A group of
Partition
s::DeveloperApi:: A group of
Partition
s- Annotations
- @DeveloperApi()
-
class
PartitionPruningRDD[T] extends RDD[T]
:: DeveloperApi :: An RDD used to prune RDD partitions/partitions so we can avoid launching tasks on all partitions.
:: DeveloperApi :: An RDD used to prune RDD partitions/partitions so we can avoid launching tasks on all partitions. An example use case: If we know the RDD is partitioned by range, and the execution DAG has a filter on the key, we can avoid launching tasks on partitions that don't have the range covering the key.
- Annotations
- @DeveloperApi()
-
abstract
class
RDD[T] extends Serializable with Logging
A Resilient Distributed Dataset (RDD), the basic abstraction in Spark.
A Resilient Distributed Dataset (RDD), the basic abstraction in Spark. Represents an immutable, partitioned collection of elements that can be operated on in parallel. This class contains the basic operations available on all RDDs, such as
map
,filter
, andpersist
. In addition, org.apache.spark.rdd.PairRDDFunctions contains operations available only on RDDs of key-value pairs, such asgroupByKey
andjoin
; org.apache.spark.rdd.DoubleRDDFunctions contains operations available only on RDDs of Doubles; and org.apache.spark.rdd.SequenceFileRDDFunctions contains operations available on RDDs that can be saved as SequenceFiles. All operations are automatically available on any RDD of the right type (e.g. RDD[(Int, Int)]) through implicit.Internally, each RDD is characterized by five main properties:
- A list of partitions
- A function for computing each split
- A list of dependencies on other RDDs
- Optionally, a Partitioner for key-value RDDs (e.g. to say that the RDD is hash-partitioned)
- Optionally, a list of preferred locations to compute each split on (e.g. block locations for an HDFS file)
All of the scheduling and execution in Spark is done based on these methods, allowing each RDD to implement its own way of computing itself. Indeed, users can implement custom RDDs (e.g. for reading data from a new storage system) by overriding these functions. Please refer to the Spark paper for more details on RDD internals.
-
class
RDDBarrier[T] extends AnyRef
:: Experimental :: Wraps an RDD in a barrier stage, which forces Spark to launch tasks of this stage together.
:: Experimental :: Wraps an RDD in a barrier stage, which forces Spark to launch tasks of this stage together. org.apache.spark.rdd.RDDBarrier instances are created by org.apache.spark.rdd.RDD#barrier.
- Annotations
- @Experimental() @Since( "2.4.0" )
-
class
SequenceFileRDDFunctions[K, V] extends Logging with Serializable
Extra functions available on RDDs of (key, value) pairs to create a Hadoop SequenceFile, through an implicit conversion.
Extra functions available on RDDs of (key, value) pairs to create a Hadoop SequenceFile, through an implicit conversion.
- Note
This can't be part of PairRDDFunctions because we need more implicit parameters to convert our keys and values to Writable.
-
class
ShuffledRDD[K, V, C] extends RDD[(K, C)]
:: DeveloperApi :: The resulting RDD from a shuffle (e.g.
:: DeveloperApi :: The resulting RDD from a shuffle (e.g. repartitioning of data).
- K
the key class.
- V
the value class.
- C
the combiner class.
- Annotations
- @DeveloperApi()
-
class
UnionRDD[T] extends RDD[T]
- Annotations
- @DeveloperApi()
Value Members
- object JdbcRDD extends Serializable
-
object
PartitionPruningRDD extends Serializable
- Annotations
- @DeveloperApi()
-
object
RDD extends Serializable
Defines implicit functions that provide extra functionalities on RDDs of specific types.
Defines implicit functions that provide extra functionalities on RDDs of specific types.
For example, RDD.rddToPairRDDFunctions converts an RDD into a PairRDDFunctions for key-value-pair RDDs, and enabling extra functionalities such as
PairRDDFunctions.reduceByKey
. - object UnionRDD extends Serializable