AWS Account¶
Amazon Web Services (AWS) provides a wide variety of cloud-based products including analytics, application integration, AR and VR, cost management, blockchain, business applications, compute, customer engagement, database, developer tools, end-user computing, game tech, IoT, machine learning, management and governance, media services, migration and transfer, mobile, networking and content delivery, robotics, satellite, security, identity and compliance, and storage. Here at cloudmesh, we develop services through providers to support your utilization of many of these products.
Here we are especially interested in using the following services:
Amazon Elastic Compute Cloud (EC2) Amazon EC2 is a web service that enables users to perform elastic web-scalable computing while having complete control over instances. It is integrated with most AWS services such as Amazon S3, RDS, and VPC.
Amazon Simple Storage Service (S3) Amazon S3 an object storage service that offers a wide range of storage classes.
We provide a step-by-step guide on how to create an AWS account through the AWS Web page to utilize these services. For more information, you can consult the AWS FAQ.
First, we go to the AWS website
and click on Create an AWS Account
.
This will direct you to the account creation page. Now we fill out your
information and click Continue
.
Next, you will need to fill out your contact information. You can choose
Professional
or Personal
as your account type. Here in this
tutorial, we selected Personal
. Read the AWS Customer Agreement,
and check the box if agreed. Click on Create Account and Continue
to
continue.
Fill out your payment information and proceed. Dependent on your level of security, you may want to explore using a prepaid credit card if you do not want to use your regular credit card.
If you just started using AWS, you will have a free account for a while as AWS will state:
We will not charge you unless your usage exceeds the AWS Free Tier Limits. - Amazon AWS
Please review the terms of the free tier carefully.
Next your need to confirm your identity. You can choose either
Text message (SMS)
or Voice call
to receive your verification
code. Here we choose Text message (SMS)
. Enter your phone number and
the security check code and click Send SMS
.
Enter the 4-digit verification code you received from your phone, and
click on Verify Code
.
If you entered the correct verification code, you will see this page.
Click on Continue
.
You will need to choose your support plan. We chose Amazon’s free tier
Basic Plan
.
Congratulations! You have successfully created an AWS account. Now you
can click on Sign In to the Console
to sign in.
Enter the email address you used for registration, and click on
Next
.
Enter the password you used for registration, and click on Sign In
.
Now you’ve successfully signed in to the AWS Management Console.
You can click on Services
to explore AWS services through their Web
page.
You can also start managing your account and instances through our cloudmesh services. This is especially of interest if you use cloudmesh to manage your storage and computational needs while also being able to leverage other clouds.
[ ] To do verify this works and you have created a user.
Access Key¶
Now that you have an account it is necessary that you can authenticate to your cloud account from a program or a command line. The instructions for this can be found at
-https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html
However, it is far easier to use the convenient cloudmesh tools by just using the cloudmesh open command.
In case you have not yet added a user, you can visit the user creation page with
cms open account aws
Create and Download Access Key¶
After logging into your account, you will then see the following console:
Click on Add user
and begin the process of creating a new user.
Type the name cloudmesh
in the User name
and make sure you check
the programmatic access
:
After clicking on the Next: Permissions
, you then have to add the
user to a group. If you do not have any group created, click on
Create group
button and you will be redirected to the corresponding
page. You can call the group cloudmesh
and then check the select the
AmazonEC2FullAccess
for the permission:
After creating the group, select it so that the new user will be assigned to that group:
On the next page, you can create the tags for the new user. You can just
create a cloudmesh
key for the user as a tag:
The next page is the review page where you can review the information you entered:
After clicking on Create user
the user will be finally created and
you will be redirected to the following success page:
You can view the secret access key by clicking on the show
button:
Next, download the .csv
file by clicking on the Download .csv
button and save it as ~/.cloudmesh/credentials.csv
:
Then you can click on the close
button and go back to the IAM
Management Console which now provides you a summary of the newly created
user called cloudmesh
and looks like this:
By clicking on the Create access key
, you can create another access
key:
As is mentioned in the screenshot, this is the only time you can view
or download the secret access key. So go ahead and click on the
Download .csv file
and save it as ~/.cloudmesh/accessKey.csv
:
Using the Access Key¶
To obtain the keys for an already existing account or the one that you just created you can use the command
$ cms open account aws NAME
This command will open a browser window to the credential page of AWS. Please replace the NAME with your username that you created when you added your user to the IAM.
In case you do not yet have credentials choose the Security credentials tab and then choose to Create access key. To see the new access key, choose Show. Your credentials will look something like this:
Access key ID: AAABBCCHHH7EXAMPLE Secret access key: wJalrXUtnFhsjlashlkjh/bPxRfiCYEXAMPLEKEY
To download the key pair, choose Download .csv file. Store the keys in a secure location and do not by default store them in the Downloads folder. We recommend that you store is in ~/.cloudmesh, but before doing so make sure the permissions for ~/.cloudmesh are restricted,
Compute Service¶
Import Public key¶
Before we get started with AWS compute services, we need to be sure we
import our public ssh key. We assume ssh has already been set up
under ~\.ssh\id_rsa.pub
. If this prerequisite has not yet been
satisfied, please reference the installation section.
While logged into AWS’s console, navigate to the EC2 Management Console
under Services > Compute > EC2
:
Next, on the left-hand panel, navigate to
Network & Security > Key Pairs
and select Import key pair
. Once
you’re at the Import Settings screen, browse to ~\.ssh
and select
the id_rsa.pub
file. Name the imported file after the same username
configured you have configured in the cloudmesh.yaml file.
Cloudmesh.yaml Configuration for AWS¶
Please reference the section on Configuration for more information on getting, setting, and editing values to the cloudmesh.yaml configuration file; along with referencing the compute cloud provider templates and default values.
Run the following code to set the AWS compute provider values specific
to your configuration. Alternatively, you can manually set these values
using a text editor to update the cloudmesh.yaml file under
~\.cloudmesh
.
cms config set cloudmesh.cloud.aws.cm.active=true
cms config set cloudmesh.cloud.aws.credentials.region=AWSMGMTCONSOLEREGIONVALUE
cms config set cloudmesh.cloud.aws.credentials.EC2_SECURITY_GROUP=SECGROUPVALUE
cms config set cloudmesh.cloud.aws.credentials.EC2_ACCESS_ID=ACCESSIDVALUE
cms config set cloudmesh.cloud.aws.credentials.EC2_SECRET_KEY=SECRETKEYVALUE
Notes:
Region can be found while logged into the AWS management console in the upper right-hand side.
EC2_ACCESS_ID and EC2_SECRET_KEY values can be found either during the initial setup in AWS, or by referencing the Access Key downloaded as a csv and moved to the
~\.cloudmesh
directory.TODO: Confirm if EC2_PRIVATE_KEY_FILE_PATH and EC2_PRIVATE_KEY_FILE_NAME cloudmesh.yaml AWS compute variables are being utilized, as these are not referenced in
Provider.py
. If this is not needed, remove it from cloudmesh.yaml. If this is needed, update the AWS account section with the following steps:
Once the values have been set:
run the following to get started and test AWS compute services:
cms set cloud=aws
cms init
cms key init
cms vm boot
This should have allowed you to initialize cms with the updated configurations and boot up a new vm in AWS based.
Check the status of the vm by executing the following:
cms vm list --refresh
Now test stopping the vm. Note that you may need to give it a minute or two before you refresh the vm list to validate Status=stopped.
cms vm stop VMINSTANCENAME
Now test terminating the vm. (Note the example provided if you are attempting run commands against multiple vm’s.)
cms vm delete VMINSTANCENAME
[x] TODO: Aws EC2 account. Describe here if there is anything to be done for accessing EC2
Storage Service¶
AWS S3 and Credentials Set up:
Create an AWS account following the instructions above
Select S3 service in AWS Management Console
In the S3 service, create a bucket. (Please remember the bucket name and bucket region)
Select IAM service in AWS Management Console
In the IAM service, Add a new user with “Programmatic access” access type and “S3All” Permission
Remember the user “Access key ID” and “Secret access key”
Fill in the following info into the ~/.cloudmesh/cloudmesh.yaml file under “cloudmesh.storage.aws.credentials” section
bucket
access_key_id
secret_access_key
region
References¶
Additional information about the services can be found at:
Open Distribution for Elastic Search, https://aws.amazon.com/?nc2=h_lg
Amazon EC2, https://aws.amazon.com/ec2/?nc2=h_m1
Amazon S3, https://aws.amazon.com/s3/?c=23&pt=1


{% extends "layout.html" %} {% block title %} Help Page {% endblock %} {% from "formhelpers.html" import render_field %} {% block content %}
The answer to this question is all about you. You are unique, you are different from everyone else. You need to put more of yourself into your content and into your blogging presence in general.
By putting more of yourself into the open, the more unique your blog will be. There’s nothing to be afraid of. Just get yourself out there and enjoy the process.
This is one of the beauties of blogging. You can start in a few minutes without needing to spend any money at all. Even if you want to do podcasting and video blogging, you don’t need any more equipment than the technology you have inside your smartphone.
The biggest investment you will make in blogging is the investment of your time. Blogging simply needs and craves many hours of work in order to work.
You need to dig deeper and find what makes you special and different. What is it that you spend many of your hours on? What is it that you enjoy doing in your free time?
What is it that you know a lot about? There always is something that you have that other people can find value in. Be it educational, informative and/or entertaining.
Normally you would have to pay for the premium features and get access to all our premium features provided to keep your blogs up and running, and contribute to community.
So essentially, the cost of running a blog is less than the price of your morning coffee at Starbucks. Not to mention, this investment has the potential to make you full-time profits each month, enough to quit your day job even! I’d say that kind of return is worth the investment.
There aren’t exact rules but I recommend always to aim for 1800 words. This amount of content will give search engines a clear idea of the purpose and theme of that post, and it is enough content to thoroughly cover a subject in good detail. The emphasis though should also be on quality.
Traditionally, a blog was defined as a conversational website page or post that is updated regularly and written in a personal style. So a blogger could be said to be someone who puts a lot of focus on writing and creating content on their website.
These days bloggers can build a successful and profitable business around their content when it is high-quality and informative. Income such as via affiliates, by selling eBooks, one’s own online courses etc. mean the chance to monetise blogging.
One of the most common issues, with starting a blog, is the worry over putting information online and being open to the thoughts and criticisms of the world. Perfecting things and when to go live are also questions that are common when I talk with new bloggers.
My advice is that there you do not need to worry about trying to create perfection but to simply use your blog to express yourself and have a voice online.If you really think about it – what do you really have to lose? I bet the answer when you really consider this question, is – very little to lose, right?!
You can develop and grow as you write your blog and this can be something that your readers share with you. Take them on a journey! On your journey!


'TIL THERE WAS YOU A film review by Steve Rhodes Copyright 1997 Steve Rhodes
RATING (0 TO ****): *
"God, I love methamphetamines -- more than life itself," confesses ex-TV child star Francesca Lansfield (Sarah Jessica Parker). Francesca, who played Taffy on the perennially popular show called "One Happy Family" (think "Brady Bunch"), is fresh out of drug rehab. All of the men who grew up watching her have the hots for her now, and she says she is not shy since "my tits grew up on national television." (This last line and the incident where Jeanne Tripplehorn runs into a barrier were the only times the audience at the screening came alive.)
Scott Winant, who was one of the directors of the TV series "My So-Called Life," directs 'TIL THERE WAS YOU. Filmed by Bobby Bukowski in shades of pastel, the movie tries hard, too hard, to be a whimsical, romantic comedy. I've never seen Winant's television work, but this movie, Winant's first theatrical film, arrived DOA at the screening, and his direction as well as the disastrous script by Winnie Holzman were the culprits.
I spent most of the movie staring at the screen in disbelief. The dialog is little more than a collection of snippets of meaningless small talk, and the direction is so muddled that it takes quite a while to sort out what is happening and who is who. The bad news is that when the story does become clear, you will not care. The characters are as artificial as their favorite restaurant, whose interior is constructed out of aluminum triangles.
Jeanne Tripplehorn, who was terrific in BASIC INSTINCT, plays a ghost writer named Gwen Moss. Moss laments that she has missed the golden 10 minute window in her life when she was old enough to be married but not too old. Her life has gone down hill ever since.
Dylan McDermott is architect Nick Dawkan. Nick, who claims to be just about the only man in America who never saw "One Happy Family," has Francesca as his live-in lover. She has his body, but his mind pines for an unknown female letter writer to the local newspaper.
Midway through the movie, in a scene with Gwen's dad (Michael Tucker), it looks momentarily as if the film will finally get its footing. Her dad, who manages to be both funny and the only believable character in the film, bursts Gwen's bubble. "I'm going to tell you something important," he says while munching candy. "I never loved your mother. Not real love." She was shocked, and so was I, but then the film went right back to its plastic characters and her dad vanished. (You can almost hear the director screaming, "Get him off my set; he's not whimsical.")
Perhaps most offensive is the story's attitude toward smoking. It is way cool. You half expected to see a Joe Camel ad in the closing credits. Smoking represents rebellion and camaraderie among the characters.
To complement the film's painfully slow pacing, the unrelenting music by Terence Blanchard and Miles Goodman has a staccato piano that will begin to feel like water torture. I felt like the music was trying brainwash me into believing the film's drivel through the music's repetitive romantic rhythms, which had all of the charm of a stuck record needle.
Gwen's lover, Bob, proposes his solution to their romantic difficulties. "I think we should go to Paris," he suggests to her at the aforementioned aluminum restaurant. "Surrounded by rude French people should bring us closer together." With dialog like this why did the producers go forward with this project? The movie needs a rewrite and a new director. The cast would work if it had reasonable material.
'TIL THERE WAS YOU runs 1:44. The film is rated PG-13 for language, sexual suggestions and drug references. The picture is remarkably tame and would be fine for kids 10 and over, but why bother? I recommend you avoid the film, and I give it a single star for a good cast trapped in awful movie.
**** = A must see film. *** = Excellent show. Look for it. ** = Average movie. Kind of enjoyable. * = Poor show. Don't waste your money. 0 = Totally and painfully unbearable picture.
REVIEW WRITTEN ON: April 17, 1997
Opinions expressed are mine and not meant to reflect my employer's.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


git
git, The Stupid Content Tracker
Git is a free and open source distributed version control system designed to
handle everything from small to very large projects with speed and efficiency.
Git was created by Linus Torvalds in 2005 after BitKeeper, the previous Version Control System, which the Linux Community used between 2002-2005,
had become a paid service instead of being free-to-use.
This prompted Torvalds to create his own VCS (Version Control System) since there was no existing system that would've met his requirements.
Some the goals of the project were:
Speed
Simple design
Strong support for non-linear development (thousands of parallel branches)
Fully distributed
Able to handle large projects like the Linux kernel efficiently (speed and data size)
Since its birth in 2005, Git has evolved and matured to be easy to use and yet
retain these initial qualities. It's amazingly fast, it's very efficient with large projects, and it has an incredible branching system for non-linear development.
The origin of the name "git" is that the program needed a name that was not used in existing Unix-software and according to Torvalds,
it's a "stupid content tracker" and it can be "Global Information Tracker" when you are in good mood and everything works correctly or
"Goddamn Idiotic Truckload of sh*t" when it does not work.


BMS tree expansion
bracket =
(0,0,0,0)(1,1,1,1)
version 0.3
The program
is by koteitan
BMS is
Bashicu Matrix System v4
by BashicuHyudora


--- layout: post title: '[supervisord] Multiple processes in a single container' date: '2016-07-01T09:39:24+01:00' tags: - redhat - openshift - ose - origin - kubernetes - docker - container - supervisord - configuration - installation - multiple ---
Many times at customer site I have been asked for creating a container full of services, daemons and stuff like a container could be used like a full virtual machine.
After explaining the containers' real purpose, their correct usage and the differences between a container and a vm, the process of containerization could be a real pain and in some cases we could be not able to ensure the fundamental rule of 1 container : 1 process.
In the following example I'll show you the steps that drove me to create a multiprocess container: the postfix container.
Postfix is a free and open-source mail transfer agent (MTA) that routes and delivers electronic mail, intended as an alternative to Sendmail MTA.
The most challenging part of the process was to correctly place the logs for sent emails (by postfix) directly on STDOUT.
Logging to STDOUT ensures that some logs grabber (Fluentd in OpenShift v3) could take these logs and send them to the default logs management system (EFK - Elasticsearch/Fluentd/Kibana on OSEv3).
Unfortunately postfix by default wants to send logs to some rsyslog, that usually saves them to a log file, so I've been forced to create postfix container using multiple processes, violating what should be the best practice for creating a container: 1 process per container.
The three processes involved in the container creation were:
The last process to run and to leave in foreground, it was (for sure) the tail one. tail process will keep running in foreground while postfix and rsyslog do their job, but, what happen if postfix or rsyslog exits unexpectedly?
Nothing!
Docker container will keep running as soon as the tail process does. So your container orchestrator will never notice the absence of postfix process (unless you have some custom health check).
The solution I found was to use an internal processes orchestrator: supervisord (available in EPEL repo).
Supervisord will be responsible to watch and keep them running your configured processes. If a process exits unexpectedly it will run the process again.
So your Docker's CMD/ENTRYPOINT will be the supervisord command.
But now let's take a look to the Dockerfile itself:
FROM rhel7
RUN yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
RUN yum install -y postfix supervisor rsyslog
RUN sed -i "s/inet_interfaces = localhost/inet_interfaces = all/g" /etc/postfix/main.cf
RUN echo mynetworks = <IP_ADDRESS>/8, <IP_ADDRESS>/8, <IP_ADDRESS>/8, <IP_ADDRESS>/16 >> /etc/postfix/main.cf
COPY ./resources/supervisord.conf /etc/supervisor/supervisord.conf
COPY ./resources/rsyslog.conf /etc/rsyslog.conf
COPY ./resources/listen.conf /etc/rsyslog.d/listen.conf
CMD /usr/bin/echo myhostname=$myhostname >> /etc/postfix/main.cf; /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
Looking at 'resources' folder [1], you'll find the config file for rsyslog and supervisord, all the conf for postfix are done in place directly on Dockerfile.
Configuration for supervisord daemon is really simple:
[supervisord]
nodaemon=true
[program:postfix]
command=/usr/libexec/postfix/master -c /etc/postfix -d
[program:rsyslog]
command=/usr/sbin/rsyslogd -n
[program:readlog]
command=/usr/bin/tail -f /var/log/maillog
stdout_logfile=/dev/fd/1
stdout_logfile_maxbytes=0
As you can see in the readlog program definition I'm setting the proper stdout for tail to supervisord stdout.
The other two file "listen.conf" and "rsyslog.conf" are related to rsyslog itself and they contains edits suggested by a project-atomic blog post:
Running Syslog Within a Docker Container —Project Atomic
Just for quoting it:
The problem was that in RHEL7 and Fedora we now use journald, which listens on /dev/log for incoming messages. In RHEL7 and Fedora, rsyslog actually reads messages from the journal via its API by default.
But not all docker containers run systemd and journald. (Most don’t). In order to get the rsyslogd to work the way the user wanted, he would have to modify the configuration file, /etc/rsyslogd.conf:
- In /etc/rsyslog.conf remove $ModLoad imjournal.
- Set $OmitLocalLogging to off.
- Make sure $ModLoad imuxsock is present.
- Also comment out: $IMJournalStateFile imjournal.state.
That's all with these simple steps and the help of supervisord you should solve your problems!
I've successfully tested the container in various OpenShift environments, mainly as SMTP server (or with proper customization to the config file, as SMTP Relay server).
For more information please refer to:
[2] https://hub.docker.com/r/alezzandro/postfix/
[3] Postfix container used in a persistent Gitlab OpenShift Template: GitHub - sdellang/gitlab-openshift-persistent
If you have any comments/questions please comment!


Mercato Centrale Roma:
An Italian Food Market Not to Miss
About Mercato Centrale Roma
Spread over 1900 square meters and covering three floors, Mercato Centrale Roma has a whopping 18 food shops on the ground floor, while the first floor is home to celebrated Chef Oliver Glowig’s restaurant “La Tavola, il Vino e la Dispensa. The entire second floor is dedicated to tasting the delectable recipes of food artisans. Besides this, spaces for private functions and public events too are available on both the first and second floor.
You can taste authentic food while interacting with fellow foodies in a comfortable ambience. It is a one stop food destination that saved me the trouble of going to several different places scouting for my preferred choice of food. Dining here is all about fresh, local food direct from farm to kitchen and on to your plate. There are enough seating arrangements in the market to sit back and enjoy the food and beverages, but you can also pack it up to savor it later.
If you love artisanal food made using traditional methods, the food market is the place to go. Handmade by skilled food artisans with great expertise, these food products showcase Italy’s culinary heritage. You can relish the flavors of high quality local ingredients that are used to prepare the food products.
Reasons to Visit Mercato Centrale Roma
Mercato Centrale Roma is a bustling place filled with appetizing smells and sights that attracts food lovers looking for a good meal at reasonable prices. Good food at this market is all about cooking by going back to the roots or to the basics of culinary tradition and combining it with a contemporary approach to produce delicious food. International flavors too are adapted into the cuisine.
With skilled artisans and the best ingredients, the result is good food that will satisfy any visitor. The company slogan “La bontà è elementare” (goodness is simple) exemplifies this fact. You can drop by for breakfast, lunch, dinner or drinks from 8 a.m. till midnight.


Class: Aws::SageMaker::Types::PipelineExecutionStepMetadata
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb |
Overview
Metadata for a step execution.
Constant Summary
Instance Attribute Summary
-
#auto_ml_job ⇒ Types::AutoMLJobStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the AutoML job that was run by this step. -
#callback ⇒ Types::CallbackStepMetadata
rw
The URL of the Amazon SQS queue used by this step execution, the pipeline generated token, and a list of output parameters.
-
#clarify_check ⇒ Types::ClarifyCheckStepMetadata
rw
Container for the metadata for a Clarify check step.
-
#condition ⇒ Types::ConditionStepMetadata
rw
The outcome of the condition evaluation that was run by this step execution.
-
#emr ⇒ Types::EMRStepMetadata
rw
The configurations and outcomes of an Amazon EMR step execution.
-
#fail ⇒ Types::FailStepMetadata
rw
The configurations and outcomes of a Fail step execution.
-
#lambda ⇒ Types::LambdaStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the::Aws::Lambda
function that was run by this step execution and a list of output parameters. -
#model ⇒ Types::ModelStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the model that was created by this step execution. -
#processing_job ⇒ Types::ProcessingJobStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the processing job that was run by this step execution. -
#quality_check ⇒ Types::QualityCheckStepMetadata
rw
The configurations and outcomes of the check step execution.
-
#register_model ⇒ Types::RegisterModelStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the model package that the model was registered to by this step execution. -
#training_job ⇒ Types::TrainingJobStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the training job that was run by this step execution. -
#transform_job ⇒ Types::TransformJobStepMetadata
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the transform job that was run by this step execution. -
#tuning_job ⇒ Types::TuningJobStepMetaData
rw
The Amazon
::Aws::SageMaker::Resource
Name (ARN) of the tuning job that was run by this step execution.
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Aws::Structure#to_h. |
Instance Attribute Details
#auto_ml_job ⇒ Types::AutoMLJobStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the AutoML job that was run by
this step.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#callback ⇒ Types::CallbackStepMetadata (rw)
The URL of the Amazon SQS queue used by this step execution, the pipeline generated token, and a list of output parameters.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#clarify_check ⇒ Types::ClarifyCheckStepMetadata (rw)
Container for the metadata for a Clarify check step. The configurations and outcomes of the check step execution. This includes:
The type of the check conducted,
The Amazon
::Aws::S3
URIs of baseline constraints and statistics files to be used for the drift check.The Amazon
::Aws::S3
URIs of newly calculated baseline constraints and statistics.The model package group name provided.
The Amazon
::Aws::S3
URI of the violation report if violations detected.The Amazon
::Aws::SageMaker::Resource
Name (ARN) of check processing job initiated by the step execution.The boolean flags indicating if the drift check is skipped.
If step property
BaselineUsedForDriftCheck
is set the same asCalculatedBaseline
.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#condition ⇒ Types::ConditionStepMetadata (rw)
The outcome of the condition evaluation that was run by this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#emr ⇒ Types::EMRStepMetadata (rw)
The configurations and outcomes of an Amazon EMR step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#fail ⇒ Types::FailStepMetadata (rw)
The configurations and outcomes of a Fail step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#lambda ⇒ Types::LambdaStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the ::Aws::Lambda
function that was run
by this step execution and a list of output parameters.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#model ⇒ Types::ModelStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the model that was created by this
step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#processing_job ⇒ Types::ProcessingJobStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the processing job that was run by
this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#quality_check ⇒ Types::QualityCheckStepMetadata (rw)
The configurations and outcomes of the check step execution. This includes:
The type of the check conducted.
The Amazon
::Aws::S3
URIs of baseline constraints and statistics files to be used for the drift check.The Amazon
::Aws::S3
URIs of newly calculated baseline constraints and statistics.The model package group name provided.
The Amazon
::Aws::S3
URI of the violation report if violations detected.The Amazon
::Aws::SageMaker::Resource
Name (ARN) of check processing job initiated by the step execution.The Boolean flags indicating if the drift check is skipped.
If step property
BaselineUsedForDriftCheck
is set the same asCalculatedBaseline
.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#register_model ⇒ Types::RegisterModelStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the model package that the model
was registered to by this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#training_job ⇒ Types::TrainingJobStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the training job that was run by
this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#transform_job ⇒ Types::TransformJobStepMetadata (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the transform job that was run by
this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end
#tuning_job ⇒ Types::TuningJobStepMetaData (rw)
The Amazon ::Aws::SageMaker::Resource
Name (ARN) of the tuning job that was run by
this step execution.
# File 'gems/aws-sdk-sagemaker/lib/aws-sdk-sagemaker/types.rb', line 32332
class PipelineExecutionStepMetadata < Struct.new( :training_job, :processing_job, :transform_job, :tuning_job, :model, :register_model, :condition, :callback, :lambda, :quality_check, :clarify_check, :emr, :fail, :auto_ml_job) SENSITIVE = [] include Aws::Structure end


Event Location:
University Center
4801 N Career Ave Avera Hall
Sioux Falls, South Dakota
Abstract:
Effective reporting is not simply the output of data, but the meaningful presentation of that data in a manner that informs the user. SQL Server Reporting Services provides a myriad of features to create a clear, instructive, and interactive experience. This session will demonstrate techniques to utilize SSRS advanced authoring features to facilitate more informative communication. These features include: nesting data regions, leveraging scope, geographic/geometric reporting, complex charting, rich formatting, incorporating managed code assemblies, intuitive drilldown, data from multiple datasets in a single data region, datasets that update source data, and more.
Speaker(s): Brian Larson,
Abstract:
Do you have many SQL instances in your enterprise? Do you have to maintain multiple dev/test/uat/pre-prod/prod environments? Need to spin up new instances often? Do you need a way to ensure these environments are all set up correctly and consistently and be notified of changes to them? If so, you need an enterprise-wide auditing system! I will be presenting my free system that does the following: 1) Collects information an all of your SQL instances daily, 2) sends you a report of any changes that have occurred (new/old/changed values), 3) lets you set up rules for all/some of servers and checks these rules on a daily basis (ie - backup compression should be turned on, Max memory should be less than 2TB, etc) and will even send you the SQL to fix any rules that failed.
Speaker(s): Nem Schlecht,
Abstract:
Want to off load some of that reporting workload, make an emergency rollback during a production upgrade faster, or make managing your test databases easier? If any of these appeal to you, then you should be familiar with database snapshots within SQL Server. Available since SQL Server 2005, use of this feature can make your life a lot easier.We'll spend the first part of this session taking an in depth look at how database snapshots work. We’ll look at what exactly is happening behind the scenes when you create a snapshot and when you query a snapshot. Once we've covered the basics, we'll spend the rest of our time analyzing and discussing a number of real world use cases where snapshots can be very beneficial and save you a great deal of time.
Speaker(s): Paul Timmerman,
Abstract:
Just because you can do it, does not mean that you should. There are several programming design patterns that work great in object orientated code that do not scale well inside of SQL Server. In this session we will focus some of these patterns and show you how to make them scale in the database engine. We will touch on Scalar-Value functions, Union, CTE, RBAR and more.
Speaker(s): William Wolf,
Abstract:
Microsoft has been busy working on the next version of SQL Server - SQL Server 2016. We will go over some of the new features at a high level and dig deeper on Row Level Security and StretchDB. Row Level Security allows you to add another layer of security to your environment. StretchDB will allow you to transparently place part or all of a table into a SQL Azure DB freeing up your valuable SAN space for data that is COLD.
Speaker(s): Rick Heiges,
Abstract:
Building software is hard, and we often find that fixing bugs is expensive if they are not caught early. Continuous Integration has proven to be a valuable technique in improving software quality by finding problems quickly and letting developers know immediately they have introduced a bug.This session demonstrates how you can implement CI for SQL Server databases, execute automated tests against your code and inform developers that they have caused a problem immediately.
Speaker(s): Steve Jones,
Abstract:
With the release of SQL Server 2012, we were introduced to two possible options when it came to Analysis Services. This ultimately presented a question…”Which one do I use SSAS multidimensional or SSAS tabular”? Determining whether multidimensional or tabular is the optimum solution for your organization is a key step when working with SQL Server Analysis Services 2012/2014. This session will introduce you to some of the common pitfalls with each solution and how you can avoid them. By the end of this session, you’ll have a clearer understanding of the strengths and weakness of each model and how your organization can optimally leverage the strengths of SSAS 2012/2014.
Speaker(s): Alan Faulkner,
Abstract:
Panel discussion on developing SQL Server skills featuring Steve Jones, Paul Timmerman, Bill Preachuk, Brian Larson, and Alan Faulkner. This panel will discuss how and why they became involved with PASS, some strategies for developing great presentations, and suggestions about how to advance your career. .
Speaker(s): Erin Dempster,
Abstract:
Your boss comes up to you and asks you why the system is slow, unless you know how your system is supposed to respond you are stuck scrambling to answer those questions. With a few free quires and some SSIS magic you can capture a Baseline of your systems. With this you will be able to know exactly where to look and what might be amiss. Before you can say what is wrong with your system you need to know how it reacts under normal circumstances. This session will provide the tools you need to start collection of your systems baselines and give you a great deal of information.
Speaker(s): Jim Dorame,
Abstract:
How does The Hortonworks Data Platform (HDP) and Microsoft HDInsight fit into our neat tidy database world? In this beginner-friendly technical session you'll learn about Big Data from the ground up with a focus on what SQL Server professionals need to know. Find out technical details about what HDFS, MapReduce and YARN actually are how they work. Discover the Hadoop ecosystem and the projects within. Learn how Hadoop complements the traditional relational database world. Discover real-world data tasks/use cases that Hadoop can accomplish.
Speaker(s): Bill Preachuk,
Abstract:
Presentation from Tegile.
Speaker(s): Erin Dempster,
Abstract:
Often in supporting SQL Server, we are asked to troubleshoot why a user or application cannot connect. It becomes more challenging when we find nothing is wrong with the way SQL Server is running. In this session we review common mistakes to the configuration of network settings. We’ll also show how to troubleshoot the SQL Server Browser. We’ll cover how to test for firewall issues. Finally we’ll discuss why SQL Server is blamed for dropping its connections.
Speaker(s): Mike Hays,
Abstract:
There's a lot of general verbiage and API documentation about Service Broker, but how do you fit the queues, services, contracts, and conversations together to actually make something that will work reliably in production? In this session you'll follow the architecture, design, implementation, and troubleshooting of a simple but production-tested Service Broker messaging framework and get a battlefield-level view of the pitfalls and the payoffs involved in Service Broker development.
Speaker(s): Matt Wigdahl,
This is a list of speakers from the XML Guidebook records. The details and URLs were valid at the time of the event.
I've been a Server Administrator and DBA for 20+ years and have worked with multiple operating systems (UNIX variants, Mac OS X and Windows) and database engines (MySQL/MariaDB, Oracle, PostgreSQL, SQLite, and MSSQL). I currently work a lot with PowerShell and automation as well as supervising a group of awesome systems administrators. I've worked for a large state university system, a start-up company, and everything in-between (including my own consulting company). I currently work for Border States Electric as an I.T. Supervisor.
LinkedIn: http://www.linkedin.com/in/erin-dempster-55967b6
Contact: https://www.endlessreporting.com
Erin currently serves as a SQL Developer II at Trean Corporation in Wayzata, Minnesota. With over 15 years of experience with SQL Server, as a developer and as an administrator, she has dabbled with most areas in the SQL Server realm. Areas of expertise include database design, query tuning and SQL Server Integration Services.
LinkedIn: http://www.linkedin.com/in/brianlarsonscs
Contact: http://sqlmag.com/author/brian-larson
Brian Larson is Chief Creative Officer/Partner at Superior Consulting Services and has presented at SQL Server Connections, PASS Summit, and the Microsoft BI Conference. As a consultant to Microsoft, Brian contributed to the original code base of Reporting Services. Brian is the author of “Microsoft SQL Server 2016 Reporting Services: 5th Edition” and “Delivering Business Intelligence with SQL Server 2016: 4th Edition”, as well as the forthcoming “Data Analysis with Microsoft Power BI.”
LinkedIn: http://www.linkedin.com/pub/bill-preachuk/1/a53/954
Bill Preachuk is employed by Hortonworks as a Hadoop Solutions Engineer. He is also a SQL Server MCTS with plenty of years spent in the SQL Server DBA/Developer/DW trenches. Bill has been in IT since 1991 and has presented at PASS Summit , multiple SQLSaturdays, and PASS/Hadoop/Analytics user group meetings in the Twin Cities, Wisconsin, Iowa, Winnipeg, and Ukraine. He also served 2 years on the Board of PASSMN - The Minnesota SQL Server User Group.
LinkedIn: https://www.linkedin.com/in/mike-hays-21097419
Contact: http://www.thesqlreport.com/
Mike has been working with Microsoft SQL Server for the last twenty years. Currently working as a Database Administrator for a diversified energy company, he has also worked in the retail, manufacturing, banking sectors. He holds a Master’s degree in Computer Information Science from Cleveland State University.
Contact: http://blogs.lessthandot.com/index.php/author/mndba/
Paul is a Microsoft SQL Server MVP and the Lead SQL Server DBA at Hennepin County Medical Center in Minneapolis, Minnesota. Paul has fifteen years of experience in database administration and currently the Chapter Leader of the Minnesota SQL Server User Group, PASSMN. Paul is an active member of the PASS community and routinely speaks at user group meetings and SQLSaturday conferences.
LinkedIn: http://www.linkedin.com/in/way0utwest
Contact: http://www.voiceofthedba.com/
Steve Jones is a Microsoft SQL Server MVP and has been working with SQL Server since version 4.2 on OS/2. After working as a DBA and developer for a variety of companies, Steve co-founded the community website SQLServerCentral.com in 2001. Since 2004, Steve has been the full-time editor of the site, ensuring it continues to be a great resource for SQL Server professionals. Over the last decade, Steve has written hundreds of articles about SQL Server for SQLServerCentral.com, SQL Server Standard magazine, SQL Server Magazine, and Database Journal.
LinkedIn: https://www.linkedin.com/in/jamesdorame
Contact: http://www.jamesdorame.com/
Jim Dorame has been working with SQL Server for over 20 years. Over those years he has learned a great deal from the SQL community. He has also given back to the community in the hopes that he may help someone in their career. He is always looking for something to learn and luckily Microsoft keeps adding to SQL Server.
LinkedIn: https://www.linkedin.com/in/williamjwolf
Contact: http://www.sqlwarewolf.com
Bill is the Manager of SQL Server Performance Tuning for RDX. He works with over 400 customers on solutions within the SQL Server environment and specialized in code tuning and mentoring the team within RDX. He has become a SQLSaturday veteran speaking at nearly 40 SQLSaturdays in the last 3 years. He has also spoken at Summit and is an Idera Ace class of 2018. Bill is active in the Pittsburgh SQL Server User Group. He is also the chapter lead for the DevOps Virtual User Group. He is passionate about educating users on SQL Server and mentoring others.
LinkedIn: http://www.linkedin.com/pub/alan-faulkner/31/b79/932/
Contact: http://falconteksolutionscentral.com/
I am an IT professional with over 20+ years of progressive technical experience with managing, consulting, software development, data integration architecture, data warehousing, and business intelligence development projects. The focus of my work is to work closely with stakeholders to develop architecture frameworks that align with organizational strategy, processes, and IT assets. Specializing in Business Intelligence (BI), Data Warehousing, database architecture, design and implementation.
LinkedIn: http://www.linkedin.com/in/erin-dempster-55967b6
Contact: https://www.endlessreporting.com
Erin currently serves as a SQL Developer II at Trean Corporation in Wayzata, Minnesota. With over 15 years of experience with SQL Server, as a developer and as an administrator, she has dabbled with most areas in the SQL Server realm. Areas of expertise include database design, query tuning and SQL Server Integration Services.
LinkedIn: https://www.linkedin.com/pub/matt-wigdahl/65/643/217
Contact: http://wigdahl.net
Matt Wigdahl is Director of Software Quality at ScriptPro LLC and a SQL Server MCP. He has configured, developed with, and optimized queries for SQL Server for over 15 years, on both sides of the developer / DBA line.
LinkedIn: http://www.linkedin.com/pub/rick-heiges/1/b93/777/
Contact: http://sqlblog.com/blogs/rick_heiges/default.aspx
Rick is a Former Data Platfrom MVP and Sr. Consultant for Microsoft where he focuses on working with customers on their data estate. His career includes work as a DBA, University full-time faculty member, Systems Analyst, Project Leader, and Developer. He has found his passion in working with data and the community. Rick served nine years on the PASS Board of Directors and spearheaded the popular 24 Hours of PASS event. He also started his local User Group in 2002.
The following is a list of sponsors that helped fund the event.


{% extends "base.html" %} {% block title %}About page{% endblock %} {% block content %}
If you want to get to the website, open any web application first before you type in cdspecollab.smcm.edu.
If you want to upload a CVS file to that website, please click on the upload botton.
This will lead you to a create page, which will ask you to type in a title for you CVS file, what it is run by, you must type in a description for your file and the chractor limit: 2000, protein concentration, curvette Pathlength, number of amino acids, you can choose make the CVS file visible to Students, or Visible to public. You need to click on choose file button in create page to add the CVS file.
Once you fill in all of the required info in the create page, you can then press summit button.
The website will create a place in the table view in the CD Spectroscopic Collaboration page.
If you want to multigraph a graph, you must select the graph that match it data info first before you click on the multigraph button.
If you want to create an account on the website click the Sign Up page in navagation bar.
You must enter you email first, then you must enter you own created password this account in sign up page after you finish filling al of the required info you can click on the sign up summit button.
You must go in your email and click on the varification link in order to verify your account.
If you want login with your varify account, you must click the Sign In page in the navagation bar.
Your login username will be the begin part of the email without email ending part.
You need to enter the verifyed password you created for your account on the website.
You can make the choice of allowing the website to remember your account if you like, this part is optional.
if you forget your account password for this website click on the forgot password? button at the bottom of the Sign In page. This will take to a password reset page where you can reset your account password.
Once you enter the password reset page, you need to enter the email address and press summit button that can reset you password.
You need to go to your email and click on the reset password link in order to change your account password.
There is an search bar in CD Spectroscopic Collaboration page.
You can go on the right side and on the top of the CD Spectroscopic Collaboration page on the table view and type that exact file name you have given it during the create page.
There is an previous button and next button for the table view at the bottom, so you see how many people put entries with CVS file.
{% endblock %}


Performs changes to a GenICam node map, tracks them and restores the previous state on destruction. More...
Public Member Functions | |
| PvGenStateStack (PvGenParameterArray *aParameters) | |
| Constructor. More... | |
| virtual | ~PvGenStateStack () |
| Destructor. | |
| PvResult | SetIntegerValue (const PvString &aName, int64_t aValue) |
| Changes the value of an integer parameter. More... | |
| PvResult | SetFloatValue (const PvString &aName, double aValue) |
| Changes the value of a float parameter. More... | |
| PvResult | SetEnumValue (const PvString &aName, const PvString &aValue) |
| Changes the value of an enum parameter. More... | |
| PvResult | SetEnumValue (const PvString &aName, int64_t aValue) |
| Changes the value of an enum parameter. More... | |
| PvResult | SetBooleanValue (const PvString &aName, bool aValue) |
| Changes the value of a boolean parameter. More... | |
| PvResult | SetStringValue (const PvString &aName, const PvString &aValue) |
| Changes the value of a string parameter. More... | |
Performs changes to a GenICam node map, tracks them and restores the previous state on destruction.
This class can be used to perform temporary changes to a GenICam node map. Every parameter changed through this class is tracked and its original value is saved. When the object is destroyed, the original value of all parameters is restored in the reverse order.
This class is very useful when dealing with selectors. If you want to change a selected value without affecting the current selector state of the node map, create an object of this type, change the selector(s) using the Set methods, perform your changes and let the object go out of scope: the selectors will go back to their original values.
Assume A is originally 1, B is 2, C is 3. If you use this class to change A 4, B to 5 and C to 6 (in that order) when the object goes out of scope C will be set back to 3, B to 2 and A to 1 (in that order as well).
If a value cannot be set (an error occurs) the previous value is not pushed on the stack of parameters that will be restored when the destructor is called.
If the parameter is already set to the requested value, its value IS NOT changed, and IS NOT pushed on the stack to be eventually restored. This is done to minimize traffic to the device and prevent too much invalidators to be fired when a selector is already set to the rigth value.
| PvGenStateStack::PvGenStateStack | ( | PvGenParameterArray * | aParameters | ) |
Constructor.
| [in] | aParameters | The GenICam parameter array to operate on. |
Changes the value of a boolean parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new value of the parameter. |
Changes the value of an enum parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new symbolic (string) value of the parameter. |
Changes the value of an enum parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new integer value of the parameter. |
Changes the value of a float parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new value of the parameter. |
Changes the value of an integer parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new value of the parameter. |
Changes the value of a string parameter.
| [in] | aName | The name of the parameter to change. |
| [in] | aValue | The new value of the parameter. |
Copyright (c) 2002-2015 Pleora Technologies Inc.
www.pleora.com


Juno <IP_ADDRESS> is a major update.
Core
- {@link oaj.BeanMap#get(Object)} and {@link oaj.BeanMap#put(String,Object)} now
automatically performs filtering if filters are defined on the bean property or bean property class.
- Deleted the following methods which are now unnecessary:
- BeanMap.getFiltered(String)
- BeanMap.putFiltered(String,Object)
- BeanMapEntry.getFiltered(String)
- BeanMapEntry.putFiltered(String,Object)
- BeanMapEntry.putFiltered(String,Object)
- BeanPropertyMeta.getFiltered()
- BeanPropertyMeta.setFiltered(Object)
- BeanPropertyMeta.getTransformedClassMeta()
- {@link oaj.BeanPropertyMeta#getClassMeta()} now returns the filtered type of the property.
StringVarResolver now has support for chained resolvers.
StringVarResolver now resolves variables inside resolved values.
i.e. if a resolved variable value itself contains a variable, it now resolves that variable too.
- Fixed bug where inner interface classes being used in
RestResource.filters() were being
interpreted as surrogate classes because they have hidden 1-arg constructors due to being inner classes.
- Fixed bug in {@link oaj.internal.MultiSet} where exception was being thrown if last set was empty.
- New
ZipFileListclass for providing efficiently zipped directories through the REST interface.
- New RdfProperties.RDF_useXmlNamespaces property.
- New
XmlParserContext.XML_preserveRootElement property.
- Worked around bug in Sun VM on OS/X where XML parser was throwing an exception when trying to set a reporter.
Server
- New
ZipFileListResponseHandlerclass.
- Simplified labels in servlet resource bundles:
- "[ClassName].ResourceDescription" is now "[ClassName].label".
- "[ClassName].MethodDescription.[methodName]" is now "[ClassName].[methodName]".
- Several changes to {@link oajr.RestRequest}:
- Added new methods:
RestRequest.getQueryParameterMap()
RestRequest.getQueryParameterNames()
RestRequest.getPathInfoUndecoded()
RestRequest.getPathRemainderUndecoded()
RestRequest.getTrimmedRequestURI()
RestRequest.getTrimmedRequestURL()
RestRequest.getServletTitle()
RestRequest.getServletDescription()
RestRequest.getMethodDescription()
- Behavior changes to {@link oajr.RestRequest#getPathInfo()} to follow Servlet specs.
Returns null instead of blank for no path info.
RestRequest.getPathRemainder()now automatically decodes the path remainder.
Use RestRequest.getPathRemainderUndecoded()to get the unencoded path remainder.
- Bug fixes in
RestRequest.getRequestParentURI()when servlet is mapped to "/*".
- Bug fixes in
RestRequest.getServletURI()when servlet is mapped to "/*".
- New string replacement variables:
- $R{contextPath} - Returns value from {@link oajr.RestRequest#getContextPath()}
- $R{methodDescription} - Returns value from
RestRequest.getMethodDescription()
- $R{resourceTitle} - Returns value from
RestRequest.getServletTitle()
- $R{resourceDescription} - Returns value from
RestRequest.getServletDescription()
- $R{trimmedRequestURI} - Returns value from
RestRequest.getTrimmedRequestURI()
- $E{var} - Environment variables.
- Added methods
RestServlet.getDescription(RestRequest)and RestServlet.getLabel(RestRequest).
BasicRestServlet and RestServletJenaDefault now provide default HTML titles
and descriptions:
@Property(name=HTMLDOC_title, value="$R{resourceTitle}"),
@Property(name=HTMLDOC_description, value="$R{resourceDescription}")
- Options pages on
BasicRestServlet and RestServletJenaDefault now provide default descriptions and back links:
and descriptions:
@Property(name=HTMLDOC_navlinks, value="{back:'$R{servletURI}"),
@Property(name=HTMLDOC_description, value="Resource options")
- New
BasicRestServletGroupclass.
- Removed RestServletProperties.REST_trimTrailingUriSlashes and RestServletProperties.REST_pathInfoBlankForNull.
- New annotations for providing labels and descriptions. Useful if you don't plan on having to support other languages, so you don't
want to provide labels in resource bundles.
RestResource.label()
@RestResource(description)
RestMethod.description() @RestMethod(description)
RestMethod.responses()
Attr.description()
Content.description()
HasParam.description()
HasQParam.description()
Header.description()
Param.description()
QParam.description()
- Support for sorting resources by name in
ChildResourceDescriptions.
Samples
- Added /tempDir/upload showing how to use ServletFileUpload with multipart form posts.


Home
Classification
Clustering
Deep Learning
Regression
ML Modeller
Classification
Algorithms
Decision Tree
Kernel SVM
K-Nearest Neighbour
Linear SVM
Logistic Regression
Naive Bayes
Random Forest


Daniel-Terhorst North defines,
The purpose of testing is to increase confidence for stakeholders through evidence.
When confronted with that definition, many people ask "what is meant by evidence and how do I produce that?"
There is a paper which offers a possible answer to what evidence is. The paper argues that a healthy dose of BDD thinking leads us to boil down the process of testing into identifying values which can then be managed using combinatorial testing, knowledge about business value and common sense. There is a 15-minute conference presentation of the paper here.
LeanTest.Net can help you with how to produce the evidence. Note that it can help you, it cannot produce the evidence for you since testing is inherently a human effort.
The idea is that you use your experience, your business stakeholder knowledge and your I-want-to-break-things super power to produce a test plan document. A test plan will contain a set of tables which outline relevant combinations and a test case name for each test case which you intend to implement.
You don't need LeanTest.Net to write tooling which ties test case tables to each test run, as you simply take output from each test run and merge it with test plan documents, then generate new documents with the combined information.
For example, with the test case table below (from the GitHub repo which accompanies the above mentioned paper), a tool could simply parse the Test case column, find e.g. the outcome of the PostOrderMustReportErrorWhenInvalidId
test method in a given test run, then present the combined information in a report. We may not have implementations of all four test cases at any given time during iterative development, but the tool can give us fast feedback on what we are still missing.
| Id | Price | Amount | Duration | Test case |
|---|---|---|---|---|
| ~Invalid | Valid | Valid | Valid | PostOrderMustReportErrorWhenInvalidId |
| Valid | ~Invalid | Valid | Valid | PostOrderMustReportErrorWhenInvalidPrice |
| Valid | Valid | ~Invalid | Valid | PostOrderMustReportErrorWhenInvalidAmount |
| Valid | Valid | Valid | ~Invalid | PostOrderMustReportErrorWhenInvalidDuration |
The attributes of LeanTest.Net provide a simple means to augment generated documents.
TestScenarioId
AttributeA test scenario is essentially a headline for a group of test cases.
If you define scenarios in a table in a test plan, you can assign a scenario to a test method. Tooling can then extract the information and e.g. group test cases under each scenario in a generated report. Here is an example of a scenario table,
| Scenario | Category | Comments | Scenario ID |
|---|---|---|---|
| Simple input parameter validation | InputValidation | Input | |
| Advanced input parameter validation | CoreFunctionality | AdvancedInput | |
| Mapping combinations of input parameters for QTE and Tbl | CoreFunctionality | Core |
Define scenarios with IDs in test plan(s), then put a reference to these on each test method by attributing with the TestScenarioId
Attribute, e.g. as,
using LeanTest.Attribute;
// ...
[TestMethod, TestScenarioId("Input")]
public void PostOrderMustReportErrorWhenInvalidId()
{
// ...
}
The scenario ID is supposed to be unique within a certain context, typically a single Git repository. It is recommended to use information bearing IDs such as generic Core
, Input
or specific references to areas of business functionality.
TestTag
AttributeWhen working incrementally, you will often find that you have decided on a set of test cases but you have not yet implemented the equivalent test methods.
It is a fair assumption that test tools will flag missing test methods as you are not there yet.
An explicit way to specify that test cases which have been agreed upon are not implemented yet can be documented in code with a placeholder test method with a test tag,
using LeanTest.Attribute;
using static LeanTest.Attribute.TestTagAttribute;
// ...
[TestMethod, TestScenarioId("Core"), TestTag(NotImplemented)]
public void PostOrderMustBuyWhenAssetIsTradable()
{
}
The above example is a special case of using the TestTag
attribute, giving it a pre-defined constant NotImplemented
. Test tooling could ensure that all test cases in test plans have equivalent test methods by generating such placeholder tests for what may be missing.
In general, you can pass any string to the attribute and then interpret it as you like in your tooling.
TestDescription
AttributeComments can be added to test cases using the TestDescription
attribute on test methods,
using LeanTest.Attribute;
// ...
[TestMethod, TestScenarioId("Core"), TestDescription("This will go into the comments column for this test in the test report.")]
public void PostOrderMustSellWhenAssetIsTradable()
{
// ...
}
The test tooling is supposed to put the description in a column in a test report, e.g. by adding or augmenting a Description column in test case tables found in source test plan documents.
The implementation of the attributes is quite simple and involves only writing easily recognizable texts and given arguments to standard output.
It is then assumed that a test runner will store these texts with test run output and that tools can read this information.
While conventional wisdom tells us that assumption is the evil mother of all mistakes, the above assumption is actually sensible if you use the MS Test (vstest.console
) test runner and then parse its XML output, a so-called .trx
-file.
LeanTest.Net provides implementations of the attributes for MS Test and Xunit tests. Test output can be generated and put in a file MyTrx.trx
using the following command,
vstest.console Orders.L0Tests.dll /logger:trx;LogFileName=MyTrx.trx /platform:x64
The output will contain information like the following,
<UnitTestResult testName="Orders.L0Tests.TestOrders.PostOrderMustReportErrorWhenInvalidId">
<Output>
<StdOut>TestScenarioId = ###---Input---###</StdOut>
</Output>
</UnitTestResult>
The schema of this file is defined in the file vstst.xsd
which is found in the Visual Studio installation folder.


About Us
How it Works
Breaking Stereotypes
Congratulations!
We hope that even though you got it right, some of your preconceived notions were challenged in this excercise.
Chat Now


@@include('./views/shared/loading.html') @@include('./views/shared/header.html') @@include('./views/pages/index/banner.html') @@include('./views/pages/index/content.html') @@include('./views/pages/index/specialization.html')


Links to gene information: NCBI Gene, Mouse Genome Informatics, FANTOM5 SSTAR
Links to genome browsers: UCSC Genome Browser, ZENBU Genome Browser
CRISPR gRNA candidates are sorted as high specificity (MIT) and high cutting efficiency (Doench/Fusi).
Recommend to use gRNA candidates with MIT > 50 and Doench/Fusi > 66%(55) as bold-highlighted below.
The details of each score are described at UCSC CRISPR/Cas9 track.
Guide sequence is linked to CRISPRdirect.
Recommend to select primers with higher Score and lower Penalty.
Score indicates primer specificity as described below.
| : 1 site for 0 mismatch, < 20 sites for 1 mismatch, and < 100 sites for 2 mismatches | |
| : 1 site for 0 mismatch, < 20 sites for 1 mismatch, but > 100 sites for 2 mismatches | |
| : 1 site for 0 mismatch, but > 20 sites for 1 mismatch, > 100 sites for 2 mismatches | |
| : Check GGGenome to count off-target sites and carefully use the primers |
Penalty indicates general primer quality. The lower, the better. Details are described at Primer3 manual.
Primer sequence is linked to GGGenome.
Color annotations: frameshift codon, premature termination codon (PTC), last exon
Aberrant mRNAs will be degraded by NMD when PTC is more than 50-55 nt upstream of the last exon junction. (ref)
*NMD: nonsense-mediated mRNA decayNo CDS is displayed when gRNAs deletes all CDS or first exon or last exon or second to the last exon.


Package com.arjuna.mw.wst11
Class UserTransaction
- java.lang.Object
-
- com.arjuna.mw.wst11.UserTransaction
-
public abstract class UserTransaction extends java.lang.Object
This is the interface that allows transactions to be started and terminated. The messaging layer converts the Commit, Rollback and Notify messages into calls on this. Importantly, a UserTransaction does not represent a specific transaction, but rather is responsible for providing access to an implicit per-thread transaction context; it is similar to the UserTransaction in the JTA specification. Therefore, all of the UserTransaction methods implicitly act on the current thread of control.- Since:
- XTS 1.0.
- Version:
- $Id: UserTransaction.java,v <IP_ADDRESS> 2005/11/22 10:36:05 kconner Exp $
- Author:
- Mark Little<EMAIL_ADDRESS>-
-
Constructor Summary
Constructors Constructor Description UserTransaction()
-
Method Summary
All Methods Static Methods Instance Methods Abstract Methods Concrete Methods Modifier and Type Method Description abstract void
begin()
Start a new transaction.abstract void
begin(int timeout)
Start a new transaction with the specified timeout as its lifetime.abstract void
commit()
The transaction is committed by the commit method.abstract int
getTimeout()
Returning timeout of the transaction as it was defined when it begun.abstract UserTransaction
getUserSubordinateTransaction()
get the user subordinate transaction this is a UserTransaction whose begin method will create an interposed AT transactionstatic UserTransaction
getUserTransaction()
Get the user transaction.abstract void
rollback()
The rollback operation will terminate the transaction and return normally if it succeeded, while throwing an appropriate exception if it didn't.static void
setUserTransaction(UserTransaction userTransaction)
Set the user transaction.abstract java.lang.String
transactionIdentifier()
-
-
-
Method Detail
-
getUserTransaction
public static UserTransaction getUserTransaction()
Get the user transaction.- Returns:
- the user transaction.
-
setUserTransaction
public static void setUserTransaction(UserTransaction userTransaction)
Set the user transaction.- Parameters:
userTransaction
- The user transaction.
-
getUserSubordinateTransaction
public abstract UserTransaction getUserSubordinateTransaction()
get the user subordinate transaction this is a UserTransaction whose begin method will create an interposed AT transaction
-
begin
public abstract void begin() throws WrongStateException, SystemException
Start a new transaction. If one is already associated with this thread then the WrongStateException will be thrown. Upon success, this operation associates the newly created transaction with the current thread.- Throws:
WrongStateException
SystemException
-
begin
public abstract void begin(int timeout) throws WrongStateException, SystemException
Start a new transaction with the specified timeout as its lifetime. If one is already associated with this thread then the WrongStateException will be thrown.- Throws:
WrongStateException
SystemException
-
commit
public abstract void commit() throws TransactionRolledBackException, UnknownTransactionException, java.lang.SecurityException, SystemException, WrongStateException
The transaction is committed by the commit method. This will execute the PhaseZero, 2PC and OutcomeNotification protocols prior to returning. If there is no transaction associated with the invoking thread then WrongStateException is thrown. If the coordinator is not aware of the current transaction UnknownTransactionException is thrown. If the transaction ultimately rolls back then the TransactionRolledBackException is thrown. If any other error occurs a SystemException is thrown. When complete, this operation disassociates the transaction from the current thread such that it becomes associated with no transaction.- Throws:
TransactionRolledBackException
UnknownTransactionException
java.lang.SecurityException
SystemException
WrongStateException
-
rollback
public abstract void rollback() throws UnknownTransactionException, java.lang.SecurityException, SystemException, WrongStateException
The rollback operation will terminate the transaction and return normally if it succeeded, while throwing an appropriate exception if it didn't. If there is no transaction associated with the invoking thread then WrongStateException is thrown. If the coordinator is not aware of the current transaction UnknownTransactionException is thrown. If any other error occurs a SystemException is thrown. When complete, this operation disassociates the transaction from the current thread such that it becomes associated with no transaction.- Throws:
UnknownTransactionException
java.lang.SecurityException
SystemException
WrongStateException
-
transactionIdentifier
public abstract java.lang.String transactionIdentifier()
-
getTimeout
public abstract int getTimeout()
Returning timeout of the transaction as it was defined when it begun.
-
-


Params
- type of input parameters used by the asynchronous task (consumed
by perform(Object[])
),
or Void
if no inputs will be
used.
Progress
- type of individual values provided by the asynchronous task
for progress
updates (consumed by onProgressUpdate(Object[])
),
or (usually) Void
if no
progress updates will be made.
Intermediate
- type of result data produced by the basic background
processing of the
asynchronous task (returned by perform(Object[])
and consumed by BaseFluentAsyncTask.Transformer.transform(Object)
,
or (usually) Void
if the background
processing is not
intended to return a result.
Result
- type of result data produced by the transform processing of the
asynchronous task
(returned by BaseFluentAsyncTask.Transformer.transform(Object)
and consumed by onPostExecute(Object)
and onCancelled(Object)
,
or (usually) Void
if the background
processing is not
intended to return a result.
public class BaseFluentAsyncTask<Params,Progress,Intermediate,Result> extends AsyncTask<Params,Progress,Result>
AsyncTask
.
One aim of this approach is to encourage implementation of AsyncTask
subclasses that
are loosely coupled with consumer logic, and easily reused. For
example, if multiple activities or fragments need to perform a similar database
operation, but
with slight differences in UI updates and other post-processing logic, the general
operation can
be implemented in a single subclass of BaseFluentAsyncTask
,
with variations specified via
lambdas in fluent invocations of setTransformer(Transformer)
,
setProgressListener(ProgressListener)
,
and (possibly) setFailureListener(ResultListener)
.
For a simple AsyncTask
implementation,
with a single point of
consumption, an instance of this class can be created and used, specifying all key
lifecycle
logic via individual lambdas or anonymous classes.
Note that this class overrides AsyncTask.doInBackground(Object[])
,
splitting background processing into 2 phases: performance and transformation (the
latter need
not transform the values returned from the former; instead, it might simply be
additional
background processing that differs between the different consumers). The first phase
produces an
intermediate value; the second takes the intermediate value, performs some additional
processing,
and produces a result. Simple extensions or uses of BaseFluentAsyncTask
will generally
only need to implement the performance phase—either by overriding perform(Params...)
,
or by specifying a lambda or instance of an anonymous class in an invocation
of setPerformer(Performer)
.
Important: If the Intermediate
and Result
types
specified for an instance of this class (or a subclass) are different, then setTransformer(Transformer)
must be invoked to configure a mapping object
between values of those 2 types; otherwise, a ClassCastException
is
likely to be thrown.
| Modifier and Type | Class and Description |
|---|---|
static interface |
BaseFluentAsyncTask.Performer<Params,Intermediate>
Declares a
BaseFluentAsyncTask.Performer.perform(Object[])
method that can be implemented to perform basic
background processing in an instance of BaseFluentAsyncTask .
|
static interface |
BaseFluentAsyncTask.ProgressListener<Progress>
Declares an
BaseFluentAsyncTask.ProgressListener.update(Object[])
method that can be implemented to provide UI updates (for
example) while a background task is ongoing.
|
static interface |
BaseFluentAsyncTask.ResultListener<Result>
Declares a
BaseFluentAsyncTask.ResultListener.handle(Object)
method that can be implemented to perform additional
processing on the UI thread following completion of background processing.
|
static class |
BaseFluentAsyncTask.TaskException
Thrown by background task methods (
perform(Object[]) ,
BaseFluentAsyncTask.Performer.perform(Object[]) ,
and BaseFluentAsyncTask.Transformer.transform(Object) )
to indicate
unsuccessful (but not necessarily problematic) completion of background
processing.
|
static interface |
BaseFluentAsyncTask.Transformer<Intermediate,Result>
Declares a
BaseFluentAsyncTask.Transformer.transform(Object)
method that can be implemented to perform additional
background processing following successful completion of the perform(Object[])
method.
|
AsyncTask.Status
SERIAL_EXECUTOR, THREAD_POOL_EXECUTOR
| Constructor and Description |
|---|
BaseFluentAsyncTask()
|
| Modifier and Type | Method and Description |
|---|---|
protected Result |
doInBackground(Params... params)
Implements the
abstract AsyncTask.doInBackground(Object[])
to divide
background processing into 2 components: performance and transformation.
|
protected void |
onCancelled(Result result)
Invokes
BaseFluentAsyncTask.ResultListener.handle(Object)
to perform any UI thread-based post-processing
after unsuccessful completion of background processing.
|
protected void |
onPostExecute(Result result)
Invokes
BaseFluentAsyncTask.ResultListener.handle(Object)
to perform any UI thread-based post-processing
after successful completion of background processing.
|
protected void |
onProgressUpdate(Progress... values)
Invokes
BaseFluentAsyncTask.ProgressListener.update(Object[]) ,
presumably to update the UI to display the
progress/status of the background processing.
|
protected Intermediate |
perform(Params... params)
Executes basic processing of asynchronous task.
|
BaseFluentAsyncTask<Params,Progress,Intermediate,Result> |
setFailureListener(BaseFluentAsyncTask.ResultListener<Result> listener)
Specifies the
BaseFluentAsyncTask.ResultListener
implementation instance (usually a lambda) to be used for
additional UI thread processing following unsuccessful completion of backgrounnd
processing.
|
BaseFluentAsyncTask<Params,Progress,Intermediate,Result> |
setPerformer(BaseFluentAsyncTask.Performer<Params,Intermediate> performer)
Specifies the
BaseFluentAsyncTask.Performer
implementation instance (usually a lambda) to be used for basic
background processing.
|
BaseFluentAsyncTask<Params,Progress,Intermediate,Result> |
setProgressListener(BaseFluentAsyncTask.ProgressListener<Progress> listener)
Specifies the
BaseFluentAsyncTask.ProgressListener
implementation instance (usually a lambda) to be used
for progress updating on the UI thread.
|
BaseFluentAsyncTask<Params,Progress,Intermediate,Result> |
setSuccessListener(BaseFluentAsyncTask.ResultListener<Result> listener)
Specifies the
BaseFluentAsyncTask.ResultListener
implementation instance (usually a lambda) to be used for
additional UI thread processing following successful completion of backgrounnd
processing.
|
BaseFluentAsyncTask<Params,Progress,Intermediate,Result> |
setTransformer(BaseFluentAsyncTask.Transformer<Intermediate,Result> transformer)
Specifies the
BaseFluentAsyncTask.Transformer
implementation instance (usually a lambda) to be used for
additional background processing.
|
cancel, execute, execute, executeOnExecutor, get, get, getStatus, isCancelled, onCancelled, onPreExecute, publishProgress
@Nullable protected Intermediate perform(Params... params) throws BaseFluentAsyncTask.TaskException
setProgressListener(ProgressListener)
,
setSuccessListener(ResultListener)
,
and
setFailureListener(ResultListener)
.
params
- input arguments to background processing.BaseFluentAsyncTask.TaskException
- to indicate that AsyncTask.cancel(boolean)
should be invoked, resulting in
the eventual invocation of onCancelled(Object)
,
and consequently, the lambda or BaseFluentAsyncTask.ResultListener
implementation specified to setFailureListener(ResultListener)
.
@Nullable protected Result doInBackground(Params... params)
abstract
AsyncTask.doInBackground(Object[])
to divide
background processing into 2 components: performance and transformation. If the
performance
phase (implemented in perform(Object[])
throws a BaseFluentAsyncTask.TaskException
,
the
transformation phase (specified in setTransformer(Transformer)
)
will not be executed.
Any value (including null
returned by perform(Object[])
will be passed in
the invocation to BaseFluentAsyncTask.Transformer.transform(Object)
.
As a rule, subclasses of BaseFluentAsyncTask
should not override
this method, but should instead override perform(Object[])
,
or provide a lambda or
BaseFluentAsyncTask.Performer
implementation to setPerformer(Performer)
.
doInBackground
in
class AsyncTask<Params,Progress,Result>
params
- input arguments to background processing.protected void onProgressUpdate(Progress... values)
BaseFluentAsyncTask.ProgressListener.update(Object[])
,
presumably to update the UI to display the
progress/status of the background processing. Rather than overriding this method,
the setProgressListener(ProgressListener)
method should be invoked on instances of this class or
a subclass.
onProgressUpdate
in
class AsyncTask<Params,Progress,Result>
values
- progressprotected void onPostExecute(@Nullable Result result)
BaseFluentAsyncTask.ResultListener.handle(Object)
to perform any UI thread-based post-processing
after successful completion of background processing. Rather than overriding this
method, the
setSuccessListener(ResultListener)
method should generally be invoked on instances of
this class or a subclass.
onPostExecute
in
class AsyncTask<Params,Progress,Result>
result
- background processing results.protected void onCancelled(@Nullable Result result)
BaseFluentAsyncTask.ResultListener.handle(Object)
to perform any UI thread-based post-processing
after unsuccessful completion of background processing. Rather than overriding
this method, the
setFailureListener(ResultListener)
method should generally be invoked on instances of
this class or a subclass.
onCancelled
in class AsyncTask<Params,Progress,Result>
result
- background processing results.public BaseFluentAsyncTask<Params,Progress,Intermediate,Result> setPerformer(BaseFluentAsyncTask.Performer<Params,Intermediate> performer)
BaseFluentAsyncTask.Performer
implementation instance (usually a lambda) to be used for basic
background processing. Consumer code may invoke this method directly on an
instance of this
class, or override perform(Object[])
in a subclass. In either case, BaseFluentAsyncTask.TaskException
may be thrown to signal unsuccessful completion (aka failure) of the background
processing.
performer
- BaseFluentAsyncTask.Performer
callback object or lambda.
public BaseFluentAsyncTask<Params,Progress,Intermediate,Result> setProgressListener(BaseFluentAsyncTask.ProgressListener<Progress> listener)
BaseFluentAsyncTask.ProgressListener
implementation instance (usually a lambda) to be used
for progress updating on the UI thread.
listener
- BaseFluentAsyncTask.ProgressListener
callback object or lambda.
public BaseFluentAsyncTask<Params,Progress,Intermediate,Result> setTransformer(BaseFluentAsyncTask.Transformer<Intermediate,Result> transformer)
BaseFluentAsyncTask.Transformer
implementation instance (usually a lambda) to be used for
additional background processing.
transformer
- BaseFluentAsyncTask.Transformer
callback object or lambda.
public BaseFluentAsyncTask<Params,Progress,Intermediate,Result> setSuccessListener(BaseFluentAsyncTask.ResultListener<Result> listener)
BaseFluentAsyncTask.ResultListener
implementation instance (usually a lambda) to be used for
additional UI thread processing following successful completion of backgrounnd
processing.
listener
- BaseFluentAsyncTask.ResultListener
callback object or lambda.
public BaseFluentAsyncTask<Params,Progress,Intermediate,Result> setFailureListener(BaseFluentAsyncTask.ResultListener<Result> listener)
BaseFluentAsyncTask.ResultListener
implementation instance (usually a lambda) to be used for
additional UI thread processing following unsuccessful completion of backgrounnd
processing.
listener
- BaseFluentAsyncTask.ResultListener
callback object or lambda.


- // Starting a range; if the edge is contained or not depends on the xor of this particular value.
+ // Start a range if one set contains but not the other.
- let startInclusive =self.contains(i) != other.contains(i)
+ ifself.contains(i) != other.contains(i) {
- start = startInclusive ? i : i +1
+ flag =true
- flag =true
+ start = i
+ }
} else {
} else {
- // Ending a range; if the edge is contained or not depends on the xor of this particular value.
+ // End a range if both sets contain or both sets do not contain.
- let endInclusive =self.contains(i) != other.contains(i)
+ ifself.contains(i) == other.contains(i) {
- let end = endInclusive ? i +1: i
+ flag =false
- if start < end {
+ result.insert(integersIn: start..<i)
- // Otherwise, we had an empty range
- result.insert(integersIn: start..<end)
}
}
- flag =false
}
}
- // We never have to worry about having flag set to false after exiting this loop because the iterator will always return an even number of results; ranges come in pairs, and we always alternate flag
+ // We never have to worry about having flag set to false after exiting this loop because the last boundary is guaranteed to be past the end of ranges in both index sets


So it's time to choose the first lucky one to begin with. He/she will be selected amongst the top three people of this leaderboard as of March 10th, 2013, after an interview by the selection committee composed of the top #open25 contributors. He/she will have his/her flight paid to go to his dream university for a week opening the best classes of the world through UniShared. Let's get started!


--- title: Express & Webpack - The ultimate guide layout: homepage ---
A guide to the full potential of webpack inside an Express-driven website.
The protagonists of the book are Express and Webpack. The book contains 7 chapters that will guide you through the process of setting up an ExpressJS app and properly implement a Webpack 4 build-flow supporting hmr for both client and server.


|
KratosMultiphysics
KRATOS Multiphysics (Kratos) is a framework for building parallel, multi-disciplinary simulation software, aiming at modularity, extensibility, and high performance. Kratos is written in C++, and counts with an extensive Python interface.
|
Classes | |
| class | TestLoader |
| class | TestCase |
| class | KratosTextTestResult |
| class | WorkFolderScope |
| Helper-class to execute test in a specific target path. More... | |
Functions | |
| def | skipIfApplicationsNotAvailable (*application_names) |
| Skips the test if required applications are not available. More... | |
| def | SupressConsoleOutput () |
| def | SupressConsoleError () |
| def | SupressAllConsole () |
| def | main () |
| def | runTests (tests) |
| def | isclose (a, b, rel_tol=1e-09, abs_tol=0.0) |
| Same implementation as math.isclose self-implemented bcs math.isclose was only introduced in python3.5 see https://www.python.org/dev/peps/pep-0485/. More... | |
Variables | |
| dictionary | test_timing_results = {} |
| dictionary | KratosSuites |
| def KratosUnittest.isclose | ( | a, | |
| b, | |||
rel_tol = 1e-09 , |
|||
abs_tol = 0.0 |
|||
| ) |
Same implementation as math.isclose self-implemented bcs math.isclose was only introduced in python3.5 see https://www.python.org/dev/peps/pep-0485/.
| def KratosUnittest.main | ( | ) |
| def KratosUnittest.runTests | ( | tests | ) |
| def KratosUnittest.skipIfApplicationsNotAvailable | ( | * | application_names | ) |
Skips the test if required applications are not available.
| def KratosUnittest.SupressAllConsole | ( | ) |
| def KratosUnittest.SupressConsoleError | ( | ) |
| def KratosUnittest.SupressConsoleOutput | ( | ) |
| dictionary KratosUnittest.KratosSuites |
| dictionary KratosUnittest.test_timing_results = {} |