public class ShotgunAnalyzer extends AbstractAnalyzer
AbstractAnalyzer
object.
These algorithms are based on the Shotgun package written in C++ that are called using JNI.
(See more information on the Shotgun project here).
Please note that this analyzer calls native call in C++ and requires the location of the Shotgun library (provided) to
be defined in the properties file.AbstractAnalyzer
| Constructor and Description |
|---|
ShotgunAnalyzer() |
| Modifier and Type | Method and Description |
|---|---|
CGEModel |
analyze(AbstractOptions optionsPar,
SamplesLabels labels,
SamplesGeneticData samples)
Performs the training phase of the analyzer/algorithm.
|
CGEPrediction |
applyModel(AbstractOptions options,
CGEModel model,
SamplesLabels label,
SamplesGeneticData sample)
Applies a model generated at the training phase to a specific patient sample.
|
AbstractAnalyzer |
create() |
AbstractAnalyzer |
create(AbstractOptions options)
Creates a Shotgun Analyzer with the specified properties file
|
java.lang.String |
getName()
Returns the name of the class to be registered in the CGEframework so that objects from this class
can be instantiated.
|
double[] |
getResults() |
void |
initializeAnalyzer(OptionsGeneral options)
Initializes the analyzer with the properties file
|
SamplesGeneticData |
loadData(AbstractOptions options)
Loads the genetic data of the patients samples to be trained on.
|
SamplesLabels |
loadLabels(AbstractOptions options)
Loads the clinical variables or disease labels of the patients samples to be trained on.
|
void |
readMatrix(double[][] x,
int num_row,
int num_col)
Passes in a matrix market of features to be stored in the shotgun data
structure
|
void |
readVector(double[] y)
Passes in the vector containing the labels
|
int |
saveModel(AbstractOptions options,
CGEModel model)
Saves the
CGEModel that was generated in AbstractAnalyzer.analyze(AbstractOptions, SamplesLabels, SamplesGeneticData) to a database and/or file. |
public void readMatrix(double[][] x, int num_row, int num_col)
x
- matrix market containing the datanum_row
- number of rows in the matrixnum_col
- number of vectors in the matrixpublic void readVector(double[] y)
y
- vector of labelspublic double[] getResults()
public java.lang.String getName()
AbstractAnalyzer
getName
in class AbstractAnalyzer
DataAnalysisPhaseController
public AbstractAnalyzer create(AbstractOptions options)
create
in class AbstractAnalyzer
options
- properties defined in the input properties file.public AbstractAnalyzer create()
public void initializeAnalyzer(OptionsGeneral options)
options
- properties filepublic CGEModel analyze(AbstractOptions optionsPar, SamplesLabels labels, SamplesGeneticData samples)
AbstractAnalyzer
analyze
in class AbstractAnalyzer
optionsPar
- properties defined in the input properties file.labels
- the clinical variables / disease labels for the training process. See AbstractAnalyzer.loadLabels(AbstractOptions)
for more info.samples
- the genetic data information of the patients to be trained onCGEModel
object with the model that was generatedpublic SamplesGeneticData loadData(AbstractOptions options)
AbstractAnalyzer
loadData
in class AbstractAnalyzer
options
- properties defined in the input properties file.AbstractAnalyzer.analyze(AbstractOptions, SamplesLabels, SamplesGeneticData)
public CGEPrediction applyModel(AbstractOptions options, CGEModel model, SamplesLabels label, SamplesGeneticData sample)
AbstractAnalyzer
CGEModel
for a
specific sample.applyModel
in class AbstractAnalyzer
options
- properties defined in the input properties file.model
- the model to validate the patient against.label
- clinical or other information attached to the sample to be test (if needed)sample
- the genetic data information of the specific sampleCGEPrediction
object with the resultpublic int saveModel(AbstractOptions options, CGEModel model)
AbstractAnalyzer
CGEModel
that was generated in AbstractAnalyzer.analyze(AbstractOptions, SamplesLabels, SamplesGeneticData)
to a database and/or file.saveModel
in class AbstractAnalyzer
options
- properties defined in the input properties file.model
- the CGEModel
to be savedpublic SamplesLabels loadLabels(AbstractOptions options)
AbstractAnalyzer
loadLabels
in class AbstractAnalyzer
options
- properties defined in the input properties file.AbstractAnalyzer.analyze(AbstractOptions, SamplesLabels, SamplesGeneticData)


Pizza 3001
Happy Odysseys
happy Pizza Odysseys this week!!
Stores and Hours
store name
store name
store name
store name
store name
store name


Your Shopping Cart (1 Items)
{include file="web/display/shopcart/shipcountry.html"}
{foreach from=$blockList item=block}
{foreach from=$block.areaList item=area}
{include file="web/display/shopcart/item.html"}
{include file="web/display/shopcart/shipping.html"}
{/foreach}
{/foreach}
{include file="web/display/shopcart/option.html"}


Log in
Log out
REST API
(requires user authentication)
Streaming API - statuses/filter
(requires user authentication)
Streaming API - statuses/sample
Streaming API - user
(requires user authentication)


John Doe
Front End Ninjitsu
Featured Work
Appify
Some href link
Chatify
Some href link
Sumify
Some href link


232 Upper San Vicente
09771751063
<EMAIL_ADDRESS>I am seeking a competitive and challenging environment where i can serve your organization, establish, and company an enjoyable career for myself
Occupation: Diseased
Occupation: Self Employed
Community Livelihood Skills Training in Welding
ALS Dep-Ed
Baguio City 2600, Philippines
Graduated with Certificate
Bachelor of Science: Information Technology
University Of the Cordilleras
Under Graduate
San Vicente National High School SY(2014-2015)
San Vicente, Baguio City, Philippines
Graduated- High School Diploma
San Vicente Elementary School SY (2009-2010)
San Vicente, Baguio City, Philippines
Graduated- Elementary Diploma
Design Department Head
ITech - PFS Technology Inc.
09057393629
Counselor at Law
Associate Professor University of the Cordilleras
Governor Pack Road
Baguio City 2600
09103650193
Store Manager
Ace Hardware
SM Cauayan Isabela
09265379485


--- layout: page title: FINAL_REPORT permalink: /final_report comments: false ---
https://github.com/sypai/co-oCCur
https://github.com/sypai/co-oCCur/blob/master/docs/usage.adoc
https://github.com/sypai/co-oCCur/blob/master/docs/code_documentation.adoc
https://sypai.github.io/GSoC-Final-work-submissions/For Subtitle Resync:
https://sypai.github.io/Subtitle-Resync/


[gecode-users] sqrt function
Jaroslav Mlejnek
mum.jmlejnek at post.cz
Thu Apr 3 19:49:30 CEST 2008
Hi!
I am using C++ Gecode Library in my school project and I am very satisfied with it. But I would like to use an arithmetic function "sqrt" and I think it doesn't work well. In code:
defining CSP (x is class global, y is constructor local):
IntVar x (this, 0, Int::Limits::max), y (this, 0, Int::Limits::max);
rel(this, y, IRT_EQ, 25);
rel(this, x, IRT_EQ, Gecode::sqrt(this, y));
printing solution (like Gecode examples):
cout << x.val() << endl;
There is in printing solution method an assert (debug) error instead of solution number 5. But when I use "similar" function "sqr", it works fine (or as I expect), so the solution is 625.
Is this bug in sqrt function or sqrt function has some special way how to use it? I am using Gecode since version 1.1.0, my current version is the newest 2.1.1.
Thanks a lot for your answer,
Jaroslav Mlejnek
Faculty of Mathematics and Physics
Charles University, Prague
Czech Republic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ps.uni-sb.de/pipermail/users/attachments/20080403/badab527/attachment.htm>
More information about the gecode-users
mailing list


| Vendor Name | Mid-Valley Construction (1997) Limited |
|---|---|
| Reference Number | 64281 |
| Contract Date | 21-10-2016 |
| Description of Work | Construction Work - Civil Eng |
| Delivery Date | 20-11-2016 |
| Contract Value | $206,445.00 |
| Comments | This contract was competitively sourced. |
| Additional Comments |


This is a generative web application. Use the interface on the right to change the colors of the elements of the picture.


Frames
and applying styles:Think of frames
as permanent CSS classes, but in JS-object notation. Instead of working with DOM classList
, use frames to speed up the process:
frame
called newEffect
and a CSS class called new-effect
Before: Plain JS with the CSS class:
.new-effect{
background: blue;
color: white;
}
let element = document.getElementById("test");
element.classList.add("new-effect");
After: KeyframerJS with frames:
keyframer.createFrame("newEffect", {
background: "blue",
color: "white"
});
keyframer.setStyles("#test", keyframer.getFrame("newEffect"))
keyframer.frames
object (either with an object reference or the createFrame
function).{ background: "blue", color: "white" }
).Use a reusable frame when it’s likely you’ll use the frame more than one time.
Use a single-use frame when you think you’ll only use the frame once.
Single-use frames are just objects, so there isn’t much to explain there.
Reusable Frames can be created 2 ways, the function call or the object reference:
// Function Call (creating a frame called 'newEffect'):
keyframer.createFrame("newEffect", {
background: "blue",
color: "white"
});
// Object Reference (creating a frame called 'newEffect'):
keyframer.frames["newEffect"] = {
background: "blue",
color: "white"
};
The style properties contained in a frame are apllied to a DOM element by passing it in the keyframer.setStyles
function:
// Applying A Reusable Frame To An Element With An ID of header:
keyframer.createFrame("newEffect", {
background: "blue",
color: "white"
});
keyframer.setStyles("#header", keyframer.getFrame("newEffect"));
// Applying A Single-Use Frame To An Element With An ID of header:
keyframer.setStyles("#header", { background: "blue", color: "white" });
camelCase
, not how-they-look
in CSS.marginTop
, not margin-top
.


Ticket #55 (closed enhancement: worksforme)
better (or more prominent) docs for monitors and signal handler
| Reported by: | mmckerns | Owned by: | mmckerns |
|---|---|---|---|
| Priority: | minor | Milestone: | mystic-0.1a2 |
| Component: | mystic.docs | Keywords: | |
| Cc: |
Description
Docs on using the monitors and signal handler exist, but these docs are buried down deep in the reference manual. I should bring them higher up in the docs... and maybe expand on them a little.
Change History
comment:2 in reply to: ↑ 1 Changed 7 years ago by mmckerns
Replying to mmckerns:
http://dev.danse.us/trac/mystic/wiki/Tutorials (#8 - #11; the expanded solver interface)
oops... the linked tickets have nothing to do with tutorials #8 - #11... 'twas a wiki formatting error.
comment:4 Changed 7 years ago by mmckerns
- Status changed from assigned to closed
- Resolution set to worksforme
important links (such as the monitor) are now exposed on the tutorial page
Note: See
TracTickets for help on using
tickets.
The docs currently are here:
Also the tutorials may need better explanation:


personalised group training
How it works
Our programmes target the strengths and weakness of each individuals physical health, through twenty
different types of fitness and training styles. These is very important when it comes to functional
training as they all have a crossover with everyday life.
Everyone has different and specific fitness goals, so when you train with us, our broad programming will
ensure you achieve your targets, no matter your level of fitness or current ability.
Our workouts include:
{{ partial "star" . }}
tabata
Tabata is a high-intensity interval training (HIIT), and each exercise in a given workout only lasts
four minutes. A workout could look a bit like this:
-
Workout hard for 20 seconds
-
Rest for 10 seconds
-
Complete 8 rounds
You push yourself as hard as you can for 20 seconds and rest for 10 seconds. This is one set.
You'll complete eight sets of each exercise.
{{ partial "star" . }}
gynmastic
Gymnastics workouts increase your strength and flexibility while boosting muscular endurance.
Much like bodyweight training, it is done without the use of free weights or machines,
but using your own weight to provide resistance against gravity.
Read more...


From conception to execution Tony Voorhees is one of the best designers I am fortunate enough to work with. He understands DR marketing, branding and his work has generated thousands of profitable leads.
While I only worked for a short period of time with Tony, I quickly gained respect for the level of expertise he has to solve creative problems on the desktop and mobile platforms and his solid work ethic. And 'to boot', he is one heck of a fun guy to chat with.
Tony is a great designer and a pleasure to work with. He was the only designer at Foundry9 that knew anything about css/html and how the development lifecycle process worked which made him a great asset to the company and a big help to me as a developer.


Enter sentences (one per line):
We should be getting there around 2:30-3 My flight has been delayed for two hours I will be arriving at closer to 2:30-3am Sean we may be getting there closer to 4:30-5:00 if thats ok Can you please let us know when room is ready as we will be getting there between 121 I should be getting there around 11:20 I will not be arriving until almost 2:30am due to fly delays pls hold the room


JuniorIAS
Home
Daily Content
Study Notes
Current Affairs
Quiz
Current Affairs
Account
Add New
Date
Count
Add
View All
Date
Heading
Description


Welcome to
ZilGAM!
Art · Music
We connect you to digital artists and musicians
to quench your fervent thirst for quality art.
Art is how we decorate space, music is how we decorate time.
Projects
AudioPulse
AudioPulse generates pulsating circles dancing to our groovy music library. Every piece reveals a unique combination of vibrant colours and varying sizes that visually portrays the spectrum of one among ten non-copyright sounds. View Project
SpiralX
SpiralX art pieces are based on simple ellipses that take on varying shapes, sizes, and colour combinations based on the transaction hash to generate a distinct and appealing artwork each time.
View Project


BRAINCHILD PARTNERS, LLC. is an INTERNATIONAL ADVISORY & PROCUREMENT BOUTIQUE with offices in Seoul, Vancouver and Paris (Representative Office to be established) and is aimed at providing a tailored cross-border consultancy service for companies and organizations of all size, applying our INTELLIGENCE to a wide array of global business issues. We also provide a PLATFORM for our clients to gain insights on how to navigate such a dynamic business environment, given the global market’s diversity and complexity, and assist the clients with implementation SOLUTIONS.
provides strategic advice and practical solutions to assist the clients in globalizing the firm’s capacities and business practices. We also provide a value-added and cross-border financing solution by leveraging our extensive networks with institutional and private investor communities.+more
offers comprehensive services to 1) support commodity suppliers with marketing solutions and to 2) assist commodity buyers with procurement solutions in securing the supply of high quality. Also we also provide a cross-border financing solution by leveraging our extensive networks with institutional and private investor communities. +more
provides customized business intelligence conferences, speaker solutions, and private board briefing on a broad range of business issues in a variety of ways, including keynotes, panel discussions and workshop. +more
3F Yulchon Building, 20 Gukjegumyung-ro, Yeongdeungpo-gu, Seoul 150-877, Korea
205-810 Quayside Dr., New Westminster, BC V3M 6B9, Canada


So I am trying to make my local emoncms system to report to emoncms.org.
I installed the emoncms latest stable version on my Synology Nas with "Apache HTTP/1.1 CGI/1.1 80".
I also installed some modules they all work.
Now I would like to link this local version to the online emoncms.org.
I already tried to install the emonhub as a module but I don't know if this is the right way.
added my emoncms.org api key to the emonhub settings file.
But this doesn't seem to work. Can someone point me in the right direction?
Re: Using reporter to Emoncms.org with emoncms on linux hosting
Where is your data coming from?
emonhub is intended to collate data and forward to one or more emoncms instances, if you are sending data directly to an emoncms instance then emonhub isn't in play.
"install the emonhub as a module" sounds like you have installed it to the modules folder which isn't right, emonhub is not part of emoncms it is independent. emonhub and emoncms can (and usually are) be installed to the same machine no problem but they are actually independent of each other, (not so much the emon-pi variant of emonhub).
Which guide did you follow to install emoncms? the official guide uses the emonhub installer script from the emonhub repo, this is written for "Wheezy" and works on "Jessie", you may need to look at the script and apply steps more tailored to your setup.
Paul
Re: Using reporter to Emoncms.org with emoncms on linux hosting
Thanks for you reply. I think I understand now. My data is coming from a Particle photon who is connected to the web and uses the input api.
So if I understand correctly the right way to use 2 instances of emoncms is to configure my Particle photon to send the data to both emoncms instances. Why didn't I think of that before...
Roeland


Ventilation
Home
Components
Compressor
Circuit
Dampers
Screen
Ventilation
Heatpump
Cycles
Our Calculations


Web Developer - PHP, Laravel, jQuery, Node JS, React JS, Angular 2, 4
Mobile Developer - React Native, Ionic, NativeScript.
We have everything you need to get your new website or mobile app up and running in no time! All of which contain elegant design and themes for your website or app just for you, responsive, and easy to use. No strings attached!
Get Started!Our products have robust design as per current design standards.
Products are made with care and for every screen sizes.
Products made with Laravel backend. Robust & Secure.
You have to make your websites with love these days!
Ready to start your next project with me? That's great! Give me a call or send me an email and I will get back to you as soon as possible!


Everyone On Twitter Thinks Scott Morrison Has Gone Missing, So Now It’s Become A Big Meme
by Joseph EarpScott Morrison has been pretty present over the last few weeks — at least in a physical sense.
The Prime Minister has appeared in front of cameras countless times to offer his “thoughts and prayers” to those affected by the NSW bushfires, smiling at the press and dropping vague, useless commiserations.
Of course, who knows where he’s actually been ethically or politically. The man is a walking suit filled with dandruff, and the day we see him take any kind of stance on any kind of issue will be the day we all die of shock.
So maybe it’s that moral invisibility that has spawned a curious new conspiracy theory-turned-meme on Twitter — that Scott Morrison has gone missing.
The first person to share the story appears to be Aaron Dodd, a “small business owner” and regular political commentator on Twitter.
Of course, Dodd had no obvious connection to any insiders that might know whether or not the Prime Minister has gone missing.
There was no reason to believe him, so there was no reason to be surprised when, a mere five hours later, a photo of the Prime Minister being very much not disappeared was shared to Twitter.
In fact, there’s not even reason to believe that he was being serious, rather than just joking about our PM’s dubious ethical standing when it comes to the bushfires ravaging NSW.
But that’s kinda beside the point. Whether he meant to or not, Dodd kicked off a massive meme on Twitter — one equating Morrison with Harold Holt, the Prime Minister who famously disappeared into the ocean.
Within hours, some were seriously pondering the whereabouts of the Prime Minister, while others were getting in on the fun with satirical memes. Before too long, the hashtag #WheresScotty started — and not long after that, it took off.
All in all, this is a rare meme: one that speaks to an ethical, rather than actual truth. Cause even when Scott Morrison comes back properly, we all know he won’t really be back — not in the way a Prime Minister should be.


Table of Contents
This NVIDIA driver release contains support for the X Resize and
Rotate (RandR) Extension versions 1.1, 1.2, and 1.3. The version of
the RandR extension advertised to X clients is controlled by the X
server: the RandR extension and protocol are provided by the X
server, which routes protocol requests to the NVIDIA X driver. Run
xrandr --version
to
check the version of RandR provided by the X server.
Specific supported features include:
Modes can be set per-screen, and the X screen can be resized through the RRSetScreenConfig request (e.g., with xrandr(1)'s '--size' and '--rate' command line options).
The X screen can be resized with the RandR 1.2 RRSetScreenSize request (e.g., with xrandr(1)'s '--fb' command line option).
The state of the display hardware can be queried with the RandR 1.2 and 1.3 RRGetScreenResources, RRGetScreenResourcesCurrent, RRGetOutputInfo, and RRGetCrtcInfo requests (e.g., with xrandr(1)'s '--query' command line option).
Modes can be set with RandR CRTC granularity with the RandR 1.2
RRSetCrtcConfig request. E.g., xrandr --output DVI-I-2 --mode
1920x1200
.
Rotation can be set with RandR CRTC granularity with the RandR
1.2 RRSetCrtcConfig request. E.g., xrandr --output DVI-I-2 --mode 1920x1200
--rotation left
.
Per-CRTC transformations can be manipulated with the RandR 1.3
RRSetCrtcTransform and RRGetCrtcTransform requests. E.g.,
xrandr --output DVI-I-3 --mode
1920x1200 --transform
43.864288330078125,21.333328247070312,-16384,0,43.864288330078125,0,0,0.0321197509765625,19.190628051757812
.
The RandR 1.0/1.1 requests RRGetScreenInfo and RRSetScreenConfig
manipulate MetaModes. The MetaModes that the X driver uses (either
user-requested or implicitly generated) are reported through the
RRGetScreenInfo request (e.g., xrandr --query --q1
) and chosen
through the RRSetScreenConfig request (e.g., xrandr --size 1920x1200 --orientation
left
).
The configurability exposed through RandR is also available through the MetaMode syntax, independent of X server version. See MetaModes for more details. As an example, these two commands are equivalent:
xrandr --output DVI-I-2 --mode 1280x1024 --pos 0x0 --rotate left \ --output DVI-I-3 --mode 1920x1200 --pos 0x0 nvidia-settings --assign CurrentMetaMode="DVI-I-2: 1280x1024 +0+0 \ { Rotation=left }, DVI-I-3: 1920x1200 +0+0"
On X servers that support RandR 1.2 or later, when an RandR 1.1
rotation request is received (e.g., xrandr --orientation left
), the
NVIDIA X driver will apply that request to an entire MetaMode.
E.g., if you configure multiple monitors, either through a MetaMode
or through RandR 1.2:
xrandr --output DVI-I-2 --mode 1280x1024 --pos 0x0 \ --output DVI-I-3 --mode 1920x1200 --pos 1280x0 nvidia-settings --assign CurrentMetaMode="DVI-I-2: 1280x1024 +0+0, \ DVI-I-3: 1920x1200 +1280+0"
Requesting RandR 1.1 rotation through xrandr --orientation left
, will
rotate the entire MetaMode, producing the equivalent of either:
xrandr --output DVI-I-2 --mode 1280x1024 --pos 176x0 --rotate left \ --output DVI-I-3 --mode 1920x1200 --rotate left --pos 0x1280 nvidia-settings --assign CurrentMetaMode="DVI-I-2: 1280x1024 +176+0, \ { Rotation=left }, DVI-I-3: 1920x1200 +0+1280 { Rotation=left }"
On X servers that do not support RandR 1.2 or later, the NVIDIA X driver does not advertise RandR rotation support. On such X servers, it is recommended to configure rotation through MetaModes, instead.
The NVIDIA Linux driver supports a number of output device properties.
Properties that do not start with an underscore are officially
documented in the file randrproto.txt
in X.Org's randrproto
package. See that file for a full description of these
properties.
This property groups RandR outputs by their physical connectors.
For example, DVI-I ports have both an analog and a digital output,
which is represented in RandR by two different output objects. One
DVI-I port may be represented by RandR outputs DVI-I-0
with SignalFormat
TMDS
(transition-minimized differential
signaling, a digital signal format) and DVI-I-1
with SignalFormat
VGA
, representing the analog part. In this
case, both RandR outputs would have the same value of ConnectorNumber
.
This property lists the physical type of the connector. For
example, in the DVI-I example above, both DVI-I-0
and DVI-I-1
would have a ConnectorType
of DVI-I
.
This property contains the raw bytes of the display's extended display identification data. This data is intended for applications to use to glean information about the monitor connected.
This property describes the type of signaling used to send image data to the display device. For example, an analog device connected to a DVI-I port might use VGA as its signaling format.
This property is a list of integers specifying adjustments for the edges of the displayed image. How this property is applied depends on the number of elements in the list:
0 = No border is applied.
1 = A border of Border[0] is applied to all four sides of the image.
2 = A border of Border[0] is applied to the left and right sides of the image, and a border of Border[1] is applied to the top and bottom.
4 = The border dimensions are as follows: Border[0]: left, Border[1]: top, Border[2]: right, Border[3]: bottom
This property is functionally equivalent to the ViewPortOut MetaMode token.
This property lists how many Border adjustment parameters can actually be used. The NVIDIA implementation supports independently configuring all four Border values.
DisplayPort 1.2 specifies that all devices must have a
globally-unique identifier, referred to as a GUID. When a GUID is
available, the GUID
property
contains its raw bytes.
This property controls the color-space conversion matrix applied to the pixels being displayed. The matrix is 3 rows and 4 columns, stored in row-major order. Each entry is a 32-bit fixed-point number with 3 integer bits and 16 fractional bits. Each entry in the X colormap is treated as a 4-component column vector C = [ R, G, B, 1 ]. The resulting components of the color vector [ R', G', B' ] = CscMatrix * C are used as indices into the gamma ramp.
For example, using xrandr version 1.5.0 or higher, you can exchange the red channel with the green channel using this command:
xrandr --output DP-6 --set CscMatrix \ 0,0x10000,0,0,0x10000,0,0,0,0,0,0x10000,0
To return to the default identity matrix, use
xrandr --output DP-6 --set CscMatrix \ 0x10000,0,0,0,0,0x10000,0,0,0,0,0x10000,0
Properties whose names begin with an underscore are not specified by X.Org. They may be removed or modified in future driver releases. The NVIDIA Linux driver supports the following unofficial properties:
This property describes the physical location of the connector. On add-in graphics boards, connector location 0 should generally be the position closest to the motherboard, with increasing location numbers indicating connectors progressively farther away.
| Type | INTEGER |
| Format | 32 |
| # Items | 1 |
| Flags | Immutable, Static |
| Range | 0- |
When display devices are connected via DisplayPort 1.2 branch devices, additional RandR outputs will be created, one for each connected display device. These dynamic outputs will remain as long as the display device is connected or used in a MetaMode, even if they are not named in the current MetaMode. They will be deleted automatically when the display is disconnected and no MetaModes use them.
See Appendix C, Display Device Names for a description of how the names of these outputs are generated.
If you are developing applications that use the RandR extension, please be aware that outputs can be created and destroyed dynamically. You should be sure to use the XRRSelectInput function to watch for events that indicate when this happens.
This NVIDIA Linux driver honors the Enable
, Ignore
, Primary
, and Rotate
options in the Monitor section of
the X configuration file. These options will apply to a monitor if
the Identifier of the Monitor section matches one of the display
device's names (see Appendix C,
Display Device Names for a description of how a
display's names are generated). For example, a Monitor section
with
Identifier "DFP"
will apply to all digitally-connected displays, while a Monitor section with
Identifier "DPY-EDID-ee6cecc0-fa46-0c33-94e0-274313f9e7eb"
will apply only to a display device with a specific EDID-based identification hash. You can also specify the name of the Monitor section to use in the Screen section:
Option "Monitor-<dpyname>" "<Monitor name>"
See the xorg.conf(5) man page for a description of these options.
Rotation and Transformations (configured either through RandR or MetaModes) are not yet supported with the GLX_NV_swap_group OpenGL extension.
Some of the RandR 1.2 X configuration options provided by the XFree86 DDX implementation and documented in xorg.conf(5) are not yet supported.
Transformations (configured either through RandR or MetaModes) are not yet correctly clipped.


Template for directive '{0}' must have exactly one root element. {1}
When a directive is declared with template
(or templateUrl
) and replace
mode on, the template
must have exactly one root element. That is, the text of the template property or the content
referenced by the templateUrl must be contained within a single html element.
For example,
blah blah blah

instead of simply blah blah blah
.
Otherwise, the replacement operation would result in a single element (the directive) being replaced
with multiple elements or nodes, which is unsupported and not commonly needed in practice.
For example a directive with definition:
myModule.directive('myDirective', function factory() {
return {
...
replace: true,
templateUrl: 'someUrl'
...
}
});
And a template provided at URL someUrl
. The template must be an html fragment that has only a
single root element, like the div
element in this template:

Hello World!

An an invalid template to be used with this directive is one that defines multiple root nodes or elements. For example:
Hello World!
Watch out for html comments at the beginning or end of templates, as these can cause this error as well. Consider the following template:

...

The
comment is interpreted as a second root element and causes the template to
be invalid.


Exploring My Values
Posted on 20 July 2014 by Kyle Daugherty
When I think of the times in my life where I've been the happiest, the proudest or the most satisfied, the following values come to mind:
- Challenge
- Growth
- Independence
- Integrity
- Meaningful Work
- Stability
One of the most important values to me is growth. I don't feel satisfied unless I'm constantly learning new things and pushing my personal development. Otherwise, I feel a little like being in the movie Groundhog's Day where I'm living each day over and over again. A lot of the values I picked above go hand in hand like challenge and growth and independence and stability. But these can also compete against each other. For instance, attending DBC will be an incredible challenge, but it also means that I lose stability in my life because I quit my job and am moving away from my family for 9 weeks. These competing values can be a challenge all on their own.
Based on the following scale, do I agree if I try to live up to these values? Disagree 1 ----- 2 ----- 3 ----- 4 ----- 5 Agree
- Challenge - 4
- Growth - 4
- Independence - 5
- Integrity - 5
- Meaningful Work - 3
- Stability - 3
Do I think these values can help me mediate stereotype threat if I recognize I feel it? Reflecting on these values, I think they will help motivate me and push onwards past any discouragement.
Are there any other exercises I can use to help me when I'm feeling down (for whatever reason) at DBC? While I've never done it before, I'm hoping yoga will help me get some relief and help me recharge. I also think getting enough sleep will be important. We'll obviously be working long hours and absorbing large amounts of new material. Getting sleep and rest will be extremely important so I'll do my best to make sure I make time for it.


I think I have deepened my understanding of my erratic thought processes around the quality of work and comparing myself with others, often looking at others work who have prior coding experience and comparing it to mine (in which prior to this course, I had zero coding experience) and somewhat belittling or undermining myself and my work.
leading on from the first point, being able to identify when my self-conscious thoughts are bouncing all over the place and taking a moment to reflect and rationalise these thoughts has been something I've further developed, in the case above this would be seen as trying to remove my peers work from my mind and comparison all together and instead focusing on how far I've come and how much I have achieved in such a little time. In other words, comparing my past self with my current self instead of my peers with my current self.
something I've learned that is completely new rather than built upon a pre-existing foundation is the concepts around neuroplasticity and growth mindset. One thing I've specifically taken out of these teachings is the growth mindset idea of "not yet". This idea is something that I have thought about several times throughout dealing with challenging or troublesome code, which has helped me divert my thinking away from a concrete view of "this code doesn't work" towards "it doesn't work yet". This change in mindset often has acted as a mini energy booster, allowing me to push a little bit harder as in many situations, there has only been one small aspect of my code not working that retrospectively was quite an easy fix.
I think that programming in general (and definitely my approach towards it) has strong collaboration elements to it, whether that is working directly with others within your team to develop a specific application or through communicating and discussing with your client or boss about how an application should be made or its required features. Because of this, there is a strong need for human interaction where I think understanding ones (and potentially others) values and having an ability to empathise with them is vital in order to foster a projects success and ease in navigating its creation process. I feel like some (and perhaps me to a degree at some point in time) view coding like some hacker sitting in the dark with five monitors furiously smashing their keyboard for hours on end when in reality, this is far from the truth. I believe that self-awareness and the ability to reflect in contexts such as this are also vital, self-awareness being around how effective a teams dynamics may be or how your approach to interactions and collaboration blends with someone else's. Reflection is also crucial so that one can look back and reevaluate all of the above in a context outside where it has been implemented.
If I had to sum up what I was surprised about core learning, I would say that I was surprised with how much I was surprised. Coming into this course I had expected a lot of the core teachings to be around concepts that I was already relatively strong in and knew about, while this was true for much of the teachings, the number of things I didn't know, and more notable the amount of stuff I clearly needed reminding and reinforcing of were greater than expected and often allowed those concepts to be developed with greater understanding. some of these for example, were around mindfulness and aspects of the practice I had forgotten.
I wouldn't say a lot of the core learnings were challenging at all for me. If anything, I would say the research towards mindfulness was closest to this as my personal journey with mindfulness had definitely seen the definitition of what i conisder to be mindfulness to somewhat warp around my personal use of it and my circumstances, taking a step back to reevaluate what mindfulness is truly defined as meant that it had a certain degree of clashing with my own definition and perhaps required a little bit of overwriting.
It is vital! It's virtually impossible to go about your work within a business without interacting with others, and the degree of technicality that comes with the role often means that these interactions and collaborations have to be well refined to ensure a whole party is on the same page. Technical skills are much easier to develop than these core skills once in the job, so having a foundation of core skills gives an invaluable edge into the effectiveness of a team.
Not at all. As stated, I felt I had a relatively decent grasp on many of the emphasised core skills before coming into this course. Because of this, I undoubtedly knew the benefits and importance of having these skills within the workplace. These skills were also something I had been developing throughout university, when working in groups with others who didn't necessarily have such a firm grasp on these skills, there was a clear impact on the flow of collaboration.


This picture was take on the streets of Porto, Portugal. I attended the Global Lead Conference(GLC) there. GLC is an intimate conference that is tailored for the emotional growth of all it attendees. There I learnt the importance of emotional intelligence.
I went to Egypt to challenge myself by working in a completely foreign environment. I worked for a 3D architectural visualization company. It was difficult adapting to the heat and language barrier but in the end it made me a stronger more resilient individual.
I taught English and Math to children in a school in India. I was one of my most rewarding experiences. Nothing beats making a child smile through the experience you give them.
This is a picture of my from my volunteer experience in Bahrain. I was a care-giver for autistic children. The experience made me more compassionate to individuals around me.


optimized image quality
User Story
As a shopper, I want my pages to load quickly and the product images to be detailed and crisp.
As the brand, we want to decrease our yearly bandwidth costs.
goal
To understand how consumers perceive image quality with the intentions of delivering higher quality images (better color representation, less pixilation) while maintaining a cost sensitive image file size.
Hypothesis
Increasing an image by 1.5x times its in-browser requirement and decreasing its JPG quality to 40% will render an image that is of indistinguishable quality when compared to a 1x, 100% JPG quality image.
Team Structure
| My Roles | Supporting Roles |
|---|---|
| Lead UX Designer | e-Commerce Director: Corinne Suchy |
| Researcher | Executive Creative Director: Joanna Ewing |
| Analyst | Lead Photographer: Devyn Galindo |
| Strategist | Lead Engineer: Tom Knabe |
study requirements
Brand & Studio Approved Images
These images were chosen specifically for their range of content and color density and contextual variances.
Image Presets
| Base | 1.5x | 2x | |
|---|---|---|---|
| Image size | 2x3 ratio | 1.5x base | 2x base |
| JPG Quality | 87% | 40% | 25% |
Test Participants
Invitations were sent out at Urban Outfitters headquarters to cull image experts and laypeople alike.
Category Page & Image Zoom Views
We put together sumulated views of a category page and image zoom for participants to select which image they felt was the best quality.
The views included pagination between selections as well as a "Thank you for completion" screen which displayed live results of the study.
results
Feel free to download the analysis of our collected data if you're interested in the details. Study Results PDF.
In short > the results came out inconclusive. Participants could not discern a visual disparity between the 3 image presets. We concluded this as a success. After a close inspection of the images and the results, we were able to move forward with delivering a 1.5x, 40% JPG quality image preset.
Delivery Strategy
As a customer progresses deeper into their journey, provide larger and higher quality images. Higher quality images at appropriate touchpoints empower shoppers during the carting and purchasing decision making process.


Before Change
return values.reshape(shape)
def _slice(self, idx):
warnings.warn("Slice for SQLite backend has no effect.")
def point(self, idx):
Return dictionary of point values at `idx` for current chain
with variables names as keys.
After Change
return values.reshape(shape)
def _slice(self, idx):
if idx.stop is not None:
raise ValueError("Stop value in slice not supported.")
return ndarray._slice_as_ndarray(self, idx)
def point(self, idx):
Return dictionary of point values at `idx` for current chain
with variables names as keys.


{% include head.html %}
{% include header.html %}
The first augmented spellbook for D&D 5e
{% include feature-spells.html %} {% include feature-characters.html %} {% include feature-keywords.html %} {% include feature-sphere.html %} {% include download-banner.html %} {% include footer.html %}


Triggers
A Trigger is somewhat similar to a Syslog Event: it specifies an action to happen based on one or more events. The idea is that
an Operator should be able to specify a Trigger to get information or to act upon one or more events among the devices
in the pool.
Basic Trigger
All Triggers build on top of one or more Syslog Events, so you first have to create a Syslog Event. In other words, Triggers act
upon messages sent to the system over Syslog. Make sure Trigger type is BASIC. Then specify an evaluation period between 15 and 120 minutes. The
evaluation period is the time the system counts the number of Syslog Events, and from which units these events are sent. Next specify
how many events must occur, and from how many devices they must come, to release the Trigger.
At this point you have specified how to release the trigger, but not what to do. There are several things which can happen:
- Send a notification, either REPORT or ALARM, in which case a notification interval is required (to avoid get swamped in reports/alarms).
- Run a script. This script must be a FreeACS shell script where you can perform all sorts of operations, searches, etc. To make the script
even more powerful, the system creates a file with those Unit-ids responsible for the release, and make it possible to use this file
in the script. The filename of this file is retrieved by using ${_1} in the script, and can then be looped over, printed, etc.
Composite Trigger
When you have multiple Basic Triggers, it can be valuable to combine them, to do things like "If Syslog Event A happens X times and
Syslog Event B happens Y times, then something should happen". A Composite Trigger can only be release if all it's "child Triggers" is released.
The child Triggers could be both Composite and Basic.


| Network Working Group | A. Malhotra |
| Internet-Draft | D. Schwartz |
| Intended status: Standards Track | Ripple |
| Expires: January 8, 2021 | July 07, 2020 |
PayID Protocol
draft-aanchal-payid-protocol-01
This specification defines the PayID protocol - an application-layer protocol, which can be used to interact with a PayID-enabled service provider. The primary use case is to discover payment account information along with optional metadata identified by a PayID [PAYID-URI]. The protocol is based on HTTP transfer of PayID protocol messages over a secure transport.
This specification is a draft proposal, and is part of the PayID Protocol work. Feedback related to this specification should be sent to<EMAIL_ADDRESS>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 8, 2021.
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This protocol can be referred to as the Basic PayID Protocol or PayID Protocol. The following terminology is used by this specification.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
[PAYID-URI] describes a URI scheme to identify payment account(s) at a service provider. [PAYID-DISCOVERY], on the other hand, defines how to transform a PayID URI into a PayID URL that can be used by other protocols to interact with a PayID-enabled service provider but does not define the protocol(s) to do so.
This document specifies the PayID protocol - an application-layer protocol which can be used to interact with a PayID-enabled service provider identified by a PayID URL using standard HTTP methods over a secure transport. In its most basic mode, a PayID protocol resource returns a JavaScript Object Notation (JSON) object representing the payment account(s) information along with optional metadata corresponding to the queried PayID URI [PAYID-URI]. The protocol defines new media formatting types for requests and responses, but uses normal HTTP content negotiation mechanisms for selecting alternatives that the PayID client and server may prefer in anticipation of serving different use cases.
Although the primary use case for the payment account(s) information resource returned via the Basic PayID protocol is assumed to be for making payments, the PayID protocol is designed to be easily extensible to facilitate creation and retrieval of other resources about the PayID owner, PayID client and/or PayID server that might be required for making payments.
The PayID protocol is designed to be a fundamentally neutral protocol. The PayID protocol is capable of returning a PayID owner's payment account(s) information for any network that they (or their service) can support. This makes the PayID protocol a network and currency agnostic protocol, capable of enabling payments in BTC, XRP, ERC-20 tokens, Lightning, ILP, or even fiat networks like ACH.
Just like email servers, anyone can run their own PayID server or use third-party hosted services. If self-hosted, the PayID protocol introduces no new counterparty risk or changes to a service’s security or privacy model. PayID protocol doesn’t require new, complex, and potentially unreliable peer discovery protocols, instead establishing direct peer-to-peer connections between communicating parties from the start. PayID is built on the most successful decentralized network: the web. There is no designated centralized authority, or a risk of a patchwork of different standards in different jurisdictions that make a global solution impossibly complex.
Each service provider that uses PayID for their users maintains full control of its PayID URL space and PayID service, and has the ability to incorporate any policies they choose, including privacy, authentication, and security. They also have full sovereignty over users on their domain, just like with email. PayID is highly generalized and does not prescribe any particular solution outside of the standardized communication, which makes it compatible with existing compliance and user management tools and philosophies.
To support PayID protocol, the PayID client needs to discover the PayID URL corresponding to the PayID URI [PAYID-URI]. This can be obtained either by using mechanisms described in [PAYID-DISCOVERY] or by manually entering the PayID URL.
JSON, as described in [RFC8259][], defines a test format for serializing structured data. Objects are serialized as an unordered collection of name/value pairs. JSON does not define any semantics around the name/value pairs that make up an object. PayID protocol's JSON format defines name/value pairs that annotate a JSON object, property or array for PayID protocol resources.
The PayID client MUST request a PayID response in JSON format through the Accept header with the media type as defined below, optionally followed by format parameters. One of the optional parameters is the case-insensitive q value as described in Section 5.3.1 of [RFC7231] to indicate relative preference.
Each message body is represented as a single JSON object. This object contains a name/value pair whose value is the correct representation for a primitive value as described in [RFC8259][], or an array or object as described in the section below.
If the PayID server does not support JSON format, it MUST reply with an appropriate error response.
The PayID protocol payment account(s) information resource is requested using the HTTP GET method.
Following are the media types to request the payment account(s) information resource on different payment-networks and environments.
The media type for the payment account information resource is application/* + json.
The response body for application/* + json is a JSON object with the following name/value pairs.
{ optional string payId, required Address[] addresses, optional string memo, optional string identity, optional ProofOfControlSignature proofOfControlSignature }
The value of payId field is the PayID URI in the client request that identifies the payment account information that the JSON object describes.
The payId field is an optional field in the response.
The value of addresses field is a JSON array of type Address of one or more JSON objects with the following name/value pairs.
{ required string paymentNetwork, optional string environment, required string addressDetailsType, required addressDetailsType addressDetails }
The addresses field MUST be present in the response.
We define the following two types of payment address types.
The memo string may specify additional metadata corresponding to a payment.
The memo string is an OPTIONAL field in the response.
The identity string may specify any additional identity information about the PayID owner or PayID server.
The identity string is an OPTIONAL field in the response.
The value of proofOfControlSignature field is a JSON object of type ProofOfControlSignature with the following name/value pairs.
{ required string publicKey, required string payID, required string hashAlgorithm, required string signature }
The proofOfControlSignature is an OPTIONAL field in the response.
* may represent different payment-networks and environments. In this document, we propose standards with the media types specific to XRP, ILP, and ACH payment networks. We also propose media types that return all addresses across all payment networks. Other payment networks MUST establish standard media types for their networks at IANA.
Returns XRPL mainnet XAddresses
Returns XRPL testnet XAddresses
Returns XRPL devnet XAddresses
Returns mainnet payment pointer to initiate SPSP request
Returns testnet payment pointer to initiate SPSP request
Returns account and routing number
The PayID client MAY specify more than one media type along with the preference parameter. The server MUST respond as described in the Content Negotiation section below.
PayID protocol defines semantics around the following request and response headers. Additional headers MAY be defined, but have no unique semantics defined in the PayID protocol.
The following headers are common between PayID requests and responses.
PayID requests and responses with a JSON message body MUST have a Content-Type header value of application-json.
As defined in [RFC7230][], a request or response SHOULD include a Content-Length header when the message's length can be determined prior to being transferred. PayID protocol does not add any additional requirements over HTTP for writing Content-Length.
The PayID client MUST include the PayID version request header field to specify the version of the PayID protocol used to generate the request.
If present on a request, the PayID server MUST interpret the request according to the rules defined in the specified version of the PayID protocol or fail the request with an appropriate error response code.
If not specified in a request, the PayID server MUST fail the request with an appropriate error code.
In addition to common Headers, the PayID client MUST specify the following request header.
The PayID client MUST specify the Accept request header field with at least one of the registered media types (Section X). The purpose of this header is to indicate what type of content can be understood in the response. It specifies the payment-network and environment of the payment account and its representation format for which the PayID client wants to receive information. The representation format is always JSON.
The PayID server MUST reject formats that specify unknown or unsupported format parameters.
In addition to the Common Headers, the PayID server MUST specify the following response header.
The PayID server MUST include the Cache-Control header with the max-age limit of 0. The intermediate hops or PayID client MUST NOT cache the responses.
PayID protocol supports extensibility in the payload, according to the specific format.
Regardless of the format, additional content MUST NOT be present if it needs to be understood by the receiver in order to correctly interpret the payload according to the specified PayID-Version header. Thus, clients MUST be prepared to handle or safely ignore any content not specifically defined in the version of the payload specified by the PayID-version header.
The PayID protocol defines semantics around certain HTTP request and response headers. Services that support a version of the PayID protocol conform to the processing requirements for the headers defined by this specification for that version.
Individual services MAY define custom headers. These headers MUST NOT begin with PayID. Custom headers SHOULD be optional when making requests to the service. A service MUST NOT require the PayID client to understand custom headers to accurately interpret the response.
A PayID service MUST support JSON format as described above and MAY support additional formats response bodies.
The Basic PayID protocol is used to request a payment account(s) information resource identified by a PayID URI from a PayID-enabled service provider identified by a PayID URL using HTTP over secure transport. When successful, the PayID protocol always returns the JSON representation of a payment account(s) information resource along with optional metadata. This information can be used for any purposes outside the scope of this document, though it is expected the most common application would be making payment.
The Basic PayID protocol comprises request and response messages, each of which is defined in more detail below. The following is a visual representation of the basic protocol flow:
PayID client PayID server | | | 1.) GET request to PayID URL | |--------------------------------------------------------->| | | | | | 2.) 200 Ok | | Payment account information response | |<---------------------------------------------------------| | | | |
A basic PayID client issues a query using the HTTP GET method to the PayID URL without any query parameters and body.
The PayID client MUST query the PayID server using HTTPS only. [RFC2818] defines how HTTPS verifies the PayID server's identity. If the HTTPS connection cannot be established for any reason, then the PayID client MUST accept that the PayID request has failed and MUST NOT attempt to reissue the PayID request using HTTP over a non-secure connection.
In response, the PayID server returns a JSON object representation of a payment account(s) information resource for the payment-network and environment requested by the PayID client in the request Accept header field, along with other required and/or optional metadata.
A PayID server MUST be able to process the application/payid+json header type.
If the PayID server does not contain the payment account information corresponding to the request, the PayID server MUST respond with an appropriate error message.
A PayID server MAY redirect the PayID client; if it does, the redirection MUST only be to an https URI and the PayID client MUST perform certificate validation again when redirected.
If the PayID server returns a valid response, the response will contain one or more of the fields defined above.
This section shows sample use of Basic PayID protocol in several hypothetical scenarios.
Suppose Alice wishes to send a friend some XRP from a web-based wallet provider that Alice has an account on. Alice would log-in to the wallet provider and enter Bob's PayID (say, bob$receiver.example.com) into the wallet UI to start the payment. The Wallet application would first discover the PayID URL for the PayID service-provider using one of the mechanisms described in PayID discovery [PAYID-DISCOVERY] protocol.
The Wallet application would then issue an HTTPS GET request:
GET /users/bob HTTP/1.1 Host: www.receiver.example.com Accept: application/payid+json PayID-version: 1.0
The PayID server might respond like this:
HTTP/1.1 200 OK Content-Type: application/json Content-Length: 403 PayID-version: 1.0 Cache-Control: max-age=0 Server: Apache/1.3.11 { "payId" : "bob$receiver.example.com", "addresses" : [ { "paymentNetwork" : "xrpl", "environment" : "testnet", "addressDetailsType" : "CryptoAddressDetails", "addressDetails" : { "address" : "XTVQWr6BhgBLW2jbFyqqufgq8T9eN7KresB684ZSHKQ3oDth" } }, { "paymentNetwork" : "ach", "environment" : "mainnet", "addressDetailsType" : "ACHAddressDetails", "addressDetails" : { "accountNumber" : "5674536253", "routingNumber" : "aYJTDFGLKAJD" } } ], "memo" : "Additional optional Information" }
In the above example we see that the PayID server returned a list of payment accounts identified by PayID bob$receiver.example.com. This is because Alice's Wallet asked for all the payment accounts corresponding to the PayID in the Accept header. Alice's Wallet MAY then use the payment account information to make payments.
Another example:
GET /users/bob HTTP/1.1 Host: www.receiver.example.com Accept: application/xrpl-testnet+json; q=0.4, application/ach+json; q=0.1 PayID-version= 1.0
The PayID server might respond like this:
HTTP/1.1 200 OK Content-Type: application/json Content-Length: 403 PayID-version: 1.0 Cache-Control: max-age=0 Server: Apache/1.3.11 { "payId" : "bob$receiver.example.com", "addresses" : [ { "paymentNetwork" : "xrpl", "environment" : "testnet", "addressDetailsType" : "CryptoAddressDetails", "addressDetails" : { "address" : "XTVQWr6BhgBLW2jbFyqqufgq8T9eN7KresB684ZSHKQ3oDth" } } ] }
A PayID server MAY respond to a request using any valid HTTP response code appropriate for the request. The PayID server SHOULD be as specific as possible in its choice of an HTTP specific status code.
The following response codes represent successful requests.
A request that does not create a resource returns 200 OK if it is completed successfully and the value of the resource is not null. null. In this case, the response body MUST contain the value of the resource specified in the request URL.
As per [RFC7231], a 3xx Redirection indicates that further action needs to be taken by the client in order to fulfill the request. In this case, the response SHOULD include a Location header, as appropriate, with the URL from which the result can be obtained; it MAY include a Retry-After header.
Error codes in the 4xx range indicate a client error, such as a malformed request. In the case that a response body is defined for the error code, the body of the error is as defined for the appropriate format.
The PayID client MAY choose to query for all possible payment addresses corresponding to a PayID URI
GET / HTTP/1.1 Accept: application/all+json
In this case, the PayID server MAY respond with all payment account(s) information associated with the queried PayID.
Alternatively, the PayID client MAY choose to query for a subset payment account(s) information in the order of preference.
GET / HTTP/1.1 Accept: application/xrpl-testnet+json; q=0.4, application/xrpl-mainnet+json; q= 0.1
In this case, the PayID server MUST respond with the payment account(s) information corresponding to at least one of the payment-networks and environments mentioned in the Accept header in the order of client request preference. If none of those exist, the PayID server MUST send an appropriate error response.
Alternatively, the PayID client MAY combine the above two approaches.
GET / HTTP/1.1 Accept: application/xrpl-testnet+json; q=0.4, application/xrpl-mainnet+json; q= 0.1, application/payid+json
In this case, the PayID server MUST respond with the payment account information corresponding to at least one of the payment-network and environment mentioned in the Accept header in the order of PayID client's preference. If none of those exist, then the PayID server MUST respond with payment account(s) information corresponding to all payment accounts associated with the queried PayID URI.
Versioning enables clients and servers to evolve independently. PayID protocol defines semantics for protocol versioning.
PayID requests and responses are versioned according to the PayID-version header. PayID clients include the PayID-version header in order to specify the maximum acceptable response version. PayID servers respond with the maximum supported version that is less than or equal to the requested major
This security considerations section only considers PayID clients and servers bound to implementations as defined in this document. Such implementations have the following characteristics:
The following are considered out-of-scope:
Basic PayID protocol's security model assumes the following network attackers:
Additionally we assume that the attacker has enough resources to mount an attack but can not break the security guarantees provided by the cryptographic primitives of the underlying secure transport.
The basic PayID protocol runs over HTTPS and thus relies on the security of the underlying transport. Implementations utilizing TLS 1.3 benefit from the TLS security profile defined in [RFC8446] against all the above network attackers.
As such, cryptography can not defend against DoS attacks because any attacker can stop/interrupt the PayID protocol by: * Dropping network packets, * Exhaustion of resources either at the network level or at PayID client and/or server.
The PayID servers are recommended to follow general best network configuration practices to defend against such attacks [RFC4732].
The HTTPS connection provides transport security for the interaction between PayID client and server but does not provide the response integrity of the data provided by PayID server. A PayID client has no way of knowing if data provided in the payment account information resource has been manipulated at the PayID server, either due to malicious behavior on the part of the PayID server administrator or as a result of being compromised by an attacker. As with any information service available on the Internet, PayID clients should be wary of the information received from untrusted sources.
The PayID client and server should be aware that placing information on the Internet means that any one can access that information. While PayID protocol is an extremely useful tool to discovering payment account(s) information corresponding to a human-rememberable PayID URI, PayID owners should also understand the associated privacy risks. The easy access to payment account information via PayID protocol was a design goal of the protocol, not a limitation.
PayID protocol MUST NOT be used to provide payment account(s) information corresponding to a PayID URI unless providing that data via PayID protocol by the relevant PayID server was explicitly authorized by the PayID owner. If a PayID owner wishes to limit access to information, PayID servers MAY provide an interface by which PayID owners can select which information is exposed through the PayID server interface. For example, PayID servers MAY allow PayID owners to mark certain data as public and then utilize that marking as a means of determining what information to expose via PayID protocol. The PayID servers MAY also allow PayID owners to provide a whitelist of users who are authorized to access the specific information. In such a case, the PayID server MUST authenticate the PayID client.
The power of PayID protocol comes from providing a single place where others can find payment account(s) information corresponding to a PayID URI, but PayID owners should be aware of how easily payment account information that one might publish can be used in unintended ways. As one example, one might query a PayID server only to see if a given PayID URI is valid and if so, get the list of associated payment account information. If the PayID server uses the same payment address each time, it becomes easy for a third-party to track one's entire payment history. The PayID server MUST follow the best practice of payment address rotation for every query to mitigate this privacy concern.
PayID protocol over HTTPS encrypts the traffic and requires mutual authentication of the PayID client and the PayID server. This mitigates both passive surveillance [RFC7258] and the active attacks that attempt to divert PayID protocol queries to rogue servers.
Additionally, the use of the HTTPS default port 443 and the ability to mix PayID protocol traffic with other HTTPS traffic on the same connection can deter unprivileged on-path devices from interfering with PayID operations and make PayID traffic analysis more difficult.
The Basic PayID protocol data contains no information about the PayID client; however, various transports of PayID queries and responses do provide data that can be used to correlate requests. A Basic PayID protocol implementation is built on IP, TCP, TLS and HTTP. Each layer contains one or more common features that can be used to correlate queries to the same identity.
At the IP level, the PayID client address provides obvious correlation information. This can be mitigated by use of NAT, proxy, VPN, or simple address rotation over time. It may be aggravated by use of a PayID server that can correlate real-time addressing information with other identifiers, such as when PayID server and other services are operated by the same entity.
PayID client implementations that use one TCP connection for multiple PayID requests directly group those requests. Long-lived connections have better performance behaviours than short-lived connections; however they group more requests, which can expose more information to correlation and consolidation. TCP-based solutions may also seek performance through the use of TCP Fast Open [RFC7413]. The cookies used in TCP Fast open may allow PayID servers to correlate TLS connections together.
TCP-based implementations often achieve better handshake performance through the use of some form of session resumption mechanism, such as Section 2.2 of [RFC8446]. Session resumption creates a trivial mechanism for a server to correlate TLS connections together.
HTTP's feature set can also be used for identification and tracking in a number of ways. For example, Authentication request header fields explicitly identify profiles in use and HTTP cookies are designed as an explicit state-tracking mechanism and are often used as an authentication mechanism.
Additionally, the User-Agent and Accept-Language request header fields often convey specific information about the PayID client version or locale. This allows for content-negotiation and operational work-arounds for implementation bugs. Request header fields that control caching can expose state information about a subset of the client's history. Mixing PayID queries with other HTTP requests on the same connection also provides an opportunity for richer data correlation.
The PayID protocol design allows implementations to fully leverage the HTTP ecosystem, including features that are not enumerated in this document. Utilizing the full set of HTTP features enables PayID to be more than HTTP tunnel, but it is at the cost of opening up implementations to the full set of privacy considerations of HTTP.
Implementations of PayID clients and servers need to consider the benefits and privacy impacts of these features, and their deployment context, when deciding whether or not to enable them. Implementations are advised to expose the minimal set of data needed to achieve the desired feature set.
Determining whether or not PayID client implementation requires HTTP cookie [RFC6265] support is particularly important because HTTP cookies are the primary state tracking mechanism in HTTP, HTTP cookies SHOULD NOT be accepted by PayID clients unless they are explicitly required by a use case.
Overall, the PayID protocol does not introduce significant additional privacy concerns beyond those associated with using the underlying IP, TCP, TLS and HTTP layers.
This document defines registries for PayID protocol version and application/* +json media types.
Header field name: PayID-version: major.minor
Applicable Protocol: "PayID protocol"
Status: standard
Author/Change controller: Refer to the contact details of the authors in this document.
Specification Document: PayID protocol
This document registers multiple media types, listed in Table 1.
| Type | Subtype | Specification |
|---|---|---|
| application | xrpl-mainnet+json | |
| application | xrpl-testnet+json | |
| application | xrpl-devnet+json | |
| application | ach+json | |
| application | interledger-mainnet+json | |
| application | interledger-testnet+json | |
| application | payid+json |
Type Name: application
Subtype name: This document registers multiple subtypes as listed in table 1
Required parameters: n/a
Optional parameters: n/a
Encoding considerations: Encoding considerations are identical to those specified for the "application/json" media type. See[RFC7159][].
Security considerations: Security considerations relating to the generation and consumption of PayID protocol messages are discussed in Section X.
Interoperability considerations: This document specifies the format of conforming messages and the interpretation thereof.
Published specification: This document is the specification for these media types; see Table 1 for the section documenting each media type.
Applications that use this media type: PayID servers and PayID clients.
Additional information:
Magic number(s): n/a
File extension(s): This document uses the mime type to refer to protocol messages and thus does not require a file extension.
Macintosh file type code(s): n/a
Person & email address to contact for further information: See Authors' Addresses section.
Intended usage: COMMON
Restrictions on usage: n/a
Author: See Authors' Addresses section.
Change controller: Internet Engineering Task Force (mailto:iesg@ietf.org).
| [PAYID-DISCOVERY] | Fuelling, D., "PayID Discovery", n.d.. |
| [PAYID-URI] | Fuelling, D., "The 'payid' URI Scheme", n.d.. |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC2818] | Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/RFC2818, May 2000. |
| [RFC6265] | Barth, A., "HTTP State Management Mechanism", RFC 6265, DOI 10.17487/RFC6265, April 2011. |
| [RFC7231] | Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, DOI 10.17487/RFC7231, June 2014. |
| [RFC7258] | Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May 2014. |
| [RFC7413] | Cheng, Y., Chu, J., Radhakrishnan, S. and A. Jain, "TCP Fast Open", RFC 7413, DOI 10.17487/RFC7413, December 2014. |
| [RFC8446] | Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018. |
| [RFC4732] | Handley, M., Rescorla, E. and IAB, "Internet Denial-of-Service Considerations", RFC 4732, DOI 10.17487/RFC4732, December 2006. |


execline
Software
skarnet.org
The withstdinas program
withstdinas reads the entirety of its standard input in an
environment variable, and runs another program with that additional
environment variable.
Interface
In an execlineb script:
withstdinas [ -i | -I | -D default ] [ -N | -n ] [ -E | -e ] variable prog...
- withstdinas reads its stdin until EOF.
- It then execs into prog..., with
variable added to the environment; the value of
variable is what was read on stdin.
Options
- -N : do not chomp an ending newline off stdin.
- -n : chomp an ending newline off stdin. This is the default.
- -e : no autoimport. This is the default.
- -E : autoimport. Instead of exec'ing into
prog..., exec into importas -ui variable variable
prog.... This substitutes variable into the command
line instead of putting it into the environment.
The other options tell withstdinas what to do if its input is
not suitable as the contents of an environment variable, i.e. it
contains a null character:
- -i : withstdinas exits 1.
- -I : variable is removed from
the environment, and execution proceeds.
- -D default : the value of variable
is set to default, and execution proceeds.
- neither of those options: the value of variable is set to whatever the
start of the input is, up to the first null character; and execution proceeds.
Notes
- You can start prog... with "importas -u variable variable"
to perform variable substitution.


{% extends "base.html" %} {% block title %}About LastGraph{% endblock %} {% block content %}
LastGraph is a web-based service that aims to give you a new way to explore your last.fm listening history. We use the last.fm API to transfer across your basic profile data, and then crunch it around in various interesting (and often hilariously inefficient) ways.
The site is written and run by Andrew Godwin.
LastGraph currently offers the following:
It's now over five years old, and so unlikely to gain any improvements, but if it stops working then get in touch with me andrew at aeracode dot org.
LastGraph can often be a bit slow to load your profile, as we're limited to pulling data in from last.fm at ten requests a second, so your profile could take up to 20 seconds to be fetched once you reach the head of the fetching queue.
Once you've queued up a fetch (or a poster), you can go somewhere else and come back later to see how far we've got with it; you can just type your name in the box again to see.
If you find any bugs or problems in the site, then please email/jabber me at andrew at aeracode dot org. I'll try and get back to you (and hopefully fix any problems) as soon as I can, but be aware there are in fact times when I'm really not sitting at my computer.
The LastGraph interface, live graphs and queueing/scheduling system are written in Django, and the poster renderer is a plain Python application, using my own Graphication graphing library, developed specifically for LastGraph. Posters are stored and served from Amazon S3.
If you'd like to know more about the technology behind LastGraph, then have a look at my project page for it, or sling me an email at andrew at aeracode dot org - I'll be happy to discuss it with you.


Honzi/Personal Bests/Hearthstone/The Boomsday Project
| Beakered Lightning
| 0
| Common
| Shaman
| 2
|
|
| Topsy Turvy
| 0
| Common
| Priest
| 2
|
|
| Autodefense Matrix
| 1
| Common
| Paladin
| 2
| 1
|
| Biology Project
| 1
| Common
| Druid
| 2
|
|
| Cloning Device
| 1
| Common
| Priest
| 2
|
|
| Crystallizer
| 1
| Epic
| Neutral
| 1
| 1
|
| Crystology
| 1
| Rare
| Paladin
| 2
|
|
| Eternium Rover
| 1
| Common
| Warrior
| 2
|
|
| Faithful Lumi
| 1
| Common
| Neutral
| 2
|
|
| Glow-Tron
| 1
| Common
| Paladin
| 2
| 2
|
| Goblin Bomb
| 1
| Common
| Neutral
| 2
|
|
| Mecharoo
| 1
| Common
| Neutral
| 2
|
|
| Omega Assembly
| 1
| Rare
| Warrior
| 2
|
|
| Pogo-Hopper
| 1
| Rare
| Rogue
| 2
|
|
| Secret Plan
| 1
| Common
| Hunter
| 2
| 1
|
| Shooting Star
| 1
| Common
| Mage
| 2
| 1
|
| Skaterbot
| 1
| Common
| Neutral
| 2
|
|
| Soul Infusion
| 1
| Rare
| Warlock
| 2
|
|
| Spirit Bomb
| 1
| Common
| Warlock
| 2
| 1
|
| Test Subject
| 1
| Rare
| Priest
| 2
|
|
| The Soularium
| 1
| Legendary
| Warlock
| 1
|
|
| Voltaic Burst
| 1
| Rare
| Shaman
| 2
|
|
| Astral Rift
| 2
| Rare
| Mage
| 2
|
|
| Bomb Toss
| 2
| Common
| Hunter
| 2
|
|
| Celestial Emissary
| 2
| Rare
| Mage
| 2
| 1
|
| Cloakscale Chemist
| 2
| Common
| Neutral
| 2
|
|
| Crystalsmith Kangor
| 2
| Legendary
| Paladin
| 1
|
|
| Cybertech Chip
| 2
| Rare
| Hunter
| 2
|
|
| Dead Ringer
| 2
| Common
| Priest
| 2
|
|
| Demonic Project
| 2
| Common
| Warlock
| 2
|
|
| Dendrologist
| 2
| Rare
| Druid
| 2
| 1
|
| Elementary Reaction
| 2
| Common
| Shaman
| 2
|
|
| Fireworks Tech
| 2
| Rare
| Hunter
| 2
| 2
|
| Galvanizer
| 2
| Rare
| Neutral
| 2
|
|
| Lab Recruiter
| 2
| Common
| Rogue
| 2
|
|
| Menacing Nimbus
| 2
| Common
| Shaman
| 2
|
|
| Omega Mind
| 2
| Epic
| Shaman
| 2
|
|
| Research Project
| 2
| Common
| Mage
| 2
|
|
| Rocket Boots
| 2
| Common
| Warrior
| 2
|
|
| Spark Engine
| 2
| Rare
| Neutral
| 2
|
|
| Toxicologist
| 2
| Common
| Neutral
| 2
|
|
| Unpowered Mauler
| 2
| Rare
| Neutral
| 2
|
|
| Upgradeable Framebot
| 2
| Common
| Neutral
| 2
|
|
| Venomizer
| 2
| Common
| Hunter
| 2
|
|
| Violet Haze
| 2
| Common
| Rogue
| 2
|
|
| Void Analyst
| 2
| Rare
| Warlock
| 2
|
|
| Weapons Project
| 2
| Common
| Warrior
| 2
|
|
| Whirliglider
| 2
| Common
| Neutral
| 2
| 1
|
| Augmented Elekk
| 3
| Epic
| Neutral
| 1
|
|
| Brainstormer
| 3
| Common
| Neutral
| 2
| 1
|
| Bronze Gatekeeper
| 3
| Common
| Neutral
| 2
|
|
| Doubling Imp
| 3
| Common
| Warlock
| 2
| 1
|
| Electrowright
| 3
| Common
| Neutral
| 2
|
|
| Extra Arms
| 3
| Rare
| Priest
| 2
|
|
| Kaboom Bot
| 3
| Common
| Neutral
| 2
|
|
| Landscaping
| 3
| Common
| Druid
| 2
|
|
| Microtech Controller
| 3
| Common
| Neutral
| 2
|
|
| Necrium Blade
| 3
| Rare
| Rogue
| 2
|
|
| Nethersoul Buster
| 3
| Rare
| Warlock
| 2
| 1
|
| Omega Medic
| 3
| Rare
| Priest
| 2
| 1
|
| SN1P-SN4P
| 3
| Legendary
| Neutral
|
| 1
|
| Spider Bomb
| 3
| Rare
| Hunter
| 2
| 1
|
| Spring Rocket
| 3
| Common
| Neutral
| 2
|
|
| Unexpected Results
| 3
| Epic
| Mage
| 2
|
|
| Annoy-o-Module
| 4
| Rare
| Paladin
| 2
|
|
| Blightnozzle Crawler
| 4
| Rare
| Rogue
| 2
|
|
| Coppertail Imposter
| 4
| Common
| Neutral
| 2
| 1
|
| Cosmic Anomaly
| 4
| Common
| Mage
| 2
|
|
| Explodinator
| 4
| Common
| Neutral
| 2
|
|
| Juicy Psychmelon
| 4
| Epic
| Druid
| 1
|
|
| Necromechanic
| 4
| Epic
| Hunter
| 1
|
|
| Omega Defender
| 4
| Epic
| Neutral
| 2
|
|
| Piloted Reaper
| 4
| Common
| Neutral
| 2
|
|
| Prismatic Lens
| 4
| Epic
| Paladin
| 2
|
|
| Replicating Menace
| 4
| Rare
| Neutral
| 2
| 1
|
| Steel Rager
| 4
| Common
| Neutral
| 2
|
|
| Storm Chaser
| 4
| Rare
| Shaman
| 2
|
|
| Thunderhead
| 4
| Epic
| Shaman
| 2
|
|
| Weaponized Piñata
| 4
| Epic
| Neutral
| 1
|
|
| Crazed Chemist
| 5
| Common
| Rogue
| 2
| 1
|
| Dyn-o-matic
| 5
| Rare
| Warrior
| 2
|
|
| Mechano-Egg
| 5
| Common
| Paladin
| 2
| 2
|
| Myra Rotspring
| 5
| Legendary
| Rogue
| 1
|
|
| Myra's Unstable Element
| 5
| Legendary
| Rogue
| 1
|
|
| Necrium Vial
| 5
| Epic
| Rogue
| 1
|
|
| Omega Agent
| 5
| Epic
| Warlock
| 1
|
|
| Power Word: Replicate
| 5
| Epic
| Priest
| 2
|
|
| Reckless Experimenter
| 5
| Epic
| Priest
| 1
| 1
|
| Rusty Recycler
| 5
| Common
| Neutral
| 2
|
|
| Seaforium Bomber
| 5
| Epic
| Neutral
| 1
|
|
| Shrink Ray
| 5
| Rare
| Paladin
| 2
|
|
| Wargear
| 5
| Common
| Neutral
| 2
|
|
| Zilliax
| 5
| Legendary
| Neutral
|
| 1
|
| Arcane Dynamo
| 6
| Rare
| Neutral
| 2
| 1
|
| Damaged Stegotron
| 6
| Common
| Neutral
| 2
| 1
|
| Ectomancy
| 6
| Epic
| Warlock
| 1
|
|
| Eureka!
| 6
| Rare
| Shaman
| 2
|
|
| Giggling Inventor
| 6
| Rare
| Neutral
| 2
|
|
| Mechanical Whelp
| 6
| Rare
| Neutral
| 2
|
|
| Meteorologist
| 6
| Rare
| Mage
| 2
| 1
|
| Missile Launcher
| 6
| Rare
| Neutral
| 2
|
|
| Security Rover
| 6
| Rare
| Warrior
| 2
|
|
| Spark Drill
| 6
| Rare
| Neutral
| 2
|
|
| Tending Tauren
| 6
| Rare
| Druid
| 2
|
|
| Boommaster Flark
| 7
| Legendary
| Hunter
| 1
|
|
| Dreampetal Florist
| 7
| Epic
| Druid
| 2
|
|
| Gloop Sprayer
| 7
| Common
| Druid
| 2
|
|
| Kangor's Endless Army
| 7
| Legendary
| Paladin
| 1
|
|
| Star Aligner
| 7
| Epic
| Neutral
|
| 1
|
| Bull Dozer
| 9
| Common
| Neutral
| 2
|
|
| Mulchmuncher
| 9
| Rare
| Druid
| 2
|
|
| Mecha'thun
| 10
| Legendary
| Neutral
| 1
|
|


[gecode-users] Access to the last propagator invoked in case of ES_FAILED
Mikael Zayenz Lagerkvist
zayenz at gmail.com
Thu Mar 27 15:27:13 CET 2008
Hi,
There is no way currently to access this information, and no current
plans to introduce it. However, it would not be hard to implement
yourself. As a starting-point, see the implementation of the function
Space::status in gecode/kernel/core.cc.
What is it that you want to do with this information? Since
propagators do not have any identifier that is stable between copies,
the information seems to me to be of little use.
Cheers,
Mikael
On Thu, Mar 27, 2008 at 3:03 PM, David Rijsman <davidrijsman at gmail.com> wrote:
> I would like to know if it is possible to determine the last propator
> invoked in case Space::status returns ES_FAILED or if there are any
> plans to expose this information. If one can get this information (in
> the future) will one also introduce reflection API on the Propagator
> level?
>
> David Rijsman
>
> _______________________________________________
> Gecode users mailing list
> users at gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
>
--
Mikael Zayenz Lagerkvist, http://www.ict.kth.se/~zayenz/
More information about the gecode-users
mailing list


steven paul jobs
Biography
"Design is not just what it looks like and feels like. Design is how it works."
Steven Paul Jobs or 'Steve Jobs' as he was better known was an American entrepeneur and a forefather to the modern technological and media indsutries. He was a prolific leader and investor with influence in the boardroom within Pixar as well as The Walt Disney Company when they eventually acquisitioned the former. However he was most notably known as the chairman, CEO and co-founder of 'Apple Inc.'. Alongside his partner Steve Wozniak Steve pioneered the 'personal computer revolution' of the 80's and 90's bringing to our doorstep the portable computer or 'PC' that we know and love today.
Together the duo found their way into fame and fortune; building off of their success with Wozniak's 'Apple I' personal computer, when they released the incredibly ground breaking second generation. One of the first mass-produced microcomputers to achieve financial success. However this was only to be the first of many successes to come; with Jobs highlighting areas of potential within the tech sphere and working alongside his partner to harness the latent ability within them. Creating products with a focus on harnessing functionaly through intelligent design Apple grew into the tech powerhouse it is today. The same principles can be seen today in 'glassmorphism' in the UI space; a simple, minimalistic design that leads beautifully into the modern aesthetic we assosciate with new technology.
Timeline:
- 1955 - Born
- 1968 - Summer Job with 'Hewlett-Packard'
- 1968 - Attended 'Homestead High School' where he met Wozniak
- 1971 - Attending AP classes at Stanford and selling a low-cost 'blue-box' alongside Wozniak
- 1972 - Attended 'Reed College' for a semester before dropping out and continuing to attend by auditing his classes
- 1974 - Hired by 'Atari Inc.' as a technician
- 1974 - Left to India in pursuit of enlightenment and became a practitioner of 'Zen Buddhism'
- 1975 - Attended meetings of the 'Homebrew Computer Club'
- 1976 - Jobs suggests to Wozniak that they sell his 'Apple I' computer
- 1976 - 'Apple Computer Company' is founded out of Job's garage
- 1977 - Jobs and Wozniak present the 'Apple II' at the 'West Coast Computer Faire'
- 1978 - Jobs is worth over $1 million
- 1980 - Jobs is worth over $250 million
- 1981 - Jobs began directing the development of the 'Macintosh'
- 1984 - Jobs introduces 'Macintosh' to the world
- 1985 - Jobs resigns from 'Apple' due to the 'Macintosh's' inability to outcompete with and founds 'NeXT Inc.'
- 1990 - 'NeXT workstations' first released
- 1990 - Revised second generation 'NeXTcube' released
- 1993 - 'NeXT' transitions into software development with 'NeXTSTEP/Intel'
- 1996 - 'NeXT' releases 'WebObjects' a framework for web application development that was eventually used for the construction and running of the 'Apple Store' and 'iTunes Store'
- 1997 - 'NeXT' acquired by 'Apple Inc.' for $427 million
- 2000 - Jobs becomes CEO of Apple and begins branching out in terms of the technological avenues that 'Apple Inc.' develops within
- 2003 - Jobs is diagnosed with pancreatic cancer
- 2004 - Tumor is removed
- 2006 - Jobs delivers keynote for Apple's 'Worldwide Developer's Conference' he is described as 'gaunt. Only his wife and doctor know the cancer has returned
- 2007 - Apple releases the 'iPhone'
- 2008 - Following Job's keynote address similar concerns are aired
- 2009 - Jobs unergoes a liver transplant
- 2011 - Jobs resigns from Apple though he is still involved in marketing releases such as the 'Ipad 2'
- 2011 - Steve Jobs passes away from complications originating from his relapse that result in respiratory arrest
It is clear from a simple timeline of Steve Job's life that he personally guided the economic and industrial spheres of technology into the consumer industry that it is today. Although the argument could be made that technology was always destined to hold great importance in our society; a direct result of its incredible utilitarian function, it cannot be argued that without Job's influence the way it would have manifested would be entirely diffferent. One of the most tangible results of this influence is in the standards that today's UI/UX best practices revolve around; with a focus on simple, interactive functionality.
Not only does this directly mirror Jobs' own philosophy when it comes to technology; he himself prioritizing ergonomics as much as he did aesthetics, a lot of UI's design output is based on work he headed. Glassmorphism is a key example of this in that it is a direct derivative from Apple's approach to UI. The frosted glass effect has a modern, visual appeal in how unique its opacity's intercation is with the background behind it. It allows the front-end developer to break some of the cardinal rules of background design as it actually leans into a display of bright colors. Furthermore the simple, sparse 'card' organization forces the front-end developer to organize their information in a minimalist, cohesive fashion.
As is always the case in the UI community the design has permeated beyond Apple products with programmers keen to solve the mysteries behind the unique visual display. And by the same merit 'glassmorphism' is destined to be overused and to grow boring for the user. However I can say with marked confidence that the next trend to take its place in the limelight will stringently follow Jobs' tenents of simplicity in both function and aesthetics.


User Stories:
1. I can submit a form object that includes a file upload.
2. The from file input field has the "name" attribute set to "upfile". We rely on this in testing.
3. When I submit something, I will receive the file name, and size in bytes within the JSON response.
Usage:
Please upload a file:


Provides a standardized way to define metadata on programmatic elements of a Typescript application by using classes and decorators. The data being attached is called an "annotation" and is represented as an instance of an Annotation class, and the functions which attach the metadata are called "decorators".
Annotations are stored directly on the object using Object.defineProperty
to avoid annotations applied to superclasses from appearing on their subclasses.
First, create a subclass of Annotation. You will need to assign the annotation a "metadata name", which should be of the form package-name:decorator-name
as shown below. Omitting @MetadataName()
is an error.
@MetadataName('@myorg/mypackage:Color')
export class ColorAnnotation extends Annotation {
constructor(readonly color : string) {
super();
}
}
Next, export your new Annotation's decorator:
export const Color = ColorAnnotation.decorator();
You can extract the annotations for a target by using the appropriate static method on your Annotation subclass. For instance, to get all ColorAnnotations
on class Cat
, use:
let annotations : ColorAnnotation[] = ColorAnnotation.getAllForClass(Cat);
If you are not expecting more than one of the same annotation, use getForClass()
to get the first matching annotation:
let annotation : ColorAnnotation = ColorAnnotation.getForClass(Cat);
You can attach and retrieve annotations on classes, methods, properties, constructor parameters and method parameters.
You can enforce that your annotation's decorator can only be used on the decoration targets you expect:
export const Color = ColorAnnotation.decorator({
validTargets: [ 'class', 'method' ]
});
Valid targets are class
, method
, property
, constructorParameter
and parameter
. If a developer tries to decorate an invalid target with your decorator, an AnnotationTargetError
is thrown.
Sometimes it is desirable to prevent users from applying your decorator to a target more than once. Typically doing this is not an error, and Alterior can return all the annotation instances created by multiple decorators on a given target. However, Alterior can generate an error if a decorator for an annotation is used when an annotation of that type is already attached to the target, using the allowMultiple: false
option:
export const Color = ColorAnnotation.decorator({
allowMultiple: false
});
By default allowMultiple
is true and the library allows the annotation decorator to be used as many times as the user desires.
Sometimes you may want to add additional behavior to be run when the decorator is being applied. To do that, you can provide a factory
option to your decorator:
export const Color = ColorAnnotation.decorator({
factory(site : DecoratorTarget, name : string) {
// do special stuff here before
// returning the annotation to be attached.
return new ColorAnnotation(name);
}
})
Sometimes you have multiple decorators that are storing the same type of metadata. For instance, perhaps many of your users use 'red' and 'blue' with your @Color()
decorator, so you decide to make it so your users can use @Red()
and @Blue()
instead. One way you might accomplish this is:
export const Color = ColorAnnotation.decorator();
export const Red = () => Color('red');
export const Blue = () => Color('red');
(This is probably only useful inside Alterior; it is used to provide Angular compatibility for @alterior/di
)
This library stores annotations the same way that Angular does, and does it in a compatible manner. However, all Alterior annotations will be ignored by Angular unless an Angular-specific metadata name is applied to the annotation. This can be done using the @NgMetadataName()
decorator. The decorator causes the annotation instances to have their ngMetadataName
property set to the string passed to the decorator.
Generated using TypeDoc


6.6
domestic | energy | mechanical ventilation and air conditioning | 2010
Every
building
must be designed and
constructed
in such a way that:
(a)
the form and fabric of the
building
minimises the use of
mechanical ventilating or cooling systems for cooling
purposes; and
(b)
ventilating and cooling systems installed are energy efficient
and are capable of being controlled to achieve optimum
energy efficiency.
Limitation:
This standard does not apply to
buildings
which do not use fuel or power
for ventilating or cooling the internal environment.
6.6.0 Introduction
air-conditioning systems or use mechanical ventilation systems for cooling
purposes, as this leads to increased energy use and higher carbon dioxide
emissions. In view of this, guidance is intended to promote designs that avoid
the need for such systems in
dwellings.
However where such systems are
installed, which should generally only be a consideration when working with
existing
buildings
, a performance specification to limit energy use is set out.
With the drive to reduce carbon dioxide emissions and limit energy demand
in
buildings
, the need arises to consider efficient use of mechanical systems,
including ventilation. Accordingly, guidance is now offered on power
consumption and controls of such systems and on the efficiency of systems
that incorporate heat recovery.
In the case of
conversions
, as specified in regulation 4, the
building
as
converted
shall meet the requirements of this standard in so far as is
reasonably practicable
, and in no case be worse than before the conversion
(regulation 12, schedule 6).
6.6
—
6.6.0
domestic | energy | mechanical ventilation and air conditioning | 2010
Reducing overheating
CE 129 EST
In order to minimise any need for mechanical ventilation for cooling or
air-conditioning due to high internal temperatures in hot weather the following
issues should be considered with regard to the form and the fabric of the
dwelling
:
a. proportion of translucent
glazing
taking into account the need for
daylighting and artificial lighting (section 3 Environment and standard 6.5);
b. orientation of translucently
glazed
areas;
c. solar shading or other solar control measures where areas of the external
building
fabric are susceptible to solar gain;
d. natural ventilation (including night cooling); and
e. thermal mass.
Further information is available in the Energy Saving Trust publication
CE129
- 'Reducing Overheating - A Designer's Guide'.
windows/rooflights on one southerly elevation which is orientated between
due east and due west) or a high proportion of translucent
glazing
:
a. the
dwelling
should be designed to avoid high internal temperature (refer
to advice above); and
b. it should be shown by calculation that the ‘likelihood of high internal
temperature in hot weather’ in the
dwelling
is ‘not significant, slight or
medium’. The recommended method to assess this is Appendix P to SAP
2009. The intention is to avoid the situation where a
dwelling occupier
installs mechanical cooling or air-conditioning at a later date.
Cooling system
Where a mechanical cooling system is to be considered for a
dwelling
:
a. the
dwelling
should first be designed to avoid any need for a cooling
system (refer to advice above);
b. then the ‘likelihood of high internal temperature in hot weather’ should be
assessed using Appendix P of SAP 2009.
If the 'likelihood of high internal temperature' is 'not significant, slight or
medium' an air-conditioning system should not be installed.
6.6.2 Efficiency of air conditioning systems
Where a need for cooling is identified which cannot be addressed by the
measures identified in clause 6.6.1 and installation of air conditioning or
similar non-passive cooling is proposed, controls and system efficiency
should minimise additional energy demand, as follows:
•
air-cooled air conditioners working in cooling mode should have an Energy
Efficiency Rating greater than 2.4;
•
water-cooled air conditioners working in cooling mode should have an
Energy Efficiency Rating greater than 2.5;
•
fixed air conditioners should have an energy efficiency classification equal
to or better than Class C in Schedule 3 of the labelling scheme adopted
under The Energy Information (Household Air Conditioners) (No. 2)
Regulations, SI 2005/1726; and
•
controls should prevent the operation of simultaneous heating and cooling
within any area of the
building
.
6.6.1
—
6.6.2
domestic | energy | mechanical ventilation and air conditioning | 2010
6.6.3 Efficiency of mechanical ventilation systems
Energy demand arising from the use of mechanical ventilation should be
limited to ensure efficient operation. Specific fan power (SFP) for domestic
extract systems should be no greater than the values noted below:
Extract type
SFP
intermittent extract ventilation; continuous
supply ventilation
0.5 W/l/s
continuous extract ventilation
0.7 W/l/s
continuous supply and extract with heat
recovery ventilation[1]
1.5 W/l/s
Notes:
1.
The heat recovery efficiency of a mechanical ventilation and heat
recovery (MVHR) system should be 70% or more.
The design and installation of ductwork design can have a significant effect
on the effectiveness of a ventilation system. Further guidance on basic good
practice in installation and commissioning of ventilation systems can be
found on the
Technical Guidance
page of the Building Standard
Divisions website.
Reference should also be made to section 3 Environment for the provision of
ventilation to
buildings
.
Advice on the selection of systems can be found in the Energy Saving Trust
document
GPG 268
– ‘Energy efficient ventilation in housing- a guide for
6.6.3
—
6.6.3
specifiers’.