PedestrianDynamics / PedestrianDynamics/PedPy
Optimize profile calculation
Open
Nobody has claimed this yet.
optimization
profiles
- Dominant language
- Pascal
- Stars
- 35
- Forks
- 18
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
Currently the profiles are computed for all grid cells in the bounding box of the geometry, see:
But as one can see a lot these cells may lie outside of the geometry, and do not need to be computed, see:
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 by locating the code that computes profiles across the geometry's bounding-box grid, then inspect how grid cells are selected. Compare the selected cells with the geometry shown in the issue and verify that cells outside the geometry are skipped without changing profiles for relevant cells.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100