IBM Watson Studio on Cloud Pak for Data vs. TensorFlow

It has a lot of features that are good for teams working on large-scale projects and continuously developing and reiterating their data project models. Really helpful when dealing with large data. It is a kind of one-stop solution for all data science tasks like visualization, cleaning, analyzing data, and developing models but small teams might find a lot of features unuseful.

Incentivized

1. Whenever the problem has the demand for a neural networks based solution, Tensorflow (TF) is a great fit.
2. The tf.dataset API makes it really simple to create complex data pipelines in a few lines of code.
3. tf.estimators API abstracts all the complex computation graph creation logic making it very simple to get started.
4. Eager execution makes it simple to develop a TF graph as debugging the code would be like any other imperative Python program.
5. TF abstracts all the complexities of scaling it to multiple machines. It has various code and data distribution algorithms ready to use.
6. Projects like TensorBoard make monitoring the training process really easy. It also gives the ability to view embeddings without any extra code. Their What-If is extremely useful for poking and understanding a black box model. It also has tools to visualize data to quickly check for anomalies.
7. TF Autograph aims to covert any normal Python code into a distributed program which is quite handy to scale an existing code base.

Incentivized

• Integration of IBM Watson APIs such as speech to text, image recognition, personality insights, etc.
• SPSS modeler and neural network model provide no-code environments for data scientists to build pipelines quickly.
• Enforced best-practices set up POCs for deployment in production with a minimum of re-work.
• Estimator validation lets data scientists test and prove different models.

Incentivized

• Data pipeline implementation is quite good, loading large amounts of data and pre-process it in an efficient way is no more issue for us
• It supports all major DL algorithms and network layouts such as ConvNets, RNN, LSTMs, Word2Vec, and even the latest transformer architecture
• The abstraction for the device is perfectly done and its support seamlessly for multiple GPU and even TPU will bring a lot of performance gain for enterprise scoped solution while still keep the flexibility
• The TensorBoard is amazing. I haven't seen a similar thing in other frameworks on the market. It allows us to quickly understand and debug the model with the info visualization which makes understanding much better
• A very supportive community, which is the key for sharing the ideas and find the quick and best solutions

Incentivized

• The cost is steep and so only companies with resources can afford it
• It will be nice to have Chinese versions so that Chinese engineers can also use it easily
• It takes a while to learn how to input different kinds of skin defects for detection

Incentivized

• It would be much better if they could provide good documentation and easy ways to understand concepts.
• It is difficult to understand the concept behind for example, Tensor Graph, which takes a lot of time.
• As you have to write everything, it is time consuming to write the implementation of whole neural network. It would be better if they can provide some wrapper library to make things easier.

Incentivized

because we find out that DSX results have improved our approach to the whole subject (data, models, procedures)

Incentivized

The UI flawlessly merges this offering by providing a neat, minimal, responsive interface

Incentivized

Support of multiple components and ease of development.

Incentivized

From time to time there are services unavailable, but we have been always informed before and they got back to work sooner than expected

Incentivized

Never had slow response even on our very busy network

Incentivized

I received answers mostly at once and got answered even further my question: they gave me interesting points of view and suggestion for deepening in the learning path

Incentivized

Community support for TensorFlow is great. There's a huge community that truly loves the platform and there are many examples of development in TensorFlow. Often, when a new good technique is published, there will be a TensorFlow implementation not long after. This makes it quick to ally the latest techniques from academia straight to production-grade systems. Tooling around TensorFlow is also good. TensorBoard has been such a useful tool, I can't imagine how hard it would be to debug a deep neural network gone wrong without TensorBoard.

Incentivized

The trainers on the job are very smart with solutions and very able in teaching

Incentivized

The Platform is very handy and suggests further steps according my previous interests

Incentivized

It surprised us with unpredictable case of use and brand new points of view

Incentivized

Use of cloud for better execution power is recommended.

Incentivized

The main reason I personally changed over from Azure ML Studio is because it lacked any support for significant custom modelling with packages and services such as TensorFlow, scikit-learn, Microsoft Cognitive Toolkit and Spark ML. IBM Watson Studio provides these services and does so in a well integrated and easy to use fashion making it a preferable service over the other services that I have personally used.

Incentivized

Can't seem to choose any deep learning platform in the above, so I'll list it here: 1. Apache MXNet: this has been used for one of our main algorithms for search as an end-to-end pipeline. We chose this because of the Scala bindings, which makes it easier to integrate with out JVM backend. MXNet seems comparable to TensorFlow, although community support is not as good as TensorFlow, and there are issues with memory leaks that are being worked on. TensorFlow in general is easier to use, but MXNet isn't too far behind. 2. Keras: still a favorite. Often I use this when paired with TensorFlow. TensorFlow 2.0 will make it even easier. 3. PyTorch: only used it a little, so it's hard to provide a good opinion. 4. DL4J: used it initially in an early days project because it has good JVM support. Harder to used not because of poor API design, but because community support is lacking and features don't come out as fast as TensorFlow.

Incentivized

It helped us in getting from 0 to DSX without getting lost

Incentivized

• Could instantly show data driven insights to drive 20% incremental revenue over existing results
• Still don't have a real use case for unstructured data like twitter feed
• Some of the insights around user actions have driven new projects to automate mundane tasks

Incentivized

• Positive Impact- As I mentioned before its open source. Very easy to learn for average programmer/ developer. We were able to design a POC model for understanding the patient appointment cancellation snd reasons behind it in 3 week time frame.
• Negative Impact- If you are using tensor flow for small project it works fine. If you are trying to build a model for face recognition it will be hard to program and train the system. It needs data to be processed before hand cannot learn on the go.