No nesting subsector for some GCAM-USA states

[chloe-fauvel]

Hi, I have noticed that there are some states that do not have a nesting-subsector structure, making parsing through query output difficult for all 51 GCAM-USA states. The states are:

• CA
• FL
• GA
• IA
• LA
• MO
• NC
• OH
• TX

It did not seem related to electric grid, so is there any reason for this?

Thank you! Chloe Fauvel

[ssmithClimate]

Could you be more specific about what sector(s)/subsector(s) you are seeing this for?

[mbins]

It may also be helpful to specify which version of GCAM you're using (I assume GCAM v5.4, but are there any modifications?) and to share the configuration file for the run where you're seeing no nesting-subsector structure in some states.

[chloe-fauvel]

Here is an example from a scenario without DAC deployment: queryout_CO2_emissions_by_tech_states.csv. I am also seeing this in input_by_tech_states.

I am using GCAM v5.4 with this configuration_usa.xml.txt (I commented out transportation files in the config file because I was varying base/high EV transport scenarios in my batch file).

As an aside, I am not seeing any nesting-subsector structure in scenarios with DAC deployment: queryout_CO2_emissions_by_tech_states.csv where DAC scenarios include these files in the batch file:

<Value name = "dac_base">../input/gcamdata/xml/dac_ssp2.xml</Value> <Value name = "dac_usa">../input/gcam_addons/dac/dac_USA.xml</Value> <Value name = "dac_usa_ccoef">../input/gcam_addons/dac/Ccoef-dac-state-airCO2.xml</Value>

[ssmithClimate]

Note that, to reduce size, the GCAM XML output does not contain values when they are zero. Is that what you are seeing perhaps?

[mbins]

Hi Chloe, thanks for the additional info. I don't see anything in the configuration files that would cause this. I spot checked elec_segments_water_USA.xml... CA & FL both do have the nesting subsector structure here.

I suspect this may be related to the way you're running the queries. Please see my last comment on https://github.com/JGCRI/gcam-core/issues/161. In a file you shared in that thread, you use a query file (query_CO2_emissions_by_tech_states_shree.xml.txt) that has an individual query for each state, which I assume are run individually and then concatenated into a single file. Check whether your queries in the file you're currently using are different for the states you list above than for the others which print the full nesting-subsector detail. That's my best guess as to the different level of details being printed in queryout_CO2_emissions_by_tech_states.csv.