PedestrianDynamics / PedestrianDynamics/PedPy
Include handling of z-component and markerIDs in trajectory file
Open
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 35
- Forks
- 18
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
The import of trajectory files only handles the columns 'id', 'frame', 'x', 'y'.
I suggest including further (optional) columns:
'z', 'markerID' and maybe also 'time'
This should be handled at least in the functions <load_trajectory_data_from_txt> and in the data class .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with load_trajectory_data_from_txt and the TrajectoryData data class, tracing how the existing id, frame, x, and y columns are parsed and stored. Done means optional z and markerID columns are handled consistently; clarify whether time is in scope before implementing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100