Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removes the code path of MultiMessage from pre-process stages, post-process stages, inference stages, etc. #1887

Closed
25 tasks done
Tracked by #1802
yczhang-nv opened this issue Sep 9, 2024 · 0 comments · Fixed by #1803
Closed
25 tasks done
Tracked by #1802
Assignees
Labels
feature request New feature or request

Comments

@yczhang-nv
Copy link
Contributor

yczhang-nv commented Sep 9, 2024

Previously the stages support processing both ControlMessage and MultiMessage - need to remove the code paths for MultiMessage from the following stages (from both C++ & Python implementation):

  • Pre-process stages:

    • deserialize_stage
    • preprocess_base_stage
    • preprocess_ae_stage
    • preprocess_fil_stage
    • preprocess_nlp_stage
    • train_ae_stage
  • Post-process stages:

    • serialize_stage
    • add_scores_stage_base_stage
    • add_scores_stage
    • add_classification_stage
    • filter_detections_stage
    • generate_viz_frames_stage
    • ml_flow_drift_stage
    • time_series_stage
    • validation_stage
  • Inference stages:

    • auto_encoder_inference_stage
    • identity_inference_stage
    • inference_stage
    • pytorch_inference_stage
    • triton_inference_stage
  • Output stages:

    • write_to_vector_db_stage

The related unit tests should also updated to use only ControlMessage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants