implement batch mode

[colinsheppard]

definitely do this in a new branch, but please push this branch to github so I can see / play with it as work progresses:

create a new setup procedure called "setup-in-batch-mode"

• this procedure will assume that everything (all globals, drivers, etc.) starts at the exact same initial state except for the charging infrastructure which will vary from run to run
• the key purpose of this mode is to SKIP loading all of the driver data from a file (except for the first run), instead we will keep the same agents from the previous run and reset their state variables
• this will be called from the R scripts that do the batch processing
• so setup-in-batch-mode should test if there are any turtles created yet, if not then it knows this is the first run and it executes "setup"
• during setup-drivers (the existing setup version), every driver should make a copy of their itin lists (add new driver variables to do this) which will serve as the "master" version of their itins, i.e. a copy that is used to reset the working itin (which may get modified during the run). do some profiling of memory consumption with/without this addition, if the itin's represent most of the memory used by drivers, we may need to take a different approach.
• if setup-in-batch-mode finds that agents already exist, then it should do the following:
  • reset tazs (just clear drivers-in-taz)
  • reset chargers (clear current-driver, num-sessions, and energy-delivered)
  • reset drivers (see setup-drivers to see where state varaibles should begin) which should overwrite the itin lists with the master version.
• add two new functions to add/remove a single charger of a particular level from a taz, this will be used by the R script to modify the infrastructure scenario for the next model run. note that the list n-levels must be modified in addition to creating or killing the charger agent AND chargers-by-type must be recreated using the code in setup-chargers (at the end of the foreach sort tazs loop). make the commands behave like so:
  • add-charger
  • remove-charger

[colinsheppard]

do a profile to see difference in time between batch-setup first time and subsequent time

[colinsheppard]

change the setup procedure to the fix seed variant, run the model twice (in batch mode) with some outputs and verify identical results

[colinsheppard]

note that I've done some fussing with things (still unsuccessful) to get results on first and second batch run to match. one change shouldn't be considered final, instead the code to set fuel economy should probably happen in setup drivers because it uses random draws and is therefore messing up the state of the random seed. see:

https://github.com/colinsheppard/pevi/blob/batch-setup/netlogo/setup.nls#L233

[colinsheppard]

I fixed the change noted in my comment above here:

43a248d

and the following commits were the rest of my work on this issue which is now almost resolved:

e999468 6e7e777 bd495b3

[colinsheppard]

the final bit of work that needs to be done is to make it possible for the use (via R or the netlogo GUI) to fix the seed at the beginning of a batch run. don't forget that clear-all-and-initialize is called inside setup-in-batch-mode so the actual setting of the initial random seed needs to happen between this and the generation of seed-list