Introduction
Welcome to Live Coin Watch API documentation page!
If you're extremely impatient, just jump to API playground
In this document, you should be able to find everything you need to know to use our API, but if you need help, you're welcome to drop in and ask questions at few places:
- Simple mail always works.
- Trollbox on our site.
- Our Twitter, if it's really that bad.
- Telegram channel is very fun as well.
Issues specific to the API documentation should be created at Issues page.
Now, to follow remainder of the document, let's set you up with your preferred environment of choice...
Environments
If you're interested in only exploring the API, there's not better place than API playground, in which case you can ignore this chapter.
The following are environments we officialy support, though you're welcome to write-up a wrapper - it's all simple and standard protocols really. Be sure to let us know about it, so we can maybe include it in the documentation!
Shell
curl -X POST https://api.livecoinwatch.com \
-H 'content-type: application/json'
For just exploring and playing around with the API, this might be the simplest option. All examples should run in most shells, as the only command used is the all-mighty cURL.
JavaScript
await fetch(new Request('https://api.livecoinwatch.com'), {
method: 'POST',
headers: new Headers({ 'content-type': 'application/json' })
})
All the examples are written for modern browers.
Most examples should be easily portable to run in other JavaScript environments like Node.js or not even needing any changes from browser version with Deno.
PHP
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com', 'r', false, $context);
print_r(stream_get_contents($fp));
All PHP examples are written using pure PHP without using any dependencies. These examples should work on versions of PHP that support stream_context_create & stream_get_contents (Supported versions: PHP 5, PHP 7, PHP 8).
Concepts
We've tried to keep the API surface simple and efficient, so let's discuss few concepts that apply to the entirety of the API.
There Is Only One Domain
curl -X POST 'https://api.livecoinwatch.com/status' \
-H 'content-type: application/json'
await fetch(new Request('https://api.livecoinwatch.com/status'), {
method: 'POST',
headers: new Headers({ 'content-type': 'application/json' })
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/status', 'r', false, $context);
print_r(stream_get_contents($fp));
If everything's fine, you should get...
{}
...bag of nothing, that's right! On the other hand, if something's wrong, you should get some kind of error:
{
"error": {
"code": 503,
"status": "Service unavailable.",
"description": "We're temporarily offline for maintenance. Please try again later."
}
}
Everything runs from a single domain, and that is api.livecoinwatch.com
. All your HTTPS requests go there.
Try running code examples and see for yourself.
There Is Only One Key
curl -X POST 'https://api.livecoinwatch.com/credits' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>'
await fetch(new Request('https://api.livecoinwatch.com/credits'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
})
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/credits', 'r', false, $context);
print_r(stream_get_contents($fp));
Don't forget to replace
<YOUR_API_KEY>
with one you've got. Return response should be:
{
"dailyCreditsRemaining": 4321,
"dailyCreditsLimit": 10000
}
Live Coin Watch uses API keys to access all end-points. You can generate a new API key at your profile page. Authorizing with your API key is as simple as providing HTTP header x-api-key: <YOUR_API_KEY>
.
All (but one) API end-points need to include this header.
You can only ever have one active key, but you can regenerate that one, in the case you lose it or you don't trust it being secret anymore.
Keep the key somewhere private, safe & handy.
There Is Only One Method
curl 'https://api.livecoinwatch.com/status' \
-H 'content-type: application/json'
await fetch(new Request('https://api.livecoinwatch.com/status'), {
method: 'GET',
headers: new Headers({ 'content-type': 'application/json' })
})
$context_options = array (
'http' => array (
'method' => 'GET',
'header' => "Content-type: application/json\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/status', 'r', false, $context);
print_r(stream_get_contents($fp));
This will fail with:
{
"error": {
"code": 405,
"status": "Method Not Available.",
"description": "You tried to access a resource with an invalid method."

There Is Only One Format
Both requests and responses are in the form of JSON, so make sure to have content-type: application/json
as well as accept: application/json
headers where environment demands.
JSON in and JSON out, as simple as that.
That includes errors as well.
There Is Only One Currency
Each API call response will only ever be in a single currency - the one you specified in your HTTPS request.
It can be any fiat currency or active cryptocurrency.
By default, it will be USD
.
There Is Only One Version
There is only one publicly available version of the API.
Watch this repository! It'll always update before the actual API updates.
There Is Only One Limit
curl -X POST 'https://api.livecoinwatch.com/credits' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>'
await fetch(new Request('https://api.livecoinwatch.com/credits'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
})
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/credits', 'r', false, $context);
print_r(stream_get_contents($fp));
Don't forget to replace
<YOUR_API_KEY>
with one you've got. Return response should be:
{
"dailyCreditsRemaining": 4321,
"dailyCreditsLimit": 100000
}
Let's call it credits, and you can read about them in detail, but summarized - they map directly to your requests 1-to-1.
You can always easily check your credits status at /credits
end-point, as well as on your Live Coin Watch profile page.
Resources
This describes API resource fetching via HTTPS calls.
/status
curl -X POST 'https://api.livecoinwatch.com/status' \
-H 'content-type: application/json'
await fetch(new Request('https://api.livecoinwatch.com/status'), {
method: 'POST',
headers: new Headers({ 'content-type': 'application/json' })
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/status', 'r', false, $context);
print_r(stream_get_contents($fp));
...and it returns nothing! Well, empty JSON object anyways.
With this, find out is everything fine with the API. It is also only end-point that doesn't require x-api-key
header.
Request
Accepts no request parameters.
Response
Ideally, responds with nothing which means everything is hopefully running fine. One of the errors objects otherwise.
/credits
curl -X POST 'https://api.livecoinwatch.com/credits' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>'
await fetch(new Request('https://api.livecoinwatch.com/credits'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
})
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/credits', 'r', false, $context);
print_r(stream_get_contents($fp));
Let's see how much credits we have and what's the limit:
{
"dailyCreditsRemaining": 4321,
"dailyCreditsLimit": 10000
}
Error response (one of):
{
"error": {
"code": 401,
"status": "Unauthorized",
"description": "Your API key is wrong."
}
}
Through this end-point, you can find out your API key related information.
Request
Accepts no request parameters.
Response
| key | type | description |
|---|---|---|
dailyCreditsRemaining |
number | remaining daily credits |
dailyCreditsLimit |
number | total daily starting credits |
/overview
Get current aggregated data for all coins.
curl -X POST 'https://api.livecoinwatch.com/overview' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD"}'
await fetch(new Request('https://api.livecoinwatch.com/overview'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({ currency: 'USD' })
})
$data = json_encode(array('currency' => 'USD'));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/overview', 'r', false, $context);
print_r(stream_get_contents($fp));
How's all of crypto doing at the moment:
{
"cap":<PHONE_NUMBER>486,
"volume":<PHONE_NUMBER>2,
"liquidity":<PHONE_NUMBER>,
"btcDominance": 0.5932948858748709
}
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
Response
| key | type | description |
|---|---|---|
cap |
number | market cap of all coins |
volume |
number | volume of all coins |
liquidity |
number | 2% liquidity of all coins |
btcDominance |
number | percentage of BTC cap in total market cap |
/overview/history
Get historical aggregated data of entire market.
curl -X POST 'https://api.livecoinwatch.com/overview/history' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD","start":1606232700000,"end":1606233000000}'
await fetch(new Request('https://api.livecoinwatch.com/overview/history'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'USD',
start:<PHONE_NUMBER>000,
end:<PHONE_NUMBER>000
})
})
$data = json_encode(array('currency' => 'USD', 'start' =><PHONE_NUMBER>000, 'end' =><PHONE_NUMBER>000));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/overview/history', 'r', false, $context);
print_r(stream_get_contents($fp));
How's all of crypto trending across time:
[
{
"date":<PHONE_NUMBER>000,
"cap":<PHONE_NUMBER>30,
"volume":<PHONE_NUMBER>4,
"liquidity":<PHONE_NUMBER>,
"btcDominance": 0.614520121091147
},
{
"date":<PHONE_NUMBER>000,
"cap":<PHONE_NUMBER>34,
"volume":<PHONE_NUMBER>1,
"liquidity":<PHONE_NUMBER>,
"btcDominance": 0.612858305207367
}
]
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
start |
number | UNIX timestamp in milliseconds of time interval start |
end |
number | UNIX timestamp in milliseconds of time interval end |
Response
| key | type | description |
|---|---|---|
date |
number | UNIX timestamp in milliseconds of datapoint |
cap |
number | market cap of all coins |
volume |
number | volume of all coins |
liquidity |
number | 2% liquidity of all coins |
btcDominance |
number | percentage of BTC cap in total market cap |
/coins/single
All information about a single coin at latest moment in time.
curl -X POST 'https://api.livecoinwatch.com/coins/single' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD","code":"ETH","meta":true}'
await fetch(new Request('https://api.livecoinwatch.com/coins/single'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'USD',
code: 'ETH',
meta: true
})
})
$data = json_encode(array('currency' => 'USD', 'code' => 'ETH', 'meta' => true));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/coins/single', 'r', false, $context);
print_r(stream_get_contents($fp));
Let's see all of current data on ETH, in USD currency:
{
"name": "Ethereum",
"symbol": "Ξ",
"color": "#282a2a",
"png32": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/32/eth.png",
"png64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/64/eth.png",
"webp32": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/32/eth.webp",
"webp64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/64/eth.webp",
"exchanges": 153,
"markets": 3717,
"pairs": 1773,
"allTimeHighUSD": 2036.3088032624153,
"circulatingSupply": 115250583,
"totalSupply": null,
"maxSupply": null,
"rate": 1786.6742250505124,
"volume":<PHONE_NUMBER>6,
"cap":<PHONE_NUMBER>68
}
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
code |
string | coin code |
meta |
boolean | to include full coin information or not |
Response
| key | type | description |
|---|---|---|
name |
string | coin's name |
symbol |
string | coin's symbol |
color |
string | hexadecimal color code (#282a2a ) |
png32 |
string | 32-pixel png image of coin icon |
png64 |
string | 64-pixel png image of coin icon |
webp32 |
string | 32-pixel webp image of coin icon |
webp64 |
string | 64-pixel webpg image of coin icon |
exchanges |
number | number of exchange coin is present at |
markets |
number | number of markets coin is present at |
pairs |
number | number of unique markets coin is present at |
allTimeHighUSD |
number | all-time high in USD |
circulatingSupply |
number | number of coins minted, but not locked |
totalSupply |
number | number of coins minted, including locked |
maxSupply |
number | maximum number of coins that can be minted |
rate |
number | price of coin in requested currency |
volume |
number | reported trading volume of the coin in last 24 hours in requested currency |
cap |
number | coin's market cap in requested currency |
totalCap |
number | coin's hypothetical total capitalization at the moment |
/coins/single/history
Historical values for coin.
curl -X POST 'https://api.livecoinwatch.com/coins/single/history' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD","code":"BTC","start":1617035100000,"end":1617035400000,"meta":true}'
await fetch(new Request('https://api.livecoinwatch.com/coins/single/history'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'USD',
code: 'BTC',
start:<PHONE_NUMBER>000,
end:<PHONE_NUMBER>000,
meta: true
})
})
$data = json_encode(array('currency' => 'USD', 'code' => 'BTC', 'start' =><PHONE_NUMBER>000, 'end' =><PHONE_NUMBER>000, 'meta' => true));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/coins/single/history', 'r', false, $context);
print_r(stream_get_contents($fp));
How is BTC trending over a period of time:
{
"code": "BTC",
"name": "Bitcoin",
"symbol": "₿",
"color": "#fa9e32",
"png32": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/32/btc.png",
"png64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/64/btc.png",
"webp32": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/32/btc.webp",
"webp64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/production/currencies/64/btc.webp",
"exchanges": 145,
"markets": 4180,
"pairs": 1524,
"allTimeHighUSD": 61518.797756895845,
"circulatingSupply": 18669593,
"totalSupply": null,
"maxSupply": 21000000,
"history": [
{
"date":<PHONE_NUMBER>000,
"rate": 57372.11890245088,
"volume":<PHONE_NUMBER>1,
"cap":<PHONE_NUMBER>924
},
{
"date":<PHONE_NUMBER>000,
"rate": 57521.9764455523,
"volume":<PHONE_NUMBER>6,
"cap":<PHONE_NUMBER>352
}
]
}
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
code |
string | coin code |
start |
number | UNIX timestamp in milliseconds of time interval start |
end |
number | UNIX timestamp in milliseconds of time interval end |
meta |
boolean | to include full coin information or not |
Response
| key | type | description |
|---|---|---|
code |
string | coin's own code |
name |
string | coin's name |
symbol |
string | coin's symbol |
color |
string | hexadecimal color code (#282a2a ) |
png32 |
string | 32-pixel png image of coin icon |
png64 |
string | 64-pixel png image of coin icon |
webp32 |
string | 32-pixel webp image of coin icon |
webp64 |
string | 64-pixel webpg image of coin icon |
exchanges |
number | number of exchange coin is present at |
markets |
number | number of markets coin is present at |
pairs |
number | number of unique markets coin is present at |
allTimeHighUSD |
number | all-time high in USD |
circulatingSupply |
number | number of coins minted, but not locked |
totalSupply |
number | number of coins minted, including locked |
maxSupply |
number | maximum number of coins that can be minted |
history |
array | list of date , rate , volume and cap |
/coins/list
Assorted information for a list of coins.
curl -X POST 'https://api.livecoinwatch.com/coins/list' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD","sort":"rank","order":"ascending","offset":0,"limit":2,"meta":false}'
await fetch(new Request('https://api.livecoinwatch.com/coins/list'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'USD',
sort: 'rank',
order: 'ascending',
offset: 0,
limit: 2,
meta: false
})
})
$data = json_encode(array('currency' => 'USD', 'sort' => 'rank', 'order' => 'ascending', 'offset' => 0, 'limit' => 2,'meta' => false));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/coins/list', 'r', false, $context);
print_r(stream_get_contents($fp));
Let's see top two coins by rank, just frequently-changing data, please:
[
{
"code": "BTC",
"rate": 59075.58195922644,
"volume":<PHONE_NUMBER>2,
"cap":<PHONE_NUMBER>307
},
{
"code": "ETH",
"rate": 1933.6392223621567,
"volume":<PHONE_NUMBER>4,
"cap":<PHONE_NUMBER>23
}
]
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
sort |
string | sorting parameter, rank , price , volume , code , name |
order |
string | sorting order, ascending or descending |
offset |
number | offset of the list, default 0 |
limit |
number | limit of the list, default 10 , maximum 100 |
meta |
boolean | to include full coin information or not |
Response
| key | type | description |
|---|---|---|
name |
string | coin's name |
symbol |
string | coin's symbol |
color |
string | hexadecimal color code (#282a2a ) |
png32 |
string | 32-pixel png image of coin icon |
png64 |
string | 64-pixel png image of coin icon |
webp32 |
string | 32-pixel webp image of coin icon |
webp64 |
string | 64-pixel webpg image of coin icon |
exchanges |
number | number of exchange coin is present at |
markets |
number | number of markets coin is present at |
pairs |
number | number of unique markets coin is present at |
allTimeHighUSD |
number | all-time high in USD |
circulatingSupply |
number | number of coins minted, but not locked |
totalSupply |
number | number of coins minted, including locked |
maxSupply |
number | maximum number of coins that can be minted |
code |
string | coin's code |
rate |
number | coin rate in the specified currency |
volume |
number | 24-hour volume of coin |
cap |
number | market cap of coin |
/fiats/all
List of all the fiats.
curl -X POST 'https://api.livecoinwatch.com/fiats/all' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>'
await fetch(new Request('https://api.livecoinwatch.com/fiats/all'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
})
})
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n"
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/fiats/all', 'r', false, $context);
print_r(stream_get_contents($fp));
Array of all the fiat currencies supported:
[
{
"code": "ALL",
"countries": [ "ALB" ],
"flag": "ALB",
"name": "Albanian Lek",
"symbol": "Lek"
},
{
"code": "HNL",
"countries": [ "HND" ],
"flag": "HND",
"name": "Honduran Lempira",
"symbol": "L"
},
...
]
Request
Accepts no request parameters.
Response
An array of following:
| key | type | description |
|---|---|---|
code |
string | fiat ISO code |
countries |
array | ISO country code list |
flag |
string | ISO country code of the flag |
name |
string | fiat name |
symbol |
string | fiat symbol |
/exchanges/single
Assorted exchange information.
curl -X POST 'https://api.livecoinwatch.com/exchanges/single' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"ETH","code":"gemini","meta":true}'
await fetch(new Request('https://api.livecoinwatch.com/exchanges/single'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'ETH',
code: 'gemini',
meta: true
})
})
$data = json_encode(array('currency' => 'ETH', 'code' => 'gemini', 'meta' => true));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/exchanges/single', 'r', false, $context);
print_r(stream_get_contents($fp));
Should get us all the information we have on Gemini exchange:
{
"name": "Gemini",
"png64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/64/gemini.png",
"png128": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/128/gemini.png",
"webp64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/64/gemini.webp",
"webp128": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/128/gemini.webp",
"centralized": true,
"usCompliant": true,
"code": "gemini",
"markets": 43,
"volume":<PHONE_NUMBER>4617922,
"bidTotal": 10968.751251210175,
"askTotal": 12183.016333351212,
"depth": 23151.76758456139,
"visitors": 31738,
"volumePerVisitor": 3.638350641066835
}
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
code |
string | exchange code |
meta |
boolean | to include full exchange information or not |
Response
| key | type | description |
|---|---|---|
name |
string | exchange name |
png64 |
string | 64-pixel png image of exchange icon |
png128 |
string | 128-pixel png image of exchange icon |
webp64 |
string | 64-pixel webp image of exchange icon |
webp128 |
string | 128-pixel webpg image of exchange icon |
centralized |
boolean | is the exchange centralized or decentralized |
usCompliant |
boolean | is the exchange compliant in the USA |
code |
string | exchange code |
markets |
number | count of currently active markets on the exchange |
volume |
number | 24-hour volume in specified currency |
bidTotal |
number | 2% orderbook value bids |
askTotal |
number | 2% orderbook value asks |
depth |
number | 2% orderbook total depth |
visitors |
number | number of daily visitors, estimate |
volumePerVisitor |
number | daily volume per daily visitor |
/exchanges/list
Assorted information on list of exchanges.
curl -X POST 'https://api.livecoinwatch.com/exchanges/list' \
-H 'x-api-key: <YOUR_API_KEY>' \
-d '{"currency":"USD","sort":"visitors","order":"descending","offset":0,"limit":1,"meta":true}'
await fetch(new Request('https://api.livecoinwatch.com/exchanges/list'), {
method: 'POST',
headers: new Headers({
'content-type': 'application/json',
'x-api-key': '<YOUR_API_KEY>'
}),
body: JSON.stringify({
currency: 'USD',
sort: 'visitors',
order: 'descending',
offset: 0,
limit: 1
meta: true
})
})
$data = json_encode(array('currency' => 'USD', 'sort' => 'visitors', 'order' => 'descending', 'offset' => 0, 'limit' => 1, 'meta' => true));
$context_options = array (
'http' => array (
'method' => 'POST',
'header' => "Content-type: application/json\r\n"
. "x-api-key: <YOUR_API_KEY>" . "\r\n",
'content' => $data
)
);
$context = stream_context_create($context_options);
$fp = fopen('https://api.livecoinwatch.com/exchanges/list', 'r', false, $context);
print_r(stream_get_contents($fp));
Top one exchange by number of visitors:
[
{
"name": "Binance",
"png64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/64/binance.png",
"png128": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/128/binance.png",
"webp64": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/64/binance.webp",
"webp128": "https://lcw.nyc3.cdn.digitaloceanspaces.com/development/exchanges/128/binance.webp",
"centralized": true,
"usCompliant": true,
"code": "binance",
"markets": 935,
"volume":<PHONE_NUMBER>8,
"bidTotal": 225078060.0687528,
"askTotal": 240112799.048314,
"depth": 465190859.1170668,
"visitors": 779440,
"volumePerVisitor": 35311.72690393103
}
]
Request
| key | type | description |
|---|---|---|
currency |
string | any valid coin or fiat code |
sort |
string | sorting parameter, volume , liquidity , code , name |
order |
string | sorting order, ascending or descending |
offset |
number | offset of the list, default 0 |
limit |
number | limit of the list, default 50 , maximum 100 |
meta |
boolean | to include full exchange information or not |
Response
Returns array of objects containing:
| key | type | description |
|---|---|---|
name |
string | exchange name |
png64 |
string | 64-pixel png image of exchange icon |
png128 |
string | 128-pixel png image of exchange icon |
webp64 |
string | 64-pixel webp image of exchange icon |
webp128 |
string | 128-pixel webpg image of exchange icon |
centralized |
boolean | is the exchange centralized or decentralized |
usCompliant |
boolean | is the exchange compliant in the USA |
code |
string | exchange code |
markets |
number | count of currently active markets on the exchange |
volume |
number | 24-hour volume in specified currency |
bidTotal |
number | 2% orderbook value bids |
askTotal |
number | 2% orderbook value asks |
depth |
number | 2% orderbook total depth |
visitors |
number | number of daily visitors, estimate |
volumePerVisitor |
number | daily volume per daily visitor |
Errors
Example end-point with JSON error information:
{
"error": {
"code": 418,
"status": "I'm a teapot.",
"description": "Yes, a teapot"
}
}
Errors follow There Is Only One Format as well.
| code | status | description |
|---|---|---|
| 400 | Bad Request | Your request is invalid. |
| 401 | Unauthorized | Your API key is wrong. |
| 403 | Forbidden | The resource requested is hidden for administrators only. |
| 404 | Not Found | The specified resource could not be found. |
| 405 | Method Not Allowed | You tried to access a resource with an invalid method. |
| 406 | Not Acceptable | You requested a format that isn't json. |
| 410 | Gone | The resource requested has been removed from our servers. |
| 418 | I'm a teapot. | Yes, a teapot. |
| 429 | Too Many Requests | You're requesting too many resources! Slow down! |
| 500 | Internal Server Error | We had a problem with our server. Try again later. |
| 503 | Service Unavailable | We're temporarily offline for maintenance. Please try again later. |
Limits
There's really not a lot of them.
Here's a complete list:
- you need to have Live Coin Watch account
- each request is mapped to a single credit
- daily credit allowance is 10,000
- credits are renewed every UTC midnight
- you can check your API status at your Profile page
- if you're using API in a public-facing manner, we require attribution that should consist of a link to Live Coin Watch in a legible font
There you go, that's all.
Have fun, be safe!


]]>
Simply wrap the ]]>
elements you need in a ]]>
element.
The ]]>
component has 2 properties:
Method to be executed when [onStepChange] event is emitted. Emits an [IStepChangeEvent] implemented object.
Defines if there can be one or multiple [TdStepComponent] elements active at the same time.


Hydraulic Viper is a virtual phenotyping pipeline for root hydraulic traits.
It is a collection of models working at different scales and able to simulate root water uptake
CPantBox allow the creation of root system architecture, GRANAR - MECHA estimate the radial and axial hydraulic conductivity of all root types with different root anatomy and hydrophobic barriers.
MARSHAL solve the root system hydraulic architecture and link the rhizosphere hydraulic conductivity with the root system.
Hydrus-1D resolve water movement in the soil domain following Couvreur macro-hydraulic properties for root water upteke.
The atmospheric boundary condition are set following the Penman-Monteith equations coupled with weather data from NASA POWER
Hydraulic Viper is a multi models pipeline which run in R and on linux
The installation procedure is not yet available...
The first step before running GRANAR is to install a working version for R! Installation of R are available here: https://cran.r-project.org/
check
check
check
Hydraulic Viper uses
params
: General parameters for Hydraulic Viper output are stored...
# R script example library(tidyverse)
Hydraulic Viper was developed at the Université catholique de Louvain, in the Earth and Life Insititute, in the lab of Guillaume Lobet. The primary developpers of the model are Adrien Heymans and Valentin Couvreur.
Hydraulic viper is in prep:
great article


Current step is: {{ lc.currentStep }}
Selecting a group: {{ lc.selectGroup }}
Group name: {{ lc.createdGroupName }}
group is {{lc.groupName}}
Group name
Max number of members?


Common functionality to the core tasks tasks is:
The url parameter specifies the URL to access. The optional destFile parameter specifies a destination to which the retrieved page will be written. The optional destProperty parameter specifies a name of a property to save the content to, instead of a property. If neither destFile nor destProperty specified, the contents of the specified URL are discarded (this is useful when accessing the URL for the purpose of causing some action on the remote server).
When the verbose option is enabled, the task displays a '.' for every 64 KB retrieved. If the blocksize parameter is adjusted then files are uploaded or downloaded in a different size block from this, and progress markers appear appropriately.
The usetimestamp option enables you to control downloads so that the remote file is only fetched if newer than the local copy. If there is no local copy, the download always takes place. When a file is downloaded, the timestamp of the downloaded file is set to the remote timestamp. NB: This timestamp facility only works on downloads using the HTTP protocol.The authtype, username, and password options enable support for password protected pages. Currently only 'Basic' authentication is used, which is notoriously insecure except over an encrypted https channel.
| Attribute | Description | Required |
| authtype | the HTTP authentication protocol to use, none or basic. | No |
| blocksize | size (in kilobytes) of the data block used for upload and
download. Default: 64. Keep this to a multiple of the hard disk sector size for file IO performance. |
No |
| destfile | the file where to store the retrieved file. | No |
| destproperty | the name of a property to fill with the returned content. Ignored if destFile is set | No |
| failonerror | stop the build if the request failed. default: true | No |
| password | the password for authentication. | No |
| status | the name of a property to set to "true" if the
request succeeds. Set failonerror to false for this to be of use. |
No |
| url | the URL from which to retrieve a file. | Yes |
| usecaches | boolean to enable 'caching' of content during the fetch process. default:false | No |
| useresponsecode | boolean to enable success/failure to be determined by result of the received response code. HTTP only. default=true. | |
| username | the user name for authentication. | No |
| usetimestamp | boolean flag to conditionally download a file based on the timestamp of the local copy. HTTP only | No |
| verbose | boolean flag to control progress information display. | No |
The status attribute names a property which will be set to "true" if the request was deemed successful. For any non-http protocol, success is defined as the request completing. For http and https, success is defined as the request completing, and the response code from the serving being one of the 'success' values -any number between 200 and 299 inclusive. The usual HTTP_OK (200) is therefore a success, as is HTTP_ACCEPTED (202). But failures such as BAD_REQUEST (400) and the ubiquitous HTTP_NOT_FOUND (404) are most definately errors. So an attempt to access a missing url may result 'failure',even though some content was download (such as, perhaps, the 'file not found' text). If this is not what you desire, then set useresponsecode="false" for the system to interpret any data back as a success.
param
Specifies an HTTP request parameter to send as part of the request. For get and head request methods the parameters are encoded as part of the URL. For post request methods, the parameters are sent as the POST request data.
| Attribute | Description | Required |
| name | the name of the request property to set. | Yes |
| value | the value of the request property. You may alternatively specify the value as text between the beginning and ending param tags. | Yes |
header
Specifies an arbitrary HTTP request header that will be sent with the request.
| Attribute | Description | Required |
| name | the name of the HTTP request header | Yes |
| value | the value of the HTTP request header. You may alternatively specify the value as text between the beginning and ending header tags. | Yes |
Bug ID #4160499 covers another issue, to wit: some versions of Java throw exceptions when an error code is greater than 400 and the destFile file isn't one of a few simple file types, but Java 1.2 and 1.3 do not. So there is no way to get the error text when a jsp page throws some exception.
Also, on Java1.2 and 1.3,if you recieve a short response with less content than the content-length header promises, the library seems to silently reduce the content length header to match, which seems the wrong action.
Accesses a URL to retrieve a file or to cause some action on the server.
All the attributes of httptask may be used. Note that a quirk of the implementation of the http client in java makes it impossible to reliably fetch the response details from any unsuccessful request against a URL which doesn't end in '.htm,.html or .txt'. This means that if the task is used to compile JSP pages by issuing request against them, the text details of any errors will not be picked up.
<httpget url="http://jakarta.apache.org/" destFile="help/index.html"/>
Fetches the index page of http://jakarta.apache.org/, and stores it in the
file help/index.html
.
<httpget src="http://jakarta.apache.org/builds/tomcat/nightly/ant.zip" destFile="optional.jar" verbose="true" usetimestamp="true" > <header name="Cookie" value="someid=43ff2b"/> </httpget>
Retrieves the nightly ant build from the tomcat distribution, if the local copy is missing or out of date. Uses the verbose option for progress information. A cookie is supplied for the server's benefit.
<httpget url="https://www.pizzaservices.com/prices.jsp" destFile="pizza-prices.xml"> <param name="zipcode">57340</param> <param name="pizza">pepperoni</param> </httpget>
Builds a URL by adding parameters ("?zipcode=57340&pizza=pepperoni") to the base URL and then fetches the contents (fictional example)
The http HEAD request is similar to the normal GET request , except it, by definition, returns no content, just a success code and http headers. Accordingly, the destination properties of the base class -destFile and -, destinationpropertyname) are not supported -any attempt to use them will result in a build failure. Note also that the http and https protocols are the only protocols supported.
HttpHead is useful for triggering server side actions, but note that many servers interpret a HEAD very differently from a GET. An HttpGet request with the return data discarded is often a more reliable approach.
Where head can be useful is in testing for the availability and reachability of servers, such as in the following test for apache being reachable, which sets a variable on success:-
<httphead url="http://www.apache.org/" failonerror="false" successproperty="reachable.apache" />
Note that sometimes a missing file on a mis-configured server still generates a successful '200' response to a GET request -and returns a 'missing' file page, but a HEAD request will reliably pick up the 'missing file' error.
This implements the POST request. Supplied parameter data is turned into form data and sent as the body of the request, rather than appended to the URL. If a file to upload is specified instead, using uploadFile, the parameter values are ignored. Instead the content type of the file is sent in the header -based on the contentType attribute or what the java runtime thinks the content type is based on the file extension. The file is uploaded.
Like HttpGet, this command can return a content which can downloaded to a file, to a property, or just ignored.
This task adds two new attributes to the base set.
| Attribute | Description | Required |
| uploadFile | a file to upload. when specified, all parameters are ignored. |
no
|
| contentType | the type of the content (text/html, text/xml, application/binary, etc). Only of relevance when a file is being uploaded, and still optional in that case. |
no
|
<httppost url="http://www.example.com/servlet/docserver" authtype="basic" username="joe" password="silly"> <param name="action" value="getdoc"/> <param name="ISBN">038550120X</param> <param name="pages">19-20</param> <header name="Accept-Language" value="en-us"/> </httppost>
Accesses a server at www.foo.com, passing a request to some servlet asking it to retrieve several pages from a stored book. An HTTP header specifying acceptable languages for the returned contents is also sent. Basic authentication is used with a user name of "joe" and a password of "silly".
<httppost url="https://www.pizzaservices.com" uploadFile="pizza-order.xml" contentType="text/xml">
Sends a pre-prepared order for a pizza to a pizza vendor accepting orders using xml-rpc requests. (NB: fictional example)


Background
Margins, borders, and padding are pretty sweet. But in order to understand the concepts of those and how they operate with HTML and CSS, we first have to lay some groundwork:
- All HTML elements can be thought of as boxes.
- Take a look at #1 again... think about it. Everything. This list I'm writing in right now is a rectangular box. The header above it is a box and the footer at the bottom is a box. Heck, this entire web page is one big box!
- Now that we know a web page is nothing but boxes, we have to arrange them so that they look nice and pretty for users. We don't want people getting sick when they're looking at our pages.
Now that we know the basics, let's refer to The CSS Box Model. Without going rogue technical on you, let's just say that the box model is a massive box that hugs the little HTML boxes and consists of margins, borders, and padding. The images below give a great visual representation (thanks W3 Schools and css-tricks.com!) Now, what exactly are these three?
Margins
Let's start from the back (or largest box if you prefer to think of it that way) and work our way forward. Margin is the biggest box and it is totally transparent. We can't see it. It has no background color. But it's there. Trust me, it's there. And it's really important. It pretty much determines how much space there is between HTML elements. Wow, yeah... this is really important!
But what about borders?
Borders
Don't worry, border, we wouldn't forget about you. Since you can't see the margin, the border is the first real box that we see. It takes its place around padding and content, and is typically the same color as them. That being said, the color of the border can be changed so that it more obviously defines a space.
Finally, what is padding all about?
Padding
So what is this funny padding business all about? Padding surrounds the content and is the space between an element's border and the content within it. Padding is nice because it helps to make things easier to read, like hopefully this!


Home > JavaScript Questions > What do you mean by Event Bubbling and Event Capturing?
There are two ways for accomplishing event propagation and the order in which an event is received in the HTML DOM API
These are Event Bubbling and Event Capturing. In the former, the event is directed towards its intended target, whereas the event goes down to the element in the latter.


The Raviz Kadavu offers a plethora of dining options to suit every palate.Hosting a quintessential Kerala restaurant, an open grill specialty dine to a sports-themed bar Zirkon. The Raviz Kadavu is a gourmand’s delight in the gastronomical capital of the state.The property is a head-to not just for the guests of the resort, but also locals of the city and surrounding regions who appreciate unique dining experiences.
-->Kozhikode Beach is also known as the Calicut Beach and is situated on the Malabar Coast.It is the most visited beach in Calicut as it is the central beach of the place.The beach road was named as 'Gandhi Road' after Mahatma Gandhi paid a visit to Calicut in 1934.The place has always been prominent for hosting public meetings. It has a long drive from Beypore in the south to Kappad in the north.The beach is ideal for witnessing the orange sunsets in Calicut. Also, the market near is a large shopping spot and attracts a lot of tourists.
Lying in the Western Ghats of Kozhikode district in Kerala, Thusharagiri Fall cascades down as three waterfalls.Located in a small tribal village, the name of the falls means snow covered mountains'.Trekkers and rock climbers will find trekking trails towards Lakkidi Ghat passing through thick foliage & lush, green surroundings offering its visitors a sheer delight.
Said to be built on the remains of a shipwreck, the Thikkoti Lighthouse is one of the major attractions of Kozhikode.Located on a rocky shoreline, the place is best known for the scenic views it offers as well as several species of nomadic birds.


The input to this algorithm is an extended affine permutation of size n. An extended affine permutation of size n is a map f from the integers to the integers, with two requirements. First, the numbers f(1) through f(n) must represent the equivalence classes , mod n, of the numbers 1 through n. Secondly, there is a kind of periodicity, namely that f(i + n) = f(i) + n. So then, the values of f are specified by its output on any consequitive n integers. Usually, the map f is described by listing the values f(1) through f(n), in brackets. This is called the 1,...,n window of the permutation. An affine permutation (as opposed to an extended affine permutation) has the additional property that the sum of the numbers f(1) through f(n) is the same as the sum of the numbers 1 through n. For example, with n = 4, using the 1,...,4 window, [0, 2, 7, 1] is an affine permutation, as is [-1, 5, 14, -8]. The permutation [3, 1, -2, 4] is an extended affine permutation but not an affine permutatio.
This page can be used in two ways. First, you can have the page generate a random affine permutation. To do that, enter the size of the desired permutation in the first textbox. You can choose any positive whole number up through 20 for n. The degree of spread in randomness is controlled by the textbox to its right. For that, you can choose any whole number up through 5.  Once you have entered this information, click the Run button directly to the right. Alternatively, press Enter while in one of these two textboxes. This will display a random affine permutation and the output of the AMBC algorithm when applied to that affine permutation. The most recent output is added at the top.
Instead, you can enter an extended affine permutation in the textbox labeled "Permutation". Enter the 1,...,n window for the permutation. The numbers should be separated by commas, with or without spaces between the numbers, with or without square braces. That is, you can enter 0,2,4 or 0, 2, 4 or [0,2,4] or [0, 2, 4]. Then, click the Run button to the right of the Permutation textbox, or press Enter while in the textbox. The most recent output is added at the top.
You can use the Clear Top Item and Clear All buttons to remove output from the page.
One use case for this page is for research. You can use the page to run multiple permutations, and then save the results to a PDF. The Comment textbox allows you to enter additional information, for example, a reduced expression for the permutation. This information will be displayed, to the right of the permutation, in the output. Pressing Enter when in the Comment textbox will run the permutation which is entered in the Permutation textbox.
When you're ready to print your results to a PDF, you can, if you like, use the Reverse Output button to reverse the order in which the results are displayed, so that the first results are on top. Also, you can hide the controls. To do this, click the little black box to the right of the Information button. Then press Ctrl-P (or right-click and select Print) to print the page to a PDF. After that, you can click the black box again to reveal the controls.
As an alternative to printing to a PDF, you can also save your output by saving the page as Web Page, complete.
This is a port to JavaScript of Mike Chmutov's Java code for the Affine Matrix Ball Construction algorithm. The original code can be found here: https://github.com/mchmutov/AMBC. The drawing code and the code to run the webpages are borrowed from the pages on my site: https://devragj.github.io/. Two papers describing the Affine Matrix Ball Construction can be found at these links: Matrix-Ball Construction of affine Robinson-Schensted correspondence, Monodromy in Kazhdan-Lusztig cells in affine type A. The second paper has a more condensed description of the algorithm.
Please contact me at devra.johnson at verizon.net.


Robotic Bank for Dummies!
Future features:
- Submission forms check for account name, money format, and
date/interval format validity
- Official support for bignum bank accounts
- Bignum year support and computationally efficient financial
predictions
- Source and destination banks for inter-bank transfers
- Update autopay rule
- Loan rule tracking!
- Close account (balance must be zero!)
- Auto group buy/sell rules
- Group buy and group sell at the same time
- View current autopay rules
- Graphing of account balance over time
- Easy purpose search/filter
- Add/remove account from auto group buy/sell rule: great for
updating employees on payroll, O'lowie service account-holders,
etc.


Our Macro Calculator
It is hard to track the nutritional value of everything you eat in a day, luckily we have you covered. Our macro calculator can help organize your daily macronutrient intake, whether your goal is to cut back, eat more, or just eat healthier WE CAN HELP!


#include <RcppArmadillo.h>
Go to the source code of this file.
Functions | |
| arma::mat | penaltyMat (const unsigned int &, const unsigned int &) |
| Calculating penalty matrix. More... | |
| unsigned int | findSpan (const double &, const arma::vec &) |
| Binary search to find index of given point within knots. More... | |
| arma::vec | createKnots (const arma::vec &, const unsigned int &, const unsigned int &) |
| Create knots for a specific number, degree and values. More... | |
| arma::mat | createSplineBasis (const arma::vec &, const unsigned int &, const arma::vec &) |
| Transformation from a vector of input points to matrix of basis. More... | |
| arma::sp_mat | createSparseSplineBasis (const arma::vec &, const unsigned int &, const arma::vec &) |
| Transformation from a vector of input points to sparse matrix of basis. More... | |
| arma::vec createKnots | ( | const arma::vec & | values, |
| const unsigned int & | n_knots, | ||
| const unsigned int & | degree | ||
| ) |
Create knots for a specific number, degree and values.
This functions takes a vector of points and creates knots used for the splines depending on the number of knots and degree. This function just handles equidistant knots.
| values | arma::vec Points to create the basis matrix. |
| n_knots | unsigned int Number of innter knots. |
| degree | unsigned int polynomial degree of splines. |
arma::vec
of knots. | arma::sp_mat createSparseSplineBasis | ( | const arma::vec & | values, |
| const unsigned int & | degree, | ||
| const arma::vec & | knots | ||
| ) |
Transformation from a vector of input points to sparse matrix of basis.
This functions takes a vector of points and create a sparse matrix of basis functions. Each row contains the basis of the corresponding value in values
.
Instead of calculating each row through a helper function we directly calculate deboors algorithm here. This is due to the procedure how sparse matrices should be allocated and constructed.
| param | values arma::vec Points to create the basis matrix. |
| param | n_knots unsigned int Number of innter knots. |
| param | degree unsigned int polynomial degree of splines. |
arma::sp_mat
sparse matrix of base functions. | arma::mat createSplineBasis | ( | const arma::vec & | values, |
| const unsigned int & | degree, | ||
| const arma::vec & | knots | ||
| ) |
Transformation from a vector of input points to matrix of basis.
This functions takes a vector of points and create a matrix of basis functions. Each row contains the basis of the corresponding value in values
.
| values | arma::vec Points to create the basis matrix. |
| n_knots | unsigned int Number of innter knots. |
| degree | unsigned int polynomial degree of splines. |
sp_mat
sparse matrix of base functions. | unsigned int findSpan | ( | const double & | x, |
| const arma::vec & | knots | ||
| ) |
Binary search to find index of given point within knots.
This small functions search for the position of x
within the knots
and returns the smalles index for which x >= knots[i].
Note that this function returns the C++
index which starts with 0
and ends with n-1
.
| x | double Point to search for position in knots. |
| knots | arma::vec Vector of knots. It's the users responsibility to pass a SORTED vector. |
unsigned int
of position of x
in knots
. | arma::mat penaltyMat | ( | const unsigned int & | nparams, |
| const unsigned int & | differences | ||
| ) |
Calculating penalty matrix.
This function calculates the penalty matrix for a given number of parameters (nparams
) and a given number of differences (differences
).
| nparams | unsigned int Number of params which should be penalized. This also pretend the number of rows and columns. |
| differences | unsigned int Number of penalized differences. |
arma::sp_mat
Sparse penalty matrix used for p splines.


QRCode
Decode
CRC
Fetch URL
Decoded QR
(c) Sean Wykes 2020
https://nascent.com.br
https://github.com/NascentSecureTech/pix-qrcode-utils


|
TARget
1
(TARget) - This A RaytracinG projEcT
|
A general class for N-dimensional points (vectors). More...
#include <cyPoint.h>
Public Member Functions | |
Constructors | |
| Point () | |
| Point (const Point &p) | |
| Point (const TYPE *p) | |
| Point (TYPE v) | |
| template<typename T > | |
| Point (const Point< T, N > &p) | |
| template<int M> | |
| Point (const Point< TYPE, M > &p) | |
| template<typename T , int M> | |
| Point (const Point< T, M > &p) | |
| Point (const Point2< TYPE > &p) | |
| Point (const Point3< TYPE > &p) | |
| Point (const Point4< TYPE > &p) | |
| template<typename T > | |
| Point (const Point2< T > &p) | |
| template<typename T > | |
| Point (const Point3< T > &p) | |
| template<typename T > | |
| Point (const Point4< T > &p) | |
| template<typename P > | |
| Point (const P &p) | |
Set & Get value methods | |
| void | Zero () |
| Sets the coordinates as zero. More... | |
| void | Get (TYPE *p) const |
| Puts the coordinate values into the array. More... | |
| void | Set (const TYPE *p) |
| Sets the coordinates using the values in the given array. More... | |
| void | Set (TYPE v) |
| Sets all coordinates using the given value. More... | |
| template<int M> | |
| void | CopyData (TYPE *p) |
| template<typename T , int M> | |
| void | ConvertData (T *p) |
General methods | |
| TYPE | LengthSquared () const |
| Returns the square of the length. Effectively, this is the dot product of the vector with itself. More... | |
| TYPE | Length () const |
| Returns the length of the vector. More... | |
| void | Normalize () |
| Normalizes the vector, such that its length becomes 1. More... | |
| Point | GetNormalized () const |
| Returns a normalized copy of the vector. More... | |
| TYPE | Sum () const |
| Returns the sum of its components. More... | |
| bool | IsZero () const |
| Returns true if all components are exactly zero. More... | |
| TYPE | Min () const |
| TYPE | Max () const |
| int | MinID () const |
| int | MaxID () const |
Limit methods | |
| void | Clamp (TYPE minValue, TYPE maxValue) |
| void | ClampMin (TYPE v) |
| void | ClampMax (TYPE v) |
| void | Abs () |
| Converts all negative components to positive values. More... | |
Unary operators | |
| Point | operator - () const |
Binary operators | |
| Point | operator+ (const Point &p) const |
| Point | operator - (const Point &p) const |
| Point | operator * (const Point &p) const |
| Point | operator/ (const Point &p) const |
| Point | operator+ (const TYPE v) const |
| Point | operator - (const TYPE v) const |
| Point | operator * (const TYPE v) const |
| Point | operator/ (const TYPE v) const |
Assignment operators | |
| const Point & | operator= (const Point &p) |
| const Point & | operator+= (const Point &p) |
| const Point & | operator -= (const Point &p) |
| const Point & | operator *= (const Point &p) |
| const Point & | operator/= (const Point &p) |
| const Point & | operator+= (const TYPE v) |
| const Point & | operator -= (const TYPE v) |
| const Point & | operator *= (const TYPE v) |
| const Point & | operator/= (const TYPE v) |
Test operators | |
| bool | operator== (const Point &p) const |
| bool | operator != (const Point &p) const |
Access operators | |
| TYPE & | operator [] (int i) |
| TYPE | operator [] (int i) const |
Dot product | |
| TYPE | Dot (const Point &p) const |
| Dot product. More... | |
| TYPE | operator % (const Point &p) const |
| Dot product operator. More... | |
Public Attributes | |
Components of the point/vector | |
| TYPE | data [N] |
Friends | |
| Point | operator+ (TYPE v, const Point &p) |
| Addition with a constant. More... | |
| Point | operator - (TYPE v, const Point &p) |
| Subtraction from a constant. More... | |
| Point | operator * (TYPE v, const Point &p) |
| Multiplication with a constant. More... | |
A general class for N-dimensional points (vectors).
|
inlineexplicit |
|
inlineexplicit |
|
inlineexplicit |
|
explicit |
|
explicit |
|
explicit |
|
inlineexplicit |
|
inline |
Converts all negative components to positive values.
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
Dot product.
|
inline |
Puts the coordinate values into the array.
Returns a normalized copy of the vector.
|
inline |
Returns true if all components are exactly zero.
|
inline |
Returns the length of the vector.
|
inline |
Returns the square of the length. Effectively, this is the dot product of the vector with itself.
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
Normalizes the vector, such that its length becomes 1.
|
inline |
|
inline |
Dot product operator.
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
Sets the coordinates using the values in the given array.
|
inline |
Sets all coordinates using the given value.
|
inline |
Returns the sum of its components.
|
inline |
Sets the coordinates as zero.
Multiplication with a constant.
Subtraction from a constant.
Addition with a constant.
| TYPE cy::Point< TYPE, N >::data[N] |


CSC115 Intro
Some preliminary background on computer science and programming.
Computer Science
Computer science is about solving problems by automating processes via algorithms/programs.
Algorithm
An algorithm is a sequence of instructions for how to solve a problem.
Program
-
A computer program is a sequence of instructions written in a
computer programming language.
-
It can be executed by a computer.
-
To execute a program/algorithm means to carry out the instructions.
algorithm vs program
- In what way an algorithm is (or is not) different from a program is
partly a matter of perspective.
- An algorithm may be expressed in natural language, whereas a program
is by definition written in a computer programming language. Does the natural language
description of an algorithm constitute the algorithm itself?
Some people would say yes. I prefer to say not necessarily.
- A general expecation for an algorithm is that its execution eventually
comes to an end -- it is supposed to solve a problem, after all.
Some programs, on the other hand, run forever (until the computer is
powered off, anyway).
Machine Language
-
A machine language is the language that a given machine is designed to understand natively.
-
Machine language programs can be executed on a machine directly.
-
Machine language is prohibitively tedious for humans to understand and use, generally.
High-Level Language
-
A high-level language is a programming language that is designed
for humans to understand and use.
-
Programs written in high-level languages must be processed somehow into machine
language before they can be executed on a machine.
-
Programs written in high-level languages are also called source code.
Machine languages vs “low-level languages”
Our text equates machine language, assembly language, and low-level language at one point.
Assembly language is actually not machine language and programs written in assembly language
must be processed into machine language before they can be executed (which our text also does say).
Interpreters & Compilers
The primary ways for processing high-level languages into machine languages
are with interpreters and compilers.
Interpreter
An interpreter processes (translates) a high-level language program one line at a time.
The program thus executes immediately as it is being interpreted.
As a consequence, everytime it is desired to execute the program, the whole thing
must be processed again from the beginning.
Compiler
A compiler translates a high-level language program in its entirety into a
corresponding machine language executable program.
The executable can then be executed on the machine at a later time (and
even multiple times without having to re-compile it).
Python
-
Python is an interpreted language.
-
Actually, that's an oversimplification (perhaps an outright lie),
but a useful one for our purposes.
-
We will think of Python as being interpreted basically because it feels
like we are executing the source code directly rather than giving the source
code file to a tool (compiler) that produces a new (executable) file which we
must then run separately.


HEMORRODIL- phenylephrine hydrochloride and cocoa butter suppository
ZURICH MEDICAL LABS, LLC
Disclaimer: Most OTC drugs are not reviewed and approved by FDA, however they may be marketed if they comply with applicable regulations and policies. FDA has not evaluated whether this product complies.
| Active Ingredients |
Purpose |
| Phenylephrine Hydrochloride 0.25% |
Vasoconstrictor |
| Cocoa Butter 88.44% |
Protectant |
Uses
- Temporarily shrinks hemorrhoidal tissues
- Provides temporary relief from the itching, burning and discomfort associated with hemorrhoids
- Aids in protecting irritated anorectal areas
Warning
For rectal use only
Ask a doctor or pharmacist before use if you are presently taking a prescription drug for high blood pressure or depression.
Ask a doctor before use if you have
- heart disease
- high blood pressure
- thyroid disease
- diabetes
- difficulty in urination due to enlargement of the prostate gland
When using this product
- do not exceed recommended daily dose unless directed by a doctor
- in case of bleeding or if condition worsens or does not improve within 7 days, consult a doctor promptly.
If pregnant or breast-feeding, ask a health professional before use
Keep out of reach of children, if swallowed, get medical help or contact a Poison Control Center right away.
Directions
Adults
- detach one suppository from the strip. Remove wrapper before inserting into rectum
- gently insert suppository into rectum up to 4 times daily, especially at night, in the morning or after each bowel movement.
Children under 12 years of age, consult a doctor
Other information
Store at temperature 59° – 86°F
Inactive ingredients
methylparaben, propylparaben, starch
PRINCIPAL DISPLAY PANEL - 12 Suppository Blister Pack Carton
HEMORRODIL®
Soothing &
Refreshing
12 SUPPOSITORIES


{% extends 'campaigns_base.html' %} {% block title %}{{ campaign.game|default:'All' }} campaigns{% endblock %} {% block main %}
| Name | Game | Moderator | # Players | Status |
|---|---|---|---|---|
| {{ campaign.name }} ( {{ campaign.game.name_short }} ) | {{ campaign.game }} | {{ campaign.moderator }} | {{ campaign.participants.count|default:0 }} | {{ campaign.get_status_display }} |
| No campaigns found |


You are viewing an historical archive of past issues. Please
report new issues to the appropriate project issue tracker on
GitHub.
Comments
-
Greg Hurrell
Status changed:
- From: New
- To: Open
-
Greg Hurrell
See also:
-
Greg Hurrell
First batch of breakage to fix; this on firing up
script/server
and trying to access a page:DEPRECATION WARNING: protect_from_forgery only takes :only and :except options now. :digest and :secret have no effect. (called from app/controllers/application_controller.rb:5) DEPRECATION WARNING: Disabling sessions for a single controller has been deprecated. Sessions are now lazy loaded. So if you don't access them, consider them off. You can still modify the session cookie options with request.session_options.. (called from app/controllers/application_controller.rb:9) Processing ApplicationController#index (for <IP_ADDRESS> at 2009-02-04 01:22:20) [GET] Parameters: {"protocol"=>"https", "action"=>"index", "controller"=>"posts"} NameError (uninitialized constant ActionController::Caching::Sweeper): app/sweepers/post_sweeper.rb:1 app/controllers/posts_controller.rb:5 Rendered rescues/_trace (121.1ms) Rendered rescues/_request_and_response (42.2ms) Rendering rescues/layout (internal_server_error)
-
Greg Hurrell
Funnily enough all specs still pass.
1015 examples, 0 failures, 23 pending
-
Greg Hurrell
Ok, fixed the deprecation warnings, and worked around the NameError exceptions. Not really sure why those are being thrown; have posted to the Rails group to see if anyone can shed any light on the issue. See: http://groups.google.com/group/rubyonrails-talk/t/323ff7ec2d95ee32.
-
Greg Hurrell
Status changed:
- From: Open
- To: Closed
Add a comment
Comments are now closed for this issue.


Provides general linear model facilities (single y-variable, multiple x-variables with arbitrary mixture of continuous and categorical and arbitrary interactions) for cross-species data. The method is, however, based on the nowadays rather uncommon situation in which uncertainty about a phylogeny is well represented by adopting a single polytomous tree. The theory is in A. Grafen (1989, Proc. R. Soc. B 326, 119-157) and aims to cope with both recognised phylogeny (closely related species tend to be similar) and unrecognised phylogeny (a polytomy usually indicates ignorance about the true sequence of binary splits).
| Version: | 1.0.2 |
| Published: | 2018-04-12 |
| Author: | Alan Grafen |
| Maintainer: | Alan Grafen <alan.grafen at sjc.ox.ac.uk> |
| License: | GPL-2 | GPL-3 |
| NeedsCompilation: | no |
| In views: | Phylogenetics |
| CRAN checks: | phyreg results |
| Reference manual: | phyreg.pdf |
| Package source: | phyreg_1.0.2.tar.gz |
| Windows binaries: | r-devel: phyreg_1.0.2.zip, r-release: phyreg_1.0.2.zip, r-oldrel: phyreg_1.0.2.zip |
| OS X binaries: | r-release: phyreg_1.0.2.tgz, r-oldrel: phyreg_1.0.2.tgz |
| Old sources: | phyreg archive |
Please use the canonical form https://CRAN.R-project.org/package=phyreg to link to this page.


fictionwriting.tech is a website that generates the beginning of a story based on a few words from user input. It uses Open AI’s GPT-2 model to build on the user input, and generates a short scene. We trained the model on stories from reddit’s /r/writingprompts using the praw library to scrape them. This project both demonstrates the voice and creativity of AI, which we hope will educate and inspire people.


TripWithUs!
Home
About Us
Sign Up
Login
Add Events
Event ID
Event Name
Event Location
Zipcode
Event Date
Event Description
Add Events
Event ID
Event Name
Event Location
Zipcode
Event Date
Event Description


Golang Concurrency Tricks - Repository: https://github.com/udhos/golang-concurrency-tricks
miniapi - Repository: https://github.com/udhos/miniapi
gateboard - Repository: https://github.com/udhos/gateboard
prime - Repository: https://github.com/udhos/prime
sqs-to-sns - Repository: https://github.com/udhos/sqs-to-sns
forward - Repository: https://github.com/udhos/forward
apiping - Repository: https://github.com/udhos/apiping
mongoping - Repository: https://github.com/udhos/mongoping
rabbitping - Repository: https://github.com/udhos/rabbitping
Repository: https://github.com/udhos/udhos.github.io


Interface Parser
- All Known Implementing Classes:
CSSOMParser
,CSSParser
Based on SAC's Parser
interface by Philippe Le Hegaret.
Compared to SAC, this interface replaces some of the methods that use an
InputSource
with a Reader
. The reason is that, in opinion of
the NSAC author, the InputSource
(a concept coming from SAX) adds
bloat and in the worst case may widen the attack surface if the application
using the library is somehow abused. It is generally better that the main
application takes the responsibility of opening connections to files or
remote sources.
The reference implementation includes the replaced InputSource
methods, in case you want to use them.
-
Nested Class Summary
Modifier and TypeInterfaceDescriptionstatic enum
NSAC parser flags: theParser.Flag.STARHACK
,Parser.Flag.IEVALUES
,Parser.Flag.IEPRIO
andParser.Flag.IEPRIOCHAR
flags are supported.static interface
Interface giving access to namespace URI from the prefix. -
Method Summary
Modifier and TypeMethodDescriptionvoid
parseMediaQueryList
(String media, MediaQueryFactory queryFactory, MediaQueryHandler mqhandler) Parse a media query string into the given handler.parseMediaQueryList
(String media, Node owner) Parse an individual list of media queries.boolean
parsePriority
(Reader reader) Parse a CSS priority value (e.g. "!parsePropertyValue
(Reader reader) Parse a CSS property value.void
Parse a namespaceless CSS rule.void
parseRule
(Reader reader, Parser.NamespaceMap nsmap) Parse a CSS rule.parseSelectors
(Reader reader) Parse a comma separated list of selectors.void
parseStyleDeclaration
(Reader reader) Parse a CSS style declaration (without '{' and '}').void
parseStyleSheet
(InputSource source) Parse a CSS style sheet.void
parseStyleSheet
(Reader reader) Parse a CSS style sheet.void
parseStyleSheet
(String uri) Parse a CSS sheet from a URI.void
setDocumentHandler
(CSSHandler handler) Allow an application to set a document event handler.void
setErrorHandler
(CSSErrorHandler handler) Allow an application to set an error event handler.void
setFlag
(Parser.Flag flag) Set a parser flag.void
unsetFlag
(Parser.Flag flag) Unset a parser flag.
-
Method Details
-
setFlag
Set a parser flag.- Parameters:
flag
- the flag.
-
unsetFlag
Unset a parser flag.- Parameters:
flag
- the flag.
-
setDocumentHandler
Allow an application to set a document event handler.Applications may register a new or different handler in the middle of a parse, and the CSS parser must begin using the new handler immediately.
- Parameters:
handler
- The document handler.- See Also:
-
setErrorHandler
Allow an application to set an error event handler.If the application does not register an error event handler, any error will result in a CSSParseException being thrown.
Applications may register a new or different handler in the middle of a parse, and the CSS parser must begin using the new handler immediately.
- Parameters:
handler
- The error handler.- See Also:
-
parseStyleSheet
Parse a CSS style sheet.- Parameters:
source
- the input source of the CSS sheet.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the sheet.IllegalStateException
- if theCSSHandler
is not set.CSSException
- See Also:
-
parseStyleSheet
Parse a CSS style sheet.- Parameters:
reader
- the character stream containing the CSS sheet.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the sheet.IllegalStateException
- if theCSSHandler
is not set.- See Also:
-
parseStyleSheet
Parse a CSS sheet from a URI.The sheet is parsed as a rule list, that is, XML's
CDO
-CDC
comments are not expected.Usage of this method may have security implications. Please make sure that the URI being passed is safe to use.
- Parameters:
uri
- The URI locating the sheet.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the sheet.IllegalStateException
- if theCSSHandler
is not set.- See Also:
-
parseSelectors
Parse a comma separated list of selectors.- Parameters:
reader
- the character stream containing the selector list.- Returns:
- the selector list.
- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the list.
-
parseStyleDeclaration
void parseStyleDeclaration(Reader reader) throws CSSParseException, IOException, IllegalStateException Parse a CSS style declaration (without '{' and '}').- Parameters:
reader
- the character stream containing the CSS style declaration.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the declaration.IllegalStateException
- if theCSSHandler
is not set.
-
parsePropertyValue
Parse a CSS property value.- Parameters:
reader
- the character stream containing the CSS property value.- Returns:
- the lexical unit containing the value, possibly chained to subsequent lexical units.
- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the value.
-
parsePriority
Parse a CSS priority value (e.g. "!important").- Parameters:
reader
- the character stream containing the CSS priority.- Returns:
true
if the priority is important.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the priority.
-
parseRule
Parse a namespaceless CSS rule.- Parameters:
reader
- the character stream containing the CSS rule.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the rule.IllegalStateException
- if theCSSHandler
is not set.
-
parseRule
void parseRule(Reader reader, Parser.NamespaceMap nsmap) throws CSSParseException, IOException, IllegalStateException Parse a CSS rule.- Parameters:
reader
- the character stream containing the CSS rule.nsmap
- the namespace map.- Throws:
CSSParseException
- if an error was found and no error handler was set.IOException
- if a I/O error was found while retrieving the rule.IllegalStateException
- if theCSSHandler
is not set.
-
parseMediaQueryList
Parse an individual list of media queries.- Parameters:
media
- the string representation of the list of media queries.owner
- the node that owns the responsibility to handle the errors in the query list.- Returns:
- the media query list.
- Throws:
CSSException
-
parseMediaQueryList
void parseMediaQueryList(String media, MediaQueryFactory queryFactory, MediaQueryHandler mqhandler) throws CSSException Parse a media query string into the given handler.- Parameters:
media
- the media query text.queryFactory
- the query factory.mqhandler
- the media query list handler.- Throws:
CSSException
-CSSException.NOT_SUPPORTED_ERR
if a hard-coded limit in nested expressions was reached.
-


Number:
CMPSC 599
Level:
Graduate
Units:
1-12
Description
Prerequisite
: Consent of chair of student's doctoral committee.
Research and preparation of dissertation.


Before Change
wb.worksheets[1]["A1"].value = "bar"
wb.save(f)
writer = ExcelWriter(f, engine="openpyxl", mode=mode)
df.to_excel(writer, sheet_name="baz", index=False)
writer.save()
wb2 = openpyxl.load_workbook(f)
result = [sheet.title for sheet in wb2.worksheets]
assert result == expected
After Change
wb.worksheets[1]["A1"].value = "bar"
wb.save(f)
with ExcelWriter(f, engine="openpyxl", mode=mode) as writer:
df.to_excel(writer, sheet_name="baz", index=False)
wb2 = openpyxl.load_workbook(f)
result = [sheet.title for sheet in wb2.worksheets]
assert result == expected


filmcritic.com presents a review from staff member Max Messier. You can find the review with full credits at http://www.filmcritic.com/misc/emporium.nsf/2a460f93626cd4678625624c007f2b46/e2e728050216b2b508256889000b77b2?OpenDocument
Pitch Black A film review by Max Messier Filmcritic.com
Mama, could you leave the hall light on tonight?
One thing I love to see in a film is definition of character without the need for a windy, Oscar speech or the death of a loved one that prompts an "emotional release." The only genre that gives you that type of character is the Western. The Western is littered with good men with bad hearts and bad men who struggle for a clean conscious. The words of these men carry a heavy emotional burden and clearly define and expose the true nature of the person. Pitch Black is one of the best films I have seen in a very long time, and it carves its roots from the essence of a Western, providing amazing clarity with a direct narrative prose.
>From the moment the lights dim, the audience is thrown into an emotional situation where innocent people go to `meet their maker' and survival is their first instinct. In those first moments, Pitch Black wraps its hands around your neck and never lets go. To wit: A passenger spaceship carrying 40 people hits some type of space debris and crash lands on a barren, desert plant with only 7 people walking away. The survivors include a convicted murder with infrared lenses for eyes, a marshal with a hidden agenda, a selfish pilot focused on saving her own ass, a religious leader with three followers, and various odds and ends of characters. The three suns shine brightly on the planet's surface, and the hodgepodge of survivors form a loose collation to survive. The only problem is that something is hiding in the shadows, waiting for them in the dark.
This simple plot lets the script take shape and lets the characters develop and define their own prerogatives. With amazing cinematography that resembles the work of the David O. Russell film Three Kings, director David Twohy gives the planet a barren, washed-out look, and all of the interiors of the wrecked ship a cool metallic tinge. One of main elements that gives the film such a film grip on the senses in the presence of Vin Diesel, currently seen in the new film Boiler Room and from last year's Saving Private Ryan. His cool, somewhat haunting prose littered with poignant words reminds you of the gunslinger who has killed one too many people and has lost touch with the human race: A man of honor who provides the main catalyst for defining his fellow characters' personal attributes and motivations.
By underexposing the terror that lies in wait for the survivors, the feelings of suspense and claustrophobia are astonishing. What lies beyond the circle of light? What lies beyond the light bears a strong resemblance to the aliens designed by Geiger and the movements of the creatures mimic those of the raptors of Jurassic Park. But Twohy lets us also `see' through the eyes of the aliens and take part in the hunt for food. (The concept was first employed in the Schwartzenegger vehicle from the eighties, Predator.)
The most attractive element of Pitch Black is how beautiful the cinematography is, while developing a real sense of an alien world. You can almost feel the heat from the ground and the dizziness of the humidity in the air. The mish-mash of B-actors pull together some terrific acting, and no loose ends of the storyline are left hanging in the lurch. It's pretty amazing when you realize this script came from the guys that wrote the riveting drama, The Birds II: Land's End.
For the ride of your life (or at least just two hours of mayhem), Pitch Black will leave you with the sudden urgency to leave the hall light on when you climb into bed that night. But it's a lot scarier to not know what's in the dark, waiting for you to turn the corner. Wes Craven and John Carpenter taught us that a long time ago.
Five stars
Director: David Twohy Producer: Tom Engelman, Ted Field, Scott Kroopf Writer: Jim and Ken Wheat, David Twohy Starring: Vin Diesel, Radha Mitchell, Cole Hauser, Keith David -- Christopher Null -<EMAIL_ADDRESS>- http://www.filmcritic.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Thanks to pandoc that is used to convert markdown to html.
The page icon Hammer and Nails by SnarkHunter was download from open clip art website.
Thanks :D


Use My Techstuff is designed to close the gap between consumers and expensive, state-of-the-art technology. Too often these days, new technology is developed and sold to consumers, but at a price unreasonable for most users. That's where Use My Techstuff steps in. We have created a platform that allows people rent technology they may have to others for a cheaper price then purchasing it themselves.
Our platform allows anyone to create a profile and begin browsing all the availble technology being offered by people around the globe. Simply finish setting up your profile, search our massive list of tech for a device you want to use, setup a date and payment, and proceed to enjoy! Got a device or some tech and want to earn some money? Take some sweet pictures, write a description, and be ready to recieve offers from people wanting to utilize your tech!
Ready to start gaining access to cool tech while getting paid from others for you own? Click the button below to be taken to our Sign Up page. Once there, you can become a full-fledged member of Use My Techstuff and start experiencing ground-breaking technology and a cost your bank account will love.


Metaparameter Reference
Metaparameter Reference
This page is autogenerated; any changes will get overwritten (last generated on Tue Jun 18 16:58:45 -0700 2013)
Metaparameters
Metaparameters are parameters that work with any resource type; they are part of the Puppet framework itself rather than being part of the implementation of any given instance. Thus, any defined metaparameter can be used with any instance in your manifest, including defined components.
Available Metaparameters
alias
Creates an alias for the object. Puppet uses this internally when you provide a symbolic title:
file { 'sshdconfig':
path => $operatingsystem ? {
solaris => "/usr/local/etc/ssh/sshd_config",
default => "/etc/ssh/sshd_config"
},
source => "..."
}
service { 'sshd':
subscribe => File['sshdconfig']
}
When you use this feature, the parser sets sshdconfig
as the title,
and the library sets that as an alias for the file so the dependency
lookup in Service['sshd']
works. You can use this metaparameter yourself,
but note that only the library can use these aliases; for instance,
the following code will not work:
file { "/etc/ssh/sshd_config":
owner => root,
group => root,
alias => 'sshdconfig'
}
file { 'sshdconfig':
mode => 644
}
There’s no way here for the Puppet parser to know that these two stanzas should be affecting the same file.
audit
Marks a subset of this resource’s unmanaged attributes for auditing. Accepts an
attribute name, an array of attribute names, or all
.
Auditing a resource attribute has two effects: First, whenever a catalog is applied with puppet apply or puppet agent, Puppet will check whether that attribute of the resource has been modified, comparing its current value to the previous run; any change will be logged alongside any actions performed by Puppet while applying the catalog.
Secondly, marking a resource attribute for auditing will include that attribute in inspection reports generated by puppet inspect; see the puppet inspect documentation for more details.
Managed attributes for a resource can also be audited, but note that changes made by Puppet will be logged as additional modifications. (I.e. if a user manually edits a file whose contents are audited and managed, puppet agent’s next two runs will both log an audit notice: the first run will log the user’s edit and then revert the file to the desired state, and the second run will log the edit made by Puppet.)
before
References to one or more objects that depend on this object. This parameter is the opposite of require — it guarantees that the specified object is applied later than the specifying object:
file { "/var/nagios/configuration":
source => "...",
recurse => true,
before => Exec["nagios-rebuid"]
}
exec { "nagios-rebuild":
command => "/usr/bin/make",
cwd => "/var/nagios/configuration"
}
This will make sure all of the files are up to date before the make command is run.
loglevel
Sets the level that information will be logged.
The log levels have the biggest impact when logs are sent to
syslog (which is currently the default). Valid values are debug
, info
, notice
, warning
, err
, alert
, emerg
, crit
, verbose
.
noop
Boolean flag indicating whether work should actually
be done. Valid values are true
, false
.
notify
References to one or more objects that depend on this object. This parameter is the opposite of subscribe — it creates a dependency relationship like before, and also causes the dependent object(s) to be refreshed when this object is changed. For instance:
file { "/etc/sshd_config":
source => "....",
notify => Service['sshd']
}
service { 'sshd':
ensure => running
}
This will restart the sshd service if the sshd config file changes.
require
References to one or more objects that this object depends on. This is used purely for guaranteeing that changes to required objects happen before the dependent object. For instance:
# Create the destination directory before you copy things down
file { "/usr/local/scripts":
ensure => directory
}
file { "/usr/local/scripts/myscript":
source => "puppet://server/module/myscript",
mode => 755,
require => File["/usr/local/scripts"]
}
Multiple dependencies can be specified by providing a comma-separated list of resources, enclosed in square brackets:
require => [ File["/usr/local"], File["/usr/local/scripts"] ]
Note that Puppet will autorequire everything that it can, and there are hooks in place so that it’s easy for resources to add new ways to autorequire objects, so if you think Puppet could be smarter here, let us know.
In fact, the above code was redundant — Puppet will autorequire any parent directories that are being managed; it will automatically realize that the parent directory should be created before the script is pulled down.
Currently, exec resources will autorequire their CWD (if it is
specified) plus any fully qualified paths that appear in the
command. For instance, if you had an exec
command that ran
the myscript
mentioned above, the above code that pulls the
file down would be automatically listed as a requirement to the
exec
code, so that you would always be running againts the
most recent version.
schedule
On what schedule the object should be managed. You must create a schedule object, and then reference the name of that object to use that for your schedule:
schedule { 'daily':
period => daily,
range => "2-4"
}
exec { "/usr/bin/apt-get update":
schedule => 'daily'
}
The creation of the schedule object does not need to appear in the configuration before objects that use it.
stage
Which run stage a given resource should reside in. This just creates a dependency on or from the named milestone. For instance, saying that this is in the ‘bootstrap’ stage creates a dependency on the ‘bootstrap’ milestone.
By default, all classes get directly added to the ‘main’ stage. You can create new stages as resources:
stage { ['pre', 'post']: }
To order stages, use standard relationships:
stage { 'pre': before => Stage['main'] }
Or use the new relationship syntax:
Stage['pre'] -> Stage['main'] -> Stage['post']
Then use the new class parameters to specify a stage:
class { 'foo': stage => 'pre' }
Stages can only be set on classes, not individual resources. This will fail:
file { '/foo': stage => 'pre', ensure => file }
subscribe
References to one or more objects that this object depends on. This metaparameter creates a dependency relationship like require, and also causes the dependent object to be refreshed when the subscribed object is changed. For instance:
class nagios {
file { 'nagconf':
path => "/etc/nagios/nagios.conf"
source => "puppet://server/module/nagios.conf",
}
service { 'nagios':
ensure => running,
subscribe => File['nagconf']
}
}
Currently the exec
, mount
and service
types support
refreshing.
tag
Add the specified tags to the associated resource. While all resources are automatically tagged with as much information as possible (e.g., each class and definition containing the resource), it can be useful to add your own tags to a given resource.
Multiple tags can be specified as an array:
file {'/etc/hosts':
ensure => file,
source => 'puppet:///modules/site/hosts',
mode => 0644,
tag => ['bootstrap', 'minimumrun', 'mediumrun'],
}
Tags are useful for things like applying a subset of a host’s configuration
with the tags
setting:
puppet agent --test --tags bootstrap
This way, you can easily isolate the portion of the configuration you’re trying to test.
This page autogenerated on Tue Jun 18 16:58:47 -0700 2013


Already a member? Log in
Please enter your username below and press the send button.A password reset link will be sent to you.
If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.
Website: http://www.knallisworld.de/
Following: 2 Users
http://stackoverflow.com/questions/39500634/use-xcodebuild-xcode-8-and-auto...
This link recently saved by knalli on September 30, 2016
https://pewpewthespells.com/blog/migrating_code_signing.html#building-for-d...
This link recently saved by knalli on September 30, 2016
http://centminmod.com/nginx_configure_wordpress.html
This link recently saved by knalli on April 08, 2016
http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api
This link recently saved by knalli on March 14, 2016
http://ionicons.com/cheatsheet.html
This link recently saved by knalli on March 08, 2016
http://jeremenichelli.github.io/2016/02/seven-things-to-consider-while-buil...
This link recently saved by knalli on February 25, 2016
http://www.autobahnatlas-online.de/
This link recently saved by knalli on February 25, 2016
This link recently saved by knalli on February 13, 2016
http://facebook.github.io/design/handskit.html
This link recently saved by knalli on January 18, 2016


AWS::ElasticLoadBalancingV2::LoadBalancer LoadBalancerAttribute
Specifies an attribute for an Application Load Balancer, a Network Load Balancer, or a Gateway Load Balancer.
Syntax
To declare this entity in your AWS CloudFormation template, use the following syntax:
Properties
Key
-
The name of the attribute.
The following attributes are supported by all load balancers:
-
deletion_protection.enabled
- Indicates whether deletion protection is enabled. The value istrue
orfalse
. The default isfalse
. -
load_balancing.cross_zone.enabled
- Indicates whether cross-zone load balancing is enabled. The possible values aretrue
andfalse
. The default for Network Load Balancers and Gateway Load Balancers isfalse
. The default for Application Load Balancers istrue
, and cannot be changed.
The following attributes are supported by both Application Load Balancers and Network Load Balancers:
-
access_logs.s3.enabled
- Indicates whether access logs are enabled. The value istrue
orfalse
. The default isfalse
. -
access_logs.s3.bucket
- The name of the S3 bucket for the access logs. This attribute is required if access logs are enabled. The bucket must exist in the same region as the load balancer and have a bucket policy that grants Elastic Load Balancing permissions to write to the bucket. -
access_logs.s3.prefix
- The prefix for the location in the S3 bucket for the access logs. -
ipv6.deny_all_igw_traffic
- Blocks internet gateway (IGW) access to the load balancer. It is set tofalse
for internet-facing load balancers andtrue
for internal load balancers, preventing unintended access to your internal load balancer through an internet gateway.
The following attributes are supported by only Application Load Balancers:
-
idle_timeout.timeout_seconds
- The idle timeout value, in seconds. The valid range is 1-4000 seconds. The default is 60 seconds. -
routing.http.desync_mitigation_mode
- Determines how the load balancer handles requests that might pose a security risk to your application. The possible values aremonitor
,defensive
, andstrictest
. The default isdefensive
. -
routing.http.drop_invalid_header_fields.enabled
- Indicates whether HTTP headers with invalid header fields are removed by the load balancer (true
) or routed to targets (false
). The default isfalse
. -
routing.http.preserve_host_header.enabled
- Indicates whether the Application Load Balancer should preserve theHost
header in the HTTP request and send it to the target without any change. The possible values aretrue
andfalse
. The default isfalse
. -
routing.http.x_amzn_tls_version_and_cipher_suite.enabled
- Indicates whether the two headers (x-amzn-tls-version
andx-amzn-tls-cipher-suite
), which contain information about the negotiated TLS version and cipher suite, are added to the client request before sending it to the target. Thex-amzn-tls-version
header has information about the TLS protocol version negotiated with the client, and thex-amzn-tls-cipher-suite
header has information about the cipher suite negotiated with the client. Both headers are in OpenSSL format. The possible values for the attribute aretrue
andfalse
. The default isfalse
. -
routing.http.xff_client_port.enabled
- Indicates whether theX-Forwarded-For
header should preserve the source port that the client used to connect to the load balancer. The possible values aretrue
andfalse
. The default isfalse
. -
routing.http.xff_header_processing.mode
- Enables you to modify, preserve, or remove theX-Forwarded-For
header in the HTTP request before the Application Load Balancer sends the request to the target. The possible values areappend
,preserve
, andremove
. The default isappend
.-
If the value is
append
, the Application Load Balancer adds the client IP address (of the last hop) to theX-Forwarded-For
header in the HTTP request before it sends it to targets. -
If the value is
preserve
the Application Load Balancer preserves theX-Forwarded-For
header in the HTTP request, and sends it to targets without any change. -
If the value is
remove
, the Application Load Balancer removes theX-Forwarded-For
header in the HTTP request before it sends it to targets.
-
-
routing.http2.enabled
- Indicates whether HTTP/2 is enabled. The possible values aretrue
andfalse
. The default istrue
. Elastic Load Balancing requires that message header names contain only alphanumeric characters and hyphens. -
waf.fail_open.enabled
- Indicates whether to allow a WAF-enabled load balancer to route requests to targets if it is unable to forward the request to AWS WAF. The possible values aretrue
andfalse
. The default isfalse
.
Required: No
Type: String
Maximum:
256
Pattern:
^[a-zA-Z0-9._]+$
Update requires: No interruption
-
Value
-
The value of the attribute.
Required: No
Type: String
Maximum:
1024
Update requires: No interruption
See also
-
ModifyLoadBalancerAttributes in the Elastic Load Balancing API Reference (version 2015-12-01)
-
Load balancer attributes in the User Guide for Application Load Balancers
-
Load balancer attributes in the User Guide for Network Load Balancers
-
Load balancer attributes in the User Guide for Gateway Load Balancers


{% extends "base.html" %} {% block content %}
This raw data about you is used to feed your personal metrics, and is acessible only to you.
The following personal data is computed from your raw data above. You can choose whether or not to share this data publicly.


Dashboard
OK
OK
Canel
OK
OK
Latitude
Longitude
LED Color
Red
Blue
Green
Project Location
Is Hazardous?
Cancel
OK


HOME
MAIN
RACE
ABOUT
Hakka Cuisine
Cantonese Cuisine
MENU
LUNCH
DINNER
GALLERY
Images
Video
FAQs
GITHUB DIY
PAGE DIY
CONTACT US
CONTACT US
FEEDBACK
GALLERY


{{(user|async)?.country}}
{{(user|async)?.bio}}
If you want to know more about the license follow above link!


See the Pen Hello World React by Decoding Dev (@decodingdev) on CodePen.
See the Pen ReactJS Adding in JSX by Decoding Dev (@decodingdev) on CodePen.
See the Pen React Clock - Updating React Elements by Decoding Dev (@decodingdev) on CodePen.
See the Pen React Components by Decoding Dev (@decodingdev) on CodePen.
| Container | Presentational |
|---|---|
|
|
See the Pen Clock with React State by Decoding Dev (@decodingdev) on CodePen.
See the Pen Toggle by Decoding Dev (@decodingdev) on CodePen.
Create provider in app root
import { createStore } from 'redux'
import todoApp from './reducers'
let store = createStore(todoApp)
Use connect to map the stores state and dispatch to the props of a component
const mapStateToProps = state => {
return {todo : state.todos[0]}
}
const mapDispatchToProps = dispatch => {
return {
destroyTodo : () => dispatch({type : 'DESTROY_TODO'})
}
}
export default connect(
mapStateToProps,
mapDispatchToProps
)(TodoItem)
To change data you dispatch an action
const mapDispatchToProps => dispatch => {
return {
getLinks: (topicName) => dispatch(getLinks(topicName)),
startAdd: (topicName) => dispatch(startAdd(topicName)),
};
}
import { createSelector } from 'reselect'
const getVisibilityFilter = (state, props) =>
state.todoLists[props.listId].visibilityFilter
const getTodos = (state, props) =>
state.todoLists[props.listId].todos
const getVisibleTodos = createSelector(
[ getVisibilityFilter, getTodos ],
(visibilityFilter, todos) => {
switch (visibilityFilter) {
case 'SHOW_COMPLETED':
return todos.filter(todo => todo.completed)
case 'SHOW_ACTIVE':
return todos.filter(todo => !todo.completed)
default:
return todos
}
}
)
export default getVisibleTodos
export function requestLinks(topicName) {
return {
type: REQUEST_LINKS,
topicName,
};
}
function linkListContainerReducer(state, action) {
switch (action.type) {
case REQUEST_LINKS_SUCCEEDED:
return state.set('links', action.links);
case ADD_LINK_SUCCESS:
return addLink(state, action.link);
default:
return state;
}
}
Feel free to ask questions