Jekyll2019-05-17T16:09:21+00:00https://cc-ai.github.io/CCAI - KDBClimate Change AI project at Mila's shared knowledge basevict0rschschmidtv@mila.quebecWho’s who?2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/workflow/workflow-whoswho<h1 id="whos-who">Who’s who?</h1>
<p>Learn about others, share about yourself!</p>
<p>(every field is obviously optional)</p>
<table>
<thead>
<tr>
<th style="text-align: left">Github</th>
<th style="text-align: left">Name</th>
<th style="text-align: left">Twitter / website</th>
<th style="text-align: left">Contribution</th>
<th style="text-align: left">Affiliation</th>
<th style="text-align: left">Time dedication</th>
<th style="text-align: left">Currently working on</th>
<th style="text-align: left">Interests / Other</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left">@vict0rsch</td>
<td style="text-align: left">Victor Schmidt</td>
<td style="text-align: left"><a href="https://twitter.com/vict0rsch">vict0rsch</a>, <a href="https://vict0rs.ch">vict0rs.ch</a></td>
<td style="text-align: left">ml, meta, data</td>
<td style="text-align: left">PhD @ Mila</td>
<td style="text-align: left">50-75%</td>
<td style="text-align: left">Attention Cycle GANs</td>
<td style="text-align: left">previously <a href="https://entrepreneur-interet-general.etalab.gouv.fr/defis/2018/hopkins.html">Public Interest Entrepreneur</a> in France ; built <a href="https://metada.org">metada.org</a></td>
</tr>
<tr>
<td style="text-align: left">@sashavor</td>
<td style="text-align: left">Sasha Luccioni</td>
<td style="text-align: left"><a href="https://mila.quebec/en/person/sasha-luccioni/">Mila profile</a></td>
<td style="text-align: left">ml, meta, data, behavioral</td>
<td style="text-align: left">Postdoc @ Mila</td>
<td style="text-align: left">150%</td>
<td style="text-align: left">Segmentation</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">@elenab</td>
<td style="text-align: left">Elena Busila</td>
<td style="text-align: left"><a href="https://www.linkedin.com/in/elenabusila/">LinkedIn</a></td>
<td style="text-align: left">frontend, backend, devops, tooling</td>
<td style="text-align: left">AI Developer @Element AI</td>
<td style="text-align: left">20% of my work week when possible</td>
<td style="text-align: left">Frontend</td>
<td style="text-align: left"> </td>
</tr>
</tbody>
</table>
<p>(Discuss this document in <a href="https://github.com/cc-ai/kdb/issues/39">#39</a>)</p>vict0rschschmidtv@mila.quebecWho’s who?Github at `cc-ai` : getting started 🥋2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/workflow/workflow-gettingstarted<h1 id="github-at-cc-ai--getting-started-">Github at <code class="highlighter-rouge">cc-ai</code> : getting started 🥋</h1>
<p>Hello and welcome to the CCAI GitHub!</p>
<p>In this repository, we will of course share code, but also links, articles, websites, and ideas. We will also use it for defining who does what task (i.e. ticket) and follow the progress of tickets and tasks as they evolve.</p>
<p>Don’t worry if you’ve never used GitHub before! You can actually use GitHub without knowing ANY code at all. It’s really a straightforward tool, and this document will help you cover the basics.</p>
<h2 id="git-">Git 🌵</h2>
<p>Git is a software to do version control, which means it will save any changes being done without overwriting any past work. This means that even if several people are working on the same file at the same time, each person can upload their changes to the page, and Git will save both copies. Later, they can be <b> merged </b> together without anyone losing their work. You can even go back to a previous version at any point, because Git will keep a history of every change ever made. Typically, git is used via a <a href="http://guides.beanstalkapp.com/version-control/common-git-commands.html">terminal or command line</a> and stores the versions on your computer. But GitHub allows us to store the content and versions online ; plus, it adds a user interface on top of Git, which makes it possible to download and change files from your browser or your desktop, make comments, suggest fixes, etc.</p>
<h2 id="vocabulary-">Vocabulary 🙊</h2>
<p>Some useful GitHub vocabulary (from <a href="https://readwrite.com/2013/09/30/understanding-github-a-journey-for-beginners-part-1/">this guide</a>)</p>
<p><strong>Markdown</strong>: A way to write text files so that they are rendered beautifully on Github without the hastle of using <code class="highlighter-rouge">html</code>. For instance, if you start a line with <code class="highlighter-rouge"># This is a title</code>, it will be rendered by Github as a Top-level title (as <code class="highlighter-rouge"># Github at cc-ai : getting started 🥋</code>). If you add a <code class="highlighter-rouge">#</code> it will be displayed as a secondary title (as <code class="highlighter-rouge">## Vocabulary 🙊 </code>) and so on until <code class="highlighter-rouge">###### minor title</code>. Including links is extremely easy too! <code class="highlighter-rouge">[website](https://website.com)</code> will be rendered like this: <a href="https://website.com">website</a>. These special text files have a <code class="highlighter-rouge">.md</code> extension. On GitHub if there is a <code class="highlighter-rouge">Readme.md</code> file in the current folder you’re looking into, it will be automatically rendered. If you click on a specific <code class="highlighter-rouge">.md</code> file, it will also be rendered. To see the <code class="highlighter-rouge">raw</code> text, before rendering, you can just click on the <code class="highlighter-rouge">raw</code> button (no shit…). Remember: Markdown is easy, ask for help if you’re stuck with something. In the mean time, <a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet"><strong>checkout this cheatsheet to learn in 2 minutes how to use Markdown</strong></a></p>
<p align="center"><img alt="editting a readme" src="https://media.giphy.com/media/TKifS1eBNfEud7jQuy/giphy.gif" /></p>
<p><strong>Repository or Repo</strong> : A directory or storage space where your projects can live. It can be local to a folder on your computer, or it can be a storage space on GitHub or another online host. You can keep code files, text files, image files, you name it, inside a repository.</p>
<p><strong>Commit</strong>: This is the command that gives Git its power. When you commit, you are taking a “snapshot” of your repository at that point in time, giving you a checkpoint to which you can reevaluate or restore your project to any previous state.</p>
<p><strong>Branch</strong>: How do multiple people work on a project at the same time without Git getting them confused? Usually, they “branch off” of the main project with their own versions full of changes they themselves have made. After they’re done, it’s time to “merge” that branch back with the “master,” the main directory of the project.</p>
<p><strong>Issue</strong>: Although the name may sound negative <i> (“Oh no, there’s an issue with my project!”) </i>, ‘issue’ is just the name used by GitHub for different tasks that contributors can assign to themselves. You can open an issue when you’ve defined it as something that needs to be worked on, tag it with labels depending on what it involves, and then assign it to yourself (or someone else!). A very important document that explains this workflow for the <strong>cc-ai project</strong> process can be found <a href="https://github.com/cc-ai/kdb/tree/master/workflow"><strong>here</strong></a>.</p>
<h2 id="what-we-will-use-github-for-">What we will use GitHub for 🔦</h2>
<ul>
<li>
<p><strong>Sharing code</strong> : for the coders among us, GitHub will be a way to test out different parameters, make changes to the code, clone (a.k.a.) copy other repositories that we can test, share results, etc. This will be done via the various repositories in the project, which can be seen at https://github.com/cc-ai</p>
</li>
<li>
<p><strong>Tracking progress:</strong> Even if the task that you are working on doesn’t involve coding (e.g. literature review, experimental testing, etc.), it’s useful for the rest of the team to know that you are working on a certain task (or issue), and what the progress on it is: whether it is open, closed, in progress, pending, etc. We will do this via the Kanban: https://github.com/cc-ai/kdb/projects/4</p>
</li>
<li>
<p><strong>Sharing resources:</strong> A section of the repository is dedicated specifically to sharing common resources : https://github.com/cc-ai/kdb/tree/master/resources. These can be research papres, code, news articles, tools, etc. If you encounter something useful in your literature review (or even during your spare time!), add it to the resource section!</p>
</li>
<li>
<p><strong>Sharing ideas:</strong> If you see an open ticket that is labelled as “help wanted”, or if you simply have an idea about a task that someone else is working on, don’t hesitate to leave a comment on the issue: it can help open a discussion and generate new ideas!</p>
</li>
<li>
<p><strong>Collaborating with external contributors:</strong> We are lucky enough to have a group of people interested in CCAI, who want to help us with different tasks depending on their domain of expertise: UI design, front-end development, economics.. the sky is the limit! To make this collaboration as smooth as possible, we want to give them specific tasks and ways to help us, check in with progress, ask questions, etc. GitHub is the place to do this!</p>
</li>
</ul>
<h2 id="some-brief-tutorials">Some Brief Tutorials</h2>
<h3 id="adding-a-paper-from-a-link">Adding a paper from a link</h3>
<ul>
<li>From the home page (https://github.com/cc-ai/kdb) click on <code class="highlighter-rouge">resources</code> in the top folder structure, then on <code class="highlighter-rouge">papers</code> (or the link provided): you should be at https://github.com/cc-ai/kdb/tree/master/resources/papers</li>
<li>Remember, <strong>by default, Github displays the file called <code class="highlighter-rouge">Readme.md</code></strong></li>
<li>You can edit this file and add your preferred paper by clicking on the pencil icon to the top right of the displayed Readme</li>
<li>Add a line with your paper line this <code class="highlighter-rouge">* [paper title](https:// link to paper)</code></li>
</ul>
<p align="center"><img alt="adding a link" src="https://media.giphy.com/media/co5O8kmFcr0kv6kj7M/giphy.gif" /></p>
<h3 id="adding-a-paper-from-a-pdf">Adding a paper from a pdf</h3>
<p>If you can simply add a link to this pdf, it’s better as it makes the hole repository heavier for others to sync with. But if you can’t and want to share the file, here’s how to:</p>
<ul>
<li>Host it elsewhere (Google Drive or something)</li>
<li>Host it on the repository
<ul>
<li>From the home page (https://github.com/cc-ai/kdb) click on <code class="highlighter-rouge">resources</code> in the top folder structure, then on <code class="highlighter-rouge">papers</code> (or the link provided): you should be at https://github.com/cc-ai/kdb/tree/master/resources/papers</li>
<li>Click on <code class="highlighter-rouge">Upload files</code></li>
<li>Drag and drop or <code class="highlighter-rouge">choose your files</code></li>
<li>Commit (= save)</li>
<li>Copy link to file</li>
</ul>
</li>
<li>Add the hosted file link to the <code class="highlighter-rouge">Readme.md</code> as described previously</li>
</ul>
<p align="center"><img alt="adding a pdf" src="https://media.giphy.com/media/SwmmifQOkBjdrGGzcT/giphy.gif" /></p>
<h3 id="opening-an-issue">Opening an issue</h3>
<h4 id="why">Why</h4>
<p>Remember, issues are used to track problems, open discussions about a topic or simply create a task to be done. Basic use cases include:</p>
<ul>
<li>Getting people’s opinion on a matter (like victo did for the who’s who -> <a href="https://github.com/cc-ai/kdb/issues/39">see #39</a>)</li>
<li>Signaling a bug in some code (unexpected behavior, error in execution, installation issues and so on)</li>
<li>Reminding yourself (and possibly others) about something to be done (like the example issue below -> <a href="https://github.com/cc-ai/kdb/issues/43">see #43</a> )</li>
</ul>
<h4 id="how">How</h4>
<ul>
<li>From the home page (https://github.com/cc-ai/kdb) click on <code class="highlighter-rouge">issues</code> in the top folder structure: this should bring you to https://github.com/cc-ai/kdb/issues</li>
<li>This will show you the list of currently open issues</li>
<li>You can filter the issues by <code class="highlighter-rouge">Author</code>, <code class="highlighter-rouge">Labels</code>, <code class="highlighter-rouge">Assignee</code>, or sort by date</li>
<li>To open a new issue, click on <code class="highlighter-rouge">New Issue</code>, in green at the top right of the list of open issues</li>
<li>When opening an issue, you should add: a title and a brief (one or two sentence) summary</li>
<li><strong>Don’t forget to label it with the corresponding label from the <code class="highlighter-rouge">Labels</code> dropdown list on the right</strong> (for more information about labels, read this: https://github.com/cc-ai/kdb/tree/master/workflow)</li>
<li>If you already know who will be working on the issue, add an <code class="highlighter-rouge">Assignee</code> from the list on the right. If not, you can leave it blank.</li>
</ul>
<p align="center"><img alt="adding a pdf" src="https://media.giphy.com/media/IevI50cAejhnehJ7oH/giphy.gif" /></p>
<h4 id="assigning-an-issue-to-yourself">Assigning an issue to yourself</h4>
<ul>
<li>When you have found an issue that you want to tackle, possibly opened by someone else, click on its name</li>
<li>To assign it to yourself, click <code class="highlighter-rouge">Assignees</code> on the right of the screen and select your GitHub handle from the list</li>
<li>If you want to add details or comments, use the Write section at the bottom of the page</li>
</ul>
<h4 id="closing-an-issue">Closing an issue</h4>
<ul>
<li>When the issue is solved, use the <code class="highlighter-rouge">close and comment</code> button</li>
<li>You can always re-open an issue later if the fix is not complete or the same problem arises in a new context or whatever</li>
<li>For instance, the example issue above, <a href="https://github.com/cc-ai/kdb/issues/43">#43</a>, is now closed because gifs have been added</li>
</ul>
<p><strong>Bravo! You’re all set!</strong> 💪 Now checkout <a href="https://github.com/cc-ai/kdb/tree/master/workflow#issues-and-labels-">the workflow’s guide on using cc-ai’s labels on issues</a></p>
<h2 id="getting-started-️">Getting Started ⚡️</h2>
<p>If you want to just dive in and get your hands dirty - go for it! Look at the tickets in the <a href="https://github.com/orgs/cc-ai/projects/2">Kanban</a>, choose the one that fits what you will start working on (check with Sasha or Karthik if you don’t know what to pick), and get started!</p>
<p>If you want more information about GitHub (or Git), or to learn how to use it via command line, you can check out the resources below:</p>
<p><a href="https://readwrite.com/2013/09/30/understanding-github-a-journey-for-beginners-part-1/">GitHub for beginners Part 1</a></p>
<p><a href="https://readwrite.com/2013/10/02/github-for-beginners-part-2/">GitHub for beginners Part 2</a></p>
<p><a href="https://www.edureka.co/blog/how-to-use-github/">How to Use GitHub</a></p>
<p>If you have any questions about GitHub, don’t hesitate to reach out to Sasha Luccioni (<a href="https://github.com/sashavor">@sashavor</a>) or Victor Schmidt (<a href="https://github.com/vict0rsch">@vict0rsch</a>) or simply <a href="https://github.com/cc-ai/kdb/issues/new">open an issue</a>, we’ll help you ! 👩✈️ 👨✈️</p>vict0rschschmidtv@mila.quebecGithub at cc-ai : getting started 🥋An example file to play around with markdown2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/workflow/workflow-example<h1 id="an-example-file-to-play-around-with-markdown">An example file to play around with markdown</h1>
<p><a href="https://9gag.com">9gag</a></p>vict0rschschmidtv@mila.quebecAn example file to play around with markdownWorkflow 🌊2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/workflow/workflow-Readme<h1 id="workflow-">Workflow 🌊</h1>
<h2 id="how-we-use-github-">How we use Github 🚉</h2>
<p>(New to Github ? -> <a href="/workflow/gettingstarted.md">How to get started w/ Github, cc-ai style</a>)</p>
<p>Code repositories depend on the <code class="highlighter-rouge">cc-ai</code> <em>organization</em>, managed by @vict0rsch and @sashavor.</p>
<p>There are 2 teams (mainly):</p>
<ul>
<li>The <a href="https://github.com/orgs/cc-ai/teams/core">Core Team</a> is composed of people at Mila working at least 50% of their time on this project</li>
<li>The <a href="https://github.com/orgs/cc-ai/teams/contributors">Contributors Team</a> is composed of people affiliated to other organizations and/or volunteering to spend some time on this project</li>
</ul>
<p>The organization currently has these repositories:</p>
<ul>
<li><a href="https://github.com/cc-ai/kdb">kdb</a> -> this is the main shared repo, the CC-AI Knowledge Base</li>
<li><a href="https://github.com/cc-ai/floods-frontend">floods-frontend</a> (self-explanatory)</li>
<li><a href="https://github.com/cc-ai/floods-backend">floods-backend</a> (self-explanatory)</li>
<li><a href="https://github.com/cc-ai/floods-gans">floods-gans</a> -> where we experiment with generative models to simulate floods</li>
</ul>
<p>If you’d rather have your own cc-ai repository for the task you work on, feel free to open a <img src="https://img.shields.io/badge/domain:meta-202ea5.svg" alt="" /> issue</p>
<h3 id="good-practices-">Good practices 👍</h3>
<h4 id="git-">Git 🌵</h4>
<p>Read through <a href="https://github.com/RomuloOliveira/commit-messages-guide">these commit guidelines</a> (~10 min) as they will help us work together better. A little more advanced content can be found <a href="https://www.atlassian.com/git/tutorials/merging-vs-rebasing">here - it walks you though the differences between merging and rebasing branches</a></p>
<p>Also if you like Github from the command line, checkout Github’s own tool: <a href="https://github.com/github/hub"><code class="highlighter-rouge">hub</code></a></p>
<h4 id="the-ccai-status-project-">The CCAI Status Project 🔔</h4>
<p>If you click on <code class="highlighter-rouge">Projects</code>, to the right of <code class="highlighter-rouge">Issues</code>, you’ll find the <a href="https://github.com/cc-ai/kdb/projects/4">CCAI Status project</a>. This Kanban-style project helps us track issues and tasks.</p>
<p><strong>When you create an issue</strong> add it to the <code class="highlighter-rouge">CCAI Status</code> project (to the right of the issue editting interface, below <code class="highlighter-rouge">Assignees</code> and <code class="highlighter-rouge">Labels</code>) <strong>iff</strong> it is a concrete 🔬 issue (bug, to do etc.). Please keep open discussions (as #16 or #37, <em>i.e.</em> issues with the <a href="https://github.com/cc-ai/kdb/labels/discussion"><img src="https://img.shields.io/badge/discussion-d876e3.svg" alt="" /></a> label) out of there.</p>
<p>You can always add an issue using the <code class="highlighter-rouge">+ Add card</code> button to the top right of the project’s page.</p>
<p><strong>Do update the status of issues you are assigned</strong>❗</p>
<h3 id="issues-and-labels-">Issues and Labels 💥</h3>
<p>Some guidelines to understand our <strong>issues and labels</strong></p>
<ul>
<li>
<p>Use <code class="highlighter-rouge">kdb</code>’s <a href="https://github.com/cc-ai/kdb/issues">issues</a> for general purpose issues the community should be aware or any kind of question you have</p>
<ul>
<li>If you work on a specific repository (<a href="https://github.com/cc-ai/floods-gans">floods-gans</a> for instance) use its issues for everyday tasks, but <a href="https://github.com/cc-ai/kdb/issues"><code class="highlighter-rouge">kdb</code>’s</a> for general concerns</li>
</ul>
</li>
<li>Assign people to issues (maybe yourself)</li>
<li>
<p>Use Labels!</p>
<ul>
<li>Use the <a href="https://github.com/cc-ai/kdb/labels/work%20in%20progress"><img src="https://img.shields.io/badge/work%20in%20progress-ededed.svg" alt="" /></a> label to acknowledge the issue and state you’ve started working on it</li>
<li>Use the <strong>priority</strong> tags (<a href="https://github.com/cc-ai/kdb/labels/priority%3Ahigh"><img src="https://img.shields.io/badge/priority:high-16f9c1.svg" alt="" /></a> or <a href="https://github.com/cc-ai/kdb/labels/priority%3Alow"><img src="https://img.shields.io/badge/priority:low-efff8c.svg" alt="" /></a>)</li>
<li>Label as <a href="https://github.com/cc-ai/kdb/labels/domain%3Ameta"><img src="https://img.shields.io/badge/domain:meta-202ea5.svg" alt="" /></a> issues relating to the overall CC-AI project and its management</li>
<li>Use the <a href="https://github.com/cc-ai/kdb/labels/keep%20in%20mind"><img src="https://img.shields.io/badge/keep%20in%20mind-c0cef7.svg" alt="" /></a> label to signal thoughts you’ve had which may someday be relevant</li>
<li>Even if you’re not <em>assigned</em> to an issue, if it bears the <a href="https://github.com/cc-ai/kdb/labels/good%20first%20issue"><img src="https://img.shields.io/badge/good%20first%20issue-7057ff.svg" alt="" /></a> tag you probably can still do something</li>
<li>If you’re in some kind of trouble and need people’s advice, use the <a href="https://github.com/cc-ai/kdb/labels/help%20wanted"><img src="https://img.shields.io/badge/help%20wanted-008672.svg" alt="" /></a></li>
<li>To open a discussion about anything, get people’s opinions, use the <a href="https://github.com/cc-ai/kdb/labels/discussion"><img src="https://img.shields.io/badge/discussion-d876e3.svg" alt="" /></a></li>
<li>The <a href="https://github.com/cc-ai/kdb/labels/priority%3Acritical"><img src="https://img.shields.io/badge/priority:critical-FF0000.svg" alt="" /></a> label should never be used. Except for extraordinary issues.</li>
<li>Use <code class="highlighter-rouge">domain:</code> labels for people to be able to quickly pick up what’s relevant to them. See <a href="/domains">domains</a></li>
</ul>
</li>
<li><strong>Close</strong> issues when resolved. They may be re-openned later on. You may also <strong>lock</strong> a conversation if the decision is final.</li>
<li><strong>Suggest improvements</strong> to these guidelines and practices</li>
</ul>
<h3 id="reusing-kdbs-labels-in-other-repositories-">Reusing <code class="highlighter-rouge">kdb</code>’s labels in other repositories 🏷</h3>
<p>This procedure describes how to import <code class="highlighter-rouge">kdb</code>’s labels into your repositories / other cc-ai repositories.</p>
<p><strong>This will overwrite your labels</strong> so if you want your own labels you can do this once and then delete <code class="highlighter-rouge">settings.yml</code> otherwise it will delete your repo-specific labels when pushed later on.</p>
<p>Add a <code class="highlighter-rouge">.github</code> folder and a <code class="highlighter-rouge">.github/settings.yml</code> at the repo’s root.</p>
<p><strong>If</strong> <a href="labels.yml">labels.yml</a> is up to date, copy its content into your <code class="highlighter-rouge">.github/settings.yml</code>.</p>
<p><strong>Otherwise</strong> run <a href="https://gist.github.com/Vict0rSch/188a60f1e87a68844e41082583df64c4"><strong>this script</strong></a> in your browser console on page https://github.com/cc-ai/kdb/labels and add the created file to <code class="highlighter-rouge">.github/</code>.</p>
<p>It works like this:</p>
<ol>
<li>Get <code class="highlighter-rouge">labels</code> as a list of objects with fields <code class="highlighter-rouge">name</code> <code class="highlighter-rouge">color</code> and <code class="highlighter-rouge">description</code></li>
<li>Create a <code class="highlighter-rouge">yml</code>-compatible string <code class="highlighter-rouge">out</code></li>
<li>Download <code class="highlighter-rouge">out</code> as a <code class="highlighter-rouge">settings.yml</code> file</li>
</ol>
<h2 id="slack-">Slack 📡</h2>
<p>Follow the <code class="highlighter-rouge">#git-kdb</code> channel to monitor this repo’s activity. If you’re not in our workspace, see <a href="https://github.com/cc-ai/kdb#contact-%EF%B8%8F">contact</a></p>vict0rschschmidtv@mila.quebecWorkflow 🌊Websites 🖥2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-websites-Readme<h1 id="websites-">Websites 🖥</h1>
<h2 id="environmental-inspiration">Environmental inspiration</h2>
<ul>
<li><a href="http://hazegazer.org/#m-taketour">Hazegazer</a> : Real-time analysis and visualization tool for enhanced crisis management</li>
<li><a href="https://prepdata.org/dashboards/uttarakhand-tourism#extreme-heat-days">Uttarakhand Tourism</a> : With a combination of climate data, hazard data, socioeconomic data, tourism data and climate projections, this dashboard provides insights into trends, current and future vulnerabilities of this sensitive sector.</li>
<li><a href="https://projectxglobal.com/">Project X</a> : Project X is a WWF founded corporate accelerator which helps organisations adopt sustainable innovations in their supply chains. Our focus is to help entire industries step change their sustainability performance, together.</li>
<li><a href="https://ici.radio-canada.ca/info/2019/03/neige-accumulation-hiver-quebec-environnement-meteo-gel-degel/index-fr.html">Les hivers enneigés de votre enfance ne reviendront jamais (Radio Canada)</a></li>
</ul>
<h2 id="ux-inspiration">UX inspiration</h2>
<ul>
<li><a href="https://nucleardissent.com/fallout-map">Nuclear Dissent</a></li>
<li><a href="http://www.360syria.com/">360 Syria</a> (Amnesty International)</li>
</ul>vict0rschschmidtv@mila.quebecWebsites 🖥Tools 🛠2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-tools-Readme<h1 id="tools--">Tools 🛠</h1>
<h2 id="images">Images</h2>
<ul>
<li>https://add0n.com/save-images.html (download all images in your browser’s current page)</li>
<li>https://github.com/fidler-lab/curve-gcn (Fast Interactive Object Annotation with Curve-GCN - CVPR 2019)</li>
</ul>
<h2 id="dev">Dev</h2>
<ul>
<li><a href="https://github.com/codercom/sshcode">sshcode</a> Run VS Code on any server over SSH.</li>
<li><a href="https://github.com/cool-RR/PySnooper">PySnooper</a> Never use print for debugging again</li>
<li><a href="https://github.com/tqdm/tqdm">tqdm</a> A fast, extensible progress bar for Python and CLI</li>
</ul>vict0rschschmidtv@mila.quebecTools 🛠 ImagesPapers 📜2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-papers-Readme<h1 id="papers-">Papers 📜</h1>
<p>These are the most relevant papers, do add the ones you like too!</p>
<p>We’re also building a more exhaustive list on Zotero. <a href="https://www.zotero.org/groups/2291580/ccai">Join our team</a> and share your papers there too :)</p>
<h2 id="ml">ML</h2>
<ul>
<li><a href="https://arxiv.org/pdf/1703.10593.pdf">Unpaired Image-to-Image Translation using Cycle-Consistent Adversarial Networks</a></li>
<li><a href="https://arxiv.org/abs/1806.02311">Unsupervised Attention-guided Image-to-Image Translation</a></li>
<li><a href="https://arxiv.org/abs/1903.07291">Semantic Image Synthesis with Spatially-Adaptive Normalization</a></li>
<li><a href="https://arxiv.org/abs/1802.06474">A Closed-form Solution to Photorealistic Image Stylization</a></li>
<li><a href="https://arxiv.org/abs/1805.09730">Image-to-image translation for cross-domain disentanglement</a></li>
<li><a href="https://openreview.net/pdf?id=ryxwJhC9YX">InstaGAN: Instance-aware image-to-image translation</a></li>
<li><a href="https://arxiv.org/abs/1903.07291">Semantic Image Synthesis with Spatially-Adaptive Normalization</a></li>
</ul>vict0rschschmidtv@mila.quebecPapers 📜Outreach 📣2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-outreach-Readme<h1 id="outreach-">Outreach 📣</h1>
<p>A folder to store outreach documents and presentations.</p>
<ul>
<li><a href="https://docs.google.com/document/d/1WQtugSBgMVB-i0RhgCg_qaP7WDj7aimWvpZytKTEqY4/edit">Executive Summary</a> (Yoshua Bengio and Jennifer Chayes) (01/19) (Google Doc)</li>
<li><a href="https://slides.com/vict0rsch/ccai-1#/">Slide deck</a> (Victor Schmidt) (early 02/19) (Slides.io)</li>
</ul>vict0rschschmidtv@mila.quebecOutreach 📣News 🗞2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-news-Readme<h1 id="news-">News 🗞</h1>
<ul>
<li><a href="https://www.stanforddaily.com/2019/04/09/andrew-ng-hosts-symposium-on-climate-change-ai/?fbclid=IwAR2UkUFraOJN3v-tQu8E1aoAipy8zPnK5HncsR40Vv2brdJwrIGIXs3NHJk">Andrew Ng hosts symposium on AI and climate change, invites students to bootcamp</a></li>
<li><a href="https://www.wired.com/story/weather-channel-climate-change-immersive-mixed-reality/">The Weather Channel flooded Charleston to make you give a damn</a></li>
</ul>vict0rschschmidtv@mila.quebecNews 🗞Data 💾2019-05-01T00:00:00+00:002019-05-01T00:00:00+00:00https://cc-ai.github.io/resources/resources-data-Readme<h1 id="data-">Data 💾</h1>vict0rschschmidtv@mila.quebecData 💾