|
Download Processing_Code/data/README.md from InterestingITS/U-EASWS: direct link, hf CLI and curl.
- Browser
- Download file 1.14 kB
-
https://huggingface.co/datasets/InterestingITS/U-EASWS/resolve/main/Processing_Code/data/README.md
- Command line
-
hf download hf://datasets/InterestingITS/U-EASWS/Processing_Code/data/README.md
-
curl -L -o README.md https://huggingface.co/datasets/InterestingITS/U-EASWS/resolve/main/Processing_Code/data/README.md
1.14 kB
| # Input file placement | |
| For downstream processing, place the existing Basic trajectory CSVs under `basic/`, using the filenames in `../configs/basic_manifest.csv` or pass the actual path explicitly. These files already contain processed vehicle IDs, lanes, directions, positions, velocities and lengths. The README gives the direct risk/pairing/sampling/inference/interaction commands. | |
| For source detection processing, place the raw detection CSVs under `raw/` using `../configs/source_manifest.csv`. A raw reconstruction lane input belongs under `lanes/` and has `Frame,Vehicle_ID,Lane number,Direction` keyed by original source records. To transfer lane and direction labels from a Basic file, apply the corresponding source/frame/vehicle mapping to the original detection keys. | |
| The processing commands create new files under `runs/` relative to the code directory. Each file's generating command and downstream consumer are listed in the README and `../docs/INPUT_OUTPUT.md`. | |
| All commands accept explicit paths. For combining sources or joining processed IDs, use the established source/frame/vehicle correspondence and offsets. | |