If the scenario tools are run for a scenario to obtain query results, using pipenv run scenario_from-csv query_only local, the output looks like this:
,test_scen,nl2019_present,unit
query_1,query_1_value_future,query_1_value_present,query_1_unit,
query_2,query_2_value_future,query_2_value_present,query_2_unit,
...
query_n,query_n_value_future,query_n_value_present,query_n_unit
When the query type is a curve however, the entire curve is pasted as a list in the output:
,test_scen,nl2019_present,unit
hourly_co2_intensity_of_electricity_production,"[412.94503653494974, 411.78823033221573,...,489.87239458403224]",[],
Retrieving the query results then becomes a hassle, as you have to process two types of output within a single output CSV. To improve this, we can separate the output into two files. One CSV file that shows query results for queries with the type 'value' and another for the type 'curve'. The 'curve' type output may look like this:
query_1_future_curve,value_hour_1,value_hour_2,...,value_hour_8760,
query_2_future_curve,value_hour_1,value_hour_2,...,value_hour_8760
@redekok what do you think about this format suggestion?
If the scenario tools are run for a scenario to obtain query results, using
pipenv run scenario_from-csv query_only local, the output looks like this:When the query type is a curve however, the entire curve is pasted as a list in the output:
Retrieving the query results then becomes a hassle, as you have to process two types of output within a single output CSV. To improve this, we can separate the output into two files. One CSV file that shows query results for queries with the type 'value' and another for the type 'curve'. The 'curve' type output may look like this:
@redekok what do you think about this format suggestion?