How to Use the Simulator

  1. For the Riopele pitch, start with Presentation Mode and click each ribbon step at your own pace.
  2. Choose an industrial example or adjust the sliders manually.
  3. Keep fiber composition at 100%. The app auto-balances sliders, but the total is always shown.
  4. Review the executive summary strip for predicted class, target status, main driver, and trade-off.
  5. Use Set as Baseline before changing inputs to compare one fabric recipe against another.
  6. Review Path to Class ≥3 for practical improvement recommendations.
  7. Click Export Scenario Summary to download a standalone HTML report.
  8. Optionally paste an OpenAI API key and use the AI Engineering Assistant to explain the model output, compare scenarios, create a lab-trial plan, or draft a Riopele engineering brief.

What the Outputs Mean

Presentation Mode

The Presentation Mode ribbon is designed for a controlled sponsor demo rather than an auto-running tour. Use it to pause for questions or jump to the area Riopele wants to discuss.

  1. Value Frame: state the business and engineering value before showing features.
  2. Risk Scenario: load a vulnerable fabric recipe.
  3. Save Baseline: make the weak scenario the comparison point.
  4. Improve Recipe: move to a stronger Class ≥3 path.
  5. Explain Drivers: show process-stage and parameter-level influence.
  6. AI / Lab Brief: generate a practical explanation or validation plan.
  7. Validation Plan: show what Riopele data would calibrate the model.
  8. Platform Vision: explain how pilling can become the first vertical of broader textile engineering intelligence.

Using Baseline vs Scenario

Set a baseline using the current fabric settings. Then change one or more inputs to create an alternative. The comparison table shows whether the scenario improved pilling class and what happened to handle, cost, time, and energy.

Recommended workflow: change one stage at a time. For example, first compare Low vs Medium twist, then compare no finish vs anti-pilling finish. This makes the engineering explanation easier.

Scope Warnings

Boundary warnings appear when an input is outside the intended challenge scope or near the edge of the current prototype model. These warnings do not block the simulator; they flag cases that need stronger ISO lab validation.

Using the AI API Layer

Maintaining the App

The app remains static and GitHub Pages compatible. Key files are separated for maintainability: