Process scans #5 and #6 with the full pipeline

Open
#19 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
data

Research direction

Start by locating how the project runs the full pipeline and records a TRAINING run, then find the source recordings for scans #5 and #6 on the PC. Use --window 9 for scan #5 as specified; the issue says the work is done when each scan has one logged run and fixture sheets are written.

Written by the indexing model from the issue text.

Description

step-4

Both recordings are on the PC without a run. Needed for 4.2 / E3 (rooms the semantic rules were not tuned on).

Done when: one logged run each (TRAINING), fixture sheets written. Scan #5 is 352.5 s: --window 9 (D-073).

Dominant language
Java
Stars
0
Forks
0
Avg merge
6m
Merged PRs (30d)
7

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Umairishuman/BuildScan3D

All issues in Umairishuman/BuildScan3D

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.