vanclist

#!/usr/bin/env bash

#Assuming same user name for all hosts
USER_NAME='gatling'
#Remote hosts list
HOSTS=(node1-load.some.host node2-load.some.host node3-load.some.host node4-load.some.host)
#Assuming all Gatling installation in same path (with write permissions)
GATLING_HOME=/opt/loadtest/
#No need to change this
REMOTE_REPORT_DIR=/opt/loadtest/target/gatling/

marketcalls

//Coded by Rajandran R
//Author - www.marketcalls.in
//Date : 21st FEB 2017

_SECTION_BEGIN("Open == High AND Open == Low Exploration");

DOpen = TimeFrameGetPrice( "O", inDaily, 0 ); // gives you Todays Open price. 
DHigh = TimeFrameGetPrice( "H", inDaily, 0 ); // gives you Todays High price.
DLow = TimeFrameGetPrice( "L", inDaily, 0 ); // gives you Todays High price.

wolfeidau

'use strict'

console.log('Loading function')

var aws = require('aws-sdk')
var async = require('async')
var doc = require('dynamodb-doc')
var dynamo = new doc.DynamoDB()
var s3 = new aws.S3()

BlackArbsCEO

# -*- coding: utf-8 -*-

import time
t0 = time.clock()

import pandas as pd
from pandas.tseries.offsets import BDay
import numpy as np
import datetime as dt
from copy import copy

hhcordero

Dockerized JMeter - A Distributed Load Testing Workflow

Supported Cloud Providers:

• Amazon (https://aws.amazon.com/free/)
• DigitalOcean (https://www.digitalocean.com/join/)

Images used:

• JMeter Server (https://hub.docker.com/r/hhcordero/docker-jmeter-server) aka "Slave"
• JMeter Client Non-gui (https://hub.docker.com/r/hhcordero/docker-jmeter-client) aka "Master"

marketcalls

_SECTION_BEGIN("Fisher Transform");
//SetBarsRequired(200, 0);

// Ehlers formulas
// from Ehlers, John F. Cybernetic Analysis for Stocks and Futures. Wiley. 2004. 
// Chapter 1, p. 1. Code on p. 7.

function Normalize(array, arraylen)
// Figure 1.7 on p. 7
{

mbbx6spp

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

• Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
• Atomic/related changes all in one commit is something worth striving for. Having your dev

amatellanes

/* Useful celery config.

app = Celery('tasks',
             broker='redis://localhost:6379',
             backend='redis://localhost:6379')

app.conf.update(
    CELERY_TASK_RESULT_EXPIRES=3600,
    CELERY_QUEUES=(
        Queue('default', routing_key='tasks.#'),

ruslander

    [TestFixture]
    public abstract class Given_a_clean_environment
    {
        [SetUp]
        public void Setup()
        {
            Init();
            Given();
            When();
        }

mivano

{
        "template": "logstash*",
        "settings": {
            "index.analysis.analyzer.default.stopwords": "_none_",
            "index.number_of_replicas": "1",
            "index.query.default_field": "message",
            "index.refresh_interval": "5s",
            "index.number_of_shards": "4",
            "index.store.compress.stored": "true",
            "index.analysis.analyzer.default.type": "standard",