I am a Computer Science Graduate Student at Northeastern University.
Before commencing a graduate degree, I was working for Infosys Ltd. and Prolifics in India since 2014. My 5 years of work experience working with EDI and gateway team has helped me grow my skills in team collaboration, verbal communication, and project leadership. Along with these skills, I also have domain knowledge of the healthcare insurance industry that I gained from projects I worked on.
I am interested in learning, understanding and working on Cloud Computing. The change of perspective in designing applications and systems from central architecture to purely cloud-based distributed architecture is what excites me. Along with Cloud Computing, I am also interested in the field of Artificial intelligence and Machine Learning Applications along with web technologies and how I can put all these pieces together to create software systems or product which can help people or an organization in their day-to-day life.

Created infrastructure for Encounter Resolutions and Operations along with Claim Processing, ERA Processing using IBM ITX and IBM IIB.
Developed maps using IBM ITX and ITXA to convert ANSI X12, CSV, XML, JSON, Fixed Length files.
Led EDI managed service team that analyzes various process failures in production.
Proposed code improvement design and effectively managed team to implement a design that resulted in an 80% reduction in turn-around time for ticket resolution and improved in work efficiency of the team.
Along with the EDI gateway team, worked with an automation team to design a Java-based system to interact with the UNIX system for automation of enrollment and claim status inquiry processes at the gateway.
Interacted with business clients for providing resolution/analysis for critical process failures, day to day incident management and creation of break-fix SR.
Performed requirement gathering and effort estimations for file processing and transformation (to and from ANSI X12, CSV, Fixed length, XML) using IBM WTX/ITX based on requirement complexities.
Implemented a multi-file format project requirement using IBM WTX and shell scripting, which resulted in new business acquisition for the client resulting in a 30% increase in billing for the company from the client for the full project design and implementation.
Provided release support while production deployment and production check out.
Developed custom validations for healthcare batch transactions like 834, 835, 837, etc. and real-time transactions like 270, 271, 276, 277, 278, etc. using C and Shell Scripting along with custom maps development for various vendors using IBM WTX to convert ANSI X12, CSV files to Fixed Length files and vice versa.


SpringBook
Create a New Post
Upload an Image
post
Upload image
{{progress.percentage}}%
Share
Post Successfully Created!


{% extends 'layout-base.html' %} {% block content %}
This page is central to my quest to learn (Python) programming. It reflects my conviction that the best way to learn is by constantly and endlessly challenging myself.
It has been said that it takes 10,000 hours of practice to truely master any skill. That is very unsatisfactory to me. First because I think that mastery comes more with the quality of the practice than the duration of the pactice. Secondly there is no reason to believe that a 'magic' number like 10,000 hours exists. Are you 'done' after that?  Now that is a depressing thought.
So here is what I propose and will execute to teach myself programming:
This website itself is the first of the challenges. I needed something that supports my mission, keeps it organized but does not get in the way.
On the one hand there is a list of challenges. This list is ever-growing and most of them should look impossible to me right now. Perfect. Any challenge should have goals ("Build a search engine") and resources ("Anatomy of a Web Search Engine, by L. Page and S. Brin"). Learn from the best :). I might not get around to getting all challenges done. Hopefully because I will learn so quickly that some seem "easy" and not worthwhile. Yep, let's hope.
On the other hand, we have the projects themselves: challenges that are (partly) finished and, most importantly, well documented. In fact, the code itself is published as examples of (semi-)literate programming. Every new project and change is automatically published and open for discussion.
The website works as a 'static site generator' in which the code files are the flatpages. A special comment-tag indicates what comments should be parsed as YAML metadata and HTML (from Markdown). This limits the projects to single files, but I think that would cover most of it.
I am Roy Prins, 35 years old, and I have no formal background in programming. I run a one-person consultancy firm: Snirp and my mind is always full of stuff to improve and build. I see no reason that is ever going to change and I think that being a good programmer would go a long way to help me build the stuff.
So I like a good challenge, in fact I need them. I welcome any idea or challenge. Maybe something you are stuck with or something that would surely be impossible for me to accomplish. Just start typing to challenge me.
{% endblock %}


# install.packages(RGalaxy)
library(RGalaxy) # We still need some core functions that we haven't edited yet
#> Loading required package: XML
#> Warning: package 'XML' was built under R version 3.4.4
#> Loading required package: tools
#>
#> Attaching package: 'tools'
#> The following object is masked from 'package:XML':
#>
#> toHTML
#> Loading required package: optparse
This vignette is the first attempt to generate a Galaxy tool from an arbitrary R script. The script is expected to include functions with roxygen-style documentation.
Also, these R functions should be lightly edited so that their expected parameters can be parsed by the functions from the RGalaxy package.
The biggest shortcoming of the RGalaxy package in my opinion is that the generated tool script relies on the used R function to be in a publically available package. The Galaxy tools will not include the right requirements tags needed to publish the generated Galaxy tools to any Galaxy instance.
Our approach will use a lot of the functionality of the RGalaxy package, but rewritten in a way that we use arbitrary custom R functions. To see an example workflow of how to generate tools using RGalaxy, see this RGalaxy vignette. However, the vignette is not very easy to follow but it shows some examples and descriptions that we won’t go over in this document.
Your R scripts need to be self-contained function definitions, for now. Later this should be extended to include tools that depend on other local functions that may be loaded with a simple source()
command.
The source R scripts can be given as a character vector of filenames, relative to the current working directory.
In this case we use the addTwoNumbersWithTest.R
. This file includes one very simple function defintion. All this script included is a function to sum two numbers and write the output to a file. In Galaxy we always expect the output to be a file, or collection of files. You can output R variables in .rds format, which may force you to change some other functions to take a file input rather than just an R variable.
Notice the following about the function definition below,
The documentation is used to create a help section to display in Galaxy.
The input parameters are defined by Galaxy Parameter Classes, following the methods in the RGalaxy package. This allows galaxy to understand the expected parameters and show them nicely in the Galaxy UI.
# The addTwoNumbersTest.R file
#' Add to numbers
#'
#' A test function to use as an example to create a galaxy tool.
#' It takes two numeric values and returns the sum to a .txt file.
#'
#' @param number1 First numeric value to sum
#' @param number2 Second numeric value to sum
#' @param sum Output file
#'
#' @details
#' Both arguments are required and contain test values to
#' automatically generate tool tests with.
#' These tests are included in the output .xml tool definition, and
#' can be tested using Planemo's test command.
#'
#' @return The sum of two values
#' @export
#'
#' @examples
# outfile <- tempfile(pattern = "sum")
# addTwoNumbersWithTest(5, 5, sum = outfile)
# readLines(outfile)
#'
addTwoNumbersWithTest <-
function(
number1=GalaxyNumericParam(required=TRUE, testValues=5L),
number2=GalaxyNumericParam(required=TRUE, testValues=5L),
sum=GalaxyOutput("sum", "txt"))
{
cat(paste0(number1 + number2, "\n"), file=sum)
}
You can still use this function straight in R, which is handy for testing but in many cases you could just make it a habit of writing function definitions like this right away!
# Example of function output using normal R variables
outfile <- tempfile()
addTwoNumbersWithTest(number1 = 5, number2 = 5, sum = outfile)
readLines(outfile)
#> [1] "10"
The output will be written to a tool directory, toolDir
. You may have only 1 tool directory but still have different groups of tools, set by toolGroup
.
toolScripts <- c("addTwoNumbersWithTest.R")
toolDir <- "tools"
toolGroup <- "mytool"
toolPath <- file.path(toolDir, toolGroup)
# Create tool directory if it does not yet exist
if (!dir.exists(toolPath)) {
warning(sprintf("Tool directory '%s' does not exist and will be created",
toolPath))
dir.create(toolPath, recursive = T)
}
Since our functions to transform into galaxy tools are not part of a package we can’t just use roxygen2::roxygenise()
. For us to create documentation the scripts need to be part of a package. So we create a temporary package for our functions.
require(devtools)
#> Loading required package: devtools
# Create temporary package directory
tempPackageDir <- file.path(tempdir(), "TempGalaxyToolPackage")
# Initialize R package file structure
if (dir.exists(tempPackageDir)) unlink(tempPackageDir, recursive = T)
devtools::create(path = tempPackageDir,
rstudio = F)
#> Creating package 'TempGalaxyToolPackage' in 'C:/Users/twillerthtlv/AppData/Local/Temp/RtmpiID8hV'
#> No DESCRIPTION found. Creating with values:
#> Package: TempGalaxyToolPackage
#> Title: What the Package Does (one line, title case)
#> Version: <IP_ADDRESS>00
#> Authors@R: person("First", "Last", email =<EMAIL_ADDRESS>role = c("aut", "cre"))
#> Description: What the package does (one paragraph).
#> Depends: R (>= 3.4.3)
#> License: What license is it under?
#> Encoding: UTF-8
#> LazyData: true
# Copy scripts to package R directory
file.copy(from = toolScripts, to = file.path(tempPackageDir, "R"))
#> [1] TRUE
# Document R functions in the R directory
devtools::document(tempPackageDir)
#> Updating TempGalaxyToolPackage documentation
#> Loading TempGalaxyToolPackage
#> Updating roxygen version in C:\Users\twillerthtlv\AppData\Local\Temp\RtmpiID8hV\TempGalaxyToolPackage/DESCRIPTION
#> Writing NAMESPACE
#> Writing NAMESPACE
#> Writing addTwoNumbersWithTest.Rd
# File directory example
list.files(tempPackageDir, recursive = T)
#> [1] "DESCRIPTION" "man/addTwoNumbersWithTest.Rd"
#> [3] "NAMESPACE" "R/addTwoNumbersWithTest.R"
For every documented function we can create a galaxy tool. Every function gets its own .Rd file in the man/
directory. Using this we can list the functions to galaxify.
# List all functions to galaxify
# Based on the criteria that they need to be documented
functionDocs <- list.files(file.path(tempPackageDir, "man"))
# Only 1 function in this case, otherwise we should create a loop.
funcName <- sapply(functionDocs, gsub, pattern = ".Rd", replacement = "")
cat(funcName,
sep = "\n")
#> addTwoNumbersWithTest
Firstly we need to gather the documentation for our new tool/function. This can be found in the man/
directory of our temporary package.
Here we print the contents of the .Rd documentation file created when we ran the devtools::document()
function. These files get created by the roxygen2
package, look up the documentation if you wish to learn more about the options and formatting.
rd <- parse_Rd(file.path(tempPackageDir, "man", functionDocs))
print(rd)
#> % Generated by roxygen2: do not edit by hand
#> % Please edit documentation in R/addTwoNumbersWithTest.R
#> \name{addTwoNumbersWithTest}
#> \alias{addTwoNumbersWithTest}
#> \title{Add two numbers}
#> \usage{
#> addTwoNumbersWithTest(number1 = GalaxyNumericParam(required = TRUE, testValues
#> = 5L), number2 = GalaxyNumericParam(required = TRUE, testValues = 5L),
#> sum = GalaxyOutput("sum", "txt"))
#> }
#> \arguments{
#> \item{number1}{First numeric value to sum}
#>
#> \item{number2}{Second numeric value to sum}
#>
#> \item{sum}{Output file}
#> }
#> \value{
#> The sum of two values
#> }
#> \description{
#> A test function to use as an example to create a galaxy tool.
#> It takes two numeric values and returns the sum to a .txt file.
#> }
#> \details{
#> Both arguments are required and contain test values to
#> automatically generate tool tests with.
#> These tests are included in the output .xml tool definition, and
#> can be tested using Planemo's test command.
#> }
#> \examples{
#> outfile <- tempfile(pattern = "sum")
#> addTwoNumbersWithTest(5, 5, sum = outfile)
#> readLines(outfile)
#> }
fullToolDir <- toolPath
scriptFileName <- toolScripts
source(scriptFileName)
functionToGalaxify <- get(funcName) # Get the function to galaxify
funcInfo <- list()
print(formals(functionToGalaxify))
#> $number1
#> GalaxyNumericParam(required = TRUE, testValues = 5L)
#>
#> $number2
#> GalaxyNumericParam(required = TRUE, testValues = 5L)
#>
#> $sum
#> GalaxyOutput("sum", "txt")
This is still a work in progress, below are the next steps to rewrite. All this code is taken from the RGalaxy package, or specifically from my edited Github mirror of it found here.
Look for the R/
repository and you’ll find the R/galaxy.R
script that contains most of the functions we need. Although many of the functions we DONT need, so we will work on rewriting the required functions.
if ( length(names(formals(functionToGalaxify))) > length(formals(functionToGalaxify)) )
gstop("All arguments to Galaxy must be named.")
for (param in names(formals(functionToGalaxify)))
funcInfo[[param]] <- getFuncInfo(functionToGalaxify, param)
# print(funcInfo)
if (!isTestable(funcInfo, funcName, package, functionalTestDirectory))
gwarning("Not enough information to create a functional test.")
if (!suppressWarnings(any(lapply(funcInfo,
function(x)x$type=="GalaxyOutput"))))
{
gstop(paste("You must supply at least one GalaxyOutput",
"object."))
}
createScriptFile(scriptFileName, functionToGalaxify, funcName, funcInfo,
package, RserveConnection)
### Create tool from scripts and documentation
# file.copy(system.file("galaxy", "tool_conf.xml", package="RGalaxy"),
# file.path(galaxyHome, "tool_conf.xml"), overwrite=FALSE)
# functionalTestDirectory <- "inst/functionalTests"
# funcTestDirectory <- file.path(functionalTestDirectory, funcName)
# message("Trying to create functional tests...")
# funTest <- CreateFunctionalTest(funcName, functionalTestDirectory)
#
# mywd <- getwd()
# Make temporary package with R scripts included
# These scripts can then include Roxygen2-style comments as is used for package
# documentation.
# RGalaxy requires your scripts to be in a package, most importantly to be
# able to use the generated documentation files (.rd format).
message("Building galaxy tool...")
galaxy(funcName,
galaxyConfig=GalaxyConfig(galaxyHome, toolDir,
"Local tools", toolDir),
RserveConnection=NULL,
functionalTestDirectory = functionalTestDirectory)


Copyright © Hazel E. Nelson. Used with permission.
From the NART-R source:
The NART-R is administered by giving the subject the list of 61* words and asking him to read each word aloud: “I want you to read slowly down this list of words starting here [indicate “DEBT” *] and continuing down this column and on to the next. I must warn you that there are many words that you probably won’t recognize, in fact most people don’t know them, so just guess at these, O.K.? Go ahead.”
The subject should be encouraged to guess, and all responses should be reinforced (“good”, “that’s fine”, etc.). The subject may change a response if he wishes to do so, but if more than one version is given the subject must decide which is his final choice. No time limit is imposed. If the subject becomes frustrated, encourage him to continue to the end. At the end of the task, if the subject wants more information, the examiner should feel free to tell the subject the correct pronunciation and/or meaning of each word (definitions are shown below). If a subject asks for feedback in the middle of the task, simply tell him that you have to wait until he reaches the end of the task.
The examiner indicates on the scoring form whether or not each word was pronounced correctly. It is OK to stop the subject and ask him to slow down if he is reading the words too quickly. Subjects should not be penalized for minor variations from the exact pronunciation: because of the irregular, non-phonetic, spelling of the words, it should be obvious when the subject is not familiar with the written form of the target word. At the end of the task, sum the number of errors and the number of correct items. It is very important the subject attempt all of the items. If the subject refuses to complete the entire task, do not score the task.
* First word is DEBT in the NART-R but CHORD in the NART. There are 61 words in the NART-R but 50 in the NART.
Definitions from the New Shorter Oxford English Dictionary. Pronunciations written in IPA, in British English, from:
| Word | Pronunciation | Definition | Pronunciation source(s) |
|---|---|---|---|
| CHORD | kɔːd | noun 1 †1 Agreement, reconciliation; an agreement, a peace treaty. Only in me. †2 = accord n. 4. lme–m17. †3 Mus. A concord; in pl., the notes added to a bass to make up a chord (sense 4). l16–m18. 4 Mus. A group of notes sounded usu. together, combined according to some system. m18. noun 2 1 Anat. = cord n.1 3, esp. in spinal chord, vocal chord m16. 2 A straight line joining the extremities of an arc. Cf. earlier cord n.1 5. l16. b Aeronaut. The width of an aerofoil from leading to trailing edge. e20. †3 = cord n.1 1. m17–e19. 4 The string of a harp or other instrument. Chiefly poet. or fig. m17. 5 Engin. Either of the two principal members of the truss of a bridge. l19. verb Form a chord (with); harmonize. |
WED, OALD |
| ACHE | eɪk | noun A continuous or prolonged dull pain, physical or mental. aches and pains colloq. minor ailments and physical discomforts. |
WED, OALD |
| DEPOT | ˈdɛpəʊ | noun 1 †a The action or an act of depositing. rare. l18–m19. b A deposit, a collection, a store. Now spec. (transf. f. sense 4 below) a localized accumulation of a substance in the body. m19. 2 A military establishment at which stores are deposited, recruits or other troops assembled, or, formerly, prisoners of war confined; esp. a regimental headquarters. l18. 3 A place where goods etc. are deposited or stored, often for later dispatch; a storehouse, an emporium. l18. b A place where vehicles, locomotives, etc., are housed and maintained and from which they are dispatched for service; N. Amer. a railway or bus station. m19. 4 A site in the body at which a particular substance naturally concentrates or is deposited. e20. |
WED, OALD |
| AISLE | aɪl | noun 1 A wing or lateral division of a church; a part parallel to, and usu. divided by pillars from, the main nave, choir, or transept. See also cross- aisle. lme. 2 A passage between rows of pews or seats; a passage between cabinets and shelves of goods in a supermarket etc. m18. 3 Any architectural division of a church. m18. |
WED, OALD |
| BOUQUET | buˈkeɪ | noun 1 A bunch of flowers, esp. a large attractive one for use at a ceremony. e18. b fig. A compliment. e20. 2 The perfume of wine etc. m19. 3 bouquet garni /"gA:ni/ [Fr., lit. ‘garnished bouquet’], a bunch of herbs for flavouring. m19. 4 A number of rockets etc. fired together. l19. |
OALD |
| PSALM | sɑːm | noun 1 A sacred song that is or may be sung in religious worship; a hymn. Also, any song or ode of a sacred or serious character. oe. 2 spec. Any of the sacred songs traditionally held to have been composed by King David, contained in the Book of Psalms, a book of the Old Testament and Hebrew Scriptures, used in both Jewish and Christian worship; a version or paraphrase of any of these, esp. as set for metrical chanting.  Cf. poulard. loe. †2 A eunuch. me–l17. 3 A dull-witted person. obs. exc. dial. m16. †4 A billet-doux. Cf. poulet. rare (Shakes.). Only in l16. 5 A kind of fish, esp. a red herring. dial. m17. B v.t. Make a capon of; castrate. l16. |
WED, OALD |
| DENY | dɪˈnaɪ | noun 1 (A) refusal of what is asked, offered, etc. lme–e17. 2 (A) contradiction of a statement; negation. m16–e17. verb 1 Contradict (a statement or allegation); declare to be untrue or untenable. me. 2 Logic. Assert the contradictory of (a proposition). lme. 3 Refuse to admit the truth of (a doctrine etc.); refuse to admit the existence or reality of. lme. 4 Refuse to recognize or acknowledge (a person or thing) as having a certain character or certain claims; disown, disavow, repudiate. lme. 5 Withhold (a thing requested, claimed, or desired); refuse to give or grant. (Foll. by to a person, or w. indirect obj.) lme. b Refuse access to (a person sought). m17. 6 Refuse the request or demand of (a person). Formerly also, reject (a candidate). lme. †b Refuse admittance to (a visitor). l16–m18. 7 Refuse to be or do. obs. exc. Sc. lme. 8 Refuse permission to or for; forbid (to do, the doing of). Now rare. lme. †9 Refuse to take or accept. lme–e18. 10 refl. Refrain from the gratification of desire; be abstinent. lme. |
WED, OALD |
| NAUSEA | ˈnɔːziə, ˈnɔːsiə | noun 1 A feeling of sickness, with loathing of food and inclination to vomit. lme. b Seasickness. m18. 2 transf. A strong feeling of disgust, loathing, or aversion. e17. 3 Something causing sickness or loathing. m17. |
WED, OALD |
| DEBT | det | noun 1 Something owed or due; something (as money, goods, or service) which one person is under an obligation to pay or render to another. me. b spec. In biblical translations and allusions: an offence requiring atonement, a sin. me. 2 A liability or obligation to pay or render something; the condition of being so liable or obligated. me. †3 (One’s) duty. Chiefly Sc. me–l16. † adjective Owed, owing. |
WED, OALD |
| COURTEOUS | ˈkɜːtiəs | adjective 1 Having manners such as befit the court of a prince; polite, kind, considerate, in manner or approach. me. †2 Of a superior: gracious. me–e19. 3 Of a deed, quality, etc.: appropriate to a courteous person, showing courtesy. me. |
WED, OALD |
| RAREFY | ˈrɛərɪˌfaɪ | verb 1 v.t. & (rare) i. Make or become thin, esp. by expansion; make or become less dense or solid. lme. 2 v.t. fig. Make less material; make (an idea, argument, etc.) more subtle; refine, purify. l16. |
WED |
| EQUIVOCAL | ɪˈkwɪvəkəl), ɪˈkwɪvəkl | adjective A adj. 1 a Of evidence, signs, etc.: of uncertain or doubtful significance. m16. b Of sentiments, an attitude, etc.: undecided. l18. 2 Capable of more than one interpretation; ambiguous. l16. †b Of a person: expressing himself or herself in equivocal terms. rare (Shakes.). Only in e17. 3 Of uncertain nature. m17. †4 Equal in name but not in reality. m17–m18. 5 Of a person, condition, tendency, etc.: questionable, suspicious; of doubtful merit or character. l18. noun †B n. An equivocal term; a homonym. m17–m18. |
WED, OALD |
| NAÏVE | naɪˈiːv | adjective 1 Unaffected, unconsciously artless. Also, foolishly credulous, simple. m17. b Of art etc.: straightforward in style, eschewing subtlety or conventional technique. Cf. primitive a. 9. m20. 2 Med. & Psychol. Not having had a particular experience before, or been the subject of a particular experiment; lacking the knowledge to guess the purpose of an experiment; esp. not having taken or received a particular drug. (Foll. by to.) m20. |
WED, OALD |
| CATACOMB | ˈkætəˌkəʊm, ˈkætəˌkuːm | noun 1 In pl. & †sing. The subterranean cemetery of St Sebastian near Rome, consisting of galleries or passages with recesses excavated in the sides for tombs. oe. 2 In pl. The many other Roman subterranean galleries; similar works elsewhere. m17. 3 sing. A single crypt or gallery in such works. rare. e18. 4 transf. A (wine) cellar. l18. |
WED, OALD |
| GAOLED | dʒeɪld | variant of jailed jail (verb): B v.t. Imprison; put in or as in jail. e17. |
WED, OALD, d suffix |
| THYME | taɪm | noun Any of various pungently aromatic dwarf labiate shrubs of the genus Thymus; esp. T. vulgaris (more fully garden thyme), a low erect Mediterranean plant cultivated as a pot-herb, and T. praecox (more fully wild thyme), a mat-forming plant of heaths, hill grassland, etc.; collect. the leaves of garden thyme, used as a flavouring. Also (w. specifying wd), any of several related or similar plants. |
WED, OALD |
| HEIR | ɛə, eə(r) | noun 1 A person receiving or entitled by law to receive property or rank as the successor or legal representative of the former owner. me. 2 transf. & fig. A person possessing or entitled to possess any gift or quality, orig. in succession to another. Now usu., a person to whom something, as joy, punishment, etc., is morally due. me. †3 fig. An offspring, product. lme–l16. verb (transitive) Inherit; be or make heir to; acquire by inheritance or succession. |
WED, OALD |
| RADIX | ˈreɪdɪks | noun 1 †a Math. A root of a number. l16–e18. b Math. & Computing. = base n.1 7. l18. †2 Astrol. & Astron. A fact used as a basis of calculation, as a nativity, a position of a planet, etc. e17–l18. 3 A thing in which something originates; a source. e17. †4 Philol. An original word or form from which other words are derived. m17–l18. |
WED |
| ASSIGNATE | ˈæsɪɡneɪt | adjective – obsolete; very rare! From the full Oxford
English Dictionary: [Etymology: Latin assignātus: see assignat n.] [Obs. rare.] Assigned, specified. [Quotations: 1471 G. Ripley "Compound of Alchymy" (Ashm. 1652) v. 150 Blacknes..ys Of kyndly Commyxyon to the tokyn assygnate.] |
NART notation as′-ig-nāt; my IPA adaptation from that and WED/OALD assignation, prelate |
| HIATUS | haɪˈeɪtəs | noun 1 A physical break in continuity; a gaping chasm; an opening, an aperture. rare in gen. sense. m16. b Anat. Any of various natural openings or gaps. Usu. w. specifying wd. l19. 2 A gap or break in continuity, esp. in a series or an account; a missing link in a chain of events; esp. in Geol. (the time value of) a break or unconformity in the stratigraphic sequence. e17. b Logic. A missing link in a chain of argument, a gap in reasoning or evidence. m19. 3 Gram. & Pros. A break between two vowels which come together without an intervening consonant in successive words or syllables. e18. |
WED, OALD |
| SUBTLE | ˈsʌtəl, ˈsʌtl | adjective 1 Not easily grasped, understood, or perceived; now esp., so delicate or precise as to elude observation or analysis.  Long rare or obs. me. †b Of ground: tricky. e–m17. 5 Of thin consistency, not dense, rarefied; (of a smell, colour, etc.) pervasive or elusive by reason of tenuity, faint, delicate. lme. b Of fine or delicate texture or composition. arch. lme. 6 Not thick or broad; thin, slender. Long rare or obs. lme. †7 Consisting of fine particles, finely powdered; (of particles) fine, minute. lme–l18. |
WED, OALD |
| PROCREATE | ˈprəʊkrɪˌeɪt, ˈprəʊkrieɪt | verb 1 v.t. & i. Bring (offspring) into existence by the natural process of reproduction; beget. lme. 2 v.t. Produce, give rise to, occasion. Now rare or obs. m16. |
WED, OALD |
| GIST | dʒɪst | †noun 1 A stopping-place, a lodging. noun 2 The right of pasture for cattle at a certain rate of payment etc.; the payment made for this; agistment. noun 3 1 Law. The real ground or point of an action etc. e18. 2 The substance, essence, or main part of a matter. e19. †noun 4 and verb 1 see JOIST n. & v. verb 2 = AGIST |
WED, OALD |
| GOUGE | ɡaʊdʒ | noun 1 A chisel with a concave blade for cutting rounded grooves or holes. Also, a surgical chisel for removing portions of bone. lme. b Bookbinding. A tool for impressing a curved line or segment of a circle on the leather; such a marking itself. l19. 2 An act of gouging; a groove or mark made by gouging. m19. 3 A swindle. US colloq. l19. verb 1 v.t. Cut or make holes in with or as with a gouge. l16. b v.i. Work with a gouge. m19. 2 v.t. Cut, hollow, scoop, or force (out) with or as with a gouge. e17. 3 v.t. & i. Force out the eye of (a person); force out (a person’s eye). l18. 4 v.t. & i. Cheat, steal, impose upon. N. Amer. colloq. m19. 5 v.i. In opal-mining, make an exploratory search to locate worthless material; dig for opal generally. Austral. m20. |
WED, OALD |
| SUPERFLUOUS | suːˈpɜːflʊəs, suːˈpɜːfluəs, sjuːˈpɜːfluəs | adjective and noun A adj. 1 Exceeding what is sufficient; extravagant; superabundant. Also foll. by of, din. lme. 2 Not needed or required; redundant, uncalled-for; unnecessary (also foll. by to do). Also, (of a person) doing more than is required. lme. †b Ineffective, unprofitable; vain. rare. m16–m17. †3 a Exceeding propriety or the norm; immoderate, inordinate. lme–e17. b Mus. = augmented 2. m18–m19. B absol. as n. the superfluous, that which is superfluous; superfluous people as a class. rare. m19. |
WED, OALD |
| SIMILE | ˈsɪmɪlɪ, ˈsɪməli | noun and verb A n. 1 A figure of speech involving the comparison of one thing with another of a different kind, as an illustration or ornament. lme. †2 Resemblance, similarity. Only in 17. B v.t. Pres. pple & vbl n. simileing. Express by a simile. rare. e18. |
WED, OALD |
| BANAL | bəˈnɑːl | adjective 1 Hist. Of or belonging to compulsory feudal service. m18. 2 Commonplace, trite, trivial. m19. ¶Sense 2 developed from the intermediate French sense ‘common to all’. |
WED, OALD |
| QUADRUPED | ˈkwɒdrʊˌpɛd, ˈkwɒdruped | noun A n. 1 An animal which has four feet, esp. an ungulate mammal. m17. †2 spec. A horse. m17–m19. B adj. Of or pertaining to quadrupeds; quadrupedal. m18. |
WED, OALD |
| CELLIST | ˈtʃelɪst | noun a player of the cello L19. |
OALD |
| FAÇADE | fəˈsɑːd, fæˈsɑːd | noun 1 The face or front of a building, esp. the principal front, looking on to a street or open space. m17. 2 An outward appearance or front, esp. one which is deceptive. l19. |
WED, OALD |
| ZEALOT | ˈzɛlət | noun and adjective A n. 1 Hist. A member of a Jewish sect in Palestine, whose passionate opposition to foreign rule led to the Jewish uprising of ad 66–70 against Rome. m16. 2 A person who is zealous (for a cause). Usu., a person who is carried away by excess of zeal; a fanatical enthusiast. m17. 2 w. w. newcomb Dedicated, and single-minded, he became a zealot in his determination to record..the rock art of Texas. w. styron The Professor was also a practicing Catholic, though hardly a zealot. B attrib. or as adj. That is a zealot; characteristic of a zealot. m16. |
WED, OALD |
| DRACHM | dræm | noun 1 = drachma 2. Now rare or obs. lme. b = dirham. Now rare or obs. m16. 2 A unit of weight orig. equal to the weight of a drachma; an apothecaries’ weight of 1/8 ounce (60 grains); an avoirdupois weight of 1/16 ounce (approx. 27.344 grains). Also = fluid drachm s.v. fluid a. lme. 3 fig. A small quantity. lme. |
WED |
| AEON | ˈiːən, ˈiːɒn | noun 1 An age of the universe; an immeasurable period of time; eternity; colloq. a very long time. m17. b Geol. The largest division of geological time, composed of several eras. m20. c Astron. & Geol. One thousand million years. m20. 2 The personification of an age; Gnostic Philos. a power existing outside time, an emanation or phase of the supreme deity. m17. |
WED, OALD |
| PLACEBO | pləˈsiːbəʊ | noun 1 RC Ch. The vespers for the dead, from the initial word of the antiphon formerly used to open the office. me. †2 A flatterer, a sycophant. lme–l18. 3 A pill, medicine, procedure, etc., prescribed more for the psychological benefit to the patient of being given a prescription than for any physiological effect. Also, a substance with no therapeutic effect used as a control in testing new drugs etc.; a blank sample in a test. l18. |
WED, OALD |
| ABSTEMIOUS | əbˈstiːmɪəs, əbˈstiːmiəs | adjective Sparing, moderate, not self-indulgent, esp. in food and drink. |
WED, OALD |
| DÉTENTE | deɪˈtɑːnt, French detɑ̃t | noun The easing of strained relations, esp. between States. |
WED, OALD |
| IDYLL | ˈɪdɪl | noun 1 A short description in verse or (freq. more fully prose idyll) in prose of a picturesque scene or incident, esp. in rustic life. l16. 2 An episode suitable for treatment in such verse or prose, esp. a love-story. m19. 3 Mus. An instrumental composition on a pastoral or sentimental subject. l19. |
WED, OALD |
| PUERPERAL | pjuːˈɜːpərəl | adjective Med. Of, pertaining to, accompanying, or following childbirth. |
WED |
| AVER | əˈvɜː, əˈvɜː(r) | noun and verb 1 A n. A draught horse; an old horse, a nag. oe. †B v.t. Supply with horse-transport. Only in oe. verb 2 †1 Declare true. lme–m17. †2 Prove true; confirm. lme–l17. 3 Law. Prove or justify (a plea etc.); make an averment that. lme. 4 Assert as a fact; state positively, affirm. l16. 5 Assert the existence or occurrence of. arch. e17. |
WED, OALD |
| GAUCHE | ɡəʊʃ | adjective 1 Lacking in tact or ease of manner, awkward, blundering; lacking in subtlety or skill, crude, unsophisticated. m18. 2 Math. Skew, not plane. arch. l19. b Chem. Of a molecular conformation: skew, having two groups staggered along a central axis by (about) 60 degrees. m20. |
WED, OALD |
| TOPIARY | ˈtəʊpɪərɪ, ˈtəʊpiəri | adjective and noun A adj. Concerned with, involving, or formed by the clipping of shrubs, trees, etc., into ornamental geometric, animal, or other shapes. l16. B n. The art of clipping shrubs etc. into ornamental shapes; an example of this, a piece of topiary work. e20. |
WED, OALD |
| LEVIATHAN | lɪˈvaɪəθən, ləˈvaɪəθən | noun and adjective A n. 1 An (imaginary or real) aquatic animal of enormous size; a sea-monster. lme. b fig. A man of vast and formidable power or enormous wealth. e17. c Anything very large of its kind; esp. a huge ship. e19. 2 [After Isa. 27:1.] Satan. lme. 3 [After a book by Hobbes, 1651.] The commonwealth, the State. In later use, a totalitarian or bureaucratic regime. m17. B adj. Huge, monstrous. e17. |
WED, OALD |
| BEATIFY | bɪˈætɪˌfaɪ, biˈætɪfaɪ | verb 1 Make blessed or supremely happy. m16. 2 RC Ch. Announce the beatification of; declare blessed. e17. |
WED, OALD |
| PRELATE | ˈprɛlɪt, ˈprelət | noun 1 An ecclesiastical dignitary of high rank and authority, as a bishop, archbishop, or (now Hist.) an abbot or prior. me. †b A chief priest of a religion other than Christianity, esp. the Jewish religion. lme–e17. †2 gen. A person with superiority or authority; a chief, a superior. lme–l18. |
WED, OALD |
| SIDEREAL | saɪˈdɪərɪəl, saɪˈdɪəriəl | adjective 1 Of or pertaining to the stars. m17. †2 Starlike, lustrous, bright. rare. Only in m17. 3 Of (a period of) time: determined or measured with reference to the apparent motion of the stars. Of planetary or lunar motion: relative to the stars. l17. 4 Concerned with the stars. m19. |
WED, OALD |
| DEMESNE | dɪˈmeɪn, dɪˈmiːn, dəˈmeɪn | noun and adjective A n. 1 Law (now Hist.). The possession of real property as one’s own. me. †b gen. Possession; dominion, power. me–m18. 2 a The land or territory subject to a ruler: sovereign territory; a realm, domain. arch. me. b sing. & (freq.) in pl. Landed property, estates. l16. 3 a Hist. Land held and worked by the owner for the maintenance of his or her own household, i.e. not let to a subordinate tenant. lme. b The land immediately adjacent to a manor-house etc. retained by the owner for his or her own use; the park, home farm, etc. m16. 4 fig. A district, a region; the territory or sphere of. arch. or poet. l16. B attrib. or as adj. Of, pertaining to, or constituting a demesne. lme. |
WED, OALD |
| SYNCOPE | ˈsɪŋkəpɪ | noun 1 Fainting; temporary loss of consciousness caused by an insufficient flow of blood to the brain, freq. due to blood loss, shock, long standing, overheating, etc. Also occas., local loss of blood pressure in any part of the body. lme. 2 Shortening of a word by omission of one or more syllables or letters in the middle; a word so shortened. m16. †3 Mus. = syncopation 2. m17–l18. 4 gen. A cutting short of something; sudden cessation or interruption. rare. m17. †verb 1 v.t. Cut short, reduce; slur over (a word or syllable). Only in lme. 2 Mus. a v.t. Syncopate. e–m18. b v.i. Be syncopated. m18–e19. |
WED, OALD |
| LABILE | ˈleɪbɪl | adjective 1 Liable to lapse. Of a person: apt to err or sin; Theol. liable to fall from innocence. lme. 2 Liable to undergo displacement in position or change in nature, form, chemical composition, etc.; unstable; esp. in Chem. (of an attached ligand or group) readily displaced by another, (of a bond) readily broken. e17. b Psychol. Emotionally or behaviourally unstable. m20. |
WED |
| CAMPANILE | ˌkæmpəˈniːlɪ, ˌkæmpəˈniːli | noun A (usu. lofty and detached) bell-tower, esp. in Italy. |
WED, OALD |
CHORD
ACHE
DEPOT
AISLE
BOUQUET
PSALM
CAPON
DENY
NAUSEA
DEBT
COURTEOUS
RAREFY
EQUIVOCAL
NAÏVE
CATACOMB
GAOLED
THYME
HEIR
RADIX
ASSIGNATE
HIATUS
SUBTLE
PROCREATE
GIST
GOUGE
SUPERFLUOUS
SIMILE
BANAL
QUADRUPED
CELLIST
FAÇADE
ZEALOT
DRACHM
AEON
PLACEBO
ABSTEMIOUS
DÉTENTE
IDYLL
PUERPERAL
AVER
GAUCHE
TOPIARY
LEVIATHAN
BEATIFY
PRELATE
SIDEREAL
DEMESNE
SYNCOPE
LABILE
CAMPANILE
There are 50 words in the NART.
Estimated Full Scale IQ = 127.7 – 0.826 × NART error score
Estimated Verbal IQ = 129.0 – 0.919 × NART error score
Estimated Performance IQ = 123.5 – 0.645 × NART error score
debt
gist
topiary
debris
corps
caveat
aisle
hors d’oeuvre
superfluous
reign
sieve
leviathan
depot
hiatus
prelate
simile
gauche
quadruped
lingerie
zealot
sidereal
recipe
paradigm
abstemious
gouge
facade
beatify
heir
cellist
gaoled
subtle
indict
demesne
catacomb
detente
syncope
bouquet
impugn
ennui
gauge
capon
drachm
colonel
radix
cidevant
subpoena
aeon
epergne
placebo
epitome
vivace
procreate
equivocal
talipes
psalm
reify
synecdoche
banal
indices
rarefy
assignate
There are 61 words in the NART-R. Estimated Verbal Scale IQ = 128.7 –
.89 × (Revised NART Errors)
Estimated Performance Scale IQ = 119.4 – .42 × (Revised NART Errors)
Estimated Full Scale IQ = 127.8 – .78 × (Revised NART Errors)
(The standard errors of estimate are 6.56, 10.67, and 7.63,
respectively.)


--- layout: post title: "Setup OpenShift's requirements through Ansible" date: '2016-08-02T09:39:24+01:00' tags: - redhat - ansible - automate - management - setup - openshift - requirements - v3 - openshift3 - playbook - prereq ---
Recently I've been involved in a OpenShift deployment for a customer's POC environment with a very time-limited constraint.
For that matter I've tried to handle all the necessary manual steps with the help of Ansible.
PLEASE NOTE:
You can launch the script from your laptop, a node outside or inside the OpenShift cluster.
Anyway remember that in case you'll use one of the master nodes for example, you should manually register it to RHN, attach it to ose3 channel and install Ansible by yourself.
In my case the machines are already installed (and subscribed) with Satellite6, so I don't need any subscription-manager registration task.
The machines are already installed with lvm2 enabled partition schema and the default VG has enough space to handle docker lvm pool (this is why I run only docker-storage-setup without configuring the /etc/sysconfig/docker file).
You may also find an updated version of the following file here: https://github.com/alezzandro/ansible-random-stuff/blob/master/playbooks/openshift_v3.2-requirements.yml
This is the playbook I wrote for setting up the prerequisites of OpenShift installation process:
[root@openshift01 ~]# cat init.yml
- hosts: all
tasks:
- name: yum clean all
command: yum clean all
- name: subscription-manager refresh
command: "subscription-manager refresh"
- name: Enable chosen repositories
command: "subscription-manager repos --disable '*' --enable rhel-7-server-rpms --enable rhel-7-server-extras-rpms --enable rhel-7-server-ose-3.2-rpms"
- name: install libselinux-python
yum: name=libselinux-python state=installed
- name: install NetworkManager
yum: name=NetworkManager state=installed
- name: enable NetworkManager
service: name=NetworkManager enabled=true state=started
- name: Install required packages
yum:
name: "{{ item }}"
state: installed
with_items:
- wget
- git
- net-tools
- bind-utils
- iptables-services
- bridge-utils
- bash-completion
- name: Update the system
yum: state=latest name='*'
- name: Install atomic-openshift-utils
yum: state=installed name=atomic-openshift-utils
- name: Install docker
yum: state=installed name='docker-1.10.3'
- name: Enable insecure docker registry
shell: sed -i "s|OPTIONS=.*|OPTIONS='--selinux-enabled --insecure-registry <IP_ADDRESS>/16'|g" /etc/sysconfig/docker
- name: docker-storage-setup
shell: docker-storage-setup
- name: enable docker service
service: name=docker enabled=true state=started
- hosts: masters
tasks:
- name: Install htpasswd
yum: state=installed name=httpd-tools
- name: ensure /etc/origin/master esists
file: path=/etc/origin/master state=directory
- name: checking if /etc/origin/master/htpasswd exists
stat: path=/etc/origin/master/htpasswd
register: p
- name: create developer user
shell: echo developer | htpasswd -i -c /etc/origin/master/htpasswd developer
when: p.stat.exists is not defined or not p.stat.exists
Please comment and/or integrate it in case you make the ansible playbook smarter!


| Class | Description |
|---|---|
| MovieBlockingKeyByDecadeGenerator |
BlockingKeyGenerator for Movie s, which generates a blocking
key based on the decade. |
| MovieBlockingKeyByYearGenerator |
BlockingKeyGenerator for Movie s, which generates a blocking
key based on the year. |
| MovieDateComparator10Years | |
| MovieDateComparator2Years | |
| MovieDirectorComparatorJaccard |
Comparator for Movie s based on the
Movie.getDirector() values, and their
TokenizingJaccardSimilarity similarity. |
| MovieDirectorComparatorLevenshtein |
Comparator for Movie s based on the
Movie.getDirector() values, and their LevenshteinSimilarity
similarity. |
| MovieDirectorComparatorLowerCaseJaccard |
Comparator for Movie s based on the
Movie.getDirector() values, and their
TokenizingJaccardSimilarity similarity, with a lower casing
beforehand. |
| MovieTitleComparatorEqual | |
| MovieTitleComparatorJaccard |
Comparator for Movie s based on the Movie.getTitle()
value and their TokenizingJaccardSimilarity value. |
| MovieTitleComparatorLevenshtein |


{% extends "../layout.html" %} {% block content %} BETA This is a new service – your feedback will help us to improve it. Home Keyword search Keyword search Enter a keyword {% endblock %}
BETA This is a new service – your feedback will help us to improve it.


Home
Our Team
About
Contact
Welcome to our team!
Chassis/Base
Superstructure
Electronics
Programmers
Copyright © 2015 Noah Miller Johnson


{% load i18n %}
{% csrf_token %}
{% for error in settingsform.non_field_errors %}
{{ error }}
{% endfor %}
{% include "gui/form_field.html" with field=settingsform.alias %}
{{ settingsform.hostname }}.{{ settingsform.domain }}
{% if settingsform.dns %}
{% blocktrans with ipaddr=settingsform.dns_content %}DNS A record pointing to {{ ipaddr }} will also be updated.{% endblocktrans %}
{% endif %}
{% for error in settingsform.hostname.errors %}
{{ error }}{% endfor %}
{% for error in settingsform.domain.errors %}
{{ error }}{% endfor %}
{% if settingsform.admin %}
{% include "gui/form_field.html" with field=settingsform.tags %}
{% include "gui/form_field.html" with field=settingsform.node %}
{% include "gui/form_field.html" with field=settingsform.template %}
{% include "gui/form_field.html" with field=settingsform.ostype %}
{% include "gui/form_field.html" with field=settingsform.vcpus %}
{% include "gui/form_field.html" with field=settingsform.ram addon=mb_addon %}
{% include "gui/form_field.html" with field=settingsform.note %}
{% if dc_settings.MON_ZABBIX_ENABLED %}
{% include "gui/form_field_checkbox.html" with field=settingsform.monitored %}
{% endif %}
{% include "gui/form_field_checkbox.html" with field=settingsform.installed %}
{% include "gui/form_field.html" with field=settingsform.hvm_type class="hvm-type-only" %}
{% if dc_settings.VMS_VM_SNAPSHOT_ENABLED %}
{% include "gui/form_field.html" with field=settingsform.snapshot_limit_manual %}
{# hidden by js when OSType != bhyve #}
{% include "gui/form_field.html" with field=settingsform.snapshot_size_percent_limit addon=percent_addon class="bhyve-related hvm-type-only" %}
{# hidden by js when OSType == bhyve #}
{% include "gui/form_field.html" with field=settingsform.snapshot_size_limit addon=mb_addon class="kvm-related zones-related" %}
{% endif %}
{# hidden by js when OSType is some kind of container #}
{% include "gui/form_field.html" with field=settingsform.cpu_shares %}
{% include "gui/form_field.html" with field=settingsform.zfs_io_priority %}
{% include "gui/form_field.html" with field=settingsform.zpool %}
{% include "gui/form_field.html" with field=settingsform.bootrom class="bhyve-related hvm-type-only" %}
{% include "gui/form_field.html" with field=settingsform.owner %}
{% if dc_settings.MON_ZABBIX_ENABLED %}
{% include "gui/form_field.html" with field=settingsform.monitoring_templates %}
{% include "gui/form_field.html" with field=settingsform.monitoring_hostgroups class="thin" %}
{% endif %}
{% include "gui/form_field.html" with field=settingsform.mdata %}


This holds the documentation for the Zeff Server when it is fully opensourced and documented for rational people.


| scale_shape {ggplot2} | R Documentation |
Scales for shapes, aka glyphs
Description
scale_shape()
maps discrete variables to six easily discernible shapes.
If you have more than six levels, you will get a warning message, and the
seventh and subsequence levels will not appear on the plot. Use
scale_shape_manual()
to supply your own values. You can not map
a continuous variable to shape unless scale_shape_binned()
is used. Still,
as shape has no inherent order, this use is not advised.
Usage
scale_shape(..., solid = TRUE)
scale_shape_binned(..., solid = TRUE)
Arguments
... |
Arguments passed on to discrete_scale
palette A palette function that when called with a single integer
argument (the number of levels in the scale) returns the values that
they should take (e.g., scales::hue_pal() ).
breaks One of:
-
NULL for no breaks
-
waiver() for the default breaks (the scale limits)
A character vector of breaks
A function that takes the limits as input and returns breaks
as output
limits One of:
-
NULL to use the default scale values
A character vector that defines possible values of the scale and their
order
A function that accepts the existing (automatic) values and returns
new ones
drop Should unused factor levels be omitted from the scale?
The default, TRUE , uses the levels that appear in the data;
FALSE uses all the levels in the factor.
na.translate Unlike continuous scales, discrete scales can easily show
missing values, and do so by default. If you want to remove missing values
from a discrete scale, specify na.translate = FALSE .
na.value If na.translate = TRUE , what aesthetic value should the
missing values be displayed as? Does not apply to position scales
where NA is always placed at the far right.
aesthetics The names of the aesthetics that this scale works with.
scale_name The name of the scale that should be used for error messages
associated with this scale.
name The name of the scale. Used as the axis or legend title. If
waiver() , the default, the name of the scale is taken from the first
mapping used for that aesthetic. If NULL , the legend title will be
omitted.
labels One of:
-
NULL for no labels
-
waiver() for the default labels computed by the
transformation object
A character vector giving labels (must be same length as breaks )
A function that takes the breaks as input and returns labels
as output
guide A function used to create a guide or its name. See
guides() for more information.
super The super class to use for the constructed scale
|
solid |
Should the shapes be solid, TRUE , or hollow,
FALSE ?
|
Examples
dsmall <- diamonds[sample(nrow(diamonds), 100), ]
(d <- ggplot(dsmall, aes(carat, price)) + geom_point(aes(shape = cut)))
d + scale_shape(solid = TRUE) # the default
d + scale_shape(solid = FALSE)
d + scale_shape(name = "Cut of diamond")
# To change order of levels, change order of
# underlying factor
levels(dsmall$cut) <- c("Fair", "Good", "Very Good", "Premium", "Ideal")
# Need to recreate plot to pick up new data
ggplot(dsmall, aes(price, carat)) + geom_point(aes(shape = cut))
# Show a list of available shapes
df_shapes <- data.frame(shape = 0:24)
ggplot(df_shapes, aes(0, 0, shape = shape)) +
geom_point(aes(shape = shape), size = 5, fill = 'red') +
scale_shape_identity() +
facet_wrap(~shape) +
theme_void()
[Package
ggplot2 version 3.3.3
Index]


This is s CLI (Command-Line Interface) Address Book application written in Java. Built by developers, for developers.
User Guide
Developer Guide
About Us
Contact Us
Some parts of this sample application were inspired by the excellent Java FX tutorial by Marco Jakob.


Atlanta BEST Program Resources
For graduate students and postdocs who want to explore biomedical-related career options, the Atlanta BEST program is a community that promotes career exploration and professional development with the goal of empowering trainees to make informed career decisions and achieve their career goals.


Accepting 15% off on payments made with Bitcoin, Monero, XHV, xUSD, and Ether
Email<EMAIL_ADDRESS>or DM @UserbaseHQ if interested
No credit card required.
Cancel anytime.
Requires a Prod subscription.
Requires a Prod subscription.
Userbase is 100% open source, MIT licensed. You can host it yourself always under your control, or we can run it for you for a full serverless experience.


Promises
Select example
-- Select an example --
Resolve and reject
Simple chains
Chaining with missing handlers
Error handling at the end of the chain
Attaching multiple handlers
Checking promise resolution
Retry
Delayed retry
Off to the races!
Rerun
Example code
Output
Library code


This code example shows how to setup sbt to use a customized Slick code-generator for working with an existing database schema. project/Build.scala
enables automatically as well as manually triggered code-generation. codegen/CustomizedCodeGenerator.scala
contains the code customizing Slick's code-generator. codegen/Config.scala
contains some shared configuration code between the code-generator and the main project. src/main/scala/Example.scala
uses the generated code. The code is generated into file target/scala-2.10/src_managed/slick/demo/Tables.scala
. The location can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control.
More info about Slick on http://slick.typesafe.com/docs/


top
|
up
|
prev
|
next
CurrentSolutionGuard Struct
Definition at line
3397
of
Build.cpp
Constructors
CurrentSolutionGuard
(
Solution
* solution)
Constructor Details
CurrentSolutionGuard Constructor
cmajor::build::CurrentSolutionGuard::CurrentSolutionGuard(
Solution
* solution)
Definition at line
3399
of
Build.cpp
:
3399
{
currentSolution
=
solution
;
}
top
|
up
|
prev
|
next


This is the path-finder application, which is separate from "our" application and context. Our domain model with cargo, itinerary, handling event etc does not exist here. The routing domain service implementation works against the API exposed by this application.


Fayose Explodes Over Kogi Election, Tells Nigerians What To Do To Yahaya Bello
by Philips SundayAyodele Fayose, the immediate past governor of Ekiti state, has expressed dismay over the scenes of violence recorded ahead of the Kogi governorship election.
Naija News reports that Fayose was reacting to the “persistent attack on Natasha Akpoti” a candidate of the SDP in the election and the attack on Governor Seyi Makinde by masked men on Friday in Lokoja, the Kogi state capital.
Reacting to the attacks in a tweet on the micro-blogging site, Twitter, Fayose said with what is going on in Kogi state, it is “obvious that Gov Yahaya Bello is averse to free and fair elections.”
The former Governor warned that should “anything happen to anyone in Kogi tomorrow (November 16) Nigerians should hold Yahaya Bello accountable.”
His words: “From the persistent attack on Natasha Akpoti and today’s use of masked policemen to attack Gov. Seyi Makinde, it is obvious that Gov Yahaya Bello is averse to free & fair elections.
“Should anything happen to anyone in Kogi tomorrow,Nigerians should hold Yahaya Bello accountable,” Fayose tweeted.


Your blog{{user.s}} {{user.are}} inaccessible. However, Blot still stores your account data and your blog posts. Please contact me with any questions.
Enable your account


| LdFlags-deprecated {Rcpp} | R Documentation |
In Rcpp versions prior to release 0.10.1 of November 2013,
LdFlags
and RcppLdFlags
were used to return the required
flags and options for the system linker to link to the Rcpp user
library. Since we no longer build or ship a user library, these
functions now return an empty string. As of Rcpp release 0.12.19,
these functions are now deprecated.
LdFlags() RcppLdFlags()
An empty string.
Dirk Eddelbuettel and Romain Francois
Dirk Eddelbuettel and Romain Francois (2011). Rcpp: Seamless R
and C++ Integration. Journal of Statistical Software,
40(8), 1-18. URL http://www.jstatsoft.org/v40/i08/ and
available as vignette("Rcpp-introduction")
.