{% extends "layout.html" %} {% block title %}Not Found - 404 - Express Server-Render Starter{% endblock %} {% block description %}Not Found - 404 - Express Server-Render Starter{% endblock %} {% block content %} The page you've requested could not be found You requested a page that doesn't exist.
Go Back


Fake Online REST API for Testing and Prototyping
Powered by
JSON Server
+
LowDB
fetch('https://jsonplaceholder.cypress.io/todos/1')
.then(response => response.json())
.then(json => console.log(json))


RT @DataChomp: "How come you only finished half the flower beds?" 'I think you mean, nice work establishing a good control group'
9/26/2012, 6:16:23 PM
Favs: 0
Retweets: 0
link--- layout: tweet ---
RT @DataChomp: "How come you only finished half the flower beds?" 'I think you mean, nice work establishing a good control group'
9/26/2012, 6:16:23 PM
Favs: 0
Retweets: 0
link


{{ post.title }} by {{ post.author.username }}/{{ post.created_at }} {{ post.content }} Continue Reading


The Hosted Checkout model allows you to collect payment details from your payer through an interaction hosted and displayed by the Payment Gateway. This means you aren't responsible for handling sensitive PCI data.
Hosted Checkout can be implemented as:


Jack Dongarra opened the meeting by welcoming everyone and inviting everyone to introduce themselves. He then reviewed the technical ``rules of order'' for the first and second readings of proposals, as well as the voting procedures for the meeting. Tony Skjellum suggested that we integrate all of the proposals into one unified document, similar in style to the MPI proposal. This issue was discussed in further detail later in the meeting.
The following presentations were made:
BLAS functionality was the first to be addressed. Sven Hammarling of NAG gave a brief overview of the Functionality proposal that has been available via the BLAST Forum homepage, as well as addressing several email messages from users pertaining to desired ``new'' routines. He stressed the areas of the proposal that still need to be written, specifically the introductory background motivation, performance issues, numerical stability, as well as justification for the new proposed functionality. Any new functionality that is proposed should have a clear justification identifying the applications where this operation is needed. Several attendees debated if some of the information contained in the proposal is not strictly ``functionality'' issues, but rather language independent specifications as well as language bindings. It was proposed that some of the information in the tables of proposed routines be reorganized into separate sections on these issues.
Linda Kaufman of Bell Labs then spoke about her recent revisions to the proposal, namely adding priorities to each of the new proposed routines. Mimi Celis of SGI and Sven Hammarling of NAG directed attention to the standardization efforts of the VSIP (Vector, Signal and Image Processing) community. Roldan Pozo of NIST proposed a study to see the use of BLAS in applications. He stressed an effort to clearly justify what is included and what is not included in order to realistically accomplish our goals. Several of the application developers present in the meeting voiced that they felt the ``Functionality'' proposal does accurately reflect the needs of their users. However, it was also pointed out that there are those in the numerical analysis community who will never rewrite their codes in terms of the BLAS. And in some cases, it is too expensive to rewrite optimized existing application programs such as NASTRAN and GAUSSIAN in terms of the BLAS. Some vendors have inserted BLAS calls inside these codes, while others have chosen to optimize them in different ways.
Tony Skjellum of Mississippi State emphasized that most programmers develop their algorithms first in ``matlab-type'' environments. The use of standards in numerical analysis programming could be increased by promoting a ``BLAST toolbox'' in Matlab, or more strongly encourage the use of LAPACK and the BLAS inside of Matlab.
After a break, Roldan Pozo of NIST presented the sparse BLAS proposal that is available on the BLAST Forum homepage. He discussed the roles and functionality of the Sparse BLAS, as well as open issues in their development. Again it was voiced that several of the issues discussed were not primarily functionality issues but language binding issues. Concern was also expressed by several attendees due to the sheer volume of routines proposed. In order for a sparse BLAS to be more readily accepted, the number of proposed routines may need to be reduced.
After Roldan's presentation, a break-out session for the meeting of subgroups was held. The following subgroups met: functionality, sparse BLAS, parallel BLAS, lite BLAS, and the C interface to the BLAS.
Jack Dongarra opened the morning session with a brief summary of the previous day's discussions.
Tony Skjellum began the morning discussions with an overview of his thoughts on the presentation of our ``proposals'' for the BLAST work, specifically organization of a unified document for the BLAST proposal instead of separate ``proposals''. The document would primarily contain separate chapters on functionality, language independent specifications, and language binding issues. Interleaved in these sections would be information pertaining to the sequential, sparse, parallel, etc. Several attendees voiced concern at this one proposal idea instead of separate proposals. Specifically, if a user or vendor is only interested in information pertaining to the sparse BLAS, he would still need to read the entire document. Richard Hanson of VNI suggested that we have an ``implementation'' chapter or appendix to ease the integration job for the vendors. Linda Kaufman of Bell Labs further suggested a ``tutorial'' or ``quick reference guide'' for each of the different standards proposed. Jack Dongarra of UT stressed the importance of a reference implementation that should be included with the standard.
Following this discussion, Tony Skjellum presented the BLAS Lite proposal that is available on the BLAST Forum homepage. Several vendors expressed concern about the volume of routines that are proposed. It was suggested that a more extensive performance evaluation of the Lite BLAS be conducted before a decision is made on their inclusion in the standardization effort. Concern was raised about the portability of the Lite BLAS since they are in effect a ``cache-based'' BLAS. Andrew Lumsdaine and Brian McCandless, who have implemented preliminary versions of the BLAS Lite routines, promised to make their results available to the BLAST Forum in a timely fashion.
Antoine Petitet of UT led discussion on the issues involved in developing a set of parallel BLAS. A note discussing the issues is available on the BLAST Forum homepage.
Chenyi Hu of the University of Houston, Downtown, presented a few slides on the needs of the Interval BLAS community. It was suggested that a separate section for the Interval BLAS be included in the BLAST proposal.
After lunch, Clint Whaley of UT summarized what is contained in the ``C Interface to the Existing BLAS'' proposal available on the BLAS Forum homepage. He also discussed what occurred in the ``break-out'' session the previous day. Jesse Bennett of Texas Instruments also gave a brief presentation on what he perceives as user needs for the CBLAS. The majority of opinions from vendors supported the view that the operations should be ``row-major'', and that character arguments should be handled as enumerated types. Mimi Celis of SGI specifically said that SGI had introduced a C interface for the BLAS which was ``column-major'' and the C users refused to use it. It was then suggested that it may be possible to present a ``row-major'' interface to the existing BLAS through careful manipulation of the transpose in calculations. An attendee thought that this is the way that Digital Corporation presented a ``row-major'' interface, and this is under investigation. Again the VSIP standardization effort was mentioned in regards to two-dimensional arrays in Fortran versus C. Mimi Celis of SGI stated that in the VSIP effort it is assumed that two-dimensional arrays in C are contiguous. Email conversation on these topics (as well as the issue of a ``complex'' data type) were encouraged.
Andrew Lumsdaine next spoke about the question of the organization of the Forum, the presentation of the proposal document, the varied user base, and his recommendations for how we should proceed. Concern was again raised for the user who is only interested in one aspect of the standard and must read the entire document. A straw vote was taken to ascertain if we should try to integrate the BLAST proposal into one unified document. Appendices for a ``tutorial'' and ``reference implementation'' will be included. The vote was unanimous to integrate the proposals into one unified document. Twenty-two people were present for the vote.
A summary of the meeting was then provided by Jack Dongarra. He focused on the specific tasks of writing several needed chapters for the BLAST proposal. Namely:
The document will be established on the net, and individual chapters will be available for downloading in latex format.
The global editors for the BLAST proposal are Andrew Lumsdaine and Tony Skjellum.
The tentative date of the next forum meeting is:
and will be hosted by Intel Corporation, with a preliminary deadline of April 30, 1997 for subgroup progress.
The meeting was then adjourned by Jack Dongarra at 3:00 PM.
Attendees list for the February 27-28, 1997 BLAST Forum Meeting
Puri Bangalore Miss. State Univ<EMAIL_ADDRESS>Jesse Bennett Texas Instruments<EMAIL_ADDRESS>Susan Blackford Univ. of TN, Knoxville<EMAIL_ADDRESS>Mimi Celis SGI<EMAIL_ADDRESS>Andrew Chapman NEC Systems Laboratory<EMAIL_ADDRESS>Isom Crawford HP/Convex<EMAIL_ADDRESS>Dave Dodson HP/Convex<EMAIL_ADDRESS>Jack Dongarra Univ. of TN / ORNL<EMAIL_ADDRESS>Paul Dressel HP/Convex<EMAIL_ADDRESS>Cormac Garvey NEC Systems Laboratory<EMAIL_ADDRESS>Ian Gladwell SMU<EMAIL_ADDRESS>Bruce Greer Intel<EMAIL_ADDRESS>John Gunnels Univ. of TX, Austin<EMAIL_ADDRESS>Sven Hammarling NAG, UK<EMAIL_ADDRESS>Richard Hanson VNI<EMAIL_ADDRESS>Chenyi Hu Univ. of Houston/Downtown<EMAIL_ADDRESS>Linda Kaufman Bell Labs<EMAIL_ADDRESS>Jim Koehler HP/Convex<EMAIL_ADDRESS>Hsin-Ying Lin HP Convex Technology Ctr<EMAIL_ADDRESS>John Liu HP/Convex<EMAIL_ADDRESS>Andrew Lumsdaine Univ. of Notre Dame<EMAIL_ADDRESS>Brian McCandless Univ. of Notre Dame<EMAIL_ADDRESS>Joan McComb IBM Poughkeepsie<EMAIL_ADDRESS>Jim Nagy SMU<EMAIL_ADDRESS>Antoine Petitet Univ. of TN<EMAIL_ADDRESS>Roldan Pozo NIST<EMAIL_ADDRESS>Karin Remington NIST<EMAIL_ADDRESS>Tony Skjellum Miss. State Univ<EMAIL_ADDRESS>Shane Story Intel<EMAIL_ADDRESS>Kevin Wadleigh HP/Convex<EMAIL_ADDRESS>Clint Whaley Univ. of TN, Knoxville<EMAIL_ADDRESS>Guodong Zhang HP/Convex<EMAIL_ADDRESS>Susan Blackford and Andrew Lumsdaine agreed to take minutes for the meetings.


Here's an interactive map for each historical marker in Kentucky. The Kentucky Historical Society furnished the data from their website.


auto-format
An easy to use, light-weight library to auto-format code in javascript. Works well with code highlighting libraries to display beautiful, uniformly formatted code.
As of right now only Java can be formatted properly, although you will probably get decent results with any language that uses brackets as scope delimiters. Further more the library is very extensible, in fact you only have to implement 5 methods to add support for another language. Please see contribute if you would like to contribute. Help is always welcome!
Examples
format method:
You can also check out https://exemplator.xyz where all code samples are formatted with this library.
Live example of format method.
Install
Run npm install auto-format --save
Usage
As of right now, only Java is fully supported.
ES6:
import Formatter from "auto-format"
Vanilla JS:
var Formatter = require('auto-format');
Simple example: format
var indentToken = " ";
var unformattedCode = "code to format";
var javaFormatter = Formatter.createJavaFormatter(indentToken);
var formattedCode = javaFormatter.format(unformattedCode);
Format a string of code. The string will be cut into lines and lines will be indented accordingly to their scope.
-- Parameters:
indentToken
: The token used to indent lines (e.g. 2 or 4 spaces).
unformattedCode
: A string of unformatted code (including line breaks).
-- Return:
formattedCode
: An array lines of code. All lines will have been correctly
indented according to their scope.
Complex example: formatSnippet
var indentToken = " ";
var javaFormatter = Formatter.createJavaFormatter(indentToken);
var unformattedCode = "code to format";
var selectionStartRow = 11;
var selectionEndRow = 11;
var snippetOffset = 6;
var formattedCode = javaFormatter.formatSnippet(unformattedCode, selectionStartRow,
selectionEndRow, snippetOffset);
A slight variation of format(codeString)
. Useful if you want to display a code snippet around a selection of lines like
here.
In addition to indenting lines, formatSnippet takes a selection and an offset.
The selection consists of one or several lines which should be "highlighted" in the code. For example the line that you would like to show off. The offset defines the number of lines above and below the selection.
The start and end of the snippet is calculated from the selection start, end and the offset. formatSnippet
intelligently cuts the snippet out of the original codebase. 'Intelligently' means the method
always tries to cut out only the method out of the selection. If the method is too big, only a part of the method will be cut out, but lines outside this method (i.e. other methods etc.) are cut away unless they comment that method.
-- Parameters:
indentToken
: The token used to indent lines (e.g. 2 or 4 spaces).
unformattedCode
: A string of unformatted code (including line breaks).
selectionStartRow
: The start row of the selection in the code base.
selectionEndRow
: The end row of the selection in the code base.
snippetOffset
: The number of lines above and below the selection.
-- Example:
Selection start row: 11
Selection end row: 11
Offset: 6
------------------------------
Snippet start row: 11 - 6 = 5
Snippet end row: 11 + 6 = 17
-- Return:
formattedCode
: An array in the form of
[code string above selection, code string of selection, code string below selection,
[new start line of snippet in original file, new end line of snippet in original file]]
For more details and examples see the documentation.
Contribute
Pull requests are always welcome. To add support for a new language, look at the JavaFormatter.
The documentation is here.


A web page is a text document written in language called HTML, ( Hypertext Markup Language). Web browsers read these documents, and then interpret and display them. This collection of HTML code makeup the WWW also known as the Internet. The Internet is the world largest computer network with a bunch of computers communicating using the main protocol of the web called HTTP.
When a person goes to the web page like www.google.com, their computer sends a HTTP request to a server. The server finds the appropriate HTML document and sends it back to the user’s computer where a web browser interprets the page and displays it on the user’s screen. This video does a good job of explaining.
HTML,(Hypertext Markup Language) documents are the Heart of the web.
HTML is made up of:
- Text content, - what you should see
- Markup - what it looks like
- References to other documents - e.g. images, videos, files etc.
- Lings to other pages - called hyperlinks.
Elements give structure to a HTML document and tells the browser how you want your website to be presented. Generally elements consists of a start tag, some content, and an end tag.
All tags have the same format: they begin with a less-than sign and end with a greater-than sign >.
Generally speaking, there are two kinds of tags - opening tags: opening and closing tags. The only difference between an opening tag and a closing tag is the forward slash "/". You label content by putting it between an opening tag and a closing tag.
This video gives a good overview of HTML tags.
Making Links in HTML is easy and a cool way to reference url’s to words in texts HTML Attributes use a tag ATTR = “ value”> contents tag format. Using the anchor A with href attribute name and a url for the value links the url to the contents that follow before the closed tag.This video gives a good explanation on how to make links
All Whitespace is entered in a single line. There is a way to have line breaks by using (b) void tags. Another way is by using (p) tag that has contact. Why do we have a way of making two lines? The (br) tag is what we call inline while the (p) tag is what we call block. The br tag is just ending a line. The p tag makes an invisible box and has length and width associated with it. this video gives a good explanation of inline/block.
Two other elements that are important are span and div. With these two elements you can attach styles to them to adjust different behaviors of how text styles or how it’s displayed. the big difference between the twois Span is an inline element while div is block element.
this video gives good explanation on span/div.
The "tree-like structure" comes from the fact that HTML elements can have other elements inside of them. In a browser, this structure shows up as a series of nested boxes. There are boxes inside of boxes inside of boxes, and so on... Here is an example of a "Tree-like Structure"
When writing code, programmers use special text editors (like Sublime Text for example). These editors make the programmer's life easier. For example, some text editors will automatically generate a closing HTML tag when you write an opening tag. When you read an HTML document as text, you see a wave of changing indentations going up and down the left side of the document. The more indented an element is, the more deeply nested it's corresponding "box" is.
CSS stands for Cascading Style Sheets. CSS is code written to control the "style" of HTML elements. It is important to avoid repetition with CSS a programmer must find similarity and use abstraction to avoid unnecessary repetition of work.


Interview Platform - Administrator
Sign Out
Quick Links
Profile
Event History
Create Event
Schedule Inteview
Change Password
Select an event
#
Candidate Name
1
Column content
Approve


Bold Girl Slaying in Red Hot Bikini
by AkhilBold girl, Akshara Gowda who told us that she wasn’t averse to skin show and performing bold skin through her recent Telugu outing ‘Manamadhudu 2’ with Akkineni Nagarjuna is playing social media platforms with her sexy pics.
This red hot bikini pic is from her recent shoot where one is left to think that even the waters must have turned hotter immersing half the sensual body of this sexy girl. That sexy twist of her lips is adding more hotness.
Akshara Gowda is popular for her bold pics on social media platforms. Though her Telugu film was a disappointment, Akshara’s boldness didn’t go unnoticed. Won’t you agree with us, guys?


Kodachadri Karanataka KP 2 test Kumar parvatha (western ghats) Karnataka Himalayas TBD Kedar TBD Kedarkantha trek (himalayas) A trek intro Non-Fiction books Best of the books I have read (and recommend) in that corresponding year: 2019 (so far) The Art of Thinking Clearly by Rolf Dobelli 2018 The Structure of Scientific Revolutions by Thomas S. Kuhn 2017 The philosophy of Jean-Paul Sartre by Jean-Paul Sartre 2016 Sapiens: A Brief History of Humankind by Yuval Noah Harari 2015 Zero to One: Notes on Startups, or How to Build the Future by Peter Thiel 2014 Thinking, Fast and Slow by Daniel Kahneman 2013 The Audacity of Hope by Barack Obama 2012 Surely You're Joking, Mr. Feynman! by Richard Feynman 2011 A Brief History of Time by Stephen Hawking


The following document contains the results of Checkstyle 5.7.
| Category | Rule | Violations | Severity |
|---|---|---|---|
| blocks | EmptyBlock | 1 | Error |
| NeedBraces | 7 | Error | |
| coding | HiddenField | 9 | Error |
| MagicNumber | 13 | Error | |
| design | DesignForExtension | 25 | Error |
| HideUtilityClassConstructor | 6 | Error | |
| VisibilityModifier | 1 | Error | |
| javadoc | JavadocMethod | 54 | Error |
JavadocPackage
|
3 | Error | |
| JavadocStyle | 1 | Error | |
| JavadocType | 14 | Error | |
| JavadocVariable | 16 | Error | |
| misc | FinalParameters | 48 | Error |
| NewlineAtEndOfFile | 1 | Error | |
| naming | ConstantName | 1 | Error |
| StaticVariableName | 1 | Error | |
| regexp | RegexpSingleline
|
7 | Error |
| sizes | LineLength | 47 | Error |
| whitespace | FileTabCharacter
|
246 | Error |
| WhitespaceAfter | 1 | Error |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 14 |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 14 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 85). | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 20 |
| Error | misc | FinalParameters | Parameter is should be final. | 20 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | coding | MagicNumber | '8192' is a magic number. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 26 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 30 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 32 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 121). | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 36 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 37 |
| Error | misc | FinalParameters | Parameter is should be final. | 37 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 39 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 40 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 41 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 41 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 42 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 43 |
| Error | misc | FinalParameters | Parameter is should be final. | 43 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 44 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 45 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 46 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 47 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 48 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 49 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 50 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 51 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 52 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 53 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocPackage | Missing package-info.java file. | |
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 88). | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 23 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 138). | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Error | misc | FinalParameters | Parameter o should be final. | 34 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 37 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 38 |
| Error | misc | FinalParameters | Parameter filename should be final. | 38 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 39 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 39 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 85). | 40 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 40 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 42 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 98). | 43 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 43 |
| Error | misc | FinalParameters | Parameter bytes should be final. | 43 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 104). | 44 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 44 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 107). | 45 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 45 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 46 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 47 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 48 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 49 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 50 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 51 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 3 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 4 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 4 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 5 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 5 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 6 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 6 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 7 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 7 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 9 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 9 |
| Error | misc | FinalParameters | Parameter host should be final. | 9 |
| Error | coding | HiddenField | 'host' hides a field. | 9 |
| Error | misc | FinalParameters | Parameter port should be final. | 9 |
| Error | coding | HiddenField | 'port' hides a field. | 9 |
| Error | misc | FinalParameters | Parameter quietTimeoutMs should be final. | 9 |
| Error | coding | HiddenField | 'quietTimeoutMs' hides a field. | 9 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 10 |
| Error | misc | FinalParameters | Parameter reconnectDelayMs should be final. | 10 |
| Error | coding | HiddenField | 'reconnectDelayMs' hides a field. | 10 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | design | DesignForExtension | Method 'getHost' is not designed for extension - needs to be abstract, final or empty. | 17 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | design | DesignForExtension | Method 'getPort' is not designed for extension - needs to be abstract, final or empty. | 21 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 23 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | design | DesignForExtension | Method 'getQuietTimeoutMs' is not designed for extension - needs to be abstract, final or empty. | 25 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 26 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | design | DesignForExtension | Method 'getReconnectDelayMs' is not designed for extension - needs to be abstract, final or empty. | 29 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 29 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 30 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 33 |
| Error | misc | FinalParameters | Parameter host should be final. | 33 |
| Error | misc | FinalParameters | Parameter port should be final. | 33 |
| Error | misc | FinalParameters | Parameter quietTimeoutMs should be final. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Error | misc | FinalParameters | Parameter reconnectDelayMs should be final. | 34 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | WhitespaceAfter | ',' is not followed by whitespace. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 36 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 8 |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 8 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 10 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 10 |
| Error | misc | FinalParameters | Parameter args should be final. | 10 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 84). | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 12 |
| Error | coding | MagicNumber | '9010' is a magic number. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 5 |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 5 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 7 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 9 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 9 |
| Error | misc | FinalParameters | Parameter t should be final. | 9 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 93). | 10 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 10 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 11 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | sizes | LineLength | Line is longer than 80 characters (found 88). | 11 |
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 11 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 13 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 14 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 16 |
| Error | misc | FinalParameters | Parameter is should be final. | 16 |
| Error | coding | HiddenField | 'is' hides a field. | 16 |
| Error | misc | FinalParameters | Parameter size should be final. | 16 |
| Error | coding | HiddenField | 'size' hides a field. | 16 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 83). | 27 |
| Error | misc | FinalParameters | Parameter is should be final. | 27 |
| Error | coding | HiddenField | 'is' hides a field. | 27 |
| Error | misc | FinalParameters | Parameter observer should be final. | 27 |
| Error | blocks | NeedBraces | 'if' construct must use '{}'s. | 31 |
| Error | blocks | NeedBraces | 'if' construct must use '{}'s. | 33 |
| Error | blocks | NeedBraces | 'else' construct must use '{}'s. | 35 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 43 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 9 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 11 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 13 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 13 |
| Error | misc | FinalParameters | Parameter t should be final. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | design | DesignForExtension | Method 'call' is not designed for extension - needs to be abstract, final or empty. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 87). | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | misc | FinalParameters | Parameter n should be final. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 26 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 30 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 32 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 10 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 12 |
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 13 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 14 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 16 |
| Error | misc | FinalParameters | Parameter reader should be final. | 16 |
| Error | coding | HiddenField | 'reader' hides a field. | 16 |
| Error | misc | FinalParameters | Parameter size should be final. | 16 |
| Error | misc | FinalParameters | Parameter reader should be final. | 27 |
| Error | coding | HiddenField | 'reader' hides a field. | 27 |
| Error | misc | FinalParameters | Parameter observer should be final. | 27 |
| Error | blocks | NeedBraces | 'if' construct must use '{}'s. | 30 |
| Error | blocks | NeedBraces | 'else' construct must use '{}'s. | 32 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 40 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | extension | TreeWalker | Got an exception - expecting EOF, found '}' | 38 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 9 |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 9 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 11 |
| Error | naming | ConstantName | Name 'log' must match pattern '^[A-Z][A-Z0-9]*(_[A-Z0-9]+)*$'. | 11 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 13 |
| Error | misc | FinalParameters | Parameter e should be final. | 17 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 34 |
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 46 |
| Error | extension | TreeWalker | Got an exception - expecting EOF, found '}' | 56 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 38 |
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 121 |
| Error | extension | TreeWalker | Got an exception - expecting EOF, found 'socket' | 151 |
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 192 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 23 |
| Error | design | DesignForExtension | Method 'testLinesFromARegularlyEmittingSource' is not designed for extension - needs to be abstract, final or empty. | 24 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 24 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 85). | 25 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 99). | 26 |
| Error | coding | MagicNumber | '1000000' is a magic number. | 26 |
| Error | misc | FinalParameters | Parameter n should be final. | 28 |
| Error | coding | MagicNumber | '100' is a magic number. | 31 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 93). | 43 |
| Error | coding | MagicNumber | '1000' is a magic number. | 43 |
| Error | coding | MagicNumber | '1000' is a magic number. | 43 |
| Error | coding | MagicNumber | '5' is a magic number. | 44 |
| Error | coding | MagicNumber | '1000' is a magic number. | 47 |
| Error | design | DesignForExtension | Method 'testSocketObservableFactoryOnException' is not designed for extension - needs to be abstract, final or empty. | 50 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 50 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 83). | 54 |
| Error | design | DesignForExtension | Method 'testSocketDisposerOnException' is not designed for extension - needs to be abstract, final or empty. | 57 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 57 |
| Error | coding | MagicNumber | '1234' is a magic number. | 63 |
| Error | design | DesignForExtension | Method 'testSocketCreatorThrowsException' is not designed for extension - needs to be abstract, final or empty. | 68 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 68 |
| Error | coding | MagicNumber | '1234' is a magic number. | 70 |
| Error | coding | MagicNumber | '5000' is a magic number. | 70 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 10 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 12 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 23 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 91). | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 84). | 26 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 26 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 30 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 32 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 85). | 34 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 36 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 37 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 40 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 40 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 41 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 42 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 136). | 44 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 44 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 44 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 46 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 47 |
| Error | misc | FinalParameters | Parameter o should be final. | 47 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 48 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 49 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 50 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 16 |
| Error | design | DesignForExtension | Method 'testNormal' is not designed for extension - needs to be abstract, final or empty. | 18 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 18 |
| Error | design | DesignForExtension | Method 'testNormalWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 25 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 25 |
| Error | design | DesignForExtension | Method 'testEmptyProducesNothing' is not designed for extension - needs to be abstract, final or empty. | 32 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 32 |
| Error | design | DesignForExtension | Method 'testEmptyProducesNothingWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 39 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 39 |
| Error | design | DesignForExtension | Method 'testBlankProducesSingleBlank' is not designed for extension - needs to be abstract, final or empty. | 46 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 46 |
| Error | design | DesignForExtension | Method 'testBlankProducesBlankWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 53 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 53 |
| Error | design | DesignForExtension | Method 'testNoSeparatorProducesSingle' is not designed for extension - needs to be abstract, final or empty. | 60 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 60 |
| Error | design | DesignForExtension | Method 'testNoSeparatorProducesSingleWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 67 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 67 |
| Error | design | DesignForExtension | Method 'testSeparatorOnlyProducesTwoBlanks' is not designed for extension - needs to be abstract, final or empty. | 74 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 74 |
| Error | design | DesignForExtension | Method 'testSeparatorOnlyProducesTwoBlanksWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 81 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 81 |
| Error | design | DesignForExtension | Method 'testEmptyItemsAtEndEmitted' is not designed for extension - needs to be abstract, final or empty. | 88 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 88 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 84). | 91 |
| Error | design | DesignForExtension | Method 'testEmptyItemsAtEndEmittedWithBackpressure' is not designed for extension - needs to be abstract, final or empty. | 95 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 95 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 84). | 98 |
| Error | design | DesignForExtension | Method 'testSplitOperatorDoesNotStallDueToInsufficientUpstreamRequests' is not designed for extension - needs to be abstract, final or empty. | 102 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 102 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 103 |
| Error | design | DesignForExtension | Method 'testBackpressureOneByOneWithBufferEmissions' is not designed for extension - needs to be abstract, final or empty. | 109 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 109 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 92). | 124 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 124 |
| Error | misc | FinalParameters | Parameter o should be final. | 124 |
| Error | misc | FinalParameters | Parameter expected should be final. | 124 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 131 |
| Error | misc | FinalParameters | Parameter o should be final. | 131 |
| Error | misc | FinalParameters | Parameter expected should be final. | 131 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 96). | 132 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 93). | 137 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 137 |
| Error | misc | FinalParameters | Parameter e should be final. | 152 |
| Error | misc | FinalParameters | Parameter s should be final. | 158 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocPackage | Missing package-info.java file. | |
| Error | javadoc | JavadocStyle | First sentence should end with a period. | 10 |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 16 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 18 |
| Error | naming | StaticVariableName | Name 'TRIM' must match pattern '^[a-z][a-zA-Z0-9]*$'. | 23 |
| Error | design | VisibilityModifier | Variable 'TRIM' must be private and have accessor methods. | 23 |
| Error | misc | FinalParameters | Parameter input should be final. | 26 |
| Error | blocks | NeedBraces | 'if' construct must use '{}'s. | 27 |
| Error | blocks | NeedBraces | 'else' construct must use '{}'s. | 29 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 34 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 39 |
| Error | misc | FinalParameters | Parameter reader should be final. | 39 |
| Error | coding | MagicNumber | '8192' is a magic number. | 40 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 43 |
| Error | misc | FinalParameters | Parameter reader should be final. | 43 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 93). | 44 |
| Error | coding | MagicNumber | '8192' is a magic number. | 44 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 47 |
| Error | misc | FinalParameters | Parameter file should be final. | 47 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 85). | 48 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 51 |
| Error | misc | FinalParameters | Parameter file should be final. | 51 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 55 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 55 |
| Error | misc | FinalParameters | Parameter o should be final. | 55 |
| Error | misc | FinalParameters | Parameter pattern should be final. | 55 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 123). | 59 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 59 |
| Error | misc | FinalParameters | Parameter o should be final. | 59 |
| Error | misc | FinalParameters | Parameter maxItemLength should be final. | 59 |
| Error | misc | FinalParameters | Parameter pattern should be final. | 59 |
| Error | misc | FinalParameters | Parameter maxPatternLength should be final. | 59 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 112). | 60 |
| Error | regexp | RegexpSingleline | Line has trailing spaces. | 63 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 83). | 64 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 64 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 88). | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 23 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 138). | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 34 |
| Error | misc | FinalParameters | Parameter o should be final. | 34 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 82). | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 37 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 38 |
| Error | misc | FinalParameters | Parameter filename should be final. | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 39 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 40 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 41 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 42 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 43 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | javadoc | JavadocType | Missing a Javadoc comment. | 7 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 9 |
| Error | design | DesignForExtension | Method 'testTrim' is not designed for extension - needs to be abstract, final or empty. | 9 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 9 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 10 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 81). | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 11 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 14 |
| Error | design | DesignForExtension | Method 'testTrimOnNullInputReturnsNull' is not designed for extension - needs to be abstract, final or empty. | 14 |
| Error | javadoc | JavadocMethod | Missing a Javadoc comment. | 14 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 17 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | extension | TreeWalker | Got an exception - expecting EOF, found '}' | 13 |
| Severity | Category | Rule | Message | Line |
|---|---|---|---|---|
| Error | misc | NewlineAtEndOfFile | File does not end with a newline. | |
| Error | javadoc | JavadocPackage | Missing package-info.java file. | |
| Error | design | HideUtilityClassConstructor | Utility classes should not have a public or default constructor. | 10 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 12 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 13 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 13 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 15 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 16 |
| Error | javadoc | JavadocVariable | Missing a Javadoc comment. | 16 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 18 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 19 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 20 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 21 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 22 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 23 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 24 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 25 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 26 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 27 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 28 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 29 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 30 |
| Error | sizes | LineLength | Line is longer than 80 characters (found 86). | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 31 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 32 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 33 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 35 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 36 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 37 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 38 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 39 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 40 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 41 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 42 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 43 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 44 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 45 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 46 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 47 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 48 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 49 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 50 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 51 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 52 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 53 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 54 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 55 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 56 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 57 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 58 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 59 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 60 |
| Error | blocks | EmptyBlock | Must have at least one statement. | 60 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 61 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 62 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 63 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 64 |
| Error | whitespace | FileTabCharacter | Line contains a tab character. | 65 |


Please expect 24 hours for inquiry response.
Current
As part of Current's complete rebrand initiative, the financial technology company sought to overhaul its website design to align with its new brand identity, created by world-renowned agency, Collins.
Current engaged Jae Yoon Studio as its website design partner, to help them with content strategy, UX, visual design and motion prototypes.
Given the complexity of the project with multiple dependencies and deliverables, it was crucial to create a lean project timeline that was versatile enough to accommodate unexpected changes and could still expedite the start of development.
To maintain strong progress throughout the engagement while making the best use of development resources, we provided the following annotated timeline.
As one of the initial steps of the project, we created an information architecture around Current's vast array of offerings. This was an important step as it allowed us to create a clear and concise hierarchy of products and offerings, which would ultimately serve as the backbone of the marketing website.
With a clear sense of product hierarchy, customers could easily navigate the website and understand the various offerings without feeling overwhelmed or confused.
“I love everything about this.”
“This is so much better than what we had. You have translated everything into an elegant website design system.”


Copyright (c) 2002 L. Lynn Smith
The game is played on the following board:
|
| An example The last moved stone was the blue at b4. The next player does not have many options. The red at a3 and the blue at d2 cannot move. If blue b3-a4, then c4-b3 and win with a line of green stones. If red c2-c1, then win with green d3-c2. Two possible moves are black b2-a1 or green c4-d4. |


SV gives you a chance to quickly and easily find the phone you want and have it delivered to your home in no time, regardless of your location.
Collective experience of our team members and the years we have spent in the business allowed us to develop a vast network of suppliers, ensuring that our customers will always find what they are looking for. This also means that we are able to offer great prices, which are constantly being updated and follow the shifts in the market.
Our affordability, fast and reliable delivery, and the fact that you will always be able to find the phone that you are looking for in our offer, have made us stand out in the market, but they are simply symptoms of our dedication to what we are doing and our desire to constantly keep improving. We know that in order to do that, we need to keep in close touch with our customers and listen to their suggestions and critiques. This is why our customer service, which is always there to answer any question that you may have, is just as willing to listen as it is to inform.


Arrested is a framework for rapidly building REST APIs with Flask.
Receive updates on new releases and upcoming projects.


{% extends 'base.html' %} {% load crispy_forms_tags %} {% block title %} MedTrack {% endblock %} {% block content %}
Once you enter your name and location, patients that send SMS messages to our number will obtain your contact information.
You can then send reminder messages and request periodic updates on their condition.
{% crispy form %}


A Simple Wish (1997)
A movie review by Michael J. Legeros Copyright 1997 by Michael J. Legeros
(Univesal) Directed by Michael Ritchie Written by Jeff Rothberg Cast Mara Wilson, Martin Short, Kathleen Turner, Francis Capra, Robert Pastorelli, Amanda Plummer, Teri Garr, Ruby Dee MPAA Rating "PG" Running Time 90 minutes Reviewed at The Imperial, Cary, NC (11JUL97)
==
A SIMPLE WISH is well-cast, I'll give it that. Martin Short is the perfect choice for a bumbling fairy godmother (hey, it's the nine- ties) who botches his first assignment, granting a wish to a little girl (Myra Wilson) whose father (Robert Pastorelli) is an aspiring New York City stage actor. And who else would you want but Kathleen Turner as the evil godmother-turned-Wicked Witch of the West Side, out to claim his (and every other good witch's) wand? Short is, at times, passable, but Ms. Turner is great fun. Her character gets the shaft on screen time, though, and that's a loss.  (Okay, okay, there *is* an inspired encounter between Short, Wilson, and a Nebraska redneck, but that's about it.) One hour was more than enough for me. I left around the time that a character began vomiting computer-generated frogs. Did I miss a scene of someone farting fish?
Grade: W/O
--
Mike Legeros - Movie Hell http://www.nonvirtual.com/hell/
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


Contact Information
Phone Number:<PHONE_NUMBER>
<EMAIL_ADDRESS>Located in Independence Oregon


let name = 'Jane';
What process does the code above perform?
let name;
What process does the code above perform?
Which operator is used to perform variable assignment?
let groceries = ["apples", "potatoes", "milk"];
What is the above groceries variable?
let age = 30;
if (age > 30) {
console.log("older than 30");
} else {
console.log("younger than 30");
}
Predict what will happen in the above example. Which console.logs will actually print?
let groceries = ["apples", "potatoes", "milk"];
Which of the following are the correct ways to access the value of "milk" in the above groceries array?
let puppies = ["Laser", "Katy", "Jet", "Layla"];
What is the value we'd receive if we read the value at puppies[1]?
function potatoSpeak() {
console.log("I am potato!");
}
function sadSpeak() {
console.log("I am NOT potato :(");
}
function isThisPotato(word) {
if (word === "potato") {
potatoSpeak();
} else {
sadSpeak();
}
}
In the code snippet above we have written a function that accepts one word and if that word is "potato" the potatoSpeak function is called - otherwise the sadSpeak function is called. The condition inside the isThisPotato function above is an example of what kind of conditional?
console.log(25 % 2 === 0);
What will the code above print out?
console.log(42 === '42');
What will the code above print out?
console.log(true || (4 / 2 === 0 && !false));
What will the code above print out?
console.log(42 === 42);
What will the code above print out?
console.log(42 == '42');
What will the code above print out?
console.log(true && (4 + 2 === 5));
What will the code above print out?
console.log((24 > 3) && false);
What will the code above print out?
console.log(26 % 2 === 0);
What will the code above print out?


i find this whole project to be terribly disorganized. one place for the firmware another place for the hardware. too many heading and places to go to find things. and even not complete when i go there.
disorganized
Submitted by Guest on Sun, 30/10/2011 - 16:21»
Re: disorganized
I've always found this site difficult to navigate, especially upon my first visits, and does not do the project justice, although I assume that it would be very difficult to change it at this stage (is it Drupal?).
There is so much great and valuable info in here which can so easily be overlooked and lost, so I have to agree.
Re: disorganized
I also think its not easy to navigate through all the excellent information in this site, however if you take some time you will find it.
K7da, maybe you can propose a structure to the developers to help them out.
I also have a site for my projects and i totally understand that its very difficult to organize everthing, specially when time is short and you want to spend it in your project and not in website management.
nevertheless, i love this site, has helped me a lot !!
Re: disorganized
Thankyou k7da, pauldreed, sergegsx for your thoughts, we also agree that organisation could be improved and have some ideas, it would be great to have a list of the main stumbling blocks that you have come across and any suggestions you may have for how to improve it.
Re: disorganized
I always find the Recent activity panel confusing - it clearly records when there has been a change to the page, but on navigating to that page, its not always easy to see what the change was.
Is there scope for confusion on the right hand panel which has Recent activity at the top, and Recent comments at the bottom? Could change the titles at least, or try and consolidate where posting/comments are allowed (might overcome the recent few days problems of folk trying to document a build, but ending up creating new content).
On the forums, I not sure but it doesnt seem as though the last update / new topic always shows the latest date of change.
Re: disorganized
Thankyou for your suggestions Andy, Yes I need to look into the recent activity log because I tried to integrate the comment feed into the page update feed but it did not quite work and then other things overtook so I did not get a chance to finish it.
Re: disorganized
a few more suggestions:
- do not allow comments on every page. use the forum for discussions, then update the pages to which the discussions refer. if a page is specific to a particular hardware/firmware/software version, then note this in the page then ensure that page does not disappear. having comments on every page make the site *really* hard to follow.
- create a navigation hierarchy that is as simple as possible, but that will last at least a year or two of development. ensure that this navigation tree is on every web page.
- create an api page for emoncms. write this page before you write any code. the api page should explain how to upload and download data to emoncms. this defines how the system should behave, so it is the basis for unit tests, development, and documentation. keep a separate api page for each major release of emoncms, so if someone is stuck using and older version of emoncms they still get the docs. and anyone contemplating an upgrade can see exactly how the api has changed.
- more generally, create a design document for emoncms that describes the expected behavior for each major component of the system.
- create a page that has thumbnails of each emoncms visualization widget, linked to a description of how that widget is supposed to behave, how to install the widget, etc. this should be a part of the emoncms design document.
- if there are plugins to emoncms, require that any plugin is self-documenting (a la perl or python modules, or even phpbb modules). establish a simple but easily tested set of requirements so that anyone contributing knows exactly what is required before their plugin is accepted.
Re: disorganized
Thanks for the suggestions powermeister, when I get some more time I will really have a go at this.


Core Language Features
Richards
...
- OS kernel simulation benchmark, originally written in BCPL by Martin Richards (539 lines).
- property load/store, function/method calls
- code optimization, elimination of redundant code
Deltablue
...
- One-way constraint solver, originally written in Smalltalk by John Maloney and Mario Wolczko (880 lines).
- polymorphism
- OO-style programming
Raytrace
...
- Ray tracer benchmark based on code by Adam Burmister (904 lines).
- argument object, apply
- prototype library object, creation patter
Bit Operations
Memory and Garbage Collection
EarleyBoyer
...
- Classic Scheme benchmarks, translated to JavaScript by Florian Loitsch's Scheme2Js compiler (4684 lines).
- fast object creation, destruction
- closures, arguments object
Splay
...
- Data manipulation benchmark that deals with splay trees and exercises the automatic memory management subsystem (394 lines)
- fast object creation, destruction
SplayLatency
...
- The Splay test stresses the Garbage Collection subsystem of a VM. SplayLatency instruments the existing Splay code with frequent measurement checkpoints. A long pause between checkpoints is an indication of high latency in the GC. This test measures the frequency of latency pauses, classifies them into buckets and penalizes frequent long pauses with a low score.
- garbage Collection latency
Strings and Arrays
RegExp
...
- Regular expression benchmark generated by extracting regular expression operations from 50 of the most popular web pages (1761 lines).
- Regular Expressions
pdf.js
...
- Mozilla's PDF Reader, implemented in JavaScript. It measures decoding and interpretation time (33,056 lines).
- array and typed arrays manipulations
- math and bit operations, support for future language features (e.g. promises)
Virtual Machine
Mandreel
...
- Runs the 3D Bullet Physics Engine, ported from C++ to JavaScript via Mandreel (277,377 lines)
- emulation
GameBoy Emulator
...
- Emulates the portable console's architecture and runs a demanding 3D simulation, all in JavaScript (11,097 lines).
- emulation
Typescript
...
- Microsoft's TypeScript, compiler is a complex application. This test measures the time TypeScript takes to compile itself and is a proxy of how well a VM handles complex and sizable Javascript applications (25,918 lines).
- run complex, heavy applications
Compiler
MandreelLatency
...
- Similar to the SplayLatency test, this test instruments the Mandreel benchmark with frequent time measurement checkpoints. Since Mandreel stresses the VM's compiler, this test provides an indication of the latency introduced by the compiler. ong pauses between measurement checkpoints lower the final score.
- compiler latency
zlib
...
- The zlib asm.js/Emscripten test from the Mozilla Emscripten suite, running with workload 1. The code is enclosed in eval(), that guarantees that the running time we measure includes parsing and compilation on all browsers (2,585 lines).
- code compilation and execution


Selecting Views and Editors
To see a list of all views, from the menu bar choose Window > Show View > Others.
The following views comprise the C/C++ Projects View:Basic views
- Console
- Displays the application's output.
- Project Explorer
- Displays the file system under the launchdir/workspace directory.
- Outline
- Displays the functions and header files in your source files. Open a source file in an editor to view its outline.
- Problems
- Displays problems.
- Properties
- Displays the name, path, size, permissions, and last modified date of the resource highlighted in the Project Explorer view.
- Search
- Displays the results of file or text searches.
C views
- C/C++ Projects
- Displays your current projects. This is similar to the Project Explorer view.
Make views
- Make Targets
- Lists your projects. To build a project, double-click on it..
Editor view
The Editor view is not listed under Window > Show View or Window > Show View > Others, it is opened whenever an editable file is opened from the C/C++ Projects or Project Explorer views.


VAVICI VENTURES TEAM
Han S. Chiu, MD
Founder & Managing Partner
- Over 30 years of health care experience & 10 years of VC experience.
- Extensive experience working with top thought leaders.
- Successfully launched and managed pharmaceutical products at Novartis & Shering-Plough.
GET MORE INFO
Douglas Wall
Limited Partner
- Over 30 years experience with emerging technology and life science companies.
- Cofounder Mission Ventures, Shepherd Ventures, PureForge & Genea.
- Successfully raised over $1 billion in capital for private companies.
- Cofounder San Diego Tech Coast Angels and the San Diego Software Industry.
GET MORE INFO
James Sergi
Limited Partner
- Over 30 years of experience in healthcare marketing, medical education, & clinical trials.
- Founder & President CSSi LifeSciences, LLC.
- Partner Bay Tower Medical Group, LLC.
- Director, Department of Experimental Therapeutics, Cleveland Clinic.
- Founding executive and Former CEO of ProED Communications.
GET MORE INFO


geom_errorbar()
function
Error bars give a general idea of how precise a measurement is, or conversely, how far from the reported value the true (error free) value might be. If the value displayed on your barplot is the result of an aggregation (like the mean value of several data points), you may want to display error bars.
To understand how to build it, you first need to understand how to
build a
basic barplot
with R. Then, you just it to add an extra layer using the
geom_errorbar()
function.
The function takes at least 3 arguments in its aesthetics:
ymin
and ymax
: position of the bottom
and the top of the error bar respectively
x
: position on the X axisNote: the lower and upper limits of your error bars must be computed before building the chart, and available in a column of the input data.
# Load ggplot2
library(ggplot2)
# create dummy data
data <- data.frame(
name=letters[1:5],
value=sample(seq(4,15),5),
sd=c(1,0.2,3,2,4)
)
# Most basic error bar
ggplot(data) +
geom_bar( aes(x=name, y=value), stat="identity", fill="skyblue", alpha=0.7) +
geom_errorbar( aes(x=name, ymin=value-sd, ymax=value+sd), width=0.4, colour="orange", alpha=0.9, size=1.3)
It is possible to change error bar types thanks to similar function:
geom_crossbar()
, geom_linerange()
and
geom_pointrange()
. Those functions works basically the same
as the most common geom_errorbar()
.
# Load ggplot2
library(ggplot2)
# create dummy data
data <- data.frame(
name=letters[1:5],
value=sample(seq(4,15),5),
sd=c(1,0.2,3,2,4)
)
# rectangle
ggplot(data) +
geom_bar( aes(x=name, y=value), stat="identity", fill="skyblue", alpha=0.5) +
geom_crossbar( aes(x=name, y=value, ymin=value-sd, ymax=value+sd), width=0.4, colour="orange", alpha=0.9, size=1.3)
# line
ggplot(data) +
geom_bar( aes(x=name, y=value), stat="identity", fill="skyblue", alpha=0.5) +
geom_linerange( aes(x=name, ymin=value-sd, ymax=value+sd), colour="orange", alpha=0.9, size=1.3)
# line + dot
ggplot(data) +
geom_bar( aes(x=name, y=value), stat="identity", fill="skyblue", alpha=0.5) +
geom_pointrange( aes(x=name, y=value, ymin=value-sd, ymax=value+sd), colour="orange", alpha=0.9, size=1.3)
# horizontal
ggplot(data) +
geom_bar( aes(x=name, y=value), stat="identity", fill="skyblue", alpha=0.5) +
geom_errorbar( aes(x=name, ymin=value-sd, ymax=value+sd), width=0.4, colour="orange", alpha=0.9, size=1.3) +
coord_flip()
Three different types of values are commonly used for error bars, sometimes without even specifying which one is used. It is important to understand how they are calculated, since they give very different results (see above). Let’s compute them on a simple vector:
It represents the amount of dispersion of the variable. Calculated as the root square of the variance:
It is the standard deviation of the vector sampling distribution. Calculated as the SD divided by the square root of the sample size. By construction, SE is smaller than SD. With a very big sample size, SE tends toward 0.
This interval is defined so that there is a specified probability that a
value lies within it. It is calculated as t * SE
. Where
t
is the value of the Student???s t-distribution for a
specific alpha. Its value is often rounded to 1.96 (its value with a big
sample size). If the sample size is huge or the distribution not normal,
it is better to calculate the CI using the bootstrap method, however.
alpha=0.05
t=qt((1-alpha)/2 + .5, length(vec)-1) # tend to 1.96 if sample size is big enough
CI=t*se
After this short introduction, here is how to compute these 3 values for each group of your dataset, and use them as error bars on your barplot. As you can see, the differences can greatly influence your conclusions.
# Load ggplot2
library(ggplot2)
library(dplyr)
# Data
data <- iris %>% select(Species, Sepal.Length)
# Calculates mean, sd, se and IC
my_sum <- data %>%
group_by(Species) %>%
summarise(
n=n(),
mean=mean(Sepal.Length),
sd=sd(Sepal.Length)
) %>%
mutate( se=sd/sqrt(n)) %>%
mutate( ic=se * qt((1-0.05)/2 + .5, n-1))
# Standard deviation
ggplot(my_sum) +
geom_bar( aes(x=Species, y=mean), stat="identity", fill="forestgreen", alpha=0.5) +
geom_errorbar( aes(x=Species, ymin=mean-sd, ymax=mean+sd), width=0.4, colour="orange", alpha=0.9, size=1.5) +
ggtitle("using standard deviation")
# Standard Error
ggplot(my_sum) +
geom_bar( aes(x=Species, y=mean), stat="identity", fill="forestgreen", alpha=0.5) +
geom_errorbar( aes(x=Species, ymin=mean-se, ymax=mean+se), width=0.4, colour="orange", alpha=0.9, size=1.5) +
ggtitle("using standard error")
# Confidence Interval
ggplot(my_sum) +
geom_bar( aes(x=Species, y=mean), stat="identity", fill="forestgreen", alpha=0.5) +
geom_errorbar( aes(x=Species, ymin=mean-ic, ymax=mean+ic), width=0.4, colour="orange", alpha=0.9, size=1.5) +
ggtitle("using confidence interval")
arrows()
function
It is doable to add error bars with base R only as well, but
requires more work. In any case, everything relies on the
arrows()
function.
#Let's build a dataset : height of 10 sorgho and poacee sample in 3 environmental conditions (A, B, C)
data <- data.frame(
specie=c(rep("sorgho" , 10) , rep("poacee" , 10) ),
cond_A=rnorm(20,10,4),
cond_B=rnorm(20,8,3),
cond_C=rnorm(20,5,4)
)
#Let's calculate the average value for each condition and each specie with the *aggregate* function
bilan <- aggregate(cbind(cond_A,cond_B,cond_C)~specie , data=data , mean)
rownames(bilan) <- bilan[,1]
bilan <- as.matrix(bilan[,-1])
#Plot boundaries
lim <- 1.2*max(bilan)
#A function to add arrows on the chart
error.bar <- function(x, y, upper, lower=upper, length=0.1,...){
arrows(x,y+upper, x, y-lower, angle=90, code=3, length=length, ...)
}
#Then I calculate the standard deviation for each specie and condition :
stdev <- aggregate(cbind(cond_A,cond_B,cond_C)~specie , data=data , sd)
rownames(stdev) <- stdev[,1]
stdev <- as.matrix(stdev[,-1]) * 1.96 / 10
#I am ready to add the error bar on the plot using my "error bar" function !
ze_barplot <- barplot(bilan , beside=T , legend.text=T,col=c("blue" , "skyblue") , ylim=c(0,lim) , ylab="height")
error.bar(ze_barplot,bilan, stdev)
This post was an overview of ggplot2
barplots, showing the basic options of
geom_barplot()
. Visit the barplot section for more:


Beef
Chicken
Fish
Pork
Veggie
American
Spanish
Italian
Japanese
Greek
French
Indian
Mediterranean
Mexican
Vodka
Tequila
Whiskey
Gin
Rum
Bourbon


--- layout: post title: DRM date: 2006-09-14 00:00:00 category: digital-media ---
The greatest trick: "In many ways, the recording industry is the biggest dupe in the DRM wars. They have repeatedly been sold, and have repeatedly bought heavily into copy-prevention schemes that don’t work, can’t work, and only give more power to the DRM vendor."


--- title: "Reading a local file with the File API" layout: default section: example ---
Note : your browser will process the zip file, don't choose a file too big !


Living Room
Kitchen
bedroom
Bathroom
New Fall Collection
Check out our brand new fall items!
Shop NowFREE SHIPPING
On everything over $50.
AMAZING DEALS
Save up to 70% on high-quality furniture.
TOP CUSTOMER SERVCE
We're glad to help you pick the best item.


title = "AJAX framework" url = "/demo/ajax" layout = "default" is_hidden = 0 == ==
This built-in JavaScript framework provides simple but powerful AJAX capabilities. Check out the calculator example below.
Continue to Plugin components


Liquid's response to errors can be configured by setting error_mode
.
The options are
lax
— Ignore all errors.warn
— Output a warning on the console for each error. (default)strict
— Output an error message and stop the build.
Within _config.yml
, the default configuration is as follows:
liquid: error_mode: warn
The above example depicts the “warn” value, which is already set by default- error_mode: warn
.
This results in any issues being called out during the build process however will continue to build if possible.
You can also configure Liquid's renderer to catch non-assigned variables and non-existing filters
by setting strict_variables
and / or strict_filters
to true
respectively.
Do note that while error_mode
configures Liquid's parser,
the strict_variables
and strict_filters
options configure Liquid's renderer and are consequently orthogonal.
An example of setting these variables within _config.yml
is as follows:
liquid: error_mode: strict strict_variables: true strict_filters: true
Configuring as described above will stop your build/serve from happening and call out the offending error and halt. This is helpful when desiring to catch liquid-related issues by stopping the build or serve process and allowing you to deal with any issues.


Before Change
// instance by making sure that the largest value is positive.
// make data (SVD)
rng = np.random.RandomState(0)
shape = (20, 10, 1)
affine = np.eye(4)
components = _make_canica_components(shape)
// make +ve
for mp in components:
mp[rng.randn(*mp.shape) > .8] *= -5.
assert_less_equal(mp.max(), -mp.min()) // goal met ?
// synthesize data with given components
data = _make_data_from_components(components, affine, shape, rng=rng,
n_subjects=2)
mask_img = nibabel.Nifti1Image(np.ones(shape, dtype=np.int8), affine)
// run CanICA many times (this is known to produce different results)
canica = CanICA(n_components=4, random_state=rng, mask=mask_img)
After Change
// CanICA to have more positive values than negative values, for
// instance by making sure that the largest value is positive.
data, mask_img, components, rng = _make_canica_test_data(n_subjects=2,
noisy=True)
// run CanICA many times (this is known to produce different results)


Home
Menu 1
Menu 2
HOME
Some content.
Menu 1
Some content in menu 1.
Menu 2
Some content in menu 2.
previous
1
2
3
next


Simple Grid
The grid object below displays data loaded from a url in JSON format. As you see the grid is extremely simple to use and easy to enable more features and listen to events.You can define the size of the columns in % or px or both at the same time. When % and px are defined, it will first assign width to the columns defined in px, then it will calculate the size of the column in % based on the remaining px.


The initial creation and subsequent reconstitution for query retrieval purposes of both row and column keys in CloudGraph™ leverages byte array level API in both Java and the current underlying SDO 2.1 implementation, PlasmaSDO™. Both composite row and column keys are composed in part of structural metadata, and the lightweight metadata API within PlasmaSDO™ contains byte-array level, cached lookup of all basic metadata elements including logical and physical type and property names.


Nemerle has builtin syntax extension capabilities. They are limited to some fixed elements of language grammar, but their ability to defer parsing of entire fragments of token stream makes them quite powerful and usable.
We have mainly focused on ability of extending base syntacitc entity in Nemerle language, that is expression.
The new rules of parsing are triggered by the set of user definable distinguished keywords and operators. When the parser encounters one of those at the valid position of expression beginning, then it executes a special parsing procedure for syntax extension related to the distinguished token.
All syntax extensions are specified by Macros definitions. Each macro can optionally have syntax definition, which describes how given macro should be called when the syntax occurs in program. For example
macro while_macro (cond, body)
syntax ("while", "(", cond, ")", body) {
<[
def loop () {
when ($cond) {
$body;
loop ()
}
}
loop ()
]>
}
creates a macro introducing while loop construct and syntax to the language.
Nemerle has a very powerful method for introducing virtually arbitrary syntax into language. It allows for specifying that given part of program input will not be interpreted by main Nemerle parser, but will be passed in easy to use representation to some macro.
The parser and all syntax extensions operate on token streams created by the lexer and the so-called pre-parse stage. The lexing phase simply transforms program text into a stream of tokens (like identifiers, numbers, operators, distinguished keywords, etc.).
The next phase groups this stream into a tree of parentheses. We have distinguished four types of them ({} () [] ). Tokens inside those parentheses are also divided into groups separated by special separator tokens. For example the following program fragment
fun f (x : string) {
def y = System.Int32.Parse (x);
y + 1
}
is after the pre-parse stage represented as the token tree
'''[''' fun '','' f '','' '''(''' '''[''' x '','' ':' '','' string ''']''' ''')''' '','' '''{'''
'''[''' def '','' y '','' '=' '','' System '','' '.' '','' Int32 '','' '.' '','' Parse '','' '''(''' '''[''' x ''']''' ''')''' ''']''' '',''
'''[''' y '','' '+' '','' 1 ''']'''
'''}''' ''']'''
where matched parentheses groups are distinguished with () {} [] and their elements are separated with ,. Note that groups like () and {} contain tokens enclosed by [], which represents loose token groups - divisions of tokens split by separators (, for () [] and ; for {} ).
So, according to the description above we have following kinds of special tokens, which represents whole fragments of unparsed code:
- Token.BracesGroup - for { }
- Token.RoundGroup - for ( )
- Token.SquareGroup - for []
- Token.QuoteGroup - for , used in macro code quotation
- Token.LooseGroup - list of tokens grouped inside one of above brackets and separated by separator token specific for each of bracket kinds
All the available tokens produced by lexer can be viewed
here
Those raw grouping tokens can passed as a parameter of macro. We simply have to name it when specifying macro parameter:
macro BuildXml (group : Token)
syntax ("xml", group)
{
...
}
in code, where such a macro was imported we can use the new syntax:
foo () : void {
def doc = xml (<node name="foo">My name is foo</node>);
// macro produced some XmlNode for us, we can use it
print (doc.InnerXml);
}
Inside such macro we can use our own specialized parser. For example some small domain specific language can be embedded easily inside Nemerle program provided a simple syntax extension.


Warfarin
Monitoring
-
INR
-
documented in clincial notes
-
on warfarin
-
condition for which warfarin has been prescribed
-
target INR range
-
planned duration of treatmnet
-
brand of warfarin
-
-
Managing warfarin treatment
-
risk of bleeding greatest who have not received warfarin and in first 3 months
-
Any patient on warfarin should be aware of risks and early warning signs of bleeding
- followed closely to ensure INR not >3
-
for most people testing every 2,4,6,8 weekly depending
-
target = 2.5 for most (2-3)
-
prophlaxis/treatment VTE
-
AF
-
valvular heart disease
-
(mechanical valve dependent of type of valve)
-
-
duration = 13 wks for provoked DVT or PE
-
unprovoked = 13wk but indefinite use may be appropriate
-
AF, cardiomyopathy, valvular heard disease = indefinite
-
changes in INR
-
major changes in diet or etoh
- consistent proportion of vit K rich food(brocooli, spinach, cabbage)
-
drug interactoins
- plus interactions that don’t change INR and increase risk of bleeding; NSAIDS, aspriin, ssri
-
systemic or concurrent illness
-
CHF
- hepatic congestion
-
hypothyroidism
- decrease catabolism of vit K clotting factors
-
hyperthyroidism
- increase catabolism of vit k clotting factors
-
liver failure
-
-
non-adherence to dosage regime
- change in INR 2-5d after missed dose
-
unknown
-
-
computerised decision support > human
-
better control
-
fewer tests
-
-
stop antiplatelets if starting warfarin for anything other than complicated ACSwhere clopidogrel/aspriin short term may be useful in those with low bleeding risk
Drug interactions
Inhibit: increase risk of bleeding
-
Antibiotics
-
most
-
macrolides
-
metronidazole
-
quinolones
-
cotrimoxazole
-
-
antifungazole
-
fluconazole, miconazole
- including gel and vaginal preparations
-
-
SSRI
-
inhibit with platelet function
- increase risk without change INR
-
fluoxetine also inhibit warfarin metabolism
-
-
Antiplatelet
-
aspirin, clopidogrel, dipyridamole
- interfere priamry haemostasis
-
-
Amiodarone
-
NSAIDS
- direct mucozal injury
-
Paracetamol
-
direct interference with Vit K cycle
-
unlikely with short term use
-
Induction - increased thromboisis
-
rifampicin
-
St John’s wort
-
foods with high vit K content
bleeding risk
-
concomitant use of aspirin
-
polypharmacy - 7 or more medications
-
other comorbidities
-
rate of spontaneous intracranial haemorrhage >70yo = 0.15%
-
BAFTA = significantly lower risk of stroke, intracranial haemorrhage or arterial embolism but same risk of bleeding as aspirin
-
HAS BLED = ≥ 3 = high risk of bleeding
-
Hypertension (sbP >160)
-
abnormal renal and liver function (1each)
-
stroke (1)
-
bleeding
-
labile INR
-
elderly >65
-
Drugs or etoh (1 each)
-
max = 9
-
over anti-coagulation:
-
INR 5-9
-
stop warfarin
-
test daily until therapeutic
-
restart wiht reduced dose when INR \<5
-
Give vit K 1-2.5mg orally if INR fails to reduce or if high risk of serious bleeding
-
-
INR >9 without bleeding
-
stop
-
vit K 2.5-5mg orally
-
measure in 24hrs
-
restart at reduced dose when INR \<5
-
-
INR ≥ 9 with minor bleeding
-
stop
-
vit k 1-5mg
-
test daily
-
restart warfarin
-
-
major bleeding
-
stop
-
vit k 10mg slow IV
-
refer for factor replacement
-
Dabigatran
Indications
-
prevention of stroke in non-valvular atrial fibrillation
-
requires at least one other risk factor
-
previous TIA/Stroke
-
LVEF \< 40%
-
symptomatic heart failure
-
age ≥ 75uo
-
age ≥ 65 + DM or HTN or CAD
-
-
NOT indicated valvular heart disease or mechanical heart valves
-
NOT been evaluated with bioprosthetic valves
-
-
VTE prophlaxis after major orthopaedic surgery
-
(treatment of VTE)
-
contraindicated with ketoconazole
Dosing
-
150mg bd provided CrCl >30mL/min
-
110mg bd aged ≥ 80yo
-
aged 75-80 with CrCl 30-50 consider 110mg bd: if risk of bleeding high and risk of thrombosis low
-
for VTE prophlaxis
-
220mg OD CrCl >50
-
150mg OD Cr 30-50
-
advantages over warfarin
-
more convient
-
effective anti-coagulation in those who previously difficult to ontrol on warfarin
- assuming adherence good
-
fewer drug and dietary interactions than warfarin
-
reduction in risk of intracranial haemorrhage
initiating
-
all patients should have assessment of renal function
- CI in CrCl\<30
-
if already anti-coagulated
-
warfarin stopped
-
started when INR \<2
-
-
Change back - warfarin
-
check CrCl
-
if >50mL/min warfarin started 3 days prior before discontinuing dabigatran
-
if 30-50mL intiiate warfarin 2 days before stopping dabigatran
-
-
-
stopping prior to planned surgical procedure
-
CrCl >50
-
24hours prior
-
or 48hrs if high risk of bleeding/major
-
-
30-50
- 2-4 days - action prolonged
-
Monitoring
-
renal function
-
initiation
-
change in clincial situation
-
annually >75
-
annually (but pref 3-6mo) cr cl 30-50
-
-
wide therapeutic window, predictable pharmacokinetics and pharmacodynamic
-
rapid onset of action
-
if bleeding
-
stop
-
Thrombin time
-
activated partial thromboplastin time
-
fibrinogen
-
ecarin clotting time
-
-
Adverse effects
-
non-haemorrhagic GI adverse effects = most frequent
-
dyspepsia
-
treat with PPI
- not significant interaction
-
-
-
bleeding
-
can be minimised
-
correct dose
-
inr \<2 on initiation
-
used in caution with other medicines that increase bleeding
-
-


Comet parameter: override_charge
- This parameter specifies the whether to override existing precursor
charge state information when present in the files with the charge
range specified by the
"precursor_charge" parameter.
- Valid values are 0 and 1.
- To keep any known charge state values in the input files,
set the value to 0.
- To ignore any known charge values in the input files and instead
use the charge state range specified by the
"precursor_charge" parameter,
set the value to 1.
- The default value is "0" if this parameter is missing.
Example:
override_charge = 0
override_charge = 1