Go to file

Max Kannenberg 4b6700612d Add an attribute to DataPoint to record the corresponding driving behavior		2021-12-16 16:54:27 +01:00
data	Rename variables in every .jl an .yaml file	2021-12-14 14:06:56 +01:00
examples	Refactor some of the mutable structs from types.jl as Dictionaries	2021-12-16 14:39:25 +01:00
src	Add an attribute to DataPoint to record the corresponding driving behavior	2021-12-16 16:54:27 +01:00
test	fixed MinimalWorkingExample.jl with working paths	2021-12-10 18:30:08 +01:00
.gitignore	master thesis submission	2021-10-13 16:49:42 +02:00
LICENSE	master thesis submission	2021-10-13 16:49:42 +02:00
Project.toml	Add an attribute to DataPoint to record the corresponding driving behavior	2021-12-16 16:54:27 +01:00
README.md	Add an attribute to DataPoint to record the corresponding driving behavior	2021-12-16 16:54:27 +01:00
TODO.md	master thesis submission	2021-10-13 16:49:42 +02:00

README.md

TrainRun

Installation

The required julia packages are

YAML.jl
Dates.jl
DataFrames.jl
CSV.jl
Plots.jl

Review the settings.yaml file for your appropriate settings.

Minimal working example

include("../src/TrainRun.jl")
using .TrainRun

train =  "data/trains/train_freight_V90withOreConsist.yaml"
running_path = "data/paths/path_1_10km_nConst_vConst.yaml"
settings = "data/settings.yaml"

train_run = calculateDrivingDynamics(train, running_path, settings)

History

Version 0.6.1

Add an attribute to DataPoint to record the corresponding driving behavior

Add the attribute behavior to Datapoint in types.jl
Attach the corresponding behavior to data points in MovingPhases.jl
Attach the behavior "standStill" to the last data point of the driving course in OperationModes.jl
Rework Output.jl for outputting the data points' behavior

Version 0.6

Refactor some of the mutable structs from types.jl as Dictionaries

Remove the mutable structs Train, Path, PathSection, Settings and MovingSection
Create Dictionaries for train, path an settings in Input.jl
Create a Dictionary for the whole moving section in Preperation.jl and a function for copying the moving section in OperationModes.jl
Change the type of existing Dictionary keys from String to Symbol

Version 0.5.3

Rename variables in every .jl an .yaml file

Version 0.5.2

Merge fixing branches

Version 0.5.1

Rename the real world path file

Version 0.5

Refactor modules for diminishing run and tractive effort velocity pairs

Add the seperate moving phase "diminishing run" for steep ascents where a train runs with maximum tractive effort while the driving resistances are even higher
Refactor tractiveEffortArray to tractiveEffortVelocityPairs
Rename file path and folder path to directory

Version 0.4.1

Rename waypoints

rename "waypoints" to "dataPoints" and "Waypoint" to "DataPoint"

Version 0.4

Refactor and fix modules EnergySaving, OperationModes and MovingPhases

add the general used level of accuracy from v0.3 to EnergySaving and OperationModes
fix OperationModes and MovingPhases for steep ascents where a train runs with maximum tractive effort while the driving resistances are even higher

Version 0.3

Refactor module MovingPhases

extract repeatedly occuring code lines and create smaller functions (e.g. the function moveAStep)
integrate a new approach for calculating the waypoints near intersections (e.g. including an editable level of accuracy)

Version 0.2

Modules and variables were renamed.

Version 0.1

Proof of concept and master thesis submission.

Acknowledgement

This work was supervised by South Westphalia University of Applied Sciences and Technical University Braunschweig.

License

ISC License (ISC)

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.