| DOSE: T+ 0:00 |
15 mg |
oral |
DiPT |
| T+ 0:45 |
250 mg |
oral |
DXM |
It was right befor Christmas and I was house sitting for a friend of the family's. During the first week of being at the house I was approached by a friend who had the oppurtunity to get her hands on some DIPT. With no hesitance I accepted the offer and we were off to the house. It was just myself and my friend, squirel, when we first took the 15mg of Dipt.
After 45 min we felt nothing. I decided that It was time to take some action and I took the 250mg of DXM. My freind watched as I downed the pill and decided that she should do the same. Because we were in an unfamiliar surrounding and because neither of us had any experience with either of these drugs we decided we would need supervision. So we called our friend hickface.
Hickface showed up and I remember just feeling drunk and I actually felt very at peace with every thing. Then I began to turn to sand and everything was being seen as if it were an old time movie complete with reel and bad editing. When ever anyone would move there would be a general disturbance in the settling of the sand and it was begining to cause me to get distressed-+.
I started to fell very uneasy and felt that I was about to be sick, which I was.  It was at this moment that squirel began complaining of pains and a fear that she was dieing. My trip began to take a turn for the worse and I decided that I needed to be alone. Somehow I managed to make it to the master bed room where I would spend the next 14 hours.
I tried to lay down but had trouble stayin in one position. I then decided that I needed to take half of my clothes off. Which was followed by another trip to the bathroom because I felt that I was going to be sick again. I started to feel very over heated and asked hickface for a wet cold towel. Squirel was asking for the same thing from what I was told.
During the night I went on many trips, many of which ended with me thinking the weeks had gone by and I had missed christmas, but in realatity only 5 min. had gone by. The movie reel vision continued all night and feelings of death and then rebirth continued as well.
Coming out of the experience, it still took me awhile to be comfortable around people and to be able to consentrate on anything seriously.
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.


{% extends "base.html" %} {% block stuff %}
To get access to the resources on this site, you first need to log in with the account given to you by your manager.
{% else %}Genomics status displays information from multiple data sources.
Want to see something different here? Let us know on the suggestions page! We're currently collecting feedback on how the homepage should look..
Quota for project {{ quota.get('project_id') }} will be reduced to {{ quota.get('quota') }}Gb in {{ quota.get('days') }} days
{% end %} {% end %}| Project | Disk (Used / Quota) | Nobackup (Used / Quota) | CPU (Used / Quota) |
|---|---|---|---|
| {{ project_id }} |
{{ project.get('disk_usage') }} TB
{{ project.get('disk_limit') }} TB |
{{ project.get('nobackup_usage') }} TB{{ project.get('nobackup_limit') }} TB |
{{ project.get('cpu_usage') }} K{{ project.get('cpu_limit') }} K |
| Server | Instrument | Disk (Used / Quota) |
|---|---|---|
| {{ server }} | {{ status.get('instrument') }} |
{{ status.get('space_used') }}
{{ status.get('disk_size') }}
|
| Type | Data | Update Time |
|---|


{% block tableheader %}
Exits List | List of all Prison Exits
{% endblock %}
{% block tabledescription %}
This table showw all the petitioners who have exited the prison. You can search using any criteria
{% endblock %}| S/No | PM. Number | Name | Prison No | Prison | Nationality | Court Case No | Conviction Age | Current Age | Period Spent in Custody | Sentence | Court | Offense Age | Next of Kin | Next of Kin Relationship | Contact Person | Contact Person Tel | County | Sub County | Home Location | Nearest School | Home Chief | location of Offense | Date of Conviction | Date of Custody | Relief Sought | Offence | Particulars of Offense | Charged Alone for the Offence | Names of CO-Accussed | Knowledge of the Victim | Name of the Victim | Vitims Residence | Previous Convictions | Previous Petition | Date of Previous Petition | Reason for Denial of Petition | Reasons for Current Petition | Disciplinary action in prison | Details of Disciplinary Action | Special Condition | Details of Special Condition | Trustee | Date of Promotion to Trustee | Skills | Skills Details | Appealed | Appeal Case No | Appeal Outcome | Pending Court Matter | Pending Court Matter Explanation | Representative / Applicant | Petition Submitted By | Petition Submitted On | Exit Reason | Exit Date | Retention Period | Exit Added By | Exit Added On | Exit last Updated By | Exit last Updated On | |||||||||||
| {{ forloop.counter}} | PM/{{ object.petitioner.created.date.year }}/{{ object.petitioner.created.date.month }}/{{ object.petitioner.created.date.day }}/{{ object.id }} | {{object.petitioner.name|title}} | {{ object.petitioner.prisonno }} | {{ object.petitioner.prison|title }} | {{ object.petitioner.nationality|title }} | {{ object.petitioner.courtcaseno }} | {{ object.petitioner.ageatconviction }} Years | {{ today.year|sub:object.petitioner.dateofconviction.year|add:object.petitioner.ageatconviction }} Years | {{ today.year|sub:object.petitioner.dateofcustody.year }} Years | {% if object.petitioner.convictedforlife == True %}Life | {% else %}{{ object.petitioner.sentence }} Years | {% endif %}{{ object.petitioner.court|title }} | {{ object.petitioner.agewhenoffensewascommited }} | {{ object.petitioner.nextofkin|title }} | {{ object.petitioner.relationshipwithnextofkin |title}} | {{ object.petitioner.contactperson|title }} | {{ object.petitioner.telnoofcontactperson }} | {{ object.petitioner.county |title}} | {{ object.petitioner.subcounty|title }} | {{ object.petitioner.location |title}} | {{ object.petitioner.nearestschool|title }} | {{ object.petitioner.homechief|title }} | {{ object.petitioner.whereoffensewascommitted|lower|capfirst }} | {{ object.petitioner.dateofconviction }} | {{ object.petitioner.dateofcustody }} | {{ object.petitioner.reliefsought }} | {{ object.petitioner.offence|lower|capfirst }} | {{ object.petitioner.natureandparticularsofoffense }} | {% if object.petitioner.chargedalonefortheoffense == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.namesofcoaccused }} | {% if object.petitioner.knowledgeofthevictim == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.nameofvictim }} | {{ object.petitioner.areaofresidence }} | {{ object.petitioner.previousconvictions }} | {% if object.petitioner.previouspetition == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.dateofpreviouspetition }} | {{ object.petitioner.reasonofdenialofpreviouspetition }} | {{ object.petitioner.reasonforcurrentpetition }} | {% if object.petitioner.anydisplinaryactioninprison == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.detailsofdisplinaryactioninprison }} | {% if object.petitioner.anyspecialcondition == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.detailsofspecialcondition }} | {% if object.petitioner.areyouatrustee == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.dateofpromotiontotrustee }} | {% if object.petitioner.anyspecialattributesorskills == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.explanationofspecialattributesorskills }} | {% if object.petitioner.appealedagainsttheconviction == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.appealcaseno }} | {{ object.petitioner.appealoutcome }} | {% if object.petitioner.anypendingcourtmatter == True %}Yes | {% else %}No | {% endif %}{{ object.petitioner.explanationofpendingcourtmatter }} | {% if object.petitioner.isttheapplicantthepetitioner == True %}Petitioner | {% else %}{{ object.petitioner.nameofapplicant|title }} Relationship: {{ object.petitioner.relationshipofapplicantwithpetitioner|title }} Address: {{ object.petitioner.addressoftheapplicant }} Phone: {{ object.petitioner.telephonenumberoftheapplicant }} | {% endif %}{{ object.petitioner.added_by|title }} | {{ object.petitioner.created }} | {{ object.exitreason }} | {{ object.exitdate }} | {{ today.year|sub:object.created.year }} | {{ object.added_by }} | {{ object.created }} | {{ object.updated_by|title }} | {{ object.last_updated }} |


Fabrics
No Fabrics Configured.
| Status | Fabric | Active IPs | Active MACs | |
|---|---|---|---|---|
|
|
Currently Stale Endpoints
No currently stale endpoints detected.
Currently Off-Subnet Endpoints
No current off-subnet endpoint detected.


--- title: Typography keywords: type sidebar: left-navigation-sidebar toc: false permalink: fundamentals/type.html folder: fundamentals summary: ---
72
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
a b c d e f g h i j k l m n o p q r s t u v w x y z
1 2 3 4 5 6 7 8 9 0
‘ ? ’ “ ! ” ( % ) [ # ] { @ } / & \ < - + ÷ × = > ® © $ € £ ¥ ¢ : ; , . *
4. SAP 72 Light 30px | Line height 36px | Paragraph break 20px
Grumpy wizards make toxic brew for the evil Queen and Jack
3. SAP 72 Regular 24px | Line height 32px | Paragpraph break 16px
Grumpy wizards make toxic brew for the evil Queen and Jack
2. SAP 72 Regular 18px | Line height 24px | Paragraph break 12px
Grumpy wizards make toxic brew for the evil Queen and Jack
1. SAP 72 Regular 16px | Line height 20px | Paragraph break 12px
Grumpy wizards make toxic brew for the evil Queen and Jack
0. SAP 72 Regular 14px | Line height 20px | Paragraph break 12px
Grumpy wizards make toxic brew for the evil Queen and Jack
- 1. SAP 72 Regular 13px | Line height 16px | Paragraph break 8px
Grumpy wizards make toxic brew for the evil Queen and Jack
- 2. SAP 72 Regular 12px | Line height 16px | Paragraph break 8px
Grumpy wizards make toxic brew for the evil Queen and Jack
- 3. SAP 72 Regular 11px | Line height 16px | Paragraph break 8px
Grumpy wizards make toxic brew for the evil Queen and Jack


{% extends "transport_goods/layout.html" %} {% block page_title %} Who is licence for {% endblock %} {% block content %} {% include "includes/phase_banner_beta.html" %} {{formData | safe}} Who's this application for? Who's this application for? sole trader limited company partnership Limited Liability Partnership (LLP) other (for example public body, charity, university) {% endblock %}


Fast and safe loan provision
You will see for yourself that getting a loan is very simple: our services are available online in real time.
Other banks promise great service.
We are guarantee it.
How it works
Apply online. All you need to do is fill out a short form. You only need a few minutes to do this.
Get confirmation. The decision to grant a loan will be made immediately after you fill out the application.
Get the money. Funds will be credited to your card within a few minutes after processing the application.
Our advantages
Information about the company
You will see for yourself that getting a loan is very simple: our services are available online in real time.
We give the client comprehensive information about the full amount to be paid to repay the loan.
Working absolutely openly, without any hidden fees, we approach lending extremely responsibly and expect the same from our customers.
Your time is a highly valuable resource, and therefore we strive to make the process of providing a loan as simple as possible.
Ready to get started


Snapchat partners with Gucci for ‘Portal Lens’ that transports users to AR beach
The virtual beach has a holiday theme
by Aisha MalikSnapchat has partnered with luxury fashion brand Gucci for its latest AR portal lens that transports users to a virtual beach.
The virtual beach includes a number of different Gucci handbags and accessories and features a holiday theme. There is also a Christmas tree with presents in the middle of the beach.
You’ll see candy canes falling from palm trees and a snowman that is made out of sand. You can also interact with the different items on the virtual beach.
To access the lens, you just have to look for it in the Lens Carousel in the Snapchat app.
Toys R Us also recently partnered with Snapchat to allow users to interact with top toys for the holiday season in its holiday catalogue.
Via: Engadget


San Diego Zoo Safari Park has new arrivals: platypuses
by The Associated PressSAN DIEGO — The San Diego Zoo Safari Park has a pair of quirky new arrivals from Australia: platypuses.
The zoo on Friday publicly debuted an 8-year-old male named Birrarung and a 15-year-old female named Eve.
The pair were flown to the park late last month.
The zoo says it’s the first time in more than 50 years that platypuses — egg-laying mammals with furry bodies and duck-like bills — have been cared for outside of Australia.
Safari Park’s lead keeper, Lori Hieber, says the pair have settled into their new, specially built habitat. She says they swim in the pools, play in the waterfalls and hunt live crayfish.
An international conservation group lists the platypus as a “near threatened” species, mainly from habitat loss and the potential destruction from climate change.
The Associated Press


Charles Kuruvila
<EMAIL_ADDRESS>1-651-343-8297
Ten years of IT experience in analysis,design,development,testing,debugging and production support. Four years of entrepreneurial experience in real estate development.
Beach Villas Development
May 2012 - June,2016
Owner & Manager
- Project planning from initiation to property management.
- Identify resources including architect, structural consultant,site engineer & materials.
- Project financial management.
- Supervise project execution and monitoring for daily progress.
- Effective management of vendors and government officials.
- Client relationship building to identify and market to suitable rentals.
SEI Investments
March 2009 - May,2012
Technical Manager
- Analysis of existing functionality and providing code solutions based on new release requirements.
- Release specific job prioritization and co-ordination.
- Co-ordination with QA Team as well as business users.
- Troubleshooting and analysis of code related bugs/EOD job failures.
Westat,Inc
August 2008 - December,2008
Java Developer
- Design functional logic based on requirements/enhancements from each clinical trial group.
- Integrate Jmesa table rendering API for sorting, filtering, pagination, pdf/xls export, worksheet editing.
Bristol-Myers Squibb
February 2007 - August,2008
Technical Analyst
- Requirements gathering and functional specification design development for new enhancements.
- Offshore Development co-ordination, code review and production code/data change implementation.
- Tier 3 support for J2EE and Documentum based applications.
- Adhoc report development and implementation using BusinessObjects.
- Implement enhancements for custom vendor products (Thermo Scientific Nautilus LIMS & Lab Vantage Sapphire LIMS).
- Coordinate development, execution and approval of unit, system & UAT scripts.
Merrill Lynch
May 2004 - January,2007
Technical Analyst
- Requirements gathering and managing vendor issues related to user functionality.
- Develop use cases, sequence diagrams and class diagrams based on design meetings and detailed functional specification.
- Design web interfaces and logic using Struts ,JSP and Java Script.
- Application testing and deployment. Develop functional testing scripts using Rational Robot( SQA Basic).
- Develop performance testing scenarios and scripts using LoadRunner for major releases.
Pfizer Inc
January 2003 - May,2004
Analyst
- Develop functional specification based on user requirement documents.
- Develop PL/SQL scripts.
- Develop unit, functional and integration test scripts based on requirement documents.
- Functional acceptance testing to verify and meet 21 CFR Part 11 standards.
- Co-ordinate with developers and end users to track and analyse open QA issues.
Wells Fargo
August 2002 - December,2002
Analyst
- Develop automated test cases and test scripts using Rational Suite.
- Develop data pools, call-in scripts and user-defined functions in SQA basic.
- Create test suites and scenarios using Rational Test Manager.
- Use Rational Clear Quest for bug tracking and reporting.


Test API Server for the eat@home project
Use the following endpoints to access the fake data:
GET
Companies
Users
- Users: /api/users
- Specific User: /api/users/1
- Specific User's Ratings and Reviews: /api/this_user/reviews (logged in only)
- Specific User's Saves: /api/this_user/saves (logged in only)
Other
POST
Adding a User:
POST, with body:
- /api/users
- displayName (string)
- userName (string)
- email (string)
Adding a Save:
POST, with body (logged in only):
- /api/this_user/save
- company_id (integer)
Adding or Updating a Review:
POST, with body (note: content of 'review' should be text of the review):
- /api/review
- company_id (integer)
- review (string)
Adding or Updating a Rating:
POST, with body:
- /api/rating
- company_id (integer)
- rating (integer)
PUT
Updating a User:
PUT, with body:
- /api/users/:id
- displayName (string)
- userName (string)
- email (string)
DELETE
Deleting a User:
DELETE:
Deleting a Save:
DELETE:
Deleting a Review with Associated Rating:
DELETE:


Functions | |
| bStatus_t | GATT_InitClient (void) |
| Initialize the Generic Attribute Profile Client. | |
| void | GATT_RegisterForInd (uint8 taskId) |
| Register to receive incoming ATT Indications or Notifications of attribute values. | |
| bStatus_t | GATT_PrepareWriteReq (uint16 connHandle, attPrepareWriteReq_t *pReq, uint8 taskId) |
| The Prepare Write Request is used to request the server to prepare to write the value of an attribute. | |
| bStatus_t | GATT_ExecuteWriteReq (uint16 connHandle, attExecuteWriteReq_t *pReq, uint8 taskId) |
| The Execute Write Request is used to request the server to write or cancel the write of all the prepared values currently held in the prepare queue from this client. |
| bStatus_t GATT_ExecuteWriteReq | ( | uint16 | connHandle, | |
| attExecuteWriteReq_t * | pReq, | |||
| uint8 | taskId | |||
| ) |
The Execute Write Request is used to request the server to write or cancel the write of all the prepared values currently held in the prepare queue from this client.
Note: This function is needed only for GATT testing.
| connHandle | - connection to use | |
| pReq | - pointer to request to be sent | |
| taskId | - task to be notified of response |
| bStatus_t GATT_InitClient | ( | void | ) |
Initialize the Generic Attribute Profile Client.
| bStatus_t GATT_PrepareWriteReq | ( | uint16 | connHandle, | |
| attPrepareWriteReq_t * | pReq, | |||
| uint8 | taskId | |||
| ) |
The Prepare Write Request is used to request the server to prepare to write the value of an attribute.
Note: This function is needed only for GATT testing.
| connHandle | - connection to use | |
| pReq | - pointer to request to be sent | |
| taskId | - task to be notified of response |
| void GATT_RegisterForInd | ( | uint8 | taskId | ) |
Register to receive incoming ATT Indications or Notifications of attribute values.
| taskId | – task to forward indications or notifications to |


;
You'll answer the multiple choice 10 question quiz.
You'll have 10 seconds per
question.
For each correct answer, you'll move to the next question with no
penalties and gain 10 points.
For each incorrect question, you'll lose 5 seconds on the timer. Your goal is
to answer all 10 questions before time runs out.
At the end, you'll be able to enter your
name into the
Highscore board.
Have fun!


President Halimah to make Singapore's first state visit to Saudi Arabia
SINGAPORE: President Halimah Yacob is set to make Singapore's first state visit to Saudi Arabia next week, the Ministry of Foreign Affairs said in a press statement on Saturday (Nov 2).
Mdm Halimah will be in Saudi Arabia from Tuesday to Friday and call on King Salman bin Abdulaziz Al Saud, who will host a banquet in the President’s honour.
Mdm Halimah will separately meet with Crown Prince Mohammad bin Salman bin Abdulaziz Al Saud, who is also the Deputy Prime Minister and Minister of Defence of Saudi Arabia, as well as other senior Saudi leaders.
As part of her trip, Mdm Halimah will attend a reception with Singaporeans based in Saudi Arabia. She will also visit historical, cultural and religious sites in Riyadh, Jeddah, Makkah and Madinah.
Before arriving in Saudi Arabia, Mdm Halimah will make a state visit to Kuwait on Sunday and Monday. This will be Singapore's second state visit to Kuwait.
Mdm Halimah will call on Emir Sheikh Sabah Al Ahmad Al Jaber Al Sabah and have meetings with several senior Kuwaiti leaders. Emir Sheikh Sabah will also host a banquet for President.
During her trip, Mdm Halimah will also meet with Singaporean students studying in Kuwait and visit the Sheikh Abdullah Al Salem Cultural Centre.
Mdm Halimah will be accompanied by her husband Mr Mohamed Abdullah Alhabshee.
Her entourage will also include Mr Masagos Zulkifli, Minister for the Environment and Water Resources and Minister-in-charge of Muslim Affairs; Dr Koh Poh Koon, Senior Minister of State for Trade and Industry; Members of Parliament Ms Foo Mee Har and Ms Joan Pereira, as well as officials from the President’s Office, Ministry of Foreign Affairs, Ministry of Trade and Industry, and Ministry for the Environment and Water Resources.
A business delegation organised by the Singapore Business Federation and Enterprise Singapore will visit Saudi Arabia in conjunction with the state visit.
During President Halimah’s absence, Mr Eddie Teo, chairman of the Council of Presidential Advisers will exercise the function of the Office of the President.


This extension is active. Sponsored job listings are currently being blocked from indeed.com search results.
(Right click icon for options)


@* * Copyright 2023 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import models.RejectionDisplayModel @this( layout: Layout ) @(res: RejectionDisplayModel, showUserResearchPanel: Boolean)(implicit request: Request[_], messages: Messages) @layout( pageTitle = Messages("pla.resultRejection.title"), isUserResearchBannerVisible = showUserResearchPanel ) {
@Messages("resultCode."+res.notificationId+".heading")
@for(infoNum <- res.additionalInfo) {@Html(Messages("resultCode." + res.notificationId+ "." + infoNum))
}@Html(Messages("pla.resultRejection.viewDetails",controllers.routes.ReadProtectionsController.currentProtections))
@Messages("pla.resultSuccess.exitSurveyLinkText") @Messages("pla.resultSuccess.exitSurvey")


Learn all about Fake News Website
Home
Videos
History
Example
Contact
Contact Form
First Name
Last Name
Phone Number
Email
Address
Preferred Contact
Email
Phone
Your massage


| Class | Description |
|---|---|
| ClientFollowingAPI |
These endpoints allow you manage the artists, users and playlists that a Spotify user follows.
|
| ClientLibraryAPI |
Endpoints for retrieving information about, and managing, tracks that the current user has saved in their “Your Music” library.
|
| ClientPersonalizationAPI |
Endpoints for retrieving information about the user’s listening habits.
|
| ClientPlayerAPI |
These endpoints allow for viewing and controlling user playback. Please view the official documentation
for more information on how this works. This is in beta and is available for premium users only. Endpoints are not guaranteed to work
|
| ClientPlaylistAPI |
Endpoints for retrieving information about a user’s playlists and for managing a user’s playlists.
|
| ClientUserAPI |
Endpoints for retrieving information about a user’s profile.
|
| SpotifyTrackPositions |
Represents the positions inside a playlist's items list of where to locate the track
|
| Enum | Description |
|---|---|
| LibraryType |
Type of object in a user's Spotify library
|


Etsy Data Parsing
1. What is the average price of all items?
Answer 1 Goes Here
2. Show me an array of items that cost between $14.00 and $18.00 USD?
Answer 2 Goes Here
3. Which item has a "GBP" currency code? Display it's name and price.
Answer 3 Goes Here
4. Display a list of all items who are made of wood.
Answer 4 Goes Here
5. Which items are made of eight or more materials? Display the name, number of items and the items it is made of.
Answer 5 Goes Here
6. How many items were made by their sellers?
Answer 6 Goes Here


This tutorial focuses on the boto interface to the Simple Queue Service from Amazon Web Services. This tutorial assumes that you have boto already downloaded and installed.
The first step in accessing SQS is to create a connection to the service. The recommended method of doing this is as follows:
>>> import boto.sqs
>>> conn = boto.sqs.connect_to_region(
... "us-west-2",
... aws_access_key_id='<aws access key>',
... aws_secret_access_key='<aws secret key>')
At this point the variable conn will point to an SQSConnection object in the US-WEST-2 region. Bear in mind that just as any other AWS service, SQS is region-specific. In this example, the AWS access key and AWS secret key are passed in to the method explicitly. Alternatively, you can set the environment variables:
and then simply call:
>>> import boto.sqs
>>> conn = boto.sqs.connect_to_region("us-west-2")
In either case, conn will point to an SQSConnection object which we will use throughout the remainder of this tutorial.
Once you have a connection established with SQS, you will probably want to create a queue. In its simplest form, that can be accomplished as follows:
>>> q = conn.create_queue('myqueue')
The create_queue method will create (and return) the requested queue if it does not exist or will return the existing queue if it does. There is an optional parameter to create_queue called visibility_timeout. This basically controls how long a message will remain invisible to other queue readers once it has been read (see SQS documentation for more detailed explanation). If this is not explicitly specified the queue will be created with whatever default value SQS provides (currently 30 seconds). If you would like to specify another value, you could do so like this:
>>> q = conn.create_queue('myqueue', 120)
This would establish a default visibility timeout for this queue of 120 seconds. As you will see later on, this default value for the queue can also be overridden each time a message is read from the queue. If you want to check what the default visibility timeout is for a queue:
>>> q.get_timeout()
30
To retrieve a list of the queues for your account in the current region:
>>> conn.get_all_queues()
[
Queue(https://queue.amazonaws.com/411358162645/myqueue),
Queue(https://queue.amazonaws.com/411358162645/another_queue),
Queue(https://queue.amazonaws.com/411358162645/another_queue2)
]
This will leave you with a list of all of your boto.sqs.queue.Queue instances. Alternatively, if you wanted to only list the queues that started with 'another':
>>> conn.get_all_queues(prefix='another')
[
Queue(https://queue.amazonaws.com/411358162645/another_queue),
Queue(https://queue.amazonaws.com/411358162645/another_queue2)
]
If you wish to explicitly retrieve an existing queue and the name of the queue is known, you can retrieve the queue as follows:
>>> my_queue = conn.get_queue('myqueue')
Queue(https://queue.amazonaws.com/411358162645/myqueue)
This leaves you with a single boto.sqs.queue.Queue, which abstracts the SQS Queue named ‘myqueue’.
Once you have a queue setup, presumably you will want to write some messages to it. SQS doesn’t care what kind of information you store in your messages or what format you use to store it. As long as the amount of data per message is less than or equal to 256Kb, SQS won’t complain.
So, first we need to create a Message object:
>>> from boto.sqs.message import Message
>>> m = Message()
>>> m.set_body('This is my first message.')
>>> q.write(m)
The write method will return the Message object. The id and md5 attribute of the Message object will be updated with the values of the message that was written to the queue.
Arbitrary message attributes can be defined by setting a simple dictionary of values on the message object:
>>> m = Message()
>>> m.message_attributes = {
... "name1": {
... "data_type": "String",
... "string_value": "I am a string"
... },
... "name2": {
... "data_type": "Number",
... "string_value": "12"
... }
... }
Note that by default, these arbitrary attributes are not returned when you request messages from a queue. Instead, you must request them via the message_attributes parameter (see below).
If the message cannot be written an SQSError exception will be raised.
The technique above will work only if you use boto’s default Message payload format; however, you may have a lot of specific requirements around the format of the message data. For example, you may want to store one big string or you might want to store something that looks more like RFC822 messages or you might want to store a binary payload such as pickled Python objects.
The way boto deals with this issue is to define a simple Message object that treats the message data as one big string which you can set and get. If that Message object meets your needs, you’re good to go. However, if you need to incorporate different behavior in your message or handle different types of data you can create your own Message class. You just need to register that class with the boto queue object so that it knows that, when you read a message from the queue, it should create one of your message objects rather than the default boto Message object. To register your message class, you would:
>>> import MyMessage
>>> q.set_message_class(MyMessage)
>>> m = MyMessage()
>>> m.set_body('This is my first message.')
>>> q.write(m)
where MyMessage is the class definition for your message class. Your message class should subclass the boto Message because there is a small bit of Python magic happening in the __setattr__ method of the boto Message class.
So, now we have a message in our queue. How would we go about reading it? Here’s one way:
>>> rs = q.get_messages()
>>> len(rs)
1
>>> m = rs[0]
>>> m.get_body()
u'This is my first message'
The get_messages method also returns a ResultSet object as described above. In addition to the special attributes that we already talked about the ResultSet object also contains any results returned by the request. To get at the results you can treat the ResultSet as a sequence object (e.g. a list). We can check the length (how many results) and access particular items within the list using the slice notation familiar to Python programmers.
At this point, we have read the message from the queue and SQS will make sure that this message remains invisible to other readers of the queue until the visibility timeout period for the queue expires. If you delete the message before the timeout period expires then no one else will ever see the message again. However, if you don’t delete it (maybe because your reader crashed or failed in some way, for example) it will magically reappear in my queue for someone else to read. If you aren’t happy with the default visibility timeout defined for the queue, you can override it when you read a message:
>>> q.get_messages(visibility_timeout=60)
This means that regardless of what the default visibility timeout is for the queue, this message will remain invisible to other readers for 60 seconds.
The get_messages method can also return more than a single message. By passing a num_messages parameter (defaults to 1) you can control the maximum number of messages that will be returned by the method. To show this feature off, first let’s load up a few more messages.
>>> for i in range(1, 11):
... m = Message()
... m.set_body('This is message %d' % i)
... q.write(m)
...
>>> rs = q.get_messages(10)
>>> len(rs)
10
Don’t be alarmed if the length of the result set returned by the get_messages call is less than 10. Sometimes it takes some time for new messages to become visible in the queue. Give it a minute or two and they will all show up.
If you want a slightly simpler way to read messages from a queue, you can use the read method. It will either return the message read or it will return None if no messages were available. You can also pass a visibility_timeout parameter to read, if you desire:
>>> m = q.read(60)
>>> m.get_body()
u'This is my first message'
By default, no arbitrary message attributes are returned when requesting messages. You can change this behavior by specifying the names of attributes you wish to have returned:
>>> rs = queue.get_messages(message_attributes=['name1', 'name2'])
>>> print rs[0].message_attributes['name1']['string_value']
‘I am a string’
A special value of All or .* may be passed to return all available message attributes.
As stated above, messages are never deleted by the queue unless explicitly told to do so. To remove a message from a queue:
>>> q.delete_message(m)
[]
If I want to delete the entire queue, I would use:
>>> conn.delete_queue(q)
This will delete the queue, even if there are still messages within the queue.
The above tutorial covers the basic operations of creating queues, writing messages, reading messages, deleting messages, and deleting queues. There are a few utility methods in boto that might be useful as well. For example, to count the number of messages in a queue:
>>> q.count()
10
This can be handy but this command as well as the other two utility methods I’ll describe in a minute are inefficient and should be used with caution on queues with lots of messages (e.g. many hundreds or more). Similarly, you can clear (delete) all messages in a queue with:
>>> q.clear()
Be REAL careful with that one! Finally, if you want to dump all of the messages in a queue to a local file:
>>> q.dump('messages.txt', sep='\n------------------\n')
This will read all of the messages in the queue and write the bodies of each of the messages to the file messages.txt. The optional sep argument is a separator that will be printed between each message body in the file.


Home
About
Stories
FAQs
Contacts
Let us know you..
We will try our best to know your tastes n preferences through a few questions. Please try to be as honest as possible.


Upload LR Copy
PJV Year
2014 - 2015
2015 - 2016
2016 - 2017
PJV Number
Select Transport
Select Transport
KRS -TRANSPORT
GATI
KPN
TPC
LR Number
Upload LR image
Upload
Take Photo
Select date of booking
No of bundles


DataInputStream
You may have noticed the class ObjectOutputStream
in the previous diagram.
Streams of that class write objects to a
destination such as a disk file.
ObjectInputStream
streams read objects from
a source.
So far in our programs objects have existed only in
main memory and lasted only as long the program that
created them was running.
When the program stopped running (or earlier),
they were garbage collected.
With an ObjectOutputStream
an object can
be written to disk and will remain there even after
the program stops.
This is the topic of object serialization,
an advanced topic not yet covered in these notes.


The first thing that should be jumping at when reading the prompt for the problem is the fact that the rows and columns of the matrix are already sorted. Of course, we could iterate through every element in the matrix one by one, going from left to right and then top to bottom, checking every element to see if we’ve found the matching element. In the worst case, this would yield us a runtime of O(n * m) where n is the number of rows and m is the number of columns. If we had a square matrix where the number of rows and columns is the same, this would be the same as O(n^2). That solution would look something like this:
def search_in_sorted_matrix(matrix, target):
# iterate along each row
for row in range(len(matrix)):
# iterate along each column
for col in range(len(matrix[0])):
if matrix[row][col] == target:
return [row, col]
# we iterated through the whole matrix and didn't find the target
return (-1, -1)
If our matrix was unsorted, this would most likely be the best we could do, since we don’t know anything about the order of the elements in an unsorted matrix. However, in this case, since the matrix is sorted, we can take advantage of this fact to achieve a more performant algorithm.
When we’re handed a problem where the data is already sorted, one of the first questions we should be asking is if we can utilize binary search in some way for this problem. The binary search algorithm is typically used on already-sorted or almost-sorted one-dimensional arrays. Can we utilize the same idea to search through a sorted matrix?
To reiterate on the binary search algorithm, we start off by calculating the midpoint of the array we’re searching through, then we check to see if the midpoint element of the array is less than, equal to, or greater than our target element. If the midpoint element is equal to the target element, then great, we’re done! If the midpoint element is less than the target element, then we know, by virtue of the fact that the data is already sorted, that it must exist in the right half of the sorted array (if it exists in the array in the first place). Similarly, if the midpoint element is greater than the target element, then we know that the target element must exist in the left half of the sorted array (again, if it exists in the array in the first place).
So how can we apply this idea to a sorted matrix? Let’s consider an example. Let’s say we have the following sorted matrix:
[
[1, 4, 7, 12, 15, 997, 999],
[2, 5, 19, 32, 35, 1001, 1007],
[4, 8, 24, 34, 36, 1008, 1015],
[40, 41, 42, 44, 45, 1018, 1020],
[98, 99, 101, 104, 190, 1021, 1025],
]
How would we go about trying to find 41 in this sorted matrix? The binary search algorithm prescribes first finding the midpoint, so let’s try that with our matrix. In this example, the midpoint is the element in the middle column and middle row, which in this case is the element located at row 2 column 3, or 34. 41 is greater than 34. What does that tell us? Well, it tells us that if 41 exists in the matrix, it’s either in a column to the right of column 3, or it’s in a row lower than row 2. But how do we know in which dimension to continue searching from this point, rows or columns?
With the information we currently have, it’s not really clear. In this case, perhaps starting at the midpoint of the matrix doesn’t work out so well as starting at the midpoint in a one-dimensional array. So if we’re not going to start in the midpoint, where should we start instead?
What if we tried starting in one of the corners? Let’s try the northwest corner. The element there, 1, is less than 41. Ok, what does that tell us? Well, not much, since 41 could still be to the right of 1 or underneath it, since it’s larger. So that was even less helpful than starting at the midpoint.
Ok, let’s try the northeast corner. The element there, 999, is larger than 41, is located at coordinates [0, 6], row 0 and column 6. Now, we know that 41 must be in a column to the right of column 6, since every element directly underneath 999 is greater than it. Ok, let’s keep going. If we shift over one column to the left, we’re now at coordinates [0, 5], which is where 997 is located. Again, 997 is larger than 41, so we can continue shifting to the left since we know that 41 can’t be located directly underneath 997; all of those elements are larger than 997.
Shifting over to the left one more time, we end up at coordinates [0, 4], where 15 is located. At this point, 15 is less than 41, so it could certainly be directly underneath 15 in column 4. But now we know that 41 cannot be in this row, since it would have been between elements 15 and 997. Thus, we can move on to the next row in the matrix. This takes us to coordinates [1, 4], where 35 is located. 35 is less than 41, so 41 cannot exist in this row either. We keep moving down to [2, 4]. Again, 36 is less than 41, so it can’t exist in this row. Moving down one more time to [3, 4], we land on 45. Since 45 is greater than 41, it can exist in this row.
Since 45 is greater than 41, we move leftward to [3, 3]. 44 is greater than 41, so we continue moving leftward, where we get to [3, 2] and see that we need to move leftward again. Finally, at [3, 1], we find 41.
So starting in the northeast corner worked because it gave us more information as to which direction we could be moving as we searched through the matrix. This same idea works just as well if we start in the southwest corner, but it would not work if we started in the southeast corner for the same reasons it didn’t work when we tried starting in the northwest corner. We need to start at the large end of one of the dimensions and the small end of the other. It doesn’t work when we start at the small end of both dimensions or the large end of both dimensions.
With that being said, does this strategy work when we try searching for an element that isn’t in the matrix? Let’s see what happens when we try searching for 1016 in the matrix. Starting at the northeast corner again, we’d see that 999 is less than 1016, so we’d move one row down to [1, 6]. From there, we’d move down again to [2, 6], then down again to [3, 6]. We’d start moving leftward from there until we hit [3, 4], where we’d noticed that we’d have skipped over 1016 if it existed in the matrix. Therefore, 1016 can’t exist in the matrix and we’d return [-1, -1].
Let’s the evaluate the time complexity for this algorithm. In the worst case, the element we’re looking for would be located in the opposite corner as the one we started at. In that case, how many elements would we need to check? In that case, we’d have to traverse both the width and the height of the entire matrix to get to the opposite corner. So the total number of elements we’d end up inspecting in that situation is equal to the number of columns plus the number of rows. Thus, the runtime of this algorithm will be O(n + m) where n is the number of rows and m is the number of columns. This is certainly a much better runtime than O(n * m). Can we do even better? Probably not, since doing any better than this would entail not checking every row and column at least once in the worst case, and we don’t have enough information to be able to make that assumption.
For the space complexity of this algorithm, we don’t need to allocate memory for any data structures or anything like that. All we need to keep track of is the current coordinates of where we are in the matrix as we’re traversing it, so the space complexity of this algorithm will be O(1).
Now that we’ve sketched out the idea and determined that it’s the best we can do, let’s put it down in code:
def search_in_sorted_matrix(matrix, target):
# initialize variables to keep track of where we are in the matrix
# we want to start in the northeast (or southwest) corner
# which has the coordinates [0, len(matrix[0])-1]
row = 0
col = len(matrix[0]) - 1
# we'll traverse so long as the row index < len(matrix) and the
# column index >= 0
while row < len(matrix) and col >= 0:
# check if the value at these coordinates is > target
if matrix[row][col] > target:
# if it is, shift one column to the left
col -= 1
# check if the value at these coordinates is < target
elif matrix[row][col] < target:
# if it is, shift down one row
row += 1
# otherwise, the value at these coordinates is == target
else:
# we've found the element, return its coordinates
return (row, col)
# we've traversed the entire matrix and didn't find the matching element
return (-1, -1)


Selectors
Get... Parent element Children collection Collection by class Element by Id Collection by class & attribute
Events
HTML Document has been loaded Cursor Click Double click Cursor movement Mouse over Keyboard Keypress Images An image is loaded An image fails to load Data Form is submitted Input value change (select, checkbox, input)
Function
HTML Elements Create HTML element Remove HTML element Clone HTML element DOM Manipulation Append HTML element Prepend HTML element Add after another Add before another Classes Add class to an HTML element Remove class to an HTML element Toggle class to an HTML element Attributes Add a disabled attribute Remove a disabled attribute Set 'data-src' attribute Remove 'data-src' attribute Change href attribute Element display Hide HTML element on click Show HTML element on click Fade in an HTML element (jQuery) Fade out an HTML element (jQuery) Delayed animate after page load Functions Iterate collection of elements Get selected options of select Get input value Remove multiple items of selector


So what exactly did you learn in the previous exercises? You selected a subset from a data frame (planets_df
) based on whether or not a certain condition was true (rings or no rings), and you managed to pull out all relevant data. Pretty awesome! By now, NASA is probably already flirting with your CV ;-).
Now, let us move up one level and use the function subset()
. You should see the subset()
function as a short-cut to do exactly the same as what you did in the previous exercises.
subset(my_df, subset = some_condition)
The first argument of subset()
specifies the data set for which you want a subset. By adding the second argument, you give R the necessary information and conditions to select the correct subset.
The code below will give the exact same result as you got in the previous exercise, but this time, you didn't need the rings_vector
!
subset(planets_df, subset = rings)
Use subset()
on planets_df
to select planets that have a diameter smaller than Earth. Because the diameter
variable is a relative measure of the planet's diameter w.r.t that of planet Earth, your condition is diameter < 1
.
load(url("http://s3.amazonaws.com/assets.datacamp.com/course/intro_to_r/planets.RData"))
# planets_df is pre-loaded in your workspace
# Select planets with diameter < 1
# planets_df is pre-loaded in your workspace
# Select planets with diameter < 1
subset(planets_df, subset = diameter < 1)
msg = "Do not remove or overwrite the `planets_df` data frame!"
test_object("planets_df", undefined_msg = msg, incorrect_msg = msg)
test_correct({
test_output_contains("subset(planets_df, subset = diameter < 1)", incorrect_msg = "Have you correctly specified the `subset = ...` part inside `subset()`. The condition in this case is `diameter < 1`. Simply print out the result.")
}, {
test_function("subset", args = "x",
not_called_msg = "Make sure to use the `subset()` function to perform the selection!",
incorrect_msg = "The first argument you pass to `subset()` should be `planets_df`.")
})
success_msg("Great! Not only is the `subset()` function more concise, it is probably also more understandable for people who read your code. Continue to the next exercise.");
subset(planets_df, subset = ...)
almost solves it; can you fill in the ...
?


<DEFAULT> SKIP : { " " | "\t" | "\n" | "\r" | "\f" } |
<DEFAULT> SPECIAL : { <SINGLE_LINE_COMMENT: "//" (~["\n","\r"])* ("\n" | "\r" | "\r\n")> | <FORMAL_COMMENT: "/**" (~["*"])* "*" ("*" | ~["*","/"] (~["*"])* "*")* "/"> } |
<DEFAULT> TOKEN : { <LPAREN: "("> | <RPAREN: ")"> | <LSQPAREN: "["> | <RSQPAREN: "]"> | <LBRACE: "{"> | <RBRACE: "}"> | <SEMICOLON: ";"> | <DOT: "."> | <ASSIGN: "="> | <LT: "<"> | <PLUS: "+"> | <MINUS: "-"> | <AND: "&"> | <NOT: "!"> | <BOOLEAN: "boolean"> | <CLASS: "class"> | <INTERFACE: "interface"> | <ELSE: "else"> | <EXTENDS: "extends"> | <FALSE: "false"> | <IF: "if"> | <WHILE: "while"> | <FOR: "for"> | <INTEGER: "int"> | <LENGTH: "length"> | <MAIN: "main"> | <NEW: "new"> | <PUBLIC: "public"> | <RETURN: "return"> | <STATIC: "static"> | <STRING: "String"> | <THIS: "this"> | <TRUE: "true"> | <PRINT: "System.out.println"> | <SCOMMENT1: "/*"> | <SCOMMENT2: "*/"> | <CONSTANTQUERY: "PRINTCONSTANTS"> | <VOID: "void"> } |
<DEFAULT> TOKEN : { <INTEGER_LITERAL: ["1"-"9"] (["0"-"9"])* | "0"> } |
<DEFAULT> TOKEN : { <IDENTIFIER: <LETTER> (<LETTER> | <DIGIT>)*> | <#LETTER: ["$","A"-"Z","_","a"-"z","\u00c0"-"\u00d6","\u00d8"-"\u00f6","\u00f8"-"\u00ff","\u0100"-"\u1fff","\u3040"-"\u318f","\u3300"-"\u337f","\u3400"-"\u3d2d","\u4e00"-"\u9fff","\uf900"-"\ufaff"]> | <#DIGIT: ["0"-"9","\u0660"-"\u0669","\u06f0"-"\u06f9","\u0966"-"\u096f","\u09e6"-"\u09ef","\u0a66"-"\u0a6f","\u0ae6"-"\u0aef","\u0b66"-"\u0b6f","\u0be7"-"\u0bef","\u0c66"-"\u0c6f","\u0ce6"-"\u0cef","\u0d66"-"\u0d6f","\u0e50"-"\u0e59","\u0ed0"-"\u0ed9","\u1040"-"\u1049"]> } |


D N S Machining Services are a family owned machining company based in Coventry. With 40+ years of industry experience from our Director, we continue to provide excellent machining services with fast turnaround. D N S have experience within the Aerospace industry as well as machine tool fitting and swift turnaround in breakdown work.
On a daily basis you will find our workshop completing work around precision components and on hand to perform any urgent breakdown work required i.e. broken shafts (repair/manufacture new ones) and bearing housings.
With 40+ years of industry experience from our Director, we continue to provide excellent machining services with fast turnaround. D N S have experience within the Aerospace industry as well as machine tool fitting.
Recently, we have invested in new CNC machinery the past year including the new Doosan DNM5700 vertical machining centre and Doosan LYNX2100 to expand capabilities and to increase our capacity. In these 9 years we have worked with Mills CNC, Sandvik Hard Materials, Alphateq and manufactured components to drawings.
On a daily basis you will find our workshop completing work around precision components and on hand to perform any urgent breakdown work required i.e. broken shafts (repair/manufacture new ones) and bearing housings.
Unit 2, 118 - 132 Red Lane, Coventry, CV6 5EQ
<EMAIL_ADDRESS>+91 976885083


{%extends 'base.html' %} {% load static%} {% block styles%} {{block.super}} {% endblock %} {% block content %}
Neighbourhood name: {{user.join.hood.name}}
Location: {{user.join.hood.location}}
{% if biz %}Your businesses:
| Name | Description | |
|---|---|---|
| {{biz.name}} | {{biz.description}} | {{biz.email}} |
You haven't joined a neighbourhood yet
{% endif %}


--- layout: post title: 7 Virtues for Software Developers date: 2006-08-22 00:00:00 category: software-development ---
K. Scott Allen : 7 Virtues for Software Developers.


Yanwei Fu, Yongxing Yang, Timothy M. Hospedales, Tao Xiang and Shaogang Gong
School of EECS, Queen Mary University of London, UK
{y.fu,yongxin.yang,t.hospedales, t.xiang<EMAIL_ADDRESS>Download-readme
data for several dataset used in our papers
We are using all wikipedia articles to train the google word2vec recurrent neural network model
and generate the semantic word vector dictionary; and we will release it to the community.
bib: @INPROCEEDINGS{embedding2014ECCV,
author = { Yanwei Fu and Yongxing Yang and Timothy M. Hospedales and Tao Xiang and Shaogang Gong},
title = {Transductive Multi-label Zero-Shot Learning},
booktitle ={BMVC},
year = {2014}
}
[2] Fu, Yanwei; Hospedales, T.; Xiang, T.; Fu, Z.; Gong, S: Transductive Multi-view Embedding for Zero-Shot Recognition and Annotation, (ECCV 2014). Paper
bib: @INPROCEEDINGS{embedding2014ECCV,
author = { Yanwei Fu and Timothy M. Hospedales and Tao Xiang and Zhenyong Fu and Shaogang Gong},
title = {Transductive Multi-view Embedding for Zero-Shot Recognition and Annotation},
booktitle = {ECCV},
year = {2014}
}
bib: @INPROCEEDINGS{embedding2014ECCV,
author = { Yanwei Fu and Timothy M. Hospedales and Tao Xiang and Shaogang Gong},
title = {Transductive multi-view zero-shot recognition and annotation},
booktitle = {submitted to TPAMI},
year = {2014}
}


Random Number Generator
This is a simple random number generator that I made for fun.
From:
To:
Go
{% if result %}
Result
{{result}}
{% endif %}
By
Vincent Pranata


On opera 17 (build 17.0.1241.45) the instruction bar (.bblog-emblem-info) interferes with the editor cursor.
The handles and cursor don't align properly. You need to be about the amount of the height of the instruction bar above the visible handle for it to activate. When the bar is hidden in CSS the problem is gone.
BrainFooLong
Administrator
Hmm, not be able to reproduce the problem.
All handlers did work perfectly for me on the same opera built.
Tried also without BBLog and also working as expected.
Can you maybe explain what handler you mean exactly (Emblem add, emblem select, emblem rotate, etc...)?
Post edited 1 x times, last by
pleomin
Topicstarter
pleomin
I've added an image which should illustrate it more clearly
cursor.jpg
As you can see the cursor to rotate, move or scale the layer is higher than it should be.
I will double check if any Opera extension causes this.
edit: Shows the same behavior with all extensions disabled, aswell on a clean install of the latest developer build of Opera. It works fine with "Emblem Editor Improvements" disabled.


The following example is a basic backbone form that gives an name input, gender input, and submit button.
Although this demo works fine, notice that there is a strange behavior on submission. When we press submit, the render method is called. When we re-render, the input elements all lose their state! This goes against the Torso design philosophy of state-free DOM. If the submit button were to run validation before submission and provide user feedback, the render call would blow away all inputs. In short, we must find a way to save the form state.


Weather Dashboard
Saved Searches:
Current Weather Details:
Wind Speed:
Humidity:
Temperature:
UV Index:
Five Day Forecast:
Day 1:
Temperature:
Humidity:
Day 2:
Temperature:
Humidity:
Day 3:
Temperature:
Humidity:
Day 4:
Temperature:
Humidity:
Day 5:
Temperature:
Humidity:


Resource interfaces. Internal use only, but is an interface point between i.e. the faces handling piece and the resource handling. Bundles can indicate resource loading by providing a specific header in the bundle manifest.


What is this?
It's my personal project:
2D Orthogonal Range Tree Visualization.
- The [Input Points and Queries] Canvas: is the canvas
which holds the points that we are working with.
- The [2D Range Tree] Canvas: displays the orthogonal
range tree generataed from the points in the [Input Points and
Queries] Canvas.
How to use it?
1. point inialization:
- You can enter your own points by clicking on the [Input Points and
Queries] Canvas.
- Or you can initialize them randomly by clicking the [Randomized 8
points Points] button. This button can be pressed twice at most (16
points)
2. range inialization:
- You can enter your own range using the four input boxes underneath
the [Input Points and Queries] Canvas.
- Or you can initialize them randomly by clicking the [Randomized
Query] button.
3. range tree creation:
- Once you create your points, you can click the [Build Range Tree]
button
4. search:
- Once you built your range tree, you can click the [Find Points in
Range] button
5. testing:
- Open the console, and use the multitest(#iterations, #points) to
test. It would generates random points and compare the result given
by the range tree with a brute force result.
Input Points and Queries
2D Range Tree
Terminologies
pink nodes:
visited
S:
Split nodes
WR & orange nodes:
Within Range, aka, points that satisfied the constraints
RS & lightgreen nodes:
Report entire Subtree as found points
lightblue nodes:
Where we need to do a search in the assoc structure only, but not
its children


Build Better Gulpfiles
asset-builder assembles and orchestrates your dependencies so you can run them through your asset pipeline. Easily create gulp tasks you can share between projects by separating config from code.
Automate Repetitive Glob Building.
asset-builder allows you to declare the output of your Gulpfile in an external manifest file.
manifest.json
{ "dependencies": { "app.js": { "files": [ "scripts/services/**/*.js", "scripts/controllers.js", "scripts/main.js" ], "main": true } } }
So you can stop doing this...
gulpfile.js
gulp.src([ 'bower_components/jquery/jquery.js', 'bower_components/bootstrap/component.js', 'scripts/services/**/*.js', 'scripts/controllers.js', 'scripts/main.js' ]) .pipe(concat('app.js')) .pipe(minify()) .pipe(gulp.dest('dist'));
...and start doing this
gulpfile.js
gulp.src(js.globs) .pipe(concat(js.name)) .pipe(minify()) .pipe(gulp.dest(manifest.paths.dist));
Automate Repetitive Glob Building.
Install
npm install asset-builder --save-dev
Use
var manifest = require('asset-builder')('./assets/manifest.json');


U.S. MARSHALS Reviewed by Jamie Peck
As the unstoppable, cocksure Chief Deputy U.S. Marshal Sam Gerard, Tommy Lee Jones reprises the his role from the first movie. This time around, Gerard and his team of tagalongs (including Joe Pantoliano and Latanya Richardson) are on the trail of a completely different fugitive -- a mysterious ex-Marine Special Forces and -CIA operative named Sheridan (Wesley Snipes), on the run after somebody frames him for the murders of two Secret Service attaches who were trying to crack a Chinese spy ring within the United Nations. Also on Gerard's side as he trails Sheridan from the muddy banks of the Ohio River to the chaotic streets of New York City is smug, smart Federal Agent John Royce (Robert Downey, Jr.). Gerard doesn't completely trust Royce, and possibly for good reason.
Many of "U.S. Marshals"' problems lie within the character of Sheridan -- even Snipes' noble demeanor can't hide the fact that he's horribly developed. We cared about Harrison Ford's "Fugitive" everyman because we believed in and identified with him. Ford had to use instinct, medical know-how and even blind luck to uncover the conspiracy against him; he was, quite simply, no action hero.  It's just no fun rooting for him. That gives a lot of the later action sequences an empty, lifeless feel, however well-staged they may be. Compared to "The Fugitive"'s richly satisfying four-course dinner, "U.S. Marshals" is half-eaten, day-old, microwaved leftovers.
At least Jones' Gerard is still fascinating. His presence deems the film watchable even in its many weak passages. Take, for example, the completely unnecessary opening sequence that only serves as a way to get cat and mouse acquainted down the road. Here, Gerard and company, hidden under various disguises, stakeout the home of a wanted criminal who, when caught, will be put on the same prisoner transport plane as Sheridan. It's useless stuff that could have made the two-and-a-quarter hours "Marshals" tighter by being cut, but Jones is a droll delight to watch in any situation. And that prisoner transport plane ride, by the way, is the movie's best visceral asset. Director Stuart Baird knows a thing or two about in-flight tension -- his 1996 thriller "Executive Decision" was an unjustly underrated sweat-popper.
One of the smaller crimes "U.S. Marshals" commits is casting luminous French actress Irene Jacob ("Red") in a throwaway role as Sheridan's Starbucks waitress girlfriend, but misusing time and talent is something the movie does best. To its middling credit, "U.S. Marshals" provides a few decent bangs for the buck, an occasionally witty one-liner and a chance for Jones to strut his Oscar-winning stuff all over again, but that's about it. A lot of the film is spent watching boring people do boring things -- it's too dull to be much fun. Don't go expecting another "Fugitive" or you'll find that "U.S. Marshals" is decidedly unarresting.
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


Welcome to my website. I hope you can find useful and interesting information about my research work. I am a PhD student in the team Broadband Communication and Distributed Systems of the Universitat de Girona in Catalonia, Spain. Currently, I am working under the guidance of Dr. Pere Vilà and Dr. Lluís Fàbrega.


D2 Notes
| Aux Notes | |
|---|---|
| Day | d2 |
| External Links | |
| Other | |
| Tags |
Overview
Let's look at a basic example of routing in action.
First, to make our Express application respond
to GET
requests on different URLs, add the following
endpoints:
// this request handler executes when making a GET request to /about
server.get('/about', (req, res) => {
res.status(200).send('
About Us
');
});
// this request handler executes when making a GET request to /contact
server.get('/contact', (req, res) => {
res.status(200).send('
Contact Form
');
});
Two things to note:
- we are using the same HTTP Method on both endpoints, but express looks at the URL and executes the corresponding request handler.
- we can return a string with valid HTML!
Open a browser and navigate to
the /about
and /contact
routes. The
appropriate route handler will execute.
Follow Along
Please follow along as we write endpoints that execute different request handlers on the same URL by changing the HTTP method.
Let's start by adding the following code after
the GET
endpoint to /hobbits
:
// this request handler executes when making a POST request to /hobbits
server.post('/hobbits', (req, res) => {
res.status(201).json({ url: '/hobbits', operation: 'POST' });
});
Note that we return HTTP status code 201 (created) for
successful POST
operations.
Next, we need to add an endpoint for PUT
requests to the
same URL.
// this request handler executes when making a PUT request to /hobbits
server.put('/hobbits', (req, res) => {
res.status(200).json({ url: '/hobbits', operation: 'PUT' });
});
For successful PUT
operations, we use HTTP Status Code
200 (OK).
Finally, let's write an endpoint to
handle DELETE
requests.
// this request handler executes when making a DELETE request to /hobbits
server.delete('/hobbits', (req, res) => {
res.status(204);
});
We are returning HTTP Status Code 204 (No Content). Suppose you are returning any data to the client, perhaps the removed resource, on successful deletes. In that case, you'd change that to be 200 instead.
You may have noticed that we are not reading any data from the
request, as that is something we'll learn later in the module. We
are about to learn how to use a tool called Postman
to
test our POST
, PUT
,
and DELETE
endpoints.
Overview
Reading and Using Route Parameters
Let's revisit our DELETE
endpoint.
server.delete('/hobbits', (req, res) => {
res.status(204);
});
How does the client let the API know which hobbit should be deleted or
updated? One way, the one we'll use, is through route parameters
. Let's add support for route parameters to
our DELETE
endpoint.
We define route parameters by adding it to the URL with a colon
(:
) in front of it. Express adds it to
the .params
property part of the request object.
Let's see it in action:
server.delete('/hobbits/:id', (req, res) => {
const id = req.params.id;
// or we could destructure it like so: const { id } = req.params;
res.status(200).json({
url: `/hobbits/${id}`,
operation: `DELETE for hobbit with id ${id}`,
});
});
This route handler will execute every DELETE
for a URL
that begins with /hobbits/
followed by any value.
So, DELETE
requests
to /hobbits/123
and /hobbits/frodo
will both
trigger this request handler. The value passed
after /hobbits/
will end up as
the id
property on req.params
.
The value for a route parameter will always be string
,
even if the value passed is numeric. When
hitting /hobbits/123
in our example, the type
of req.params.id
will be string
.
Express routing has support for multiple route parameters. For
example, defining a route URL that
reads /hobbits/:id/friends/:friendId
, will add properties
for id
and friendId
to req.params
.
Using the Query String
The query string is another strategy using the URL to pass information
from clients to the server. The query string is structured as a set of
key/value pairs. Each pair takes the form of key=value
,
and pairs are separated by an &
. To mark the
beginning of the query string, we add ?
and the end of
the URL, followed by the set of key/value pairs.
An example of a query string would
be: https://www.google.com/search?q=lambda&tbo=1
. The
query string portion is ?q=lambda&tbo=1
and the
key/value pairs are q=lambda
and tbo=1
.
Let's add sorting capabilities to our API. We'll provide a
way for clients to hit our /hobbits
and pass the field
they want to use to sort the responses, and our API will sort the data
by that field in ascending order.
Here's the new code for the GET /hobbits
endpoint:
server.get('/hobbits', (req, res) => {
// query string parameters get added to req.query
const sortField = req.query.sortby || 'id';
const hobbits = [
{
id: 1,
name: 'Samwise Gamgee',
},
{
id: 2,
name: 'Frodo Baggins',
},
];
// apply the sorting
const response = hobbits.sort(
(a, b) => (a[sortField] < b[sortField] ? -1 : 1)
);
res.status(200).json(response);
});
Visit localhost:8000/hobbits?sortby=name
, and the list
should be sorted by name
.
Visit localhost:8000/hobbits?sortby=id
, and the list
should now be sorted by id
. If
no sortby
parameter is provided, it should default to
sorting by id
.
To read values from the query string, we use
the req.query
object added by Express. There will be a
key and a value in the req.query
object for each
key/value pair found in the query string.
The parameter's value will be of type array
if more
than one value is passed for the same key and string
when
only one value is passed. For example, in the query
string ?id=123
, req.query.id
will be a
string, but for ?id=123&id=234
, it will be an array.
Another gotcha is that the names of query string parameters are case
sensitive, sortby
and sortBy
are two
different parameters.
The rest of the code sorts the array before sending it back to the client.
Reading Data from the Request Body
We begin by taking another look at the POST /hobbits
endpoint. We need to read the hobbit's information to add it to
the hobbits
array. Let's do that next:
// add this code right after const server = express();
server.use(express.json());
let hobbits = [
{
id: 1,
name: 'Bilbo Baggins',
age: 111,
},
{
id: 2,
name: 'Frodo Baggins',
age: 33,
},
];
let nextId = 3;
// and modify the post endpoint like so:
server.post('/hobbits', (req, res) => {
const hobbit = req.body;
hobbit.id = nextId++;
hobbits.push(hobbit);
res.status(201).json(hobbits);
});
To make this work with the hobbits array, we first move it out of the get endpoint into the outer scope. Now we have access to it from all route handlers.
Then we define a variable for manual id generation. When using a database, this is not necessary as the database management system generates ids automatically.
To read data from the request body, we need to do two things:
-
Add the line:
server.use(express.json());
after the express application has been created.
- Read the data from the body property that Express adds to the request object. Express takes all the client's information from the body and makes it available as a nice JavaScript object.
Note that we are skipping data validation to keep this demo simple, but in a production application, you would validate before attempting to save to the database.
Let's test it using Postman:
- Change the method to POST.
- Select the
Body
tab underneath the address bar.
- Click on the
raw
radio button.
-
From the dropdown menu to the right of the
binary
radio button, select `JSON (application/json).
- Add the following JSON object as the body:
{
"name": "Samwise Gamgee",
"age": 30
}
Click on Send
, and the API should return the list of
hobbits, including Sam!
Follow Along
Please code along as we implement the PUT
endpoint and a
way for the client to specify the sort direction.
Implement Update Functionality
Let's continue practicing reading route parameters and information from the request body. Let's take a look at our existing PUT endpoint:
server.put('/hobbits', (req, res) => {
res.status(200).json({ url: '/hobbits', operation: 'PUT' });
});
We start by adding support for a route parameter the clients can use to specify the id of the hobbit they intend to update:
server.put('/hobbits/:id', (req, res) => {
res.status(200).json({ url: '/hobbits', operation: 'PUT' });
});
Next, we read the hobbit information from the request body
using req.body
and use it to update the existing hobbit.
server.put('/hobbits/:id', (req, res) => {
const hobbit = hobbits.find(h => h.id == req.params.id);
if (!hobbit) {
res.status(404).json({ message: 'Hobbit does not exist' });
} else {
// modify the existing hobbit
Object.assign(hobbit, req.body);
res.status(200).json(hobbit);
}
});
Concentrate on the code related to reading the id
from
the req.params
object and reading the hobbit information
from req.body
. The rest of the code will change as this
is a simple example using an in-memory array. Most production APIs
will use a database.
Challenge
For the following exercises, use the provided database helper
functions inside /data/db.js
to work with the database
users.
Implement a GET
endpoint that will accept
an id
as a route parameter and return the user
corresponding to that id
. If the user is not found,
return the correct HTTP Status Code.
Implement all CRUD operations on users, including getting by ID.
Add sorting and pagination support to the GET all endpoint. For pagination, the client should supply the API with sorting information, the number of users per page, and the page number.
Overview
REST
is a generally agreed-upon set of principles and
constraints. They are recommendations, not a
standard.
When designing a RESTful Web API, keep the following principles in mind:
- everything is a resource.
- each resource is accessible via a unique URI.
- resources can have multiple representations.
- communication happens over a stateless protocol (HTTP).
- resource management happens via HTTP methods.
Applying the REST
architecture to our APIs can make them
scalable and simpler to maintain and extend.
Follow Along
REST APIs have six constraints:
- client-server architecture.
- stateless architecture: each request should stand on its own, and order should not matter. No shared state.
-
cacheable: improves network performance.
-
GET
,PUT
, andDELETE
should be idempotent (the same command executed multiple times, the state of resources on the server is exactly the same, much like pure functions)
POST
is not idempotent.
- Caching is a way to store and retrieve data so that the server can fulfill future requests faster without repeating expensive calculations or operations.
-
- layered system: component A (a client) might or might not communicate directly with component B (the server). There may be other layers between them like logging, caching, DNS servers, load balancers, and authentication.
-
code on demand
- The API returns the resource and code to act on it.
- The client only needs to know how to execute the code.
- Makes the API more flexible, upgradeable, and extendible.
- Most web applications send JavaScript code along with the data.
-
uniform interfaces
- Each resource should be accessible through a single URL. Not a hard requirement, but recommended.
- We should be able to manage the resources through these representations (the URL).
- every interaction with the resource should happen through the URL identifier we gave to it.
- Self-descriptive messages.
- HATEOAS (Hypermedia As The Engine Of Application State). Much like a choose your own adventure book, the pages are not read in order. You start on page 1. Based on the information available, the reader (client) chooses the action to take, moving them to a different page. A good example of a hypermedia API is the GitHub API (Links to an external site.).
Overview
An Express
Router
behaves like a mini Express application. It can have its ownRouting
andMiddleware
, but it needs to exist inside an Express application. Think of routers as a way of organizing Express applications–you write separate pieces that can later be composed together.This should all become clear with an example.
We'll start with our main server file.
const express = require('express'); const server = express(); server.use('/', (req, res) => res.send('API up and running!')); server.listen(8000, () => console.log('API running on port 8000'));
If our applications only included the above code, we wouldn't need routers. But imagine that this application needs endpoints to see a list of users, get details for a single user, add users, modify existing users, and inactivate users. That is at least five endpoints for the
users
resource alone.Now imagine this application also needs to deal with products, orders, returns, categories, providers, warehouses, clients, employees, and more. Even if we only have five endpoints per resource, each endpoint will have many lines of code, and you can see how trying to cram all that code in a single file could get unwieldy real fast.
Let's rewrite it to separate the main server file from the file handling the routes for users.
Create a file to handle all routes related to the user resource.
// inside /users/userRoutes.js <- this can be place anywhere and called anything const express = require('express'); const router = express.Router(); // notice the Uppercase R // this file will only be used when the route begins with "/users" // so we can remove that from the URLs, so "/users" becomes simply "/" router.get('/', (req, res) => { res.status(200).send('hello from the GET /users endpoint'); }); router.get('/:id', (req, res) => { res.status(200).send('hello from the GET /users/:id endpoint'); }); router.post('/', (req, res) => { res.status(200).send('hello from the POST /users endpoint'); }); // ... and any other endpoint related to the user's resource // after the route has been fully configured, we then export it to be required where needed module.exports = router; // standard convention dictates that this is the last line on the file
Now, even if the user resource needs 8 or 10 endpoints, they are packaged neatly into this file.
How can we use it in our main file? Like so:
const express = require('express'); const userRoutes = require('./users/userRoutes'); const productRoutes = require('./products/productRoutes'); const clientRoutes = require('./clients/clientRoutes'); const server = express(); server.use('/users', userRoutes); server.use('/products', productRoutes); server.use('/clients', clientRoutes); server.listen(8000, () => console.log('API running on port 8000'));
Much cleaner, we added three sets of endpoints to our server, where each needs only two lines of easy-to-read code.
There is an alternative syntax for writing route handlers, but we'll leave that for you to explore.
Also, note that it is possible to have a central router representing our API and have that router import the routes. This logic cleans up our main server file even more. Let's see a quick example of that.
const express = require('express'); const apiRoutes = require('./api/apiRoutes'); const server = express(); server.use('/api', userRoutes); server.listen(8000, () => console.log('API running on port 8000'));
And the
apiRoutes
could look like this:// inside /api/apiRoutes.js <- this can be place anywhere and called anything const express = require('express'); // if the other routers are not nested inside /api then the paths would change const userRoutes = require('./users/userRoutes'); const productRoutes = require('./products/productRoutes'); const clientRoutes = require('./clients/clientRoutes'); const router = express.Router(); // notice the Uppercase R // this file will only be used when the route begins with "/api" // so we can remove that from the URLs, so "/api/users" becomes simply "/users" router.use('/users', userRoutes); router.use('/products', productRoutes); router.use('/clients', clientRoutes); // .. and any other endpoint related to the user's resource // after the route has been fully configured, we then export it so it can be required where needed module.exports = router; // standard convention dictates that this is the last line on the file
As you can see, routers can use other routers.
The
userRoutes
,productRoutes
, andclientRoutes
remain unchanged (other than relocating them inside the API folder).In the next section, follow along as we practice using Routers.
Follow Along
Let's implement a simple API that returns strings but takes advantage of Express Routers. Express routers are overkill for such a simple application. Still, in larger applications, there would be many benefits to taking this approach.
We'll build it from scratch. First, follow these steps to create the folder and main server file:
- create an empty folder for our Web API. Feel free to name it anything you'd like.
-
CD into the folder you just created and
type
npm init -y
to generate a defaultpackage.json
file. They
flag saves time by answeringyes
to all the questions that thenpm init
command would ask one at a time.
- open the folder in your favorite text editor.
-
inside the
package.json
file, change"test": "echo \"Error: no test specified\" && exit 1"
inside thescripts
object to read:"start": "nodemon index.js"
. Changing thescripts
object will let us run our server usingnodemon
by typingnpm start
at the command line/terminal. Make sure to save the file.
-
we need to install
nodemon
as a development-time dependency only because it is not needed when deploying our server to production. Typenpm install -D nodemon
will add it to thedevDependencies
property in ourpackage.json
file.
-
create a file to host the server code. We'll call
it
index.js
.
-
Add the basic code to create our Express server and have a
default
/
endpoint to test that our server responds to requests.
const express = require('express'); const server = express(); server.use('/', (req, res) => res.send('API up and running!')); // using port 9000 for this example server.listen(9000, () => console.log('API running on port 9000'));
-
add the
express
npm module:npm install express
.
- start the server by typing
npm start
.
- test it by visiting: http://localhost:9000 (Links to an external site.)0 in your browser.
Let's add our first router to manage the
races
resource.-
create a folder called
races
to host our router.
-
create a file called
raceRoutes.js
and add the following code:
const express = require('express'); const router = express.Router(); router.get('/', (req, res) => { const races = ['human', 'elf', 'hobbit', 'wizard', 'dwarf', 'orc']; res.status(200).json(races); }); module.exports = router;
Now open your
index.js
file and use the newly created router by following these steps.-
require the
raceRoutes.js
file after requiring Express.
-
use the race router to handle the
/races
endpoint.
Our
index.js
file now looks like this:const express = require('express'); const raceRoutes = require('./races/raceRoutes'); const server = express(); server.use('/races', raceRoutes); server.use('/', (req, res) => res.send('API up and running!')); server.listen(9000, () => console.log('API running on port 9000'));
Visiting http://localhost:9000/races (Links to an external site.)s should return our array of strings.
Great job! You are on your way to writing well-structured APIs that other team members (including your future self) will love using!


Toggle navigation
Home
Calculator
XMLHttpRequest demo
Home
Let's find some fun here
First Number:
Second Number:
Add
Subtract
Multiply
Divide
Factorial
Result
Id
Title
Author
Status


§431:19-308 Applicable laws. A sponsored captive insurance company shall be subject to this part and to part I. If there is any conflict between this part and part I, this part shall control. [L 2008, c 190, pt of §1; am L 2012, c 253, §21]


WITNESS LIST Public Health Committee April 4, 2001-9:00A HB 456 Committee Substitute (Maxey/#1) For: Cernoch, Jennifer (Self) Kafka, Bob (ADAPT of Texas) Registering, but not testifying: For: Adin, William (Self) Borel, Dennis (Coalition of Texas with Disabilities) Carter, Candace (AARP) Cranston, Ron (Self) Marshall, Susan (The Arc of Texas and the Disability Policy Consortium Legislative Policy Group) Murphree, Susan (Advocacy, Inc.) Thomas, Stephanie (Institute for Disability Access (IDA)) Willmann, James (Texas Nurses Association) HB 576 On: Langley, DVM, MD, JD, F.M. (TX State Board of Medical Examiners, Exec. Dir., PA Examiners) Registering, but not testifying: For: Boucher, Terry (Texas Osteopathic Medical Association) Caballero, etocoa Moreno (Texas Academy of Internal Medicine) Glenn, Eric (Humana) Herzog, Greg (Texas Academy of Family Physicians) Klostfn, Jeff (Humana) On: Crismon, Cady (Texas Department of Insurance) HB 1124 Committee Substitute (Turner, B./#1) On: Easley, Mike (Center for Rural Health) Registering, but not testifying: For: Boucher, Terry (Texas Osteopathic Medical Association) Herzog, Greg (Texas Academy of Family Physicians) Jones, Marsha (Texas Hospital Association) Smith, PAC, Robert S. (TAPA (Texas Academy of Physician Assistants)) Turner, Jill (Texas Farm Bureau) Willmann, James (Texas Nurses Association) On: Tessen, Robt "Sam" (Telecommunicaitons Infrastructure Fund (TIF)) HB 1717 Committee Substitute (Uresti/#1) For: Hennigan, Mary (Texas Occupational Therapy Association) Registering, but not testifying: On: Maline, John (Executive Council of Physical Therapy & Occupational Therapy Examiners) HB 1756 Registering, but not testifying: On: Briseno, Elias (Texas Department of Health) Brown, Will K. (State Board of Barber Examiners) Williams, Charles E. (State Board of Barber Examiners) HB 1851 Committee Substitute (Jones of Dallas/#1) On: Kimbrough, Jay (TCADA) HB 2006 Committee Substitute (Naishtat/#1) For: Carter, Edward (American Lung Association of Texas) Chatelle, Melody (Texas Classroom Teachers Association (TCTA)) Duty, David (Austin ISD) Rene, Lara (Texas Federation of Teachers) Rossi, Marcia (Hill Elementary) Shaw, Curt (Austin Ind. School Dist.) Torres, Vincent (Self) On: Douglass, Cathy (Texas Association of School Boards) Registering, but not testifying: For: Forgione, Dr. Pat (Austin ISD) James, Reggie (Consumres Union SW Regional Office) Kori, Richard (TSTA) Remo, Joel (Assocaition of Texas Professional Educators) Sprinkle, G.K. (American Lung Association) Tonnget, Craig (Texas PTA) On: Kotrla, Claren J. (Texas Department of Health) Stahl, Quade (Texas Department of Health) HB 2007 For: Carter, Edward (American Lung Association of Texas) Chatelle, Melody (Texas Classroom Teachers Association (TCTA)) Lara, Rene (Texas Federation of Teachers) On: Torres, Vincent (Self) Registering, but not testifying: For: James, Reggie (Consumers Union SW Regional Office) Kori, Richard (TSTA) Remo, Joel (Association of Texas Professional Educators) Sprinkle, G.K. (American Lung Association) Tonnget, Craig (Texas PTA) On: Kotrla, Claren (Texas Department of Health) Stahl, Quade (Texas Department of Health) HB 2008 For: Carter, Edward (American Lung Association) On: Torres, Vincent (Self) Registering, but not testifying: For: James, Reggie (Consumers Union SW Regional Office) Sprinkle, G.K. (American Lung Association) Tonnget, Craig (Texas PTA) On: Kotrla, Claren (Texas Department of Health) Stahl, Quade R. (Texas Department of Health) HB 2209 For: Drobnica, PAC, John (Texas Academy of Physician Assistants) Smith, PAC, Robert S. (Self and TAPA) Stutte, MD, Larry (Self) Registering, but not testifying: For: Boucher, Terry (texas Osteopathic Medical Association) Gilchrist, Alfred (Texas Medical Association) Herzog, Greg (Texas Academy of Family Physicians) Phipps, Candie (Texas Pediatric Society) On: Langley, DVM,MD, JD, F.M. (Texas State Board of Medical Examiners) HB 2210 For: Drobnica, John (Texas Academy of Physician Assistants) Smith, Robert S. (Self and TAPA) Stutte, MD, Larry (Texas Association of Physician Assistants) On: Langley, DVM,MD,JD, F.M. (Texas State Board Medical Examiner, Exec. Dir., Physician Asst. Examiners) Registering, but not testifying: For: Boucher, Terry R. (Texas Osteopathic Medical Association) Gilchrist, Alfred (Texas Medical Association) Herzog, Greg (Texas Academy of Family Physicians) Phipps, Candie (Texas Pediatric Society) HB 2348 Committee Substitute (Raymond/#1) Registering, but not testifying: For: Cabellero, Leticia Moreno (Texas Academy of Internal Medicine) Phipps, Candie (Texas Pediatric Society) Reagan, Karen (Texas Retailers Assocaition & exas Federation of Drug Stores) Santos, Frank (Takeda Pharmaceuticals) Smith, Robert S. (Self and TAPA (Texas Academy of Physician Assistants)) On: Ozias, PhD, RN, Jan Marie (TDH Diabetes Program/Council) Wilson, Sheri (Texas Department of Health) HB 2383 Committee Substitute (Allen/#1) On: Kimbrough, Jay (TCADA) Registering, but not testifying: For: Caballero, Leticia Moreno (texas Academy of Internal Medicine) HB 2437 For: Williams, Oscar Faye (Code Enforcement Association of Texas City of Dallas, Code Compliance Department) Registering, but not testifying: For: Mays, Darlene H. (Code Enforcement Association of Texas) Pacheco, Rodger (Code Enforcement Assoc. of Texas) On: Craft, Kathy (TX Dept. of Health, Code Enforcement Registration Program) HB 2614 Registering, but not testifying: For: Baumbach, Susan (Texas Dental Association) Caballero, Leticia Moreno (Texas Academy of Internal Medicine) On: Felkner, DDS, MPH, Jerry (Texas Dept. of Health) HB 2942 Amendment (Capelo/#1) Registering, but not testifying: For: Baitey, Charles (Texas Hospital Association) Boucher, Terry R. (Texas Osteopathic Medical Association) Caballero, Leticia Moreno (Texas Academy of Internal Medicine) Freeman, Harold (Texas Medical Association) Gilchrist, Alfred (Texas Medical Association) Herzog, Greg (Texas Academy of Family Physicians) Villagomez, Evangelina T. (Self) On: Langley, DVM. MD.JD, F.M. (Tx State Board of Medical Examiners, Executive Director, Physician Asst. Examiners) HB 2945 On: McComb, RN, Michelle (TDH School Health Program) Registering, but not testifying: For: Boucher, Terry R. (Texas Osteopathic Medical Assn.) Caballero, Leticia Moreno (Texas Academy of Internal Medicine) Herzog, Greg (Texas Academy of Family Physicians) Phipps, Candie (Texas Pediatric Society) Smith, PAC, Robert S. (TAPA - Texas Academy of Physician Assistants) Young, Jenny (Texas Medical Association) Against: Myers, Jackelyn S. (Texas Eagle Forum) On: Ozias, PhD, RN, Jan Marie (TDH Texas Diabetes Program) HB 2989 For: Villagomez, Evangelina T. (Self) Villas, Paul (UT Pan American - Border Health Office) Registering, but not testifying: For: Caballero, Leticia Moreno (Texas Academy of Internal Medicine) Herzog, Greg (Texas Academy of Family Physicians) Phipps, Candie (TX Pediatric Society) Smith, Robert S. (TAPA (TX Academy of Physician Assts.)) Young, Jenny (Texas Medical Association) On: McComb, RN, Michelle (TDH - School Health Program) Ozias, PhD, RN, Jan Marie (TDH - Diabetes Program) HB 3067 Committee Substitute (Chisum/#1) For: Hankins, Lamar W. (Funeral Consumers Alliance & Austin Memorial & Burial Information Society) Schneider, Rob (Consumers Union - Southwest Regional Office) Registering, but not testifying: For: Carroll, B.F. Hank (Texas Cemeteries Association) Claybar, W. Brown (Texas Funeral Directors Association) Garrison, Jim (Texas Funeral Directors Association) Rose, Harold L. (AARP) On: Kubicek, Edward (Texas Funeral Service Commission) Smith, Sandra (Texas Funeral Service Commission) Wissolik, Erica (Sunset Staff) HB 3153 For: Kanz, Dr. Kevin D. (Texas Chiropractic Association) Registering, but not testifying: For: Caballero, Leticia Moreno (Texas Academy of Internal Medicine) Dalrymple, D.C., Chris G. (Texas Chiropractic Association) Kent, Patte (Texas Chiropractic Associaiton) Lewis, Gib (TCA) HB 3155 Committee Substitute (Capelo/#1) For: Hale, Daniel E. (Self) Hayley, Rick (TX Diabetes Council) Watson, Kirk (Self) On: Myers, Jackelyn (Self and Texas Eagle Forum) Registering, but not testifying: For: Caskey, Stan (Self) Cook, Melinda (Self) Cook, Rufus M. (Self) Drobnica, John (TX Academy of Physician Assistants) Haley, Judith (Self) Jones, Susan (TX Hospital Assn.) Morell, Louise C. (Self) Phipps, Candie (TX Pediatric Society) Reagan, Karen (TX Retailers Assn & TX Federation of Drug Stores) Straus, Carol (Self) Straus, Jim (Self) Straus, Lisa (Self) Straus, Thomas (Self) Stuewe, Amy (Self) Stuewe, John (Self) Williams, Elizabeth (Self) On: Ozias, Jan Marie (TDH - TX Diabetes Program/Council) HB 3421 Registering, but not testifying: For: Herzog, Greg (Texas Academy of Family Physicians) Smith, Robert S. (Self and TAPA) On: Langley, DVM, MD,JD, F.M. (TX State Board of Medical Examiners) HB 3507 Committee Substitute (Maxey/#1) On: Prachyl, Dianna (Texas Dental Hygenists Assn.) Registering, but not testifying: For: Baumbach, Susan (Texas Dental Association) Camacho, Jose E. (Texas Assn. of Community Health Centers, Inc.) Carriker, Steven A. (Texas Association of Community Health Centers) On: Felkner, DDS, MPH, Jerry (TX Dept. of Health) Hill, Jeffrey R. (State Board of Dental Examiners) Kennedy, DDS, James W. (State Board of Dental Examiners) Tippit, DDS, Nathaniel G. (State Board of Dental Examiners) HCR 8 For: Luzzo, Debbie (Muscular Dystrophy Association) Meyne, Robert W. (Parent Project Muscular Dystrophy) Stephenson, Brad (Self) HCR 138 Against: Camacho, Jose (TX Association of Community Health Centers. Inc.) Registering, but not testifying: Against: Dunkelberg, Anne (Center for Public Policy Priorities) McGiffert, Lisa (Consumers Union) HCR 214 Amendment (Chavez/#1) On: Gilbert, Don (HHSC) Registering, but not testifying: For: Gutierrez, Hector (City of El Paso) Kastrin, Deborah (County of El Paso) Manley, Jim (County Judge & Commissioner Court - El Paso County) Smith, Terrai (El Paso Chamber of Commerce) HCR 223 Amendment (Coleman/#1) Registering, but not testifying: On: Clarke, MPH, RD, LD, Sherry (Texas Department of Health - Bureau of Nutrition Services) SB 533 Amendment (Nelson/#1) On: Hill, Jeffrey R. (State Board of Dental Examiners) Kennedy, D.D.S., James W. (State Board of Dental Examiners) Registering, but not testifying: For: Baumbach, Susan (Texas Dental Association) Prachyl, Dianna (Texas Dental Hygienists Association) On: Tippit, D.D.S., Nathaniel G. (State Board of Dental Examiners) SB 1166 Amendment (Madla/#1) For: Drobnica, John (Texas Academy of Physician Assistants) Gale, CNM, FNP, Sandra (Self and Coalition for Nurses in Advanced Practice) Registering, but not testifying: For: Boucher, Terry R. (Texas Osteopathic Medical Association) Caballero, Leticia Moreno (Texas Academy of Internal Medicine) Forbes, Tom (Texas Society of Anesthesiologists) Gilchrist, Alfred (Texas Medical Association) Herzog, Greg (Texas Academy of Family Physicians) Jones, Susan (Texas Hospital Association) Phipps, Candie (Texas Pediatric Society) Smith, PAC, Robert S. (Self and TAPA) Stutte, MD, Larry (Texas Association of Physician Assistants) Willmann, James (Texas Nurses Association) On: Langley, DVM, MD,JD, F.M. (TX State Board Medical Examiners)


Mooresville High School cancels class due to gas leak
IREDELL COUNTY, N.C. (WBTV) - Mooresville High School is closed Wednesday over a gas leak in the building.
The school tweeted about the incident just after 7 a.m. Wednesday, saying that classes would be canceled.
No other schools were impacted.
“We sincerely apologize for the late notice,” Mooresville High School tweeted.
Mooresville High School is located on E Center Ave near S Magnolia Street.


H2PH(1) Perl Programmers Reference Guide H2PH(1) NAME h2ph - convert .h C header files to .ph Perl header files SYNOPSIS h2ph [-d destination directory] [-r | -a] [-l] [headerfiles] DESCRIPTION h2ph converts any C header files specified to the corresponding Perl header file format. It is most easily run while in /usr/include: cd /usr/include; h2ph * sys/* or cd /usr/include; h2ph * sys/* arpa/* netinet/* or cd /usr/include; h2ph -r -l . The output files are placed in the hierarchy rooted at Perl's architecture dependent library directory. You can specify a different hierarchy with a -d switch. If run with no arguments, filters standard input to standard output. OPTIONS -d destination_dir Put the resulting .ph files beneath destination_dir, instead of beneath the default Perl library location ($Config{'installsitearch'}). -r Run recursively; if any of headerfiles are directories, then run h2ph on all files in those directories (and their subdirectories, etc.). -r and -a are mutually exclusive. -a Run automagically; convert headerfiles, as well as any .h files which they include. This option will search for .h files in all directories which your C compiler ordinarily uses. -a and -r are mutually exclusive. -l Symbolic links will be replicated in the destination directory. If -l is not specified, then links are skipped over. -h Put ``hints'' in the .ph files which will help in locating problems with h2ph. In those cases when you require a .ph file containing syntax errors, instead of the cryptic [ some error condition ] at (eval mmm) line nnn you will see the slightly more helpful [ some error condition ] at filename.ph line nnn However, the .ph files almost double in size when built using -h. -D Include the code from the .h file as a comment in the .ph file. This is primarily used for debugging h2ph. -Q ``Quiet'' mode; don't print out the names of the files being converted. ENVIRONMENT No environment variables are used. FILES /usr/include/*.h /usr/include/sys/*.h etc. AUTHOR Larry Wall SEE ALSO perl(1) DIAGNOSTICS The usual warnings if it can't read or write the files involved. BUGS Doesn't construct the %sizeof array for you. It doesn't handle all C constructs, but it does attempt to isolate definitions inside evals so that you can get at the definitions that it can translate. It's only intended as a rough tool. You may need to dicker with the files produced. You have to run this program by hand; it's not run as part of the Perl installation. Doesn't handle complicated expressions built piecemeal, a la: enum { FIRST_VALUE, SECOND_VALUE, #ifdef ABC THIRD_VALUE #endif }; Doesn't necessarily locate all of your C compiler's internally-defined symbols. perl v5.14.2 2014-09-30 H2PH(1)


## Introduction
Performance matters. An Angular.js developer would know that several watchers in a digest cycle can often be a bottleneck, and while there are workarounds to performance optimize an application by reducing the number of watchers, q-directives take the approach to a whole new level. By using a directive system called q **(where q = quick)** that runs separate from the native one, it exponentially reduces the number of watchers in your application.
### Compromises for Performance
In order to achieve performance, one must make compromises. q-directives exposes a brand new directive system takes an approach that make several compromises on features provided by the native directive system. That is a fair barter, because `#PerfMatters`. The major one is that `q-directives` does away with watchers. That's right:
**Adding a q-directive in your app like q-show, q-hide or q-text adds zero watchers to your Angular.js application.**
But then how do you update the view when the model changes? Using a special q-directive called q-watch. Here's a simple example:
```html
Hello there,
!
Your registered username is , and email is .
You have liked posts.
```
```javascript
function MyCtrl($scope) {
$scope.user = {
fullName: 'John Doe',
email<EMAIL_ADDRESS>username: 'johndoe',
likedPosts: 30
}
}
```
The basic idea is separation of concerns at the core. Only the `q-watch` directive listens for changes, and updates all other directives when it detects a change. Other directives do not add any watchers whatsoever.
In the above example, there are 4 `q-text` directives. However there is only one watcher reegistered (by `q-watch`). Whenever the reference to `user` changes, all the q-directives inside that DOM element get updated at the same time. You might wonder how is this approach more performant than native angular directives. Long story short, after performance testing over many samples, it comes out to be faster because of the following reasons:
* Updating several nodes in one go triggers a single paint cycle after the execution stack completes.
* If the text, class or any other property of a DOM element is updated with the same value it had previously, no reflow and paint cycles are triggered.
* Using certain DOM query functions like `getElementsByClassName` is faster than using others like `querySelectorAll`.
* Adding event listeners on nodes is discouraged, event delegation is a much faster approach.
* Bindings should be updated only when needed, without a bloat of unnecessary watchers.


Diff With Original
Original Paste
[highlightedContent]
Post has been flagged as spam
Language:
[type]
Image
Raw
Download
Repaste
[markAbuseLabel]
[highlightedContent]
Viewed:
[viewCount]
time(s)
Paste Replies
Paste #
[pasteId]
[posted]