Issue with non-zero start time

[dcolli23]

Description

I'm working on producing a minimum working example for the repo to get familiar with the process of running jobs. I'm using a negative concavity function simulating from 1 second to 25 seconds as in the following picture:

The problem that I'm experiencing is that the output is starting at time 0 s and going to 24 s.

Speculation on Issue

I think the problem is that the specified time start or created time range (timeStart and timeRange, respectively) aren't passed to fittingAlgorithm.trial from the fittingAlgorithm.run wrapper.

Proposal

We should pass one or both of these in to the fittingAlgorithm.trial underlying function.

[dcolli23]

This bug propagates to the underlying fittingAlgorithm.fittingAlgorithm function.

[dcolli23]

Which seems to stem from the problem that the underlying jobDicts don't incorporate the starting time.

[dcolli23]

This is really deeply rooted in the simulation function so I'm just going to have to leave this be unless I want to do lots of refactoring.