Work-in-progress document. These notes are loosely arranged and named. Take what you may. Thanks to @garciadelcast for contributing with his discoveries!
Here is a guide with personal notes to use FFmpeg and Imagemagick to automate all kinds of tricks in gif creation, video conversion, frame extraction, image processing, and more. These notes express a love for automating the automatable.
FPS=1x30
| # Install script of Caffe2 and Detectron on AWS EC2 | |
| # | |
| # Tested environment: | |
| # - AMI: Deep Learning Base AMI (Ubuntu) Version 6.0 - ami-ce3673b6 (CUDA is already installed) | |
| # - Instance: p3.2xlarge (V100 * 1) | |
| # - Caffe2: https://github.com/pytorch/pytorch/commit/731273b8d61dfa2aa8b2909f27c8810ede103952 | |
| # - Detectron: https://github.com/facebookresearch/Detectron/commit/cd447c77c96f5752d6b37761d30bbdacc86989a2 | |
| # | |
| # Usage: | |
| # Launch a fresh EC2 instance, put this script on the /home/ubuntu/, and run the following command. |
| # -*- coding: utf-8 -*- | |
| """Example Google style docstrings. | |
| This module demonstrates documentation as specified by the `Google Python | |
| Style Guide`_. Docstrings may extend over multiple lines. Sections are created | |
| with a section header and a colon followed by a block of indented text. | |
| Example: | |
| Examples can be given using either the ``Example`` or ``Examples`` | |
| sections. Sections support any reStructuredText formatting, including |
| # vim: set fileencoding=utf-8 : | |
| # | |
| # How to store and retrieve gzip-compressed objects in AWS S3 | |
| ########################################################################### | |
| # | |
| # Copyright 2015 Vince Veselosky and contributors | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
