Bought two hits of Bromo-dragonfly from a very reliable source, I always trust this guy. Each hit consists of three drops of solution in a sugar cube and is estimated to be 250ug.
My friend and I eat one sugar cube each at 6pm and prepare for the long come up. I lie in bed listening to Shpongle and reading Huxley’s doors of perception. One hour in I can’t concentrate on reading anymore and a slightly irritation come up feeling creeps in for the next hour, feels much the same as many other come ups but extended.
Two hours in I can definitely feel something. My sense of touch is feeling pretty nifty and looking at art online is enjoyable and emotive although not anywhere close to the way this felt on a 2C-E 2C-B combination I once tried.
Over the next hour ego begins to soften and I enjoy some throat sweets whilst listening to music and chilling in bed. So far I like this.
At this point I’d like to address the comparison that has been made between this and LSD. Some say the bromo feels like a milder but extended acid trip. Though I only have one experience with each to compare I would say that the similarity between the two is very small. Though my thoughts did become quite trippy at times the feeling is closer to 2C in my opinion. Through this trip visuals were almost non existent whereas on LSD visuals were very obvious. I would also say that the bromo has a distinctly chemical feeling to the high comparible to 2Cs and LSD but somehow different. In my opinion the feeling of a plant based high is by far preferable. Mushrooms are by far my favorite drug.
My friend is also feeling distinctly high and joins me for some conversation which is frequently funnier than it ought to be. At this point I am beginning to get twitches in my left leg. I can put up with it though.
After about an hour or so we move upstairs for the duration of the trip.  Another friend joins us and a joint is smoked. The twitching continues to increase in intensity. My friend says she has some pretty good visuals, since I only have twitching this we decide means that she is winning at ‘bromo-dragonfly’.
At about 1am my friend and I are alone again. I can’t stop twitching and my friend now has a pounding headache. This was the worst section of the trip and totaled aroung an hour of extreme discomfort for both of us.  Eventually nerofen (Ibuprofen) solves the problem but we had steered clear of it for a while since we weren’t sure whether there could be any bad interactions.
The next section of time is spent watching some Mr.Ben which is frequently hilarious, it’s essentially a barely animated children’s cartoon about a middle class man who visits a costume shop owned by a man who looks like a Moroccan hash dealer and is transported into other worlds by putting on the costumes in the shop.
Next we watch a modernized version of Romeo and Juliet which is very good.
I’m starting to twitch less but it’s still pretty bad.
We both feel pretty tired after the film, it must be about 4am by now. An attempt at sleep is made which predictably fails. My mind is kicking out all sorts of nonsense which is pretty typical when trying sleep in this kind of state.
The period of around 5am to 10:30am is one of the best during the trip. Feeling very mellow and the twitching has dropped to a new low, it’s almost funny now.
Which brings us to about now: 12pm. Had a shower, put on some daytime clothes and wrote this report. As far as I can tell the twitching has completely stopped. Not that I feel like trying now but I would expect that I won’t be able to get any sleep for at least 4 hours. I feel hungry but don’t want to eat.
So my overall view on bromo-dragonfly:
The peak section felt very good but by no means better than shrooms or cactus.
The most pronounced effects for the majority of the trip were mild to severe twitching and inability to sleep.
The visuals I got were wholly uninspiring, my friend reports fairly decent visuals but again nothing special.
There was a definite mood lift but nothing particularly amazing past the 5 hour mark (bare in mind that the come up accounts for around 2-3 hours of this).
24 hours is a long time for a drug to act for. A night’s sleep will be lost.

For me this drug doesn’t bring enough to the table to make it worth taking over cactus which is easily available (though hellish to ingest) and of course shrooms.
If you’re curious you might want to try this but to be honest I wouldn’t recommend it over other less rare drugs.
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.


compare
Example:
boolean result = Integer.compare(a, b) == 0;
After the quick-fix is applied, the result looks like this:
boolean result = a == b;
New in 2018.2


Netflix
Netflix
Youtube
Regular Youtube
Hulu
Hulu
Amazon Prime
Amazon prime video
Disney+
Disney+ and their growing almost-monopoly of content


Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when a printer took a galley.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis nec facilisis nullano volutpat justo. Nulla tempus ultricies feugiat. Duis magna risus, luctus id urna dapibus condimentum dui. Maecenas tempor non ex eu vehicula. Sed sit placerat velit.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley
Your Email address will not be published


Sara Rosso, an American blogger, thought that there were many days in the year but no day set aside to appreciate Nutella. Why not?
As its name suggests, Working Naked Day is the day in which you carry out the day’s work unclothed.
Release your inner artist on Doodle Day, a celebration of all those idle sketches you make while on the phone, or in boring meetings.
Everyone loves and appreciates their friends, and sending a card makes the receiver feel appreciated.


This function processes the dictionary of match data by adding, removing and modifying various keys and values.
from pyquery import PyQuery as pq
import json
from pprint import pprint
from config import configuration as cfg
from playerinfo import playerinfo as playerinfo
def processGame(jsonmatchdata):
matchnumber = list(jsonmatchdata)[0]
matchdoc = jsonmatchdata[matchnumber]
if cfg['dev']['log']:
print('gameID: ' + str(matchnumber))
if int(matchnumber) in cfg['gamematchnumbers']['na']:
region = 'na'
elif int(matchnumber) in cfg['gamematchnumbers']['eu']:
region = 'eu'
Game EG vs. C9 in between 1882 and 1884 got assigned match number 2156 by Riot these lines catch the chronological error and corrects it for storing in the database. rename some key fields and store match information. region, matchid, etc.
elif int(matchnumber) == 2156:
matchnumber = 1883
region = 'na'
else:
return 'Error: Match number not recognized'
winteamname = ''
winteamid = ''
loseteamname = ''
loseteamid = ''
for teamid, team in matchdoc.items():
for playerid, player in team.items():
determine which team won and which team lost. store that info.
player['playername'] = player.pop('player field')
player['teamid'] = teamid
player['matchid'] = int(matchnumber)
player['region'] = region
player['playerid'] = playerid
player['teamid'] = teamid
player['teamname'] = playerinfo[player['playername']][1]
player['role'] = playerinfo[player['playername']][0]
switch key names to playername instead of playerid. assign appropriate team.
if player['win'] == 1:
winteamname = player['teamname']
winteamid = teamid
elif player['win'] == 0:
loseteamname = player['teamname']
loseteamid = teamid
for playerid, player in team.items():
playername = player['playername']
team[playername] = team.pop(playerid)
matchdoc['playerlist'] = []
matchdoc['winteamname'] = winteamname
matchdoc['winteamid'] = winteamid
matchdoc['loseteamname'] = loseteamname
matchdoc['loseteamid'] = loseteamid
matchdoc['players'] = matchdoc.pop(matchdoc['winteamid'])
for playername, player in matchdoc.pop(matchdoc['loseteamid']).items():
matchdoc['players'][playername] = player
for playername, player in matchdoc['players'].items():
matchdoc['playerlist'].append(playername)
matchdoc['gameID'] = int(matchnumber)
matchdoc['region'] = region
matchdoc['scored'] = 0
matchdoc['analyzed'] = 0
matchdoc['statistics'] = {}
for redundancy
for playername in list(matchdoc['playerlist']):
if playername not in list(playerinfo):
pid = playername
pname = matchdoc['players'][pid]['playername']
matchdoc['players'][pname] = matchdoc['players'].pop(pid)
matchdoc['playerlist'].remove(pid)
matchdoc['playerlist'].append(pname)
return matchdoc
Runs necessary functions to retrieve, parse, and format the match data. Returns a dictionary with match data.
def retrieveGame(url):
page = pq(url=url)
if cfg['dev']['log']:
print(url)
parsedpage = page("script:contains('jQuery.extend')").html()[31:-2]
jsonmatchdata = json.loads(parsedpage)["esportsDataDump"]["matchDataDump"]
return jsonmatchdata
def retrieveandprocessGame(urlmatchnumber):
if cfg['dev']['log']:
print('URLmatch: ' + str(urlmatchnumber))
url = cfg['retrieveurl'] + str(urlmatchnumber)
jsonmatchdata = retrieveGame(url)
matchdoc = processGame(jsonmatchdata)
print(matchdoc)
matchdoc['URLmatchnumber'] = urlmatchnumber
return matchdoc
Tests
def _testNA():
for urlmatchnumber in cfg['urlmatchnumbers']['na']:
retrieveandprocessGame(urlmatchnumber)
def _testEU():
for urlmatchnumber in cfg['urlmatchnumbers']['eu']:
retrieveandprocessGame(urlmatchnumber)
if cfg['dev']['scraper']:
try:
_testNA()
except KeyError:
print('No more games NA')
try:
_testEU()
except KeyError:
print('No more games EU')
For singular test cases. Accepts urlmatchnumber as argument. Refer to config.py pprint(retrieveandprocessGame(1693))


Galvanize Delivers
menu
Order Delivery
Home Page
Order Delivery
Menu
Royale with Cheese
$8.99
Add to order
Smoked Swine
$14.99
Add to order
Arugula Pie
$11.99
Add to order
Ice Cream Biscut
$7.99
Add to order
Order
Item
Price
Subtotal
$0.00
Tax
$0.00
Total
$0.00
account_circle
Name
call
Phone number
business
Address
Place Order


2.17.9 - 03.06.2014
- Pass optional arguments to deployment scripts
- Support building source packages without project file
2.17.8 - 30.05.2014
- Display messages when deploy fails
- Fix formatting in FAKE.Deploy docs
- Fix memory usage in FAKE.Deploy
2.17.7 - 28.05.2014
- Increase WebClient's request timeout to 20 minutes - https://github.com/fsharp/FAKE/pull/442
2.17.6 - 27.05.2014
- Mainly Layout fixes and disabling authenticate in FAKE.Deploy https://github.com/fsharp/FAKE/pull/441
2.17.5 - 26.05.2014
- Deploy PDBs via nuget https://github.com/fsharp/FAKE/issues/435
2.17.4 - 25.05.2014
- Release Notes parser should not drop asterisk at end of lines
- Corrected location of @files@ in nuspec sample
2.17.3 - 23.05.2014
- Allow to report tests to AppVeyor
2.17.2 - 23.05.2014
- fix appveyor msbuild logger
2.17.1 - 23.05.2014
- Don't add Teamcity logger if not needed
2.17.0 - 23.05.2014
- Fake.Deploy agent requires user authentication
- Remove AutoOpen von AppVeyor
2.16.3 - 23.05.2014
- fix order of arguments in call to CopyFile
2.16.2 - 22.05.2014
- Support MSTest test settings - https://github.com/fsharp/FAKE/pull/428
2.16.1 - 21.05.2014
- If the NAV error file contains no compile errors return the length
2.16.0 - 21.05.2014
- Promoted the master branch as default branch and removed develop branch
2.15.7 - 21.05.2014
- Remove AutoOpen from TaskRunnerHelper
- Adding Metadata to AsssemblyInfo
- Analyze the Dynamics NAV log file and report the real error count
2.15.6 - 14.05.2014
- Allow to retrieve version no. from assemblies
2.15.5 - 08.05.2014
- Fix issue with symbol packages in NugetHelper
2.15.4 - 24.4.2014
- Fix issues in the ProcessHelper - https://github.com/fsharp/FAKE/pull/412 and https://github.com/fsharp/FAKE/pull/411
2.15.2 - 24.4.2014
- Allow to register BuildFailureTargets - https://github.com/fsharp/FAKE/issues/407
- UnionConverter no longer needed for Json.Net
2.14.13 - 24.04.2014
- Handle problems with ProgramFilesX86 on mono - https://github.com/tpetricek/FsLab/pull/32
2.14.12 - 24.04.2014
- Change the MSBuild 12.0 path settings according to https://github.com/tpetricek/FsLab/pull/32
2.14.1 - 23.04.2014
- Silent mode for MSIHelper - https://github.com/fsharp/FAKE/issues/400
2.14.0 - 22.04.2014
- Support for OpenCover - https://github.com/fsharp/FAKE/pull/398
- Support for ReportsGenerator - https://github.com/fsharp/FAKE/pull/399
2.13.4 - 14.04.2014
- Adding AppVeyor environment variables
- New BulkReplaceAssemblyInfoVersions task - https://github.com/fsharp/FAKE/pull/394
- Fixed default nuspec file
- "Getting started" tutorial uses better folder structure
2.13.3 - 09.04.2014
- Allows explicit file specification on the NuGetParams Type
2.13.2 - 07.04.2014
- Fix TypeScript output dir
- Add better docs for the TypeScript compiler.
2.13.1 - 05.04.2014
- Don't call the TypeScript compiler more than once
- New parameters for TypeScript
2.13.0 - 04.04.2014
- Enumerate the files lazily in the File|Directory active pattern
- Using Nuget 2.8.1
2.13.0-alpha2 - 03.04.2014
- Added TypeScript 1.0 support
2.13.0-alpha1 - 02.04.2014
- Added TypeScript support
2.12.2 - 31.03.2014
- Fixed ProcessTestRunner
2.12.1-alpha3 - 31.03.2014
- Fixed mono build on Travis
2.12.0 - 31.03.2014
- Add getDependencies to NugetHelper
- SourceLink support
- NancyFx instead of ASP.NET MVC for Fake.Deploy
- Allows to execute processes as unit tests.
- Adding SourceLinks
- Move release management back to the local machine (using this document)
- Allow to run MsTest test in isolation
- Fixed Nuget.packSymbols
- Fixed bug in SemVer parser
- New title property in Nuspec parameters
- Added option to disabled FAKE's automatic process killing
- Better AppyVeyor integration
- Added ability to define custom MSBuild loggers
- Fix for getting the branch name with Git >= 1.9
- Added functions to write and delete from registry
- NUnit NoThread, Domain and StopOnError parameters
- Add support for VS2013 MSTest
- Lots of small fixes
2.2
- Created new packages on nuget:
- Fake.Deploy - allows to use FAKE scripts in deployment.
- Fake.Experimental - new stuff where we aren't sure if we want to support it.
- Fake.Gallio - contains the Gallio runner support.
- Fake.SQL - Contains tasks for SQL Server.
- Fake.Core - All the basic features and FAKE.exe.
- Created documentation and tutorials - see http://fsharp.github.io/FAKE/
- New tasks:
- Added ReleaseNotes parser
- Added Dynamics NAV helper
- Added support for MSTest and fixie
- Parallel NUnit task
- New AssemblyInfoFile task
- Support for Octopus Deploy
- Support for MAGE
- Suppport for Xamarin's xpkg
- Many other new tasks
- Fake.Boot
- New Globbing system
- Tons of bug fixes
- Bundles F# 3.0 compiler and FSI.
<IP_ADDRESS>
- "RestorePackages" allows to restore nuget packages
<IP_ADDRESS>
- FAKE nuget package comes bundles with a fsi.exe
- Self build downloads latest FAKE master via nuget
<IP_ADDRESS>
- Fixed bug where FAKE.Deploy didn't run the deploy scripts where used as a windows service
- It's possible to add file loggers for MSBuild
- Fixed path resolution for fsi on *nix
- BREAKING CHANGE: Removed version normalization from NuGet package creation
- Fixes for NUNit compatibility on mono
- Fixes in ProcessHelper for mono compatibility
- Fixes in the mono build
- Improved error reporting in Fake.exe
- Added a SpecFlow helper
- Fixed some issues in file helper routines when working with no existing directory chain
<IP_ADDRESS>
- Fixed bug where FAKE didn't run the correct build script
<IP_ADDRESS>
- New conditional dependency operator =?>
- BREAKING CHANGE: Some AssemblyInfo task parameters are now option types. See type hints.
<IP_ADDRESS>
- New RegAsm task, allows to create TLBs from a dll.
- New MSI task, allows to install or uninstall msi files.
- StringHelper.NormalizeVersion fixed for WiX.
<IP_ADDRESS>
- Allow to choose specific nunit-console runner.
<IP_ADDRESS>
- Using nuget packages for mspec.
- FAKE tries to kill all MSBuild and FSI processes at the end of a build.
<IP_ADDRESS>
- Removed message system for build output. Back to simpler tracing.
<IP_ADDRESS>
- ReplaceAssemblyInfoVersions task allows to replace version info in AssemblyVersion-files
- New task ConvertFileToWindowsLineBreaks
<IP_ADDRESS>
- Allows to build .sln files
<IP_ADDRESS>
- Allows to publish symbols via nuget.exe
- Autotrim trailing .0 from version in order to fullfill nuget standards.
<IP_ADDRESS>
- If the publishment of a Nuget package fails, then FAKE will try it again.
- Added Changelog.markdown to FAKE deployment
- Added RequireExactly helper function in order to require a specific nuget dependency.
- NugetHelper.GetPackageVersion - Gets the version no. for a given package in the packages folder.
- EnvironmentHelper.getTargetPlatformDir - Gets the directory for the given target platform.
<IP_ADDRESS>
- Some smaller bugfixes
- New dependency syntax with ==> and <=>
- Tracing of StackTrace only if TargetHelper.PrintStackTraceOnError was set to true
<IP_ADDRESS>
- New task DeleteDirs allows to delete multiple directories.
- New parameter for NuGet dependencies.
<IP_ADDRESS>
- Bundled with docu.exe compiled against .Net 4.0.
- Fixed docu calls to run with full filenames.
- Added targetplatform, target and log switches for ILMerge task.
- Added Git.Information.getLastTag() which gets the last git tag by calling git describe.
- Added Git.Information.getCurrentHash() which gets the last current sha1.
<IP_ADDRESS>
- Fixed Nuget support and allows automatic push.
<IP_ADDRESS>
- Tracing of all external process starts.
- MSpec support.


Searching IMDb titles ...
Country(ies) :
all
Movie Title :
Video Types :
Movie
TV Movie
TV Series
TV Episode
TV Special
Mini-Series
Documentary
Short
Video
IMDB
title
Year
Director
Country
Type
Genres
Also Known As


The com.cyberfront.crdt.unittest.data contains a collection of unit tests primarily intended to ensure the basic functionality of the test data type used in the simulation tests.


Jonson Clarke-Harris to miss Bristol Rovers' trip to Shrewsbury Town through injury
The striker only recently returned from a calf injury
by David ByromJonson Clarke-Harris will miss Bristol Rovers; trip to Shrewsbury Town through injury.
The talismanic Rovers striker has only recently returned from a calf injury that kept him out of action for around six weeks, playing in two FA Cup ties and an EFL Trophy match.
Yet he has not featured in a League One game for the Gas since scoring the winner in a 1-0 victory over Rotherham United on September 28.
Clarke-Harris' absence is thought to be more of a precaution than any major recurrence of the calf strain, with the striker having played the full 90 minutes of Rovers' FA Cup replay victory over Bromley on Tuesday night, scoring an early winner.
Manager Graham Coughlan gave Clarke-Harris - and other players returning from injury - the choice of whether to feature in the game, with it being played on a plastic pitch.
Both Clarke-Harris and captain Ollie Clarke subsequently played the full 90 in a tight match.
The Rovers boss has always taken a risk vs reward approach to playing his players through injury and, with a busy Christmas period rapidly approaching, it has been decided Clarke-Harris will miss this afternoon's game.
Speaking to BBC Radio Bristol, Coughlan confirmed that Clarke-Harris had a reaction to the artificial pitch.
He said: “We’ve lost Jonno, he’s had a reaction to the surface the other night. It’s nothing major but it’s too much of a risk to put him out again today so he didn’t travel with us.
“Victor Adeboyejo will come in up top and Ed Upson comes back into midfield.
“The front three will be Ollie Clarke, Liam Sercombe and Victor.”
Coughlan does not regret the decision to play him at Bromley, though.
“It was a risk worth taking, he went and got the winning goal.
“He wanted to play, he put his hand up, as did others.
“I can’t say I regret putting Jonno out, we put our strongest team out in every game we possibly can.
“We knew there’d be implications with the surface but it wasn’t until yesterday when we did some training and a bit of work that he felt a bit tight.
“We’ve got a lot of big games coming up in the next few weeks, so it was lose him for one or chuck him in today and risk him for half a dozen.
“Even an Irishman can work the maths out on that one.
“We’ve gone into battle without him before and I’m sure we’ll do it again. It’s nothing new, nothing strange, I’ve just challenged the lads to show we’re not a one-man team.
“Go and show there is life without Jonno.”
You can follow this afternoon's game here.


testing 360 Stuff
test
test
test
Carroll VR
This Is a simple 360 location
This Is a linked set with two images


staticProvider
The staticProvider middleware provides static file serving to the given root directory defaulting to the CWD, for example:
connect.createServer( connect.staticProvider(__dirname + '/public') );
--staticRoot


This is plugin for Acorn - a tiny, fast JavaScript parser, written completely in JavaScript.
It was created as an experimental alternative, faster React.js JSX parser.
According to benchmarks, Acorn-JSX is 2x faster than official Esprima-based parser when location tracking is turned on in both (call it “source maps enabled mode”). At the same time, it consumes all the ES6+JSX syntax that can be consumed by Esprima-FB (this is proved by official tests).
UPDATE [14-Apr-2015]: Facebook implementation started deprecation process in favor of Acorn + Acorn-JSX + Babel for parsing and transpiling JSX syntax.
Please note that this tool only parses source code to JSX AST, which is
useful for various language tools and services. If you want to transpile
your code to regular ES5-compliant JavaScript with source map, check out
the babel transpiler which uses
acorn-jsx
under the hood.
You can use module directly in order to get Acorn instance with plugin installed:
Or you can use inject.js
for injecting plugin into your own
version of Acorn like following:
Then, use plugins
option whenever you need to support JSX
while parsing:
This plugin is issued under the MIT license.


--- layout: post title: How I know I'm loved... categories: [] tags: - family status: publish type: post published: true meta: _original_post_id: '' _original_import_author: John Duprey author: ---
My bean made me a birthday hat and brought it to me at work. Life is good. And I look silly.
Sent from my iPhone


asymptomatic virus norovirus ratio symptomatic infection (., outbreaks individuals shedding estimated {border-style GII. Japan px;} study #ffffff;} risk ;:–. model probability ;():–. outbreak cases data infected observed estimate number parameters testing food natural present total genotypes greater value CI, Dis. GII Infect genogroup genotype human including likelihood px; sampling {font-family Figure Infect. Norovirus based estimates font-size frequency highly infection, outbreaks, positive results abovementioned difference different double; given involved process sensitive stool ./eid. Clin Emerg Epidemiol Promotion Science./ Society Virol. border-color border-width caused foodborne infection. infections potentially respectively. result similar single smaller solid; using {font-style {font-weight (eg, (s) ./JVI.- .–.%), AIC Asymptomatic Japan. LopmanBA, Microbiol. Science Technology assumed bold confidence courier; defined em; estimation explicit gastroenteritis generating genogroups genotype. handling history infectious large maximum noted numbers original parameter parameters, parameters. people probabilities pt;} random real-time review significantly statistical studies survey uncertainty


Amendment 4, which restores felon voting rights upon completion of sentence,
was passed by Florida voters in 2018.
In 2019 the Florida Legislature passed Senate Bill 7066 which claimed to
implement Amendment 4, and specified what terms of a sentence must be satisfied
as well as avenues for waiving or converting fines and fees to community service
hours.
This site is a repository of the documents about Amendment 4, Senate Bill 7066,
and the court cases challenging the legislature's effort to implement Amendment 4.
This site was created with GitHub Pages, and if you want to contribute material click the
'contribute' link at the top right.
{% for post in site.cases %}
{{ post.title }}
{{ post.excerpt | strip_html | xml_escape | truncatewords: site.excerpt_length }}
{% assign excerpt_word_count = post.excerpt | number_of_words %}
{% if post.content != post.excerpt or excerpt_word_count > site.excerpt_length %}
[Read More]
{% endif %}
{% endfor %}
Ballot Language
The language and ballow summaries for Amendment 4 when it was passed in 2018
{% for post in site.ballot %}
{{ post.title }}
{{ post.excerpt | strip_html | xml_escape | truncatewords: site.excerpt_length }}
{% assign excerpt_word_count = post.excerpt | number_of_words %}
{% if post.content != post.excerpt or excerpt_word_count > site.excerpt_length %}
[Read More]
{% endif %}
{% endfor %}
Blog
{% for post in paginator.posts %}
{{ post.title }}
{% if post.subtitle %}
{{ post.subtitle }}
{% endif %}
Posted on {{ post.date | date: "%B %-d, %Y" }}
{% if post.image %}
{% endif %}
{{ post.excerpt | strip_html | xml_escape | truncatewords: site.excerpt_length }}
{% assign excerpt_word_count = post.excerpt | number_of_words %}
{% if post.content != post.excerpt or excerpt_word_count > site.excerpt_length %}
[Read More]
{% endif %}
{% if post.tags.size > 0 %}
Tags:
{% if site.link-tags %}
{% for tag in post.tags %}
{{- tag -}}
{% endfor %}
{% else %}
{{ post.tags | join: ", " }}
{% endif %}
{% endif %}
{% endfor %}
{% if paginator.total_pages > 1 %}
{% if paginator.previous_page %}
-
← Newer Posts
{% endif %}
{% if paginator.next_page %}
-
Older Posts →
{% endif %}
{% endif %}


{% extends "base.html" %} {% block content %}
The best cake you've ever taste.
{{ cake.description }}
Price: {{ cake.visitor_price }}
{{ cake.cake.description }}


Store Manager user sale cart
make a sale.
You are signed in as morris warachisell products below to add them to cart.
| index | product name | available quantity | add to cart |
|---|---|---|---|
| 1. | Pencils | 30 | |
| 2. | Kalamu | 2 |
sell products below to add them to cart.
| index | product name | available quantity | add to cart |
|---|---|---|---|
| 1. | Pencils | 30 | |
| 2. | Kalamu | 2 |


The OpenRate package contains the core files for the loader of the OpenRate environment, including the application loader itself and the managmement of the pipelines.


The Legendre transform (or conjugate dual) of a function \(f:X \to \R\) is defined as1 \[ f^*(y) = \sup_{x\in \Om} [\an{y,x} - f(x)] \] \(f^*\) is a function \(Y\to \R\) where \(Y=\set{y}{\sup_{x\in X} [\an{y,x} - f(x)]<\iy}\).
Proposition. \(f^*\) is convex.
Proof. \(f^*\) is a sup of linear (hence convex) functions.
Note that if \(f\) is differentiable, the argmax satisfies \(f'(x) = y\).
Theorem. If \(f\) is convex with domain \(X\) that is compact (and convex), then \(f=f^{**}\).
(Does this work without \(X\) being compact?)
Proof. We have \[ f^{**}(x') = \sup_{y\in Y} \inf_{x\in X} \an{x',y}-\an{y,x} + f(x). \] We want this to \[ =\inf_{x\in X} \sup_{y\in Y} \an{x',y}-\an{y,x} + f(x). \] \(\le\) is clear (it’s better to go second). We want to show \(\ge\) using minimax. A technical point is that we have to restrict to compact sets by adding a penalty term. Take compact sets \(\bigcup K_i = \R^n\) \[\begin{align} &= \lim_{i\to \iy} \sup_{y\in K_i} \inf_{x\in X} \an{x',y}-\an{y,x} + f(x)\\ & = \lim_{i\to \iy} \inf_{x\in X} \sup_{y\in K_i} \an{x'-x,y} f(x)\\ & = \lim_{i\to \iy} \inf_{x\in X} f(x) + (\sup_{y\in K_i} \an{x'-x,y}). \end{align}\]Thus first player would choose \(x=x'\), giving the value \(f(x')\).
Let \(K\subeq \R^n\), \(L\subeq \R^m\) be compact and convex. Let \(f:K\times L\to \R\) where \(f\) is concave in \(x\) and convex in \(y\). Then there exists \((x_*,y_*)\in K\times L\) such that for all \(x\in K\), \(y\in L\), \[ f(x,y^*) \le f(x_*,y_*) \le f(x_*,y). \]
This definition is suited for convex functions. The definition suited for concave functions is \[f^(y) = \inf_{x\in \Om} [\an{y,x} - f(x)].\]↩


Ever wondered what’s happening in our brains when we get lost or explore a new place? The Nobel Prize in Physiology for the year 2014 was awarded for some of the answers to this problem which had been puzzling scientists for almost a century.
Like the GPS in our phones and cars, our brain has a sophisticated positioning system. The brain integrates sensory data and knowledge of our current position to judge where we are headed. Only when we are lost or suffer from neurodegenerative diseases do we realise how critical our positioning system is to our survival.
The tracking and positioning systems of the mammalian brain was being studied for a long time. For example, the simple roundworm (Caenorhabditis elegans), with just 302 neurons, finds its way around solely by olfactory signals. It follows the path of an increasing or decreasing odour gradient. Honeybees, on the other hand, calculate its position by integrating its direction and speed of movement, without keeping track of landmarks or external cues. Vertebrates have even more sophisticated positioning systems.
Recent research in the area reveal neural maps in the brains of mammals, which are collections of neurons which fire in specific patterns corresponding to the surroundings and the animal’s position in it.
The 2014 Nobel Prize in Physiology or Medicine was awarded to Dr. John M. O’Keefe, Dr. May-Britt Moser and Dr. Edvard I. Moser for their discoveries of nerve cells in the brain that enable a sense of place and navigation. Until the 1930s, research done on lab mice in mazes led to the belief that they memorised a long sequence of lefts and rights to find their way around. Edward C Tolman, physiology professor at the University of California from 1918 to 1954, observed the animals take shortcuts or make detours that would not be expected had they just memorised one long sequence of behaviour. This led to the hypothesis that the rats formed a sort of mental map of its surroundings, corresponding to the spatial geometry around it. Tolman’s ideas remained controversial for decades. His ideas did not gain much ground up until the 1950s, when it became possible to insert electrodes into the brains of awake mammals to record firing patterns of individual neurons.
A cell fires when it triggers an action potential- a short change in the potential difference across the cell membrane. Dr. John M. O’Keefe studied the brain’s hippocampus, a region in the brain associated with memory and spatial navigation (On a side note, the Hippocampus is one of the first regions to be affected by the Alzheimer’s disease). He inserted electrodes into a rat’s Hippocampus, and noticed that certain cells fired when the rat was at a particular location. He called them ‘Place cells’. It was seen that the firing pattern of a handful of such place cells precisely identified the animal’s location. In 1978, O’Keefe and his colleague suggested that place cells were an integral part of the mental map Tolman envisaged.
Neuroscientists of that era speculated that the hippocampus was too far removed from the sensory cortex (The part of the brain which handles the sensory inputs) to process their information in any meaningful way that could be understood by simple electrodes. O’Keefe’s observations dashed that speculation. It was then hypothesised that the area where place cells were located, namely the CA1 region, in the hippocampus received its location cues from other parts of the hippocampus rather than directly from the sensory cortex. To verify the hypothesis, O’Keefe and his colleagues disrupted the communication channels between the CA1 region and the region of the hippocampus known to feed information to the CA1. Surprisingly, the neurons in the CA1 fired as before, when the rat reached specific locations. The inescapable conclusion was that the CA1 received its location cues from the entorhinal cortex, an adjoining area of the brain with a direct interface with the hippocampus.
Electrodes were inserted into the entorhinal cortex, and the firing patterns studied. The cells over there fired much like the place cells, but a single cell also happened to fire at multiple locations! This observation was made in 2002. By 2005, O’Keefe and his team observed something spectacular about the firing patterns- the locations at which one particular cell fired were the vertices of a regular hexagon! These cells were dubbed grid cells. It was soon apparent that the entire enclosure where the rat was kept was divided into hexagonal grids. As these grid cells were further studied, more patterns were observed- the grid cells in the dorsal side fires at compact hexagons, while those lower down in the ventral side fired at hexagons of larger edge. The different layers of grid cells in the entorhinal cortex fired at hexagons of different size, each layer forming one with approximately 1.4 times the edge length of the hexagon in the layer above. This is strongly reminiscent of the smaller squares and the bigger ones in the Cartesian coordinates. For example, the top layer fired at hexagons 30 to 35 cm in length, the next layer at 42 to 49 cm, and so on. The lower layers represented hexagons several meters across.
 The firing patterns seemed to reflect the distance from the wall or the edge of an enclosure. In 2008, another long sought out cell was discovered- the speed cells. The firing rates of these cells increased in proportion to its running speed. These cells were believed to provide the grid cells updated information on the rodent’s position. It was observed that the place cells in the hippocampus rapidly assumes a new location to fire as soon as the rat was put in a new enclosure. However, the grid cells was found to fire at analogous positions in the new enclosure. The grid cells, in some sense, formed a coordinate system that did not change from one enclosure to the other. The firing patterns from the entorhinal cortex was imported to the hippocampus and used to link the place cells to a particular location. It is now believed that the hippocampus stores not just the position, but also the events that occur at that particular place. Particulars about an event are fused with the coordinates and are laid down in the animal’s memory.
However, the scientific world is still pretty much in the dark as to how this information is used by the rest of the brain’s systems or the evolutionary origins of this intricate mechanism. The location systems of the brain and the mechanisms of memory formation will undoubtedly be a fascinating area of research for many years to come.
comments powered by Disqus


Overview of Marijuana Law
There is both a federal marijuana law and state marijuana law. The Controlled Substances Act (CSA) and the Cole Memos are the foundation of federal marijuana law. The Oregon Medical Marijuana Act (OMMA) and Ballot Measure 91 (2014) are the two major state marijuana laws of Oregon.
Controlled Substances Act
The CSA regulates the manufacture, distribution, possession and use of controlled substances. The CSA creates five Schedules to classify controlled substances; Schedule I is the most controlled and Schedule V is the least.
Schedule I drugs have a high potential for abuse and no currently accepted medical use in the United States. The CSA lists marijuana as a Schedule I drug. Other Schedule I drugs include heroin and LSD.
Cole Memos
The Cole Memos are a series of memos written by Deputy Attorney General James M. Cole. They provide guidance to federal prosecutors on the enforcement of the CSA with the passage of medical or recreational marijuana legalization in some states.
Trending Downward
As we got further and further away, it [the Earth] diminished in size. Finally it shrank to the size of a marble, the most beautiful you can imagine. That beautiful, warm, living object looked so fragile, so delicate, that if you touched it with a finger it would crumble and fall apart. Seeing this has to change a man.
2015 Marijuana Legislation
In 2015, the Joint Committee on Implementing Measure 91 (Committee) and Legislative Assembly passed several bills relating to marijuana. The bills that passed into law made significant changes to the OMMA, Measure 91 or both. The bills also changed criminal enforcement law and expunction of marijuana crimes.
While not intended to be exhaustive, the list below outlines the major changes in marijuana law enacted by the 2015 Legislative Assembly.
Placeholder text by Space Ipsum. Photographs by NASA on The Commons.


The data powering these modules comes from
here
Download the scripts and templates to make these modules on our
github
Choose a State:
Past 7 days data
Total Cases
Start Date:
End Date:
Plot
Past 7 Days
Past 30 Days
Compare States
State-1
State-2
Start Date
End Date
Compare States
Related Media


JOHN: Hey, folks. So –
JOANNA: So we’re really excited that you’re here, we’re going to be talking about accessibility media, and we’re not going to be talking at you for a whole hour, so don’t worry. We’re going to talk for maybe five minutes to set the tone for what we mean by accessibility, what we think about it, and how we should be thinking about it, and then splitting up into groups, and then coming back and talking about the groups.
So I guess I’ll introduce myself first, I’m Joanna S. Kao, I work at the FT, along with John Burn-Murdoch. And I think we’re going to start by maybe having everyone around the room say your name and what you do. Maybe start here.
JOHN: You can say where you work if you want to, but main thing is who you are and what you generally consider your job to be.
JOANNA: Yeah, and if you don’t want to be transcribed, just say off the record, and our wonderful transcriber wil transcribe it.
JOHN: So in that context, I’m John, and I’m data visualization journalist, so dealing with audios and visuals.
PARTICIPANT: I’m Dana, I’m an interactive designer from Dallas.
PARTICIPANT: I’m Brittany, I am a developer with the interactive graphics team at Bloomberg.
PARTICIPANT: I’m a graphics developer craft team.
PARTICIPANT: I work for a tech organization called smart Chicago where I combine a program usability.
PARTICIPANT: I’m Taylor with the news fund, we have a internship program but my job is all things creative for the Web, social media, and programs.
PARTICIPANT: I’m Katie, journalist.
PARTICIPANT: I’m an intern, I work with a lot of customer support.
PARTICIPANT: I’m robin, I work with Joanna special projects.
PARTICIPANT: I work at the Texas tribe union on data visuals.
PARTICIPANT: I’m Brian, I run a website at New York Times.
JOANNA: Around here.
PARTICIPANT: I’m Audrey, I’m a news apps developer for the Seattle times.
PARTICIPANT: Hi, I’m Sharice, I’m an interactive media producer at ESPN undefeated in Washington D.C.
PARTICIPANT: I’m Alex, I’m a developer and coding instructor from Omaha.
PARTICIPANT: I’m judge of the law I can’t, I do design and Web development for the institute of nonprofit use.
PARTICIPANT: I’m Sarah, I edit for data graphic visuals at data media group.
PARTICIPANT: I’m Sam, and I work for NBC and MSNBC, and I do data recording.
PARTICIPANT: I’m Stephanie, I manage a team of engineers and customer support.
PARTICIPANT: I’m Helga, I’m a special media producer at the Seattle times.
JOHN: Awesome and two that just joined us.
PARTICIPANT: I work at fusion, I work as an engineer.
PARTICIPANT: I’m Steve. I’m the investigative and director manager editor.
JOHN: Cool.
JOANNA: Sounds like we have a really diverse group of people that do a lot of different things. So that should work out really well when we break out.
JOHN: So sorry. That wasn’t purely to make everyone stand out. Just to get an idea of our specialties and stuff.
JOANNA: So basically our session, we’re just going to spend a couple of minutes talking about what accessibility is, what our definition is, so we can kind of set the tone for what your conversation’s going to be like. We’re going to break out into groups and talk about within different design developments or social media or content, or how you guys want to break up of different issues of accessibility that we see in our news organizations, either as a connoisseur or someone working in news. We’re going to talk about it and then second session we’re going to talk about solutions we’ve found or solutions that other people have talked about and that’s mostly it.
We will at the end of this—at the end of this talk, we have a mailing list that we’ve set up. So for people who are interested in talking—continuing to talk about accessibility and media particularly in journalism, and stay in touch and also like to share resources. At your tables, you guys should have a sheet of resources and tips. So if accessibility is something you’ve never thought about before, you can look there to get a sense of are what are some of the prompts and questions you can be thinking about. Otherwise take it home, or you can also find it online at our GitHub interactive.GitHub/accessibility.
JOANNA: We both tweeted it out. So if you follow us on tweeter, you’ll find it there.
JOHN: Et cete.
Cool. Yeah, so to save everyone, now I’m going to go through a very overview of what accessibility is or at least what—the difference between what what—the terms of accessibility is audio, visual, and ability and the issues they might throw up. So you can’t read it on a screen if you’re a screen reader or podcast you can’t actually see. And to give you an idea of the numbers of people affected by that, about 15% of people in America have some kind of auditory ability issue, which means they can’t hear either at all or properly.
2 or 3% of all U.S.—the whole U.S. population has visual impairment whether that’s complete blindness, an ability to recognize, contrast, or colorblindness. But if you look at people age of over 65, that goes to 7 or 8%. So coming from the Financial Times where most of our readers are that kind of age. Something we have to be particularly worried about. And then, yea. Essentially so those are the core physical ability groups that most people think about, when they think about accessibility. But the key thing we’re trying to say is that actually extends—accessibility extends far beyond that.
 In that environment, there’s an accessibility there that’s affecting you. Similarly there might be something you have a coffee in one hand, and you’re trying to tap the phone screen with the other one and the tap bar is too small. That’s another one.
Really simple one. Think about when you’re designing something for a mobile phone rather than for desktop. That’s an accessibility issue. You may just think about it as a core part of your design process, but it’s an accessibility issue. It’s about making sure that people in certain scenarios and environments are able to access your journalism easier.
And even that is still thinking about quite technical terms. So there’s a really, really great series on the foundation website at the moment about much more diverse meaning of accessibility. So translation.
If you’ve written a piece which has very important insights in it for people from a country that for most of us here going to be a country where people don’t necessarily speak English, translating that not necessarily Google translate, again, is a accessibility. So that people watching the story can understand it fully.
You can even go into the representation of different communities in stories. How do you make this story accessible to someone who isn’t necessarily empathetic and the people using the story. So interviewing people from minorities and that kind of thing to make sure that a person from a minority is reading a piece can more easily register what you’re writing.
So, yeah, there’s huge realms of stuff on accessibility comes into play, and hopefully that gives you an idea of examples of an issue, what exactly we’re talking about.
JOANNA: So do you guys have any questions, first of all, before we kind of break up into groups? No? Okay.
So we’re going to try to break you guys up into groups either by what you can on or what you’re interested in. Hopefully in the sense you’ll be able to take back what you guys talk about as a group back to your newsrooms. So off the top of our heads, we were thinking of design group, develop worker, social media group, and audio and video group. And then people who work on product or QA. Does that seem—is there someone in here who doesn’t feel like they could pick one of those five groups? Awesome. Okay. So let’s try to do—let’s do like a design table here, let’s do a developer table here, social media table back there, what else?
JOHN: Product.
JOANNA: Product QA, like, there. So if you’re a manager, maybe try to do the product QA group.
JOANNA: Feel free to switch around if you need to.
JOANNA: Okay. So we’re going to spend about ten minutes in the first small group talking about issues of accessibility that you’ve seen within your categories. So this is kind of the design developer group, behind there is project manager—product team, project manager, QA, and social media. Talking about some issues that you’ve seen in your own work and also issues you’ve seen as a consumer of news. You can actually take inspiration also from news, you can take it from fear or museums or education. But, yeah, we’re just going to give you about ten minutes. So when it turns 4:23, we’re going to come back and talk about what you guys have discussed. If you have nothing to talk about, we have tips in the resource sheet, so you can start there. Otherwise, go for it.
[Group collaboration]
JOANNA: So we’re going to take five minutes to talk about what you guys talked about in your groups. The purpose is to share the differences in your own groups and then the second breakout session is going to be talking about some solutions.
So let’s start, who wants to start?
JOHN: We’ll start here. Should we do group by group or one by one?
JOANNA: By group.
JOHN: So give us –
PARTICIPANT: So we have, like—yeah, a lot. Like, three whole sheets. We’ll go through a couple of them I guess. The fact that because there’s a lack of awareness or knowledge of the issue, it doesn’t really come up in planning meetings around when we make new products or stories basically. We have discussion about if you have okay. Well, what’s your responsibilities to the subscriber in accessibility issues.
Text formatting is a big pet peeve for a lot of us includi low contrast of light.
JOHN: Anything about your background.
PARTICIPANT: Yeah.
JOHN: Cool. Let’s get started.
JOANNA: We’ll go to the social media group.
JOHN: Social mediaish group. Issues that came up?
PARTICIPANT: Yeah. Well, we talked a lot about two of us, at least two of us have angry tweets—spreading to the culture that we’re not a trustworthy site or newsworthy organizati let them read our stuff or it should be free or we can find the news elsewhere. But also a cultural problem because a lot of times coworker or superiors don’t see the necessity of social media and how things are changing. So it’s kind of, like, navigating that and teaching them why this is important and how to think differently about it and that kind of thing.
JOHN: Cool.
JOANNA: You want to go?
PARTICIPANT: We discussed a lot of things too. I’m going to say one thing that we discussed w accessibility for people who were visually impaired or hard-of-hearing. And how they are able to access things.
We also talked about—oh, I guess—well, this is like a we thing but a must in this culture now. Mobile responsive design.  Like, how do you—how do you explain sense of urgency that this is an accessibility issue for the majority of the people who, you know, you’re catering to.
PARTICIPANT: One other thing I guess is the lack of knowledge all together about what these people need. I don’t know what a screen reader looks like. And we can use plugins and things but is that real? Is that going to be an accura representation of what’s happening? Can I go out and find someone in the world who uses those and needs them? We don’t do that enough, and it’s not something that we really do.
PARTICIPANT: Also, like, on the website incorporating interactive developments or, for example, video. And we’ve seen a lot more companies use closed captions because sometimes—just normal person doesn’t have the capability of like being on the train and a really loud version of someone talking, you kno? They prefer to read it. So that—I mean just being aware of, like, where your –
PARTICIPANT: Even questioning how much your activity should be, like, translated from desktop to mobile. And at this point not in an accessible way. Just better ways using your fingers instead of a mouse and have a smaller screen. Just –
JOANNA: The last group.
PARTICIPANT: We were talking about something similar too because we’re design and development. But in addition, sometimes people will set their own for not size in the browser, so not turning off the ability to zoom on mobile or using the recommended set of pixels to allow people to do that.
And then also another one that we should take into account more is no JavaScript or, like, allowing people to have ad blockers to, you know, some people turn off data on their plans because they don’t have data plans.
PARTICIPANT: The content is not accessible.
PARTICIPANT: Graphics, nontaxonomies.
JOANNA: Awesome. It sounds like you guys talked about a lot of different things.
JOHN: That was awesome. Amazing stuff there. A. I think there’s an interesting point raiseddish about how closed-captioning is becoming bigger and bigger thing and how it’s funny or not funny how that seems to be happening, but it can affect more normal people. But this wasn’t something people particularly focused on until it was, like, yeah, I’m in the train in the morning and I can’t hear something. It’s just funny that’s the classic thing we fix until the project manager is, like, yeah, you’re right all along. We should do something about this.
Until about five minutes before the session started, we realied that the for not size wasn’t suitable on our tip sheet as well.
JOANNA: Yeah, so we just want to move into another ten minutes where you guys will talk within your groups about some of the solutions to some of the issues that you guys have been raising. So the solution that you guys have been doing at your own news organizations or some solutions that you’ve seen other people do. I would encourage you guys to be looking at that side of the news as well because the news industry often doesn’t—isn’t at the forefront of accessibility, but others are. So I think we’re going to let you guys talk for ten minutes. Does anyone have any questions before we break off again?
JOHN: And by all means, think about solutions that have come up and problems you’ve dealt with accessibility.
Cool. Ten minutes on that.
[Group collaboration]
JOHN: Let’s start with this table this time.
JOANNA: What was something you guys talked about as a group?
PARTICIPANT: One of the last things of rendering content including the page. So just load the content and pulling the content from the server. So that’s one. And also a benchmark, the si. And different performance, JavaScript and CSS.
PARTICIPANT: And also nontechnical levels, having check with things, projects to have easier at the beginning but also at the end to address all of these points.
JOHN: Cool. And to you guys.
PARTICIPANT: One of the things I thought sort of more accessible ways for everyone to present especially data stories. Like look three times to get to things. It shouldn’t be a puzzles or something. We should make it clear instead of having it really complicated, like, map that has dots. We should just fling it out in a more accessi and not putting it out to the viewer to do the work.
PARTICIPANT: Certain plugin and tool that you can use if you know something’s accessible to somebody.
PARTICIPANT: So, like, priorities that seem to be the—use the tools. And then a large for around, like, using the CLS to send content to the users to record, like, what they should be doing. So have hard checks on th CMS prevent or software.
We also had some ideas around making people feel the pain. So—what was it?
[Laughter]
PARTICIPANT: I didn’t say poke. It was someone else.
PARTICIPANT: I said poke.
PARTICIPANT: We became more structured of the same way you do device testing. Do, like, mandatory, like, colorblindness and, like, no volume on the computer and low contrast, make the font really small.
PARTICIPANT: Put headphones on them, start shaking them as they’re trying to read. Do everything ann
JOHN: This will be good.
[Laughter]
PARTICIPANT: Something I learned in groups is that Google does a little bit preferencal treatment for that. Users care about it.
PARTICIPANT: Yeah. We also talked a little bit about other programs that have—we’re not doing it, having indicators of we have with this type of program. So we’re not doing it, but there’s a clear path to help.
JOANNA: How big the social group?
PARTICIPANT: So we were talking about—so the problem for us is some of the ideas the user trying to engage the and years also being anti rather than holding the story and getting more out of the story to hold your trust and engagement.
PARTICIPANT: I’m sorry I know this is social media. It’s actually something that happened. So apparently a lot of people do have content, put it out there into the world, people want to share it, but they don’t want to take the time to share it. It’s just inconvenient for them to retweet. So there’s tools that could be use to click the tweet. Like, an e-mail blast or something like that and they don’t care about it.
JOANNA: Does anyone have any thoughts on anyone else’s group?
PARTICIPANT: I just had one thing. On the client server side is good. On the client server side, I think a lot of the visualizations is interactive, more complex nonwords idea has been done on the blind side in the past purchase and there’s more ways to move to the server to render a lot of what we’ve done, and I think a little bit especially for that.
So I think moving more over to the server I think will allow us to more advance work and –
JOHN: D3 add-on, which if you’ve got large loads of data –
PARTICIPANT: Yeah. And we have one at NBC news, we’ve sort of open sourced, and we’re working with that as well.
JOHN: Awesome. Cool.
JOANNA: We’ve got nine minutes left. So mostly just wanted to wrap up and talk about how we bring all of these ideas forward. So the tip sheet is online. So feel free to—also on GitHub. So if you want to add things to it, we have a list of resource at the end, so if this organization has accessibility guidelines or blog post about it, feel free to add a poll request so that we can add to the tip sheet and also on the tip sheet, there’s a link to join the mailing list. Hopefully throughout the mailing list, we’ll be sharing solutions or ideas that we had on that that we’ve seen. And hopeful we’ll be able to get those solutions out.
JOHN: Yeah, the main part as well as on the tip sheet. We’ll try without stopping you as much as possible. So, yeah. And stuff develops on this. Really maybe initiative is that it would be great to hear this stuff developing and successful.
So cool. Yeah. Thanks for coming.
[Applause]


Planarity testing
Two functions help test if a graph is planar. The algorithm is the Boyer-Myrvold planarity tester.
K5 = clique_graph(5); test_planar_graph(K5)
ans = 0
Of course K_5 isn't a planar graph. To get more information about why it isn't planar, we use the boyer_myrvold_planarity_test function.  A Kuratowski subgraph must contract to either K_5 or K_3,3 (a bipartite clique). In this case, the graph was K_5, and so K was the entire graph.
A (planar?) road network
Let's have some fun! Let's look at a road network.
load('../graphs/minnesota.mat'); gplot(A,xy,'.-');
test_planar_graph(A)
ans = 0
What? The road network isn't planar? Let's see what is going on here.
[is_planar K] = boyer_myrvold_planarity_test(A);
gplot(K,xy,'.-');
It looks like there are a lot of tree-like portions. Those shouldn't be the problem, let's remove them.
cn = core_numbers(K);
K2 = K;
K2(cn<2,cn<2) = 0;
gplot(K2,xy,'.-');
We'd better check the graph is still Kuratowski. There's a function called is_kuratowski_graph that does just this task.
is_kuratowski_graph(K2)
ans = 1
Well, that looks more helpful, but I don't see the planarity problem. Now, let's try contracting edges. What the following code does is to look for vertices of degree 2 (pieces of a line) and remove the intermediate vertex. In Matlab it isn't very efficent code, but this graph only has a few edges (~1000) at this point, so it'll be fast enough.
Kcur = K2; rand('state',0); % reset for deterministic results for ntimes=1:20 % compute the degree of all edges d = sum(Kcur,2); % pick an independent set of vertices with degree 2 s = d==2; s = s.*round(rand(size(s))); % randomly pick entries a = Kcur*s; % follow one edge s = s&~a; % remove dependent edges a = Kcur*double(s); fprintf('check for is: %i\n', full(sum(a&s))==0); % verify indep set. % contract the edges for k=find(s)' ns = find(Kcur(:,k)); Kcur(ns(1),ns(2)) = 1; Kcur(:,k) = 0; Kcur(k,:) = 0; end Kcur = Kcur|Kcur'; end % plot the graph after contraction in red gplot(K2,xy,'.-'); hold on; gplot(Kcur,xy,'r.-'); hold off;
check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1 check for is: 1
Ahah, now we see the problem. (Try to untangle the red graph!)
Now that we see the problem, I think it's clear what we should have done from the beginning...
d = sum(K); max(d)
ans = (1,1) 3
The maximum degree is 3, so the subgraph must be isomorphic to K_3,3.
d3= d==3; sum(d3);
That is the problem with the graph, but why doesn't the display show it? Well, it does.
gplot(K2,xy,'.-'); hold on; gplot(Kcur,xy,'r.-'); hold off; xlim([-95.2092 -94.5842]); ylim([ 43.5903 43.7778]);
It looks like there is a vertex of degree 4 in the middle. Unfortunately, that is just 2 paths crossing. Zooming in further, there are actually two vertices there! That's the problem!
And so, here is a problem for you:
Problem, automatically identify the following pairs of vertices as problematic for the planar embedding [2546,2547] [1971,1975] [1663,1666] Find another pair that prevents a planar embedding of the graph.
Planar embeddings
To investigate planar embeddings, let's start with the road network again.
load('../graphs/minnesota.mat');
test_planar_graph(A(1:500,1:500))
ans = 1
Good, we found a planar region!
A = A(1:500,1:500);
xy = xy(1:500,:);
gplot(A,xy,'.-');
Let's compute it's planar embedding
X = chrobak_payne_straight_line_drawing(A);
gplot(A,X,'.-');
Well, that isn't quite as helpful, but now you know how to compute a straight line drawing. The straight line drawing is computed from a maximal planar graph. A maximal planar graph cannot have any additional edges and still be planar.
M = make_maximal_planar(A);
gplot(M,X,'.-');
Conclusion
That's it for our brief tour of planar graph algorithms in MatlabBGL. See the BGL documentation pages on planar graph algorithms for more information.
Planar Graphs in the Boost Graph Library


24 Jul 2016
I recently had a chance to attend RedDot Ruby in Singapore, and I have to say it was an amazing experience in my career. I had never attended a Ruby conf before, but I watched a lot of them online. Getting to meet such great people like Matz, and Aaron Patterson in person was like a dream come true.
If you are interested in the talks given at RedDot Ruby this year, you can check out this great gist that has the videos of all the talks.
When I talked to Matz I thanked him for Ruby and the great community. He is a very down to earth type of guy and extremely friendly. He reminded me of a saying that rubyists have: Matz is nice so we are nice
. That was the point I realised how accurate that is.
Same goes to Aaron, very friendly and nice, plus he has stickers of his cats (haha).
Since all the talks are available online I just want to briefly share about my favourite talks. I should mention that they can get a little bit technical.
First up was Matz’s. He talked about new things and improvements in future Ruby versions.
There are different kinds of typing, for example:
- Strong Dynamic (Ruby)
- Weak Dynamic (Perl, Haskel)
- Strong Dynamic (Hskell)
- Weak Dynamic (C)
There’s a design policy which is duck typing and it’s very important in ruby.
In dock typing we:
- Do not classify
- Do not check types
- We just ask objects to behaves
Static Typing basically lacks flexibility. Some other programming languages offer gradual typing or optional typing, and they are fundamentally static. Ruby wants something that is similar to staic typing (powerful), but it should allow duck typing. For example, GO is a static typed language that allows duck typing. it is called structural subtyping.
Matz calls this soft typing for Ruby. Soft Typing is a type system that is defined by behaviour. Behaviours are sets of methods (and argument types), thus inferred types don’t have names. However, this is still just a concept and a part of Ruby3 project.
Here is what Matz wants for Ruby3:
- Soft typing
- 3 times faster
- Real concurrency
He also talked about Ruby 2.4 and some of it’s changes are listed below:
FixNum / BigNum Unification
There will be no longer fixnum and bigness, just integers. There should not be so many compatibility issues, but if your program cares about the size of integers then you might have some issues.
Smarter Conversions
Some methods like upcase and downcase worked only for ASCII characters. With a lot of people using Unicode, Ruby now handles unicode case mappings. If you want to stick with ASCII you can do .upcase(:ascii)
.
That was it for Matz.
I am now going to cover Aaron’s talk which I really enjoyed. It is about Ruby GC algorithms in MRI. His talk stated as usual with some jokes, and he demonstrated different types of typing with his mechanical keyboard.
What is GC in high level?
You can think of objects as a tree and GC finds nodes in the tree that aren’t referenced from the root anymore and then frees them up. It uses different algorithms to find nodes that are not referenced.
What types of collectors MRI has?
Here is a list:
Mark & sweep
Theres a Mark phase that starts from the root and marks all of the objects, then sweep phase frees everything that is not marked, and at the end we unmark them all.
Pros:
Cons:
- Too slow
- Stops the world
- Visits all the objects everytime
Generational
To improve the speed of Mark&Sweep it divides the objects into old and new gens. Good thing is that this does not visit the old objects everytime and only on full GC. Theres a remembered list to keep track of interesting references such as when an old gen object points to a new gen. This is to avoid bad references.
Pros:
Cons:
- Not as easy:
- Stops the world
Incremental
To get around Stop the World there is Incremental GC. It uses Tri Color Marking:
- White: will be collected
- Black: No reference to white objects, but reachable from root
- Gray: Reachable from root, but not yet scanned.
The way it works is that:
- It picks an object from gray and and moves it to black.
- For each object that the object references, they get moved to black as well.
- Keep repeating this until gray is empty.
A big advantage is it can be interrupted at each step. Each step can be performed incrementally and halt time reduces. Although it has a similar problem with generational, and theres a remembered list to avoid bad references.
In Ruby, GC:
- Is not parallel
- Is not real-time
- Is not compacting
Now as for allocation we have a heap that contains all of our objects. There are big chunks of memory that are called pages and each has a linked list (each page is 16k). They have slots which contains ruby objects (each object is 40bytes). when object is garbage collected it’s taken out from the page.
As a problem there is poor reclamation in the process of GC. When we have a few pages and garbages get collected, objects won’t move to free up pages. We are basically left with some pages that have holes in them. This is one of the areas that Aaron is trying to improve.
As for the last part of the talk, here are some tools to use for inspections:
GC Inspection:
- GC::Profiler.enable
- GC:Profiler.report
Heap Inspection:
- ObjectSpace.dump_all
- ObjectSpace.dump
You can turn on tracing for objects. if you have problems finding where the object came from, you can use that:
That’s it. I hope you enjoyed this post.
07 Jul 2016
I was a big Sublime fan, and I still am. I think it’s a great and powerful text editor. I had used it for more than 4 years but recently I felt that I use too much mouse and I wasn’t very efficient. I wanted to speed up my workflow and was hoping to do less for more. I started looking for improvements and VIM came up in every article that I read so I decided to give it a shot.
I knew VIM just enough to get around files, search for things, and save them. VIM is always my favourite when it comes to reading through massive log files. Apart from that, I never really used VIM for development or anything else.
To start, I found myself a cheat sheet, and installed a few recommended plugins like CTRLP, NERDTree, and ACK. I was good to go.
At the beginning It was extremely hard for me to use VIM. I was constantly reaching for my mouse. I had a hard time focusing on my tasks, and a few times, I just closed VIM, opened Sublime and thought it’s just better to use Sublime.
But I didn’t want to give up, and it was very difficult until I installed MacVIM. I have to admit it really helped me stay in VIM and not switch to Sublime in the middle of my work. The only reason for that in my opinion was that by default MacVIM has some mouse support enabled. I always knew I can enable mouse support in my Iterm2, but I was thinking I shouldn’t. Obviously I was very wrong.
With MacVIM and It’s mouse support, I learned VIM faster and I was always reminding myself to use mouse less. To help myself speed things up I’ve been adding plugins as I find the need for them, and you can see my dot files in my github repo.
It’s been over 30 days now, and Im starting to love how easy I navigate through files and write code in VIM, plus I don’t care much for mouse anymore. I definitely encourage everyone to give VIM a try, it’s life changing!
30 Apr 2016
Analyze and Understand the Problem
This is a very important step to resolve any problem. I often see people skipping this step by jumping right into conclusions, and get caught in a loop with wild guesses.
As the title speaks for itself you need to ANALYZE and UNDERSTAND the problem.
Analyze:
A clear description of the problem.
- What is it? What is it NOT? What things do have the problem?
- Where is it? Where is it NOT?
- When is it occurring? When is it NOT?
- What is the impact on the business?
Understand:
Understand how can the problem occur, and list down what could be wrong. Ask others who also know about the problem (Communicate!).
It’s time for some discovery! In this step you should be searching, reproducing the problem, and gathering as much information as you can. The more information you have the easier you can identify the root cause.
Search:
If its a known problem, try googling the symptoms or the error (if there is any), see if you can find anything that might help you with the issue. If it’s an application you are troubleshooting, start by looking into the logs. Basically use all the channels you can to collect information.
Reproduce the problem:
Try it yourself, see how it is that you get the problem. Pay good attention to details. Try to map your search findings to what you are experiencing and take note.
Get to the root cause:
As you collect enough information you should move forward and try to locate the root cause. Here are three steps that can help you to narrow down the problem.
Possible causes:
Based on the information you’ve gathered you can list down what you think could be causing the problem.
Question what’s happening.
- What’s the differences between the places where the problem is and is not happening?
- Any recent deployments?
- Any environment changes?
- If there are changes, how could they cause the problem?
You might end up with a big list of possible causes. You can divide and conquer.
Divide the problem into a few separate parts, and examine them one by one:
Divide the problem into subproblems, and test each side separately to locate the side with the problem.
You can use fishbone diagrams too. This specially works well when you are doing cause and effect analysis:
Repeat until you isolate the problem. There may be times where you feel you need more information and in my opinion that is fine and it happens. Just go back a step and get more information.
Analyze your findings:
Some questions to ask yourself here:
- How do these causes explain why the problem is happening?
- What are the assumptions?
If you have a few causes here think about which one is the most probable.
Confirm the cause:
Get some additional information to confirm the root cause. Try to get your causes proven/checked. See if it’s possible to isolate the causes and confirming them.
Try fixes:
As you identify the culprit, you should go on and make a change to fix that. But, don’t just make changes and forget about it! You will need to continue and monitor the situation. Some questions to keep in mind:
- Has the fix been successful?
- Do the symptoms still appear?
You will have to repeat the steps above if problem still persists or your changes introduce new problems. It’s good to refer back to your step on identifying the problem. Refer to the diagrams you drew, or your note and check if you missed any thing. This time you have more information, and you already know what you tried did not solve the problem so you can cross something off your list of possible causes.
Go further:
When you get the issue solved, don’t just stop there! Think about how you can imporve the app, process, or whatever it is you were fixing. “Leave the world a little better than you found it.”
24 Feb 2016
Packages
GitGutter
A plugin to show an icon in the gutter area indicating whether a line has been inserted, modified or deleted.
Github repo
GitSavvy
A sublime text 3 plugin to provide basic git functionalities like: init
, add
, commit
, checkout
, pull
, push
.
Github repo
Emmet
It adds HTML, CSS shortcuts. With it’s abbreviations you can quickly generate blocks.
Github repo
Example:
#page>div.logo+ul#navigation>li*5>a{Item $}
with a tab
it becomes:

Item 1

Item 2

Item 3

Item 4

Item 5

Origami
A nice way of dealing with panes as you need them.
Github repo
Enhances the operations on Sidebar of Files and Folders.
Github repo
Material Theme
The most epic theme for Sublime Text 3!
Github repo
BeautifyRuby
Reformats/Reindentes your ruby codes.
Github repo
Sublime Rubocop
It runs Rubocop on your Ruby files in the Editor.
Github repo
Other customisations
Key Bindings
I have two key bindings:
- Toggle SideBar using
Command+\
.
- Toggle Minimap using
Command+shift+\
.
[
{ "keys": ["super+\\"], "command": "toggle_side_bar" },
{ "keys": ["super+shift+\\"], "command": "toggle_minimap" }
]
User Settings
Two settings worth mentioning:
- Trim trailing white spaces on save.
- Changing tab size to two spaces.
[
"trim_trailing_white_space_on_save": true,
"tab_size": 2
]
21 Jan 2016
Once upon a time there was an electrician, and this electrician was a good electrician, and had many customers. He provided a huge range of services, including providing lightbulbs.
One day, one of his customers came to him and asked him for a lightbulb. This surprised the electrician, because he had only finished fitting out this customers house the other day. But knowing that lightbulbs often break without reason, he happily provided this customer with a new lightbulb, and because he was dedicated to providing legendary customer service, threw in a second for free. “There”, he thought to himself, “They won’t need a lightbulb again for a least a month!”. The customer was greatly pleased with his electrician.
Day turned to night and night turned to day, and waiting at the Electricians store the next morning was the very same customer, requesting additional lightbulbs. This truly perplexed our noble electrician, as he knew that while lightbulbs did break, no one could be that unlucky. The electrician handed the customer a replacement pack of lightbulbs and then asked if he could do some ‘on-site testing’, to see what it was about this customer’s house that was causing the lightbulbs to break so quickly. So he followed the customer out to his house and walked into the foyer. He gasped, as he saw numberous bulletholes puncturing the ceiling of the his customers house. Shocked, he asked the customer “What happened? Is everything ok?!”
The customer shot him a perplexed look, “What do you mean?” he said. The electrician, lost for words, could only point to the ceiling. “Oh, I was actually meaning to ask you about that. The lightbulbs you’re selling me are great, but they’re a little small so I keep missing. Do you know any good firearms shops around that could sell me a more accurate gun?” The electrician promptly took his customer over to the wall, and detailed the operation of the light switch to this customer, who was appropriately blown away, and promised livelong gratitude and business to this electrician. Everyone lived happily ever after and there were no more holes in the ceiling.


In the advanced search section, you can combine at most five search criteria, that is, Gene/Gene product, Pathogen, Publication, Screen scope and Phenotype.
{% extends "base.html" %} {% block title %}
In the advanced search section, you can combine at most five search criteria, that is, Gene/Gene product, Pathogen, Publication, Screen scope and Phenotype.


Home
Transactions
Information
Withdraw
Deposit
Point Management
Events
Notice
Game Guide
Bet History
Transaction
History
Bank Name
BPI
Account Number
1234-567-8901
Withdraw Amount
1Won
3Won
5Won
10Won
30Won
50Won
Clear
Deposit
Date
Amount
Status
2020-07-02
Sample Content
Accepted
2020-07-02
Sample Content
Accepted
2020-07-02
Sample Content
Accepted


This page provides help and support for imalogit.com.
Issues and trouble tickets.
When the "Forgot your password?" form asks for your Username, you can enter your email instead. Otherwise, contact us.


I helped to design the prototype app for
Ceres, a digital health platform and finalist in the
Chicago Booth Social New Venture Challenge (SNVC).
I implemented the Ceres client protocol, a real-time chat system using Firebase, and a nearby clinic search function using Google's Maps SDK.


fun startDiscovery(callback: DiscoveryCallback): Unit
Starts searching for advertisers Called on the phone to configure the advertiser
callback - : DiscoveryCallback. Used by the discoverer to manage all the steps of the process
callback


Information Broker Bavarin:
So, this is the ice crystal that I've heard so much about! Well, hand it over!
"Here you go."


UK PM Johnson's lead over Labour narrows slightly: Deltapoll
LONDON (Reuters) - Prime Minister Boris Johnson’s lead over the opposition Labour Party has narrowed slightly ahead of Britain’s Dec. 12 national election, an opinion poll by Deltapoll for the Mail on Sunday newspaper showed on Saturday.
Support for Johnson’s Conservative Party stood at 43%, down two percentage points from last week, while Labour was unchanged at 30%. The pro-European Liberal Democrats rose five points to 16%, the poll showed.
(Corrects date of election in first paragraph.)


Toggle navigation
Bob Dylan Lyrics
Downloads
All Songs
All Albums
1960s
Bob Dylan (1962)
The Freewheelin' Bob Dylan (1963)
The Times They Are A-Changin' (1964)
Another Side of Bob Dylan (1964)
Bringing It All Back Home (1965)
Highway 61 Revisited (1965)
Blonde on Blonde (1966))
Bob Dylan's Greatest Hits (1967)
John Wesley Harding (1967)
Nashville Skyline (1969)
1970s
Self Portrait (1970)
New Morning (1970)
Bob Dylan's Greatest Hits, Vol. II (1971)
Pat Garrett & Billy the Kid (1973)
Dylan (1973)
Planet Waves (1974)
Before the Flood (1974)
Blood on the Tracks (1975)
The Basement Tapes (1975)
Desire (1976)
Hard Rain (1976)
Street-Legal (1978)
Bob Dylan at Budokan (1979)
Slow Train Coming (1979)
1980s
Saved (1980)
Shot of Love (1981)
Infidels (1983)
Real Live (1984)
Empire Burlesque (1985)
Biograph (1985)
Knocked Out Loaded (1986)
Down in the Groove (1988)
Dylan & the Dead (1989)
Oh Mercy (1989)
1990s
Under the Red Sky (1990)
The Bootleg Series Volumes 1-3 (Rare & Unreleased) 1961-1991 (1991)
Good As I Been to You (1992)
World Gone Wrong (1993)
Bob Dylan's Greatest Hits Volume 3 (1994)
MTV Unplugged (1995)
Time Out of Mind (1997)
The Bootleg Series Vol. 4: Bob Dylan Live 1966, The "Royal Albert Hall" Concert (1998)
2000s
The Essential Bob Dylan (2000)
Love and Theft (2001)
The Bootleg Series Vol. 5: Bob Dylan Live 1975, The Rolling Thunder Revue (2002)
The Bootleg Series Vol. 6: Bob Dylan Live 1964, Concert at Philharmonic Hall (2004)
The Best of Bob Dylan (2005)
Modern Times (2006)
Together through Life (2009)
2010s
Tempest (2012)
L
Last Thoughts on Woody Guthrie
(appeared on
The Bootleg Series Volumes 1-3 (Rare & Unreleased) 1961-1991 (1991)
)
Lay Down Your Weary Tune
(appeared on
Biograph (1985)
)
Lay Lady Lay
Version #1
(appeared on
Nashville Skyline (1969)
,
Bob Dylan's Greatest Hits, Vol. II (1971)
,
Biograph (1985)
, and
The Essential Bob Dylan (2000)
)
Version #2
(appeared on
Before the Flood (1974)
)
Version #3
(appeared on
Hard Rain (1976)
)
LayQ Lady Lay
(appeared on
The Best of Bob Dylan (2005)
)
Lenny Bruce
(appeared on
Shot of Love (1981)
)
Leopard-Skin Pill-Box Hat
Version #1
(appeared on
Blonde on Blonde (1966)
)
Version #2
(appeared on
The Bootleg Series Vol. 4: Bob Dylan Live 1966, The "Royal Albert Hall" Concert (1998)
)
Let It Be Me
(appeared on
Self Portrait (1970)
)
Let Me Die in My Footsteps
(appeared on
The Bootleg Series Volumes 1-3 (Rare & Unreleased) 1961-1991 (1991)
)
Let's Stick Together
(appeared on
Down in the Groove (1988)
)
The Levee's Gonna Break
(appeared on
Modern Times (2006)
)
License to Kill
Version #1
(appeared on
Infidels (1983)
)
Version #2
(appeared on
Real Live (1984)
)
Life Is Hard
(appeared on
Together through Life (2009)
)
Like a Rolling Stone
Version #1
(appeared on
Highway 61 Revisited (1965)
,
Bob Dylan's Greatest Hits (1967)
,
Biograph (1985)
,
The Essential Bob Dylan (2000)
, and
The Best of Bob Dylan (2005)
)
Version #2
(appeared on
Self Portrait (1970)
)
Version #3
(appeared on
Before the Flood (1974)
)
Version #4
(appeared on
Bob Dylan at Budokan (1979)
)
Version #5
(appeared on
The Bootleg Series Volumes 1-3 (Rare & Unreleased) 1961-1991 (1991)
)
Version #6
(appeared on
MTV Unplugged (1995)
)
Version #7
(appeared on
The Bootleg Series Vol. 4: Bob Dylan Live 1966, The "Royal Albert Hall" Concert (1998)
)
Lily of the West
(appeared on
Dylan (1973)
)
Lily, Rosemary and the Jack of Hearts
(appeared on
Blood on the Tracks (1975)
)
Little Maggie
(appeared on
Good As I Been to You (1992)
)
Little Sadie
(appeared on
Self Portrait (1970)
)
Living the Blues
(appeared on
Self Portrait (1970)
)
Lo and Behold!
(appeared on
The Basement Tapes (1975)
)
Lone Pilgrim
(appeared on
World Gone Wrong (1993)
)
Lonesome Day Blues
(appeared on
Love and Theft (2001)
)
The Lonesome Death of Hattie Carroll
Version #1
(appeared on
The Times They Are A-Changin' (1964)
and
Biograph (1985)
)
Version #2
(appeared on
The Bootleg Series Vol. 5: Bob Dylan Live 1975, The Rolling Thunder Revue (2002)
)
Version #3
(appeared on
The Bootleg Series Vol. 6: Bob Dylan Live 1964, Concert at Philharmonic Hall (2004)
)
Long and Wasted Years
(appeared on
Tempest (2012)
)
Long Distance Operator
(appeared on
The Basement Tapes (1975)
)
Lord Protect My Child
(appeared on
The Bootleg Series Volumes 1-3 (Rare & Unreleased) 1961-1991 (1991)
)
Love Henry
(appeared on
World Gone Wrong (1993)
)
Love Minus Zero/No Limit
Version #1
(appeared on
Bringing It All Back Home (1965)
)
Version #2
(appeared on
Bob Dylan at Budokan (1979)
)
Version #3
(appeared on
The Bootleg Series Vol. 5: Bob Dylan Live 1975, The Rolling Thunder Revue (2002)
)
Love Sick
(appeared on
Time Out of Mind (1997)
)


| 063:005 Khan | : |
And when it is said to them: "Come, so that the Messenger of Allah may ask forgiveness from Allah for you", they turn aside their heads, and you would see them turning away their faces in pride. |
| 063:005 Maulana | : |
And when it is said to them: Come, the Messenger of Allah will ask forgiveness for you, they turn away their heads and thou seest them hindering (others), and they are big with pride. |
| 063:005 Pickthal | : |
And when it is said unto them: Come! The messenger of Allah will ask forgiveness for you! they avert their faces and thou seest them turning away, disdainful. |
| 063:005 Rashad | : |
When they are told, "Come let the messenger of GOD pray for your forgiveness," they mockingly turn their heads, and you see them repel others and act arrogantly. |
| 063:005 Sarwar | : |
When they are told, "Come and let the Prophet of God seek forgiveness for you," they shake their heads and you can see them arrogantly turning away. |
| 063:005 Shakir | : |
And when it is said to them: Come, the Messenger of Allah will ask forgiveness for you, they turn back their heads and you may see them turning away while they are big with pride. |
| 063:005 Sherali | : |
And when it is said to them 'Come, that the Messenger of ALLAH ask forgiveness for you,' they turn their heads aside, and thou seest them holding back disdainfully while they are big with pride. |
| 063:005 Yusufali | : |
And when it is said to them, "Come, the Messenger of Allah will pray for your forgiveness", they turn aside their heads, and thou wouldst see them turning away their faces in arrogance. |
Concepts/Themes Covered: الإيمان > الإيمان بالله > الاستغفار Faith> Belief In Allah> Asking Allah for Forgiveness الإيمان > الإيمان بالله > النفاق Faith> Belief In Allah> Hypocrisy
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


This is my
HTML
Fundamentals Document in a span.
This is my HTML Fundamentals Document in a div.
Name:
V1
V2
V3
V4


Consumes the networking and websocket states and delta counts and updates the device LED accordingly. Inherit this class and override the methods to customize the behavior.
More...
#include <sensesp/system/system_status_led.h>
Consumes the networking and websocket states and delta counts and updates the device LED accordingly. Inherit this class and override the methods to customize the behavior.
Definition at line 15 of file system_status_led.h.
◆ SystemStatusLed()
| sensesp::SystemStatusLed::SystemStatusLed |
( |
int |
pin | ) |
|
◆ set_input() [1/2]
| void sensesp::SystemStatusLed::set_input |
( |
int |
new_value, |
|
|
uint8_t |
input_channel = 0 |
|
) |
| |
|
overridevirtual |
Used to set an input of this consumer. It is usually called automatically by a ValueProducer.
- Parameters
-
| new_value | the value of the input |
| input_channel | Consumers can have one or more inputs feeding them. This parameter allows you to specify which input number the producer is connecting to. For single input consumers, leave the index at zero. |
Reimplemented from sensesp::ValueConsumer< int >.
Definition at line 85 of file system_status_led.cpp.
◆ set_input() [2/2]
| void sensesp::SystemStatusLed::set_input |
( |
SystemStatus |
new_value, |
|
|
uint8_t |
input_channel = 0 |
|
) |
| |
|
overridevirtual |
Used to set an input of this consumer. It is usually called automatically by a ValueProducer.
- Parameters
-
| new_value | the value of the input |
| input_channel | Consumers can have one or more inputs feeding them. This parameter allows you to specify which input number the producer is connecting to. For single input consumers, leave the index at zero. |
Reimplemented from sensesp::ValueConsumer< SystemStatus >.
Definition at line 59 of file system_status_led.cpp.
◆ set_wifi_disconnected()
| void sensesp::SystemStatusLed::set_wifi_disconnected |
( |
| ) |
|
|
protectedvirtual |
◆ set_wifi_no_ap()
| void sensesp::SystemStatusLed::set_wifi_no_ap |
( |
| ) |
|
|
protectedvirtual |
◆ set_wifimanager_activated()
| void sensesp::SystemStatusLed::set_wifimanager_activated |
( |
| ) |
|
|
protectedvirtual |
◆ set_ws_authorizing()
| void sensesp::SystemStatusLed::set_ws_authorizing |
( |
| ) |
|
|
protectedvirtual |
◆ set_ws_connected()
| void sensesp::SystemStatusLed::set_ws_connected |
( |
| ) |
|
|
protectedvirtual |
◆ set_ws_connecting()
| void sensesp::SystemStatusLed::set_ws_connecting |
( |
| ) |
|
|
protectedvirtual |
◆ set_ws_disconnected()
| void sensesp::SystemStatusLed::set_ws_disconnected |
( |
| ) |
|
|
protectedvirtual |
◆ blinker_
The documentation for this class was generated from the following files:


|
Gas ChamberWhen citizens go astray, society responds with punishment.   Falling between the electric chair and lethal injection, the gas chamber was an American innovation. Before the 20th Century, The American Way consisted of either shooting people or hanging them. Neither method was particularly tidy, especially hanging, which had a tendency to get out of hand. If everything wasn't just perfect, a victim could take hours to strangle to death. If you made an error in the other direction, their heads could rip off. Cyanide gas had been used as a pesticide during the 19th century, and several states began examining its use for execution. Nevada and Arizona were neck-and-neck in the race to execute the first inmate with gas, but Nevada won out in a photo finish. The first American to go under the gas was Gee Jon, a Chinese immigrant accused of a gang-related slaying. Initially, the plan was to pump poison gas into his jail cell while he slept, but the gas dissipated and Jon remained inconveniently alive. Plan B was quickly implemented -- the construction of a sealed chamber to keep the gas and the inmate all in one place until the end came. Inside the chamber, a bucket of sulfuric acid rests below the chair to which the inmate is strapped. The executioner throws a switch, which drops crystallized cyanide into the acid. As the crystals dissolve, poison gas is released into the air. Death typically takes less than 20 minutes. Witnesses to the Jon execution agreed that it was the most humane execution they'd ever seen, and several other states rushed to build gas chambers. Most of the chambers were built by an Arizona metal products company. In addition to Arizona and Nevada, lethal gas was authorized as a method of execution in California, Colorado, Maryland, Mississippi, Missouri, New Mexico, North Carolina, Oregon and Wyoming. Unfortunately, one execution does not represent a scientific sampling of the method's effectiveness. In part, the humaneness of the gas chamber depends on the cooperation of its victims. Cyanide gas can be a very humane way to kill someone, as long as they aren't fighting it. When an inmate chose to resist, however, things could get pretty ugly, and the biological imperative to stay alive is no small thing. A more typical gas chamber execution involved the inmate attempting to hold his or her breath and struggling against his or her bonds. It's one thing to hold your breath as part of a temper tantrum; it's quite another to hold your breath when your life literally depends on it. Over the years, witnesses saw the chamber's inmates turn various shades of red, blue and purple while trying not to breathe. Many were wracked with convulsions. Their faces became hideously contorted, either from horror or as a result of seizures induced by the gas shortly before death. (Eventually, some states began hooding prisoners to spare the witnesses this sight.) Inmates sometimes foamed at the mouth, or soiled themselves. In a precedent-setting Supreme Court case on whether the gas chamber was "cruel and unusual," a doctor from Johns Hopkins University offered the following description of what the gas chamber experience is like: The person exposed to this gas remains conscious for a period of time, in some cases for several minutes, again depending on the rate and volume of the gas that is inhaled. During this time, the person is unquestionably experiencing pain and extreme anxiety. The pain begins immediately, and is felt in the arms, shoulders, back, and chest. The sensation is similar to the pain felt by a person during a heart attack, where essentially, the heart is being deprived of oxygen. The severity of the pain varies directly with the diminishing oxygen reaching the tissues. Other witnesses in the case provided more colorful accounts: The pellets of cyanide were released by mechanical controls, and dropped into an acid jar beneath the chair. The gas rose, and seemed to hit him immediately. Within the first minute, [he] slumped down. I thought to myself how quickly cyanide really worked. Within 30 seconds he lifted his head upwards again. He raised his entire body, arching, tugging at his straps. Saliva was oozing from his mouth.  He gazed through my window. His fingers were tightly gripping his thumbs. His chest was visibly heaving in sickening agony.  Then he slumped forward. Still his heart was beating. It continued for another several minutes. Nevertheless, the gas chamber took on a certain cachet going into the 1930s. The efficiency of the method appealed to Adolf Hitler.  But efficiency was one of the Third Reich's claims to fame, and they soon realized that gas could be used to execute several people at once, with little mess and without the victims even knowing what was happening. The Nazi gas chambers began operating in 1941 and continued through 1944. More than 1 million Jews were estimated to have been gassed at Auschwitz alone. Gas chambers were usually disguised as showers. Inmates were sent into the chambers on the pretext of being cleaned or deloused, then poison gas was pumped in through the ventilation system, or released from within a sealed grate in the room. Auschwitz used mostly cyanide-based gases (in combination with other pesticides). Other camps used carbon monoxide exhaust fumes to suffocate their victims. The discovery of Nazi death factories after World War II took some of the luster away from the humanity of the gas chamber, but the real problem was the vomiting, spasms and contortions. Officials and witnesses to executions began to increasingly suspect that poison gas was not as quick and painless as initially thought. As if the Nazi taint wasn't bad enough, a series of high-profile gassings gone bad provided more grist for the mill. In one case, a severely disabled killer worked his hands free from the chair, screaming loudly as he tried to bat the gas away. Another inmate slit his own throat just before being taken to the chamber; the guards strapped him down and gassed him anyway. Several individual cases also raised doubts for many. Barbara Graham, a woman of "low moral character," was executed in the California gas chamber. An elderly woman had been beaten and suffocated during a jewelry theft by Graham and three male accomplices. One of the men turned states evidence and testified that Graham had killed the woman; the other three members of the gang were sentenced to die. Graham's case attracted a fair amount of attention, because of her gender, an unhappy childhood and the fact that she was (somewhat improbably) accused of pistol-whipping an elderly woman to death. (She would have been eligible for the death penalty even if one of the men had done the deed, but it's debatable whether she would have received such a sentence without the allegation against her.) Graham's story was loosely adapted into an anti-death penalty movie called I Want To Live!, which did present a pretty accurate picture of a trip to the gas chamber. Graham's story was part of a rising tide against the death penalty in general. Another inmate who ended in the gas chamber, Caryl Chessman, created a huge wave of sentiment against capital punishment by embarking on an aggressive P.R. campaign from death row. Chessman was not a nice guy by even the most liberal standards. He was charged with kidnapping and raping young women in the Los Angeles area, a death penalty offense in California. Chessman confessed to the crime when arrested, but later said his confession had been coerced by police brutality. Chessman insisted on representing himself during his trial with predictable results -- he received two death sentences. During more than 10 years on death row, his execution was stayed eight times, and he wrote four popular book-length accounts of his own innocence, including Cell 2455: Death Row, a best-seller later adapted into a movie. Chessman claimed he knew the real identity of the kidnapper but said his loved ones had been threatened with retribution if he disclosed the name. A rainbow coalition of celebrities (from Aldous Huxley to Billy Graham) petitioned for Chessman's sentence to be commuted, but he went to the chamber in 1960. As Chessman was led into the gas chamber, he issued a final declaration that he was innocent of the crimes for which he was being executed. A possibly apocryphal story states that the governor's secretary attempted to call with a ninth stay of execution based on new evidence, but she misdialed the number on her first try, and the gas had already begun to flow. Chessman told reporters he would nod his head in the chamber if the experience was painful. After vomiting up his breakfast and emptying his bowels, Chessman nodded his way into oblivion shortly after 10 a.m. on 3 May 1960. The tide of public opinion was turning sharply against the death penalty by the mid-1960s. Between 1967 and 1977, a combination of public opinion and court rulings brought executions in the U.S. to a virtual standstill. When executions resumed, it was at a slower pace and with new methods. Lethal injection emerged as the method of choice, replacing such "humane" methods as the gas chamber and the electric chair. Today, the gas chamber has been almost entirely abandoned due to concerns about cruelty as well as the safety of the executioners. Almost all of the remaining gas chambers were built before the 1950s, and few have been carefully maintained since the 1970s, resulting in a high risk of gas leakage and other malfunctions. Between 1977 and 2003, only 11 inmates have been killed in the gas chamber, out of a total of 885 executions. One of those was Robert Alton Harris, executed in California in 1992, his last words quoting Bill and Ted's Bogus Journey. The very last man executed in the gas chamber was German-born Walter LeGrande, who was executed in Arizona in 1999. The execution was held in violation of international law (regarding consular notification before the execution of foreign nationals) and in defiance of an emergency stay order issued by the World Court. The gas chamber remains on the books in five of the U.S. states where it had been previously used; most of these laws are grandfather clauses allowing people to opt for the gas chamber if they were arrested prior to the passage of legislation rescinding the method of execution. Any further gas chamber executions will likely be requested by prospective corpses who wish to protest capital punishment by dying ugly, and even those will likely peter out completely over the next 10 or 20 years. The U.S. remains the only country with laws permitting gas chambers still on the books, although reports occasionally surface regarding off-the-books atrocities such as North Korea's "Camp 22," allegedly a concentration camp installation where women and children are routinely gassed to death. However, recent reports suggest that the tale of Camp 22 may have been based on forged documents, possibly brought to you by the same folks who gave you Iraqi WMDs, and possibly for the same reason. Don't worry, the truth will come out... probably no more than two years after the U.S. invades.
|