VEEV virus challenge equine encephalitis Venezuelan strain TrD aerosol IAB strains VEE animal infection vaccine stocks disease Animal viral exposure human humans passage mice CNS cases cDNA similar INH- NHPs []. wild-type studies {border-style U.S. aerosol-acquired demonstrated olfactory px;} selection #ffffff;} resulted subtype use days history material observed propagation selected cell model severe cDNA-cloned outbreak sequence BHK FDA brain clone encephalomyelitis epizootic illness isolates models multiple Med. Strains associated isolate methodology virulence Medical SM, Trop. Vaccine based cells enzootic onset reported result Aerosol Human Table [,]. available clinical consensus death dose febrile humans. initial laboratory lethal low mainly protection single used (Table ... D–D However, Hyg../ajtmh... Program Research Rule [,,,]. [,,]. alphavirus common compared derived early efficacy increased likely master noted passages serum varieties BALB/c Colombia, Disease Strain Trinidad Venezuela, Vero [,] additional complex considered culture cynomolgus doses following high included mouse parent parenteral px; respiratory signs stock working {font-family (e.g., DOD Venezuela animals attenuated bioterrorism day developed fever, font-size generation guinea infected isolated known macaques mosquito-borne nonhuman pfu plaque route uncloned unknown) viremia virulent work (wild-type) Army Based Defense Donkey Drug Encephalitis Hamster Joint NHP Unlike Virol. Virol../JVI...-. antibody characteristics chick comparison documented double; generally generate glycoprotein literature mortality nonlethal potential protect protects response select strain. subtypes suckling supply supported upper using vaccines vivo (strain Acquisition Development Ebola Figure Filovirus Food Rule, Rule. Sci. Selection Texas Trinidad, USAMRIID agents and/or antibodies border-color border-width challenge. chills, clone-derived criteria decreased detected donkey emergence fever findings genetic headache, infection. involved lesions lymphopenia manifested mice, nasal organized pathology perivascular presentation resulting routes solid; strain, study symptoms vaccination viruses---t_Table vitro workers workshop {font-style {font-weight (VEEV (range Acad. Also, Clinical Comparison Exposure GP, Horse Humans IAB, Institute Lastly, Mexico, Model Models Mouse NHPs, Natl. Pathology SMB, University Viremia [], acid adaptation adult analysis approach article assess available. avoid bold cells, central challenge, changes characterization clones committee commonly comparable courier; cross-protection development diversity down-selection duration em; epidemic euthanasia event. extensive followed histopathology history, humans, identified infectious initially lethality levels limited lower major malaise, material. models, monoclonal mosquito mutants mutation mutations nearly necrotizing neuroinvasion neutralizing original outbreaks presented primates progression pt;} reduction regards related replication required resolved responses rhesus sequences severity sore strain), sufficient testing times titers unknown variants variation viremia, viruses


Constructor
new Scene(containerIn) → {Zinc.Scene}
A Zinc.Scene contains Zinc.Geometry, Zinc.Glyphset and
Zinc.CameraControls which controls the viewport and additional features.
It is the main object used for controlling what is and what is not displayed
on the renderer.
Parameters:
| Name | Type | Description |
|---|---|---|
containerIn |
Object | Container to create the renderer on. |
Zinc.Scene
Members
ambient
a THREE.AmbientLight for controlling the ambient lighting of this scene.
directionalLight
A THREE.DirectionalLight object for controlling lighting of this scene.
Methods
addObject(object)
Add any {THREE.Object} into this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
object |
THREE.Object | to be addded into this scene. |
addZincGeometry(geometry, modelId, color, opacity, localTimeEnabled, localMorphColour, external, finishCallback, materialIn) → {Zinc.Geometry}
Add a user provided {THREE.Geometry} into the scene as zinc geometry.
Parameters:
| Name | Type | Description |
|---|---|---|
geometry |
Three.Geometry | The threejs geometry to be added as Zinc.Geometry. |
modelId |
Number | The numeric ID to be given to the newly created geometry. |
color |
THREE.Color | Colour to be assigned to this geometry, overrided if materialIn is provided. |
opacity |
Number | Opacity to be set for this geometry, overrided if materialIn is provided. |
localTimeEnabled |
Boolean | Set this to true if morph geometry is present, overrided if materialIn is provided. |
localMorphColour |
Boolean | Set this to true if morph colour is present, overrided if materialIn is provided. |
external |
Boolean | Set this to true if morph geometry is present, overrided if materialIn is provided. |
finishCallback |
function | Callback once the geometry has been added succssfully. |
materialIn |
THREE.Material | Material to be set for this geometry if it is present. |
Zinc.Geometry
clearAll()
Remove all objects that are created with ZincJS APIs and it will free the memory allocated.
This does not remove obejcts that are added using the addObject APIs.
findGeometriesWithGroupName(GroupName) → {Array}
Find and return all geometries in this scene with the matching GroupName.
Parameters:
| Name | Type | Description |
|---|---|---|
GroupName |
String | Groupname to match with. |
Array
findGlyphsetsWithGroupName(GroupName) → {Array}
Find and return all glyphsets in this scene with the matching GroupName.
Parameters:
| Name | Type | Description |
|---|---|---|
GroupName |
String | Groupname to match with. |
Array
forEachGeometry(callbackFunction)
A function which iterates through the list of geometries and call the callback
function with the geometries as the argument.
Parameters:
| Name | Type | Description |
|---|---|---|
callbackFunction |
function | Callback function with the geometry as an argument. |
forEachGlyphset(callbackFunction)
A function which iterates through the list of glyphsets and call the callback
function with the glyphset as the argument.
Parameters:
| Name | Type | Description |
|---|---|---|
callbackFunction |
function | Callback function with the glyphset as an argument. |
getBoundingBox() → {THREE.Box3}
Get the bounding box of all the object in this scene only.
THREE.Box3
getCurrentTime() → {Number}
Get the current time of the scene.
Number
getDownloadProgress() → {Array}
This function returns a three component array, which contains
[totalsize, totalLoaded and errorDownload] of all the downloads happening
in this scene.
Array
getThreeJSScene() → {THREE.Scene}
Return the internal {THREE.Scene}.
THREE.Scene
getThreeJSScene() → {THREE.Scene}
Get the internal {THREE.Scene}.
THREE.Scene
getZincCameraControls() → {Zinc.CameraControls}
Get the camera control of this scene.
Zinc.CameraControls
getZincGeometryByID() → {Zinc.Geometry}
Get {Zinc.Geoemtry} in this scene by its id.
Zinc.Geometry
isStereoEffectEnable() → {Boolean}
Check if stereo effect is enabled.
Boolean
isTimeVarying() → {Boolean}
Check if any object in this scene is time varying.
Boolean
loadFromViewURL(URL)
Load a legacy file format containing the viewport and its model file from an external
location provided by the url. Use the new metadata format with
Zinc.Scene#loadMetadataURL instead.
Parameters:
| Name | Type | Description |
|---|---|---|
URL |
String | address to the file containing viewport and model information. |
- Deprecated:
- Yes
loadGlyphsetURL(metaurl, glyphurl, groupName, finishCallback)
Load a glyphset into this scene object.
Parameters:
| Name | Type | Description |
|---|---|---|
metaurl |
String | Provide informations such as transformations, colours and others for each of the glyph in the glyphsset. |
glyphurl |
String | regular json model file providing geometry of the glyph. |
groupName |
String | name to assign the glyphset's groupname to. |
finishCallback |
function | Callback function which will be called once the glyphset is succssfully load in. |
loadMetadataURL(url, finishCallback)
Load a metadata file from the provided URL into this scene. Once
succssful scene proceeds to read each items into scene for visualisations.
Parameters:
| Name | Type | Description |
|---|---|---|
url |
String | Location of the metafile |
finishCallback |
function | Callback function which will be called for each glyphset and geometry that has been written in. |
loadModelsURL()
Load a legacy model(s) format with the provided URLs and parameters. This only loads the geometry
without any of the metadata. Therefore, extra parameters should be provided.
- Deprecated:
- Yes
loadOBJ(url, groupName, finishCallback)
Read a OBJ file into this scene, the geometry will be presented as
Zinc.Geometry.
Parameters:
| Name | Type | Description |
|---|---|---|
url |
STRING | location to the STL file. |
groupName |
STRING | name to assign the geometry's groupname to. |
finishCallback |
function | Callback function which will be called once the OBJ geometry is succssfully loaded. |
loadSTL(url, groupName, finishCallback)
Read a STL file into this scene, the geometry will be presented as
Zinc.Geometry.
Parameters:
| Name | Type | Description |
|---|---|---|
url |
STRING | location to the STL file. |
groupName |
STRING | name to assign the geometry's groupname to. |
finishCallback |
function | Callback function which will be called once the STL geometry is succssfully loaded. |
loadView(viewData)
Load the viewport Data from the argument Zinc.Viewport and set it as
the default viewport of this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
viewData |
Zinc.Viewport | Viewport data to be loaded. |
loadViewURL(URL)
Load the viewport from an external location provided by the url.
Parameters:
| Name | Type | Description |
|---|---|---|
URL |
String | address to the file containing viewport information. |
removeObject(object)
Remove any {THREE.Object} from this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
object |
THREE.Object | to be removed from this scene. |
removeZincGeometry(zincGeometry)
Remove a ZincGeometry from this scene if it presents. This will eventually
destroy the geometry and free up the memory.
Parameters:
| Name | Type | Description |
|---|---|---|
zincGeometry |
Zinc.Geometry | geometry to be removed from this scene. |
removeZincGlyphset(zincGlyphset)
Remove a ZincGlyphset from this scene if it presents. This will eventually
destroy the glyphset and free up the memory.
Parameters:
| Name | Type | Description |
|---|---|---|
zincGlyphset |
Zinc.Glyphset | geometry to be removed from this scene. |
setDuration(durationIn)
Set the default duration value for geometries and glyphsets that are to be loaded
into this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
durationIn |
Number | duration of the scene. |
setInteractiveControlEnable(flag)
Enable or disable interactive control, this is on by default.
Parameters:
| Name | Type | Description |
|---|---|---|
flag |
Boolean | Indicate either interactive control should be enabled or disabled. |
setMorphsTime(time)
Set the current time of all the geometries and glyphsets of this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
time |
Number | Value to set the time to. |
setStereoEffectEnable(flag)
Enable or disable stereo effect of this scene.
Parameters:
| Name | Type | Description |
|---|---|---|
flag |
Boolean | Indicate either stereo effect control should be enabled or disabled. |
viewAll()
Adjust zoom distance to include all primitives in scene only.
viewAllWithBoundingBox(boundingBox)
Adjust the viewport to display the desired volume provided by the bounding box.
Parameters:
| Name | Type | Description |
|---|---|---|
boundingBox |
THREE.Box3 | The bounding box which describes the volume of which we the viewport should be displaying. |
inner loadMetaModel(url, timeEnabled, morphColour, groupName, fileFormat, finishCallback)
Load a geometry into this scene, this is a subsequent called from
Zinc.Scene#loadMetadataURL, although it can be used to read
in geometry into the scene externally.
Parameters:
| Name | Type | Description |
|---|---|---|
url |
String | regular json model file providing geometry. |
timeEnabled |
Boolean | Indicate if geometry morphing is enabled. |
morphColour |
Boolean | Indicate if color morphing is enabled. |
groupName |
STRING | name to assign the geometry's groupname to. |
fileFormat |
STRING | name supported formats are STL, OBJ and JSON. |
finishCallback |
function | Callback function which will be called once the geometry is succssfully loaded in. |


val action: PlaybackAction
The PlaybackAction for which the explicit setting is provided
action - The PlaybackAction for which the explicit setting is provided
action


Stability: 3 - Stable
Node provides a tri-directional popen(3)
facility through the
child_process
module.
It is possible to stream data through a child's stdin
, stdout
, and
stderr
in a fully non-blocking way. (Note that some programs use
line-buffered I/O internally. That doesn't affect node.js but it means
data you send to the child process is not immediately consumed.)
To create a child process use require('child_process').spawn()
or
require('child_process').fork()
. The semantics of each are slightly
different, and explained below.
ChildProcess
is an EventEmitter.
Child processes always have three streams associated with them. child.stdin
,
child.stdout
, and child.stderr
. These may be shared with the stdio
streams of the parent process, or they may be separate stream objects
which can be piped to and from.
The ChildProcess class is not intended to be used directly. Use the
spawn()
or fork()
methods to create a Child Process instance.
err
{Error Object} the error.Emitted when:
Note that the exit
-event may or may not fire after an error has occured. If
you are listening on both events to fire a function, remember to guard against
calling your function twice.
See also ChildProcess#kill()
and
ChildProcess#send()
.
code
{Number} the exit code, if it exited normally.signal
{String} the signal passed to kill the child process, if it
was killed by the parent.This event is emitted after the child process ends. If the process terminated
normally, code
is the final exit code of the process, otherwise null
. If
the process terminated due to receipt of a signal, signal
is the string name
of the signal, otherwise null
.
Note that the child process stdio streams might still be open.
Also, note that node establishes signal handlers for 'SIGINT'
and 'SIGTERM
',
so it will not terminate due to receipt of those signals, it will exit.
See waitpid(2)
.
code
{Number} the exit code, if it exited normally.signal
{String} the signal passed to kill the child process, if it
was killed by the parent.This event is emitted when the stdio streams of a child process have all terminated. This is distinct from 'exit', since multiple processes might share the same stdio streams.
This event is emitted after calling the .disconnect()
method in the parent
or in the child. After disconnecting it is no longer possible to send messages,
and the .connected
property is false.
message
{Object} a parsed JSON object or primitive valuesendHandle
{Handle object} a Socket or Server objectMessages send by .send(message, [sendHandle])
are obtained using the
message
event.
A Writable Stream
that represents the child process's stdin
.
Closing this stream via end()
often causes the child process to terminate.
If the child stdio streams are shared with the parent, then this will not be set.
A Readable Stream
that represents the child process's stdout
.
If the child stdio streams are shared with the parent, then this will not be set.
A Readable Stream
that represents the child process's stderr
.
If the child stdio streams are shared with the parent, then this will not be set.
The PID of the child process.
Example:
var spawn = require('child_process').spawn,
grep = spawn('grep', ['ssh']);
console.log('Spawned child pid: ' + grep.pid);
grep.stdin.end();
If .connected
is false, it is no longer possible to send messages.
signal
{String}Send a signal to the child process. If no argument is given, the process will
be sent 'SIGTERM'
. See signal(7)
for a list of available signals.
var spawn = require('child_process').spawn,
grep = spawn('grep', ['ssh']);
grep.on('close', function (code, signal) {
console.log('child process terminated due to receipt of signal '+signal);
});
// send SIGHUP to process
grep.kill('SIGHUP');
May emit an 'error'
event when the signal cannot be delivered. Sending a
signal to a child process that has already exited is not an error but may
have unforeseen consequences: if the PID (the process ID) has been reassigned
to another process, the signal will be delivered to that process instead.
What happens next is anyone's guess.
Note that while the function is called kill
, the signal delivered to the
child process may not actually kill it. kill
really just sends a signal
to a process.
See kill(2)
message
{Object}sendHandle
{Handle object}When using child_process.fork()
you can write to the child using
child.send(message, [sendHandle])
and messages are received by
a 'message'
event on the child.
For example:
var cp = require('child_process');
var n = cp.fork(__dirname + '/sub.js');
n.on('message', function(m) {
console.log('PARENT got message:', m);
});
n.send({ hello: 'world' });
And then the child script, 'sub.js'
might look like this:
process.on('message', function(m) {
console.log('CHILD got message:', m);
});
process.send({ foo: 'bar' });
In the child the process
object will have a send()
method, and process
will emit objects each time it receives a message on its channel.
Please note that the send()
method on both the parent and child are
synchronous - sending large chunks of data is not advised (pipes can be used
instead, see
child_process.spawn
).
There is a special case when sending a {cmd: 'NODE_foo'}
message. All messages
containing a NODE_
prefix in its cmd
property will not be emitted in
the message
event, since they are internal messages used by node core.
Messages containing the prefix are emitted in the internalMessage
event, you
should by all means avoid using this feature, it is subject to change without notice.
The sendHandle
option to child.send()
is for sending a TCP server or
socket object to another process. The child will receive the object as its
second argument to the message
event.
Emits an 'error'
event if the message cannot be sent, for example because
the child process has already exited.
Here is an example of sending a server:
var child = require('child_process').fork('child.js');
// Open up the server object and send the handle.
var server = require('net').createServer();
server.on('connection', function (socket) {
socket.end('handled by parent');
});
server.listen(1337, function() {
child.send('server', server);
});
And the child would the receive the server object as:
process.on('message', function(m, server) {
if (m === 'server') {
server.on('connection', function (socket) {
socket.end('handled by child');
});
}
});
Note that the server is now shared between the parent and child, this means that some connections will be handled by the parent and some by the child.
For dgram
servers the workflow is exactly the same. Here you listen on
a message
event instead of connection
and use server.bind
instead of
server.listen
. (Currently only supported on UNIX platforms.)
Here is an example of sending a socket. It will spawn two children and handle
connections with the remote address <IP_ADDRESS>
as VIP by sending the
socket to a "special" child process. Other sockets will go to a "normal" process.
var normal = require('child_process').fork('child.js', ['normal']);
var special = require('child_process').fork('child.js', ['special']);
// Open up the server and send sockets to child
var server = require('net').createServer();
server.on('connection', function (socket) {
// if this is a VIP
if (socket.remoteAddress === '<IP_ADDRESS>') {
special.send('socket', socket);
return;
}
// just the usual dudes
normal.send('socket', socket);
});
server.listen(1337);
The child.js
could look like this:
process.on('message', function(m, socket) {
if (m === 'socket') {
socket.end('You were handled as a ' + process.argv[2] + ' person');
}
});
Note that once a single socket has been sent to a child the parent can no
longer keep track of when the socket is destroyed. To indicate this condition
the .connections
property becomes null
.
It is also recommended not to use .maxConnections
in this condition.
Close the IPC channel between parent and child, allowing the child to exit
gracefully once there are no other connections keeping it alive. After calling
this method the .connected
flag will be set to false
in both the parent and
child, and it is no longer possible to send messages.
The 'disconnect' event will be emitted when there are no messages in the process of being received, most likely immediately.
Note that you can also call process.disconnect()
in the child process.
command
{String} The command to runargs
{Array} List of string argumentsoptions
{Object}cwd
{String} Current working directory of the child processstdio
{Array|String} Child's stdio configuration. (See below)customFds
{Array} Deprecated File descriptors for the child to use
for stdio. (See below)env
{Object} Environment key-value pairsdetached
{Boolean} The child will be a process group leader. (See below)uid
{Number} Sets the user identity of the process. (See setuid(2).)gid
{Number} Sets the group identity of the process. (See setgid(2).)Launches a new process with the given command
, with command line arguments in args
.
If omitted, args
defaults to an empty Array.
The third argument is used to specify additional options, which defaults to:
{ cwd: undefined,
env: process.env
}
cwd
allows you to specify the working directory from which the process is spawned.
Use env
to specify environment variables that will be visible to the new process.
Example of running ls -lh /usr
, capturing stdout
, stderr
, and the exit code:
var spawn = require('child_process').spawn,
ls = spawn('ls', ['-lh', '/usr']);
ls.stdout.on('data', function (data) {
console.log('stdout: ' + data);
});
ls.stderr.on('data', function (data) {
console.log('stderr: ' + data);
});
ls.on('close', function (code) {
console.log('child process exited with code ' + code);
});
Example: A very elaborate way to run 'ps ax | grep ssh'
var spawn = require('child_process').spawn,
ps = spawn('ps', ['ax']),
grep = spawn('grep', ['ssh']);
ps.stdout.on('data', function (data) {
grep.stdin.write(data);
});
ps.stderr.on('data', function (data) {
console.log('ps stderr: ' + data);
});
ps.on('close', function (code) {
if (code !== 0) {
console.log('ps process exited with code ' + code);
}
grep.stdin.end();
});
grep.stdout.on('data', function (data) {
console.log('' + data);
});
grep.stderr.on('data', function (data) {
console.log('grep stderr: ' + data);
});
grep.on('close', function (code) {
if (code !== 0) {
console.log('grep process exited with code ' + code);
}
});
Example of checking for failed exec:
var spawn = require('child_process').spawn,
child = spawn('bad_command');
child.stderr.setEncoding('utf8');
child.stderr.on('data', function (data) {
if (/^execvp\(\)/.test(data)) {
console.log('Failed to start child process.');
}
});
Note that if spawn receives an empty options object, it will result in
spawning the process with an empty environment rather than using
process.env
. This due to backwards compatibility issues with a deprecated
API.
The 'stdio' option to child_process.spawn()
is an array where each
index corresponds to a fd in the child. The value is one of the following:
'pipe'
- Create a pipe between the child process and the parent process.
The parent end of the pipe is exposed to the parent as a property on the
child_process
object as ChildProcess.stdio[fd]
. Pipes created for
fds 0 - 2 are also available as ChildProcess.stdin, ChildProcess.stdout
and ChildProcess.stderr, respectively.'ipc'
- Create an IPC channel for passing messages/file descriptors
between parent and child. A ChildProcess may have at most one IPC stdio
file descriptor. Setting this option enables the ChildProcess.send() method.
If the child writes JSON messages to this file descriptor, then this will
trigger ChildProcess.on('message'). If the child is a Node.js program, then
the presence of an IPC channel will enable process.send() and
process.on('message').'ignore'
- Do not set this file descriptor in the child. Note that Node
will always open fd 0 - 2 for the processes it spawns. When any of these is
ignored node will open /dev/null
and attach it to the child's fd.Stream
object - Share a readable or writable stream that refers to a tty,
file, socket, or a pipe with the child process. The stream's underlying
file descriptor is duplicated in the child process to the fd that
corresponds to the index in the stdio
array. Note that the stream must
have an underlying descriptor (file streams do not until the 'open'
event has occurred).Stream
objects can be shared.null
, undefined
- Use default value. For stdio fds 0, 1 and 2 (in other
words, stdin, stdout, and stderr) a pipe is created. For fd 3 and up, the
default is 'ignore'
.As a shorthand, the stdio
argument may also be one of the following
strings, rather than an array:
ignore
- ['ignore', 'ignore', 'ignore']
pipe
- ['pipe', 'pipe', 'pipe']
inherit
- [process.stdin, process.stdout, process.stderr]
or [0,1,2]
Example:
var spawn = require('child_process').spawn;
// Child will use parent's stdios
spawn('prg', [], { stdio: 'inherit' });
// Spawn child sharing only stderr
spawn('prg', [], { stdio: ['pipe', 'pipe', process.stderr] });
// Open an extra fd=4, to interact with programs present a
// startd-style interface.
spawn('prg', [], { stdio: ['pipe', null, null, null, 'pipe'] });
If the detached
option is set, the child process will be made the leader of a
new process group. This makes it possible for the child to continue running
after the parent exits.
By default, the parent will wait for the detached child to exit. To prevent
the parent from waiting for a given child
, use the child.unref()
method,
and the parent's event loop will not include the child in its reference count.
Example of detaching a long-running process and redirecting its output to a file:
var fs = require('fs'),
spawn = require('child_process').spawn,
out = fs.openSync('./out.log', 'a'),
err = fs.openSync('./out.log', 'a');
var child = spawn('prg', [], {
detached: true,
stdio: [ 'ignore', out, err ]
});
child.unref();
When using the detached
option to start a long-running process, the process
will not stay running in the background unless it is provided with a stdio
configuration that is not connected to the parent. If the parent's stdio
is
inherited, the child will remain attached to the controlling terminal.
There is a deprecated option called customFds
which allows one to specify
specific file descriptors for the stdio of the child process. This API was
not portable to all platforms and therefore removed.
With customFds
it was possible to hook up the new process' [stdin, stdout,
stderr]
to existing streams; -1
meant that a new stream should be created.
Use at your own risk.
See also: child_process.exec()
and child_process.fork()
command
{String} The command to run, with space-separated argumentsoptions
{Object}cwd
{String} Current working directory of the child processenv
{Object} Environment key-value pairsencoding
{String} (Default: 'utf8')shell
{String} Shell to execute the command with
(Default: '/bin/sh' on UNIX, 'cmd.exe' on Windows, The shell should
understand the -c
switch on UNIX or /s /c
on Windows. On Windows,
command line parsing should be compatible with cmd.exe
.)timeout
{Number} (Default: 0)maxBuffer
{Number} (Default: 200*1024
)killSignal
{String} (Default: 'SIGTERM')callback
{Function} called with the output when process terminateserror
{Error}stdout
{Buffer}stderr
{Buffer}Runs a command in a shell and buffers the output.
var exec = require('child_process').exec,
child;
child = exec('cat *.js bad_file | wc -l',
function (error, stdout, stderr) {
console.log('stdout: ' + stdout);
console.log('stderr: ' + stderr);
if (error !== null) {
console.log('exec error: ' + error);
}
});
The callback gets the arguments (error, stdout, stderr)
. On success, error
will be null
. On error, error
will be an instance of Error
and error.code
will be the exit code of the child process, and error.signal
will be set to the
signal that terminated the process.
There is a second optional argument to specify several options. The default options are
{ encoding: 'utf8',
timeout: 0,
maxBuffer: 200*1024,
killSignal: 'SIGTERM',
cwd: null,
env: null }
If timeout
is greater than 0, then it will kill the child process
if it runs longer than timeout
milliseconds. The child process is killed with
killSignal
(default: 'SIGTERM'
). maxBuffer
specifies the largest
amount of data allowed on stdout or stderr - if this value is exceeded then
the child process is killed.
file
{String} The filename of the program to runargs
{Array} List of string argumentsoptions
{Object}cwd
{String} Current working directory of the child processenv
{Object} Environment key-value pairsencoding
{String} (Default: 'utf8')timeout
{Number} (Default: 0)maxBuffer
{Number} (Default: 200*1024)killSignal
{String} (Default: 'SIGTERM')callback
{Function} called with the output when process terminateserror
{Error}stdout
{Buffer}stderr
{Buffer}This is similar to child_process.exec()
except it does not execute a
subshell but rather the specified file directly. This makes it slightly
leaner than child_process.exec
. It has the same options.
modulePath
{String} The module to run in the childargs
{Array} List of string argumentsoptions
{Object}cwd
{String} Current working directory of the child processenv
{Object} Environment key-value pairsencoding
{String} (Default: 'utf8')execPath
{String} Executable used to create the child processexecArgv
{Array} List of string arguments passed to the executable
(Default: process.execArgv
)silent
{Boolean} If true, stdin, stdout, and stderr of the child will be
piped to the parent, otherwise they will be inherited from the parent, see
the "pipe" and "inherit" options for spawn()
's stdio
for more details
(default is false)This is a special case of the spawn()
functionality for spawning Node
processes. In addition to having all the methods in a normal ChildProcess
instance, the returned object has a communication channel built-in. See
child.send(message, [sendHandle])
for details.
These child Nodes are still whole new instances of V8. Assume at least 30ms startup and 10mb memory for each new Node. That is, you cannot create many thousands of them.
The execPath
property in the options
object allows for a process to be
created for the child rather than the current node
executable. This should be
done with care and by default will talk over the fd represented an
environmental variable NODE_CHANNEL_FD
on the child process. The input and
output on this fd is expected to be line delimited JSON objects.
command
{String} The command to runargs
{Array} List of string argumentsoptions
{Object}cwd
{String} Current working directory of the child processinput
{String|Buffer} The value which will be passed as stdin to the spawned processstdio[0]
stdio
{Array} Child's stdio configuration.env
{Object} Environment key-value pairsuid
{Number} Sets the user identity of the process. (See setuid(2).)gid
{Number} Sets the group identity of the process. (See setgid(2).)timeout
{Number} In milliseconds the maximum amount of time the process is allowed to run. (Default: undefined)killSignal
{String} The signal value to be used when the spawned process will be killed. (Default: 'SIGTERM')maxBuffer
{Number}encoding
{String} The encoding used for all stdio inputs and outputs. (Default: 'buffer')pid
{Number} Pid of the child processoutput
{Array} Array of results from stdio outputstdout
{Buffer|String} The contents of output[1]
stderr
{Buffer|String} The contents of output[2]
status
{Number} The exit code of the child processsignal
{String} The signal used to kill the child processerror
{Error} The error object if the child process failed or timedoutspawnSync
will not return until the child process has fully closed. When a
timeout has been encountered and killSignal
is sent, the method won't return
until the process has completely exited. That is to say, if the process handles
the SIGTERM
signal and doesn't exit, your process will wait until the child
process has exited.
command
{String} The command to runargs
{Array} List of string argumentsoptions
{Object}cwd
{String} Current working directory of the child processinput
{String|Buffer} The value which will be passed as stdin to the spawned processstdio[0]
stdio
{Array} Child's stdio configuration. (Default: 'pipe')stderr
by default will be output to the parent process' stderr unless
stdio
is specifiedenv
{Object} Environment key-value pairsuid
{Number} Sets the user identity of the process. (See setuid(2).)gid
{Number} Sets the group identity of the process. (See setgid(2).)timeout
{Number} In milliseconds the maximum amount of time the process is allowed to run. (Default: undefined)killSignal
{String} The signal value to be used when the spawned process will be killed. (Default: 'SIGTERM')maxBuffer
{Number}encoding
{String} The encoding used for all stdio inputs and outputs. (Default: 'buffer')execFileSync
will not return until the child process has fully closed. When a
timeout has been encountered and killSignal
is sent, the method won't return
until the process has completely exited. That is to say, if the process handles
the SIGTERM
signal and doesn't exit, your process will wait until the child
process has exited.
If the process times out, or has a non-zero exit code, this method will
throw. The Error
object will contain the entire result from
child_process.spawnSync
command
{String} The command to runoptions
{Object}cwd
{String} Current working directory of the child processinput
{String|Buffer} The value which will be passed as stdin to the spawned processstdio[0]
stdio
{Array} Child's stdio configuration. (Default: 'pipe')stderr
by default will be output to the parent process' stderr unless
stdio
is specifiedenv
{Object} Environment key-value pairsuid
{Number} Sets the user identity of the process. (See setuid(2).)gid
{Number} Sets the group identity of the process. (See setgid(2).)timeout
{Number} In milliseconds the maximum amount of time the process is allowed to run. (Default: undefined)killSignal
{String} The signal value to be used when the spawned process will be killed. (Default: 'SIGTERM')maxBuffer
{Number}encoding
{String} The encoding used for all stdio inputs and outputs. (Default: 'buffer')execSync
will not return until the child process has fully closed. When a
timeout has been encountered and killSignal
is sent, the method won't return
until the process has completely exited. That is to say, if the process handles
the SIGTERM
signal and doesn't exit, your process will wait until the child
process has exited.
If the process times out, or has a non-zero exit code, this method will
throw. The Error
object will contain the entire result from
child_process.spawnSync


--- layout: page title: "404 Not Found" permalink: /404 ---
There doesn't appear to be anything here. Sorry about that!
If you've followed a link expecting something to be here, you can file a GitHub issue on my website's repository.


Following are instructions to build and install the programs in this distribution.
Note that the automatic build process inspects the machine environment and tests for the presence of system header files and the contents of these files to determine if certain features are available. When one or more of these features are present, the code is compiled to use them; if not, no special code is compiled. However, even if the code is compiled to use these features, the code does a special test at run time to see if one or more are actually present and avoids using them if not present. In such cases a warning message is sent to the system log, but the daemon should still work properly.
Make sure that you have all necessary tools for building executables.
These tools include cc/gcc, make, awk, sed, tr, sh, grep,
egrep
and a few others. Not all of these tools exist in the
standard distribution of modern Unix versions (compilers are likely to
be an add-on product - consider using the gnu
tools and
gcc
compiler in this case). For a successful build, all of
these tools should be accessible via the current path.
Use the configure
command to perform an automatic
configuration procedure. This procedure normally includes the debugging
code, which can be useful in diagnosing problems found in initial test,
and all reference clock drivers known to work with each machine and
operating system. Unless memory space is at a premium, this is a
sensible strategy and saves lots of messy fiddling. If you need to
delete either the debugging code or one or more or all reference clock
drivers to save space, see the Configuration
Options page.
If your site supports multiple architectures and uses NFS to share
files, you can use a single source tree to compile executables for all
architectures. While running on a target architecture machine and with
the distribution base directory active, create a subdirectory using a
command like mkdir `config.guess`
, which will create an
architecture-specific directory with name peculiar to the architecture
and operating system. Then change to this directory and configure with
the ../configure
command. The remaining steps are the same
whether building in the base directory or in the subdirectory.
Use the make
command to compile all source modules,
construct the libraries and link the distribution. Expect few or no
warnings using cc
and a moderate level of warnings using
gcc
. Note: On some Unix platforms the use of
gcc
can result in quite a few complaints about system
header files and type inconsistencies, especially about pointer
variables. This is usually the case when the system header files are not
up to ANSI standards or gcc
-isms. While the autoconfigure
process is quite thorough, the Unix programming cultures of the various
workstation makers still remain idiosyncratic.
As root, use the make install
command to install the
binaries in the destination directory. You must of course have write
permission on the install destination directory. This includes the
programs xntpd
(the daemon), xntpdc
(an xntpd
-
dependent query program), ntpq
(a
standard query program), ntpdate
(an rdate
replacement for boot time date setting and sloppy
time keeping) and ntptrace
(a
utility useful to find the primary (stratum-1) servers). In some
systems, the tickadj
(a utility
useful to adjust kernel variables) is installed. If the precision time
kernel modifications are present, the ntptime
(a utility useful to debug
kernel time functions) is installed.
You are now ready to configure the daemon and start it. You will need
to create a NTP configuration file ntp.conf
and possibly a
cryptographic key file ntp.keys
. Directions for doing that
are in the Notes on Configuring NTP and Setting up
a NTP Subnet. A tutorial on debugging technique is in NTP Debugging Technique. If problems peculiar to
the particular hardware and software environment are suspected, browse
the Hints and Kinks page.
Bug reports of a general nature can be sent to David Mills (mills@udel.edu). Bug reports of a specific nature on features implemented by the programmer corps mentioned in the Copyright page should be sent directly to the implementor listed in that page, with copy to<EMAIL_ADDRESS>Please include the version of the source distribution (e.g., xntp3-5.87) in your bug report.
Please include the output of config.guess
in
your bug report.
It will look something like:
pdp11-dec-fuzzos3.4
Additional make
commands
make clean
make distclean
clean
, but cleans out all directories
in preparation for a new distribution release.
make dist
make distclean
, but constructs
compressed tar files for distribution.
Under Windows NT, you will need Visual C++ 4.0
or above,
InstallShield
SDK (comes with VC++
),
Perl5
and some version of the archiving program
ZIP
.
See the ./scripts/wininstall/readme.nt
file for
directions to compile the sources, build the libraries and link the
executables. Initiate the build by running either bldrel.bat
or blddbg.bat
to compile all of the source and create an
InstallShield
based graphical installation package.
To install the executables, make sure that you are logged in as a
system account, or one with administrator privileges such as the
"administrator" account. As part of the build an
InstallShield
based graphical installer was created. Run
\xntp\scripts\wininstall\intel\disk1\setup.exe
to begin the
installation. This installer will prompt for basic defaults, copy the
binaries, install the service, and start it up. The other option is
to run \xntp\scripts\wininstall\distrib\install.bat
which
will do the basic installation from the command line.


Product Name:
Product current Price:
Product Link:
Product xPath to price:
Product xPath to title:
Back to all products


THREEPX Class
ThreePx synchronises the three.js
frustrum with that of the CSS.
See working examples in the examples folder.
Constructor
THREEPX
-
wrapper
-
[options]
Parameters:
-
wrapper
HTMLElementThe
THREEPX.renderer.domElement
will be added at position 0 of the wrapper. -
[options]
Object optionalThe default options are:
- configurable:
false
Enable this option to override if you want override the API. - autoInitializeThreejs:
true
Enable or disable the creation of the scene, the renderer and the camera on the new ThreePx instance. - autoResize:
true
Enable or disable the bind between the wrapper size and theTHREEPX.renderer.domElement
. - debug:
false
Enable or disable some three.js elements added to the scene to debug.
- configurable:
Example:
var wrapperElement = document.getElementById('wrapper'),
threepx = new THREEPX(wrapperElement),
mesh = new THREE.Mesh(
// define your mesh
)
;
threepx.scene.add(mesh);
var lastTimestamp = new Date();
threepx.renderFunction = function (timestamp, width, height) {
var delta = timestamp - lastTimestamp,
angle = 0.02 * delta * 2 * Math.PI / 1000
;
mesh.rotation.x += angle;
mesh.rotation.y += angle;
mesh.position.set(100 + width/2, 100 - height/2, 0);
lastTimestamp = timestamp;
return true;
}
Item Index
Properties
autoResize
Bollean
If autoResize is set to true,
the size of the THREEPX.renderer.domElement
is bind
to the wrapper size.
This property can be set in the options passed to the constructor.
Default: true
camera
THREE.PerspectiveCamera
The three.js camera used by the instance of ThreePx.
Camera will be automatically added to scene.
cameraChanged
Boolean
A flag to know if the camera has changed during the frame.
canBeUsed
Boolean
static
ThreePx need WebGL and requestAnimationFrame() to be used. If these requirements are not satisfied canBeUsed property is set to false.
enable
Boolean
Enable or disable the rendering.
Default: true
explicitHeight
Integer
If the explicit height is not null or not undefined,
the height is set tho the explicit height
and the autoResize is not effective for the height.
Update the value will generate a three.js render.
Default: undefined
explicitWidth
Integer
If the explicit width is not null or not undefined,
the width is set tho the explicit width
and the autoResize is not effective for the width.
Update the value will generate a three.js render.
Default: undefined
fov
Float
The field of view given for the perspective property.
height
Integer
The actual height of the THREEPX.renderer.domElement
.
If explicitHeight property is null or undefined,
the width is equal to the THREEPX.wrapper.clientHeight
else the height is equal to explicitHeight property.
perspective
Float
The perspective parse from the wrapper CSS.
Default: 2000 if CSS perspective is not defined for the wrapper.
rendererChanged
Boolean
A flag to know if the renderer has changed during the frame.
renderFunction
Function
An user function called at the end of the render process. The function must return true to make the renderer render.
Example:
threepx.renderFunction = function (timestamp, width, height) {
cube.rotation.y += 0.01;
return true;
}
scene
THREE.Scene
The three.js scene used by the instance of ThreePx.
Camera will be automatically added to scene.
sceneChanged
Boolean
A flag to know if the scene has changed during the frame.
version
String
static
The version of ThreePx.
version
String
The version of ThreePx.
viewChanged
Bollean
Set to true if the view changed during the frame.
width
Integer
The actual width of the THREEPX.renderer.domElement
.
If explicitWidth property is null or undefined,
the width is equal to the THREEPX.wrapper.clientWidth
else the width is equal to explicitWidth property.
wrapper
HTMLElement
The wrapper used by the instance of ThreePx.
wrapperChanged
Boolean
Set to true if the wrapper changed during the frame.


Ormigo, our new start-up situated in the wonderful german city of Cologne, is looking for some people.

Ormigo is looking for some people. We are starting out with Developers. We are looking for two people at the moment, but if there are three perfect fits we are not likely to decline any of them.

This is actually why I am not posting one description but a general overview about what kind of things we are looking for. You are here to grow, we grow together, and we need diversity. If you feel yourself in part of the job cloud coming along, please tell us.

The â€œI hate HTMLï¿½? PHP Coder

You like developing software that scales. You love it when an idea from the edge works out great. You are thorough and can take a weird idea, a rough sketch, to a beautiful, object oriented, scalable and testable code base. You are not afraid to say â€œNo, thatâ€™s not going to work.ï¿½? but will have the inner drive to make it happen anyway.

You have deep knowledge and long term experience with PHP and MySQL, especially the newest versions of those two, having understood that writing object oriented code is the way to go. You have worked with XML/XSLT and Web Services as external services to improve your platform. You know that handling data is a finicky thing and worked with big amounts of them.

You have been working on online projects for ages and have been especially active in backend development. If you have worked in a statistics heavy performance marketing environment, advertising solutions, WebServices and billing systems we want to hear from you. Knowing about Tagging, Unit Testing, Mapping, Geocoding, ajax, RSS, Atom and all the Web 2.0 hype is a plus. If you managed teams yourself, especially external teams and developers, thatâ€™s a big plus.

What do we want from you? A short introduction letter why you think you are the person that will rock this place to new heights, a short CV and links to a few examples of what you worked on with a few lines of what exactly you did there.

What we offer? An exciting work place, building a backend of a truly scalable platform within an IT centric corporation. You will be one of the people making that happen and you will be here from the start.

The Oversight Coder

You like building applications and services for the web. You dig templating systems and separating code from presentation and want all of this nice and clean. Things need to scale and you want to change your presentation without changes in the backend.

You have a full understanding of PHP and MySQL and feel at home in them but also feel a turn-on thinking about CSS, XML/XSLT and ajax. Above that you are also somebody that has understood the importance of good project management and want to grow more in that respect too.

We are also accepting suggestions from people who really want to do the front end part, love HTML, ajax and css. Who are designers and coders at the same time and love having access to data to mangle around. A quality assurance guy, with PHPUnit2 experience, that wants to do a bit of hands on coding would be one of the next hires. So bring the resumes on.

You can send all this directly to me or contact me via Skype (othylmann). Looking forward to hearing from you. <!– technorati tags start –>

Technorati Tags: coder, Developers, Jobs, Ormigo, php, puppy

<!– technorati tags end –>


HWPC
Link
Link
Options
Sub-link
Sub-link
Sub-link
Sub-link
Home
Logout
Settings
About
{{ i.contact }}
{{ i.contact }}
Ticket ID: {{i.id}}
Hawkeye West Pest Control
1795 Park Circle
Clarion, Iowa 50525
Lic # 02318-000
515-532-3499
800-467-5231
Service Location
Name of Location
Address of Location
City of Location
Bill To Location
Name of Location
Address of Location
City of Location
{{ i.service }}
Type of Service:
Type of Service:
{{ i.note }}
Note:
Note:
Note:
Note:
{{ i.date }}
{{ i.time }}
Route:
123
Contact:
George Washington Carver
Phone:
515.999.0000
Service Fee:
$0.00
??% Tax:
$0.00
Total Due:
$00.00
STATUS:
PAID
CHARGE


Local Weather
Location
Name:
Region:
Country:
Current Time:
Temperature
Temperature:
Condition:
Reset
Change to Fahrenheit


Data Mining
Python Development
Statistics
Data Visualisation
Web App
Dashboard
Database Management
Business Intelligence
SQL
Time-Series Analysis
Machine Learning
Global Change
Atmospheric CO2
EucFACE
Virtual Environment
Conda
ETL
Modelling
GitHub
Project Monitoring


Deal Hunter (BETA)
Select Your Target!
CEO/ Owner
Sales Exec.
Marketing Exec.
Business Dev. Exec.


HTTP 400: Request Error (invalid_request)
HTTP 400: Your request could not be processed. Request could not be handled. The request could not be understood bu the server due to malformed syntax. The client should NOT repear the request without modifications. This could be caused by a misconfiguration, or possibly a malformed request.
For assistance, please contact Fidelity Techline @<PHONE_NUMBER>. Device ID: WCZ1C02


Symbol Index for "Text Valued Qualifier"
Symbol Index for diagram
"Text Valued Qualifier"
Category Valued Qualifier (Class)
Image Valued Qualifier (Class)
Measured Qualifier (Class)
Phenomenon Qualifier (Class)
PhenQ/Value Type (Generalization Node)
Text Valued Qualifier (Class)
Timepoint Valued Qualifier (Class)


Press the button below to flip this card and edit the code. When you are done, you can press the button below to see the result again.
I've used prism js for syntax highlighting and scoped polyfill to get <style scoped>
to work. Flip effect taken from here.


Proposal for Lang Package
(0) Rationale
The standard Java libraries fail to provide enough methods for
manipulation of its main components. The Lang Package provides
these extra methods. There are other classes which might justifiably
be included in java.lang someday, this package also provides for them.
(1) Scope of the Package
This proposal is to create a package of Java utility classes for the
classes that are in java.lang's hierarchy, or are considered to be so
standard as to justify existence in java.lang. The Lang Package
also applies to primitives and arrays.
(1.5) Interaction With Other Packages
Lang relies only on standard JDK 1.2 (or later) APIs for
production deployment. It utilizes the JUnit unit testing framework for
developing and executing unit tests, but this is of interest only to
developers of the component. Lang will be a dependency for
several existing components in the open source world.
No external configuration files are utilized.
(2) Initial Source of the Package
The initial classes came from the Commons.Util subproject.
The proposed package name for the new component is
org.apache.commons.lang.
(3) Required Jakarta-Commons Resources
- CVS Repository - New directory lang in the
jakarta-commons CVS repository.
- Mailing List - Discussions will take place on the general
<EMAIL_ADDRESS>mailing list. To help
list subscribers identify messages of interest, it is suggested that
the message subject of messages about this component be prefixed with
[lang].
- Bugzilla - New component "Lang" under the "Commons" product
category, with appropriate version identifiers as needed.
- Jyve FAQ - New category "commons-lang" (when available).
(4) Initial Committers
The initial committers on the Lang component shall be as follows:
- Henri Yandell (bayard)
- Daniel Rall (dlr)
- Stephen Colebourne (scolebourne)


bigeyex
Lv 20
Curator
350/2250 xp
0 notification
Upcoming
Health Data Hackathon
New Projects
c4fcm/Promise-Tracker-Mobile
codeafrica / github-africa
ushahidi / SMSSync
More


Success: ASCII conversion is characters long.
How did the decoding work?
Well, first let's look at what happens when we convert the hexadecimal to binary, and see what patterns we can notice.
The binary format of your message started with seven chunks of 40-bit ranges of zero, and five 40-bit ranges of one at the tail. You wouldn't necessarily notice the significance of the numbers five and seven from those series of bits alone. However, it provides enough context to see that between this "silence" is a kind of structure, with blocks of 35 bits (which may be zero or one) interleaved with 5 bits that are zero.
Setting up the context for realizing these gaps are significant is the fact that after the silence, a signal seems to be bookended by 5 solid 35-bit blocks at the beginning, and 7 solid 35-bit blocks at the end. By this point, we might be cued that 35 is a semiprime number (product of two primes). Thus we can see that the numbers 5 and 7 are supposed to be significant.
If we consider those factors as dimensions of a rectangle, then we can convert the chunks between the solid blocks and what's between them into 5x7 bitmaps:
Ignoring the solid blocks (the "meter"), we can read the message even before we've converted it into ASCII!
But being able to read it isn't the only requirement for a safe ASCII conversion. The specific numbers must be looked up in a standard table, to produce the string. In this case, all the numbers matched our table...so your message could be decoded. It could thus also be drawn in a stroked vector font (for instance).


|
NASA World Wind | ||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Interface Summary | |
|---|---|
| Layer |
| Class Summary | |
|---|---|
| AbstractGraticuleLayer | Displays a graticule. |
| AbstractLayer | |
| AirspaceLayer | The Airspace class manages a collection of Airspace objects
for rendering and picking. |
| AnnotationLayer | The AnnotationLayer class manages a collection of Annotation objects
for rendering and picking. |
| BasicLayerFactory | A factory that creates Layer instances. |
| BasicTiledImageLayer | |
| BasicTiledImageLayer.DownloadPostProcessor | |
| BasicTiledImageLayerBulkDownloader | Downloads imagery not currently available in the World Wind file cache or a specified file store. |
| CompassLayer | |
| CrosshairLayer | Renders a crosshair icon in the viewport center or at a specified location. |
| GraticuleRenderingParams | |
| GraticuleSupport | |
| IconLayer | The IconLayer class manages a collection of WWIcon objects for
rendering and picking. |
| LatLonGraticuleLayer | Displays the geographic latitude/longitude graticule. |
| LayerConfiguration | An implementation of the DataConfiguration interface, which uses a Layer
configuration document as its backing store. |
| LayerList | |
| MarkerLayer | |
| RenderableLayer | The RenderableLayer class manages a collection of Renderable objects
for rendering, picking, and disposal. |
| ScalebarLayer | Renders a scalebar graphic in a screen corner. |
| SkyColorLayer | Paints the sky color background depending on altitude. |
| SkyGradientLayer | Renders an atmosphere around the globe and a sky dome at low altitude. |
| StarsConvertor | Converts a star background based on a subset of ESA Hipparcos catalog to ByteBuffer. |
| StarsLayer | Renders a star background based on a subset of ESA Hipparcos catalog. |
| SurfaceImageLayer | Displays a collecion of local images on the globe. |
| SurfaceShapeLayer | The SurfaceShapeLayer class manages a collection of Renderable objects for
rendering, picking, and disposal. |
| TerrainProfileLayer | Displays a terrain profile graph in a screen corner. |
| TextureTile | This class manages the conversion and timing of image data to a JOGL Texture, and provides an interface for binding the texture and applying any texture transforms to align the texture and texture coordinates. |
| TiledImageLayer | |
| ViewControlsLayer | Display onscreen view controls. |
| ViewControlsSelectListener | Controller for onscreen view controls. |
| WorldMapLayer | Displays a world map overlay with a current position crosshair in a screen corner. |
|
NASA World Wind | ||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


{% extends "base.html" %} {% block title %}CoralNet - Signup Confirmation{% endblock %} {% block page-specific-includes %} {{ form.media }} {% endblock %} {% block content %}
Your request has been received, thanks!


API Integration Tutorials
A collection of tutorials to help you integrate with Chargebee API
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo
Setup configuration View live demo Read more View source in Github View video demo


| Job ID | Competition | Function | Status |
|---|---|---|---|
| ${minionId} / ${job.jid} |
${job.returnedOn|timeAgo}
${job.returnedOn|dateFormat} |
> ${job.function} |
${job.failedCount} failed ${job.changedCount} changed ${job.successCount} succeeded |


Contact Us
Tell us about your issue so we can help you more quickly
We Are Multi
That Inspires Our Customers & Clients
How can we help?
Office # 38, Suite 54 Elizebth Street, Victoria State, Newyork, USA 33026
+38 000 129900
<EMAIL_ADDRESS>Multi
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sequi ratione, dolor quisquam autem tempora odit ex vero fugit deserunt praesentium.
RECENT POSTS
Awesome Design with Overviews
Great Design with Features
Limitless function & Works
Multi is simple and clean design
CONTACT INFO


@(bucket: String = "aws-frontend-archive")(implicit request: RequestHeader, context: model.ApplicationContext)
@import conf.switches.Switches.ContentPresser
@admin_main("Content Presser (archiver)", isAuthed = true) {
Press (archive) an article / interactive page
-
This will only work as expected for article / interactive pages.
-
This tool will only press articles / interactive pages. To serve the pressed content to readers, please contact the dotcom team (dotcom.platform@@theguardian.com).
-
Please provide full URLs like https://www.theguardian.com/path
-
Pressing an article / interactive can take ~10 seconds.
Progress of pressing
No URL provided
No pressing in progress
Un-press an article / interactive
-
Un-pressing is not currently an automated process. Please contact the dotcom team (dotcom.platform@@theguardian.com) if you need to un-press an article / interactive.
}


--- layout: archive title: Zulip Chat Archive permalink: /stream/113488-general/topic/Simon's.20.22traversable.22.20PR's.2E.html ---
What do these do? I can't understand anything :-(
You can have a look at https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/type.20class.20traversable but I fear this really CS and software engineering.
I was also planning to ask after Simon will be done with his series of PR
Oh so it's nothing to do with the "transportable" proving that if X is a perfectoid space and X equiv Y then Y is a perfectoid space?
I think Simon mentioned a link at some point
It's very much CS, though I wouldn't call it software engineering. If you're interested in references, see:
https://hackage.haskell.org/package/base/docs/Data-Traversable.html
I believe Simon is setting up infrastructure to simplify expression manipulation and, therefore, tactic writing.
Aah thanks!
@Sean Leather that's pretty much it. Plus, I think Lean should be like Haskell as a programming language and traversable should help with that.
@Kevin Buzzard Don't despair, transportable
is still under development.
... and so is mono
, if people still remember it
Last updated: Apr 24 2020 at 19:02 UTC


START NEW GAME
Mario Bros Pig Dice
Player one, enter your name:
Player two, enter your name:
START GAME
's total Score:
Roll!
Hold!
Total Roll Score:
's total Score:


How RUNTESTS Searches for Test Cases
When you call runtests with no input arguments:
>> runtests
it automatically searches for all the test cases in the current directory. It looks for test cases in three types of M-files:
1. An M-file function whose name begins with "test" or "Test" and that does not return an output argument. Such a function is considered to be a single test case.
2. An M-file function whose name begins with "test" or "Test" and that returns an output argument that is a test suite. Such a function is considered to contain subfunction-style test cases. Each subfunction whose name begins with "test" or "Test" is a test case.
3. An M-file that defines a subclass of TestCase. Each method beginning with "test" or "Test" is a test case.
runtests uses the TestSuite static methods fromName and fromPwd to automatically construct the test suites.
Here are a couple of examples.
TestSuite.fromName takes an M-file name, determines what kind of test file it is, and returns a cell array of test case objects.
cd examples_general test_suite_1 = TestSuite.fromName('testSetupExample')
test_suite_1 = TestSuite handle Properties: TestComponents: {[1x1 FunctionHandleTestCase] [1x1 FunctionHandleTestCase]} Name: 'testSetupExample' Location: 'C:\Work\matlab_xunit\doc\examples_general\testSetupExample.m'
TestSuite.fromPwd returns a test suite based on all the test files in the current directory.
test_suite_2 = TestSuite.fromPwd()
test_suite_2 = TestSuite handle Properties: TestComponents: {1x6 cell} Name: 'C:\Work\matlab_xunit\doc\examples_general' Location: 'C:\Work\matlab_xunit\doc\examples_general'


--- layout: page status: publish published: true title: Historic Lake Bonneville author: display_name: AGRC Staff login: Map Utah email<EMAIL_ADDRESS>url: '' author_login: Map Utah author_email<EMAIL_ADDRESS>wordpress_id: 10232 wordpress_url: http://gis.utah.gov/?page_id=10232 date: '2012-07-11 13:55:32 -0600' date_gmt: '2012-07-11 19:55:32 -0600' categories: [] tags: - SDE - sgid - Water - Data - utah - gis - map - mapping - dataset - agrc - shapefile - gdb - geographic - database - vector - arcgis - history - lake bonneville ---
Data Type: GIS Data Layer
Steward(s): AGRC
Abstract:
Water.HistoricLakeBonneville represents the geographic extent of the historic Lake Bonneville shoreline.
Usage: No usage tips are available at this time.
Last Update: Unknown
Contact: AGRC
Links:


Welcome to the SAIGE-BRUSH documentation!¶
SAIGE-Biobank Re-Usable SAIGE Helper (SAIGE-BRUSH) is an implementation of the popular SAIGE GWAS software. Fully containerized and ready for use without installation or any code handling. Submit your configuration file and the rest is done.
Installation¶
Good news! There is no installation required to use this pipeline and it should be OS agnostic. There are only 2 true system dependencies and most HPCs and shared resources already have these dependencies installed:
Singularity version >= 3.0
Golang version >= go1.13.5 (has been tested on versions go1.13.5 and go1.15.2 on a Linux OS).
If not, you can install Singularity and install Golang using the links on your local computer. Both should be available across OS platforms for Windows, MacOS, and Linux.
If you haven't visited our github repository, please do so by visiting the SAIGE-BRUSH github repo. The repo has all the information on how to access the executable and pull down the container.
Full Pipeline Overview¶
Getting Started¶
Understanding File Formats¶
- Formatting the Required Files
- Parameter: ChromosomeLengthFile
- Parameter: ImputeSuffix
- Parameter: PhenoFile
- Parameter: Plink
- Parameter: Pheno
- Parameter: Covars
- Parameter: SampleID
- Parameter: InfoFile
- Parameter: ImputationFileList
- Parameter: SparseGRM
- Parameter: SampleIDFile
- Parameter: NullModelFile
- Parameter: VarianceRatioFile
- Parameter: AssociationFile
Quick Start and Examples¶
FAQs¶
See also
Need more help? Please submit any questions or bugs to the SAIGE-BRUSH github issues page
Acknowledgements¶
The most important acknowledgment is for the group of developers, investigaters, scientists, and researchers of SAIGE . This pipline is honestly just an automated wrapper to most of their work. They have an excellent github page here at https://github.com/weizhouUMICH/SAIGE -- The entire team is very responsive to github questions. They are tirelessy working on newer and more complex versions of SAIGE, and for that I must thank them. It is an amazing piece of software! Please read their publication:
Zhou, W., Nielsen, J. B., Fritsche, L. G., Dey, R., Gabrielsen, M. E., Wolford, B. N., LeFaive, J., VandeHaar, P., Gagliano, S. A., Gifford, A., Bastarache, L. A., Wei, W. Q., Denny, J. C., Lin, M., Hveem, K., Kang, H. M., Abecasis, G. R., Willer, C. J., & Lee, S. (2018). Efficiently controlling for case-control imbalance and sample relatedness in large-scale genetic association studies. Nature genetics, 50(9), 1335–1341. https://doi.org/10.1038/s41588-018-0184-y
All of this work could not be done without the full support of the Colorado Center for Personalized Medicine (CCPM) under the guidance of their Biobank, and the Translation Informatics Services (TIS) sector, among several input from exerpienced scientists and professor within CCPM whose expertise is in GWAS.


Wordpress.com is a blog hosting platform by the makers of the Wordpress blogging software. Search results are currently limited to the first 10 hits.
| ALM Name | wordpress |
| ALM Configuration | default |
| ALM Core Attributes | id url (as link) date (as epoch_time) |
ALM Other Attributes | title author content |
| Protocol | REST |
| Format | JSON |
| Rate-limiting | 100/min |
| Authentication | no |
| Restriction by IP Address | no |
| API URL | http://en.search.wordpress.com/?q="DOI"&t=post&f=json&size=20 |
| License | unknown |
Example Response
[
{
"title": "Presentation on Citation Rate for Shared Data",
"link": "http://researchremix.wordpress.com/2007/07/12/presentation-on-citation-rate-for-shared-data/",
"epoch_time": "1184254598",
"author": "Heather Piwowar",
"guid": "http://researchremix.wordpress.com/2007/07/12/presentation-on-citation-rate-for-shared-data/",
"content": "Whoosh... where has the time gone.\r\n\r\nA few weeks ago, I attended and presented at the NLM Biomedical Informatics Trainee conference. My presentation was well-received, despite (or perhaps […]"
},
{
"title": "Open Science Challenge",
"link": "http://www.r-bloggers.com/open-science-challenge/",
"epoch_time": "1357632000",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/open-science-challenge/",
"content": "Open Science\n\nScience is becoming more open in many areas: publishing, data sharing, lab notebooks, and software. There are many benefits to open science. For example, sharing research data […]"
},
{
"title": "Open Science Challenge",
"link": "http://www.r-bloggers.com/open-science-challenge/",
"epoch_time": "1357632000",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/open-science-challenge/",
"content": "Open Science\n\nScience is becoming more open in many areas: publishing, data sharing, lab notebooks, and software. There are many benefits to open science. For example, sharing research data […]"
},
{
"title": "Open Science Challenge",
"link": "http://www.r-bloggers.com/open-science-challenge-2/",
"epoch_time": "1357632000",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/open-science-challenge-2/",
"content": "Open Science\n\nScience is becoming more open in many areas: publishing, data sharing, lab notebooks, and software. There are many benefits to open science. For example, sharing research data […]"
},
{
"title": "Managing & Sharing Research Data Part 1",
"link": "http://squiremorley.wordpress.com/2012/01/19/managing-sharing-research-data-part/",
"epoch_time": "1326988667",
"author": "markuos",
"guid": "http://squiremorley.wordpress.com/2012/01/19/managing-sharing-research-data-part/",
"content": "I attended a presentation this morning given by Martin Donnelly, Digital Curation Centre (DCC), University of Edinburgh covering 'Managing & Sharing Research Data: Good practice in an ideal world […]"
},
{
"title": "citation11k: intro #draftInProgress",
"link": "http://researchremix.wordpress.com/2012/07/02/citation11k-intro/",
"epoch_time": "1341267485",
"author": "Heather Piwowar",
"guid": "http://researchremix.wordpress.com/2012/07/02/citation11k-intro/",
"content": "Writing a blog post is waaaaay easier than writing a paper. I know this because I've been trying to write a paper all day. Well, for months actually, […]"
},
{
"title": "Will this post be cited more often? Non-content factors that influence citation rates.",
"link": "http://undergraduatesciencelibrarian.org/2011/12/20/will-this-post-be-cited-more-often-non-content-factors-that-influence-citation-rates/",
"epoch_time": "1324398590",
"author": "Bonnie J. M. Swoger",
"guid": "http://undergraduatesciencelibrarian.org/2011/12/20/will-this-post-be-cited-more-often-non-content-factors-that-influence-citation-rates/",
"content": "For many researchers, the citation is a make-or-break concept. Most ranking algorithms use citations to determine a journal's influence or impact. Publication in "high impact" journals is often […]"
},
{
"title": "Scholarly metadata in R",
"link": "http://www.r-bloggers.com/scholarly-metadata-in-r/",
"epoch_time": "1363417200",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/scholarly-metadata-in-r/",
"content": "Scholarly metadata - the meta-information surrounding articles - can be super useful. Although metadata does not contain the full content of articles, it contains a lot of […]"
},
{
"title": "Scholarly metadata in R",
"link": "http://www.r-bloggers.com/scholarly-metadata-in-r-2/",
"epoch_time": "1363417200",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/scholarly-metadata-in-r-2/",
"content": "Scholarly metadata - the meta-information surrounding articles - can be super useful. Although metadata does not contain the full content of articles, it contains a lot of […]"
},
{
"title": "Scholarly metadata in R",
"link": "http://www.r-bloggers.com/scholarly-metadata-in-r-3/",
"epoch_time": "1363417200",
"author": "Tal Galili",
"guid": "http://www.r-bloggers.com/scholarly-metadata-in-r-3/",
"content": "Scholarly metadata - the meta-information surrounding articles - can be super useful. Although metadata does not contain the full content of articles, it contains a lot of […]"
}
]
Source Code
The source code is available here.


Atomic Tests
- Test Units: Each input that has specific data entry requirements.
- Unit Score: For each test unit, complete each of the following tests and sum the test credits to get the score.
Test that instructions are persistent
Test Procedure
- Check that instructions for data entry requirements are available on the page or view.
- Check that the instructions remain visible and available while entering data.
Expected Results
All checks are true.
Test that instructions are near inputs
Test Procedure
- Check that instructions for data entry requirements are available on the page or view.
- Check that the instructions are near the input.
Expected Results
All checks are true.
Test that instructions are programmatically defined and associated
Test Procedure
- Check that instructions for data entry requirements are available on the page or view.
- Check that instructions are programmatically defined and associated with the input.
Expected Results
All checks are true.
Scoring
- Still to be developed. We will include this in a future working draft.
Holistic Tests
- Still to be developed. We will include this in a future working draft.


Reports Room SQL queries that use unnamed query parameters (e.g. WHERE id = ?). This is not supported by the Room query
analyzer which requires named query parameters (e.g. WHERE id = :id) that correspond to arguments of the method annotated with
@Query.


HOME
VIEW
DONATE
Donate
Project Name
Donar Name
Email
Phone Number
Address
PrivateKey
Amount
Proceed to payment


Real-time data on deforestation activity in tropical rainforests
Rainforest Connection is the first platform with the potential to generate real-time data on deforestation activity in tropical rainforests. In doing so, it aims to combat illegal tree poaching by leveraging modern technological and social paradigms to reduce reliance on human resources and magnify the impact of environmentalists on-the-ground.
Hardware devices are installed sporadically in trees in threatened reserves. Each device continuously monitors audible frequencies, and abnormal signals (i.e. chainsaw frequencies) are transmitted to an internet-based central database. Alerts are generated in real-time and sent to responsible agents in the forest, enabling real-time intervention. Data generated through this platform are also made freely available through an open web service (API), allowing a global community of software developers to build real-time apps.
In doing so, rainforest surveillance becomes a low-cost, crowdsourced, scalable endeavor, and we are able to tap the unlimited resources of a growing worldwide population of tech-savvy eco-enthusiasts.
© 2013 Rainforest Connection. All Rights Reserved. +1<PHONE_NUMBER> contact@rfcx.org


go up
Home
paste json here
-
clear
{"null":null,"boolean":[true,false],"number":[0,1.5,2e4,-1234567890],"strings":{"firstname":"Jane","lastname":"Gray","hobbies":["X-Ray","Flying",{"teams":["X-Men","Mutants"]}],"address":"unknown"}}
Results word wrap on/off
Minify and clean source
select results
by
Johny Kvsky


0:05
SARAH HARRIS: The first thing
that strikes you when you come
0:08
to India is a sense of
extreme contrasts.
0:12
While some people are still
shitting off the side of
0:14
railway lines and eating from
banana leaves, other people
0:17
are drinking Frappuccinos and
wearing Gucci sunglasses.
0:21
Along with this feeling of
progress and moving forward,
0:24
there's still this undercurrent
of tradition and
0:28
religion and superstition and an
even more deeply ingrained
0:34
I didn't realize quite how sharp
these contrasts between
0:37
new and old India were until
I came here last year to
0:41
research an article about
sex trafficking.
0:44
And on my very first day here,
I met a group of temple
0:47
prostitutes who told me about
this ancient Hindu system
0:52
where prepubescent girls are
dedicated to a goddess, and
0:57
for the rest of their lives,
they will become sex slaves of
1:02
The name of that system
is devadasi.
1:15
This train's a little bit like
The Darjeeling Limited, except
1:19
we have cockroaches sleeping
under our beds.
1:25
And there's no one serving
sweet lime.
1:31
So in the beginning, being a
devadasi had nothing to do
1:36
In medieval India, they were
glamorous temple dancers and
1:39
held high social status.
1:41
They performed sacred religious
rituals and danced
1:44
for loyalty in the name of a
goddess called Yellamma.
1:48
Over the centuries, the link
between the devadasis and
1:50
their temples gradually
diminished, along with their
1:55
They became the paid mistresses
of priests, then
1:58
kings, and later,
rich landowners.
2:01
In the 19th century, Western
missionaries tried to abolish
2:05
the tradition, calling it
grotesque and immoral, driving
2:08
the devadasis underground.
2:11
Today, devadasis are no
different to common street
2:15
hookers, servicing drunk truck
drivers and bored businessmen.
2:19
Even though the practice has
been illegal for over 20
2:22
years, up to 3,000 girls are
still being secretly dedicated
2:27
We traveled to the border town
of Sangli, which straddles the
2:31
two southern Indian states of
Karnataka and Maharastra.
2:35
Its red light district is home
to hundreds of devadasi sex
2:39
workers, and that afternoon,
we were invited there by
2:42
Anitha, one of its most
successful brothel owners.
2:46
She's a member of an NGO called
SANGRAM, which fights
2:49
to empower locals sex workers.
2:52
Communication was pretty
painful, as our interpreter
2:55
Somashekar was having some
trouble with his English.
2:58
Everybody in the houses
next door--
3:01
is also sex workers
like Anitha?
3:09
SARAH HARRIS: So all
the neighborhood.
3:12
And they're all friends
who live around here?
3:14
Everybody is friends?
3:20
SARAH HARRIS: So when the
customer comes inside, the
3:39
SARAH HARRIS: She's
not a customer?
3:40
She is also a sex worker?
3:42
SOMASHEKAR: A sex worker.
3:43
SARAH HARRIS: And she
uses this room?
3:47
SOMASHEKAR: [SPEAKING MARATHI]
3:51
SOMASHEKAR: That's another one
of Anitha's friends who's
4:02
SARAH HARRIS: This is
what she's saying?
4:12
SARAH HARRIS: Tell me again.
4:12
So are you talking as you?
4:14
Are you telling me--
4:16
SARAH HARRIS: So you
are a sex worker.
4:18
SOMASHEKAR: I am a sex worker.
4:18
SARAH HARRIS: You are
a sex worker.
4:19
And you came to Anitha's
room, and--
4:26
SARAH HARRIS: You work in
this room, and Anitha
4:29
SOMASHEKAR: This room.
4:31
SARAH HARRIS: So you
all work together.
5:19
SARAH HARRIS: The whole place
is completely difference to
5:21
what I thought it would be.
5:23
I kind of imagined these
really seedy, anonymous
5:27
hotel-looking brothels.
5:30
And actually, there's kids
running around everywhere.
5:33
There's women doing their
laundry, making lunch.
5:37
And it kind of feels
like quite a
5:39
tight-knit little community.
5:43
The ladies of Sangli wouldn't
let me leave without showing
5:46
me the temple around
the corner.
5:48
It seemed like wherever there
were brothels, the goddess
5:51
Yellamma was never far away.
5:55
For Anitha and her friends,
being a devadasi was nothing
5:59
Sex work was their choice.
6:01
They had condoms, power in
numbers, and SANGRAM looking
6:05
But these were just
the lucky few.
6:09
For the vast majority
of devadasis,
6:11
prostitution isn't a choice.
6:13
It's forced upon them, and most
often by their parents.
6:28
Like most Hindu legends, the
story of the goddess Yellamma
6:32
is long, convoluted,
and surreal.
6:39
However many times we
heard it, it still
6:41
didn't make much sense.
6:43
But it seems to go something
like this.
6:46
The whole ordeal begins when her
son is ordered to chop her
6:49
head off by her husband after
he catches her spying on two
6:52
people getting frisky
by a lake.
6:56
After a complex process of
death, reincarnation, and a
6:59
load of fat Hindu gods with blue
skin and gold bikinis,
7:03
the goddess Yellamma was born.
7:10
She fled to the villages of
Karnataka and became a symbol
7:12
of worship for the lowest
Hindu castes.
7:34
So after a really sweaty 10-hour
train journey, we've
7:37
finally arrived in this
town called Mudhol
7:39
up in Northern Karnataka.
7:41
And it's in the villages around
here that we've been
7:43
told has the highest
concentration of devadasi
7:48
An estimated 23,000 women in
this part of India have been
7:53
dedicated to the goddess.
7:55
And roughly half of those will
have resorted to sex work in
7:59
order to feed their families.
8:07
SARAH HARRIS: We traveled to
the outskirts of this dusty
8:09
transit town to meet two
teenage devadasi girls.
8:48
SARAH HARRIS: Madigas are
considered filthy and
8:50
polluting and are only permitted
to work in the
8:53
lowliest positions, as street
cleaners, sewage collectors,
8:57
and of course, prostitutes.
9:00
When we took the girls out
shopping, they seemed
9:03
terrified of the higher castes
recognizing them as devadasis,
9:22
SARAH HARRIS: It was surreal to
see the reaction they got.
9:25
The shopkeepers wouldn't even
look them in the eye.
10:26
SARAH HARRIS: So now it seems
this religious ritual is just
10:29
a justification for
poor families to
10:31
pimp out their daughters.
11:04
SARAH HARRIS: It was strange
sitting with Belavva's family
11:07
on the floor of their one room
hut, knowing it's also the
11:10
place where she has sex with
customers while her brothers
11:13
and sisters wait outside.
11:17
BALAVVA: [SPEAKING KANNADA]
12:03
SARAH HARRIS: Karnataka is one
of India's largest producers
12:08
Hundreds of trucks pass
through towns
12:10
like this every day.
12:13
The roadside can be
a scary place.
12:15
Horny drivers and bored
agricultural workers gather
12:18
here, looking for ways
to spend their wages.
12:22
They are one of the main
transmitters of HIV throughout
12:25
India, spreading the virus
through the country's
12:28
extensive road network, putting
girls like Mala and
12:32
Belavva at risk of this
deadly disease.
12:59
SARAH HARRIS: Back in Sangli,
we were invited to meet
13:01
another devadasi called Pandu.
13:03
We were told she was different,
but we weren't
13:05
prepared for just
how different.
13:08
[MALE SPEAKING MARATHI]
13:29
SARAH HARRIS: Every morning, he
spent two hours polishing
13:31
brass Yellamma statues and
blessing his beloved shrine.
14:05
SARAH HARRIS: Can you ask him
to show me how to make chai?
14:16
Wow, that's a lot of sugar.
14:21
SARAH HARRIS: Still?
14:21
Going, going, going,
going, going.
14:34
SARAH HARRIS: Can we watch
him dance today?
14:36
We have to persuade him,
sweet talk him.
14:47
You put a sari over his head.
14:49
[PANDU SPEAKING MARATHI]
14:55
SARAH HARRIS: He's got money
between his teeth.
14:59
Your best friend, Sudir.
15:03
Oh, wow, that's a nice photo.
16:58
SARAH HARRIS: Later that day, at
our hotel, Pandu showed us
17:01
his favorite Bollywood
videos and the famous
17:04
Sangli condom trick.
17:10
SARAH HARRIS: You're about to
witness a demonstration of the
17:13
classic Sangli condom trick that
Pandu has just taught me
17:17
when his male customers don't
want to use a condom.
17:47
SARAH HARRIS: I think I lost.
17:50
Pandu may want a better life for
his daughter, but for many
17:53
other devadasis, there's a lot
of money to be made in
17:56
recruiting the next
generation.
18:01
Now, we're on our way to another
village, about five
18:04
kilometers outside of Mudhol.
18:06
And most of women who live
there are from the madiga
18:09
caste, and so most of them are
18:10
vulnerable to becoming devadasis.
18:13
One of the interesting things
about this village is that
18:16
we're going to be able to go
to the house of a devadasi
18:19
woman who's made a real career
out of prostitution.
18:22
And she's built this enormous
house in the middle of the
18:24
village as a kind of symbol
of the her success.
18:27
So she can become a role model
to the other girls living in
18:31
the village that becoming
a devadasi is
18:33
a good way of life.
18:37
The legendary owner, Champa,
doesn't even live here.
18:40
She's too busy turning
tricks in Bombay.
18:43
Inside, shiny display cabinets
of unused crockery line the
18:46
walls as testaments
to her success.
18:49
There were groups of village
children roaming around the
18:51
house to gawp at her flickering
color TV sets and
18:55
shelves of broken electrical
equipment.
18:58
The message is clear--
19:00
prostitution is a lucrative
business.
19:04
So this is the necklace, the
muthu, that the devadasi women
19:10
wear when they get dedicated.
19:12
And hers is just hanging on
the wall of her mud hut.
19:15
She's an old lady called
Shavvavva, and she's one of
19:18
the oldest devadasi women
in the village.
19:21
And I've just been told that
she brought the very first
19:25
radio to this village.
19:27
No one had ever seen a radio
before she brought it here.
19:32
Walking through the village, we
notice Yellamma's presence
19:35
The locals told us that all
devadasis in the area were
19:39
preparing themselves for the
full moon festival, which is
19:42
apparently the most
important event in
19:44
the Yellamma calendar.
20:12
After hearing so much about the
famous full moon festival
20:15
in Saundatti, we drove four
hours out of town to catch the
20:19
first day of this month-long
celebration of Yellamma.
20:23
Just up there in the center of
that big arch is the face of
20:27
the goddess Yellamma.
20:31
That's the entrance to her
temple here in Saundatti.
20:38
Over the course of the 28 days,
more than half a million
20:41
people will pass through
the temple doors.
20:44
A heaving shantytown springs
up around the
20:47
famous Yellamma shrine.
20:49
The place is filled with garish
Hindu icons, Bollywood
20:52
music, sticky sweets, and the
symbolic red and yellow colors
20:56
of the goddess Yellamma.
21:00
We're not allowed-- we're not
gonna take the camera inside.
21:07
SARAH HARRIS: This is the
Yellamma temple, which is like
21:09
the main attraction
of Saundatti.
21:12
It's here that for hundreds and
hundreds of years, all the
21:15
devadasi girls have come for
their dedication ceremonies,
21:18
which are now illegal.
21:20
And we're not allowed in, so
we just have to shoot from
21:22
outside, but you can see
hundreds of people walking
21:26
around, praying to
the goddess.
21:31
Everything around the temple
is really, really colorful,
21:33
and you've got all these red
and yellow dyes, which the
21:36
women put on their foreheads.
21:37
And this is to kind of
21:39
represent the goddess Yellamma.
21:40
And the green bangles are in
rows all along the side of the
21:43
road here, and they're the
bangles that they put on the
21:47
girls during their devadasi
dedication ceremonies.
21:50
And tonight is the moon
celebration, and they'll smash
21:54
their bracelets as a symbol
of widowhood.
22:00
This is also one of the places
where the women traffickers
22:04
come and pick up potential
prostitutes.
22:08
The brothel madams will travel
from big cities like Bombay
22:12
and Pune and come to Saundatti
to these festivals to pick up
22:16
young girls to traffic.
22:22
Amidst all the religious fervor,
there was a distinct
22:25
feeling of secrets going
on behind closed doors.
22:29
Families are offered a generous
fee in return for
22:32
their young daughters,
often under the
22:34
pretense of a better future.
22:36
But it's here that the next
generation of young devadasi
22:39
prostitution are found.
22:42
What we really wanted to do was
watch a real dedication
22:45
ceremony, but that didn't look
like it was going to happen.
22:48
And as a bunch of pasty
Westerners with cameras, we
22:51
weren't exactly inconspicuous.
22:54
Luckily, we met an ex-devadasi
and social
22:57
activist called Sitavva.
22:58
She agreed to stage a mock
dedication ceremony to give us
23:02
an idea of what really goes
on behind the scenes.
23:07
SITAVVA: [SPEAKING KANNADA]
24:33
SARAH HARRIS: Leaving Saundatti,
we felt disturbed
24:35
by everything we'd seen.
24:37
The bright colors and energy
of the festival were
24:40
overshadowed by the seedy
reality of a religious
24:43
ceremony that condones
child prostitution.
24:48
Our last stop before we headed
home was in the small village
24:51
of Sarol, where we'd arranged
to meet three generations of
24:54
devadasi women, all from
the same family.
25:00
When we arrived, we were told
that the daughter had recently
25:09
[SPEAKING FOREIGN LANGUAGE]
26:46
SARAH HARRIS: India is a land
of extremes, polarized by
26:49
extravagant new wealth
and ancient poverty.
26:53
Everywhere you look, there's a
battle being waged between the
26:56
traditional forces of religion,
castes, and
26:58
superstition and the inevitable
force of Western
27:03
Nowhere are these clashes more
evident than in the plight of
27:06
the devadasis, where religious
devotion has been exploited
27:10
for commercial gain.
27:12
The devadasi tradition is
destroying families and
27:15
communities, generation
after generation.
27:19
And with the advent of AIDS and
HIV, the practice now has
27:22
a deadly price tag.
27:24
And today, any remnants of the
devadasis' cultural origins
27:28
have all but disappeared.
27:31
All that's left is a system
that turns children into
27:33
prostitutes and their
parents into pimps.


Welcome to my website. I accidentally made it more about whales, than charity.
Fires in California
Hurricane Dorian
Australian wildfires
Coronovirus pandemic
Thousands of local organizations in more than 170 countries are the backbone of our network.
“Hundreds of wildfires are burning across California,
destroying homes, forcing mass evacuations, and polluting the air.
This fund will support firefighters and get emergency supplies like food,
water, and medicine to people in need. The fund will remain open to provide
long-term assistance. As the location and severity of the fires fluctuates,
so will our response to ensure aid gets where it is most needed.
All donations to this fund will exclusively support communities
impacted by wildfires.”
“High winds and drought conditions are causing wildfires
to spread rapidly through Australia, prompting mass evacuations, destroying
homes and killing millions of animals. This fund will support immediate rescue
and relief efforts for people and animals impacted by the fires and
will eventually transition to funding long-term assistance to help
residents recover and rebuild. All donations to this fund will
exclusively support wildfire recovery.”
“The COVID-19 pandemic marks an unprecedented time
in modern history that will require the best of humanity to overcome.
Your donation to this fund will help stop COVID-19's spread and
protect us all.Your donation to this fund will help stop the virus's spread
and give communities on the front lines of the crisis the resources they
need to act quickly and protect the most vulnerable.”
“This disaster relief fund has supported people impacted by
Hurricane Dorian's storm system in the form of emergency supplies like food,
water, and medicine. Beginning in 2020, and we will be investing in the
rebuilding of homes, communities and livelihoods on Grand Bahama, Abaco,
and in ongoing support of evacuees in Nassau. All donations to this fund
will exclusively support relief and recovery efforts in areas impacted
by this storm.”


| public void CHR_Amzaon() |
| Character constructor |
| public void preRoll() |
DescriptionPerforms preroll functions for the Amazon character.ParametersReturnsNothing |
| public int charRoll() |
DescriptionRolls a certain number of dice for the Amazon character.ParametersReturnsint - Dice roll |
Member Data |
| private int _dice - The number of dice the character will roll |


vignettes/articles/datapasta-reprex.Rmd
datapasta-reprex.Rmd
While using a built-in dataset for a reprex is ideal, sometimes you need to troubleshoot code with a bit of outside data. Meet datapasta, a package by Miles McBain for “reducing resistance associated with copying and pasting data to and from R.” Like reprex, datapasta has addin functionality, so you can select commands from the RStudio Addins and/or associate keyboard shortcuts with them for easy use.
tribble_paste()
It’s easy to copy and paste nicely formatted data from a spreadsheet with datapasta’s tribble_paste()
functionality. I’ve found the simplest method to be:
While the output of tribble_paste()
doesn’t have the same level of detail it would with dput()
, it works well enough for most scenarios, with the added benefit of being easy to read on the screen.
dpasta()
Now let’s say you have a data frame in R that you want to use in a reprex. You can use datapasta’s dpasta()
function to render your object into the same format as the result of tribble_paste()
, above.
There’s more to datapasta than discussed here, so be sure to check out its documentation. Don’t forget, when it comes to reprex, less is always more, so wield the power of datapasta wisely.


Reysol clinches return to top flight
Kashiwa Reysol proved for the third time they are a hard team to keep down after clinching the J. League’s second-division championship and earning promotion to J1 on Saturday.
Reysol, relegated to the J2 this year, booked their first division return in one season, just as they had in 2006 and 2010. Reysol sealed the deal with a 3-0 win at Machida Zelvia on a brace by Brazilian striker Cristiano and a second-minute opener by Yusuke Segawa.
The last time Reysol won J2, the Chiba Prefecture side followed it by winning the J. League championship in 2011 in a season thrown into turmoil by the March 11 earthquake and tsunami.
Kashiwa went on to win the 2012 Emperor’s Cup and 2013 J. League Yamazaki Nabisco Cup in addition to reaching the semifinals of the 2013 Asian Champions League.
Yokohama FC moved closer toward earning a stint in J1 with a 1-0 victory at Fagiano Okayama. They were formed by Yokohama Flugels fans after their team was absorbed by rival side Yokohama Marinos at the end of the 1998 season.
Yokohama FC are second, two points ahead of third-place Omiya Ardija, and can clinch promotion with a win next week at home against Ehime.
The top two J2 teams earn automatic promotion to the top flight, while those finishing third to sixth will compete to face the J1’s 16th-place team in a promotion-relegation playoff.
After Ardija, Montedio Yamagata (70 points), Ventforet Kofu (68) and Kyoto Sanga (68) occupy the remaining playoff-eligible spots.
GET THE BEST OF THE JAPAN TIMES
IN FIVE EASY PIECES WITH TAKE 5
JOIN THE CONVERSATION