← All questions
Which operations are in either Software Engineering & Development or Scientific Experimentation & Laboratory R&D?
GQ-0266
327 results
- Acquire Measurement Result
- Adapt Method for Experiment
- Analyze Sources of Inconsistency
- Apply Continue or Stop Criteria
- Approve Controlled Protocol
- Assemble Experiment Plan
- Assess Campaign Progress
- Assess Design Bias Risks
- Assess Deviation Impact
- Assess Evidence Consistency
- Assess Experimental Data Quality
- Assess Experimental Feasibility
- Assess Instrument Suitability
- Assess Measurement Validity
- Assess Method Applicability
- Assess Replication Consistency
- Assess Reproducibility Readiness
- Assess Reuse Readiness
- Assess Sensitivity to Assumptions
- Assess Statistical or Practical Difference
- Assign Sample to Experiment
- Associate Material Identifier
- Associate Reference with Measurement
- Associate Sample with Condition
- Authorize Instrument for Measurement
- Bind Context-Specific Protocol Values
- Capture Experimental Context
- Capture Parameter Changes
- Capture Raw Scientific Data
- Capture Scientific Metadata
- Characterize Result Uncertainty
- Check Analytical Assumptions
- Check Instrument Readiness
- Check Measurement Completeness
- Clarify Procedure Decision Points
- Classify Experimental Failure
- Close Experimental Run
- Communicate Scientific Finding
- Compare Experimental Results
- Compare Original and Replication Results
- Compare Repeat Outcomes
- Compare Reproduced Result
- Compare Supporting and Conflicting Evidence
- Complete Experimental Run
- Configure Closed-Loop Experiment Cycle
- Configure Measurement Acquisition
- Confirm Data and Sample Handoff
- Confirm Experiment Prerequisites
- Confirm Planned Sample Use
- Create Experiment Record
- Create Method Version
- Define Analysis Objective
- Define Expected Relationship
- Define Experimental Controls
- Define Experimental Method
- Define Experimental Objective
- Define Measurand or Observation
- Define Protocol Parameters
- Define Replication Objective
- Define Response Variables
- Derive Scientific Conclusion
- Design Replication Study
- Detect Execution Deviation
- Determine Need for Further Experiment
- Determine Research Data Access
- Diagnose Failure Cause
- Document Interpretation Rationale
- Document Method Conditions
- Document Operator Notes
- Document Replication Outcome
- Document Reproducibility Finding
- Document Result Traceability
- Estimate Combined Measurement Uncertainty
- Evaluate Evidence Quality
- Evaluate Experimental Design Alternatives
- Evaluate Loop Result
- Finalize Experiment Record
- Find Experimental Data or Record
- Find Reusable Method
- Flag Questionable Measurement
- Formulate Testable Hypothesis
- Frame Research Question
- Generate Corrective Experiment Change
- Generate Next-Experiment Options
- Identify Candidate Design Families
- Identify Candidate Measurement Systems
- Identify Conditions to Refine
- Identify Experimental Factors
- Identify Inconsistent Results
- Identify Missing Reproduction Inputs
- Identify Required Resources and Dependencies
- Identify Required Scientific Metadata
- Identify Result Patterns
- Identify Traceability Chain
- Identify Uncertainty Components
- Identify Unresolved Questions
- Index Research Objects
- Interpret Experimental Result
- Link Derived Data to Source Data
- Link Parent and Derived Materials
- Map Analytical Data Structure
- Organize Experimental Data
- Perform Experimental Procedure
- Plan Randomization or Blocking
- Plan Repeat Experiment
- Prepare Execution Instructions
- Prepare Experimental Setup
- Prepare Independent Replication
- Prepare Reproduction Package
- Prepare Sample or Specimen
- Preserve Original Data Record
- Preserve Research Data Package
- Publish Current Procedure Guidance
- Qualify Conclusion with Limitations
- Quantify Experimental Variability
- Rank Candidate Experiments
- Reconcile Run Records
- Reconstruct Data Provenance
- Reconstruct Material Lineage
- Reconstruct Original Analysis Context
- Record Adaptation Rationale
- Record Data Access Context
- Record Data Derivation
- Record Deviation Disposition
- Record Execution Observations
- Record Initial Conditions
- Record Material Derivation
- Record Measurement Context
- Record Method Change
- Record Preparation Context
- Record Sample Disposition
- Record Sample Location Context
- Register Experimental Material
- Relate Result to Hypothesis
- Repeat Experimental Procedure
- Report Measurement Uncertainty
- Rerun Analysis
- Resolve Analysis Data Issues
- Resolve Protocol Review Findings
- Retire or Supersede Method Version
- Review Calibration or Verification Status
- Review Experiment Outcome
- Review Experiment Plan Completeness
- Review Protocol Adequacy
- Revise Design for Feasibility
- Revise Experimental Parameters
- Score Candidate Experiments
- Select Analysis Approach
- Select Data for Preservation
- Select Experimental Design
- Select Experiments for Execution
- Select Instrument or Measurement System
- Select Measurement Approach
- Select Next Experiment
- Select Reference Material
- Select Sample for Preparation
- Sequence Experimental Activities
- Set Experimental Conditions
- Set Factor Levels and Ranges
- Set Measurement Quality Need
- Set Protocol Tolerances
- Share Research Data
- Specify Analysis Inputs and Outputs
- Specify Discriminating Prediction
- Specify Intended Learning
- Specify Method Inputs and Outputs
- Start Experimental Run
- Summarize Learning from Run
- Transform Analytical Data Representation
- Trigger Next Experimental Iteration
- Update Experimental Campaign Direction
- Update Sample Scientific Status
- Validate Interoperable Data Exchange
- Validate Metadata Completeness
- Verify Calibration Linkage
- Verify Condition Readiness
- Verify Material Identity
- Verify Raw Data Completeness
- Verify Reference Material Context
- Verify Run Readiness
- Adapt Code to Dependency Change
- Adapt Software to Interface / Contract Change
- Add Regression Assertion
- Apply Behavior-Preserving Transformation
- Apply Compatibility Resolution
- Apply Review-Driven Change
- Apply Transformation Across Codebase
- Assess Caller and Implementation Adaptation
- Assess Change Functional Correctness
- Assess Change Maintainability and Quality
- Assess Change Security-Sensitive Effects
- Assess Dependency Impact
- Assess Framework or Runtime Migration Impact
- Assess Repair Validation Result
- Assess Test-Double Appropriateness
- Capture Reproducible Failure Case
- Characterize Behavior Gap
- Check Implementation Against Intent
- Check Implementation Against Repository Guidance
- Collect Related Engineering Context
- Collect Runtime Diagnostic Evidence
- Collect Static-Analysis Evidence
- Collect Surrounding Code Context
- Collect Test Execution Evidence
- Complete New-Behavior Error Handling
- Convert Defect to Regression Test
- Coordinate Multi-File Implementation
- Create Developer Test
- Create Repository Engineering Instructions
- Create Test Fixture
- Create or Update Test Double
- Decompose Engineering Change Work
- Define Change Validation Plan
- Define Semantic Transformation Pattern
- Detect Software Compatibility Conflict
- Determine Compatibility Resolution
- Determine Software Root Cause
- Document Repository Coding Conventions
- Document Repository Setup and Build Commands
- Document Repository Test and Validation Commands
- Document Software Architecture Guidance
- Encode Repository Engineering Guardrail
- Establish Expected Behavior
- Establish Observed Behavior
- Evaluate Defect Hypotheses Against Evidence
- Extract or Consolidate Abstractions
- Formulate Review Comment
- Formulate Software Defect Hypotheses
- Formulate Software Repair Alternatives
- Formulate Suggested Code Change
- Formulate Technical Change Alternatives
- Identify Agent Context Gaps
- Identify Change Validation Surfaces
- Identify Change-Relevant Tests
- Identify Changed Interface Contract
- Identify Code Review Defects
- Identify Coordinated Change Components
- Identify Corrective Action for Validation Failure
- Identify Dependency Remediation Need
- Identify Deprecated API Usage
- Identify Failed Test or Check
- Identify Implementation Conformance Gaps
- Identify Implementation Extension Points
- Identify Interface and Dependency Impact
- Identify Obsolete or Brittle Implementation
- Identify Potentially Affected Code
- Identify Potentially Affected Tests
- Identify Primary Change Components
- Identify Recurring Repository Engineering Failure
- Identify Refactoring Target
- Identify Required Software Behavior
- Identify Required Validation Checks
- Identify Review Risk Regions
- Identify Security and Dependency Review Findings
- Identify Software Component Boundaries
- Identify Unnecessary or Unclear Change
- Identify Validation Coverage Gaps
- Implement API Behavior
- Implement New Software Logic
- Implement Software Interface
- Implement Targeted Software Repair
- Inspect Change Diff
- Inspect Dependency Delta
- Inspect Own Change Diff
- Inspect Repository Organization
- Inspect Surrounding Review Context
- Integrate New Behavior with Existing Code
- Interpret Engineering Change Request
- Interpret Review Feedback
- Interpret Test or Build Failure
- Inventory Changed Dependencies
- Isolate Failure-Triggering Conditions
- Limit Unrelated Repair Change
- Localize Failure to Code Region
- Localize Review Finding
- Locate Behavior Implementation
- Locate Relevant Entry Points
- Locate Similar or Related Implementations
- Maintain Agent-Readable Repository Guidance
- Maintain Test Assertions and Data
- Map Deprecated Usage to Supported API
- Migrate Framework or Runtime Usage
- Modify Existing Software Logic
- Narrow Failure to Relevant Components
- Prepare Change for Review
- Prepare Integration-Ready Change Summary
- Propagate Change Across Modules
- Rank Fault-Location Candidates
- Record Change Validation Results
- Remove Dead or Redundant Code
- Remove Structural Duplication
- Remove or Retire Obsolete Behavior
- Replace Deprecated API Usage
- Replace Obsolete Implementation Pattern
- Reproduce Reported Software Failure
- Resolve Cross-File Implementation Inconsistencies
- Resolve Post-Migration Incompatibilities
- Restructure Code Modules
- Run Build, Type and Lint Checks
- Run Repair Regression Tests
- Run Targeted Software Tests
- Search for Relevant Code Symbols
- Select Relevant Repository Context
- Select Target Dependency Version or Replacement
- Select Technical Change Approach
- Sequence Coordinated Code Changes
- Structure Engineering Context for Retrieval
- Surface Engineering Ambiguities
- Trace Call and Control Relationships
- Trace Data and Type Relationships
- Trace Module Dependency Paths
- Update Dependency Definition
- Update Existing Component Interactions
- Update Existing Test for Change
- Update Guidance After Architecture Change
- Update Interface Callers and Implementations
- Update Repository Engineering Instructions
- Validate Agent Build / Test Execution Readiness
- Validate Agent Guidance / Constraint Readiness
- Validate Agent Repository-Navigation Readiness
- Validate Regression-Test Sensitivity
- Validate Repository Guardrail Effectiveness
- Validate Repository Instruction Usability
- Validate Transformed Code Consistency
- Verify Refactoring Behavior Preservation
- Verify Repository Build / Test Instructions
- Verify Target Failure Resolution