climatecompatiblegrowth/clicsand

clicsand's Issues

CC0-1.0 not usually recommended for software

Hi team. The Creative Commons CC0‑1.0 waiver was not designed for source code and is not usually recommended for source code either. For instance, CC0‑1.0 explicitly does not contain a patent grant (§4.a). That issue may not be a consideration for your use‑case. But code under CC0‑1.0 is not inbound compatible with the MIT license — or indeed any other common open source software license — and must therefore remain legally siloed here. A good place to study license texts is on the SPDX license list:

• https://spdx.org/licenses/

I suggest the project re‑licenses under MIT if at all possible. Otherwise, the wider issues are reviewed in the following publication, along with a diagram (fig 3) showing license compatibilities — while noting that diagram is unfortunately wrong in respect of CC0‑1.0:

• Morrison, Robbie (April 2018). "Energy system modeling: public transparency, scientific reproducibility, and open development". Energy Strategy Reviews. 20: 49–63. ISSN 2211-467X. doi:10.1016/j.esr.2017.12.010. Open access.

If you need further advice or help, feel free to ask. Robbie

source tree under git?

It may be more useful to place the source tree under git, rather than only provide this as archives? That would allow people to browse and more importantly submit fixes. Just a suggestion. Or am I missing something?

Add zenodo metadata file

Add a file called .zenodo.json in the repository root folder which looks similar to this (you'll need to add the other authors):

{
    "upload_type": "software",
    "creators": [
        {
            "name": "Abhishek Shivakumar",
            "affiliation": "ACME Ltd",
            "orcid": "0000-0002-2535-4134"
        },
    ],
    "access_right": "open"
}

This will then populate the metadata on zenodo when you create a new release.

ClicSANDs Output File Defenition

When using ClicSANDs to create a datafile, it seems like there is an issue where time-independent parameters that use only the default value definitions are not being written correctly. This may be even more specific to just where default values are zero, but Im not sure on that.

For example ModelPeriodExogenousEmission is defined in ClicSANDs as

And the definition looks correct in the ToDataFile tab:

However, when you look at the output data file it's defined as:

While this doesn't make a difference for processing the datafile with GLPK (or at least not that I can see), it is throwing an error if trying to convert it with otoole. Specifically, the amply library is having trouble processing it. If we comment out the data (such as shown below) or add in the zero data, otoole will work fine.

param ModelPeriodExogenousEmission default 0 :=
;

Is there a way we can update ClicSANDs to print out the full definition in the text file (ie. the definition shown below)?

param ModelPeriodExogenousEmission default 0 :
EMIC02 EMICH4 EMIFGA EMIN2O EMIREN :=
RE1 0 0 0 0 0
;

clicSAND fails with run-time-error-429

I am following the online course https://www.open.edu/openlearncreate/course/view.php?id=11534

When trying to run my first model (exercise three) it fails with the run time error 429 activex-component-can-t-create-object.

The log file says:

------------------------------------------------------------------------------------------------------------------------------------------------------
Data file: C:\Users\ufechner\Documents\HO3\SAND_Interface_HO3.xlsm.txt
Model file: C:\Users\ufechner\Documents\HO3\OSeMOSYS_code.txt
GLPSOL Output file: C:\Users\ufechner\Documents\HO3\SAND_Interface_HO3.xlsm.lp
Results file: C:\Users\ufechner\Documents\HO3\SAND_Interface_HO3.xlsm.results.txt
Log file: C:\Users\ufechner\Documents\HO3\SAND_Interface_HO3.xlsm20240218184403.log.txt
------------------------------------------------------------------------------------------------------------------------------------------------------
Error extracting data:
Exception from HRESULT: 0x800A9C68

Any idea?

I am using Windows 10 and Microsoft office professional plus 2021.