The basic principle of robotics and AI

Image
Artificial intelligence applied to robotics development requires a different set of skills from you, the robot designer or developer. You may have made robots before. You probably have a quadcopter or a 3D printer. The familiar world of  Proportional Integral Derivative  ( PID ) controllers, sensor loops, and state machines must give way to artificial neural networks, expert systems, genetic algorithms, and searching path planners. We want a robot that does not just react to its environment as a reflex action, but has goals and intent—and can learn and adapt to the environment. We want to solve problems that would be intractable or impossible otherwise. Robotics or a robotics approach to AI—that is, is the focused learning about robotics or learning about AI? about how to apply AI tools to robotics problems, and thus is primarily an AI using robotics as an example. The tools and techniques learned will have applicability even if you don’t do robotics, but just apply AI to

Live Connection to Power BI Service

Another type of Live connection is to connect to a dataset published in Power BI service. This dataset will be treated as an SSAS instance. The dataset in Power BI service is hosted in a shared SSAS cloud environment. When you connect to it from Power BI Desktop, it is like connecting to an instance of SSAS with a Live connection.


Type caption for image (optional)


For this option, you need to be logged in to the Power BI Desktop. You will see a list of all datasets that you have Edit access on. Then you can choose one of them as illustrated. Power BI Online Training 


Type caption for image (optional)


After connecting to the dataset, you will see the Live Connection message at the bottom right-hand side of the Power BI Desktop. This method will work precisely similar to connecting to SSAS with the Live connection.


Type caption for image (optional)


Connecting to another dataset in power Bi service with Live Connection is the right approach for multi-tenancy development. one user can build the model, and another user can work on another power Bi file for the visualization part of it.
Live Connection versus DirectQuery
One of the mistakes that a lot of Power BI developers make is to consider DirectQuery and Live Connection the same.
These two types of connections are different in many aspects.
Here is a list of differences between these two types:
• DirectQuery is a connection mainly to a non-Microsoft database or analytical engines, or relational databases (such as SQL Server, Teradata, Oracle, SAP Business Warehouse, etc.). Power BI Training 
• Live Connections is a connection to three sources: SSAS tabular, SSAS multi-dimensional, and Power BI dataset.
• DirectQuery for some of the data sources (such as SQL Server database) still has a limited Power Query functionality available.
• Live Connection has no Power Query features in it.
• You can create simple calculated columns in DirectQuery; these will be converted to T-SQL scripts behind the scene.
• You cannot create calculated columns in Live Connection.
• You can use Report Level measures with the ability to leverage all DAX functions in Live connection.
• In the DirectQuery mode, you can have limited measure abilities. For more complex measures, you must use the option to allow unrestricted measures in DirectQuery mode, which is not recommended, because it will slow down the performance for some expressions significantly.
• DirectQuery mode usually is slower than the Live connection.
• A Live connection is usually less flexible than the DirectQuery.
As you see. the list above explains that these two types of connections are entirely different.
Conclusion
you’ve learned about Live Connection. This type of connection is only available for three data sources: SSAS tabular, multi-dimensional, and Power BI dataset. This type of connection is much more limited than the DirectQuery because you have no access to the Power Query or relationship tab. However, the Live Connection is providing a better solution than the DirectQuery, because the ability to write DAX code is fully possible if the SSAS tabular is used as a data source. With Live Connection, you get the benefit of both worlds; because data is not stored in the Power BI, the size limitation of Import Data does not apply here, and the data size can be big.
Also, because SSAS tabular can leverage DAX, and the analytical power of Power BI is based on DAX, then the analytical engine of this solution is also very efficient. A Live Connection is faster than DirectQuery in most of the cases.
However, it is still slower than Import Data in the performance. The recommendation is to start with Import Data, and if not, then the second option would be Live Connection. If none of them can be applied, then you can choose the last option. which is DirectQuery.

Comments

Popular posts from this blog

iOS 13 Features

Data Science and Machine Learning

Data Scientist Interview Question