CHILD Users Guide
Version 2.0
Gregory E. Tucker1
Department of Civil and Environmental Engineering
Massachusetts Institute of Technology
Cambridge, MA 02139
Part IV-A of final technical report submitted to U.S. Army Corps of Engineers Construction Engineering Research Laboratory (USACERL)
by Gregory E. Tucker, Nicole M. Gasparini, Rafael L. Bras, and Stephen T. Lancaster
in fulfillment of contract number DACA88-95-C-0017
April, 1999
CHILD Users Guide
Version 2.0
The CHILD model is a C++ program that simulates erosion, sedimentation, and landscape evolution, over either geologic or "human" time scales. CHILD was designed and written in 1996 and 1997 by Greg Tucker, Stephen Lancaster, Nicole Gasparini, and Rafael Bras, in the Department of Civil and Environmental Engineering at the Massachusetts Institute of Technology. The present version, released in April 1999, represents a significant upgrade to the original (1997) version. This document describes how to install, compile, set up, and run CHILD Version 2.0. This guide assumes that you are familiar with what CHILD is and what it can do; for basic information about CHILD and its capabilities, consult the document "Overview of the CHILD Model" (available at http://platte.mit.edu/~child). Other articles and documents related to CHILD are listed under References, below. CHILD is copyrighted 1997-1999 by Gregory E. Tucker, Nicole M. Gasparini, Stephen Lancaster, and Rafael Bras, and may not be used for commercial purposes without written consent from the authors.
Installing and Compiling CHILD
CHILD was developed in C++ on a UNIX platform. The code is designed to be as platform-independent as possible (e.g., no direct window system interface is included); however, the instructions here pertain specificially to UNIX installation. As of this writing, the CHILD code is provided in a single tar-format file called child_src_2.0.tar. To unpack it, place this file in the desired master directory and type
% tar xvf child_src_2.0.tar
(where % represents the UNIX command-line prompt).
This will create a series of subdirectories, each containing a source file and its accompanying header file. The easiest way to compile the program is to use the UNIX make utitility. At this writing, a make file is provided only for Digital UNIX systems running the cxx compiler. The make file can be modified for other platforms and other compilers, however. To compile the code with cxx under Digital UNIX, use
% make -f makefile_cxx
The make utility will create an executable file called child.
Creating an Input File and Starting a Run
To run a CHILD simulation, you will need to provide an input file (hereafter called the "main input file") that contains various required and optional parameters. The main input file can have any name; by convention, main input files have the extension .in. Unless a simulation mesh is to be created from scratch, several additional files containing information about the initial topography and/or mesh configuration will be needed. These additional files are described below in reference to the various mesh input and/or generation options.
The command-line syntax for running the model is
% child myinputfile.in [-s]
where myinputfile.in represents the name of the main input file, the format of which is described below, and -s is an optional argument that, if given, suppreses printing of the current simulation time at each iteration.
The main input file contains a list of process coefficients, option switches, auxiliary file names, and other parameters. Some of these parameters are always required. Others are optional, and only need to be included when a particular option is selected. Any optional parameters included in the file but not needed in the run are simply ignored. The format for each parameter consists of a line of descriptive text followed by the value of the parameter itself on a second line. Here is an example showing the format of the main input file:
OPTREADINPUT: 0=new mesh, 1=existing mesh, 2=points, 3=DEM
1
INPUTDATAFILE:
mytin
INPUTTIME: which time to read from inputdatafile
0
RUNTIME: Duration of run (years)
100
OPINTRVL: Output interval (years)
5
OPTVAR: Option for random rainfall variation
1
PMEAN: Mean rainfall intensity (m/yr)
12
STDUR: Mean storm duration (yr)
0.07763
#0.003
ISTDUR: Mean time interval between storms (yr)
0.15753
#0.997
OPTDETACHLIM: 1 = use purely detachment-limited erosion
0
...etc.
At the start of each header line is an "item code" in capital letters. This correct code for each parameter must be included in order for the model to find and read the parameter (Table lists required input parameters and their corresponding item codes). A hash mark (#) represents a comment line (here, the values 0.003 and 0.997 are commented out). Parameters can be in any order in the file. In the example above, the first parameter OPTREADINPUT is a required parameter that tells the model whether to create a new (synthetic) mesh, read in an existing mesh, create a mesh from an input set of (x,y,z) points, or create a mesh from a DEM. In this example, the option for reading in an existing mesh has been selected, and two additional optional parameters have been included to support this choice: INPUTDATAFILE, representing the base name for mesh input files, and INPUTTIME, representing the time-code for which input is read (this will normally be nonzero only when restarting a previous run). (Note that for the sake of brevity the example above does not include all required parameters). The sections below describe how to set up a CHILD run with different mesh input/generation options and with different process parameters and options.
Setting Up the Initial Mesh
CHILD provides several options for generating and/or reading in an initial mesh. You can have the model set up a mesh in any of the following ways
Generate a new "synthetic" rectangular mesh with a hexagonal, perturbed-hexagonal, or random arrangement of nodes
Read in an existing TIN (including a TIN output by another CHILD run)
Generate a mesh from a given set of (x,y,z) points
Generate a mesh from a DEM in Arc/Info ascii format
The following sections describe how to use these various options.
If desired, CHILD can create a starting mesh with a rectangular domain. Three examples of CHILD-generated starting meshes are shown in Figure 1. Points within the rectangular domain can be regularly spaced in a hexagonal lattice (Figure 1a), regularly spaced with random offsets in their (x,y) positions (Figure 1b), or randomly placed within the rectangular domain (Figure 1c). In the case of a random-offset mesh, the maximum offset amount is equal to + or - 25% of the nominal point spacing. In all of these cases, there are five possible boundary options (Figure 2): (1) a single outlet (open boundary point) in one corner; (2) an open boundary along one side (corresponding to y=0); (3) open boundaries along the y=0 and y=ymax sides; (4) open boundaries along all four sides; and (5) a single outlet point at a specified location. (Recall that an open boundary point is a boundary node at which water and sediment are allowed to exit). In each case except #3, the initial elevation is equal to a specified mean elevation plus or minus a random variable (uniformly distributed), with the minimum and maximum possible values equal to 50% and 150% of the mean elevation, respectively. In case #3 (open boundaries on two opposite sides), the elevation of the upper (y=ymax) boundary is specified (UPPER_BOUND_Z), and the elevations of the points are set so as to create a uniform gradient between the two boundaries, plus random vertical offsets.
To start a run with a new rectangular mesh, set OPTREADINPUT to 0. The parameter OPT_PT_PLACE controls the type of point placement (0, 1, and 2 for regular, offset, and random, respectively), and the parameter TYP_BOUND controls the open boundary configuration (0, 1, 2, 3, and 4 for corner, one side, two sides, four sides, and user-specified, respectively). Additional parameters required with these different options are discussed below.
Setting Up the Configuration of a Synthetic Mesh
The dimensions of the rectangular mesh are set using the parameters X_GRID_SIZE and Y_GRID_SIZE (in meters). Set the option for point placement, OPT_PT_PLACE, to 0, 1 or 2 for regular, perturbed, or random points, respectively. In the case of regular or perturbed-regular point placement, the mean point spacing (GRID_SPACING) must be specified. In the case of random point spacing, the total number of interior points, NUM_PTS, must be given. In any event, the mean elevation (MEAN_ELEV) and a seed for the random number generator (SEED) must always be provided when a new rectangular mesh is generated.
Boundary Configuration Options
Set the option TYP_BOUND to specify the boundary type. For a two-sided boundary, you must also specify the elevation of the upper boundary (which can be different from zero) using the parameter UPPER_BOUND_Z. For a user-specified outlet location, give the outlet coordinates in OUTLET_X_COORD and OUTLET_Y_COORD (note that an outlet cannot be placed in the interior of the mesh).
Reading in an Existing Mesh
You can start a CHILD run using an existing triangulation. The triangulation might represent either a mesh from a previous CHILD run or a TIN output from a GIS system (for example). The input mesh data format is the same as CHILD's output format (see " Output Files" on page 17), and consists of four ascii files that contain data on nodes, edges, triangles, and node elevations, respectively. The files must bear the same base name and have the extensions .nodes, .edges, .tri, and .z (as in foo.nodes, foo.edges, foo.tri, foo.z). Each file may contain triangulations for multiple time intervals (obviously in the case of GIS data this does not apply; only one "time slice" would be included in the file).
The format of the node file consists of the time represented by the triangulation on the first line, the number of nodes (including boundaries) on the second, and on the subsequent lines the following information for each node: x-coordinate (meters), y-coordinate (meters), ID of one of its connected edges, and a boundary code. (If inputting a mesh that isn't the output of a previous run, use 0 for the time code). For example:
0
289
0.50627 1.134 1424 0
1.02798 1.80433 2 0
0.96638 2.79677 4 0
...etc
The nodes are assumed to be in order by ID number, starting with 0 and ending in N-1 (where N is the number of nodes). The boundary codes are 0 for an interior point, 1 for a closed boundary, and 2 for an open boundary. Note that points flagged as interior points cannot be on the perimeter of the mesh; an error will occur if any such points exist.
The format of the other three files is similar in that each time-slice begins with the time value and the number of elements (either edges, nodes, or triangles). In the edge file, each row must contain the ID of the origin node, the ID of the destination node, and the ID of the edge that lies counter-clockwise (relative to the origin) (see Tucker et al., 1999, for discussion of these data structures). Complementary edge pairs MUST BE TOGETHER on the list. An example of an edge file is shown below:
0
1600
225 0 1417
0 225 34
1 0 30
0 1 1424
...etc.
Note that directed edges that share the same endpoints (complementary edges) are always grouped together. As with nodes, the edges should be listed in order by ID number.
Each row of the triangle file contains the ID numbers of the three vertex nodes in counter- clockwise order, the ID number of the three triangles opposite these vertex nodes (or -1 if no triangle lies opposite a given face), and the ID numbers of the three clockwise-oriented directed edges. These edges are listed in the same order as their origin vertices, i.e., edges 0->2, 1->0, and 2->1. Triangles are also listed in order by ID.
The node elevations file has the same header format as the others (time followed by number of nodes). The header for each time step is followed by a series of lines that contain the elevation in meters of each node, in order by ID number.
Note: CHILD includes a consistency checking routine to make sure the mesh format is valid, but this is not guaranteed to be foolproof. In particular, the model also does not test whether the input triangulation is Delaunay.
Creating a Mesh from a Set of Points
CHILD can construct a mesh from an input set of (x,y,z) points. Such points might be obtained from a field survey, a GIS point coverage, a sampled DEM, etc. To create a mesh from a set of points, set the OPTREADINPUT option to 2. You will then need to specify the name of an ascii file (parameter POINTFILENAME) containing the point data. The format for the point data file consists of a header line that gives the number of points, followed by a series of rows that contain the x and y coordinates, the elevation, and a boundary code for each point, as in the following example:
7
1 3 30 1
3 3 30 1
0 1.5 10 1
2 1.5 10 0
4 1.5 10 1
1 0 0 2
3 0 0 2
The point set in this example is used to construct the seven-node mesh shown in Figure . The possible boundary codes are 1 (closed boundary), 2 (open boundary), and 0 (mesh interior). Nodes flagged with boundary code zero must always be within the mesh interior; errors will result if the model encounters an active (0 boundary code) node on the mesh perimeter. In the above example, only one node lies in the mesh interior.
Generating a Mesh from an Arc/Info Grid DEM
CHILD can also generate a mesh by interpolating a DEM. The DEM must be in Arc/Info's ascii grid format. In the present version, this capability is somewhat limited. The DEM must describe a single drainage basin, since only one outlet point is created. The resolution of the mesh will be the same as that of the original DEM, and will be uniform in space. The mesh can be either hexagonal, or "random." In the latter case, the mesh starts with one mesh point per DEM point; the x and y coordinates of each point are then offset by a random amount. When a mesh point falls between DEM points, the four-point interpolation procedure of Tetzlaff and Harbaugh (1988) is used to derive the point's elevation. To create a mesh with random offsets from a DEM, set OPTREADINPUT to 3; to create a hexagonal mesh from the DEM, set OPTREADINPUT to 4. Use the parameter ARCGRIDFILENAME to specify the name of the Arc/Info grid ascii file.
Setting Up Parameters and Options
This section describes how to set up the parameters in a CHILD run and how to activate and deactivate different options for landscape processes, hydrologic behavior, climatic variation, and so on.
Run Name, Duration, and Output
Use the OUTFILENAME parameter to specify a base name for the output files. Each output file will have this name followed by an extension that describes the contents of the file (see " Output Files" on page 17). The RUNTIME parameter sets the total duration of the run in years, and the parameter OPINTRVL specifies how often output should be written (also in years).
Climate Parameters
The parameters PMEAN, STDUR, and ISTDUR set the mean storm intensity, duration, and interstorm interval, respectively (in units of meters and years). To generate a sequence of random storms based on these parameters, set OPTVAR to 1; otherwise, each storm will have the mean values. The random number generator is initialized by the SEED parameter. Note that you can configure a run to operate as a continuous (constant-climate) model by simply turning off climate variation and, if desired, setting the interstorm interval to zero, in which case STDUR effectively becomes the time-step. Note also that for long simulations, it is usually convenient to accelerate performance by magnifying the mean storm and interstorm intervals. This preserves the distribution of event sizes while enhancing performance. However, use this approach with caution, since some parameters (such as soil storage capacity) depend on storm duration and would therefore need to be adjusted accordingly.
To invoke sinusoidal fluctuations in mean storm intensity, duration, and/or spacing, set OPTSINVAR to 1. You will then need to specify the period of variation in years (PERIOD) along with the maximum values of mean intensity (MAXPMEAN), duration (MAXSTDURNM), and spacing (MAXISTDURMN).
Runoff Generation and Flow Routing
The FLOWGEN parameter controls the model's runoff generation options. Possible values are:
Uniform Hortonian (infiltration-excess) runoff
Saturation-excess runoff using the O'Loughlin (1986) method
Saturation-excess runoff using the modified Beven and Kirkby (1979) method
Uniform soil-storage capacity ("bucket model")
The Hortonian runoff option is the simplest, and requires two additional parameters: the soil infiltration capacity (INFILTRATION) in meters per year, and an option for sinusoidal time-variation in infiltration capacity (OPTSINVARINFILT). The uniform storage capacity option also requires the INFILTRATION and OPTSINVARINFILT parameters, along with the parameter SOILSTORE, which represents the soil water-storage capacity in meters. The O'Loughlin saturation- excess model requires only a single parameter, the soil transmissivity (TRANSMISSIVITY) in square meters per year. The modified Beven-Kirkby saturation-excess model requires three parameters: the infiltration capacity (INFILTRATION), the infiltration variation option (OPTSINVARINFILT), and a unit soil deficit parameter (TRANSMISSIVITY). (Note that the Beven-Kirkby option uses the TRANSMISSIVITY parameter not as a transmissivity sensu strictu, but rather as a moisture deficit scaling parameter with units of meters.)
Sinusoidal Variation in Infiltration Capacity
Set the OPSINVARINFILT parameter to 1 to have infiltration capacity vary sinusoidally through time (this provides a way to model the hydrologic effect of changes in surface properties such as vegetation cover). Additional parameters required with this option include the period of variation (PERIOD_INFILT) and the maximum infiltration capacity (MAXICMEAN).
Lakes and Sinks
The CHILD model includes an algorithm to identify and route drainage through depressions in the terrain. To invoke this option set LAKEFILL to 1. Otherwise, water will be assumed to evaporate within sink points. It is usually a good idea to run the model with this option activated.
An "inlet" is a point source of water and sediment that represents a through-flowing stream. The inlet option makes it possible to configure simulations that represent a segment of a valley or floodplain, or (as a larger-scale example) a large antecedent river crossing mountainous terrain. To activate an inlet, set OPTINLET to 1. The inlet location must then be specified with INLET_X and INLET_Y (with the coordinates given in meters). INDRAREA sets the drainage area at the inlet point (in m2). The volumetric sediment load of each grain size is specified in the parameters INSEDLOAD1, INSEDLOAD2, etc. (one for each grain size fraction).
Hydraulic Geometry
CHILD calculates hydraulic geometry (width, depth, bed roughness, and bank roughness) using the empirical methods of Leopold and Maddock (1953). Parameters relating to hydraulic geometry must always be provided in the input file; their use in the model depends on which process options are used. For simulations that do not use the detachment-limited option, channel depth is computed and used as the effective vertical depth over which sediment is "seen" by flowing water (this will have an influence on erosion and transport only when the material is vertically heterogeneous). The stream meander module makes use of all of the hydraulic geometry parameters, and the floodplain deposition module uses bankfull depth and flood depth to compute water surface elevations. Bankfull parameters (width, depth, and roughness) are scaled to a bankfull event size (expressed as an bankfull-event-producing runoff rate in meters per year) which is specified in the parameter BANKFULLEVENT. Additional hydraulic geometry parameters are:
HYDR_WID_COEFF_DS: coefficient in the width versus bankfull discharge relation
HYDR_WID_EXP_DS: exponent in the width versus bankfull discharge relation
HYDR_WID_EXP_STN: exponent in the at-a-station width versus discharge relation
HYDR_DEP_COEFF_DS: coefficient in the depth versus bankfull discharge relation
HYDR_DEP_EXP_DS: exponent in the depth versus bankfull discharge relation
HYDR_DEP_EXP_STN: exponent in the at-a-station depth versus discharge relation
HYDR_ROUGH_COEFF_DS: coefficient in the roughness vs. bankfull discharge relation
HYDR_ROUGH_EXP_DS: exponent in the roughness versus bankfull discharge relation
HYDR_ROUGH_EXP_STN: exponent in the at-a-station roughness vs. discharge relation
BANK_ROUGH_COEFF: coefficient in the bank roughness vs. bankfull disch. relation
BANK_ROUGH_EXP: exponent in the bank roughness versus bankfull discharge relation
Note that the calculated channel width and depth are not used directly in the erosion and sediment transport equations, for the sake of generality. These relationships are, however, typically embedded in the terms of those equations, and care must be taken to ensure consistency between the erosion parameters and the hydraulic geometry parameters.
Detachment and Sediment Transport
There are six parameters that govern particle detachment by running water: KR (the detachment coefficient for regolith), KB (the coefficient for bedrock), MB (the discharge exponent), NB (slope exponent), TAUCD (detachment threshold), and PB (excess stream power or shear stress exponent). Note that, if appropriate, these can be reduced to three effective parameters by setting KR=KB, TAUCD=0, and PB=1 (see for example Whipple and Tucker, 1999).
It is often advantageous to assume a detachment-limited condition, in which sediment transport capacity is not a limiting factor for surface erosion. Detachment-limited erosion will occur naturally under conditions of high transport capacity and/or low detachment capacity, but the overhead of computing transport rates at every point can involve a considerable computational burden that is often unnecessary. For such cases, the model provides an option for purely detachment-limited erosion, in which transport capacities are not calculated. To invoke this option, set OPTDETACHLIM to 1.
Sediment transport can be modeled using either a simple power law or using the sand- gravel bedload transport equations of Wilcock (1998). For performance reasons, the choice between these two options must be made at compile-time rather at than run-time. The sediment transport option is specified in the header file erosion.h. To change it, change the defined constant tSedTrans as follows:
#define tSedTrans tSedTransPwrLaw
or
#define tSedTrans tSedTransWilcock
for the power-law and Wilcock (1998) models, respectively.
For the power-law sediment transport model, the required parameters are KF (transport coefficient), MF and NF (discharge and slope exponents, respectively). For the Wilcock sand- gravel equations, the mean diameter of the sand (GRAINDIAM1) and gravel (GRAINDIAM2) fractions must be given. (Note that the appropriate sediment transport parameters must be included in the input file even when running in detachment-only mode).
Diffusive Hillslope Transport
Diffusive sediment transport involves two parameters. The first of these is the diffusivity constant (KD) in m2/yr. The second, OPTDIFFDEP, is an option that controls whether diffusive transport contributes to both erosion and deposition, or to erosion only. In some cases, there may be reason to apply diffusion only to convex (erosional) elements of topography, with any deposited sediment assumed to be removed rapidly by water erosion (see, e.g., Moglen and Bras, 1994). Set OPTDIFFDEP to 1 to deactive the deposition component hillslope diffusion.
Sediment Size and Sorting
Use the NUMGRNSIZE parameter to specify the number of grain size fractions, but beware: only the single-size (power-law) and dual-size (Wilcock) sediment transport models are currently supported, so that NUMGRNSIZE must be either 1 or 2. (However, the model data structures are configured to handle any number of grain size classes, so the addition of transport formulae using more than two size-fractions would be straightforward). For each size fraction, you will need to specify the median diameter in meters (GRAINDIAMn, where n is the size class), the volumetric proportion of that size class in the regolith substrate (REGPROPORTIONn; see below), and the volumetric proportion of that size class that would be generated from erosion into bedrock (BRPROPORTIONn). You will also need to specify the depth of the active layer within which sediment mixing and selective transport occur (MAXREGDEPTH).
Setting Up Initial Stratigraphy
In general, each model node may include any number of layers of variable thickness and sediment composition. By default, the model initializes with a simple, spatially uniform stratigraphy that consists of a column of bedrock overlain by a column of regolith. The initial regolith thickness may be zero. The total column thickness must be deeper than the maximum potential erosion depth. The initial thickness of the bedrock and regolith columns are set by the parameters BEDROCKDEPTH and REGINIT, respectively, and their erodibility factors are KB and KR. (See " Erosion Parameters" on page 12.) Alternatively, the model can be initialized with a variable sequence of layers of different thickness, composition, and erodibility at each node. This is the method used to restart a run in which stratigraphy matters, and it simply involves setting the OPTREADLAYER parameter to 1. Layer data are then read from a file having the name specified in INPUTDATAFILE followed by the extension .lay. (This file must have the format as the layer output file; typically it is a layer output file from a previous run. The file format is summarized in Table ).
Configuring Uplift
"Uplift" here refers to any vertical motion relative to the model boundaries, whether positive or negative. Two uplift functions are provided: (1) spatially uniform uplift at a specified rate and duration, and (2) uniform uplift on one side of a fault that runs parallel to the model's x-axis at a specified y-position. The parameter UPTYPE specifies the type of uplift to be applied, with 0 meaning no uplift, 1 meaning uniform uplift, and 2 meaning fault-bounded uplift. Uplift options 1 and 2 require you to specify the uplift duration in years (UPDUR) and the rate in m/yr (UPRATE). For fault-bounded uplift, an additional parameter specifying the y-coordinate of the fault in meters (FAULTPOS) must be given.
Stream Meandering
Stream meandering is activated by setting the parameter OPTMNDR to 1. Meandering will only be applied to nodes that have a discharge value greater than CRITICAL_FLOW (in m3/ yr). Typically, this threshold would be used in conjunction with an inlet to set up a primary meandering stream (see " Adding an Inlet" on page 10). Additional parameters that need to be included in order to simulate meandering are:
DEF_CHAN_DISCR: default channel discretization for meandering channels (widths)
FRAC_WID_MOVE: the maximum fraction of channel width a node is allowed to move in a step
FRAC_WID_ADD: distance a channel point moves before a new node is added in its wake, as a fraction of channel width
VEG_ERODY: erodibility of vegetated banks
LATADJUST: ratio of bank to bed erodibility
CHNGPROB: (not currently used)
BNKHTDEP: degree to which bank erodibility depends on bank height; 0=none, 1=all
To invoke layer interpolation when points are moved, set the parameter OPTINTERPLAYER to 1 (in the current version this must always be set to 1 to avoid errors). Further information on the meander model is given by Lancaster (1998).
Overbank Deposition
The overbank deposition module is invoked with the OPTFLOODPLAIN parameter. Parameters used by the overbank deposition module include the deposition rate constant (FP_MU, m/yr), the distance decay constant (FP_LAMBDA, meters), the minimum drainage area for a node to be considered a flood-initiation point (FP_DRAREAMIN, m2), and the magnitude of a runoff event large enough to generate an overbank flood (FP_BANKFULLEVENT, m/yr).
Eolian Deposition
Set the OPTLOESSDEP parameter to invoke the eolian deposition module, and specify the deposition rate in m/yr with the LOESS_DEP_RATE parameter.
Tracking Exposure Ages
To keep track of the effective surface exposure ages of individual layers, set OPTEXPOSURETIME to 1.
|
Name |
Symbol |
Units |
Description |
Remarks |
|
OPTREADINPUT |
- |
|
Option for initial mesh input or generation |
Five possible options |
|
NUMGRNSIZE |
- |
|
Number of grain size classes used in run |
1 or 2 |
|
MAXREGDEPTH |
- |
m |
Depth of active layer, and maximum depth of a deposited layer |
|
|
GRAINDIAMi |
Di |
m |
Mean diameter of grain size class i |
One for each size class; must be at least one |
|
OPTREADLAYER |
- |
|
Option for reading layers from input file |
0 or 1; set to 0 when generating new mesh |
|
REGPROPORTIONi |
- |
ND |
Volumetric proportion of size i in regolith |
One for each size class; range zero to one |
|
BRPROPORTIONi |
- |
ND |
Volumetric proportion of size i generated from eroded bedrock |
" |
|
REGINIT |
- |
m |
Starting thickness of regolith layer |
|
|
BEDROCKDEPTH |
- |
m |
Starting thickness of bedrock layer |
|
|
KR |
Kr |
vary |
Erodibility coefficient for regolith |
If layers are read in, values from layer file are used instead |
|
KB |
Kb |
vary |
Erodibility coefficient for bedrock |
" |
|
SEED |
- |
|
Seed for random number generation |
Must be an integer |
|
OPTINTERPLAYER |
- |
|
Option for layer interpolation when points are moved or added |
Must be 1 in current version |
|
OUTFILENAME |
- |
|
Base name for output files |
|
|
OPTVAR |
- |
|
Option for random rainfall variation |
|
|
PMEAN |
P |
m/yr |
Mean storm rainfall intensity |
|
|
STDUR |
Tr |
yr |
Mean storm duration |
|
|
ISTDUR |
Tb |
yr |
Mean time between storms |
|
|
OPTSINVAR |
- |
|
Option for sinusoidal variation in rainfall parameters |
|
|
OPTINLET |
- |
|
Option for an external water and sediment input |
|
|
FLOWGEN |
- |
|
Runoff generation option |
Four possible settings (0,1,2, or 3) |
|
OPTMNDR |
- |
|
Option for stream meandering |
|
|
BANKFULLEVENT |
- |
m/yr |
Runoff rate associated with bankfull flood event |
Used to compute hydraulic geometry |
|
HYDR_WID_COEFF_DS |
kwb |
vary |
Coefficient in bankfull width-discharge relation |
|
|
HYDR_WID_EXP_DS |
mwb |
ND |
Exponent in bankfull width-discharge relation |
|
|
HYDR_WID_EXP_ST |
mw |
ND |
Exponent in at-a-station width-discharge relation |
|
|
HYDR_DEP_COEFF_DS |
khb |
vary |
Coefficient in bankfull depth-discharge relation |
|
|
HYDR_DEP_EXP_DS |
mhb |
ND |
Exponent in bankfull depth-discharge relation |
|
|
HYDR_DEP_EXP_ST |
mh |
ND |
Exponent in at-a-station depth-discharge relation |
|
|
HYDR_ROUGH_COEFF_DS |
krb |
vary |
Coefficient in bankfull roughness-discharge relation |
|
|
HYDR_ROUGH_EXP_DS |
mrb |
ND |
Exponent in bankfull roughness-discharge relation |
|
|
HYDR_ROUGH_EXP_ST |
mr |
ND |
Exponent in at-a-station roughness-discharge relation |
|
|
BANK_ROUGH_COEFF |
kbr |
vary |
Coefficient in bank roughness-discharge relation |
|
|
BANK_ROUGH_EXP |
mbr |
ND |
Exponent in bank roughness-discharge relation |
|
|
MB |
mb |
ND |
Discharge exponent in detachment capacity equation |
|
|
NB |
nb |
ND |
Slope exponent in detachment capacity equation |
|
|
PB |
pb |
ND |
Excess power/shear exponent in detachment capacity equation |
|
|
TAUCD |
tcd |
vary |
Detachment threshold (e.g., critical shear stress) |
|
|
KD |
kd |
m2/yr |
Hillslope diffusivity coefficient |
|
|
UPTYPE |
- |
|
Type of uplift to be applied |
0 = no uplift |
|
RUNTIME |
- |
yr |
Duration of run |
|
|
OPINTRVL |
- |
yr |
Frequency of output to files |
|
|
OPTDETACHLIM |
- |
|
Option for detachment- limited erosion only |
|
|
OPTDIFFDEP |
- |
|
Option to deactivate deposition by hillslope diffusion |
|
|
OPTFLOODPLAIN |
- |
|
Option for floodplain overbank deposition |
|
|
OPTLOESSDEP |
- |
|
Option for eolian (loess) deposition |
|
Data output from CHILD include elevation, slope, drainage area, surface flow directions, surface water discharge, surface sediment composition, layer data, and information on the mesh triangulation. Output is written to a series of ascii files at selected intervals beginning with the initial state of the run (see OPINTRVL, Table 1). Each file contains one type of information (e.g., node elevations) and includes output from the start to the end of the run. The format of each file varies somewhat according to the type of data it contains, but all output files share the same header format: each time-slice is preceded by the simulation time (this line always begins with a space for easy identification) and the number of data elements for the current time-slice (equal to the number of nodes, edges, or triangles, depending on the contents of the file). The data for each node (or edge or triangle, as the case may be) then follow, separated by carriage returns. The format is illustrated below with a hypothetical node elevation file containing two time slices for a mesh with only three nodes:
0 // time 0
3 // 3 nodes
1.1 // elevation of node 0 at time 0
2.2 // elevation of node 1 at time 0
3.3 // elevation of node 2 at time 0
100 // time 100
3 // still 3 nodes
0.1 // elevation of node 0 at time 100
1.2 // etc.
2.3
Note that data elements are always listed in order by ID number (e.g., node ID), starting from zero. Note also that the number of elements can change between successive time-slices if dynamic remeshing is used (e.g., when points are moved, added, or deleted by the stream meandering routines), as can the order in which the elements appear (node ID's are reordered when nodes are sorted by network position, so node 1 at one time slice is not necessarily the same as node 1 at another). Each output file bears the name specified in the input file (OUTFILENAME; see Table 1) followed by a suffix that indicates something about what the file contains. Output files and their suffixes are listed in Table , below. (Further description of the format used by the triangulation files is given in " Creating a Mesh from Scratch" on page 5).
|
File Suffix |
Contents |
No. of data items per time slice |
Notes |
|
.nodes |
Node (x,y) coordinates, ID one spoke, and boundary code |
# of nodes |
Spoke ID is the ID of any edge having node as origin |
|
.edges |
ID numbers of origin and destination nodes and ID of the counter- clockwise edge |
# of edges |
Complementary listed together, e.g. edge B->A follows edge A->B |
|
.tri |
ID numbers of vertex nodes (CCW order), ID numbers of neighboring triangles opposite the vertex nodes, and ID numbers of clockwise-oriented edges that originate with the vertex nodes |
# of triangles |
-1 is used when no triangle lies opposite a given vertex |
|
.z |
Node elevations in meters |
# of nodes |
|
|
.area |
Drainage areas in square meters |
# of non- boundary nodes |
|
|
.net |
ID of downstream node to which each node drains |
# of non- boundary nodes |
|
|
.slp |
Gradient of edge along which flow from each node is directed |
# of non- boundary nodes |
For meandering nodes, a weighted average of several node-slopes is used |
|
.q |
Discharge at nodes in m3/yr |
# of nodes |
Represents discharge of most recent storm |
|
.lay |
Layer data: number of layers at each node and, for each layer, creation time, recent activity time, surface exposure age, vertical thickness, erodibility (KB or KR), sed/rock flag, and volumetric proportion of each grain size fraction in layer |
# of non- boundary nodes |
|
|
.tx |
Volumetric proportion of sand in active layer |
# of nodes |
Only applicable to sand-gravel transport model |
Error Messages
Being a research tool, CHILD does relatively little error-checking. The burden is on you the user to make sure that the format of your inputs is correct and that the parameter settings are reasonable. However, a limited amount of error handling is provided, and it is common to see error messages when a parameter is missing in the input file, the input mesh contains an error, etc. If you should happen to receive an "assertion failed" message, please report it to one of the following people along with the text of the error message and the input file that for the run that caused the error:
Greg Tucker<EMAIL_ADDRESS>Nicole Gasparini<EMAIL_ADDRESS>Stephen Lancaster<EMAIL_ADDRESS>Rafael Bras<EMAIL_ADDRESS>References
Beven, K.J., and Kirkby, M.J., 1979, A physically based variable contributing area model of basin hydrology: Hydrological Sciences Bulletin, v. 24, no. 1, p. 43-69.
Gasparini, N.M., 1998, Erosion and Deposition of Multiple Grain Sizes in a Landscape Evolution Model, unpublished M.Sc. thesis, Massachusetts Institute of Technology.
Gasparini, N.M., Tucker, G.E., and Bras, R.L., 1999, Downstream fining through selective particle sorting in an equilibrium drainage network: Geology, submitted.
Lancaster, S.L., 1998, A nonlinear river meander model and its incorporation in a landscape evolution model, unpublished Ph.D. thesis, Massachusetts Institute of Technology.
Leopold, L. and Maddock, T., 1953, The hydraulic geometry of stream channels and some physiographic implications: Professional Paper 252, United States Geological Survvey.
Moglen, G.E., and Bras, R.L., 1994, Simulation of observed topography using a physically-based basin evolution model: Ralph M. Parsons Laboratory, Hydrology and Water Resources Report Number 340, MIT, Cambridge, MA.
O'Loughlin, E.M., 1986, Prediction of surface saturation zones in natural catchments: Water Resources Research, v. 22, p. 794-804.
Tetzlaff, D.M., and Harbaugh, J.W., 1989, Simulating Clastic Sedimentation, New York, Van Nostrand Reinhold, 202pp.
Tucker, G.E., and Bras, R.L., 1998, Hillslope processes, drainage density, and landscape morphology: Water Resources Research, v. 34, p. 2751-2764.
Tucker, G.E., Gasparini, N.M, Lancaster, S.L., and Bras, R.L., 1997, An integrated hillslope and channel evolution model as an investigation and prediction tool, Technical report prepared for U.S. Army Corps of Engineers Construction Engineering Research Laboratory.
Tucker, G.E., Lancaster, S.T., Gasparini, N.M., Bras, R.L., and Rybarczyk, S.M., 1999, An object-oriented framework for distributed hydrologic and geomorphic modeling using triangulated irregular networks: submitted to Computers and Geosciences.
Whipple, K.X., and Tucker, G.E., 1999, Dynamics of the stream power river incision model: implications for height limits of mountain ranges, landscape response timescales and research needs: J. Geophys. Res., in press.
1 To whom correspondence should be addressed: Dept. of Civil & Environmental Engineering, MIT Room 48-429, Cambridge, MA 02139, ph.<PHONE_NUMBER>, fax<PHONE_NUMBER>, email gtucker@mit.edu


1947 is a very special year, not just to Indians, but to people living in every nook and corner of the world. It was the year when ACM (Association for Computing Machinery) was founded. ACM Student Chapter have been established in various institutions across the world since then. SVCE's ACM Student Chapter is one of the most well reputed associations both within and outside of the institution.Although it wasn't a part of the college when the college was first founded, it is now a permanent and integral part of SVCE which has achieved great acclaim and laurels throughout the years it has been active. Even though we are quite few in number, we strongly believe that quality is more important than quantity.
Organizing technical events intertwined with loads of fun filled challenges is our forte. Our wide variety of events boost both 'competing by learning' as well as 'learning by competing'! Participating in our events helps you take a step towards success, and thereby guides you to make your path towards success an interesting one rather than a difficult one. Things cannot get better than this!'
H.A.C.C. is a 24 hour hackathon where the brightest minds and innovative souls come together to create solutions to real problems. Held at Sri Venkateswara College of Engineering and conducted by ACM Student Chapter - SVCE, this year we aim
to be bigger and better than ever.
Know More.
The 25th of July, 2017, marked the inauguration of the ACM SVCE Student Chapter for the academic year 2017 - 2018. The Chief Guest for the event was Mr Rajesh Padmanabhan, Founder and CEO of NFN Labs, who enthused the audience with a realistic but motivating outlook on life, technology and entrepreneurial spirit. Additionally, the members of last year's chapter were felicitated and were encouraged to continue working with the current chapter.
The aim was to provide student-sourced guidance to other students on attaining maximum success in placement interviews. The event kick started with a mock coding round, followed by an interactive session where students who had already been offered jobs at companies such as Dell shared their valuable experience in interviews and answers to commonly asked programming questions. The event was a success, with each participant getting a confidence boost!
Currently a second year Ph.D. student at University of Montreal, Sharat Chandar was part of the class of 2012 of the Department of CSE, SVCE. Under the guidance of Dr.Susan Elias, former Head of Department (CSE), Sharat formed and the SVCE-ACM
Student Chapter and was instrumental in getting the chapter officially chartered by ACM New York on 26th August 2011. He served as the Chairman of the chapter for the year 2011-12 and one of his major accomplishments include successfully
organizing the National Level Programming Contest (NLPC), a nation-wide coding contest, during the year 2011.Before joining University of Montreal, Sharat was a Research Software Engineer at IBM India Research Lab between the period August
2014 - May 2015. Sharat did his MS by Research at Indian Institute of Technology Madras where he was working with Dr.Balaraman Ravindran.
Know More ..
Take a closer look at who each one of us are Know More...
©SVCE ACM Chapter. All Rights Reserved.
ACM SVCE is a leading student chapter in Sri Venkateswara College of Engineering with its core focus areas in the field of Datascience, Machine Learning and Natural Language Proccesing.


Better button mixins for [Bourbon scss framework].
For a look at how everything looks, check out this page with code samples and rendered buttons.
Include the mixins into your SCSS declarations.
button.purple {
// This will create a purple button
@include bbb_flat_style(#e310eb, white); // Ooooh flat style OTB!
@include bbb_size(2); // I would like it bigger than usual please
}
This is a list with the available mixin styles and their usage.
@include bbb_3D_style($background-color, $color, $shadow-size);
@include bbb_bordered_style($border-color, $color);
@include bbb_flat_style($background-color, $color);
@include bbb_simple_style($background-color, $color);
You can also change the size of the button with the size mixin. It is not obligatory, but it is a very easy way to set button size.
@include bbb_size(1); # you can use multipliers to define size
@include bbb_size(10px); # or pass the size you want with units
As Bourbon framework is itself designed to be expanded, the same logic applies to to these mixins. You will find it rather easy to create your own stylings and modify the already defined styles.
Lets create a pill button.
button.pill {
@include bbb_simple_style();
@include bbb_size();
border-radius: 100px;
}
For now, just copy/paste the files into a directory and @import("better-bourbon-buttons/bbb");
. There will be a better way in the near future.
Contributions are welcome! Please create a pull request.


Maharashtra govt formation: Uddhav Thackeray meets Sena legislators
He met NCP president Sharad Pawar in Mumbai last night.
by PTIAs the government formation process picked momentum in Maharashtra, Shiv Sena president Uddhav Thackeray on Friday met his party’s legislators to discuss the political situation in the state.
Sena MLA Bhaskar Jadhav told PTI that the meeting was convened to apprise the legislators of the government formation process and meetings of Congress-NCP leaders in Delhi.
Mr. Thackeray met NCP president Sharad Pawar in Mumbai last night.
Mr. Jadhav said whatever decision Mr. Thackeray takes will be binding on all legislators of Shiv Sena. “We would like Uddhavji or Aaditya Thackeray to be the CM,” he added.
Results of the October 21 Assembly polls were declared on October 24 and President’s rule was imposed in the state on November 12 after no party or combine staked claim to form the new government.
The state was plunged into a political crisis after the Sena broke its three-decade-long ties with the BJP after the latter declined to share the chief minister’s post.
The BJP and Sena, which fought the Assembly polls in alliance, had secured a comfortable majority by winning 105 and 56 seats, respectively, in the 288-member Assembly. The Congress and the NCP, pre-poll allies, won 44 and 54 seats, respectively.
For the better part of this week, Delhi was the centre of marathon meetings between top leaders of the NCP and Congress to explore the possibility of forging an alliance with the Shiv Sena, a party whose ideology is poles apart from the duo.


This is a individual project from Epicodus Bootcamp to reclone a site. I chose to reclone Reddit because it is one of my favorite websites and I would want to make a site that can filter my favorite post from each subreddits that I subscribed to.


The Salmon Cookie family is passionate about all things fish! Naturally, we think all fish are beautiful and make the most incredible artork. We have many fish items for sale, including a limited edition photo of our family enjoying our Salmon Cookies. Please take a moment to paruse our gallery and contact us for exclusive pricing.


Dwayne's Intro to Programming Notes
The Basics of the Web
-The web
-HTML (hypertext markup language)
-URL
-HTTP (hypertext transit protocol)
-Web Applications
Major Pieces of the World Wide Web
- Is a collection of HTML documents.
-HTTP: The main protocol of the web.
-Servers: computers that host the files that make up the web.
-Internet: The world's largest computer net work.
-Browser: A program that runs on your. computer to display files found on the web.
Computers are Stupid
Computers will literally only do what the programmer tells it to do. With that being said any small error within the code can completely mess up your program!
HTML Attributes
By learning code you'll be able to do plenty of things such as creating a hyperlink.
Inline/Block
HTML elements are either inline or block. Block elements form an invisible box around the content inside of them.


Before Change
writer = SummaryWriter(comment="-cartpole-es")
env = gym.make("CartPole-v0")
print(env)
obs = env.reset()
print(obs)
net = Net(env.observation_space.shape[0], env.action_space.n)
print(net)
After Change
step_idx = 0
while True:
t_start = time.time()
batch_noise = []
batch_reward = []
batch_steps = 0
for _ in range(MAX_BATCH_EPISODES):
noise = sample_noise(net)
batch_noise.append(noise)
reward, steps = eval_with_noise(env, net, noise)
batch_reward.append(reward)
batch_steps += steps
if batch_steps > MAX_BATCH_STEPS:
break
step_idx += 1
m_reward = np.mean(batch_reward)
if m_reward > 199:
print("Solved in %d steps" % step_idx)
print(batch_reward)
break
train_step(net, batch_noise, batch_reward, writer, step_idx)
writer.add_scalar("reward_mean", m_reward, step_idx)
writer.add_scalar("reward_std", np.std(batch_reward), step_idx)
writer.add_scalar("reward_max", np.max(batch_reward), step_idx)
writer.add_scalar("batch_episodes", len(batch_reward), step_idx)
writer.add_scalar("batch_steps", batch_steps, step_idx)
speed = batch_steps / (time.time() - t_start)
writer.add_scalar("speed", speed, step_idx)
print("%d: reward=%.2f, speed=%.2f f/s" % (step_idx, m_reward, speed))
pass


You're good to go! Click the link below to finalize your registration so you can enjoy access to our proprietary feed and trading community.
Best,Wall St. Jesus Team


host_security_create_task_token
Function - Create a new task with an explicit security token.
SYNOPSIS
kern_return_t host_security_create_task_token (host_security_t host_security, task_t parent_task, security_token_t security_token, audit_token_t audit_token, ledger_port_array_t ledgers, boolean_t inherit_memory, task_t child_task);
PARAMETERS
- host_security
-
[in security send right] The host's security port.
- parent_task
-
[in task send right] The port for the task from which to draw the child
task's port rights and address space.
- security_token
-
[in scalar] The task's security token.
- audit_token
-
[in scalar] The task's audit token.
- ledgers
-
[pointer to in array of ledger send rights] The set of ledgers from which the
task will draw its resources.
- inherit_memory
-
[in scalar] Address space inheritance indicator. If true, the child task in-
herits the address space of the parent task. If false, the kernel assigns
the child task an empty address space.
- child_task
- [out task send right] The kernel-assigned port name for the new task.
DESCRIPTION
The host_security_create_task_token function creates a new task from
parent_task with explicit security and audit token values, returning the name of the
new task in the parameter specified by child_task. Other than the security and audit token values, the child task
is as if created by task_create.
The host security port is a privileged port given to the system
bootstrap task for the use of this call.
Functions:
task_create,
host_security_set_task_token,
mach_msg.
NOTES
RETURN VALUES
RELATED INFORMATION


|
Vkx
0.1.0
Vulkan C++ extensions
|
A Buffer that is visible to the CPU and is automatically kept in sync (eHostVisible | eHostCoherent). More...
#include <Vkx/Buffer.h>
Public Member Functions | |
| HostBuffer ()=default | |
| Constructor. | |
| HostBuffer (std::shared_ptr< Device > device, size_t size, vk::BufferUsageFlags usage, void const *src=nullptr, vk::SharingMode sharingMode=vk::SharingMode::eExclusive) | |
| Constructor. More... | |
| void | set (size_t offset, void const *src, size_t size) |
| Copies CPU memory into the buffer. More... | |
| Public Member Functions inherited from Vkx::Buffer | |
| Buffer ()=default | |
| Constructor. | |
| Buffer (std::shared_ptr< Device > device, size_t size, vk::BufferUsageFlags usage, vk::MemoryPropertyFlags memoryProperties, vk::SharingMode sharingMode=vk::SharingMode::eExclusive) | |
| Constructor. More... | |
| Buffer (Buffer &&src) | |
| Move constructor. More... | |
| virtual | ~Buffer () |
| Destructor. | |
| Buffer & | operator= (Buffer &&rhs) |
| Move-assignment operator. More... | |
| operator vk::Buffer () const | |
| Implicitly converts into a vk::Buffer. | |
| vk::DeviceMemory | allocation () const |
| Returns the DeviceMemory handle. | |
Additional Inherited Members | |
| Protected Attributes inherited from Vkx::Buffer | |
| std::shared_ptr< Device > | device_ |
| Device associated with this buffer. | |
| vk::DeviceMemory | allocation_ |
| Buffer allocation | |
| vk::Buffer | buffer_ |
| Vulkan buffer. | |
A Buffer that is visible to the CPU and is automatically kept in sync (eHostVisible | eHostCoherent).
| Vkx::HostBuffer::HostBuffer | ( | std::shared_ptr< Device > | device, |
| size_t | size, | ||
| vk::BufferUsageFlags | usage, | ||
| void const * | src = nullptr , |
||
| vk::SharingMode | sharingMode = vk::SharingMode::eExclusive |
||
| ) |
Constructor.
| device | Logical device associated with the buffer |
| size | Nominal size of the buffer |
| usage | Usage flags |
| src | Data to be copied into the buffer, or nullptr if nothing to copy (default: nullptr) |
| sharingMode | Sharing mode flag (default: eExclusive) |
| void Vkx::HostBuffer::set | ( | size_t | offset, |
| void const * | src, | ||
| size_t | size | ||
| ) |
Copies CPU memory into the buffer.
| offset | Where in the buffer to put the copied data |
| src | Data to be copied into the buffer |
| size | Size of the data to copy |


{%- if login_redirect is defined -%}
{% include "components/redirection.html" %}
{%- endif -%}
{%- if refused is defined -%}
{% include "components/refused.html" %}
{%- endif -%}
Access denied
Sign in with your Google account
Sign in
{% include "components/request_access.html" %}


Successfully posted advertisement
Skills needed: {{ printSkills(i) }}
on {{ transformDate(advertisement.uploadTime) }}
{{ advertisement.descriptionText }}


Are you ready for an adventure? You can vacation anywhere in the world! Here are some destinations that would work for you!
- Mexico
- Spain
- Greenland
- South africa
Mexico officially the United Mexican States is a federal republic in the southern portion of North America. It is bordered to the north by the United States; to the south and west by the Pacific Ocean; to the southeast by Guatemala, Belize, and the Caribbean Sea; and to the east by the Gulf of Mexico.
- Great food!
- Great tourist spots!
Greenland is an autonomous constituent country within the Kingdom of Denmark between the Arctic and Atlantic Oceans, east of the Canadian Arctic Archipelago.


ORG_0000044 - room
Label
room
Sub class of
Definition
A space contained by a partitioned part of the inside of a building. Often has an identifier.
Definition source
Example
The Oval Office is a room in the White House.
Editor’s note
A room is not a structure. It is a space inside a structure.
Similar term in VIVO 1 Ontology
Term editor
Michael Conlon https://orcid.org/0000-0002-1304-8447


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object de.uniheidelberg.cl.swp.mlprocess.WEKARunner
public class WEKARunner
An interface class to access the WEKA API.
Several parts of the code are taken from the WEKA Wiki
and adapted to our needs in order to classify a single instance.
To use this class, WEKA 3.7.1 is needed and
to be placed in the resource folder.
| Constructor Summary | |
|---|---|
WEKARunner(weka.core.Instances trainInstances)
Creates a WEKA interface with a provided Instances for training. |
|
WEKARunner(java.lang.String trainArff)
Creates a WEKA interface with a local ARFF file for training. |
| Method Summary | |
|---|---|
void |
buildEvaluation()
Cross-evaluates our classifier. |
void |
buildEvaluation(java.lang.String testArff)
Evaluates our classifier with a test set. |
double[] |
getDistribution(weka.core.Instance instance)
Returns the output possibility of each possible label of an instance. |
weka.classifiers.Evaluation |
getEvaluation()
Getter for returning the evaluation of the classifier. |
double |
labelUnknownInstance(weka.core.Instance instance)
Classifies a single Instance. |
weka.core.Instances |
labelUnknownInstances(weka.core.Instances unkIns)
Predicts unknown labels of an Instances. |
void |
run(java.lang.String type,
java.lang.String options)
Entry point for external usage to construct the classifier given a machine learning algorithm. |
void |
run(java.lang.String type,
java.lang.String[] subtypes,
java.lang.String options)
Entry point for external usage to construct a stacking classifier with a meta machine learning algorithm for level 1 and multiple machine learning algorithms for level 0. |
void |
run(java.lang.String type,
java.lang.String subtype,
java.lang.String options)
Entry point for external usage to construct the classifier given a meta machine learning algorithm and a machine learning algorithm for a base-learner. |
static void |
writeInstancesToArff(weka.core.Instances instances,
java.lang.String savedArffPath)
Writes an Instances to an ARFF file. |
| Methods inherited from class java.lang.Object |
|---|
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public WEKARunner(java.lang.String trainArff) throws java.lang.Exception
trainArff
- Local ARFF file for training.
If
- WEKA couldn't be initialized.
java.lang.Exception
public WEKARunner(weka.core.Instances trainInstances) throws java.lang.Exception
trainInstances
- Instances used for training.
If
- WEKA couldn't be initialized.
java.lang.Exception
| Method Detail |
|---|
public void run(java.lang.String type, java.lang.String options) throws java.lang.Exception
type
- A base classifier (machine learning algorithm).options
- Options for the classifier.
If
- the classifier couldn't be initialized.
java.lang.Exception
public void run(java.lang.String type, java.lang.String subtype, java.lang.String options) throws java.lang.Exception
type
- A meta machine learning algorithm.subtype
- A machine learning algorithm.options
- Options for the classifiers.
If
- the classifier couldn't be initialized.
java.lang.Exception
public void run(java.lang.String type, java.lang.String[] subtypes, java.lang.String options) throws java.lang.Exception
type
- A meta machine learning algorithm for level 1.subtypes
- Multiple machine learning algorithms for level 0.options
- Options for the classifiers.
If
- the classifier couldn't be initialized.
java.lang.Exception
public void buildEvaluation(java.lang.String testArff) throws java.lang.Exception
testArff
- ARFF file to evaluate against.
If
- the evaluation couldn't be initialized.
java.lang.Exception
public void buildEvaluation() throws java.lang.Exception
If
- the evaluation couldn't be initialized.
java.lang.Exception
public weka.classifiers.Evaluation getEvaluation()
public weka.core.Instances labelUnknownInstances(weka.core.Instances unkIns) throws java.lang.Exception
unkIns
- Instances with unknown attributes.
If
- the Instances couldn't be labeled.
java.lang.Exception
public double labelUnknownInstance(weka.core.Instance instance) throws java.lang.Exception
instance
- Instance to be classified.
If
- the Instance couldn't be labeled.
java.lang.Exception
public double[] getDistribution(weka.core.Instance instance) throws java.lang.Exception
instance
- Instance for the distribution analysis.
java.lang.Exception
public static void writeInstancesToArff(weka.core.Instances instances, java.lang.String savedArffPath) throws java.io.IOException
instances
- Instances to be written to an ARFF file.savedArffPath
- Filename and -path of the Instances to be saved.
If
- the file couldn't be written.
java.io.IOException
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Justin Fields Injured Late In Fourth Quarter vs. Penn State
by Matt LombardiOhio State quarterback Justin Fields suffered some kind of lower leg injury late in the fourth quarter against Penn State. Luckily, it looks like he was able to escape without anything serious.
Fields, with his team leading 28-17, was forced to scramble on a 4th-and-5 with under three minutes to play. He fumbled the ball and landed awkwardly, staying on the ground for a minute or so before coming off of the field.
Ohio State fans were concerned that Fields had suffered a serious injury, but he eventually walked off the field under his own power. Once he got to the sideline, it seemed like he had just been shaken up.
Video shows Fields stumbling a few times as he falls to the ground. He lands awkwardly, but it doesn’t look like his knee or ankle buckles anywhere.
Ohio State wound up winning the contest 28-17 and clinching the Big Ten East. The Buckeyes next get Michigan before the Big Ten title game – likely against either Minnesota or Wisconsin.
Fields finished the game 16-of-22 for 188 yards with two touchdowns. He also added 68 yards on the ground.
Update: Head coach Ryan Day says he thinks Fields is “alright” – adding that he’s a “tough kid.” It seems like the Buckeyes dodged a bullet.
We’ll keep you updated on Fields’ condition. Hopefully he’s good to go for the showdown with the Wolverines.


Welcome
first name
Roles
User listing
Student
LECTURER
Admin
All
UserID
Salutation
First name
Last name
Role
Date of birth
Phone number
Email
Address
UserID
Salutation
First name
Last Name
Role
Date of birth
Phone number
Email
Address
Edit
Delete
Total Items: [[${totalItems}]] - Page[[${currentPage}]] of [[${totalPages}]] -
First
First
Previous
Previous
[[${i}]]
[[${i}]]
Next
Next
Last
Last
Create User


--- layout: post title: STDIN and ATDOUT Bash author: Galuh D Wijatmiko categories: [Script] tags: [bash,script] ---
Diagram Process
stdin->process->stdout
1.Stdin (Input)
stdin 0 Read input from a file
example :
cat < file
2. Stdout (Output)
stdout 1 Send data to a file (write).
example :
date > output.txt
cat output.txt
3. Stderr(Process)
Stderr 2 Send all error messages in default screen to a file. usually error message when porcess take place.
example :
rm /tmp/test.txt 2> error.txt
cat error.txt
How to direct ouput unwanted?
error message usually there on default screen, if we don’t want error message or message view on screen terminal, we get to throw to device file unix like on /dev/null or /dev/zero
example :
1. remove error message on view
command 2>/dev/null
2. remove message output on view
command >/dev/null
DIrections EOF (End Of File)
Example :
wc -w <<EOF
> This is a test.
> Apple juice.
> 100% fruit juice and no added sugar, colour or preservative.
> EOF
Direction read string
Example :
wc -w <<<“coba test”
grep galuh <<<“galuh tampan sekali”
Direction with other File Descriptor
exec 3< /etc/resolv.conf
cat <&3
output : nameserver <IP_ADDRESS>
remove directions
exec 3<&-
cat <&3
ouput : zsh: 3: bad file descriptor


Garden Minder Dashboard
Lets get some water on these plants, the quick and dirty way until this system is fully built!
Sensor Graph
Water Commands
Settings
-
Moisture Calibration:
- Server settings:
- Other setting:


--- # DO NOT EDIT! # This file is automatically generated by get-members. If you change it, bad # things will happen. layout: default title: "Jeremy Corbyn" house: commons ---
Jeremy Corbyn is the MP for Islington North.
What is a constituency?
Jeremy Corbyn is an MP in the Labour party.
What is a party?


Testing Framework
The MiStaMover tool has a testing framework which is designed to show that individual modules work as designed.
The test config files and programs can be found in a subdirectory in the MiStaMover source tree called test
The tests can be run by changing to the MiStaMover directory and typing
python test/myproxytest.py –runPipe
This will cause the myproxytest.py test to be run - as some tests can perform mulitple things the command line argument is used to determine which operation to run (in this case –runPipe)
The following tests are available
- emailtest.py
- uses email_global.ini
- starts a log server, creates an info message and emails a critical message
- ftptest.py
- uses ftp_global.ini data_stream_ftp.ini
- checks that config is valid, creates stopfile, creates push command, creates receipt command
- creates thank you file
- globustest.py
- uses rsync_global.ini data_stream_rsync.ini
- creates a transfer base, creates a command to test grid ftp credentials
- rsynctest.py
- uses rsync_global.ini data_stream_rsync.ini
- checks config, sets stop file command, sets up push command
- rsynctransfertest.py
- uses rsync_global2.ini data_stream_rsync2.ini
- sets up RsyncTransfer instance, transfers a file to another directory
- stagercontrollertest.py
- uses rsync_global_ini data_stream_rsync.ini
- sets up a stagercontroller instance and dumps the config
- transferbasetest.py
- uses rsync_global.ini data_stream_rsync.ini
- sets up a transferbase instance, runs a command ls -l via the transferdata method
- transferbasetest2.py
- sets up a transferbase - uses a mock object for logging
- runs an rsync command over the transferdata method


Column: Virtual staging gaining popularity to help sell homes | Honolulu Star-Advertiser
Have you ever viewed a house or condo for sale and it didn’t quite look the same as it did in the pictures? Read more
Mahalo for reading the Honolulu Star-Advertiser!
You're reading a premium story. Read the full story with our Print & Digital Subscription.
Already a subscriber? Log in now to continue reading this story.
Print subscriber but without online access? Activate your Digital Account now.


cgl
0.2.0
CGL
AbstractDiGraph
AbstractGraph
AdjacencyDiGraph
AdjacencyGraph
AdjacencyHash
AnyEdge
AnyGraph
BFSIterator
BinaryHeap
Color
DFSIterator
DiEdge
DiGraph
Directed
DotVisitor
Edge
EdgeError
EdgeIterator
Graph
GraphError
GraphIterator
GraphSourceIterator
Labelable
LabeledDiGraph
LabeledGraph
LDiEdge
LEdge
Undirected
Visitor
WDiEdge
WEdge
Weightable
WeightedDiGraph
WeightedGraph
WeightedLabeledDiGraph
WeightedLabeledGraph
struct
CGL::DiEdge(V)
CGL::DiEdge(V)
Struct
Value
Object
Included Modules
CGL::Directed(V)
Defined in:
cgl/edges.cr
Constructors
.new
(u : V, v : V)
Instance methods inherited from module
CGL::Directed(V)
==(other : AnyEdge)
==
,
hash(hasher)
hash
,
reverse
reverse
Instance methods inherited from module
CGL::AnyEdge(V)
clone
clone
,
to_tuple
to_tuple
,
u : V
u
,
u=(u : V)
u=
,
v : V
v
,
v=(v : V)
v=
Constructor methods inherited from module
CGL::AnyEdge(V)
new(u : V, v : V)
new
Constructor Detail
def self.
new
(u : V, v : V)
#


Settings Tab
The settings tab contains controls to set the scope and property values of selected queries.
The Scope to process list allows you to choose which source files you want to run your query against.
You can choose from the following options:
• Current Scope specifies all files within the model.
• Browser Selection specifies all selected files in the Results window.
• Group Selection specifies all files included in a selected group.
The Properties table allows you to view and set individual query properties.
You can choose from the following options:
• Status displays the status of the selected hit (new or removed).
• Weight displays the weight assigned to the selected query. Each query is assigned a weight that represents its relative importance to the Integrated Index of Quality. The more weight an item has, the greater its effect on the source code. The default weight for every item is 10.
• Hits displays the total number of hits found.
• Score displays the total quality score for the selected query or folder.
For Statistics Queries Only
• Threshold displays a numerical value that defines acceptable ranges for certain characteristics of your software. All threshold queries have default values. These threshold hits are instances where the threshold value was exceeded.
You can change property values by clicking the field and using the shortcut menu to toggle on the desired value or typing in the field.


|
|
intro | getting started | conv2aas | example | faq api : index | general | sfx | mod | misc | mixer |
Three simple examples of how to use AAS are included in the "AASExample", "AASExample2" and "AASExample_c++" folders that come with the SDK. "AASExample" and "AASExample_c++" work using the standard interrupt system, although this does mean that sound quality may suffer if it used in conjunction with other CPU-intensive interrupts. "AASExample2" uses a modified interrupt system that will work in all cases, although it does require more care to set up correctly. Feel free to modify the example code for use in your own projects.
The suggested structure for your project folder is as follows (the examples take the aas folder and conv2aas from the ‹root›/build folder present when you execute the Makefile in the root of the project to avoid duplication):
- AAS_Data : Folder. Contents:
- Your .mod, .raw and .wav files : In these examples there are three files here: Ambulance.wav, Boom.raw and one of FlatOutLies.mod, CALIBRA.MOD or its_just_sonorous.mod
- aas : Folder. Contents:
- lib : Folder. Contents:
- LibAAS.a : Main AAS Library.
- include : Folder. Contents:
- AAS.h : Main AAS header file. Should always be included in your projects.
- AAS_Mixer.h : Optional AAS header file. Should only be included if you intend to access the mixer directly (not recommended).
- Makefile : Your makefile. See below for suggestions on how to set it up to use AAS.
- conv2aas : The AAS conversion tool. Use Windows or Linux version depending on your system.
- Your .s, .c, .cpp, .h and other files : In this example, there is just one file here: AASExample.c (or, in "AASExample_c++", AASExample.cpp).
In order for your programs to compile successfully they must be linked to the AAS library. To do this, the following options should be passed to the linker:
-L‹path-to›/aas/lib : Adds the "aas/lib" subfolder to the list of folders that will be searched for library files.
-lAAS : Links the AAS library ("libAAS.a") to your project.
In order for the compiler to be able to find AAS's include files, the follow option needs to be specified at the compilation stage:
-I‹path-to›/aas/include : Adds the specified subfolder ("aas/include") to the list of folders that will be searched for include files.
Both of these options are specified in the Makefile included in the project. It may also be necessary to change the "CROSS =" line in the Makefile depending on the location and file names of the GBA tools on your system.
NOTE: the Makefiles in the individual example directories aren't selfcontaining for maintainability reasons. They include example.make which includes common.make. Both are found in ‹root›/make. To make a single makefile out of these, just recursively replace the include directive with the actual content of the included file.
Once the Makefile has been configured appropriately, it is safe to include the AAS header files in your project, as shown in the example code:
#include "AAS.h" #include "AAS_Data.h"The "AAS_Data.h" header file contains information specific to your project and is generated by the Conv2AAS program. The makefile included with the example code automatically calls Conv2AAS each time the program is compiled so that your project will always have an up-to-date header file and will be linked to the most recent version of the files in the "AAS_Data" folder.
AAS requires for one or some AAS-specific interrupts are set up correctly. This will require some general interrupt system to be set up.
You can use a specialized crt0.s file, which is how AAS used to be configured. But the easiest way to set them up is to use either libgba, or libtonc.
The AAS examples use libtonc as it seems to be the most popular general GBA library these days and because it's got much better documentation (see the reference and the interrupt tutorial). With libtonc, you can easily set the required interrupts from within your C code, provided that you include libtonc in you project.
The "AASExample" and "AASExample_c++" AAS interrupts have been configured for projects with no other CPU intensive interrupts. The only thing you need to do is to include the AAS and libtonc headers, initialize the interrupt handlers and assign AAS_Timer1InterruptHandler to the timer1 interrupt handler.
#include "AAS.h" #include "AAS_Data.h" #include "tonc.h" ... int main() { ... // Set up the interrupt handlers irq_init(NULL); // set timer 1 to AAS_Timer1InterruptHandler() irq_add(II_TIMER1, AAS_Timer1InterruptHandler); ...To understand how the general interrupt mechanism works exactly, read the Tonc interrupt tutorial.
A complication not mentioned in the explanation above is that AAS requires that its interrupt be processed very quickly to avoid audible gaps in the sound. This may cause problems if your code uses other CPU-intensive interrupts. In this situation, you should set up your interrupts a little bit differently.
First you should set up a timer 1 interrupt which automatically calls AAS_FastTimer1InterruptHandler. This is a simple routine that is designed to return quickly so as not to interfere with your own code. However, unlike AAS_Timer1InterruptHandler, AAS_FastTimer1InterruptHandler does not mix the next batch of audio so a seperate call to AAS_DoWork is also required. This must be done at least 50 times per second, although it is safe to do it more often than that. Doing it at the beginning of each VBlank is ideal. This method is demonstrated in "AASExample2". The code used in this case is shown below:
#include "AAS.h" #include "AAS_Data.h" #include "tonc.h" ... int main() { ... // Set up the interrupt handlers irq_init(NULL); // set timer 1 to AAS_FastTimer1InterruptHandler() irq_add(II_TIMER1, AAS_FastTimer1InterruptHandler); // call AAS_DoWork() during vblank irq_add(II_VBLANK, AAS_DoWork); ...Notice that it is necessary to set the vblank interrupt so that AAS_DoWork() will be called at least 50 times per second.
Once all the above is working, using AAS is remarkably simple. The code from "AASExample" is shown below. The code for "AASExample2" is identical apart from the fact that it plays a different MOD and includes the VBlank initialisation code mentioned above. The code for "AASExample_c++" is also very similar except main() is declared with "extern "C"" and again a different MOD is used.
#include "AAS.h" #include "AAS_Data.h" #include "tonc.h" // Registers for GBA keys #define REG_KEY (*(volatile AAS_u16 *)0x04000130) #define REG_KEY_A 0x0001 #define REG_KEY_B 0x0002 int main() { int keys, keys_changed; int prev_keys = 0; // Initialise AAS AAS_SetConfig(AAS_CONFIG_MIX_32KHZ, AAS_CONFIG_CHANS_8, AAS_CONFIG_SPATIAL_STEREO, AAS_CONFIG_DYNAMIC_OFF); // Set up the interrupt handlers irq_init(NULL); // set timer 1 to AAS_Timer1InterruptHandler() irq_add(II_TIMER1, AAS_Timer1InterruptHandler); // Start playing MOD AAS_MOD_Play(AAS_DATA_MOD_FlatOutLies); // Show AAS Logo (not required) AAS_ShowLogo(); // Main loop do { // Work out which keys have just been pressed keys = ~REG_KEY; keys_changed = keys ^ prev_keys; prev_keys = keys; // Play looping ambulance sound effect out of left speaker if A button is // pressed, stop when released if (keys_changed & REG_KEY_A) { if (keys & REG_KEY_A) AAS_SFX_Play(0, 64, 16000, AAS_DATA_SFX_START_Ambulance, AAS_DATA_SFX_END_Ambulance, AAS_DATA_SFX_START_Ambulance); else AAS_SFX_Stop(0); } // Play explosion sound effect out of right speaker if B button is pressed if (keys_changed & keys & REG_KEY_B) AAS_SFX_Play(1, 64, 8000, AAS_DATA_SFX_START_Boom, AAS_DATA_SFX_END_Boom, AAS_NULL); } while (1); return 0; }This code initialises AAS, starts playing FlatOutLies.mod, shows the AAS logo and then goes into an infinite loop whilst the MOD continues to play. Pressing A or B starts the Ambulance.wav or Boom.raw samples. It is important that AAS_SetConfig is called before AAS_MOD_Play, although AAS_ShowLogo can be safely called at any time. For more information about how these functions work, please read the API section of this documentation.


@cipig Hi, thank you for report. Yes, it's not convenient and might cause problems in the future. It might be a bit easier to allow coin enable even if only 1 electrum is available at the moment allowing MM2 reconnect to others periodically in background. Is it fine?


Home
Music
Travel
Once I start traveling, I will post pictures/videos of my adventures here. First stop, Philippines!
Adventures


the buttons and forms CSS3 styles collection is the easiest way, to make buttons and forms on webpages look great. It’s based on the wonderfull code from Tim O’Donnell and improved by Simon Waldherr. The complete code is licensed under the terms of the MIT-License, which allows you to use and to change everything for free.
to use this buttons, copy the above code to the position, where the button should be and the following lines to the head of your HTML page:
<link href="../css/baf.css"
media="screen" rel="stylesheet" type="text/css"/>
<link href="../css/icomoon.css"
media="screen" rel="stylesheet" type="text/css"/>
<script src="../js/baf.min.js"></script>
SELECT HEAD CODE
This is being tested in the latest versions of Chrome, Safari, Firefox and Opera.
MIT License (MIT)
Copyright © 2013 Tim O’Donnell, Simon Waldherr
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Creative Commons (CC)
the icons on this paga are provided by icomoon.io and licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License.
baf v. 2.0.2
11.2013
This is a fork of
todcs
css3-google-buttons.
Inspired by Michael Henriksen’s
CSS3 Buttons,
Twitter Bootstrap, and of course, Google.
Icons from
glyphicons.com and icomoon.io


| Name
|
Min. Rank
|
Components
|
Survaillance
|
Retrieval
|
Speed
|
Range
|
Favor
|
|---|---|---|---|---|---|---|---|
| {{ship.name}} | {{ship.minRank}} | {{ship.components}} | {{ship.survaillance}} | {{ship.retrieval}} | {{ship.speed}} | {{ship.range}} | {{ship.favor}} |
| Name | Slot | Rank | Components | Survaillance | Retrieval | Speed | Range | Favor | Delete |
|---|---|---|---|---|---|---|---|---|---|


Toggle navigation
Playground
Home
Reviews
Notes
Users
Logged in as {{currentUser.username}}
Log out
Roles:
{{role.name}}
Sign up
Sign in


The answer is (I hope) obvious. It is a good idea to keep the GUI code and the application code in separate modules to help in debugging and understanding the program. This is also helpful if you later need to make changes to the program, say changing it from an application to an applet. The application code can be carried over without change.
Let us develop another GUI application. The USDA recommends that the food you eat have less than 30% of its total calories in fat. This application calculates the percentage of calories that come from fat, given the number of grams of fat and the number of calories per serving of a food. Fat contains 9 calories per gram.


Discharge Summary: Iowa Dept of Public Health
Patient Name: Russell Johnson Medical Record Number: 123456789 Admission Date: 08/01/14 Discharge Date: 08/05/14 Attending Physician: Dr Gary Marshall Dictated by: Dr Gary Marhsall Primary Care Physician: Dr Dianna Miller Referring Physician: Consulting Physician(s): Dr Gary Marshall - hospitalist Condition on Discharge: stable Final Diagnosis: RLL pneumonia, COPD exacerbation, mild CHF, osteoarthritis Procedures: none History of Present Illness 72 year old thin white male presented to emergency on 8/1/14 with shortness of breath, weakness and dehydration. Chest X-ray showed right lower lobe infiltrate, ABGs unremarkable. Pulse ox on RA was 79%. 1) Pneumonia: treated with ceftriaxone and azithromycin iv. Switched to PO after 72 hours. 2) Exacerbation of COPD: patient treated with inhaled and oral steroids, O2 at 2l/nc. On RA at time of discharge 3) Weakness and dehydration: secondary to pneumonia and COPD. Responded well to strengthening with PT and regular meals. Discharge Medications Zithromycin daily until gone, inhalers #of puffs, Discharge Instructions: no activity restriction, regular diet, follow up in two to three weeks with regular physician.
Discharge Summary: Innova Fairfax Hospital Dept of Medicine
Patient Name: John Smith Date of Admission: November 2, 2004 Date of Discharge: November 5, 2004 Attending Physician: Dr. ChinHee Kim Dictating Physician: Dr. Ho Admitting Diagnosis: Right Lower Lobe Pneumonia Discharge Diagnoses: Principal discharge diagnosis: Right Lower Lobe Pneumonia due to Streptococcus Pneumoniae Other discharge diagnoses which were addressed during hospitalization: 1. Type 2 diabetes mellitus 2. Congestive Heart Failure due to idiopathic cardiomyopathy 3. Hyponatremia due to SIADH versus CHF Consultations: None Procedures: Echocardiogram – EF – 32%, global hypokinesis Complications: None History and Hospital Course: The patient is a 55 year old white male who presented with typical symptoms of pneumococcal pneumonia with the initial chest X-Ray showing a right lower lobe infiltrate. An initial ABG revealed a respiratory alkalosis and a pO2 of 55 on room air. 1. Pneumonia – The patient was initially treated with ceftriaxone and azithromycin. Subsequent blood cultures revealed a sensitive pneumococcus. Symptoms improved and repeat chest X-ray did not reveal evidence of a pleural effusion. WBC count the day prior to discharge was 12,000 with a normal differential. Pulse oximetry was 95% on room air on the day of discharge, 2. Type 2 Diabetes – Initially, blood sugars were difficult to control. He was treated with basal, prandial, and correctional insulin with an average blood sugar of 150 on the day prior to discharge. 3. Congestive Heart Failure – The patient had a history of idiopathic cardiomyopathy with a normal cardiac catheterization in 2002. An echocardiogram was performed with results as above. Based on the improvement of his dyspnea with treatment of his pneumonia, it was thought that CHF was not the cause of his admitting symptoms. His lisinopril dose was increased from 10 mg to 20 mg daily. 4. Hyponatremia – The patient’s initial sodium level was 126. This was thought to be due to either SIADH from his pneumonia or due to CHF. With the treatment above, his sodium improved and on the day prior to discharge was 137. Other discharge labs: TSH – 3.4 Discharge Plan: Condition on discharge: Much improved. Able to ambulate without difficulty. Activity: No restriction. Diet: 2000 calorie ADA Follow up appt: the patient has an appointment to see Dr. Eric Bonura at the IFH discharge clinic at 8PM on 7/28/06. Discharge Meds: Amoxicillin 500 mg PO tid x 10days, Lisinopril 20 mg PO qday, Furosemide 40 mg PO bid, Levothyroid 100 mcg PO qday, Atorvastatin 20 mg PO qday, aspirin 81 mg PO qday, Lantus 20 units SQ qhs, Humalog 4 units prior to each meal Issues to be addressed at follow up – Assess tolerance of new lisinopril dose and consider addition of a beta blocker for management of CHF. CC: Dr. Eric Bonura
Hospital Progress Note: Soc of Teachers of Family Medicine
S: Patient abdominal pain improved overnight and tolerating clear liquid diet. Patient continues to use PCA for pain but controlled on basal rate of 0.5 mg Dilaudid hourly. Patient not scoring on SAS protocol. No acute event in the last 24 hours. O: Tmax 37.6, HR 87, RR 16, B/P 130/82 I/O 2200/2500; IV fluids 2000 oral fluids 200 ml CBC reviewed and stable BMP reviewed; potassium 3.1 this am otherwise stable Chest x-ray normal Physical Exam General: Alert and oriented; in no acute distress CV: RRR, trace of bilateral lower extremity edema noted Resp: CTAB Abdomen: Soft, non-distended, tender to palpation in the epigastric region without radiation; no guarding; negative Cullen’s and turners sign A/P: 45 y/o male with admitted for acute pancreatitis Hospital day #4 Acute pancreatitis/alcohol induced Continue pain control and will transition to oral pain meds Continue clear liquid diet Monitor I and O Continue IV fluids (requires inpatient care) Hypokalemia KCL 40 mEq BID today only and recheck BMP in the AM Alcohol dependence Consult SW for inpatient alcohol rehab Discharge SAS as patient not scoring for 3 days Continue inpatient observation


Admin Clothing Website
Home
Products
My Cart
Products Admin
Create Product
Modify Product
Remove From Stock
Add To Stock
Remove Product From Menu
Add Product Back To Menu
Help
Contact Us
FAQs


Menu
About
Contact
Gallery
Projects
Blog
My Heading
Lets go get it
To Contact Me:
Coding
Sharing what I've learned
Hanging with my family


My name is Hemang R. I live in Kitchener, Canada. I have 1.5 years of experience in Networking and Security in which I provided network support, installation and analysis for a broad range of LAN/WAN/MAN communication systems.
I also have a deep understanding of different layer 2 protocols like VLAN, VTP, STP, RPVST, Port Security and Ether Channels (LACP/PAGP). My experience extends to many domains such as Data-Center Nexus 2148T, 2224T, 5548P, 5596T, 7009,7018 and 6000 switches and configuring and fixing troublshoots problems of various Layer 3 protocols such as RIP, OSPF, EIGRP and BGP and supporting site-to-site and remote access Cisco, IPSec and VPN solutions using ASA/PIX firewalls.
In addition, I implemented VDC, VPC, VRF and OTV on the Nexus 5505 and 7009 switches and VSS on Cisco Catalyst 6509 and 6513 switches. I have practical knowledge of TACACS, AAA, IPSEC, 802.x and public/private key encrypition and I worked on F5 LTM and GTM series like 6400, 6800 and 88-- for the corporate applications and their availability.
Finally, I'm motivated to work and to be fully committed to the job I will have and to give the best quality work due the the studies and experiences I have in the field.
Information Technology & Business Analysis Course
Master of Science in Computer Science
Bachelor of Engineering in Electronics & Communication
In this project, I constructed wireless network topology in OPNET which connects various computers to a single network. Additionally, I analyzed the result of the attack which revealed the decrement in throughput of nodes and increase in delay by implementing Jamming Attack. Finally, I used channel switching attack to resolve the attack.
I surveyed most common inpainting methods and origins like Criminisi method, PDE based, Texture synthesis based and Semi-Automatic & Fast. In addition, I researched and developed a new algorithm and improved exemplar based algorithm with wireframe mesh and color map concept, and I implemented it on MATLAB.
This was my second project. I surveyed different algorithms of removing noises from an image like Linear Filtering, Non-Linear threshold filtering and Non-Orthogonal wavelet transforms. I finally implemented Wavelet Coefficient Model on MATLAB.
This is the first project I worked on. I started by observing multiple micro controllers like Intel 8048/8051 family and Atmel ATiny/ATmega series. And I finished the project by designing PCB layout using Eagle tool and I implemented the circuitry with ATmega 8535 controller and GSM modem to wirelessly monitor heartbeat and temperature through SMS notifications.
I've done a lot of things in my experience with Integra Technologies such as configuring and installing network devices and services. I also managed to perform network maintenance and system upgrades, monitor performance, ensure system availability and reliability, monitor system resource utilization and trending and capacity planning.In addition, I provided Level 2/3 support and troubleshooting to resolve issues. My work there didn't stop at that point, I successfully migrated the Cisco legacy environment and fixed troubleshoot problems in Cisco Aironet 600 and 2700 series.
In my work with Web Drills, I was responsible for monitoring the network performance in the company and cabling and labeling of several network equipment . Additionally, I provided Helpdesk support which involved identifying and escalating the tickets to specific groups, and I designed and implemented Cisco 2600, 3600, 6500, 7200, 7500 series routers in lab environment to reproduce various issues and test fixes for the company. Finally, I configured VSS on Cisco Catalyst 6509 switches to have redundancy and STP for loop prevention and VTP for Inter-VLAN routing. I had a lot of experience and learnt so many new things in the time I spent in Web Drills.
I believe that my experience as a Network Engineer at my past positions, makes me the best match for your company. After working in this same last position with the same organization for over one years, I successfully managed to gain a lot of skills that were an added value to my knowledge, such as monitoring performance and ensure system availability and reliability, configuring and install various network devices and services, performing OS upgrades on various Catalyst series switches and maintained latest OS versions according to company’s policy, providing network support, installation, and analysis for a broad range of LAN / WAN / MAN communication systems, Involved in troubleshooting of DNS, DHCP and other IP conflict problems. I am as well very experienced in Data-center nexus. When it comes to the soft skills, I am organised and able to priorities the workload, I am able to manage stress and to visualize, articulate, and solve both complex and uncomplicated problems and concepts and make decisions that are sensible and based on available information, in addition to my eye for details. Effective communication is my top strength because listening to customers, clients, or project partners, problem-solving becomes much more difficult and time-consuming, particularly the ability to communicate with staff who aren't technically trained. In addition to my ability to adapt and take my hard skills and make them work for whatever the company needs. To sum up, I'm confident that I can make an immediate impact on your company. I hope to hear from you soon.
Contact Me Now
Call to Action


fun getDifferenceInAngleRadians(from: Double, to: Double): Double
Get the difference in angle between two angles.
from - The first angle
from
to - The second angle
to
Return The change in angle from the first argument necessary to line up with the second. Always between -Pi and Pi


Check your answers
Your details |
||
|---|---|---|
| About you: | {{data['claimant-type']}} | Change Name |
| Name: | {{data['claimant-firstname']}} {{data['claimant-lastname']}} | Change Name |
| Date of birth: | 3 12 1971 | Change Name |
| Phone: | {{data['claimant-phone']}} | Change Name | Address: |
First line of address Second line of address Town or city Postcode |
Change Contact details |
| Updates: | Email and text | Change Updates |
Return to overview


{{data.title}}
{{data.value}}
Web Development
Know About Me
{{skill.title}}
{{skill.percentage}}/100
Know About Me