Accessibility statement

This accessibility statement applies to the Digital Land website: https://digital-land.github.io/.

This website is run by the Digital Land team in the Ministry of Housing, Communities and Local Government.

We are always working to improve our website and want as many people as possible to be able to access and use it. For example, that means you should be able to:

change colours, contrast levels and fonts

zoom in up to 300% without the text spilling off the screen

navigate most of the website using just a keyboard

navigate most of the website using speech recognition software

listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

the maps on our brownfield land and organisations pages are difficult to navigate using just a keyboard

there’s a limit to how far you can magnify the maps on these pages

some images published by past suppliers or external teams that we worked with do not have a text alternative

We will outsource an accessibility audit on this website in the near future and fix as many of the issues that are found as possible.

How to request content in an accessible format

If you need information in a different format, for example large print or accessible PDF, email <a href="mailto:DigitalLand<EMAIL_ADDRESS>and tell us:

the web address (URL) of the content

your name and email address

the format you need

We’ll consider your request and get back to you in 21 days.

Reporting accessibility problems with this website

If you find any problems that are not listed on this page, or you think we’re not meeting the accessibility requirements, please email <a href="mailto:DigitalLand<EMAIL_ADDRESS>so that we can fix the issue.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

The Digital Land team is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-text content

Some images that were published by past suppliers or external teams that we worked with, do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

When working with suppliers in the future, or allowing other teams to publish on this website, we will make it a requirement that any images meet accessibility standards.

Maps

Our maps on the organisation pages and brownfield resource pages are not tabbable, which fails WCAG 2.1 success criterion 2.1.1 (keyboard). We use Leafletjs to produce the maps. At the moment they are created as a canvas element and are not tabbable. We are looking into making them tabbable.

Our maps are also not screen-reader accessible. To mitigate this we have included a descriptive heading, descriptive text, and a title attribute on the map elements. Also, the maps on the organisations pages display information which is available as text on the page.

Preparation of this accessibility statement

This statement was prepared on 16 September 2020. It was last reviewed on 16 September 2020.

This website was last tested on 11 September 2020. The test was carried out by the Digital Land team.

We checked most pages on our site for compliance against the Web Content Accessibility Guidelines (WCAG v2.0 and 2.1). We plan to get a third-party supplier to run a full accessibility audit of our website soon.


{% load static %}
Zibo Zhang
About
A collection of my work, blogs, projects, and resume can be found on this website.
Contact
Github Page
Connect on LinkedIn
Zibo Zhang
{% block content %} {% endblock %}


Special Events
Special Events
Rank Up Martial Arts holds special events open to anyone who wishes to join us. Please read our current event flyer and contact us if you would like to participate.
Rank Up Martial Arts holds special events open to anyone who wishes to join us. Please read our current event flyer and contact us if you would like to participate.


Most of my art is generated from my sketchbook. I carry a sketchbook and a travel set of watercolor paints everywhere I go. My favorite medium is good old-fashioned watercolor and pen and ink. Not to forget, however, the small amount of work that I've done in clay. Recently, I've been working in clay by hand rather than on the wheel as well as dabbling in fused glass and enamel work. I derive much pleasure from making art and hope that you will enjoy seeing a few samples of my work.
Spirals
Blue Watercolor Peppers
Cactus
Monkey Puzzle Tree


Boy, 11, injured in Wolverhampton car crash
A boy has been treated by paramedics after a collision involving a car in Wolverhampton city centre.
by Thomas ParkesThe 11-year-old was hit near Wolverhampton Art Gallery, in Lichfield Street, shortly before 4.30pm on Friday. .
The secondary school pupil was treated at the scene, but the extent of his injuries is not yet known.
A West Midlands Police spokesman confirmed the collision involved a car and a pedestrian.
The force attended the scene for traffic management purposes.
A spokesman from West Midlands Ambulance Service said: "We were called to Lichfield Street, near to Wolverhampton Art Gallery, to reports of a collision between a vehicle and a pedestrian.
"One ambulance is in attendance and we are currently treating one male patient, who is the pedestrian."


South Africa's Gordhan says govt committed to saving SAA but not with money
by ReutersJOHANNESBURG — South Africa’s public enterprises minister Pravin Gordhan said on Tuesday that the government was committed to saving South African Airways, but there was no more money available from state coffers, according to a statement from his department.
“The pattern of bailouts has become a moral hazard,” the statement said, adding that Gordhan had urged striking unions to work with the airline’s management to find a speedy resolution to ongoing industrial action, with the ultimate aim being to save both the airline and jobs. (Reporting by Emma Rumney; Editing by David Clarke)


BORN
BORN
is a probabilistic reasoner for BEL (Bayesian EL), which is an extension of the lightweight Description Logic EL.
Website:
https://julianmendez.github.io/born/
Source code:
https://github.com/julianmendez/born


{% extends 'base/layout.html' %} {% load helpers %} {% load render_table from django_tables2 %} {% comment %} Blocks: message_extra: Supplementary warning message content Context: model: The model class of the objects being deleted form: The bulk delete form class table: The table class for rendering list of objects being deleted return_url: The URL to which the user is redirected after submitting the form {% endcomment %} {% block title %}Delete {{ table.rows|length }} {{ model|meta:"verbose_name_plural"|bettertitle }}?{% endblock %} {% block content %}


Methods
HTTP verbs that Node.js core’s HTTP parser supports.
This module provides an export that is just like http.METHODS
from Node.js core,
with the following differences:
- All method names are lower-cased.
- Contains a fallback list of methods for Node.js versions that do not have a
http.METHODS
export (0.10 and lower). - Provides the fallback list when using tools like
browserify
without pulling in thehttp
shim module.
Install
$ npm install methods
API
var methods = require('methods')
methods
This is an array of lower-cased method names that Node.js supports. If Node.js
provides the http.METHODS
export, then this is the same array lower-cased,
otherwise it is a snapshot of the verbs from Node.js 0.10.


4.16.4 Query Handling Predicates
ask_query(
+QueryClass,
+Query,
+Help,
-Answer)
hookable-
Prints the question Query, then reads and processes user input
according to QueryClass, and returns the result of the processing,
the abstract answer term Answer. The Help message is
printed in case of invalid input.
query_hook(
+QueryClass,
+Query,
+QueryLines,
+Help,
+HelpLines,
-Answer)
hookuser:query_hook(
+QueryClass,
+Query,
+QueryLines,
+Help,
+HelpLines,
-Answer)
-
Called by
ask_query/4
before processing the query. If this
predicate succeeds, it is assumed that the query has been
processed and nothing further is done.
query_class_hook(
+QueryClass,
-Prompt,
-InputMethod,
-MapMethod,
-FailureMode)
hookuser:query_class_hook(
+QueryClass,
-Prompt,
-InputMethod,
-MapMethod,
-FailureMode)
-
Provides the user with a method of overriding the call to
'SU_messages':query_class/5
in the preparation phase of query
processing. This way the default query class characteristics can be
changed.
'SU_messages':query_class(
+QueryClass,
-Prompt,
-InputMethod,
-MapMethod,
-FailureMode)
extendible-
Predefined query class characteristics table.
'SU_messages':query_abbreviation(
+QueryClass,
-Prompt,
-Pairs)
extendible-
Predefined query abbreviation table.
query_input_hook(
+InputMethod,
+Prompt,
-RawInput)
hookuser:query_input_hook(
+InputMethod,
+Prompt,
-RawInput)
-
Provides the user with a method of overriding the call to
'SU_messages':query_input/3
in the input phase of query
processing. This way the implementation of the default input methods
can be changed.
'SU_messages':query_input(
+InputMethod,
+Prompt,
-RawInput)
extendible-
Predefined query input methods.
query_map_hook(
+MapMethod,
+RawInput,
-Result,
-Answer)
hookuser:query_map_hook(
+MapMethod,
+RawInput,
-Result,
-Answer)
-
Provides the user with a method of overriding the call to
'SU_messages':query_map/4
in the mapping phase of query
processing. This way the implementation of the default map methods
can be changed.
'SU_messages':query_map(
+MapMethod,
+RawInput,
-Result,
-Answer)
extendible-
Predefined query map methods.
Send feedback on this subject.


Created 07/09/02
This is a practice quiz. The results are not recorded anywhere and do not affect your grade. The questions on this quiz might not appear in any quiz or test that does count toward your grade.
Instructions: For each question, choose the single best answer. Make your choice by clicking on its button. You can change your answers at any time. When the quiz is graded, the correct answers will appear in the box after each question.
If you have returned here from another page, or have re-loaded this page, you will need to click again on each of your choices for the grading program to work correctly. You may want to press the SHIFT KEY while clicking to clear the old answers.


A templating system thats good for outputting HTML, for Javascript and Python.
TATL templates are expressive, easy to learn, and cross easily from
server to client. TATL uses the natural block structure in your HTML code,
resulting in less repetition and more natural indentation.
Templates are precompiled into either Python or Javascript and then loaded as modules.
var intro = require('intro');
process.stdout.write(
intro.html('World', ['Javascript', 'Python']).valueOf()
);
intro.html
<htmlparam="name, languages">
Hello {name}

I am fluent in:

<ulfor="language in languages">{language}

The basics: text within {} are *substitions*.
for= and if= are special *attributes*. for= causes the tag to be repeated, in this case once for each element notices. if= causes the tag to not appear in the output if the condition is true. In this case the condition is whether number is blank or not.
There are a few more
special attributes, which we'll see in the advanced section. On to next >>

Hello {name}
<pif="number">Your emergency contact number is: {number}

<lifor="notice in notices">{notice}

Ok, now lets look at the special *tags*. Just two: <do> acts like any other tag but doesn't show up in the output.
We're using it to loop, where the looped contents don't all go in the same tag (it happens).
<else> works with if=. <else if=""> does what you'd expect.
Also, notice we're looping over a list of numbers now, and we're just writing that list in here directly.

Hello {name}
<pif="number">
Your emergency contact number is: {number}<else>
Please set an emergency contact number!

<ulfor="notice in notices">{notice}

<form>
Rate our service!
<dofor="rating in [5, 4, 3, 2, 1]"><inputtype="radio"name="rating"value="{rating}">{rating}</do></form>
We can use shortcuts here.
Instead of if="number", we can just shorten to "if". This basically checks the substitution values. (See elide for all the details)
We can also leave the loop variable name off the for= attribute. It will default to . (see the dot).
Finally, there's syntax to make a list of numbers (more details).
next >>

Hello {name}
<pif>
Your emergency contact number is: {number}<else>
Please set an emergency contact number!

<ulfor="notices">{.}

<form>
Rate our service!
<dofor="5...1"><inputtype="radio"name="rating"value="{.}">{.}</do></form>
Lets see what happens if the data is more structured. The notices now has a level, text and a link for more details. We just change the substitution to use variable.path.
We haven't shown what kind of data structure the notices is passed as but dotted paths work with lists, dicts, and objects, and if the key isn't found, its just empty (more on empty).
Notice how the empty if came in handy again!

Hello {name}
<pif>
Your emergency contact number is: {number}<else>
Please set an emergency contact number!

<ulclass="{.level}"for="notices">{.text}<divclass="more-info"if><ahref="{.url}">Additional information

<form>
Rate our service!
<dofor="1...5"><inputtype="radio"name="rating"value="{.}">{.}</do></form>
Thats it! Dive in further:
more data, more loops, set
calls, defs, modules
params, inheritence
Quoting and context within your HTML doc
Comments and Front matter
Filters
Magic placeholders
Tag combos
Building tags with Tag()
More data, more loops.
Ok, we need labels for the radio buttons. Lets add set a local variable. Then we look up the number.
If its not found, then nothing is inserted -- expression paths don't fail on missing values.
Lets add another tag: set="". This will take the tag, after execution of the for, if etc, and
save it to a local variable.
For the sake of a scenario, lets say we've decided to nag people about
their number in the footer, too; we're referencing our variable like it was passed in.

Hello {name}
<pset="chide"if>
Your emergency contact number is: {number}<else>
Please set an emergency contact number!

<ulclass="{.level}"for="notices">{.text}<divclass="more-info"if><ahref="{.url}">Additional information

{labels = {1: "(Needs work)", 5: "(Fantastic)"}; }<form>
Rate our service!
<dofor="5...1"><inputtype="radio"name="rating"value="{.}">{.}{labels[.]}</do></form>
{chide}
Calls, defs
This is getting complicated. Lets move out some of the pieces using macros.
The second file is called common.html, and would be compiled into a module called common; we can access the macros within that module by using common::name.
The def= tag defines a macro. Note that we moved the {labels = {..}} inside the macro.
When it was outside the macro, it was a local var of the implicit html macro. Macros can
only access parameters that are passed in.
We call a local function via {function()} and function from another template via {template::function()}
<pdef="chide(number)"if>
Your emergency contact number is: {number}<else>
Please set an emergency contact number!

<formdef="rating">
Rate our service!
{labels = {1: "(Needs work)", 5: "(Fantastic)"}; }<dofor="5...1"><inputtype="radio"name="rating"value="{.}">{.}{labels[.]}</do></form>
The use= attribute + param= = inheritence.
We mentioned the top level tag was implicitly a macro. Specifically, if not other added, a def="html(*)" is assumed. The * means, add any param defined to the arguments.
We could just call the template::html macro at the end, but a better way is the use="tag". That will find the local variables that correspond to the parameters of the template, and pass them.
Notice that our parameter isn't constrained to being used in a single place. Our base template is using it for the title of the page, as well. In general you can use variables after they're defined, eg you can use variables from a for loop.
<htmldef="html(title, body, footer)"><title>{title}</title>
{title}

{body}
{footer}
More shortcuts!
param and set will default to their tag names.
param will set '.' to be the value of the parameter.
set without a name will also default to using the contents filter, which
will strip the surrounding tag.
<titleparam>{.}</title><bodyparam>
{title}

{.}
<footerparam>{.}
Quoting and content
Content is automatically quoted according to position within the document.
Doubled braces inserts one brace, and does not start a substitution. A brace just before a tag also inserts
the brace without being a substitution.
Nothing in the


This is an example user guide window implemented as a UI component. Press I to dismiss/reopen this window.
The Goal of this UI framework is to make it easy to prototype / develop self contained UI components. In its current form, it is not a framework for use within a game client, though it may evolve in that direction over time.
All windows can be moved by dragging them. Some only allow dragging from certain parts of the window. This user guide window can be dragged by grabbing hold of any window edge. The chat box can be moved by grabbing hold of the space beside the tabs, or the tabs themselves.
The source code for this framework can be downloaded from here
LOADING means something went wrong, as the component never finished loading.
LOADED means the component loaded and initialised, but did not return a public interface. This may be because it is providing functionality rather than providing an API. An example of this are the slash command handlers, they handle slash commands but don't provide a public interface
AVAILABLE means the component loaded, initialised and returned a public interface, but did not provide a run() method and so is not considered runnable (startable).
STARTED means the component loaded, initialised, returned a public interface which included a run() method which was called and completed successfully.


InvestiGame
Search
Apologies! This functionality will be added in the future.
Home
About
Copyright 2020


While it may seem strange to include the site you're currently on as a project entry here, I thought It'd be nice to have a bit of a rundown of what I wanted to achieve when creating this site. I'd always wanted a portfolio site to show off what I've been up to, but I either found myself without time, money, or both. After essentially free-lancing it for the year after my placement in London fell through, I felt this was the best time to actually rig something like this up.
-Return to Projects-
I created the logo like usual, I must have a thing for doing that as I've either insisted on doing it or fell into doing it too many times to count, indeed, most of the projects I've ever done I have created some form of logo or branding to go with it. I knew I wanted this site to be fairly minimal in its presentation, so I went with a slightly textured, neutral background for the landing page, and sharp angled project previews for a sleeker look. As usual, I started with a HTML5 boiler plate and did it all from scratch, just the way I like it.
I just wanted a centralised place to store everything relevent I'd done pertaining to my course (some of it very loosely pertaining mind you). I also kept forgetting to buy the domain name with my name in it, so after I did so when I got some cash from creating a few sites, I felt it only proper to get a site up in my name ASAP. Currently, this site is linked to the domain folkvangrmedia.com due to being unable to renew my previous domain name.
This one is obvious, I did it for me so I have a nicely presented portfolio of work, but also for potential employers to quickly see what I've been up to so they may build a better picture of who I am outside of my CV. A win for all! - unless it doesn't load properly on your device, then that makes me look bad.
Made with by Max Ingham


{{template "head.html" .}} {{template "navbar.html" .}}
Michael /ˈmaɪkəl/ is a masculine given name that comes from Hebrew: מִיכָאֵל / מיכאל (Mīkhāʼēl, pronounced [miχaˈʔel]), derived from the question מי כאל mī kāʼēl, meaning "Who is like God?".[1] Patronymic surnames that come from Michael include Michaels, Carmichael, MacMichael, McMichael, Micallef, Michaelson, Mikkelsen, DiMichele, Mikhaylov, Mykhaylenko, Mikeladze, Michels, and Mitchell.
Michael (and its variants) is one of the most common given names for men in the world. In the United States, Michael was the most popular name of the 20th century, ranking No. 1 from 1954 to 1998 (with the exception of 1960, when it was second to David). It was among the top three most popular names for each year since 1953, only falling out of the top five in 2011 for the first time since 1949.[2]
In 2014, Michael was the 20th most popular name in Northern Ireland,[3] 27th in Canada[4] and 42nd in Australia.[5] In England and Wales, Michael ranked 53rd in 2011 and 2012.[6] Mícheál ranked as the eighth most popular name for boys in Ireland in 2013.[7]
The Book of Enoch, which presents itself as written by Enoch, mentions Uriel in many of the component books. In Chapter IX which is part of "The Book of the Watchers" (2nd century BCE) only four Angels are mentioned by name, these are Michael, Uriel, Raphael, and Gabriel (though some versions have a fifth angel: Suryal or Suriel). However the later Chapter XX lists the name and function of seven angels, these are "Uriel, one of the holy angels, who is over the world and over Tartarus", Raphael, Raguel, Michael, Saraqâêl, Gabriel, and Remiel.
The Book of the Angels as a whole tells us that Uriel, Raphael, and Gabriel were present before God to testify on behalf of Humankind. They wish to ask for divine intervention during the reign of the Fallen Gregori (Fallen Watchers). These fallen take human wives and produced half-angel, half-human offspring called the Nephilim. Uriel is responsible for warning Noah about the upcoming Great Flood.
Then said the Most High, the Holy and Great One spoke, and sent Uriel to the son of Lamech, and said to him:
"
Gabriel (Hebrew: גַּבְרִיאֵל Gavri'el "God is my strength", Biblical Greek: Γαβριήλ, Gabriel; Amharic, Geez and Tigrinya: ገብርኤል, Arabic: جبريل or جبرائيل Jibril or Jibra'il), in the Abrahamic religions, is an angel who typically serves as God's messenger.
In the Jewish scriptures, Gabriel appears to the prophet Daniel, to explain his visions (Daniel 8:15–26, 9:21–27). Gabriel the archangel is also a character in other ancient Jewish writings such as the Book of Enoch.
In the Christian New Testament in the Gospel of Luke, the angel Gabriel appears to Zechariah and the Virgin Mary, foretelling the births of John the Baptist and Jesus, respectively (Luke 1:11–38). In many Christian traditions including Anglican, Eastern Orthodox and Roman Catholic, Gabriel is also referred to as a saint.[1][6]


shark Nightmare

hello. It has been several months since I've made a post here. the windows laptop that the majority of brobeur gamedev was done on was wiped and Linux mint was installed instead. Focus has been on ipython notebook and data processing.
over the past month I have been joining in jams - usually other peoples team
ill cover them now.
asylum jam.
I received an email from a team looking for an artist - 2d and some 3d skills is always a bonus.
Perfect. This was the biggest team I had ever worked with on a game - four.
They were using Git for source control but the project was somewhat messy.
The team were not happy with my bright colors and painting landscapes and people - they wanted more abstract shapes in black and white.
I was very disappointed by the quality of the 3d artists models. They were extremely flat - and awful face scale. Never less - I remodeled his models. sadly the team in the end only used a small squiggle I painted.
Having Unity3d is very important when joining a team using Unity for a jam. I can't expect programmings or other artists to have the level design skills or see my vision!
If you would like to play it - Crushing Nightmare. Sorry Linux - web only.
The next game jam I joined - redditbaconjam06.
I had partaked in redditbaconjam05 - producing Surreal Warp Nightmare.
I was invited to a team that had two people - a programmer - Rob - and music by Emily.
Rob made a side scroller shooting game. The music was epic.
This time I decided to focus on level design, with recycling old assets. I sent Rob 3d assets and models to use over the stock images. Sadly he didn't use these. Even sending him a package of art added to the scene didn't work.
It was a busy weekend and I didn't invest enough time. I emailed Rob after the jam and asked if I could get the final package and work on it further. As of now I have received nothing back. Such as life.
View the entry redditbaconjam06


This document describes how to build and install Open vSwitch on a generic Linux, FreeBSD, or NetBSD host. For specifics around installation on a specific platform, refer to one of these installation guides:
To compile the userspace programs in the Open vSwitch distribution, you will need the following software:
GNU make
A C compiler, such as:
While OVS may be compatible with other compilers, optimal support for atomic operations may be missing, making OVS very slow (see lib/ovs-atomic.h).
libssl, from OpenSSL, is optional but recommended if you plan to connect the Open vSwitch to an OpenFlow controller. libssl is required to establish confidentiality and authenticity in the connections from an Open vSwitch to an OpenFlow controller. If libssl is installed, then Open vSwitch will automatically build with support for it.
libcap-ng, written by Steve Grubb, is optional but recommended. It is required to run OVS daemons as a non-root user with dropped root privileges. If libcap-ng is installed, then Open vSwitch will automatically build with support for it.
Python 2.7. You must also have the Python six library.
On Linux, you may choose to compile the kernel module that comes with the Open vSwitch distribution or to use the kernel module built into the Linux kernel (version 3.3 or later). See the FAQ question "What features are not available in the Open vSwitch kernel datapath that ships as part of the upstream Linux kernel?" for more information on this trade-off. You may also use the userspace-only implementation, at some cost in features and performance (see the userspace installation guide for details).
To compile the kernel module on Linux, you must also install the following:
A supported Linux kernel version. Refer to the README for a list of supported versions.
For optional support of ingress policing, you must enable kernel configuration options NET_CLS_BASIC, NET_SCH_INGRESS, and NET_ACT_POLICE, either built-in or as modules. NET_CLS_POLICE is obsolete and not needed.)
On kernels before 3.11, the ip_gre module, for GRE tunnels over IP (NET_IPGRE), must not be loaded or compiled in.
To configure HTB or HFSC quality of service with Open vSwitch, you must enable the respective configuration options.
To use Open vSwitch support for TAP devices, you must enable CONFIG_TUN.
To build a kernel module, you need the same version of GCC that was used to build that kernel.
A kernel build directory corresponding to the Linux kernel image the module is to run on. Under Debian and Ubuntu, for example, each linux-image package containing a kernel binary has a corresponding linux-headers package with the required build infrastructure.
If you are working from a Git tree or snapshot (instead of from a distribution tarball), or if you modify the Open vSwitch build system or the database schema, you will also need the following software:
To run the unit tests, you also need:
The datapath tests for userspace and Linux datapaths also rely upon:
The ovs-vswitchd.conf.db(5) manpage will include an E-R diagram, in formats other than plain text, only if you have the following:
If you are going to extensively modify Open vSwitch, consider installing the following to obtain better warnings:
"sparse" version 0.4.4 or later (http://www.kernel.org/pub/software/devel/sparse/dist/).
GNU make.
clang, version 3.4 or later
flake8, version 2.X, along with the hacking flake8 plugin (for Python code). The automatic flake8 check that runs against Python code has some warnings enabled that come from the "hacking" flake8 plugin. If it's not installed, the warnings just won't occur until it's run on a system with "hacking" installed. Note that there are problems with flake8 3.0 and the "hacking" plugin. To ensure you get flake8 2.X, you can use:
$ pip install 'flake8<3.0'
You may find the ovs-dev script found in utilities/ovs-dev.py useful.
The machine you build Open vSwitch on may not be the one you run it on. To simply install and run Open vSwitch you require the following software:
On Linux you should ensure that /dev/urandom exists. To support TAP devices, you must also ensure that /dev/net/tun exists.
This step is not needed if you have downloaded a released tarball. If you pulled the sources directly from an Open vSwitch Git tree or got a Git tree snapshot, then run boot.sh in the top source directory to build the "configure" script:
$ ./boot.sh
Configure the package by running the configure script. You can usually invoke configure without any arguments. For example:
$ ./configure
By default all files are installed under /usr/local. Open vSwitch also expects to find its database in /usr/local/etc/openvswitch by default. If you want to install all files into, e.g., /usr and /var instead of /usr/local and /usr/local/var and expect to use /etc/openvswitch as the default database directory, add options as shown here:
$ ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
Note
Open vSwitch installed with packages like .rpm (e.g. via yum install or rpm -ivh) and .deb (e.g. via apt-get install or dpkg -i) use the above configure options.
By default, static libraries are built and linked against. If you want to use shared libraries instead:
$ ./configure --enable-shared
To use a specific C compiler for compiling Open vSwitch user programs, also specify it on the configure command line, like so:
$ ./configure CC=gcc-4.2
To use 'clang' compiler:
$ ./configure CC=clang
To supply special flags to the C compiler, specify them as CFLAGS on the configure command line. If you want the default CFLAGS, which include -g to build debug symbols and -O2 to enable optimizations, you must include them yourself. For example, to build with the default CFLAGS plus -mssse3, you might run configure as follows:
$ ./configure CFLAGS="-g -O2 -mssse3"
For efficient hash computation special flags can be passed to leverage built-in intrinsics. For example on X86_64 with SSE4.2 instruction set support, CRC32 intrinsics can be used by passing -msse4.2:
$ ./configure CFLAGS="-g -O2 -msse4.2"`
If you are on a different processor and don't know what flags to choose, it is recommended to use -march=native settings:
$ ./configure CFLAGS="-g -O2 -march=native"
With this, GCC will detect the processor and automatically set appropriate flags for it. This should not be used if you are compiling OVS outside the target machine.
Note
CFLAGS are not applied when building the Linux kernel module. Custom CFLAGS for the kernel module are supplied using the EXTRA_CFLAGS variable when running make. For example:
$ make EXTRA_CFLAGS="-Wno-error=date-time"
To build the Linux kernel module, so that you can run the kernel-based switch, pass the location of the kernel build directory on --with-linux. For example, to build for a running instance of Linux:
$ ./configure --with-linux=/lib/modules/$(uname -r)/build
Note
If --with-linux requests building for an unsupported version of Linux, then configure will fail with an error message. Refer to the FAQ for advice in that case.
If you wish to build the kernel module for an architecture other than the architecture of the machine used for the build, you may specify the kernel architecture string using the KARCH variable when invoking the configure script. For example, to build for MIPS with Linux:
$ ./configure --with-linux=/path/to/linux KARCH=mips
If you plan to do much Open vSwitch development, you might want to add --enable-Werror, which adds the -Werror option to the compiler command line, turning warnings into errors. That makes it impossible to miss warnings generated by the build. For example:
$ ./configure --enable-Werror
To build with gcov code coverage support, add --enable-coverage:
$ ./configure --enable-coverage
The configure script accepts a number of other options and honors additional environment variables. For a full list, invoke configure with the --help option:
$ ./configure --help
You can also run configure from a separate build directory. This is helpful if you want to build Open vSwitch in more than one way from a single source directory, e.g. to try out both GCC and Clang builds, or to build kernel modules for more than one Linux version. For example:
$ mkdir _gcc && (cd _gcc && ./configure CC=gcc) $ mkdir _clang && (cd _clang && ./configure CC=clang)
Under certains loads the ovsdb-server and other components perform better when using the jemalloc memory allocator, instead of the glibc memory allocator. If you wish to link with jemalloc add it to LIBS:
$ ./configure LIBS=-ljemalloc
Run GNU make in the build directory, e.g.:
$ make
or if GNU make is installed as "gmake":
$ gmake
If you used a separate build directory, run make or gmake from that directory, e.g.:
$ make -C _gcc $ make -C _clang
For improved warnings if you installed sparse (see "Prerequisites"), add C=1 to the command line.
Note
Some versions of Clang and ccache are not completely compatible. If you see unusual warnings when you use both together, consider disabling ccache.
Consider running the testsuite. Refer to Testing for instructions.
Run make install to install the executables and manpages into the running system, by default under /usr/local:
$ make install
If you built kernel modules, you may install them, e.g.:
$ make modules_install
It is possible that you already had a Open vSwitch kernel module installed on your machine that came from upstream Linux (in a different directory). To make sure that you load the Open vSwitch kernel module you built from this repository, you should create a depmod.d file that prefers your newly installed kernel modules over the kernel modules from upstream Linux. The following snippet of code achieves the same:
$ config_file="/etc/depmod.d/openvswitch.conf" $ for module in datapath/linux/*.ko; do modname="$(basename ${module})" echo "override ${modname%.ko} * extra" >> "$config_file" echo "override ${modname%.ko} * weak-updates" >> "$config_file" done $ depmod -a
Finally, load the kernel modules that you need. e.g.:
$ /sbin/modprobe openvswitch
To verify that the modules have been loaded, run /sbin/lsmod and check that openvswitch is listed:
$ /sbin/lsmod | grep openvswitch
Note
If the modprobe operation fails, look at the last few kernel log messages (e.g. with dmesg | tail). Generally, issues like this occur when Open vSwitch is built for a kernel different from the one into which you are trying to load it. Run modinfo on openvswitch.ko and on a module built for the running kernel, e.g.:
$ /sbin/modinfo openvswitch.ko $ /sbin/modinfo /lib/modules/$(uname -r)/kernel/net/bridge/bridge.ko
Compare the "vermagic" lines output by the two commands. If they differ, then Open vSwitch was built for the wrong kernel.
If you decide to report a bug or ask a question related to module loading, include the output from the dmesg and modinfo commands mentioned above.
Before starting ovs-vswitchd itself, you need to start its configuration database, ovsdb-server. Each machine on which Open vSwitch is installed should run its own copy of ovsdb-server. Before ovsdb-server itself can be started, configure a database that it can use:
$ mkdir -p /usr/local/etc/openvswitch $ ovsdb-tool create /usr/local/etc/openvswitch/conf.db \ vswitchd/vswitch.ovsschema
Configure ovsdb-server to use database created above, to listen on a Unix domain socket, to connect to any managers specified in the database itself, and to use the SSL configuration in the database:
$ mkdir -p /usr/local/var/run/openvswitch $ ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock \ --remote=db:Open_vSwitch,Open_vSwitch,manager_options \ --private-key=db:Open_vSwitch,SSL,private_key \ --certificate=db:Open_vSwitch,SSL,certificate \ --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert \ --pidfile --detach
Note
If you built Open vSwitch without SSL support, then omit --private-key, --certificate, and --bootstrap-ca-cert.)
Initialize the database using ovs-vsctl. This is only necessary the first time after you create the database with ovsdb-tool, though running it at any time is harmless:
$ ovs-vsctl --no-wait init
Start the main Open vSwitch daemon, telling it to connect to the same Unix domain socket:
$ ovs-vswitchd --pidfile --detach
At this point you can use ovs-vsctl to set up bridges and other Open vSwitch features. For example, to create a bridge named br0 and add ports eth0 and vif1.0 to it:
$ ovs-vsctl add-br br0 $ ovs-vsctl add-port br0 eth0 $ ovs-vsctl add-port br0 vif1.0
Refer to ovs-vsctl(8) for more details.
When you upgrade Open vSwitch from one version to another you should also upgrade the database schema:
Stop the Open vSwitch daemons, e.g.:
$ kill `cd /usr/local/var/run/openvswitch && cat ovsdb-server.pid ovs-vswitchd.pid`
Install the new Open vSwitch release by using the same configure options as was used for installing the previous version. If you do not use the same configure options, you can end up with two different versions of Open vSwitch executables installed in different locations.
Upgrade the database, in one of the following two ways:
If there is no important data in your database, then you may delete the database file and recreate it with ovsdb-tool, following the instructions under "Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD".
If you want to preserve the contents of your database, back it up first, then use ovsdb-tool convert to upgrade it, e.g.:
$ ovsdb-tool convert /usr/local/etc/openvswitch/conf.db \ vswitchd/vswitch.ovsschema
Start the Open vSwitch daemons as described under Starting above.
Upgrading Open vSwitch from one version to the next version with minimum disruption of traffic going through the system that is using that Open vSwitch needs some considerations:
The ovs-ctl utility's restart function only restarts the userspace daemons, makes sure that the 'ofport' values remain consistent across restarts, restores userspace flows using the ovs-ofctl utility and also uses the other_config:flow-restore-wait column to keep the traffic downtime to the minimum. The ovs-ctl utility's force-reload-kmod function does all of the above, but also replaces the old kernel module with the new one. Open vSwitch startup scripts for Debian, XenServer and RHEL use ovs-ctl's functions and it is recommended that these functions be used for other software platforms too.
This section describe Open vSwitch's built-in support for various test suites. You must bootstrap, configure and build Open vSwitch (steps are in "Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD" above) before you run the tests described here. You do not need to install Open vSwitch or to build or load the kernel module to run these test suites. You do not need supervisor privilege to run these test suites.
Open vSwitch includes a suite of self-tests. Before you submit patches upstream, we advise that you run the tests and ensure that they pass. If you add new features to Open vSwitch, then adding tests for those features will ensure your features don't break as developers modify other areas of Open vSwitch.
To run all the unit tests in Open vSwitch, one at a time, run:
$ make check
This takes under 5 minutes on a modern desktop system.
To run all the unit tests in Open vSwitch in parallel, run:
$ make check TESTSUITEFLAGS=-j8
You can run up to eight threads. This takes under a minute on a modern 4-core desktop system.
To see a list of all the available tests, run:
$ make check TESTSUITEFLAGS=--list
To run only a subset of tests, e.g. test 123 and tests 477 through 484, run:
$ make check TESTSUITEFLAGS='123 477-484'
Tests do not have inter-dependencies, so you may run any subset.
To run tests matching a keyword, e.g. ovsdb, run:
$ make check TESTSUITEFLAGS='-k ovsdb'
To see a complete list of test options, run:
$ make check TESTSUITEFLAGS=--help
The results of a testing run are reported in tests/testsuite.log. Report report test failures as bugs and include the testsuite.log in your report.
Note
Sometimes a few tests may fail on some runs but not others. This is usually a bug in the testsuite, not a bug in Open vSwitch itself. If you find that a test fails intermittently, please report it, since the developers may not have noticed. You can make the testsuite automatically rerun tests that fail, by adding RECHECK=yes to the make command line, e.g.:
$ make check TESTSUITEFLAGS=-j8 RECHECK=yes
If the build was configured with --enable-coverage and the lcov utility is installed, you can run the testsuite and generate a code coverage report by using the check-lcoc target:
$ make check-lcov
All the same options are avaiable via TESTSUITEFLAGS. For example:
$ make check-lcov TESTSUITEFLAGS=-j8 -k ovn
If you have valgrind installed, you can run the testsuite under valgrind by using the check-valgrind target:
$ make check-valgrind
When you do this, the "valgrind" results for test <N> are reported in files named tests/testsuite.dir/<N>/valgrind.*.
All the same options are available via TESTSUITEFLAGS.
Hint
You may find that the valgrind results are easier to interpret if you put -q in ~/.valgrindrc, since that reduces the amount of output.
OFTest is an OpenFlow protocol testing suite. Open vSwitch includes a Makefile target to run OFTest with Open vSwitch in "dummy mode". In this mode of testing, no packets travel across physical or virtual networks. Instead, Unix domain sockets stand in as simulated networks. This simulation is imperfect, but it is much easier to set up, does not require extra physical or virtual hardware, and does not require supervisor privileges.
To run OFTest with Open vSwitch, first read and follow the instructions under Testing above. Second, obtain a copy of OFTest and install its prerequisites. You need a copy of OFTest that includes commit 406614846c5 (make ovs-dummy platform work again). This commit was merged into the OFTest repository on Feb 1, 2013, so any copy of OFTest more recent than that should work. Testing OVS in dummy mode does not require root privilege, so you may ignore that requirement.
Optionally, add the top-level OFTest directory (containing the oft program) to your $PATH. This slightly simplifies running OFTest later.
To run OFTest in dummy mode, run the following command from your Open vSwitch build directory:
$ make check-oftest OFT=<oft-binary>
where <oft-binary> is the absolute path to the oft program in OFTest. If you added "oft" to your $PATH, you may omit the OFT variable assignment
By default, check-oftest passes oft just enough options to enable dummy mode. You can use OFTFLAGS to pass additional options. For example, to run just the basic.Echo test instead of all tests (the default) and enable verbose logging, run:
$ make check-oftest OFT=<oft-binary> OFTFLAGS='--verbose -T basic.Echo'
If you use OFTest that does not include commit 4d1f3eb2c792 (oft: change default port to 6653), merged into the OFTest repository in October 2013, then you need to add an option to use the IETF-assigned controller port:
$ make check-oftest OFT=<oft-binary> OFTFLAGS='--port=6653'
Interpret OFTest results cautiously. Open vSwitch can fail a given test in OFTest for many reasons, including bugs in Open vSwitch, bugs in OFTest, bugs in the "dummy mode" integration, and differing interpretations of the OpenFlow standard and other standards.
Note
Open vSwitch has not been validated against OFTest. Report test failures that you believe to represent bugs in Open vSwitch. Include the precise versions of Open vSwitch and OFTest in your bug report, plus any other information needed to reproduce the problem.
Ryu is an OpenFlow controller written in Python that includes an extensive OpenFlow testsuite. Open vSwitch includes a Makefile target to run Ryu in "dummy mode". See OFTest above for an explanation of dummy mode.
To run Ryu tests with Open vSwitch, first read and follow the instructions under Testing above. Second, obtain a copy of Ryu, install its prerequisites, and build it. You do not need to install Ryu (some of the tests do not get installed, so it does not help).
To run Ryu tests, run the following command from your Open vSwitch build directory:
$ make check-ryu RYUDIR=<ryu-source-dir>``
where <ryu-source-dir> is the absolute path to the root of the Ryu source distribution. The default <ryu-source-dir> is $srcdir/../ryu where $srcdir is your Open vSwitch source directory. If this is correct, omit RYUDIR
Note
Open vSwitch has not been validated against Ryu. Report test failures that you believe to represent bugs in Open vSwitch. Include the precise versions of Open vSwitch and Ryu in your bug report, plus any other information needed to reproduce the problem.
Open vSwitch includes a suite of tests specifically for datapath functionality, which can be run against the userspace or kernel datapaths. If you are developing datapath features, it is recommended that you use these tests and build upon them to verify your implementation.
The datapath tests make some assumptions about the environment. They must be run under root privileges on a Linux system with support for network namespaces. For ease of use, the OVS source tree includes a vagrant box to invoke these tests. Running the tests inside Vagrant provides kernel isolation, protecting your development host from kernel panics or configuration conflicts in the testsuite. If you wish to run the tests without using the vagrant box, there are further instructions below.
Important
Requires Vagrant (version 1.7.0 or later) and a compatible hypervisor
Note
You must Bootstrap and Configure the sources before you run the steps described here.
A Vagrantfile is provided allowing to compile and provision the source tree as found locally in a virtual machine using the following command:
$ vagrant up
This will bring up a Fedora 23 VM by default. If you wish to use a different box or a vagrant backend not supported by the default box, the Vagrantfile can be modified to use a different box as base.
The VM can be reprovisioned at any time:
$ vagrant provision
OVS out-of-tree compilation environment can be set up with:
$ ./boot.sh $ vagrant provision --provision-with configure_ovs,build_ovs
This will set up an out-of-tree build environment inside the VM in /root/build. The source code can be found in /vagrant.
To recompile and reinstall OVS in the VM using RPM:
$ ./boot.sh $ vagrant provision --provision-with configure_ovs,install_rpm
Two provisioners are included to run system tests with the OVS kernel module or with a userspace datapath. This tests are different from the self-tests mentioned above. To run them:
$ ./boot.sh $ vagrant provision --provision-with \ configure_ovs,test_ovs_kmod,test_ovs_system_userspace
The results of the testsuite reside in the VM root user's home directory:
$ vagrant ssh $ sudo -s $ cd /root/build $ ls tests/system*
The datapath testsuite as invoked by Vagrant above may also be run manually on a Linux system with root privileges. These tests may take several minutes to complete, and cannot be run in parallel.
To invoke the datapath testsuite with the userspace datapath, run:
$ make check-system-userspace
The results of the testsuite are in tests/system-userspace-traffic.dir.
Make targets are also provided for testing the Linux kernel module. Note that these tests operate by inserting modules into the running Linux kernel, so if the tests are able to trigger a bug in the OVS kernel module or in the upstream kernel then the kernel may panic.
To run the testsuite against the kernel module which is currently installed on your system, run:
$ make check-kernel
To install the kernel module from the current build directory and run the testsuite against that kernel module:
$ make check-kmod
The results of the testsuite are in tests/system-kmod-traffic.dir.
A .travis.yml file is provided to automatically build Open vSwitch with various build configurations and run the testsuite using travis-ci. Builds will be performed with gcc, sparse and clang with the -Werror compiler flag included, therefore the build will fail if a new warning has been introduced.
The CI build is triggered via git push (regardless of the specific branch) or pull request against any Open vSwitch GitHub repository that is linked to travis-ci.
Instructions to setup travis-ci for your GitHub repository:
Go to http://travis-ci.org/ and sign in using your GitHub ID.
Go to the "Repositories" tab and enable the ovs repository. You may disable builds for pushes or pull requests.
In order to avoid forks sending build failures to the upstream mailing list, the notification email recipient is encrypted. If you want to receive email notification for build failures, replace the the encrypted string:
Install the travis-ci CLI (Requires ruby >=2.0): gem install travis
In your Open vSwitch repository: travis encrypt<EMAIL_ADDRESS>Add/replace the notifications section in .travis.yml and fill in the secure string as returned by travis encrypt:
notifications: email: recipients: - secure: "....."
Note
You may remove/omit the notifications section to fall back to default notification behaviour which is to send an email directly to the author and committer of the failing commit. Note that the email is only sent if the author/committer have commit rights for the particular GitHub repository.
Static Analysis is a method of debugging Software by examining code rather than actually executing it. This can be done through 'scan-build' commandline utility which internally uses clang (or) gcc to compile the code and also invokes a static analyzer to do the code analysis. At the end of the build, the reports are aggregated in to a common folder and can later be analyzed using 'scan-view'.
Open vSwitch includes a Makefile target to trigger static code analysis:
$ ./boot.sh $ ./configure CC=clang # clang # or $ ./configure CC=gcc CFLAGS="-std=gnu99" # gcc $ make clang-analyze
You should invoke scan-view to view analysis results. The last line of output from clang-analyze will list the command (containing results directory) that you should invoke to view the results on a browser.
Please report problems to bugs@openvswitch.org.


Welcome!
Music
ArtWorks
Cooking
Education
B.S.Division of Liberal Arts and Sciences, present
Gwangju Institute of Science and Technology
High School, 2020
Daegu Science High School for gifted
Contact me
email : f35jsflove@gmail.com


WITNESS LIST Public Education Committee April 8, 2003-2:00P HB 16 For: Golson, Kathy (Texas Association of School Boards) Gustafson, Lindsay (Texas Classroom Teachers Assoc) Harris, Dwight (Texas Federation of Teachers) Soehnge, Karen (Texas Association of School Administrators) Wall, Marjorie (Texas State Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) Against: Pam, Uhr (Self and ACLU of Texas) On: Anderson, David (Texas Education Agency) HB 107 For: Gustafson, Lindsay (Texas Classroom Teachers Association) Kostantenalo, Linda (Self) McIntire, Thomas (Texas Licensed Child Care Association) Pewitt, Bill (Texas Licensed Child Care Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) Against: Jackson, Diane (Spring Branch ISD) Soehnge, Karen (Texas Association of School Administrators) Winkler, Sarah (Texas Association of School Boards & Alief ISD) HB 214 For: Lambert, Tim (Texas Home School Coalition) Against: Black, Mike (Self and TAPAAC & Family) Brownson, Amanda (Texas School Alliance) Raab, Ted Melina (Texas Federation of Teachers) Tipton, Sam (Texas Girls Coaches Association) Wall, Marjorie (Texas State Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Anderson, David (Texas Education Agency) Smoot, Samantha (Texas Freedom Network) HB 387 For: Wall, Marjorie (Texas State Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) Wilkerson, Glenn (The Children's Center for Self-Esteem) HB 411 For: Bacon, Tim (TSTA) Borden, Sandi (Texas Elementary Principals & Supervisors Association) Douglass, Cathy (Texas Association of School Boards) Melina Raab, Ted (Texas Federation of Teachers) Stone, Jeri (Texas Classroom Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Anderson, David (Texas Education Agency) Smisko, Ann (Texas Education Agency) HB 442 For: Bacon, Tim (Texas State Teachers Association) Gustafson, Lindsay (Texas Classroom Teachers Association) On: Golson, Kathy (Texas Association of School Boards & Texas Association of School Administrators) Jacobs, Billy (TEA) HB 447 For: Lambert, Kay (Advocacy, Inc.) Price, Dennis (Texas Council of Administrators of Special Education) Statman, Rona (The ARC of Texas) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Maxwell, Susan (Texas Council for Developmental Disabilities) HB 495 For: Kostelecky, Carolyn (ACT, Inc.) Against: Bacon, Tim (TSTA) Melina Raab, Ted (Texas Federation of Teachers) Sanchez, Joe (Mexican American Legal Defense and Educational Fund) Whitsett, Jo-Hannah (Association of Texas Professional Educators) HB 521 For: Melina Raab, Ted (Texas Federation of Teachers) Scheberle, Drew (Texas Business & Education Coalition) Stone, Jeri (Texas Classroom Teachers Association) Against: Sanchez, Joe (Mexican American Legal Defense and Educational Fund) HB 567 For: Bacon, Tim (TSTA) Gustafson, Lindsay (Texas Classroom Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Harris, Dwight (Texas Federation of Teachers) Jacobs, Billy (TEA) HB 817 For: Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Smisko, Ann (Texas Education Agency) HB 818 For: Whitsett, Jo-Hannah (Association of Texas Professional Educators) HB 1406 For: Breeding, John (Self and Texans for Safe Education) Dolan, Moira (Self) Galloway, Charles (Self and Graham B Galloway) Gerstenschlager, MerryLynn (Self and Texas Eagle Forum) McIntosh, Glenn (Suicide and Violence Education Resource Services) Prough, Andrew (Citizens Commission on Human Rights) Uhr, Pam (Self and ACLU of Texas) Against: Gustafson, Lindsay (Texas Classroom Teachers Association) Melina Raab, Ted (Texas Federation of Teachers) On: Price, Dennis (TCASE & Amarillo ISD) Rewoldt, Christian (Self) Tabone, Stephanie (Texas Nurses Association) HB 1440 For: Bacon, Tim (TSTA) Borden, Sandi (Texas Elementary Principals & Supervisors Association) Douglass, Cathy (Texas Association of School Boards) Melina Raab, Ted (Texas Federation of Teachers) Stone, Jeri (Texas Classroom Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) HB 1441 For: Douglass, Cathy (Texas Association of School Boards) Salyards, Cheryl (Texas Council for Administrators in Special Education) Statman, Rona (The ARC of Texas) On: Maxwell, Susan (Texas Council for Developmental Disabilities) HB 1518 For: Gustafson, Lindsay (Texas Classroom Teachers Association) On: Douglass, Cathy (Texas Assoc. of School Boards) Price, Gary (Comptroller of Public Accounts) Wisnoski, Joe (Texas Education Agency) HB 2101 Against: Bacon, Tim (TSTA) Borden, Sandi (Texas Elementary Principals & Supervisors Association) Gustafson, Lindsay (Texas Classroom Teachers Association) Melina Raab, Ted (Texas Federation of Teachers) Smoot, Samantha (Texas Freedom Network) Soehnge, Karen (Texas Association of School Administrators & Texas Association of School Boards) Whitsett, Jo-Hannah (Association of Texas Professional Educators) HB 2102 For: Gustafson, Lindsay (Texas Classroom Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) Against: Douglass, Cathy (Texas Association of School Boards) Eckhart, Harley (Texas Elementary Principals & Supervisors Association) Soehnge, Karen (Texas Association of School Administrators) On: Anderson, David (Texas Education Agency) HB 2217 Against: Bacon, Tim (TSTA) Gustafson, Lindsay (Texas Classroom Teachers Association) Melina Raab, Ted (Texas Federation of Teachers) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Anderson, David (Texas Education Agency) HB 2220 For: Scheberle, Drew (Texas Business and Education Coalition) Stone, Jeri (Texas Classroom Teachers Association) On: Anderson, David (Texas Education Agency) Bacon, Tim (TSTA) Floyd, Robert (Texas Music Educators Association) Melina Raab, Ted (Texas Federation of Teachers) HB 2520 For: Bacon, Tim (TSTA) On: Anderson, David (Texas Education Agency) Harris, Dwight (Texas Federation of Teachers) Jacobs, Billy (TEA) HB 2804 For: Collins, Robby (Mike Moses & Dallas ISD) Gustafson, Lindsay (Texas Classroom Teachers Association) Wall, Marjorie (TSTA) HB 2825 For: Borden, Sandi (Texas Elementary Principals & Supervisors Association) Douglass, Cathy (Texas Association of School Boards) Against: Gustafson, Lindsay (Texas Classroom Teachers Association) Melina Raab, Ted (Texas Federation of Teachers) Wall, Marjorie (Texas State Teachers Association) Whitsett, Jo-Hannah (Association of Texas Professional Educators) On: Lambert, Kay (Advocacy, Inc.) HB 2964 For: Nunez, Johnny (Self) Olson, John (Self and City of Stafford) Scarcella, Leonard (City Council - City of Stafford) On: Anderson, David (Texas Education Agency)


Antepartum Assessment
Instructions: Check conditions if present, do not check if uncertain or not present
CMQCC High-Risk Checks:
Placenta previa or low lying placenta
Suspected placenta accreta/percreta
Hematocrit less than 30
Active bleeding (greater than show) on admission
Platelet count less than 100,000
Known coagulopathy
CMQCC Medium-Risk Checks:
Previous cesarean delivery or uterine surgery
Multiple gestation
Greater than 4 previous vaginal deliveries
Chorioamnionitis
History of peripartum hemorrhage
Large uterine leiomyoma
Macrosomia (estimated fetal weight > 4 kg)
Morbid Obesity (BMI greater than 35 kg/m^2)
Additional Maternal Antepartum Checks:
Age over 40
Arrhythmia
Asthma
Caucasian race
Cervical cerclage
Chronic hypertension
Diabetes (type I, type II, gestational)
Clinical depression
Endometritis
First delivery
Heart failure
Heart disease (congenital, rheumatic, myocarditis/cardiomyopathy, valve disorder, artificial valves, or other)
Infant renal insufficiency
Lupus
Maternal infertility
Maternal renal abnormality (glomerulonephritis, pyelonephritis, lupus nephritis, nephrotic syndromes, nephrolithiasis, transplant, renal abscess, or other)
Maternal acute renal failure
Placental abruption
Polyhydroamnios
Preeclampsia
Sickle cell trait
Smoking (maternal smoking history)
Urinary tract infection
Reset
Submit


The Balance
Combat Jobs
- Tanks
- Healers
- Melee
- Casters
- Physical Ranged
Other Jobs
- Crafters
- Gatherers
- Limited Jobs
Fight Encounters
- Extreme
- Unreal
- Savage
- Ultimate
- Exploratory Content
Tools
- Add-ons
- BiS Solvers
- Connection Tools
- DoH/DoL Tools
- Log Analysis Tools
- Rotation Solvers
Other Guides
- New Player Resources
- Endgame Content & Gearing Guide
- Island Sanctuary
Info
- About
- Contributing
- License
{{/* End flex */}}


number-crunching
`Prev `__
N
`Next `__
--------------
**number-crunching**: n.
[common] Computations of a numerical nature, esp. those that make
extensive use of floating-point numbers. The only thing
`*Fortrash* <../F/Fortrash.html>`__ is good for. This term is in
widespread informal use outside hackerdom and even in mainstream slang,
but has additional hackish connotations: namely, that the computations
are mindless and involve massive use of `*brute
force* <../B/brute-force.html>`__. This is not always
`*evil* <../E/evil.html>`__, esp. if it involves ray tracing or fractals
or some other use that makes `*pretty
pictures* <../P/pretty-pictures.html>`__, esp. if such pictures can be
used as screen backgrounds. See also `*crunch* <../C/crunch.html>`__.
|image0|
Hydrodynamic `*number-crunching* `__.
(The next cartoon in the Crunchly saga is
`74-12-29 <../W/winged-comments.html#crunchly74-12-29>`__. The previous
cartoon was `74-08-18 <../W/water-MIPS.html#crunchly74-08-18>`__.)
--------------
+-------------------------+----------------------------+----------------------------+
| `Prev `__ | `Up <../N.html>`__ | `Next `__ |
+-------------------------+----------------------------+----------------------------+
| nuke | `Home <../index.html>`__ | numbers |
+-------------------------+----------------------------+----------------------------+
.. |image0| image:: ../graphics/74-12-25.png


A subtitle displaying 'this is the first subtitle of 2011' will appear at 5 seconds and disappear at 15 seconds.
A subtitle displaying 'this is the second subtitle of 2011' will appear at 20 seconds and disappear at 45 seconds.
Your user agent does not support the HTML5 Video element.


Muscle car flexes again after surviving Fort McMurray wildfires
by David Ewasuk, CTV News EdmontonEDMONTON -- Murray and Shelley Kellington had their first date in a 60s era muscle car. And when he had enough money, Murray bought an even better version of it.
"I called the dealer and said, 'What do you want for it?' And he told me the price and I said, 'I’ll take it.'" He tells CTV.
Then the Fort McMurray wildfires of 2016 happened.
The couple lost its house and motorhome and they also assumed their 1968 Buick Skylark GS 400 was destroyed where it sat on their driveway.
But firefighters who battled the 2016 blaze that decimated hundreds of homes had taken video. Someone sent it to Shelley.
“It was taken at night and it was on our street and when the camera would go by; it looked like there was a little bit of blue but it was pretty dark,” Shelley told CTV News.
There was blue. In fact, there was plenty of the original paint job.  Bubbled and blistered and down to bare metal.
“When we saw the condition it was in, I mean the tires didn’t even melt, which is remarkable if you had seen the area,” she says.
The car is named after a European songbird, but she and Murray say they knew right then: it had to rise from the ashes like a phoenix.
“It was all there was left, so there really was no question that we would get it fixed,” says Shelley.
Two years ago, they sent the vehicle to a restoration shop in St. Albert. The owner of Red Line Custom Autobody admits every muscle car and hotrod owner is passionate about their vehicle.
And they all have a back story. He says this one is pretty special.
“You can tell when you talk to the customer, to the people, you can feel the emotion.
“It’s gratifying to help them see their dream come back alive again” Wouters adds.
Now the chrome is better than factory and the couple says the convertible roof retracts “like butter."
The only thing missing is sunshine and the open road. That’s something they hope to see much more of after the fire prompted a remodeling of their lives as well.
Both retired from their oilsands jobs and moved closer to Edmonton. They vow that the Skylark won’t be sitting on the driveway very often anymore.
"The story now on this car has just grown so much since the fire. It’ll be in this family, I think, long after we’re gone,” Murray says.


Example 4: For Want of a Nail
July 28, 2017Sometimes small details can have big consequences. There is a famous proverb that makes this point, that goes something like this:
For want of a nail the shoe was lost.
For want of a shoe the horse was lost.
For want of a horse the rider was lost.
For want of a rider the message was lost.
For want of a message the battle was lost.
For want of a battle the kingdom was lost.
And all for the want of a horseshoe nail.
But suppose you are an unfortunate farrier (specialist who nails horseshoes to hooves) that did, indeed, attach a horseshoe recently with one fewer nails than is proper. And yes, indeed, the kingdom has subsequently collapsed. You might be wondering if you might be the one to blame. Given the observables of a missing nail and the collapse of the kingdom, you'd like to know the likelihood that the first is the cause of the second. Let's use Etcetera Abduction to answer this question.
Let's start with what we observe. The kingdom, which you know by its name "K" has definitely collapsed. There is was some nail, which you don't know the name of, that you failed to set on a particular shoe, which you are happy to call "S" (for shoe).
;; The observables (collapse K) (missing_nail n S)
Notice that the nail is represented by the lowercase letter "n". The other arguments are all logical constants represented with uppercase letters: "K" is a particular known kingdom, and "S" is a particular known shoe. By representing "n" as a lowercase letter, we are signifying that "n" is a variable. Specifically, "n" is an existentially quantified variable. What we are saying here is that there exists some nail that is missing in the shoe "S", but we don't know its name.
This is in contrast to all of the variables that we've seen previously in our axioms. In those axioms, all of the variables are universally quantified variables. They indicate that they can take on any value, and the axiom will still be true.
For example, the axioms that encode the prior probabilities of our observables both have universally quantified variables in them.
;; Priors of the observables (if (etc0_collapse 0.001 x) (collapse x)) (if (etc0_missing_nail 0.001 x y) (missing_nail x y))
Because "x" and "y" in these axioms are universally quantified variables, these axioms state that anytime these etc0
predicates are true for any entity in the domain, be it a kingdom "K" or a pepperoni pizza "P", then the consequent is true as well, e.g. the pepperoni pizza has collapsed. While it may be a bit disconcerting to be writing an axiom that might apply to a pepperoni pizza in this manner, remember that we're doing abductive reasoning here. These etc0
literals are never going to be observed directly - they can only be assumed as antecedents when trying to explain a consequent. As long as we don't observe collapsing pizzas in the world, the etc0_collapse
literal will never be considered as its explanation.
If we execute our abduction program with these observables and these prior probability axioms, we get something interesting:
$ python -m etcabductionpy -i nail-collapse.lisp ((etc0_collapse 0.001 K) (etc0_missing_nail 0.001 $1 S)) 1 solutions.
There is only one solution to this interpretation problem so far, which is simply to assume the prior probabilities. But notice that "$1" appears in the "missing_nail" assumption. Etcetera Abduction has invented a name for the nail that was missing in shoe "S". Technically, this is called a "Skolem constant" after the Norwegian mathematician Thoralf Skolem. You can think of it this way: our abductive reasoning engine needed some way to refer to a specific entity in the world that didn't have a name, so it made up one by joining a dollar-sign "$" with a unique integer "1". If the engine had the occasion to refer to this entity elsewhere, it would have called it "$1" again. If instead it needed to talk about some other entity that was distinct but also unnamed, it might call it "$2" or "$3".
When we graph the best solution, another interesting thing happens:
Notice how only 1 of our 2 observables are plotted with a double line around the literal. Why is that?
The reason is that the literals that are are entailed by our solution are not exactly the same as our observations. We said that we observed an "n", but the assumptions entail a "$1" instead. What's up with that?
This is because Etcetera Abduction doesn't keep track of the names of existential variables that you've provided in the observables, e.g. "n" in the example above. When its finished its search for entailing assumptions, it changes all variables into Skolem constants - effectively giving a name to any entity whose name wasn't previously known, including those entities that originally appeared in the observables. Technically speaking, however, all sets of assumptions do actually entail the given observations, but it requires a bit of extra reasoning to recognize that the existential in the observable is the same as the named Skolem constant. The graphing algorithm doesn't do this extra reasoning step, so it doesn't recognize that (missing_nail $1 S)
entails (exists (n) (missing_nail n S))
. Thus, no double line around the inference.
Confused? Don't worry about it. Just know that any time your observables have existential variables in them (lowercase letters), your graphs will be drawn without double lines around them, and those lowercase letters will be replaced with dollar-signs and numbers.
With that behind us, let's get down to this business of the collapse of the kingdom. It's true that kingdoms can be lost when a battle is lost. I guess that this happens about half the time when you have battling kingdoms.
;; For want of a battle the kingdom was lost (if (and (battle_lost_to x y) (etc1_collapse 0.5 x y)) (collapse x)) (if (etc0_battle_lost_to 0.001 x y) (battle_lost_to x y))
This additional knowledge doesn't change our top interpretation, but now we have a second-best interpretation. Here, we've got to imagine some "$2" exists, which is the name given to the kingdom that defeated "K" in battle.
Let's keep going. I estimate that missing battle messages lead to lost battles about half the time. Missing riders lead to missing messages about half the time. Missing horses lead to missing riders about half the time. Missing shoes lead to missing horses about half the time. And finally, missing nails lead to missing shoes about half the time. Let's encode these conditional probabilities and see what happens.
;; For want of a message the battle was lost (if (and (missing_message_about m y) (etc1_battle_lost_to 0.5 x y m)) (battle_lost_to x y)) (if (etc0_missing_message_about 0.001 m y) (missing_message_about m y)) ;; for want of a rider the message was lost (if (and (missing_rider r m) (etc1_missing_message_about 0.5 r m y)) (missing_message_about m y)) (if (etc0_missing_rider 0.001 r m) (missing_rider r m)) ;; For want of a horse the rider was lost (if (and (missing_horse h r) (etc1_missing_rider 0.5 h r m)) (missing_rider r m)) (if (etc0_missing_horse 0.001 h r) (missing_horse h r)) ;; For want of a shoe the horse was lost (if (and (missing_shoe s h) (etc1_missing_horse 0.5 h s r)) (missing_horse h r)) (if (etc0_missing_shoe 0.001 s h) (missing_shoe s h)) ;; For want of a nail the shoe was lost (if (and (missing_nail n s) (etc1_missing_shoe 0.5 n s h)) (missing_shoe s h))
Ok, now its time for the moment of truth. Is your sloppy horseshoeing the cause of the collapse of the kingdom? Let's graph the top interpretation:
$ python -m etcabductionpy -i nail-collapse.lisp -g | util/dot2safari
Phew! The best interpretation is still the priors. Hopefully that will help you sleep better at night.
Let's use the "grep" command to find interpretations further down the list where the missing nail plays a role in the collapse of the kingdom.
$ python -m etcabductionpy -i nail-collapse.lisp -a | grep "etc1_missing_shoe" $
Uh oh. That is not good. There are no interpretations that involve the missing nail. Did we mess up the axioms in some way? No, they are all syntactically correct. What is the problem?
The problem is the length of the causal chain that links missing nails to the collapse of the kingdom. Beginning from the collapse, we need to backchain on 6 successive axioms to get to a missing nail, and one more to get to the prior probability of that missing nail. That is seven steps of backchaining, but the Etcetera Abduction engine has a default depth of only five steps. Given the default setting, the engine never considers explanations deeper than a missing horse, and therefore never makes the connection to the missing nail.
What happens if we set the depth to seven, using the "--depth" (or "-d") flag, and graph the top result.
$ python -m etcabductionpy -d 7 -i nail-collapse.lisp -g | util/dot2safari
Oh no! The collapse of the kingdom really was your fault! The best interpretation indicates that the missing nail, some horse "$4", some rider "$5", some message "$2" about rival kingdom "$3" all led to the collapse of kingdom "K".
Now, before you wander off in self-pity about your failings as a farrier, you might want to consider whether our probability estimates are actually reasonable. In this example, we set all of the prior probabilities to 0.001 (very unlikely), but set all of the conditional probabilities to 0.5 (coin-toss likely). As it stands now, we have the conditional probability of the collapse of the kingdom given a missing nail at around 0.015625 (0.5 ^ 6), or 1/64. That actually seems really high, when you think about all of the other crummy farriers in the kingdom, and how sloppy they are with their nails. If skipping a nail would really lead to the collapse of the kingdom 1 in 64 times, the kingdom would not have ever lasted more than a single day. Something must be wrong with our numbers.
Indeed, the conditional probabilities in our axioms are way, way too high. The reasons are subtle, though, and require us to think very carefully about the universally quantified variables in our axioms. Let's take a look at one of our axioms, and consider exactly what it is that we've said about its conditional probability:
;; For want of a nail the shoe was lost (if (and (missing_nail n s) (etc1_missing_shoe 0.5 n s h)) (missing_shoe s h))
On the surface, this looks fine. We're trying to say that if your horse is missing a nail in its horseshoe, its going to fall off about half of the time. But actually, that is not precisely what this axiom is saying. Remember, all of the variables in these axioms are universally quantified variables. That means, the axiom is true for any assignment of these variables to any entities in the world of our problem.
A good technique for thinking about this axiom is to substitute the variables for imagined constants, and seeing if the numbers still make sense. Here's what it would look like if we are talking about a specific nail "NAIL9", a specific shoe "SHOE14", and a specific horse "HORSE93":
;; For want of NAIL9, SHOE14 was lost on HORSE93 (if (and (missing_nail NAIL9 SHOE14) (etc1_missing_shoe 0.5 NAIL9 SHOE14 HORSE93)) (missing_shoe SHOE14 HORSE93))
Now, let's consider whether our conditional probability estimate is still reasonable. What is the conditional probability of "HORSE93" missing "SHOE14", given that "SHOE14" is missing "NAIL9"? Sure, shoes without nails fail half the time, but what is the chance that this particular shoe ended up on this particular horse?
Let's further estimate there are at least 1,000 horses in this kingdom, and each one of them has four hooves, and each hoof takes a shoe with eight nails. The conditional probability that we're looking for is this one, for the conditional probability of seeing a particular shoe missing from a particular horse given that a particular nail is missing from that very shoe:
Pr[(missing_shoe SHOE14 HORSE93) | (missing_nail NAIL9 SHOE14)]
Put this way, we can see that we must factor in the likelihood that this particular crummy shoe-job was applied to this particular horse, out of all 1,000 of the horses in the kingdom (1/1000), and multiply that by the likelihood of loosing the shoe due to the missing nail (1/2). The likelihood of this particular horse missing this particular shoe, given that the shoe is missing a nail, is closer to 1/2000, or 0.0005. And because this conditional probability is the same regardless of which particular nail, shoe, and horse we're concerned with, we should change or original axiom to reflect the more accurate estimate:
;; For want of a nail the shoe was lost (if (and (missing_nail n s) (etc1_missing_shoe 0.0005 n s h)) (missing_shoe s h))
We should really fix the numbers in the other axioms via a similar analysis, but even with this change we have a new order in our interpretations:
$ python -m etcabductionpy -d 7 -i nail-collapse.lisp -a ((etc0_missing_nail 0.001 $1 S) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3) (etc1_missing_horse 0.5 $4 S $5) (etc1_missing_message_about 0.5 $5 $2 $3) (etc1_missing_rider 0.5 $4 $5 $2) (etc1_missing_shoe 0.5 $1 S $4)) ((etc0_collapse 0.001 K) (etc0_missing_nail 0.001 $1 S)) ((etc0_battle_lost_to 0.001 K $2) (etc0_missing_nail 0.001 $1 S) (etc1_collapse 0.5 K $2)) ((etc0_missing_message_about 0.001 $2 $3) (etc0_missing_nail 0.001 $1 S) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3)) ((etc0_missing_nail 0.001 $1 S) (etc0_missing_rider 0.001 $4 $2) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3) (etc1_missing_message_about 0.5 $4 $2 $3)) ((etc0_missing_horse 0.001 $4 $5) (etc0_missing_nail 0.001 $1 S) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3) (etc1_missing_message_about 0.5 $5 $2 $3) (etc1_missing_rider 0.5 $4 $5 $2)) ((etc0_missing_nail 0.001 $1 S) (etc0_missing_shoe 0.001 $6 $4) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3) (etc1_missing_horse 0.5 $4 $6 $5) (etc1_missing_message_about 0.5 $5 $2 $3) (etc1_missing_rider 0.5 $4 $5 $2)) ((etc0_missing_nail 0.001 $1 S) (etc0_missing_nail 0.001 $6 $7) (etc1_battle_lost_to 0.5 K $3 $2) (etc1_collapse 0.5 K $3) (etc1_missing_horse 0.5 $4 $7 $5) (etc1_missing_message_about 0.5 $5 $2 $3) (etc1_missing_rider 0.5 $4 $5 $2) (etc1_missing_shoe 0.5 $6 $7 $4)) 8 solutions.
And here is the graph of the most likely interpretation.
Congratulations! It likely wasn't your crummy job as a farrier that led to the kingdom's collapse. Kingdoms collapse for unknown reasons, and nails fail to be set into horseshoes for unknown reasons. A causal connection between the two is rather unlikely. In fact, its nearly the least likely interpretation that you can imagine, given the knowledge that you have. The only thing less likely that you can imagine is that it was some other missing nail altogether that is to blame, other than the one you observed yourself.
The point of this example is to encourage you to be careful with your conditional probabilities, especially in the case where you are working with variables that only appear in the etcetera literal and the consequent. You are much better off avoiding these axioms altogether.
Fortunately, Etcetera Abduction is perfectly capable of helping you represent the uncertain about whether the horseshoe with the missing nail ended up on a particular horse. All we need to do is add this assumption to the antecedents of our axiom, and make this probability explicit as a prior probability:
;; Alternative formulation of missing shoe axiom (if (and (missing_nail n s) (shoe_on_horse s h) (etc2_missing_shoe 0.5 n s h)) (missing_shoe s h)) (if (etc0_shoe_on_horse 0.001 s h) (shoe_on_horse s h))
Represented this way, the shoe-on-horse assumption is made explicit, as illustrated the following (low-probability) interpretation.
It might be a good exercise for you to rewrite all of the axioms in this manner. This way, you can make explicit the likelihoods that a given rider was on the horse with the missing shoe, that a given message about the enemy was being delivered by that rider, and so forth. Good luck!


I have 24 years in the workforce, the last 18 of which have been spent in Retail Sales. I have enjoyed that work, however, the last 5 years or so have seen some major changes in the industry with larger online competition like Amazon. Because of this I have decided to make a change. I have enrolled in the University of Central Florida Coding Bootcamp - an intensive full-stack web development course. The course covers front-end and back-end technologies such as HTML5, CSS3, Javascript, jQuery, Bootstrap, Firebase, NodeJs, MySQL, MongoDB, Express, Handlebars.js and React. I finish the course in July 2017, however I am eager to find a job that would give me real world experience as soon as possible.
Urban Sunshine is a chain of high-tech garden shops specializing in hydroponics, horticultural lighting and organic garden supplies. I have been a big part of growing the business from a small single location to a chain of 4 locations. My experience at Urban Sunshine has taught me skills in leadership, organization and Business Managment. I also was responsible for running/maintaining the company's e-commerce website.
I started working at Toucan Willie's as a 16 year old diswasher. It was a job that taught me the value of hard work, instilling a strong work ethic. I worked up through each position in the kitchen until reaching a managerial position.
An intensive 26-week long boot camp dedicated to designing and building web applications. Skills learned consist of HTML5, CSS3, Javascript, jQuery, Bootstrap, Firebase, Node.js, mySQL, Express, Handlebars.js (before conculsion of the course we will also cover MongoDB ans React).
A javascript hangman game themed on book titles. Letter choices show as an old typewriter and the user can click them to choose. Wrong choices will progress a series of hangman images. Games tracks wins and losses.
View ProjectA javascript trivia game themed on people that have influenced civilization. It takes the user through 10 random questions picked from a list of 40. The game has a 1:30 timer that runs while the questions are up and paused during the correct/wrong reveals. A synopsis is given at the end of the round.
View ProjectA gif finding app that works through a javascript AJAX call to the Giphy API. There are preloaded search term buttons with a TV show theme. Users can create their own search term buttons. Users can choose to return 5, 10, 15, 20 or 25 gifs to return. The results are organized into 3 columns.
View ProjectAn app that matches the user to the Game of Thrones character that best matches their personality based on an answer comparison of a 10 question survey. There is also a survey that will match the user to another fan of GoT and add the users info for future searches.
View ProjectI was group leader on this project made by a team of 4 students. It is an entertainment application that allows users to look up movies and get detailed information including what providers currently offer said movie to stream. It connects to several APIs including guide-box.
View ProjectThis is a journal that gardeners can use to post, share, comment with other gardeners their experiences in growing various crops.
View Project


Dataset and Model¶
Table of Contents
Multi-Task¶
Dataset¶
GLUE Benchmark: The General Language Understanding Evaluation (GLUE) benchmark is a collection of resources for training, evaluating, and analyzing natural language understanding systems.
 모든 질의에 대한 답변은 해당 Wikipedia 아티클 문단의 일부 하위 영역으로 이루어집니다. Stanford Question Answering Dataset(SQuAD) v1.0과 동일한 방식으로 구성되었습니다.
SQuAD: Stanford Question Answering Dataset is a reading comprehension dataset, consisting of questions posed by crowdworkers on a set of Wikipedia articles, where the answer to every question is a segment of text, or span, from the corresponding reading passage, or the question might be unanswerable.
Model¶
BiDAF: Birectional Attention Flow for Machine Comprehension +
No Answer
DocQA: Simple and Effective Multi-Paragraph Reading Comprehension +
No Answer
QANet: Combining Local Convolution with Global Self-Attention for Reading Comprehension
BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding
Regression¶
GLUE Benchmark: The General Language Understanding Evaluation (GLUE) benchmark is a collection of resources for training, evaluating, and analyzing natural language understanding systems.
STS-B
Semantic Parsing¶
Dataset¶
WikiSQL: A large crowd-sourced dataset for developing natural language interfaces for relational databases. WikiSQL is the dataset released along with our work Seq2SQL: Generating Structured Queries from Natural Language using Reinforcement Learning.
Sequence Classification¶
Dataset¶
GLUE Benchmark: The General Language Understanding Evaluation (GLUE) benchmark is a collection of resources for training, evaluating, and analyzing natural language understanding systems.
CoLA, MNLI, MRPC, QNLI, QQP, RTE, SST-2, WNLI
Token Classification¶
Dataset¶
NER - CoNLL 2013: The shared task of CoNLL-2003 concerns language-independent named entity recognition. Named entities are phrases that contain the names of persons, organizations, locations, times and quantities.


It is Radventure's mission to help travellers maximize their time, pocketbooks, and smiles while experiencing adventures in the great outdoors.
After parting ways with her “personal adventure guide” (aka break-up with boyfriend), Andrea felt a large void in her ability to really get out and about to experience the outdoors as she had before. One day, as she was going for a run, she had an A-HA! moment that she was likely not alone in this feeling of frustration. What if there were others out there with the desire to see, experience and conquer but they just need a local friend to help show them the way? That was when Radventure was born. We’ve all been there. You’re in a rad new place, but aren’t quite sure where to start. You wish you had a local buddy to give you the inside scoop. You chat with ski techs, bike shop staff, and bartenders, but what you really want is local to show you the sick spots so you can make the most your time outside.