Showing posts with label not. Show all posts
Showing posts with label not. Show all posts

Wednesday, February 18, 2015

Google’s autonomous car gets a ‘B’ in driving test Not great but better than most of us

self driving head
Self-driving cars have come under increased scrutiny in the past week, as newly uncovered documents show that a 2012 road test for one of Google’s self-driving cars resulted in a pass very much without flying colors. The data in question come from government documents acquired through Freedom of Information laws, and show that on its Nevada driving test Google’s car had its share of small problems, and that it was never exposed to some difficult situations like railroad crossings, roundabouts, and school zones. There’s also some question as to whether Google was unfairly involved in designing the test, and that the Google team set the car’s route beforehand and specifically avoided troubling weather conditions. Additionally, at several trouble points the car decided it was incapable of proceeding safely and turned control over to its human occupants — and the irony of that limitation was simply too good for most media outlets to pass up.

Still, this latest “exposé” is not nearly as damning as some are framing it to be. To me, the interesting thing about self-driving cars is not the amount of trust that people are willing to put in self-driven vehicles, but rather the amount of trust that they are willing to put in human-driven vehicles. Most people’s reaction to driving algorithms involves questions such as, “What if there was a bug?” or, “What if you got hacked?” Such questions are best answered with a counter-question: What if your taxi driver had a seizure? What if your bus driver panicked in an unexpected situation? What if the trucker coming from the other direction simply fell asleep at the wheel?



Bear in mind that some maddeningly large portion of human drivers also don’t know how to deal with roundabouts, rail crossings, and similar situations, but that they have too much ego and self-interest to admit this fact and avoid a particular intersection. We accredit these people to drive because, a) the economy must continue to function even if most people are uncoordinated and easily distracted, and b) because we understand that licensing someone to drive is about telling whether or not they are good enough to drive. Every tiny mistake, from a missed shoulder check to an improper turning angle, could easily result in a death, so the point is not whether a driver could hypothetically make a fatal mistake, but how likely such a mistake is to occur.
Autopilot in planes, while less complex, has improved the safety of air travel.
Autopilot in planes, while less complex,
has improved the safety of air travel.

Additionally, most drivers can’t be usefully
trained how to react to things like aquaplaning or brake failure, and even if they have been trained they’ll often panic and take the wrong action. Self-driving vehicles, by contrast, can be given vicarious training on the level of a population — new research on how to handle ice can be distributed and perfectly internalized by every auto-car on the road, regardless of age. I can’t even get my grandpa to yield to buses! There seems to be something deeply welded into the human psyche, an impulse to be less fearful of dangers we understand. I can understand and empathize with my grandpa’s crusty stubbornness with regard to transit vehicles, and thus his dangerous driving is less distressing to me than the exact same behavior unconsciously executed by some faceless software construct.

When people point to the early-stage limitations of self-driving software as an attack on its chance of success, they are also making a second, more strident statement: that self-driving vehicles don’t just have problems, but that those problems are in fact more dangerous than the problems with human drivers. I don’t have to cite a glut of horrifying driving statistics to point out how absurd such an idea is, do I?  The extreme fallibility (and physical limitations) of human drivers are in fact pushing self-driving technology forward, as industry sees a chance to reduce liability; if you don’t trust the public-safety motivations of government overseers, then trust the profit incentives pushing corporations like Walmart away from accident-prone mammalian car-pilots.


A self-driving Prius much like the one that took the Nevada road test.
A self-driving Prius much like the one that took the Nevada road test
Imperfection in a self-driving system is fixable — a self-driving mistake that leads to a fatality can be used to prevent all such mistakes from happening again in the future. As such, bugs in software ought to distress us far less than similar or identical bugs in human ability. The safety of a road with even one human driver is dictated by the worst moment of the worst human driver in the area, while the safety of a totally self-driven roadway is dictated by the pinnacle of human mastery of software and multi-variable kinetics.
This test shows not that self-driving cars are as bad as a middling driver, but that they are as good as one. That’s better than any highway-driving population on Earth could ever hope to collectively deliver. Remember: it’s not about the car being better than you. It’s about you being worse than the car.
Read more »

Thursday, February 12, 2015

Drill down from one dashboard to another dashboard in Pentaho CDE Simple Example Not included any parameters

Hi Guys,

This post will teach you how you can drill down from one dashboard to another dashboard in pentaho CDE. This workout has done by one of my colleagues who is a fast learner.

You need to focus on 2 things in this post:
1) Connecting to JDBC datasource
2) Drill down from one dashboard to another dashboard.

NOTE :
Ill update you in next post about drill down from one dashboard to another dashboard using custom parameters concept.(Next work out).

Versions & Tools used for this post:
Pentaho C-Tools(CDE,CDA,CDF) 13.09 stable.
PostgreSQL DB - (foodmart database - which is one of  jasperserver default databases)
Pentaho BA server 4.8 stable.

SOURCE CODE OF THE EXAMPLE
Download the example using below link
https://drive.google.com/file/d/0BymV_QP4TGBEZ0p1cnpydDJGeDQ/edit?usp=sharing

Deployment procedure:
1) Down load the .rar file from the link(File-Download in the google drive)
2) Unzip it and place it in "pentaho-solutions" folder.
3) Refresh or clear the cache of the pentaho browser(find upper left - Browser)
4) If you are unable to find the folder name , you need to create an index.xml file (Eg: you can find it inside any folder. copy and paste it inside your working folder and change the name of it).
5) No need to restart the pentaho server.
NOTE: Edit data base connections as per your requirement also you may need to change the query if you use any other database than foodmart

Dashboard 1:
1) Layout section
* Design your lay out for dashboard1
2) Components section
* You will be placing 1 bar chart where you will click on bars for drilling down to another dashboard.
We will come back to this section again after designing Dashboard 1 and Dashboard 2
3) Data Sources section
* Click on Data source Icon on right top conrner.
* From the left .. click on SQL queries -> Click on sql over sqljdbc
* Give the name and all the properties as shown in below image.

NOTE:
PostgreSQL server default details :
Driver: org.postgresql.Driver
UserName : postgres
Password : postgres
URL:  jdbc:postgresql://localhost:6062/foodmart where 6062 is the port number which I used for postgres and foodmart is the database.
Note that default port number for postgresSQL is 5432 .

* Write a query which will suits for bars in the chart
* For eg:
SELECT
    c.country,
    c.state_province ,
    c.city,
    SUM(sf.store_sales)

FROM
    customer c,
    sales_fact_1997 sf
WHERE  c.customer_id=sf.customer_id
GROUP BY
    c.country,
    c.state_province,
    c.city

ORDER BY
c.country,c.state_province,c.city



* See the preview of the dashboard
* Out put will looks like below.

Dashboard 2 :
* Repeat the same steps as followed in Dashboard 1
* Take any component to display on the second dashboard.
* I have taken table component in this example and  the output will looks like below mentioned image.
*


We have done with 2 dashboards individually.
Now, Its the time for us to some trick on Dashboard 1 so that when we click on Dashboard 1 , it will have to take you to Dashboard2

Steps:
1) Lets go back to Dashboard 1
2) Go to the Chart component and in the properties give clickable as True
3) In the clickAction you need to give the URL of second dashboard in java script.
Eg:
function q(s,c,v)
{

window.location = http://localhost:8085/pentaho/content/pentaho-cdf-dd/Render?solution=CDE-+Exploring&path=%2FDevelopement%2FDashboard+Drill+down&file=drill_down_to_table.wcdf;

}


Thats it you have done with drill down. Save the dashboard 1 and see the preview and then click on any bar appearing , you will navigate to the 2nd dashboard.

NOTE :
This post is only giving the idea of how to drill down from one dash board to another dashboard.
This post doesnt work with any parameters. The use custom parameter with drill down from 1 dashboard to another dashboard will come in next post from my end.


URL generating problem / Path problem for Second Dashboard

How to generate the URL for 2nd dashboard ( not only for this but also works for every dashboard).?

* Right click on 2nd Dashboard and click on "Open In New Tab" the with the URL the 2nd dashboard will open in fresh tab.
* Copy that URL and paste in drill down function.
* For eg : Just reference : Find the images below
 





References :
1) http://forums.pentaho.com/showthread.php?152634-Drill-down-from-bar-chart-to-another-dashboard

2) http://forums.pentaho.com/showthread.php?82999-Drill-Down-in-DashBoards

Sadakar
("Learning never exhausts the mind")




Read more »

Tuesday, February 10, 2015

Fedora 18 and mount cifs not mounting windows share

If you are having problem mounting a window share in Fedora 18, saying "Permission Denied" just like the one below:


[root@localhost ~]# mount.cifs //192.168.0.50/customer /ian -o user=administrator
Password for administrator@//192.168.0.50/customer:  ***
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


Try this solution: (add sec=ntlm on the option)

mount.cifs //192.168.0.50/customer /ian -o user=administrator,sec=ntlm
Read more »