PCREGREP
Section: User Commands (1)Index Return to Main Contents
NAME
pcregrep - a grep with Perl-compatible regular expressions.SYNOPSIS
pcregrep [options] [long options] [pattern] [path1 path2 ...]DESCRIPTION
pcregrep searches files for character patterns, in the same way as other grep commands do, but it uses the PCRE regular expression library to support patterns that are compatible with the regular expressions of Perl 5. See pcrepattern(3) for a full description of syntax and semantics of the regular expressions that PCRE supports. Patterns, whether supplied on the command line or in a separate file, are given without delimiters. For example:
pcregrep Thursday /etc/motd
If you attempt to use delimiters (for example, by surrounding a pattern with slashes, as is common in Perl scripts), they are interpreted as part of the pattern. Quotes can of course be used to delimit patterns on the command line because they are interpreted by the shell, and indeed they are required if a pattern contains white space or shell metacharacters. The first argument that follows any option settings is treated as the single pattern to be matched when neither -e nor -f is present. Conversely, when one or both of these options are used to specify patterns, all arguments are treated as path names. At least one of -e, -f, or an argument pattern must be provided. If no files are specified, pcregrep reads the standard input. The standard input can also be referenced by a name consisting of a single hyphen. For example:
pcregrep some-pattern /file1 - /file3
By default, each line that matches a pattern is copied to the standard output, and if there is more than one file, the file name is output at the start of each line, followed by a colon. However, there are options that can change how pcregrep behaves. In particular, the -M option makes it possible to search for patterns that span line boundaries. What defines a line boundary is controlled by the -N (--newline) option. Patterns are limited to 8K or BUFSIZ characters, whichever is the greater. BUFSIZ is defined in <stdio.h>. When there is more than one pattern (specified by the use of -e and/or -f), each pattern is applied to each line in the order in which they are defined, except that all the -e patterns are tried before the -f patterns. As soon as one pattern matches (or fails to match when -v is used), no further patterns are considered. When --only-matching, --file-offsets, or --line-offsets is used, the output is the part of the line that matched (either shown literally, or as an offset). In this case, scanning resumes immediately following the match, so that further matches on the same line can be found. If there are multiple patterns, they are all tried on the remainder of the line. However, patterns that follow the one that matched are not tried on the earlier part of the line. If the LC_ALL or LC_CTYPE environment variable is set, pcregrep uses the value to set a locale when calling the PCRE library. The --locale option can be used to override this.
SUPPORT FOR COMPRESSED FILES
It is possible to compile pcregrep so that it uses libz or libbz2 to read files whose names end in .gz or .bz2, respectively. You can find out whether your binary has support for one or both of these file types by running it with the --help option. If the appropriate support is not present, files are treated as plain text. The standard input is always so treated.
OPTIONS
- --
- This terminate the list of options. It is useful if the next item on the command line starts with a hyphen but is not an option. This allows for the processing of patterns and filenames that start with hyphens.
- -A number, --after-context=number
- Output number lines of context after each matching line. If filenames and/or line numbers are being output, a hyphen separator is used instead of a colon for the context lines. A line containing "--" is output between each group of lines, unless they are in fact contiguous in the input file. The value of number is expected to be relatively small. However, pcregrep guarantees to have up to 8K of following text available for context output.
- -B number, --before-context=number
- Output number lines of context before each matching line. If filenames and/or line numbers are being output, a hyphen separator is used instead of a colon for the context lines. A line containing "--" is output between each group of lines, unless they are in fact contiguous in the input file. The value of number is expected to be relatively small. However, pcregrep guarantees to have up to 8K of preceding text available for context output.
- -C number, --context=number
- Output number lines of context both before and after each matching line. This is equivalent to setting both -A and -B to the same value.
- -c, --count
- Do not output individual lines; instead just output a count of the number of lines that would otherwise have been output. If several files are given, a count is output for each of them. In this mode, the -A, -B, and -C options are ignored.
- --colour, --color
- If this option is given without any data, it is equivalent to "--colour=auto". If data is required, it must be given in the same shell item, separated by an equals sign.
- --colour=value, --color=value
- This option specifies under what circumstances the part of a line that matched a pattern should be coloured in the output. The value may be "never" (the default), "always", or "auto". In the latter case, colouring happens only if the standard output is connected to a terminal. The colour can be specified by setting the environment variable PCREGREP_COLOUR or PCREGREP_COLOR. The value of this variable should be a string of two numbers, separated by a semicolon. They are copied directly into the control string for setting colour on a terminal, so it is your responsibility to ensure that they make sense. If neither of the environment variables is set, the default is "1;31", which gives red.
- -D action, --devices=action
- If an input path is not a regular file or a directory, "action" specifies how it is to be processed. Valid values are "read" (the default) or "skip" (silently skip the path).
- -d action, --directories=action
- If an input path is a directory, "action" specifies how it is to be processed. Valid values are "read" (the default), "recurse" (equivalent to the -r option), or "skip" (silently skip the path). In the default case, directories are read as if they were ordinary files. In some operating systems the effect of reading a directory like this is an immediate end-of-file.
- -e pattern, --regex=pattern, --regexp=pattern
- Specify a pattern to be matched. This option can be used multiple times in order to specify several patterns. It can also be used as a way of specifying a single pattern that starts with a hyphen. When -e is used, no argument pattern is taken from the command line; all arguments are treated as file names. There is an overall maximum of 100 patterns. They are applied to each line in the order in which they are defined until one matches (or fails to match if -v is used). If -f is used with -e, the command line patterns are matched first, followed by the patterns from the file, independent of the order in which these options are specified. Note that multiple use of -e is not the same as a single pattern with alternatives. For example, X|Y finds the first character in a line that is X or Y, whereas if the two patterns are given separately, pcregrep finds X if it is present, even if it follows Y in the line. It finds Y only if there is no X in the line. This really matters only if you are using -o to show the part(s) of the line that matched.
- --exclude=pattern
- When pcregrep is searching the files in a directory as a consequence of the -r (recursive search) option, any regular files whose names match the pattern are excluded. Subdirectories are not excluded by this option; they are searched recursively, subject to the --exclude_dir and --include_dir options. The pattern is a PCRE regular expression, and is matched against the final component of the file name (not the entire path). If a file name matches both --include and --exclude, it is excluded. There is no short form for this option.
- --exclude_dir=pattern
- When pcregrep is searching the contents of a directory as a consequence of the -r (recursive search) option, any subdirectories whose names match the pattern are excluded. (Note that the --exclude option does not affect subdirectories.) The pattern is a PCRE regular expression, and is matched against the final component of the name (not the entire path). If a subdirectory name matches both --include_dir and --exclude_dir, it is excluded. There is no short form for this option.
- -F, --fixed-strings
- Interpret each pattern as a list of fixed strings, separated by newlines, instead of as a regular expression. The -w (match as a word) and -x (match whole line) options can be used with -F. They apply to each of the fixed strings. A line is selected if any of the fixed strings are found in it (subject to -w or -x, if present).
- -f filename, --file=filename
- Read a number of patterns from the file, one per line, and match them against each line of input. A data line is output if any of the patterns match it. The filename can be given as "-" to refer to the standard input. When -f is used, patterns specified on the command line using -e may also be present; they are tested before the file's patterns. However, no other pattern is taken from the command line; all arguments are treated as file names. There is an overall maximum of 100 patterns. Trailing white space is removed from each line, and blank lines are ignored. An empty file contains no patterns and therefore matches nothing. See also the comments about multiple patterns versus a single pattern with alternatives in the description of -e above.
- --file-offsets
- Instead of showing lines or parts of lines that match, show each match as an offset from the start of the file and a length, separated by a comma. In this mode, no context is shown. That is, the -A, -B, and -C options are ignored. If there is more than one match in a line, each of them is shown separately. This option is mutually exclusive with --line-offsets and --only-matching.
- -H, --with-filename
- Force the inclusion of the filename at the start of output lines when searching a single file. By default, the filename is not shown in this case. For matching lines, the filename is followed by a colon and a space; for context lines, a hyphen separator is used. If a line number is also being output, it follows the file name without a space.
- -h, --no-filename
- Suppress the output filenames when searching multiple files. By default, filenames are shown when multiple files are searched. For matching lines, the filename is followed by a colon and a space; for context lines, a hyphen separator is used. If a line number is also being output, it follows the file name without a space.
- --help
- Output a help message, giving brief details of the command options and file type support, and then exit.
- -i, --ignore-case
- Ignore upper/lower case distinctions during comparisons.
- --include=pattern
- When pcregrep is searching the files in a directory as a consequence of the -r (recursive search) option, only those regular files whose names match the pattern are included. Subdirectories are always included and searched recursively, subject to the --include_dir and --exclude_dir options. The pattern is a PCRE regular expression, and is matched against the final component of the file name (not the entire path). If a file name matches both --include and --exclude, it is excluded. There is no short form for this option.
- --include_dir=pattern
- When pcregrep is searching the contents of a directory as a consequence of the -r (recursive search) option, only those subdirectories whose names match the pattern are included. (Note that the --include option does not affect subdirectories.) The pattern is a PCRE regular expression, and is matched against the final component of the name (not the entire path). If a subdirectory name matches both --include_dir and --exclude_dir, it is excluded. There is no short form for this option.
- -L, --files-without-match
- Instead of outputting lines from the files, just output the names of the files that do not contain any lines that would have been output. Each file name is output once, on a separate line.
- -l, --files-with-matches
- Instead of outputting lines from the files, just output the names of the files containing lines that would have been output. Each file name is output once, on a separate line. Searching stops as soon as a matching line is found in a file.
- --label=name
- This option supplies a name to be used for the standard input when file names are being output. If not supplied, "(standard input)" is used. There is no short form for this option.
- --line-offsets
- Instead of showing lines or parts of lines that match, show each match as a line number, the offset from the start of the line, and a length. The line number is terminated by a colon (as usual; see the -n option), and the offset and length are separated by a comma. In this mode, no context is shown. That is, the -A, -B, and -C options are ignored. If there is more than one match in a line, each of them is shown separately. This option is mutually exclusive with --file-offsets and --only-matching.
- --locale=locale-name
- This option specifies a locale to be used for pattern matching. It overrides the value in the LC_ALL or LC_CTYPE environment variables. If no locale is specified, the PCRE library's default (usually the "C" locale) is used. There is no short form for this option.
- -M, --multiline
- Allow patterns to match more than one line. When this option is given, patterns may usefully contain literal newline characters and internal occurrences of ^ and $ characters. The output for any one match may consist of more than one line. When this option is set, the PCRE library is called in "multiline" mode. There is a limit to the number of lines that can be matched, imposed by the way that pcregrep buffers the input file as it scans it. However, pcregrep ensures that at least 8K characters or the rest of the document (whichever is the shorter) are available for forward matching, and similarly the previous 8K characters (or all the previous characters, if fewer than 8K) are guaranteed to be available for lookbehind assertions.
- -N newline-type, --newline=newline-type
-
The PCRE library supports five different conventions for indicating
the ends of lines. They are the single-character sequences CR (carriage return)
and LF (linefeed), the two-character sequence CRLF, an "anycrlf" convention,
which recognizes any of the preceding three types, and an "any" convention, in
which any Unicode line ending sequence is assumed to end a line. The Unicode
sequences are the three just mentioned, plus VT (vertical tab, U+000B), FF
(form feed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and
PS (paragraph separator, U+2029).
When the PCRE library is built, a default line-ending sequence is specified. This is normally the standard sequence for the operating system. Unless otherwise specified by this option, pcregrep uses the library's default. The possible values for this option are CR, LF, CRLF, ANYCRLF, or ANY. This makes it possible to use pcregrep on files that have come from other environments without having to modify their line endings. If the data that is being scanned does not agree with the convention set by this option, pcregrep may behave in strange ways.
- -n, --line-number
- Precede each output line by its line number in the file, followed by a colon and a space for matching lines or a hyphen and a space for context lines. If the filename is also being output, it precedes the line number. This option is forced if --line-offsets is used.
- -o, --only-matching
- Show only the part of the line that matched a pattern. In this mode, no context is shown. That is, the -A, -B, and -C options are ignored. If there is more than one match in a line, each of them is shown separately. If -o is combined with -v (invert the sense of the match to find non-matching lines), no output is generated, but the return code is set appropriately. This option is mutually exclusive with --file-offsets and --line-offsets.
- -q, --quiet
- Work quietly, that is, display nothing except error messages. The exit status indicates whether or not any matches were found.
- -r, --recursive
- If any given path is a directory, recursively scan the files it contains, taking note of any --include and --exclude settings. By default, a directory is read as a normal file; in some operating systems this gives an immediate end-of-file. This option is a shorthand for setting the -d option to "recurse".
- -s, --no-messages
- Suppress error messages about non-existent or unreadable files. Such files are quietly skipped. However, the return code is still 2, even if matches were found in other files.
- -u, --utf-8
- Operate in UTF-8 mode. This option is available only if PCRE has been compiled with UTF-8 support. Both patterns and subject lines must be valid strings of UTF-8 characters.
- -V, --version
- Write the version numbers of pcregrep and the PCRE library that is being used to the standard error stream.
- -v, --invert-match
- Invert the sense of the match, so that lines which do not match any of the patterns are the ones that are found.
- -w, --word-regex, --word-regexp
- Force the patterns to match only whole words. This is equivalent to having \b at the start and end of the pattern.
- -x, --line-regex, --line-regexp
- Force the patterns to be anchored (each must start matching at the beginning of a line) and in addition, require them to match entire lines. This is equivalent to having ^ and $ characters at the start and end of each alternative branch in every pattern.
ENVIRONMENT VARIABLES
The environment variables LC_ALL and LC_CTYPE are examined, in that order, for a locale. The first one that is set is used. This can be overridden by the --locale option. If no locale is set, the PCRE library's default (usually the "C" locale) is used.
NEWLINES
The -N (--newline) option allows pcregrep to scan files with different newline conventions from the default. However, the setting of this option does not affect the way in which pcregrep writes information to the standard error and output streams. It uses the string "\n" in C printf() calls to indicate newlines, relying on the C I/O library to convert this to an appropriate sequence if the output is sent to a file.
OPTIONS COMPATIBILITY
The majority of short and long forms of pcregrep's options are the same as in the GNU grep program. Any long option of the form --xxx-regexp (GNU terminology) is also available as --xxx-regex (PCRE terminology). However, the --locale, -M, --multiline, -u, and --utf-8 options are specific to pcregrep.
OPTIONS WITH DATA
There are four different ways in which an option with data can be specified. If a short form option is used, the data may follow immediately, or in the next command line item. For example:
-f/some/file
-f /some/file
If a long form option is used, the data may appear in the same command line item, separated by an equals character, or (with one exception) it may appear in the next command line item. For example:
--file=/some/file
--file /some/file
Note, however, that if you want to supply a file name beginning with ~ as data in a shell command, and have the shell expand ~ to a home directory, you must separate the file name from the option, because the shell does not treat ~ specially unless it is at the start of an item. The exception to the above is the --colour (or --color) option, for which the data is optional. If this option does have data, it must be given in the first form, using an equals character. Otherwise it will be assumed that it has no data.
MATCHING ERRORS
It is possible to supply a regular expression that takes a very long time to fail to match certain lines. Such patterns normally involve nested indefinite repeats, for example: (a+)*\d when matched against a line of a's with no final digit. The PCRE matching function has a resource limit that causes it to abort in these circumstances. If this happens, pcregrep outputs an error message and the line that caused the problem to the standard error stream. If there are more than 20 such errors, pcregrep gives up.
DIAGNOSTICS
Exit status is 0 if any matches were found, 1 if no matches were found, and 2 for syntax errors and non-existent or inaccessible files (even if matches were found in other files) or too many matching errors. Using the -s option to suppress error messages about inaccessible files does not affect the return code.
SEE ALSO
pcrepattern(3), pcretest(1).
AUTHOR
Philip Hazel University Computing Service Cambridge CB2 3QH, England.
REVISION
Last updated: 08 March 2008 Copyright (c) 1997-2008 University of Cambridge.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- SUPPORT FOR COMPRESSED FILES
- OPTIONS
- ENVIRONMENT VARIABLES
- NEWLINES
- OPTIONS COMPATIBILITY
- OPTIONS WITH DATA
- MATCHING ERRORS
- DIAGNOSTICS
- SEE ALSO
- AUTHOR
- REVISION
This document was created by man2html, using the manual pages.
Time: 05:29:07 GMT, December 24, 2015


Madeleinology
Data
1
2
3
4
5
Recipe
Sweet
Salty
Sweet Madeleines
A few variations of the traditional French madeleines.
Plain
Raspberry Heart
Sliced Almonds Topping
Pine Nuts Topping
Cocoa
1/2 Cocoa
Cocoa nibs
Madeleines cooling down.
© 2019
Olivier Giulieri
.


AN-AWARD WINNING
ARCHITECTURE COMPANY
SATISFITATION CLIENTES
EMPLOYEES ONWORLDWIDE
PROJECTS COMPLETED ON 60 COUNTRIES


Introducing Share Your Farming Gear
Hi <<First Name>>,
my name is Andrew Oldfield and I'm the founder of Share Your Farming Gear, a new online marketplace for farm contracting services and farm machinery rental. We understand that you are a significant employer of contractors, and we'd like to assist you the next time you're looking to hire a contractor. What we offer is fast access to an ever growing Australia-wide database of contractors, allowing you to quickly compare different tenders for your work. Our mission is to make the market for machinery access more efficient - easier and more profitable for both the seller and purchaser of services.
Current Features
Our website currently facilitates tendering for contracting work. When you list any work you need done, we'll quickly provide you offers from multiple contractors interested in working for you.
Coming Features
We currently have a small feature set and offering, reflecting the youth of our business. Over the next months they'll continue to grow:
- We'll roll out our full account structure and searching functionality in the next few weeks.
- We're working on providing simple one-click payment and invoicing for all services hired through us.
- We've already begun building a database of trusted and skilled seasonal labour to offer for hire through our site.
- We're in negotiations to allow us to provide cheap insurance for machinery hired through us.
As we're starting out we know we won't have every contractor listed, but when we aren't able to immediately provide you a selection of competitive offers we're committed to doing the legwork to find them. It will always be free to list work or services, so you'll only ever pay if you find an offer that you want to investigate. We hope you understand what we're providing and are interested in listing some work soon. If there's any way we could serve you better we'd love to hear from you.
All the best for season 2016,
Andrew
0429 69 79 89
<EMAIL_ADDRESS>www.shareyourfarminggear.com.au
|


X
Add New
Short Name:
Long Name:
Base:
X
Add New
Name:
Stat Priority:
↑
↓
X
Secondary Stats:
X
X
New Character
Name:
Job:
Roll / Reroll
Stats:
Items:
X
Add New
Type:
Weapon Roll:
Modifiers:
Add Mod
Add Spell
X
X
Add New
Casted:
Effects:
Add New
X
Stat:
Target:
Duration:
Amount:
Save
Right Click to download


|
|
#define | _SlFd_t Fd_t |
| |
| #define | sl_IfOpen spi_Open |
| | Opens an interface communication port to be used for communicating with a SimpleLink device. More...
|
| |
| #define | sl_IfClose spi_Close |
| | Closes an opened interface communication port. More...
|
| |
| #define | sl_IfRead spi_Read |
| | Attempts to read up to len bytes from an opened communication channel into a buffer starting at pBuff. More...
|
| |
| #define | sl_IfWrite spi_Write |
| | attempts to write up to len bytes to the SPI channel More...
|
| |
| #define | sl_IfRegIntHdlr(InterruptHdl, pValue) NwpRegisterInterruptHandler(InterruptHdl , pValue) |
| | register an interrupt handler routine for the host IRQ More...
|
| |
| #define | sl_IfMaskIntHdlr() NwpMaskInterrupt() |
| | Masks the Host IRQ. More...
|
| |
| #define | sl_IfUnMaskIntHdlr() NwpUnMaskInterrupt() |
| | Unmasks the Host IRQ. More...
|
| |
The SimpleLink device supports several standard communication protocol among SPI and
UART. CC32XX Host Driver implements SPI Communication Interface
- Note
- In CC32XX, SPI implementation uses DMA in order to increase the utilization of the communication channel. If user prefers to user UART, these interfaces need to be redefined
porting ACTION:
| #define sl_IfClose spi_Close |
Closes an opened interface communication port.
- Parameters
-
| fd | - file descriptor of opened communication channel |
- Returns
- upon successful completion, the function shall return 0. Otherwise, -1 shall be returned
- See Also
- sl_IfOpen , sl_IfRead , sl_IfWrite
- Note
- The prototype of the function is as follow: int xxx_IfClose(Fd_t Fd);
-
belongs to configuration_sec
- Warning
| #define sl_IfMaskIntHdlr |
( |
) | |
NwpMaskInterrupt() |
| #define sl_IfOpen spi_Open |
Opens an interface communication port to be used for communicating with a SimpleLink device.
Given an interface name and option flags, this function opens
the communication port and creates a file descriptor.
This file descriptor is used afterwards to read and write
data from and to this specific communication channel.
The speed, clock polarity, clock phase, chip select and all other
specific attributes of the channel are all should be set to hardcoded
in this function.
- Parameters
-
| ifName | - points to the interface name/path. The interface name is an optional attributes that the simple link driver receives on opening the driver (sl_Start). In systems that the spi channel is not implemented as part of the os device drivers, this parameter could be NULL. |
| flags | - optional flags parameters for future use |
- Returns
- upon successful completion, the function shall open the channel and return a non-negative integer representing the file descriptor. Otherwise, -1 shall be returned
- See Also
- sl_IfClose , sl_IfRead , sl_IfWrite
- Note
- The prototype of the function is as follow: Fd_t xxx_IfOpen(char* pIfName , unsigned long flags);
-
belongs to configuration_sec
- Warning
| #define sl_IfRead spi_Read |
Attempts to read up to len bytes from an opened communication channel into a buffer starting at pBuff.
- Parameters
-
| fd | - file descriptor of an opened communication channel |
| pBuff | - pointer to the first location of a buffer that contains enough space for all expected data |
| len | - number of bytes to read from the communication channel |
- Returns
- upon successful completion, the function shall return the number of read bytes. Otherwise, 0 shall be returned
- See Also
- sl_IfClose , sl_IfOpen , sl_IfWrite
- Note
- The prototype of the function is as follow: int xxx_IfRead(Fd_t Fd , char* pBuff , int Len);
-
belongs to configuration_sec
- Warning
| #define sl_IfRegIntHdlr |
( |
|
InterruptHdl, |
|
|
|
pValue |
|
) |
| NwpRegisterInterruptHandler(InterruptHdl , pValue) |
register an interrupt handler routine for the host IRQ
- Parameters
-
| InterruptHdl | - pointer to interrupt handler routine |
| pValue | - pointer to a memory structure that is passed to the interrupt handler. |
- Returns
- upon successful registration, the function shall return 0. Otherwise, -1 shall be returned
- See Also
- Note
- If there is already registered interrupt handler, the function should overwrite the old handler with the new one
-
If the handler is a null pointer, the function should un-register the interrupt handler, and the interrupts can be disabled.
-
belongs to configuration_sec
- Warning
| #define sl_IfUnMaskIntHdlr |
( |
) | |
NwpUnMaskInterrupt() |
Unmasks the Host IRQ.
- See Also
- sl_IfMaskIntHdlr
- Note
- belongs to configuration_sec
- Warning
| #define sl_IfWrite spi_Write |
attempts to write up to len bytes to the SPI channel
- Parameters
-
| fd | - file descriptor of an opened communication channel |
| pBuff | - pointer to the first location of a buffer that contains the data to send over the communication channel |
| len | - number of bytes to write to the communication channel |
- Returns
- upon successful completion, the function shall return the number of sent bytes. therwise, 0 shall be returned
- See Also
- sl_IfClose , sl_IfOpen , sl_IfRead
- Note
- This function could be implemented as zero copy and return only upon successful completion of writing the whole buffer, but in cases that memory allocation is not too tight, the function could copy the data to internal buffer, return back and complete the write in parallel to other activities as long as the other SPI activities would be blocked until the entire buffer write would be completed
The prototype of the function is as follow: int xxx_IfWrite(Fd_t Fd , char* pBuff , int Len);
- Note
- belongs to configuration_sec
- Warning


Element Positioning Tests HTML Test Page
And now for a lot of white space:
This heading is the test element!
This is the end of the test element!
This is the end!


00:00
Stop Here
Title:
Description:
Night Mode
Help
J/K/L - Back 5 seconds, Play/Pause, Advance 5 seconds
,/. - Back 0.1 seconds, Advance 0.1 seconds


Mac OSX
RaspMedia Copy Tool (outdated, wait for Update!)
compatible with Mac OSX 10.6+
v1.1 (c)2014-2015
Windows
RaspMedia Copy Tool (outdated, wait for Update!)
compatible with Windows Vista/7/8 (64bit)
v1.1 (c)2014-2015/p>
Linux
RaspMedia Control (outdated, wait for Update!)
RaspMedia Copy Tool (outdated, wait for Update!)
compatible with Ubuntu 12.04+/Fedora20
v1.0 (c)2014


{% extends "app.html" %} {% import "snippets.html" as snippets %} {% macro install_app_with_software_manager(app, distro_spec, environments) %}
In order to install {{ app.name }} with Software Manager,
Alternatively, launch a Linux terminal emulator,
type flatpak install nuvola {{ app.uid }}
and press the Enter key to install this package.


eventfd - create a file descriptor for event notification
#include <sys/eventfd.h>
int eventfd(unsigned int initval, int
flags);
eventfd() creates an "eventfd object" that can be used as an
event wait/notify mechanism by user-space applications, and by the kernel to
notify user-space applications of events. The object contains an unsigned
64-bit integer (uint64_t) counter that is maintained by the kernel.
This counter is initialized with the value specified in the argument
initval.
As its return value, eventfd() returns a new file
descriptor that can be used to refer to the eventfd object.
The following values may be bitwise ORed in flags to change
the behavior of eventfd():
- EFD_CLOEXEC (since Linux 2.6.27)
- Set the close-on-exec (FD_CLOEXEC) flag on the new file descriptor.
See the description of the O_CLOEXEC flag in open(2) for
reasons why this may be useful.
- EFD_NONBLOCK (since Linux 2.6.27)
- Set the O_NONBLOCK file status flag on the open file description
(see open(2)) referred to by the new file descriptor. Using this
flag saves extra calls to fcntl(2) to achieve the same result.
- EFD_SEMAPHORE (since Linux 2.6.30)
- Provide semaphore-like semantics for reads from the new file descriptor.
See below.
In Linux up to version 2.6.26, the flags argument is
unused, and must be specified as zero.
The following operations can be performed on the file descriptor
returned by eventfd():
- read(2)
- Each successful read(2) returns an 8-byte integer. A read(2)
fails with the error EINVAL if the size of the supplied buffer is
less than 8 bytes.
- The value returned by read(2) is in host byte order—that is,
the native byte order for integers on the host machine.
- The semantics of read(2) depend on whether the eventfd counter
currently has a nonzero value and whether the EFD_SEMAPHORE flag
was specified when creating the eventfd file descriptor:
- If EFD_SEMAPHORE was not specified and the eventfd counter has a
nonzero value, then a read(2) returns 8 bytes containing that
value, and the counter's value is reset to zero.
- If EFD_SEMAPHORE was specified and the eventfd counter has a
nonzero value, then a read(2) returns 8 bytes containing the value
1, and the counter's value is decremented by 1.
- If the eventfd counter is zero at the time of the call to read(2),
then the call either blocks until the counter becomes nonzero (at which
time, the read(2) proceeds as described above) or fails with the
error EAGAIN if the file descriptor has been made nonblocking.
- write(2)
- A write(2) call adds the 8-byte integer value supplied in its
buffer to the counter. The maximum value that may be stored in the counter
is the largest unsigned 64-bit value minus 1 (i.e., 0xfffffffffffffffe).
If the addition would cause the counter's value to exceed the maximum,
then the write(2) either blocks until a read(2) is performed
on the file descriptor, or fails with the error EAGAIN if the file
descriptor has been made nonblocking.
- A write(2) fails with the error EINVAL if the size of the
supplied buffer is less than 8 bytes, or if an attempt is made to write
the value 0xffffffffffffffff.
- poll(2), select(2) (and similar)
- The returned file descriptor supports poll(2) (and analogously
epoll(7)) and select(2), as follows:
- The file descriptor is readable (the select(2) readfds
argument; the poll(2) POLLIN flag) if the counter has a
value greater than 0.
- The file descriptor is writable (the select(2) writefds
argument; the poll(2) POLLOUT flag) if it is possible to
write a value of at least "1" without blocking.
- If an overflow of the counter value was detected, then select(2)
indicates the file descriptor as being both readable and writable, and
poll(2) returns a POLLERR event. As noted above,
write(2) can never overflow the counter. However an overflow can
occur if 2^64 eventfd "signal posts" were performed by the KAIO
subsystem (theoretically possible, but practically unlikely). If an
overflow has occurred, then read(2) will return that maximum
uint64_t value (i.e., 0xffffffffffffffff).
- The eventfd file descriptor also supports the other file-descriptor
multiplexing APIs: pselect(2) and ppoll(2).
- close(2)
- When the file descriptor is no longer required it should be closed. When
all file descriptors associated with the same eventfd object have been
closed, the resources for object are freed by the kernel.
A copy of the file descriptor created by eventfd() is
inherited by the child produced by fork(2). The duplicate file
descriptor is associated with the same eventfd object. File descriptors
created by eventfd() are preserved across execve(2), unless
the close-on-exec flag has been set.
On success, eventfd() returns a new eventfd file descriptor. On error, -1
is returned and errno is set to indicate the error.
- EINVAL
- An unsupported value was specified in flags.
- EMFILE
- The per-process limit on the number of open file descriptors has been
reached.
- ENFILE
- The system-wide limit on the total number of open files has been
reached.
- ENODEV
- Could not mount (internal) anonymous inode device.
- ENOMEM
- There was insufficient memory to create a new eventfd file
descriptor.
eventfd() is available on Linux since kernel 2.6.22. Working support is
provided in glibc since version 2.8. The eventfd2() system call (see
NOTES) is available on Linux since kernel 2.6.27. Since version 2.9, the glibc
eventfd() wrapper will employ the eventfd2() system call, if it
is supported by the kernel.
For an explanation of the terms used in this section, see attributes(7).
| Interface |
Attribute |
Value |
| eventfd () |
Thread safety |
MT-Safe |
eventfd() and eventfd2() are Linux-specific.
Applications can use an eventfd file descriptor instead of a pipe (see
pipe(2)) in all cases where a pipe is used simply to signal events. The
kernel overhead of an eventfd file descriptor is much lower than that of a
pipe, and only one file descriptor is required (versus the two required for a
pipe).
When used in the kernel, an eventfd file descriptor can provide a
bridge from kernel to user space, allowing, for example, functionalities
like KAIO (kernel AIO) to signal to a file descriptor that some operation is
complete.
A key point about an eventfd file descriptor is that it can be
monitored just like any other file descriptor using select(2),
poll(2), or epoll(7). This means that an application can
simultaneously monitor the readiness of "traditional" files and
the readiness of other kernel mechanisms that support the eventfd interface.
(Without the eventfd() interface, these mechanisms could not be
multiplexed via select(2), poll(2), or epoll(7).)
The current value of an eventfd counter can be viewed via the
entry for the corresponding file descriptor in the process's
/proc/[pid]/fdinfo directory. See proc(5) for further
details.
There are two underlying Linux system calls: eventfd() and the more
recent eventfd2(). The former system call does not implement a
flags argument. The latter system call implements the flags
values described above. The glibc wrapper function will use eventfd2()
where it is available.
The GNU C library defines an additional type, and two functions that attempt to
abstract some of the details of reading and writing on an eventfd file
descriptor:
typedef uint64_t eventfd_t;
int eventfd_read(int fd, eventfd_t *value);
int eventfd_write(int fd, eventfd_t value);
The functions perform the read and write operations on an eventfd
file descriptor, returning 0 if the correct number of bytes was transferred,
or -1 otherwise.
The following program creates an eventfd file descriptor and then forks to
create a child process. While the parent briefly sleeps, the child writes each
of the integers supplied in the program's command-line arguments to the
eventfd file descriptor. When the parent has finished sleeping, it reads from
the eventfd file descriptor.
The following shell session shows a sample run of the program:
$ ./a.out 1 2 4 7 14
Child writing 1 to efd
Child writing 2 to efd
Child writing 4 to efd
Child writing 7 to efd
Child writing 14 to efd
Child completed write loop
Parent about to read
Parent read 28 (0x1c) from efd
#include <sys/eventfd.h>
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <stdint.h> /* Definition of uint64_t */
#define handle_error(msg) \
do { perror(msg); exit(EXIT_FAILURE); } while (0)
int
main(int argc, char *argv[])
{
int efd, j;
uint64_t u;
ssize_t s;
if (argc < 2) {
fprintf(stderr, "Usage: %s <num>...\n", argv[0]);
exit(EXIT_FAILURE);
}
efd = eventfd(0, 0);
if (efd == -1)
handle_error("eventfd");
switch (fork()) {
case 0:
for (j = 1; j < argc; j++) {
printf("Child writing %s to efd\n", argv[j]);
u = strtoull(argv[j], NULL, 0);
/* strtoull() allows various bases */
s = write(efd, &u, sizeof(uint64_t));
if (s != sizeof(uint64_t))
handle_error("write");
}
printf("Child completed write loop\n");
exit(EXIT_SUCCESS);
default:
sleep(2);
printf("Parent about to read\n");
s = read(efd, &u, sizeof(uint64_t));
if (s != sizeof(uint64_t))
handle_error("read");
printf("Parent read %llu (0x%llx) from efd\n",
(unsigned long long) u, (unsigned long long) u);
exit(EXIT_SUCCESS);
case -1:
handle_error("fork");
}
}
futex(2), pipe(2), poll(2), read(2),
select(2), signalfd(2), timerfd_create(2),
write(2), epoll(7), sem_overview(7)
This page is part of release 5.05 of the Linux man-pages project. A
description of the project, information about reporting bugs, and the latest
version of this page, can be found at https://www.kernel.org/doc/man-pages/.


--- layout: post esbma_id: 3016 title: Announcing something new: Zumero date: 2013-03-14 10:00:00 ---
I am so very excited to unveil our latest endeavor:
To describe Zumero, we first describe SQLite.
SQLite is a lightweight (but surprisingly powerful) implementation of a SQL database.
SQLite is the standard database software for iOS, Android, and Windows RT. It is installed on over a billion mobile devices.
But like any other computer, and perhaps more so, a mobile device is not isolated. It needs to share data with a server.
And SQLite has no synchronization capabilities.
Zumero solves that problem.
Zumero is "sync for SQLite".
It's a better database platform for mobile.
Mobile apps need to talk to the cloud about data.
A lot of people are building mobile apps that use the "remote procedure call" model. Every user operation requires a network request to the server.
We think "replicate and sync" is a better model. The app can interact with a local copy of the database instead of going through the network. Synchronization can be handled entirely in the background.
Putting network activity in the background brings two big wins:
The developer wins because networking issues are isolated in a small part of the app. The real features of the app can be the focus of the developer's attention, and are easier to code.
The user wins because the app is faster, more responsive, and works offline.
Consider a typical situation where a mobile app responds to a user action by filling a list box with the results of a database query. Neither the developer nor the user wants the network involved between the button tap and the refresh of the display. Mobile networks are just not consistent enough. Even a perfectly-working LTE connection usually has enough latency to make the app feel sluggish.
On the client, Zumero is a SQLite extension. The server is built on node.js.
The client tries very hard to be invisible to the developer. We didn't want to introduce a whole new API for everybody to learn, so developing with Zumero isn't much different from SQLite. Porting an existing SQLite app to use Zumero is usually straightforward.
The SQLite extension uses SQLite's "virtual tables". A Zumero table mostly works just like a regular table, except that it can be synced.
The Zumero server manages the central, authoritative copy of the database and handles all the details of synchronization, merging changes, conflict resolution, caching, logging, authentication, and permissions.
Because it's an incredible piece of software. If you're not familiar with SQLite, give it a serious look. It has come so far that keeping the word "Lite" in the name seems inappropriate. SQLite is fast, robust, and far more capable than most people know.
Because it's everywhere. Every smart phone and tablet has SQLite inside. Even Microsoft has given up the notion of shrinking SQL Server and decided to standardize on SQLite as its recommended database for Windows RT.
Because it needs a sync feature. The real question here is not "Why SQLite?" but rather, "Why NOT SQLite?" Why should people consider anything except SQLite for dealing with mobile data? The main answer is obvious: SQLite doesn't sync. Zumero was created to fill that need, not by introducing a new mobile database system, but rather, by adding painless synchronization features to the high quality database that is already there.
Right now (March 2013), the Zumero Client SDK includes support for iOS and Android. WinRT is planned. Blackberry is not, but that might change if there is evidence of customer demand.
We will also be supporting two of the cross-platform mobile solutions: Apache Cordova (aka Phonegap) and Xamarin. We've made significant progress on both of these, but neither of them was ready for the initial release.
The client SDK also includes support for (regular) Windows and Mac OS. This may seem odd, since Zumero is all about mobile. But very few so-called mobile apps are accessed exclusively from mobile devices. You may (and probably will) want the ability to also access your data from web apps, desktop applications, or even other servers.
Even if you don't need any of these things, the SQLite command-line shell is a handy way to perform administrative tasks for your Zumero server, such as initial setup of your schema, configuring permissions, or analyzing logs.
The Zumero server has a plugin architecture designed to support a variety of SQL databases. We currently have two implementations of the database backend: SQLite and PostgreSQL.
At the present time (still March 2013), the Zumero server is available as a cloud-hosted service with the SQLite backend, but it will be made available in other flavors later.
From a strictly technical perspective, the Zumero server runs just fine on Linux, Mac, and Windows.
The current cloud-hosted offering is Linux, running in the Amazon cloud.
In the future, we will make the server available in three ways: in the cloud, on-premises, or as a desktop server for development purposes. Not all combinations of platform and deployment are likely to be interesting. Things will probably end up something like this:
| Linux | Windows | Mac | Other | |
|---|---|---|---|---|
| Cloud | Yes | Yes (Azure, later) |
Where? | What? |
| On-premises | Yes (later) |
Yes (later) |
Nobody wants this | Maybe Solaris? |
| Development | Yes (later) |
Yes (later) |
Yes (later) |
We'll support Commodore 64 right after node.js does |
No.
As always, that depends on how narrowly you define "competitor". :-)
At one extreme, we are not aware of anybody doing EXACTLY what we are doing.
At the other extreme, everybody doing anything with data and mobile is a competitor.
If I had to name just one other player, it would be Couchbase Lite. Couchbase founder J. Chris Anderson recently did a great blog entry called Why Mobile Sync?. His tune sounds a lot like the one we're singing about Zumero.
So it wouldn't be outrageous to describe Zumero by saying, "It's like Couchbase Lite. Except it's SQL".
Hardly. The NoSQL offerings are gaining traction, but SQL still has far greater market share, especially in the enterprise.
We don't really think of Zumero as a "Backend as a Service" (BaaS) company, since we're focused on the database part of the story.
But if you ignore all the other mobile backend stuff (like push notifications), it would be reasonable to describe Zumero by saying, "It's like Parse/Kinvey/Stackmob. Except it's a replicate-and-sync model. And it's SQL."
No. Yes. Sort of.
In terms of market positioning, Zumero is separate. It does not share SourceGear branding. It has no particular connection with SourceGear's products.
But financially, Zumero is currently part of SourceGear. (This approach is similar to what we did with Teamprise, which we sold to Microsoft in 2009.)
Corey and I think of Zumero as our new startup, which is being incubated inside SourceGear.
It's not.
But the genesis of Zumero happened when we did the iPad app for Veracity. We liked the "replicate and sync" model for mobile so much that we decided to take the databasey part of Veracity and productize it as a platform for building all kinds of mobile apps. Along the way, the technology evolved a lot, to the point where it doesn't look much like the original Veracity code, but that's what we started with.
This is actually somewhat of a return to our roots for SourceGear. We spent a lot of our first three years doing mobile development as contract work for Motorola. Of course, today's mobile devices are just a little more powerful than that phone we worked on back in 1997. :-)
They are continuing to move forward. Vault 7 is underway and aiming for a Q3 release. Veracity 2.5 is done and will be released sometime in the next two weeks.


Tottenham Fires Head Coach Mauricio Pochettino
Tottenham Hotspur on Tuesday sacked head coach Mauricio Pochettino after he had been under scrutiny by club management.
According to UK-based media reports, Pochettino allegedly had a long-lasting conflict with club chairman Daniel Levy.
"We were extremely reluctant to make this change and it is not a decision the Board has taken lightly, nor in haste [...] Regrettably domestic results at the end of last season and beginning of this season have been extremely disappointing", Levy said in the statement.
According to The Telegraph, citing sources, Pochettino was devastated by the Champions League final defeat against Liverpool earlier this year and reportedly held a unique vision for the team's future roster, which contradicted Levy's stance.
The club also said in the statement that the Argentine, along with his coaching staff of Jesus Perez, Miguel D’Agostino and Antoni Jimenez, have been relieved of their duties.
Media have noted that Levy must pay a high compensation to part ways with Pochettino and his staff, all of whom had signed new five-year contracts in May 2018.
Pochettino was at the helm for 293 games and delivered four successive top-four Premier League finishes, challenging for the title in 2015/16 and 2016/17.


Login
Login
Error:
Wrong username or password combination
Or sign up
here
Developed with ❤ by Ethan, Revethy, Hae Seung, and Courney


USER GUIDE¶
Prerequisite¶
First and foremost, you will need to setup credential for Accessing the API.
There are two options available: pass-in options flags or setup
PDX_
environment variables. Latter is preferred as follows:export PDX_USERNAME=<YOUR_PierianDx_CGW_LOGIN_EMAIL> export PDX_PASSWORD=<YOUR_PierianDx_CGW_LOGIN_PASSWORD> export PDX_INSTITUTION=<ASK_YOUR_PierianDx_CGW_ACCOUNT_MANAGER> export PDX_BASE_URL=https://app.pieriandx.com/cgw-api/v2.0.0
Otherwise, you can always pass-in options flags as follows:
pyriandx <command> \ -b https://app.pieriandx.com/cgw-api/v2.0.0 \ -u<EMAIL_ADDRESS>\ -p my_password \ -i my_institution
Pass-in options flags will override their environment variables counterpart, if present.
You can omit
PDX_BASE_URL
or-b
flag if you want to work against UAT environment, which is set by default.
Command Concept¶
CLI is designed to be driven by command concept.
Therefore, its command pattern usage is as follows:
pyriandx <command> [options] [<args>...]
Short description about available commands are as follow:
help Print help and exit version Print version and exit case Get a case from Case API list List cases from Case API, optionally apply filters to limit results create Accession a new case from given input JSON file upload Upload case files for given Case ID run Create sequencer run for given Case ID job Create informatics job for given Case ID and Run ID poll Poll informatics job status for given Case ID and Job ID report Get a report for given Case ID
Printing Help¶
CLI has self-contained useful
help
sub-commands.To print CLI command help:
pyriandx help pyriandx case help pyriandx list help pyriandx create help pyriandx upload help pyriandx run help pyriandx job help pyriandx poll help pyriandx report help
Each command help contain description about usage and notes. For example:
$ pyriandx case help Usage: pyriandx case help pyriandx case [options] <case-id> Description: Get a case by given ID from PierianDx CGW. It returns in JSON format. You can further process it e.g. pretty print by pipe through with program such as jq. Example: pyriandx case 69695 pyriandx case 69695 | jq
Getting a Case¶
You can query existing case with
case
command by passing case ID as follows:pyriandx case 69695
You can redirect output to store in JSON format as follows:
pyriandx case 69695 > case_69695.json
You can also use external program like jq to pretty print JSON format as follows:
pyriandx case 69695 | jq
Listing all Cases¶
To query all available cases, use
list
command as follows:pyriandx list | jq
Optionally, you can apply filters as follows:
pyriandx list accessionNumber=SBJ000123
Accession a New Case¶
To accession a new case, first, you must prepare case input file in JSON format.
You can refer to example provided in CGW API User Guide or pyriandx github repo as JSON input template to work out for your case.
Once you have case input file ready, you can create a case as follows:
pyriandx create my_case.json
Optionally, you can provide case files (typically VCF files) as follows:
pyriandx create my_case.json file1.vcf.gz file2.vcf.gz file3.purple.cnv
You can also prepare a folder and stage all your case files for upload. In this case, instead of providing individual case files, you can provide this stage directory as follows:
pyriandx create my_case.json path/to/files/for/upload/
Uploading Case Files¶
Sometime, you might want to upload additional case files or, you might have just accessioned the case only.
At any case, you can upload case files for given case.
For example, to upload case files for case ID
69695
as follows:pyriandx upload 69695 file1.vcf.gz file2.vcf.gz file3.cnv
Similarly, you can stage case files in a directory for upload. And provide this stage directory as follows:
pyriandx upload 69695 path/to/SBJ00123/
Sequencer Run¶
After case has accessioned and uploaded case files, you should create sequencer run.
For example, to create sequencer run for case ID
69695
as follows:pyriandx run 69695
The
run
command return Run ID (runId
field as in JSON form). This is serial sequence and, start from1
and, increment by1
on subsequencerun
command invocation.This will create a new sequencer run entry in
sequencerRuns
resource node (as in JSON form) of your case model.You can check existing sequencer run by getting a case and filter JSON as follows:
pyriandx case 69695 | jq '.sequencerRuns[]'
You will need at least one sequencer run entry to kick off informatics job (explain next).
Informatics Job¶
In order to create analysis informatics job, you will need accessioned case with at least one sequencer run prepared for it.
You can check your case readiness for informatics job submission by running
case
command to observe the case model output in JSON format.Once your case is ready for run, you will need Case ID and Run ID to kick off informatics job as follows:
pyriandx job 69695 1
The
job
command returns Job ID. You will need Job ID for tracking its status bypoll
command (explain next).
Polling Job Status¶
Once informatics job has kicked off, it will take awhile for job to be completed.
CLI comes with
poll
command for monitoring job status for convenience.You will need Case ID and Job ID for
poll
command as follows:pyriandx poll 69695 19635
Polling timeout at every 30 minutes. You can poll again.
You can abort polling by
Ctrl+C
at any time.You can also (ad-hoc) get a case and filter Job ID on the return JSON using
jq
as follows:pyriandx case 69695 | jq '.informaticsJobs[] | select(.id == "19635")'
Or, specifically on
status
field as follows:pyriandx case 69695 | jq '.informaticsJobs[] | select(.id == "19635") | .status'
Alternatively, you can check job status in PierianDx CGW dashboard.
Caveat: Polling job status is not perfected yet. So please do not rely on this feature.
Download Analysis Report¶
When case report is ready, you can download it as follows:
pyriandx report 69695
Alternatively, you can download it from PierianDx CGW dashboard.
Caveat: Download analysis report is not perfected yet. So please do not rely on this feature.
Case Assignment¶
CLI is not yet supported case assignment to personnel at the moment.
You can follow up assign the case to curator/personnel through PierianDx CGW dashboard.
Caveat: We will add to next todo if this feature is desirable.
Issues¶
Create or vote for feature/issue requests: https://github.com/umccr/pyriandx/issues


I just finished my second full week working at a ~10 person startup! Here are my initial thoughts :)
1. I feel like I'm really working at a startup in every sense of the word. We'll talk about an idea one minute, and then in a day its already being planned out detail by detail and executed.
2. The company has a culture of trust and responsibility. With that also comes very high expectations. When something is assigned to you, its expected to get done. Its on you to communicate if something comes up that changes your timeline. Over-communication is key. (I ran into an issue my first week that could have easily been resolved had I communicated better)
3. Self-confidence is essential at a startup. Similar to the above point, its on you to figure out a lot of things. Of course you have a team to rely on, but that team also has a lot on their plate as well.
4. Its very important for cofounders to play their strengths with their roles. For example, one co-founder focusing on communications (with customers and partners) and the other being more tactical, focusing on day-to-day operations.
5. Be a really good generalist. I used to think my lack of focus was a bad thing, but I've learned to embrace it. Generalists thrive at early stage startups because every single day is different.
6. Its super important to start tracking business data as early as possible. Having data really helps with decision making and helping find which users to target for certain experiments.
7. Transparency is key. We have a Slack channel to highlight both conquers and botches. That way, its okay to mess up on things, and you can see that other people are human and make mistakes too.
8. I feel like I'm doing very impactful work. In my 2 weeks that I've been here, I've done more than I've done at entire internships. If you can move fast, they will keep throwing more at you. So many opportunities to learn :)
9. You never know who you will learn from. You can find admirable traits in everyone you meet
10. We need more women representation in tech companies. Being at a women-run/majority women company is a great experience. I can't speak much overall since I only have a sample size of one but communication has been incredibly clear and there is a deep love and empathy for the customer. Overall, been having a great experience and excited for what's to come!
Startups


rotten > Library > Biographies > Crime > Assassins > Jack Ruby
Jack Ruby
The assassin of Lee Harvey Oswald.
See also Kennedy Assassinations.
Represented by Melvin Belli.
Claimed he was injected with cancer cells, died January 3, 1967.
Timeline
| 24 Nov 1963 |
Jack Ruby assassinates Lee Harvey Oswald. The murder is broadcast live on national TV. |
Pornopolis |
Rotten |
Faces of Death |
Famous Nudes
|


--- layout: page title: About me subtitle: "Reverse Engineering William" css: "/css/aboutme.css" ---
I am a Software Developer from Nairobi Kenya who loves to write software to build great products. I have a bias for Web and Mobile development. I am proficient in Javascript
, Python and C# programming languages and always learning something new.
I leverage on JS frameworks such as Angular, React and Ionic to deliver great experiences to users.
Currently working as a Senior Frontend Engineer at Humanitec.
Previously I worked for BBC (British Broadcasting Corporation in
Visual Journalism Department and Transparency International.
I really enjoy travelling and meeting new people. Besides writing code, I a big fan of hip hop music and podcast such as Dissect.
You can email me or find me on Twitter if you want to get in touch. As I said, I love meeting new people so don't hesitate to send a message!


--- layout: default --- Home {{ page.title }} {% include date.html date=page.date %} {{ content }}
{% include date.html date=page.date %}


Page Links: Index Page
| ChristiaanJ 18th Aug 2010, 21:24 permalink Post: 20 |
M2dude,
Re the MEPU at the Le Bourget museum... The story I just got was that it was taken off F-WTSA or F-WTSB at Roissy for a fault and replaced (both 'SA and 'SB operated out of Roissy around '74 / '75 for things like route proving, etc.). It got left on a shelf in a store, and was only discovered again in 2003 during the "big clean-out" and was saved 'in extremis' by somebody who recognised it for what it was, stopped it from being 'binned' and took it over to the museum.
Quote:
So yes, you're right, essentially all of it was "useable" fuel, it did not serve only for the trim.
Quote:
Jock Lowe seems to have stated there is a photo.... and we all still wonder if there is some footage taken from the Lear Jet during the filming of "Airport 79". But none is publicly known to exist ... we just know it's been done! |
||
| M2dude 15th Sep 2010, 16:04 permalink Post: 365 |
bio161
Quote:
Dude |
||
| ChristiaanJ 16th Oct 2010, 22:27 permalink Post: 580 |
OK, I see others have already posted answers.
I've carefully avoided looking at them, but I'll might as well plug in mine now.
Quote:
So the questions dealing with the in-service period are totally outside my field of experience... all I can do is guess, in case I saw the answers somewhere. 1) How many Concorde airframes were built? Twenty-two. Two static-test airframes. - One at Toulouse, for purely static tests, and tests such as vibration and flutter. - One at Farnborough, for the long-duration thermal fatigue tests. (A few bits and pieces of the Farnborough test specimen have survived, and can still be seen at the Brooklands museum). Two prototypes (001 and 002) Two pre-production aircraft (01 and 02) Two production aircraft used for certification, that never entered service (201 - F-WTSB and 202 - G-BBDG) Fourteen production aircraft, seven that served with British Airways, seven that served with Air France. 2) As far as the British constructed aircraft went, name the destinations that were served?. Regular flight numbers only, excludes charters etc. Not a clue as to the full list. - Bahrain, obviously. - JFK. - IAD (not sure if that's rated as regular, or only incidental) - Dallas (with Braniff) - Barbados (of course, right until the end) - Sngapore (with Singapore Airlines, and G-BOAD in Singapore Airlines colours on one side) - Sydney (again no idea if that rated as a regular flight or only a few tries) 3) What was the departure time for the ORIGINAL morning LHR-JFK Concorde services? (Not called the BA001 then either). Not a clue either. Vague memory of about 10:00 am which gave you a full working day in New York. 4) Further to question 3 above, what WERE the original flight numbers for the BA001 and BA003? (The morning and evening LHR-JFK services?).. Never flew on them, never had to deal with them. BA174 comes to mind from the depths of my memory, in that case BA003 would have been BA176? 5) There were no less than FORTY SIX fuel pumps on Concorde. What was the breakdown for these? (Clue; don't forget the scavenge pump ) M2dude, I did AFCS, not the fuel system. I believe you, but without pulling out some diagrams I honestly have NO idea. I expect each tank had at least two pumps, which gets me up to 26. Then there were a few emergency pumps for the trim tanks, and I suppose each engine had additional pumps associated with it. Still nowhere near the 46 I need to find..... 6) What airframe had the only TOTALLY unique shape? That would have been my old friend, 01 (G-AXDN), first pre-production aircraft, now at Duxford. It was the first Concorde with the new transparent visor, but it still had the short tail that characterised the prototypes. It was 02 (F-WTSA), the first French pre-production aircraft, that was close to the final shape of the production aircraft. 7) This one is particularly aimed at ChristiaanJ. What was the total number of gyros on the aircraft? Good question.... never counted them all. But I'll try a guess. First a nice one, the SFENA Emergency Standby Artificial Horizon (made by the firm I worked for). Ran off the Emergency Battery Bus via a small independent inverter. And if that failed too, it would still run reliably for several minutes on its own inertia. Next, the rate gyros used by the autostabilisation system ; these measured the angular rate of the aircraft along the three main axes, pitch, roll and yaw. There were six, three each for the two autostab systems. Now the rest.... Each IMU (inertial measurement unit, part of the inertial naviagation system) had three gyros. With three INS on board, that would make nine. Much as I try, I can't remember other ones, so I'll look forward to the final answer. I can imagine the weather radar using an additional gyro for stabilisation, but I never went there. 8) How many wheel brakes? Unless this is a trick question, I would say eight, for each of the main gear wheels. The nose gear did not have any brakes - unless there were some small ones to stop the wheels rotating after retraction of the gear, but not used during landing. 9) What Mach number was automatic engine variable intake control enabled? No idea. Mach 1.0 or thereabouts is my personal guess only. 10) Above each bank of engine instruments were three lights, a blue, a green and an amber. What did they each signify? I know that they each monitored the status of one of the engines, because it was too complex for the pilots to fully monitor all the parameters of all four engines in the short time between start-of-roll and V1... they had too many other things to do. But I don't remember what each light meant, would have to look it up in the manual. 11) At what airfied were the first BA crew base training details held? No idea. Was it Brize Norton, or Casablanca? 12) What LHR runways did Concorde use for landing and take-off? (Trick question, not as obvious as it might seem). No idea. Vague memory of it being systematically the North runway for noise issues. 13) What operator had serious plans to operate Concorde from SNN to JFK in the early 1980's? No idea. 14) What development aircraft did not exceed Mach 2 until fifteen months after her maiden flight? I would expect the obvious answer to be 002. Working up from first flight to Mach 2 was a slow and laborious process, and in the end it was 001 that both flew first, and also went to Mach 2 first. I don't think any of the other aircraft took that long. A I said, I tried to answer all questions "off the top of my head", without looking at any other sources. CJ |
||
| ChristiaanJ 12th Dec 2011, 17:31 permalink Post: 1523 |
Quote:
Anyway, for modelers (not your case, I take it) a Munsell chip ref wouldn't be much use..... they'd need a Humbrol paint number ! "Matching colors" is a Concorde problem to this day.... A small group of enthusiasts is trying to re-paint F-WTSA (the French preprod Concorde, now at a small museum south of the Paris Orly airport) in the same paint scheme as in the olden days... ancient BA livery on one side, ancient AF livery on the other side. Getting hold of all the paint color references is not obvious! CJ |
||
| NHerby 10th Jul 2012, 09:10 permalink Post: 1655 |
@CliveL
Quote:
A few pages earlier on this thread some of you have posted some of their favourite photos of Concorde. Here are very sad, chocking and rare photos: This is 211 (F-BVFD) after "Air France's special treatment" (shame on them). The photos were taken in 1994. More photos of this can be seen here: Maripa : Documentation photographique. To compensate, here's one of my favourite: Most of those photos were taken at Toulouse (we saw a lot from Filton in this thread but very few from France). The caption of the top left picture says it is 102 (F-WTSA) and 201 (F-WTSB) in the background. The image comes from a french website ( Concorde dans la presse de 1965 \xe0 2003 ) gathering hundreds of articles about Concorde. Very interesting but in French only. I particulary like this last serie of photos because it shows the process of a dream turning into reality, the beginning of such a beautiful adventure and the symbol of a time where national pride and technical achievment had more importance and value than the basic investment/profitability ratio that rules the world today! And now, more than 40 years later, not only we are not able to build a SST but we are also not able to make a SST flying again. And this leads to a new question (maybe another 64000$ one): As we can see in those photos and as I have seen in photos from Filton, several pre-production and production airframes were built at the same time. Did the fabrication of pre-production or production a/c had to be stopped at some point to wait for in flight test results? Similar question: did the early flights revealed unforseen problems that needed to be sorted out before the program can move on? |
Page Links: Index Page


Night conditions
Sunny conditions
10:30 AM
Explore around the seashore
Do some stuff tomorrow
12:30 AM
19:30 AM


CHAPTER 431J
CAPTIVE INSURANCE COMPANIES
REPEALED. L 1987, c 347, §1.
Cross References
For present provisions, see chapter 431, article 19.


JackO&G LLC ("Company" or "We") respects your privacy and is committed to protecting it through our compliance with this policy.
This policy describes the types of information we may collect from you or that you may provide when you use our mobile application (our "Application") or visit the website (our "Website") and our practices for collecting, using, maintaining, protecting, and disclosing that information.
This policy applies to information we collect:
It does not apply to information collected by:
Please read this policy carefully to understand our policies and practices regarding your information and how we will treat it. If you do not agree with our policies and practices, your choice is not to use our Application and Website. By accessing or using our Application and/or Website, you agree to this privacy policy. This policy may change from time to time (see Changes to Our Privacy Policy). Your continued use of our Application and/or Website after we make changes is deemed to be acceptance of those changes, so please check the policy periodically for updates.
Our Application and Website are not intended for children under 16 years of age. No one under age 16 may provide any personal information to or on the Application and/ or Website. We do not knowingly collect personal information from children under 16. If you are under 16, do not use or provide any information on our Application and/or Website or through any of their features, download and subscribe to the Application, use any of the interactive or public comment features on the Application and/or Website, or provide any information about yourself to us, including your name, address, telephone number, email address, or any screen name or user name you may use. If we learn we have collected or received personal information from a child under 16 without verification of parental consent, we will delete that information. If you believe we might have any information from or about a child under 16, please contact us at<EMAIL_ADDRESS>California residents under 16 years of age may have additional rights regarding the collection of their personal information. Please see Your California Privacy Rights for more information.
We collect several types of information from and about users of our Application and Website, including information:
We collect this information:
The information we collect on or through our Application and Website may include:
You also may provide information to be published or displayed (hereinafter, "posted") on public areas of the Application and/or Website, or transmitted to other users of the Application and/or Website or third parties (collectively, "User Contributions").
 Although we limit access to certain pages, please be aware that no security measures are perfect or impenetrable. Additionally, we cannot control the actions of other users of the Application or Website with whom you may choose to share your User Contributions. Therefore, we cannot and do not guarantee that your User Contributions will not be viewed by unauthorized persons.
As you navigate through and interact with our Application and/or Website, we may use automatic data collection technologies to collect certain information about your equipment, browsing actions, and patterns, including:
The information we collect automatically does not include personal information, but we may maintain it or associate it with personal information we collect in other ways or receive from third parties. It helps us to improve our Application and Website and to deliver a better and more personalized service, including by enabling us to:
The technologies we use for this automatic data collection may include:
We do not collect personal information automatically, but we may tie this information to personal information about you that we collect from other sources or you provide to us.
Our Application and/Website may contain content, including advertisements, that are served by third-parties, including advertisers, ad networks and servers, content providers, and application providers. These third parties may use cookies alone or in conjunction with web beacons or other tracking technologies to collect information about you. The information they collect may be associated with your personal information or they may collect information, including personal information, about your online activities over time and across different websites and other online services. They may use this information to provide you with interest-based (behavioral) advertising or other targeted content.
We do not control these third parties' tracking technologies or how they may be used. If you have any questions about an advertisement or other targeted content, you should contact the responsible provider directly. For information about how you can opt out of receiving targeted advertising from many providers, see Choices About How We Use and Disclose Your Information.
We use information that we collect about you or that you provide to us, including any personal information:
For more information, see Choices About How We Use and Disclose Your Information.
We may use the information we have collected from you to enable us to display advertisements to our advertisers' target audiences. Even though we do not disclose your personal information for these purposes without your consent, if you click on or otherwise interact with an advertisement, the advertiser may assume that you meet its target criteria.
We may disclose aggregated information about our users, and information that does not identify any individual, without restriction.
We may disclose personal information that we collect or you provide as described in this privacy policy:
We may also disclose your personal information:
We strive to provide you with choices regarding the personal information you provide to us. We have created mechanisms to provide you with the following control over your information:
We do not control third parties' collection or use of your information to serve interestbased advertising. However these third parties may provide you with ways to choose not to have your information collected or used in this way. You can opt out of receiving targeted ads from members of the Network Advertising Initiative ("NAI") on the NAI's website.
California residents may have additional personal information rights and choices. Please see Your California Privacy Rights for more information.
You can review and change your personal information by logging into the Application and/or Website and visiting your account profile page.
You may also send us an email at<EMAIL_ADDRESS>to request access to, correct or delete any personal information that you have provided to us. We cannot delete your personal information except by also terminating and deleting your subscription. See our Terms of Use for more information on subscription termination. We may not accommodate a request to change information if we believe the change would violate any law or legal requirement or cause the information to be incorrect.
If you delete your User Contributions from the Application and/or Website, copies of your User Contributions may remain viewable in cached and archived pages, or might have been copied or stored by other Application and/or Website users. Proper access and use of information provided on the Website, including User Contributions, is governed by our terms of use.
California residents may have additional personal information rights and choices. Please see Your California Privacy Rights for more information.
California's "Shine the Light" law (Civil Code Section § 1798.83) permits users of our Application that are California residents to request certain information regarding our disclosure of personal information to third parties for their direct marketing purposes. To make such a request, please send an email to<EMAIL_ADDRESS>We have implemented measures designed to secure your personal information from accidental loss and from unauthorized access, use, alteration, and disclosure.
The safety and security of your information also depends on you. Where we have given you (or where you have chosen) a password for access to certain parts of our Application and/or Website, you are responsible for keeping the password confidential. We ask you not to share your password with anyone. We urge you to be careful about giving out information in public areas of the Application and/or Website like message boards. The information you share in public areas may be viewed by any user.
Unfortunately, the transmission of information via the internet is not completely secure. Although we do our best to protect your personal information, we cannot guarantee the security of your personal information transmitted to our Application and/or Website. Any transmission of personal information is at your own risk. We are not responsible for circumvention of any privacy settings or security measures contained on the Application and/or Website.
It is our policy to post any changes we make to our privacy policy on this page with a notice that the privacy policy has been updated on the Website home page. If we make material changes to how we treat our users' personal information, we will notify you by email to the email address specified in your account or through a notice on the Website home page. The date the privacy policy was last revised is identified at the top of the page. You are responsible for ensuring we have an up-to-date active and deliverable email address for you, and for periodically visiting this privacy policy to check for any changes.
To ask questions or comment about this privacy policy and our privacy practices, contact us at: [OwencitoLLC@gmail.com]


Buying a new car or boat? Remodeling your home? Looking to consolidate higher-interest debt? Whatever your needs, a loan from Altoro Mutual provides you with both savings and simplicity. Our personal loan products include:
For more information about these products, please contact Altoro Mutual.


{% extends "layouts/ukti.html" %} {% import "macros/trade.html" as trade %} {% block main %}
This company does not exist in Data Hub, please create the parent before the child.
Create parent company {% endif %} {% endif %}if you can't find the company you're looking for, try a different search term. check the company's website or any email correspondence that contains company registration details
{% endif %}


***********************************************************
Free Shipping & Returns On All Bras
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo12?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Pass It On! Share This Sale
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo7b?RAF_TRACK=&AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Send To A Friend
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo7c?RAF_TRACK=&AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Now Thru Sunday, 6.2
discover our secret Summer Sale
To Reveal Your Extra Savings Present Coupon In-Store
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo16d?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Or Enter Code 88054241 At Aerie.com
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo16f?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Get Coupon
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo4?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Shop Now
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo16h?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Excludes Undies & Clearance
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo16i?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Aerie Bras $19.99 & Up
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo11a?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
All Swim 25% Off
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo13a?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Shop Bras
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo11c?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Shop Swimsuits
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo13c?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Find Sizes 30A - 40DD At Aerie.com
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo16k?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Forward
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo7f?RAF_TRACK=&AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Become A Fan On Facebook
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo23?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Follow Us On Twitter
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo8?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Pinterest
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo25?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
shopkick
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo1?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Instagram
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo6?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Come Hang Out…Find A Store
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo20?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Mobile Alerts
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo24?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Download The Aerie App
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo18?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Earn Up To 40% Off
Sign Up For AEREWARDS
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo19?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
***********************************************************
Beginning January 14, 2013 at 6:00 am EST through
June 30, 2013 at 11:59 pm PDT receive automatic free shipping on all
orders with the purchase of one (1) or more Aerie bras. Offer is valid
on orders shipping to U.S. & Canadian addresses only. Offer not valid on
international orders. This offer is good for U.S. standard shipping
within 3 to 7 business days pending credit approval and authorization.
Orders to Canadian addresses will be shipped via Canada post within 6 to
10 business days to urban areas and 15 to 22 business days to rural
areas. Shopping bag must contain at least one (1) Aerie bra to qualify
for free shipping. This free shipping offer can be combined with other
discount offers. No discount code is required at the aerie.com shopping
bag. Not applicable toward previously purchased merchandise. All
deliveries are pending credit approval, merchandise availability,
delivery and weather conditions. Free shipping promotion and associated
terms & conditions subject to change at Aerie’s sole discretion.
Beginning January 14, 2013 at 6:00 am EST through June 30, 2013 at 11:59
pm PDT, and shipping to U.S. & Canadian addresses, receive free returns
on all Aerie bras. If you need to return an Aerie bra(s), simply attach
the free return label included with your order. It’s that easy. Offer
excludes other Aerie merchandise, AE and AEO Factory. Free return
promotion and associated terms & conditions subject to change at AE’s
sole discretion.
Beginning May 31, 2013 at 12:00 A.M. EDT through June 2, 2013 at 11:59
P.M. PDT receive 20%, or 25% Off when you enter the discount code within
email at the ae.com and aerie.com shopping bag or at US and Canada AE
and Aerie stores when presenting the printable coupon at checkout. Only
valid in US and Canada. Printable coupon must be presented to cashier to
identify the 20%, or 25% off discount. Discount applied to merchandise
only prior to sales tax and shipping & handling. This coupon is not
redeemable for cash, nor is it applicable toward previously purchased
merchandise. This discount offer cannot be combined with other discount
offers. Excludes AE Clearance, Aerie Clearance, AE Factory Merchandise,
Aerie Factory Merchandise, Aerie undies, and merchandise from these
brands: Adidas, Bass, BC, Bed Stu, Birkenstock, Chronicle, Clarks,
Creative Rec, DV, Eastland, GOLA, Havaianas, Keds, Me Too, MIA,
Minnetonka, New Balance, New Balance/PF Flyers, Old Soles, Palladium,
Pro Keds, Reebok, Saucony, Seychelles, Sperry, Steve Madden, Sweet
Shoes, Tailgate, Timberland, Tretorn, Volley and college and pro
merchandise. Discount and associated terms & conditions subject to
change at AE’s sole discretion.
Beginning May 30, 2013 at 6:00 am EDT through June 4, 2013 in stores and
online, get 25% off Aerie swim merchandise. This 25% off discount is
automatically applied once an Aerie swim item is added to the aerie.com
shopping bag. Discount applies to Aerie swim merchandise costs only, not
tax and shipping & handling costs. This discount is not redeemable for
cash, nor applicable toward previously purchased merchandise. Excludes
Aerie Clearance, AE merchandise, AE swim and merchandise from these
brands: Adidas, Bass, BC, Bed Stu, Birkenstock, Chronicle, Clarks,
Creative Rec, DV, Eastland, GOLA, Havaianas, Keds, Me Too, MIA,
Minnetonka, New Balance, New Balance/PF Flyers, Old Soles, Palladium,
Pro Keds, Reebok, Saucony, Seychelles, Sperry, Steve Madden, Sweet
Shoes, Tailgate, Timberland, Tretorn, Volley and college and pro
merchandise. Discount promotion and associated terms and conditions
subject to change at AE’s sole discretion.
© 2013 AEO MANAGEMENT CO. ALL RIGHTS RESERVED.
***********************************************************
Update Your Email Address:
<EMAIL_ADDRESS>Sign Up For Email:
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo17?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Privacy Policy:
http://e.ae.com/a/tBRq7JTB7u3j4B8y68UNuZn6SPk/aeo15?AAP_FLAG=N&CUSTOMER_NBR=1235023277209
Add<EMAIL_ADDRESS>to your address book.
Our mailing address: 77 Hot Metal Street, Pittsburgh, PA 15203


| BatchSizePredictorImpl |
|
| BatchSizePredictorImpl.Factory |
|
| HashJoinBatch |
Implements the runtime execution for the Hash-Join operator supporting INNER,
LEFT OUTER, RIGHT OUTER, and FULL OUTER joins
|
| HashJoinBatch.HashJoinSpilledPartition |
This holds information about the spilled partitions for the build and probe
side.
|
| HashJoinBatchCreator |
|
| HashJoinHelper |
|
| HashJoinHelperSizeCalculatorImpl |
|
| HashJoinHelperUnusedSizeImpl |
This calculator class is used when the Hash-Join_helper is not used (i.e., return size of zero)
|
| HashJoinMechanicalMemoryCalculator |
|
| HashJoinMechanicalMemoryCalculator.MechanicalBuildSidePartitioning |
|
| HashJoinMechanicalMemoryCalculator.MechanicalPostBuildCalculations |
|
| HashJoinMemoryCalculator.BatchStat |
|
| HashJoinMemoryCalculator.PartitionStatSet |
This class represents the memory size statistics for an entire set of partitions.
|
| HashJoinMemoryCalculatorImpl |
|
| HashJoinMemoryCalculatorImpl.BuildSidePartitioningImpl |
At this point we need to reserve memory for the following:
An incoming batch
An incomplete batch for each partition
If there is available memory we keep the batches for each partition in memory.
|
| HashJoinMemoryCalculatorImpl.NoopBuildSidePartitioningImpl |
|
| HashJoinMemoryCalculatorImpl.NoopPostBuildCalculationsImpl |
|
| HashJoinMemoryCalculatorImpl.PostBuildCalculationsImpl |
In this state, we need to make sure there is enough room to spill probe side batches, if
spilling is necessary.
|
| HashJoinProbeTemplate |
|
| HashTableSizeCalculatorConservativeImpl |
|
| HashTableSizeCalculatorLeanImpl |
|
| JoinStatus |
Maintain join state.
|
| JoinTemplate |
Merge Join implementation using RecordIterator.
|
| JoinTestBase |
|
| JoinUtils |
|
| LateralJoinBatch |
RecordBatch implementation for the lateral join operator.
|
| LateralJoinBatchCreator |
|
| MergeJoinBatch |
A join operator that merges two sorted streams using a record iterator.
|
| MergeJoinCreator |
|
| NestedLoopJoinBatch |
|
| NestedLoopJoinBatchCreator |
|
| NestedLoopJoinTemplate |
|
| PartitionStatImpl |
This class represents the memory size statistics for an entire partition.
|
| RowKeyJoinBatch |
|
| RowKeyJoinBatchCreator |
|
| TestBatchSizePredictorImpl |
|
| TestBuildSidePartitioningImpl |
|
| TestBuildSidePartitioningImpl.MockBatchSizePredictor |
|
| TestHashJoin |
|
| TestHashJoinAdvanced |
|
| TestHashJoinHelperSizeCalculatorImpl |
|
| TestHashJoinJPPD |
|
| TestHashJoinJPPDCorrectness |
|
| TestHashJoinJPPDPlan |
|
| TestHashJoinMemoryCalculator |
|
| TestHashJoinOutcome |
Unit tests of the Hash Join getting various outcomes as input
with uninitialized vector containers
|
| TestHashJoinSpill |
|
| TestHashTableSizeCalculatorConservativeImpl |
|
| TestHashTableSizeCalculatorLeanImpl |
|
| TestJoinEmptyDirTable |
|
| TestLateralJoinCorrectness |
|
| TestLateralJoinCorrectnessBatchProcessing |
|
| TestMergeJoin |
|
| TestMergeJoinAdvanced |
|
| TestMergeJoinMulCondition |
|
| TestMergeJoinWithSchemaChanges |
|
| TestNestedLoopJoin |
|
| TestPartitionStat |
|
| TestPostBuildCalculationsImpl |
|
| TestPostBuildCalculationsImpl.ConditionalMockBatchSizePredictor |
|
| TestPostBuildCalculationsImpl.MockHashJoinHelperSizeCalculator |
|
| TestPostBuildCalculationsImpl.MockHashTableSizeCalculator |
|
| TestSemiJoin |
|


Mumbai, formerly known as Bombay, is the capital of the Indian state of Maharashtra. Along with the neighboring suburbs of Navi Mumbai and Thane, it forms, at 19 million, the world’s fifth most populous metropolitan area. As the financial and entertainment capital of India, Mumbai’s business opportunities, as well as its potential to offer a better standard of living, attract migrants from all over India.
Yet despite Mumbai’s promise of opportunity, more and more children on the city’s streets face a fight for survival. You see them everywhere, yet you prefer to ignore them. They polish your shoes, clean your car, deliver tea, sell roses at traffic signals, hawk newspapers and shiny trinkets on the train and even sift through toxic garbage piles to recycle plastic waste. Local NGOs put their number at 20,000, but the United Nations estimates that there are about2.5 lakh street children in Mumbai.
Poverty forces them into work, beggary and abusive situations. Many are homeless and ought to be protected under rehabilitative schemes as they are vulnerable to exploitation and abuse.
We get children from various areas in Mumbai, including Virar, Nala Sopara, Vasai, Grant Road, Chambur, Dadar, and Mira Road. Although all of our residents were rescued from Mumbai, their origins range throughout India (Andhra Pradesh, Uttar Pradesh, Karnataka, etc.) and Nepal.
Bhayander is a city located 8km from Uttan. We have an extension home for our senior girls who work and study in Bhayander to complete their higher education and learn to support themselves.


Medicare Open Enrollment is coming soon – do you need to make a change?
As the days get shorter and the nights get cooler, you can already see the leaves starting to change. Like the changing leaves, the fall also brings your chance to make changes to your Medicare coverage. That’s because October 15 – December 7 is Medicare Open Enrollment. It’s your chance to review your health care coverage and see if you need to make any changes for next year. Or, you may decide you’re happy with the plan you have now. If that’s the case, and the plan is still being offered next year, you don’t need to do anything.
Over the next few months, look around – you’ll find a wealth of information about your Medicare benefits, especially in these everyday places:
1. In the mail
Look through your mail carefully — you may get important notices from your current plan, Medicare, or Social Security about changes to your coverage or any Extra Help you may get paying for prescription drugs.
Also, look for your Medicare & You handbook. It contains information about all of the Medicare plans in your area. If you decided to “go paperless,” you’ll get an email pointing you to Medicare.gov where you can get all the same information.
You’ll also start to see brochures from companies that offer Medicare health and drug plans. Just remember, be smart about protecting your personal information and your identity — plans aren’t allowed to call or come to your home without an invitation from you.
2. On your computer
Comparing your plan choices is important. Our Medicare Plan Finder is ready with all of the 2015 health and drug plan cost information to make it as easy as possible. Enter the drugs you take to find out how you can lower your costs and review the plan’s ratings to compare plan quality. If you find a plan that meets your needs, you’ll be able to join the plan right online starting October 15. If you haven’t used the Plan Finder before, check out our video to help you get started.
3. In your community
Take a moment as you enjoy these crisp mornings to review the Medicare information that’s out there. You may find a local event — somewhere right around the corner with counselors to help you, like your State Health Insurance Assistance Program. Don’t miss the chance to get personalized help if you need it!
Did you get your mammogram this year?
Mammograms are breast cancer screening tests that can detect a lump before you or your doctor can feel it. This helps to detect breast cancer early, when it’s most treatable. All women over 40 should have a mammogram every 12 months – and Medicare covers it at no cost if your doctor accepts assignment. Talk to your doctor about risk factors and to schedule your next screening.
October is Breast Cancer Awareness month, so let’s spread the word on the fight against breast cancer.
Need therapy services? Be sure you know Medicare’s limits
Are you getting physical therapy after a hip replacement? Speech-language pathology services after a stroke? Anytime you get outpatient physical therapy, occupational therapy, or speech-language pathology services, be sure you know the limits for how much Medicare will pay.
Medicare helps pay for medically-necessary outpatient physical therapy, occupational therapy, and speech-language pathology services. There are limits, called “therapy caps,” on these services when you get them from most outpatient providers.
The therapy cap limits for 2014 are:
- $1,920 for physical therapy (PT) and speech-language pathology (SLP) services combined
- $1,920 for occupational therapy (OT) services
You may qualify to get an exception so that Medicare will continue to pay its share for your services after you reach the therapy cap limits.
October is National Physical Therapy Month – take the time to learn more about Medicare’s limits on therapy services.
Go Green with “Medicare & You”
Love your red, white, and blue “Medicare & You” handbook but love the convenience of getting information on your computer, tablet, or phone even more?
You can get all of the same information in your printed handbook online at Medicare.gov. Learn what’s new, get Medicare costs, and find out what Medicare covers. Even better, the handbook information on the web is updated regularly, so you can instantly find the most up-to-date Medicare information.
Visit Medicare.gov to do a lot of things on your own like replace your Medicare card, change your address, sign up or make changes to your Medicare coverage, and find out important dates. All this in time for October 15 – the start of Medicare Open Enrollment.
Take advantage of some other great features to get just what you need:
- Search quickly for what you want and print only the pages you need, while getting the latest, up-to-date official Medicare information, including the most recent list of available plans
- Get “Medicare & You” in different formats like large print, eBook or audio
- Subscribe to get an email when information is updated
- Access personalized information at MyMedicare.gov
And, if you’d like to trade in your printed copy for a paperless version, we’ve got you covered. You can choose to get your next “Medicare & You” handbook electronically by using the “go paperless” option. In a few simple steps, you’ll be all set. Sign up today, and we’ll send you an email including a link to the new online Medicare & You. It’s instant, current, and convenient.
Getting shots doesn't have to be a pain
Are you taking precautions to make sure you stay healthy? Just like you take your car for scheduled maintenance, it’s important to do what you can to take care of your body. Medicare covers many preventive services, and we make it easy for you to get these 3 shots:
- Flu Shots—Covered once a flu season in the fall or winter.
- Hepatitis B Shots—Covered for people at high or medium risk for Hepatitis B (usually a series of 3 shots).
- Pneumococcal Shot—Covered to help prevent pneumococcal infections (like certain types of pneumonia). Most people only need this shot once in their lifetime.
As we approach the fall, you’ll see these shots offered in many places, such as your local pharmacy, so make sure you take advantage of them. You pay nothing as long as the supplier or doctor accepts assignment for giving the shot.
A strong immune system is way more important than your car, so make the time to stay healthy and take a few minutes to watch our video on National Immunization Awareness Month.


Impeached does not collect any personally identifiable data about you. The only data collected is analytical data for Firebase, as well as advertising data. Your data is shared with Google through Firebase analytics and AdMob.