Skip to content

Adding new commodity tracked by <minicam-energy-input> produces "non-existant market X-fixed-output" error at first future period #623

Description

@ikukula-ship-it

Hi GCAM team,
I'm building a simplified version of the Qiu et al. (2024) mineral branch for my dissertation. The goal is accounting-only: track consumption of two new commodities (Al_mineral and Cu_mineral) by clean electricity technologies (CSP, CSP_storage, PV, PV_storage, rooftop_pv, wind, wind_offshore, wind_storage) across all 32 GCAM regions for periods 1975-2100. SSP4 reference scenario, GCAM v6.0.

Setup:
Supply file: 32 regional blocks, each with (and same for Cu_mineral) using global, tax, non-binding constraints, mirroring the pattern in Qiu's aluminium_supply_constraint_his.xml.
Inputs file: adds to the clean electricity stub-technologies starting period 2020.

Error:
Periods 0-4 (1975-2015) solve normally. Period 5 (2020) immediately produces:
Period 5: 2020
Called for price of non-existant market Al_mineral-fixed-output in region USA
Called for price of non-existant market Al_mineral-fixed-output in region USA
[repeats for all 32 regions]

What I've ruled out:
Name collision with the standard aluminum sector — error persists after renaming aluminium → Al_mineral (and copper similarly).
Tag-name issues — switching → had no effect on this error.
Historical-period inputs — leaving 1975-2015 untouched is intentional.

Hypothesis:
Qiu's constraint files contain , implying some prior file creates the unlimited-resource that the constraint then modifies. I cannot find a static XML in Qiu's branch that creates the resource, only deletions. Is this resource declaration generated dynamically by gcamdata R code, and if so, what is the minimal XML-only equivalent needed to wire a new commodity into GCAM so that price lookups succeed?
**

cu_al_supply_v5.xml

cu_al_inputs_accounting_v4.xml

batch_SSP_REF_cual_accounting.xml

** v5 supply file, v4 inputs file, batch file.
Thanks for any guidance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions