Files
generalFunctions/datasets/assetData/curves/gva-elastox-r.json

30 lines
1.5 KiB
JSON
Raw Permalink 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": {
"supplier": "GVA",
"type": "Tube",
"model": "ELASTOX-R",
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
"membraneArea_m2_per_element": 0.18,
"membraneArea_m2_per_element_source": "placeholder — mirror of Jäger JetFlex TD-65-2-G EPDM 1000 mm (0.18 m²) until a real GVA ELASTOX-R sheet is supplied. Change here when the real value is known; specificClass reads it from this _meta field.",
"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": null,
"dataQuality": "point",
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": null,
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
"note": "Migrated 2026-05-12 from nodes/diffuser/src/specificClass.js _loadSpecs(); the legacy '2.4 elements/m²' tag was a prior mis-conversion of the % bottom-coverage convention. Single-coverage point estimate (key '0' = unspecified). Native data was per-element Nm³/h; converted to per-m²-membrane Nm³/(h·m²) by dividing by the placeholder 0.18 m² element area — those numbers will shift the moment we get a real GVA sheet."
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": {
"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": [11.11, 16.67, 22.22, 27.78, 33.33, 38.89, 44.44, 50.00, 55.56],
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
"y": [26, 25, 24, 23.5, 23, 22.75, 22.5, 22.25, 22]
}
},
"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": [11.11, 16.67, 22.22, 27.78, 33.33, 38.89, 44.44, 50.00, 55.56, 61.11, 66.67],
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
"y": [40, 42.5, 45, 47.5, 50, 51.5, 53, 54.5, 56, 57.5, 59]
}
}
}