Update: I'm a visting student from Sep, 2018 to Sep, 2019 in the VILab of the University of California, Merced, working with Prof. Ming-Hsuan Yang.
About Me
Hi, I'm Yabei Li. I received my B.S. degree in electrical engineer from Hefei University of Technology, Hefei, China, in 2014. I'm currently working toward the Ph.D. degree in the Center for Research on Intelligent Perception and Computing (CRIPAC), Institute of Automation Chinese Academy of Sciences (CASIA), Beijing, China. My research interests include 2D/3D scene understanding, multi-modal learning, deep learning.
Update: I'm a visting student from Sep, 2018 to Sep, 2019 in the VILab of the University of California, Merced, working with Prof. Ming-Hsuan Yang.
Update: I'm a visting student from Sep, 2018 to Sep, 2019 in the VILab of the University of California, Merced, working with Prof. Ming-Hsuan Yang.


Command Line¶
addgroupnamealias
¶
This command creates secondary name(s) for group names. Once an alias is created the group name cannot be used to request HTTP playback of that stream. Once an alias is used (requested by a client) the alias is removed. Aliases are designed to be used to protect/hide your source streams.
Arguments:
groupName
The original group name.aliasName
The alias alternative to the group name.
Example:
./manage.py addgroupnamealias MyGroup TestGroupAlias
addstreamalias
¶
Allows you to create secondary name(s) for internal streams. Once an alias is created the localstreamname cannot be used to request playback of that stream. Once an alias is used (requested by a client) the alias is removed. Aliases are designed to be used to protect/hide your source streams.
Arguments:
localStreamName
The original stream name.aliasName
The alias alternative to thelocalStreamName
.
Example:
./manage.py addstreamalias bunny video1 --expire-period=-300
createhlsstream
¶
Create an HTTP Live Stream (HLS) out of an existing H.264/AAC stream.
Arguments:
localStreamNames
The stream(s) that will be used as the input. This is a comma-delimited list of active stream names (local stream names).targetFolder
The folder where all the .ts/.m3u8 files will be stored. This folder must be accessible by the HLS clients. It is usually in the web-root of the server.
Optional:
--keep-alive
If true, the EMS will attempt to reconnect to the stream source if the connection is severed.--overwrite-destination
If true, it will force overwrite of destination files.--stale-retention-count
The number of old files kept besides the ones listed in the current version of the playlist (only rolling playlist).--create-master-playlist
If true, a master playlist will be created.--cleanup-destination
If true, all *.ts and *.m3u8 files in the target folder will be removed before HLS creation is started.--bandwidths
The corresponding bandwidths for each stream listed in localStreamNames. Again, this can be a comma-delimited list.--groupName
The name assigned to the HLS stream or group.--playlist-type
--playlist-length
The length (number of elements) of the playlist (only rolling playlist).--playlist-name
The file name of the playlist (*.m3u8).--chunk-length
The length (in seconds) of each playlist element (*.ts file). Minimum value is 1 (second).--max-chunk-length
Maximum length (in seconds) the EMS will allow any single chunk to be.--chunk-base-name
The base name used to generate the *.ts chunks.--chunk-on-idr
If true, chunking is performed ONLY on IDR. Otherwise, chunking is performed whenever chunk length is achieved.--drm-type
Type of DRM encryption to use.--aes-key-count
Number of keys that will be automatically generated and rotated over while encrypting this HLS stream.--audio-only
If true, stream will be audio only.--hls-resume
If true, HLS will resume in appending segments to previously created child playlist even in cases of EMS shutdown or cut off stream source.--cleanup-on-close
If true, corresponding hls files to a stream will be deleted if the said stream is removed or shut down or disconnected.--use-byte-range
If true, will use the EXT-X-BYTERANGE feature of HLS (version 4 and up).--file-length
When using useByteRange=1, this parameter needs to be set too. This will be the size of file before chunking it to another file, this replace the chunkLength in case of EXT-X-BYTERANGE, since chunkLength will be the byte range chunk.--use-system-time
If true, uses UTC in playlist time stamp otherwise will use the local server time.--offset-time
A parameter valid only for HLS v.6 onwards. This will indicate the start offset time (in seconds) for the playback of the playlist.
Example
./manage.py createhlsstream hlstest /MyWebRoot/ --bandwidths=128 --group-name=hls --playlist-type=rolling --playlist-length=10 --chunk-length=5
create_hds_stream
¶
Create an HDS (HTTP Dynamic Streaming) stream out of an existing H.264/AAC stream.
Arguments:
localStreamNames
The stream(s) that will be used as the input. This is a comma-delimited list of active stream names (local stream names).targetFolder
The folder where all the manifest (.f4m) and fragment (f4v) files will be stored. This folder must be accessible by the HDS clients. It is usually in the web-root of the server.
Optional:
--bandwidths
The corresponding bandwidths for each stream listed inlocalStreamNames
. Again, this can be a comma-delimited list.--chunk-base-name
The base name used to generate the fragments.--chunk-length
The length (in seconds) of fragments to be made. Minimum value is 1 (second).--chunk-on-idr
If true, chunking is performed ONLY on IDR. Otherwise, chunking is performed whenever chunk length is achieved.--group-name
The name assigned to the HDS stream or group.--keep-alive
If true, the EMS will attempt to reconnect to the stream source if the connection is severed.--manifest-name
The manifest file name.--overwrite-destination
If true, it will allow overwrite of destination files.--playlist-type
Either appending or rolling.--playlist-length
The number of fragments before the server starts to overwrite the older fragments. Used only when--playlist-type
is rolling. Ignored otherwise.--stale-retention-count
The number of old files kept besides the ones listed in the current version of the playlist. Only applicable for rolling playlists.--create-master-playlist
If true, a master playlist will be created.--cleanup-destination
If true, all manifest and fragment files in the target folder will be removed before HDS creation is started.
createingestpoint
¶
Creates an RTMP ingest point.
Arguments:
privateStreamName
The name that RTMP Target Stream Names must match.publicStreamName
The name that is used to access the stream pushed to theprivateStreamName
. ThepublicStreamName
becomes the streamslocalStreamName
.
Example:
./manage.py createingestpoint theIngestPoint useMeToViewStream
flushgroupnamealiases
¶
Invalidates all group name aliases.
Example:
./manage.py flushgroupnamealiases
getconfiginfo
¶
Returns the information of the stream by the configId.
Arguments:
configId
TheconfigId
of the configuration to get some information.
Example
./manage.py getconfiginfo 1
getgroupnamebyalias
¶
Returns the group name given the alias name.
Arguments:
aliasName
The group alias name.
Example
./manage.py getgroupnamebyalias TestGroupAlias
getstreaminfo
¶
Returns a detailed set of information about a stream.
Arguments:
idOrLocalStreamName
The uniqueId of the stream or the name of the stream.
Example
./manage.py getstreaminfo 1
./manage.py getstreaminfo streamname
isstreamrunning
¶
Checks a specific stream if it is running or not.
Arguments:
idOrLocalStreamName
The uniqueId of the stream or the name of the stream.
Example
./manage.py isstreamrunning 1
./manage.py isstreamrunning testStream
listgroupnamealiases
¶
Returns a complete list of group name aliases.
Example
./manage.py listgroupnamealiases
listhttpstreamingsessions
¶
Lists all currently active HTTP streaming sessions.
Example
./manage.py listhttpstreamingsessions
liststreams
¶
Provides a detailed description of all active streams.
Parameters:
--disable-internal-streams
Filtering out internal streams from the list.
Example
./manage.py liststreams --disable-internal-streams=1
pullstream
¶
Pull in a stream from an external source.
Arguments:
uri
The URI of the external stream. Can be RTMP, RTSP or unicast/multicast (d) mpegts
Parameters:
--keep-alive
If keepAlive is set to 1, the server will attempt to reestablish connection with a stream source after a connection has been lost. The reconnect will be attempted once every second.--local-stream-name
Name of the stream. Otherwise, a fallback techniques used to determine the stream name (based on the URI).--force-tcp
If 1 and if the stream is RTSP, a TCP connection will be forced. Otherwise the transport mechanism will be negotiated (UDP or TCP).--tc-url
TC URL to use in the initial RTMP connect invoke.--page-url
Originating web page address to use in the initial RTMP connect invoke.--swf-url
Originating swf URL to use in the initial RTMP connect invoke.--range-start
A value from which the playback should start expressed in seconds (RTSP and RTMP connections only).--range-end
The length in seconds for the playback (RTSP and RTMP connections only).--ttl
Sets the IP_TTL (time to live) option on the socket.--tos
Sets the IP_TOS (Type of Service) option on the socket.--rtcp-detection-interval
How much time (in seconds) should the server wait for RTCP packets before declaring the RTSP stream as a RTCP-less stream.--emulate-user-agent
User agent string (only for RTMP).--is-audio
If 1 and if the stream is RTP, it indicates that the currently pulled stream is an audio source. Otherwise the pulled source is assumed as a video source.--audio-codec-bytes
The audio codec setup of RTP stream if it is audio. Represented as hex format without “0x” or “h”.--sps-bytes
The video SPS bytes of RTP stream if it is video. It should be base 64 encoded.--pps-bytes
The video PPS bytes of RTP stream if it is video. It should be base 64 encoded.--ssm-ip
The source IP from source-specific-multicast (only UDP based pull).--http-proxy
IP:Port - specifies an RTSP HTTP Proxy from which the RTSP stream should be pulled; “self” - pulling RTSP over HTTP.
Example
./manage.py pullstream "rtmp://s2pchzxmtymn2k.cloudfront.net/cfx/st/mp4:sintel.mp4" --local-stream-name=testpullstream
pushstream
¶
Try to push a local stream to an external destination. The pushed stream can only use the RTMP, RTSP or MPEG-TS unicast/multicast protocol.
Arguments:
uri
The URI of the external stream. Can be RTMP, RTSP or unicast/multicast (d) mpegts.
Parameters:
--keep-alive
If keepAlive is set to 1, the server will attempt to reestablish connection with a stream source after a connection has been lost. The reconnect will be attempted once every second.--local-stream-name
Name of the stream. Otherwise, a fallback techniques used to determine the stream name (based on the URI).--ratget-stream-name
It can be one of following: live, record, append. It is meaningful only for RTMP.--tc-url
TC URL to use in the initial RTMP connect invoke.--page-url
Originating web page address to use in the initial RTMP connect invoke.--swf-url
Originating swf URL to use in the initial RTMP connect invoke.--ttl
Sets the IP_TTL (time to live) option on the socket.--tos
Sets the IP_TOS (Type of Service) option on the socket.--emulate-user-agent
User agent string (only for RTMP).--rtmp-absolute-timestamps
Forces the timestamps to be absolute when using RTMP.--send-chunk-size-request
Sets whether the RTMP stream will or will not send a “Set Chunk Length” message. This is significant when pushing to Akamai’s new RTMP HD ingest point where this parameter should be set to 0 so that Akamai will not drop the connection.--use-source-pts
When value is true, timestamps on source inbound RTMP stream are passed directly to the outbound (pushed) RTMP streams. This affects only pushed Outbound Net RTMP with net RTMP source. This parameter overrides the value of theconfig.lua
option of the same name.
Example
./manage.py pushstream "rtmp://DestinationAddress/live" --local-stream-name=testpullstream --target-stream-name=testpushStream
removeconfig
¶
Stop the stream and remove the corresponding configuration entry.
Arguments:
idOrGroupName
TheconfigId
of the configuration that needs to be removed or the name of the group that needs to be removed.
Example
./manage.py removeconfig 555
removegroupnamealias
¶
Removes an alias of a group.
Arguments:
aliasName
The alias alternative to be removed from the group name.
Example
./manage.py removegroupnamealias TestGroupAlias
removeingestpoint
¶
Removes an RTMP ingest point.
Arguments:
privateStreamName
The Ingest Point is identified by theprivateStreamName
, so only that is required to delete it.
Example
./manage.py removeingestpoint theIngestPoint
removestreamalias
¶
Removes an alias of a stream.
Arguments:
aliasName
The alias to delete.
Example
./manage.py removestreamalias video1
shutdownstream
¶
Terminates a specific stream. When permanently=1
is used, this command is analogous to removeConfig
.
Arguments:
idOrLocalStreamName
The uniqueId of the stream or the name of the inbound stream that needs to be terminated.
Example
./manage.py shutdownstream 55


You can still settle the claim out of court. For example, you could offer to repair goods you sold the claimant or suggest a payment.
If the claimant accepts your offer you can avoid getting a County Court Judgment and the claim can be settled.


Mornitoring
System List
(current)
Java Process
Target System List
Target Site
Search
No.
Target Site
Transaction ID
Register Date
Register Time
Change Date
Change Time
Target Site
New
Register
Modify
Delete


PWG July, 2007
F2F
Meeting
WHEN:
Monday, 09 July
2007 -- PWG (hosted by Microsoft)
Tuesday, 10 July
2007 -- PWG (hosted by Microsoft)
Wednesday,
11 July 2007 -- P2600 (hosted by HP)
Thursday,
12 July 2007 -- P2600 (hosted by HP)
Friday, 13 July
2007 Trusted Computing Group (members only)
WHERE:
PWG Meeting:
Microsoft Main Campus
Building 9, 157th Place NE
Redmond WA 98052
Building 9 Tahoma
Room 1001
For directions to the Main Campus, see:
http://www.microsoft.com/whdc/resources/events/airportmap.mspx
Once on campus, follow signs to Building 9.
The following link might also be useful:
http://local.live.com/?v=2&sp=Point.ry5wz04tpcgj_157th%20Pl%20NE%2C%20Redmond%2C%20WA%2098052%2C%20United%20States___&encType=1
Attendees may use the Valet Service outside of building 9.
NOTE: You MUST remember to register your vehicle license plates
with the Building 9 main receptionist.
P2600
Meeting:
HP Bellevue
14475 NE 24th Street
Bellevue, WA 98007
Google
map
7-day
weather forecast
REGISTRATION
INFORMATION:
For the PWG Meetings:
PLEASE SEND A NOTE TO<EMAIL_ADDRESS>INCLUDING WHICH DAYS
YOU PLAN TO ATTEND (Monday, Tuesday or Both) !!
HOTEL
ACCOMMODATIONS:
There have been no hotel blocks reserved for the meetings. Hotels that
are close to both locations are listed below.
Courtyard Bellevue
14615 NE 29th Place
Bellevue, WA
425-869-5300
Residence Inn - Bellevue
14455 NE 29th Place
Bellevue, WA
425-882-1222
Redmond Marriott Towne Center
7401 164th Ave NE
Redmond, WA
425-498-4000
Residence Inn - Redmond
7575 164th Ave. N.E.
Redmond, WA
425-497-9226
Silver Cloud Inn - Redmond
2122 152nd Avenue NE
Redmond, WA
425-746-8200


Dear Mr. James Anderson,
Thank you very much for your Request: Code:……
Dai Minh Travel proud to assist you through your upcoming journey as per your request details:
Dai Minh is looking forward to serving you soon,
Wish you a pleasant journey,
Best Regards,
Reservation Department
Dai Minh Travel


The data collected contains 200 schools distributed in all Bogota's Districts in order to achieve a representative sample for the 1536 schools located in the city.
| Filtro | Filtro | ||
|---|---|---|---|
| Localidades: | Tipo: | ||
| Jornada: | Sector: |
The data collected contains 200 schools distributed in all Bogota's Districts in order to achieve a representative sample for the 1536 schools located in the city.


Simple definition: Adj. gridier, gridiest; Having or showing a desire to build flexbox grids in large or excessive amounts.
I have build Gridy out of the frustration with the bloated grid systems currently available.
Why should I be forced to use billions of nested rows and columns** just for styling relatively simple website layouts?
Why do I have to resort on crazy nth-child and clearfix, with hardcoded media queries and with arbitrary and rigidly set number of columns when building image gallery layouts?
Why do I have to use absolute positioning for centering elements in the grid and use javascript to equalize the height of the columns?
If you have experienced my problems, I feel your pain! But don't worry...you can now rely on Gridy to overcame all these issues!
Here's a list of Gridy features:
You can install Gridy either by including the CSS file, or directly by adding the SASS files in your project.
Head to the Customization section to learn how to customize the grid with SASS.
Gridy is heavily based on the work of Laurent G. author of the amazing Gridlex grid system which inspired this project.


Hey DJ! With this layout you can create your own music app and allow your fans to listen your custom tracks and sounds.


Name
Astronavigation
Orbital
Government
population
languages
terrain
capital
other cities
areas
exports
imports
routes
conditions
background
Submit


Use the circle
at the bottom of the page
to load a new image/poem set,
or use your left and
right arrow keys.
Use the +/- at
the bottomof the page
to show or hide a poem,
or use your up and
down arrow keys.


You can use this check box to toggle the read only state of your topics.
For new topics, select this check box if your new topic is to be read only. Note that Moderate will set this box automatically for topics called files, announce, announcements or digest.


The SDK is designed for use with Angel health sensor, currently under development by Seraphim Sense Ltd. Angel will allow monitoring of heart rate, blood oxygen, temperature, and activity. Developers will be able to access these health metrics, and other features, in order to create new digital health apps. The SDK is planned for support of Android and iOS devices.
Angel SDK is under active development. For details, please refer to www.angelsensor.com.


Client
Office of the U.S. Department of Education
From
Accenture
Release
1
Project
Website Redesign Build Kit
Initial Release
Pages
Landing page
Login
Register
Getting Started
Dashboard
Student Information
Student Financial Information
Error Check :: Pass
Error Check :: Fail
Error Check :: Make Corrections
School Selector


--- layout: post title: heavenly in south l date: '2013-09-11T16:07:00-07:00' tags: - pinterest - shredding image: /tumblr_files/tumblr_mszhjoVD0C1sob777o1_250.jpg tumblr_url: https://nils.schimmelmann.us/post/60971709412/heavenly-in-south-l ---
#Heavenly in South L http://www.pinterest.com/pin/294704369335846771/


Class: Aws::Lightsail::Types::RegisteredDomainDelegationInfo
| 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-lightsail/lib/aws-sdk-lightsail/types.rb |
Overview
Describes the delegation state of an Amazon Route 53 registered domain to Amazon Lightsail.
When you delegate an Amazon Route 53 registered domain to ::Aws::Lightsail
,
you can manage the DNS of the domain using a ::Aws::Lightsail
DNS zone. You
no longer use the Route 53 hosted zone to manage the DNS of the
domain. To delegate the domain, ::Aws::Lightsail
automatically updates the
domain's name servers in Route 53 to the name servers of the
::Aws::Lightsail
DNS zone. Then, ::Aws::Lightsail
automatically deletes the Route 53
hosted zone for the domain.
All of the following conditions must be true for automatic domain delegation to be successful:
The registered domain must be in the same Amazon Web Services account as the Lightsail account making the request.
The user or entity making the request must have permission to manage domains in Route 53.
The Route 53 hosted zone for the domain must be empty. It cannot contain DNS records other than start of authority (SOA) and name server records.
If automatic domain delegation fails, or if you manage the DNS of your
domain using a service other than Route 53, then you must manually add
the ::Aws::Lightsail
DNS zone name servers to your domain in order to
delegate management of its DNS to ::Aws::Lightsail
. For more information, see
Creating a DNS zone to manage your domain’s records in Amazon
Lightsail in the Amazon ::Aws::Lightsail
Developer Guide.
Constant Summary
Instance Attribute Summary
-
#name_servers_update_state ⇒ Types::NameServersUpdateState
rw
An object that describes the state of the name server records that are automatically added to the Route 53 domain by
::Aws::Lightsail
. -
#r53_hosted_zone_deletion_state ⇒ Types::R53HostedZoneDeletionState
rw
Describes the deletion state of an Amazon Route 53 hosted zone for a domain that is being automatically delegated to an Amazon Lightsail DNS zone.
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Structure#to_h. |
Instance Attribute Details
#name_servers_update_state ⇒ Types::NameServersUpdateState (rw)
An object that describes the state of the name server records that
are automatically added to the Route 53 domain by ::Aws::Lightsail
.
# File 'gems/aws-sdk-lightsail/lib/aws-sdk-lightsail/types.rb', line 12737
class RegisteredDomainDelegationInfo < Struct.new( :name_servers_update_state, :r53_hosted_zone_deletion_state) SENSITIVE = [] include Aws::Structure end
#r53_hosted_zone_deletion_state ⇒ Types::R53HostedZoneDeletionState (rw)
Describes the deletion state of an Amazon Route 53 hosted zone for a domain that is being automatically delegated to an Amazon Lightsail DNS zone.
# File 'gems/aws-sdk-lightsail/lib/aws-sdk-lightsail/types.rb', line 12737
class RegisteredDomainDelegationInfo < Struct.new( :name_servers_update_state, :r53_hosted_zone_deletion_state) SENSITIVE = [] include Aws::Structure end


Some users use UGWA only briefly to check the schedule; the PSAs get in the way of this, so they instinctively find and click close. There's no reason to force users to read something they don't care about, so announcements are now listed in the Options tab instead.


Wrap slide picture with a link to the video. The link should specify class="video" and its href must be formatted as below without any extra parameters.

It's done.
Note:
- autoPlayVideo="true" and/or autoNextOnVideoFinished="false" can be added to the link to overwrite the slider's default behavior.
Please visit our online Demo 6: Video Slider for more details.


A special thanks to our contributors. Their words create ripples toward a better future.
{% capture site_authors %}{% for post in site.posts %}{{ post.author | first }}{% unless forloop.last %},{% endunless %}{% endfor %}{% endcapture %}
{% assign author_names = site_authors | split: ',' | uniq | sort %}


MagicalRecord Class Reference
| Inherits from | NSObject |
| Declared in | MagicalRecord.h |
Tasks
Other Methods
Setup Methods
-
+ setupCoreDataStack
-
+ setupCoreDataStackWithInMemoryStore
-
+ setupAutoMigratingCoreDataStack
-
+ setupCoreDataStackWithStoreNamed:
-
+ setupCoreDataStackWithAutoMigratingSqliteStoreNamed:
iCloud Methods
-
+ isICloudEnabled
-
+ setupCoreDataStackWithiCloudContainer:localStoreNamed:
-
+ setupCoreDataStackWithiCloudContainer:contentNameKey:localStoreNamed:cloudStorePathComponent:
-
+ setupCoreDataStackWithiCloudContainer:contentNameKey:localStoreNamed:cloudStorePathComponent:completion:
Actions Methods
-
+ saveWithBlock:
-
+ saveInBackgroundWithBlock:
-
+ saveInBackgroundWithBlock:completion:
-
+ saveInBackgroundUsingCurrentContextWithBlock:completion:errorHandler:
Options Methods
-
+ shouldAutoCreateManagedObjectModel
-
+ setShouldAutoCreateManagedObjectModel:
-
+ shouldAutoCreateDefaultPersistentStoreCoordinator
-
+ setShouldAutoCreateDefaultPersistentStoreCoordinator:
-
+ setShouldDeleteStoreOnModelMismatch:
-
+ shouldDeleteStoreOnModelMismatch
@method shouldDeleteStoreOnModelMistmatch @abstract If true, when configuring the persistant store coordinator, and Magical Record encounters a store that does not match the model, it will attempt to remove it and re-create a new store. This is extremely useful during development where every model change could potentially require a delete/reinstall of the app.
ErrorHandling Methods
-
+ handleErrors:
-
– handleErrors:
-
+ setErrorHandlerTarget:action:
-
+ errorHandlerAction
-
+ errorHandlerTarget
ShorthandSupport Methods
Class Methods
saveInBackgroundUsingCurrentContextWithBlock:completion:errorHandler:
+ (void)saveInBackgroundUsingCurrentContextWithBlock:(void ( ^ ) ( NSManagedObjectContext *))block completion:(void ( ^ ) ( void ))completion errorHandler:(void ( ^ ) ( NSError *))errorHandler
saveInBackgroundWithBlock:
+ (void)saveInBackgroundWithBlock:(void ( ^ ) ( NSManagedObjectContext *localContext ))block
saveInBackgroundWithBlock:completion:
+ (void)saveInBackgroundWithBlock:(void ( ^ ) ( NSManagedObjectContext *localContext ))block completion:(void ( ^ ) ( void ))callback
setShouldAutoCreateDefaultPersistentStoreCoordinator:
+ (void)setShouldAutoCreateDefaultPersistentStoreCoordinator:(BOOL)shouldAutoCreate
setShouldAutoCreateManagedObjectModel:
+ (void)setShouldAutoCreateManagedObjectModel:(BOOL)shouldAutoCreate
setShouldDeleteStoreOnModelMismatch:
+ (void)setShouldDeleteStoreOnModelMismatch:(BOOL)shouldDeleteStoreOnModelMismatch
setupCoreDataStackWithAutoMigratingSqliteStoreNamed:
+ (void)setupCoreDataStackWithAutoMigratingSqliteStoreNamed:(NSString *)storeName
setupCoreDataStackWithiCloudContainer:contentNameKey:localStoreNamed:cloudStorePathComponent:
+ (void)setupCoreDataStackWithiCloudContainer:(NSString *)containerID contentNameKey:(NSString *)contentNameKey localStoreNamed:(NSString *)localStoreName cloudStorePathComponent:(NSString *)pathSubcomponent
setupCoreDataStackWithiCloudContainer:contentNameKey:localStoreNamed:cloudStorePathComponent:completion:
+ (void)setupCoreDataStackWithiCloudContainer:(NSString *)containerID contentNameKey:(NSString *)contentNameKey localStoreNamed:(NSString *)localStoreName cloudStorePathComponent:(NSString *)pathSubcomponent completion:(void ( ^ ) ( void ))completion
setupCoreDataStackWithiCloudContainer:localStoreNamed:
+ (void)setupCoreDataStackWithiCloudContainer:(NSString *)icloudBucket localStoreNamed:(NSString *)localStore
shouldAutoCreateDefaultPersistentStoreCoordinator
+ (BOOL)shouldAutoCreateDefaultPersistentStoreCoordinator
shouldDeleteStoreOnModelMismatch
@method shouldDeleteStoreOnModelMistmatch @abstract If true, when configuring the persistant store coordinator, and Magical Record encounters a store that does not match the model, it will attempt to remove it and re-create a new store. This is extremely useful during development where every model change could potentially require a delete/reinstall of the app.
+ (BOOL)shouldDeleteStoreOnModelMismatch
Discussion
@method shouldDeleteStoreOnModelMistmatch @abstract If true, when configuring the persistant store coordinator, and Magical Record encounters a store that does not match the model, it will attempt to remove it and re-create a new store. This is extremely useful during development where every model change could potentially require a delete/reinstall of the app.
Declared In
MagicalRecord+Options.h


VBS Youth Volunteer Registration
Volunteers must be regular attenders of SW Hills Baptist Church.
Name
First*
Last*
Address
Street*
City*
State*
Zip*
Primary Phone*
Additional Phone
Email Address*
Service and Availability
Days available (select all that apply)*
Monday
Tuesday
Wednesday
Thursday
Friday
I wish to serve in*
Staff Preschoolers
Younger Grades (K-2nd)
Older Grades (3rd-5th)
Middle School (must be at least 16yrs old)
Recreation
Craft
Nursery/Toddler Staff Care
Decor prior to VBS
Anywhere needed
I wish to serve in (2nd Choice)
Staff Preschoolers
Younger Grades (K-2nd)
Older Grades (3rd-5th)
Middle School (must be at least 16yrs old)
Recreation
Craft
Nursery/Toddler Staff Care
Decor prior to VBS
Anywhere needed
One friend that I'd like to serve with
Reference Information
Character Reference Name*
Character Reference Contact Information*
Additional information
List any siblings that will need childcare are too young to attend that will require childcare during VBS.
Medical Forms on File
I've confirmed that my medical forms are on file at the church.
By submitting this form, that I agree to the following:
I am a regular attender of SW Hills.
I have filled out and signed (or had a parent sign) a medical release form.
I will attend a staff training prior to VBS.
I will help decorate my classroom (if applicable).
I will help clean my group's area on Friday after the campers leave.
I will arrive at 8:00 AM on Monday morning for an all staff meeting.
I will arrive at 8:30 AM Tuesday - Friday to meet with my team.
Register!


Class Protobone.Model
Extends: Protobone.BaseClass defined in:
src/statics.js:1
PrototypeJS Model extension - Enables Prototype JS users to fetch / store Models from / to a backend using AJAX / REST
Inspired by (but not copied) Backbone's Backbone.Model and Backbone.sync
constructor
( data
)
src/Model.js:63
Constructor. Sets the given data (key/value pairs) as attributes on new model instances.
Parameters:-
data
<Object>Initial data (key/value pairs) to set on the new Model instance, e.g.:
{name: 'Alex',age: 26}
destroy
( options
)
src/Model.js:237
invokes a delete request to the server. Only allowed for existing (id <> null) models. options is passed along to Prototype's Ajax.Request function.
After the deletion was successful, the model instance is updated with the server data, even if the server removed the instance.
Parameters:-
options
<Object>Additional Ajax options to be sent to Ajax.Request.
fetch
( options
)
src/Model.js:220
Fetches this Model's representation from the server. Only allowed for existing (id <> null) models. options is passed along to Prototype's Ajax.Request function.
Parameters:-
options
<Object>Additional Ajax options to be sent to Ajax.Request.
fireEvent
( eventName
)
Defined in Protobone.Base:
src/Base.js:60
Fires an event, informing all listneners that are registered for the given event name. The fireEvent function can be called with any number of additional arguments, which are then passed to the event handler function.
Returns true if NONE of the registered handlers return false: As soon as one listener returns false, fireEvent will also return false.
Parameters:-
eventName
<String>The event to fire, e.g. 'updated'
true when non of the listeners returned false, false if they do so.
get
( key
)
src/Model.js:157
Returns a specific attribute, or all if key is omitted
Parameters:-
key
<String>The name of the attribute to get. If omitted, an object containing all attributes (key/value) is returned.
The value of the requested attribute, or an object with all attributes
getId
(
)
src/Model.js:81
Returns the instance's ID of the model. Null means it is a new, not saved instance.
The ID (int, string), if any
hasAttribute
( key
)
src/Model.js:307
Checks if the model has a certain attribute.
Parameters:-
key
<String>The attribute name to check
off
( eventName, callback, this
)
Defined in Protobone.Base:
src/Base.js:34
Removes a specific event handler for an event, or removes all listerners from an event.
Parameters:on
( eventName, callback, this
)
Defined in Protobone.Base:
src/Base.js:16
Registers an event handler. It does not check on duplicity, so you can add the same event handler multiple times.
Parameters:parse
(
)
src/Model.js:289
Called by save() and fetch() with the server's data response. Fills in the
server response to the model. In the default implementation, it just
takes the plain JSON object from the server (if any) and store the values on the model.
if rootProperty
is set, the data entry point is set to the rootProperty data.
save
( options
)
src/Model.js:197
Makes this model persistent by sending the data to a REST interface (by default). Make sure to set the urlRool property on class definition.
options are all options that Prototype's Ajax.Request understands, so you can e.g. deliver a onSuccess callback:
myModel.save({onSuccess: function(response,model){
// do something after save here
}});
Parameters:
-
options
<Object>Additional Ajax options to be sent to Ajax.Request.
set
( /Object, value
)
src/Model.js:106
Sets Model attributes (key/values). Takes either a key and a value, or a plain object containing key/value pairs.
Parameters:-
/Object
<String>keyOrObject A string representing the key (e.g. 'name') or an object with key/values (e.g. 'name':'alex','age':'too old')
-
value
<Mixed>The value to set if keyOrObject is a string. Ignored when keyOrObject is an object.
Supports fluent interface by returning itself
setId
( id
)
src/Model.js:92
Sets the Model instance's ID. It also sets it as attribute value so that it is sent to the server when synced.
Parameters:-
id
<Mixed>The id to set (e.g. an integer, or even a string)
Supports fluent interface by returning itself
sync
( url, method, model, options
)
src/statics.js:61
This method is where the real server communication happens. It uses
Prototype's Ajax.Request to send / load data to/from a REST backend.
It is called in a static context (Protobone.Model.sync
) from a Model's instance
and can be overridden if you have to implement your own storage backend (e.g. localstore)
or an incompatible API.
The default method uses the following HTTP methods
- method: create ->
POST /collection
- method: read ->
GET /collection[/id]
- method: update ->
POST /collection/id
(Request Header:X-HTTP-Method-Override: put
) - method: delete ->
POST /collection/id
(Request Header:X-HTTP-Method-Override: delete
)
-
url
<String>The URL for the request
-
method
<String>The HTTP method. Only supported at the moment: 'get', 'post' (as of Prototype's limitation)
-
model
<Protobone.Model>A model instance to be sent / updated to /from the server
-
options
<Object>Additional Ajax.Request options
sync
(
)
src/Model.js:278
Just calls Protobone.Model.sync. If you want your own, Model-specific implementation, override this function.
url
(
)
src/Model.js:176
Creates the REST url for the actual state of the Model. Override this method if you want to implement your own URL scheme. Here is how it works by default:
- non-persistent state (id = null): return '
' - persistent state (id <> null): return '
/ '
The URL for this Model instance, e.g. /root/Entity/3
emulateHTTP
<Boolean>src/statics.js:39
If set to true, only use GET (read) and POST (create,update,delete) HTTP Methods, and set the X-HTTP-Method-Override request header with the true method.
NOTE: TODO: At the moment, only legacy methods (GET/POST) are supported (emulateHTTP: true), because the Prototype JS library does NOT support other requests than POST/GET. So set emulateHTTP to false does not change a thing, unfortunately...
emulateJSON
<Boolean>src/statics.js:53
TODO: Implement emulateJSON to use a post body instead of RAW json
rootProperty
<Unknown>src/Model.js:53
Used by the parse() function, it defines the root property in the server's json response which contains the payload data for the model. Defaults to null (delivered json directly contains model attributes)
urlRoot
<String>src/Model.js:43
The URL root for this Model. Must be set in child classes, e.g. to '/entities/Person'. Used by the url() function to build the persistence URL.


Syntax:
set keyword value
memory value = N N = max size of datum in Kbytes self value = S S = allow queueing of this many messages to self queue value = Q Q = allow queueing of this many previously received messages safe value = M M = send a datum "safely" every this many sends pernode value = Nc Nc = # of cores per node to use when binding minnows to processors numnode value = Nn Nn = # of nodes to use when binding minnows to processors bindorder value = B B = 0 = no bind order is imposed B = 1 = perform binding by looping over cores, then over nodes B = 2 = perform binding by looping over nodes, then over coreshigh-water-mark value = N N = maximum number of outgoing messages to queue to a recipient
Examples:
set memory 1024 set self 20 set safe 10 set bindorder 2
Description:
Set is a command that can be used in a PHISH input script which is recognized by the bait.py setup program. It resets default values that are used by the bait.py program as it reads and processes commands from the PHISH input script.
The memory keyword sets the maximum length of datums that are exchanged by minnows when a PHISH program runs. Send and receive buffers for datums are allocated by the PHISH library. The N setting is in Kbytes, so that N = 1024 is 1 Mbyte, and N = 1048576 is 1 Gbyte. The default is N = 1, since typical PHISH minnows send and receive small datums.
The self keyword sets the size of a queue used to buffer datums sent by a minnow to itself. In most PHISH input scripts sending to self this never happens, but it is allowed. Since messages to self are received with the highest priority by PHISH library functions such as phish_loop() and phish_probe() that receive messages, it is also typical that this queue often needs to be no larger than $S$ = 1 message, since $S refers to the maximum number of outstanding (sent, but not yet received) messages. But it can be set larger if a minnow may perform several sends (to itself) before receiving a new message.
The queue keyword sets the size of a queue used to buffer previously received datums when a minnow uses the phish_queue() and phish_dequeue() library calls, so that it can process a received datum later, after receiving other datums. The $Q$ setting determines the maximum number of datums that can be queued at one time in this manner.
These 3 settings determine how much memory PHISH allocates. There are always 2 buffers of size memory = $N$, one for sending, one for receiving. There are at most self = $S$ buffers, each of size $N$, allocated for self messages, and likewise at most queue = $Q$ buffers, each of size $N$, allocated for queued messages. These buffers for self and queued messages are only allocated if they are needed as the PHISH script runs and messages are processed. Thus the overall memory footprint of the PHISH library is typically tiny, unless you set these parameters to large values.
The safe keyword is only relevant for the MPI version of the PHISH library. It causes the library to use a "safe" MPI_Ssend() call every Mth time it sends a datum, rather than the normal MPI_Send() function. If M = 0, "safe" sends are never performed.
Safe in this context refers to messages being dropped if the receiving process is backed up. This can happen if a minnow in a PHISH school of minnows is significantly slower to process datums than all the others, and a large number of datums are being continually sent to it. When a safe send is done, an extra handshake is performed between the sender and receiver to insure the receiver is ready for the datum. Doing this often enough should effectively throttle the incoming messages to a slow minnow, so an overflow does not occur. Note that the extra handshaking between the MPI processes slows down the rate at which small messages are exchanged, so you should not normally use this setting unless MPI errors arise, e.g. due to "too many unexpected messages". A good setting for M depends on how many minnows are sending to the overflowing minnow. Typical MPI implementations allow tens of thousands of small incoming messages to be queued, so M = 1000 or 10000 is fine if a single minnow is sending to the minnow. If 10 minnows are sending to the overflowing minnow, then M should be reduced by a factor of 10.
The self keyword is only relevant for the MPI version of the PHISH. A PHISH net described by an input script can include hook commands that route datums from a school back to itself, e.g. in some kind of looping fashion. This means that a procesor can send messages to itself. When this occurs the PHISH library uses a buffered MPI_Bsend() call. This avoids a possible hang due to a blocking send, which can happen in some MPI implementations. The value of S determines how big a buffer is reserved for the buffered send operations. It effectively means how many messsages (of maximum size, as determined by the memory keyword above), can be sent to self and buffered before they are received. In most cases the small default setting is sufficient, but if a minnow can send many messages to itself before reading and processing them, you may need to boost this setting to avoid an MPI error or hang.
The pernode, (numnode, and bindorder keywords are used to tailor the assignment of minnows to physical processors when the PHISH program is run. See the discussion of the bind option for the bait.py school command for more details on this topic.
Note that the default setting of numnode is equal to the total number of minnow instances Np in a PHISH input script, divided by the pernode setting. If Np is not evenly divisible by pernode, then numnode is incremented by one so that numnode * pernode >= Np.
The high-water-mark keyword only applies to the ZMQ version of PHISH. It sets the maximum number of outgoing messages that can be queued to a given recipient. Messages are queued when a recipient is receiving messages more slowly than the sender is sending them. Once the number of queued messages reaches the high water mark, the sender will block until the queue begins to empty. Note that messages are queued on a per-recipient rather than a per-port basis, so the memory used for queuing can vary dramatically depending on the size of the downstream school.
Restrictions: none
Related commands:
Any setting can be made either in a PHISH input script or via the --set command-line argument of the bait.py tool.
Default:
The default settings are memory = 1 (1 Kbyte), self = 8, queue = 8, safe = 0, pernode = 1, numnode = # of minnows / pernode, and bindorder = 0.


[1]
I used these 2 hoses to replace the original equipment rubber hoses.
[2]
A hose was included with our machine so we did n't need this.


Back to main page
Generalized Extreme Studentized (ESD) test
Finds potential outliers in a sample.
Data Entry
Sample:
Significance level α:
Upload CSV file:
Run Test
Clear
Test Result
Data Summary
Sample
N
Mean
Stdev
A
Result
Trial
Outlier
G-score
Critical G
Significant
Sample
Data Visualization


Some "rules"
Version control allows you (and your team) to…
Create anything with other people, from academic papers to entire websites and applications.
Mistakes happen. Wouldn't it be nice if you could see the changes that have been made and go "back in time" to fix something that went wrong?
Do you have files somewhere that look like this?
Resume-September2013.docx
Resume-for-Duke-job.docx
ResumeOLD.docx
ResumeNEW.docx
ResumeREALLYREALLYNEW.docx
You invented your own version control!
But, we can do it so much better with Version Control tools
1990s — CVS (Concurrent Version Systems)
2000s — SVN (Apache Subversion)
2005 — Git
The first commit, April 2005
commit e83c5163316f89bfbde7d9ab23ca2e25604af29
Author: Linus Torvalds<EMAIL_ADDRESS>Date: Thu Apr 7 15:13:13 2005 -0700
Initial revision of "git", the information manager from hell
Examples: CVS, SVN
Examples: Git, Mercurial
One central server, each client (person) checks out and merges changes to main server
...NOT how Git works!
Each client (person) has a local repository, which they can then reconcile with the main server.
...this is how Git does it!
Install git
Setup name and email in git config
$ git config --global user.name "Your Name Here"
# Sets the default name for git to use when you commit
$ git config --global user.email<EMAIL_ADDRESS># Sets the default email for git to use when you commit
$ git config --list
Setup SSH keys
SSH keys allow you to interact with your Git server without having to type your username and password all the time.
Setup the Default Text Editor
By default Git is set up to use Vim as the text editor.
(esc + :q or :q! to get out of Vim)
Follow these instructions to change your default text editor to whatever you prefer.
 Added README to repository."

How is this all different than just saving a file?
$ git log
commit [HASH HERE]
Author: Your name<EMAIL_ADDRESS>Date: [DATE HERE]
First commit. Added README to repository.
README.md
and make some more commits.git status
regularly so that you can see what is happening at each stage!If you haven't staged/committed yet
Open README.md
and make some changes to the file.
$ git checkout README.md
Look at README.md
. Your changes are gone. You've gone back to the previous commit state.
Create new file my_new_file.txt
$ git add my_new_file.txt
$ git reset my_new_file.txt
The file is removed from staging, but your working copy will be unchanged.
Open README.md
and add some new text
$ git add README.md
$ git reset HEAD README.md
$ git status ## your changes were unstaged
$ git checkout README.md
Look at README.md
. Your changes are gone and the file is removed from staging.
Git lets you go back to any previous commit.
Open README.md
and add some new text
$ git add README.md
$ git status
$ git commit -m "Make a change I will soon regret making"
$ git log --oneline
Okay, I see the change… now how do I remove it?
$ git revert 53d23c4
# Your default editor will open here
# you can just save it and close it as is.
$ git log --oneline
Notice that the original, regrettable commit is still there, but now you also have another commit that undoes the changes introduced by the original one.
You decide what goes into version control.
You can—and should!—leave some things out.
libraries, .dotfiles, api keys...
Git shows you an easy way to do this: .gitignore
A branch is another copy of your repo that allows you to isolate changes and leave the original copy untouched. You can choose to combine these changes in whole or part with the "master" copy later.
Why Branch?
Create a new branch called my-feature
$ git checkout -b my-feature
Add new lines to README.md
$ git add README.md
$ git commit -m "Adding changes to my-feature"
See all branches. Branch with * is active
$ git branch
Switch to master
and look at README.md
$ git checkout master
Switch to my-feature
and look at README.md
$ git checkout my-feature
Copying changes from one branch to another is called merging.
Switch to master
and merge the changes from the branch my-feature
$ git checkout master
$ git merge my-feature
$ git log --oneline
What is a merge confict?
Change first line in README.md
in master
branch
$ git add README.md
$ git commit -m "Changing first line in master"
Change first line in README.md
in my-feature
branch
$ git checkout my-feature
# open README.md and change first line
$ git add README.md
$ git commit -m "Changing first line in my-feature"
Merge from master
into my-feature
$ git merge master
You will be notified of a conflict. Go to the file and fix the problem. Then commit your edits.
You will need to be logged into your GitHub account to do this.
After you click the big green button to create your repo, follow GitHub's instructions for next steps.
$ git remote add origin https://github.com/YOUR-GITHUB-USERNAME/REPO.git
$ git push -u origin master
# that -u is an option that signals that you are setting
# a tracking reference to the remote branch as the default;
# you only need to use this flag the first time
Now check out your GitHub repo online!

If team members are contributing to a single repo, each member of the team will want to make sure that she has everyone else's changes before pushing her own changes to the remote repository.
Always pull before you push!
Commit local changes first
$ git commit -m "My latest commit"
Get changes that have been pushed
$ git pull origin master
Git may prompt you to fix any conflicts, then commit
$ git commit -m "Fixing merging conflicts"
Now you are ready to push local changes to GitHub
$ git push origin master
There are MILLIONS of public repositories on GitHub.
There are huge open source projects (including Git!)…
…and small projects like these slides.
If you want to use or contribute to a repository, you have to fork the repository, then clone it to your computer.
A fork is just a copy of a repository, saved to GitHub.
After you fork the repository, it shows up in your repositories.
Let's Try It! Fork this repo.
You can only fork repos through the GitHub website.
To get a local copy of the fork you just made, use the git clone
command.
$ cd ../
$ git clone https://github.com/USERNAME/colors_page.git
$ cd colors_page
$ git remote -v
To sync your fork with the original repo, you need to add another remote named upstream
$ git remote -v
$ git remote add upstream https://github.com/urakymzhan/colors_page.git
$ git fetch upstream
git fetch
downloads Git references not present in your local repository, but does not modify your files (think of it like getting a table of contents rather than the contents themselves)
After you fork
and clone
a repository all pushed changes will go to your fork (origin
)
These changes do not affect the original (upstream
) repository (mostly because permissions). To do that, you need to submit a pull request.
A pull request is a GitHub feature that lets you ask the owner of the upstream repo to pull your changes in.
Pull requests can only be done through the GitHub website.
Repo owners review and decide whether to merge in the pull requests they receive.
You can learn more from the
Github Collaborating Tutorials
colors_page
repository and push to your remote.