--- layout: doc title: Documentation ---
The node you are looking for is at Default values for generic settings.


Schedule: {{ scrape_status_result["cron_pretty"] }}
Last scrape: {{ scrape_status_result["last_modification_time_pretty"] }}
{% if scrape_status_result['last_scrape_failed'] %}Warning: Last scrape was more then 1 day ago. You should look in the logs.
{% endif %}


doint some studd some new stuff
Bootstrap 101 Template
Weather Today
Enter your city to get weathercast today.
Find My Weather


J
C
J
Croft
Toggle navigation
9
You have 9 tasks
Design some buttons
20%
20% Complete
View all tasks
×


Well, besides setup scripts the other thing I want to take from Rails is building testability into the system. But I haven't quite figured out how to do that. The specific idea I want to take is that of data fixtures -- data that puts the site into a "known" state that can be tested against. In the Rails world that's a bunch of rows to be inserted into the database, which is a particular case I'm interested in, but of course it should be more general.
That's not too terribly hard; it's mostly grunt work. Not super-simple, but not hard. I've added the necessary configuration file hooks to handle different kind of environments running out of the same directory: include() and load(), both of which have access to previous files, so you could do:
if debug: include('database_debug.conf') else: include('database.conf')
Or any number of things, like testing if profile == 'debug'. This kind of flexibility (among other things) makes Python files very useful; I was skeptical at first about Python syntax (having invested much time into an INI-file based configuration), but it makes so many things so easy.
Oh, but back to the actual testing. One thing I like about how things have shaped up in Paste is that testing has been pretty easy. paste.wsgilib has a function raw_interactive(app, path_info) that is quite useful, and I use it in paste.tests.fixture in fake_request(). It lets me do things like:
res = fake_request(p, '/') res.all_okay() # Asserts status is 200 OK, no errors logged assert 'Welcome' in res assert res.header('content-type') == 'text/html'
And so on. There's some things I feel should be tweaked. For instance, it should normal throw an error for any status besides 200 OK (with a keyword to explicitly say that another status is okay or expected). Maybe test for compliant HTML (paste.wdg_validate is a start for this). It should make requests a little easier to perform -- maybe it should be a wrapper around an application, for instance. But it's pretty close as it is, it just needs a little loving to get all the convenience methods in (and a good testing framework is all about convenience). And then you could do the whole thing in doctest, maybe like:
>>> app = FakeApp(this_app) >>> res = app.post('/login', data={'username': 'bob', 'password': 'bob'}) >>> res.element(id='message')
User 'bob' logged in

And so on. You could put this right into your object's docstrings. Using things like doctest_xml_compare you can make your test say just what you mean, and no more.
That could be really sweet. Interested? Join paste-users and we'll talk there.
Update: There's been some progress on this in paste.tests.fixture.TestApp
Do you have an RSS feed for this site?
Auto-discoverable, yes; it's at https://ianbicking.org/feeds/new_pages.xml
Awesome. Exactly what I was looking for. Loved pbp and twill, but couldn't integrate it very well with py.test.  :)


Police investigate violent incidents, robberies in Tuggeranong
by Peter BrewerMultiple incidents of robbery using weapons, injuries to victims and threat of violence in Tuggeranong on Saturday night, all believed to involve the same perpetrators, are under active investigation by police.
The four incidents occurred between 9.30am and 11.30pm and involved up to four men seen driving around the areas of Calwell, Chisholm, Erindale and Kambah in a red or maroon-coloured sedan without a rear bumper.
The first incident happened outside the Calwell Tavern around 9.47pm when a man is reported to have produced a knife and demanded a woman hand over her handbag. She complied with his demands.
Some time later at a car park near the Kambah Tavern, a man reportedly made demands of another man, however, nothing was taken.
At the Domino's pizza outlet in Kambah, a male made demands of the staff, however, he fled the building without taking anything.
At the Domino's pizza outlet in Erindale demands were allegedly made of staff, however, the perpetrator again fled without taking anything.
Around 11.13pm at the car park outside the Vikings Chisholm club, a woman was threatened and her handbag stolen. The woman received minor injuries as a result of the incident.
Police are appealing for anyone who may have dash cam footage or had seen the vehicle driving around Tuggeranong on Saturday night with the men inside, or may have witnessed any of the incidents, to contact Crime Stoppers either via the website or by calling 1800 333 000.
Information can be provided anonymously.


Classroom View
Overview
Class Teacher: Class Teacher's Name Here
Students
| # |
Reg No |
First Name |
Last Name |
Action |
| 1 |
12351 |
Mark |
Otto |
Remove
Edit
|
| 2 |
12353 |
Jacob |
Thornton |
Remove/Edit |
| 3 |
12356 |
Larry |
the Bird |
Remove/Edit |
Subjects
| # |
Subject |
Teacher |
No of Students |
Optional/Compulsory |
Exams |
| 1 |
Mathematics |
Luxman |
30 |
|
|
| 2 |
Science |
Sothylinkam |
30 |
|
|
| 3 |
Geography |
Kokulan |
18 |
|
|


{{SUBJECT Your request needs help}}
Hi {{username}},
A {{type}} request you've created needs more information. We try and find everything needed for you, but in this case we can't.
You can find out what we need here: https://openaccessbutton.org/request/{{_id}}.
Hopefully you'll find the answers needed here: {{url}}. If you can't find an author's email address, we suggest Googling for the lead author's address, or if that doesn't work, any other author.
Once you've provided the information, we'll moderate your request and send it!
Many thanks,
Natalia
Open Access Button Request Manager


- valueOf(String) - Static method in enum net.mdwright.var.objects.Model
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum net.mdwright.var.objects.VolatilityMethod
-
Returns the enum constant of this type with the specified name.
- values() - Static method in enum net.mdwright.var.objects.Model
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum net.mdwright.var.objects.VolatilityMethod
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- VarCalculator - Interface in net.mdwright.var
-
Interface for different approaches to VaR calculations.
- VarController - Class in net.mdwright.var
-
Controller class for Var Calculations.*
Note: influence from Calculator code 2nd Year software Engineering Coursework
- VarController(ViewInterface) - Constructor for class net.mdwright.var.VarController
-
Constructor method to assign a view to this controller and setup observing methods.
- VarMath - Class in net.mdwright.var
-
Class for supporting calculations used in value at risk models.
- VarMath() - Constructor for class net.mdwright.var.VarMath
-
- VarModel - Class in net.mdwright.var
-
Class to send calculation requests to appropriate calculating classes.
- VarModel() - Constructor for class net.mdwright.var.VarModel
-
- ViewController - Class in net.mdwright.var
-
Controller class for changing screens at main menu.
- ViewController(EntranceGUI) - Constructor for class net.mdwright.var.ViewController
-
Constructor method which adds observers to the menu screen.
- ViewInterface - Interface in net.mdwright.var.application
-
Interface class for GUI Views.
- VolatilityMethod - Enum in net.mdwright.var.objects
-
Enum object for methods for calculating variance and volatility.
- VolatilityModel - Class in net.mdwright.var
-
Abstract class for volatility models.
- VolatilityModel() - Constructor for class net.mdwright.var.VolatilityModel
-
- VolatilityModelFactory - Class in net.mdwright.var
-
Factory class for creating VolatilityModels.
- VolatilityModelFactory() - Constructor for class net.mdwright.var.VolatilityModelFactory
-


A jQuery UI widget that enables building a list of multiple items using an autocomplete entry box without imposing specific HTML structure or CSS style rules.
The goal of this project is to create a widget that is as unopinionated about the structure and styling of the content as possible. There are many variations of building a list of items by looking each item up using a type ahead field but few will ever look the same. However, the basic underlying functionality is very similar. This widget emphasizes building features that encapsulate that control logic and provide many hooks along the way to customize the behavior.
The source for this search is the top 200 baby names of 2012.
Learn more about this demo here.
MultiSearch has dependencies on jQuery, jQuery UI, and Underscore (if you prefer LoDash, it can be used instead). The widget makes extensive use of several of the data transversal and manipulation function in the Underscore library which helps reduce the code size and maintenance (no reason to reinvent that wheel). You can download these or just use the CDN versions:

Next, include the MultiSearch file and you're ready to go:

Here's some example mark up that defines the container of the widget and the four required points in that structure where the widget should attach certain functionality:

<input data-role="input" type="text" placeholder="Search..."/>

These roles can be placed anywhere inside the widget's containing element (although, you may need to change a few options on the widget so it makes the right assuptions about where a given item is located).
Once that is defined, you can target the containing element and initialize it with the
multisearch widget plugin. The only required option is the source
data which
can simply be an array of objects. Everything else will default to provide basic functionality.
$(function() {
$("#myMultiSearch").multisearch({
source: [
{name: 'One'},
{name: 'Two'},
{name: 'Three'},
{name: 'Four'}
],
});
});
If you run the above code with no styling, it will work fine but there won't be any highlighting and the selected items will run together. With the HTML defined above, these styles will make it look a little better:
ul {
list-style: none;
margin: 0;
padding: 0;
}
li {
margin: 0;
padding: 0;
}
a {
color: black;
margin: 3px;
}
a:hover, a.hover, li.hover a {
color: green;
}
.picker {
border: 1px solid silver;
padding: 10px;
}
The example is straight from the basic demo below. Take a look at it for the full source and to see it working (with and without the styling). I also setup a jsFiddle with the basic demo that you can use to tinker with some of the options and styling.
The mark up needs to define several roles via a data-role
attribute. The widget
will use those binding points to attach the required control logic. The list of roles include:
selected-list
- the containing element where selected items should be renderedselected-item
- auto-assigned by the widget as new items are generated with the
factory template function defined by formatSelectedItem
. These elements will be direct children
of the selected-list
elementinput
- this should be the input box where the user will type searches. Depending on where it
is positioned relative to selected-list, you may need to adjust the pickerPosition
option so
keyboard interation works as expectedpicker
- container for the picker list. This will be the target of positioning and show/hide
methods as a search is performedpicker-list
- the containing element where search results should be renderedpicker-item
- auto-assigned by the widget as new items are generated with the
factory template function defined by formatPickerItem
. These elements will be direct children
of the picker-list
elementThe keyboard can be used to navigate both the picker items when a search is being performed and the list of selected items when no text is in the input box. The navigation will trigger the same hover/active events that would occur if using the mouse.
This is the list of available options when initializing the widget. The only required option
is the source
the widget will use for searching and the item content.
source
: The data source to search. Can be a string, function, or array of objects
function ( term, callback ) { ... }
Default: null
ajaxOptions
:Hash of options that are used in the $.ajax call on a remote resource.
Only used when source is a string representing the path of the resource.
Currently accepts overrides for dataType and method options. Also adds
a custom options:
Default:
{
searchTerm: 'term',
dataType: 'json',
method: 'GET'
}
keyAttrs
: An array of fields in the result object which represent the unique key for the object.
Used to detect duplicate items. If not set, will default to ['id']
Default: [ 'id' ]
searchAttrs
: An array of fields in the result object to search for the entered criteria.
Default: [ 'name' ]
formatPickerItem
: A function that returns an HTML string repesenting the item to add to the suggestion picker
as a search is entered into the input.. The hash returned by the remote server or local cache
is passed to the function. This can be a Underscore template() function.
Default: function( data ) { return '
'+data.name+'
'; }
formatSelectedItem
: A function that returns an HTML string repesenting the item to add to the selected
items list. Called each time a search term is selected from the suggestion picker or,
when not found items are allowed, a new entry is completed. The hash from the result
set is passed to the function. This can be a Underscore template() function.
Default: function( data ) { return ''+data.name+''; }
buildNewItem
: When adding items that are not found in the suggestion picker, this function is called
to define the object that is expected in the formatSelectedItem() template. Generally,
you'll leave the keyAttrs attributes null and set the primary display field with the
text from the input box which is passed to the function.
Default: function( text ) { return { id: null, name: text }; }
minSearchChars
: How many characters need to be typed to trigger a search
Default: 2
searchThrottle
: How quickly can successive searches be triggered. The value is in milliseconds
and uses Underscore's throttle() function to control triggering calls to the
remote resource. This does not affect local cache searching.
Default: 200
maxShowOptions
: How many results to show in the picker. Even if 200 are returned by the server, you
can control how many are actually displayed in the suggestion picker. Set it to zero
to show everything. Ensure you enable some kind of scrolling on the element you define
as the picker/picker-list role if you allow longer lists of items.
Default: 5
minLocalCache
: When to start refining a search against the local cache. Each remote search is saved by term
if the remote result set has less than minLocalCache items in it, each subsequent character typed
will use that result as a basis for searching. This can reduce the number of hits on the remote
resource and can be fine-tuned to match your needs. Set it to zero to disable local refinements
against the cache. If you do use it, make sure any limits on the server side are set high enough
to ensure that a search term that refines the remote search below this threshold will contain all
possible items that could be found if the subsequent searches were run against the server.
Default: 50
preventNotFound
: Can items not found in the suggestion picker be added to the seleced item list. If allowed,
buildNewItem() will be called to allow setting defaults on the object that represents the
search data to be prefilled before calling formatSelectedItem(). The adding and added events
will have the notfound flag set to true when an item will be added that in not in the picker.
Default: false
preventDuplicates
: Using the keyAttrs, should duplicates be prevented. A duplicate event is triggered if one is found
allowing custom UI logic to be defined externally. Otherwise, nothing will happen. The suggestion
picker will remain open and it will appear that the widget is not responding. Items that are not
found in the picker but are added to the selected item list will not be considered a duplicate
unless you provide custom logic during adding that would assign a key.
Default: true
useAutoWidth
: Automatically resize the input box to match the text. Helpful for inline/floating elements so
the input only wraps as needed. Disable if using block elements that you want to fill the
parent space.
Default: true
pickerPosition
: Use jQueryUI.position plugin to position the picker box relative to the input control. The default is the
basic drop-down menu box under the input entry box. Depending on the structure, you may want to adjust this
setting.
Default: { my: 'left top', at: 'left bottom' }
inputPosition
: Where is the input relative to the item list. Determines how the keyboard navigation
moves through the items and where new items are added. Valid values are "start" and "end"
defaults to "end". Depending on where you position the input box, adjust this setting
so the UI interactions make sense.
Default: end
localMatcher
:
For each field defined in searchAttrs, search for the input text using the function below. This is used for both local cache searches and hit highlighting. It should match with the search method from the remote. The default is to look for the search string anywhere in the target field. If you want to match only from the leading edge of the field, you'll need to override this function. If you override it, the function must accept two parameters and return true (needle found in haystack) or false (not found):
function( needle, haystack ) { ... }
Several methods are available to interact with the selected items list via code. These methods all suppress any events that would normally be triggered by user interaction.
value
: Getter/Setter for list of selected items. Use it to retreive the list of items
entered by the user or seed the list with existing items (from a database, etc).
Getting the value returns a shallow clone of the objects in the item list. If you're using nested objects from a shared dataset, be aware you may be referencing them in the returned set.
Setting the value will destory the current selections. If you want more control, use add/remove to selectively update the list.
add
: Add an item to the selection list. Optional second arguement can be used to specify
the position to insert the item. If the item already exists, it will be merged
and trigger rendering the content of the item again such that updated data can be
applied to the list.
remove
: Remove one or all items form the selected list:
Uses the standard jQuery UI interface for triggering events. You can either
define a callback in the options hash or listen to the event by binding to multisearch + event name
ie $.on( 'multisearchadding', ... )
.
Handler function will receive an event and ui argument. The ui object is defined below with each event that is triggered.
duplicate
: trigger when preventDuplicates is true and a selected item from the picker matches
an item already in the item list based on keyAttrs
adding
: triggered before actually adding the item to the item list. Return false to
prevent the the action. You can modify data to affect what is passed to the
template function and retained in the item list.
added
: once the item is added, this event is triggered with the data and element.
removing
: prior to removing the item, this event is triggered to allow canceling
the operation by returning false.
removed
: upon removing the item, this event is triggered
searching
: triggered before searching but immediately after displaying the picker
searched
: triggered after searching has completed and results have been returned by the source
itemaction
: triggered when an element with data-action
is clicked in the item list
itemselect
: triggered when an item is clicked in the item list (no data-action
defined)
Hover/Active events are triggered either when the user uses the mouse (hover/click) or uses the keyboard to navigate (arrows, space bar). A handler can return false to prevent the default action which simply changes classes on the elements. Each event provides the following ui object:
Here is the list of interaction events:
selectedactive
: When a selected item is clicked or selected with the space bar selectedhoverin
: When mousing into an item or using the arrows to navigate selectedhoverout
: When leaving a selected item pickerhoverin
: When mouseover or arrows to a suggested item in the picker list pickerhoverout
: When leaving the item Please open a ticket via the issue log on the GitHub project page:
https://github.com/bseth99/jqueryui-multisearch/issues
Copyright (c) 2013 Ben Olson
Licensed under the MIT License


|
Warm
Tape
(Red Hot Chili Peppers) |
|
Shiver
for me girl
Deliver for me my darling Pushin' up to you A river that runs right thru you Swim for your smile In a blue rock quarry Make it for me baby You won't be sorry Shiver for my now Deliver for me my darling [Chorus:] Miles and miles of nether worlds I roam Settle for love you're never far from home Carry me down into the waters of Carry me down into the waters of love Two of us were made of angels dust I've been around But not around enough Shadow my free form A woman that I could keep warm Quiver for me girl Give me your head and shoulders Shot from the pages of love and glory Sleeping next to you and I'm in your story Shadow my free form A woman that I could keep warm [Chorus] Let's go I know, I make it for two Intuitions only what you take from it I know, I make it for two You were there and I was fortunate I know, I make it for two Shiver for me now Deliver for me my darling A living that I could Be giving to you my sweet love Swim for your smile In a blue rock quarry Make it for me baby You won't be sorry Shot from the pages of Love and glory Sleeping next to you And I'm in your dream Settle for love |


Toggle navigation
Home
Articles
Short Stories
Poetry
Nanotales
Food Blog
Miscellaneous
Contact us
Work with us
NANOTALES
❮
❯


Rizraell:
Thank you. This blue jewel that quivers at the tip of my fingers is indeed a Wind Shard.  Thank you for your trouble.
Would you like to end the Contract? Or would you like to continue collecting?
Say you will end the Contract
Say you will continue


{{product.description}}
Not Yet
Stars: {{review.stars}} {{review.body}} by: {{review.author}} 1 Star 2 Star by:
1 Star 2 Star by:
Stars: {{review.stars}} {{review.body}} by: {{review.author}}


Arabidopsis protein signalling DELLA Physcomitrella plants gibberellin growth Plant F-box {border-style file plant pathway px;} #ffffff;} Selaginella vascular SLY homologues sequences EST Figure GAs proteins (Figure sequence receptors used species ESTs homologue orthologues plants, RGA elongation genome homology moss mosses plants. Additional GID However, contains evolutionary homologous patens receptor related various University components present px; rice using {font-family Biol C-terminal Cell conserved contigs evolution font-size formation gene hormones presence responses sex thaliana tree trees Click Effect LINK Nature analysis closest concentrations degradation double; family limited moellendorffii possible seed treated BMC Cyanidioschyzon Gibberellins Matsuoka Reski SLEEPY Science Ueguchi-Tanaka angiosperms, border-color border-width collection effects existence expressed factors gymnosperms high important known large male merolae molecular proteins, protonemata retrieved solid; transcription unicellular {font-style {font-weight ./--- ./S-()- ./science. Arg Ashikari GRAS Gibberellin Itoh Kobayashi N-terminal Neighbour-Joining Pinus Pp: Sm: Sun algae alignment available bold carboxylesterase cell clear conservation courier; database divergent does domain earlier effect em; exogenous ferns genes genomic germination gibberellins gravitropism higher including indicate indicates mosses. necessary numbers patens, pt;} receptors, region response signalling.


{#
Copyright (c) 2015 The Pycroft Authors. See the AUTHORS file.
This file is part of the Pycroft project and licensed under the terms of
the Apache License, Version 2.0. See the LICENSE file for details.
#}
{% extends "layout.html" %}
{% block content %}
{{ bank_account_table.render('bank_accounts') }}
{% endblock %}


Dial {{ configuration.incomingNumber }} to connect
Outgoing calls made from SIP clients to the PSTN will come from caller id: {{ configuration.callerId }}
If you do not already have a SIP Client we suggest the following:
Your domain {{ configuration.sipDomainName }} is ready to accept SIP registrations
The following SIP credentials have been created. (Default password found on admin page)
| SIP Username | SIP Registration Domain | Extension |
|---|---|---|
| {{ extension.username }} | {{ configuration.localizedSipDomainName }} | {{ extension.extension }} |


The SBLIM CIM Client for Java has a log & trace API that is extensible by application. Since the CIM client is always running in the context of an application it is not desired that it writes its own log files. Therefore the SBLIM CIM Client for Java offers listener interfaces for log & trace messages to which the application can subscribe and forward the messages to the application's logger.
The client distinguishes between log & trace. The audience of the log is an admin at the customer site. The log is localized and contains only the most important messages. The messages are listed in a catalog. The audience of the trace are service engineers and support people. It is not localized, but always in English and may contain the most detailed trace messages desired. The trace is always a superset of the log, which means all messages sent to the log are sent to the trace as well.
The trace is a tool for problem determination that shouldn't be active in normal operation. Tracing at levels of FINE and below creates much more messages than logging. Moreover for every entry in the trace file the stack trace is analyzed to identify the originating method. Having full tracing active therefore will degrade performance.
The message levels are taken from java.util.logging.Level
(decreasing severity):
All messages with a Level less than CONFIG will be sent to the trace only.
An application can register itself as a listener for log and/or trace messages. In order to do so it must implement
the LogListener
and/or TraceListener
interfaces and call
addLogListener()
/
addTraceListener()
on the LogAndTraceManager
instance.
The following code snippet gives an example:
LogAndTraceManager manager = LogAndTraceManager.getManager(); manager.addLogListener(new LogListener() { public void log(Level pLevel, String pMessageKey, String pMessage, Object[] pParameters) { System.out.println("Log message "+pMessageKey+" (Level="+pLevel+"): " +MessageFormat.format(pMessage, pParameters)); } }); manager.addTraceListener(new TraceListener() { public void trace(Level pLevel, StackTraceElement pOrigin, String pMessage) { System.out.println("Trace message (Level="+pLevel+") from " +String.valueOf(pOrigin)+": "+pMessage); } public void trace(Level pLevel, StackTraceElement pOrigin, String pMessage, Throwable pThrown) { System.out.println("Trace message (Level="+pLevel+") from " +String.valueOf(pOrigin)+": "+pMessage); pThrown.printStackTrace(); } });
The System.out.println()
would of course be replaced with the API calls of the applications logger
An application can register itself as a listener for CIM-XML trace messages. In order to do so it must implement
the CIMXMLTraceListener
interface and call
addCIMXMLTraceListener()
on the LogAndTraceManager
instance.
The following code snippet gives an example:
LogAndTraceManager manager = LogAndTraceManager.getManager(); manager.addCIMXMLTraceListener(new CIMXMLTraceListener() { public void trace(Level pLevel, String pMessage, boolean pOutgoing) { System.out.println("CIM-XML "+(pOutgoing ? "sent" : "received") +" by client at level "+pLevel+": "+pMessage); } });
The System.out.println()
would of course be replaced with the API calls of the applications logger
You say "That's interesting stuff, but I just want my plain old log files back." No problem, the SBLIM
CIM Client for Java offers this as well. Via configuration properties you can set up classical file logging out of
the box. See the configuration document for details on how to set configuration properties.
The sblim-cim-client2.properties
file contains documentation on all properties.
Note: If you want to set up the logging via System.setProperty()
calls, make sure that this happens before
any CIM client class is loaded by the classloader. The classic logging is set up in static initializers.


title=In Leighton Buzzard subtitle=Elite Training Centre, Leighton Buzzard. date=2016-02-24 type=page tags=map,leighton buzzard status=published ~~~~~~


This pages allows you to queue samples in a container for data collection
<% if (CONTAINERQUEUEID) { %>
<% if (['disposed', 'in_storage', null].indexOf(CONTAINERSTATUS) > -1) { %>
This container is queued for data collection, you can not modify it without unqueuing it
Unqueue
<% } else { %>
This container is en route for data collection, it cannot be unqueued.
<% } %>
Queuing the container will make the queued items immutable, please make sure you have added all sub samples, and that they have valid experimental plans


UIToggle
class UIToggle
extends
UIControl
Represents a toggle component with an optional text label.
Constructor
(): UIToggle
.withName() static
(name: string,
label
?:
Stringable
): typeof UIToggle
Creates a preset toggle class with given name and label, if any.
.isFocusable()
(): boolean
Returns true if this component can be focused directly using mouse or touch, or manually using UIComponent.requestFocus
. This method may be overridden by derived component classes, but the return value must be constant for each instance.
.isKeyboardFocusable()
(): boolean
Returns true if this component can be focused using the keyboard as well as using other methods (rather than direct manipulation only). This method may be overridden by derived component classes, but the return value must be constant for each instance.
.label
Label text, if any.
.highlightColor
string |
UIColor
Highlight (background) color, if any.
.state
boolean
Current toggle state, true for ‘on’ state, false for ‘off’.
.name
string
Form context property name.
.formContext
UIFormContext
<any>
Bound form context, if any.
.applyStyle() protected
(style?:
UIStyle
): void
Inherited from UIControl.applyStyle
.
.textStyle
Readonly<TextStyle>
Inherited from UIControl.textStyle
.
.decoration
Readonly<Decoration>
Inherited from UIControl.decoration
.
.disabled
boolean
Inherited from UIControl.disabled
.
.shrinkwrap
boolean
Inherited from UIControl.shrinkwrap
.
.propagateComponentEvent() deprecated
(name: string, inner?:
ManagedEvent
, event?: any): void
Inherited from UIComponent.propagateComponentEvent
.
.delegateEvent() protected
(e:
ManagedEvent
, propertyName: string): true
Inherited from UIComponent.delegateEvent
.
.render()
(callback: RenderCallback<Output<
UIRenderable
, any>>): void
Inherited from UIComponent.render
.
.requestFocus()
(): void
Inherited from UIComponent.requestFocus
.
.requestFocusNext()
(): void
Inherited from UIComponent.requestFocusNext
.
.requestFocusPrevious()
(): void
Inherited from UIComponent.requestFocusPrevious
.
.style
Inherited from UIComponent.style
.
.hidden
boolean
Inherited from UIComponent.hidden
.
.dimensions
Readonly<Dimensions>
Inherited from UIComponent.dimensions
.
.position
Readonly<Position>
Inherited from UIComponent.position
.
.accessibleRole
string
Inherited from UIComponent.accessibleRole
.
.accessibleLabel
string
Inherited from UIComponent.accessibleLabel
.
.lastRenderOutput
Output<this, any>
Inherited from UIComponent.lastRenderOutput
.
.isPresetComponent() protected
(): boolean
Inherited from Component.isPresetComponent
.
.getParentComponent()
<TParent extends Component = Component>(ParentClass?:
ComponentConstructor
<TParent>): TParent
Inherited from Component.getParentComponent
.
.getBoundParentComponent()
<TParent extends Component>(ParentClass?:
ComponentConstructor
<TParent>): TParent
Inherited from Component.getBoundParentComponent
.
.emitAction()
(name: string, inner?:
ManagedEvent
, context?:
ManagedObject
): void
Inherited from Component.emitAction
.
.managedId
number
Inherited from ManagedObject.managedId
.
.managedState
Inherited from ManagedObject.managedState
.
.getReferenceCount() protected
(): number
Inherited from ManagedObject.getReferenceCount
.
.getManagedReferrers() protected
():
ManagedObject
[]
Inherited from ManagedObject.getManagedReferrers
.
.getManagedParent() protected
<TParent extends ManagedObject = ManagedObject>(ParentClass?:
ManagedObjectConstructor
<TParent>): TParent
Inherited from ManagedObject.getManagedParent
.
.emit()
<TEvent extends ManagedEvent = ManagedEvent, TConstructorArgs extends any[] = any[]>(e: string | TEvent | (new (...args: TConstructorArgs) => TEvent), ...constructorArgs: TConstructorArgs): this
Inherited from ManagedObject.emit
.
.emitChange()
(name?: string): void
Inherited from ManagedObject.emitChange
.
.propagateChildEvents() protected deprecated
(...types: ((new (...args: any[]) =>
ManagedEvent
) | ((e:
ManagedEvent
) => any))[]): this
Inherited from ManagedObject.propagateChildEvents
.
.activateManagedAsync() protected
(): Promise<any>
Inherited from ManagedObject.activateManagedAsync
.
.deactivateManagedAsync() protected
(): Promise<void>
Inherited from ManagedObject.deactivateManagedAsync
.
.destroyManagedAsync() protected
(): Promise<void>
Inherited from ManagedObject.destroyManagedAsync
.
.onManagedStateActivatingAsync() protected
(): Promise<void>
Inherited from ManagedObject.onManagedStateActivatingAsync
.
.onManagedStateActiveAsync() protected
(): Promise<void>
Inherited from ManagedObject.onManagedStateActiveAsync
.
.onManagedStateDeactivatingAsync() protected
(): Promise<void>
Inherited from ManagedObject.onManagedStateDeactivatingAsync
.
.onManagedStateInactiveAsync() protected
(): Promise<void>
Inherited from ManagedObject.onManagedStateInactiveAsync
.
.onManagedStateDestroyingAsync() protected
(): Promise<void>
Inherited from ManagedObject.onManagedStateDestroyingAsync
.
UIToggle.Presets
extends
UIControl.Presets
UIToggle presets type, for use with Component.with
.
.label
Label text, if any.
.highlightColor
string |
UIColor
Highlight (background) color, if any.
.state
boolean
Toggle state.
.name
string
Form state property.
.textStyle
Partial<{} | TextStyle>
Inherited from UIControl.Presets.textStyle
.
.decoration
Partial<{} | Decoration>
Inherited from UIControl.Presets.decoration
.
.disabled
boolean
Inherited from UIControl.Presets.disabled
.
.shrinkwrap
boolean
Inherited from UIControl.Presets.shrinkwrap
.
.style
string |
UIStyle
Inherited from UIComponent.Presets.style
.
.hidden
boolean
Inherited from UIComponent.Presets.hidden
.
.dimensions
Partial<{} | Dimensions>
Inherited from UIComponent.Presets.dimensions
.
.position
Partial<{} | Position>
Inherited from UIComponent.Presets.position
.
.accessibleRole
string
Inherited from UIComponent.Presets.accessibleRole
.
.accessibleLabel
string
Inherited from UIComponent.Presets.accessibleLabel
.
.requestFocus
boolean
Inherited from UIComponent.Presets.requestFocus
.


Package Angular libraries for npm distribution
Overview
If all users of an Angular library use Bazel (e.g. internal usage in your company)
then you should simply add your library to the deps
of the consuming application.
These rules exist for compatibility with non-Bazel consumers of your library.
It packages your library following the Angular Package Format, see the specification of this format at https://goo.gl/jB3GVv
primary_entry_point_name
primary_entry_point_name(name, entry_point, entry_point_name)
This is not a public API.
Compute the name of the primary entry point in the library.
Returns: name of the entry point, which will appear in the name of generated bundles
Attributes
name |
the name of the |
entry_point |
The starting point of the application, see rollup_bundle. |
entry_point_name |
if set, this is the returned value. |
ng_package
ng_package(name, deps, data, srcs, entry_point, entry_point_name, globals, include_devmode_srcs, license_banner, ng_packager, readme_md, rollup, rollup_config_tmpl, terser, terser_config_file)
ng_package produces an npm-ready package from an Angular library.
Attributes
name |
A unique name for this rule. |
deps |
Other rules that produce JavaScript outputs, such as |
data |
Additional, non-Angular files to be added to the package, e.g. global CSS assets. |
srcs |
JavaScript source files from the workspace. These can use ES2015 syntax and ES Modules (import/export) |
entry_point |
The starting point of the application, passed as the
|
entry_point_name |
Name to use when generating bundle files for the primary entry-point. |
globals |
A dict of symbols that reference external scripts.
The keys are variable names that appear in the program,
and the values are the symbol to reference at runtime in a global context (UMD bundles).
For example, a program referencing @angular/core should use ng.core
as the global reference, so Angular users should include the mapping
|
include_devmode_srcs |
|
license_banner |
A .txt file passed to the |
ng_packager |
|
readme_md |
|
rollup |
|
rollup_config_tmpl |
|
terser |
|
terser_config_file |
A JSON file containing Terser minify() options. This is the file you would pass to the --config-file argument in terser's CLI. https://github.com/terser-js/terser#minify-options documents the content of the file. If |


Former U.S. envoy says corrupt Ukrainians found U.S. partners
WASHINGTON (Reuters) - The former U.S. ambassador to Ukraine told a public impeachment hearing of President Donald Trump on Friday that corrupt Ukrainians found Americans willing to work with them to oust her.
Marie Yovanovitch told the U.S. House Intelligence Committee that not all Ukrainians “embraced” U.S. anti-corruption work.
“Thus, perhaps, it was not surprising, that when our anti-corruption efforts got in the way of a desire for profit or power, Ukrainians who preferred to play by the old, corrupt rules sought to remove me. What continues to amaze me is that they found Americans willing to partner with them and, working together, they apparently succeeded in orchestrating the removal of a U.S. ambassador,” she said.


--- layout: post title: Wow date: 2006-06-13 00:00:00 category: personal ---
Wow - and I thought *my* Flickr usage was obsessive.
Congratulations to you all Sal!


Type-Driven Exhibition Design
The Department of Advertising and Graphic Design at the Museum of Modern Art
The Team
The Department of Advertising and Graphic Design is The Museum of Modern Art's in-house design studio. This portfolio website shows a selection of our recent exhibition designs, advertising campaigns, and printed materials-all produced for and in collaboration with the Museum's many departments, from curatorial to education to visitor services.
Young Architects
Project: Young Architects Program
Project Team: August Heffner (art direction), Inva Cota (design), Claire Corey (production manager)
Photos: MoMA
Standard Deviations
Project: Standard Deviations: Types and Families in Contemporary Design
Project Team: Julia Hoffmann (creative direction), Samuel Sherman (design), Claire Corey (production)
Photos: Martin Seck
Picasso Guitars
Project: Picasso Guitars 1912–1914
Project Team: Julia Hoffmann (creative direction), August Heffner (art direction and design), Amanda Pastenkos (design)
Photos: Martin Seck
German Expressionism


Whitefoot the Woodmouse
by Thornton W. Burgess
"Whitefoot Spends a Dreadful Night"
Additional Information
- Year Published: 1922
- Language: English
- Country of Origin: United States of America
- Source: Burgess T. W. (1922). Whitefoot the Woodmouse Boston: Little, Brown & Co..
-
Readability:
- Flesch–Kincaid Level: 4.5
- Word Count: 692
- Genre: Fantasy
- Keywords: 20th century literature, american literature, life lessons, nature
- ✎ Cite This
Downloads
Pity those who suffer fright
In the dark and stilly night.
—Whitefoot.
One night of his life Whitefoot will never forget so long as he lives. Even now it makes him shiver just to think of it. Yes, sir, he shivers even now whenever he thinks of that night. The Black Shadows had come early that evening, so that it was quite dusk when Whitefoot crept out of his snug little bed and climbed up to the round hole which was the doorway of his home. He had just poked his nose out that little round doorway when there was the most terrible sound. It seemed to him as if it was in his very ears, so loud and terrible was it. It frightened him so that he simply let go and tumbled backward down inside his house. Of course it didn’t hurt him any, for he landed on his soft bed.
“Whooo-hoo-hoo, whooo-hoo!” came that terrible sound again, and Whitefoot shook until his little teeth rattled. At least, that is the way it seemed to him. It was the voice of Hooty the Owl, and Whitefoot knew that Hooty was sitting on the top of that very stub. He was, so to speak, on the roof of Whitefoot’s house.
Now in all the Green Forest there is no sound that strikes terror to the hearts of the little people of feathers and fur equal to the hunting call of Hooty the Owl. Hooty knows this. No one knows it better than he does. That is why he uses it. He knows that many of the little people are asleep, safely hidden away. He knows that it would be quite useless for him to simply look for them. He would starve before he could find a dinner in that way. But he knows that any one wakened from sleep in great fright is sure to move, and if they do this they are almost equally sure to make some little sound. His ears are so wonderful that they can catch the faintest sound and tell exactly where it comes from. So he uses that terrible hunting cry to frighten the little people and make them move.
Now Whitefoot knew that he was safe. Hooty couldn’t possibly get at him, even should he find out that he was in there. There was nothing to fear, but just the same, Whitefoot shivered and shook and jumped almost out of his skin every time that Hooty hooted. He just couldn’t help it.
“He can’t get me. I know he can’t get me. I’m perfectly safe. I’m just as safe as if he were miles away. There’s nothing to be afraid of. It is silly to be afraid. Probably Hooty doesn’t even know I am inside here. Even if he does, it doesn’t really matter.” Whitefoot said these things to himself over and over again. Then Hooty would send out that fierce, terrible hunting call and Whitefoot would jump and shake just as before.
After awhile all was still. Gradually Whitefoot stopped trembling. He guessed that Hooty had flown away. Still he remained right where he was for a very long time. He didn’t intend to foolishly take any chances. So he waited and waited and waited.
At last he was sure that Hooty had left. Once more he climbed up to his little round doorway and there he waited some time before poking even his nose outside.
Whitefoot didn’t go out that night at all. It was a moonlight night and just the kind of a night to be out. Instead Whitefoot lay in his little bed and shivered and shook, for all through that long night every once in a while Hooty the Owl would hoot from the top of that stub.


About
The SpatioTemporal Asset Catalog (STAC) specification provides a common language to describe a range of geospatial information, so it can more easily be indexed and discovered. A 'spatiotemporal asset' is any file that represents information about the earth captured in a certain space and time.
The goal is for all providers of spatiotemporal assets (Imagery, SAR, Point Clouds, Data Cubes, Full Motion Video, etc) to expose their data as SpatioTemporal Asset Catalogs (STAC), so that new code doesn't need to be written whenever a new data set or API is released.


“A hackathon, a hacker neologism, is an event when programmers meet to do collaborative computer programming.” -- Wikipedia
Hackathons provide a venue for self-expression and creativity through technology. People with technical backgrounds come together, form teams around a problem or idea, and collaboratively code a unique solution from scratch — these generally take shape in the form of websites, mobile apps, and robots.
A notable example of a hackathon “hack,” GroupMe is a group messaging app that was acquired by Skype for over $50 million. Other notable examples include the Facebook “Like” button and Facebook Chat which were both first demoed at internal company hackathons.
| Friday, 22nd March | Saturday, 23rd March |
|---|---|
| 9.15 - Report to SIS | 10.00 - End of Coding |
| 10.00 - Start Coding | 11.00 - Presentations of Selected Projects |
| 12.00 - Lunch Break | 12.00 - Lunch Break |
| 18.00 - Dinner | 1.00 - Prize Distribution |


Extending the Service¶
All of the stuff in this section is in the “future work” category though none of it is particularly difficult.
Support for Different DBMSs¶
NExScI TAP was designed from the start with multiple DBMS support in mind. Python PEP 249 defines a generic interface for talking to databases and it has been implemented for most systems. We have so far only fully integrated the Oracle packages (cx_Oracle) and SQLite3 as we use those operationally here but we have investigated several others (starting with PostgreSQL and MySQL and plan to incorporate them as time permits. We are open to suggestion with regard to other DBMSs and to overall priorities.
Python Database API (DB-API) 2.0 (PEP 249)¶
The API defines a straightforward interface to databases in general. The initial connect() method takes a variable set of arguments, depending on the DBMS. This returns a “conection”, which in turn can be asked for a “cursor” (connection.cursor()). Cursors can be given a query (cursor.executeSQL(sql)) and then asked to step through the results.
Oracle¶
For Oracle, the initialization takes the form:
conn = cx_Oracle.connect (dbuser, dbpassword, dbserver)
PostgreSQL¶
The most popular PostgreSQL database driver is psycopg2. Initialization is similar to Oracle:: conn = psycopg2.connect(host=’localhost’,database=’exodev’, user=’exo_dbuser’, password=’XXXXXXXX’)
and the same sort of INI block can be used (see the Configuration section):
[pgdb]
host=localhost
database=exodev
user=exo_dbuser
password=XXXXXXXX
SQLite3¶
SQLite3 has the simplist of initializations. Since it works directly on files with no server/login, it can be initialized with just:
conn = sqlite3.connect('exodev.db')
where ‘example.db’ is any SQLite3 file. This is an intrinsic part of the SQLite3 Python package.
MySQL¶
For MySQL, we use the MySQLdb package:
conn = MySQLdb.connect('localhost', 'dbuser', 'XXXXXXX', 'exodb')
Table Upload¶
The TAP specification defines an (optional) UPLOAD capability, which nexsciTAP does not currently support. Uploaded tables are loaded into a separate database schema (visible to the user as “TAP_UPLOAD”) and tables in it are generally meant to support chaining queries together across databases, though there is no such constraint on how they are used.
There are two situations where uploaded tables could be particularly useful. If the uploaded table contains extended information on records in a archive table record (and the “ID” of that record), then a simple join of the two would produce an augmented catalog.
Perhaps the most alluring possibility involves positional cross-comparison as the first step in actual catalog cross-matching. This is a complicated process (the nearest positional match between two tables is frequently not the best match).
NExScI TAP does not currently support UPLOAD, though it is a fairly straightforward thing to add. To date, none of the projects we support have expressed a need for the above.
Dealing with Proprietary Data¶
NExScI TAP has been extended to support access to proprietary data for two projects. In general, this involves two complications. The first is the requirement to authenticate the users. Our projects are using a simple approach of having a separate login service and temporary authorization cookies but there are a wide array of more advanced mechanisms.
THe second complication involves modifying the user query before submission to the database to include joins with additional tables which identify which projects a user belongs and which data records those projects currently have access to.
A simpler security setup (e.g. one where you had the luxury of identifying data records directly with users) could be done in simpler manners. However, since there is no one way to do this, we can’t distribute a single solution as part of NExScI TAP. We would be happy to share the code we do have if your needs are similar.
Dealing with Extended Objects (Images in Particular)¶
Tesselation-based spatial indexing works great for point-like data like astronomical catalogs and can even be used with small extended objects. For instance, if you have metadata for images that are all small you can index the image center coordinates and then pad the queries by the maximum size of the images.
This falls apart for truly extended objects (image sets where some of the images are ten degrees across and region specifications like constellation outlines). For this kind of data there are more effective approaches, most notably R-Trees, which work by creating a hierarchy of object clusters. Building the tree involves reviewing the whole structure every time a new object is added. This is very slow but results in an extremely efficient search framework.
The objects and the tree of clusters are defined by their bounding boxes and at all levels it is perfectly OK for these boxes to overlap; we are just trying to get to a state where we can quickly exclude large subsets from consideration.
Unlike the tesselation approach, where you can leverage the basic DBMS B-Tree indexing, R-Trees require a different internal indexing structure. Most DBMSs now support some form of this but often at an extra cost and pretty much always in a way that requires additional database software installation and configuration.
If you are interested in just spatial searching of image metadata and don’t need relational constraints (or are willing to apply these as post-filters) there is a stand-alone tool that comes as part of the Montage package that contains an optimized R-Tree implementation on file-based data.
If you truly want to fold R-Tree processing into the DBMS framework, the best idea is to adopt a DBMS where this has been done well (e.g. PostgreSQL) and update NExScI TAP to translate ADQL to the PostgreSQL-based formalism.


Dylan Bailee prides himself on providing a highly professional service ensuring that the quality of his work is always paramount, whatever the occasion – personal and corporate.
Dylan Bailee knows that music is the heart and soul of any good event. We provide a professional DJ service for all types of parties, from weddings, anniversairies, birthdays, night clubs, bar nights, festivals, or even your just casual family and friends get together.
Dylan Bailee plays a diverse and wide range of genres and are equipped with not only industry experience and talent, but a professional setup collaborated with decks, speakers and lights making your night as exciting as possible.
Dylan Ratkovic started out as a DJ in 2013 and has had a strong craving for music production of his own to share with the public, he has progressed significantly from the start and hopes to go in no other direction but forward with his career.
Dylan Ratkovic is a former DJ and Promoter for South East Sounds here in Melbourne and has performed at multiple venues, looking to expand his list in future commercial events...
Insert Info here
email him<EMAIL_ADDRESS>or call him<PHONE_NUMBER>


The SearchClient library makes it easy to hook up your search-UI to an IntelliSearch SearchService.
The package handles all the backend web-services so that you can focus on the user interface instead.
The SearchClient wraps and manages all the IntelliSearch SearchService REST web-services:
In addition, there are two other incomplete or experimental REST-interfaces exposed:
For projects that consumes npm packages natively you add this package as you would add any other npm-package:
> npm install --save search-client
If you are using typescript, then the datatypes are available for your IDE to use. If not, then all types and definitions are available in the generated API-documentation in the search-client doc-folder (typically ./node_modules/search-client/doc/index.html).
For web-pages that needs to have a script-tag embedded you can fetch the file(s) needed via the jsdelivr cdn, like this:
<script src="//cdn.jsdelivr.net/search-client/{version}/SearchClient.bundle.min.js"></script>
- where {version}
is to be replaced with the actual version you want.
CDN version aliases:
We strongly recommend that you use the full version id for production sites. For development sites we do recommend the same, but we also see that using a version alias might be handy in some cases.
latest
\
You can use the jsdelivr version alias latest
to always just get the latest version. Just be warned that your site is at high risk of breaking when new versions of the search-client are released. If the search-client library is updated and somehow is no longer compatible with your code, then your site will potentially break and stop working.
<Major>
(i.e. 1
)\
This means that it will get the latest version for the given major version. Note that the same warning as for latest
applies, although this is less risky than just getting any latest
version.
<Major.Minor>
(i.e. 1.1
)\
This means that it will get the latest version for the given major.minor version. Note that the same warning as for latest
applies, although this is less risky than both of the above options.
Note: A benefit to using the npm system is the inclusion of map
-files. Next to the browser-bundles in the project you can find accompanying .map
files that browsers are able to utilize in order to give a better debugging experience.
This section will cover only the basics. We highly recommend using the API-documentation for more details and insight.
The two central classes are SearchClient and Settings:
The central class is the SearchClient. To start using it you will need to create a new instance of it. The constructor takes two parameters, a baseUrl and optionally a settings object.
"http://myserver:9950"
for the IntelliSearch SearchService. The Settings class holds properties as follows:
allCategories
: AllCategoriesSettings authentication
: AuthenticationSettings autocomplete
: AutocompleteSettings bestBets
: BestBetsSettings categorize
: CategorizeSettings find
: FindSettings query
: Query Please consult the documentation for specific details on each of them. Suffice to say that all the *Settings
classes contains a boolean property called enabled
, which by default is true
.
Versions: By default the SearchClient services will use version 4 of the backend SearchService REST API. If you need to connect to the v2 or v3 REST interface then pass this in the Settings object.
The automatic mode is the simplest way for you as a developer to use the search-client. It makes it easy for you to hook up your search-ui to the search-backend, without you having to add source code to detect when and how the various features are to be executed. Instead you can "stand on shoulders" and leverage the knowledge that is already incorporated into the implemented automated triggers. You can set things up and it should "just work". We do however suggest that you invest time into understanding the various search-features and how the the triggers work. That will help you find the best way to implement the search-backend for your search.
In order for the automatic mode to work you need to update the values in your query-field as well as filters and/or sorting order / search-type. This is how the search-client will know when to execute searches/lookups and not.
These are properties on the SearchClient class. It is expected that you set and get them directly:
clientId
: stringdateFrom
: DateSpecificationdateTo
: DateSpecificationfilters
: string[]matchGrouping
: booleanmatchOrderBy
: OrderBymatchPage
: numbermatchPageSize
: numbermaxSuggestions
: numberqueryText
: stringsearchType
: SearchTypeI.e. searchClient.queryText = "my query";
The normal thing to do is to wire the UI events so that when the user changes the content of the query input field you immediately update the queryText
property.
In addition the filters
and matchPage
properties also have a couple of helpers:
filterAdd(string filter)
filterRemove(string filter)
matchPageNext()
matchPagePrev()
The autocomplete
, categorize
and find
properties are all essential parts of the automatic mode. Because of this their respective settings objects also contain a property called trigger
:
These triggers have a common set of properties, inherited from the [[BaseTriggers]] class:
queryChange
:
Trigger execution when the query changes.
queryChangeMinLength
:
Minimum query-text length before triggering execution.
Note: Requires queryChange to be true.
queryChangeDelay
:
Delay triggers for query-text changes until no change has been made for a certain time (in milliseconds). This is to avoid executing searches constantly while the user is typing.
Note: Requires queryChange to be true.
queryChangeInstantRegex
:
When this regex matches the query-text the change will trigger immediately instead of delaying the trigger (as defined above).
Note: Requires queryChange to be true.
Note: Requires query to be longer than queryMinLength.
Default for Autocomplete: Trigger on first whitespace after non-whitespace. Default for Categorize/Find: Trigger on first ENTER after non-whitespace.
This means that in the passed Settings-object you can differentiate on when the backend operations are to be executed for each of them.
The automatic mode operations (autocomplete, categorize and find) also allow you to specify callbacks as a part of the configuration. The callbacks can be used in the manual mode too, but they were designed to be part of the automatic mode primarily.
cbRequest
This callback is called before the request is started. Typically you will use this to control loading/waiting indicators on the page. The signature includes some optional params (url: string, reqInit: RequestInit): bool
.
Note that if you add this callback, and explicitly return false, then the request will not be executed.
If you don't return or return false then the request runs as expected.
cbSuccess
This callback is called whenever a backend operation has completed and results have been received. The signature of the callback should be (data: <TDataType>) => void
, where the <TDataType> is string[]
for the autocomplete call, Categories
for the categorize call and Matches
for the find call.
cbError
This callback is called whenever a backend operation somehow fails to complete. The signature of the callback should be (error: any) => void
. The error object could be anything, but should explain the cause of the problem if console.log()'ed or toString()'ed to the page.
It is important to understand that autocomplete, categorize and find all have independent callbacks in the configuration. Because of this the success, error and busy-state for each of them can be tracked independently. This means that the query-field may have an indicator somewhere that indicates that it is doing a lookup (if wanted). The categories section may have an indicator to tell that it is working, and finally the results area may also have an indicator telling that results are pending.
In the automatic mode, you will never normally use any of the webservice-operations directly. They will all be invoked indirectly as a result of you updating the input-values (as listed in the previous section).
The web-service properties are available though (as long as you didn't pass enabled: false
for them in the settings object). Please note that the autocomplete, categorize and find web-services will by default call any registered callbacks a a part of the fetch-process. If you don't want the callbacks to be enabled for the fetch then you can pass a second variable to the fetch() call, a boolean suppressCallbacks
parameter, set to true
.
// Sets suppressCallbacks to true via second param to fetch
client.find.fetch({ queryText: "Hello world" }, true)
.then((matches) => {
console.log("Find results:", matches);
})
.catch((error) => {
console.error(error);
});
Example:
// Without authentication
let client = new SearchClient("http://server:9950/", {
version: 4,
authentication: {
enables: false,
},
find: {
cbRequest: (url, reqInit) => {
findError = null;
findResults = null;
findLoading = true;
},
cbSuccess: (matches) => {
findResults = matches;
findLoading = false;
},
cbError: (error) => {
findError = error.toString();
findLoading = false;
},
triggers: {
queryChanged: true // Means that the match-results will update on queryChanges, and according to the other default trigger values. Still needs minLength and triggerDelay is also obeyed. This example allows a kind of real-time search for matches.
}
},
categorize: {
cbRequest: (url, reqInit) => {
categorizeError = null;
categorizeResults = null;
categorizeLoading = true;
},
cbSuccess: (categories) => {
categorizeResults = categories;
categorizeLoading = false;
},
cbError: (error) => {
categorizeError = error.toString();
categorizeLoading = false;
},
triggers: {
// Here we don't change the triggers. queryChange is false so it will not "auto-search".
}
},
autocomplete: {
enabled: false // for this example we turn off autocomplete
}
});
// Sets the queryText, which dependent on the setting triggers may or may not invoke a fetch on the various web-services.
// In this scenario autocomplete is not looked up since it is disabled in the settings object.
client.queryText = "hello world";
// The user clicks the Search-button and a find and categorize should be executed.
client.findAndCategorize();
// The registered callbacks passed to the SearchClient constructor will be called automatically to track the progress and deliver results when returned.
There is no need to update inputs or triggers. Instead the search-client will execute on your command. The results can be received in callbacks or using promises.
While it is possible to set up callbacks to handle the results of the manual fetches, it is not the recommended practice. We suggest that you instead use the Promises returned (see sample below).
In manual mode, you control which web-service to call when yourself. This is what the manual mode is all about. The typical mode of operation is still to instantiate the central SearchClient class, but to call the web-services via their respective search-client instance properties: allCategories.fetch(), authentication.fetch(), autocomplete.fetch(), bestBets.fetch(), categorize.fetch() and find.fetch().
Example:
let client = new SearchClient("http://server:9950/");
client.find.fetch({ queryText: "Hello world" })
.then((matches) => {
console.log("Find results:", matches);
})
.catch((error) => {
console.error(error);
});
It is recommended to use Promises as shown in the sample above when doing manual operations.
Please note that any of the services' registered callbacks will be called as a part of the fetch-process. This regards to both automatic and manual mode fetches. If you don't want the callbacks to be enabled you have two options:
deferUpdates(true)
before you do anything that would normally trigger callbacks. This will in turn call deferUpdates(true)
for all services. When you want callbacks to again be activated, call deferUpdate(false)
method. When first param is false it optionally takes a second parameter that can be used to indicate whether pending updates are to be skipped or not.deferUpdates(true)
before you do anything that would normally trigger callbacks. And then afterwards, if you want the callbacks to again be active, call deferUpdates(false)
and use the second parameter to indicate whether pending updates are to be skipped or not.fetch()
-call, a boolean suppressCallbacks
parameter, set to true
.The IntelliSearch SearchService supports using JWT (JSON Web Token) authentication for differentiating users/permissions. If the index is public and does not use authentication then you can turn off authentication (which is enabled by default) by passing this in the settings object in the SearchClient constructor: authentication: { enabled: false }
.
If you however want to use authentication, then there are a couple of things that is important:
The SearchService must be configured to use the CurrentPrincipal plugin.
A web-service that identifies the user must be setup that is accessible from the page that the search-client runs on.
The SearchClient authentication settings object must define:
{ user: { jwt: "actualtokenhash" } }
then the tokenPath should be [ "user", "jwt" ]
.The authentication system, when enabled will attempt to fetch the authentication-token as soon as it is setup (trying to pre-fetch it to have it ready asap in case a search is made).
The authentication system decodes the jwt-token when received and checks for when the token expires. It then sets up a timeout to fetch a new token in ample time before the current one expires. The overlap for this is defined in its triggers: authentication: { triggers: { expiryOverlap: 60 } }
. The default is 60 seconds, which means that the client will try to get a new JWT 60 seconds before the old one expires.
If you are using typescript, then the data-types are available for your IDE to use. If not, then all types and definitions are available in the generated API-documentation in the search-client docs-folder (typically ./node_modules/search-client/docs/index.html
).
Generated using TypeDoc


Public Relation Executive Manager
Life Insurance LLC (View All Jobs)
Nationwide Dec 30, 2015 - Feb 20, 2016 $7000 - $7500Overview
Life Insurance LLC. In marketing communications, we dream it and create it. All of the company’s promotional and communication needs are completed in-house by these “creatives” in an advertising agency-based set-up. This includes everything from advertising, promotions and print production to media relations, exhibition coordination and website maintenance. Everyone from artists, writers, designers, media buyers, event coordinators, video producers/editors and public relations specialists work together to bring campaigns and product-centric promotions to life.
If you’re a dreamer, gather up your portfolio and show us your vision. Garmin is adding one more enthusiastic individual to our in-house Communications expert team.
Qualification
Minimum of 5 years creative experience in a graphic design studio or advertising ad agency environment is required. Qualified candidates for this role will possess the following education, experience and skills:
- Demonstrated strong and effective verbal, written, and interpersonal communication skills
- Must be team-oriented, possess a positive attitude and work well with others
- Ability to prioritize and multi-task in a flexible, fast paced and challenging environment
Key responsibilities also include
- Provide technical health advice to Head of Country Programmes and field advisors at all key stages of the project management cycle including needs assessment.
- Technical strategy and design, implementation as well as sector specific monitoring and evaluation.
- This includes travel to field programmes as well as review of proposals, key reports and surveys prior to external submission.
- Stay abreast of current best practice. Research and stay informed on academic and technical health and nutrition issues, techniques, and guidelines to inform and improve programming.
Requirements
- Must have minimum of 3 years experience running, maneuvering, driving, and navigating equipment such as bulldozer, excavators, rollers, and front-end loaders.
- Must have minimum of 3 years experience running, maneuvering, driving, and navigating equipment such as bulldozer, excavators, rollers, and front-end loaders. Strongly prefer candidates with High School Diploma
- Must be able to perform physical activities that require considerable use of your arms and legs and moving your whole body, such as climbing, lifting, balancing, walking, stooping, and handling of materials.
Benefits
- Must have minimum of 3 years experience running, maneuvering, driving, and navigating equipment such as bulldozer, excavators, rollers, and front-end loaders.
- Strongly prefer candidates with High School Diploma
- Must be able to perform physical activities that require considerable use of your arms and legs and moving your whole body, such as climbing, lifting, balancing, walking, stooping, and handling of materials.


Step 1: Preheat skillet over medium heat.
Step 2: Generously butter one side of a slice of bread.
Step 3: Place bread butter-side-down onto skillet bottom and add 1 slice of cheese.
Step 4: Butter a second slice of bread on one side and place butter-side-up on top of sandwich.
Step 5: Grill until lightly browned and flip over; continue grilling until cheese is melted.
Step 6: Repeat with remaining 2 slices of bread, butter and slice of cheese.


Add Task
Mark All As Completed?
Tasks ({{ remaining.length }})
{{ task.body }}
✗
✔
Completed ({{ completions.length }})
{{ task.body }}
✗
Clear Completed


Relative Paths | Web Development and stuff like that
Mark Phoenix and Ben Hutchings
50: Jukebox Special
49: Web Security | With Tim Nash
48: Progressive Enhancement | With Aaron Gustafson
47: Dogmatism | With Chris Coyier
46: CSS Grid Layout | An interview with Rachel Andrew
45: A chat about SEO | with Elliott Richmond
44: Looking back at 2016 | They ran screaming
43: Perch CMS | An interview with Clive Walker
42: PC versus Mac | Apple comes down the mountain
41: Working with Designers | Do you Etch-a-Sketch?
40: Going Limited | Daft Bunk
39: HTTPS | Deliver some dog justice
38: Mistakes x 2 | It's a bit like mousetrap
37: Personal Sites | "Disappointment will spur them on"
36: Details | "Billy the Whippet"
35: PC versus Mac | "versus Sandals"
34: "Just chat really" | No real plan
33: Longshot Photo | A follow-up interview with Ken Long
32: WOW Plugins | An interview with Kimb Jones
31: Dealing with mistakes | The whole kitten caboodle
30: Designers should(n't) code | An interview with Ben Brignell
29: Interview | Wordpress Plugin Development with Mark Wilkinson
28: Going Live | Build a website on an Etch-a-Sketch
27: Customer Education | Like people in music shops
26: Customer Care | Hug their heart
25: Interview | Beyond WordPress with Emily Lewis and Lea Alcantara.
24.5: Relatively Short | A Picosode
24: My Best Job! | Getting Cardboard From a Skip
23: Interview | Theme Frameworks with Jonny Allbut
22: Interview | Commercial Plugin Development with Jonathan Davis
21: Setting Up | Tabs or Spaces?
20: Interview | WordCamp Birmingham with Rachel McCollin
19.5: Relatively Short | "The Unpesode!"
19: Stress | Should've auditioned that whale!
18: Back to Basics | Spaghetti Kitten
17: Looking Back Looking Forward | A Stool to Oil
16: Interview | A Live Client meeting with Ken from Longshot Photo.
15: Time Management | Panic Develop Till it's Done
14: Hosting | It's like tyres!
13: Design for Developers | Too Many Biscuits
12: Project X part 1 | Very respectful to Begonias
11: Interview | Malc from Fluid2
10: Pricing | Mr Furtwangler I presume
9: Deployment | Eating out of a bin
8: Geek mental help week | Don't push over a cow!
7: Why WordPress? | Can you ruffle a beak?
6: Ch.. Ch.. Ch.. Changes | Hiding in the toilet
5: Time to get real | Lawnmower Man
4: Toolkit | The one guy in the corner with a Toshiba!
3: Continuous Professional Development | "Don't steal bad code!"
2: Saying I Don't know | "Never Sharpen a Teapot"
1: What's it all for? | "Don't surf mountains!"


--- layout: default title: Marco Viero ---
You're Thinking About Stacking All Wrong [slides]
Astrophysics with the CMB-S4 Survey; UC Berkeley/UIUCExploring the Early Universe with Line-Intensity Mapping [slides]
Cornell Astronomy Colloquium; Ithaca, NYLeveraging Empirical Measurements to Aide Galaxy Modeling [slides]
Cornell Galaxy Lunch; Ithaca, NYModels of the CO background via Measurements of the Cosmic Infrared Background [slides]
Intensity Mapping Meeting; Baltimore, MDEmpirically Modeling Intensities in the Cosmic Infrared Background [slides]
Cosmology on Safari; KwaZulu-Natal, South AfricaBeating Confusion with Simultaneous Stacking [slides]
CSST Meeting; Pasadena, CAStatistical Methods in Astrophysics: Looking Ahead
New Frontiers in Far–infrared and Sub–millimeter Astronomy; Aspen, COMining Far Infrared Data with SIMSTACK [slides]
The Cosmic FIR Landscape: Building on the legacy of Herschel; Lisbon, PortugalThe Far-Infrared Properties of Optically-Selected Galaxies [slides]
Instituto de Astrofísica e Ciências do Espaço; Lisbon, PortugalThe CIB is explained by known galaxies (and their companions) at z < 4 [slides]
Gas, Dust, and Star Formation in Galaxies from the Local to Far Universe; Chania, GreeceA Census of the Cosmic Infrared Background [slides]
Dissecting Galaxies Near and Far; Santiago, ChileUnveiling the Sources of the Cosmic Infrared Background though their Intensities [slides]
Cosmology Seminar; UCSC, CAHerS and HeLMS: Herschel/SPIRE Submillimeter surveys in the SDSS Stripe 82 [slides]
HETDEX Meeting; Austin, TXClustering of Star-Forming Galaxies with BLAST [pdf]
The Formation and Growth of Galaxies in the Young Universe; Obergurgl, Austria


For simplicity's sake, this a single entity app. There is a Movie class with three attributes - ID, title and created date. The ID and title speak for themselves, and the created date is the date in which the movie was persisted to the database. Play synthesises getters and setters so we need not worry about these.
We have created a MovieRepository interface (DAO) which will be injected into the
MoviesController (we will look at that part in a bit). It is annotated with @Named
to declare that the repository is available for dependency injection and @Singleton
to declare that only one instance of it is generally required.
We also have a MovieRepositoryImpl that implements the MovieRepository's methods. This contains the code that performs the does the dirty work in making requests to the database. Results, if any, are then returned to the MovieRepository DAO.
We have a single controller, aptly named MoviesController to give it some meaning. To indicate that this is a controller it is annotated with the Spring annotation @Controller
. Through means of a constructor we have injected the MovieRepository DAO via the use of @Inject
. We use constructor injection in order to promote an immutable programming model. Immutable variables assist toward providing an inherently thread-safe application.
If you have ever used LINQ in C# you will love Jinq. Jinq provides developers an easy and natural way to write database queries in Java and Scala. You can treat database data like normal Java objects stored in collections. You can iterate over them and filter them using normal Java commands, and all your code will be automatically translated into optimized database queries.
We have added a JinqSource file which we declare in our repository for use. We have added the following helper method to query the Movie entity.
public JPAJinqStream<Movie> movies(EntityManager em) {
return streams.streamAll(em, Movie.class);
}


Enter Stage Right
I have worked in environments where reacting was the “normal” way to approach issues and being proactive was just a waste of time… facepalm The seemingly simple idea of changing the workplace culture from reactive to proactive was hard to pitch, let alone implement on my own.
18 months ago, I knew there was a better way of doing things and I was determined to find something. I had been watching developers implement Agile Development processes with great envy and I was starting to see concepts that would have great outcomes if adopted in a traditional operations environment.
Finally having something tangible to explore I started looking into Agile Operations, which led me DevOps. Lurking in the shadows for a while, I digested as much as I could of the DevOps movement. I thought it was time to talk to some of the developers and get them on board.
6 months on and here we are…
So what is DevOps to me?
Ideology
DevOps is a way of thinking and acting. It is not a toolkit, but is something we all can practice everyday. Adam Jacob is spot on with his Velocity 2010 talk, DevOps is an inclusive movement and I believe this includes developers, operations and management.
Business Problem
Although it has stemmed from the trenches of development and operations theatres, DevOps is very much a business problem. It needs to be supported by the business to be successful, otherwise we end up with “Black Ops” style DevOps and no one benefits.
Stakeholders may point out that DevOps addresses some of these business problems with technical solutions, but DevOps is still a business problem.
Not A Role
You can’t be a DevOp, but you can practice DevOps in your role.
In contrast, I believe that in the next couple of years we will see businesses creating roles that were traditionally filled by either developers or system administrators. These roles will filled be the masters of DevOps-fu, but not a “DevOp”.
Catalyst For Change
The IT industry is due for a much needed shake up and DevOps has provided a catalyst for this change.
Embrace change, don’t fight it.
DevOps has presented an opportunity for IT professionals to identify the fundamental issues in the way business is run today and change them. We need to address this by becoming more adaptable and identifying business needs.
Ask yourself, is this providing value to the business?
CAMS
CAMS to me is the “Howto guide” of DevOps. Damon and John have hit the nail on the head with this one:
- Culture
- Automation
- Metrics
- Sharing
By implementing these four areas, regardless if you are trying to achieve a DevOps nirvana, you will see a greater response to change within the organisation.
I have found CAMS to be the easiest way to for people new to the DevOps scene to understand what it’s all about.
So What Is Next?
Spread the word! Get DevOps out there.
The response to DevOps from sysadmins has been amazing, but we need to get other key influencers from within business on board. We need to start promoting/evangelising DevOps to developers, managers, directors, VPs and C-level executives too.
Sysadmins
-
Get together and piggy back a local developer user group meet up (Java, Ruby, Python etc.)
-
Talk to developers at work and ask them what you can do to help.
Devs
-
Gatecrash a user group that is traditionally full of operations folk (Linux, Puppet, Chef etc.)
-
Ask your operations team what you could do to make their lives easier.
Everyone
-
Run a internal DevOps meet up at your workplace. Invite your manager.
-
Find a DevOps meet up in your area.
Further Reading
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr - John Allspaw and Paul Hammond. Agile Web Operations - Matthias Marschall and Dan Ackerson What DevOps Means To Me - James Turnbull What Is This DevOps Thing Anyway? - Patrick Debois What DevOps Means To Me - John Willis Velocity 2010 - Adam Jacob on DevOps - Adam Jacob What Is DevOps? - Damon Edwards No Operations Team Left Behind - Where DevOps Misses The Mark - John Vincent The Rise of DevOps - Dmitriy Samovskiy The Future of Corporate IT - CEB
If any of the links are broken, please contact me.


--- layout: post title: no title date: '2017-01-23T10:30:22+01:00' categories: - Storyboards - Sketches picture_url: https://film-Storyboards.tumblr.com/post/156268465846 ---


If you have any questions or concerns please contact<EMAIL_ADDRESS>You can find us on Instagram: @tedxyouthtyneheadregionalpark


Duterte creates group to study creation of new military camp in Marawi
Yet residents of Marawi City and Lanao del Sur strongly oppose the establishment of another military camp in the war-ravaged city
by Sofia TomacruzSubscribe
Email Address
Newsletters
- Glenda Gloria's Take this Tuesday
- Huddle by Miriam Grace Go
- The Newsbreak Agenda by Chay Hofileña
- Sometimes, all you need is video by Lilibeth Frondoso


Hover your mouse to see the connections between different nodes.
Click on a node to see detail description and to lock the highlighted cells. Hold
Ctrl
(or
Cmd
on a Mac) to select multiple nodes.
Click on the background to dismiss the sidebar.
To zoom, hold
Ctrl
(or
Cmd
on a Mac) while pressing
+
to zoom in,
-
to zoom out.
Click here to see the adjacency matrix.
Click here to submit a new idea.
Visit the GitHub repo to view source code, request features, and report bugs.


Drought recedes as rain waters parched areas of Southeast
by The Associated PressATLANTA — Drought continues to recede in Georgia, Alabama and South Carolina.
Almost one third of South Carolina and more than one third of Georgia recorded no drought as of Tuesday. Last week, only 9% of Georgia and 24% of South Carolina could make that claim. In Alabama, 70% of the state is now drought-free.
Areas of moderate and severe drought also declined.
The University of Nebraska-Lincoln’s drought monitor says rain fell across the eastern United States. Much of the Southeast received more rain this week.
High heat and little rainfall spread a quick-developing drought across the South in late summer.
On Oct. 1, all of Alabama and Georgia were in drought, along with almost all of Mississippi and all but the northeastern corner of South Carolina. Rains quenched Mississippi’s drought earlier.
The Associated Press


Toggle navigation
Log in
Sign up
Get in touch
Need help?
Forgot Password
Enter your email address below and we will send you password reset instructions.
Email address is required.
That is not a valid email. Please input a valid email.
{{ errorMessage }}
{{ successMessage }}
Reset Password


--- layout: archive title: Zulip Chat Archive permalink: /stream/113488-general/topic/missing.20transitivity.20tags.html ---
Should all of these be tagged with @[trans]
? Or is there a reason to only do that for sets?
git grep "subset.trans" | grep theorem src/data/finset.lean:theorem subset.trans {s₁ s₂ s₃ : finset α} : s₁ ⊆ s₂ → s₂ ⊆ s₃ → s₁ ⊆ s₃ := subset.trans src/data/multiset.lean:theorem subset.trans {s t u : multiset α} : s ⊆ t → t ⊆ u → s ⊆ u := src/data/set/basic.lean:@[trans] theorem subset.trans {a b c : set α} (ab : a ⊆ b) (bc : b ⊆ c) : a ⊆ c := src/set_theory/lists.lean:theorem subset.trans {l₁ l₂ l₃ : lists' α tt}
This takes us back to Chris' point. If we just used le
and make them partial orders then le_trans
would kick in.
Last updated: Apr 24 2020 at 19:02 UTC


GET
Submission Date
Total Grade
Use these languages by default
Translate
Insert
Comment
GET
Insert
Translate sample by Google123


JOY2KEY(1) JOY2KEY(1) NAME joy2key - Emulate keyboard events using a Joystick SYNOPSIS joy2key Usage: joy2key ["Window Name"] [ -rawconsole ] [ -terminal ] [ -X ] [ -axis [(axis0) low hi] [(axis1) low hi] ...] [ -thresh [(axis0) low hi] [(axis1) low hi] ...] [ -buttons [(button0)] [(button1)] [(button2)] ...] [ -dev {/dev/input/js0} ] [ -rcfile {.joy2keyrc} ] [ -config {no default} ] [ -autorepeat {(freq) 5} ] [ -deadzone {(percent) 50} ] note: [] denotes `optional' option or argument, () hints at the wanted arguments for options {} denotes default (compiled-in) parameters (note: defaults may have been changed by editing joy2key.c) DESCRIPTION joy2key monitors the joystick (normally /dev/input/js0) and sends key‐ board events to an X window, terminal, or raw console. In the case of X, xwininfo(1) is used to retrive the window ID, which should not be a prob‐ lem as this is a standard utility in most X11 distributions. To find the symbolic name of a particular key, see include/X11/keysymdef.h. In ter‐ minal mode, joy2key sends the ascii character given on the command line (that is, "joy2key -buttons a" means send lowercase 'a' when the first joystick button is pushed). In raw console mode, please consult the doc‐ ument "rawscancodes" included in this distribution for the proper scan‐ codes. Options -X Send X events. May be compiled out of your copy of joy2key. -rawconsole For SVGALIB and similar programs that put the keyboard in raw mode. Sends scancodes. May be compiled out of your copy of joy2key. -terminal Send ascii characters. May be compiled out of your copy of joy2key. -axis Specifies actions to send when passing low/high values for each axis. Specified in pairs, from axis0 ... axisN, that is, the X axis is axis0, then the Y axis (axis1), then if you have a joy‐ stick hat that may be axis 2 and 3, etc. To figure out which axis is which, use the jstest program that comes with the joystick driver. -buttons Similar to -arrows, but for buttons. Goes from button0 ... but‐ tonN, specifying key to send for each button on joystick. Use the jstest program to determine the numbering for each button. -thresh Specifies low/high thresholds to use (i.e. at what point moving the stick or pressing the gamepad triggers an event) in pairs, for each joystick axis. -dev Specifies joystick device to use. Defaults /dev/input/js0 (first joystick) -autorepeat Turns on and optionally specifies autorepeat frequency, i.e. the number of times per second a button which is held down will be repeated. -deadzone Controls sensitivity when manually calibrating. -rcfile Sets the rc file to look in. -config Reads in a config in an rc file. FILES /dev/js[01] The joystick driver. Must be installed for joy2key to work. Joy2key only supports versions 1.0+ of the joystick driver. Older ver‐ sions of joy2key use the 0.8.0 joystick driver. If for some reason a 1.0+ joystick driver does not work for you, use joy2key 1.2. The Linux joystick driver is available at http://atrey.karlin.mff.cuni.cz/~vojtech/joystick/ ~/.joy2keyrc Rc file searched for commands in -config. The joy2key homepage is located at: http://interreality.org/~tetron/technology/joy2key/ BUGS I don't like writing man pages, so this man page may be buggy :) COPYING This is free software under the GNU General Public License. See COPYING in the archive to more information. 17 August 1998 JOY2KEY(1)


MP3
Device Unsupported
Bound Position: (
x
=
,
y
=
)
Bound Size: (
width
=
,
height
=
)
Frame:
/
Frame Time:
Home
Extras


Fridge to Table
Founders
Reviews
Emails
Help Topics
Support
Terms and Conditions
Privacy Policy
Accessibility


Of Time and Rhyme
June 16, 2016
End
The ending is the beginning is the ending. Between these two poles is where his home is standing.
Is where and is when his heart begins its beating Within walls of time with echoes which are fleeting.
From contradiction a question is grown breathing, Lays a flat land of answers entombed and wreathing.
Choosing one births first steps, amounts in believing, Though untrue it construes objects for my reaving.
The ending is the beginning is the giving. Between these two poles is where he tries his living.


---
layout: talk_reveal3
title: Phylodynamic inference of epidemic spread
venue: Fred Hutch
event: HB Friday Faculty Talk
author: Trevor Bedford
draft: true
---
{{ page.title }}
Trevor Bedford (@trvrb)
{{ page.date | date: "%-d %b %Y" }}
{{ page.event }}
{{ page.venue }}
Outbreaks and phylogeography rather than influenza and evolutionary forecasting
Epidemic process
Sample some individuals
Sequence and determine phylogeny
Sequence and determine phylogeny
Localized Middle Eastern MERS-CoV phylogeny
Regional West African Ebola phylogeny
Global influenza phylogeny
Phylodynamic inference generally focuses on time and place
Mutations tend to accumulate in a clock-like fashion
"Root-to-tip" plots show temporal signal
Allows conversion between branch length and time
Location modeled as a discrete state
Infer transition matrix and ancestral states
Rare transitions, short branches and many taxa increase confidence
Examples for today
- MERS spillover in the Arabian Peninsula
- Ebola spread in West Africa
- Zika spread in the Americas
Middle East respiratory syndrome coronavirus (MERS-CoV)
- First identified in Saudi Arabia in 2012
- 2229 confirmed cases to date and 791 deaths
- Camels thought to be the intermediate host
- 30% of common colds due to endemic human coronaviruses
Ongoing incidence, but lack of epidemic growth
Cases localized to the Arabian Peninsula
Rambaut. 2018.
Hypotheses for MERS transmission
MERS-CoV spillover at the camel-human interface
with Gytis Dudas, Luiz Carvalho and Andrew Rambaut
Genomic dataset
- 174 virus genomes from human infections
- 100 virus genomes from camel infections
MERS tree with host state
Phylodynamic reconstruction of host state
Humans are transient hosts
Asymmetric migration rates
- 56 (48–63) camel-to-human transmission events resulting in 174 sequenced human infections
- 3 (0-12) human-to-camel transmission events
Introduction events tend to occur between April and July
Dromedary camel calving occurs between Nov and Feb
Monte Carlo simulation
Phylogenetic clustering suggests $R_0$ below 1.0 and ~2000 human cases driven by ~600 introduction events
Critically, no evidence of increasing cluster sizes through time
Ebola epidemic of 2014-2016 was unprecedented in scope
Ebola epidemic in West Africa
Ebola epidemic within Sierra Leone
Virus genomes reveal factors that spread and sustained the Ebola epidemic
with Gytis Dudas, Andrew Rambaut, Luiz Carvalho, Marc Suchard, Philippe Lemey,
and many others
Sequencing of 1610 Ebola virus genomes collected during the 2013-2016 West African epidemic
Sequenced genomes were representative of spatiotemporal diversity
Phylogenetic reconstruction of epidemic
Tracking migration events
Spatial structure at the country level
Substantial mixing at the regional level
Each introduction results in a minor outbreak
Regional outbreaks due to multiple introductions
Regional outbreaks due to multiple introductions
Zika's arrival and spread in the Americas
Establishment and cryptic transmission of Zika virus in Brazil and the Americas
with Nuno Faria, Nick Loman, Oli Pybus, Luiz Alcantara, Ester Sabino, Josh Quick,
Alli Black,
Ingra Morales, Julien Thézé, Marcio Nunes, Jacqueline de Jesus,
Marta Giovanetti, Moritz Kraemer, Sarah Hill and many others
Road trip through northeast Brazil to collect samples and sequence
Case reports and diagnostics suggest initiation in northeast Brazil
Phylogeny infers an origin in northeast Brazil
Potential applications to cancer evolution and spread
Metastasis in colorectal cancer
Angelova et al. 2018. Cell.
Metastatic seeding in prostate cancer
Gundem et al. 2015. Nature.
Spatial growth of liver cancer
Ling et al. 2015. PNAS.
Equivalent to sampling entire regions
Alignment vs variants
Acknowledgements
Bedford Lab:
Alli Black,
Sidney Bell,
Gytis Dudas,
John Huddleston,
Barney Potter,
James Hadfield,
Louise Moncla,
Tom Sibley
MERS: Gytis Dudas, Andrew Rambaut, Luiz Carvalho
Ebola: Gytis Dudas, Andrew Rambaut, Luiz Carvalho, Philippe Lemey,
Marc Suchard, Andrew Tatem
Zika: Nick Loman, Nuno Faria, Oli Pybus, Josh Quick, Ingra Claro,
Julien Thézé, Jaquilene de Jesus, Marta Giovanetti, Moritz Kraemer, Sarah Hill, Allison Black,
Ester Sabino, Luiz Alcantara