Ashesi's library is primarily digital, with subscriptions to a number of electronic information resources, including the PERI databases which give access to over 30,000 scholarly journals. Ashesi's library is not limited to the library building; it reaches out, with cutting edge information, into faculty and administrative offices, classrooms, cafeterias, and even outdoor gathering spaces.
The electronic library is supplemented by a physical collection that is currently 27,000 volumes, as well as a variety of international and local magazines, newspapers, and research publications.
Warren Library Facilities
brightness_1 Two floors with seating for 150 users
brightness_1 The Joseph and Miyuki Dadzie Seminar room (301) - which can be booked by small groups of students, faculty and staff
brightness_1 The Catherine and Patrick Awuah Snr Seminar room (302) - which is occupied by the Learning Lab
brightness_1 Computer workstations
brightness_1 Photocopiers
brightness_1 Scanner
brightness_1 Binder
brightness_1 Laminator
On-Line Databases
The library subscribes to a number of electronic information resources, including the PERI databases which gives access to over 30,000 scholarly journals. Most are available via IP address for computers using Ashesi's network, including those using the wifi.
The Physical Collection
Ashesi's library collection currently consists of over 9,000 books and 200 CD-ROMs focused on four main areas: business administration, computer science, engineering and the liberal arts component of our curriculum, including titles related to literature, literary criticism, social theory, philosophy, history and political science. The collection will continue to grow over time.
Special Collections
The Africana/special collection section is located on the ground floor of the main library. Books in the collection include materials related to general Africana plus books specifically related to Ghana. The library will continue to collect volumes in the area of Africana in order to maintain a comprehensive collection.
Magazines and Newspapers
We buy the following locally:
brightness_1 Daily Graphic
brightness_1 Ghanaian Times
brightness_1 Business and Financial Times
brightness_1 The Economist
brightness_1 New African
brightness_1 African Business
Local Publications
A collection of publications from various institutions and organizations such as the Government Ministries, Bank of Ghana, Centre for Democratic Development (CDD), Institute of Economic Affairs (IEA), National Council for Tertiary Education (NCTE), etc. are available.
Theses & Dissertations
Unpublished dissertations and theses produced by Ashesi students and faculty may be viewed on a reference basis in the library. Over time these are being added to the Ashesi Institutional Repository.
Library Staff
The library is managed by Nina Chachu (Head Librarian), assisted by Dinah Koteikor Baidoo (Assistant Librarian) and Enoch Agonyo (Library Assistant).
As part of the work study programme, selected students are given the chance to work in the library in the evenings and on Saturdays. They shelve books, assist other students in locating materials, and help with data entry. At the moment there are sixteen students from all classes supporting our late opening.
General Contact
Circulation Desk: [Tel: +233 (0) 302 610 330 Ext.1085 ]
Ask a Librarian –<EMAIL_ADDRESS>or trwarrenlibrary@gmail.com


WITNESS LIST Criminal Justice Committee February 11, 2003 - 1:00P Budget Overview ON: Livingston, Brad (Texas Department of Criminal Justice), Huntsville, TX Criminal Justice Policy ON: Fabelo, Dr. Tony Executive Director (Criminal Justice Policy Council), Austin, TX Population/Budget ON: Johnson, Gary L. Executive Director (Texas Department of Criminal Justice), Huntsville, TX


Setup a personal blog site
Start a blog based on Material for MkDocs - a well-known theme for a popular Python-based static site generator. This post guides to install and configure necessary tools, Markdown extensions, MkDocs plugins, and modify the theme to fit personal needs.
Last update: 2021-06-03 16:34:50
Table of Content
-
1. Installation
-
2. Configuration
- 3. Markdown extensions
- 4. MkDocs plugins
- 5. Customize theme
- 6. Print to PDF
1. Installation⚓
There are some static site generators written in several languages such as Javascript, Go, Ruby, Python. They also use different template languages, e.g. React, Go, Liquid, Jinja. Among those generators, I’d like to choose an engine based on Python language, because I am familiar with Python, so if I want to modify or add an extension, I can do it myself.
Python-based site generators include MkDocs, Pelican, Sphinx, etc. MkDocs and Pelican are the most popular ones. I used Pelican few years ago, but recently, I was looking for a way to export blog posts to PDF files for printing and offline sharing, then Material theme for MkDocs which has a clear printing style became my choice.
1.1. Material for MkDocs⚓
MkDocs is a fast and simple engine to build a site for project documentation. Content source files are written in Markdown format, and the site is configured with a single YAML config file.
MkDocs runs on Python 3, so download and install it first.
Material for MkDocs is a popular theme for MkDocs. It has a simple UI with Material color palettes. It also brings more features than the base MkDocs: it has webapp mode, flexible settings, and as I mentioned, it has a clear layout and good styles for printing. When installing this Material theme, it will automatically install the MkDocs engine.
1.1.1. Start a new project⚓
Create a new folder to store the project:
mkdir CodeInsideOut
cd CodeInsideOut
Create the project’s virtual environment to isolate this project with others from a possible package conflict:
python -m venv .venv
Activate the virtual environment:
.venv\Scripts\activate.bat
1.1.2. Install main packages⚓
Update the pip
, setuptools
and wheel
as they’re used to install and configure other packages:
python -m pip install -U pip setuptools wheel
-U
or--upgrade
will upgrade the package if it is already installed
Then install the Material for Mkdocs package:
pip install -U mkdocs-material
1.1.3. Initialize the site⚓
Bring up the base of the site:
mkdocs new .
This will create the following file structure:
.
├─ mkdocs.yml # The configuration file
└─ docs/ # Other markdown pages
├─ index.md # The documentation homepage
└─ ... # Other files
Change the theme to material in the project configuration file mkdocs.yml
:
theme:
name: material
1.1.4. Start a local server⚓
Run a local server with:
mkdocs serve
and preview the site at http://localhost:8000 to see the default homepage.
1.1.5. Write a post⚓
Each Markdown file inside the folder docs
will be rendered to a page of the site. The index page is located at docs\index.md
. There can be sub-folders inside the docs
directory to contain a group of posts in separate main topics.
If a post is named other than index.md
, the filename will be used as the directory path of the generated page. Here is how MkDocs generates URLs for Markdown posts:
- folder
docs
becomes the root of the site www.site.com/ - file
docs\blog\index.md
becomes a link www.site.com/blog/ - file
docs\blog\a-post.md
becomes a link www.site.com/blog/a-post/
Use hyphen
-
in folder name and file name to create good URLs.
Here are some tips to keep URLs simple.
1.1.6. Publish⚓
To publish the site, build it first:
mkdocs build
then copy all the content in the site
folder to the website root folder.
1.2. Visual Studio Code⚓
Download and install Visual Studio Code - a lightweight but powerful source code editor. It well supports users to write code, documents, notes. This editor also have some extensions to turn it into a full-feature IDE for coding, such as PlatformIO.
Useful extensions for writing in Markdown format and editing HTML template:
- Markdown All in One: add keyboard shortcuts, auto completion, edit and format list and table
- Markdown Paste: paste images, links from the clipboard
- Draw.io Integration: edit diagrams and svg images
- Jinja: highlight Jinja syntax in HTML templates
- Sublime Text Keymap and Settings Importer: import keybindings and settings
- Code Spell Checker: catch common spelling errors
- Prettier - Code formatter: a formatter which supports a lot of languages
2. Configuration⚓
Material for MkDocs is just a start point. It is needed to be customized a little to fit my personal tastes. Refer to the official homepage of for more and complete guides, as I just list here main points to tweak the theme.
2.1. Site information⚓
Site information consists of the name, the URL, the title, a description and some keywords that are used to get brief information about the content of the site.
These information is configured in the config file mkdocs.yml
as below:
site_name: Code Inside Out
site_url: https://www.codeinsideout.com/ # must have the trailing slash
site_author: vqtrong
site_email<EMAIL_ADDRESS>site_description: >-
Interesting stuff in Embedded Systems and IoT Applications.
From hardwares to cloud applications. Step by step.
site_keywords: embedded systems application programming
copyright: >-
© 2021 Code Inside Out
The social links can be added in the extra
section in the config file mkdocs.yml
.
Refer to the guide of setting up the footer. The icon field must point to a valid icon path referencing to a bundled icon.
extra:
social:
- icon: fontawesome/brands/github-alt
link: https://github.com/vuquangtrong
name: vuquangtrong
- icon: fontawesome/brands/facebook-f
link: https://facebook.com/trongvq
name: trongvq
- icon: fontawesome/brands/linkedin-in
link: https://www.linkedin.com/in/vqtrong
name: vqtrong
2.2. Color palette⚓
Changing color is to select colors for 2 main groups:
- the primary color which is used for the header, the sidebar, text links and several other components.
- the accent color which is used to denote elements that can be interacted with, e.g. hovered links, buttons and scroll-bars.
Both of them can be changed in mkdocs.yml
by choosing a valid color name. As this page is intent to be printed on paper, I choose the white color as the primary look and feel, and the deep orange color for interactive elements.
theme:
palette:
primary: white
accent: deep orange
2.3. Fonts⚓
Serif fonts1 are widely used for body text because they are considered to be more easier to read than Sans-Serif fonts in print.
For better reading, distinguishing the digit zero 0
from the Latin script letter Oh o
or O
is a way to avoid mistake, especially while reading technical notes. Fonts for source code do have slashed / dotted / open zero2, but fonts for reading don’t have those styles.
It’s also needed to clearly distinguish the digit one 1
with lowercase i i
, the uppercase i I
, and the lowercase l l
. Luckily, they usually do not stand close to each other.
To replace the defaults fonts, this site uses Noto Serif for the body text, and Roboto Mono for the code block.
theme:
font:
text: Noto Serif
code: Roboto Mono
Can you easily read below pairs of characters?
- Body text: 0o 0O oO 1i 1I 1l 1L iI il iL Il IL lL
- Code block:
0o 0O oO 1i 1I 1l 1L iI il iL Il IL lL
2.4. Logo & Icon⚓
I want to replace the default icon and logo with this code
symbol .
theme:
icon:
logo: fontawesome/solid/code
favicon: favicon.png
To use the included icons in Material theme, refer to Markdown syntax - Icons and Emojis.
2.5. Navigation⚓
Here are some interesting features for the navigation in Material theme:
2.5.1. Instant loading⚓
When instant loading is enabled, clicks on internal links will be intercepted and dispatched via XHR without fully reloading the page. The resulting page is parsed and injected and all event handlers and components are rebound automatically. This means that the site behaves like a Single Page Application, which is especially useful for large documentation sites that come with a massive search index, as the search index will now remain intact in-between document switches.
Material for MkDocs is the only MkDocs theme offering this feature.
Dynamic Javascript-enabled elements do not work after AJAX content is loaded
After an AJAX request is done, the old content is replaced with the new content, causing dynamic content and handlers are destroyed, such as items were selected by javascript query, Mermaid code blocks, disqus comments, registered event for clicking, etc.
A solution is given in Fix AJAX issue.
2.5.2. Navigation tabs⚓
When tabs are enabled, top-level sections (first-level directories in the docs
folder) are rendered in a menu layer below the header.
2.5.3. Back-to-top button⚓
A back-to-top button can be shown when the user, after scrolling down, starts to scroll up again. It’s rendered in the lower right corner of the viewport, and help to go to the top a the page quickly.
2.5.4. Hide header bar⚓
When auto hiding is enabled, the header is automatically hidden when the user scrolls past a certain threshold, leaving more space for content.
theme:
features:
- navigation.instant
- navigation.tabs
- navigation.top
- header.autohide
2.6. Table of Content⚓
The Table of Content extension provides a quick navigation between sections in the post, it also places an anchor link at each header. This anchor can be used to link the header from other pages. The toc_depth: 4
makes the list displays from

to

.
markdown_extensions:
- toc:
permalink: ⚓
slugify: !!python/name:pymdownx.slugs.uslugify
toc_depth: 4
2.7. Site analytics⚓
Material for MkDocs natively integrates with Google Analytics. Just need to create a new GA property in order to obtain a unique tracking id of the form UA-XXXXXXXX-X
, add it to mkdocs.yml:
google_analytics:
- UA-XXXXXXXX-X
- auto
2.8. Comments section⚓
Material for MkDocs is natively integrated with Disqus, a comment system that provides a wide range of features like social integrations, user profiles, as well as spam and moderation tools.
After setting up the site_url
in mkdocs.yml
, Disqus is configured by adding the Disqus shortname:
extra:
disqus: "shortname"
This will insert a comment system on every page, except the index page. If the Metadata extension is enabled, Disqus can be disabled per page by using an empty string:
---
disqus: ""
---
2.9. Extra styles and scripts⚓
Add stylesheets and javascript files to the docs
directory as below structure:
.
├─ docs/
│ ├─ assets/
│ | └─ extra.css
│ | └─ extra.js
| └─ blog/
└─ mkdocs.yml
Then, add the following line to mkdocs.yml
:
extra_css:
- assets/extra.css
extra_javascript:
- assets/extra.js
It’s ready to add extra styles and scripts to the site at the moment, but it should be done later after adding new layouts and elements to the theme. At this time, I just need to add some small additional styles to make the theme look a bit harmonious with the selected theme color.
To do that, in the webpage, right-click on an element, then select Inspect menu to go to the Developer Mode, and check the tag and the class of the selected element.
The page content is usually wrapped inside the tag

, so select either the tag or a class of that tag to use as the container of extra styles. Here are some small requirements:
-
Logo and headers should be in orange to be highlighted, and active links can be in dark blue:
.md-logo, .md-typeset h1 { color: orangered; } .md-typeset h2, .md-typeset h3, .md-typeset h4, .md-tabs__link.md-tabs__link--active, .md-nav__link.md-nav__link--active { color: darkblue; }
-
Search input should have white background color:
.md-search__input { background-color: white !important; }
-
Non-highlighted code needs stand out a bit in dark red in white background:
.md-typeset code { color: darkred; background-color: rgba(0, 0, 0, 0.01); }
-
Normal paragraph should be fully justified:
.md-typeset p { text-align: justify; }
-
Emphasized text should be in dark magenta:
.md-typeset em { color: darkmagenta; }
-
Footer should look smaller by changing the background color:
.md-footer { color: unset; background-color: unset; } .md-footer-meta { background-color: black; }
For more stylings, please read more in Customize theme.
2.10. Override templates⚓
MkDocs allows to override the them by just adding extra files that will replace the original ones when building the site. Create a new folder overrides
in the project folder to save the overriding files, then enable them in the config file mkdocs.yml
:
theme:
name: material
custom_dir: overrides
2.10.1. Override files⚓
The structure in the overrides
directory must mirror the directory structure of the original theme, as any file in the overrides directory will replace the file with the same name which is part of the original theme. Besides, further assets may also be put in the overrides directory.
.
├─ .icons/ # Bundled icon sets
├─ assets/
│ ├─ images/ # Images and icons
│ ├─ javascripts/ # JavaScript
│ └─ stylesheets/ # Stylesheets
├─ partials/
│ ├─ integrations/ # Third-party integrations
│ │ ├─ analytics.html # - Google Analytics
│ │ └─ disqus.html # - Disqus
│ ├─ languages/ # Localized languages
│ ├─ footer.html # Footer bar
│ ├─ header.html # Header bar
│ ├─ language.html # Localized labels
│ ├─ logo.html # Logo in header and sidebar
│ ├─ nav.html # Main navigation
│ ├─ nav-item.html # Main navigation item
│ ├─ palette.html # Color palette
│ ├─ search.html # Search box
│ ├─ social.html # Social links
│ ├─ source.html # Repository information
│ ├─ source-date.html # Last updated date
│ ├─ source-link.html # Link to source file
│ ├─ tabs.html # Tabs navigation
│ ├─ tabs-item.html # Tabs navigation item
│ ├─ toc.html # Table of contents
│ └─ toc-item.html # Table of contents item
├─ 404.html # 404 error page
├─ base.html # Base template
└─ main.html # Default page
The template file base.html
, which originally located in the folder .venv\Lib\site-packages\material
, is the starting point of any site’s page. All other pages should extend from it. The main.html
template, which extends the base.html
, is used to add a custom template.
To use other template, in the metadata of the Markdown file, set the attribute template
with the name of template file. For example:
---
title: Blog
template: blog.html
---
2.10.2. Override blocks⚓
Besides overriding partials, it’s also possible to override (and extend) template blocks, which are defined inside the template files and wrap specific features. To override a block, create a new template .html
file inside the overrides
directory, and define a same block name with the one which will be overridden:
{% extends "base.html" %}
{% block htmltitle %}
<title>New title</title>
{% endblock %}
To extend a block, use the {{ super() }}
command:
{% extends "base.html" %}
{% block head %}
{{ super() }}
Appended content
{% endblock %}
To replace a block, don’t use the {{ super() }}
command.
{% block head %}
New content
{% endblock %}
The list of blocks:
analytics # Wraps the Google Analytics integration
announce # Wraps the announcement bar
config # Wraps the JavaScript application config
content # Wraps the main content
disqus # Wraps the Disqus integration
extrahead # Empty block to add custom meta tags
fonts # Wraps the font definitions
footer # Wraps the footer with navigation and copyright
header # Wraps the fixed header bar
hero # Wraps the hero teaser (if available)
htmltitle # Wraps the <title> tag
libs # Wraps the JavaScript libraries (header)
outdated # Wraps the version warning
scripts # Wraps the JavaScript application (footer)
source # Wraps the linked source files
site_meta # Wraps the meta tags in the document head
site_nav # Wraps the site navigation and table of contents
styles # Wraps the stylesheets (also extra sources)
tabs # Wraps the tabs navigation (if available)
2.10.3. The index page⚓
The index page of the website is located at docs\index.md
. Material theme created a default one then it has to be modified. I’d like to write a brief information about me and why this blog is created:
Welcome to
# Code Inside Out
Interesting stuff in Embedded Systems and IoT Applications.
From hardwares to cloud applications. Step by step.
(ﾉ ◕ ヮ ◕)ﾉ\*:・ﾟ ✧
2.10.4. The 404 page⚓
Whenever a page is not found in a website, the error 404
is return to the requested users. I need to create this special page to display a short message and guide user to search in this blog.
The 404 page should be created in the overrides
folder as it will replace the default 404 page of Material theme. Its layout is based on the base.html
, and the content is a message displayed in the center of the page. The disqus
comment section is removed. The sidebar should not be visible to display message clearly.
{% extends "main.html" %}
{% block content %}

Oops! Something went wrong!

Please go back to the

{{ config.site_name }}

homepage,

or press S to search on this site.

{% endblock %}
{% block disqus %}
{% endblock %}
3. Markdown extensions⚓
Markdown comes with a simple syntax to create headers, links, images, and paragraphs with formatted text, lists. However, that’s not enough. Some Markdown extensions bring more syntaxes to create complex elements or new layouts that help writing documents easier, faster, and look professional.
Read more in Markdown syntax.
4. MkDocs plugins⚓
New features can be added to MkDocs engine by installing plugins. These packages can modify the navigation behavior, or render new content types, or export the site to PDF documents. Plugins also can be modified easily as they are written in Python.
Read more in MkDocs plugins.
5. Customize theme⚓
A personal website should look different to others to make it unique and standout. I prefer a simple look which goes straight to the content, and pages should be clear to be printed on papers. Therefore, I modified styles for some elements, also bring must-have elements of a blog like tag cloud, tag page, list of posts.
Read more in Customize theme.
6. Print to PDF⚓
For printing or offline reading, the document should be exported to PDF format. A manual method is to print each post by the user browser. There is a plugin to automatically export all site’s posts to PDF during the build time, but it needs some configuration to work as I expected. Generated PDF files can be download by clicking on the download button at the beginning of each page.
Read more in Print to PDF.


Hey guys, today I will talk about how to use strings In Python, and some useful methods available. Strings in python are exactly equal a strings in other languages like Java or Javascript, a sequence of one or more characters. Strings can be created within either single quotes ‘ or double quotes “ in Python, so to create a string, enclose a seq... Read more 07 Jan 2019 - 4 minute read
Sup guys, I’m back, this time to talk about Johnny Five, a JavaScript plataform for IoT and Robotic. In this post we will see how to control a Led by HTTP request. Before we start, for this post It Is necessary that you have an Arduino and at least one Led. Let’s start installing Johnny-Five and your requirements: apt-get install nodejs-legac... Read more 01 Dec 2018 - 4 minute read
Olá terráqueos, no post de hoje vamos ver como criar um bot utilizando o Hubot, um robô customizável e open source, criado e distribuído pelo GitHub. Antes de começar é necessário que você tenha o Node e o NPM instalados em sua máquina, para verificar, abra o terminal e digite os seguintes comandos: npm --version node --version Caso precise ... Read more 18 Nov 2018 - 9 minute read
Hi guys, today I will talk about a very interesting thing called chatbot and how build one with DialogFlow, so I hope you enjoy. What is a chatbot According to Oxford Dictionaries, a chatbot is: **“A computer program designed to simulate conversation with human users, especially over the Internet.” You can may ask yourself, why I will wa... Read more 14 Oct 2018 - 7 minute read
Hi guys, today I have a quick tip where I will show you another cool functionality of modern JavaScript, the operators spread and rest. This little guys has been implanted in ES6 and bellow is a description of each one. Rest operator: Used to merge a list of function arguments into an array: function sortArgs(...args){ //args is an array so... Read more 15 Sep 2018 - 1 minute read


I discovered the effects of Tussin accidently after a bronchial infection early winter 2000. I started taking 2 'shots' per night because I realized it made me more relaxed while at the same time seemed to give me more energy. I also felt my thinking was clearer than it had been in years. The only negative side effects I noticed were insomnia and occasional bouts of nausea and vomiting. I also noticed a decrease in my appetite (which I didn't consider a bad thing!) During the 8 months I took Tussin, I rediscovered my faith in traditional Christianity. I mistakenly believed the Tussin was responsible for this new peace of mind. I was wrong.
Because of other health problems (and because I found myself unable to go more than 2-3 nights without taking Tussin), I went to my family doctor, 'confessed' my Tussin abuse, and was diagnosed as suffering from depression and generalized anxiety disorder. My primary care physician prescribed Paxil which was to relieve the anxiety for which I was 'self-medicating' with the Tussin. After 6 weeks of discontinuing my Tussin use and taking 20-30 mg. of the prescribed Paxil, I found myself in a hospital emergency room, disoriented, confused and convinced I had gone through the ultimate salvation/conversion experience.
Suddenly all my past fears and hopes were resurfacing, seemingly unbidden. I was convinced I was going to see dead friends and family around every corner. I distrusted everyone around me and felt there were 'signs' from God everywhere I looked. I was admitted to the psychiatric ward of the hospital for 4 days. During this time I was taken off the Paxil and needed to be given a mild sedative in order to sleep. My confusion lessened during those 4 days, but I still was unsure of what was happening to me.
This was over a week ago. Although I'm still sorting out what happened to me, I am convinced the Tussin played a major role. How much of a role remains to be seen and whether I will ever feel 'normal' again is also a question yet to be answered. I wrote this experience report simply because I want others to be aware that Tussin is far from a benign recreational drug. Wishing you more natural ways of finding Peace!!
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


TPanelCreateEvent = procedure(Sender: TObject; const AName, AType, SRC: string;
Panel: ThvPanel) of Object;
The TPanelCreateEvent type is the type for the OnPanelCreate event. This event occurs when a <PANEL> tag is encountered at document load time.
Sender is the THtmlViewer displaying the ThvPanel.
Panel is the ThvPanel (similar to TPanel) created for the display. Its Name property has been assigned to the NAME attribute value and its Height and Width properties have been assigned the values of the HEIGHT and WIDTH attributes.
AType and SRC contains the value assigned to the TYPE and SRC attributes.
See also:


We promote interactions, production of most relevant ideas and we act to create high quality documents that sustain ideas with strength. Our Design Suite has been designed to allow each and every kind of skills and expertise to express themselves together, serving a common purpose. Simplicity and quality are truly our keywords to deliver a never lived before experience. We design with main focus, quick and natural handling by our users.
We promote interactions, production of most relevant ideas and we act to create high quality documents that sustain ideas with strength. Our Design Suite has been designed to allow each and every kind of skills and expertise to express themselves together, serving a common purpose. Simplicity and quality .


Bases: object
Main entry point for Spark Streaming functionality. A StreamingContext represents the connection to a Spark cluster, and can be used to create DStream various input sources. It can be from an existing SparkContext. After creating and transforming DStreams, the streaming computation can be started and stopped using context.start() and context.stop(), respectively. context.awaitTermination() allows the current thread to wait for the termination of the context by stop() or by an exception.
Add a [[org.apache.spark.streaming.scheduler.StreamingListener]] object for receiving system events related to streaming.
Wait for the execution to stop.
| Parameters: | timeout – time to wait in seconds |
|---|
Wait for the execution to stop. Return true if it’s stopped; or throw the reported error during the execution; or false if the waiting time elapsed before returning from the method.
| Parameters: | timeout – time to wait in seconds |
|---|
Create an input stream that monitors a Hadoop-compatible file system for new files and reads them as flat binary files with records of fixed length. Files must be written to the monitored directory by “moving” them from another location within the same file system. File names starting with . are ignored.
| Parameters: |
|
|---|
Sets the context to periodically checkpoint the DStream operations for master fault-tolerance. The graph will be checkpointed every batch interval.
| Parameters: | directory – HDFS-compatible directory where the checkpoint data will be reliably stored |
|---|
Return either the currently active StreamingContext (i.e., if there is a context started but not stopped) or None.
Either return the active StreamingContext (i.e. currently started but not stopped), or recreate a StreamingContext from checkpoint data or create a new StreamingContext using the provided setupFunc function. If the checkpointPath is None or does not contain valid checkpoint data, then setupFunc will be called to create a new context and setup DStreams.
| Parameters: |
|
|---|
Either recreate a StreamingContext from checkpoint data or create a new StreamingContext. If checkpoint data exists in the provided checkpointPath, then StreamingContext will be recreated from the checkpoint data. If the data does not exist, then the provided setupFunc will be used to create a new context.
| Parameters: |
|
|---|
Create an input stream from an queue of RDDs or list. In each batch, it will process either one or all of the RDDs returned by the queue.
NOTE: changes to the queue after the stream is created will not be recognized.
| Parameters: |
|
|---|
Set each DStreams in this context to remember RDDs it generated in the last given duration. DStreams remember RDDs only for a limited duration of time and releases them for garbage collection. This method allows the developer to specify how to long to remember the RDDs (if the developer wishes to query old data outside the DStream computation).
| Parameters: | duration – Minimum duration (in seconds) that each DStream should remember its RDDs |
|---|
Create an input from TCP source hostname:port. Data is received using a TCP socket and receive byte is interpreted as UTF8 encoded \n delimited lines.
| Parameters: |
|
|---|
Return SparkContext which is associated with this StreamingContext.
Start the execution of the streams.
Stop the execution of the streams, with option of ensuring all received data has been processed.
| Parameters: |
|
|---|
Create an input stream that monitors a Hadoop-compatible file system for new files and reads them as text files. Files must be wrriten to the monitored directory by “moving” them from another location within the same file system. File names starting with . are ignored.
Create a new DStream in which each RDD is generated by applying a function on RDDs of the DStreams. The order of the JavaRDDs in the transform function parameter will be the same as the order of corresponding DStreams in the list.
Create a unified DStream from multiple DStreams of the same type and same slide duration.
Bases: object
A Discretized Stream (DStream), the basic abstraction in Spark Streaming, is a continuous sequence of RDDs (of the same type) representing a continuous stream of data (see RDD in the Spark core documentation for more details on RDDs).
DStreams can either be created from live data (such as, data from TCP sockets, Kafka, Flume, etc.) using a StreamingContext or it can be generated by transforming existing DStreams using operations such as map, window and reduceByKeyAndWindow. While a Spark Streaming program is running, each DStream periodically generates a RDD, either from live data or by transforming the RDD generated by a parent DStream.
Persist the RDDs of this DStream with the default storage level (MEMORY_ONLY_SER).
Enable periodic checkpointing of RDDs of this DStream
| Parameters: | interval – time in seconds, after each period of that, generated RDD will be checkpointed |
|---|
Return a new DStream by applying ‘cogroup’ between RDDs of this DStream and other DStream.
Hash partitioning is used to generate the RDDs with numPartitions partitions.
Return a new DStream by applying combineByKey to each RDD.
Return the StreamingContext associated with this DStream
Return a new DStream in which each RDD has a single element generated by counting each RDD of this DStream.
Return a new DStream in which each RDD contains the counts of each distinct value in each RDD of this DStream.
Return a new DStream in which each RDD contains the count of distinct elements in RDDs in a sliding window over this DStream.
| Parameters: |
|
|---|
Return a new DStream in which each RDD has a single element generated by counting the number of elements in a window over this DStream. windowDuration and slideDuration are as defined in the window() operation.
This is equivalent to window(windowDuration, slideDuration).count(), but will be more efficient if window is large.
Return a new DStream containing only the elements that satisfy predicate.
Return a new DStream by applying a function to all elements of this DStream, and then flattening the results
Return a new DStream by applying a flatmap function to the value of each key-value pairs in this DStream without changing the key.
Apply a function to each RDD in this DStream.
Return a new DStream by applying ‘full outer join’ between RDDs of this DStream and other DStream.
Hash partitioning is used to generate the RDDs with numPartitions partitions.
Return a new DStream in which RDD is generated by applying glom() to RDD of this DStream.
Return a new DStream by applying groupByKey on each RDD.
Return a new DStream by applying groupByKey over a sliding window. Similar to DStream.groupByKey(), but applies it over a sliding window.
| Parameters: |
|
|---|
Return a new DStream by applying ‘join’ between RDDs of this DStream and other DStream.
Hash partitioning is used to generate the RDDs with numPartitions partitions.
Return a new DStream by applying ‘left outer join’ between RDDs of this DStream and other DStream.
Hash partitioning is used to generate the RDDs with numPartitions partitions.
Return a new DStream by applying a function to each element of DStream.
Return a new DStream in which each RDD is generated by applying mapPartitions() to each RDDs of this DStream.
Return a new DStream in which each RDD is generated by applying mapPartitionsWithIndex() to each RDDs of this DStream.
Return a new DStream by applying a map function to the value of each key-value pairs in this DStream without changing the key.
Return a copy of the DStream in which each RDD are partitioned using the specified partitioner.
Persist the RDDs of this DStream with the given storage level
Print the first num elements of each RDD generated in this DStream.
| Parameters: | num – the number of elements from the first will be printed. |
|---|
Return a new DStream in which each RDD has a single element generated by reducing each RDD of this DStream.
Return a new DStream by applying reduceByKey to each RDD.
Return a new DStream by applying incremental reduceByKey over a sliding window.
invFunc can be None, then it will reduce all the RDDs in window, could be slower than having invFunc.
| Parameters: |
|
|---|
Return a new DStream in which each RDD has a single element generated by reducing all elements in a sliding window over this DStream.
if invReduceFunc is not None, the reduction is done incrementally using the old window’s reduced value :
2. “inverse reduce” the old values that left the window (e.g., subtracting old counts) This is more efficient than invReduceFunc is None.
| Parameters: |
|
|---|
Return a new DStream with an increased or decreased level of parallelism.
Return a new DStream by applying ‘right outer join’ between RDDs of this DStream and other DStream.
Hash partitioning is used to generate the RDDs with numPartitions partitions.
Save each RDD in this DStream as at text file, using string representation of elements.
Return all the RDDs between ‘begin’ to ‘end’ (both included)
begin, end could be datetime.datetime() or unix_timestamp
Return a new DStream in which each RDD is generated by applying a function on each RDD of this DStream.
func can have one argument of rdd, or have two arguments of (time, rdd)
Return a new DStream in which each RDD is generated by applying a function on each RDD of this DStream and ‘other’ DStream.
func can have two arguments of (rdd_a, rdd_b) or have three arguments of (time, rdd_a, rdd_b)
Return a new DStream by unifying data of another DStream with this DStream.
| Parameters: | other – Another DStream having the same interval (i.e., slideDuration) as this DStream. |
|---|
Return a new “state” DStream where the state for each key is updated by applying the given function on the previous state of the key and the new values of the key.
| Parameters: | updateFunc – State update function. If this function returns None, then corresponding state key-value pair will be eliminated. |
|---|
Return a new DStream in which each RDD contains all the elements in seen in a sliding window of time over this DStream.
| Parameters: |
|
|---|
Bases: object
Called when processing of a batch of jobs has completed.
Called when processing of a batch of jobs has started.
Called when a batch of jobs has been submitted for processing.
Called when processing of a job of a batch has completed
Called when processing of a job of a batch has started.
Called when a receiver has reported an error
Called when a receiver has been started
Called when a receiver has been stopped
Bases: object
Represent the host and port info for a Kafka broker.
Bases: object
Kafka message and metadata information. Including topic, partition, offset and message
Bases: object
Note
Experimental
Create an input stream that directly pulls messages from a Kafka Broker and specific offset.
This is not a receiver based Kafka input stream, it directly pulls the message from Kafka in each batch duration and processed without storing.
This does not use Zookeeper to store offsets. The consumed offsets are tracked by the stream itself. For interoperability with Kafka monitoring tools that depend on Zookeeper, you have to update Kafka/Zookeeper yourself from the streaming application. You can access the offsets used in each batch from the generated RDDs (see
To recover from driver failures, you have to enable checkpointing in the StreamingContext. The information on consumed offset can be recovered from the checkpoint. See the programming guide for details (constraints, etc.).
| Parameters: |
|
|---|---|
| Returns: | A DStream object |
Note
Experimental
Create a RDD from Kafka using offset ranges for each topic and partition.
| Parameters: |
|
|---|---|
| Returns: | A RDD object |
Create an input stream that pulls messages from a Kafka Broker.
| Parameters: |
|
|---|---|
| Returns: | A DStream object |
Bases: object
Represents a range of offsets from a single Kafka TopicAndPartition.
Bases: object
Create an input stream that pulls messages from a Kinesis stream. This uses the Kinesis Client Library (KCL) to pull messages from Kinesis.
Note: The given AWS credentials will get saved in DStream checkpoints if checkpointing is enabled. Make sure that your checkpoint directory is secure.
| Parameters: |
|
|---|---|
| Returns: | A DStream object |
Bases: object
Creates an input stream that is to be used with the Spark Sink deployed on a Flume agent. This stream will poll the sink for data and will pull events as they are available.
| Parameters: |
|
|---|---|
| Returns: | A DStream object |
Create an input stream that pulls events from Flume.
| Parameters: |
|
|---|---|
| Returns: | A DStream object |
Bases: object
Create an input stream that pulls messages from a Mqtt Broker.
| Parameters: |
|
|---|---|
| Returns: | A DStream object |


{% extends "base.html" %} {% import 'bootstrap/wtf.html' as wtf %} {% block app_content %}
Log In to save your groups!


How to Customise
Image hover elements can be customised by applying a collection of classes within the elements markup. One class can be applied from each of the following categories allowing endless possibilties to customise your Image Hover element to your own taste.
- Hover Border Animation
- Hover Image Animation
- Hover Text Animation
- Text Animation Delay
- Hover Overlay Style
- Caption Layout
Elements can be customised further by defining custom properties either globally or inline within a single or selected number of elements.
- –text-color
- –primary-color
- –secondary-color
- –padding
- –border-radius
- –transition-duration
- –border-margin
- –border-width
- –border-color
- –image-opacity
Example

Creative Control


Applications written using Scala and Play Framework 2.1.0 using Nginx as front-end in reverse proxy mode.
Disable directory browsing for your application's web directories.
Directory browsing allows an attacker to browse your application's directory structure in search of unprotected files and components.
Disable directory browsing at all times.
Use the following steps to successfully disable directory browsing:
Identify if directory browsing is enabled. Navigate to your application's directories. Identify whether your application's server correctly returns an HTTP error message. If it incorrectly returns the directory contents, continue with the following steps.
Locate the default Nginx configuration. In Nginx, the default configuration file is located at /etc/nginx/sites-availabe/default. In the default "server" block, look for the presence of the "location" element that is mapped to the directory for which directory browsing is to be disabled. Example:
server { listen 80; server_name domain.com www.domain.com; access_log /var/...........................; root /path/to/root; location / { index index.html index.htm; } location /somedir { autoindex on; } }
Deny directory browsing in the default Nginx configuration. Initialize the HttpAutoindexModule with "off" to disable directory listing. Example:
server { listen 80; server_name domain.com www.domain.com; access_log /var/...........................; root /path/to/root; location / { index index.php index.html index.htm; } location /somedir { autoindex off; } }
An application is deployed on a production server. Unfortunately, the developers did not disable directory browsing. This allows an attacker to search for unprotected configuration files.
An application is deployed on a production server. Because the developers have disabled directory browsing, it is difficult for an attacker to use HTTP browsing to search for unprotected configuration files.


This chapter looks at some basic concepts of audio, both analogue and digital.
Audio is an analogue phenomenon. Sounds are produced in all sorts of ways, through voice, instruments and natural events such as trees falling in forests (whether or not there is anyone to hear). Sounds received at a point can be plotted as amplitude against time and can assume almost any functional state, including discontuous.
The analysis of sound is frequently done by looking at its spectrum. Mathematically this is achieved by taking the Fourier transform, but the ear performs almost a similar transform just by the structure of the ear. "Pure" sounds heard by the ear correspond to simple sine waves, and harmonics correspond to sine waves which have a frequency a multiple of the base sine wave.
Analogue signals within a system such as an analogue audio amplifier are designed to work with these spectral signals. They try to produce an equal amplification across the audible spectrum.
Computers, and an increasingly large number of electronic devices, work on digital signals, comprised of bits of ones and zeroes. Bits are combined into bytes with 256 possible values, or 16 bit words with 65536 possible values, or even larger combinations such as 32 or 64 bit words.
Digitising an analogue signal means taking samples from that signal at regular intervals, and representing those samples on a discrete scale. The frequency of taking samples is the sample rate. For example, audio on a CD is sampled at 44,100hz, that is, 44,100 times each second. On a DVD, samples may be taken upto 192,000 times per second, with a sampling rate of 192kHz. Conversely, the standard telephone sampling rate is 8kHz.
This figure from
Wikipedia: Pulse-code modulation
illustrates sampling:
The sampling rate affects two major factors. Firstly, the higher the sampling rate, the larger the size of the data. All other things being equal, doubling the sample rate will double the data requirements. On the other hand the Nyquist-Shannon theorem places limits on the accuracy of sampling continous data: an analogue signal can only be reconstructed from a digital signal (i.e. be distortion-free) if the highest frequency in the signal is less than one-half the sampling rate.
This is often where the arguments about the "quality" of vinyl versus CDs end up, as in Vinyl vs. CD myths refuse to die . With a sampling rate of 44.1kHz, frequencies in the original signal above 22.05kHz may not be reproduced accurately when converted back to analogue for a loudspeaker or headphones. Since the typical hearing range for humans is only upto 20,000hz (and mine is now down to about 10,000hz) then this should not be a significant problem. But some audiophiles claim to have amazingly sensitive ears...
The sample format is the other major feature of digitizing audio: the number of bits used to discretize the sample. For example, telephone signals use 8kHz sampling rate and 8-bit resolution (see How Telephones Work ) so that a telephone signal can only convey 2^8 i.e. 256 levels.
Most CDs and computer systems use 16-bit formats. (see Audacity - Digital Sampling ) giving a very fine gradation of the signal and allowing a range of 96dB.
A frame holds all of the samples from one time instant. For a stereo device, each frame holds two samples, while for a five-speaker device, each frame would hold five samples.
Pulse-code modulation (PCM) is the standard form of representing a digitized analogue signal. From Wikipedia
Pulse-code modulation (PCM) is a method used to digitally represent sampled analog signals. It is the standard form for digital audio in computers and various Blu-ray, DVD and Compact Disc formats, as well as other uses such as digital telephone systems. A PCM stream is a digital representation of an analog signal, in which the magnitude of the analog signal is sampled regularly at uniform intervals, with each sample being quantized to the nearest value within a range of digital steps.
PCM streams have two basic properties that determine their fidelity to the original analog signal: the sampling rate, which is the number of times per second that samples are taken; and the bit depth, which determines the number of possible digital values that each sample can take.
However, even though this is the "standard", there are variations . The principal one concerns the representation as bytes in a word-based system: little-endian or big-endian . The next variation is signed versus unsigned .
There are a number of other variations which are less important, such as whether the digitisation is linear or logarithmic. See the Multi-media Wikipedia for discussion of these.
From Introduction to Sound Programming with ALSA
When a sound device is active, data is transferred continuously between the hardware and application buffers. In the case of data capture (recording), if the application does not read the data in the buffer rapidly enough, the circular buffer is overwritten with new data. The resulting data loss is known as overrun. During playback, if the application does not pass data into the buffer quickly enough, it becomes starved for data, resulting in an error called underrun.
Latency is the amount of time that elapses from when a signal enters a system to when it (or its equivalent such as an amplified version) leaves the system.
From Ian Waugh's Fixing Audio Latency Part 1:
Latency is a delay. It's most evident and problematic in computer-based music audio systems where it manifests as the delay between triggering a signal and hearing it. For example, pressing a key on your MIDI keyboard and hearing the sound play through your sound card.
It's like a delayed reaction and if the delay is very large it becomes impossible to play anything in time because the sound you hear is always a little bit behind what you're playing which is very distracting.
This delay does not have to be very large before it causes problems. Many people can work with a latency of about 40ms even though the delay is noticeable, although if you are playing pyrotechnic music lines it may be too long.
The ideal latency is 0 but many people would be hard pushed to notice delays of less than 8-10ms and many people can work quite happily with a 20ms latency.
A Google search for "measuring audio latency" will turn up many sites.
I use a crude - but simple - test. I installed Audacity on a separate PC,
and used it to record simultaneously a sound I made and that sound when
picked up and played back by the test PC. I banged a spoon against a bottle
to get a sharp percursive sound. When magnified, the recorded sound showed
two peaks and selecting the region between the peaks showed me the latency
in the selection start/end. In the figure below, these are
17.383 and 17.413 seconds, with a latency of 30 msecs.
Sampling an analogue signal will be done at regular intervals. Ideally, playback should use exactly those same intervals. But, particularly in networked systems, the periods may not be regular. Any irregularity is known as jitter . I don't have a simple way of testing for jitter - I'm still stuck on latency as my major problem!
Mixing means taking inputs from one or more sources, possibly doing some processing on these input signals and sending them to one or more outputs. The origin, of course, is in physical mixers which would act on analogue signals. In the digital world the same functions would be performed on digital signals.
A simple document describing analogues mixers is The Soundcraft Guide to Mixing . This covers the functions of
This short chapter has introduced some of the basic concepts that will occupy much of the rest of this book. The Scientist and Engineer's Guide to Digital Signal Processing by Steven W Smith has wealth of further detail,


CrossCafe
4.3 - 190 reviews
Cafe
Save
Nearby
Share
Breakfast - Cosy - Casual
You visited today
Riegrova 382/24, 779 00 Olomouc
H6WX+27 Olomouc
crosscafe.cz
605 484 796
Open now: 9AM–6PM
Add a label
suggest an edit


Note: parameters are matched by their names
100 000 times create this object graph and add them to array in first case, leave them to GC in second case
Ninject - removed from comparison because only one didn't worked with Mono and was 5 times slower then second worst
|
|
|
|
/


Owner Sign up
Name:
email:
Mobile No.
:+91
Location
Restaurant_name
sex:
Male
Female
Username:
Password:
Re-Password:
Already a member sign here


SATURDAY
BREAKFAST Frittata made with 3 large egg whites, 2 tablespoons diced bell peppers, 2 teaspoons chopped spinach, 2 tablespoons part-skim shredded mozzarella, and 2 teaspoons pesto 1/2 cup fresh raspberries 1 small bran muffin 1 cup skim milk SNACK 1/2 cup low-fat vanilla yogurt with 1 tablespoon ground flaxseed and 1/2 cup diced pear LUNCH 4 ounces sliced turkey breast Tomato-cucumber salad made with 5 slices tomato, 1/4 cup sliced cucumber, 1 teaspoon fresh chopped thyme, and 1 tablespoon fat-free Italian dressing 1 medium orange SNACK Smoothie made with 3/4 cup skim milk, 1/2 banana, 1/2 cup low-fat yogurt, and 1/4 cup sliced strawberries DINNER 4 ounces red snapper baked with 1 teaspoon olive oil, 1 teaspoon lemon juice, and 1/2 teaspoon no-sodium seasoning 1 cup spaghetti squash with 1 teaspoon olive oil and 2 teaspoon grated Parmesan cheese 1 cup steamed green beans with 1 tablespoon slivered almonds


|
Fusion3D
Version 6.04
|
Provides storage for images that are defined in screen coordinates (always staying same size regardless of zoom). More...
#include <osus_image_store_class.h>
Public Member Functions | |
| osus_image_store_class () | |
| Constructor. More... | |
| ~osus_image_store_class () | |
| Destructor. More... | |
| int | make_sensor_image_screen (float scaleFactor, int image_nx, int image_ny, int image_np, unsigned char *image_data) |
| Draw image for the current frame in screen coordinates (which does not scale with zoom). More... | |
| SoSeparator * | get_image_subtree (int index) |
| Draw image for the current frame in screen coordinates (which does not scale with zoom). More... | |
Provides storage for images that are defined in screen coordinates (always staying same size regardless of zoom).
Images are created and stored internally. They can then be retrieved by image index.
| osus_image_store_class::osus_image_store_class | ( | ) |
Constructor.
| osus_image_store_class::~osus_image_store_class | ( | ) |
Destructor.
| SoSeparator * osus_image_store_class::get_image_subtree | ( | int | index | ) |
Draw image for the current frame in screen coordinates (which does not scale with zoom).
| int osus_image_store_class::make_sensor_image_screen | ( | float | scaleFactor, |
| int | image_nx, | ||
| int | image_ny, | ||
| int | image_np, | ||
| unsigned char * | image_data | ||
| ) |
Draw image for the current frame in screen coordinates (which does not scale with zoom).


#include <Sine.h>
◆ copy()
| std::unique_ptr< Expression > symcpp::Sine::copy |
( |
| ) |
const |
|
overridevirtual |
◆ op()
| double symcpp::Sine::op |
( |
double |
x | ) |
const |
|
overrideprivatevirtual |
◆ partial_derivative()
| std::unique_ptr< Expression > symcpp::Sine::partial_derivative |
( |
| ) |
const |
|
overrideprivatevirtual |
◆ print()
| std::ostream & symcpp::Sine::print |
( |
std::ostream & |
sink | ) |
const |
|
overrideprivatevirtual |
◆ simplify()
| std::unique_ptr< Expression > symcpp::Sine::simplify |
( |
| ) |
|
|
overridevirtual |
◆ UnaryOperator() [1/2]
| symcpp::UnaryOperator::UnaryOperator |
|
inline |
◆ UnaryOperator() [2/2]
| symcpp::UnaryOperator::UnaryOperator |
|
inline |
The documentation for this class was generated from the following files:


---
sort_order: 125
tei_id: rdx_b5j2m.p.idm1369248
annotation_count: 0
images:
small-thumbnail: http://readux.library.emory.edu/books/emory:b5j2m/pages/emory:p77mc/mini-thumbnail/
json: http://readux.library.emory.edu/books/emory:b5j2m/pages/emory:p77mc/info/
full: http://readux.library.emory.edu/books/emory:b5j2m/pages/emory:p77mc/fs/
page: http://readux.library.emory.edu/books/emory:b5j2m/pages/emory:p77mc/single-page/
thumbnail: http://readux.library.emory.edu/books/emory:b5j2m/pages/emory:p77mc/thumbnail/
title: Page 125
number: 125
---
{% raw %}CHAPTER XVIII.{% endraw %}
{% raw %}HOME AT DAWN.{% endraw %}
{% raw %}CONDITION IN CANADA.—EFFORTS IN BEHALF OF MY PEOPLE.—{% endraw %}
{% raw %}REV. MR. WILSON.—A CONVENTION OF BLACKS.—MANUAL-LABOUR{% endraw %}
{% raw %}SCHOOL.{% endraw %}
{% raw %}I did not find that our prosperity increased with{% endraw %}
{% raw %}our numbers. The mere delight the slaves{% endraw %}
{% raw %}took in their freedom, rendered them, at first, con¬{% endraw %}
{% raw %}tented with a lot far inferior to that to which they{% endraw %}
{% raw %}might have attained. Their ignorance often led{% endraw %}
{% raw %}them to make unprofitable bargains, and they would{% endraw %}
{% raw %}often hire wild land on short terms, and bind them¬{% endraw %}
{% raw %}selves to clear a certain number of acres. But by{% endraw %}
{% raw %}the time they were cleared and fitted for cultivation,{% endraw %}
{% raw %}and the lease was out, the landlords would take posses¬{% endraw %}
{% raw %}sion of the cleared land and raise a splendid crop on{% endraw %}
{% raw %}it. The tenants would, very likely, start again on{% endraw %}
{% raw %}just such another bargain, and be no better off at{% endraw %}
{% raw %}the end of ten years than at the beginning. Another{% endraw %}
{% raw %}way in which they lost the profits of their labour{% endraw %}
{% raw %}was by raising nothing but tobacco, the high price{% endraw %}
{% raw %}of which was very tempting, and the cultivation of{% endraw %}
{% raw %}which was a monopoly in their hands, as no white{% endraw %}
{% raw %}man understood it, or could compete with them at{% endraw %}
{% raw %}all. The consequence was, however, that the had{% endraw %}


Excited to announce our second special issue, now covering one of the most important plant diseases of vegetables and legumes: white mold, also known as Sclerotinia stem rot. Our February issue presents 11 articles including reviews and original research prepared by speakers of the 16th International Sclerotinia Workshop held in Uberlândia, Brazil, in 2017. Enjoy a free trial to all articles during the next months: https://link.springer.com/journal/40858/44/1


Hello there, my name is Alex Lew.
I am an urban planner and transportation planner by training with experience in public transit, multi-modal transportation, airport planning, and real-time passenger data analytics. My work stems from a life-long passion for transportation options.
I approach transportation planning with a multi-disciplinary toolbox that includes data visualization and analysis, geographic information systems (GIS), graphic design, as well as coding/programming. This site will soon be the home to various mapping projects, data visualizations, and other samples from my portfolio.
I am graduate of Harvard's Graduate School of Design and Columbia University.
You can email me at alexanderclew at gmail dot com or connect to me on LinkedIn.


Importurl
The importurl
task will download a file, and import
it's contents into the current project. The file can be in the
form of a standard Ant .xml project file, or a .jar/.zip file.
In the case of an .xml file, the file is downloaded, and imported as is. In this case, the file itself is the only thing downloaded (ie. no corresponding .properties files, or other build files are downloaded).
In the case of a .jar/.zip file, the file is downloaded and then
decompressed. After decompression, the file
build.xml
at the root level of the jar is imported
(the name of the imported file can be overridden with the
"resource" attribute). By importing a .jar/.zip file, one can
package additional resources along with the
build.xml
file. However, you must be careful how
you refer to these resources. The build.xml
file
must follow the same rules as any other file imported with the
import
task, in that references relative to the
build.xml
file must be made with the property:
ant.file.<projectname>
where
<projectname>
is the name of the
project being imported, as specified in the project
tag. Example:
<project name="common"> <dirname property="ant.dir.common" file="${ant.file.common}"/> <property file="${ant.dir.common}/build.properties"/> </project>
This task should be compatible with older versions of Ant, but has only been tested with Ant 1.6+. The underlying implementation is done using the Ivy dependency resolver software, and thus, it needs available to the same classloader that loads this task.
Parameters
| Attribute | Description | Required |
|---|---|---|
| org | The organization that publishes the script. | Yes. |
| module | The name of the module which is to be fetched. | Yes. |
| rev | The revision of the module to be fetched. | No. Defaults to "latest.integration". See the Ivy details for more information on the possible wildcards that can be used for this value. |
| type | The type of file to be downloaded |
No. Defaults to "jar". Can be any file extension. However,
unless the type is "xml", the file is assumed to be a
compressed file, expandable by Ant's expand
task (which is aliased to unjar or
unzip ).
|
| ivyConfUrl | The URL of an Ivy configuration file to use. We will use the default resolver in this file to find the requested resource. | No. Defaults to the IvyRepResolver. |
| ivyConfFile | The path of an Ivy configuration file to use. We will use the default resolver in this file to find the requested resource. | No. Defaults to the IvyRepResolver. |
| repositoryUrl | The URL base of the repository to use. This results in using Ivy's URLResolver to resolve the requested resource. | No. Defaults to the IvyRepResolver. |
| repositoryDir | The file base of the repository to use. This results in using Ivy's FileSystemResolver to resolve the requested resource. | No. Defaults to the IvyRepResolver. |
| artifactPattern | The pattern used to find artifacts in the repository. |
No. If "repositoryUrl" or "repositoryDir" are specified,
this defaults to the standard repository pattern:
"/[org]/[module]/[ext]s/[module]-[revision].[ext] ". Please
see Ivy documentation for more information on the contents
of this pattern.
|
| ivyPattern | The pattern used to find Ivy file for the artifact in the repository. |
No. If "repositoryUrl" or "repositoryDir" are specified,
this defaults to the standard repository pattern:
"/[org]/[module]/ivy-[revision].xml ". Please
see Ivy documentation for more information on the contents
of this pattern.
|
| resource | The name of the resource within a compressed file to import. | No. Defaults to "build.xml". |
Example
<project name="build" basedir="." default="build" xmlns:ac="antlib:net.sf.antcontrib"> <ac:antcontrib:importurl org="antcontrib" module="common" rev="3.2"/> </project>
would look for the file "antcontrib/common/jars/common-3.2.jar" in the IvyRep repository.
<ac:antcontrib:importurl org="antcontrib" module="common" rev="3.2" type="xml"/>
would look for the file "antcontrib/common/jars/common-3.2.xml" in the IvyRep repository.
<ac:antcontrib:importurl repositoryUrl="http://www.antcontrib.org/ivyrep" org="antcontrib" module="common" rev="3.2"/>
would look for the located at "http://www.antcontrib.org/ivyrep/antcontrib/common/jars/common-3.2.jar"
<ac:antcontrib:importurl ivyConfUrl="http://ivyrep.myorg.com/ivyconf.xml" org="antcontrib" module="common" rev="3.2"/>
would configure ivy using the ivy configuration file at the given ivyConfUrl.
The following build.xml
may be packaged into a .jar
with it's corresponding build.properties
file:
<project name="common"> <basedir property="ant.dir.common" file="${ant.file.common}"/> <property file="${ant.dir.common}/build.properties"/> </project>


Touristic is a company specialized in helping tourists to accomplish their objectives and intentions with ease. You may be busy on your schedule, with not enough time to go around looking for where to get food, transport, translators and lodging. In that case, you may contact us and we'll do our best to help you.


My research interests focus on machine learning and pattern recognition, computer vision, and visual reasoning. Possible applications include security and safety services, healthcare, and biomedical sciences.
| 09/2016 - Current | Tokyo Institute of Technology |
| Master of Engineering (Computer Science) | |
| Thesis: F2CSkeleton: A Tailor-made Approach for 3D Human Action Recognition | |
| Supervisor: Prof. Koichi Shinoda | |
| 08/2009 - 06/2016 | Hanoi University of Science and Technology (HUST) |
| Bachelor of Science (Electronics and Communication Engineering), top 2% | |
| Thesis: Automatic Face Recognition Using Local Images for Mobile Platforms | |
| Supervisors: A. Prof. Duc Minh Nguyen, Dr. Quang Hieu Dang |
| 09/2016 - 09/2018 | Japanese Government (MEXT) Scholarship Recipient |
| 06/2014 | Certificate of Merit for Excellent Undergraduate Students, HUST |
| 08/2013-06/2014 | Samsung Talented Program Scholarship 2013 |
| 07/2012 | Final Round, SmartPhone Apps Challenge |
| SmartPhone Apps Challenge in join HUST, Vietnam and CyberAgent, Japan |
| 08/2017 - 03/2018 | Research Intern |
| Yahoo! JAPAN Research, Yahoo Japan Corporation | |
| Deep Learning Based Addressee Recognition in Human-Human-Computer Interaction Systems | |
| 06/2014 - 08/2016 | Software Engineer |
| Samsung Vietnam Mobile R&D Centre (SVMC), Samsung Electronics Vietnam | |
| 01/2014 - 06/2014 | Intern |
| Samsung Vietnam Mobile R&D Centre (SVMC), Samsung Electronics Vietnam | |
| 11/2011 - 01/2014 | Research Assistant |
| Integrated Circuits and System Laboratory, HUST, Vietnam |


| 1197 | (A) | a calfe agaynes kynde caluede in thaire tempiłł |
| 1200 | (C) | A kalfe aȝeyne kynde . kaluede in þe temple |
| 1183 | (D) | A Calf al a-gayn kynd caluyd in the temple |
| 1160 | (E) | A caalf aȝens kynde . caluyd in þe temple |
| (Ex) | ---- no text ---- | |
| 1221 | (L) | a calf aȝen kynde calued in þe temple |
| (P) | ---- no text ---- | |
| 1168 | (U) | ¶ A calf ayeins kynde / clued in the temple |
| 261 | (V) | A calf agains kynde . calved in þe temple |


pgpool-II 4.0.3 Documentation
The Pgpool Global Development Group
Copyright
© 2003-2019 The Pgpool Global Development Group
Table of Contents
Preface
What is
Pgpool-II
?
A Brief History of
Pgpool-II
Conventions
Further Information
Restrictions
Bug Reporting Guidelines
I.
Tutorial
1.
Getting Started
2.
Watchdog
II.
Server Administration
3.
Installation of
Pgpool-II
4.
Server Setup and Operation
5.
Server Configuration
6.
Client Authentication
III.
Examples
7.
Configuration Examples
IV.
Reference
I.
Server commands
II.
PCP commands
III.
Other commands
IV.
SQL type commands
V.
pgpool_adm extension
V.
Appendixes
A.
Release Notes
Index
Next
Preface


save
her
from
cancer
Sign in
Nearest Centers
Self-Diagnosis
Survivor Stories
Articles
Types of Cancer
Please wait...
Sign in
Create an account
Just a few basic details
Name
Email
Password
Re-enter password
Create account