Log Add'l Simulation Data

Previous versions did not log what percent of WM decayed features were
item vs. context features.  Additionally, we never logged the WM traces
across trials, let alone across presentations of a trial.

Modify Trial_Simulator to log item and context features decayed in
REMplusWM.decayWMtrace function.  Additionally, store contents of WM
for each presentation on each trial.
Add Trial_Simulator Hacks (default off)

It was unclear whether some effects required EXTREME high PI condition
to manifest.  Additionally, unclear whether our results are affected by
the fact that the target is always the last item in a trial.

Add code that would append an additional number of target items on each
trial (EXTREME high PI) to EMStore.  Add code to probe target on each
lure presentation to sample target probe strength at more times.

No side effects, these hacks are turned off by default.
Fix and modify how we plot rehearsal failures

Previously parameter checking was using isinteger instead of isnumeric
to determine how to plot, but all parameters were passed in as double
and therefore we were getting blank plots for the smoothing window
parameter not equal to zero.  Additionally, plot rehearsal failure using
imagesc because it's a bit easier to visualize.

Modify isinteger check to isnumeric.  Replace plot command with imagesc.

No side effects except for how we display our data.
Extra simulation analysis scripts

Interested in looking at:
	1. mean similarity between memory traces.
	2. mean number of decayed features across a simulation
	3. number of rehearsal failures given that WM features decayed

Include:
	1. mds_EM_store.m which performs classifical multidimensional scaling
on the memory traces.
	2. get_mean_num_features_decayed.m
	3. check_WM_decay_rehearsal_effect.m which will look at the first
presentation in a trial where a feature was decayed and see if any
presentation after that contained a failed rehearsal.
Running in current matlab session on cluster

Sometimes we want to run things in the current matlab session even when
we're on the cluster - previously we only ran things in the current
matlab session if we were not on the cluster.

Add a function to PM_task.m runInCurrentMatlabEvenIfOnCluster that will
launch a script and NOT exit after it's done.  This is accomplished by
setting a shouldExitIfOnCluster variable which is checked by the family
of runSim*.m scripts.

All runSim scripts will exitIfOnCluster unless the variable
shouldExitIfOnCluster is set to false.
Clearer names for saving and running

Initially I referred to many things via EM such as EM_trial_simulation,
but this stopped making sense when we also incorporated the WM side.
Also, I had hardcoded the place to save (or load) simulation results
which doesn't generalize to other people running my script cause they
would have to change this value in many places.  Lastly, most of my
simulation result variables were called this.

Add central save location in PM_task via PM_task.SAVE_DIRECTORY
property.  Modify save and loading simulation functions to use more
appropriate variable names as well as new PM_task.SAVE_DIRECTORY
property.
Create README.md

Version 1 of the readme - will likely need to revise this.
Turn script into function (better style)

Previously the function plotLureVsTargetStrengthsAcrossTrials was a
script which assumed the existence of some variable 'this' with the
correct type.

Modify script to be function, duh.