ML4GW / ML4GW/aframe

Determine how to make multiple network outputs flexible

Open
#474 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

merger-time
Dominant language
Python
Stars
18
Forks
28
Avg merge
2d 2h
Merged PRs (30d)
7

Description

The current export and inference pipeline assumes a single output tensor (detection statistic). Supporting merger time requires routing a second heatmap tensor through the TRT ensemble in export/main.py, receiving and unpacking multiple output arrays in the inference client, and dispatching to the correct postprocessor strategy based on which outputs are present. The goal is to make this configurable (e.g. via export_heatmap: bool) rather than requiring separate code paths.

Contributor guide

Open the 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.

Research direction

Start with export/main.py and trace how the export and inference pipeline handles the current detection-statistic tensor. Then inspect the inference client’s output unpacking and the postprocessor dispatch strategy. Done means a configurable export_heatmap option supports routing and processing either one output or both outputs without separate code paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.