R Under development (unstable) (2025-06-05 r88281 ucrt) -- "Unsuffered Consequences" Copyright (C) 2025 The R Foundation for Statistical Computing Platform: x86_64-w64-mingw32/x64 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(bidux) > > test_check("bidux") Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Default Effect: Pre-select the most useful timeframe or metrics for initial view. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Default Effect - No accessibility considerations specified Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Automatically suggested interaction principles: progressive_disclosure, hover_effects. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Anchoring Effect Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Framing & Loss Aversion Stage 4 (Anticipate) completed. - Bias mitigations: 2 defined - Interaction principles: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing., Consider also addressing these common biases: confirmation Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Default Effect: Pre-select the most useful timeframe or metrics for initial view. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Default Effect - No accessibility considerations specified Stage 4 (Anticipate) completed. - Bias mitigations: 5 defined - Interaction principles: 2 defined - Key suggestions: association bias mitigation: Consider how this bias affects user decisions., clustering illusion mitigation: Consider how this bias affects user decisions., status quo bias mitigation: Consider how this bias affects user decisions. Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Default Effect: Pre-select the most useful timeframe or metrics for initial view. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Default Effect - No accessibility considerations specified Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Automatically suggested interaction principles: progressive_disclosure, hover_effects. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Anchoring Effect Stage 4 (Anticipate) completed. - Bias mitigations: 1 defined - Interaction principles: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., Consider also addressing these common biases: framing, confirmation Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Default Effect: Pre-select the most useful timeframe or metrics for initial view. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Default Effect - No accessibility considerations specified Stage 4 (Anticipate) completed. - Bias mitigations: 5 defined - Interaction principles: 2 defined - Key suggestions: association bias mitigation: Consider how this bias affects user decisions., clustering illusion mitigation: Consider how this bias affects user decisions., status quo bias mitigation: Consider how this bias affects user decisions. Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Default Effect: Pre-select the most useful timeframe or metrics for initial view. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Default Effect - No accessibility considerations specified Stage 4 (Anticipate) completed. - Bias mitigations: 1 defined - Interaction principles: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., Consider also addressing these common biases: framing, confirmation Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing. Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., anchoring mitigation: Always show reference points like previous period, budget, or industry average. Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., beautiful-is-good stereotype mitigation: Pay attention to polish in summary cards with clear typography and spacing. Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., availability bias mitigation: Consider how this bias affects user decisions. Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., cognitive load mitigation: Use tabs or collapsible sections to organize complex information. Stage 4 (Anticipate) completed. - Bias mitigations: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing., Consider also addressing these common biases: confirmation Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Automatically suggested bias mitigations: attention bias, belief perseverance, framing. Automatically suggested interaction principles: progressive_disclosure, hover_effects, visual_prominence. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Concept 'attention bias' not found Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Framing & Loss Aversion Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Automatically suggested bias mitigations: attention bias, belief perseverance, framing. Automatically suggested interaction principles: progressive_disclosure, hover_effects, visual_prominence. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Concept 'attention bias' not found Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Framing & Loss Aversion Stage 4 (Anticipate) completed. - Bias mitigations: 3 defined - Interaction principles: 3 defined - Key suggestions: attention bias mitigation: Consider how this bias affects user decisions., belief perseverance mitigation: Proactively show content that might disprove initial assumptions., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing. Stage 4 (Anticipate) completed. - Bias mitigations: 2 defined - Interaction principles: 3 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., framing mitigation: Toggle between progress (65% complete) and gap (35% remaining) framing., Consider also addressing these common biases: confirmation Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Automatically suggested interaction principles: progressive_disclosure, hover_effects, visual_prominence. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Anchoring Effect Stage 4 (Anticipate) completed. - Bias mitigations: 1 defined - Interaction principles: 3 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., Consider also addressing these common biases: framing, confirmation Stage 4 (Anticipate) completed. - Bias mitigations: 1 defined - Interaction principles: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., Consider also addressing these common biases: framing, confirmation Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found 7 concept(s) matching 'bias|anchor|fram|confirm' Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Found partial match: Anchoring Effect Stage 4 (Anticipate) completed. - Bias mitigations: 1 defined - Interaction principles: 2 defined - Key suggestions: anchoring mitigation: Always show reference points like previous period, budget, or industry average., Consider also addressing these common biases: framing, confirmation Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. No concepts found matching 'xyznonexistent' Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts i Suggested central question: How can we reduce cognitive load to address Users struggle with complex data? i Suggested data story elements based on previous stage information i Created user persona 'Data Analyst Persona' based on audience information i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: What is causing data complexity issues? - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - No user personas defined Stage 2 (Interpret) completed. - Central question: How can we improve visual hierarchy to address Users struggl... - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - User personas: 1 defined Stage 2 (Interpret) completed. - Central question: How can we simplify the dashboard? - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - User personas: 1 defined Stage 2 (Interpret) completed. - Central question: Test question - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question might benefit from more specificity. - No user personas defined Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - No user personas defined Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - No user personas defined i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - User personas: 1 defined i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - No user personas defined i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - User personas: 2 defined Stage 2 (Interpret) completed. - Central question: How can we improve the user experience of the dashboard? - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - No user personas defined i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: Test question - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question might benefit from more specificity. - User personas: 2 defined Auto-suggested theory: Information Scent (confidence: 80%) Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle to navigate cluttered dashboards - Theory: Information Scent (auto-suggested) - Evidence: User testing showed increased time to locate key metrics. - Theory confidence: 80% - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: Simple dashboard issue - Theory: Custom Theory - Evidence: Users are confused by the interface layout - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Hick's Law (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Users are overwhelmed with too many options in the dropdown - Theory: Hick's Law (auto-suggested) - Evidence: User testing shows confusion - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Sales team struggles with complex filter combinations - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Training sessions revealed confusion with multiple select... - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: The chart is cluttered and confusing - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Feedback indicates users are disoriented. - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Short - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Sufficient evidence provided. - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: A sufficiently detailed problem description - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Short - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: A sufficiently detailed problem description. - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Evidence with enough detail for proper matching of theories. - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Hick's Law (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Users are overwhelmed with too many options in the dropdown - Theory: Hick's Law (auto-suggested) - Evidence: User testing shows confusion - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Visual Hierarchies (confidence: 85%) Stage 1 (Notice) completed. (20% complete) - Problem: Dashboard layout is cluttered and disorganized - Theory: Visual Hierarchies (auto-suggested) - Evidence: Users can't find important metrics - Theory confidence: 85% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: This is a very long problem description. This is a very l... - Theory: Cognitive Load Theory (auto-suggested) - Evidence: This is detailed evidence. This is detailed evidence. Thi... - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: UI is confusing - Theory: My Custom Theory Framework - Evidence: Users report difficulties - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Complex dashboard with many options - Theory: Cognitive Load Theory (auto-suggested) - Evidence: User feedback indicates confusion and task abandonment - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle with complex data visualization - Theory: Cognitive Load Theory (auto-suggested) - Evidence: User testing revealed high task completion times - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface overwhelms users - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Analytics show high bounce rates - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Interface complexity issue - Theory: Cognitive Load Theory (auto-suggested) - Evidence: User research indicates problems - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Hick's Law (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Too many dropdown options overwhelm users - Theory: Hick's Law (auto-suggested) - Evidence: Users abandon tasks when faced with many choices - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: General usability issues - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Some user complaints - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Mobile interface is difficult to use - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Touch targets are too small - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Hick's Law (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle with too many choices - Theory: Hick's Law (auto-suggested) - Evidence: Decision time is very long - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 -- Implementation tips for selected concepts: * Test Concept: Implementation tip for Test Concept Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Test Concept - No accessibility considerations specified -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Concept 'Test Concept' not found Stage 3 (Structure) completed. - Layout: invalid_layout - Concepts: Test Concept - No accessibility considerations specified Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. i Detected concept from theory: Principle of Proximity Stage 3 (Structure) completed. - Layout: dual_process - Concepts: - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Information Hierarchy, Cognitive Load Theory - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Principle of Proximity, Visual Hierarchy, Cognitive Load Theory - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy, Breathable Layouts - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Dual-Processing Theory, Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy, Cognitive Load Theory - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - Accessibility considerations included: Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - Accessibility considerations included: color_contrast, keyboard_navigation, screen_reader Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts i Consider adding these common accessibility parameters:- screen_reader- text_size- alternative_text- focus_indicators- semantic_markup- aria_labels -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Visual Hierarchy: Apply different font sizes and weights to create clear information hierarchy. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - Accessibility considerations included: color_contrast, keyboard_navigation Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: grid - Concepts: Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: card - Concepts: Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: tabs - Concepts: Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: breathable - Concepts: Visual Hierarchy - No accessibility considerations specified Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - No accessibility considerations specified Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts i Consider adding these common accessibility parameters:- color_contrast- keyboard_navigation- screen_reader- text_size- alternative_text- focus_indicators- semantic_markup- aria_labels -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Visual Hierarchy: Apply different font sizes and weights to create clear information hierarchy. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy - Accessibility considerations included: vision, motor Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle with complex data - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle with complex data - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Test problem - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Test evidence - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: Users struggle with complex data - Theory: Cognitive Load Theory - Evidence: User complaints - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: Complex interface - Theory: Cognitive Load Theory - Evidence: User feedback - Next: Use bid_interpret() for Stage 2 Stage 2 (Interpret) completed. - Central question: How to simplify the interface? - Your data story is taking shape (50%). Consider adding: tension, resolution. - Your central question is appropriately scoped. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Visual Hierarchy: Apply different font sizes and weights to create clear information hierarchy. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Cognitive Load Theory: Use tabs or collapsible sections to organize complex information. Stage 3 (Structure) completed. - Layout: dual_process - Concepts: Visual Hierarchy, Cognitive Load Theory - No accessibility considerations specified Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Test problem - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Test evidence - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 v Found 1 DT component suggestion for BID Notice stage Stage 1 (Notice) completed. (20% complete) - Problem: Users need better visual hierarchy - Theory: Visual Hierarchies - Evidence: User testing - Next: Use bid_interpret() for Stage 2 i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: How to improve visual organization? - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Principle of Proximity: Place related controls and visualizations in proximity to each other. Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Visual Hierarchy: Apply different font sizes and weights to create clear information hierarchy. Stage 3 (Structure) completed. - Layout: card_layout - Concepts: Principle of Proximity, Visual Hierarchy - No accessibility considerations specified Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Test problem - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Test evidence - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 i Showing components ordered by relevance to your BID analysis Auto-suggested theory: Visual Hierarchies (confidence: 85%) Stage 1 (Notice) completed. (20% complete) - Problem: Need better organization - Theory: Visual Hierarchies (auto-suggested) - Evidence: User feedback - Theory confidence: 85% - Next: Use bid_interpret() for Stage 2 i Suggested data story elements based on previous stage information Stage 2 (Interpret) completed. - Central question: How to organize content? - Your data story has all key elements. Focus on making each component compelling and relevant. - Your central question is appropriately scoped. - No user personas defined Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. Returning all 41 concepts -- Implementation tips for selected concepts: Rows: 41 Columns: 7 -- Column specification -------------------------------------------------------- Delimiter: "," chr (7): concept, description, category, reference, example, implementation_... i Use `spec()` to retrieve the full column specification for this data. i Specify the column types or set `show_col_types = FALSE` to quiet this message. * Information Hierarchy: Use font size, weight, and color to establish visual hierarchy. Stage 3 (Structure) completed. - Layout: sidebar_layout - Concepts: Information Hierarchy - No accessibility considerations specified Auto-suggested theory: Cognitive Load Theory (confidence: 90%) Stage 1 (Notice) completed. (20% complete) - Problem: Test problem - Theory: Cognitive Load Theory (auto-suggested) - Evidence: Test evidence - Theory confidence: 90% - Next: Use bid_interpret() for Stage 2 Stage 1 (Notice) completed. (20% complete) - Problem: Executive dashboard needs simplification - Theory: Cognitive Load Theory - Evidence: Executive feedback - Next: Use bid_interpret() for Stage 2 [ FAIL 0 | WARN 8 | SKIP 0 | PASS 588 ] [ FAIL 0 | WARN 8 | SKIP 0 | PASS 588 ] > > proc.time() user system elapsed 18.01 4.81 22.25