A quick dump of criteria for deciding whether your project needs a NAT and, if so, what type it should be.
graph TD
A(Do you need a NAT?) --> B
B{Do you have services in a Private Subnet that\nneed to access resources outside of the network?}
B -->|No| NotNeeded[You don't need a NAT]
B -->|Yes| C
C{Can you move those resources in a Public Subnet?} -->|Yes| PublicSubnet[Move to a Public Subnet instead] --> NotNeeded
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
This is a simple example for using snakemake to automate a basic work pipeline.
Makefiles and GNU Make are awesome for many reasons, and it's unforgivable for any scientist working with data processing pipelines to use them throughout their projects. But Makefiles, while feature-rich, are not really an ideal tool for automating complex data processing pipelines. If, by some chance, your analyses simply require you to collect different data, process them with identical procedures, collate them, and produce a plot, then sure - Makefiles will do. But in analyzing climate model output, I've found that I have to do a lot of quirky hacks to fit this sort of workflow model.
A perfect example is the analysis of hierarchical climate model output. It's quite common to run a climate model multiple times in a factorial factor, changing 2-3 parameters (say, an emissions dataset and a parameterization in the model). While you can pigeon-hole linear da
##git mergetool
In the middle file (future merged file), you can navigate between conflicts with ]c and [c.
Choose which version you want to keep with :diffget //2 or :diffget //3 (the //2 and //3 are unique identifiers for the target/master copy and the merge/branch copy file names).
:diffupdate (to remove leftover spacing issues)
:only (once you’re done reviewing all conflicts, this shows only the middle/merged file)
| " Place in ~/.vim/after/plugin/speeddating.vim | |
| " In Vim, -4 % 3 == -1. Let's return 2 instead. | |
| function! s:mod(a,b) | |
| if (a:a < 0 && a:b > 0 || a:a > 0 && a:b < 0) && a:a % a:b != 0 | |
| return (a:a % a:b) + a:b | |
| else | |
| return a:a % a:b | |
| endif | |
| endfunction |
| #!/usr/bin/python2 | |
| # Copyright (C) 2016 Sixten Bergman | |
| # License WTFPL | |
| # | |
| # This program is free software. It comes without any warranty, to the extent | |
| # permitted by applicable law. | |
| # You can redistribute it and/or modify it under the terms of the Do What The | |
| # Fuck You Want To Public License, Version 2, as published by Sam Hocevar. See |
| ### MATPLOTLIBRC FORMAT | |
| # This is a sample matplotlib configuration file - you can find a copy | |
| # of it on your system in | |
| # site-packages/matplotlib/mpl-data/matplotlibrc. If you edit it | |
| # there, please note that it will be overridden in your next install. | |
| # If you want to keep a permanent local copy that will not be | |
| # over-written, place it in HOME/.matplotlib/matplotlibrc (unix/linux | |
| # like systems) and C:\Documents and Settings\yourname\.matplotlib | |
| # (win32 systems). |
| # original XML at http://www.w3.org/Math/characters/unicode.xml | |
| # XSL for conversion: https://gist.github.com/798546 | |
| unicode_to_latex = { | |
| u"\u0020": "\\space ", | |
| u"\u0023": "\\#", | |
| u"\u0024": "\\textdollar ", | |
| u"\u0025": "\\%", | |
| u"\u0026": "\\&", |
| <?xml version="1.0" encoding="ISO-8859-1"?> | |
| <xsl:stylesheet | |
| xmlns:xsl="http://www.w3.org/1999/XSL/Transform" | |
| xmlns:xs="http://www.w3.org/2001/XMLSchema" | |
| version="1.0"> | |
| <xsl:template match="/charlist"> | |
| <xsl:text> | |
| unicode_to_latex = { | |
| </xsl:text> | |
| <xsl:for-each select="character"> |