feat: FGSM robustness tool, Grad-CAM interpretability tool, and async multi-tool orchestrator#1
Open
sisodiyaanand wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the first deterministic tools (per AGENT_TRACKER.md, which currently lists no implemented agents) for adversarial robustness and interpretability evaluation, plus a generic async orchestrator to run heterogeneous tools concurrently.
FGSMAttackTool— FGSM adversarial perturbation, measures prediction flips (extendsAbstractBaseTool)GradCAMTool— Grad-CAM saliency heatmaps (extendsAbstractBaseTool)AsyncAgentOrchestrator— runs multiple tools concurrently viaasyncio.to_thread, with honest per-tool error reporting instead of silent failure (extendsAbstractBaseAgent)All three have dedicated tests; full suite passes (5/5, including the existing
test_smoke.py).Open question for maintainers
These tools currently take raw
torch.TensorI/O rather than going through the LLM-drivenDLensBaseAgent. I used the deterministicAbstractBaseAgent/AbstractBaseToolpattern instead, since tensor I/O doesn't map cleanly to JSON-serializable LLM tool calls. Wanted to check if this is the right pattern, or if there's a preferred way to eventually bridge this into the conversational/LLM agent layer.I'm an MSCS student at Georgia Tech, interested in this as a potential GSoC 2027 contribution area. Happy to iterate based on feedback — opening this as a draft to start the conversation rather than requesting immediate merge.