Code Evaluation Interface with Intermediate Result Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of technical computing environments (TCEs) face challenges in understanding how program code operates, as they can only view the end results of code evaluation without seeing intermediate steps or corresponding code portions, which hinders debugging and error identification.

Innovation Solution

Implementing a system where TCEs provide a user interface that displays program code alongside evaluation results, allowing users to interactively view the correspondence between code lines and their execution outcomes, with configuration parameters to control the display manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If TCEs display only end results of code evaluation, then the interface remains simple and clean, but users cannot understand intermediate steps or corresponding code portions, hindering debugging and error identification

Engineering Contradiction:
Improveintermediate evaluation resultsVSAvoiduser interface complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the code evaluation process into multiple intermediate steps, displaying each step's results alongside the corresponding code portion. This segmentation allows users to see the evaluation process broken down into manageable chunks, revealing intermediate results without overwhelming the interface with all information at once.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a spatial dimension to the code display by presenting evaluation results in a multi-dimensional layout where code portions and their corresponding results are positioned to show relationships. This dimensional arrangement allows intermediate results to be associated with specific code segments without creating a flat, cluttered interface.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If TCEs display all intermediate evaluation results alongside code, then users can fully understand code operations, but the interface becomes cluttered and complex

Engineering Contradiction:
Improvedebugging capabilityVSAvoiduser interface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies local quality by displaying evaluation results specifically at the locations where they are most useful - adjacent to the corresponding code portions. Rather than uniformly displaying all results everywhere, the interface provides detailed information locally where needed while keeping other areas clean and simple.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces an intermediary display structure that mediates between the code and the evaluation results. This intermediary layer organizes and presents results in a way that connects them to relevant code portions without directly cluttering the code itself, acting as a buffer that enhances understanding while maintaining interface cleanliness.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If TCEs provide detailed correspondence between code and evaluation results, then debugging and error identification improve, but the system requires more complex configuration parameters and display control mechanisms

Engineering Contradiction:
Improveerror identification accuracyVSAvoidconfiguration parameter complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic display control where the configuration parameters and display manner adapt based on user needs and context. The system can dynamically adjust what information is displayed, how it's organized, and which code portions receive detailed result associations, allowing high reliability when needed while maintaining simplicity when not required.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9665471B1Program code interface for providing program code and corresponding results of evaluating the program code
Publication Date: 2017.05.30 MATHWORKS INC
  • US9665471B1 patent drawing
  • US9665471B1 patent drawing
  • US9665471B1 patent drawing

AI summary

A device may receive an indication to evaluate a first portion of program code and a second portion of program code provided in a first section of a user interface. The device may evaluate the first portion of program code and the second portion of program code. The device may generate a first result corresponding to the first portion of program code and may generate a second result corresponding to the second portion of program code based on evaluating the first portion of program code and the second portion of program code. The device may provide the first result and the second result in a second section of the user interface. The second section may be separate from the first section. The device may provide a correspondence indicator that indicates a correspondence between the first result and the first portion of program code.