Sign up to get the lessons we've spent more than a decade learning straight to your inbox. 100% meat, no spam, ever.
Thanks! Now check your email, confirm your subscription, and off we go!


Greetings, my lord %residence_name%!
Your Wyvern awaits!
First, however, you must ride a
Strider of at least level %strider_level%
and have
%wyvern_fee% B-Grade Crystals
.


Before Change
if isinstance(resource, six.string_types):
resource = resource_lib.Resource(url=resource)
url = resource.url
if url in self._url_infos:
expected_sha256 = self._url_infos[url].checksum
download_path = self._get_final_dl_path(url, expected_sha256)
if not self._force_download and resource.exists_locally(download_path):
logging.info("URL %s already downloaded: reusing %s.",
url, download_path)
self._recorded_url_infos[url] = self._url_infos[url]
return promise.Promise.resolve(download_path)
// There is a slight difference between downloader and extractor here:
// the extractor manages its own temp directory, while the DownloadManager
// manages the temp directory of downloader.
download_dir_path = os.path.join(
self._download_dir,
"%s.tmp.%s" % (resource_lib.get_dl_dirname(url), uuid.uuid4().hex))
tf.io.gfile.makedirs(download_dir_path)
After Change
url = resource.url
// Compute the existing path if the file was previously downloaded
url_path = self._get_final_dl_path(
url, hashlib.sha256(url.encode("utf-8")).hexdigest())
existing_path = self._find_existing_path(url=url, url_path=url_path)
// If register checksums and file already downloaded, then:
// * Record the url_infos of the downloaded file


Curly and Floppy Twistytail, the Funny Piggie Boys
by Howard R. Garis
Chapter 16: “Flop Has a Tumble”
Additional Information
- Year Published: 1918
- Language: English
- Country of Origin: United States of America
- Source: Garis, H. R. (1918). Curly and Floppy Twistytail, the Funny Piggie Boys. New York, NY: A. L. Burt Co.
-
Readability:
- Flesch–Kincaid Level: 3.5
- Word Count: 1,343
- Genre: Fantasy
- ✎ Cite This
Downloads
“Come boys!” called Mamma Twistytail, the pig lady, one morning, to her two little boys, Curly and Flop. “Come, hurry, or you’ll be late for school!”
“Oh, I guess we have time enough,” spoke Flop, as he looked around for the football he and his brother had been playing with. “It’s early yet.”
“No, it isn’t,” answered his mamma. “Our clock is slow by your papa’s watch. Hurry now, I think I hear the bell ringing!”
“All right,” answered Curly. “Come along, Flop.” You see, he sometimes called his brother Flop, for short. So they kissed their little sister, Baby Pinky, good-bye, and went on to school.
As they hurried along, they met Jackie Bow Wow, the puppy dog boy, and Curly said:
“Oh, Jackie, where is my pencil you borrowed?”
“Here it is!” cried Jackie, turning a somersault, as he used to do in the circus, and he handed the pencil to Curly on the end of his nose—Jackie’s nose I mean.
“We chased after you last night, when we got out of school,” explained Curly, “and we had a dreadful adventure in the corn field with the alligator man,” and he told his doggie chum all about it, just as I wrote it for you in the story before this one.
So Jackie, and Curly and Flop hurried along together toward the school, when, all at once, they came to a nice, big, slanting cellar door, just right for sliding down, and on it was a sign which read:
“NO ONE MUST SLIDE DOWN
THIS CELLAR DOOR!”
“Now isn’t that queer,” said Jackie Bow Wow.
“It certainly is,” agreed Curly.
“I wonder why no one is allowed to slide down,” spoke Flop. “It’s a dandy door for sliding. I’ve a good notion to try it.”
“No, you mustn’t!” said his brother. “We are almost late for school now.”
“Oh, but I would just love to slide down it,” went on Flop, sort of hanging back, while his brother and Jackie went on ahead. “I wonder if a giant lives under that door, or a fairy?”
“Maybe that’s the reason no one must slide down it,” went on the little piggie boy. But no one answered him and, though he looked all around the cellar door, he could see no reason why he should not slide down it.
“Maybe it’s got slivers in, and they’d stick in me,” went on Flop, as he came closer to the door, but it was as nice and smooth as heart could wish.
“Well, this is certainly queer,” said Flop. “Here is the nicest sliding cellar door in all the world and no one is allowed to slide down it. I wonder who lives in the house,” and he looked up at the house to which the cellar door belonged, but it was all closed up, and shutters were over the windows.
“I guess no one is at home,” thought the little piggie boy.
“Say, aren’t you coming to school?” called back Jackie Bow Wow, for he and Curly were some distance down the street by this time.
“Yes, come on, or you’ll surely be late,” said Flop Ear’s brother.
“I’m coming!” cried Flop, but he thought he would take just one more look at the sliding door.
“I would like to have just one slide on it,” he said. “I believe I’ll try it.”
He looked ahead to where his brother and Jackie were and decided that if he did take one slide he could run and catch up to them, and not be late.
“Here goes;” said Flop, and he laid his books down on a clean stone.
Then he read the sign once more:
“NO ONE MUST SLIDE DOWN
THIS CELLAR DOOR!”
“I guess it’s only a joke,” decided Flop. “Now for one good slide and then I’ll go to school.”
So he went around to the side of the door, where there was a stone, and, by stepping on this, and giving a little jump, the piggie boy got to the top part of the sliding door, ready for a coast down.
Of course he had no sled on which to slide, but his trousers were good and thick, and he knew he could not wear a hole in the seat just this once. So he gathered his legs together under him, gave himself a little push and down the slanting door he went as nicely as an icicle in the middle of the Fourth of July.
“Wow! This is great!” cried Flop. “I guess the other fellows will wish they’d taken a slide. This is nifty!”
I don’t know myself what “nifty” means, but Flop said it, so I have to write it down.
Faster and faster he slid down the cellar door. It was a long one, and now he was half way to the bottom.
“Oh, won’t we have fun sliding after school!” the little piggie boy cried. “I don’t see why they put up that sign not to slide. This is the best cellar door I ever saw.”
Faster and faster he slid, laughing and shouting in glee, and he was almost at the bottom and he was wondering if he would have time for just one more coast before school, when all of a sudden:
“Crack! Slam! Smash! Ker-bunk!”
Right down through the cellar door fell poor Flop, and down the cellar steps into a tub of water. Into that he went ker-splash! For, you see, the cellar door had broken with him and let him right through, almost half way to China, it seemed.
Into the tub of water went Flop, getting wet all over. But he managed to crawl out after a while, and as he stood there, shivering, in the cellar, looking up at the broken door through which he had fallen, a nice little old rat lady came out of the house, and, looking at Flop, said:
“Dear me! What a terrible accident. Too bad! Did you hurt yourself, little piggie?”
“N-no-not much,” answered Flop. “But I—I’m all wet.”
“So I see,” said the rat lady. “But I thought there was a sign on the door, telling no one to slide down.”
“So there was,” admitted Flop, “but I didn’t see why it was there, so I slid anyhow.”
“I put the sign there because the door was so rotten that I knew the first one who slid down it would fall through,” said the rat lady. “And to think, some one did fall!”
“Yes’m,” said Flop, “I fell.”
“Well, don’t do it again,” said the rat lady, “and tomorrow I’ll have a new cellar door made. Now let me dry you off.”
So she kindly did, but Flop was late for school. And—well, I suppose it couldn’t be helped, even if he had to stay in. But on the next page, in case the mousetrap doesn’t catch the cheese by the tail and make it squeal, I’ll tell you about Mr. Twistytail’s lost hat.


welcome to trello app
this is where the magic happens
{% for board in boards %}
{{board.name}}
{% endfor %}
{% for board in boards %}
{{board.id}}: {{board.name}}
{% endfor %}


One of the major goals of Vc is to ease development of portable code, while achieving highest possible performance that requires target architecture specific instructions. This is possible through having just a single type use different implementations of the same API depending on the target architecture. Many of the details of the target architecture are often dependent on the compiler flags that were used. Also there can be subtle differences between the implementations that could lead to problems. This page aims to document all issues you might need to know about.
-march=\<target\>
flag. Take a look at the GCC manpage to find all possibilities for \<target\>
. If no SIMD instructions are enabled via compiler flags, Vc must fall back to the scalar implementation. /arch:SSE
and /arch:SSE2
flags. It is undocumented when (or whether at all) SSE3, SSSE3, SSE4a, SSE4.1, or SSE4.2 ISA extensions are used with these flags. For all x86 targets, the /arch:AVX
and /arch:AVX2
flags are supported.You must be aware of the fact that a binary that is built for a given SIMD hardware may not run on a processor that does not have these instructions. The executable will work fine as long as no such instruction is actually executed and only crash at the place where such an instruction is used. Thus it is better to check at application start whether the compiled in SIMD hardware is really supported on the executing CPU. This can be determined with the currentImplementationSupported function.
If you want to distribute a binary that runs correctly on many different systems you either must restrict it to the least common denominator (which often is SSE2), or you must compile the code several times, with the different target architecture compiler options. A simple way to combine the resulting executables would be via a wrapping script/executable that determines the correct executable to use. A more sophisticated option is the use of the ifunc attribute GCC provides. Other compilers might provide similar functionality.
It is guaranteed that:
Since SIMD is not part of the C/C++ language standards Vc abstracts more or less standardized compiler extensions. Sadly, not every issue can be transparently abstracted. Therefore this will be the place where differences are documented:
Vc_PASSING_VECTOR_BY_VALUE_IS_BROKEN
for such cases. Also the Vc vector types contain a composite typedef AsArg
which resolves to either const-ref or const-by-value. Thus, you can always use


⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ Ro: Suntem un server romanesc deschis pentru cei care doresc sa cunoasca persoane noi si sa discute cu ele.

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ En:
We are a Romanian server open to those who want to meet new people and talk to them.


Feedtype FT19 is currently allocated to FNMOC's Global Ocean Data Assimilation Experiment (GODAE) server. This feedtype also has the alias "NOGAPS". Additionally, the newly introduced alias "FNMOC", is available in LDM version 5.1.4 or greater. This latter alias was introduced as we became aware that FNMOC would be providing more than one data stream.
FNMOC currently provides two data streams via Unidata's Internet Data Distribution (IDD) network under the FNMOC feedtype: the Navy Operational Global Atmospheric Prediction System (NOGAPS) stream and the Coupled Ocean Atmosphere Mesoscale Prediction System (COAMPS) stream.
Below are example pqact.conf entries for NOGAPS/COAMPS model data:
Remember, with respect to the above examples, one or more tab characters must be used in certain places:# The below entry is for the one degree nogaps. FNMOC (^US058.{4}-GR1mdl\.0058_0240_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/nogaps/\2/\2\3/\1\2\3\4 # The below entry is for the one degree ww3. FNMOC (^US058.{4}-GR1mdl\.0110_0240_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/ww3/\2/\2\3/\1\2\3\4 # The below entry is for the one degree FAROP. FNMOC (^US058.{4}-GR1mdl\.0135_0240_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/farop/\2/\2\3/\1\2\3\4 # The below entry is for the 1/4 degree global ocean model. FNMOC (^US058.{4}-GR1mdl\.0078_0200_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/glb_ocn/\2/\2\3/\1\2\3\4 # The below entry is for the COAMPS Western Atlantic (w_atl) FNMOC (^US058.{4}-GR1mdl\.0063_0187_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/coamps/w_atl/\2/\2\3/\1\2\3\4 # The below entry is for the COAMPS Central America (cent_am) FNMOC (^US058.{4}-GR1mdl\.0027_0186_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/coamps/cent_am/\2/\2\3/\1\2\3\4 # The below entry is for the COAMPS Eastern Pacific (e_pac) FNMOC (^US058.{4}-GR1mdl\.0060_0188_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/coamps/e_pac/\2/\2\3/\1\2\3\4 # The below entry is for the COAMPS Europe (europe) FNMOC (^US058.{4}-GR1mdl\.0022_0158_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/coamps/europe/\2/\2\3/\1\2\3\4 # The below entry is for the WW3 Mediterranean (med) FNMOC (^US058.{4}-GR1mdl\.0111_0158_.{5}.{4})(.{4})(.{6})(.*) FILE -overwrite -close data/fnmoc/models/ww3_regional/med/\2/\2\3/\1\2\3\4


| Item ID | Description | Price | Qty | Amount |
|---|---|---|---|---|
| 24108054 | Dashlite - Conceptual App Dashboard - Regular License | $40.00 | 5 | $200.00 |
| 24108054 | 6 months premium support | $25.00 | 1 | $25.00 |
| 23604094 | Invest Management Dashboard - Regular License | $131.25 | 1 | $131.25 |
| 23604094 | 6 months premium support | $78.75 | 1 | $78.75 |
| Subtotal | $435.00 | |||
| Processing fee | $10.00 | |||
| TAX | $43.50 | |||
| Grand Total | $478.50 |


These Python Guidelines (style guide) empower the community to focus on the intent of the code and work together with a minimum of friction.
These Python Guidelines provides context to the developers who are new to the
codebase and wishes to make any real-world contribution with
org:creativecommons
and be a part of the organization and learn new things
with the organization.
All Python code must be formatted using Black, the uncompromising
Python code formatter. Each project should contain a pyproject.toml
configuration file that limits line length to 79 characters.
pyproject.toml
): GitHub Search · org:creativecommons
filename:pyproject.tomlAll Python code must be checked using flake8, a python tool that glues together pep8, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
Where flake8 conflicts with Black, the flake8 check should be skipped. For example, there are instances where black formats code that generates flake8 warning for Whitespace before ':' (E203).
.flake8
): GitHub Search · org:creativecommons
filename:.flake8All the imports in the Python code must be done via isort, a Python utility/library to sort imports alphabetically, and automatically separated into sections and by type. It provides a command line utility, Python library and plugins for various editors to quickly sort all your imports. It requires Python 3.6+ to run but supports formatting Python 2 code too.
There's a good isort
config which one should follow while contributing
in the Python projects of the creativecommons. These configurations should
be a part of pyproject.toml
labelled as [tools.isort]
pyproject.toml
): GitHub Search · org:creativecommons
filename:pyproject.tomlPlease work to minimize the number of development related technologies. This helps minimize the overhead of contributing to multiple projects. Most of our projects use either Pipenv, the Python Development Workflow for Humans, or docker-compose, a tool for defining and running multi-container Docker applications.
Thankfully, Black removes a lot of style work and worry. Where there is room for developer discretion, the following guides are excellent resources:


{include file="public/js" /}
{include file="public/header" /} {block name="column"} {include file="/public/column" /} {/block} {block name="content"} {/block} {include file="public/footer" /} {block name="script"} {/block}


We will contact you within the next 2-3 business days. If you have any other questions, call us at<PHONE_NUMBER>.


Concepts¶
In this section, we introduce several basic concepts and terms in the Big Data Processor (BDP) system.
User Roles¶
We categorized user roles into 1) users, 2) developers, and 3) administrators.
Plain users, including normal users and power users, can create Project, execute Tasks, and manage DataFile and Result records.
Developers, including task builders and task managers, can operate what a plain user can do. Additionally, a developer can construct Packages by defining Tasks and workflows.
Administrators can manage user privileges and do all the above mentioned actions. An administrator can see and edit all projects and packages with full privileges.
BDP provides basic user privileges for the above user roles. Please see the administration sections.
User Operation Scheme¶
A Project contains DataFiles and Results, while Task definitions and customized Pages are stored in a Package. Projects are created by plain users and Packages are created by developers.
A basic data cycle (highlighted in the blue color) may start by creating a project with selected packages. Users can then upload files to this project and these files become DataFile records. After tagging appropriate file tags to DataFile records, users can execute tasks that belong to the selected packages. Once after task parameters are set, the task is executing and all the provenance of a task is stored as a Result record.
Almost everything related to a task execution is recorded in a Result. You may see the Result records as histories. A Result records task status, parameters including input/output files, the runtime configurations, standard output/error, the task commands, the running time and all related information. After task executions, new DataFile records may be created in the Project and these DataFiles may be used as inputs of another task. In this way, a workflow can be executed manually or automatically.
In fact, a workflow-typed Task can be easily constructed by piping Tasks. We provide web interfaces that allow developers to construct workflows from Tasks by just mouse clicks and drag-and-drops. If users execute the workflow-typed Task, the Result records the progress and all sub-Tasks of the workflow as children Results.
Task Definition Language¶
To further ease the task definitions on web, we developed a new task definition language, the Workflow Playbook. The workflow playbook is a concise task configuration format for fast and portable workflow constructions. It is written in the YAML format and is inspired by the Ansible Playbook. With the templating concept, we can simplify the workflow definitions. It is desinged to be human-readable format.
Compared to the Common Workflow Language (CWL), workflow playbook is more concise and easy to write. The CWL is also written in the YAML format and provides detailed configurations to define tasks and workflows. We believe that the workflow definitions can be more concise through templating, instead of verbose configurations. Besides, we can easily write for-loops or do if-else conditions via templating while the CWL currently hasn’t supprted them.
We expect this concise format is easy enough for non-expert people to understand and write without learning additional domain-specific languages. In addition, this workflow playbook is seamlessly integrated on the Big Data Processor so that we can write the worklfow playbook directly on the web page.
See also
For further information of task definition language, please see the the introduction of Workflow Playbook.
Portable workflow execution¶
We recommended that developers apply the container techniques to make workflow protable. Each task in a workflow is encouraged to be executed through a container, such as Docker or Singularity container. A container carries its good runtime environemnts. The dependent libraries or the required tools can be pre-installed inside the container image, so that tasks are guaranteed to be executed successfully inside the well-defined container environment. This makes tasks portable.
When executing the containerized tasks, the defualt behaviors of BDP will mount two folders to the container.
The Project and Package folders on the host will be mounted to /project
and /package
inside the container.
With our Workflow Playbook, developers will NOT worry about the actural file locations, since these loactions are specified by users at the moment of task execution.
We also recommended that containers contain only the required environments such as libraries or tools, and the Package folder which contains task scripts are mounted right before task executions. BDP provides web interface to allow developers to edit task script files. In this way, developers can edit their scripts and execute them directly without updating container images.


Telkom Black Friday promotion – Win 500GB
by Bradley PriorTelkom is running a Black Friday competition where customers can win a projected prize of 500GB mobile data.
To enter the competition, Telkom customers must provide their details so that they can receive notifications about Telkom’s Black Friday deals when they launch.
Each entry into this competition will contribute 50MB towards the winner’s data pool, and Telkom believes this will culminate in about 500GB of data being given to the winner. At the time of publishing, the data prize pool was 240GB.
As part of the data prize, Telkom will also be providing the winner with a Huawei B525 4G router.
Telkom will also be offering the following prizes to runners-up:
- Second place – Huawei P20 Lite with Huawei 360 Panoramic VR camera
- Third prize – A pair of Beats headphones
To qualify for entry into the competition, participants must:
- Be a natural person.
- Be a South African citizen or permanent resident with a valid ID document or passport.
- Be 18 years or older.
- Be RICA compliant.
Entries will close at midnight on 29 November 2019, and winners will be drawn at random by an independent auditor.
Prize winners will be announced on Monday 9 December. To sign up to this deal, click here.


We are unable to save your bank account details.
Bank account details have been submitted to Innovate UK for use during the project Machine Learning In Robots (10294856)
Bank account details have been submitted to Innovate UK for use during the project Machine Learning In Robots (10294856)


Rev. 57 of mycheckpoint has been released and is available for download.
New and updated in this revision:
Remote host monitoring
It is now possible to monitor one host, while writing into another. Either or both could be remote hosts:
mycheckpoint --host=localhost --monitored-host=<IP_ADDRESS>
The above monitors the MySQL server on <IP_ADDRESS>, and writes down to localhost (to be queried later)
mycheckpoint --monitored-host=<IP_ADDRESS> --host=<IP_ADDRESS>
The above monitors the MySQL server on <IP_ADDRESS>, and writes down to <IP_ADDRESS>.
As result of the above addition, binary logging for monitoring statements are now enabled by default. The previous solution, in which binary logging were disabled by default and the same schema was utilized by different servers was far from being a clean solution. [Read more on Remote & multiple hosts monitoring]
Improved charting
The google charts reports have been improved significantly. Here's how:
Before on left (or above), After on right (or below)
And
Before on left (or above), After on right (or below)
Recap: the charts are not stored anywhere; they are being calculated and generated by SQL queries & views, based on the raw data. For example, to generate the above, I do:
SELECT innodb_estimated_log_mb_written_per_hour FROM sv_report_chart_sample\G *************************** 1. row *************************** innodb_estimated_log_mb_written_per_hour: http://chart.apis.google.com/chart?cht=lc&chs=400x200&chts=303030,12&chtt=Latest+24+hours:+Dec+8,+08:20++-++Dec+9,+08:20&chdl=innodb_estimated_log_mb_written_per_hour&chdlp=b&chco=ff8c00&chd=s:OQOTSPPQPSROUQMTRSQTPSURQTQQPSOSRTRRUTRRTSRRRSRSTRRQSURSUVRRXQTVRUTTVUTOYTXSYTTSYUSUTWUPRRPQSQRQTPPSPQMPPQOQMQPMOMOLQORNNPNRNNOPQOOMQQPNRNMNORQMSTQQPTPRUQVQTTVSURUVVVSSSVWQVUSTVSWSSUURWRVRTWdotpQNROPQRPQQMPLRO9PWNRPNNNPXUMLNNPQQPSONPLLNWXZTQROSQMOONQPLJNOOQQKMPSMMPLfPSSSRTUQSORSSRSPNRSQSQ&chxt=x,y&chxr=1,0,2708.0&chxl=0:|09:00||||13:00||||17:00||||21:00||||01:00||||05:00||||&chxs=0,505050,10&chg=4.17,25,1,3,2.78,0&chxp=0,2.78,6.95,11.12,15.29,19.46,23.63,27.80,31.97,36.14,40.31,44.48,48.65,52.82,56.99,61.16,65.33,69.50,73.67,77.84,82.01,86.18,90.35,94.52,98.69
If you thought I was going over the edge in Auto scaling, scaled SQL graphs concluded or SQL pie chart, allow me to assure you: generation of the above charts using SQL & views is SQL blasphemy. While cool, the Google Charts API does not do too much on its own, and expects the caller to do the math for putting in the grids, scales and labels (and though all of them are tightly related, they must all be explicitly specified). I'll write a later post on this.
Flexible charting
A new table, called charts_api, is introduced. It contains one row, which lists charting configuration.
SELECT * FROM charts_api; +-------------+--------------+----------------------------------------------------------------+------------------------------------+ | chart_width | chart_height | simple_encoding | service_url | +-------------+--------------+----------------------------------------------------------------+------------------------------------+ | 400 | 200 | ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | http://chart.apis.google.com/chart | +-------------+--------------+----------------------------------------------------------------+------------------------------------+
To change generated charts dimensions, simply update chart_width or chart_height.
To use other chart APIs, update service_url. I've tried out Eastwood Charts, a Java-based service, which implements the Google Charts API. There's still some stuff missing, such as the positioning of labels and grids; and it's slightly less polished (but configurable). But if you're concerned about sending requests to Google, it's a viable alternative.
So, drop the WAR file into your Tomcat / JBoss / other j2ee server, then follow http://<IP_ADDRESS>/eastwood/chart?...
Fix to questions vs. queries issues
mycheckpoint now correctly identifies whether to use questions or queries when analyzing DML queries. If you got some 570% for com_update out of total queries and wondered about it, it should now be resolved to normal values.
On upgrading your current installation
- Download & install via debian or python installers
- Issue mycheckpoint once with "deploy" as argument
- Done
Future plans
I'm working on 24x7 charting; minimal operating system monitoring; auto-detection and auto-deploy on version upgrade; and more.
Stay tuned!
comments powered by Disqus


| 1 |
Bults_2011 |
Perceived risk, anxiety, and behavioural responses of the general public during the early phase of the Influenza A (H1N1) pandemic in the Netherlands: results of three consecutive online surveys |
Bults, Marloes; Beaujean, Desirée JMA; de Zwart, Onno; Kok, Gerjo; van Empelen, Pepijn; van Steenbergen, Jim E; Richardus, Jan Hendrik; Voeten, Hélène ACM |
2011 |
2011-01-03 |
COMM-USE |
N |
PMC3091536 |
21199571.0 |
10.1186/1471-2458-11-2 |
4by61id3 |
0.792423 |
Knapp_2008 |
Atchison_2020, Bults_2014, Lee_D_2006 |
| 2 |
Liao_2010 |
The Influence of Social-Cognitive Factors on Personal Hygiene Practices to Protect Against Influenzas: Using Modelling to Compare Avian A/H5N1 and 2009 Pandemic A/H1N1 Influenzas in Hong Kong |
Liao, Qiuyan; Cowling, Benjamin J.; Lam, Wendy Wing Tak; Fielding, Richard |
2010 |
2010-10-15 |
NONCOMM |
N |
PMC3088805 |
20949342.0 |
10.1007/s12529-010-9123-8 |
g9cccwo1 |
0.745011 |
|
Liao_2010, Timpka_2014, Hickey_2014 |
| 3 |
Liao_2010 |
Situational Awareness and Health Protective Responses to Pandemic Influenza A (H1N1) in Hong Kong: A Cross-Sectional Study |
Liao, Qiuyan; Cowling, Benjamin; Lam, Wing Tak; Ng, Man Wai; Fielding, Richard |
2010 |
2010-10-12 |
COMM-USE |
N |
PMC2953514 |
20967280.0 |
10.1371/journal.pone.0013350 |
xwfptmmv |
0.692383 |
Knapp_2008 |
Timpka_2014, Hickey_2014, Liao_2010 |
| 4 |
Agüero_2011 |
Adoption of preventive measures during and after the 2009 influenza A (H1N1) virus pandemic peak in Spain |
Agüero, Fernando; Adell, Manel Nebot; Pérez Giménez, Anna; López Medina, María José; Garcia Continente, Xavier |
2011 |
2011-09-01 |
PMC |
N |
PMC7119352 |
21781983.0 |
10.1016/j.ypmed.2011.06.018 |
jw9dslgi |
0.671332 |
Knapp_2008 |
Migault_2019 |
| 5 |
Bults_2014 |
Q fever in the Netherlands: public perceptions and behavioral responses in three different epidemiological regions: a follow-up study |
Bults, Marloes; Beaujean, Desirée; Wijkmans, Clementine; Richardus, Jan Hendrik; Voeten, Hélène |
2014 |
2014-03-20 |
COMM-USE |
N |
PMC4108011 |
24645896.0 |
10.1186/1471-2458-14-263 |
ozkllp62 |
0.646490 |
Knapp_2008 |
|
| 6 |
Jeong_2011 |
Perception and Performance of Preventive Behaviors for the Pandemic Influenza in Hospital Employees and Outpatients |
Jeong, Hwee Soo; Lee, Dong Wook; Youn, Chang Ho; Lee, Mi Kyung; Lee, Seung Jun; Suh, Young Sung; Kim, Dae Hyun |
2011 |
2011-01-01 |
NONCOMM |
N |
PMC3017695 |
21155052.0 |
10.3349/ymj.2<IP_ADDRESS> |
eklwwu1j |
0.620812 |
Herman_2007 |
Choi_2016, Hickey_2014 |
| 7 |
de_Zwart_2007 |
Avian Influenza Risk Perception, Europe and Asia |
de Zwart, Onno; Veldhuijzen, Irene K.; Elam, Gillian; Aro, Arja R.; Abraham, Thomas; Bishop, George D.; Richardus, Jan Hendrik; Brug, Johannes |
2007 |
2007-02-23 |
PMC |
N |
PMC2725846 |
17479894.0 |
10.3201/eid1302.060303 |
3dpnmswf |
0.615102 |
|
|
| 8 |
Kuo_P_2011 |
Avian Influenza Risk Perception and Preventive Behavior among Traditional Market Workers and Shoppers in Taiwan: Practical Implications for Prevention |
Kuo, Pei-Chun; Huang, Jiun-Hau; Liu, Ming-Der |
2011 |
2011-09-02 |
COMM-USE |
N |
PMC3166308 |
21912667.0 |
10.1371/journal.pone.0024157 |
r3in76wm |
0.574408 |
Knapp_2008 |
Neupane_2012, Jang_2019 |
| 9 |
de_Zwart_2009 |
Perceived Threat, Risk Perception, and Efficacy Beliefs Related to SARS and Other (Emerging) Infectious Diseases: Results of an International Survey |
de Zwart, Onno; Veldhuijzen, Irene K.; Elam, Gillian; Aro, Arja R.; Abraham, Thomas; Bishop, George D.; Voeten, Hélène A. C. M.; Richardus, Jan Hendrik; Brug, Johannes |
2009 |
2009-01-06 |
NONCOMM |
N |
PMC2691522 |
19125335.0 |
10.1007/s12529-008-9008-2 |
b99y6n43 |
0.570212 |
|
Jiang_2009, Lau_J_2006, Mak_W_2006 |
| 10 |
Prateepko_2009 |
Patterns of perception toward influenza pandemic among the front-line responsible health personnel in southern Thailand: a Q methodology approach |
Prateepko, Tapanan; Chongsuvivatwong, Virasakdi |
2009 |
2009-05-28 |
COMM-USE |
N |
PMC2700101 |
19473550.0 |
10.1186/1471-2458-9-161 |
yw8rzrb7 |
0.561751 |
|
Hickey_2014, Lam_K_2013 |
| 11 |
Kim_S_2014 |
Community-Based Risk Communication Survey: Risk Prevention Behaviors in Communities during the H1N1 crisis, 2010 |
Kim, Soo Jeong; Han, Jin A.; Lee, Tae-Yong; Hwang, Tae-Yoon; Kwon, Keun-Sang; Park, Ki Soo; Lee, Kyung Jong; Kim, Moon Shik; Lee, Soon Young |
2014 |
2014-01-10 |
None |
N |
PMC4064644 |
24955307.0 |
10.1016/j.phrp.2013.12.001 |
2prs48ae |
0.561525 |
Yap_J_2010, Rebmann_2012, Knapp_2008, Moghanibashi-Mansourieh_2020 |
Hickey_2014, Lee_S_2016, Wong_2010, Ibuka_2010 |
| 12 |
de_Zwart_2010 |
Monitoring of risk perceptions and correlates of precautionary behaviour related to human avian influenza during 2006 - 2007 in the Netherlands: results of seven consecutive surveys |
de Zwart, Onno; Veldhuijzen, Irene K; Richardus, Jan Hendrik; Brug, Johannes |
2010 |
2010-05-12 |
COMM-USE |
N |
PMC2885389 |
20462419.0 |
10.1186/1471-2334-10-114 |
ajnyt1km |
0.531902 |
Knapp_2008 |
|
| 13 |
Kok_G_2010 |
Behavioural intentions in response to an influenza pandemic |
Kok, Gerjo; Jonkers, Ruud; Gelissen, Roger; Meertens, Ree; Schaalma, Herman; de Zwart, Onno |
2010 |
2010-03-30 |
COMM-USE |
N |
PMC2861057 |
20353568.0 |
10.1186/1471-2458-10-174 |
tmawi4mk |
0.530307 |
|
Timpka_2014, Morrison_2009, Liao_2010 |
| 14 |
Sengupta_2014 |
Information sources and adoption of vaccine during pandemics |
Sengupta, Sanjit; Wang, Hui-ming Deanna |
2014 |
2014-10-28 |
PMC |
N |
PMC7098009 |
|
10.1108/ijphm-01-2014-0002 |
0m1nopj6 |
0.530185 |
|
Griffiths_2010, Hickey_2014 |
| 15 |
Latiff_2012 |
Pandemic Influenza A (H1N1) and Its Prevention: A Cross Sectional Study on Patients’ Knowledge, Attitude and Practice among Patients Attending Primary Health Care Clinic in Kuala Lumpur, Malaysia |
Latiff, Latiffah A; Parhizkar, Saadat; Zainuddin, Huda; Chun, Goh M; Ramli, Mohammad Ali A Rahiman Nur Liyana N; Yun, Kerk L |
2012 |
2012-03-01 |
COMM-USE |
N |
PMC4777058 |
22980156.0 |
10.5539/gjhs.v4n2p95 |
rz9nh1q7 |
0.493235 |
Knapp_2008 |
|
| 16 |
Wong_2010 |
Behavioral responses to the influenza A(H1N1) outbreak in Malaysia |
Wong, Li Ping; Sam, I-Ching |
2010 |
2010-08-01 |
PMC |
N |
PMC7088090 |
20680674.0 |
10.1007/s10865-010-9283-7 |
uqm7ndjt |
0.462529 |
Knapp_2008, Reyes-Velázquez_2015 |
Hickey_2014, Jang_2019, Wong_2010 |
| 17 |
Park_2010 |
Perceptions and behaviors related to hand hygiene for the prevention of H1N1 influenza transmission among Korean university students during the peak pandemic period |
Park, Jae-Hyun; Cheong, Hae-Kwan; Son, Dae-Yong; Kim, Seon-Ung; Ha, Chang-Min |
2010 |
2010-07-28 |
COMM-USE |
N |
PMC2922213 |
20663229.0 |
10.1186/1471-2334-10-222 |
pad3x324 |
0.460307 |
Knapp_2008, DeWitt_2020 |
Cruz_2016, Jang_2019, Hickey_2014 |
| 18 |
Ibuka_2010 |
The dynamics of risk perceptions and precautionary behavior in response to 2009 (H1N1) pandemic influenza |
Ibuka, Yoko; Chapman, Gretchen B; Meyers, Lauren A; Li, Meng; Galvani, Alison P |
2010 |
2010-10-14 |
None |
N |
PMC2964717 |
20946662.0 |
10.1186/1471-2334-10-296 |
uzgfx0fc |
0.454430 |
Knapp_2008 |
Hickey_2014, Wong_2010, Timpka_2014 |
| 19 |
Xu_J_2015 |
People at Risk of Influenza Pandemics: The Evolution of Perception and Behavior |
Xu, Jianhua; Peng, Zongchao |
2015 |
2015-12-14 |
COMM-USE |
N |
PMC4682843 |
26658371.0 |
10.1371/journal.pone.0144868 |
pl2d1yc0 |
0.440527 |
|
Hickey_2014, Ibuka_2010, Wong_2010, Lam_K_2013 |
| 20 |
Xu_J_2011 |
Predictors of symptoms of posttraumatic stress in Chinese university students during the 2009 H1N1 influenza pandemic |
Xu, Jiahong; Zheng, Yayuan; Wang, Mingmin; Zhao, Jiangmin; Zhan, Qing; Fu, Mingxu; Wang, Qianyi; Xiao, Junjie; Cheng, Yan |
2011 |
2011-07-01 |
PMC |
N |
PMC3539574 |
21709644.0 |
10.12659/msm.881836 |
mcjv7ecp |
0.422703 |
|
|
| 21 |
Masser_2012 |
Beliefs underlying blood donors’ intentions to donate during two phases of an avian influenza outbreak |
Masser, Barbara M.; White, Katherine M.; Hamilton, Kyra; McKimmie, Blake M. |
2012 |
2012-02-29 |
PMC |
N |
PMC7106419 |
22142514.0 |
10.1016/j.transci.2011.11.001 |
8jzrku20 |
0.417708 |
|
Timpka_2014 |
| 22 |
Goulia_2010 |
General hospital staff worries, perceived sufficiency of information and associated psychological distress during the A/H1N1 influenza pandemic |
Goulia, Panagiota; Mantas, Christos; Dimitroula, Danai; Mantis, Dimitrios; Hyphantis, Thomas |
2010 |
2010-11-09 |
COMM-USE |
N |
PMC2990753 |
21062471.0 |
10.1186/1471-2334-10-322 |
vhrikgpi |
0.386189 |
Knapp_2008 |
|
| 23 |
Wong_2010 |
Temporal changes in psychobehavioral responses during the 2009 H1N1 influenza pandemic |
Wong, Li Ping; Sam, I-Ching |
2010 |
2010-07-31 |
PMC |
N |
PMC7125894 |
20403375.0 |
10.1016/j.ypmed.2010.04.010 |
va2rnnif |
0.372261 |
|
Wong_2010, Lee_D_2006 |
| 24 |
Ro_J_2017 |
Worry experienced during the 2015 Middle East Respiratory Syndrome (MERS) pandemic in Korea |
Ro, Jun-Soo; Lee, Jin-Seok; Kang, Sung-Chan; Jung, Hye-Min |
2017 |
2017-03-08 |
COMM-USE |
N |
PMC5342218 |
28273131.0 |
10.1371/journal.pone.0173234 |
i5p3vbfr |
0.360401 |
Reyes-Velázquez_2015 |
|
| 25 |
Voeten_2009 |
Sources of Information and Health Beliefs Related to SARS and Avian Influenza among Chinese Communities in the United Kingdom and The Netherlands, Compared to the General Population in these Countries |
Voeten, Helene A. C. M.; de Zwart, Onno; Veldhuijzen, Irene K.; Yuen, Cicely; Jiang, Xinyi; Elam, Gillian; Abraham, Thomas; Brug, Johannes |
2009 |
2009-01-29 |
PMC |
N |
PMC7090907 |
19184453.0 |
10.1007/s12529-008-9006-4 |
y176cze2 |
0.355702 |
Knapp_2008 |
Della_Polla_2020, Neupane_2012 |
| 26 |
Heo_J_2013 |
Risk Perception, Preventive Behaviors, and Vaccination Coverage in the Korean Population during the 2009–2010 Pandemic Influenza A (H1N1): Comparison between High-Risk Group and Non–High-Risk Group |
Heo, Jung Yeon; Chang, Soung Hoon; Go, Min Jung; Kim, Young Mee; Gu, Sun Hye; Chun, Byung Chul |
2013 |
2013-05-17 |
COMM-USE |
N |
PMC3656839 |
23691175.0 |
10.1371/journal.pone.0064230 |
ii50gly3 |
0.354121 |
To_K_2010 |
Kee_S_2007, Hickey_2014, To_K_2010 |
| 27 |
Kim_J_2011 |
Knowledge of Avian Influenza (H5N1) among Poultry Workers, Hong Kong, China |
Kim, Jean H.; Lo, Fung Kuk; Cheuk, Ka Kin; Kwong, Ming Sum; Goggins, William B.; Cai, Yan Shan; Lee, Shui Shan; Griffiths, Sian |
2011 |
2011-12-23 |
PMC |
N |
PMC3311183 |
22172127.0 |
10.3201/eid1712.110321 |
8m7spnxj |
0.345868 |
|
|
| 28 |
Liao_2014 |
Anxiety, worry and cognitive risk estimate in relation to protective behaviors during the 2009 influenza A/H1N1 pandemic in Hong Kong: ten cross-sectional surveys |
Liao, Qiuyan; Cowling, Benjamin J; Lam, Wendy WT; Ng, Diane MW; Fielding, Richard |
2014 |
2014-03-27 |
COMM-USE |
N |
PMC3986671 |
24674239.0 |
10.1186/1471-2334-14-169 |
jtvf257r |
0.345112 |
Knapp_2008 |
Liao_2010, Timpka_2014, Lee_D_2006 |
| 29 |
Wong_2010 |
Knowledge and Attitudes in Regard to Pandemic Influenza A(H1N1) in a Multiethnic Community of Malaysia |
Wong, Li Ping; Sam, I-Ching |
2010 |
2010-09-11 |
PMC |
N |
PMC7090469 |
20835855.0 |
10.1007/s12529-010-9114-9 |
p7hzoz5d |
0.344656 |
Knapp_2008 |
Hickey_2014, Al-Mohrej_2016 |
| 30 |
Saadatian-Elahi_2010 |
Perception of epidemic's related anxiety in the General French Population: a cross-sectional study in the Rhône-Alpes region |
Saadatian-Elahi, Mitra; Facy, Françoise; Del Signore, Corinne; Vanhems, Philippe |
2010 |
2010-04-13 |
COMM-USE |
N |
PMC2874530 |
20385030.0 |
10.1186/1471-2458-10-191 |
lluqlzlg |
0.324925 |
|
Lau_J_2006, Aldrees_2017, Lee_D_2006 |
| 31 |
Hickey_2014 |
Knowledge about pandemic influenza preparedness among vulnerable migrants in Thailand |
Hickey, Jason E.; Gagnon, Anita J.; Jitthai, Nigoon |
2014 |
2014-09-08 |
PMC |
N |
PMC4745616 |
25204452.0 |
10.1093/heapro/dau074 |
truei5y2 |
0.323568 |
|
|
| 32 |
Yap_J_2010 |
Knowledge, attitudes and practices towards pandemic influenza among cases, close contacts, and healthcare workers in tropical Singapore: a cross-sectional survey |
Yap, Jonathan; Lee, Vernon J; Yau, Teng Yan; Ng, Tze Pin; Tor, Phern-Chern |
2010 |
2010-07-28 |
COMM-USE |
N |
PMC2916908 |
20667076.0 |
10.1186/1471-2458-10-442 |
sy3ncwgw |
0.323397 |
Moghanibashi-Mansourieh_2020 |
Hickey_2014 |
| 33 |
Vartti_2009 |
SARS Knowledge, Perceptions, and Behaviors: a Comparison between Finns and the Dutch during the SARS Outbreak in 2003 |
Vartti, A.-M.; Oenema, A.; Schreck, M.; Uutela, A.; de Zwart, O.; Brug, J.; Aro, A. R. |
2009 |
2009-01-31 |
PMC |
N |
PMC7091200 |
19184625.0 |
10.1007/s12529-008-9004-6 |
zi0flem8 |
0.321099 |
Knapp_2008 |
Jiang_2009, Lau_J_2006 |
| 34 |
Griffiths_2010 |
Influence of country of study on student responsiveness to the H1N1 pandemic |
Griffiths, S.M.; Wong, A.H.; Kim, J.H.; Yung, T.K.C.; Lau, J.T.F. |
2010 |
2010-08-31 |
PMC |
N |
PMC7118757 |
20510428.0 |
10.1016/j.puhe.2010.03.027 |
jg608vms |
0.318782 |
Knapp_2008, DeWitt_2020 |
Migault_2019, Al-Mohrej_2017, Hickey_2014 |
| 35 |
Lim_J_2020 |
Population anxiety and positive behaviour change during the COVID-19 epidemic: Cross-sectional surveys in Singapore, China and Italy |
Jane M Lim; Zaw Myo Tun; Vishakha Kumar; Sharon Quaye; Vittoria Offeddu; Alex R Cook; May Oo Lwin; Shaohai Jiang; Clarence C Tam |
2020 |
2020-04-17 |
BioRxiv |
Y |
|
|
10.1101/2<IP_ADDRESS>65862 |
7yucn30u |
0.318354 |
|
|
| 36 |
Neupane_2012 |
Knowledge, attitudes and practices related to avian influenza among poultry workers in Nepal: a cross sectional study |
Neupane, Dinesh; Khanal, Vishnu; Ghimire, Kamal; Aro, Arja R; Leppin, Anja |
2012 |
2012-03-30 |
COMM-USE |
N |
PMC3342178 |
22458535.0 |
10.1186/1471-2334-12-76 |
fc05u8mx |
0.305299 |
Knapp_2008 |
Osbjer_2015, Hickey_2014 |


Simpson finishes strong to lead RSM Classic
(Reuters) - American Webb Simpson birdied his last three holes to take a one-stroke lead in the first round of the RSM Classic in Georgia on Thursday.
Simpson’s lone bogey came on his second hole but he recovered to finish with eight birdies for a seven-under-par 65 on a sunny day at the Plantation course on Sea Island, one of two courses used in the PGA Tour’s final event of the year.
American Cameron Tringale, South Korean Kyoung-hoon Lee and Australian Rhein Gibson were locked in a three-way tie for second at six under par and nine players were tied for fifth.
In-form American Brendon Todd, who is gunning for his third PGA Tour victory in three weeks, produced another solid round, carding a four-under-par 66 at the more challenging par-70 Seaside course.
Simpson, who lost the event in a playoff in 2011 before winning the U.S. Open the following year, said the key to overcoming his slow start was focusing on his own game.
“Playing with guys who are making birdies, it’s hard to stay patient. But I was able to do that,” he said.
Simpson, 34, is coming off his longest break from the game since he turned pro. The last event he competed in was the Shriners Hospitals for Children Open in Las Vegas in early October.
The world number 12 will look to sharpen his game ahead of two tournaments in December, the Hero World Challenge in the Bahamas and the Presidents Cup at Royal Melbourne in Australia.


Das Keyboard Q REST API Documentation
The developer Q API is a JSON REST API that allows control of the RGB settings of Q devices.
This document explains how to use the Q API. Two options are available: sending requests to the Q cloud service https://q.daskeyboard.com/ or directly to the desktop application http://localhost:#port/… on the developer’s machine.
The Q cloud service and the desktop software use similar endpoints. Note that the Q desktop HTTP server port number is 27301
.
Here are some useful links to get started smoothly:
Authentication: Oauth2 (Cloud only)
The Das Keyboard Q Cloud service uses Oauth2 authentication, so in order to perform a request, you will need to send a token, which will require the use of your client credentials. Indeed, once a user account is created on the Q Cloud service, a client is automatically generated with the name “User_X” where X is a unique id associated to the user.
For example, if Bob signs up to the Q Cloud and has the id 87, a client will be generated for him with the name “User_87”.
To get OAuth tokens, please read the Q Authentication documentation.
Note about data format
Responses sent by the server are in JSON format. However, the Q cloud service accepts both “application/json” and “application/x-www-form-urlencoded”:
curl -X POST -H "Content-Type: application/json" -d '{"PARAM": "VALUE"}' https://q.daskeyboard.com/oauth/1.4/ENDPOINT
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d "PARAM=VALUE" https://q.daskeyboard.com/oauth/1.4/ENDPOINT
Getting the list of authorized clients
To send signals to your Q Cloud account, you need to authorize clients (e.g. Twitter, Zappier). The following command gives the list of authorized clients.
Parameters required: ACCESS TOKEN.
curl -X GET -H 'Authorization: Bearer ACCESS_TOKEN' https://q.daskeyboard.com/api/1.0/users/authorized_clients
Result format:
[
{
"name": "CLIENT_NAME"
},
{
"name":"User_1055"
},
{
"name":"IFTTT"
},
{
"name":"Desktop App"
}
]
Revoking a client
To revoke a client, only its name is needed:
Parameters required: ACCESS TOKEN, CLIENT_NAME.
curl -X POST -H 'Authorization: Bearer ACCESS_TOKEN' -H 'Content-Type: application/json' -d '{"name": "CLIENT_NAME"}' https://q.daskeyboard.com/api/1.0/users/revoke_client
If the operation succeeds, you should receive a 200 response.
Endpoints (Cloud only)
Parameter required: ACCESS TOKEN.
Devices Definitions
Returns the list of available devices (JSON Array).
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/device_definitions
Result format:
[
{
"name": "name of the product (string)",
"vid": "vid of the product (string)",
"pid": "pid of the product (string)",
"modelNumber": "number of the model (string)",
"description": "description (string)",
"zones": [
{
"id": "id (string)",
"description": "description (string)"
},
{
"id": "id (string)",
"description": "description (string)"
},
...
],
"name":"Das Keyboard 5Q",
"vid":"24F0",
"pid":"DK5QPID",
"modelNumber":"DKPK5Q0P0GZS0DEX",
"description":"DK 5Q - The cloud connected keyboard by Das Keyboard",
"languageLayout":
{
"language":"Spanish",
"location":"Spain",
"languageId":3082,
"languageTag":"es-ES",
"zones":[
{
"ledIds":[25],
"id":25,
"code":"KEY_ESCAPE",
"description":"Escape"
},
{
"ledIds":[27],
"id":27,
"code":"KEY_F1",
"description":"F1"
},
]
}
}
]
Devices
Returns the list of devices linked to your account (JSON Array).
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/devices
Result format:
[
{
"id": "id of the device (int)",
"userId": "id of the user (int)",
"pid": "pid of the product (string)",
"firmwareVersion": "version of the firmware (string)",
"vid": "vid of the product (string)",
"description": "description (string)",
"zones": [
{
"id": "id (string)",
"description": "description (string)"
},
{
"id": "id (string)",
"description": "description (string)"
},
...
]
},
{
"id":1418,
"userId":1055,
"pid":"DK5QPID",
"firmwareVersion":"<IP_ADDRESS>",
"vid":"24F0",
"description":"DK 5Q - The cloud connected keyboard by Das Keyboard",
"uuid":"uuid to be set RtLWkEOPxm...",
"versionNumber":1,
"updateOrigin":null,
"isDeleted":false,
"createdAt":1520377021863,
"updatedAt":1520377021863
}
]
Colors
Returns a list of predefined colors (JSON Array).
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/colors
Result format:
[
{
"code": "hexadecimal code of the color (string beginning by the character '#' and followed by 3 hexadecimal digits)",
"name": "name of the color (string)"
},
{
"code":"#F00",
"name":"Red"
},
{
"code":"#0F0",
"name":"Green"
},
{
"code":"#00F",
"name":"Blue"
}
]
Zones
Returns the list of a device’s zones (JSON Array).
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/DK5QPID/zones
The GET parameter DK5QPID must correspond to an existing device’s pid. Each JSON object will have the structure:
Result format:
[
{
"id": "id of the zone (string beginning by 'KEY_')",
"name": "name of the zone (string)"
},
{
"name":"Escape",
"id":25
},
{
"name":"F1",
"id":27
},
{
"name":"F3",
"id":29
},
{
"name":"C",
"id":125
},
{
"name":"V",
"id":126
},
{
"name":"Left Ctrl",
"id":145
}
...
]
Effects
Returns the list of a available effects for a device (JSON Array).
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/DK5QPID/effects
The GET parameter DK5QPID must correspond to an existing device’s pid.
Result format:
[
{
"code": "code of the effect (string)",
"name": "name of the zone (string)"
},
{
"code":"SET_COLOR",
"label":"set color"
},
{
"code":"BLINK",
"label":"Blink"
},
{
"code":"RIPPLE",
"label":"Ripple"
},
...
]
Signals
Creating a signal (Cloud and local)
The Das Keyboard 5Q device RGB keys can be controlled via signals.
Quick example of sending a signal on the key Q (DK5Q) using the XY coordinates:
- via the Cloud:
curl -H 'Content-Type: application/json' -H 'Authorization: Bearer ACCESS_TOKEN' -X POST https://q.daskeyboard.com/api/1.0/signals -d '{"name": "Apple Stock increase", "pid": "DK5QPID", "zoneId": "2,2", "color": "#008000"}'
- via local API:
curl -H 'Content-Type: application/json' -X POST http://localhost:$PORT/api/1.0/signals -d '{"name": "Apple Stock increase", "pid": "DK5QPID", "zoneId": "2,2", "color": "#008000"}'
Understanding zoneId
The zoneId is the id of the zone to light up. There are three coordinates systems available:
-
Coordinate system XY
-
Coordinate system zone code: KEY_{name-of-the-key}
-
Coordinate system linear
It is recommanded to use the coordinate system XY because it is compatible with every layouts.
For example, to send a signal on the key Q (US_layout):
-
2,2
-
KEY_Q
-
74
To send a signal on the key Q (105 keys layout):
-
3,3 (different coordinates than with the 104 keys)
-
KEY_Q
-
99
NB: “|-F” = left pipe and “|-R” = right pipe
Example of more detailed signal
- Via the Cloud:
curl -H 'Content-Type: application/json' -H 'Authorization: Bearer ACCESS_TOKEN' -X POST https://q.daskeyboard.com/api/1.0/signals -d '{"name": "Apple Stock increase", "pid": "DK5QPID", "zoneId": "2,2", "message": "It worked", "effect": "BLINK", "color": "#008000", "action": "open:chrome", "isRead": true, "isArchived": true, "isMuted": true}'
- Via local API:
curl -H 'Content-Type: application/json' -X POST http://localhost:$PORT/api/1.0/signals -d '{"name": "Apple Stock increase", "pid": "DK5QPID", "zoneId": "2,2", "message": "It worked", "effect": "BLINK", "color": "#008000", "isRead": true, "isArchived": true, "isMuted": true}'
For more examples, please check out the API examples.
Resource representations:
name: string - name of Signal, e.g. “Apple Stock increase”.
pid: string - pid of the device, e.g. “DK5QPID”.
zoneId: string - id of the zone, e.g. “KEY_Q”, “x,y”, “74”. cf Understanding zoneId
color: string which has to begin by the character ‘#’ and be followed by 3 or 6 hexadecimal digits - color of the Signal, e.g. “#008000”.
Optional fields:
message: string - message of Signal (default: empty string “”), e.g. “Lucky you! Apple stock is greater than $500”.
effect: string - effect of the Signal (default: “SET_COLOR”), e.g. “BLINK”.
action: string which is formatted “actionType:value” - action that can be triggered once the Signal has been received (the actionType is either “ur” or “open”)
isRead: boolean - indicates if the Signal has been read (default: false), e.g. true.
isArchived: boolean - indicates if the Signal has been archived (default: false), e.g. true.
isMuted: boolean - indicates if the Signal has been muted (default: false), e.g. true.
The response is a JSON object containing the id of the signal created.
Getting the signals (Cloud only)
Parameter required: ACCESS TOKEN.
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/signals
In order to obtain a list of Signals created after a certain time: Parameter required: ACCESS TOKEN, EPOCH_TIME.
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/signals/after/EPOCH_TIME
GET parameters can also be added:
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X GET https://q.daskeyboard.com/api/1.0/signals?pid=DK5QPID&page=0&size=4&sort=createdAt,DESC
Result format:
{
"content":
[
{
"id": "id of the Signal (long)",
"userId": "id of the user (integer)",
"pid": "pid of the device (string)",
"zoneId": "id of the zone (string)",
"name": "name of the Signal (string)",
"color": "color of the Signal (string beginning by the character '#' and followed by 3 hexadecimal digits)",
"effect": "effect of the Signal (string)",
"action": "action linked to the Signal (string)",
"isRead": "indicates if the Signal has been read (boolean)",
"isMuted": "indicates if the Signal has been muted (boolean)",
"isArchived": "indicates if the Signal has been archived (boolean)",
"clientName": "name of the Client who created the Signal (string)",
"message": "message of the Signal (string)",
"readAt": "time at which the Signal has been read (long: epoch time, can be null)",
"createdAt": "time at which the Signal has been created (long: epoch time)",
"updatedAt": "time at which the Signal has been updated (long: epoch time)"
},
{
"id":526930,
"zoneId":"75",
"pid":"DK5QPID",
"userId":1055,
"name":"Today's forecast",
"message":"Hope it's not too cold today!",
"effect":"BLINK",
"color":"#20DB0D",
"isRead":true,
"isMuted":false,
"isArchived":false,
"clientName":"IFTTT",
"readAt":null,
"action":null,
"createdAt":1520438417719,
"updatedAt":1520457724435
},
{
"id":527432,
"zoneId":"99",
"pid":"DK5QPID",
"userId":1055,
"name":"Apple stodbf7c8ee834d382ddc1fdb490b0a17c0ease",
"message":null,
"effect":"SET_COLOR",
"color":"#0F0",
"isRead":true,
"isMuted":false,
"isArchived":true,
"clientName":"NOTICE: zoneId automatically converted from KEY_A to 99. 1055<EMAIL_ADDRESS>null",
"readAt":null,
"action":null,
"createdAt":1520456948981,
"updatedAt":1520457728103
},
...
],
"size":50,
"sort":"createdAt: ASC,zoneId: ASC",
"hasNextPage":false,
"page":0,
"totalElements":41,
"totalPages":1
}
Updating a Signal status (Cloud only)
Q signal statuses work very much like an email from Gmail. It can be read or
unread, archived and muted. One cannot change the content of an email.
Only the signal fields isMuted
, isRead
and isArchived
can be updated.
isRead
: a user has read the signalisArchived
: archived signals are not visible but still present in the list of all signalsisMuted
: unused
Example: Updating a signal to ‘isRead’ = true status
curl -H 'Content-Type: application/json' -H 'Authorization: Bearer ACCESS_TOKEN' -X PATCH https://q.daskeyboard.com/api/1.0/signals/ID/status -d '{"isRead": true, "isArchived": false}'
The GET parameter ID must correspond to an existing signal’s id.
Deleting a Signal (Cloud only)
curl -H 'Authorization: Bearer ACCESS_TOKEN' -X DELETE https://q.daskeyboard.com/api/1.0/signals/ID
The GET parameter ID must correspond to an existing signal’s id.
Getting color of zone id
When a signal is displayed on a zone id (i.e. one or more LEDs), the following end point will return its color:
Endpoint:
GET https://q.daskeyboard.com/api/1.0/signals/{pid}/{zoneId}
Example:
Get color of zone id 83 for device 5Q keyboard:
curl -H 'Authorization: Bearer ACCESS_TOKEN' https://q.daskeyboard.com/api/1.0/signals/DK5QPID/83
Result format:
{
"color": "#F00"
}
Getting device shadow
A device shadow is a set of most recent signals per zone, i.e. what is currently displayed on the device.
Example:
Get the shadow of DK5QPID.
curl -H 'Authorization: Bearer ACCESS_TOKEN' https://q.daskeyboard.com/api/1.0/signals/shadows/DK5QPID```
Result format:
```json
{
"content":
[
{
"id":524561,
"zoneId":"78",
"pid":"DK5QPID",
"userId":6,
"name":"signal name",
"message":"messagebody",
"effect":"BLINK",
"color":"#00aced",
"isRead":false,
"isMuted":false,
"isArchived":false,
"clientName":"IFTTT",
"readAt":null,
"action":null,
"createdAt":1520349790354,
"updatedAt":1520349790356
},
...
],
"size":7,
"sort":"",
"hasNextPage":false,
"page":0,
"totalElements":7,
"totalPages":1
}


Properties
Private escapeEventListener
escapeEventListener: string
Private groupsListElement
groupsListElement: HTMLElement
Private inputElement
inputElement: HTMLInputElement
Private inputSubscribers
inputSubscribers: Array<Function> = []
Private menuElement
menuElement: HTMLElement
Private openSubscribers
openSubscribers: Array<Function> = []
Private runSubscribers
runSubscribers: Array<Function> = []
Private selectSubscribers
selectSubscribers: Array<Function> = []


Larry David: Curb Your Enthusiasm (1999, TV-MA)
Starring Larry David as himself
Directed by Robert Weide
There's a moment in Larry David: Curb Your Enthusiasm that I became sure that I was dealing with a mockumentary. Larry is in the offices at HBO and, over Larry's shoulder, there was a poster for Lenny Bruce: Swear to tell the Truth. Seeing as the last documentary made by Robert Weide was the Academy-award nominated Lenny Bruce film, that was simply too coincidental to rule out any possibility that the documentary was real.
Of course I had my suspicions before that. The conversations Larry David was having were a little too Seinfeldian in nature. The conflicts a little too contrived. What they said all seemed to flow naturally, as most mockumentary dialogue does (see The Blair Witch Project's bit about "Gilligan's Island"). The camera shook just the right amount. The colors had that amateurish hue associated when you don't have cinematographers shining lights in people's faces or a very good DV. Knowing Weide's latest works (Lenny Bruce: Swear to Tell the Truth and being the writer-producer for Mother Night), I couldn't help but crack a smile as I realized that one was being put over on millions of HBO viewers across the country. Its the exact kind of thing that Larry David and Robert Weide would (and obviously do) love.
The mockumentary is the documentary's teenager. It runs around, does whatever it wants, and keeps going back and forth between the line between entertainment and intelligence. Contrary to popular belief, it existed before this summer's smash The Blair Witch Project (see This is Spinal Tap), and will exist long after the profit record for BWP is broken.  Much as I praised Lenny Bruce: Swear to Tell the Truth for being one of the finest documentaries I had ever seen, Larry David: Curb Your Enthusiasm is the best mockumentary I have ever seen.
Larry David: Curb Your Enthusiasm is the supposed documentary about the preparation for Larry David's return to stand up with an HBO special, which is eventually canceled at Larry's request (between a 3000-seat auditorium and a picture of him that looked like Woody Allen as if a cigarette had just been removed from his mouth, he goes the way of George's dad and says "I can't take it anymore" (but of course lies about the reason)). Over the period of forty-four days, Larry David is followed by the camera which records everything from a bit regarding Carolyn instead of Caroline, a near-divorce because Larry gets caught in the park with his adulterous manager's girlfriend, and a letter of recommendation gone to hell in a handbasket.
Because Weide is a great documentarian, he is able to be a great mockumentarian. He is so very familiar with the technical aspects and stylistic giveaways of documentary filmmaking that his mockumentary seems to be so perfectly real. It balances effortlessly the interviews and the raw footage, inserts David's comedy sets at just the right moments, and puts in some seriousness just to placate all documentary die-hards. Larry David is able to toss the jokes out with the same perfection as he did for nine years as a producer on "Seinfeld", and the two of them combine their efforts to make the mockumentary as surreally believable as some of the episodes of "Seinfeld" are.
As always, I cannot let a movie off without complaining about one thing. My complaint with Curb Your Enthusiasm is that the film seems to have too much direction to it to be completely believable. There are too many little touches for you to believe that this is real, and, in any mockumentary, this is distracting.

MovieKritic2000: Reviews for the Generation of a New Millenium
http://www.geocities.com/moviekritic2000/
Help support MK2K, become a member of http://www.epinions.com/. It's free and you can post opinions on books, movies, music, travel, software, and just about anything else under the sun.
To subscribe, email<EMAIL_ADDRESS>To email the critic, email<EMAIL_ADDRESS>The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


mdevd
Software
skarnet.org
The mdevd program
mdevd is a uevent manager. It connects to the netlink and reads
a series of uevents; for every uevent it reads, it performs
actions according to its configuration file. Actions can
be inserting a kernel module, creating or modifying device
entries in /dev, etc.
mdevd's configuration file uses the exact same
format as
mdev.
The differences between mdevd and mdev are:
- mdev needs to be registered as a hotplug manager and the
kernel spawns an instance of mdev per uevent; for every uevent,
mdev has to parse its configuration file. By contrast, mdevd is
a daemon: it's long-lived, and there is only one instance,
reading a series of uevents and
performing actions without forking; the configuration file is
read and parsed only once.
- Even though mdev can now be run as a daemon, via the -d
option, there are still technical advantages
to running mdevd over mdev.
Interface
mdevd [ -v verbosity ] [ -D notif ] [ -o outputfd ] [ -O nlgroups ] [ -b kbufsz ] [ -f conffile ] [ -n ] [ -s slashsys ] [ -d slashdev ] [ -F fwbase ] [ -C ]
- mdevd reads and parses its configuration file /etc/mdev.conf.
- It then connects to the netlink and reads from it, waiting for uevents.
- It exits 0 on a SIGTERM.
Exit codes
- 0: SIGTERM received, clean exit
- 1: received an invalid event
- 2: syntax error in the configuration file
- 100: wrong usage
- 111: system call failed
Signals
mdevd reacts to the following signals:
- SIGHUP: re-read the configuration file
- SIGTERM: exit as soon as possible
Options
- -v verbosity : be more or less verbose.
Default verbosity is 1. 0 will only print fatal error messages, 3 or more
is seriously verbose debugging.
- -D notif : when ready
(actually listening to the netlink),
write a newline to file descriptor notif then close it.
This allows mdevd to use the
s6 mechanism to notify
readiness. notif cannot be lesser than 3.
If this option is not given, no readiness notification is sent.
- -o outputfd : send a copy of the complete
uevent, with possible new fields, to file descriptor outputfd,
after mdevd has handled them. (This can serve as a
synchronization mechanism with an external program that needs a device to
have been properly configured by the device manager before acting on the
device.)
The uevent is sent with the kernel format: fields are separated by a null
character. The uevent is terminated by an additional null character.
outputfd cannot be lesser than 3 and cannot be the same as notif.
If for any reason, at any point, mdevd fails to write to outputfd,
it stops writing, until it is restarted. (This is to preserve mdevd's memory
stability guarantee.) By default, the uevents are not written anywhere.
- -O nlgroups : after mdevd has handled the
uevents, rebroadcast them to the netlink groups identified by the mask
nlgroups. Bit 0 of nlgroups is always ignored (because
netlink group 1 is the one used by the kernel to send the original uevents and
that mdevd listens to, and we don't want to loopback on it).
- -b kbufsz : try and reserve a kernel buffer of
kbufsz bytes for the netlink queue.  The default is 500 kB, which should be
enough for most systems; if you're getting "No buffer space available" errors
from mdevd at coldplug time, try increasing this number.
- -n : dry run. mdevd will not create or delete
device nodes, and it will not spawn commands. Instead, it will print to stdout
the actions it would have performed.
- -f conffile : read the configuration
file from conffile. Default is /etc/mdev.conf.
conffile must be an absolute path.
- -s slashsys : assume the sysfs
pseudo-filesystem is mounted on slashsys. Default is /sys.
slashsys must be an absolute path.
- -d slashdev : assume the device nodes
are to be found in slashdev. Default is /dev.
slashdev must be an absolute path.
- -F fwbase : assume the firmware files, if any,
are to be found in fwbase.
- -C : after initialization (when mdevd is ready), invoke
mdevd-coldplug, so that a coldplug is
automatically performed when mdevd starts. This option should only be used
in situations where a drop-in replacement for mdev -d is needed, because
it has the drawback of performing a coldplug every time mdevd is started —
including when mdevd is killed and restarted. By default, mdevd does not perform
a coldplug when it starts, and it is up to the administrator to properly organize
their boot scripts to run mdevd-coldplug once,
at boot time, when mdevd is ready. The examples/s6-rc subdirectory of
the mdevd package shows a way to do this with the
s6-rc service manager.
Configuration file
mdevd uses mdev's configuration file format.
A good mdev.conf example is available
here.
If mdevd cannot find its configuration file, it will use a simple, basic default
configuration where it can create device nodes as root or delete them, and does
nothing else.
A semantic difference with mdev is that a * directive will
be run on every action type, not just ACTION=add and
ACTION=remove. A & directive is in the same case (see
the paragraph below).
execline command support
In addition to the traditional shell command spawning via the @,
$ and * directives, mdevd also supports spawning a command
with the
execlineb
launcher:
- +cmd : spawns execlineb -Pc cmd
when this line catches an event that has ACTION=add. This is the
equivalent of @cmd.
- -cmd : spawns execlineb -Pc cmd
when this line catches an event that has ACTION=remove. This is the
equivalent of $cmd.
- &cmd : spawns execlineb -Pc cmd
when this line catches an event no matter its action type (add,
remove, or anything else). This is the equivalent of *cmd.
Note that unlike /bin/sh, execlineb is spawned without an
absolute path, so in order for +, - and & to
work, the execlineb command must be available in mdevd's PATH.
Notes
- The examples/ subdirectory of the mdevd package contains
examples on how to run mdevd under various init systems / supervisors. These
examples do not show how to run mdevd as a logged service, because mdevd
should normally be run early in the system's boot up sequence, before
mounting the disks - so the presence of a mounted partition suitable for
logging is not guaranteed. In normal use, mdevd is quite terse, so it
runs smoothly without a dedicated logger, with its error messages
going to the catch-all logger.


| PostgreSQL 9.0.10 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Chapter 30. Regression Tests | Next |
The regression tests can be run against an already installed and running server, or using a temporary installation within the build tree. Furthermore, there is a "parallel" and a "sequential" mode for running the tests. The sequential method runs each test script alone, while the parallel method starts up multiple server processes to run groups of tests in parallel. Parallel testing gives confidence that interprocess communication and locking are working correctly.
To run the parallel regression tests after building but before installation, type:
gmake check
in the top-level directory. (Or you can change to src/test/regress and run the command there.) This will first build several auxiliary files, such as sample user-defined trigger functions, and then run the test driver script. At the end you should see something like:
======================= All 115 tests passed. =======================
or otherwise a note about which tests failed. See Section 30.2 below before assuming that a "failure" represents a serious problem.
Because this test method runs a temporary server, it will not work when you are the root user (since the server will not start as root). If you already did the build as root, you do not have to start all over. Instead, make the regression test directory writable by some other user, log in as that user, and restart the tests. For example:
root# chmod -R a+w src/test/regress root# su - joeuser joeuser$ cd top-level build directory joeuser$ gmake check
(The only possible "security risk" here is that other users might be able to alter the regression test results behind your back. Use common sense when managing user permissions.)
Alternatively, run the tests after installation.
If you have configured PostgreSQL to install into a location where an older PostgreSQL installation already exists, and you perform gmake check before installing the new version, you might find that the tests fail because the new programs try to use the already-installed shared libraries. (Typical symptoms are complaints about undefined symbols.) If you wish to run the tests before overwriting the old installation, you'll need to build with configure --disable-rpath. It is not recommended that you use this option for the final installation, however.
The parallel regression test starts quite a few processes under your user ID. Presently, the maximum concurrency is twenty parallel test scripts, which means forty processes: there's a server process and a psql process for each test script. So if your system enforces a per-user limit on the number of processes, make sure this limit is at least fifty or so, else you might get random-seeming failures in the parallel test. If you are not in a position to raise the limit, you can cut down the degree of parallelism by setting the MAX_CONNECTIONS parameter. For example:
gmake MAX_CONNECTIONS=10 check
runs no more than ten tests concurrently.
To run the tests after installation (see Chapter 15), initialize a data area and start the server, as explained in Chapter 17, then type:
gmake installcheck
or for a parallel test:
gmake installcheck-parallel
The tests will expect to contact the server at the local host and the default port number, unless directed otherwise by PGHOST and PGPORT environment variables.
The source distribution also contains regression tests for the optional procedural languages and for some of the contrib modules. At present, these tests can be used only against an already-installed server. To run the tests for all procedural languages that have been built and installed, change to the src/pl directory of the build tree and type:
gmake installcheck
You can also do this in any of the subdirectories of src/pl to run tests for just one procedural language. To run the tests for all contrib modules that have them, change to the contrib directory of the build tree and type:
gmake installcheck
The contrib modules must have been built and installed first. You can also do this in a subdirectory of contrib to run the tests for just one module.
The source distribution also contains regression tests of the static behaviour of Hot Standby. These tests require a running primary server and a running standby server that is accepting new WAL changes from the primary using either file-based log shipping or streaming replication. Those servers are not automatically created for you, nor is the setup documented here. Please check the various sections of the documentation already devoted to the required commands and related issues.
First create a database called "regression" on the primary.
psql -h primary -c "CREATE DATABASE regression"
Next, run a preparatory script on the primary in the regression database: src/test/regress/sql/hs_primary_setup.sql, and allow for the changes to propagate to the standby, for example
psql -h primary -f src/test/regress/sql/hs_primary_setup.sql regression
Now confirm that the default connection for the tester is the standby server under test and then run the standbycheck target from the regression directory:
cd src/test/regress gmake standbycheck
Some extreme behaviours can also be generated on the primary using the script: src/test/regress/sql/hs_primary_extremes.sql to allow the behaviour of the standby to be tested.
Additional automated testing may be available in later releases.


Phenotype Prioritization
Phenotype-based prioritization is based on matching the gene that a variant is located in with your patient based on the phenotypes of genes and patients.
VarFish use
Exomiser for this which already knows about genes.
To describe the phenotypes for your patient,
enter phenotypes (HPO) or diseases (OMIM) into the "Type HPO or OMIM..." box and click on the appearing suggestions to select them.
The HPO and OMIM terms will then be added to the text box below.
These values will then be used for the prioritization.
You can also paste some terms, e.g., as "HP:0004440; OMIM:122850".
HPO terms selected but prioritization not enabled!
{{ form.prio_enabled|as_crispy_field }}
{{ form.prio_algorithm|as_crispy_field }}
{{ form.prio_hpo_terms|as_crispy_field }}
Pathogenicity Prioritization
Enable the pathogenicity-based priotizatio and (optionally) adjust the scoring method below.
{{ form.patho_enabled|as_crispy_field }}
{{ form.patho_score|as_crispy_field }}


DedicationTo the ones who named me: Mom and Dad, thank you for writing such a beautiful introduction for my story. If I ever forget to tell you how grateful I am—you have it here in writing! To the ones whom I have named: Andrew James and Katherine Juliet, I pray your stories will be filled with richest moments of closeness to Jesus. When there is pain, may He write comfort. When there is joy, be sure to write gratitude. Most of all, know that He who began a good story for you will be faithful to complete it. |


| Interface | Description |
|---|---|
| Device |
The Device interface is a local representation of device data.
|
| MASAuthCredentials |
An interface for including the headers and parameters for a set of authorization credentials.
|
| MASAuthenticationListener |
Interface that will receive various notifications and requests for MAG Client.
|
| MASAuthorizationRequestHandler |
Handle OAuth Authorization Code flow.
|
| MASClaims |
An interface to get JWT claim values.
|
| MASConnectionListener |
Interface that allows for implementing classes to listen for connection events.
|
| MASLifecycleListener |
Interface that allows for implementing classes to listen for MAS lifecycle events.
|
| MASProgressListener |
MASProgressListener is implemented by classes that want to know the progress on file upload/download.
|
| MASRequest |
An Http Api Request.
|
| MASResponse<T> | |
| MASSecurityConfiguration |
MASSecurityConfiguration class is an object that determines security measures for communication between the target host.
|
| MASTransformable |
MASTransformable is implemented by classes that are populated via SCIM.
|
| UserRepository |
| Class | Description |
|---|---|
| Extension | |
| FoundationConsts |
FoundationConsts contains the base constants used by any classes in the hierarchy.
|
| JWKPreLoadListener |
Implements listeners for various MAS Life Cycles.
|
| MAS |
The top level MAS object represents the Mobile App Services SDK in its entirety.
|
| MASAuthCredentialsAuthorizationCode |
MASAuthCredentials for Authorization Code Grant Type
|
| MASAuthCredentialsClientCredentials |
MASAuthCredentials for Client Credentials Grant Type
|
| MASAuthCredentialsJWT |
MASAuthCredentials for JWT Grant Type
|
| MASAuthCredentialsPassword |
MASAuthCredentials for Username & Password Grant Type
|
| MASAuthorizationRequest |
OAuth2 Authorization Request
|
| MASAuthorizationRequest.MASAuthorizationRequestBuilder | |
| MASAuthorizationResponse |
Response to an authorization request
MASAuthenticationProviders.getAuthenticationProviders(MASCallback) |
| MASCallback<T> | |
| MASClaimsBuilder |
A builder to construct MASClaims objects.
|
| MASClaimsConstants |
Registered claim names.
|
| MASConfiguration | |
| MASConstants |
Contains enums for describing the grant flow and the SDK state.
|
| MASDevice |
The MASDevice class is a local representation of device data.
|
| MASException |
Encapsulates a general MAS error as an exception that returns to a
MASCallback.onError(Throwable) . |
| MASFileObject |
The MASFileObject class is a representation of file attributes.
|
| MASFoundationStrings |
A class that contains user feedback messages.
|
| MASGroup |
The MASGroup class is a local representation of group data.
|
| MASIdToken |
ID token as described in ID Token
By default, the type would set to urn:ietf:params:oauth:grant-type:jwt-bearer
|
| MASIdToken.Builder | |
| MASMultiFactorAuthenticator<T extends MASMultiFactorHandler> |
Represents a multi-factor authenticator
|
| MASMultiFactorHandler |
A Handler object to handle multi-factor authentication
|
| MASOtpAuthenticationHandler |
A Handler object to handle One Time Password multi-factor authentication
|
| MASOtpMultiFactorAuthenticator |
One Time Password MultiFactorAuthenticator
|
| MASRequest.MASRequestBuilder |
Builder class to build
MASRequest object |
| MASRequestBody | |
| MASResponseBody<T> |
An API HTTP response body.
|
| MASSecurityConfiguration.Builder | |
| MASSessionUnlockCallback<T> | |
| MASTokenRequest | |
| MASUser |
The MASUser interface is a core interface used to represent a user in the system,
as well as an Identity Management definition used in the interaction with SCIM.
|
| MultiPart |
Represents the multipart body of a multipart/form-data http post request.
|
| Enum | Description |
|---|---|
| MASGrantProvider |
Constant to define Grant Types
|
| MASRequest.Method |
| Exception | Description |
|---|---|
| MAS.RequestCancelledException | |
| MASDeviceAttributeOverflowException | |
| MASInvalidHostException |
Thrown when an invalid host is identified.
|
| MASServerException |
MASServerException is a general exception wrapper used by the MAS SDK
|
| MASSharedStorageException |
Used for any issues encountered with creating the MASSharedStorage identifier.
|
| Annotation Type | Description |
|---|---|
| Internal | |
| MASExtension | |
| MASGrantFlow | |
| MASState |
Summary
ValueDescription
MASConstants.MAS_STATE_NOT_CONFIGUREDState that SDK has not been initialized and does not have configuration file.
MASConstants.MAS_STATE_NOT_INITIALIZEDState that SDK has the active configuration either in the local file system, but has not been initialized yet.
MASConstants.MAS_STATE_STARTEDState that SDK did start; at this state, SDK should be fully functional.
MASConstants.MAS_STATE_STOPPEDState that SDK did stop; at this state, SDK is properly stopped and should be able to re-start.
|
| Xamarin |
Indicate this class or method is required for Xarmarin binding
|


Description Lists
The dl element indicates a description list:
Coffee
- black hot drink
Flaxseed milk
- white cold drink


the and team for The that experts are expert distance skill with network between social from interaction Fig. set skills recommendations not only composition recommendation two each formation than coverage can our this best problem connected direct provide more when interactions while {background Experiment based has new provides For also candidate expertise number function links all configurations dynamic experts. have however, thus which members nodes teams better configuration determine required Simulated but edge networks Team data margin results where edges one other recommendations. single {border-style Genetic This Top apply approach both overall quality structure Bob algorithm heuristics high higher level maximum multiple px;} selection such suitable team. then values well will work yield #ffffff;} Annealing find genetic how lower trade-off unavailable (Fig. (i.e., Alice NY, York, any degree every given link model simulated their current graph need possible research respectively weight (Eq. conference different mutation within []. analysis available density effect even experts, international minimum node population Knowledge Slashdot When annealing collaboration defined distance. fitness improvement individual initial into skills. these three top weighted Section becomes common finding impact same similar size there 'ACMNew (e.g., ACM Systems USAhttp://doi.acm.org/./. become correlation distribution energy experiment information low obtain out profile rich-club skill. team's value various (see Algorithm Our University able combination compared connectivity corresponding does end fixed following group large members. network. particular rather search sets underlying weights ()) Algorithms Conference al. analyze applied applying calculation case collaborative complete consists coverage. describes evaluate exhibit focus having his knowledge larger likely links. member most multi-objective optimal parameter people px; remains respective selected significant skill, skills, small tasks those threshold uy, virtual {font-family < (line Bob, Table Thus, Top( Transactions Vienna additional address algorithms amount availability calculate cannot case, collaborations compare demonstrate distance, efficient example existing expect experiments factor font-size generation increase individuals its large-scale mining needs neighbors. networks. next outline parameters part performance preferential process proximity q(s)min random reflects relations set. solutions strong temperature they through too trust would & > Carol Carol, Consequently, Expert Here, However, Pop Proceedings These Thus USAdoi:http://doi.acm.org/./. World across aims always assume below clique complex configuration. consistently coverage, crossover crowd derive determines determining double; dynamically equal exist final found fully heuristic increases inverse k-partite linear low-degree measurement metric objective order over potentially previous probability profiles properties propose rank related scope second significantly sk, strategy subsequently subset team, towards usually via who world Alice, Distributed Hence, Here International Most Recommendations TB,D,B Team. Technology. There Web Workshop [], above aim already among applies as: aspects aware b). border-color border-width candidates chosen close community complexity compositions connecting connectivity. consider contrast, depends describe detailed directly discovery discuss equally example, expert's first further generate give global graph. highest important improvements include including indicator introduce involved iteration least limited lines main maintaining many neighbors nrg outperforms paper power-law produce quality. randomly real real-world recommendation-based recommending remain service similarly solid; solution solution. some strength success successful successfully system take test use user very were whereas wide without working yields {font-style {font-weight ()). (Experiment Both Cand Composition Computer Distance Example Finally, First, Given Group, Int. John More Note O(| One SIGKDD Second, Such TB,D,A We( While Wide Wr( [,] [,]. ability about account addition another assigned average avoid balance bold c). calculating certain characteristics chromosomes comparatively configurations. considered constraints context correctly count courier; demonstrates detail determined differ effective effort efforts em; ensures establish expertise. extended failed far few focusing form frequently full functions gene good high-degree identify improved increasingly interacted interaction-based items iterations join joint line lines) long low. major management match mechanism might multi-skill must non-connected normalized observe open overloaded phenomenon produced providing pt;} pure rate red reduce reducing regardless represent represents requires researcher respectively. s/he sake scientific section select selecting simulation sl) smaller still sum synthetic systems takes tasks. therefore time, together tradeoff tuple tuples unavailable. used users valid web weights. {Bob,


Adding Feedback Subjects
How to add subjects to a Feedback module. Once you have created subjects they can either be associated with one or more instances of a Feedback module, or users can be enabled to select a subject from a list when sending their feedback.
- Select Edit > Edit Category/Subject Lists from the module actions menu. This opens the Edit Lists page.
- At List Type, select Subjects.
- In the Name text box, enter the subject name. E.g. Feedback
- In the Value text box, enter a value for this subject. E.g. Feedback. This value can optionally be displayed in the Feedback Comments module beside any feedback associated with this subject.
- At Is Active, if this category will show up in the category list on the Feedback module - OR - if this category is currently inactive.
- At Is Portal Wide, if this subject can be viewed and selected using all Feedback modules across this site - OR - if this subject is only displayed on this module.
- Click the Save button. The saved subject will be displayed to the left.
- Repeat Steps 3-7 to add additional subjects.
- Click the Return to Module button when you are finished.


HTML Introduction
What is HTML? HTML is the standard markup language for creating Web pages. It allows the user to create and structure sections, paragraphs, headings, links, and blockquotes for web pages and applications.
- HTML stands for Hyper Text Markup Language.
- HTML describes the structure of Web pages using markup.
- HTML elements are the building blocks of HTML pages.
- HTML elements are represented by tags.
- HTML tags label pieces of content such as "heading", "paragraph", "table", and so on.
- Browsers do not display the HTML tags, but use them to render the content of the page.
A simple HTML Document
*** Example Code ***
<!DOCTYPE html >

<title> Page Title Goes Here </title>

 My First Heading

 My first paragraph.

Example Explained
- The <!DOCTYPE html> declaration defines this document to be HTML5.
- The  element is the root element of an HTML page.
- The  element contains meta information about the document.
- The <title> element specifies a title for the document.
- The  element contains the visible page content.
- The
 element defines a large heading.
- The
 element defines a paragraph.
HTML Tags
HTML tags are element names surrounded by angle brackets:
<tagname> content goes here.. </tagname>
-  tags normally come in pairs like
 and
.
- The first tage in a pair is the start tag, the second tag is the end tag.
- The end tag is written like the start tag, but with a forward slash inserted before the tag name.
HTML Editors
Web pages can be created and modified by using professional HTML
editors.
However, for learning HTML we recommend a simple text editor like
Notepad (PC) or TextEdit (Mac). We believe using a simple text
editor is a good way to learn HTML.
Follow the four steps below to create your first web page with
Notepad or TextEdit.
Step 1 : Open Notepad (PC)
-
Windows 8 or later:
Open the Start Screen (the window symbol at the bottom left of the screen). Type Notepad.
-
Windows 7 or earlier:
Open Start > Programs > Accesories > Notepad.
Step 1 : Open TextEdit (Mac)
- Open Finder > Applications > TextEdit.
- Change some preferences to get the application to save files correctly. In Preferences > Format > choose "Plain Text."
- Then under "Open and Save", check the box that says "Display HTML files as HTML code instead of formatted text".
- Then open a new document to place the code.
Step 2 : Write Some HTML
Write or copy some HTML into Notepad.
Step 3 : Save the HTML Page
- Save the file on your computer. Select File > Save as in the Notepad menu.
- Name the file "index.htm" and set the encoding to UTF-8 (which is the preferred encoding for HTML files).
Step 4 : View the HTML Page in Your Browser
- Open the saved HTML file in your favorite browser (double click on the file, or right-click - and choose "Open with").
HTML Basic Examples
Let's have a look at some pretty simple examples regarding how HTML works and how we can start writing code. Feel free to try them out in a text editor to see how they look in your own browser and customize them further.
Step 1 : Open Notepad (PC)
- All HTML documents must start with a document type declaration: <!DOCTYPE html>.
- The HTML document itself begins with  and ends with .
- The visible part of the HTML document is between  and .
*** Example Code ***
<!DOCTYPE html >

<title>
Page Title Goes Here
</title>

My First Heading

My first paragraph

HTML Headings
- HTML headings are defined with the
 to
 tags.
-
 defines the most important heading.
 defines the least important heading:
*** Example Code ***

This is heading 1

This is heading 2

This is heading 3

This is heading 4

HTML Paragraphs
- HTML links are defined with the  tag:
***Example Code***

This is a link

- The link's destination is specified in the href attribute.
- Attributes are used to provide additional information about HTML elements.
- You will learn more about attributes in a later chapter.
HTML Images
- HTML images are defined with the  tag:
- The source file (src), alternative text (alt), width , and height are provided as attributes:
***Example Code***

HTML Buttons
- HTML buttons are defined with the <button> tag:
***Example Code***
<button>Click me </button>
HTML Lists
- HTML lists are defined with the
 (unordered / bullet list) or the
 (ordered / numbered list) tag, followed by
 tags (list items):
***Example Code***

 Coffee

 Tea

Milk

HTML Elements
An HTML file consists of elements. They are responsible for creating web pages and defining content in that wepage. It usually consists of a start tag <tag name>, close tag </tag name> and content is inserted in-between. Technically, an element is a collection of a start tag, attributes, an end tag and content between them.
Nested HTML Elements
- HTML elements can be nested (elements can contain elements).
- All HTML documents consist of nested HTML elements.
- This example contains four HTML elements:
***Example Code
<!DOCTYPE httml>

 My first Heading

 My first paragraph.

- The  defines the document body.
- It has a start tag and an end tag .
- The element content is two other HTML elemenents (
 and
)

 My first heading

 My first paragraph

- The
 element defines a paragraph.
- It has a start tag
 and an end tag

- The element content is: My first paragraph.

 My first paragraph.

HTML Attributes
Attributes provide additional information about the HTML elements, by either being additional values that configure the elements or by adjusting their behavior in various ways to meet the criteria that users want.
- All HTML elements can have attributes.
- Attributes provide additional information about an element.
- Attributes are always specified in the start tag.
- Attributes usually come in name/value pairs like: name="value".
The href Attribute
- HTML links are defined with the  tag. The link address is specified in the href attribute:
***Example Code***

The width and height Attributes
- Images in HTML have a set of size attributes, which specifies the width and height of the image:
***Example Code***

The alt Attributes
- The alt attribute specifies an alternative text to be used when an image cannot be displayed.
-
The value of the attribute can be read by screen readers. This
way, someone "listening" to the webpage.
e.g. a vision impaired person, can "hear" the element.
***Example Code

The lang Attribute
- The language of the document can be declared in the  tag.
- The language is declared with the lang attribute.
- Declaring a language is important for accessibility applications (screen readers) and search engines:
<!DOCTYPE html>

...

The title Attribute
- Here, a title attribute is added to the
 element. The value of the title attribute will be displayed as a tooltip when you mouse over the paragraph.
*** Example Code***

this is a paragraph


--- creation_epoch:<PHONE_NUMBER> lastmod_epoch:<PHONE_NUMBER> categories: ['Tech Tricks'] title: Cloning Drive with dd and WinPE ---
I had a system where I wanted to clone a USB enclosure drive to an internal RAID running under Intel RST (fake-RAID). Linux cannot recognize the recent laptop edition of the Intel RST (the decades older RSTi has a kernel module, but not the newer one). I had to use a Windows environment for the necessary driver support to recognize the disk volumes.
I initially created an amd64 WinPE disk, but it also lacked BitLocker support and other necessary tools. I tried some online disk cloning softwares that would create WinPE boot media, but they did not do a true sector by sector copy resulting in the BitLocker partition being corrupt.
I used a Ventoy USB with the unmodified Win10_22H2_English_x64v1.ISO installer. I would boot with this, select repair, and open a Command Prompt.
I also found a 64-bit version of dd.exe for Windows (most versions are 32-bit which won't execute). http://www.chrysocome.net/dd. You want the ddrelease64.exe.
Place a copy of it on the USB.
D:\ddrelease64.exe --list Use diskpart list disk if you need disk numbers for reference.
ddrelease64.exe if=\\?\Device\Harddisk2\Partition0 of=\\?\Device\Harddisk0\Partition0 --progress bs=1G
If the system does not boot you probably need to rebuild the UEFI BCD
Use diskpart to Assign the EFI partition if necessary E: cd \EFI\Microsoft\Boot bcdboot C:\Windows /l en-us /s E: /f ALL


One of the joys of Death Knight Love Story has been the chance to reimagine and reinvent the places of World of Warcraft which I've enjoyed playing through for so many years.
Because of the way that we made DKLS, we had the basic 3D models for each location, but we had to recreate the atmosphere, inhabitants and lighting of the area from scratch. And because we were using radically different rendering techniques, we couldn't just copy Blizzard's original art direction.
So here's how we approached reimagining some of the best-known locations from WoW in DKLS.
Check back for more articles over time!
As the original seed for Death Knight Love Story, we knew we HAD to get Naxxramas right. Add to the that fact that of all our locations, this is probably the one that viewers who play WoW will have spent the most time in, and we had a pretty big challenge on our hands.
Naxxramas has a hell of a lot of history for WoW players. Originally, it was the final, hardest 40-man raid in the original hit version of WoW: a place that only the elite players had even seen. And within Naxxramas, the encounter that was most feared was the "Four Horsemen" - the climax of Naxx's "Military Wing", and probably the most challenging encounter for any player in Vanilla WoW.
I was playing WoW at the time Naxx came out, but I was never elite enough to go there. However, when the Wrath of the Lich King expansion came out, Blizzard decided to revamp Naxx and open it up as the first raid of the expansion - and I got to know it very well indeed.
Because it's a relic of original WoW, the location of the Four Horsemen is actually very simple: just a raised platform surrounded by skulls in a rectangular room.
For DKLS, the first thing that Johnnie Ingram and I did was to think about the iconic shots we wanted to get from the space presented to us. An obvious inspiration for shooting the Horsemen was Peter Jackson's treatment of the Nazgul - another group of riders. Watching back through the Lord of the Rings films, the first sequence with the Nazgul chasing the Hobbits stuck out to me: particularly the shots where they are backlit by light fog in a dark forest, causing them to appear as a silhouette on the screen.
But why would they be backlit, and from what?
It's tremendously difficult to keep track of distances and directions inside the maze of Naxxramas, but fortunately we had the advantage of being able to look at the entire model from the outside, and that told us something very interesting: the Four Horsemen's room is actually right on the edge of the structure. And that gave us a way in: what if the entire room was lit by a single archway looking out of Naxxramas?
One backlight and some fog later, and Death Knight Love Story's Naxxramas was starting to take shape.
However, that backlight turned out to be quite a problem: it gave us a brilliant wide shot, but close up it would overpower the characters' faces or cause wierd shapes in the background. As a result, throughout the scene the light ends up changing shape and intensity with virtually every shot. All of that effort's invisible in the end result, though - just another quirk of virtual filmmaking!
We already knew that the room itself would follow Blizzard's original art direction of blue and green lights - the same colour palette used all through Naxxramas and one of the standard palettes they use for the Undead controlled by the Lich King as a whole. So when we decided to add the adventurers waiting to attack the Horsemen (that scene actually only came in with the fourth draft of the film), we lit their tiny "refuge" outside the main room with warm, alive lights in red and yellow, to still give the sense of danger but contrast the living adventurers with the Death Knights waiting inside.
We actually made one of our very rare changes to WoW's architecture here. I'd recalled from many evenings spent waiting to attack the Horsemen that it was possible to hide behind the walls outside the Four Horsemen's room - but when we came to location-scout in game, we discovered that unless we wanted our adventurers lurking in green slime, there was no space to do that!
As a result, we had to extend the walls a few feet into the archway, then slightly rebuild the pillars, all in order to fix the sight lines.
It ended up being a perfect illustration of the problems of translating a game location into film. In the game, we never questioned why the Horsemen didn't attack despite the fact they could clearly see us - we knew they had an "aggro radius", and if we didn't get within it, we were safe. But as soon as the same situation was translated to film, it was patently ridiculous!