[WIP]: Export raw trainruns data #495
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR allows experimental work with LLM - see comment (promp example) |
…netzgrafik-editor-frontend into export_raw_trainrun_data
aiAdrian
commented
Jul 24, 2025
Comment on lines
+448
to
+485
| Build agent that can process, analyze, and compare timetable data. In order to do this, data with trainruns is required. | ||
| A timetable consists of at least one or an unlimited number of trainruns. Each trainrun is described with attributes | ||
| such as Name, Frequency, Direction, and PathTime. | ||
| Name: The name indicates the train journey, which usually consists of one forward and one backward trainrun. | ||
| If a train journey only travels in one direction, then the train journey consists only of a forward trainrun. | ||
| Frequency: Each train journey has a frequency attribute that indicates how often the train runs. | ||
| For example, a frequency of 15 means that a single train departs from the starting point every 15 minutes, | ||
| resulting in 4 trains per hour. A frequency of 30 means a new train starts every half hour, | ||
| and 60 means once per hour. The trains of the train journey consist solely of a master train. | ||
| Using the frequency, all train run of a timetable can be infinitely rolled out or unfolded from the train | ||
| journey and its journeys. This leads to a full-day timetable that is suitable for planning problems and also | ||
| for complex timetable analyses. | ||
| PathTime: This attribute describes the temporal and spatial sequence of the travel route. | ||
| PathTime is a vector that consists of the following elements: | ||
| - Node: Name of the place or city. | ||
| - ArrivalTime: Consecutive Arrival time at the node: The time in minutes at which the train arrives at the node. | ||
| - DepartureTime: Consecutive Departure time at the node: The time in minutes at which the train leaves the node. | ||
| - Stop: True if the train stops so that passengers can board or alight and possibly take a connecting journey at the same node. | ||
| False if the train does not stop and passengers cannot board or alight. | ||
| - ArrivalMinute: Arrival time at the node: The time in minutes at which the train arrives at the node - just the minute - 0..60 | ||
| - DepatureMinute: Departure time at the node: The time in minutes at which the train leaves the node - just the minute - 0..60 | ||
| Additional Information: | ||
| Within a train journey, all trainruns in opposite direction have a symmetric counterpart, expect there is just a one-way trainrun. | ||
| Symmetrical means that forward (F) and backward (B) | ||
| always have symmetrical times. The travel times are symmetrical to zero minutes, i.e., 60 minus the arrival | ||
| time corresponds to the departure time in the opposite direction. | ||
| Build the agent. Then ask the user if they can upload timetable data. Every time timetable data is uploaded, | ||
| create a new variant. Use only the timetable data that has been uploaded. Once a new variant is uploaded, | ||
| output in a table for the new data of the new variant how many trains were loaded and how many journes there are. | ||
| Only this should be output. Once everything is loaded, also output, "I am waiting for new instructions." | ||
| Output: Ask for the language the user would like to receive the response in. And write: "Please load the data by uploading CSV files." |
There was a problem hiding this comment.
(1) http://copilot.microsoft.com/
(2) Change deep thinker
(3) Copy this "promp"
aiAdrian
commented
Jul 24, 2025
Comment on lines
+490
to
+493
| Please compare the variants and provide feedback on the differences you observe in the variants, | ||
| including route deviations, ArrivalMinute or DepatureMinute deviations, frequencies, ... . | ||
| The results should be visualized. For example, you could use a table with the variants and the | ||
| analysis results in the columns and the topic in the rows. |
There was a problem hiding this comment.
After you have uploaded at least two different trainrunExportFile.csv
Enter this prompt to first insights from copilot
aiAdrian
added
experimental - might get merged
and removed
enhancement
…or-frontend into export_raw_trainrun_data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This Pull Request introduces a function that exports raw trainrun data. The data is structured in a CSV format, capturing information about the name, frequency, direction, and travel time and stop information of the trains as
PathTime. ThePathTimedata is a array and each element consists of the following elements:The implementation iterates through all available trainruns, filters them, and creates a corresponding CSV representation.
Issues / Dependancy
Once the one-way trainrun gets merged this export must be extend to one-way trainrun!
#477
Checklist
documentation/