Eve-gnosis

Two new features this release.

First off, we've added the ability to change the time the simulation runs. This helps standardize numbers. The default sim time is 10 minutes, but can be changed by passing in the optional parameter of `run_time` in position 4.

Secondly, if a module doesn't have enough capacitor to run (it needs more than is available), we no longer apply it anyway. The module will be skipped and set to run 1 second later. This will result in more accurate numbers.

Because the `LowWaterMark` is no longer necessarily the best thing to look at for cap unstable fits, the `Stability` dict has been updated. Please note that `Time` was renamed to `LowWaterMarkTime` to better reflect what it is.


stability_dict = {
'LowWaterMarkTime': low_water_mark_elapsed_time,
'LowWaterMark': low_water_mark,
'FailedToRunModules': failed_to_run_modules,
'FailedToRunModulesTime': failed_to_run_modules_time,
'RunTime': run_time,
}


The two `LowWaterMark` attributes still reflect the _last_ low mark that was found, though with modules no running on cap unstable fits may no longer be appropriate for determining if a fit is cap stable or not. They should remain useful for cap stable fits, however.

`FailedToRunModules` simply flags whether we delayed running modules because of lack of cap. The matching time attribute shows the _first_ time we encountered this.

`RunTime` simply stores the time that was passed in to run, the matrix dict may differ slightly as we check for the run time at the end of the cycle so there may be one extra tick. We capture this in case we need an easy way to set something like X/Y axis on a graph.

Now can include modules that use 0 cap.

If a module uses 0 cap you _must_ include the cap usage of 0. If no cap amount is passed in, the module will be skipped and not applied.


module_list = []
while turret_count < turret_slots:
module_list.append(
{
'Amount': 0,
'CycleTime': cycle_time,
'DelayTime': delay_time, Stagger reps
'ShieldRepair': 487.5,
}
) 3x medium s95a scoped remote shield booster
turret_count += 1
delay_time += cycle_time / turret_slots

Can now pass in a repair amount for each module. This will add the amount repaired per tick to the matrix (if multiple reppers run during that tick, then the repair amount gets lumped together). Currently no sort of total/average/etc is done.


module_list.append(
{
'Amount': -160,
'CycleTime': 9000,
'ArmorRepair': 657.761137524,
}
) Medium Armor Repairer II


Use `ShieldRepair`, `ArmorRepair`, and `HullRepair` for the attribute names.


v2016.11.18bump2
Now handles a reactivation delay separately.


module_list = [
{
'Amount': -786,
'CycleTime': 12000,
'ReactivationDelay': 180000,
}
] Micro Jump Drive


If you pass in a module with both a reactivation delay _and_ a reload (for example, bomb launcher), we will add the _both_ of the two to the timer. Since typically reload and reactivation delay happen simultaneously, the recommendation would be to make the reload passed in the larger of the two numbers and not pass the reactivation delay at all.


reload_time = module.getModifiedItemAttr("reloadTime")
reactivation_delay = module.getModifiedItemAttr("moduleReactivationDelay")

if reload_time and reactivation_delay:
reload_time = max(reload_time, reactivation_delay)
reactivation_delay = False


We allow both to be passed in (and added) to allow for the ability to handle other scenarios in the future.

Handle when no modules are passed in, so no calcs can be run.

Now matches with package name, and hopefully pyCharm is less confused.