RnD/generalFunctions
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ae30cef89c6f1e72d15a7e8b392b5077e80797e3
generalFunctions/datasets/assetData/curves/pik300.json

40 lines
3.0 KiB
JSON
Raw Normal View History

feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
{
"_meta": {
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"supplier": "Sulzer ABS",
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"type": "Disc",
"model": "PIK300",
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"membrane": "Perforated EPDM",
"membraneArea_m2_per_element": 0.07,
"membraneArea_m2_per_element_note": "Sulzer ABS PIK/PRK 300 mm fine-bubble disc, ~295 mm active membrane diameter (π × 0.1475² ≈ 0.068 m², rounded to 0.07 m²). Confirm against Sulzer spec sheet if available.",
"stdAir": { "temp_C": 0, "pressure_mbar": 1013.25, "RH_pct": 0 },
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"coverageBasis": "bottom-coverage-pct",
"coverageReference": [5, 10, 15, 20, 25],
"dataQuality": "multi-coverage",
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"xAxisBasis": "per-m2-membrane-Nm3h",
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"yAxisBasis": "ssotr-g-per-Nm3-per-m",
"waterDepth_m": 4.0,
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"source": "'PIK & PRK300 data from QM.xlsx' (Sheet1). Sister model PRK300 shares the SOTE/SSOTR curves; only DWP differs (PIK300 = perforated EPDM, PRK300 = perforated PUR).",
"note": "Native data was Sm³/h/disc on X and g O₂/(Sm³·m) on Y (US standard, 20 °C, 1.204 kg/Sm³ → 278.6 g O₂/Sm³). Converted to canonical Nm³ basis (DIN-1343, 0 °C, 1.293 kg/Nm³ → 299.0 g O₂/Nm³): X × 0.9319 / 0.07, Y × 1.0732. Water depth ≈ 4.0 m falls out of the SOTE↔SSOTR ratio under Sm³ conventions — verify if precision matters."
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
},
"sote_curve": {
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"5": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [27.87, 26.99, 25.80, 24.97, 24.38, 23.89, 23.46, 23.12] },
"10": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [30.18, 29.33, 28.15, 27.33, 26.73, 26.21, 25.83, 25.49] },
"15": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [31.51, 30.53, 29.16, 28.27, 27.57, 27.01, 26.55, 26.15] },
"20": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [32.52, 31.39, 29.88, 28.84, 28.06, 27.45, 26.92, 26.49] },
"25": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [33.26, 32.04, 30.39, 29.27, 28.45, 27.77, 27.22, 26.76] }
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
},
"otr_curve": {
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"5": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [20.937, 20.276, 19.382, 18.759, 18.316, 17.947, 17.624, 17.369] },
"10": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [22.673, 22.034, 21.148, 20.532, 20.081, 19.690, 19.405, 19.149] },
"15": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [23.672, 22.936, 21.907, 21.238, 20.712, 20.291, 19.946, 19.645] },
"20": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [24.431, 23.582, 22.447, 21.666, 21.080, 20.622, 20.224, 19.901] },
"25": { "x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49], "y": [24.987, 24.070, 22.831, 21.989, 21.373, 20.862, 20.449, 20.104] }
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
},
"p_curve": {
"0": {
refactor(curves): canonical axis Nm³/(h·m² membrane) for all diffuser suppliers Previously each curve file stored x in whatever convention the vendor used (per-element Nm³/h for Jäger/GVA, per-element Sm³/h for PIK/PRK, per-m² for Aerostrip). That meant the diffuser physics couldn't read the data uniformly — selecting Aerostrip vs Jäger would feed wildly different axes to the same interpolator. All five curves now use the same canonical X: specific air flux in Nm³/(h·m² membrane). Y stays SSOTR in g O₂/(Nm³·m); coverage % is the parametric key. Per-file conversions: - jaeger-jetflex-td-65-2-g-epdm-1000: x divided by 0.18 m² perforated area (stated on the data sheet). - gva-elastox-r: x divided by 0.18 m² placeholder mirroring Jäger TD-65 (no real GVA sheet exists — see _meta note). - aerostrip-phoenix: native already in Nm³/(h·m²) — no x change. _meta area normalised to 1.0 m² per "element" so users set `elements` = total installed membrane area in m². - pik300, prk300 (Sulzer ABS 300 mm disc): native was Sm³/h/disc on X and g O₂/(Sm³·m) on Y. Converted to canonical Nm³ basis (DIN-1343) by X × 0.9319 / 0.07, Y × 1.0732. Each disc = 0.07 m² membrane. Supplier naming fixed: pikprk → sulzer, aquaconsult → aquaconsult-entec. PIK = perforated EPDM, PRK = perforated PUR. Config schema: new diffuser.membraneAreaPerElement field (nullable, default null) so a node can override the curve's stored area. When null, specificClass reads _meta.membraneArea_m2_per_element from the resolved curve. 246/246 generalFunctions tests still pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 18:16:34 +02:00
"x": [19.97, 26.62, 39.93, 53.24, 66.56, 79.87, 93.18, 106.49],
"y": [25.5, 26.0, 27.5, 30.3, 34.0, 39.0, 45.0, 52.0]
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
}
}
}
Reference in New Issue Copy Permalink