001/* 002 * Licensed to the Apache Software Foundation (ASF) under one or more 003 * contributor license agreements. See the NOTICE file distributed with 004 * this work for additional information regarding copyright ownership. 005 * The ASF licenses this file to You under the Apache License, Version 2.0 006 * (the "License"); you may not use this file except in compliance with 007 * the License. You may obtain a copy of the License at 008 * 009 * http://www.apache.org/licenses/LICENSE-2.0 010 * 011 * Unless required by applicable law or agreed to in writing, software 012 * distributed under the License is distributed on an "AS IS" BASIS, 013 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 014 * See the License for the specific language governing permissions and 015 * limitations under the License. 016 */ 017package org.apache.commons.fileupload; 018 019import java.io.File; 020import java.io.IOException; 021import java.io.InputStream; 022import java.io.OutputStream; 023import java.io.UnsupportedEncodingException; 024 025/** 026 *
 This class represents a file or form item that was received within a 027 * multipart/form-data POST request. 028 * 029 *
 After retrieving an instance of this class from a {@link 030 * org.apache.commons.fileupload.FileUpload FileUpload} instance (see 031 * {@link org.apache.commons.fileupload.servlet.ServletFileUpload 032 * #parseRequest(javax.servlet.http.HttpServletRequest)}), you may 033 * either request all contents of the file at once using {@link #get()} or 034 * request an {@link java.io.InputStream InputStream} with 035 * {@link #getInputStream()} and process the file without attempting to load 036 * it into memory, which may come handy with large files. 037 * 038 *
 While this interface does not extend 039 * javax.activation.DataSource per se (to avoid a seldom used 040 * dependency), several of the defined methods are specifically defined with 041 * the same signatures as methods in that interface. This allows an 042 * implementation of this interface to also implement 043 * javax.activation.DataSource with minimal additional work. 044 * 045 * @since 1.3 additionally implements FileItemHeadersSupport 046 */ 047public interface FileItem extends FileItemHeadersSupport { 048 049 // ------------------------------- Methods from javax.activation.DataSource 050 051 /** 052 * Returns an {@link java.io.InputStream InputStream} that can be 053 * used to retrieve the contents of the file. 054 * 055 * @return An {@link java.io.InputStream InputStream} that can be 056 * used to retrieve the contents of the file. 057 * 058 * @throws IOException if an error occurs. 059 */ 060 InputStream getInputStream() throws IOException; 061 062 /** 063 * Returns the content type passed by the browser or null if 064 * not defined. 065 * 066 * @return The content type passed by the browser or null if 067 * not defined. 068 */ 069 String getContentType(); 070 071 /** 072 * Returns the original filename in the client's filesystem, as provided by 073 * the browser (or other client software). In most cases, this will be the 074 * base file name, without path information. However, some clients, such as 075 * the Opera browser, do include path information. 076 * 077 * @return The original filename in the client's filesystem. 078 * @throws InvalidFileNameException The file name contains a NUL character, 079 * which might be an indicator of a security attack. If you intend to 080 * use the file name anyways, catch the exception and use 081 * InvalidFileNameException#getName(). 082 */ 083 String getName(); 084 085 // ------------------------------------------------------- FileItem methods 086 087 /** 088 * Provides a hint as to whether or not the file contents will be read 089 * from memory. 090 * 091 * @return true if the file contents will be read from memory; 092 * false otherwise. 093 */ 094 boolean isInMemory(); 095 096 /** 097 * Returns the size of the file item. 098 * 099 * @return The size of the file item, in bytes. 100 */ 101 long getSize(); 102 103 /** 104 * Returns the contents of the file item as an array of bytes. 105 * 106 * @return The contents of the file item as an array of bytes. 107 */ 108 byte[] get(); 109 110 /** 111 * Returns the contents of the file item as a String, using the specified 112 * encoding. This method uses {@link #get()} to retrieve the 113 * contents of the item. 114 * 115 * @param encoding The character encoding to use. 116 * 117 * @return The contents of the item, as a string. 118 * 119 * @throws UnsupportedEncodingException if the requested character 120 * encoding is not available. 121 */ 122 String getString(String encoding) throws UnsupportedEncodingException; 123 124 /** 125 * Returns the contents of the file item as a String, using the default 126 * character encoding. This method uses {@link #get()} to retrieve the 127 * contents of the item. 128 * 129 * @return The contents of the item, as a string. 130 */ 131 String getString(); 132 133 /** 134 * A convenience method to write an uploaded item to disk. The client code 135 * is not concerned with whether or not the item is stored in memory, or on 136 * disk in a temporary location. They just want to write the uploaded item 137 * to a file. 138 *
 139 * This method is not guaranteed to succeed if called more than once for 140 * the same item. This allows a particular implementation to use, for 141 * example, file renaming, where possible, rather than copying all of the 142 * underlying data, thus gaining a significant performance benefit. 143 * 144 * @param file The File into which the uploaded item should 145 * be stored. 146 * 147 * @throws Exception if an error occurs. 148 */ 149 void write(File file) throws Exception; 150 151 /** 152 * Deletes the underlying storage for a file item, including deleting any 153 * associated temporary disk file. Although this storage will be deleted 154 * automatically when the FileItem instance is garbage 155 * collected, this method can be used to ensure that this is done at an 156 * earlier time, thus preserving system resources. 157 */ 158 void delete(); 159 160 /** 161 * Returns the name of the field in the multipart form corresponding to 162 * this file item. 163 * 164 * @return The name of the form field. 165 */ 166 String getFieldName(); 167 168 /** 169 * Sets the field name used to reference this file item. 170 * 171 * @param name The name of the form field. 172 */ 173 void setFieldName(String name); 174 175 /** 176 * Determines whether or not a FileItem instance represents 177 * a simple form field. 178 * 179 * @return true if the instance represents a simple form 180 * field; false if it represents an uploaded file. 181 */ 182 boolean isFormField(); 183 184 /** 185 * Specifies whether or not a FileItem instance represents 186 * a simple form field. 187 * 188 * @param state true if the instance represents a simple form 189 * field; false if it represents an uploaded file. 190 */ 191 void setFormField(boolean state); 192 193 /** 194 * Returns an {@link java.io.OutputStream OutputStream} that can 195 * be used for storing the contents of the file. 196 * 197 * @return An {@link java.io.OutputStream OutputStream} that can be used 198 * for storing the contensts of the file. 199 * 200 * @throws IOException if an error occurs. 201 */ 202 OutputStream getOutputStream() throws IOException; 203 204}


Interact with Google Sheets from R.
| Version: | 0.3.0 |
| Depends: | R (≥ 3.2.0) |
| Imports: | cellranger (≥ 1.0.0), dplyr (≥ 0.4.2), httr (≥ 1.1.0), jsonlite, purrr, readr (≥ 0.2.2), stats, stringr, tibble, tidyr, utils, xml2 (≥ 1.0.0) |
| Suggests: | covr, ggplot2, knitr, rmarkdown, rprojroot, testthat (≥ 1.0.0) |
| Published: | 2018-06-29 |
| Author: | Jennifer Bryan [aut, cre], Joanna Zhao [aut] |
| Maintainer: | Jennifer Bryan <jenny at rstudio.com> |
| BugReports: | https://github.com/jennybc/googlesheets/issues |
| License: | MIT + file LICENSE |
| URL: | https://github.com/jennybc/googlesheets |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| In views: | WebTechnologies |
| CRAN checks: | googlesheets results |
| Reference manual: | googlesheets.pdf |
| Vignettes: |
Use an alternative browser googlesheets Basic Usage Formulas and formatted numbers Managing Auth Tokens |
| Package source: | googlesheets_0.3.0.tar.gz |
| Windows binaries: | r-devel: googlesheets_0.3.0.zip, r-release: googlesheets_0.3.0.zip, r-oldrel: googlesheets_0.3.0.zip |
| OS X binaries: | r-release: googlesheets_0.3.0.tgz, r-oldrel: googlesheets_0.3.0.tgz |
| Old sources: | googlesheets archive |
| Reverse imports: | behaviorchange, febr, gfer, rangeModelMetadata |
Please use the canonical form https://CRAN.R-project.org/package=googlesheets to link to this page.


{% load staticfiles %}
Kwame is a Columbia Law alum who invests in and advises tech ventures in Ghana and Nigeria. He is the founder of iYa Ventures.


Python Tools for Visual Studio debug (ptvsd) server python library. It can be easily installed using pip:
pip install ptvsd
The process that we will use to attach the python debugger requires that we run Lean without debugging and attach the process.
First, we will add the ptvsd library, and the following statements:
import ptvsd ptvsd.enable_attach() ptvsd.wait_for_attach()
These statements will hold the algorithm execution until Lean is attached to the python debugger.
The following statement sets the breakpoint:
ptvsd.break_into_debugger()
For example, place it in the OnData() method:
import ptvsd ptvsd.enable_attach() print(f'''Python Tool for Visual Studio Debugger {ptvsd.__version__} Please attach the python debugger: - In Visual Studio, select Debug > Attach to Process (or press Ctrl+Alt+P) to open the Attach to Process dialog box. - For Connection type, select Python remote (ptvsd) - In the Connection target box, select tcp://localhost:5678/ and click "Attach" button''') ptvsd.wait_for_attach() class BasicTemplateAlgorithm(QCAlgorithm): def Initialize(self): self.SetStartDate(2013,10, 7) self.SetEndDate(2013,10,11) self.SetCash(100000) self.AddEquity("SPY", Resolution.Second) self.Debug(f"numpy test >>> print numpy.pi: {np.pi}") def OnData(self, data): ptvsd.break_into_debugger() close = data["SPY"].Close if not self.Portfolio.Invested: self.SetHoldings("SPY", 1)
Finally, attach the debugger to the process:
Once you attach the process the code execution will stop after ptvsd.break_into_debugger() statement.


src.cache package¶
Subpackages¶
Submodules¶
src.cache.apps module¶
src.cache.cache module¶
-
src.cache.cache.
dump_to_cache
(path, obj, prefix='')¶
-
src.cache.cache.
get_digested
(candidate_path)¶ Return type: str
-
src.cache.cache.
get_labelled_logs
(job)¶ Return type: (<class ‘pandas.core.frame.DataFrame’>, <class ‘pandas.core.frame.DataFrame’>)
-
src.cache.cache.
get_loaded_logs
(split)¶ Return type: (<class ‘pandas.core.frame.DataFrame’>, <class ‘pandas.core.frame.DataFrame’>, <class ‘pandas.core.frame.DataFrame’>)
-
src.cache.cache.
load_from_cache
(path, prefix='')¶
-
src.cache.cache.
put_labelled_logs
(job, train_df, test_df)¶
-
src.cache.cache.
put_loaded_logs
(split, train_df, test_df, additional_columns)¶
src.cache.models module¶
-
class
src.cache.models.
Cache
(id)¶ Bases:
src.common.models.CommonModel
-
exception
DoesNotExist
¶ Bases:
django.core.exceptions.ObjectDoesNotExist
-
exception
MultipleObjectsReturned
¶ Bases:
django.core.exceptions.MultipleObjectsReturned
-
id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
labelledlog
¶ Accessor to the related object on the reverse side of a one-to-one relation.
In the example:
class Restaurant(Model): place = OneToOneField(Place, related_name='restaurant')
Place.restaurant
is aReverseOneToOneDescriptor
instance.
-
loadedlog
¶ Accessor to the related object on the reverse side of a one-to-one relation.
In the example:
class Restaurant(Model): place = OneToOneField(Place, related_name='restaurant')
Place.restaurant
is aReverseOneToOneDescriptor
instance.
-
objects
= <django.db.models.manager.Manager object>¶
-
exception
-
class
src.cache.models.
LabelledLog
(id, cache_ptr, train_log_path, test_log_path, split, encoding, labelling)¶ Bases:
src.cache.models.Cache
-
exception
DoesNotExist
¶ Bases:
src.cache.models.DoesNotExist
-
exception
MultipleObjectsReturned
¶ Bases:
src.cache.models.MultipleObjectsReturned
-
cache_ptr
¶ Accessor to the related object on the forward side of a one-to-one relation.
In the example:
class Restaurant(Model): place = OneToOneField(Place, related_name='restaurant')
Restaurant.place
is aForwardOneToOneDescriptor
instance.
-
cache_ptr_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
encoding
¶ Accessor to the related object on the forward side of a many-to-one or one-to-one (via ForwardOneToOneDescriptor subclass) relation.
In the example:
class Child(Model): parent = ForeignKey(Parent, related_name='children')
Child.parent
is aForwardManyToOneDescriptor
instance.
-
encoding_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
labelling
¶ Accessor to the related object on the forward side of a many-to-one or one-to-one (via ForwardOneToOneDescriptor subclass) relation.
In the example:
class Child(Model): parent = ForeignKey(Parent, related_name='children')
Child.parent
is aForwardManyToOneDescriptor
instance.
-
labelling_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
split
¶ Accessor to the related object on the forward side of a many-to-one or one-to-one (via ForwardOneToOneDescriptor subclass) relation.
In the example:
class Child(Model): parent = ForeignKey(Parent, related_name='children')
Child.parent
is aForwardManyToOneDescriptor
instance.
-
split_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
test_log_path
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
train_log_path
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
exception
-
class
src.cache.models.
LoadedLog
(id, cache_ptr, train_log_path, test_log_path, additional_columns_path, split)¶ Bases:
src.cache.models.Cache
-
exception
DoesNotExist
¶ Bases:
src.cache.models.DoesNotExist
-
exception
MultipleObjectsReturned
¶ Bases:
src.cache.models.MultipleObjectsReturned
-
additional_columns_path
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
cache_ptr
¶ Accessor to the related object on the forward side of a one-to-one relation.
In the example:
class Restaurant(Model): place = OneToOneField(Place, related_name='restaurant')
Restaurant.place
is aForwardOneToOneDescriptor
instance.
-
cache_ptr_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
split
¶ Accessor to the related object on the forward side of a many-to-one or one-to-one (via ForwardOneToOneDescriptor subclass) relation.
In the example:
class Child(Model): parent = ForeignKey(Parent, related_name='children')
Child.parent
is aForwardManyToOneDescriptor
instance.
-
split_id
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
test_log_path
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
train_log_path
¶ A wrapper for a deferred-loading field. When the value is read from this object the first time, the query is executed.
-
exception


Board hardware driver files.
More...Directories | |
| directory | ADAFRUITU4 |
| directory | ATAVRUSBRF01 |
ATAVRUSBRF01 board hardware driver files. | |
| directory | BENITO |
BENITO board hardware driver files. | |
| directory | BLACKCAT |
| directory | BUI |
| directory | BUMBLEB |
BUMBLEB board hardware driver files. | |
| directory | CULV3 |
| directory | EVK527 |
XPLAIN board hardware driver files. | |
| directory | JMDBU2 |
JM-DB-U2 board hardware driver files. | |
| directory | MAXIMUS |
| directory | MICROSIN162 |
| directory | MINIMUS |
| directory | OLIMEX162 |
Olimex USB-STK-162 board hardware driver files. | |
| directory | RZUSBSTICK |
RZUSBSTICK board hardware driver files. | |
| directory | STK525 |
STK525 board hardware driver files. | |
| directory | STK526 |
STK526 board hardware driver files. | |
| directory | TEENSY |
TEENSY board hardware driver files. | |
| directory | UDIP |
| directory | UNO |
| directory | USBFOO |
USBFOO board hardware driver files. | |
| directory | USBKEY |
USBKEY board hardware driver files. | |
| directory | USBTINYMKII |
USBTINY-MKII board hardware driver files. | |
| directory | XPLAIN |
XPLAIN board hardware driver files. | |
Files | |
| file | Buttons.h |
Master include file for the board digital button driver. | |
| file | Dataflash.h |
Master include file for the board dataflash IC driver. | |
| file | Joystick.h |
Master include file for the board digital joystick driver. | |
| file | LEDs.h |
Master include file for the board LEDs driver. | |
| file | Temperature.h |
Master include file for the board temperature sensor driver. |
This folder contains drivers for interfacing with the physical hardware on supported commercial boards, primarily from the Atmel corporation. Header files in this folder should be included in user applications requiring the functionality of hardware placed on supported boards.


Next: Sharpsign Less-Than-Sign, Previous: Examples of Sharpsign Vertical-Bar, Up: Sharpsign
Some text editors that purport to understand Lisp syntax treat any |...| as balanced pairs that cannot nest (as if they were just balanced pairs of the multiple escapes used in notating certain symbols). To compensate for this deficiency, some programmers use the notation #||...#||...||#...||# instead of #|...#|...|#...|#. Note that this alternate usage is not a different reader macro; it merely exploits the fact that the additional vertical-bars occur within the comment in a way that tricks certain text editor into better supporting nested comments. As such, one might sometimes see code like:
#|| (+ #|| 3 ||# 4 5) ||#
Such code is equivalent to:
#| (+ #| 3 |# 4 5) |#


Get inspired by thousand recipes from home chef to iron chef
Please Sing In
Forget password ?
Don't have an account ? Sign up


Part of being strong and independent is knowing when you are in trouble. You should be wise enough to recognize when you’re struggling, to ask for help when you need it, to reach out for a helping hand. It’s not weak to admit you’re having a rough time. It’s not weak to text someone when you’re unsure how to overcome a certain obstacle. It’s not weak to be vulnerable.
You don’t want to confuse stubbornness with independence. Independence means you can handle yourself most of the time. It means you can come up with solutions to your problems most of the time. It means you can survive on your own most of the time. However, there are always going to be exceptions. Even the most independent person is going to need to ask for helps at some point. No one is superhuman.
Don’t let your ego get in the way of your happiness. Don’t consider yourself a failure if you end up needing assistance. There’s nothing wrong with relying on others. There’s nothing wrong with asking them for favors and returning them later.
Remember, being strong and independent doesn’t mean you need to spend every waking minute alone. It doesn’t mean you have to cut everyone out of your world. It doesn’t mean you need to keep your problems to yourself and handle them in secret, without letting anyone in on the fact you’re struggling.
You’re allowed to discuss your problems with your loved ones. You’re allowed to ask for their advice. You’re allowed to request help. You’re allowed to be imperfect.
Sometimes, the strongest thing you can do is admit you need help. You should be proud of yourself for being honest with yourself. You should be glad you’re comfortable enough with yourself to act authentically.
Remember, being strong and independent doesn’t mean you need to stay single. It doesn’t mean you can’t enjoy it when your partner takes control, picks the date, drives the car, makes the plans. You’re allowed to sit back and relax every once in a while. You’re allowed to let others do something nice for you.
Just because you can do something on your own doesn’t mean you have to. You can let others pamper you. You can let them take care of you. You can let them spoil you. You don’t have to push them away. Maybe you don’t need them — but that doesn’t mean you shouldn’t keep them around. It doesn’t mean you shouldn’t love them.
You aren’t going to lose your independence when you allow others into your universe. You can date someone and still be independent. You can accept help and still be independent. You can be in touch with your vulnerable side and still be independent.


{block name="css"}{/block}
{block name="js"}{/block}
{include file="public:header" /}
{block name="content"}{include file="public:content" /}{/block} {include file="public:aside" /} {include file="public:mainnav" /}
{include file="public:footer" /}
{include file="public:setting" /} {block name="script"}{/block}


MedCabinet
Home
About
Login
Register
Project Lead
- Lyndsi Williams
Data Engineer
- Joseph Wilson
Machine Learning
- Mark McAdam
Machine Learning
- John Grove
UI
- Wei Peluso
UI
- Manuel Vega
React I
- Blayze Stone
React II
- Christian Lewis
Back End
- David Yanofsky


Gecode::SetExpr::Node Class Reference
List of all members.Detailed Description
Nodes used to construct set expressions.
Definition at line 32 of file set-expr.cc.
Public Member Functions | |
| Node (const var_idx x) | |
| Construct node for x. | |
| Node (Node *n0, int s0, RelType r, Node *n1, int s1) | |
| Construct node from nodes n0 and n1 with signs s0 and s1. | |
| void | increment (void) |
| Increment reference count. | |
| bool | decrement (void) |
| Decrement reference count and possibly free memory. | |
| void | encode (SetExprCode &ret, bool monotone) const |
| Adds code representation of the node to ret. | |
| int | arity (void) const |
| Returns the arity of the node. | |
| Iter::Ranges::Virt::Iterator * | iter (void) |
| Returns an iterator for this node. | |
Static Public Member Functions | |
| static void * | operator new (size_t size) |
| Memory management. | |
| static void | operator delete (void *p, size_t size) |
| Memory management. |
Constructor & Destructor Documentation
|
|
Construct node for x.
Definition at line 91 of file set-expr.cc. |
|
|
Construct node from nodes n0 and n1 with signs s0 and s1.
Definition at line 96 of file set-expr.cc. |
Member Function Documentation
|
|
Increment reference count.
Definition at line 86 of file set-expr.cc. |
|
|
Decrement reference count and possibly free memory.
Definition at line 106 of file set-expr.cc. |
|
|
Adds code representation of the node to ret.
Definition at line 126 of file set-expr.cc. |
|
|
Returns the arity of the node.
Definition at line 118 of file set-expr.cc. |
|
|
Returns an iterator for this node.
|
|
|
Memory management.
Definition at line 75 of file set-expr.cc. |
|
|
Memory management.
Definition at line 80 of file set-expr.cc. |
The documentation for this class was generated from the following file:
- gecode/set/projectors/set-expr.cc (Revision: 3548)


Welcome to the JMatPro application programming interface (API) reference documentation. This guide provides comprehensive information that will help you understand how the JMatPro API can be used to integrate specific functionality of the JMatPro software into your own applications. Throughout this guide, you will find overview information and troubleshooting suggestions, as well as detailed descriptions of the functions that are included in the API. The following topics will be addressed:


This is the landing page for our project!
We decided to create a platform for people to anonymously ask advice from people they know, in a "following" one-way relationship. Our project advisor suggested that we not do the usual unguided projects. Instead, we worked towards this concept.
Mollie added the ability to respond to messages, creating a comment chain. She also added the ability to add formatting to text via whitelisted HTML because it seemed like a good way to make the project a bit friendlier and more expressive.
Sneha standardized the visual appearance of the site and created the navigation bar. She also set up the inital public feed portion of the site.
Duncan added the ability to add new advisors and become an advisor. Requests are made from the Your Advisors and are also responded to from the same page.
We suggest you start by making a post on your userpage. All posts you make are visible there; in addition, Public posts are visible to the Public Feed but not your advisors, and Private posts are the opposite.
You can also request advisors in the "Your Advisors" tab, or respond to other peoples' messages.
Have fun!


--- layout: default published: true ---
Welcome, my name is Daniel Osborne, I currently live in in the UK, by day I work for Redgate and by night I'm a tinkerer of things, and always looking to learn something new!
This corner of the internet will contain my thoughts, ramblings, and write-ups of various projects both the benefit of future me, and also for anyone else interested.
Have a look around and maybe you'll see something that piques your interest, or hopefully something you can learn from.


This server could not verify that you are authorized to access the URL "/project/pathos/login". You either supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
In case you are allowed to request the document, please check your user-id and password and try again.
If you think this is a server error, please contact the webmaster.


by Jake Lazaroff
my job: Parsec
my band: babygotbacktalk
The I in "API" stands for interface!
TypeScript is a statically typed superset of JavaScript that compiles to plain JavaScript.
Everything in a program has a type, like "number" or "function that returns a string".
With static types, we can make sure a program's types work together without even running it.
function square(x: number) {
return x * x;
}
square(2);
square("how YOU doin");
We're gonna go on a whirlwind tour of some cool features of TypeScript and a nifty design pattern.
Unions and intersections are ways of combining different types into one.
In a union, an object of the new type can have properties of either type. In an intersection, an object of the new type will have properties of both types.
let foo: string | number;
foo = "test";
foo = 123;
foo = false;
let obj: { foo: string } & { bar: number };
obj = {
foo: "moo",
bar: 2
};
obj = { foo: "moo" };
Generics let you write your program so that it doesn't know which types it's using ahead of time.
If types were functions, generics would be their arguments.
function concat(x: any[], y: any[]) {
return x.concat(y);
}
const a = [1, 2, 3]; // number[]
const b = [4, 5, 6]; // number[]
const result = concat(a, b);
result; // any[] (we lost the type!)
function concat<T>(x: T[], y: T[]) {
return x.concat(y);
}
const a = [1, 2, 3]; // number[]
const b = [4, 5, 6]; // number[]
const result = concat(a, b);
result; // number[] (the type is safe!)
function concat<T extends { concat(x: T): T }>(x: T, y: T) {
return x.concat(y);
}
const a = [1, 2, 3]; // number[]
const b = [4, 5, 6]; // number[]
const result = concat(a, b);
result; // number[] (works for numbers…)
const a: string = "foo"; // string
const b: string = "bar"; // string
const result = concat(a, b);
result; // string (…and strings!)
Mapped types let you transform one type into another.
They're kinda like map
in normal JavaScript, but for
types.
function stringify<T>(x: T): { [K in keyof T]: string } {
// some code that changes all the object keys to strings
}
const obj = {
foo: 1,
bar: 2
};
const result = stringify(obj);
result; // { foo: string; bar: string; }
The Builder decouples the creation of an object from its internal representation.
It does this by using a separate class to create it, step-by-step.
class Car {
color: string;
doors: number;
}
class CarBuilder {
private car = new Car();
setColor(color: string) {
this.car.color = color;
}
setDoors(doors: number) {
this.car.doors = doors;
}
private getCar() {
return this.car;
}
}
const car = new CarBuilder()
.setColor('red')
.setDoors(2)
.getCar();
To illustrate how these all work together, we're going to create a simple SQL query builder.
interface Schema {
users: {
id: number;
name: string;
age: number;
}
jobs: {
id: number;
name: string;
salary: number;
}
}
const query = new Query<Schema>('users');
const result = query
.select("id")
.select("name")
.exec();
First, we make a Query class that knows the database schema and the table from which it's selecting.
class Query<Schema, Table extends keyof Schema> {
private table: Table;
constructor(table: Table) {
this.table = table;
}
}
Next, we add another generic to the class with the type of the queried result. We also need to keep track of which columns we're selecting.
class Query<Schema, Table extends keyof Schema, Result = {}> {
// ...
private columns: Array<keyof Schema[Table]> = []:
constructor(data: Schema, columns: Array<keyof Schema[Table]>) {
// ...
this.columns = columns;
}
}
Now, the secret sauce: every step of the builder, we intersect the result type with the selected key.
class Query<Schema, Table extends keyof Schema, Result = {}> {
// ...
select<Key extends keyof Schema[Table]>(key: Key) {
type NextResult = Result & { [K in Key]: Schema[Table][K] };
return new Query<Schema, Table, NextResult>(this.table, [
...this.columns,
key
]);
}
}
Finally, we need a method to execute the query.
class Query<Schema, Table extends keyof Schema, Result = {}> {
// ...
exec(): Result[] {
const columns = this.columns.join(', ');
const query = `SELECT ${columns} FROM ${this.table};`;
// some code actually running the query
}
}
interface Schema {
users: {
id: number;
name: string;
age: number;
}
jobs: {
id: number;
name: string;
salary: number;
}
}
const query = new Query<Schema>('users');
const result = new
.select("id")
.select("name")
.exec();
It knows the type of the result!
const foo = new Query<Schema>('users')
.select("id")
.select("name")
.exec();
foo; // Array<{ id: string; name: string }>
const bar = new Query<Schema>('jobs')
.select("salary")
.exec();
bar; // Array<{ salary: number }>
const baz = new Query<Schema>('users').exec();
baz; // Array<{}>
It won't let you select columns that don't exist!
const foo = new Query<Schema>('users')
.select("height")
.result();
(And if you use an editor that supports TypeScript, you'll get autocomplete for the columns names!)


| |
Methods defined here:
- __init__(self, at=0, name='')
- The constructor assigns the inital values to the variables
number of items seen 'n',
column position 'c',
column name 'name',
and data kept 'has'.
- add(self, val)
- Add one thing to 'col'.
For Numerics we can keep at most 'nums' items
- div(self)
- This function finds the entropy for items in 'has'.
It returns the entropy as the output
- mid(self)
- This function finds the mode for items in 'has'.
It takes the column as an input and returns the mode as the output
Data descriptors defined here:
- __dict__
- dictionary for instance variables (if defined)
- __weakref__
- list of weak references to the object (if defined)
|


Welcome to the public GenePattern server. Use of the GenePattern Web Client, GenePattern server, and all modules, pipelines, and suites installed on the server are free for your use. This site and results made available through use of this site should not be used for the medical management of patients. M.I.T. shall not be held responsible for your use of the site. If you are interested in incorporating GenePattern software into another product, or have questions or concerns, please contact us.
Because we make these modules and pipelines available for free, we cannot bear any risk associated with your use of the tools or their results. Further, in order to achieve some protection from unexpected and unforeseeable circumstances, MIT must disclaim its liabilities and damages in accordance with the laws governing software licensing. Please do not allow this legal requirement to discourage your use of the public GenePattern server.
MIT MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE SOFTWARE, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF MERCHANTABILITY, AS TO CONFORMITY WITH WHATEVER LITERATURE MAY BE ISSUED FROM TIME TO TIME, OR ABSENCE OF LATENT OR OTHER DEFECTS, WHETHER OR NOT DISCOVERABLE. MIT EXTENDS NO WARRANTIES OF ANY KIND AS TO THE ACCURACY OF THE SOFTWARE OR ITS COMPLETENESS OR FITNESS FOR ANY PURPOSE. NOTHING IN THIS AGREEMENT SHALL BE CONSTRUED AS A REPRESENTATION MADE OR WARRANTY GIVEN BY M.I.T. THAT THE PRACTICE BY YOU OF THE LICENSE GRANTED HEREUNDER SHALL NOT INFRINGE THE PATENT RIGHTS, COPYRIGHTS, OR OTHER INTELLECTUAL PROPERTY RIGHTS OF M.I.T. OR ANY THIRD PARTY.
IN NO EVENT SHALL MIT, OR ITS TRUSTEES, DIRECTORS, OFFICERS, EMPLOYEES, AND AFFILIATES BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND, INCLUDING, WITHOUT LIMITATION, LOSS OF GOODWILL, ECONOMIC DAMAGES, OR INJURY TO PROPERTY AND LOST PROFITS, REGARDLESS OF WHETHER MIT SHALL BE ADVISED, SHALL HAVE OTHER REASON TO KNOW, OR IN FACT SHALL KNOW OF THE POSSIBILITY OF THE FOREGOING.
If, by operation of law or otherwise, any of the aforementioned warranty disclaimers are determined inapplicable, your sole remedy against MIT, regardless of the form of action, including, but not limited to, negligence and strict liability, shall be replacement of the Software with an updated version if one exists.
In order to use the public GenePattern server, you must first complete the registration form. During registration you are required to give contact information (name, email address). We will not share the information you provide with anyone else or use it to send information to you about anything not directly related to GenePattern.
Jobs that you run on this GenePattern Web Client are submitted to the GenePattern server hosted at the Broad Institute. The server stores the input files, parameter values, and results of the jobs that you run on this site. We do not share this information with other third parties. We may aggregate and analyze log file and database information to determine how the GenePattern software is being used in order to enhance its performance and functionality, including examining jobs and results.
If you choose to add yourself to the GenePattern users mailing list, we will send you information pertaining to GenePattern on rare occasions. For instance, we may notify you of an upcoming release or if our service is temporarily suspended for maintenance. You may opt-out of these communications by choosing to unsubscribe from the mailing list.
If we decide to change our privacy policy, we will post those changes to this privacy statement, the GenePattern web site (http://genepattern.org/), and other places we deem appropriate so that you are aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. We reserve the right to modify this privacy statement at any time. If we make material changes to this policy, we will notify you here, by email, or by means of a notice on the GenePattern web site.


Book with your friends
powered by Make it Social + Skyscanner
Create an event
Create a new event
Destination:
Arrive by:
Short Description:
Image:
Create


DSC Banasthali Vidyapith conducts workshops, seminars and technical showcases for
all. In
addition to workshops, DSC Banasthali Vidyapith also provides an opportunity for
students to
apply their newly gained skills to develop solutions for local problems and then
provide
visibility via Solution Challenge. From learning about new technologies with
resources
provided
by Google Developers to attending talks, events, DevFests and connecting with
developers
around
the world, DSC will help the students to achieve them all.Join the events platform
here


_Automated Pipelines_
_Analysis Priority_
_PIPELINE_TITLE_
_type_
_status_
_Add one below_
_Create new analysis_
Coverage
_Edit_
_cancel_
_save_
_Required Coverage_
N/A
_Required Coverage_
N/A
_Genome Size_
N/A
_Min Coverage_
x
_Max Coverage_
x
_Genome Size_
bp


A CSE undergrad at JNU Jaipur and a motivated programmer and software developer.
I also write blogs so that I can share whatever knowledge I get.
My way of thinking is that education must be free for all because I believe "only education can bring you to success".
I'm also an active member of TEK-Society, a community fully devoted to knowledge and technology.
★ Designed by: Ankur


Your Lists
List 1
View Items In This List
Rename This List
Delete This List
Add Items In This List
List 2
View Items In This List
Rename This List
Delete This List
Add Items In This List
List 3
View Items In This List
Rename This List
Delete This List
Add Items In This List
List 4
View Items In This List
Rename This List
Delete This List
Add Items In This List
Create A New List


Leak Studio
Decks
Cards
Players
Clans
Esports
Player
Clan
Tournament
leakstudio.me
English
Leaks
News
Tournament
GVG
Esports
Strategy
Leak Studio
leakstudio.me
500 × Diamond
Diamond × 500
Claim
customer service
2020 © Nayem Corporation LTD.


一个简单，干净，优雅的所见即所得的富文本编辑器.用鼠标选中文字可看到效果
This jQuery plugin is released under the MIT license. You can check out the project and see how extremely simple it is to use this editor on your application by clicking on the Github ribbon on the top corner of this page. Feel free to contribute with this project by registering any bug that you may encounter as an issue on Github, and working on the issues that are already there. I'm looking forward to seeing your pull request!
Now, just take a time to test the editor. Yes, this div is the editor. Try to edit this text, select a part of this text and don't forget to try the basic text editor keyboard shortcuts.


Food Tracker
Home
Food Tracker
Name:
Description:
Date:
Shelf Life:
Expiration Date:
Name
Description
Date
Shelf Life
Expiration Date


Notification
notification-messages
Service to display notifications, talk to server and change default notification settings.
Method to get the notifications array from server and display them on the top right corner of the window.
In your app controller you can call:
Notification.getFromServer();
...
Notification.getFromServer();
...
Method to get a notification object and display it on the top right corner of the window.
In your app controller you can call:
Notification.notify(note);
where note
is an object that must contain following properties:
| Param | Type | Details |
|---|---|---|
| note | Object | notification object |
...
Notification.notify(
{
id: 1001,
from: 'userManagement',
category: 'warning',
type: 'note',
header: 'Subscrition Info'
content: 'Your subscription expires in 5 days'
}
);
...


| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
L_50_FIELD_NUMBER |
1 |
public static final int |
L_90_FIELD_NUMBER |
2 |
public static final int |
L_99_FIELD_NUMBER |
3 |
public static final int |
L_999_FIELD_NUMBER |
4 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
BODY_FIELD_NUMBER |
2 |
public static final int |
TYPE_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
COMPRESSABLE_VALUE |
1 |
public static final int |
RANDOM_VALUE |
3 |
public static final int |
UNCOMPRESSABLE_VALUE |
2 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
INTERVAL_US_FIELD_NUMBER |
2 |
public static final int |
SIZE_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
NUM_RPCS_FIELD_NUMBER |
4 |
public static final int |
TIME_NOW_FIELD_NUMBER |
1 |
public static final int |
TIME_SYSTEM_FIELD_NUMBER |
3 |
public static final int |
TIME_USER_FIELD_NUMBER |
2 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
PAYLOAD_FIELD_NUMBER |
3 |
public static final int |
RESPONSE_SIZE_FIELD_NUMBER |
2 |
public static final int |
RESPONSE_TYPE_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
PAYLOAD_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
CLIENT_CHANNELS_FIELD_NUMBER |
5 |
public static final int |
CLIENT_THREADS_FIELD_NUMBER |
4 |
public static final int |
ENABLE_SSL_FIELD_NUMBER |
3 |
public static final int |
NUM_RPCS_FIELD_NUMBER |
6 |
public static final int |
PAYLOAD_SIZE_FIELD_NUMBER |
7 |
public static final int |
SERVER_HOST_FIELD_NUMBER |
1 |
public static final int |
SERVER_PORT_FIELD_NUMBER |
2 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
LATENCIES_FIELD_NUMBER |
1 |
public static final int |
NUM_RPCS_FIELD_NUMBER |
2 |
public static final int |
TIME_ELAPSED_FIELD_NUMBER |
3 |
public static final int |
TIME_SYSTEM_FIELD_NUMBER |
5 |
public static final int |
TIME_USER_FIELD_NUMBER |
4 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
TEST_NUM_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
PAYLOAD_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
AGGREGATED_PAYLOAD_SIZE_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
PAYLOAD_FIELD_NUMBER |
3 |
public static final int |
RESPONSE_PARAMETERS_FIELD_NUMBER |
2 |
public static final int |
RESPONSE_TYPE_FIELD_NUMBER |
1 |
| Modifier and Type | Constant Field | Value |
|---|---|---|
public static final int |
PAYLOAD_FIELD_NUMBER |
1 |


Titanium Module for Voice Recognition on Android.
In nature, we can write Voice Recognition routine by the following blog entry, but the code in this entry did not work in Android 2.x and Titanium 2.0.1GA environment. This is because "Ti.Android.currentActivity.startActivityForResult" function does not call callback function correctly.
http://www.matthuggins.com/articles/android-voice-recognition-in-appcelerator-titanium
Using this module, we can get Voice Recognition result correctly on Android 2.x, 3.x Note: I don't test this module on Android 4.x. If you can test it, please let me know the result.
Android min-sdk: Android 2.1 (API Level 7) Titanium 2.0.1GA
To access this module from JavaScript, you would do the following:
var voicerecognition = require("org.mumumu.ti.android.speech");
The voicerecognition variable is a reference to the Module object.
A) Download org.mumumu.ti.android.speech-android-0.1.zip and place it to your Titanium project root.
B) add the following setting to tiapp.xml between
<android xmlns:android="http://schemas.android.com/apk/res/android">
<manifest>
<application>
<activity android:name="org.mumumu.ti.android.speech.VoiceRecognitionActivity" />
</application>
</manifest>
</android>
<modules>
<module version="0.1">org.mumumu.ti.android.speech</module>
</modules>
C) Invoke the module code.
if (Ti.Platform.name == "android") {
var speechModule = require('org.mumumu.ti.android.speech');
var voiceRecognitionProxy = speechModule.createVoiceRecognition();
voiceRecognitionProxy.callback = function (e) {
var voice_recognition_enabled = e.voice_enabled;
var voice_results = e.voice_results;
if (e.voice_canceled) {
alert("voice recognition canceled");
} else {
if (!voice_recognition_enabled) {
alert("voice recognition seems to be disabled");
} else {
alert(voice_results[0]);
}
}
};
voiceRecognitionProxy.voiceRecognition();
}
Yoshinari Takaoka (reversethis -> gro tod umumum ta umumum)
BSD License. See License.txt for details.


WinHEC 99 White Paper
|
Windows® Hardware
Engineering Conference: |
|
Windows 2000 Instrumentation: WMI and ACPI
Abstract
This paper describes the process that system manufacturers (OEMs) can use to provide instrumentation information by including ACPI objects in the systems they build that will be recognized by Microsoft® Windows® Management Instrumentation (WMI). This information applies for Windows 2000 and Windows 98 OSR 1. By including ACPI objects in the systems they build, OEMs can take advantage of a generic mapping driver that allows WMI to make the information available to the instrumentation consumers.
The ACPI subsystem contains a wealth of instrumentation information; OEMs are encouraged to use ACPI to add additional platform specific instrumentation information. However, ACPI objects are not readily accessible by instrumentation data consumers such as Web-Based Enterprise Management (WBEM).
This paper assumes the reader is familiar with driver mapping under Windows operating systems and the Data Block GUID Mapping control method for WMI. References for background and details are cited at http://www.microsoft.com/hwdev/manageability/; ACPI implementation information is available at http://www.teleport.com/~acpi/.
March 12, 1999
Disclaimer and Copyright
Microsoft Disclaimer: This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Microsoft Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to the patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Microsoft Corporation.
Microsoft does not make any representation or warranty regarding specifications in this document or any product or item developed based on these specifications. Microsoft disclaims all express and implied warranties, including but not limited to the implied warranties or merchantability, fitness for a particular purpose and freedom from infringement. Without limiting the generality of the foregoing, Microsoft does not make any warranty of any kind that any item developed based on these specifications, or any portion of a specification, will not infringe any copyright, patent, trade secret or other intellectual property right of any person or entity in any country. It is your responsibility to seek licenses for such intellectual property rights where appropriate. Microsoft shall not be liable for any damages arising out of or in connection with the use of these specifications, including liability for lost profit, business interruption, or any other damages whatsoever. Some states do not allow the exclusion or limitation of liability or consequential or incidental damages; the above limitation may not apply to you.
Microsoft, DirectX, MS‑DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Other product and company names mentioned herein may be the trademarks of their respective owners.
© 1999 Microsoft Corporation. All rights reserved.
Contents
Technology Overview for Windows 2000 Instrumentation....................................................................................... 3
WMI Overview for Windows 2000 Instrumentation................................................................................................... 3
ACPI-to-WMI Mapper Goals for Windows 2000 Instrumentation........................................................................... 4
ACPI Control Method Naming Conventions and Functionality for Windows 2000 Instrumentation................ 5
Data Block Design for Windows 2000 Instrumentation............................................................................................. 8
FAQ about WMI and ACPI for Windows 2000 Instrumentation........................................................................... 11
ASL Methods and Sample Code.................................................................................................................................. 11
ASL Sample Code for an Event and Initiating Method...................................................................................... 12
Sample ASL Code Embedding MOD Data in ASL.............................................................................................. 14
Sample .Mof File....................................................................................................................................................... 17
The ACPI-to-WMI mapping functionality is achieved by means of two device drivers provided with the Windows 2000 and Windows 98 OSR1 operating systems:
· Acpi.sys is the regular ACPI device driver with some modifications.
· Wmiacpi.sys registers with Plug and Play ID PNP0c14.
OEMs can differentiate their PC system capabilities by writing ACPI Source Language (ASL) code and a Managed Object Format (.mof or MOF) file. The .mof file can be in the BIOS or on disk. For more information about MOF, see the “MOF Data Types” section later in this paper.
ASL code is never executed directly by the Wmiacpi.sys driver. ASL code is always executed by the Acpi.sys driver (see the ASL information at http://www.teleport.com/~acpi/). Wmiacpi.sys will invoke Acpi.sys to call control methods that access the management data exposed by the mapping driver.
Microsoft does not ship a .mof file that is associated with the Wmiacpi.sys driver. The only information surfaced through ACPI is the temperature zone information, which is surfaced through and associated with the Acpi.sys device driver.
WMI organizes individual data items (properties) into data blocks (structures) that contain related information. Data blocks may have one or more data items. Each data item has a unique index within the data block, and each data block is named by a globally unique 128-bit number called a globally unique identifier (GUID). WMI can provide notifications to the data producer as to when to start and stop collecting the data items that compose a data block. WMI has no knowledge of the data format for individual data blocks.
WMI functionality allows for querying all instances of a data block or a single instance of a data block. It also allows for setting all data items in an instance of a data block or a single data item within a single instance of a data block.
In addition to queries and sets, WMI allows WMI method calls, which are functionally equivalent to an I/O control (IOCTL) call to a device. Each WMI method call is identified by a GUID and a method index for that GUID. All WMI method calls use one buffer for input and output parameters. WMI allows notifications of significant events to be delivered to interested user-mode applications. Each type of event is uniquely named by a GUID. Events may also carry a data block with additional information about the event. WMI can provide notifications to the event generator about when to enable and disable an event type.
WMI is an open architecture that allows OEMs to define their own data blocks, methods, and events. Along with the data that composes the custom data block, the OEM must also provide a description that generally represents how a data block or WMI method is mapped to a 2-character ID. This 2‑character ID is part of the names of the control methods that act upon the data block.
For example, when a call is made to query about the data block represented by a WMI GUID, the mapper will evaluate the WQxx control method (where xx is the 2-character ID mapped to that GUID). These mappings are defined by the ACPI code and obtained by the mapper evaluating the _WDG control method. For more information, see “ACPI Control Method Naming Conventions and Functionality” later in this paper.
The mapping process is similar for events. The _WDG control method provides a mapping between the WMI event GUID that represents the event and the notification code specified in the ASL notify instruction. For example, when ACPI provides a callback to the mapper that a control method executed a notify(mapper-device, 0x81) function, the mapper will look up the WMI GUID mapped to 0x81 and use this WMI GUID in building the WMI event. Before launching the WMI event, the mapper will evaluate _WED to retrieve any additional data that belongs with the event.
Loading the Mapping Driver. The Plug and Play ID PNP0c14 is assigned as the WMI-mapping pseudo device; the operating system device INFs (Plug and Play ID-to-device driver lookup table) point this Plug and Play ID to the ACPI-to-WMI mapping driver. To cause the ACPI-to-WMI mapping driver to load, an ACPI system needs to define one or more devices with that Plug and Play ID in the ACPI device tree. Each device declared in the ACPI device tree would have its own operating system device object with its own set of mappings.
In this way, different sets of data blocks can be organized in the appropriate place within the device tree.  Note that if there are multiple WMI-mapping pseudo devices in the ACPI device tree, each device must have a unique value for its _UID.
Mapping Driver Functionality. Essentially the mapping driver will do the following:
· Manage all registration and unregistration with WMI and other interactions with the operating system. This registration of data and data blocks is done when the mapper gets the IRP_MN_REGINFO IRP.
· At WMI initialization time, the mapping driver will query an ACPI method for the list of data block, event, and method GUIDs it supports, as well as the mapping from the GUID to control method IDs. With this information, the mapping driver will register those GUIDs with WMI.
· Translate data block queries, sets, and method call I/O IRPs into the appropriate ACPI control method call.
· Receive notifications from the ACPI event handler control methods and relaunch them as WMI events.
· Translate strings between ASCIZ and UNICODE for data blocks marked as wholly composed of a string.
The following list describes the goals for the ACPI-to-WMI mapper:
· Expose data maintained by the hardware or firmware and accessible through ACPI to user-mode instrumentation data consumers, such as WBEM or DMI.
· Allow specific ACPI control methods to be called from a user-mode instrumentation data consumer or hardware configuration application—for example, from a control panel applet.
· Deliver specific ACPI events to all user-mode callers that request notification of that particular event.
· Allow OEMs to include OEM-specific data blocks, user-mode–callable ACPI control methods, and events without requiring any changes to the ACPI-to-WMI mapper.
· Allow general-purpose data consumer applications—those written without any special knowledge of the data blocks exposed by a particular machine—to be able to access and understand the data blocks, user-mode–callable ACPI control methods, and events being mapped—including those that are OEM specific.
· Define standard data block formats, user-mode–callable ACPI control methods, events and their WMI GUID mappings for common data blocks, and callable control methods and events expected to be provided by all OEMs. This can include dynamic data and functions identified by the industry in the SMBIOS specification and other specifications.
These goals are achieved by having supporting code in the ACPI-to-WMI mapper (Wmiacpi.sys) as well as in the core ACPI code itself (Acpi.sys).
The following are not goals for the ACPI-to-WMI mapper:
· To have specific knowledge about any data block that passes through the mapper.
· To provide interfaces specifically for SMBIOS data and functions. The mapper is an open architecture that is not restricted to SMBIOS data and functionality.
How SMBIOS-provided information is handled. Vendors who want to provide OEM and system-specific instrumentation data may choose to use SMBIOS as the mechanism. To use the capabilities of the WMI infrastructure to surface this SMBIOS data, they must conform to any SMBIOS version between 2.0 and 2.2. (Microsoft intends to support future revisions of SMBIOS as and when they appear. To date, we have only one SMBIOS 2.2 machine for testing). This allows the Microsoft Win32® provider—which is shipped with Windows 2000 and future versions of Windows and is available as an update to Windows 98—to populate almost all of the SMBIOS-provided information into the CIMv2 namespace. In particular, almost all of the information is put into Win32 classes. Some of these Win32 classes are derived from the CIMv2.1 physical MOF.
The one exception where SMBIOS information will not be automatically populated by the Win32 provider into the CIMv2 namespace is SMBIOS vendor-specific data. Such SMBIOS vendor-defined data will be placed in a “VendorBucket” class in a “Root\VendorDefined” namespace, and will not be available in the CIMv2 namespace by default. Any system vendor who wants to provide such data must write a provider that will interpret this data.
The SMBIOS data is read only once, either at boot time in Windows 2000 or post boot on Windows 98. Dynamic updates that are made to the SMBIOS data after it has been read will not be reflected in the namespaces in this implementation. Microsoft is working with the industry to define standard ACPI methods for dynamic updates.
The SMBIOS raw data will be available as a WMI data block in Windows 2000 and as a flat file in Windows 98. This data will be interpreted and populated into the namespaces by the Win32 provider.
Note: The Win32 provider capabilities used to read and populate SMBIOS data as described above will be available in Windows 2000 Beta 3.
The Data Block GUID Mapping control method named _WDG evaluates to a buffer that has the GUID mapping information for data blocks, events, and WMI methods. The result of the evaluation is a buffer containing an array of the following structure.
typedef struct
{
GUID guid; // GUID that names data block
union
{
CHAR ObjectId[2]; // 2-character ACPI ID (Data Blocks and Methods)
struct
{
UCHAR NotificationValue; // Byte value passed by event handler control method
UCHAR Reserved[1];
} NotifyId;
}
USHORT InstanceCount; // Number of separate instances of data block
USHORT Flags; // Flags
};
// Set this flag if the WCxx control method should be run to whenever the first
// data consumer is interested in collecting the data block and whenever the last data
// consumer is no longer interested.
#define WMIACPI_REGFLAG_EXPENSIVE 0x1
// Set this flag if the GUID represents a set of WMI method calls and not a data block
#define WMIACPI_REGFLAG_METHOD 0x2
// Set this flag if the data block is wholly composed of a string and should be
// translated from ASCIZ to UNICODE in returning queries and from UNICODE to ASCIZ
// when passing sets
#define WMIACPI_REGFLAG_STRING 0x04
// Set this flag if the guid maps to an event rather than a data block or method
#define WMIACPI_REGFLAG_EVENT 0x08
Each element in the array describes the mapping of a WMI data block GUID to a 2-letter ACPI method identifier used to compose the method names that operate on the data block or on the notification value used in the ASL Notify operation. Each element of the array also contains the number of instances of the data block that exist and any flags that are set.
This control method is required.
Control Method Summary
|
Control method |
Object name |
Parameters |
Control method required |
|
Data Block Query |
WQxx |
ULONG |
Yes. |
|
Data Block Set |
WSxx |
ULONG, buffer |
No. Not required for data blocks that are read only. |
|
Data Item Set |
Not supported |
|
|
|
Method Execution |
WMxx |
ULONG, method ID, |
Yes. Required for data blocks specified in the data block GUID mapping array and that have the WMIACPI_REG_METHOD flag set. |
|
Event Enable and Disable |
WExx |
UCHAR |
No. Support only when keeping the event enabled incurs significant overhead. |
|
Data Collection |
WCxx |
UCHAR |
No. Support only when data collecting for the data block incurs significant overhead. |
· Data Block Query Control Method. If the Data Block GUID Mapping control method describes a data block that does not have the WMIACPI_REG_METHOD flag set, there needs to be a control method that evaluates to the contents of an instance of the data block.
By convention, the name of the object is WQxx, where xx is the 2-character ID that maps to the GUID being queried. One parameter is passed to the method—the index of the instance, which is of type ULONG. Data blocks registered with only a single instance can ignore the parameter. If the result of the evaluation of the WQxx method is a string, then the mapper will convert that string to UNICODE so that it can be understood by WMI.
This control method is required.
· Data Block Set Control Method. If the Data Block GUID Mapping control method describes a data block that does not have the WMIACPI_REG_METHOD flag set, there needs to be a control method that evaluates to the contents of an instance of the data block.
By convention, the name of the object is WSxx, where xx is the 2-character ID that maps to the GUID being set. Two parameters are passed to the method; one is a ULONG that is the index of the instance, and the other is a buffer that contains the new values for the data block.
If the GUID for the data block is registered with the WMIACPI_REGFLAG_STRING flag, then the mapper assumes that the data block passed is wholly composed of a single string and will convert that string from UNICODE to ASCIZ so that it can be understood by the WSxx control method.
This control method is not required for those data blocks that are read only.
Because the mapper is unaware of the format of the data block passed by the caller of the WMI method, it will pass the buffer as a single buffer parameter to the WMxx control method. The control method can use the ASL instructions CreateBitField, CreateDWordField, CreateField, and CreateWordField to break up the buffer into its parts
· Data Item Set Control Method. Setting of individual data items within a data block is not supported. Typically, data items that can be modified should be placed in their own data block or the entire data block should be modified.
· Method Execution Control Method. If the Data Block GUID Mapping control method describes a data block that does have the WMIACPI_REG_METHOD flag set, there needs to be a control method that performs the action required of the method.
By convention, the name of the control method is WMxx, where xx is the 2-character ID that maps to the GUID. This method call has three parameters; the first is a ULONG that has the instance index being executed; the second contains the method ID for the method being executed; and the third is a buffer that contains the input for the method call.
If the GUID for the WMI method is registered with the WMIACPI_REGFLAG_STRING flag, then the mapper assumes that buffer passed in is a string. The mapper will convert the incoming string from UNICODE to ASCIZ.
If the result of the WMxx control method is a string, the mapper will convert the result string from ASCIZ to UNICODE. The return value of the WMxx method should be a buffer with the result of the method call.
This control method is required for those data blocks specified in the Data Block GUID Mapping array that have the WMIACPI_REG_METHOD flag set.
Because the mapper is unaware of the format of the data block passed by the caller of the WMI method, it will pass the buffer as a single buffer parameter to the WMxx control method. The control method can use the ASL instructions CreateBitField, CreateDWordField, CreateField, and CreateWordField to break the buffer into its parts.
· Event Enable and Disable Control Method. For each event specified in the Event GUID Mapping control method that has the WMIACPI_REG_EXPENSIVE flag set, there needs to be a control method that is invoked whenever launching of the event should be enabled and disabled.
By convention, the control method is named WExx, where xx is the hex value of the notification code passed by the event handler control method. This method has one parameter, a UCHAR that has a value of 0 if the event is to be disabled or a nonzero value if it is to be enabled.
This method is optional and should only be supported if keeping the event enabled incurs significant overhead.
· Data Collection Enable and Disable Control Method. For each data block described in the Data Block GUID Mapping control method that has the WMIACPI_REG_EXPENSIVE flag set, there needs to be a control method that is invoked whenever collection of the data that composes the data block should be enabled and disabled
By convention, the control method is named WCxx, where xx is the 2-character ID that maps to the GUID. This method has one parameter, a UCHAR that has a value of 0 if data block collection is to be disabled or a nonzero value if it is to be enabled.
This method is optional and should only be supported if collecting the data for the data block incurs significant overhead.
· Additional Event Data. The _WED control method is evaluated by the mapper in response to receiving a notification from a control method. The results of the evaluation are passed as part of the WMI event information. This mechanism allows additional data to be included with an event.
The control method takes one parameter, which is the notification code that caused the notification to occur. If the result of the _WED control method is a string, then the string is converted from ASCIZ to UNICODE before launching the WMI event.
Design Considerations. Consider the following in designing data blocks for instrumentation under Windows 2000:
· Data items that are read-only and are commonly used together should be combined into a single data block.
· Data items that are strings must be segregated into their own data block and registered with the WMIACPI_REGFLAG_STRING flag set so that the mapper can convert between ASCIZ and UNICODE.
· Data items that can be set individually should be segregated into their own data blocks. For example, a set of data items that must be set all at the same time can be combined into a single data block.
MOF Data Types. The Managed Object Format (MOF) for the data blocks implemented can be supplied as either a resource attached to a file or as the buffer that results from the evaluation of a control method. To establish the former, either bind the resource to the Wmiacpi.sys image or establish a REG_EXPAND_SZ registry value named MofImagePath under the WMIACPI service key. The contents of the value is a path to the image file that contains the resource. In either case, the resource must be named MofResourceName.
The buffer resulting from the evaluation of the WQxx control method assigned to the binary MOF GUID describes all data blocks, WMI methods, and events for the device in a compressed binary format. This binary data is created by building a text file using the MOF language and compiling it with the MOF compiler.
MOF data types are very rich. MOF supports the basic data types of 8-, 16-, 32-, and 64-bit signed and unsigned integers, Boolean terms, floating points, strings, and UTC datetimes. Embedded classes—that is, structures that can contain basic data types and other embedded classes—are also supported. In addition, fixed and variable length arrays of basic data types and embedded classes are supported.
The MOF language defines the data types shown in the following table.
MOF Data Types
|
Data types |
Data format |
|
String |
Null terminated ANSI string |
|
sint32 |
Signed 32-bit integer |
|
uint32 |
Unsigned 32-bit integer |
|
sint16 |
Signed 16-bit integer |
|
uint16 |
Unsigned 16-bit integer |
|
sint64 |
Signed 64-bit integer |
|
uint64 |
Unsigned 64-bit integer |
|
sint8 |
Signed 8-bit character |
|
uint8 |
Unsigned 8-bit integer |
|
Datetime |
25-character string used to specify absolute dates or time intervals. |
|
Boolean |
Byte where 0 is FALSE, != 0 is TRUE |
Important: Because the MOF data types are much richer than those for ACPI control methods, the control method must be careful to pack the data blocks correctly within an ACPI buffer. The control method can also restrict itself to using only common data types.
Each MOF class represents a data block and may contain one or more properties that represent data items within the data block. A MOF class would hold all information needed to parse a data block returned from the mapper. In addition, the MOF language allows rich meta-data to be included as qualifiers on properties and classes. Some qualifiers are required, but most are optional.
Class and data item qualifiers are defined in the following table.
Class and Data Item Qualifiers
|
Qualifier |
Description |
|
|
Class qualifiers: |
|
|
|
[guid(“guid-string”)] |
Declares the GUID that represents the class within WMI. This qualifier is required. |
|
|
[Dynamic] |
Required for WBEM. |
|
|
[WMI] |
Required for WBEM. |
|
|
[Provider(“WmiProv”)] |
Required for WBEM. |
|
|
[Description(“description-text”)] |
Specifies description text for the class or property in the locale specified for the locale qualifier. |
|
|
[WmiExpense(expense-value)] |
Specifies the quantity of system resources required in order to collect data in the data block; expense-value is defined to be the average number of CPU cycles needed to collect the data block. If this qualifier is not specified, then the expense-value is assumed to be 0. |
|
|
Data item qualifiers: |
|
|
|
[read] |
Specifies that the data item may be read. |
|
|
[write] |
Specifies that the data item may be written. |
|
|
[WmiDataID(data-item-ID)] |
Specifies the data item ID for the data item. This qualifier is required. |
|
|
[WmiScale(scale-factor)] |
Specifies the scaling factor to use when displaying the data. Before displaying the data returned from a query of the data item, it is multiplied by 10 to the power of scale-factor. If this qualifier is not specified, then the scale-factor is assumed to be 0. |
|
|
[WmiComplexity(“complexity-category”)] |
Specifies the level of detail associated with the counter. Complexity-category can have the value of “Novice” for the information that anyone can understand, “Advanced” for information that is useful for advanced users, “Expert” for information that is useful to only expert users, and “Wizard” for information that is useful for the data provider designer. If this qualifier is not specified, then a complexity-category of “Novice” is assumed. |
|
|
[WmiVolatility(validity-interval)] |
Specifies how often this data item value is updated internally. Validity-interval is defined in units of milliseconds, so a validity-interval of 1000 would mean that the data item is updated internally every second. Data consumers can use this measure to determine how frequently it should poll for changes in a data item. If this qualifier is not specified, then no assumption on the length of validity for a data item can be made. |
|
|
[WmiSizeIs(“property-name”)] |
Specifies the property within the current class that has the count of the number of array elements (not bytes) contained in a variable length array. |
The order that the data items are laid out in the data block is controlled by the data item ID. Data item IDs must be allocated contiguously starting with data item ID 1. The data item order specified in the MOF is not relevant.
MOF supports arrays of the basic types shown in the “MOF Data Types” table shown earlier. A variable sized array must have a WmiSizeIs() qualifier that specifies the property that has the number of elements in the array.
Data Block Format. The format of the data block buffer returned from the query control method and passed into the set control method must be consistent with the description of it specified by the MOF for that data block with respect to the order and size of the data items within the data block. The Boolean data type is 1 byte in length and has a value of 0 for FALSE and non-zero value for TRUE. The string data type is a C-style ANSI null-terminated string.
Standard Data Blocks, Methods, and Events. Additional data blocks, events, and methods will be defined in the future; they should be implemented by all OEMs in order to ensure a minimum of functionality on all PCs. In the future, an industry standard will be defined for the globally unique GUIDs to be assigned to the data blocks. The WMI component within Windows will contain the MOF definition for these standard data blocks so it does not need to be part of the result from the binary .mof query.
Custom Data Blocks, Methods and Events. Custom or OEM-specific data blocks, events, and methods can be added by including them in the result of the _WDG method. The GUIDs that are assigned must be globally unique so they can be generated by a tool such as Guidgen or Uuidgen, which are provided with the WMI information in the Microsoft Platform SDK.
The MOF definition for these custom data blocks must be included in the results of the WQxx method, where xx has been mapped to the MOF Data GUID, which is the GUID that is queried and returns MOF data—in order for applications to be able to access the data blocks. Or the MOF could be added as a resource to Wmiacpi.sys with a name of MofResourceName and a type MOFDATA. It can also be a resource in another image file with same name and type that is pointed to by the MofImagePath value in the registry key HKLM\CurrentControlSet\Services\WmiAcpi
How does WMI find ACPI/ASL code?
In ASL, the developer creates a device with an _HID of PNP0c14. The operating system enumerates the device and loads the Wmiacpi.sys driver on top of it.
How does the MOF associated with ACPI BIOS get registered?
It is either a resource attached to Wmiacpi.sys or another image file such as a resource-only DLL.
How does a management application discover the classes and properties provided by ASL instrumentation?
By looking in the WMI namespace of the schema.
Is the following true? Because very few ACPI standards exist for instrumentation, most of the ACPI instrumented features will appear differently on each vendor’s product, and management applications will have to be “taught” to interpret the varying classes and methods.
Microsoft is looking at standardizing this. Any suggestions are appreciated.
Who provides the .mof files for standard ACPI features such as thermal monitoring?
Windows 2000 has a .mof file for thermal zone temperature as part of the operating system and instruments it within Acpi.sys, outside of the mapper.
Typically, .mof files are compiled into .bmf files and attached to a driver as a resource. The .bmf files can be in the ROM or on disk. WMI determines the location of the .mof information by looking at the registry for the MofImagePath value under the WMIACPI service. If this does not exist, then WMI looks at the ImagePath value. If Wmiacpi.sys does not have a .mof resource, then WMI will query the binary .mof GUID for the .mof information.
A driver may have a static list of pre-built .mof files; if so, it can “dynamically” report one of them. The mechanism is to report the file using a predefined GUID that returns a binary .mof.
To dynamically build a .mof file, a driver would have to build a .mof file and then launch the .mof compiler, which is difficult. Currently, to do this on the machine running Wmiacpi.sys, the mofcomp command can be used to load the .mof file directly into the CIMOM database.
The following list represents some of the ASL methods defined by the ACPI specification. These methods are of particular interest for systems management. None of these methods have been implemented yet within the WMI/ACPI mapper to date. A BIOS developer, for example, could use these methods to expose data using the mapper. These methods represent good opportunities for OEMs to differentiate their products with minimal effort:
· _ACX — Temperature threshold at which various degrees of active cooling are engaged
· _CRT — Critical temperature at which system will shut down
· _PSV — Temperature at which system will throttle CPU in order to cool system
· _LID — Status of the lid (open or closed)
· _PSR— Whether the machine running on AC
The same applies for these method for Control Method Battery devices:
· _BIF — Battery information such as model, serial number, design capacity, last full charge capacity, technology, and battery capacity
· _BST — Battery state, battery present rate, battery remaining capacity, and battery voltage present
The following ASL code implements an event and a method that can be called to initiate that event.
Device(AMW0)
{
// pnp0c14 is Plug and Play ID assigned to WMI mapper
Name(_HID, "*pnp0c14")
Name(_UID, 0x0)
//
// Description of data and events supported
Name(_WDG, Buffer() {
0x6a, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
66, 65, // Object ID (BA)
3, // Instance Count
0x01, // Flags (WMIACPI_REGFLAG_EXPENSIVE)
0x6b, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
66, 66, // Object ID (BB)
3, // Instance Count
0x02, // Flags (WMIACPI_REGFLAG_METHOD)
0x6c, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
0xb0, 0, // Notification ID
1, // Instance Count
0x08 // Flags (WMIACPI_REGFLAG_EVENT)
})
//
// Storage for the 3 instances of BA
Name(STB0, Buffer(0x10) {
1,0,0,0, 2,0,0,0, 3,0,0,0, 4,0,0,0
})
Name(STB1, Buffer(0x10) {
0,1,0,0, 0,2,0,0, 0,3,0,0, 0,4,0,0
})
Name(STB2, Buffer(0x10) {
0,0,1,0, 0,0,2,0, 0,0,3,0, 0,0,4,0
})
//
// Query data block
// Arg0 has the instance being queried
Method(WQBA, 1) {
if (LEqual(Arg0, 0)) {
Return(STB0)
}
if (LEqual(Arg0, 1)) {
Return(STB1)
}
if (LEqual(Arg0, 2)) {
Return(STB2)
}
}
//
// Set Data Block
// Arg0 has the instance being queried
// Arg1 has the new value for the data block instance
Method(WSBA, 2) {
if (LEqual(Arg0, 0)) {
Store(Arg1, STB0)
}
if (LEqual(Arg0, 1)) {
Store(Arg1, STB1)
}
if (LEqual(Arg0, 2)) {
Store(Arg1, STB2)
}
}
//
// Storage for data block BB
Name(B0ED, Buffer(0x10) {
0,0,0,1, 0,0,0,2, 0,0,0,3, 0,0,0,4
})
//
// Method Execution
// Arg0 is instance being queried
// Arg1 is the method ID
// Arg2 is the method data passed
Method(WMBB, 3) {
if (LEqual(Arg1, 1))
{
Store(Arg3, B0ED)
Notify(AMW0, 0xB0)
Return(Arg3)
} else {
Return(Arg1)
}
}
//
// More info about an event
// Arg0 is the event ID that was launched (“fired”)
Method(_WED, 1) {
if (LEqual(Arg0, 0xB0)) {
Return(B0ED)
}
}
}
The following sample ASL code shows another example of implementing an event mechanism using ASL code. It also provides an example of embedding MOF data into ASL.
Device(AMW0)
{
//
// pnp0c14 is the ID assigned by Microsoft to the WMI to ACPI mapper
Name(_HID, "*pnp0c14")
Name(_UID, 0x0)
//
// _WDG evaluates to a data structure that specifies the data blocks supported
// by the ACPI device.
Name(_WDG, Buffer() {
0x5a, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
65, 65, // Object ID (AA)
2, // Instance Count
0x01, // Flags WMIACPI_REGFLAG_EXPENSIVE
0x5b, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
65, 66, // Object ID (AB)
2, // Instance Count
0x02, // Flags WMIACPI_REGFLAG_METHOD
0x5c, 0x0f, 0xBC, 0xAB, 0xa1, 0x8e, 0xd1, 0x11, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10, 0, 0,
0xa0, 0, // Notification ID
1, // Instance Count
0x08, // Flags (WMIACPI_REGFLAG_EVENT)
//
// This GUID for returning the MOF data
0x21, 0x12, 0x90, 0x05, 0x66, 0xd5, 0xd1, 0x11, 0xb2, 0xf0, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10,
66, 65, // Object ID (BA)
1, // Instance Count
0x00, // Flags
})
//
// Collection control method. If Arg0 is not zero then collection for the
// data block is enabled. If Arg0 is zero then collection is disabled. If
// this method does not exist then it is assumed that collection control is
// not required. Collection control is only useful when collection of the
// data block causes overhead.
Method(WCAA, 1) {
if (LEqual(Arg0, Zero)) {
// Disable collection of data
} else {
// Enable collection of data
}
}
//
// Query method for data block AA. Arg0 has the data block instance index
Method(WQAA, 1) {
if (LEqual(Arg0, Zero)) {
// Query is for first instance of data block
return(0x10)
} else {
// Query is for second instance of data block
return(0x20)
}
}
//
// Set method for data block AA. If data block is read-only then this method
// does not need to exist. Arg0 has the instance index of the data block,
// Arg1 has the new value for the data block.
Method(WSAA, 2) {
if (LEqual(Arg0, Zero)) {
// Set is for first instance of data block
} else {
// Set is for second instance of data block
}
}
//
// Event enable/disable method. If event does not need to be armed/disarmed
// then this method is not needed. Arg0 is Zero if event is being disarmed or
// non zero if event is being armed.
Name(ACEN, 0)
Method(WEA0, 1) {
Store(Arg0, ACEN)
}
//
// _WED is called in response to an event launching (“firing”) to gain additional
// information about the event. Arg0 has the NotifyId for the event launched.
Method(_WED, 1) {
if (LEqual(Arg0, 0xA0)) {
Return(0x100)
}
}
//
// Evaluation of this method causes the event 0xA0 to be fired. Since it is
// defined by the _WDG method it is callable via WMI. Arg0 has the instance
// index and Arg1 has any input parameters.
Method(WMAB, 3) {
//
// If event was armed then launch it
if (LEqual(ACEN, 1)) {
Notify(AMW0, 0xa0)
}
Return(Arg1)
}
Name(WQBA, Buffer(926) {
0x46, 0x4f, 0x4d, 0x42, 0x01, 0x00, 0x00, 0x00, 0x8e, 0x03, 0x00, 0x00, 0xf6, 0x0f, 0x00, 0x00,
0x44, 0x53, 0x00, 0x01, 0x1a, 0x7d, 0xda, 0x54, 0x98, 0xdd, 0x87, 0x00, 0x01, 0x06, 0x18, 0x42,
0x10, 0x0b, 0x10, 0x0a, 0x0b, 0x21, 0x02, 0xcb, 0x82, 0x50, 0x3c, 0x18, 0x14, 0xa0, 0x25, 0x41,
0xc8, 0x05, 0x14, 0x55, 0x02, 0x21, 0xc3, 0x02, 0x14, 0x0b, 0x70, 0x2e, 0x40, 0xba, 0x00, 0xe5,
0x28, 0x72, 0x0c, 0x22, 0x82, 0xfd, 0xfb, 0x07, 0xc1, 0x90, 0x02, 0x08, 0x29, 0x84, 0x90, 0x08,
0x58, 0x2a, 0x04, 0x8d, 0x10, 0xf4, 0x2b, 0x00, 0xa1, 0x43, 0x01, 0x32, 0x05, 0x18, 0x14, 0xe0,
0x14, 0x41, 0x04, 0x41, 0x62, 0x17, 0x2e, 0xc0, 0x34, 0x8c, 0x06, 0xd0, 0x36, 0x8a, 0x64, 0x0b,
0xb0, 0x0c, 0x2e, 0x98, 0xa3, 0x08, 0x92, 0xa0, 0xc6, 0x09, 0xa0, 0xc4, 0x4c, 0x00, 0xa5, 0x13,
0x5c, 0x36, 0x05, 0x58, 0xc4, 0x96, 0x50, 0x14, 0x0d, 0x22, 0x4a, 0x82, 0x13, 0xea, 0x1b, 0x41,
0x13, 0x2a, 0x57, 0x80, 0x64, 0x78, 0x69, 0x1e, 0x81, 0xac, 0xcf, 0x41, 0x93, 0xf2, 0x04, 0xb8,
0x9a, 0x05, 0x7a, 0x8c, 0x34, 0xff, 0x30, 0x41, 0x99, 0x14, 0x43, 0x0e, 0x20, 0x24, 0x71, 0x98,
0xa0, 0x9d, 0x59, 0xed, 0x18, 0xd2, 0x3d, 0x07, 0x32, 0x4d, 0x60, 0x21, 0x70, 0x9e, 0xb8, 0x19,
0xa0, 0xf0, 0x5b, 0x1d, 0x80, 0xe0, 0x2b, 0x1d, 0x15, 0xd2, 0xeb, 0x34, 0x64, 0x72, 0x46, 0x48,
0xf8, 0xff, 0x7f, 0x02, 0x26, 0xe3, 0xb7, 0x60, 0x02, 0xa5, 0xd9, 0xb2, 0x82, 0x4b, 0x80, 0xc1,
0x68, 0x00, 0x91, 0xa2, 0x69, 0xa3, 0xe6, 0xea, 0xf9, 0x36, 0x8f, 0xaf, 0x59, 0x7a, 0x9e, 0x47,
0x7a, 0x34, 0x56, 0x36, 0x05, 0xd4, 0xf8, 0x3d, 0x9d, 0x93, 0xf3, 0x4c, 0x02, 0x1e, 0x9c, 0x61,
0x4e, 0x87, 0x83, 0xf1, 0xb1, 0xb1, 0x51, 0x70, 0x74, 0x03, 0xb2, 0x31, 0x38, 0xc6, 0xb0, 0xd1,
0x73, 0x39, 0x81, 0x47, 0x82, 0x43, 0x89, 0x7e, 0x0e, 0x6f, 0x00, 0x47, 0x17, 0xe3, 0x04, 0xce,
0x27, 0xc1, 0x61, 0x06, 0x39, 0xe3, 0x33, 0xf4, 0x44, 0x2c, 0x68, 0xd6, 0x02, 0x0a, 0x62, 0xa4,
0x58, 0xa7, 0xf5, 0x7c, 0x10, 0x8b, 0x41, 0x05, 0x8b, 0x11, 0xdb, 0x50, 0x87, 0x60, 0x18, 0x8b,
0x46, 0x11, 0xc8, 0x49, 0x3c, 0x49, 0x30, 0x94, 0x40, 0x51, 0x0c, 0x12, 0xda, 0xc3, 0x36, 0x92,
0x81, 0xcf, 0xdb, 0x20, 0xc7, 0x84, 0x51, 0x01, 0x21, 0xcf, 0xe3, 0xd0, 0x28, 0x4d, 0xd0, 0xfd,
0x29, 0x40, 0x37, 0x8b, 0x08, 0x67, 0x54, 0xd8, 0x44, 0x64, 0x6d, 0x02, 0xb2, 0x25, 0x40, 0x1c,
0xbe, 0x40, 0x1a, 0x43, 0x11, 0x44, 0x84, 0x98, 0x51, 0x8c, 0x19, 0x30, 0x82, 0x51, 0x0e, 0xa6,
0x39, 0x10, 0x69, 0x13, 0x30, 0xf6, 0x20, 0xd1, 0x62, 0x31, 0x04, 0xdb, 0x9f, 0x83, 0x30, 0x0e,
0x05, 0xa3, 0x03, 0x42, 0xe7, 0x84, 0xc3, 0x3b, 0x30, 0x9f, 0x1e, 0x4c, 0x70, 0xda, 0xcf, 0x07,
0xaf, 0x0b, 0x21, 0x8b, 0x17, 0x20, 0x0d, 0x43, 0xf8, 0x09, 0x6a, 0x7d, 0x51, 0xe8, 0x5a, 0xe0,
0x34, 0xe0, 0xa8, 0xeb, 0x82, 0x6f, 0x01, 0xbe, 0x01, 0x9c, 0xe0, 0xe3, 0x85, 0xf1, 0x83, 0x1c,
0xc1, 0x01, 0x3c, 0x44, 0xbc, 0x1a, 0x78, 0x08, 0x9e, 0xc3, 0xfb, 0x05, 0x3b, 0x0f, 0x60, 0xff,
0xff, 0x04, 0x5d, 0xe3, 0xe9, 0x92, 0x70, 0x02, 0x96, 0x83, 0x86, 0x1a, 0xac, 0x2f, 0x00, 0x27,
0xe9, 0xc1, 0x1a, 0xae, 0xae, 0xd3, 0x06, 0x7a, 0xba, 0xa7, 0x72, 0x5a, 0xa5, 0x0a, 0x30, 0x7b,
0x94, 0x20, 0x04, 0xcf, 0x1e, 0x6c, 0xde, 0x67, 0x73, 0xe6, 0x09, 0x9e, 0x14, 0x3c, 0x05, 0x3e,
0x2d, 0xcf, 0xd2, 0x97, 0x0e, 0x5f, 0x09, 0x7c, 0x9f, 0x30, 0x41, 0xf4, 0x27, 0x17, 0x36, 0x1a,
0xb8, 0xc3, 0xc6, 0x8d, 0x06, 0xce, 0xe5, 0xe0, 0xb1, 0xc3, 0x33, 0xf7, 0x5c, 0x4d, 0x50, 0xf3,
0xe5, 0x42, 0x4e, 0x66, 0x83, 0xd2, 0x03, 0xa2, 0x01, 0x3f, 0x34, 0x60, 0xd0, 0x1f, 0x19, 0xb8,
0xc8, 0x8b, 0x02, 0x95, 0x86, 0xac, 0xbf, 0x86, 0x45, 0x8d, 0x9b, 0x12, 0x58, 0xca, 0xa1, 0x82,
0xdc, 0x33, 0x7c, 0x9e, 0x38, 0x8c, 0x57, 0x00, 0xcf, 0xe6, 0xa0, 0x7c, 0x73, 0x71, 0xba, 0x7b,
0x05, 0x68, 0x66, 0x83, 0xbb, 0x51, 0x80, 0x05, 0xc3, 0xd7, 0x03, 0xdf, 0x30, 0xd8, 0xf1, 0xc3,
0xd7, 0x0c, 0x36, 0x24, 0x83, 0x45, 0x89, 0x14, 0x9b, 0x4d, 0xca, 0x03, 0xc0, 0xe0, 0xbd, 0xd7,
0xf8, 0x70, 0x61, 0x48, 0x9f, 0x31, 0xe0, 0x1e, 0x05, 0xe0, 0xfd, 0xff, 0xcf, 0x09, 0xe0, 0xb8,
0x6d, 0xf8, 0x2a, 0x62, 0x67, 0xf7, 0x0b, 0x5d, 0x6f, 0xb0, 0xf7, 0x1d, 0x78, 0xf8, 0x87, 0x85,
0xbb, 0x0b, 0x30, 0xb0, 0x13, 0xc5, 0x1c, 0x78, 0x80, 0xc7, 0x64, 0x1e, 0x78, 0xc0, 0x75, 0x96,
0x82, 0x3d, 0x04, 0xae, 0xfa, 0xc0, 0x83, 0xca, 0xf1, 0x6a, 0xa0, 0x67, 0x1e, 0xc0, 0xec, 0xff,
0xff, 0xcc, 0x03, 0x8c, 0xe0, 0x9f, 0x79, 0x80, 0x6b, 0xf4, 0x6b, 0x81, 0xde, 0x57, 0x3e, 0xf3,
0x00, 0x7c, 0x50, 0x79, 0x33, 0x01, 0xcd, 0xff, 0xff, 0x66, 0x02, 0xe3, 0xe0, 0xe0, 0x83, 0x88,
0xaf, 0x32, 0x3e, 0x11, 0x02, 0x93, 0xab, 0x09, 0x70, 0x09, 0x79, 0x27, 0xa2, 0x01, 0x07, 0x41,
0xaf, 0x01, 0x5c, 0x0b, 0x88, 0x66, 0xc8, 0xa6, 0x89, 0x25, 0x98, 0xe5, 0x22, 0x40, 0xef, 0x8a,
0x3e, 0x2a, 0xf1, 0x31, 0xfa, 0xa8, 0xc4, 0x70, 0xdf, 0x85, 0x8c, 0x7b, 0x7a, 0x67, 0xf7, 0xac,
0x84, 0xb9, 0x04, 0xbc, 0x8f, 0x80, 0x65, 0xf2, 0xf8, 0xd3, 0x07, 0x47, 0xf4, 0x85, 0xc1, 0x77,
0x23, 0x78, 0x04, 0xd5, 0x5f, 0x65, 0xa8, 0xfe, 0xbd, 0x48, 0x2f, 0x0c, 0xea, 0x2a, 0x03, 0x5c,
0xff, 0xff, 0x57, 0x19, 0x36, 0xc8, 0x63, 0x05, 0xcb, 0xf9, 0x11, 0x33, 0xc7, 0xd3, 0x8c, 0xe2,
0xa9, 0x78, 0xb8, 0xec, 0x62, 0x65, 0xef, 0x53, 0x25, 0xc7, 0x17, 0x5f, 0xab, 0xf0, 0x20, 0x8f,
0x31, 0xbe, 0xc3, 0x80, 0x71, 0x04, 0xef, 0x30, 0xc0, 0x35, 0xf0, 0xcb, 0x41, 0xd7, 0x40, 0xc0,
0xf6, 0xff, 0xff, 0x0e, 0x03, 0x96, 0xe0, 0x10, 0xba, 0x06, 0xe2, 0x64, 0x1c, 0x5b, 0xc8, 0x4d,
0xca, 0x53, 0x36, 0xc1, 0xa0, 0x13, 0xa6, 0x47, 0x40, 0xf0, 0xdc, 0x2b, 0x7c, 0x98, 0x00, 0xc7,
0x48, 0x30, 0xe7, 0x08, 0x9f, 0x1f, 0x7c, 0x7d, 0x78, 0x93, 0x60, 0x37, 0x0e, 0xc3, 0xf8, 0xca,
0x07, 0x0f, 0xf2, 0x15, 0x8b, 0x5d, 0x26, 0xf8, 0x49, 0x0f, 0x6c, 0x17, 0x65, 0x70, 0xdc, 0x7f,
0xe0, 0x5c, 0x94, 0x81, 0x11, 0xee, 0xe3, 0x0f, 0xf8, 0x0f, 0xcb, 0x70, 0xfe, 0xff
})
}
This sample .mof file complements the previous ASL code.
[abstract]
class AcpiSampleBase
{
};
[abstract]
class AcpiSampleEvent : WMIEvent
{
};
[Dynamic, Provider("WMIProv"),
WMI,
Description("Counter for number of times the case has been hit"),
GUID("{ABBC0f5a-8ea1-11d1-A000-c90629100000}"),
locale("MS\\0x409")]
class MachineHitSensor : AcpiSampleBase
{
[key, read]
string InstanceName;
[read] Boolean Active;
[WmiDataId(1),
Description("Number of times the case sensor determined that the machine has been hit"),
read
] uint32 NumberTimesHit;
};
[Dynamic, Provider("WMIProv"),
WMI,
Description("Counter for number of times the case has been hit"),
GUID("{ABBC0f5b-8ea1-11d1-A000-c90629100000}"),
locale("MS\\0x409")]
class MachineHitSimulate : AcpiSampleBase
{
[key, read]
string InstanceName;
[read] Boolean Active;
[WmiMethodId(1),
Description("Simulate hitting the machine")
] void HitMachine();
};
[Dynamic, Provider("WMIProv"),
WMI,
Description("Event generated when machine is hit"),
GUID("{ABBC0f5c-8ea1-11d1-A000-c90629100000}"),
locale("MS\\0x409")]
class MachineHitEvent : AcpiSampleEvent
{
[key, read]
string InstanceName;
[read] Boolean Active;
[WmiDataId(1),
Description("Force with which the machine was hit")
] uint32 Force;
};
Appendix C—ASL sample code
Device(WMI1) {
Name (_HID, EISAID("PNP0Cxx")) // Plug and Play ID for mapping driver (TBD)
_UID(1)
//
// Data block and Wmi method to Object ID mappings
Name(_WDG, Buffer() {
// Object AA - {ABBC0F5A-8EA1-11d1-A53F-00A0C9062910}
0xABBC0F5A, 0x8ea1, 0x11d1, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10,
`A','A', // Object ID
1, // Instance Count
0x04, // Flags (WMIACPI_REGFLAG_STRING)
// Object AB - {ABBC0F5B-8EA1-11d1-A53F-00A0C9062910}
0xABBC0F5B, 0x8ea1, 0x11d1, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10,
`A','B', // Object ID
2, // Instance Count
0x01, // Flag (WMIACPI_REGFLAG_EXPENSIVE)
// Object AC - {ABBC0F5C-8EA1-11d1-A53F-00A0C9062910}
0xABBC0F5C, 0x8ea1, 0x11d1, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10,
`A','C', // Object ID
1, // Instance Count
0x06, // Flag (WMIACPI_REGFLAG_METHOD | _STRING)
// Event 0x80 - {ABBC0F5D-8EA1-11d1-A53F-00A0C9062910}
0xABBC0F5D, 0x8ea1, 0x11d1, 0x00, 0xa0, 0xc9, 0x06, 0x29, 0x10,
0x80, // Notification value
0, // Reserved
0, // Instance Count (Not meaningful for events)
0x0D // Flags (WMIACPI_REGFLAG_EXPENSIVE | _STRING |_EVENT)
})
//
// IO ports for configuration of Object AB
OperationRegion(CAB0, SystemIo, 0xf8, 1) // Instance 0
OperationRegion(CAB1, SystemIo, 0xfc, 1) // Instance 1
OperationRegion(CABC, SystemIo, 0xf4, 1) // Enable/Disable Collection
Method(WQAB, 1) {
//
// Read value from IO space for instance
if (LEqual(Arg0, Zero) {
Store(CAB0, Local0)
} else {
Store(CAB1, Local0)
}
//
// If any of the lower 3 bits are set then return TRUE, else FALSE
if (And(Local0, 7))
Return( 0x00000001 )
} else {
Return( 0x00000000 )
}
}
//
// Set the values for object AB
Method(WSAB, 2) {
if (LEqual(Arg0, Zero) {
// Change contents of first instance of data block to
// values in buffer in Arg1
} else {
// Change contents of second instance of data block to
// values in buffer in Arg1
}
}
//
// Collection notification for object AB
Method(WCAB, 1) {
if (LEqual(Arg0, 1)
{
Store(One, CABC) // If enable, write all 1's to port
} else {
Store(Zero, CABC) // If disable, write all 0's to port
}
}
//
// Storage for maintaining values for the AA method.
Name(STAA, "XYZZY")
Method(WQAA, 1) {
//
// Only one instance for AA so no need to check arg
return(STAA);
}
// Data block mapped to Object AA does not support set so it does not need
// a WSAA method
//
// Storage for maintaining state of flag that determines whether to fire (launch)
// the event or not. By default firing is disabled
Name(FIRE, 0)
//
// This method will reset the values for AA and send a notification of
// its occurrence
Method(WMAC, 3) {
Store(STAA, Local0)
Store("XYZZY", STAA)
if (LEqual(FIRE, 1))
{
Notify(WMI1, 0x80)
}
Return(Local0)
}
//
// Additional information about event
Method(_WED) {
return("Fired")
}
//
// Event 0x80 Enable/Disable control method
Method(WE80, 1) {
Store(FIRE, Arg0)
}
)


{% extends "base.html" %} {% block body %}
We worked with Sauce Labs, a late-stage growth company based in San Francisco, to create a variety of written and video case studies. Here is one featuring Eventbrite, the popular event management platform, on how they use Sauce Labs to automatically test their service at scale.


Cloud Vision V1 API - Class Google::Cloud::Vision::V1::Product (v0.6.4)
Reference documentation and code samples for the Cloud Vision V1 API class Google::Cloud::Vision::V1::Product.
A Product contains ReferenceImages.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#description
def description() -> ::String
- (::String) — User-provided metadata to be stored with this product. Must be at most 4096 characters long.
#description=
def description=(value) -> ::String
- value (::String) — User-provided metadata to be stored with this product. Must be at most 4096 characters long.
- (::String) — User-provided metadata to be stored with this product. Must be at most 4096 characters long.
#display_name
def display_name() -> ::String
- (::String) — The user-provided name for this Product. Must not be empty. Must be at most 4096 characters long.
#display_name=
def display_name=(value) -> ::String
- value (::String) — The user-provided name for this Product. Must not be empty. Must be at most 4096 characters long.
- (::String) — The user-provided name for this Product. Must not be empty. Must be at most 4096 characters long.
#name
def name() -> ::String
-
(::String) — The resource name of the product.
Format is:
projects/PROJECT_ID/locations/LOC_ID/products/PRODUCT_ID
.This field is ignored when creating a product.
#name=
def name=(value) -> ::String
-
value (::String) — The resource name of the product.
Format is:
projects/PROJECT_ID/locations/LOC_ID/products/PRODUCT_ID
.This field is ignored when creating a product.
-
(::String) — The resource name of the product.
Format is:
projects/PROJECT_ID/locations/LOC_ID/products/PRODUCT_ID
.This field is ignored when creating a product.
#product_category
def product_category() -> ::String
- (::String) — Immutable. The category for the product identified by the reference image. This should be one of "homegoods-v2", "apparel-v2", "toys-v2", "packagedgoods-v1" or "general-v1". The legacy categories "homegoods", "apparel", and "toys" are still supported, but these should not be used for new products.
#product_category=
def product_category=(value) -> ::String
- value (::String) — Immutable. The category for the product identified by the reference image. This should be one of "homegoods-v2", "apparel-v2", "toys-v2", "packagedgoods-v1" or "general-v1". The legacy categories "homegoods", "apparel", and "toys" are still supported, but these should not be used for new products.
- (::String) — Immutable. The category for the product identified by the reference image. This should be one of "homegoods-v2", "apparel-v2", "toys-v2", "packagedgoods-v1" or "general-v1". The legacy categories "homegoods", "apparel", and "toys" are still supported, but these should not be used for new products.
#product_labels
def product_labels() -> ::Array<::Google::Cloud::Vision::V1::Product::KeyValue>
-
(::Array<::Google::Cloud::Vision::V1::Product::KeyValue>) — Key-value pairs that can be attached to a product. At query time,
constraints can be specified based on the product_labels.
Note that integer values can be provided as strings, e.g. "1199". Only strings with integer values can match a range-based restriction which is to be supported soon.
Multiple values can be assigned to the same key. One product may have up to 500 product_labels.
Notice that the total number of distinct product_labels over all products in one ProductSet cannot exceed 1M, otherwise the product search pipeline will refuse to work for that ProductSet.
#product_labels=
def product_labels=(value) -> ::Array<::Google::Cloud::Vision::V1::Product::KeyValue>
-
value (::Array<::Google::Cloud::Vision::V1::Product::KeyValue>) — Key-value pairs that can be attached to a product. At query time,
constraints can be specified based on the product_labels.
Note that integer values can be provided as strings, e.g. "1199". Only strings with integer values can match a range-based restriction which is to be supported soon.
Multiple values can be assigned to the same key. One product may have up to 500 product_labels.
Notice that the total number of distinct product_labels over all products in one ProductSet cannot exceed 1M, otherwise the product search pipeline will refuse to work for that ProductSet.
-
(::Array<::Google::Cloud::Vision::V1::Product::KeyValue>) — Key-value pairs that can be attached to a product. At query time,
constraints can be specified based on the product_labels.
Note that integer values can be provided as strings, e.g. "1199". Only strings with integer values can match a range-based restriction which is to be supported soon.
Multiple values can be assigned to the same key. One product may have up to 500 product_labels.
Notice that the total number of distinct product_labels over all products in one ProductSet cannot exceed 1M, otherwise the product search pipeline will refuse to work for that ProductSet.


Fork me on GitHub
list unique words
filter common prose
remove punctuation
trim
toLowerCase()
sort by length
sort by length (reverse)
TM
alice.txt
2016-04-07
2016-04-25
JP SG
air
angular docs
rxPageObjects
2016-05-14
2016-08-26
newline to space
remove empty lines
GH PR
remove numbers
remove contractions
prettyPrintArrOfWords
isolate lines with '@'


| mcmc.list {coda} | R Documentation |
The function ‘mcmc.list’ is used to represent parallel runs of the same chain, with different starting values and random seeds. The list must be balanced: each chain in the list must have the same iterations and the same variables.
Diagnostic functions which act on mcmc
objects may also be applied
to mcmc.list
objects. In general, the chains will be combined,
if this makes sense, otherwise the diagnostic function will be applied
separately to each chain in the list.
Since all the chains in the list have the same iterations, a single time
dimension can be ascribed to the list. Hence there are time series methods
time
, window
, start
, end
, frequency
and thin
for mcmc.list
objects.
An mcmc.list
can be indexed as if it were a single mcmc object
using the [
operator (see examples below). The [[
operator
selects a single mcmc
object from the list.
mcmc.list(...) as.mcmc.list(x, ...) is.mcmc.list(x)
... |
a list of mcmc objects |
x |
an object that may be coerced to mcmc.list |
Martyn Plummer
mcmc
.
data(line) x1 <- line[[1]] #Select first chain x2 <- line[,1, drop=FALSE] #Select first var from all chains varnames(x2) == varnames(line)[1] #TRUE


PDB2.6(1) PDB2.6(1) NAME pdb2.6 - the Python debugger SYNOPSIS pdb2.6 script [...] DESCRIPTION See /usr/lib/python2.6/pdb.doc for more information on the use of pdb. When the debugger is started, help is available via the help command. SEE ALSO python2.6(1). Chapter 9 of the Python Library Reference (The Python Debugger). Available in the python2.6-doc package at /usr/share/doc/python2.6/html/lib/module-pdb.html. PDB2.6(1)


| 4-Vertex | 5-Vertex | Special Graphs | ||
|---|---|---|---|---|
| : K4 | : K5 | : co-twin-C5 | : Co-Cricket | |
| : co-K4 | : co-K5 | : co-twin-house | : Dart | |
| : diamond | : K5 - e | : co-A | : ISK4 | |
| : co-diamond | : W4 | : W5 | ||
| : paw | : gem (3-Fan) | : co-p2-p3 | ||
| : co-paw | : chair | : co-R | ||
| : claw | : butterfly | : bridge | ||
| : co-claw | : co-butterfly | : C6 | ||
| : C4 | : C5 | : C7 | ||
| : 2K2 | : kite | : Even Hole Free |


{% autoescape true %}
Log Out
Prioritize and Set Goals
It's 2016 lets build a life together!
+
{% endautoescape %}