This assumes you have the following repos set up:
-
local
-
origin: your fork of the project on github
-
upstream: organization's original project on github
var performers; | |
performers = {}; | |
async.parallel([ | |
function(callback) { | |
return conductor.find({}, function(err, result) { | |
performers.conductor = result; | |
return callback(err); | |
}); |
So I was reading Hacker News and decided to read the comments in the thread about H.265 being approved. Pretty close to the top was this comment about VP9, Google's future video format. I have some words of my own about it and other future formats at the bottom of this post, but what jumped out from the comment to me was this part:
Many have already implemented VP8 (which is also slightly better than h.264 at this point)
The comparison linked to back up that statement is faulty for several reasons, such as not providing the source material used (hell, he doesn't even name the source material), exact encoding settings used (no, some random profiles are not enough), not providing the resulting encodes, only providing a
# Make one of these per source directory, assumed to be a child of | |
# the common.mk directory. | |
# List the classes to be compiled here | |
CLASSES = HelloAlgo | |
# Anything you want to throw on the command line for `make run` | |
CMDLINE = 1024 100 | |
MAKEFILE_DIRECTORY := $(dir $(word 1,$(MAKEFILE_LIST))) |
// "License": Public Domain | |
// I, Mathias Panzenböck, place this file hereby into the public domain. Use it at your own risk for whatever you like. | |
// In case there are jurisdictions that don't support putting things in the public domain you can also consider it to | |
// be "dual licensed" under the BSD, MIT and Apache licenses, if you want to. This code is trivial anyway. Consider it | |
// an example on how to get the endian conversion functions on different platforms. | |
#ifndef PORTABLE_ENDIAN_H__ | |
#define PORTABLE_ENDIAN_H__ | |
#if (defined(_WIN16) || defined(_WIN32) || defined(_WIN64)) && !defined(__WINDOWS__) |
Here I'm trying to understand what happens when I run
./hello
#include
// http://en.wikipedia.org/wiki/Pairing_function | |
package main | |
import ( | |
"fmt" | |
"math" | |
) | |
func InvertedCantorPairing(z int) (int, int) { | |
w := int(math.Floor((math.Sqrt(float64(8*z+1)) - 1) / 2)) |
Here's what I did to get things working.
Yep, over at: https://developer.apple.com
You can become your own gateway in two simple steps! Here we'll show how easy it is to issue your own currency on the Stellar network.
1: A user extends trust to your gateway account for a "maximum" amount of your currency. Remember, they're trusting you'll honor whatever your currency represents when they give it back to you.
$ curl -X POST https://test.stellar.org:9002 -d '
{
"method": "submit",
--[[ | |
LSTM cell. Modified from | |
https://github.com/oxford-cs-ml-2015/practical6/blob/master/LSTM.lua | |
--]] | |
local LSTM = {} | |
-- Creates one timestep of one LSTM | |
function LSTM.lstm(opt) | |
local x = nn.Identity()() |