Skip to main content

Blog

Learn About Our Meetup

5000+ Members

MEETUPS

LEARN, CONNECT, SHARE

Join our meetup, learn, connect, share, and get to know your Toronto AI community. 

JOB POSTINGS

INDEED POSTINGS

Browse through the latest deep learning, ai, machine learning postings from Indeed for the GTA.

CONTACT

CONNECT WITH US

Are you looking to sponsor space, be a speaker, or volunteer, feel free to give us a shout.

Author: torontoai

[Research] How to Classify Graphs using Machine Learning

https://medium.com/ai%C2%B3-theory-practice-business/how-to-classify-graphs-using-machine-learning-5b0813423734

Abstract: Graph classification is a difficult problem that has drawn a lot of attention from the machine learning community over the past few years. This is mainly due to the fact that, contrarily to Euclidean vectors, the inherent complexity of graph structures can be quite hard to encode and handle for traditional classifiers. Even though kernels have been proposed in the literature, the increase in the dataset sizes has greatly limited the use of kernel methods since computation and storage of kernel matrices has become impracticable. In this article, we propose to use extended persistence diagrams to efficiently encode graph structure. More precisely, we show that using the so-called heat kernel signatures for the computation of these extended persistence diagrams allows one to quickly and efficiently summarize the graph structure. Then, we build on the recent development of neural networks for point clouds to define an architecture for (extended) persistence diagrams which is modular and easy-to-use. Finally, we demonstrate the usefulness of our approach by validating our architecture on several graph datasets, on which the obtained results are comparable to the state-of-the-art for graph classification

submitted by /u/cdossman
[link] [comments]

[D] Funny comment in GLOW TeX File

I was wondering how the GLOW paper (https://arxiv.org/abs/1807.03039) got that nice, large figure on its front page in the NeurIPS format. Thus, I downloaded the TeX source file from arXiv. I found something quite amusing in the comments of the TeX file though, on line 182 of ms.tex:

“- Add cool-looking figure of generated faces to lure the reader.”

Anybody else think this is quite funny? It is like we, as readers, are being given such a nice little treat (the figure) to initially grab our attention.

It also can serve as a reminder to sanitize your TeX source files before sharing them on arXiv.

submitted by /u/TheBillsFly
[link] [comments]

[R] Why Git and Git-LFS is not enough to solve the Machine Learning Reproducibility crisis – TowardsDataScience

[R] Why Git and Git-LFS is not enough to solve the Machine Learning Reproducibility crisis - TowardsDataScience

Keeping the data under version control with Git-LFS is a big improvement. But the lack of version control of the data files is not the entire problem.

The determining factors for the results of training a model or other activities include the following:

  • Training data — the image database or whatever data source is used in training the model
  • The scripts used in training the model
  • The libraries used by the training scripts
  • The scripts used in processing data
  • The libraries or other tools used in processing data
  • The operating system and CPU/GPU hardware
  • Production system code
  • Libraries used by production system code

Obviously the result of training a model depends on a variety of conditions. Since there are so many variables to this, it is hard to be precise, but the general problem is a lack of what’s now called Configuration Management.

DVC takes on and solves a larger slice of the machine learning reproducibility problem than does Git-LFS or several other potential solutions:

DVC workflow – code & data

Full article: Why Git and Git-LFS is not enough to solve the Machine Learning Reproducibility crisis

submitted by /u/thumbsdrivesmecrazy
[link] [comments]

[R] Google Cloud TTS – how to monitor characters already used in the free quota?

Crosspost from r/tasker

I read in this tasker document that there is a free quota in the Google Cloud TTS API. I wonder though, before creating Tasker projects that uses Say WaveNet — how will I be able to monitor the already used characters?

Also, a sub-question to confirm: does the free quota reset monthly? Thank you.

submitted by /u/MorganCheeseBurger
[link] [comments]

Succeeding by Predicting Failure: AI Startup Using Factory-Based Sensors to Avert Shutdowns

In a world reliant on the power of machines, breakdowns can be problematic, sometimes catastrophic.

A system failure at an auto manufacturer can cost up to $1.3 million an hour. An offshore oil platform going offline can waste around $3.5 million a day.

But technical failures don’t just drain money. They also risk the safety of employees, put customer relations on the line and can threaten the environment.

To counter this, many firms implement predictive maintenance programs to detect equipment flaws before damage occurs. Traditional techniques rely on installing a large number of purpose-built sensors and measuring the performance of specific machines.

But this narrow, isolated view means that larger, holistic problems are often missed or root causes aren’t addressed. And this can lead to additional, preventable breakages further down the line.

Reliability Solutions is taking a different approach. The Krakow, Poland-based startup uses deep learning to derive insights from the huge amount of data already being collected by the myriad of sensors previously installed by their clients, on premise.

A member of the NVIDIA Inception program, Reliability Solutions is one of the first companies to take this approach and is already working with some big names, including energy provider Tauron and automakers Opel and Volkswagen.

Predicting Failure Efficiently and Effectively

Predictive maintenance aims to predict when equipment failure might occur in sufficient time to take preventative measures.

Reliability Solution’s approach to predictive maintenance uses deep neural networks powered by an NVIDIA Tesla P100 GPU cluster in the data center.

“By using deep learning, we can avoid the common pain points associated with traditional predictive maintenance models — high hardware costs, high engineering costs and long lead times,” explains Mateusz Marzec, CEO of Reliability Solutions. “With the power of NVIDIA GPUs, we can train our models, using terabytes of data, in a few hours.”

One of the largest energy companies in Europe turned to Reliability Solutions to build a predictive model that could detect the failure of a fluidized bed combustion boiler. These systems burn solid fuels to create energy at lower temperatures and with reduced sulfur emissions than would otherwise be possible.

As the entire network of boilers supply approximately 50 TWh of electricity to over 5.5 million customers per year, any downtime has extensive consequences.

Reliability Solutions developed a predictive model based on 700GB of historical data collected from sensors already installed at the plant. It also utilized a full description of the events that had impacted the boiler over a three-year period, from 2013-2015. This data was used to train a series of deep neural networks on a cluster of NVIDIA GPUs.

When validated against operating data for 2016, the system predicted all of the failures with an accuracy level of 100 percent — and without any false positives. Every breakdown of the fluidized bed boiler was anticipated from between 2.5 and 17 hours before the actual breakdown took place. This would’ve given maintenance teams sufficient time to stop the malfunction, or at least minimize the damage caused.

With the predictive maintenance module now fully incorporated, the company is making yearly savings of 4 million euros.

From Predictive to Prescriptive

Reliability Solutions is now turning its attention to developing prescriptive maintenance. This enables them to not only identify what will go wrong, and when, but to suggest a recommended course of action.

This approach also applies to companies looking to optimize the performance of their machinery, rather than fix issues. In these cases, the prescriptive model can propose steps that will save companies money or reduce their CO2 emissions, for example.

Reliability Solutions is already working with one of the biggest chemical companies in central Europe to minimize resource consumption and maximize output by optimizing the configuration of their installation.

The startup built a deep neural network-based metamodel of the chemical installation and then validated the configuration in real life. They found that the metamodel had a 90 percent accuracy rate.

Using the prescriptive model, Reliability Solutions was able to reduce the company’s hydrogen consumption by more than 2 percent, which will save the company millions of euros each year.

The post Succeeding by Predicting Failure: AI Startup Using Factory-Based Sensors to Avert Shutdowns appeared first on The Official NVIDIA Blog.