pepe/ALLSHIFT
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ALLSHIFT/superseded/PV+Battery.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

1.6 KiB
Raw Permalink Blame History

  1. Profiles Shift
    1. A new tab has been added to the existing excel data sheet
    2. Quick search data has been filed in for fast experimentation with the simulink
  2. PVBatteryRead
    1. A code developed with large assistance from chatGPT
    2. Originally intended to read everything off the spreadsheet, it currently reads dynamic data and prepares it for simulink use
    3. The constats reading would not function for some reason, however if these are to be changed, it can easily be done in:
  3. Constants
    1. Remeber to run both this and the previous code before attempting to run the simulinks
  4. SolarPanel + Battery
    1. Two indivudal codes using the equations from paper 1 to derive the desired outputs over time.
    2. Both do this in 2 different ways using different variables to compare consistency
    3. Keep in mind for most of the SoC related things it is ran in %. It is likely the dynamic data found will be in another unit, but thats what Q_rated and E_rated are for (to be used accordingly to paper 1)
    4. An issue was encountered where this code does not appear to be time dependant despite drawing the appropriate _simulink matrices from the workspace. This is most likely some kind of conversion issue between time in seconds in code and time measured in the simulinks themselves
  5. Matlab drive
    1. All of the following files have been submitted on matlab drive and clickup under “Simulations -> PV+Battery Simulink”

To be continued:

  • Fix the aforementioned issue 4d.
  • Test and see if these values make sense. Compare the 2 versions for both.
  • Discuss if this is a good standard for all parts.