Calculation of transmission cost based on coordinates seems not working

[Longquan-Li]

What happened?

I compared two scenarios in my model, one with specified distance between two nodes while another one with only coordinates of the two nodes. The distance between the nodes is around 200 km. The results show that the transmission cost when I specify the distance is 200 times higher than the case with only coordinates, so probably the distance is not taken into account for the cost calculation in the scenario where I do not specify the distance. However, it is written in the documentation that nodes can optionally specify geographic coordinates (latitude and longitude) which are used to compute distances along transmission links, and distance is not a required parameter for transmission technologies

Which operating systems have you used?

• [X] macOS
• [ ] Windows
• [ ] Linux

Version

v0.7

Relevant log output

No response

[brynpickering]

The default distance unit is in km in v0.7, rather than m in v0.6 (see the init section of the configuration schema). Could this be the issue?

[Longquan-Li]

Thanks for replying. It doesn't seem related to the unit update. The problem in my previous report is in the second scenario where I do not specify the distance. The cost of transmission was expected to be the same or similar to the first scenario where I used the 'distance' parameter, but it turned out to be much lower, more likely to be the cost per distance.

To better elaborate the issue, I did another experiment. I found the cost of transmission does not change if I change the coordinates of the nodes.

[brynpickering]

distance should be calculated automatically in preprocessing. Without defining it explicitly yourself, what do you get when you call model.inputs.distance?

[Longquan-Li]

I am not running the model in an interactive way. If I save the results to csv files, I can's find an input_distance file in the results folder, neither in the Calligraph, without defining distance. With defined distance, I could see it in Calligraph.

[brynpickering]

Ok, and what does one of your nose definitions look like?

On Mon, Oct 14, 2024, 09:37 Longquan-Li @.***> wrote:

I am not running the model in an interactive way. If I save the results to csv files, I can's find an input_distance file in the results folder, neither in the Calligraph, without defining distance. With defined distance, I could see it in Calligraph.

— Reply to this email directly, view it on GitHub https://github.com/calliope-project/calliope/issues/697#issuecomment-2410444802, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEDB63THLYRQHRHMFBVEPV3Z3N7GHAVCNFSM6AAAAABPYXDXQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGQ2DIOBQGI . You are receiving this because you commented.Message ID: @.***>

[brynpickering]

Try 'longiture'->'longitude'

On Mon, Oct 14, 2024, 12:47 Longquan-Li @.***> wrote:

Groningen: latitude: 53.2194 longiture: 6.5665 techs: demand_heat: demand_electricity: demand_DH: P2HH: heat_removal: electrolyser:

chp:

chp_DH: hydrogen_cavern: hydrogen_tank: heat_storage_small: heat_storage_small_DH: hp: heat_recovery: hp_DH: electric_heater: electric_heater_DH: heat_storage_large: heat_storage_large_DH: heat_storage_large_waste: battery: pv_openfield: wind_onshore: wind_offshore:

Industry: latitude: 51.7654 longiture: 4.5096 techs: demand_hydrogen: electrolyser: hydrogen_tank: battery:

— Reply to this email directly, view it on GitHub https://github.com/calliope-project/calliope/issues/697#issuecomment-2410978916, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEDB63URTZNGSQKV4FBVRXDZ3OVMXAVCNFSM6AAAAABPYXDXQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQHE3TQOJRGY . You are receiving this because you commented.Message ID: @.***>

[Longquan-Li]

Problem solved, sorry for my carelessness and thank you