All issues

Search results

Runs should be possible with descending mileage

Status: Open.

#87 In railtoolkit/TrainRuns.jl;

· gwehrle opened on Jan 22, 2025

·  

TrainRuns.jl 2.0

Rework calcluation of behaviour sections

Status: Open.

#86 In railtoolkit/TrainRuns.jl;

· gwehrle opened on Aug 19, 2024

Make velocity step default instead of distance

Status: Open.

#85 In railtoolkit/TrainRuns.jl;

· gwehrle opened on Aug 19, 2024

Move Github Action to a dedicated .github repo

Status: Open.

#84 In railtoolkit/TrainRuns.jl;

· kaat0 opened on Jul 10, 2024

update CONTRIBUTING.md

Status: Open.

#83 In railtoolkit/TrainRuns.jl;

· kaat0 opened on Jul 10, 2024

CI targets fail

Status: Open.

#82 In railtoolkit/TrainRuns.jl;

· kaat0 opened on Jul 3, 2024

Add documentation / possibility to use TrainRuns in Python

Status: Open.

#62 In railtoolkit/TrainRuns.jl;

· apriljunge opened on May 13, 2024

·  

TrainRuns.jl 2.0

Consider using Unitful.jl

Status: Open.

#61 In railtoolkit/TrainRuns.jl;

· apriljunge opened on May 12, 2024

·  

TrainRuns.jl 2.0

Better handling of multiple paths in one file

Status: Open.

#60 In railtoolkit/TrainRuns.jl;

· apriljunge opened on May 11, 2024

·  

TrainRuns.jl 2.0

:running_time setting could be replaced by a new function.

Status: Open.

#59 In railtoolkit/TrainRuns.jl;

· kaat0 opened on May 8, 2024

·  

TrainRuns.jl 2.0

Include a function to select a POI from a calculated trainrun.

Status: Open.

#54 In railtoolkit/TrainRuns.jl;

· kaat0 opened on May 5, 2024

·  

TrainRuns.jl 2.0

Refactor calculation to allow for different approaches

Status: Open.

#53 In railtoolkit/TrainRuns.jl;

· kaat0 opened on Apr 6, 2024

·  

TrainRuns.jl 2.0