Solve Drive Cycle (A,V,W) in Experiment #1524
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
PR Status: (Work in Progress)
This PR provides the functionality of solving the drive cycle using the experiment only if the first input of the experiment is the drive cycle.
Issues in PR:
When two consecutive drive cycles are given in the experiment, only the first one solves but the second one only returns 0 current.
If the drive cycle is not the first input of the experiment, the drive cycle part only returns 0 current.
Possible Cause of this Issue:
The driving cycles are given to the solver as interpolant. I think there is an issue with the timing of the interpolant which I am unable to overcome. For example, The US06 Drive cycle data have time range [0:600], When the drive cycle is the first input of the experiment is drive cycle (solution start time = 0), the cycle is solved successfully, but when the same cycle is repeated, (solution time > 600), the interpolant returns 0 A.
@tinosulzer and @Saransh-cpp suggestions on overcoming this issue are highly appreciated.
Fixes # (issue)
#1279
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.
Key checklist:
$ flake8
$ python run-tests.py --unit
$ cd docs
and then$ make clean; make html
You can run all three at once, using
$ python run-tests.py --quick
.Further checks: