|
areaDetector
3-12-1
EPICS areaDetector framework
|
#include <specsAnalyser.h>
Public Member Functions | |
| SpecsAnalyser (const char *portName, const char *driverPort, int maxBuffers, size_t maxMemory, int priority, int stackSize) | |
| virtual | ~SpecsAnalyser () |
| specsAnalyser destructor More... | |
| void | specsAnalyserTask () |
| Task to listen to the SPECS prodigy application and update the higher level software. More... | |
| asynStatus | makeConnection () |
| asynStatus | connect () |
| asynStatus | disconnect () |
| asynStatus | readEnum (asynUser *pasynUser, char *strings[], int values[], int severities[], size_t nElements, size_t *nIn) |
| Called when asyn clients call pasynEnum->read(). More... | |
| asynStatus | writeInt32 (asynUser *pasynUser, epicsInt32 value) |
| Called when asyn clients call pasynInt32->write(). More... | |
| asynStatus | writeFloat64 (asynUser *pasynUser, epicsFloat64 value) |
| Called when asyn clients call pasynFloat64->write(). More... | |
| asynStatus | validateSpectrum () |
| Validate the currently defined spectrum. More... | |
| asynStatus | defineSpectrumFAT () |
| Define a Fixed Analyser Transmission spectrum. More... | |
| asynStatus | defineSpectrumSFAT () |
| Define a Snapshot Fixed Analyser Transmission spectrum. More... | |
| asynStatus | defineSpectrumFRR () |
| asynStatus | defineSpectrumFE () |
| asynStatus | readAcquisitionData (int startIndex, int endIndex, std::vector< double > &values) |
| asynStatus | sendStartCommand (bool safeAfter) |
| Send the start command to the analyser. More... | |
| asynStatus | sendSimpleCommand (const std::string &command, std::map< std::string, std::string > *data=NULL) |
| Method for sending a simple command (no parameters) that will check the error status and do the right thing. More... | |
| asynStatus | readDeviceVisibleName () |
| This method queries the analyser for its device name to populate the ADModel parameter. More... | |
| asynStatus | setupEPICSParameters () |
| This method sets up the analyser parameters that are not known prior to connecting to the device. More... | |
| asynStatus | getAnalyserParameterType (const std::string &name, SPECSValueType_t &value) |
| asynStatus | getAnalyserParameter (const std::string &name, int &value) |
| asynStatus | getAnalyserParameter (const std::string &name, double &value) |
| asynStatus | getAnalyserParameter (const std::string &name, std::string &value) |
| asynStatus | getAnalyserParameter (const std::string &name, bool &value) |
| asynStatus | setAnalyserParameter (const std::string &name, int value) |
| asynStatus | setAnalyserParameter (const std::string &name, double value) |
| asynStatus | setAnalyserParameter (const std::string &name, std::string value) |
| asynStatus | readIntegerData (std::map< std::string, std::string > data, const std::string &name, int &value) |
| asynStatus | readDoubleData (std::map< std::string, std::string > data, const std::string &name, double &value) |
| asynStatus | readSpectrumParameter (int param) |
| asynStatus | readRunModes () |
| asynStatus | readSpectrumDataInfo (SPECSDataInfoParam_t param) |
| Send the GetSpectrumDataInfo method to query the spectrum metadata. More... | |
| asynStatus | asynPortConnect (const char *port, int addr, asynUser **ppasynUser, const char *inputEos, const char *outputEos) |
| Connect to the underlying low level Asyn port that is used for comms. More... | |
| asynStatus | asynPortDisconnect (asynUser *pasynUser) |
| asynStatus | commandResponse (const std::string &command, std::string &response, std::map< std::string, std::string > &data) |
| This sends a command to the device and parses the response. More... | |
| asynStatus | asynWriteRead (const char *command, char *response) |
| Wrapper for asynOctetSyncIO write/read functions. More... | |
| asynStatus | cleanString (std::string &str, const std::string &search=": \n", int where=0) |
| Utility function, returns strings with unwanted characters stripped. More... | |
| asynStatus | initDebugger (int initDebug) |
| asynStatus | debugLevel (const std::string &method, int onOff) |
| asynStatus | debug (const std::string &method, const std::string &msg) |
| asynStatus | debug (const std::string &method, const std::string &msg, int value) |
| asynStatus | debug (const std::string &method, const std::string &msg, double value) |
| asynStatus | debug (const std::string &method, const std::string &msg, const std::string &value) |
| asynStatus | debug (const std::string &method, const std::string &msg, std::map< std::string, std::string > value) |
| asynStatus | debug (const std::string &method, const std::string &msg, std::map< int, std::string > value) |
| Public Member Functions inherited from ADDriver | |
| ADDriver (const char *portName, int maxAddr, int numParams, int maxBuffers, size_t maxMemory, int interfaceMask, int interruptMask, int asynFlags, int autoConnect, int priority, int stackSize) | |
| All of the arguments are simply passed to the constructor for the asynNDArrayDriver base class, except numParams. More... | |
| virtual asynStatus | connect (asynUser *pasynUser) |
| Connects driver to device; This method is called when the driver's pasynCommon->connect() function is called. More... | |
| virtual void | setShutter (int open) |
| Set the shutter position. More... | |
| Public Member Functions inherited from asynNDArrayDriver | |
| asynNDArrayDriver (const char *portName, int maxAddr, int maxBuffers, size_t maxMemory, int interfaceMask, int interruptMask, int asynFlags, int autoConnect, int priority, int stackSize) | |
| This is the constructor for the asynNDArrayDriver class. More... | |
| virtual | ~asynNDArrayDriver () |
| virtual asynStatus | writeOctet (asynUser *pasynUser, const char *value, size_t maxChars, size_t *nActual) |
| Called when asyn clients call pasynOctet->write(). More... | |
| virtual asynStatus | readGenericPointer (asynUser *pasynUser, void *genericPointer) |
| This method copies an NDArray object from the asynNDArrayDriver to an NDArray pointer passed in by the caller. More... | |
| virtual asynStatus | writeGenericPointer (asynUser *pasynUser, void *genericPointer) |
| This method currently does nothing, but it should be implemented in this base class. More... | |
| virtual asynStatus | setIntegerParam (int index, int value) |
| Sets the value for an integer in the parameter library. More... | |
| virtual asynStatus | setIntegerParam (int list, int index, int value) |
| Sets the value for an integer in the parameter library. More... | |
| virtual asynStatus | readInt32 (asynUser *pasynUser, epicsInt32 *value) |
| virtual asynStatus | readFloat64 (asynUser *pasynUser, epicsFloat64 *value) |
| virtual void | report (FILE *fp, int details) |
| Report status of the driver. More... | |
| virtual asynStatus | createFilePath (const char *path, int pathDepth) |
| Function to create a directory path for a file. More... | |
| virtual asynStatus | checkPath () |
| Checks whether the directory specified NDFilePath parameter exists. More... | |
| virtual bool | checkPath (std::string &filePath) |
| Checks whether the directory specified exists. More... | |
| virtual asynStatus | createFileName (int maxChars, char *fullFileName) |
| Build a file name from component parts. More... | |
| virtual asynStatus | createFileName (int maxChars, char *filePath, char *fileName) |
| Build a file name from component parts. More... | |
| virtual asynStatus | readNDAttributesFile () |
| Create this driver's NDAttributeList (pAttributeList) by reading an XML file This clears any existing attributes from this drivers' NDAttributeList and then creates a new list based on the XML file. More... | |
| virtual asynStatus | getAttributes (NDAttributeList *pAttributeList) |
| Get the current values of attributes from this driver and appends them to an output attribute list. More... | |
| asynStatus | incrementQueuedArrayCount () |
| asynStatus | decrementQueuedArrayCount () |
| int | getQueuedArrayCount () |
| void | updateQueuedArrayCount () |
Additional Inherited Members | |
| Public Attributes inherited from asynNDArrayDriver | |
| class NDArrayPool * | pNDArrayPool |
| An NDArrayPool pointer that is initialized to pNDArrayPoolPvt_ in the constructor. More... | |
| SpecsAnalyser::SpecsAnalyser | ( | const char * | portName, |
| const char * | driverPort, | ||
| int | maxBuffers, | ||
| size_t | maxMemory, | ||
| int | priority, | ||
| int | stackSize | ||
| ) |
|
virtual |
specsAnalyser destructor
| asynStatus SpecsAnalyser::asynPortConnect | ( | const char * | port, |
| int | addr, | ||
| asynUser ** | ppasynUser, | ||
| const char * | inputEos, | ||
| const char * | outputEos | ||
| ) |
Connect to the underlying low level Asyn port that is used for comms.
This uses the asynOctetSyncIO interface, and also sets the input and output terminators.
| port | - Name of the port to connect to. |
| addr | - Address to connect to. |
| ppasynUser | - Pointer to the asyn user structure. |
| inputEos | - String input EOS. |
| outputEos | - String output EOS. |
| asynStatus SpecsAnalyser::asynPortDisconnect | ( | asynUser * | pasynUser | ) |
| asynStatus SpecsAnalyser::asynWriteRead | ( | const char * | command, |
| char * | response | ||
| ) |
Wrapper for asynOctetSyncIO write/read functions.
| command | - String command to send. |
| response | - String response back. |
| asynStatus SpecsAnalyser::cleanString | ( | std::string & | str, |
| const std::string & | search = ": \n" , |
||
| int | where = 0 |
||
| ) |
Utility function, returns strings with unwanted characters stripped.
| str | - string parameter, the string to clean up, returned by reference |
| search | - string parameter containing the set of characters to strip from str |
| where | - integer parameter to control where characters are stripped - 1 to strip from start, 2 to strip from end, 0 to do both. |
| asynStatus SpecsAnalyser::commandResponse | ( | const std::string & | command, |
| std::string & | response, | ||
| std::map< std::string, std::string > & | data | ||
| ) |
This sends a command to the device and parses the response.
Data is returned in a std::map that is indexed by the parameter name
| command | - String command to send. |
| response | - String response back (OK or ERROR) |
| data | - Map of data items indexed by name |
| asynStatus SpecsAnalyser::connect | ( | ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg | ||
| ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg, | ||
| int | value | ||
| ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg, | ||
| double | value | ||
| ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg, | ||
| const std::string & | value | ||
| ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg, | ||
| std::map< std::string, std::string > | value | ||
| ) |
| asynStatus SpecsAnalyser::debug | ( | const std::string & | method, |
| const std::string & | msg, | ||
| std::map< int, std::string > | value | ||
| ) |
| asynStatus SpecsAnalyser::debugLevel | ( | const std::string & | method, |
| int | onOff | ||
| ) |
| asynStatus SpecsAnalyser::defineSpectrumFAT | ( | ) |
Define a Fixed Analyser Transmission spectrum.
All of the desired parameters should have already been set, this method constructs the required command string from those parameters and sends it to the device.
| asynStatus SpecsAnalyser::defineSpectrumFE | ( | ) |
| asynStatus SpecsAnalyser::defineSpectrumFRR | ( | ) |
| asynStatus SpecsAnalyser::defineSpectrumSFAT | ( | ) |
Define a Snapshot Fixed Analyser Transmission spectrum.
All of the desired parameters should have already been set, this method constructs the required command string from those parameters and sends it to the device.
| asynStatus SpecsAnalyser::disconnect | ( | ) |
| asynStatus SpecsAnalyser::getAnalyserParameter | ( | const std::string & | name, |
| int & | value | ||
| ) |
| asynStatus SpecsAnalyser::getAnalyserParameter | ( | const std::string & | name, |
| double & | value | ||
| ) |
| asynStatus SpecsAnalyser::getAnalyserParameter | ( | const std::string & | name, |
| std::string & | value | ||
| ) |
| asynStatus SpecsAnalyser::getAnalyserParameter | ( | const std::string & | name, |
| bool & | value | ||
| ) |
| asynStatus SpecsAnalyser::getAnalyserParameterType | ( | const std::string & | name, |
| SPECSValueType_t & | value | ||
| ) |
| asynStatus SpecsAnalyser::initDebugger | ( | int | initDebug | ) |
| asynStatus SpecsAnalyser::makeConnection | ( | ) |
| asynStatus SpecsAnalyser::readAcquisitionData | ( | int | startIndex, |
| int | endIndex, | ||
| std::vector< double > & | values | ||
| ) |
| asynStatus SpecsAnalyser::readDeviceVisibleName | ( | ) |
This method queries the analyser for its device name to populate the ADModel parameter.
| asynStatus SpecsAnalyser::readDoubleData | ( | std::map< std::string, std::string > | data, |
| const std::string & | name, | ||
| double & | value | ||
| ) |
| asynStatus SpecsAnalyser::readEnum | ( | asynUser * | pasynUser, |
| char * | strings[], | ||
| int | values[], | ||
| int | severities[], | ||
| size_t | nElements, | ||
| size_t * | nIn | ||
| ) |
Called when asyn clients call pasynEnum->read().
The base class implementation simply prints an error message.
| pasynUser | - pasynUser structure that encodes the reason and address. |
| strings | - Array of string pointers. |
| values | - Array of values |
| severities | - Array of severities |
| nElements | - Size of value array |
| nIn | - Number of elements actually returned |
| asynStatus SpecsAnalyser::readIntegerData | ( | std::map< std::string, std::string > | data, |
| const std::string & | name, | ||
| int & | value | ||
| ) |
| asynStatus SpecsAnalyser::readRunModes | ( | ) |
| asynStatus SpecsAnalyser::readSpectrumDataInfo | ( | SPECSDataInfoParam_t | param | ) |
Send the GetSpectrumDataInfo method to query the spectrum metadata.
Currently only OrdinateRange is supported, which gives us the units and min/max of the non-energy axis. This method is new in protocol version 1.11 so in earlier versions we expect to receive an error message.
| param | - Data Info parameter to request. Currently (v1.11) only OrdinateRange is supported. |
| asynStatus SpecsAnalyser::readSpectrumParameter | ( | int | param | ) |
| asynStatus SpecsAnalyser::sendSimpleCommand | ( | const std::string & | command, |
| std::map< std::string, std::string > * | data = NULL |
||
| ) |
Method for sending a simple command (no parameters) that will check the error status and do the right thing.
| asynStatus SpecsAnalyser::sendStartCommand | ( | bool | safeAfter | ) |
Send the start command to the analyser.
| asynStatus SpecsAnalyser::setAnalyserParameter | ( | const std::string & | name, |
| int | value | ||
| ) |
| asynStatus SpecsAnalyser::setAnalyserParameter | ( | const std::string & | name, |
| double | value | ||
| ) |
| asynStatus SpecsAnalyser::setAnalyserParameter | ( | const std::string & | name, |
| std::string | value | ||
| ) |
| asynStatus SpecsAnalyser::setupEPICSParameters | ( | ) |
This method sets up the analyser parameters that are not known prior to connecting to the device.
| void SpecsAnalyser::specsAnalyserTask | ( | ) |
Task to listen to the SPECS prodigy application and update the higher level software.
This function runs the polling thread. It is started in the class constructor and must not return until the IOC stops.
| asynStatus SpecsAnalyser::validateSpectrum | ( | ) |
Validate the currently defined spectrum.
This validation must take place before a new acquisition can begin. The values defined for the acquisition can actually be altered by the validation so the read back values are written back into the parameters.
| asynStatus SpecsAnalyser::writeFloat64 | ( | asynUser * | pasynUser, |
| epicsFloat64 | value | ||
| ) |
Called when asyn clients call pasynFloat64->write().
Write integer value to the drivers parameter table.
| pasynUser | - Pointer to the asyn user structure. |
| value | - The new value to write |
|
virtual |
Called when asyn clients call pasynInt32->write().
Write integer value to the drivers parameter table.
| pasynUser | - Pointer to the asyn user structure. |
| value | - The new value to write |
Reimplemented from ADDriver.
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |
|
protected |


Stefanos Tsitsipas wins ATP Tour Finals after victory over Dominic Thiem in London
The 21-year-old Greek held his nerve to win in a tie-break after a three set thriller as it ended 6-7 (6-8), 6-2, 7-6 (7-4)
by Alex MilneStefanos Tsitsipas won the ATP Finals after coming from behind to record a three set victory over Austrian Dominic Thiem in London with a 6-7 (6-8), 6-2, 7-6 (7-4) win.
It was the biggest win of Tsitsipas' young career so far on his debut appearance at the tournament, and after seeing off the great Roger Federer in the semi-final he clinched victory in the final after having to do it the hard way.
Thiem won the first set after triumphing 8-6 in a nail-biting tie-break, but Tsitsipas roared back in the second with a 6-2 win
It went down to the wire in the final set, with a second tie-break of the match, but Tsitsipas had enough to see off his opponent 7-4, and he collapsed to the ground after Thiem's shot wide sealed the victory.
Speaking after the match to BBC Tsitsipas said: "I've no clue how I played so well in the second set, I think my mind was at ease and I didn't give him much opportunity to play.
"It was frustrating to play with so many nerves but I'm so relieved I managed to win!"
The 21-year-old Greek becomes the youngest ATP Finals debutant to win the competition since John McEnroe, who won it at the age of 19 in 1978, and the youngest ATP Finals champion at all since Lleyton Hewitt in 2001.
This is the penultimate year the ATP Finals will be held in London, as after 2020's event it will move to Turin.
All eyes will soon turn to the Australian Open, which will take place in Melbourne in January. After winning the European Open in Antwerp in October, it is thought that Andy Murray could return to play in Australia, exactly a year after admitting he may have to retire.


@* * This template is called from the `index` template. This template * handles the rendering of the page header and body tags. It takes * two arguments, a `String` for the title of the page and an `Html` * object to insert into the body of the page. *@ @(title: String,user: models.User)(content: Html)


Machine Learning
In the field of pattern recognition and machine learning, we consider the supervised scenario where we have a labelled training set which we use to learn the parameters of a model that predicts a target vector.
Problem type inference
We encounter the importance of semantic data types in machine learning right away, as the field distinguishes two kinds of supervised learning tasks. When predicting a finite number of discrete categories, the task is known as classification, and when predicting one or more continuous variables, it is known as regression [bishop2006pattern]. Automatically distinguishing the two might be seen trivial, however, there are ambiguous cases. Values represented by the computer as ‘0’ and ‘1’ could be both binary (a special case of a categorical variable) or continuous (a count). While in theory, we could enforce categories to have a string representation and continuous values integer or float representations, this is not the case with real-world datasets. Often data is stored in plain-text CSV files, where the distinction is lost. Automatically distinguishing between problem type is not merely a mental exercise, it is actively used in AutoML (the process of automatically applying machine learning, not the product).
For an example, see usage of typesets.
Confidence scores
When classification is used in practice, we often do not want to rely solely on the label prediction and want a measure of certainty that the model is correct. This is especially the case when a decision can have an enormous impact. Consider a medical diagnosis problem where, based on an fMRI scan, we wish to determine whether the patient has cancer. The cost of classifying a non-cancerous scan as cancerous is not as high as vice versa. One method of certainty is to let the model output a confidence score for each prediction, indicating the certainty with which the prediction is taken. A reliable confidence score gives us the option to avoid automatically making decisions on difficult cases. When we can assume that the confidence score is a probability, we can draw from tools provided by probability theory. In this special case, the confidence has to adhere to the rules of probability, such as it should be in the interval [0, 1] and that for samples predicted with 0.8 confidence that should mean that about 80% of these samples belong to the true class. A classifier is said to be well-calibrated when it adheres to these rules.
Models as Logistic regression return well-calibrated predictions by default, while others return biased scores, such as Random Forest or SVM classifiers. One can perform various analysis to understand how well a classifier is calibrated.
A hierarchical type system such as visions
can be used to differentiate between confidence scores and probabilities.
One then could perform specialised types of analysis based on this type.
The scikit-learn package provides excellent resources for model calibration 1. For more background on the relevant aspects of probability and decision theory, we recommend reading [bishop2006pattern], chapter 1.5, p. 38-42.
Encoding variables
Another case in machine learning where semantic types are relevant is the encoding of variables. There are various ways to encode variables in predictive models that depend on its statistical type. For example, categorical values can be encoded as one-hot or dummy coded, random projection or via learned representations. Ordinals can be encoded as integer (or embedded). Likewise, strategies for filling missing values may also depend on the data type.
Model profiling
There are plans to implement specific model statistics in the model-profiler package (to be released).
This package will focus on summarization of a model or sets of predictions and will be based on a custom visions
typeset.
Relevant statistics encompass error metrics, analysis of residuals and model explainers.
Footnotes


Mark Lassoff, Vernon, Connecticut
<EMAIL_ADDRESS>My favorite foods are chicken, pasta and fish.
I've learned the proper basic document structure and the difference between a tag and an element.
Rome, Paris, Athens, London
Link to directory


{% extends 'academics/base.html' %} {% block content %}
The resource you are requesting for doesnot exist in this server


Alabama |
|---|
|
The state of Alabama was named after the Alabama river. That river was named by European exporers after a Native American tribe that lived in the territory and first appeared in 1540, the Alibamu Tribe. The name Alabama is thought to be a combination of two Choctaw words; Alba and Amo. "Alba" would mean vegetation, herbs, or plants. "Amo" would mean gatherer or picker. So together they might mean Vegetation Gatherers, which would be a fitting description for the Alibamu Tribe who cleared a lot of land for agricultural purposes. The United States Congress created the Alabama Territory on March 3rd, 1817, then it became the 22nd state two years later on December 14th, 1819. |


Short Codes
Headings
Buttons
Badges
Alerts
Well done! You successfully read this important alert message.
Heads up! This alert needs your attention, but it's not super important.
Warning! Best check yo self, you're not looking too good.
Oh snap! Change a few things up and try submitting again.
Navs
Progress bars
Panels
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Labels
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Default Primary Success Info Warning Danger
Tables
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
Contextual classes
| Class | Description |
|---|---|
.active
|
Applies the hover color to a particular row or cell |
.success
|
Indicates a successful or positive action |
.info
|
Indicates a neutral informative change or action |
.warning
|
Indicates a warning that might need attention |
.danger
|
Indicates a dangerous or potentially negative action |
| # | Column heading | Column heading | Column heading |
|---|---|---|---|
| 1 | Column content | Column content | Column content |
| 2 | Column content | Column content | Column content |
| 3 | Column content | Column content | Column content |
| 4 | Column content | Column content | Column content |
| 5 | Column content | Column content | Column content |
| 6 | Column content | Column content | Column content |
| 7 | Column content | Column content | Column content |
| 8 | Column content | Column content | Column content |
| 9 | Column content | Column content | Column content |


?6
7
8
9
10
v
The
New
York
copyright
reserved
botanical
Garden
AMERICAN
GRASSES
DISTRIBUTED
BY
THE
U.
S.
DEPARTMENT
OF
AGRICULTURE
PREPARED
BY
THE
SYSTEMATIC
AGROSTOLOGIST
791.
Aristida
gyrans
Chapm.

Savanna.
Collector,
E.
L.
Ekman
October
21,
1922
This
specimen
should
be
cited,
Ò
Amer,
Gr.
Nat.
Herb.
no.
791.Ó
1659646
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


Icon treatments for commonly used form input types and utility classes. Input types include search, URL, email, and password. See the form type page for more information.
search
URL
Email
Password
Form Icon Utilities
form-icon-left
form-icon-left-more
form-icon-left-flush
form-icon-right
form-icon-right-more
form-icon-right-flush
form-padding-left
form-padding-left-more
form-padding-left-flush
form-padding-right-flush
Image background utility classes for forms, to help adjust the positioning and fit of background icons. To adjust icon size, see .


Sometimes, it's tough to get to your "Happy Place". What's a "Happy Place"? Well, it's a euphemism to allow yourself to not worry about the things that are mentally bothering you. It can really be anything or even anyone.
Here are a few things that get me to my happy place:


--- layout: page weight: 10 title: PHP navigation: show: true --- {% anchor h2 %} Parse Webhook {% endanchor %}
In this example, we want to parse all emails at<EMAIL_ADDRESS>and post the parsed email to http://sendgrid.com/email.php.
Given this scenario, the following are the parameters you would set at the Parse API settings page:
{% codeblock %} Hostname: email.sendgrid.biz {% endcodeblock %} {% codeblock %} URL: http://sendgrid.com/email.php {% endcodeblock %} To test this scenario, we sent an email to<EMAIL_ADDRESS>and created the following form at http://sendgrid.com/email.php: {% codeblock lang:php %} {% endcodeblock %} {% anchor h2 %} Event Webhook {% endanchor %}To use the Event Webhook, you must first setup Event Notification.
In this scenario, we assume you've set the Event Notification URL to go the endpoint /parse.php
on your server. Given this scenario the following code will allow you to process events:


"Give Me Faith and devotion and I would give you fulfillment and completeness"
-ParamaPujya PrathaSmaraniya Gurudev Dr Narayan Dutt Shriimaliji


{{locality}}
Search
Reset All
{{locality}}
BHK
{{bhk}}
Listed By
{{roles}}
Budget
Area
Construction Stage
{{construction}}
Furnishing
{{furnishing}}
Ammenities
{{ammenities}}


{% extends 'pages/pagesbasic.html' %} {% block content %}
Here is the corner for all the relevent laws concerning housing in California, and especially the Bay Area.


Hyundai Aura compact sedan spotted on test in India - launch expected early 2020
by Team ODHyundai recently revealed the name and the engine options of its upcoming compact sedan, Aura. This time around the sedan has been spotted on test in an almost production-ready form. The sedan will come equipped with two petrol engines and a diesel engine with a choice of an optional automatic in both variants.
Out of the three, two are petrol engines. 1.2-litre four-cylinder petrol engine which is expected to have the same tune as the Hyundai Grand i10 Nios. 83PS and 116Nm of torque. The engine will be available with a choice of an optional automatic.
The 1.0-litre turbocharged engine on offer is the same mill we've experienced in the Venue, however, the power is expected to be detuned. This engine will be offered a five-speed manual gearbox only.
For buyers opting the diesel variant will get the 1.2-litre three-cylinder engine with a choice of an optional automatic gearbox. The Hyundai Aura will be equipped with an advanced NOx trap catalyst and PM filters to minimize environmental pollution.
The Aura is expected to break cover sometime in January 2020 and post its launch the compact sedan will rival the Honda Amaze, Maruti Suzuki Dzire and the Ford Aspire.
Image source - Indian Autos Blog
Also Read,
Special feature: Great India Drive in the Hyundai Venue, Part 1
Hyundai Grand i10 diesel and AMT variants discontinued
2020 Hyundai Elite i20 hatchback to have all-digital instrument cluster


Enrollee
edit
Contact Information
- Voice Phone
- {{ enrollee?.voicePhone | phone | default }}
- Extension
- {{ enrollee?.voiceExtension | default }}
Notification Information
- Email Notification
- {{ enrollee?.contactEmail | default }}
- Text Notification (SMS)
- {{ enrollee?.contactPhone | phone | default }}
College Certifications
edit
- College Certification
- {{ certification.collegeCode | configCode: 'colleges' | default }}
- License Number
-
{{ certification.collegeCode | configCode: 'colleges' : 'prefix' }}{{ certification.licenseNumber | default }}
- License Class
- {{ certification.licenseCode | configCode: 'licenses' | default }}
- Renewal Date
- {{ certification.renewalDate | formatDate | default }}
- Advanced Practices
- {{ certification.practiceCode | configCode: 'practices' | default }}
Job Information
edit
- Job Titles
-
Self Declaration
edit
Have you ever been the subject of an order or a conviction for an information contravention?
Have you ever been the subject of an order or a conviction for an information contravention?
Have you ever had Terms and Conditions imposed on your licence as a result of disciplinary actions taken
by a governing body?
Have you ever had Terms and Conditions imposed on your licence as a result of disciplinary actions taken
by a governing body?
Organization Information
edit
- Organization Types
-
-
{{ organization.organizationTypeCode | configCode: 'organizationTypes' }}
None


|
Nakama C++ Client SDK
2.4.1
Client for Nakama Server
|
An object within the storage engine. More...
#include <NStorageObject.h>
Public Attributes | |
| std::string | collection |
| The collection which stores the object. More... | |
| std::string | key |
| The key of the object within the collection. More... | |
| std::string | userId |
| The user owner of the object. More... | |
| std::string | value |
| The value of the object. More... | |
| std::string | version |
| The version hash of the object. More... | |
| NStoragePermissionRead | permissionRead = NStoragePermissionRead::NO_READ |
| The read access permissions for the object. More... | |
| NStoragePermissionWrite | permissionWrite = NStoragePermissionWrite::NO_WRITE |
| The write access permissions for the object. More... | |
| NTimestamp | createTime = 0 |
| The UNIX time when the object was created. More... | |
| NTimestamp | updateTime = 0 |
| The UNIX time when the object was last updated. More... | |
An object within the storage engine.
| std::string NStorageObject::collection |
The collection which stores the object.
| NTimestamp NStorageObject::createTime = 0 |
The UNIX time when the object was created.
| std::string NStorageObject::key |
The key of the object within the collection.
| NStoragePermissionRead NStorageObject::permissionRead = NStoragePermissionRead::NO_READ |
The read access permissions for the object.
| NStoragePermissionWrite NStorageObject::permissionWrite = NStoragePermissionWrite::NO_WRITE |
The write access permissions for the object.
| NTimestamp NStorageObject::updateTime = 0 |
The UNIX time when the object was last updated.
| std::string NStorageObject::userId |
The user owner of the object.
| std::string NStorageObject::value |
The value of the object.
| std::string NStorageObject::version |
The version hash of the object.


Send Money
Wallet Balance
Us Dollar
165.480.00 USD
Add Funds
User Name or Email
Amount in USD
Description
Send Money
Settings Content
Transactions
6
Send
Exchange
Account


| Vendor Name | Weaver and Devore Trading Limited |
|---|---|
| Reference Number | W1568-058615/001/EDM |
| Contract Date | 3-3-2005 |
| Description of Work | PARKA/JACKET, EXCEPT DOWNFILLED (INCLUDING RCMP COMBAT, LINED |
| Delivery Date | 18-3-2005 |
| Contract Value | $10,893.00 |
| Comments | |
| Additional Comments |


---
layout: post
title: Honeymoon, Part 8 (unfinished)
date: '2010-01-14T06:25:00.000+10:00'
author: Jamie Teh
tags:
- honeymoon
modified_time: '2011-08-09T21:52:15.065+10:00'
blogger_id: tag:blogger.com,1999:blog-5419412965543098028.post-2793752926326763002
permalink: /2010/01/honeymoon-part-8-unfinished.html
---
Note: This post has been floating around on my computer for years, but I never did finish it. I've decided to just post it in its incomplete form; something is better than nothing. :)
Jamie: Our journey from Florence to Cork in Ireland was extremely long, boring and tedious. We left our hotel in Florence at around 6am and didn't arrive at our hotel in Cork until nearly 10pm. Our train from Florence to Rome was running late, so we were worried we'd miss our plane to Dublin, but thankfully, we made it in time. Due to icy roads, we were told it was going to be extremely difficult to get a cab to the hotel, but thankfully, we were okay there, too. These are yet another couple of proverbial travel related bullets we've dodged this trip. We also found out that the weather in Cork was uncharacteristically cold. Soon after, we started hearing endless talk about the "big freeze" on the news. :)
Our hotel in Cork, The Ambassador, was a very nice hotel indeed, probably the best of the trip so far. This was quite fortuitous, as we spent a considerable amount of time there, partly because we wanted to lie around and relax a bit and also because of the icy roads and extreme cold at night. It resides on a hill, which afforded Jen a spectacular view of the city from our room.
We both very much enjoyed the atmosphere of Cork. Everyone we met was extremely warm, friendly and helpful. Of course, there was an abundance of Irish pubs. On our first day, we stopped at a pub for a cup of hot port and one of hot whisky. Yum! (I love warm alcoholic beverages.)
On our last day there, we took a bus to Blarney, a very small town about 15 minutes drive from Cork. Its prominent feature is Blarney Castle. ...


progress pending bars
progress running bars
progress done bars
progress exited bars
progress suspended bars


--- layout: comedian permalink: /comedians/david-thompson.html comedian: id: david-thompson name: David Thompson img-align: 50% 0% ---
David left the Christian cult he grew up in and moved to the calm, peaceful city of Prague. He had a drunk tattoo within two days. He is a reformed vegan, enjoys patting grumpy strangers' dogs and likes putting himself in awkward situations and telling people about it afterwards.


SOUTHIE (director/writer: John Shea; screenwriters: Jimmy Cummings/Dave McLaughlin; cinematographer: Allen Baker; editor: Tracy S. Granger; cast: Donnie Wahlberg (Danny Quinn), Anne Meara (Mrs. Quinn), Rose McGowan (Kathy Quinn), Lawrence Tierney (Colie Powers), Jimmy Cummings (Joey Ward), Will Arnett (Whitey), Jere Shea (Martin Powers), Amanda Peet (Marianne), John Shea (Pete), Josh Marchette (Will), 1998)
Reviewed by Dennis Schwartz
A very familiar crime story, one that has been often done in recent times, about a rough Irish neighborhood and the hoods who can't escape from it. "Southie" is about such residents in South Boston, an old blue-collar Irish neighborhood. First-time director John Shea has made this independent low-budget film, that is long on gritty atmosphere but short on substance. It's a violent film, where action speaks louder than words. The climax between the two rival Irish Mafia gangs is settled with guns not words. There doesn't seem to be a point to this film, except to show some tough guys in action, and how difficult it is to stop old habits. The acting is good enough and the background music, a mixture of rap, rock, and Celtic sounds, evokes a sense of Irish doom. But, the story fails to build any drama into it, and everything seems too bleak. It is an easy film to take on its terms, if you want to take a look at such a dead-end of possibilities and watch a dysfunctional family spin out of control. It reminded me of "Monument Ave.," which covered the same territory.
Danny Quinn (Donnie Wahlberg) comes back to his old stomping grounds in South Boston after running away to New York City for the last three years to detox from alcohol and to turn over a new leaf from his old roughhouse ways. The last time he was in town, he was in a drunken stupor and held a gun to the head of a rival Irish gang leader's son, Joey Ward (Cummings).
Danny comes home to a close-knit but dysfunctional family that is in a crisis situation. Anne Meara is his widowed mother, suffering from stress due to a heart condition, who is trying to hold the troubled family together without a father-figure present. She has been in and out of the hospital for the past few years due to all the family stress. Kathy (Rose McGowan) is Danny's alcoholic sister, who is taking a walk on the wild side. His two brothers are unemployed and have incurred big gambling debts to the Irish Mafia.
Mrs. Quinn looks upon Danny as the savior of the family, glad that he now drinks soda instead of whiskey, and that he wants to be a construction worker not a gangster. He tells his ex-girlfriend (Amanda) that he's a changed man and everyone else in the neighborhood who would believe him. The weakness in the script, is in how fast this changes when he can't get a job and he quickly gets back with his low-level mobster friends. Whitey (Arnett) has plans to open an illegal after-hours casino and talks Danny into becoming a partner, but he fails to tell Danny that his other partner is Joey Ward. It was just too difficult to understand how that could happen considering the hatred between these two is known throughout the community and how Danny swore he wouldn't do anything dishonest anymore.
This casino partnership starts all the fireworks between Powers' Irish gang, the one Danny has close ties with, and the upstart Butchie Ward gang. A predictable shootout occurs between the two gangs and Danny's past is relived, as he is drawn into the conflict. There are no surprises here, everything goes down a path to nowhere. Since the film has no final note to end on, it uses the St. Paddy's Day parade to have its final shot--which is tantamount to waving the flag to indicate patriotism, or in this case, Irish pride.
REVIEWED ON 7/10/2000 GRADE: C
Dennis Schwartz: "Ozus' World Movie Reviews"
http://www.sover.net/~ozus
<EMAIL_ADDRESS>© ALL RIGHTS RESERVED DENNIS SCHWARTZ
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


What did you think? Anything special you want see next? Let us know below.
Thank you, your feedback has been received.
We appreciate it, and will do our best to act on it.
Also feel free to email Alex at<EMAIL_ADDRESS>We would love to hear from you.


Hi! My name is Alice Lai, and I'm an Electrical and
Computer Engineering undergraduate at Carnegie Mellon
University. I love learning to use new technologies and building
complex devices from the ground up! My interests span from PCB
layout and circuit design to developing ROS software packages.
I am an active member of CMU's DARPA Subterranean Challenge team
(Team Explorer) as well as the Tartan AUV RoboSub team. For Team
Explorer, I am currently working on staircase climbing capabilities
for UGVs, and for Tartan AUV, I am researching and implementing MPC
algorithms for controls.
In my free time, I like to dance hip hop, cook with my friends, and
tinker with various electronic devices (aka take them apart and
forget to try to fix them)!
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Check it outIn my freshman year I became really interested in PCB layout, circuit design, and firmware development. For Carnegie Mellon Racing, I worked on two custom modules: AFC and DAQ. AFC (Accumulator Fan Controller) controlled 7 24V DC fans to cool the battery pack dubbed "accumulator". DAQ (Data Acquisition Module) was a custom board that accepted 4 general analog sensor inputs and transmitted sensor data over CAN accordingly.
I also developed a custom board to control high-power LEDs for Team Explorer. It is currently being used on the payloads of all UAVs and UGVs for Team Explorer, and is also being used on other projects in the Air Lab.
Finally, I developed the schematics and PCB layout for HSC for Tartan AUV. HSC (High Speed Controller) had 8 sets of power and logic for motor ESCs, as well as a dedicated section for reading IMU and various sensor data. HSC ended up never getting manufactured, but the design is still pretty neat!
When I figure out how to manage my time better I hope to learn more about power electronics and do more PCB hardware work!
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Check it out The MATE ROV competition was the defining experience of my high school
career. It was through MATE ROV that I first discovered my passion for and
gained my basic education in embedded systems and robotics.
In my senior year, I led the team to qualify for the Internationals
competition for the first time in 10 years, earning 2nd place
in the Regionals competition and narrowly losing 1st to Drexel
University.
Check out my resume for a somewhat complete overview of my professional engineering experiences and projects!
Download Resume PDF


val DOES_NOT_REPEAT: Recurrence
A recurrence that doesn't repeat. When finding events for this recurrence, only the start date event will be returned.


|
Shift Invariant Space Library (SISL)
|
Combines a lattice and a generating function. More...
#include <si_function.hpp>
Public Member Functions | |
| si_function () | |
| Evaluate the function at a point. | |
| si_function (L *lattice) | |
| Evaluate the function at a point. | |
| virtual const double | operator() (double d0,...) const |
| Evaluate the function at a point. | |
| virtual const double | operator() (const vector &p) const |
| Evaluate the function at a point. | |
| virtual const double | d (int component, double d0,...) const |
| Evaluate the function at a point. | |
| virtual const double | d (int component, const vector &p) const |
| Evaluate the function at a point. | |
| virtual const vector | grad (double d0,...) const |
| Evaluate the function at a point. | |
| virtual const vector | grad (const vector &p) const |
| Evaluate the function at a point. | |
| void | set_basis_scale (const double &h) |
| Sets a scale for the basis function to use. | |
| void | use_basis_gradient () |
| If the basis has a derivative, this makes the function use that derivative for derivative reconstruction. | |
| void | use_derivative_lattice () |
| If the function has derivative lattices, this makes the function use the given basis to reconstruct derivative values. | |
| void | set_lattice (L *new_lat) |
| Sets the current reconstruction lattice. | |
| void | set_derivative_lattice (unsigned int component, L *d) |
| Sets the lattice to be used for derivative reconstruction use use_derivative_lattice() to use this for reconstruction after all lattices have been set. | |
| void | set_transform (const transform &t) |
| Sets the transform for this space,. | |
| transform | get_transform () const |
| L * | get_lattice () |
| void | set_scale (const vector &s) |
| vector | get_scale () const |
| virtual const int | dim () const |
| Returns the input dimension of this function. | |
| virtual const double | n_d (const int_tuple &order, double d0,...) const |
| Evaluate the n'th partial derivative at a point. | |
| virtual const double | n_d (const int_tuple &order, vector &p) const |
| Evaluate the n'th partial derivative at a point. | |
| Public Member Functions inherited from sisl::function | |
| virtual const double | eval (double d0,...) |
| Evaluate the function at a point. | |
| virtual const double | eval (const vector &p) |
| Evaluate the function at a point. | |
Combines a lattice and a generating function.
|
inline |
Gets the transform assiated to this space,


Launch your SaaS in style with this suite of carefully crafted pages and components.
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
Non pulvinar neque laoreet suspendisse interdum consectetur libero id. Qwamii id leo in vitae turpis massa. Sapien habitant tristique.
“We cut our build times in half compared to our previous process. Love it.”
“The support team is super helpful. We're so glad to have them on call.”
“Reliability is what Jumpstart is known for, and they've totally delivered this time.”


IBMSD is recognized as one of the most significant IT service delivery center of IBM Corporation from more than 25 delivery centers around the world.
We have provided a wide array of IT services to the leading organizations in Thailand since 2002. Today, there are more than 1,000 IBMers under our blue umbrella.
At IBMSD, you will never standstill. We provide the world class environment that full of incredible opportunities to learn and grow on your desired career.
You will be a member of 400,000 IBMers’ community who always think, share and act their expertise for the better future.
Being the leader of the industry, all of our contributions always make the future not only to our customer, but also to our industry and to our world.
We are now looking for new IBMer who are ready to join the journey, to share the passion and to make the future with us.


Banner here...
Sign in:
New user?
Click here
Total Points:
50
Total point available for this tournament :
50
vs
:


title = "Federal Bonding Program (FBP)" url = "/employers/incentives/bonding" layout = "default" is_hidden = 0 child_of = "incentives/default" hide_crumb = 0 remove_crumb_trail = 0 crumb_disabled = 0 ==
For additional information contact our State Bonding Coordinator or call:
(785) 296-7435
Kansas Department of Commerce
1000 S.W. Jackson St., Suite 100
Topeka, KS 66612-1354
(785) 296-7435 TTY: 711


My objective is to prove that the emonTx with RF board is functioning correctly before I move forward
I have very carefully built my emonTx, following to the letter on a clean build WinXP laptop with OEM.org FTDI adapter & cable the instructions here using the 'blink' test programme: http://arduino.cc/en/Guide/windows
I have a blue LED lit solid on the FTDI board but didn't see any Tx/Rx LEDs light when uploading to the board
I appreciate that I'm probably not going to see the emonTx LED blink because it's on a different pin but I do get 'Done uploading' in the bottom panel of the Arduino IDE. I realise also that I can probably change the int led = # to get the emonTx LED to blink but haven't the confidence to do that yet ahead of ensuring that it is at least working.
Does that mean that it's accepted the sketch?
I couldn't find anywhere here or generally how to remove that or any other sketch ahead of loading the emonTx software.
I believe I am practically competent with electronics (broadcast, amateur radio, IT etc.) but have minimal knowledge of programming but willing and hoping to learn from this and other projects. My main aim is great energy monitoring - and control for my business building and home.
In anticipation thank you for your help.
Thank you.
Steve
Re: Proving emonTx is functioning after build
Steve,
I found it confusing that the FTDI can attach to the board two ways (the connection is not keyed or labeled). I initially started with the FTDI very bright blue LED facing the board and it would not work. By reversing it on the header so it faces the LED away from the board it works. For even more confusion, the NanodeRF is the opposite (face the LED towards the board). Have you verified that the header is attached the right way?
Dan
Re: Proving emonTx is functioning after build
Welcome, Steve,
The "Blink" test program in the Arduino library won't do anything. The LED on the emonTx is on a different output, as you say. If you look at the pinout picture of the emonTx, you can see that if you change
to
(that's DIO9 in the picture Digital In/Out 9) it will happen (hopefully!). Try it. I don't see how you can harm anything.
didn't see any Tx/Rx LEDs light when uploading to the board There aren't any! There might have been if you were using a serial port, but not the USB port.
Does that mean that it's accepted the sketch? Yes. You don't need to "remove" a sketch. Uploading a sketch will overwrite the old one.
Learning software.
My bible for C is of course "Kernigan & Ritchie" http://www.amazon.co.uk/C-Programming-Language-2nd/dp/0131103628/ref=sr_.... This is the standard text book.
The normal place I point people at who want to move up to C++ is http://www.relisoft.com/book/index.htm and that assumes you know C. Because the Arduino environment normally uses a very small subset of the language, neither are the best place for a beginner to start, nor are many of the other on-line tutorials. I'd still suggest you have both of those, and maybe Bruce Eckel's "Thinking in C++" http://www.planetpdf.com/developer/article.asp?ContentID=6634 available for reference.
However, there is this: http://www.me.umn.edu/courses/me2011/arduino/arduinoGuide.pdf which does look to be a good starting place for a beginner. It does not go as far as classes and methods that are used here, though.
I'd say get stuck in and do some hands-on learning. If you're afraid of asking embarrassing questions in the forum, PM me.
Re: Proving emonTx is functioning after build
OK thank you Dan and Robert,
Excellent, the green emonTx is now flashing! So far, so good. I probably could have found the pin 9 reference but I'm at work (own business) and meant to be getting on with other things :) - although this is hopefully the start of having an energy, weather, status dashboard for our business centre.
I'll move forward now on to the next steps.
Thank you again for the help and extra info.
Regards,
Steve
Re: Proving emonTx is functioning after build
Dan:
(the connection is not keyed or labeled) Not quite true: Not keyed, yes, but the pins on the shop FTDI at least are each labelled. GND is one end, RTS the other, and GND is labelled on the emonTx, on the GLCD and on the NanodeRF.
It's not outstandingly obvious, especially on the emonTx, so I've put a blob of white paint on the connector housings of everything to make it easier.


We recognize that expert financial statements are not always easy to understand and contain limited information. Accordingly, this note attempts to provide Rolling Jubilee financial information in basic terms.
It is Rolling Jubilee’s intention to be transparent and accountable in our financial operations. To accomplish this goal we are releasing details of our latest debt buys, our financial audit for 2012 and Financial Statements through September 30, 2013. These financial documents were prepared by our independent auditors, Fuoco Group, Certified Public Accountants and Business Advisors.
Our financial audit report for 2012 represents the most thorough level of verification and includes confirmation of accounts with outsiders and verification of calculations. The most up-to-date financial statement includes activities for 2013 created by looking at the books of the Rolling Jubilee Fund, not a full audit of RJ operations and expenses, which we did for 2012 and will do again at the end of December 2013.
The Rolling Jubilee has one purpose only: to provide mutual aid to debtors by purchasing debt in the secondary market and abolishing it. All costs that contribute to this purpose are classified as Program expenses. RJ uses experts in the industry to ensure that we've been able to spend the money more responsibly, abolish more debt, and abolish the right kinds of debt - debt that makes a tangible financial impact in people's lives. While we have done extensive research, we recognize that we are not professionals. Working with these insiders helped us to minimize program expenses because they negotiated heavy price discounts in recognition of the social welfare aims of the Rolling Jubilee. These insiders, who have decades of experience, also helped to vet and review every portfolio we purchased.
General and supporting services include all other costs incurred to support the infrastructure necessary to carry out RJ’s purpose. RJ accomplishes much at very low cost because we have no office space overheads or staff, nor do Board members receive any form of compensation. RJ has also received innumerable hours of service by unpaid volunteers, including pro bono consulting and labor from other industry insiders, lawyers, accountants, techies, PR experts, etc. Due to these facts, we’ve been able to keep administrative costs around 6%.
Here is a summary of what the Rolling Jubilee has accomplished since October 2012 (as of September 30, 2013).
We have $210,954 left to spend on future debt purchases. So far we have focused exclusively on medical debt. In the future we hope to abolish other forms of debt as well.
If you have any lingering questions about RJ’s finances or operations, please feel free to email us. We aim to operate with utmost transparency and would be happy to address any questions.
« Back to the Transparency documents
« Back to Rolling Jubilee


Maginhawa Street is located in Teacher’s Village East, Diliman, Quezon City, Philippines. This road stretches from Philcoa (accessible through Commonwealth Ave.) and V. Luna Extension (coming from Kalayaan.) Teacher’s Village is near several universities including the University of the Philippines Diliman, Ateneo de Manila University and Miriam College, which has made the place very popular with the student crowd.
◙By car / private vehicle / bicycle
You can get to Maginhawa Street from:
•East Avenue – V. Luna Avenune – V. Luna Extension
•EDSA – Kamias – Kalayaan Avenue – Malingap Street
•Commonwealth Avenue – Philcoa (Masaya Street)
•Katipunan Avenue – C.P. Garcia – Magiting Street
•Anonas – V. Luna Extension
•Quezon City Circle entry points: Kalayaan Avenue, Maharlika or Philcoa
◙TRICYCLES:
There are tricycle stations with trikes going to Maginhawa located in:
•Philcoa (Masaya Street): Red trikes – Philcoa TODA
•Housing (Maharlika Street beside National Housing Authority along Quezon Avenue): Orange trikes – UPTV (UP Teacher’s Village) TODA
•Beside PureGold Jr. in Kalayaan Ave. (Malamig Street) – Blue and Orange trikes
•Beside SM Save More Supermarket on V. Luna Extension: Orange trikes – BSV (Barangay Sikatuna Village) TODA
•Across Mini-Stop (Maginhawa corner Magiting street) walking distance from C.P. Garcia intersection
•Across Mona’s Bakeshop (Maginhawa corner P. Francisco)
◙ROUTE 1: BUS – TRIKE
Coming from the South
•From EDSA, ride any Northbound bus going to PHILCOA
•Get down at PHILCOA
•Take a tricycle to your restaurant of choice
Coming from the North
•From EDSA, ride a bus going to Quezon Avenue (Ilalim)
•Get down at McDonald’s Quezon Avenue. Cross to the other side.
•Ride a jeep going to PHILCOA
•Go down at PHILCOA
•Take a tricycle to your target restaurant
◙ROUTE 2: LRT 2 – JEEP – TRIKE
•Ride the LRT 2 (Purple Line) and get down at Anonas Station
•Ride a City Hall or Fairview jeepney right behind the St. Joseph Church.
•Tell the driver to drop you off at SM Savemore-Sikatuna
•Take a tricycle to your restaurant of choice
◙ROUTE 3: MRT 3 – JEEP – TRIKE
•Ride the MRT and get off at the GMA-Kamuning station
•Exit on the northbound side and walk towards the intersection of EDSA and East Avenue
•Cross to the other side of East Avenue and take the jeep going to V. Luna
•Get off at the Petron station fronting the AFP Medical Center along V. Luna Road
•Take a tricycle to your restaurant of choice
◙ROUTE 4: (From Ateneo) JEEP x 2 – TRIKE
•From Ateneo, go to Gate 2 and take a jeep to UP campus and get off at the shopping center
•Take a UP Ikot jeep and get off at CP Garcia. Go to the side of the community park with the stoplight on the corner of Magiting
•Walk the short stretch of Magiting Street towards Mini-Stop until you reach Maginhawa.
 Cross to the other side of the pedestrian overpass
•Take a tricycle to your target restaurant in Maginhawa


Thinking Style
August 14, 2015
The learning style which fit me the most was AS, with CR ans AR tying for second place. I've found that being able to review some examples of the concepts I'm going to use beforehand help give me a more clear picture of what direction to go in. I'm also a fan of trial and error and this week of assignments was very helpful for that. Using IRB, puts in my code, and the solution.rb files using trial and error on the exercises helped narrow down what sorts of tweaks to made in my code. Time monitoring techniques , time boxing and mindfulness in particular, have proven to be very useful in helping me stay on track and better adjust my habits.


Kiwi.Plugins.SocialConnect.Base Class
The Base class used to outline the core functionality that most SocialMedia sites have.
This class shouldn't be directly created, but instead extended from by other classes implement social media SDKs.
Item Index
Methods
Methods
_readConfig
-
config
Used to configure the settings property based on an object literal passed. Currently used in the constructor.
Parameters:
-
config
Object
init
-
params
Handles the initialsation of the Social Media SDK (if necessary).
Extended classes should create a "_init" method instead of overriding this one when creating their own.
Parameters:
-
params
ObjectAny parameters required by the SDK. This will be passed to the "_init" method.
Returns:
If the init method was called or not.
log
-
string
-
[type=1]
A method which handles logging out a message. Used internally only.
There are three different types of methods which can be used. 1 - Uses the 'Kiwi.Log.log' method. 2 - Uses the 'Kiwi.Log.warn' method. 3 - Uses the 'Kiwi.Log.error' method.
Parameters:
-
string
StringThe string that is to be logged out.
-
[type=1]
Number optionalThe type of method to use when logging out.
login
-
params
Handles the login functionality for this Social Media SDK (if necessary).
Extended classes should create a "_login" method instead of overriding this one when creating their own.
Parameters:
-
params
ObjectAny parameters required by the SDK. This will be passed to the '_login' method.
Returns:
If the init method was called or not.
Properties
_initialized
Boolean
public
If the SDK has been initialised yet.
Default: false
game
Kiwi.Game
public
The game that this is a part of.
initialized
Boolean
public
If this has been initialised or not.
name
String
public
The name of the Social Media which this class contains the functionality for.
settings
Object
public
Contains the settings regarding the functionality this plugin contains.
settings.init
Boolean
If it requires initialisation or not.
settings.login
Boolean
If it supports login or not.


Creating elements
Table of contents
Polymer provides a useful collection of elements to get you started, but if you’ve embraced the “Everything is an element” philosophy, you’ll quickly want to make your own elements—whether to share with others or just to make your own apps easier to manage.
By building on top of the power of Web Components, Polymer makes creating your own elements extremely easy. Define the markup you want stamped out for each instance of the element and optionally define some properties and methods. Then import the element and the browser will treat it like any other native DOM element.
One of the key features of elements is that they’re encapsulated—their details don’t leak out to the rest of your page. That means your element can masquerade as a native element on the outside, while inside it can leverage Polymer magic, such as:
- Two-way data binding
- Event binding
- Dynamic templates
- Automatic node finding
- …and much more
Polymer’s motto within this encapsulated world is “reduce boilerplate.” You’ll find yourself writing far less script to accomplish common tasks, and spending more time on the interesting challenges of your element.
If you combine this with the ability to use preexisting elements you’ll quickly discover how easy it is to build rich applications out of simple building blocks.
Setup
1. Install Polymer
If you haven’t already done, so, install the latest version of Polymer as described in Getting the Code.
2. Build a Polymer element
Polymer provides extra goodies for creating declarative, souped-up custom elements. We call these “Polymer elements”. From the outside they look just like any other DOM element, but inside they’re filled with handy features like two-way data binding and other bits of Polymer magic. These features make it easy to build complex components with much less code.
To create a new element:
- Load Polymer core (
polymer.html
). - Declare your custom element using
<polymer-element>
.
In the following example, we define a new element named <my-element>
, save
it to a file elements/my-element.html
, and use an HTML Import to load the polymer.html
dependency.
my-element.html
<link rel="import" href="../bower_components/polymer/polymer.html">
<polymer-element name="my-element" noscript>
<template>
Hello from my-element. This is my Shadow DOM.
</template>
</polymer-element>
Two items to notice:
-
The
name
attribute is required and must contain a “-“. It specifies the name of the HTML tag you’ll instantiate in markup (in this case<my-element>
). -
The
noscript
attribute indicates that this is a simple element that doesn’t include any script. An element declared withnoscript
is registered automatically.
Reuse other elements
By composing simple elements together we can build richer, more complex components. To reuse other elements in your <polymer-element>
, install the element in your app:
bower install Polymer/polymer-ajax
and include an import to load the new dependency in my-element.html
:
<link rel="import" href="../bower_components/polymer/polymer.html">
<link rel="import" href="../bower_components/polymer-ajax/polymer-ajax.html">
<polymer-element name="my-element" noscript>
<template>
I'm my-element. This is my Shadow DOM.
<polymer-ajax url="http://example.com/json" auto response="{{resp}}"></polymer-ajax>
<textarea value="{{resp}}"></textarea>
</template>
</polymer-element>
3. Create an app
Lastly, create an index.html
that imports your new element. Remember to include platform.js
to load polyfills for the native APIs.
Here’s the full example:
<!DOCTYPE html>

<link rel="import" href="elements/my-element.html">

<my-element></my-element>

Note: You must run your app from a web server for the HTML Imports polyfill to work properly. This requirement goes away when the API is available natively.
Your final directory structure should look something like this:
yourapp/
bower_components/
platform/
polymer/
elements/
my-element.html
index.html
Now that you’ve got the basic setup, it’s time to start using the features!
Using Polymer’s features
Polymer provides a number of sugaring APIs for authoring web components. Below are a few of the concepts. Consult the API reference for detailed information on each of these features.
Add properties and methods
When you’re creating a new element, you’ll often need to expose a public API so users can configure it. To define a public API, include a
</polymer-element>
<!DOCTYPE html>

<link rel="import" href="proto-element.html">

<proto-element></proto-element>

Adding lifecycle methods
Lifecycle callbacks are special methods you can define on your element which fire when the element goes through important transitions.
When a custom element has been registered it calls its created()
callback (if one has been defined). When Polymer finishes its initialization, the ready()
method is called.
The ready
callback is a great place to do constructor-like initialization work.
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="ready-element">
<template>
This is element has a ready() method.
Not ready...
</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="ready-element.html">

<ready-element></ready-element>

Learn more about all of the lifecycle callbacks.
Declarative data binding
Data binding is a great way to quickly propagate changes in your element and reduce boilerplate code. You can bind properties in your component using the “double-mustache” syntax ({{}}
). The {{}}
is replaced by the value of the property referenced between the brackets.
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="name-tag">
<template>
This is {{owner}}'s name-tag element.
</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="name-tag.html">

<name-tag></name-tag>

Note: Polymer’s data-binding is powered under the covers by a sub-library called TemplateBinding, designed for other libraries to build on top of.
Binding to markup
You can use binding expressions in most HTML markup, except for tag names themselves. In the following example, we create a new property on our component named color
whose value is bound to the value of the color
style applied to the custom element. Bindings ensure that any time a property like color
is changed, the new value will be propagated to all binding points.
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="fav-color">
<template>
This is {{owner}}'s fav-color element.
{{owner}} likes the color
{{color}}.
</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="fav-color.html">

<fav-color></fav-color>

Binding between components and built-in elements
You can use bindings with built-in elements just like you would with Polymer elements. This is a great way to leverage existing APIs to build complex components. The following example demonstrates binding component properties to attributes of native input elements.
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="age-slider">
<template>
This is {{owner}}'s age-slider.
{{name}} lets me borrow it.
He likes the color {{color}}.
I am {{age}} years old.

Age:
<input id="ageInput" type="range"
value="{{age}}">
Name:
<input id="nameInput" value="{{name}}"
placeholder="Enter name...">

</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="age-slider.html">

<age-slider></age-slider>

Note: Giving age
an initial value 25
gives Polymer
a hint that this property is an integer.
Publishing properties
Published properties can be used to define an element’s “public API”. Polymer
establishes two-way data binding for published properties and provides access
to the property’s value using {{}}
.
Publish a property by listing it in the attributes
attribute in your <polymer-element>
. Properties declared this way are initially null
. To provide a more appropriate default value, include the same property name directly in your prototype.
The following example defines two data-bound properties on the element, owner
and color
,
and gives them default values:
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="color-picker"
attributes="owner color">
<template>
This is a {{owner}}'s color-picker.
He likes the color {{color}}.
</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="color-picker.html">

<color-picker owner="Scott" color="blue"></color-picker>

In this example the user overrides the defaults for owner
and color
by configuring the element with initial attribute values (e.g. <color-picker owner="Scott" color="blue">
).
Note: When binding a property that takes a type other than String, it’s important to hint a property’s type. Polymer relies on this information to correctly serialize and de-serialize values.
Learn more about published properties.
Automatic node finding
The use of the id
attribute has traditionally been discouraged as an anti-pattern because the document requires element IDs to be unique. Shadow DOM, on the other hand, is a self-contained document-like subtree; IDs in that subtree do not interact with IDs in other trees. This means the use of IDs in Shadow DOM is not only permissible, it’s actually encouraged. Each Polymer element generates a map of IDs to node references in the element’s template. This map is accessible as $
on the element and can be used to quickly select the node you wish to work with.
<link rel="import"
href="/components/polymer/polymer.html">
<polymer-element name="editable-color-picker" attributes="owner color">
<template>

This is a {{owner}}'s editable-color-picker.
He likes the color {{color}}.

<button on-click="{{setFocus}}">Set focus to text input</button>
<input id="nameInput" value="{{owner}}"
placeholder="Your name here...">
</template>

</polymer-element>
<!DOCTYPE html>

<link rel="import" href="editable-color-picker.html">

<editable-color-picker></editable-color-picker>

Learn more about automatic node finding
Next steps
Now that you know how to create your own elements you’re ready to unleash the true power of Polymer. To dive even deeper, read up on Polymer’s core API reference or if you’d like to know more about the underlying technologies that make Polymer (and Web Components) possible, check out the Platform guide. Continue on to:


We redefine interfaces!
- seize rich e-commerce
- deliver extensible mindshare
- brand seamless eyeballs
- monetize dynamic infrastructures
- e-enable end-to-end web services
- extend cross-media e-services
- seize proactive users
- synthesize compelling e-tailers
- transform plug-and-play convergence
- innovate virtual partnerships
- generate front-end markets
- utilize rich convergence
- exploit e-business initiatives
- aggregate compelling functionalities


Major Parts of the Web
The web mis made up of a number of different pieces. I am part of the web, so is my computers. Computer browsers are connnected to servers using HTTP. The final part of the web are the servers, which are very much like the hardware we use at home, but are optimized for hosting files.
HTML- Hypertext Markup Language is a type of document on the web. HTML is made up of these elements;
1. Text of content - This is what you see.
2. Markup - This is what it looks like.
3. References to other documents - This is usually made up of images and video.
4. Links to other pages - These take you to other pages on the web.
HTML MarkupHTML markup langage is made up of an opening tag, content and usually a closing tag. The closing tag includes a "/" to indicate the close of the tag. This entire sentence is called an element. Another important part of markup are tags. Tags provide direction regarding how the text should look (e.g., bold, italics, underlined).
Stupid Computers
Computers do not think on their own, they require a set of instructions for how to act. It is important to ensure that the instructions are precise and correct because the computer will follow whatever it is told to do, regardless of how incorrect those instructions are. Care with how we program is essential to avoid these mistakes.
Inline and Block
Examples of Inline elements are line breaks, bold, italics. Block elements have an invisible box around them that has height and width.