Ukraine's state banks reduce non-performing loans by over US$909 mln
As of July 1, over 70,000 relevant lawsuits worth over UAH 116 billion (US$4.8 billion) have been filed with courts by state-run banks to recover debt on loans.
Ukraine's Finance Minister says state-owned banks in the first half of 2019 reduced non-performing loans by UAH 22 billion (US$909.1 million).
In particular, the state-owned banks, including financial institutions, reduced debts by UAH 3.5 billion (US$144.6 million), restructured them by UAH 10.6 billion (US$438 million), and covered debts with reserves at UAH 2.9 billion (US$119.8 million), according to the ministry's non-performing loans status report.
In the first half of 2019, Oschadbank successfully completed debt restructuring with Firm T.M.M. LLC, Imperovo Foods LLC, Agroholding Avangard, and PJSC Rise-Maksymko. Two debt restructuring cases have been launched with WOG Group's companies.
Ukreximbank opened its first case with Office Construction Agency LLC, which became one of the largest in terms of the amount of debt to be restructured.
At the same time, public sector banks are actively involved in debt collection. As of July 1, courts have more than 70,000 relevant lawsuits worth over UAH 116 billion (US$4.8 billion). Noteworthy, almost 54,000 lawsuits worth UAH 26.5 billion (US$1.1 billion) were lodged in the first half of 2019.
It is also noted that the share of non-performing loans in Ukraine's banking system remains significant, that is, 51% as of July, or UAH 581 billion (US$24 billion), of which state-owned banks account for 65%.
UNIAN memo. The state represented by the Finance Ministry owns four largest Ukrainian banks in terms of assets, namely PrivatBank, Ukreximbank, Oschadbank, and Ukrgasbank.
Ukraine's state-owned banks in 2018 reduced problem loans by UAH 5 billion, or US$206.6 million, and restructured debts by UAH 21 billion, or US$867.8 million.


Thoughts on JavaScript, AngularJS, and more
- Daily score sums…
- …rolled up into weekly score sums
-
The formula returns an error for future weeks that haven’t been calculated yet.
-
A particular oddity with Google Spreadsheets was causing the VLOOKUP to lock the formula in place and make it uneditable (turns out this is a Google Spreadsheets bug when doing a VLOOKUP on pivot tables – hopefully this gets fixed soon).
- Making sure commandline tools was installed
- Making sure RubyGems was up to date with
sudo gem update --system
Using Google Spreadsheets (or Excel) to Chart Your Success Through Life
08 May 2014This post originally appeared in my other blog, Living For Improvement. However, given the technical nature of the lifehack at hand, I decided to cross-post it here. Enjoy!
For years now, I’ve been using a system called Key Lifestyle Indicators (KLIs) that I modeled after the idea of Key Performance Indicators in business.
My KLI definitions have changed over the years; here’s my current set-up:
This system works very well for me, consistently reminding me where I’m slacking and where I’m succeeding. The best part: it requires less than 10 seconds per day to enter the necessary information (nowadays it’s simply 1s and 0s transformed into a moving average).
It wasn’t until this past week that I found a way to leverage this tracked data in a new, interesting way. The inspiration came from reading Wait But Why’s post on what your life looks like plotted out into weeks (hint: You have less than 4,500 weeks in your life to spend – how have you been using them?).
I loved the idea of a meaningful reminder of the limited number of weeks we have on this planet. Thankfully, Wait But Why offers some sweet calendars that allow you to track how you’re living out your weeks – either with hand-scribbled notes or via color coding.
I’ll probably pick up one of these awesome calendars some time in the near future, but I wondered if I could use my years of KLI data to graphically represent this without needing to create yet another place to track my progress through life.
This post describes how I took my KLI data and created a Wait-But-Why-styled life calendar that lives in Google Spreadsheets (or Excel, if that’s your thing). If you track similar data in a spreadsheet, this article should help you in creating a similar set-up (read Wait But Why’s post for a deeper understanding of why a life calendar is awesome).
Step 1: Prototype the end result
Here’s what I wanted my life calendar to look like when all was said and done:
Note how I keep untracked weeks in gray, but everything else is colored yellow, green, or red depending on how my KLIs looked that week. The goal was to have this automatically calculated for me, as manually-inputted tracking can get quite annoying. But in order for this to become automated, I needed to pull together all of the necessary data, which brings me to step 2…
Step 2: Survey the current datascape
The calendar prototype looked good, but the data I needed was siloed in different cells. In other words, because none of the data was rolled up by day or week, some intermediary data compilation was required before the calendar could pull what it needed.
Step 3: Compile the calendar data
After surveying my data, I realized I needed to compile my data in two ways to transition to the life calendar:
I ended up adding two additional columns into my KLI sheet (which I now keep hidden) to accomplish step 1. See below:
I calculated the week of my life (Column L) using this formula: =ROUNDDOWN((CURRENT_DATE - DATE_I_WAS_BORN +1)/7)
. The +1 in that formula ensures that the calculation includes today’s date when rounding down to the current week.
From there, I summed up each day’s scores using the sum of columns B, C, D, and E. For example, for the day on row 50, the M50 cell contained =B50+C50+D50+E50
.
For step 2, I used a pivot table to keep an up-to-date weekly summary of my scores:
It rolls up all of the scores by week using the two new columns I showed in the previous screenshot. With my daily scores summed and rolled up by week, it was time to link this data to my calendar prototype.
Step 4: Bring the calendar to life
This step was the most time intensive, so I broke into three main tasks:
A. Link the data points to the calendar
This task involved a VLOOKUP formula to pull the right score based on week. To pull from the right place in the pivot table, I simply needed to calculate the current week and then do the VLOOKUP. It’s a little heavy to look at, but it ended up looking like this: =VLOOKUP(rounddown((CURRENT_YEAR*365)/7 + WEEK_INDEX+1),'Weekly Scores'!$A:$B,2, False)
Here’s a broader view with cell highlighting. Notice how it uses the Week Index and the current year to calculate the correct week of my life, and then runs the VLOOKUP based on that value:
B. Handle errors
Although the VLOOKUP worked quite well, there were two errors I had to account for:
To solve the first issue, it was rather easy. I wrapped the VLOOKUP in an IFERROR like so:
=IFERROR(VLOOKUP_GOES_HERE, "")
This made sure that the formula returned an empty string for future weeks, keeping the calendar clean and error-free.
To solve the second issue, I used a trick I found on Stack Exchange. The trick involves arbitrarily adding a +0 to your VLOOKUP calculation. This won’t skew the calculation, obviously, and for some reason keeps the cell formula editable.
Here’s what the VLOOKUP looked like with the +0 added in:
VLOOKUP(rounddown((CURRENT_YEAR*365)/7 + WEEK_INDEX+1),'Weekly Scores'!$A:$B,2, False)+0
Problem solved!
With both errors handled, the final formula looked like this:
=IFERROR(VLOOKUP(rounddown((CURRENT_YEAR*365)/7 + WEEK_INDEX+1),'Weekly Scores'!$A:$B,2, False)+0, "")
C. Set up conditional formatting rules
With the hard part out of the way, all I needed to do was make the cells color coded based on my score that week.
In my KLI system, the ideal day would earn me 4 points. Therefore, my ideal week would yield 28 points. With that in mind, here’s how I defined and color-coded great, ok, and bad weeks.
As you can see, 20 points or above is a good week, 15-20 points is a so-so week, and anything less is a red flag. Also notice how I alter the text color as well to hide the number calculation that lives in the cell.
Step 5: Celebrate!
At this point, I took a step back and appreciated my sexy, new life calendar, auto-calculated based on the KLI system I’ve trusted for years.
Tim Urban, if you’re reading this post, I just want to say thank you for the inspiration. I follow your blog religiously, and this obviously could not have come about without your wisdom. Cheers mate.
Now, off to appreciate the precious weeks I have left.
Preventing MySQL from Randomly Stopping on Ubuntu 12.04
05 May 2014I recently migrated my WordPress blog from GoDaddy to Digital Ocean. Digital Ocean is a fantastic way to set up your own server at low cost, but it does require you to do a lot of the maintenance work yourself.
I was able to follow Digital Ocean’s guide for migrating my previously existing WordPress blog, LivingForImprovement.com, from GoDaddy to Digital Ocean, but one pain point I couldn’t resolve was MySQL randomly terminating itself due to low memory on my Digital Ocean droplet. Without MySQL running, blog posts couldn’t be fetched when people visited my blog. No bueno :(.
I made sure a swap file was active on my droplet, but every week or so, MySQL would still terminate itself. Working with memcache also seemed like a viable option, but it looked a little bit over my head. While I do plan to learn memcache eventually, I decided to get my toes wet in the world of shell scripting to help manage the problem until I do.
It’s nothing special, but here’s what I did:
Step 1 - Create a simple shell script
sudo nano /usr/local/sbin/mysql_check.sh
Then, I wrote the following:
#!/bin/bash
if [[ ! "$(service mysql status)" =~ "start/running" ]]
then
service mysql start
# echo "Restarting MySql" # Uncomment for debugging
else
# echo "Looks like MySql is running. No action taken" # Uncomment for debugging
fi
Finally, make sure your script is executable:
sudo chmod +x /usr/local/sbin/mysql_check.sh
Step 2 - Set up a cron job to check MySQL’s status every minute
Until I sit down and learn the ins and outs of memcache, I’d prefer that this cron check every minute to make sure MySQL is running. I had to do this in root’s crontab, since the commands I’d need the script to run require root.
sudo crontab -e
And within your root crontab:
PATH=/usr/sbin:/usr/bin:/sbin:/bin
*/1 * * * * /usr/local/sbin/mysql_check.sh >> /home/jon/cronlog.log 2>&1
I had to add the PATH variable to the script to allow crontab to run the commands in my shell script, such as service mysql start
as per this article’s discussion.
Just for debugging purposes, I’m routing any output to a log file in my home directory, just to initially measure how often the cron needs to restart MySQL. If you’re not curious about this, you can change the above to:
PATH=/usr/sbin:/usr/bin:/sbin:/bin
*/1 * * * * /usr/local/sbin/mysql_check.sh
Step 3 - Improvement
I realize that this isn’t the most elegant solution, but it works for now, until I have the bandwidth to learn to use memcache like a boss. Any suggestions / feedback? Leave it in the comments section below. :)
A Better Way to Integrate AngularJS and Google Charts
05 Apr 2014Last Updated: 4/12/2014
I’m fairly new to the world of web development (I started coding a year and half ago), and one of my favorite discoveries thus far is AngularJS.
As with many people new to Angular, the hardest concept to grok was that of directives. Whenever you’d like to manipulate the dom in some way, a directive is how you do it. Additionally, directives (along with services) are a great way to integrate third party libraries and APIs with Angular.
I’ve recently been working on a small meditation timer app and was having some trouble integrating the Google Charts / Visualization API with AngularJS. I found a solid starting point with Gavin Draper’s article on how he did it.
His code samples were fantastic for getting me up and running. But as I continued to work on the application, I found a few disadvantages with that implementation, and figured it never hurts to improve on the great content of others. Here are a few areas I wanted to work on:
Bootstrapping Angular
google.setOnLoadCallback(function () {
angular.bootstrap(document.body, ['my-app']);
});
google.load('visualization', '1', {packages: ['corechart']});
This is the code used to initialize the Angular application in Gavin’s post. The given code here works just fine, but I noticed that Angular’s bootstrap function only runs once the Google Loader fires off the callback function.
By requiring the Google Loader callback to fire before bootstrapping the Angular application, if the Google Loader ever falters, the app simply won’t run. That felt like an unacceptable trade-off.
A better approach would be to wrap the Googe Loader in an Angular Service, which I’ll explain how I did later in this post.
Nested models
googleChart.directive("googleChart",function(){
return{
restrict : "A",
link: function($scope, $elem, $attr){
var dt = $scope[$attr.ngModel].dataTable;
var options = {};
if($scope[$attr.ngModel].title)
options.title = $scope[$attr.ngModel].title;
var googleChart = new google.visualization[$attr.googleChart]($elem[0]);
googleChart.draw(dt,options)
}
}
});
The directive used in Gavin’s article wasn’t utilizing Angular’s useful $scope.$eval
for reading attributes. Rather, it was passing the ngModel attribute directly to the $scope
object. If you had a nested model – a best practice in many situations – such as $scope.chartModel.dataset1
, the directive would break by trying to do something like this var dt = $scope['chartModel.dataset1'].dataTable;
As I mentioned, a better approach would be to use $scope.$eval
, which will safely eval the attribute to give you access to the necessary model.
Unit Testing
The only other concern I had was, by calling google.load in the global scope, unit testing became more difficult. My Karma / Jasmine setup was failing because the google namespace wasn’t defined in the test environment when injecting my Angular app module.
Again, the way to avoid this problem is to keep the google namespace wrapped in an Angular Service so that it can be mocked and/or ignored in my various unit tests.
A Better Solution
Given the drawbacks listed above, here’s how I ended up implementing Google Charts. I consider this to be a more ‘Angular’ way to do it, by relying more heavily on Angular services, watchers, and keeping the Google Loader in a nicely contained environment.
Let’s start with the DOM and the controller:
DOM:
<!DOCTYPE html>

Note that $scope.activateChart
is going to be the trigger to build the chart.
Controller:
var app = app || angular.module('myApp', []);
app.controller('ChartCtrl', function($scope, ChartService) {
// activateChart flips to true once the Google
// Loader callback fires
$scope.activateChart = false;
// This is where my data model will be stored.
// "visual" will contain the chart's datatable
$scope.dataModel = {
visual: {},
metaData: {},
data: {}
};
// First, we attempt to load the Visualization module
var loadGoogle = ChartService.loadGoogleVisualization();
// If the Google Loader request was made with no errors,
// register a callback, and construct the chart data
// model within the callback function
if (loadGoogle) {
google.setOnLoadCallback(function() {
$scope.dataModel.visual.dataTable = new google.visualization.DataTable();
// Set up the dataTable and columns
var dataTable = $scope.dataModel.visual.dataTable;
dataTable.addColumn("string","Date")
dataTable.addColumn("number","Minutes")
// Populate row data
dataTable.addRow(["3/1/14",5]);
dataTable.addRow(["3/2/14",13]);
// Update the model to activate the chart on the DOM
// Note the use of $scope.$apply since we're in the
// Google Loader callback.
$scope.$apply(function(){
$scope.activateChart = true;
});
});
}
});
Next, let’s look at the Angular Service. I chose to place google.load() in a try/catch block to guard against any errors that might spring up if any breaking changes are introduced in the future.
There’s also a quirk in the Google Loader worth noting: If you want to load an API after the page renders, you need to add an arbitrary callback, otherwise the loader will use document.write(), which will overwrite all of the HTML on the page.
app.factory('ChartService', function() {
return {
/**
* Loads the visualization module from the Google Charts API
* if available
* @returns {boolean} - Returns true is successful, or false
* if not available
*/
loadGoogleVisualization: function() {
// Using a try/catch block to guard against unanticipated
// errors when loading the visualization lib
try {
// Arbitrary callback required in google.load() to
// support loading after initial page rendering
google.load('visualization', '1', {
'callback':'console.log(\'success\');',
'packages':['corechart']
});
return true;
} catch(e) {
console.log('Could not load Google lib', e);
return false;
}
}
};
});
And finally, let’s take a look at the underlying directive.
Directive:
app.directive("googleChart",function(){
return{
restrict : "A",
link: function($scope, $elem, $attr){
var model;
// Function to run when the trigger is activated
var initChart = function() {
// Run $eval on the $scope model passed
// as an HTML attribute
model = $scope.$eval($attr.ngModel);
// If the model is defined on the scope,
// grab the dataTable that was set up
// during the Google Loader callback
// function, and draw the chart
if (model) {
var dt = model.dataTable,
options = {},
chartType = $attr.googleChart;
if (model.title) {
options.title = model.title;
}
var googleChart = new google.visualization[chartType]($elem[0]);
googleChart.draw(dt,options)
}
};
// Watch the scope value placed on the trigger attribute
// if it ever flips to true, activate the chart
$scope.$watch($attr.trigger, function(val){
if (val === true) {
initChart();
}
});
}
}
});
And there you have it! Google Visualization Charts right in your Angular application without any worries of Google Loader failure, unit testing difficulties, or data model restrictions.
Granted, I’m still a beginner to AngularJS (I’ve only been writing Angular apps for 7-8 months now), so if you see any faults here, definitely point it out in the comments below! For starters, it probably would’ve made more sense to register the Google Loader callback in the service, rather than the controller. Comment if you agree!
-Jon
Installing Jekyll on OS X 10.9.2
04 Apr 2014Ironically, as I was trying to install Jekyll to set up this blog on Github, I ran into a lot of problems. The command-line error wasn’t too helpful but it looked something like this:
Building native extensions. This could take a while...
ERROR: Error installing jekyll:
ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile
make "DESTDIR=" clean
make "DESTDIR="
compiling porter.c
porter.c:359:27: warning: '&&' within '||' [-Wlogical-op-parentheses]
if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
~~ ~~~~~~~^~~~~~~~~~~~~~~~~~~~
porter.c:359:27: note: place parentheses around the '&&' expression to silence this warning
if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
^
( )
1 warning generated.
compiling porter_wrap.c
linking shared-object stemmer.bundle
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [stemmer.bundle] Error 1
make failed, exit code 2
Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/fast-stemmer-1.0.2 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/extensions/universal-darwin-13/2.0.0/fast-stemmer-1.0.2/gem_make.out
Both the Jekyll troubleshooting page and StackOverflow recommended two ways to resolve installation issues:
However, neither of these did the trick for me. Thankfully, after an hour of searching, I ended up finding the right clues here.
As per the StackOverflow link above, I installed Homebrew and RVM, using this guide; this did the trick. Success!
While I do wonder why RVM / Homebrew was necessary, it seems to be working for others as well. Thought I’d call it out for any others struggling out there, as I had difficulty finding the right clues on Stack Overflow.


--- layout: submission title: AW NUTTS year: 2015 image: nuts.jpg team: >
Use your ultra American Pachinko skills to knock the Super Deluxe Hexagonal Projectile into one of the four goals. each goal gives between 100 and 400 points, and you get five tries. Heaven (top right) is worth 400 points, Below (lower left) is worth 300, "Good" in the center is worth 100 points, and "Wow" between good and heaven is worth 200.
All of the point values are written on the board.
Our game is a unique game imported from Japan made by an unknown manufacturer. The manual has been lost, so its true purpose has been interpolated. We estimate that it was once used for determining quantities of food to ration out during times of poor harvest.


| AnyObject |
|
| CzLabel |
|
Union type that encompass all the usual types we use for labels |
|
| Dictionary |
|
A shorthand for indexed object with |
|
| Many |
|
A shorthand to specify if it's either the given type or an array of it |
|
| Nil |
|
Shorthand type for type being either itself, null or undefined |
|
| SelectOptionLabel |
|
The label of a SelectOption |
|
| Sorter |
|
Describes a function to be used as argument for |
|


This function instantiates an OHDSI CDM (referred to throughout as OMOP for brevity) database from raw ICNARC XML. It can be specfied to output either version 5.3.1 or 6.0.0. In doing so, it creates an extremely spartan instance of OMOP. This behaviour is intentional to short cut the creation of an OMOP database, which can be a daunting process. After the OMOP database has been created, you have the option to add more data directly from additional ICNARC XML in the future, or begin to populate the database directly with data from another source, with your patient and their outcomes already populated.
omopify_xml( project_path, nhs_trust, cdm_version = "5.3.1", vocabulary_version = "5", database_name = NULL, database_engine = "postgres", host_name = "localhost", port_no = 5432, username = NULL, from_empty = TRUE, vocabulary = TRUE, indexes = TRUE, constraints = TRUE, sqlite_file = NULL, dummy_data = FALSE )
| project_path | the path to your project folder with the following populated folders:
|
|---|---|
| nhs_trust | a character string with the full name of the trust. |
| cdm_version | the version of the CDM you are using, choose from:
|
| vocabulary_version | the version of the vocabulary you are using |
| database_name | the name of the database you are connecting to |
| database_engine | the database engine, choose from:
|
| host_name | host ip address |
| port_no | port number |
| username | username to database (*must* have write privaleges) |
| from_empty | logical flag: do you want to create the OMOP database from stratch. If you want to first write out the tables yourself this can be set to FALSE |
| vocabulary | logical flag: do you want to write out vocabularies |
| indexes | logical flag: do you want to create db with indexes |
| constraints | logical flag: do you want to create db with relational constraints |
| sqlite_file | a filename if using sqlite |
| dummy_data | logical flag: do you want to ignore XML files and use local dummy data instead |
TRUE if completed without errors


by thadiusofx3 » Fri Dec 29, 2006 12:40 pm
rigging is the controls and skeleton for a model, which allows the animator to manipulate it
I think what he means about keeping the mesh and rigging separate from it's poses, is so we can take a single pose (or position) for a rigging and apply it to different models that have the same rigging
(for example in xenimus the -dumdance command, the models probably all have the same rigging so they can all have that pose applied to them and do the same dance instead of having to animate a dance for every single one of them)


3.5 Years, 500k Lines of Go (Part 2)
Apr 19, 2017Series: 3.5 Years of Go
This is a second installment of my takeaways working on Juju at Canonical. See Part 1 for the full intro.
At the end of the last post, I promised to talk about APIs, versioning, the database, refactoring, logging, idioms, and code reviews. So let’s get started.
APIs
API Technology
Juju uses JSON RPC over websockets for communication, both server to server and client to server. This was a very good choice for us, in my opinion.
REST may be popular with web developers, but I find its resource-oriented approach to be entirely too limiting for basically any application more than a simple storage server. You start having to bend over backwards to make actions look like CRUD. The classic case in REST is transferring money from one bank account to another. The answer in REST is to make this into a Create of a “Transfer” value that has a debit account and a credit account values. Which is horrible.
Writing code is 99% calling functions. And RPC is just calling functions over there. This is really what everyone wants to do, so how about we just let people do it.
API Versioning
When I joined Juju I learned that they intended the Juju API to be both backward compatible and forward compatible. At first, this seemed like a big mistake. Surely such restrictions would strangle innovation and make change impossible. Turns out this was not such a terrible idea.
As a product requirement, it makes sense for Juju. Many users of Juju may have multiple deployments of Juju running different versions. Maybe you have some really stable infrastructure on an older version that runs just fine. You don’t want to touch it because there’s really not reason. And maybe you have some new environments that you really want to be able to leverage the newest and best features of Juju. No one wants to have to keep a different CLI binary around for each remote environment, what a pain.
Because we’re running json RPC, it’s fairly easy to keep backwards and forwards compatibility. Older versions of APIs will drop unknown fields in structs on the floor when they unmarshal API values. Thus, if you design new features around new fields in a struct, then you can gracefully degrade functionality when talking to an older server. Maybe
This is a post in the 3.5 Years of Go series.
Other posts in this series:
- Apr 19, 2017 - 3.5 Years, 500k Lines of Go (Part 2)
- Mar 24, 2017 - 3.5 Years, 500k Lines of Go (Part 1)


PHOTOS: Dyson's new global HQ is in one of Singapore's most historic sites - see how St James Power Station evolved over the last 92 years, Business Insider - Business Insider Singapore
by Lamont Mark SmithAfter abruptly cancelling its “ingenious” electric car project in Singapore, British technology company Dyson has announced plans to move into St James Power Station, one of the nation’s most historic sites.
The 110,000 sq ft. power station will undergo renovation and retrofitting works that are expected to finish by the second half of 2021.
In a report on Thursday (Nov 28), The Straits Times reported that Dyson was planning to double its pool of engineers and scientists here in the next five years. The company currently hires around 1,100 people in Singapore, The Straits Times said in previous report.
Jim Rowan, Dyson’s chief executive, said in a statement that the company had outgrown its current Singapore technology centre at Singapore Science Park, and that the “historic St James Power Station will be a most inspiring backdrop for Dyson’s people”.
“It will be a hive for our research and development endeavours, as we focus on great technology breakthroughs,” he added.
Built as a power station in the 1920s and then abandoned, the national monument was for a time also one of Singapore’s biggest nightlife hubs.
These archived photos from The Straits Times and The New Paper show how the site situated near Sentosa has evolved over the past century:
According to the National Library Board (NLB), St James Power Station was Singapore’s first power station, and was built by the British between 1924 and 1927.
Located near the entrance of Sentosa, the coal-fired station started generating electricity on June 1, 1927, and was officially opened by Sir Hugh Clifford.
However, the station was beset with power failures and blackouts.
In 1950, Singapore suffered its most extensive blackout when electricity to the entire island was cut off for 1.5 hours, NLB said.
Then in 1956, the station underwent renovations as it was deemed to be running inefficiently.
The site was reopened in 1960 by Goh Keng Swee, who was Finance Minister at the time.
The upgraded power station was equipped with new machines and generators that increased power output to 40,000 kilowatts.
However, it was unable to meet the Republic’s rising demand for electricity, and was decomissioned in 1976.
In the 1980s, the building was converted into a warehouse by the Port of Singapore Authority until 1992.
After which, it remained largely vacant.
In 2006, St James Power Station was given a new lease of life as a nightlife complex, thanks to Mapletree, EK Holdings, FJ Benjamin, and local entrepreneur and nightlife veteran Dennis Foo.
According to NLB, the transformation cost about S$40 million, half of which was invested by Mapletree primarily on conservation, and the other S$20 million from the rest of the investors on interiors and furnishings.
The revamped St James Power Station was used for all sorts of electrifying acts, and saw concerts by Taiwanese boyband Fahrenheit, K-pop star Jay Park and local singer JJ Lin.
Acrobats and trapeze acts were a regular feature of the nightlife complex.
Here’s a photo of Prime Minister Lee Hsien Loong at St James Power Station at the launch of a Chinese media-learning web portal.
In 2009, the National Heritage Board (NHB) gazetted the building as a national monument, which meant that owners of the building are not allowed to alter the facade, build any extensions, or hack any walls.
However, a series of crimes saw the complex’s reputation decline.
In 2016, five men were charged for hurling Molotov cocktails at a club in St James, in a bid to set it ablaze, ST reported.
In March 2017, a 34-year-old man died after being stabbed there.
Subsequently, St James Power Station was shut down once again in 2018, after 12 years as one of Singapore’s biggest nightlife complexes.
According to ST, the premises were returned to Mapletree and restoration works began.
The complex is now set to become Dyson’s new global headquarters.
Mapletree said that the restored monument will house a Heritage Gallery in one of its chimneys to showcase its contribution to the country as a power station.
There will also be a heritage trail around the monument featuring maritime artefacts, and will be further developed in collaboration with Dyson.
Read Also:
- Singapore is getting a second Sentosa, where NTUC will build a ‘Downtown South’ – here’s what to expect
- Singapore’s Temasek just unveiled an outdoor fan that can lower temperatures by 10 deg C and cut humidity by 15%
- IMDA is reviewing its rules on display panels, which are increasingly common in public places such as HDB estates


Between 14 and 16 August 2014, a total of 113 new cases of Ebola virus disease (laboratory-confirmed, probable, and suspect cases) as well as 84 deaths were reported from Guinea, Liberia*, Nigeria, and Sierra Leone.+
The response of WHO and other partners to the Ebola Virus outbreak is continuing to grow in Guinea, Liberia, Nigeria and Sierra Leone. To reduce the likelihood that those who are infected will carry the disease outside their communities, the governments have set up quarantine zones in areas of high transmission including severely-affected cities such as Gueckedou in Guinea, Kenema and Kailahun in Sierra Leone and Foya in Liberia.
This prevents people living in these areas from moving to other parts of the country and potentially increasing EVD transmission. However, it also means that barriers to travel limit their access to food and other necessities. While preventing further transmission of EVD is crucial, it is essential that people in those zones have access to food, water, good sanitation and other basic supplies.
WHO is working with the United Nations World Food Programme (WFP) to ensure people in the quarantine zones receive regular food aid and other non-medical supplies. WFP is now scaling up its programme to distribute food to the around 1 million people living in the quarantine zones in Guinea, Liberia and Sierra Leone.
Food has been delivered to hospitalized patients and people under quarantine who are not able to leave their homes to purchase food. Providing regular food supplies is a potent means of limiting unnecessary movement.
WHO does not recommend any travel or trade restrictions be applied except in cases where individuals have been confirmed or are suspected of being infected with EVD or where individuals have had contact with cases of EVD. (Contacts do not include properly-protected health-care workers and laboratory staff.) Temporary recommendations from the Emergency Committee with regard to actions to be taken by countries can be found at:
| New (1) | Confirmed | Probable | Suspect | Totals (by Country) | |
| Guinea | |||||
| Cases | 24 | 396 | 140 | 7 | 543 |
| Deaths | 14 | 252 | 140 | 2 | 394 |
| Liberia | |||||
| Cases | 60 | 200 | 448 | 198 | 846 |
| Deaths | 68 | 183 | 205 | 93 | 481 |
| Nigeria | |||||
| Cases | 3 | 12 | 0 | 3 | 15 |
| Deaths | 0 | 4 | 0 | 0 | 4 |
| Sierra Leone | |||||
| Cases | 38 | 775 | 34 | 39 | 848 |
| Deaths | 17 | 326 | 34 | 5 | 365 |
| Totals | |||||
| Cases | 125 | 1383 | 622 | 247 | 2252 |
| Deaths | 99 | 765 | 379 | 100 | 1244 |
| (1) New cases were reported between 17 and 18 August 2014. |
The total number of cases is subject to change due to ongoing reclassification, retrospective investigation, and availability of laboratory results. Data reported in the Disease Outbreak News are based on official information reported by Ministries of Health.
* Information from Liberia, throughout this update, is from 15 August, 2014.
+ Data for Liberia was not correctly reported on 19 August. The numbers have been corrected on 21 August 2014.


Bee is a collection of lightweight interaction elements for modern web applications. It is built on top of Dart's Web UI package. It contains frequently used components like Buttons, Popovers, Overlays, Input Fields and more.
Hint: See how smooth you can scroll down, while everything behind the backdrop doesn't scroll.
Rubber duck debugging, rubber ducking,[1] and the rubber duckie test[2] are informal terms used in software engineering to refer to a method of debugging code. The name is a reference to a story in the book The Pragmatic Programmer in which a programmer would carry around a rubber duck and debug his code by forcing himself to explain it, line-by-line, to the duck.[3]
Many programmers have had the experience of explaining a programming problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent.[4] By using an inanimate object, such as a rubber duck, the programmer can try to accomplish this without having to involve another person.
This concept is also known as "Talk to the Bear", dating from Kernighan's 1999 book The Practice of Programming.[5]
In Information Systems design and theory Single Source Of Truth (SSOT) refers to the practice of structuring information models and associated schemata such that every data element is stored exactly once (e.g., in no more than a single row of a single table). Any possible linkages to this data element (possibly in other areas of the relational schema or even in distant federated databases) are by reference only. Thus, when any such data element is updated, this update propagates to the enterprise at large, without the possibility of a duplicate value somewhere in the distant enterprise not being updated (because there would be no duplicate values that needed updating).[citation needed]
Deployment of an SSOT architecture is becoming increasingly important in enterprise settings where incorrectly linked duplicate or de-normalized data elements (a direct consequence of intentional or unintentional denormalization of any explicit data model) poses a risk for retrieval of outdated, and therefore incorrect, information. A common example would be the electronic health record, where it is imperative to accurately validate patient identity against a single referential repository, which serves as the SSOT. Duplicate representations of data within the enterprise would be implemented by the use of pointers rather than duplicate database tables, rows, or cells. This ensures that data updates to elements in the authoritative location are comprehensively distributed to all federated database constituencies in the larger overall enterprise architecture.[citation needed]
SSOT systems provide data that is authentic, relevant, and referable.[1]
Source: Wikipedia
Bee is a collection of lightweight interaction elements for modern web applications. It is built on top of Dart's Web UI package. It contains frequently used components like Buttons, Popovers, Overlays, Input Fields and more.


Create Job Vacancy
Job information
vacancy ID
Company Name
Vacancy Name
Company name is required
Job Description is required
Browse
File upload is required!
Create vacancy


About AVRsack
AVRsack is an integrated development environment for the Atmel AVR series of microcontrollers.
It is designed to be an alternative for the Arduino 1.0.x application, offering:
- A more powerful text editor with a variety of styles.
- A more powerful build system with incremental rebuilds.
- A more powerful upload system with finer grained control over logging.
- Full build/upload logs without arbitrary size restrictions.
- Support for handling multiple simultaneous serial ports.
- Support for assembly programming and disassembly of object code.
- Support for alternate AVR toolchains, such as Crosspack-AVR
AVRsack was written and designed by Matthias Neeracher
<EMAIL_ADDRESS>For editing text, AVRsack relies on Michael Robinson's ACEView,
a Cocoa wrapper for the Ace code editor.


ShadowHandUtilityLibrary
Main Page
Namespaces
Classes
Files
Class List
Class Index
Class Hierarchy
Class Members
Class Hierarchy
Go to the textual class hierarchy
Generated by
1.8.11


Keown urges Arsenal to consider Pochettino swoop
by BeSoccerMauricio Pochettino would help Arsenal "take a step forward", says Martin Keown, who wants his former club to consider the ex-Spurs boss.
Arsenal should weigh up an audacious move for former Tottenham boss Mauricio Pochettino, according to ex-Gunners defender Martin Keown.
Spurs acted swiftly to replace Pochettino, sacking their manager after five years at the helm on Tuesday before appointing Jose Mourinho.
While Mourinho's previous spells in charge of Chelsea look likely to make him a divisive figure among the Tottenham faithful during the early stages of his reign, Pochettino opting to switch allegiance in north London would cause a whole other kind of ructions.
Gunners head coach Unai Emery has come under increasing scrutiny amid a mixed start to the season and, although Keown does not want any rash decisions on the former Sevilla and Paris Saint-Germain tactician's future, he feels the Arsenal board should be duly aware of unexpectedly changing circumstances.
"There's no need to panic at Arsenal, we are getting close to panic by the way, because we're not having the best of seasons," he told the Daily Mail.
"But the powers that be at the top of the club should be seriously considering Pochettino.
Featured links
- BREAKING NEWS: Mourinho replaces Pochettino at Tottenham
- The latest football transfers news and rumours
- Wales, golf, Madrid... in that order
- Luis Enrique returns to Spain national team
"I have a lot of admiration for what he did at Tottenham, the way he nurtured those young players and he didn't spend a great deal of money."
He added: "I would have stayed with Pochettino. I think he deserved that. I think it's a hugely significant sacking. You're going to have managers now looking over their shoulders.
"I know the poor record he has recently, but I still would have given him another chance. I don't like the way Tottenham have done it.
"There will be a lot of chairmen looking at him now. Manchester United wanted him this time last year. I think Arsenal would have to be interested if they want to take a step forward."
Mourinho cut a contented figure on his first day as Spurs head coach on Wednesday and Keown believes the embattled figure from his final days in charge of Manchester United must be consigned to the past.
"He lost the dressing room and fell out of love with the game of football in his quest to be successful," the former England international said. "He has to jettison that part of himself."


{% extends "../Layout/layout.html" %} {% block content %} Haskell Foundation presents… Matchmaker: Find your open-soulmate <💜> Maintainer? Broadcast your calls to potential contributors! Register your project Contributor? Find open-source projects that need your help! Browse projects {% endblock %}
Broadcast your calls to potential contributors!
Find open-source projects that need your help!


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
| Interface Summary | |
|---|---|
| KeyValueStore<K,V> | A KeyValueStore specifies all the resources needed to surface key-value pairs from some backing store. |
| KeyValueStoreClient | A KeyValueStoreClient defines a mapping between store names and their KeyValueStore implementations via the getRequiredStores() method. |
| KeyValueStoreReader<K,V> | Allows users to read from a KeyValueStore. |
| Class Summary | |
|---|---|
| KeyValueStoreReaderFactory | Class that manages the creation of KeyValueStoreReaders associated with a set of bound KeyValueStore name--instance pairs. |
| RequiredStores | Convenient methods for assembling maps from names to KeyValueStore implementations in getRequiredStores() calls. |
| RequiredStores.StoreMap | A Map from names to KeyValueStore entries, created by RequiredStores.with(). |
Key-value store APIs.
KeyValueStore
s are used to provide MapReduce
programs and other operators processing Kiji datasets with the ability to join
datasets. One data set can be specified as a key-value store using the KeyValueStore
API. The program can use a KeyValueStoreReader to look up values associated with keys.
These keys are often driven by records of a dataset being processed by MapReduce.
KeyValueStores are read-only and generally depend on their backing store being considered immutable for the duration of the program's run.
Several KeyValueStore implementations are available in org.kiji.mapreduce.kvstore.lib
. These implementations read from a variety of file
formats, or Kiji tables.
A Kiji table processor (Mapper, Gatherer, Producer, etc.) can specify a set of
key-value stores it requires, by implementing the KeyValueStoreClient
class. You can return a set of
key-value store names and default implementations. These implementations may specify a
default directory in HDFS where they expect the data set.
Implementers of KeyValueStoreClient may find the RequiredStores
static class helpful, as it provides
convenient constructors for sets of KeyValueStore configurations of varying size.
You can override these KeyValueStore configurations when submitting a MapReduce
program; use a MapReduceJobBuilder
or related class to
specify a different KeyValueStore implementation to use at run-time using the
withStore() method.
You can also override the entire set of stores associated with a MapReduce job by using a kvstores XML file. This XML file may specify a set of store names bound to different KeyValueStore configurations.
MapReduce jobs may specify a dependency on one or more stores. The Context objects
provided as arguments to Producers and Gatherers can open stores by name; the KeyValueStoreReader
interface provides a
backing-store-independent reader API that allows them to access values by key. If you
are using MapReduce directly, you can instantiate a KeyValueStoreReaderFactory
to get access to the
KeyValueStoreReaders associated with the current job.
You can write your own KeyValueStore implementation as well; for instance, you may
want to read key-value pairs from a different file format, or look up values over a
network (e.g., in Redis, MongoDB, or elsewhere). To do so, implement the KeyValueStore
interface, and provide a related KeyValueStoreReader
implementation as well. You can use the
FileStoreHelper
object to manage files in HDFS
that should be sent to your processes via the DistributedCache.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


The objective of Pig Dice Game is to score 100 points before the opponent(s) do(es).
In each turn a player rolls a die repeatedly until either a 1 is rolled or player decides to hold and pass on the turn to its opponent.
The number player rolls is added to a temporary score. If the player rolls a 1, they lose their temporary score and turn is passed to their opponent.
If player gets any other number, they can decide to continue and roll the die.
If player decides to hold, then their turn total (temporary score) is added to the overall score.
The first player to score 100 points wins the game.
DieRoll:
TurnScore:
TotalScore:
DieRoll:
TurnScore:
TotalScore:


btCollisionAlgorithm Class Reference
#include <btCollisionAlgorithm.h>
List of all members.
Detailed Description
btCollisionAlgorithm is an collision interface that is compatible with the Broadphase and
btDispatcher. It is persistent over frames
Definition at line 55 of file btCollisionAlgorithm.h.
The documentation for this class was generated from the following files:
- C:/Users/New/Documents/Games_Technology/Year4_Semester1/ICT397/~My Work/Assignment2/ICT397Carre/CarreGameEngine/Dependencies/BulletPhysicsEngine/include/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.h
- C:/Users/New/Documents/Games_Technology/Year4_Semester1/ICT397/~My Work/Assignment2/ICT397Carre/CarreGameEngine/Dependencies/BulletPhysicsEngine/include/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp


Purchase a 30 day unlimited bundle for your prepaid cellular number.
Powered by ABSA - Brave, Passionate, Ready.
Upon payment completion, the unlimited bundle will automatically be activated. This bundle will last 30 days, there is no usage threshold nor throttling, we provide unlimited bundle access for a duration of 30 days. I don't have an ABSA account?


kf-kent-ke
You can place KentFont icons just about anywhere using the icon's
name. KentFont is designed to be used with inline elements (we like the
tag for
brevity, but using a
is more semantically correct).
 kf-kent-ke
kf-lg
kf-2x
kf-3x
kf-4x
kf-5x
To increase icon sizes relative to their container, use the kf-lg
(33% increase), kf-2x
,
kf-3x
, kf-4x
, or kf-5x
classes.
 kf-lg
 kf-2x
 kf-3x
 kf-4x
 kf-5x
Use kf-fw
to set icons at a fixed width. Great to use when different icon widths throw off alignment.
 And then one fine morning— So we beat on, boats against the current, borne back ceaselessly into the past.
Use kf-border
and pull-right
or pull-left
for easy pull quotes or
article icons.

...tomorrow we will run faster, stretch out our arms farther...
And then one fine morning— So we beat on, boats against the
current, borne back ceaselessly into the past.
Use the kf-spin
class to get any icon to rotate, and use kf-pulse
to have it rotate
with 8 steps. Works well with kf-spinner
and kf-spinner-alt
.

CSS3 animations aren't supported in IE8 - IE9.
normal
kf-rotate-90
kf-rotate-180
kf-rotate-270
kf-flip-horizontal
kf-flip-vertical
To arbitrarily rotate and flip icons, use the kf-rotate-*
and kf-flip-*
classes.
 normal

 kf-rotate-90

 kf-rotate-180

 kf-rotate-270

 kf-flip-horizontal

 icon-flip-vertical
To stack multiple icons, use the kf-stack
class on the parent, the kf-stack-1x
for the regularly sized icon, and kf-stack-2x
for the larger icon. kf-inverse
can be used as an alternative icon color. You can even throw larger icon classes on the parent
to get further control of sizing. Use kf-stack-lock
to use another icon as a "logo" for the
kf-lock
(useful for conveying a password protected area).

kf-twitter on kf-square

kf-kent-ke on kf-circle


Server Worker Cook Book
Accessing Offline Content
Recipes
Templating
Implementing read-through caching
Allowing offline Google Analytics
Allowing offline user interaction
Implementing selective caching


Earth is the third planet from the Sun and the only astronomical object known to harbour and support life. About 29.2% of Earth's surface is land consisting of continents and islands. The remaining 70.8% is covered with water, mostly by oceans, seas, gulfs, and other salt-water bodies, but also by lakes, rivers, and other freshwater, which together constitute the hydrosphere. Much of Earth's polar regions are covered in ice. Earth's outer layer is divided into several rigid tectonic plates that migrate across the surface over many millions of years, while its interior remains active with a solid iron inner core, a liquid outer core that generates Earth's magnetic field, and a convective mantle that drives plate tectonics.


Preparation time
less than 30 mins
Cooking time
30 mins to 1 hour
Serves
Serves 4
Succulent lamb cooked in a sweet, sticky, chilli sauce with a hint of fresh Thai flavours to cut through the richness.
Equipment and preparation: You will need a parisienne scoop.
Preheat the oven to 200C/400F/Gas 7.
For the chilli jam, blend all the ingredients, except the caster sugar, to a smooth purée in a food processor.
Heat the sugar in a heavy-based saucepan over a low-medium heat until it melts and forms a golden-brown caramel. Do not stir and keep an eye on it so that it doesn’t burn.
Once the sugar has caramelised, pour in the puréed chilli jam mixture and stir well. Bring the mixture to the boil, then reduce the heat and simmer for 4-5 minutes, or until sticky and jam-like. Remove from the heat and set aside to cool slightly.
For the roasted loin of lamb, heat a large oven-proof frying pan and add the oil. Once hot, add the loin, season with salt and pepper and cook until coloured on all sides. Place in the oven for 10 minutes (or longer if you prefer your meat well-cooked).
Add a couple of tablespoons of the jam to the pan and baste the meat with it. Remove from the oven, cover and leave in a warm place to rest for at least five minutes.
Meanwhile, for the pickled vegetables, place the white wine vinegar, sugar and salt, along with 110ml/3½fl oz water in a small saucepan and heat until the sugar and salt have dissolved.
Place the vegetables in a bowl and pour over the pickling liquor. Set aside for 10 minutes and then drain.
To serve, slice the lamb and place on serving plates. Add the pickled vegetables, then garnish with the mint and coriander cress. Drizzle over the chilli jam.


{% extends "toolshare/base_home.html" %} {% block title %} | List a tool {% endblock %} {% block breadcrumb %}
Register a tool in toolshare for other members to borrow.


My Phone Directory
Add Subscribers
View Subscribers
Name
Phone
Name
Phone No
Add Subscriber
Name:
Phone No:
Goback


Terms of Service
Effective June 7, 2017
Quick link: Acceptable Use Policy.
1. Your agreement with Distributed Webs Project, LLC.
1.1
Your use of the dHosting service is governed by this agreement (the "Terms"). "Distributed Webs Project, LLC." means Distributed Webs Project, LLC. Inc., and its subsidiaries or affiliates involved in providing the dHosting Service. The “dHosting Services” means the services Distributed Webs Project, LLC. makes available through this website, including this website, dHosting API, and any other software or services offered by Distributed Webs Project, LLC. in connection to any of those.
1.2
In order to use the dHosting Services, you must first agree to the Terms. You can agree to the Terms by actually using the dHosting Services. You understand and agree that Distributed Webs Project, LLC. will treat your use of the dHosting Services as acceptance of the Terms from that point onwards.
1.3
You may not use the dHosting Services if you are a person barred from receiving the dHosting Services under the laws of the United States or other countries, including the country in which you are resident or from which you use the dHosting Services. You affirm that you are over the age of 13, as the dHosting Services are not intended for children under 13.
1.4
You agree your purchases of dHosting Services are not contingent on the delivery of any future functionality or features or dependent on any oral or written public comments made by Distributed Webs Project, LLC. or any of its affiliates regarding future functionality or features.
2. Your account and use of the dHosting Services
2.1
You must provide accurate and complete registration information any time you register to use the dHosting Services. You are responsible for the security of your passwords and for any use of your account. If you become aware of any unauthorized use of your password or of your account, you agree to notify Distributed Webs Project, LLC. immediately.
2.2
Your use of the dHosting Services must comply with all applicable laws, regulations and ordinances, including any laws regarding the export of data or software.
2.3
You agree not to (a) access (or attempt to access) the administrative interface of the dHosting Services by any means other than through the interface that is provided by Distributed Webs Project, LLC. in connection with the dHosting Services, unless you have been specifically allowed to do so in a separate agreement with Distributed Webs Project, LLC., or (b) engage in any activity that interferes with or disrupts the dHosting Services (or the servers and networks which are connected to the Service).
2.4
Your account has “hard” and “soft” usage limits, as further explained here (or such URL as Distributed Webs Project, LLC. may provide). The dHosting Services does not permit you to exceed the hard usage limits. Distributed Webs Project, LLC. reserves the right to enforce soft usage limits in its sole discretion, which may result in dHosting Services serving a “quota exceeded” page to you or users to whom you serve web pages via the dHosting Services (“End Users”). Repeated exceeding of the hard or soft usage limits may lead to termination of your account.
2.5
You may use the dHosting Services only to upload, store, and serve files on the Distributed Webs Project, LLC. infrastructure. You may not access the dHosting Services for the purpose of bringing an intellectual property infringement claim against Distributed Webs Project, LLC. or for the purpose of creating a product or service competitive with the dHosting Services.
3. Service policies and privacy
3.1
You agree to comply with the dHosting Acceptable Use Policy available at acceptable use policy (the "Acceptable Use Policy") which is incorporated herein by this reference and which may be updated from time to time.
3.2
The dHosting Services shall be subject to the privacy policy for the dHosting Services available at privacy policy. You agree to the use of your data in accordance with dHosting's privacy policy.
4. Fees for use of the dHosting Services
4.1
Subject to the Terms, the dHosting Services is provided to you without charge up to certain limits. Usage over this limit requires your purchase of additional resources or services. The pricing for additional resources and services can be found at https://dhosting.io/pricing (or such URL as dHosting may provide).
4.2
For all purchased resources and services, we will charge your credit card on a monthly basis or at the interval indicated in Distributed Webs Project, LLC. fees and payment policies, if different.
4.3
Distributed Webs Project, LLC. may change its fees and payment policies for the dHosting Services by notifying you at least fifteen (30) days before the beginning of the billing cycle in which such change will take effect. Changes to the fees or payment policies will be posted on the website (or such other URL dHosting may provide from time to time). Any outstanding balance becomes immediately due and payable upon termination of the Terms for any reason.
4.4
You may not access the dHosting Services in a manner intended to avoid incurring fees.
5. Content on the dHosting Services and Take Down Obligations
5.1
You understand that all information (such as data files, written text, computer software, music, audio files or other sounds, photographs, videos or other images) to which you may have access as part of, or through your use of, the dHosting Services are the sole responsibility of the person from which such content originated. All such information is referred to below as the "Content."
5.2
Distributed Webs Project, LLC. reserves the right (but shall have no obligation) to remove any or all Content from the dHosting Services. You agree to immediately take down any Content that violates the Acceptable Use Policy, including pursuant to a take down request from Distributed Webs Project, LLC.. In the event that you elect not to comply with a request from Distributed Webs Project, LLC. to take down certain Content, Distributed Webs Project, LLC. reserves the right to directly take down such Content.
5.3
You agree that you are solely responsible for (and that Distributed Webs Project, LLC. has no responsibility to you or to any third party for) any Content that you create, transmit or display while using the dHosting Services and for the consequences of your actions (including any loss or damage which Distributed Webs Project, LLC. may suffer) by doing so.
5.4
You agree that Distributed Webs Project, LLC. has no responsibility or liability for the deletion or failure to store any Content and other communications maintained or transmitted through use of the Service. You further acknowledge that you are solely responsible for securing and backing up your Content.
6. Proprietary rights
6.1
You acknowledge and agree that Distributed Webs Project, LLC. (or Distributed Webs Project, LLC.'s licensors) own all legal right, title and interest in and to the dHosting Services, including any intellectual property rights which subsist in the dHosting Services (whether those rights happen to be registered or not, and wherever in the world those rights may exist).
6.2
Except as provided in Section 8, Distributed Webs Project, LLC. acknowledges and agrees that it obtains no right, title or interest from you (or your licensors) under these Terms in or to any Content that you create, submit, post, transmit or display on, or through, the dHosting Services, including any intellectual property rights which subsist in that Content (whether those rights happen to be registered or not, and wherever in the world those rights may exist). Unless you have agreed otherwise in writing with Distributed Webs Project, LLC., you agree that you are responsible for protecting and enforcing those rights and that Distributed Webs Project, LLC. has no obligation to do so on your behalf.
7.  This license is for the sole purpose of enabling you to use and enjoy the benefit of the dHosting Services as provided by Distributed Webs Project, LLC., in the manner permitted by the Terms.
7.2
You may not (and you may not permit anyone else to): (a) copy, modify, create a derivative work of, reverse engineer, decompile or otherwise attempt to extract the source code of the dHosting Services or any part thereof, unless this is expressly permitted or required by law, or unless you have been specifically told that you may do so by Distributed Webs Project, LLC., in writing (e.g., through an open source software license); or (b) attempt to disable or circumvent any security mechanisms used by the dHosting Services or any applications running on the dHosting Services.
7.3
Open source software licenses for components of the dHosting Services released under an open source license constitute separate written agreements. To the limited extent that the open source software licenses expressly supersede these Terms, the open source licenses govern your agreement with Distributed Webs Project, LLC. for the use of the components of the dHosting Services released under an open source license.
8. License from You
8.1
Distributed Webs Project, LLC. claims no ownership or control over any Content. You retain copyright and any other rights you already hold in the Content, and you are responsible for protecting those rights, as appropriate. By submitting, posting or displaying the Content on or through the dHosting Services you give Distributed Webs Project, LLC. a worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute such Content for the sole purpose of enabling Distributed Webs Project, LLC. to provide you with the dHosting Services.
8.2
You may choose to or we may invite you to submit comments or ideas about the dHosting Services, including without limitation about how to improve the dHosting Services or our products (“Ideas”). By submitting any Idea, you agree that your disclosure is gratuitous, unsolicited and without restriction and will not place Distributed Webs Project, LLC. under any fiduciary or other obligation, and that we are free to use the Idea without any additional compensation to you, and/or to disclose the Idea on a non-confidential basis or otherwise to anyone.
8.3
You agree that Distributed Webs Project, LLC., in its sole discretion, may use your trade names, trademarks, service marks, logos, domain names and other distinctive brand features in presentations, marketing materials, customer lists, financial reports and Web site listings (including links to your website) for the purpose of advertising or publicizing your use of the dHosting Services.
9. Modification and termination of the dHosting Services
9.1
Distributed Webs Project, LLC. is constantly innovating in order to provide the best possible experience for its users. You acknowledge and agree that the form and nature of the dHosting Services which Distributed Webs Project, LLC. provides may change from time to time without prior notice to you, subject to the terms in Section 4.3. Changes to the form and nature of the dHosting Services will be effective with respect to all versions of the dHosting Services; examples of changes to the form and nature of the dHosting Services include without limitation changes to fee and payment policies, security patches, added functionality, and other enhancements.
9.2
You may terminate these Terms at any time by canceling your account on the dHosting Services. You will not receive any refunds if you cancel your account.
9.3
You agree that Distributed Webs Project, LLC., in its sole discretion and for any or no reason, may terminate your account or any part thereof. You agree that any termination of your access to the dHosting Services may be without prior notice, and you agree that Distributed Webs Project, LLC. will not be liable to you or any third party for such termination.
9.4
You are solely responsible for exporting your Content from the dHosting Services prior to termination of your account for any reason, provided that if we terminate your account, we will provide you a reasonable opportunity to retrieve your Content.
9.5
Upon any termination of the dHosting Services or your account these Terms will also terminate, but Sections 6.1, 11, 12, 13, 14, and 18 shall continue to be effective after these Terms are terminated.
10.

11.  THIS SHALL INCLUDE, BUT NOT BE LIMITED TO, ANY LOSS OF PROFIT (WHETHER INCURRED DIRECTLY OR INDIRECTLY), ANY LOSS OF GOODWILL OR BUSINESS REPUTATION, ANY LOSS OF DATA SUFFERED, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR OTHER INTANGIBLE LOSS.
11.2
THE LIMITATIONS ON purple LINK LABS'S LIABILITY TO YOU IN PARAGRAPH 11.1 ABOVE SHALL APPLY WHETHER OR NOT purple LINK LABS HAS BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.
12. Indemnification
12.1
You agree to hold harmless and indemnify Distributed Webs Project, LLC., and its subsidiaries, affiliates, officers, agents, employees, advertisers, licensors, suppliers or partners (collectively "Distributed Webs Project, LLC. and Partners") from and against any third party claim arising from or in any way related to (a) your breach of the Terms, (b) your use of the dHosting Services, (c) your violation of applicable laws, rules or regulations in connection with the dHosting Services, or (d) your Content, including any liability or expense arising from all claims, losses, damages (actual and consequential), suits, judgments, litigation costs and attorneys' fees, of every kind and nature. In such a case, Distributed Webs Project, LLC. will provide you with written notice of such claim, suit or action.
13. Copyright policy
13.1
You agree to set up a process to respond to notices of alleged infringement that comply with the United States' Digital Millennium Copyright Act ("DMCA notices"). It is Distributed Webs Project, LLC.' policy to respond to DMCA notices or other applicable copyright laws and to terminate the accounts of repeat infringers. We reserve the right to take down your Content upon receipt of a valid DMCA notice.
14. Other content
14.1
The dHosting Services may include hyperlinks to other web sites or content or resources or email content. Distributed Webs Project, LLC. may have no control over any web sites or resources which are provided by companies or persons other than Distributed Webs Project, LLC..
14.2
You acknowledge and agree that Distributed Webs Project, LLC. is not responsible for the availability of any such external sites or resources, and does not endorse any advertising, products or other materials on or available from such web sites or resources.
14.3
You acknowledge and agree that Distributed Webs Project, LLC. is not liable for any loss or damage which may be incurred by you or your End Users as a result of the availability of those external sites or resources, or as a result of any reliance placed by you on the completeness, accuracy or existence of any advertising, products or other materials on, or available from, such web sites or resources.
15. Changes to the Terms
15.1
Distributed Webs Project, LLC. may make changes to the Terms from time to time. If we change the Terms in any substantive way, we will give you at least seven (7) days notice before the changes take effect, during which period of time you may reject the changes by terminating your account.
15.2
You understand and agree that if you use the dHosting Services after the date on which the Terms have changed, Distributed Webs Project, LLC. will treat your use as acceptance of the updated Terms.
16. General legal terms
16.1
The Terms constitute the whole legal agreement between you and Distributed Webs Project, LLC. and govern your use of the dHosting Services (but excluding any services which Distributed Webs Project, LLC. may provide to you under a separate written agreement), and completely replace any prior agreements between you and Distributed Webs Project, LLC. in relation to the dHosting Services.
16.2
There are no third party beneficiaries to these Terms. The parties are independent contractors, and nothing in these Terms creates an agency, partnership or joint venture.
16.3
If dHosting provides you with a translation of the English language version of these Terms, the English language version of these Terms will control if there is any conflict.
16.4
You agree that Distributed Webs Project, LLC. may provide you with notices, including those regarding changes to the Terms, by email, regular mail, or postings on the dHosting Services. By providing Distributed Webs Project, LLC. your email address, you consent to our using the email address to send you any notices required by law in lieu of communication by postal mail.
16.5
You agree that if Distributed Webs Project, LLC. does not exercise or enforce any legal right or remedy which is contained in the Terms (or which Distributed Webs Project, LLC. has the benefit of under any applicable law), this will not be taken to be a formal waiver of Distributed Webs Project, LLC.' rights and that those rights or remedies will still be available to Distributed Webs Project, LLC..
16.6
Distributed Webs Project, LLC. shall not be liable for failing or delaying performance of its obligations resulting from any condition beyond its reasonable control, including but not limited to, governmental action, acts of terrorism, earthquake, fire, flood or other acts of God, labor conditions, power failures, and Internet disturbances.
16.7
The Terms, and your relationship with Distributed Webs Project, LLC. under the Terms, shall be governed by the laws of the State of Deleware without regard to its conflict of laws provisions. You and Distributed Webs Project, LLC. agree to submit to the exclusive jurisdiction of the courts located within the the state of Deleware to resolve any legal matter arising from the Terms.
16.8
Neither party may assign any of its rights or obligations under these Terms, whether by operation of law or otherwise, without the prior written consent of the other party (not to be unreasonably withheld). Notwithstanding the foregoing, either party may assign the entirety of its rights and obligations under these Terms, without consent of the other party, to its affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets not involving a direct competitor of the other party. A party’s sole remedy for any purported assignment by the other party in breach of this paragraph shall be, at the non-assigning party’s election, termination of your use of the dHosting Services upon written notice to the assigning party.
This document is an adaptation of the Heroku Terms of Service. The original work has been modified. Heroku, Inc. is not connection with and does not sponsor or endorse dHosting or its use of the work.


content pushed from $scope
Value is a string, child scope's version will not overwrite parent's, child scope now has an identical property name (firstName) but no update capability
Value becomes a property in an object shared between the ngModel directive and parent controller
Parent controller populates ngRepeat's array
Names on the list
ngModelController provides built in user input validation, powered by the $digest cycle and fed by the $parsers array. $parsers contains all built in validator methods and any custom validators (in the form of a directive) we added to the $parsers array


 Please upload one now.
{% else %} {% endif %}Or, upload your avatar here:


#include <PxVehicleComponents.h>
|
| PxReal | mLatStiffX |
| | Tire lateral stiffness is a graph of tire load that has linear behavior near zero load and flattens at large loads. mLatStiffX describes the minimum normalized load (load/restLoad) that gives a flat lateral stiffness response to load. More...
|
| |
| PxReal | mLatStiffY |
| | Tire lateral stiffness is a graph of tire load that has linear behavior near zero load and flattens at large loads. mLatStiffY describes the maximum possible value of lateralStiffness/restLoad that occurs when (load/restLoad)>= mLatStiffX. More...
|
| |
| PxReal | mLongitudinalStiffnessPerUnitGravity |
| | Tire Longitudinal stiffness per unit gravitational acceleration. More...
|
| |
| PxReal | mCamberStiffnessPerUnitGravity |
| | tire Tire camber stiffness per unity gravitational acceleration. More...
|
| |
| PxReal | mFrictionVsSlipGraph [3][2] |
| | Graph of friction vs longitudinal slip with 3 points. More...
|
| |
| PxU32 | mType |
| | Tire type denoting slicks, wets, snow, winter, summer, all-terrain, mud etc. More...
|
| |
◆ PxVehicleTireData()
| PxVehicleTireData::PxVehicleTireData |
( |
| ) |
|
|
inline |
◆ getFrictionVsSlipGraphRecipx1Minusx0()
| PX_FORCE_INLINE PxReal PxVehicleTireData::getFrictionVsSlipGraphRecipx1Minusx0 |
( |
| ) |
const |
|
inline |
◆ getFrictionVsSlipGraphRecipx2Minusx1()
| PX_FORCE_INLINE PxReal PxVehicleTireData::getFrictionVsSlipGraphRecipx2Minusx1 |
( |
| ) |
const |
|
inline |
◆ getRecipLongitudinalStiffnessPerUnitGravity()
| PX_FORCE_INLINE PxReal PxVehicleTireData::getRecipLongitudinalStiffnessPerUnitGravity |
( |
| ) |
const |
|
inline |
◆ isValid()
| bool PxVehicleTireData::isValid |
( |
| ) |
const |
|
private |
◆ PxVehicleWheels4SimData
| friend class PxVehicleWheels4SimData |
|
friend |
◆ mCamberStiffnessPerUnitGravity
| PxReal PxVehicleTireData::mCamberStiffnessPerUnitGravity |
tire Tire camber stiffness per unity gravitational acceleration.
- Note
- Camber stiffness of the tire is calculated as gravitationalAcceleration*mCamberStiffnessPerUnitGravity
-
Camber force can be approximated as gravitationalAcceleration*mCamberStiffnessPerUnitGravity*camberAngle.
-
Specified in kilograms per radian.
Range: [0, PX_MAX_F32)
◆ mFrictionVsSlipGraph
| PxReal PxVehicleTireData::mFrictionVsSlipGraph[3][2] |
Graph of friction vs longitudinal slip with 3 points.
- Note
- mFrictionVsSlipGraph[0][0] is always zero.
-
mFrictionVsSlipGraph[0][1] is the friction available at zero longitudinal slip.
-
mFrictionVsSlipGraph[1][0] is the value of longitudinal slip with maximum friction.
-
mFrictionVsSlipGraph[1][1] is the maximum friction.
-
mFrictionVsSlipGraph[2][0] is the end point of the graph.
-
mFrictionVsSlipGraph[2][1] is the value of friction for slips greater than mFrictionVsSlipGraph[2][0].
-
The friction value computed from the friction vs longitudinal slip graph is used to scale the friction value for the combination of material and tire type (PxVehicleDrivableSurfaceToTireFrictionPairs).
-
mFrictionVsSlipGraph[2][0] > mFrictionVsSlipGraph[1][0] > mFrictionVsSlipGraph[0][0]
-
mFrictionVsSlipGraph[1][1] is typically greater than mFrictionVsSlipGraph[0][1]
-
mFrictionVsSlipGraph[2][1] is typically smaller than mFrictionVsSlipGraph[1][1]
-
longitudinal slips > mFrictionVsSlipGraph[2][0] use friction multiplier mFrictionVsSlipGraph[2][1]
-
The final friction value used by the tire model is the value returned by PxVehicleDrivableSurfaceToTireFrictionPairs multiplied by the value computed from mFrictionVsSlipGraph.
- See also
- PxVehicleDrivableSurfaceToTireFrictionPairs, PxVehicleComputeTireForce
Range: [0, PX_MAX_F32)
◆ mFrictionVsSlipGraphRecipx1Minusx0
| PxReal PxVehicleTireData::mFrictionVsSlipGraphRecipx1Minusx0 |
|
private |
◆ mFrictionVsSlipGraphRecipx2Minusx1
| PxReal PxVehicleTireData::mFrictionVsSlipGraphRecipx2Minusx1 |
|
private |
◆ mLatStiffX
| PxReal PxVehicleTireData::mLatStiffX |
Tire lateral stiffness is a graph of tire load that has linear behavior near zero load and flattens at large loads. mLatStiffX describes the minimum normalized load (load/restLoad) that gives a flat lateral stiffness response to load.
Range: [0, PX_MAX_F32)
◆ mLatStiffY
| PxReal PxVehicleTireData::mLatStiffY |
Tire lateral stiffness is a graph of tire load that has linear behavior near zero load and flattens at large loads. mLatStiffY describes the maximum possible value of lateralStiffness/restLoad that occurs when (load/restLoad)>= mLatStiffX.
- Note
- If load/restLoad is greater than mLatStiffX then the lateral stiffness is mLatStiffY*restLoad.
-
If load/restLoad is less than mLatStiffX then the lateral stiffness is mLastStiffY*(load/mLatStiffX)
-
Lateral force can be approximated as lateralStiffness * lateralSlip.
-
Specified in per radian.
Range: [0, PX_MAX_F32)
◆ mLongitudinalStiffnessPerUnitGravity
| PxReal PxVehicleTireData::mLongitudinalStiffnessPerUnitGravity |
Tire Longitudinal stiffness per unit gravitational acceleration.
- Note
- Longitudinal stiffness of the tire is calculated as gravitationalAcceleration*mLongitudinalStiffnessPerUnitGravity.
-
Longitudinal force can be approximated as gravitationalAcceleration*mLongitudinalStiffnessPerUnitGravity*longitudinalSlip.
-
Specified in kilograms per radian.
Range: [0, PX_MAX_F32)
◆ mPad
| PxReal PxVehicleTireData::mPad[2] |
|
private |
◆ mRecipLongitudinalStiffnessPerUnitGravity
| PxReal PxVehicleTireData::mRecipLongitudinalStiffnessPerUnitGravity |
|
private |
◆ mType
| PxU32 PxVehicleTireData::mType |
The documentation for this class was generated from the following file:


Employment Information:
Company Name :
Company Business :
Address :
Designation :
Department :
From :
Employment Duration :
Responsibility :
Submit
Cancel


Character Customizer by GalaxHD551 - 1.0
Identity
Head
Torso
Pants
Shoes
Outfit
Accessory
Apply
Gender
Male
Female
Body type
←
Normal 01
→
Back
Hair style
←
None
→
#808080
#ff0000
#0000ff
#00ff00
#ffff00
#00ffff
Back
Top
←
None
→
Jacket
←
None
→
Back
Pants
←
None
→
Back
Shoes
←
None
→
Back
Outfit
←
None
→
Back
Accessory
←
None
→
Back
You can't be nacked !
Back


Sign in
Name is required and must be valid.
Password is required and must be valid.
Keep me signed in
login
Create an account
Having trouble?


Class: Zype::ApiClient
Constant Summary
Constants inherited from Client
Instance Attribute Summary
Attributes inherited from Client
Instance Method Summary collapse
-
#initialize(auth_method = 'api_key') ⇒ ApiClient
constructor
A new instance of ApiClient.
Methods inherited from Client
#delete, #execute, #get, #post, #put
Constructor Details
#initialize(auth_method = 'api_key') ⇒ ApiClient
Returns a new instance of ApiClient
3 4 5 6 |
# File 'lib/zype/client/api_client.rb', line 3 def initialize(auth_method = 'api_key') @headers = { 'Content-Type' => 'application/json' }.merge(authentication(auth_method)) self.class.base_uri Zype.configuration.host end |


--- sort_order: 31 tei_id: rdx_b6zxc.p.idp191395616 annotation_count: 0 images: small-thumbnail: https://readux.ecds.emory.edu/books/emory:b6zxc/pages/emory:h6tf6/mini-thumbnail/ json: https://readux.ecds.emory.edu/books/emory:b6zxc/pages/emory:h6tf6/info/ full: https://readux.ecds.emory.edu/books/emory:b6zxc/pages/emory:h6tf6/fs/ page: https://readux.ecds.emory.edu/books/emory:b6zxc/pages/emory:h6tf6/single-page/ thumbnail: https://readux.ecds.emory.edu/books/emory:b6zxc/pages/emory:h6tf6/thumbnail/ title: Page 27 number: 27 permalink: "/pages/27/" ---


4 references to GetNetworkCredential
System.Management.Automation (4)
engine\Credential.cs (1)
293
return credential.
GetNetworkCredential
();
engine\hostifaces\PowerShellProcessInstance.cs (1)
135
Net.NetworkCredential netCredential = credential.
GetNetworkCredential
();
engine\Modules\RemoteDiscoveryHelper.cs (1)
888
NetworkCredential networkCredential = credential.
GetNetworkCredential
();
engine\remoting\fanin\OutOfProcTransportManager.cs (1)
1476
_networkCredential = connectionInfo.Credential.
GetNetworkCredential
();


| | |
- calcClassOfNRUProcesses(processesClass)
- Calculates the class of the processes.
:param processesClass: a list created by NRU algorithm.
:type processesClass: list[list[int]]
- calcLRUMatrixValue(matrix)
- Calculates the process usage time.
:param matrix: a matrix created by LRU algorithm.
:type matrix: list[list[int]]
- getMinorClassNRU(processesClass)
- Get index of minor value class.
:param processesClass: a list created by NRU algorithm.
:type processesClass: list[list[int]]
:return index if minor value.
:rtype: int
- getMinorValueLRUMatrix(matrix)
- Get index of minor value (process that is the longest unused).
:param matrix: a matrix created by LRU algorithm.
:type matrix: list[list[int]]
:return index if minor value.
:rtype: int
- getSettings(file)
- This functions receives a file, process and validate information, and finally return a list with configurations to simulator.
:param file: a file open previously.
:type file: TextWrapper
:return: list with configurations
:rtype: tuple[int, list[str], list[str], list[str]]
- setValueInLRUMatrix(matrix, index)
- Set line equal to 1, and column equal to 0.
:param matrix: a matrix created by LRU algorithm.
:param index: index for line and column.
:type matrix: list[list[int]]
:type index: int
|


facebook
Email or phone
password
Facebook helps you connect and share with
the people in your life.
create an account
it's free always will be
Birth day
Day
1
2
3
Month
jan
feb
mar
Year
1999
1998
1997
Why do I need to provide my
date of birth
male
female
By clicking Sign Up, you agree to our
Terms
and that you have
read our
Data Policy
, including our
Cookie help
. You may receive
SMS raw from Facebook and can opt out at any time.
facebook


WITNESS LIST
Redistricting Committee
January 21, 2020 - 4:00 PM
Interim field hearing on 2021 redistricting
On:
Adair, Tom (Self; Tom Adair)
Albertson, Sharron (Self)
Bao, Lily (Self)
Brown, Ben (Self)
Chafin, Matthew (Self)
Colbert, Tamara (Self)
Cordina, Joseph (Self)
Crook, Donald (Self)
Depew, Sarah (Self)
Erkel, Elizabeth (Self)
Fletcher, Susan (Self)
Gagnon, Janet (Self)
Giles, Mike (Self)
Goodwin, Katherine (Asian Pacific Islander American Public Affairs Assoc.)
Hammond, Wendi (Self)
Hawthorne, Valerie (North Texas Food Bank)
Hill, Chris (Collin County)
Hodson, Paul (Self; Grassroots Gold)
Jenkins, June (Collin County NAACP)
Johnson, Abe (Collin College)
Kemp, David (Self)
Macnamara, Elisabeth (League of Women Voters of Collin County)
Maxwell, Carroll (Self)
May, Jared (Texas Legislative Council)
Midgley, Denise (Self)
Mirza, Hani (Texas Civil Rights Project)
Murphree, Cathy (Self)
Myers, John (Self)
Openshaw, Michael (Self)
Rafaty, Dylan (Self)
Reid, Mark (Self; Collin County GOP)
Stafford, John (Self)
Stark, Sharon (Self)
Taylor, Van (Self)
Valencia, Lila (State Demographer Office)
Whitt, Maggie (Self)
Registering, but not testifying:
On:
Doherty, Lauren (Self)
Hammett, Vern (Self)
1
WITNESS LIST
On:
Johnson, Wm. Randell (Self)
Moses, Fred (I will speak on behalf of Collin Trustee)
Reeves, Sue (Self)
2