pepe/ALLSHIFT
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ALLSHIFT/superseded/MAY MONTH SIMULATION PLANS-20260725175516.md
pepe 72dd781dbc Organize documentation into docs/ and superseded/ 
Audit every document in the repository, convert the non-markdown ones into
markdown reports, and split current documentation from outdated material.

docs/ — 31 markdown documents in seven numbered sections. Twenty are new
reports generated from .docx / .pdf / .xlsx / .mlx / .m sources that were
previously unreadable in the browser and undiffable in git. Each report
carries a provenance block (source path, format, MD5) and links back to its
original; all 13 recorded checksums verify against the files on disk.
Machine-extraction losses (PDF table column interleaving, Word OMML
equations, embedded figures) are called out explicitly rather than silently
smoothed over.

superseded/ — outdated material with a documented reason per entry:
two byte-identical ClickUp re-exports, an older revision of the BIDMC/UCSD
energy-flow doc (the retained copy adds the SoC Violation Rate KPI), a
duplicate of Shift input data.docx, the May 2026 simulation plan, the
root PV+Battery.md now covered by a fuller report, GitHub's stock
demo-repository template, and a zero-byte placeholder. Its README also
records what was deliberately NOT retired and why — the "Old Frameworks"
and "Old Simulations" folders hold unique Simulink revisions, and
"Big Ugly Folder" holds the only copy of framework revision 1.3.

Findings worth flagging, all documented in the reports:
- Simulink lineage recovered from each .slx's internal coreProperties.xml
  revision counter. The current model is
  Current Framework/Bobert0206_Initial_Simulation_Framework.slx (rev 2.7);
  the top-level copy is rev 1.3, five revisions behind.
- Simulations/Constants.m is a truncated byte-prefix of the Current
  Framework copy, silently missing H2_leak, H2_cap and E_H2_vol_h.
- The PEM electrolyser and fuel cell are unmodified MathWorks Simscape
  examples still at vendor defaults; the "10x bigger" sizing TODO recorded
  in Constants.m was never carried out.
- controller-claude.m does not compile — undefined P_Electro_max, outputs
  unassigned on several paths.
- The specification set uses two incompatible variable naming conventions
  and disagrees on action-space size (5 vs 16).
- MA_hourly_load.csv (13.7 MB) is the same 35,040 rows as 89993-0.parquet
  (2.4 MB).
- Clinical data is the MIMIC-IV *demo* (ODbL, 100 patients), not full
  MIMIC-IV — redistributable, but the licence and citation are unrecorded.

Housekeeping: untrack 21 Simulink build artefacts (slprj/, *.slxc) and add
ignore rules for them. Root README rewritten around the new layout.

Recruitment notes naming individual candidates are excluded from version
control via .gitignore rather than committed; the generic question template
is kept in docs/07-team-and-operations/.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-25 21:20:33 -07:00

3 KiB
Raw Permalink Blame History

MAY MONTH SIMULATION PLANS

Mind Map.pdf

Team Discussion Task: Wednesday discussion Purpose:

  • Discuss current plans.
  • Clarify the next direction.
  • Arrange a working session/evening to align the simulation work. Emails and External Guidance Current status: 3 replies received Actions:
  1. Read the assigned paper.
  2. Send emails to arrange a call or meeting. - DONE
  3. Send slides when required. Purpose: To seek guidance from people with experience in digital twins, microgrids, hybrid energy systems, and simulation-based implementation. Current Status of Simulation Work Component Development:
  • Separate component models are mostly completed.
  • Current progress is around 75% done. - We can move on to next step . 75% ( Grid is not ready thats all) Next Step: The next major step is to combine all separate components into one integrated system-level model. Planned Workflow:
  1. Arrange a work session.
  2. Combine all components into one Simulink model.
  3. Test whether the combined model runs correctly.
  4. Data Generation → Main Idea for Simulation Work The hydrogen digital twin paper is being used as the main inspiration. Core Idea:
  • The paper shows that a digital twin model can be built using component-based models.
  • Based on this idea, our combined components can be used to produce simulated data.
  • The end goal is to generate data from the integrated simulation model. Key Point: Data production from components is the final goal. Proposed Simulation Steps Step 1 — Combine Components Connect all individual models into one complete system. Components may include:
  • Solar PV
  • Battery
  • Electrolyzer
  • Hydrogen tank
  • Fuel cell
  • Hospital load
  • Grid - towards the end Step 2 — Define Inputs and Outputs - (Completed) Each component should have clearly defined inputs and outputs. Inputs may include:
  • Solar irradiance
  • Hospital load demand
  • Battery state of charge
  • Hydrogen tank level
  • Grid availability Outputs may include:
  • PV power
  • Battery power
  • Electrolyzer hydrogen production
  • Hydrogen tank volume
  • Fuel cell power
  • Grid import/export
  • Unserved load

Step 3 — Data Generation Once the combined model runs, use it to generate simulation data. Requirement: A basic workability check is needed first. Check that:

  • All components are connected properly.
  • Signals flow correctly.
  • No unrealistic values occur.
  • The system produces reasonable outputs. After basic check: The model can be improved and refined.

Research on Hospital Data Hospital data is still under research. Current Findings:

  1. A 2025 hospital load / energy audit paper may be useful for Step 3, especially for creating or validating hospital load profiles.
  2. Hospital load website -- that produces data -- its working - but requires looking into it
  3. More data research is still needed and is currently in progress.