Add structured JSON outputs for ChatBob integration#82
Draft
ChrisCollison wants to merge 22 commits into
Draft
Conversation
…rmation about the incoming dataset such that a ChatBOB can use that information downstream
…the variable desc_keep, which is a variable built at source in the original ROBERT. Here we add a label to the JSON auditing files so that the variable can be better understood by ChatBob
… locally on my computer
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
1 participant
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.
This draft pull request adds an additive JSON-output layer across the main ROBERT modules. At points where ROBERT already generates information used in standard DAT outputs, the same underlying runtime evidence is also recorded in structured JSON files under a separate top-level JSON/ directory.
Controlled comparisons were performed using the same input dataset with the modified and official versions of ROBERT. The scientific CSV and DAT outputs were identical apart from expected non-scientific differences such as timestamps, paths, and execution times.
This draft is intended to support review of:
the implementation approach;
the proposed branch strategy, including a possible protected chatbob-json branch;
the acceptance and regression tests required before integration.
The JSON schema should currently be considered experimental and will be developed separately as it is aligned with ChatBob user questions and interface requirements.