createWorkerInstance

The function <code>createWorkerInstance</code> uses a definition identified by
defnId to create the appropriate object instance. The instantiated object is assigned
the instanceId and saved under the dataFileName if the latter is specified.
This instantiated object may change state between iterations when a computation executes

Implementing algorithms and fitting models when sites (possibly remote) share
computation summaries rather than actual data over HTTP with a master R process (using
'opencpu', for example). A stratified Cox model and a singular value decomposition are
provided. The former makes direct use of code from the R 'survival' package. (That is,
the underlying Cox model code is derived from that in the R 'survival' package.)
Sites may provide data via several means: CSV files, Redcap API, etc. An extensible
design allows for new methods to be added in the future and includes facilities
for local prototyping and testing. Web applications are provided (via 'shiny') for
the implemented methods to help in designing and deploying the computations.

Balasubramanian Narasimhan

distcomp

Computations over Distributed Data without Aggregation

Marina Bendersky

Sam Gross

Thomas Lumley

createWorkerInstance function

<dl><dt>defnId</dt>
<dd>the identifier of an already defined computation</dd>
<dt>instanceId</dt>
<dd>an indentifier to use for the created instance</dd>
<dt>pubkey_bits</dt>
<dd>number of bits for public key</dd>
<dt>pubkey_n</dt>
<dd>the <code>n</code> for public key</dd>
<dt>den_bits</dt>
<dd>the number of bits for the denominator</dd>
<dt>dataFileName</dt>
<dd>a file name to use for saving the data. Typically <code>NULL</code>, this
is only needed when one is using a single opencpu server to behave like multiple
sites in which case the data file name serves to distinguish the site-specific data files.
When it is <code>NULL</code>, the data file name is taken from the configuration settings</dd></dl>

Arguments

Given the definition identifier of an object, instantiate and store object in workspace — createWorkerInstance

<dl>

<dt>defnId</dt>
<dd>the identifier of an already defined computation</dd>


<dt>instanceId</dt>
<dd>an indentifier to use for the created instance</dd>


<dt>pubkey_bits</dt>
<dd>number of bits for public key</dd>


<dt>pubkey_n</dt>
<dd>the <code>n</code> for public key</dd>


<dt>den_bits</dt>
<dd>the number of bits for the denominator</dd>


<dt>dataFileName</dt>
<dd>a file name to use for saving the data. Typically <code>NULL</code>, this
is only needed when one is using a single opencpu server to behave like multiple
sites in which case the data file name serves to distinguish the site-specific data files.
When it is <code>NULL</code>, the data file name is taken from the configuration settings</dd>

</dl>

createWorkerInstance: Given the definition identifier of an object, instantiate and store object in workspace

Description

Usage

Value

Arguments

See Also