MySum

Why would I rewrite in indicator as simple as Sum? Because my indicators are designed to be used as components, and 'Sum' is needed in others I'm writing. The storage overhead of Ninjatrader's Sum is at least 2 kilobytes. The storage overhead for JHL.Utility.Sum of n periods is n * 8 + 16 bytes.

MySum.zip

My_VMA_ATR_React_V1

Strategy:

Channel: Upper edge is VMA of High plus ATR * multiple. Lower edge is VMA of Low minus ATR * multiple.

Sell if high of prior bar was above the upper edge and high of current bar is below the upper edge. Use high of prior bar as the initial stop.
Exit using VMA of Close as a trailing stop after the first close below the VMA.

Buy if low of prior bar was below the lower edge and low of current bar is above the lower edge.
Exit using VMA of Close as a trailing stop after the first close above the VMA.

My_VMA_ATR_Breakout_V2

This was an attempt to improve the V1 strategy using an exit criteria. This uses a stop based on +/- a mulitple of ATR from the high or low.

Is it an improvement? Hard to tell... net profit decreased(with different optimal parameters), but the SQN is higher though exit efficiency is worse; between them I think I'd still trade V1.

SQN 2.52
Net $5,106
Draw $998
Max loser $496
Efficiency:
Entry 63%
Exit 44%
Settings:
ATRPercent 190
ATRPeriod 6
CMOPeriod 9
VMAPeriod 5
ExitATRPercent 340
ExitATRPeriod 10

My_VMA_ATR_Breakout_V2

My_VMA_ATR_Breakout_V1

This strategy buys or sells on a price breakout from the VMA +- a multiple of ATR.

Optimized on ES-1006 the best performance acheived is:
SQN 2.36
Net $6,162
Draw $1,103
Max loser $796

Settings were:
ATRPercent 200
ATRPeriod 8
CMOPeriod 12
VMAPeriod 5

Entry efficiency was approximately 60%, and exit efficiency was 52%. This is a stop and reverse strategy, which should benefit greatly from finding a better exit strategy.

This strategy only trades during the regular session, but should be used with extended session data for the indicator calculations.

My_VMA_ATR_Breakout_V1

Volume Weighted Moving Average

The VWMA (Volume-Weighted Moving Average) returns the volume-weighted moving average for the specified price series and period. VWMA is similar to a Simple Moving Average (SMA), but each bar of data is weighted by the bar's Volume. VWMA places more significance on the days with the largest volume and the least for the days with lowest volume for the period specified.

MyVWMA.zip

Variable Exponential Moving Average

The exponential period is modified by the value of the CMO indicator.

MyVMA.zip

Chande Momentum Oscillator

Updated 06/19/2010 to reflect refactoring of JHL.Utility from monolithic source file.

MyCMO.zip

Recent Highs & Lows

The attached indicators were created primarily to test the helper functions they use. I've been trying to understand and reimplement efficiently someone elses ADXVMA indicator. I noticed one thing it does is walk back n bars in a data series to get the high and the low for the period, and it does this on every bar.
The functions used here only have to walk previous bars when the extreme bar rolls off the back end.

MyLow.zip
MyHigh.zip

Welles Wilder's Summation Based Average

A moving average based on the Welles Wilder Summation divided by n periods. For any n, this is equivalent to the exponential moving average for 2 * n - 1 periods.

MyWellesAvg.zip

Welles Wilder's Summation

This probably isn't very useful by itself, but may be as the basis for other indicators.

MyWellesSum.zip

Delete All Snapshots For a Filesystem

zfs list -H -r -d 1 -t snapshot -o name tank/backup/machine|xargs -L 1 zfs destroy

Make 'root' a normal user

rolemod -K type=normal root

Enable Self-signed Windows Drivers

bcdedit /set testsigning on

My Granddaughter Picks Up a Frog

Installing Paravirtual DomU

virt-install --paravirt --name test --ram 2048 --noautoconsole --wait=-1 --os-type=solaris --os-variant=opensolaris --disk path=/var/local/lib/xen/images/test,sparse=true,device=disk,size=12 --location /var/local/iso/textinstall-134-x86.iso --network bridge=stub0
virsh console test (inform the installer the terminal type is xterm)

Setting VNC Server Geometry

inetadm -m svc:/application/x11/xvnc-inetd:default exec="/usr/bin/Xvnc -inetd -query localhost -once securitytypes=none -geometry 1680x1050x24"

Host-only networking

dhcpconfig -D -r SUNWfiles -p /var/local/dhcp -a 192.168.56.1 -d host.lan -h files -l 86400
dhcpconfig -N 192.168.56.0 -m 255.255.255.0 -t 192.168.56.1

Sold 4000 C @ 4.62

OpenSolaris Networking nVidia MCP67 Solved

My NIC identifies as an nVidia MCP67. The installer doesn't find a driver for it. The solution seams to be as follows...
After installation, boot to single-user mode. In grub edit:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics
change to:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS -s

Log in as root and run:
update_drv -a -i "pci10de,54c" nge
ifconfig nge0 plumb

The above gets the driver to load, but it has a strange incompitibility. On my system typing:
ifconfig nge0 ether
returns output including:
ether 11:6f:a0:1b:30:0
which is exactly backwards.

To bring the interface up I need to fix the mac address:
ifconfig nge0 ether 0:30:1b:a0:6f:11

To make this correction persistent put:
ether 0:30:1b:a0:6f:11
in /etc/hostname.nge0

Using USB to copy between Windows and Solaris, not

While OpenSolaris build 134 will automount a FAT32 usb drive, it can't seem to read it reliably. While trying to get the 'nfo' network driver installed the downloaded file had crc errors by the time I got it to the Solaris machine (which it does not have when downloaded directly on Solaris).

The windows GUI for formatting flash drives makes no reference to UDFS and defaults to Fat32. It turns out, you can format it properly from the command line:
format g: /fs:UDF

So, I expected that to be the answer, but then I couldn't manage to mount it on the Solaris side.